Sometimes Cubeprogrammer notifies "Error: unable to reset the MCU" on STM32H562

[JungerGott]

Hi,

if I connect the Cubeprogrammer via jlink to the custom board (STM32H562) and want to reset the option bytes by menu-selection "Reset MCU to factory settings", the process don't finish because the mentioned error pops-up.
Is this caused due to a missing signal on the debug connector? 
The problem is now, that the mcu is in provisioning state and I want set it back to open state.

Kindly regards,
Stefan

[Kouthair]

Hello Stefan,

Thank you for reporting this issue, I have reproduced the error concerning the pop-ups on my side "Unable to reset MCU", and I have reported this to the dedicated team. (Internal ticket number: 225526)

However, I was not able to reproduce the provisioning state, could you share any additional details (logs, steps, setup) that could help during this investigation?

PS: Ticket number: 225526 is an internal tracking number and is not accessible or usable by customers.

[JungerGott]

Hello Kouthair,

just put the MCU into provisioning state and try to do the regression to bring it back to state open. This is not possible via jlink because of the error I mentioned. I don't have logs, sorry.

BR
Stefan

[Kouthair · Accepted solution]

Hello again Stefan,

Unfortunately, Debug authentication is not currently supported through J-link. You'll have to use connect through ST-Link (SWD/JTAG) in order to go back to open state using DA or "Reset MCU to factory settings". 

Useful links:
Implementing debug authentication on STM32H5 - STMicroelectronics Community