+++ Laurent Gauch [2009-10-23 16:44 +0200]:
> It is very *HELPFUL* to have the -2 after the Amontec JTAGkey-2 and
> the -2P after the Amontec JTAGkey-2P . This will really help the
> end-user when using multiple Amontec JTAGkey generation dongle from
> the same computer ( from the same USB HOST), and this can help custom
> software too.
To use multiple jtagkeys from one USB host you need to use
ft2232_serial to distinguish between different devices of the same
type. OK, if your two devices happen to have different
ft2232_device_desc strings then you don't need ft2232_serial, but in a
production environment chances are you actually have two identical
devices so have to use the serial config. I am setting this up here
now and there is no way I can arrange each station to have one jtagkey-1
and one jtagkey-2, so the _serial ID is the thing that maps dongles to
stattions. I've set up my jtagkey2.cfg to look like this:
ft2232_device_desc "Amontec JTAGkey-2"
ft2232_layout jtagkey
ft2232_vid_pid 0x0403 0xcff8
if { [info exists FT2232_SERIAL] } {
ft2232_serial $FT2232_SERIAL
}
So that if FT2232_SERIAL is defined in the top-level config then it
gets used.
In this case the two different device_description strings just mean I
get to have two different configs that are exactly the same except for
the "-2" and have to make sure that every invocation of openocd
(there are many) uses the correct config file to source the
corresponding jtagkey config. Can a jtagkey and a jtagkey-2 have the
same serial number? If not then I still don't see how the distinction
actually helps.
For the normal case of one dongle I'd actually like openocd to get a
bit smarter and just use 'the first jtag dongle it can find' so that I
didn't have to maintain top-level configs for jtagkey, jtagkey2,
olimex-tiny etc. I couldn't see an obvious way to do that, which is a
pity, althoguh I suspect some udev magic might do it (much easier if
each device actually has a unique pid).
> Also, it is wonderful to have the same PID VID for the
> Amontec JTAGkey and Amontec JTAGkey-2 for software compatibility. This
> will stay true for the comming Amontec JTAGkey-3 with POWER CONTROL
> support and SWD support for ARM cortex serial wire debug with JTAG IO
> Voltage down to 0.9V !
Hmm, well, I can see how it helps unfortunates using Windows where
usb-driver installation is such a pain, but I'm not convinced for the
Linux libftdi case. Still, it's not my call.
Wookey
--
Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian
http://wookware.org/
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
