On 27/06/2012 15:31, Spencer Oliver wrote: > On 27 June 2012 13:44, Xiaofan Chen<[email protected]> wrote: >> Hmm, this is not good, which means that your device use the default >> FTDI VID/PID which is 0403:6010. Please try to program the EEPROM >> with a proper VID/PID. >> >> > the VID/PID do not matter for the high speed detection. > If the ftdi lib used supports high speed then the jtag interface will > be queried for it type. > > If debug info is enabled then info should be printed out, eg. FTDI > chip type: 4 "2232H" > > Spen OH GREAT I've got this : Debug: 204 283 ft2232.c:2285 ft2232_init_libftdi(): FTDI chip type: 5000 "Unknown" -_-'' Think we got a big deal ! I use libftdi-0.99 My other prod tools won't work correctly since I I have installed this one, that's why I really need to make openocd static
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
