> The SheevaPlug interface is now unusable since rev 2573: > > Error: unable to open ftdi device: device not found > Runtime error, file "command.c", line 469: > > Backing out changes from that revision does indeed fix the issue. > So what was the point of that patch? >
The original patch was to cleanup the cfg to use standard naming: -ft2232_device_desc "Olimex OpenOCD JTAG TINY A" +ft2232_device_desc "Olimex OpenOCD JTAG TINY" as openocd now will add the A as required fow win32 ftd2xx drivers. I removed the B from ShevaPlug as this does not make sense, eg. the MPSSE cannot be on ChannelB in the FT2232D. If you are saying the line 'ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"' works then ok i will revert that part. Just out of curiosity what os/driver are you using? Cheers Spen _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
