VSCode GDB Launch Configuration Not Taken From `openocd.gdb` about cortex-m-quickstart HOT 6 OPEN

You can add this to your launch.json. Worked nicely with stm32g0.

            "postLaunchCommands": [
                "monitor arm semihosting enable",
            ],

Also cortex-debug supports a lot of parameters that can be tweaked: https://github.com/Marus/cortex-debug/blob/master/package.json#L195

from cortex-m-quickstart.

AFAIK it’s not currently possible to load a gdb script through the cortex-debug extension. I would encourage you to open an issue there as I couldn’t find a related one.

I think it’s reasonable to open a PR that adds semihosting to the QEMU launch config, since the stm32f303 config is set up to use ITM. That way we have an example for both communication mechanisms. QEMU doesn’t support ITM, so it seems reasonable, to me, for it to be the one to be configured for semihosting.

from cortex-m-quickstart.

Damn, I should have read OP more carefully. It was all there.

from cortex-m-quickstart.

Can this issue be closed?

from cortex-m-quickstart.

Is there a way to configure the extension to show hprintln output?

from cortex-m-quickstart.

Ah, nevermind, hprintln output is in the gdb-server terminal.

from cortex-m-quickstart.