EmbeddedRelated.com
Forums
The 2024 Embedded Online Conference

Can't install driver for Olimex ARM-USB-TINY

Started by "Dan J." November 10, 2008
Hello,
I just got an Olimex SAM7 board and their ARM-USB-TINY JTAG interface
yesterday and am trying to set up the OpenOCD driver and Yagarto.

I'm stuck trying to install the USB driver for the ARM-USB-TINY. I've
tried the one from the CD from Olimex with the ARM-USB-TINY and a
later version.

Windows sees the new USB device and brings up the "hardware update
wizard", I point it to search in the OpenOCD driver directory:

"C:\Program Files\openocd-r717\driver\arm_usb_ocd" and it doesn't find
a driver. (Message reported: "The hardware was not installed because
the wizard cannot find the necessary software."

I also tried with the (apparently) older version from the Olimex CD
"C:\Program Files\openocd-2007re204\driver\arm_usb_ocd" with the same
result.

(I'm running windows XP SP3)

Has anyone successfully installed the OpenOCD driver for the Olimex
ARM-USB-TINY, if so how? Is there another version somewhere?

I have had the same problem when moving Yagarto to a new machine.

I think the problem is that the JTAG TINY's USB product ID is different from that of the driver, so Windows keeps asking for it. I believe the correct values (in a working .gdbinit) for the ARM-USB-TINY-A are:

#interface
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY A"
ft2232_layout "olimex-jtag"
ft2232_vid_pid 0x15BA 0x0004

The driver I loaded from C:\openocd-r717\driver\arm_usb_ocd has a product id of 0x0003 instead of 0x0004. I suspect you could just edit ftdibus.inf, add new lines defining the correct VID and PID, and try it again. There are at least two lines to be added:

[OlimexHw]
%USB\VID_15ba&PID_0003&MI_00.DeviceDesc%=FtdiBus,USB\VID_15ba&PID_0004&MI_00
%USB\VID_15ba&PID_0003&MI_00.DeviceDesc%=FtdiBus,USB\VID_15ba&PID_0004&MI_01

and near thje bottom in section [Strings]

USB\VID_15ba&PID_0004&MI_00.DeviceDesc="Olimex OpenOCD JTAG TINY Interface"
USB\VID_15ba&PID_0004&MI_00.DeviceDesc="Olimex OpenOCD JTAG TINY"

Hope this helps...

Chris

----- Original Message -----
From: Dan J.
To: A...
Sent: Sunday, November 09, 2008 2:39 PM
Subject: [AT91SAM] Can't install driver for Olimex ARM-USB-TINY
Hello,
I just got an Olimex SAM7 board and their ARM-USB-TINY JTAG interface
yesterday and am trying to set up the OpenOCD driver and Yagarto.

I'm stuck trying to install the USB driver for the ARM-USB-TINY. I've
tried the one from the CD from Olimex with the ARM-USB-TINY and a
later version.

Windows sees the new USB device and brings up the "hardware update
wizard", I point it to search in the OpenOCD driver directory:

"C:\Program Files\openocd-r717\driver\arm_usb_ocd" and it doesn't find
a driver. (Message reported: "The hardware was not installed because
the wizard cannot find the necessary software."

I also tried with the (apparently) older version from the Olimex CD
"C:\Program Files\openocd-2007re204\driver\arm_usb_ocd" with the same
result.

(I'm running windows XP SP3)

Has anyone successfully installed the OpenOCD driver for the Olimex
ARM-USB-TINY, if so how? Is there another version somewhere?

--------

7:53 AM
Before I got the suggestion from Chris (partial below), I suspected
this was the problem and edited the PID in the ftd2xx.inf file (not
the ftdibus.inf file).

This allow the driver to install, (but I'm not far enough along to
check that it works yet).

The problem was after I rebooted, windows (xp Sp3) again looked for
driver for "new hardware", and I went through the same procedure as
before (with the ftd2xx.inf file now edited) and it could not find
driver. So I changed just the PID references in ftdibus.inf from
0x0003 to 0x0004, and then it found a driver.

Does the system need both of these or just one. If so which one?

If you have ARM_USB_TINY actually working, could you check (control
panel, system, hardware, device manager) and see where it shows up?
And verify which driver files are loaded (ftdibus or ftd2xx, or both)?

In the first case I had an entry under "Other Devices",

Now I have entries under Universal Serial Bus Controllers:
"Olimex OpenOCD JTAG Interface"
"Olimex OpenOCD serial driver"

I also found an handy "USBView" utility on the ftdichip.com website
that shows the VID and PID and other parameters of each connected USB
device. This verified that I indeed want Vid 0x15ba Pid 0x0004 which I
got a clue about from the Olimex website.

I noticed ftdi has a new combined driver that may avoid the confusion
over which driver to use, but I'd need to edit the inf files for that
also to get the correct VID and PID unless Olimex takes care of it.

Thanks for the help,
Dan
--- In A..., "Chris DeLise" wrote:
>
> I have had the same problem when moving Yagarto to a new machine.
>
> I think the problem is that the JTAG TINY's USB product ID is
different from that of the driver, so Windows keeps asking for it. I
believe the correct values (in a working .gdbinit) for the
ARM-USB-TINY-A are:
>
> #interface
> interface ft2232
> ft2232_device_desc "Olimex OpenOCD JTAG TINY A"
> ft2232_layout "olimex-jtag"
> ft2232_vid_pid 0x15BA 0x0004
>
> The driver I loaded from C:\openocd-r717\driver\arm_usb_ocd has a
product id of 0x0003 instead of 0x0004. I suspect you could just edit
ftdibus.inf, ......

The 2024 Embedded Online Conference