Msp430 debugging peripherals

Development Platforms
1

Hello. I am trying to debug custom msp430f47187 board with new gcc tools. It was a little tricky to connect with a platform.io debugger, but i did that. There is one problem: i cant view core register and peripheral registers values. Is it implemented for msp430? Or i should make something like: create my own .svd or something like this?..

I have manually started gdb_agent and load firmware. Then i have attached debugger via “PIO Debug without uploading”

*.ini:
[env:stable2]
platform = https:_github.com_maxgerhardt_platform-timsp430.git (fixed to be not a link)
board = lpmsp430f47187 (created by me)

board_build.mcu = msp430f47187
board_build.f_cpuio = 16000000L

debug_tool = custom (in lunch.json i specified toolchain dir)
debug_port = :55000

platform_packages =
toolchain-timsp430@https:_github.com_maxgerhardt_pio-toolchaintimsp430-new.git

P.S. own svd seems working for peripherals, but i stiil cant view core registers.

2

Usually platforms have a misc/svd folder in which SVD files for all chips of a platform are stored (refer GitHub - platformio/platform-ststm32: ST STM32: development platform for PlatformIO), but for https://github.com/platformio/platform-timsp430 or my form that’s not the case. You’d have to fork + add those SVD files in, and then reference it in your board definition file under the debug section, refer

3

Hello. svd works (for peripherals), but core registers do not. It should work because CCS can read them. Also there is a problem with baud rate: “monitor speed” do not work for gdb-agent/mitto gdb. How to solve this? Maybe i can set up mspdebug for mitto gcc tools… (Which also do not work for me for default timsp430 platform)