cancel
Showing results for 
Search instead for 
Did you mean: 

Regression on a trust zone disabled STM32H563 in closed state and DA_cofig.obk not programmed

NithinKurian
Associate

Hi

I have STM32H563 Nucleo board which is in closed state with DA_Config.obk not programmed, And the trust zone disabled. 
This was done by mistake, Is there a way to do regression on it.
Operations Done on the device.
1.Done the regression

2.Set the product state to provisioning

3.Programmed OEMiRoT_Config.obk

4.Set the device to closed state.

Logs from ST32Cube programmer on DA Discovery
10:40:20 : STM32CubeProgrammer API v2.19.0 | Windows-64Bits
10:44:38 : Start Debug Authentication Sequence
10:44:38 : SDMOpen : 624 : open : SDM API v1.0
10:44:38 : SDMOpen : 625 : open : SDM Library version v1.2.0
10:44:38 : open_comms : 513 : open : Asserting target reset
10:44:38 : open_comms : 517 : open : Writing magic number
10:44:38 : open_comms : 537 : open : De-asserting target reset
10:44:38 : open_comms : 584 : open : Communication with the target established successfully
10:44:38 : discovery: target ID.......................:0x484
10:44:38 : discovery: SoC ID..........................:0x00000000_00000000_00000000_00000000
10:44:38 : discovery: SDA version.....................:2.4.0
10:44:38 : discovery: Vendor ID.......................:STMicroelectronics
10:44:38 : discovery: PSA lifecycle...................:ST_LIFECYCLE_CLOSED
10:44:38 : discovery: PSA auth version................:1.0
10:44:38 : discovery: ST HDPL1 status.................:0xffffffff
10:44:38 : discovery: ST HDPL2 status.................:0xffffffff
10:44:38 : discovery: ST HDPL3 status.................:0xffffffff
10:44:38 : discovery: Token Formats...................:0x200
10:44:38 : discovery: Certificate Formats.............:0x201
10:44:38 : discovery: cryptosystems...................:ST Password
10:44:38 : discovery: ST provisioning integrity status:0xf5f5f5f5
10:44:38 : discovery: permission if authorized...........:Full Regression

1 ACCEPTED SOLUTION

Accepted Solutions
lobna
ST Employee

Dear @NithinKurian 

Unfortunately, in this situation the MCU is effectively lost (no way to regress or reopen it) because debug authentication was not provisioned before moving to the CLOSED lifecycle.

Best regards

Lobna

View solution in original post

1 REPLY 1
lobna
ST Employee

Dear @NithinKurian 

Unfortunately, in this situation the MCU is effectively lost (no way to regress or reopen it) because debug authentication was not provisioned before moving to the CLOSED lifecycle.

Best regards

Lobna