Recovering STM32H563 from closed product_state

Schue · ‎2024-09-23

Hey community,

I was working on some production scripts for our H5 based boards and got myself locked out.

This occured after trying to set the obk file.

STM32_Programmer_CLI -c port=SWD ap=1 -sdp=<wrong_obk_path>

I got a corresponding warning "Error: The sdp option you trying to set is missing the obk filepath" which makes sense but I still continued to set the PRODUCTION_STATE to closed with the next command.

As I did not use a valid obk file I can not execute the regression now using my password binary file.

Any chance I can recover my device?

Thanks,
Tobias

AScha.3 · ‎2024-09-23

Hi,

take next chip and try...without errors.

Its for production, as you you wrote; so dont kill too many chips.

Or you try to hack the protection, just to prove , its not secure .

If you feel a post has answered your question, please click "Accept as Solution".

STea · ‎2024-09-24

Hello @Schue ,

I'm afraid that you cannot recover this device as the provisioning phase was not executed properly.
next time try to follow the steps needed for safer manipulation during the developing phase.

How to start with OEMiRoT on STM32H573 and 563–Arm® TrustZone® enabled - stm32mcu
Regards

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.