Skip to main content
Explorer
January 19, 2025
Solved

STM32C0116-DK - On-board ST-Link failed after update process

  • January 19, 2025
  • 1 reply
  • 570 views

Hello,

 

I have a brand new STM32C0116-DK evaluation board (official) and I fear I just bricked the on-board ST-Link :\

 

I wanted to run an example (blink LED) from the CubeIDE provided examples. When I pressed run, a popup displayed to notify me the ST-Link firmware should be updated. So I launched the process but the popup window freezed. I closed CubeIDE and disconnected the USB cable... Now the ST-Link LED is blinking RED at about 0,5 Hz and Windows doesn't detect any USB device at all (nothing is enumerated in device manager, nor a "USB device not working properly" popup) I think I did a mistake...

I will need it to work from home home for the two weeks. Is there a way I can force it to pass in update mode? I only have this board at hand right now, so is the only ST-Link debugger I have (had)...

    This topic has been closed for replies.
    Best answer by KnarfB

    Its not so easy to brick the board...

    STM32CubeProgrammer is IMHO the most reliable tool for accessing a board including ST-LINK updates.

     ST-Link LED is blinking RED at about 0,5 Hz

    This happens when power is on, but no USB comm. Try to reset the USB port / repower the computer.

    hth

    KnarfB

    1 reply

    KnarfBAnswer
    Super User
    January 19, 2025

    Its not so easy to brick the board...

    STM32CubeProgrammer is IMHO the most reliable tool for accessing a board including ST-LINK updates.

     ST-Link LED is blinking RED at about 0,5 Hz

    This happens when power is on, but no USB comm. Try to reset the USB port / repower the computer.

    hth

    KnarfB

    Loic_C137Author
    Explorer
    January 20, 2025

    [Resolved]

    Hi KnarfB,

    Thank you for your quick answer! Yes I know ST products are robust, but wasn't sure at which point the firmware was secured!

    This morning the board was working fine after a complete PC shutdown and USB unplugged. I think it was an issue with the computer USB 3.2 port. When I restarted the computer this morning, I plugged the board on a USB 2.0 port and it was working fine. I did not try again the USB 3.2 port at the moment but I was able to work with the board. 

    In the same time I ordered a second kit regarding as cheap as it is ;)