STLINK-V3MINIE not detected in debug mode

[vaucher_b]

Hello,

Maybe you can help me, I am not able to start debug session with STLINK-V3MINIE.

Context is: Windows 10 64bit, Intel(R) Core(TM) i5-9400

STMCubeIDE V1.17.0 

Tried with 2 different STLINK-V3MINIE

the STLINK-V3MINIE is seen and updated correctly to V3J15M7 using STLinkUpgrade 3.15.7 tool

When trying to open a debug session, I get the message "No ST-LINK detected! Please connect ST-LINK and restart the debug session"

I tried >20 times, connecting on different USB ports, different USB cables, 2 different STLINK-V3MINIE. I tried to switch OFF the firewall.

When I use my old STLINK-V3MINI it is working fine

When I use a Nucleo board, it is working fine

Any idea what I should do? Thanks

[Andrew Neil]

---

@vaucher_b wrote:

I get the message "No ST-LINK detected! Please connect ST-LINK and restart the debug session"

---

So can Windows itself see the ST-Link? ie, does it appear in Device Manager:

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

Note the PS there specifically for ST-Link V3

 

---

@vaucher_b wrote:

updated correctly to V3J15M7 using STLinkUpgrade 3.15.7 tool

---

Maybe it's stuck in update mode?

What happens if you try again with the updater?

[vaucher_b]

Thanks for your quick reply

In Device manager, it appears as "ST-Link Debug"- driver date 01.04.2021, version 2.2.0.0

and "Virtual COM Port"

It seems there is no error there.

The update process seems working correctly, I can update again, and I see "Upgrade Successful."

 

[Andrew Neil]

Did you see the note specific to ST-Link V3?

https://community.st.com/t5/stm32-mcus/faq-possible-communication-failure-between-stlink-v3-and-some/tac-p/736830

[vaucher_b]

Yes. I think this is not the root cause, because the computer is old (Intel(R) Core(TM) i5-9400) and it is working fine with older STLink such as Nucleo and the old STLINK-V3MINI.

When I open the menu "Run>Debug Configurations" from STM32CubeIDE , tab "Debugger", I can read the debugger S/N (result is 002E00193133510737363734).

I tried with and without USB hub, USB2 and USB3 ports on computer, it's always the same, in device manager it shows the items, in update tool it shows the STLINK-V3MINIE, but debug session always stop with the message "No ST-LINK detected! Please connect ST-LINK and restart the debug session".

Can you explain why the old STLINK-V3 are performing well, but the new STLINK-V3MINIE fail? Is there an important hardware/software difference other than the USB-C socket on the STLINK-V3MINIE and micro-USB on older types?

 

[Andrew Neil]

If it can read the serial number, then CubeIDE can see the ST-Link.

Are you sure you didn't have something else already using the ST-Link (eg, CubeProgrammer) ?

[vaucher_b]

Yes sure, only Only STM32CubeIDE is open. I checked task manager too, restart computer too. Is it useful to try re-installing CUBE-IDE?

[Kraal]

So the ST-Link is being seen correctly by the IDE, but as soon as you start the debug session, it disconnects...

Could it be that the device you are debugging is setting its pins in such a way that you have a bus contention with the debug probe (that could cause a voltage drop on the miniE so it resets) ? How is the connection between the ST-Link MINIE and the device under test ? Is it the same as with the old ST-Link MINI ?

[TDK]

What does your program do? Does it enter low-power modes or reassign the SWD pins?

[vaucher_b]

Hello Kraal, the issue occurs earlyer, the ST-Link MINIE appears unconnected while trying th start a debug session, but it correctly connected and recognized for other actions (enumeration in device manager, S/N reading, upgrade it's firmware)

[vaucher_b]

To anwser your question, my software do not enter in low power mode. I was able to debug it in the past year using my old ST-Link MINI

[Kraal]

I see the error message, but what is written in the debugger console when you try to debug ?

Maybe there you would get more information.

Another try would be to use the command line, as it is usually more verbose: either gdb server or CubeProgrammer_CLI.

Also, do you really need to specify the S/N in the debug config ? From your device manager you only use one at a time (apparently, I'm only assuming here), so it shall not be mandatory.

[vaucher_b]

I just checked again, it is still possible to debug with a Nucleo board and with the old ST-Link MINI.

The problem is limited to the ST-Link MINIE (I tested 3 different ST-Link MINIE interfaces).

[Andrew Neil]

---

@vaucher_b wrote:

The problem is limited to the ST-Link MINIE (I tested 3 different ST-Link MINIE interfaces).

---

Again, if CubeIDE can read the ST-Link's serial number, then it can see the ST-Link - so it should be able to debug.

As @Kraal said, have you tried  to debug without specifying the serial number?

If you specify the wrong serial number, then CubeIDE won't connect - even when it can see the ST-Link.

 

As @Kraal said, please post the complete console output when you attempt to start a debug session: copy & paste as text rather than a screenshot.