[OpenOCD-user] ti: using GDB debugging MSPM0G3507-launchpad?

[Zixian Z. <syc...@gm...>]

Hi, dear OpenOCD users and developers:

I'm new bird and currently trying to changing developing board from
STM32F3-discovery to TI MSPM0G3507-LaunchPad.

I like using OpenOCD and GDB to debug programs on STM32. On STM32 I just
need to do
> openocd -f board/stm32f3discovery.cfg
> arm-none-eabi-gdb <executable> #in other terminal
And using `tar ext :3333`

I found board/ti_mspm0_launchpad.cfg in mainline repo, and using the
latest openocd right away. I can connect to the board and program it.
But I can not debug it and nothing happens when I reset board through
GDB "monitor mspm0_board_reset" command.

Log below:
$ sudo openocd -f board/ti_mspm0_launchpad.cfg
Open On-Chip Debugger 0.12.0+dev-01084-gcbc32c383 (2025-07-15-10:33)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Warn : DEPRECATED: auto-selecting transport "swd". Use
'transport select swd' to suppress this message.
Warn : Transport "swd" was already selected
cortex_m reset_config sysresetreq
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : XDS110: connected
Info : XDS110: vid/pid = 0451/bef3
Info : XDS110: firmware version = 3.0.0.38
Info : XDS110: hardware version = 0x0028
Info : XDS110: connected to target via SWD
Info : XDS110: SWCLK set to 2500 kHz
Info : clock speed 10000 kHz
Info : SWD DPIDR 0x6ba02477
Info : [mspm0x.cpu] Cortex-M0+ r0p1 processor detected
Info : [mspm0x.cpu] target has 4 breakpoints, 2 watchpoints
Info : [mspm0x.cpu] Examination succeed
Info : [mspm0x.cpu] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333			<----- GDB attaching
[mspm0x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0000016a msp: 0x20208000
Info : Data region NOT available!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I want to ask if the GDB debugging feature is under developing or I used
it incorrectly? Thanks for any suggestions.

Best regards,
Zixian