Other Parts Discussed in Thread: SEGGER
Is it possible to use the ARM-CGT tools for compilation/build and use GDB to debug?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
The TI Arm compiler produces a standard output format and debug information that is supported by GDB. How are you going to be using GDB? Will you be using a JTAG debug probe, if so which one? What TI device are you using? We do not maintain a GDB agent for connecting to XDS debug probes.
Ideally, we want it integrated into VSCode using the cortex-debug extension (using the arm-none-eabi-gdb agent). We are using SEGGER J-Link (cJTAG) tools, and we are developing the TI CC2650F128 device. I have this working (to some degree) with this setup up, one issue I'm having is unable to see a call stack and when I try to step out of a function back to the calling, the debug session chokes out.
From my reading, it sounds like there are a lot of overlap of the two toolchains, and wanted see if there were some debug build options I need in order to make it work completely as expected. I also wanted to be sure there was a solution to be had in general, and it wasn't just "kind of working" and that was as good as it would get.
I checked with our compiler expert and he memtioned that there are no additional options available to support GDB. With that said, note that using the TI ARM compiler with GDB is not an officially supported environment. Hence it is not surprising that there are some issues with debug visibility. Unfortunately there is little additional support we can provide for this issue. Sorry