STM32H563Zi: Error in initializing ST-LINK device.

[jowakar122]

Hii,

I am using Nucleo-H563Zi. Suddenly I got  "Error in initializing ST-LINK device" Reason: Unknown. Please check power and cabling to target. What I have tried to solve this:

. Connected pin BOOT0 and VDD and tried to connect to cube programmer.

. tried using power down and under reset mode to connect 

none of the above helped me to connect and earse the full chip.
I have gone through every thread related to this problem but none helped. I have ran out of options. It would be great if someone assist me in this problem.

[Andrew Neil]

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/tac-p/698105/highlight/true#M956

[STea]

Hello @jowakar122 ,

did you change the default OptionBytes with cube programmer before this issue popped ?

do you have a firmware on your board related to security, OptionByte software configuration or any other protections?

did you try to connect using another cable? 
Regards

[jowakar122]

I changed the product state value to 17. 
I was trying to implement OEMiROT_BOOT on my device by following: How to start with OEMiRoT on STM32H573 and 563–Arm® TrustZone® enabled. Yes, I tried connecting using another cable.

I also tried to change the product state value but can't

[STea]

Hello @jowakar122 ,

did you try to execute the regression script as described in the wiki page section: 2.6.1. Full regression from Provisioned state using a script (included in the STM32CubeFW)
did you follow the necessary steps for the provisioning phase described in the WIKI or you changed the state manually via cubeProgramer ?
Regards

[jowakar122]

No, I didn't execute the regression script. I changed the state manually using cubeProgramer

[jowakar122]

Later I tried the full regression, but I got an error.   I checked all the files path that are used in the regression script and everything was at place. Then I tried to run one command at time as it was in the regression file to find out where the problem lies. And the first thing that takes place in regression is to stop/halt debug authentication using  cli command: "debugauth=3". It was unable to open SDM  Lib.

 Then I upgraded STM32CubeProgrammer and ST-Link but still the error remains.

[jowakar122]

@STea  would be great if you help me out with the problem.

[STea]

Hello @jowakar122 ,

1. open cubeProgrammer 
2. go to secure programming panel
    
3. click on discover while the device is disconnected
4. if you have supplied the default password when switching to provisioning state perform a full regression with the default password in the following path C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\DA_Default_Config\STM32H5\password.bin

Regards 
Hichem

[jowakar122]

Has my device got locked or what? Even with your suggestion nothing is happening.