Olimex OpenOCD JTAG TINY B ERROR

Hi all!

I try to programm a sam7h256 over openOcd JTAG TINY - all from olimex.

After install and setup and run the sample program from olimex (sam7h256-flash) i get the following error:

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: 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: hU>

I hope anyone can help!

thanks

florian

And here is my config file:

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 3
jtag_nsrst_delay 200
jtag_ntrst_delay 200

reset_config trst_and_srst separate

jtag_device 4 0x1 0xf 0xe

daemon_startup reset

target arm7tdmi little run_and_init 0 arm7tdmi_r4

run_and_halt_time 0 30

target_script 0 reset sam7flash.script

working_area 0 0x40000000 0x4000 nobackup

flash bank at91sam7 0 0 0 0 0

try to change the line

ft2232_device_desc “Olimex OpenOCD JTAG TINY A”

with

ft2232_device_desc “Olimex OpenOCD JTAG TINY B”

it seems that the description name might be wrong.

… A is the first channel, which is the only one capable of driving JTAG. The second channel only offers UART and FIFO modes. Changing the .cfg to … B won’t help.

Which OS are you using, and which version of the FTDI driver?

Regards,

Dominic

I thought “Olimex OpenOCD JTAG TINY A” was just the product descriptor string, and A or B meant something like “Rev. A” or “Rev. B”.

Anyway, I have an ARM-USB-OCD, and the first time I tried to use it, didn’t work. Then I discovered that the .cfg file used “Olimex OpenOCD JTAG A”, while my programmer has “Olimex OpenOCD JTAG” (no rev. number) as descriptor. Changing the config file by removing tha “A” did the trick.

hello!

thanks for the answer!

i use windows xp and the driver is from 15.01.2007

i try all the variations about TINY A and TINY B - nothing works!

its easier under linux (suse 10.3)?

greetings

flo

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

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