The STM32H563 cannot be connected after Secure Debug opening through Debug Authentication.

[兔兔]

Hello, I currently working with a NUCLEO-H563ZI Development Board.

I executed a script(Provisioning.bat) and set the product state to CLOSED according to the tutorial(How to start with OEM-iROT on STM32H573 and 563–Arm® TrustZone® enabled?).

I used debug authentication to turn on secure debug and succeeded, but still couldn't connect the chip with STM32CubeProgrammer.

Could you please assit me to look for steps that went wrong?

Best Regard.

[Issamos]

Hello @兔兔 

I suggest you to take a look at the AN5054 and the UM2237. That may help you to solve your issue.

Best regards.

II

[Jocelyn RICARD]

Hello @兔兔 

Have you got a running application in the flash ?

Are you still able to do a regression?

Best regards

Jocelyn

[兔兔]

Hello @Jocelyn RICARD 

I'm sorry for not responding in a timely manner.

The program in flash can execute normally(OEM-iROT,Secure code and non-secure code).

Still able to do a regression through debug authentication.

Best regards.

[Jocelyn RICARD · Accepted solution]

Hello @兔兔 

When running OEMiROT, you are running in secure HDP Level 1.

Then OEMiROT jumps to secure application and switches to HDP Level2

Secure Application jumps to non secure application and stay in HDP Level2.

So, if you want to re-open the debugger you need to select the right HDP level.

So, setting Secure Intrusive Level 1 should allow you to connect with the debugger when the code is executing the code of OEMiROT. If you select Level 2, then should be able to connect once the code is executing in secure application

Best regards

Jocelyn