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

[vaucher_b]

Ok, without S/N is the same. Console is not showing anything about debug, only about compilation:

15:11:36 **** Incremental Build of configuration Debug for project P334A ****

make -j6 all

arm-none-eabi-size P334A.elf

text data bss dec hex filename

26588 72 9792 36452 8e64 P334A.elf

Finished building: default.size.stdout

 

 

15:11:36 Build Finished. 0 errors, 0 warnings. (took 372ms)

 

I will try CLI

[Andrew Neil]

All you've showed there is the build output.

You need to show the output when it tries to start a debug session.

It will look something like this:

STMicroelectronics ST-LINK GDB server. Version 7.4.0
Copyright (c) 2023, STMicroelectronics. All rights reserved.

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled

Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
-------------------------------------------------------------------
STM32CubeProgrammer v2.14.0 
-------------------------------------------------------------------
Log output file: C:\Users\xxxx\AppData\Local\Temp\STM32CubeProgrammer_a01932.log
ST-LINK SN : 0032004D3137510239383538
ST-LINK FW : V3J15M7B5S1
Board : STLINK-V3SET
Voltage : 3.28V
SWD freq : 8000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x440
Revision ID : Rev 2.0
Device name : STM32F05x/F030x8
Flash size : 64 KBytes
Device type : MCU
Device CPU : Cortex-M0
BL Version : 0x21

Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a01932.srec
File : ST-LINK_GDB_server_a01932.srec
Size : 46.74 KB 
Address : 0x08000000

Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 46]
Download in Progress:

File download complete
Time elapsed during download operation: 00:00:03.015

Verifying ...

Download verified successfully

 

[AScha.3]

Hi,

what shows : CubeProgrammer with your MiniE ?

+

Try a good USB2 cable to MiniE ; and no other connections to mains ground - hi speed ground "noise" might stop any connection.

[vaucher_b]

This is what I get from CLI try (copy-paste from console)

C:\ST\STM32CubeIDE_1.0.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin>STM32_Programmer_CLI.exe -c port=SWD
-------------------------------------------------------------------
STM32CubeProgrammer v2.18.0
-------------------------------------------------------------------

ST-LINK SN : 002E00193133510737363734
ST-LINK FW : V3J15M7
Board : STLINK-V3MINIE
Voltage : 3.27V
SWD freq : 8000 KHz
Connect mode: Normal
Reset mode : Software reset
Device ID : 0x468
Revision ID : Rev X
Device name : STM32G43x/G44x
Flash size : 128 KBytes
Device type : MCU
Device CPU : Cortex-M4
BL Version : 0xD4

C:\ST\STM32CubeIDE_1.0.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin>

[vaucher_b]

This is another try:

C:\Users\berni>C:\ST\STM32CubeIDE_1.0.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.0.202409170845\tools\bin\ST-LINK_gdbserver.exe -p 61234 -l 1 -d -s -cp C:\ST\STM32CubeIDE_1.0.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin -m 0 -k

STMicroelectronics ST-LINK GDB server. Version 7.9.0
Copyright (c) 2024, STMicroelectronics. All rights reserved.

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled

Waiting for debugger connection...

[Andrew Neil]

If you get the serial number wrong (or specify a serial number, and that particular ST-Link is not present), you get this error:

 

Is that what you're getting?

[vaucher_b]

The lucky fact is that I have older STLINK-V3 (nucleo and other), and I can reproduce all your messages and console logs with these older hardware.

But with the new MINIE, it failing. USB cable is perfet, I tried 3 different tested cables.

I will stop searching, put my new few STLINK-V3MINIE aside for later and try to buy old hardware instead.

Thank you for trying to help!

[vaucher_b]

One last post to follow the topic

I tested on my old AMD computer, Windoes 10, and it is debugging correctly. The driver that Windows has automatically installed for ST-Link Debug (seen in device manager) is different. Driver version 10.0.19041.1 Driver Date 21.06.2006.

The note specific to ST-Link V3 apply to my 2017 computer, but only for STLINK-V3MINIE, not fot other STLINK-V3.

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

I hope my difficuties can helo ST team to figure-out the issues with driver and provide a fix or turnaround.