cancel
Showing results for 
Search instead for 
Did you mean: 

STM32U0

johannes-lichtenberger
Associate II

With the STM32CubeIDE I can't debug a firmware, as always the connection is lost: 

 

Download verified successfully

 

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Shutting down...

Exit.

 

Any ideas?

 

kind regards

Johannes

1 ACCEPTED SOLUTION

Accepted Solutions
STTwo-32
ST Employee

Hello @johannes-lichtenberger and welcome to the ST Community 😊.

I suggest you take a look at this Post. It should be helpful.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

5 REPLIES 5
Uwe Bonnes
Principal III

Tell us your hardware? Some commercial board or something you build? Check and test other cables and USB ports. Check wiring. Check your setup.

STTwo-32
ST Employee

Hello @johannes-lichtenberger and welcome to the ST Community 😊.

I suggest you take a look at this Post. It should be helpful.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

I've checked using other USB-Ports, but it didn't help. I'm going to check another USB 3 to USB-C cable, but I doubt, that it helps, either. The board is a new STM32U083C-DK.

kind regards

Johannes

Double check with STM32 Cube Programmer.

Any details on the ST-LINK/V2EC model used here?

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
johannes-lichtenberger
Associate II

Thanks, I've enabled the debugging PINs in the Cube / meaning removing them from the unused PINs... so, now it seems it's possible to debug without problems... 🙂

 

Thanks

kind regards

Johannes