Hi everyone,
I’m using a CC1352P1 LaunchXL board from TI, and I want to be able to step through code that I generated using CMAKE. I was able to flash the code onto the cc1352p1 using a flashing tool, so I know that the code does work as expected. I downloaded and installed openocd and am using arm-none-eabi-gdb. I am using the onboard XDS110 debugger.
I am able to get openocd to listen for gdb connections on port 3333 with the following command:
$ sudo openocd -f openocd.cfg
Where my openocd.cfg contains the following :
source [find interface/xds110.cfg]
source [find board/ti_cc13x2_launchpad.cfg]
gdb_flash_program enable
gdb_memory_map disable
gdb_report_data_abort enable
Then, in another terminal, when I bring up gdb, I do the following
(gdb) target remote localhost:3333
I get the following response in gdb:
Remote debugging using localhost:3333
0x00000000 in ti_sysbios_family_arm_m3_Hwi_resetVectors ()
(gdb)
and I can see my source code that I expect in the gdb window.
and in openocd:
Info : XDS110: connected
Info : XDS110: firmware version = 3.0.0.5
Info : XDS110: hardware version = 0x0023
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 2500 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: cc13x2.jrc: IR capture error; saw 0x3f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections
Info : accepting ‘gdb’ connection on tcp/3333
Error: Target not examined yet
Error executing event gdb-attach on target cc13x2.cpu:
When I try to load the program, using the following command in gdb:
(gdb) load
I get the following error in gdb:
Loading section .resetVecs, size 0x3c lma 0x0
Loading section .text, size 0xe0bc lma 0x3c
Load failed
and in openocd:
Error: Target not examined yet
Error: Target not examined yet
Error: Target not examined yet
I have tried programming the board directly from openocd, with the following command:
sudo openocd -f board/ti_cc13x2_launchpad.cfg -f path/to/interface/xds110.cfg -c “program binaryfile.out verify reset exit 0x00000000”
Open On-Chip Debugger 0.10.0+dev-00957-g9de7d9c8 (2019-11-15-11:10)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter_nsrst_delay: 100
Warn : Interface already configured, ignoring
Info : XDS110: connected
Info : XDS110: firmware version = 3.0.0.5
Info : XDS110: hardware version = 0x0023
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 2500 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: cc13x2.jrc: IR capture error; saw 0x3f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections
Info : JTAG tap: cc13x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc13x2.cpu enabled
Assertion failed: (ap->dap->ops != NULL), function dap_queue_ap_read, file src/target/arm_adi_v5.h, line 391.
Abort trap: 6
and with the following command:
sudo openocd -f board/ti_cc13x2_launchpad.cfg -f path/to/interface/xds110.cfg -c “program binaryfile.out verify reset exit 0x08000000”
Open On-Chip Debugger 0.10.0+dev-00957-g9de7d9c8 (2019-11-15-11:10)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter_nsrst_delay: 100
Warn : Interface already configured, ignoring
Info : XDS110: connected
Info : XDS110: firmware version = 3.0.0.5
Info : XDS110: hardware version = 0x0023
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 2500 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: cc13x2.jrc: IR capture error; saw 0x3f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections
Info : JTAG tap: cc13x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Error: cc13x2.jrc: IR capture error; saw 0x3f not 0x01
Warn : Bypassing JTAG setup events due to errors
** Programming Started **
Error: Target not examined yet
Error: auto_probe failed
** Programming Failed **
shutdown command invoked
Where could my error be?