Hello. I have troubles with establishing debugging with gdb over openocd.
I'm using ftdi-based xds100v2-compatible jtag emulator.
Debugging beaglebone: starting openOCD:
$ openocd -f ./tcl/board/ti_beaglebone.cfg
Open On-Chip Debugger 0.6.1 (2012-10-19-19:24)
....
Info : only one transport option; autoselect 'jtag'
adapter speed: 16000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Info : max TCK change to: 30000 kHz
Info : clock speed 15000 kHz
Info : JTAG tap: am335x.jrc tap/device found: 0x0b94402f (mfg: 0x017, part: 0xb944, ver: 0x0)
Info : JTAG tap: am335x.dap enabled
Info : am335x.cpu: hardware has 6 breakpoints, 2 watchpoints
Looks like it works normally. I tested by telnel that board's control is present.
Starting gdb from sdk:
$arm-arago-linux-gnueabi-gdb
...
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
0x000233f8 in ?? ()
(gdb) load ti-sdk-am335x-evm-05.04.01.00/board-support/u-boot-2011.09-psp04.06.00.07/am335x/spl/u-boot-spl
Loading section .text, size 0x779c lma 0x402f0400
Load failed
Trying to load binary in target's memory address 0x402F0400 specified in executable. It's right for am335x. But loading fails.
At the same moment openocd type messages:
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x2800052, MEM_AP_TAR 0x402f0400
Warn : Block write error address 0x402f0400, wcount 0xfe8
What actions I made wrong with GDB?
And what means MEM_AP_CSW name?
Thank You.
Best regards,
Dmitriy.
