On Wed, Jun 27, 2012 at 8:51 PM, Vivien Giraud <[email protected]> wrote: > On 27/06/2012 14:44, Xiaofan Chen wrote: >>>> Which FT2232 chip are you using? >>> >>> That's a FT2232HL but I don't understand why when I make a 'lsusb' I've >>> receive this : >>> >>> Bus 001 Device 039: ID 0403:6010 Future Technology Devices International, >>> Ltd FT2232C Dual USB-UART/FIFO IC >>> That's not a FT2232C this is a HL >> >> 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. > > Yes it use the default PID & VID, unfortunatly I can't change VID/PID > because we use it in my company and we got tons of it (and we built some > every time) > So I think I will let's my 'hack' in order to work well for me :) > Thanks a lot Xiaofan !
I see. Still maybe the OpenOCD codes should still be able to detect the device as FT2232H. What is the full output of "lsusb -vvv -d 0403:6010" for your device? >>> PS: I have commit a patch yesterday (with git commit -a) is it the good >>> command ? Where can I see if someone have accepted it ? >> >> Did you use the Gerrit? >> >> http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=blob;f=HACKING;hb=HEAD > > Thanks for the link ! -- Xiaofan ------------------------------------------------------------------------------ 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
