If you need a custom OpenOCD version, point to it using platform_packages (that is, grab the release package for the OpenOCD package you want, add a package.json to akin to <home folder>/.platformio/packages/tool-openocd/package.json with updated version info, and refer to the folder using file://<path> or a repository link).
digin up this topic since I have some issue debugging some c++ template on stm32, when steping into it just display the called template function, but further step into go over the whole template…
I suspect the openocd to be outdated
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2021-10-16-21:15)
when I go to https://openocd.org/ the latest version is 0.12.0 from Fri 03 March 2023
I’m new to platformio, and contributing to a project, so I don’t know where the package is specified…
I have to patch platformio here locally with the latest OpenOCD to be able to debug STM32 with FreeRTOS. This complicates replicating the development environment and handling Mac vs Linux vs Windows.
Thanks Ivan. I updated pio and am now getting an openocd version that does work with FreeRTOS. (xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (2023-01-30-15:04)
The only platformio file that I need to manually patch now is tool-openocd/openocd/scripts/target/stm32h7x.cfg, appending -rtos auto to the end of the line.
Will it be possible to address this as well? E.g. having the --rtos auto out of the box or alowing to configure it in platformio.ini. This will make it easier to other people to reproduce the project dev environment.
$_CHIPNAME.cpu0 configure -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE -work-area-backup 0 -rtos auto
Is it possible to enable RTOS without patching the original configs? Can we do this from the OpenOCD CLI or pass monitor commands to the active GDB session?