Hello Christian, On Thursday 07 August 2008 04:06:53 Christian Jaeger wrote: > I had been using (amongst a few other settings) this config at first: > > interface ft2232 > ft2232_device_desc "Olimex OpenOCD JTAG TINY" > ft2232_layout olimex-jtag > > where the desc was taken from /sys/bus/usb/devices/*/product, but it > wasn't clear from the example that ft2232_vid_pid is mandatory (*and* > ft2232_device_desc needs to be correct at the same time).
The problem is with the Windows version of the FTD2XX driver - on Windows you don't need the vid/pid at all, because the driver registers itself for a particular vid/pid combination. Additionally, you need the " A" appended on Windows, because that's how the Windows driver detects the difference between channel A (the one that does JTAG) and channel B (limited to RS232 or GPIO). On Linux you need the vid/pid, unless your device uses the FTDI default combinations. The driver probes the default plus any combination listed in the config file (could be more than just one). Additionally you need the device description (or serial number, which takes precedence over description). > (BTW turns out, by looking at the output from the -d option and a > quick look at the sources, that it was looking for the default(?) vid > / pid numbers which are hard coded (0x0403 / 0x6010).) > > In the following two mails I post patches to fix the example config > file, first I rename it to drop the -a (maybe I just don't see what > this was about), then the relevant changes. (These are formatted by > git format-patch, tell me if you're not happy with that sort of > patches.) It's probably not much use fixing the config files, because they're not really broken. A patch that adds some comments would be highly welcomed of course. Regards, Dominic _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
