2026-06-03 9:43 PM
Hi ST,
I can't seem to get debugging to function when following the above named example on a nucleo-u385RG-Q using CubeIDE and CubeProgrammer. The guidance on the README is vague when it needs to be clear - for starters what is the 'offset of the firmware execution slot'?
"1. The most efficient way to develop and debug an application is to boot directly on user flash in RDL level 0 by setting with STM32CubeProgrammer the RDP to 0xAA and the SECBOOTADD to (0x0C006000 + offset of the firmware execution slot)."
This example was designed by ST to work on a clean board, wouldn't you know the exact value? There is also nothing about adjusting the secure watermarks so the debugger does not hit a secure area by default and hard fault - I had to find that particular nugget stashed in a completely seperate project.
Many of us delving into STM32 development are not well versed in low level memory management, especially navigating across Secure / Non Secure / Bootloader sections - hence the value of a 'functioning' example out of the box to help us understand. This isn't the first example project I've come across that hasn't worked except by some 'gotcha' that wasn't covered in the documentation.
Appreciate any help with this example and look forward to getting better at this!
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.