JTAG USB OCD Tiny drivers

Development Boards MicroMod
21

Now I just have to figure out what settings are needed for my LPC2148

Header Board and make an OpenOCD configuration file for it.

You can find some example configs at http://openfacts.berlios.de/index-en.ph … CD_scripts

The configuration options are explained at http://openfacts.berlios.de/index-en.ph … figuration

I also need to get my header board powered - not sure if it can be

powered from JTAG. I am brand new to this with ARM.

It’s the other way round - several JTAGs can be powered from the board, and others, like the ARM-USB-TINY, use the voltage from the Vref pin to determine the voltage level at which the JTAG port operates.

Regards,

Dominic

22

I think I am almost there now. :smiley:

I am getting:

Info:    openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST)
Error:   ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi device: 1

when OpenOCD starts, but do not know what this means. OpenOCD does startup though, which is more progress. :slight_smile:

8-Dale

23

Change the line to change the PID in the config file also.

interface ft2232

ft2232_device_desc “Olimex OpenOCD JTAG TINY A”

ft2232_layout “olimex-jtag”

ft2232_vid_pid 0x15BA 0x0004

jtag_speed 3

24

hi people,

i have the same problem, and im struggling with this since long, i consulted assitance from olimex but that did not help either.

When i plug in the OLIMEX ARM-USB_OCD (not tiny) windows is first of all not asking for any driver installing it byself as a USB Combined Device, and the LED is lighting red on the ARM-USB_OCD. Then i try to install it by myself, i show windows the location as “C:\GCCFD\Olimex OpenOCD Driver” which came with the OLIMEX-GCCFD-190207.exe installer. This setup supplied by olimex is telling at the end of the installation that the driver has to be installed 3 times “and that it is not a joke”. In the driver folder there are “FTDIBUS.INF” and “FTDIPORT.INF” files. Ok, then i show windows this folder but windows is telling me that it cant find a better driver than the one installed now(USB Combined Device). So i try it with “Dont look, i will choose the driver to be installed option”. Then i tryied it this way, and installed “FTDIBUS.INF” and “FTDIPORT.INF” 3 times, since olimex is not telling which one to install 3 times, but this too is not helping.

Then i downloaded the drivers from FTDI directly, but these you can absolutely not install, so what am i to do? im helpless, i spend some bugs on this tool to go on developing with ARM.

I also noticed that there is no voltage output on the device.

So any help would really be apreciated. :frowning:

25

avioneer:
Then i tryied it this way, and installed “FTDIBUS.INF” and “FTDIPORT.INF” 3 times, since olimex is not telling which one to install 3 times, but this too is not helping.

You do not need to install each driver 3 times, you need to install 3 separate drivers. You only mentioned 2 of the drivers in your message but there are 3 drivers that need to be installed. The INF files for the installation are all in the ARM_USB_OCD directory under the DRIVER directory included in the directory where you installed OpenOCD. There are 3 INF files called “ftd2xx.inf”, “Ftdibus.inf”, and “Ftdiport.inf”. Just right click on each of the 3 INF files and select install from the drop down menu that appears. That’s it! All 3 drivers are installed.

–Dave

26

thanks Dave for your reply,

i installed all the 3 drivers as you said but its not helping, no change is happening, i unplug it and plug the device again, but windows is reporting me there was a problem initiating the device and still recognizing it as a usb composite device. The three inf files i found in “C:\GCCFD\Olimex OpenOCD Driver\Olimex OpenOCD driver_old”.

tarik

27

avioneer:
thanks Dave for your reply,

i installed all the 3 drivers as you said but its not helping, no change is happening, i unplug it and plug the device again, but windows is reporting me there was a problem initiating the device and still recognizing it as a usb composite device. The three inf files i found in “C:\GCCFD\Olimex OpenOCD Driver\Olimex OpenOCD driver_old”.

tarik

In myOpenOCD installation Windows Device Manager shows 3 USB instances related to the Olimex JTAG pod:

USB Composite Device - Location 0 (Olimex OpenOCD JTAG)

Olimex OpenOCD serial driver

Olimex OpenOCD JTAG Interface

A new COM port also appears in Ports section of Device Manager.

Maybe your multiple installation attempts have left multiple driver instances?

–Dave

28

my windows is showing just one instance of a usb device, maybe it is defect dave.

thanks

29

Hi all,

I have the same problem on Windows Vista. I’m using openOCD 204, ARM-USB-TINY. Here’s what I get:

Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi device: 2

Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2

Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY B

Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Xš:

This is the part of the config that matters:

#interface

interface ft2232

ft2232_device_desc “Olimex OpenOCD JTAG TINY A”

ft2232_layout “olimex-jtag”

ft2232_vid_pid 0x15BA 0x0004

jtag_speed 20

What is the solution?

Thanks,

Gil

30

Problem solved with this config:

telnet_port 4444

gdb_port 3333

interface ft2232

ft2232_device_desc “Olimex OpenOCD JTAG TINY A”

ft2232_layout “olimex-jtag”

ft2232_vid_pid 0x15BA 0x0004

jtag_speed 20

reset_config trst_and_srst separate

jtag_device 4 0x1 0xf 0xe

jtag_nsrst_delay 333

jtag_ntrst_delay 333

daemon_startup reset

target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4

run_and_halt_time 0 30

target_script 0 reset oocd_flash2294.script

working_area 0 0x40000000 0x4000 nobackup

flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v1 14746 calc_checksum

Thanks,

Gil