Home › Forums › Product support › RapidiTTy Builder › Problem …

Problem with Olimex ARM-USB-OCD

Thu, 08/14/2008 - 11:12 — Kam

Hi all, I have an Olimex ARM-USB-OCD with a hardware ID (VID_0403&PID_6010&MI_00) which differs to the driver (VID_15ba&PID_0003&MI_00) provided by RapidiTTy Builder 1.0. After modifications, the driver for the device was installed. However, RapidiTTy Builder still can’t communicate with the device.

Does anyone have any idea how to get this problem solved?

Thanks, Kam

‹ RapidiTTy Builder crashed! RapidiTTy Builder 1.02 adds support for Amontec JTAGkey ›
Thu, 08/14/2008 - 11:23 — dayavoo

Kam, processor are you trying

Kam, processor are you trying to connect to?

—

Dev

Thu, 08/14/2008 - 11:26 — Pete

Further details

Kam,

It would help if you could let us know what modifications you made in order to install the driver, and what error you are getting from OpenOCD when you try to connect. Often the problem lies in the OpenOCD script being used — that would be the first thing that I would check.

—

Peter J. Vidler
Senior Systems Developer, TTE Systems Ltd

Thu, 08/14/2008 - 13:35 — Kam

Hi Dev and Pete, I was

Hi Dev and Pete,

I was trying to connect to the LM3S8962 from Luminary Micro. For installing the driver, I modified the hardware ID on all .inf and .ini files in the RapidiTTyBuilder\OpenOCD\driver\arm_usb_ocd folder.

I got the error message saying “Unable to connect to the board - please make sure the right development board is powered up and is connected to the computer using the right cable”. In the RapidiTTy Builder’s console, it showed the messages as follows:

Info: openocd.c:93 main(): Open On-Chip Debugger (2007-12-30 17:00 CET) svn: 247 Info: openocd.c:94 main(): $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ Error: ft2232.c:1381 ft2232_init_ftd2xx(): unable to open ftdi device: 2 Error: ft2232.c:1396 ft2232_init_ftd2xx(): ListDevices: 4

Error: ft2232.c:1398 ft2232_init_ftd2xx(): 0: Dual RS232 A Error: ft2232.c:1398 ft2232_init_ftd2xx(): 1: Dual RS232 B Error: ft2232.c:1398 ft2232_init_ftd2xx(): 2: Stellaris Evaluation Board A Error: ft2232.c:1398 ft2232_init_ftd2xx(): 3: Stellaris Evaluation Board B

It seems not recognise the Olimex openOCD device.

Thanks,

Kam

Thu, 08/14/2008 - 13:49 — Pete

Settings

The VID and PID settings should be set in the arm_usb_ocd.cfg file… I don’t see why you would need to alter the .inf or .ini files at all. The version of OpenOCD you have is likely to be a little out of date — you could try installing drivers from a newer version (you will still need the old version for use with RapidiTTy, at least until the next release).

Also, you will probably need to modify the arm_usb_ocd.cfg script, changing the following line:

  1. ft2232_vid_pid 0x15BA 0x0003

It’s a bit odd for vendor and product IDs to change though — are you sure this is an Olimex ARM-USB-OCD device (and how did you find those values)? There is also an ARM-USB-TINY, which is not yet supported…

—

Peter J. Vidler
Senior Systems Developer, TTE Systems Ltd

Thu, 08/14/2008 - 14:10 — Kam

The device Id can be viewed

The device Id can be viewed in the Device Manager (properties->details->hardware Id) when the device is plugged into the USB port.

I have checked with other members in the lab. The Olimex device they are using have the same hardware ID as the ID in the driver, but is different to the one I am using.

Kam

Thu, 08/14/2008 - 14:15 — Pete

Device IDs

Presumably the device did install successfully for you to be able to access it in the Device Manager? I’m not clear on what exactly prompted you to change the .inf files, as this should never really be necessary (and will almost certainly cause problems). Is your device newer/older than the others in your lab? If not, it is possible that the hardware could be broken in some way.

That said, please try changing the line mentioned above in arm_usb_ocd.cfg and see if it makes a difference.

—

Peter J. Vidler
Senior Systems Developer, TTE Systems Ltd

Thu, 08/14/2008 - 14:57 — Kam

When the device plugged into

When the device plugged into the USB port, Windows requested for installing the driver for the device. The installation was failed, because the hardware ID written in the .inf file does not match to the device Id. Therefore, it is necessary to modify the .inf file in order to match the actually device id. I think the device I am using is an old version one as I got it nearly a year ago.

I have modified the stm32f10x_armusbocd.cfg file currently using in the project with the same hardware ID as the device, but it still failed to communicate with device.

Thanks,

Kam

Thu, 08/14/2008 - 16:04 — Kam

It is working now!!

Dear Dev and Pete,

I finally realized my ARM-USB-OCN is a faulty device. After I replace it with a new one, RapidiTTy Builder works perfectly.

Thank you very much for your help!

Kam