Roderick Chapman
Roderick Chapman
Secondly, the advanced/firmware/.vscode directory appears to me missing its launch.json file, so (cross) debugging and running on the Nordic target doesn't work at all for me... I also found I...
With Cortex-Debug, gdb-multiarch, and a self-written launch.json file, it sort-of works now... Running a program, setting breakpoints and single-stepping all seems to work OK. But... display of variable values does...
For what it's worth, I am running VSCode 1.62.3 on Ubuntu 21.10, which is itself running in a Parallels VM on top of MacOS.
Got it... debug=2 seems to do the trick for watching local variables. Perhaps that level should be the default for the course material?
So... what's going on with the "log::info!()" output?
I tried again using "defmt::log!()" and same result - no sign of the output in any of the VSCode windows...
Ah... so "cargo run" (on the command-line) invokes "probe-run", but VSCode uses the Cortex-Debug extension, which uses openocd, right? If that's right, then I will look at the openocd manual...
Some discussion here: https://github.com/Marus/cortex-debug/issues/456 Looks like it should work, but some magic is required in the launch.json file...
AdaCore said "No official support for macOS", so don't expect any help there... Clearly _something_ in the RTL or underlying pthreads libraries is allocating a Port for each task, but...
Where are the runtime library sources for macOS? I guess I'm looking for the bit that does task creation and termination in terms of pthreads...