Skip to main content
Visitor
September 4, 2026
Question

For STM32C562RE, why can CubeProgrammer validate the OEM key and report "RDP2 unlocked successfully", while does not erase existing user flash?

  • September 4, 2026
  • 0 replies
  • 9 views

For STM32C562RE, why can CubeProgrammer validate the OEM key and report "RDP2 unlocked successfully", while the RDP regression does not erase the existing user flash and flash erase remains prohibited? Is this a known CubeProgrammer/ST-LINK limitation or does this indicate that the device was provisioned with a non-regressible security configuration?

Device: STM32C562RETx / NUCLEO-C562RE
CubeProgrammer: v2.22.0
ST-LINK: V3J17M11

SWD connection works.
Device ID: 0x44E.

OEM key is available.

RDP unlock operation sometimes reports:
"Validation Status: 3"
followed by:
"RDP2 unlocked successfully"

After physical power removal and restoration:

RDP_level = 0xFF (Unknown Value)

Flash still contains:
0x08000000 : 200007C8 08000671 0800073D 08000735

Mass erase:
Error: Mass erase operation failed. Please verify flash protection

Programming:
Erasing internal memory sector 0
Error: failed to erase memory