Virtual control interface via semihosting

[inca]

I recently got semihosting up and going again using ChibiStudio (without chibi or chibi hal, unfortunely) and STM32 STD PERIPH lib.

The default startup.s and linker files from ST seem not to work with semihosting.

I've not testing the chibi startup.s and .ld script, but I'd imagine a similar outcome.

The only configuration that works for me is to use the GAE toolchain samples for semihosting in GAE/share/gcc-arm-none-eabi/samples/startup for the assembly .s and linker .ld files. I am not competent enough to tell what the meaningful differences are without a time-consuming search. I can say that the linker scripts are written in different styles and have different named sections and the startup.s has slightly different implementation to init the memory in ResetHandler().

Honestly, I'm not really sure why we've made such complex systems for describing the startup init. At the end of the day, we are moving data and that's it. Nothing else. Not sure why I need a fancy syntactical programming language of a linker script to map memory to data. And as for determining the requirements of a complete linker file? Good luck. Hence my default to the GAE versions. If it works for them, then it should work for GDB, too.

[ceremcem]

I recently got semihosting up and going again using ChibiStudio (without chibi or chibi hal, unfortunely) and STM32 STD PERIPH lib.

Is there an example project for introduction to semihosting?