Hi,
i try to flash a OLIMEX SAM7-H64 development board with my new BusBlaster v2.5 with OpenOCD. But i have no luck so far.
OpenOCD runs on a Debian Squeeze platform. My 'openocd.cfg' is:
telnet_port 4444
#
# Bus Blaster
#
# http://dangerousprototypes.com/docs/Bus_Blaster
#
interface ft2232
ft2232_device_desc "Dual RS232-HS"
ft2232_layout jtagkey
ft2232_vid_pid 0x0403 0x6010
reset_config trst_and_srst srst_pulls_trst
jtag newtap sam7s cpu -irlen 4 -ircapture 0x1 -irmask 0x0f -expected-id 0x3f0f0f0f
set _TARGETNAME sam7s.cpu
target create $_TARGETNAME arm7tdmi -endian little -chain-position $_TARGETNAME -variant arm7tdmi
flash bank 0 at91sam7 0 0 0 0 0
jtag_rclk 0
I try to flash the uC in the following way:
1. interconnect the jtag connectors of both boards
2. connect both boards to the usb-controller of my notebook. (At this point i wonder why the target LED of the BB remains dark!? Not to be confused with the red power LED that is ON. )
3. run OpenOCD, that fails with:
# /opt/openocd/bin/openocd -f openocd.cfg
Open On-Chip Debugger 0.6.0-dev-00458-ged12a65 (2012-03-13-13:46)
Licensed under GNU GPL v2
For bug reports, read
********************************
Info : only one transport option; autoselect 'jtag'
trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_open_drain
Warn : use 'sam7s.cpu' as target identifier, not '0'
RCLK - adaptive
Info : max TCK change to: 30000 kHz
Info : RCLK (adaptive clock speed)
Error: couldn't read enough bytes from FT2232 device (0 < 81)
Error: couldn't read from FT2232
Error: Trying to use configured scan chain anyway...
Error: couldn't read enough bytes from FT2232 device (0 < 2)
Error: couldn't read from FT2232
Warn : Bypassing JTAG setup events due to errors
Error: couldn't read enough bytes from FT2232 device (0 < 6)
Error: couldn't read from FT2232
Polling target failed, GDB will be halted. Polling again in 100ms
Polling target failed, GDB will be halted. Polling again in 300ms
Polling target failed, GDB will be halted. Polling again in 700ms
Polling target failed, GDB will be halted. Polling again in 1500ms
Polling target failed, GDB will be halted. Polling again in 3100ms
Polling target failed, GDB will be halted. Polling again in 6300ms
^C
[/list]
[/list]
To solve this i looked at the jtag connectors of both boards (based on the post 'BBv2 JTAGkey implementatoin'). It seems that all pins are correctly assigned, except one on the olimex board i'm not aware of. In the schematic the JTAG connector looks like:
[align=center:][attachment=0][/align:]
I wonder whether pin15, that is not connected to the uC may cause openocd to fail!?
It would be great if anybody around here can help me to solve my problem. I just want to get into arm programming, right now :)
By the way, i love the philosophy of dangerousprototypes and the awesome blog.
With best regards
This is probably more error of openocd than busblaster problem. Have you tried to ask on the mailing list ? I am sure someone will be able to help you.