Rick Altherr wrote: > You should be able to handle this like all the other chips that have > RTCK. They use 'jtag_khz 0'.
I think I need to buy new glasses ;) Thanks for this hint, I saw what you meant and did it that way. > form of intelligence in the driver about what device it is talking to > and what it is capable of is much nicer for the user. I currently using the FT2XX lib from FTDI and found a command to get the chip id. The id is different for the FT2232C/D/L (=4), FT2232H (=6) and FT4232H (=7). That's all I need. Holger Schurig wrote: > For example, my Olimex ARM-USB-TINY has ftdic.type == 2 and > ftdi_read_chipid() == 0xa5abd789. > However, I'm quite unsure if the latter isn't just garbage. Maybe > you simply use the USB VID/PIDs to differentiate the chips. .type looks a bit different from that FT2XX values. Maybe they use a different system to number the chips, will have a look at it, thanks for the hint. The chipid could be a unique id for every chip. Joern _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
