Tool/software:
When I use Vscode extensions named "TI Embedded Debug for VS Code" , I tried to burn a program into MSPM0G3507 with Openocd, which is provided by TI Embedded Debug for VS Code.
The first burn-in went well, this is the output of the terminal:
Open On-Chip Debugger 0.12.0+dev-gae70877b5-dirty (2025-01-31-10:10)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 10000 kHz
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
cortex_m reset_config sysresetreq
Info : Using CMSIS-DAPv2 interface with VID:PID=0x0d28:0x0204, serial=33e32adcd688a06200
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: JTAG supported
Info : CMSIS-DAP: SWO-UART supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: Test domain timer supported
Info : CMSIS-DAP: FW Version = 2.1.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
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 : starting gdb server for mspm0x.cpu on 3333
Info : Listening on port 3333 for gdb connections
[mspm0x.cpu] halted due to breakpoint, current mode: Thread
xPSR: 0xf1000000 pc: 0x0000057c msp: 0x20208000
** Programming Started **
** Programming Finished **
** Verify Started **
** Verified OK **
but when i try to burn-in in second time, output of the shell turns to this:
** Programming Started **
** Programming Finished **
** Verify Started **
Error: timed out while waiting for target halted
Error: error executing cortex_m crc algorithm
** Verified OK **
unless i reset chip in manual, i need cost a long time wait for Verify with some ERROR messages, after i reset the chip and burn again, burning process turn to normal, but second times and after , unless manually reset the chip , the program verify can't turn back to normal.
i tried burn with Keil5, everything is fine , so i guess this is Openocd problem, how to fix this?
