Target Unknown Error 32

[Hvan .2]

Yesterday evening I worked on an application for a Nucleo-WL55JC and STM32CubeIDE could connect to the ST-LINK just fine. I closed my PC and this morning started it again. I am trying to upload code to the CM0Plus core and now I am getting the following error:

Target unknown error 32

Error in initializing ST-LINK device.
Reason: Unknown. Please check power and cabling to target.

Things I did to diagnose and solve:

I have checked the USB cable which is perfectly fine

I changed for another USB cable which did not change the situation.

I used a similar Nucleo board which was never used and got the same error.

I checked the settings in the debug configuration. All seems fine.

I tried to access and erase the chip with STM32CubeProgrammer -> THIS WORKS FINE

I made a new project and tried connecting to the chip with STM32CubeIDE. This does not work.

I tried to upload code to the CM4 core and this worked.

Does anyone know how to solve this? I am on a very tight deadline and now I am stuck...

[Hvan .2]

I continued finding the problem and got the debugger working again (however I still get an error in the console log).

I did a clean and rebuild of the project. Not sure if it matters, but did it anyway.

Also I re-entered the parameters for the debug configuration. Probably this did the trick although it is still weird that I didn't touch this at all.

Details of what I did can be found in this video by ST:

https://www.youtube.com/watch?v=6wUDOKXJBr4&t=42s

For other people who are newly working on this MCU: check out the series by ST on the STM32WL55 here

https://www.youtube.com/watch?v=ySA71JvO9aU

The quality and content of the video is very good!

[Hvan .2 · Accepted solution]

Update: I had exactly the same problem today. There is something definitely wrong in STM32CubeIDE.

Details of the bug:

-the settings of the CM0Plus debug configuration were changed without me touching them.

The changes that I found were:

Port number was reset to 61234

Reset behavior was put at connect under reset were it was set to 'None' previously.

After changing these settings back the debugging process could be initiated, but now I am stuck because the ST-LINK keeps the MCU under reset permanently. Guess this problem will cost a few hours of unnecessary work. Thanks for this!

[Hvan .2]

Somehow the reset signal is working again. But now the BUSY signal of the SUBGHZ radio is ALWAYS high!

Is there a way how I can change my user name? I want to change my name to ST Babysitter...

[Hvan .2]

Re-did the above-mentioned tutorial twice to no avail.

Checked the status of  the option bytes with cube programmer and none were set.

Decided to unlock the chip anyway because some option bytes are hidden and CubeProgrammer bricked 

the Nucleo.

Thanks for the damage. Today I lost 6 hours of work and one Nucleo board: 625 euros! Also: I have gotten not even one millimeter further in solving my problem. In fact I went 100 meters backwards... :)

[Hvan .2]

I spent another 10 hours on this problem to no avail! It is literally sickening to see that ST does not give a d*mn about the productivity of their customers. For the rest, I will go my own way and will not explain what the solution to problems are anymore. I don't support this exploitative way ST is using their customers to solve their support questions. @st: you should be DEEPLY ASHAMED!!