STM32H573I-DK bricked - RSS_DA not booting, cannot perform DA regression

[gruna890]

Hello,

My STM32H573I-DK board is bricked after a failed provisioning attempt.

What happened:

1. Accidentally changed PRODUCT_STATE from Open (0xED) to 0x17 (Provisioning) via programmer
2. Then an AI coding assistant (Copilot) attempted some configuration via DFU mode and enabled TrustZone
3. I no longer have access to the PC where this was done

Current symptoms:

• SWD: "Unable to get core ID", "Cannot connect to access port 1"
• DA discovery (debugauth=2): "The target is unable to boot on RSS_DA or is in OPEN mode"
• DA regression (debugauth=1) with default STM32CubeFW_H5 keys: "Unable to detect DBGMCU Mailbox" or "unable to boot on RSS_DA"
• DFU (USB0): "Target device not found" (with boot jumper set to SYS/MEM)
• UART bootloader: timeout

What I tried:

• SWD with HOTPLUG, UR, HWrst, ap=0, freq=100
• DA regression with default key_3_leaf.pem and cert_leaf_chain.b64
• regression.bat from ROT_Provisioning\DA
• DFU via User USB (CN17) with JP4 on USB-PD position
• UART via ST-Link VCP

Setup:

• Board: STM32H573I-DK
• STM32CubeProgrammer: v2.22.0
• ST-Link FW: V3J17M10
• Voltage: 3.31V

Is there any way to recover this board? It seems RSS is not booting, which prevents DA entirely.

Thank you.

[Jocelyn RICARD]

Hello @gruna890 ,

I'm sorry for such late answer.

After step 1, you just had to launch regression.bat script provided in ROT_Provisioning/DA associated to the board.

It would have provisioned default DA credential and launch the regression.

For such issue it is not really a good idea to ask copilot because is mixes different STM32 and H5 is quite recent.

The fact that you can't discover the chip using DA on this DK board is not a good sign at all.

Only change is that you have removed an important jumper and your target is not powered properly. Please check you have a jumper on JP2.

Best regards

Jocelyn