Hi, when I debug my software (nrf5340 cpuapp) from the nRF Connect plugin in VS Code, when I hover over variables and buffers, only the content of the variables is shown, but not their memory location. Also, if I add a variable or array to watch, I still cannot see its memory location. This is pretty inconvenient. Could this be fixed in a future update?
When I click on some strange symbols next to a buffer/array content, a hex browser opens. (It seems to be another plugin.) But the data shown does not match the buffer/array content shown inside the debugger. This is also very confusing.
Further, when I try to check the contents of peripheral registers, (almost) all peripherals are named *_NS in the debugger view, even though I do not use TF-M. I use the standard nRF5340DK cpuapp build target without _ns. Is this a bug? It is a bit confusing because the _NS modules are located at different memory locations than the ones used in my code...
Just leaving you some feedback here, maybe you want to fix these things some time in the future. It would make debugging much simpler and more intuitive. If I overlooked something important, please let me know.
Update: I have one more issue: The nRF Connect plugin for VS code tells me all the time that my code is stale and needs a pristine build. Even when I didn't change a single thing in the configuration. Any idea what could be the reason?
Best regards,
Michael
