My config is identical and OpenOCD seems to connect. Are you sure you have the FT2232 drivers installed? In your control panel/System/Hardware lists you should see the Olimex serial port under ports and two entries for Olimex JTag under Universal Serial Bus Controllers. It has to install the drivers three times total.
I am having a different problem getting this thing to work in Slackware 12.1. I followed the guide here http://bec-systems.com/web/content/view/74/9/ but I keep getting the error I posted below. I have managed to get this thing to work in Windows but I cant get rid of this error in Slackware.
I found that I had to make sure that this line in the OpenOCD config file had to be right:
ft2232_device_desc “Olimex OpenOCD JTAG TINY A”
The string in the quotes above had to match the device string description as defined in the driver’s ftdibus.inf file in the [Strings] Section. For me, this line in ftdibus.inf is:
See how the strings match. Note that this has to be right in ftdibus.inf before you install the driver, so this strings get set up correctly in the windows registry.
I suspect that gdepaula may be able to get it to work by simply putting the line
ft2232_device_desc “Olimex OpenOCD JTAG TINY B”
instead of
ft2232_device_desc “Olimex OpenOCD JTAG TINY A”
in the OpenOCD config file, based on the error message produced by OpenOCD.
Does anyone know if the Olimex tiny USB Arm will work with the Vista 64-bit version? I cannot get the software to recognize the usb drivers. On my old xp last year it took me days to get it to work and now it seems to be taking days to get it to work on my new pc. I didn’t pick Vista but I am stuck with it.
I point it to the PLACE IN GCCFD but it doesn’t seem to like those files.
Manually hacked the .inf files to make them complient to what they’re expected to be… seems to work somewhat.
Only problem: It says it properly loads the bin onto the chip, but hangs:
'C:\olimex\openocd\bin\'openocd-ftd2xx.exe -f 'C:\olimex\openocd\bin\'armusbocd_tiny.cfg
Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Info: options.c:50 configuration_output_handler(): jtag_speed: 2, 2
Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
Info: target.c:237 target_init_handler(): executing reset script 'sam7flash.script'
Info: options.c:50 configuration_output_handler(): core state: ARM
Info: options.c:50 configuration_output_handler(): flash 'at91sam7' found at 0x00100000
Info: options.c:50 configuration_output_handler(): erased sectors 0 through 0 on flash bank 0 in 0.046002s
Info: options.c:50 configuration_output_handler(): cleared protection for sectors 0 through 1 on flash bank 0
Info: options.c:50 configuration_output_handler(): wrote 1904 byte from file main.bin in 0.282016s (6.593154 kb/s)
If I force close the programmer tool and unplug/replug the header board’s power (reset doesn’t work) then the program I loaded works fine. But I doubt that’s the normal configuration, so… any ideas?
