STM32U585I-IOT02A: Unable to revert RDP from DC to AA after password set

[shivss]

Hello,

I am working with an STM32U585I-IOT02A development board and using STM32CubeProgrammer.
I changed the RDP level to DC and set a password. After that, I am unable to get back to RDP level AA.

• I tried entering the correct password, but the unlock option does not disable the protection.

• I also attempted the "unlock RDP1 level" process, but it does not seem to work.

• Currently, I am unable to flash any code onto the device.

Is there any way to recover the board back to RDP AA level and make it programmable again?
What is the correct procedure to unlock the RDP DC level after a password has been set?

Thanks in advance.

[shivss]

Hello @STackPointer64 ,

Thanks for the update. I have a few doubts and follow-up points:

1. If the OEM1 key is incorrect, could you please clarify how the command still shows “unlock successful”? I’m unable to understand this point.

2. I have already tried all the passwords I remember, but unfortunately, none of them worked.

3. Please let me know what options I have now — I really need to continue my development work on this board.

[STackPointer64 · Accepted solution]

Hello,

The command showing “unlock successful” actually means the script finished executing; it assumes the user correctly remembers the password used. I understand this can be confusing, so I have escalated the issue to the relevant team for resolution. It is being tracked internally under ticket number 219784.

Since you have tried all remembered passwords without success, unfortunately, unless you recall the exact password used to lock and unlock RDP1, you will not be able to use the board.

Best regards,

[shivss]

Hi @STackPointer64 ,

Got it, thank you for the clarification. Just to confirm — if I replace the STM32 controller ICs with new ones, would I then be able to use the board again, since the new ICs wouldn’t be locked?

[STackPointer64]

Hello @shivss,

Yes, that is correct. Changing the locked STM32 controller would allow you to use the board again.

Best regards,

[shivss]

Hi @STackPointer64 ,

Thank you for confirming. I noticed that the board has an X-WIFI-EMW3080B (MXCHIP) module that supports Wi-Fi firmware updates for STM32 boards. Would it be possible to use this module to upload code to the board instead of replacing the STM32 controller?

Also, in case replacing the controller is the only option, could you please advise on the correct procedure for changing the STM32 IC?

[STackPointer64]

Hello @shivss,

That is not possible in your situation due to the RDP lock. Also, although the feature is available, it needs to be implemented in your application code. Regarding replacing the STM32 IC, the correct procedure is to replace it with another IC of the same package (UFBGA169). This must be done by a professional to avoid damaging other components on the board.

Best regards,

[shivss]

"Ok, understood. I will get a new board since changing the STM32 IC is not possible."