Target not reported as halted with rust project

[mrgdoubleyou]

I am in the process of setting up a VSCode configuration for a rust project and a Cortex-M4 device on Windows. The launch seems to work correctly, however it appears that my target never halts. I'm wondering if perhaps the VSCode side is unaware of the actual target status as the halt button is greyed out:

My first debug approach was to see why the target wasn't halting. However, when running manually with GDB server and GDB, it appears that the target is halted. See attached logs below. The GDB server command is the same command that cortex-debug is issuing during the launch. gdb_server_log.txt gdb_log.txt

Is it possible that the target isn't exactly halting at main and therefore confusing the debugger?

My launch.json is listed below and the "vscode" debug console output is here: debug_console.txt

Here is the gdb server console from the VSCode initiated session: cortex_debug_gdb_server_log.txt

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Cortex Debug",
            "cwd": "${workspaceFolder}",
            "executable": "./target/thumbv7em-none-eabihf/debug/rsc",
            "request": "launch",
            "type": "cortex-debug",
            "runToEntryPoint": "main",
            "servertype": "jlink",
            "serverpath": "C:/Program Files/SEGGER/JLink_V796a/JLinkGDBServerCL.exe",
            "serverArgs": ["-settingsfile", "./cfg/JLinkSettings.ini", "-speed", "2000"],
            "device": "VA416xx",
            "interface": "swd",
            "serialNumber": "",
            "jlinkscript":"./cfg/JLinkSettings.jlinkscript",
            "svdFile": "./cfg/va416xx.svd",
            "armToolchainPath": "C:/Program Files (x86)/Arm GNU Toolchain arm-none-eabi/13.2 Rel1/bin",
            "showDevDebugOutput": "vscode"
        }
    ]
}

My rust program is simple and was more or less generated with: cargo generate --git https://github.com/rust-embedded/cortex-m-quickstart

#![no_main]
#![no_std]

use panic_halt as _;

use cortex_m_rt::entry;

#[entry]
fn main() -> ! {
    loop {
        let mut i = 0;
        i += 1;
    }
}

Versions are:

• Cortex-Debug Version (this extension): 1.12.1
• OS: Windows 10 (I see the same issue with WSL Ubuntu 20.04)
• GDB Version: GNU gdb (Arm GNU Toolchain 13.2.rel1 (Build arm-13.7)) 13.2.90.20231008-git

• Compiler Toolchain Version: arm-none-eabi-gcc.exe (Arm GNU Toolchain 13.2.rel1 (Build arm-13.7)) 13.2.1 20231009

  Here is another reference I was using for setup: https://wiki.segger.com/J-Link_Visual_Studio_Code

  Any ideas on what I could be missing on the VSCode side? Thank you!

[mrgdoubleyou]

As another data point, I can see the same issue using qemu as described here: https://doc.rust-lang.org/beta/embedded-book/start/qemu.html

[mrgdoubleyou]

Okay, I have solved the mystery and the error is all on my side. I was launching the debugger with Ctrl+F5 as that is the default for the Keil IDE. Turns out that is the wrong key and I wanted F5 all along.

[mrgdoubleyou]

Thanks for the wonderful extension!