HI,
I don't know if this will help but the help page on your calbe states
you need to use lowercase characters
jtag> cable gnICE+ help
Usage: cable gnICE+ [vid=VID] [pid=PID] [desc=DESC]
[interface=INTERFACE] [driver=DRIVER]
VID USB Device Vendor ID (hex, e.g. 0abc)
PID USB Device Product ID (hex, e.g. 0abc)
DESC Some string to match in description or serial no.
INTERFACE Interface to use (0=first, 1=second, etc).
DRIVER usbconn driver, either ftdi-mpsse or ftd2xx-mpsse
Default: vid=456 pid=f001 driver=ftdi-mpsse
try:
cable gnICE+ vid=15ba pid=002a
Greetings
On Sun, Aug 5, 2012 at 7:08 AM, Elden Tyrell <eldentyr...@fastmail.fm> wrote:
> This has been bugging me for some time...
>
> Has anybody noticed that you can't actually use the VID/PID arguments to
> override the built-in USB ids for libftdi-based cables? This is really
> unfortunate, because a lot of cables out there are just knock-offs of some
> existing urjtag-supported cable with the VID/PID changed.
>
> Here's an example: I have an Olimex ARM-USB-OCD-H (FT2232H).
>
> $ lsusb | grep -i olimex
> Bus 002 Device 006: ID 15ba:002a Olimex Ltd.
>
> It isn't recognized by urjtag svn-2026 as either an ARM-USB-OCD-H or a gnICE+:
>
> UrJTAG 0.10 #2026
> Copyright (C) 2002, 2003 ETC s.r.o.
> ...
> jtag> cable ARM-USB-OCD-H
> error: Couldn't connect to suitable USB device.
> error: ftdi/ftd2xx error: ftdi_usb_open_desc() failed: device not found
> ...
> jtag> cable gnICE+
> error: Couldn't connect to suitable USB device.
> error: ftdi/ftd2xx error: ftdi_usb_open_desc() failed: device not found
>
> jtag> cable gnICE+ VID=15ba PID=002a
> error: Couldn't connect to suitable USB device.
> error: ftdi/ftd2xx error: ftdi_usb_open_desc() failed: device not found
>
> On the other hand if I change the VID and PID in the source code like this:
>
> svn diff src/tap
> Index: src/tap/cable/ft2232.c
> ===================================================================
> --- src/tap/cable/ft2232.c (revision 2026)
> +++ src/tap/cable/ft2232.c (working copy)
> @@ -2353,7 +2353,7 @@
> ft2232_flush,
> ftdx_usbcable_help
> };
> -URJ_DECLARE_FTDX_CABLE(0x0456, 0xF001, "-mpsse", "gnICE+", gniceplus)
> +URJ_DECLARE_FTDX_CABLE(0x15ba, 0x002a, "-mpsse", "gnICE+", gniceplus)
>
> const urj_cable_driver_t urj_tap_cable_ft2232_jtagkey_driver = {
> "JTAGkey",
>
> ... it works perfectly!
>
> jtag> cable gnICE+
> Connected to libftdi driver.
> jtag> idcode
> Reading 0 bytes of idcode
> Read 10010011(0x93) 11010000(0xd0) 00000001(0x01) 00110100(0x34)
> 00000000(0x00) 00000000(0x00) 00000000(0x00) 00000000(0x00)
>
> So, my question: why are the runtime VID/PID parameters ignored?
>
> Thanks,
>
> - e
>
>
> ------------------------------------------------------------------------------
> 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/
> _______________________________________________
> UrJTAG-development mailing list
> UrJTAG-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/urjtag-development
------------------------------------------------------------------------------
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/
_______________________________________________
UrJTAG-development mailing list
UrJTAG-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/urjtag-development
