[Bug]: Unable to read peripheral memory in Memory Inspector when target is halted

[steradiant]

Description

I cannot access memory regions from peripherals in the Memory Inspector while the target is halted. VS Code displays the error: "Unable to read memory." When the target is running, memory information is visible and updates correctly when periodic refresh is enabled. However, once I halt the target, the message "No results found" appears.
The Memory Inspector does, however, continue to work with global variables even when the target is halted.

Steps to Reproduce

No response

Expected Behavior

The Memory Inspector is expected to display the contents of memory regions in both states: when the target is running and when it is halted.

Additional Information

No response

[jkrech]

Could you please provide a bit more information. Which versions of the different extensions are you using. Which target and board are you using and which debug adapter. Maybe you can share even your project.

[steradiant]

Further information to my project:

• STM32G474 Nucleo board
• ATfE 21.1.1
• Win11
• VS Code 1.106.3
• Arm CMSIS Debugger v1.2.0
• CDT GDB Debug Adapter Extension v.2.5.0
• Memory Inspector v1.2.0
• Peripheral Inspector v1.8.1
• Serial Monitor v0.13.1
• GDB v14.3.Rel1

I cannot share my original project, but I was able to reproduce the issue with a minimal working example (a simple blinky project), so it should be easy to reproduce.

I also want to mention that I am using the Arm CMSIS Debugger as a standalone tool, not together with the Arm Keil Studio pack. In addition, I do not use Arm CMSIS Solution for development, as it introduces unnecessary overhead and is not well-suited for my applications. Instead, I use a Makefile-based build environment with the new Arm Toolchain for Embedded. However, I do not expect any issues arising from this workflow, since the GDB debugger should be universal, and the documentation states that the Arm CMSIS Debugger can be used independently.

[jreineckearm]

Lowering priority given usage of *.cbuild-run.yml relaxes impact (see #669 (comment)). Yet, we need to understand the differing behavior between peripheral inspector and memory inspector. But probably only after next release.