Tool/software: Code Composer Studio
I have succesfully set up Code Composer Studio to use GDB to debug a CC1352 on a Gateworks 5910. I am using OpenOCD to flash images to the chip using the following configuration file and command:
openocd -f ./gw5910.cfg -c "program rfEasyLinkNp_CC1352P1_LAUNCHXL_tirtos_debug_gcc.out verify reset exit"
cat gw5910.cfg
#
# GW5910 CC1352P JTAG Interface mapping
#
# PAD_DISP0_DAT14__GPIO5_IO08 TMS gpio-136
# PAD_DISP0_DAT15__GPIO5_IO09 TCK gpio-137
# PAD_DISP0_DAT16__GPIO5_IO10 TDO gpio-138
# PAD_DISP0_DAT17__GPIO5_IO11 TDI gpio-139
#
# PAD_DISP0_DAT23__GPIO5_IO17 RST# gpio-145
# PAD_EIM_A25__GPIO5__IO02 BOOT gpio-130
bindto 0.0.0.0
interface imx_gpio
transport select jtag
imx_gpio_peripheral_base 0x020ac000
imx_gpio_speed_coeffs 100000 5
imx_gpio_jtag_nums 9 8 11 10
imx_gpio_trst_num 17
adapter_khz 20000
source [find target/ti_cc13x2.cfg]
jtag_ntrst_delay 0
jtag_ntrst_assert_width 0
adapter_nsrst_delay 0
adapter_nsrst_assert_width 0
reset_config trst_only
In Code Composer Studio, I created a new Debug Configuration as a C/C++ remote Application, in the Main Tab selected "Manual Remote Debugging Launcher - Select Other" and selecting Manual, and in the Debugger tab, pointing the Connection Tab Host name to my Gateworks board:port 3333 which is what OpenOCD is listening to.
I have also pointed the rfEasyLinkNp project to use the debug build of the tirtos_cc13x2_cc26x2_debug_gcc project, and with that, I am able to step-debug in rfEasyLinkNp.c down to BIOS_start(); and into the tirtos project source files, however, any breakpoints I set in AtProcess.c such as the AtProcess_processingLoop() function, are never reached, and the program is never paused.
Is it possible to debug this user code using remote GDB debugging? Using the same code deployed to a Launchpad, I am able to step through all portions of the code.
