Hi!
I have received (amongst other things) an ARM-USB-TINY device.
The CD that came with it was corrupt (the installers fail the CRC check, I can’t open text files, etc… on 2 different computers and 3 different drives).
Anyway, I downloaded OpenOCD from their website and installed it, but when I plug TINY in, windows can’t find the drivers.
What to do?
Thanks in advance,
Shwouchk.
I think you should kindly ask the people whom you bought the device from for a new CD.
Those people are sparkfun…
shwouchk:
Hi!Anyway, I downloaded OpenOCD from their website and installed it, but when I plug TINY in, windows can’t find the drivers.
What to do?
Thanks in advance,
shwouchk
The YAGARTO OpenOCD installer places the drivers in the driver subdirectory under wherever you put the main OpenOCD directory. I imagine that whatever installer you used did the same. If you took the defaults, each of the hardware devices that OpenOCD supports will be in it’s own subdirectory in the driver directory. Just point the Windows installer there when it asks for a driver disk. BTW, the YAGARTO OpenOCD is a pure Windows version of OpenOCD, while the orginal will also require Cygwin to be installed on your Windows PC. At least that is the way things were before I switched to the YAGARTO version.
–Dave
Perhaps I should have mentioned that;
I did tell windows to look there, and it ‘didn’t find’ anything. I even used the ‘have disk’ option, and chose all the available drivers one by one - and time after time I was told that they hold no information regarding the hardware…
As I wasted half of my day figuring out, the Windows driver .inf and .ini files that come with the ARM-USB-TINY, and that come with OpenOCD have a PID (ProductID) of 3 but they should be 4 for the Tiny board.
There are several places that this must be changed. However, once I got all those fixed the driver installed.
Still trying to get code download and debugging going.
From Linux lsusb:
idVendor = 0x15ba
idProduct = 0x0004
iProduct = ‘Olimex OpenOCD JTAG Tiny’
– John.
Thanks for the info!
I actually don’t use windows anymore, and on linux I found information regarding using openocd and our jtag keys to be very lacking.
I did however find out how to do it more or less - I havent actually tried it, but hopefully it will work when my code is ready… 
what might help you a lot is to know that the internal chip for our devices is an ft2232…
This is the config I used to make openocd recognize my thingie :
#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY"
ft2232_layout jtagkey
ft2232_vid_pid 0x15ba 0x0004
jtag_speed 2
#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst srst_pulls_trst
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe
#target configuration
daemon_startup reset
#target <type> <startup mode>
#target arm7tdmi <reset mode> <chainpos> <endianness> <variant>
target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
target_script 0 reset h2294_init.script
run_and_halt_time 0 30
working_area 0 0x40000000 0x40000 nobackup
#flash configuration
flash bank lpc2000 0x0 0x40000 0 0 lpc2000_v1 0 14765 calc_checksum
flash bank cfi 0x80000000 0x400000 2 2 0
Put this in a file and call openocd with that file as the config file… Ill try to find the page where I found that info later on… Also please let me know if you succeed in downloading and running executables on the device, since I’m nearly at that stage…
I have been having problems with my .cfg and am going to try yours.
However, it refers to h2294_init.script
Can you post this too?
Anyway I’d prefer to do this on Linux as well but
a) other people that are used to windows need to use my setup instructions and
b) I was expecting that the Windows path was well-trodden. Apparently not for this combination.
– John.
I finally finished my code today and I discovered that I too have a problem connecting… I also have no idea what this script it, which is weird since Im pretty sure it worked…
Anyway, Ill try to find out more tommorow.
Turns out my main problem with connecting was a bad power supply. When I switched from the supply to USB power I was able to connect.
However I do have an issue with the .cfg that comes in the ‘For Dummies’ installer: I find that I cannot connect using the Eclipse environment at all. So I run from command line. The openocd config in the For Dummies installer cause me grief. But when I use one closer to what comes by default with OpenOCD I have more luck: openocd stays running while debugging instead of exiting with error…
– John.
Thats good to hear!
I wonder, do you know if exactly 6v are needed in the supply? because the supply I’m using gives out 5v which seems to be fine, but after your problem I’m a bit afraid that it might cause problems for me…
The 5V supply that a EE told me would be fine was not sufficient. Use a 6V supply or the usb cable.
– John.
Wow, that sucks - I have neither… Oh, well.
Thanks for the heads up, Im sure you just saved me hours of frustration!
You were right about the power supply - Ive switched to 7v since I dont have any 6v supplies available atm, and it seems to work well…
The problem arises when I try to run code - on it - I can download the code but I’m having trouble debugging it or even having it do what I want…
Did you succeed in what you were doing?
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