Closed mytechnotalent closed 1 year ago
What do you see in the Debug COnsole
? It has instructions to enable verbose output. Also, what is the output from openocd? I don't see any information in your bug report about what/how your manual stuff worked and how or what our extension did.
@haneefdm that was literally the totality of the info in the Debug Console
. OpenOCD performs as expected however VSCode literally does nothing when attempting to use the debug tool.
--config Debug --target badge1 --
[build] ninja: no work to do.
[build] Build finished with exit code 0
That (ninja) has NOTHING to do with our debugger. That seems to be your build output. I am saying "Debug Console" where output goes and instructions as well. It looks something like this
If you are new to VSCode, I suggest reading this
A screenshot like I sent can be helpful because I am beyond confused
I can't reproduce on my other Windows machine. The output from the DEBUG CONSOLE
literally is the following.
Cortex-Debug: VSCode debugger extension version 1.6.10 git(0458417). Usage info: https://github.com/Marus/cortex-debug#usage
This appears after attempting to press the play button on the Pico Debug (Cortex -Debug) UI.
I will close the issue.
running the Pico Debug within VS Code literally does nothing. I have openocd installed and can do everything manually on the terminal however this extension does not work
launch.json