ahh409
ahh409

Reputation: 1

"No ST-LINK connected!" issue with Nucleo-F413ZH

I'm trying to flash a basic LED blinking program to my Nucleo F413ZH board using the STM32CubeIDE, but whenever I try to debug it says:-

"No ST-LINK connected! Please connect ST-LINK and restart the debug session."

The board has the PWR and COM LEDs blinking, meaning the USB I've connected to the board is providing power, I just can't upload any code.

I've tried using the ST-LINK upgrade firmware (https://www.st.com/en/development-tools/stsw-link007.html) to install new drivers as that's what some people online have suggested but the program won't respond once I've downloaded it, which seems to be a side issue of not registering connectivity.

I'm not sure whether this is an issue with drivers or if my hardware is busted. I'm using macOS Big Sur.

Upvotes: 0

Views: 4326

Answers (3)

Hakeem Khan
Hakeem Khan

Reputation: 1

I tried many ways to remove this error, but it didn't work. When I changed the cable which is connected to USB to Nucleo. It worked.

Upvotes: 0

Chr_arj
Chr_arj

Reputation: 1

I was also getting the same error on ubuntu system while using stm cube ide, with st-link v2 programmer. blue led was continuously blinking. but solved the error just by reconnecting the usb-extention-hub, now when connected blue led is on (no blink), and now i can program and debug the target.

Upvotes: 0

Jeffrey Morrison
Jeffrey Morrison

Reputation: 1

In Windows 10 this problem occurs as a result of an incorrect driver priority as pointed out in this post. Error in initializing ST-Link Device - Failed to connect to device perhaps this solution might point you in the right direction. I have set up several new M1 Mac Minis in the past few months for clients, Big Sur and the new M1 have several compatibility issues like slow network drive access and flashing screens, the Android M1 chip has dramatically less external connectivity which is why they went from 4 thunderbolt ports on the last intel Mac Mini to just 2. I would not be surprised if Big Sur is the core of the problem. Try a different computer if you have the opportunity.

Upvotes: 0

Related Questions