2025-07-14 1:06 AM - last edited on 2025-07-14 1:47 AM by mƎALLEm
Hello Team,
Since SCB and other core registers are not included in the SVD file for STM32H5, could you please advise on the best way to access or monitor SCB registers (e.g., VTOR, AIRCR, ICSR) during debugging in VS Code with PlatformIO?
Specifically, I'm looking for guidance on:
How to inspect SCB register values during a debug session (e.g., trap cause, exception entry).
Recommended approach to capture trap/exception information like:
HardFault status (HFSR)
Configurable Fault Status (CFSR)
Bus Fault (BFAR)
MemManage Fault (MMFAR)
Any suggestions for manual mapping or watch expressions in the debugger that would allow me to monitor these registers, since they’re not shown in the peripheral view.
Any tips or best practices for bare-metal Cortex-M33 debugging without full SVD support would be greatly appreciated.
Best regards,
Manikanta
2025-08-01 12:31 AM
Can you direct me to the documentation of the vs extension.
2025-10-03 4:10 PM - edited 2025-10-03 4:20 PM
I'd like to add my request to show all of the fault registers in the "STM32CUBE FAULT STATUS REGISTERS" view. Right now, I don't see a way to inspect the fault address, for example when I get a MemFault with the MMARVALID bit set, I can't see any way to actually look at MMFAR, which rather defeats the purpose of having the MPU configured.
EDIT: I was able to inspect MMFAR by setting a Watch with its memory address (since it's a memory-mapped register). But this is far from ideal. It would be nice if all of the fault-related registers showed up in the FAULT STATUS REGISTERS window.