No ST-LINK detected Error message

[atzi]

I have been running an STM project for the past month using a NUCLEO STM32F401RE. Almost every time I try to run the program for the first time that day, I get an error message that there is no ST-LINK detected. Sometimes it will connect after a while of being connected but this time there is no connection whatsoever.

The LD1 light is slowly blinking red while the LD3 is lit red. I have updated to STMCubeIDE Version 1.18.0 and I have tried reinstalling ST-Link Server. I have also tried all ports on my Windows 11 with no luck.

I have run my program with no issue before so I am certain it is no issue with my written program or my wiring. I have set my debugging probe to ST-LINK GDB Server which had solved the problem before but now it has no effect. Any suggestions are welcome!

[KDJEM.1]

Hello @atzi and welcome to the community;

 

I recommend you to follow the steps mentioned in the following article to connect to the STM32 board using STM32CubeProgrammer: How can I connect to my STM32 evaluation board using STM32CubeProgrammer? 

Verify all physical connections, such as: USB cables and connectors, and try using a different USB port or cable.

 

Please look at this article: How to solve connection errors when connecting and programming the STM32 target board.

This article describes tips to prevent or fix errors encountered when connecting the STM32 target board to your computer such as:  “No target connected”, “Target not found”, “No ST-LINK detected”, and “ST-LINK connection error”.

I hope this help you.

Thank you.

Kaouthar

[Andrew Neil]

---

@atzi wrote:

I try to run the program for the first time that day, I get an error message that there is no ST-LINK detected.

---

In that state, can the PC itself even see the ST-Link?

Clearly, if the PC itself can't see the ST-Link, then nothing else will!

See: https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/tac-p/698105/highlight/true#M956

 

As it happens "for the first time that day", could that be related to the PC going to sleep overnight?

I have some USB devices which don't always wake properly after the PC has been asleep ...