Closed mrgdoubleyou closed 5 months ago
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
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.
Thanks for the wonderful extension!
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:![image](https://github.com/Marus/cortex-debug/assets/4704537/a52b9f9e-25ac-4a31-a717-cbb7c20ce3dd)
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
My rust program is simple and was more or less generated with: cargo generate --git https://github.com/rust-embedded/cortex-m-quickstart
Versions are:
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!