FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

ST link v3set unable to recognize anything after connected to USB

NEdom.1
Associate III

‎2024-11-01 12:06 AM - edited ‎2024-11-01 12:08 AM

I started to use this stlink v3set since year 2023. All works well until recently it get offline and reconnected immediately sometimes. The red light flashes several times then stays on after connect to USB. The STLINK_V3S disk is opened in an explorer.

The firmware for this programmer set is V3J15M7B5S1. I tried to downgrade it to V3J15M6B5S1 using CubePrg but with no luck.

NEdom1_1-1730444139802.png

 

 

Whenever downloading code in STM32CubeIDE, I get this error message:

Error in initializing ST-LINK device.
Reason: No device found on target.

Anyone could help? Thanks

Btw, I bought a J-link EDU to replace this malfunctioned stlink v3set just in case that it could be fixed.

Labels:
0 Kudos
3 REPLIES 3
SofLit
ST Employee

‎2024-11-01 12:40 AM

Hello,

It could be something related to your target not to the ST-LINK. Did you try it with another target board?

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.
Ozone
Lead II

‎2024-11-01 01:13 AM

As said, consider the target your STLinkv3 is attached to has some problems.
I once had an application which I had to power externally, the STLink could not supply enough current and bailed out.

Segger has a JLink firmware for internal STLinks for free download on its website, I think it supports V3 as well.
And this firmware is not a one-way street, you can go back to ST-Link firmware later.
You could check if this JLink firmware behaves better.

0 Kudos
Andrew Neil
Evangelist III

‎2024-11-01 01:50 AM

@NEdom.1 wrote:

Whenever downloading code in STM32CubeIDE, I get this error message:

Error in initializing ST-LINK device.
Reason: No device found on target.

Please show the full connection log - see:

https://community.st.com/t5/stm32-mcus-boards-and-hardware/st-link-clone-connects-using-st-link-utility-but-not/m-p/737753/highlight/true#M22303

But what you showed suggests that the problem is between the ST-Link and your target device.

So, as others have said, probably an issue with your target and/or connections - rather than the ST-Link itself.

Have you added low-power, and/or disabled/reassigned the SWD pins in your target?

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693

 

0 Kudos
Top