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.

[STea]

Hello @jowakar122 ,

can you try to follow the steps I've mentioned with Cubeprogrammer GUI (graphical interface) as the screenshot you sent is nothing near what I have described.

For your reference, I have tried the same manipulation you did which is:

• change the state to provisioning with the default password 
• disconnect from cube programmer 
• go to the secure programming panel
• pressing on discover 
• doing a regression (pressing full regression and not executing the script) with the default password as I have mentioned in the reply above 

this is working as expected from my side so you will need to do the same steps not with CLI (no cli action is needed)
Regards

[jowakar122]

How is it possible to move forward when this kind of errors. Can't connect through CubeProgrammer and can't perform discovery. What might be the reasons or parameters that are causing this kind of errors?

[STea]

Hello @jowakar122 ,

in here you show that you are able to connect with cubeprogrammer via GUI interface and show that you are in provisioning stat (value 17) .and now you are unable to connect, I don't get it what is really happening, is it the first or second case?
Regards

[jowakar122]

I am not able to connect now, earlier I was able to connect in HOTPLUG mode but now that is also not happening.

[jowakar122]

@STea Is there any other way to recover my device. I think it has been locked completely.

[STea]

Hello @jowakar122 ,

I'm afraid if you couldn't connect to cubeprg or perform discover command you can't do much. I don't know exactly what the status of your device is as you couldn't connect to it, and I don't know what was done to it to be in this kind of situation. if it is still in provisioning state try to connect to the bootloader and send command to revert the state of the device to open (see table 115 of STM32 microcontroller system memory boot mode - Application note)
see if this article might help you to continue the provisioning phase and try to move to close state and then perform a regression if you are able to connect via CubePRG CLI.

Regards

[jowakar122]

I tried the method you have mentioned but I got  this error:

[STea]

Hello @jowakar122 ,

I think that you got the device licked throw a combination of option byte settings that weren't supposed to be in the order you set them and thus you couldn't recuperate the device.
Regards