Genuine STLINK-V3MINIE doesn't work, but clone STLINK-V2 works

[Chupacabras]

I'm trying to make genuine STLINK-V3MINIE to work, but without success.

The target device is STM32F103C8T6.

VCC is connected to T_VCC (pin 3 of STDC14)

SWCLK is connected to T_SWCLK (pin 6 of STDC14)

SWDIO is connected to T_SWDIO (pin 4 of STDC14)

RESET is connected to T_NRST (pin 12 of STDC14)

GND is connected to GND and GNDDetect (pins 5, 7, 11 of STDC14)

STM32CubeProgrammer is properly detecting STLINK-V3MINIE, even shows voltage of the target.

But when I try to connect to target, it gives message:

Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

This is text from console:

  12:56:46:283 : UR connection mode is defined with the HWrst reset mode
  12:56:46:837 : ST-LINK SN  : [redacted]
  12:56:46:838 : ST-LINK FW  : V3J16M7
  12:56:46:838 : Board       : STLINK-V3MINIE
  12:56:46:838 : Voltage     : 3.29V
  12:56:46:839 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
  12:56:46:876 : Disconnected

I tried another PC, but with the same result.

When I connect clone STLINK-V2 instead of genuine STLINK-V3MINIE, I'm able to connect to target MCU, and download program to target.

This is the output from console:

  13:00:39:502 : UR connection mode is defined with the HWrst reset mode
  13:00:39:667 : ST-LINK SN  : [redacted]
  13:00:39:667 : ST-LINK FW  : V2J45S7
  13:00:39:667 : Board       : --
  13:00:39:667 : Voltage     : 3.18V
  13:00:39:667 : SWD freq    : 4000 KHz
  13:00:39:667 : Connect mode: Normal
  13:00:39:667 : Reset mode  : Hardware reset
  13:00:39:668 : Device ID   : 0x410
  13:00:39:668 : Revision ID : --
  13:00:39:668 : flash loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/FlashLoader/0x410.stldr is loaded
  13:00:39:668 : Debug in Low Power mode is not supported for this device.
  13:00:39:668 : Reading data...
  13:00:39:668 : r ap 0 @0x1FFFF7E0 0x00000004 bytes Data 0x00140040
  13:00:39:957 : UPLOADING OPTION BYTES DATA ...
  13:00:39:957 :   Bank          : 0x00
  13:00:39:957 :   Address       : 0x4002201c
  13:00:39:957 :   Size          : 8 Bytes
  13:00:39:958 : Reading data...
  13:00:39:958 : r ap 0 @0x4002201C 0x00000008 bytes Data 0x03FFFFFC
  13:00:39:959 :   Bank          : 0x01
  13:00:39:959 :   Address       : 0x1ffff800
  13:00:39:959 :   Size          : 16 Bytes
  13:00:39:959 : Reading data...
  13:00:39:959 : r ap 0 @0x1FFFF800 0x00000010 bytes Data 0xFFFF5AA5
  13:00:39:960 : UPLOADING OPTION BYTES DATA ...
  13:00:39:960 :   Bank          : 0x00
  13:00:39:960 :   Address       : 0x4002201c
  13:00:39:960 :   Size          : 8 Bytes
  13:00:39:960 : Reading data...
  13:00:39:961 : r ap 0 @0x4002201C 0x00000008 bytes Data 0x03FFFFFC
  13:00:39:961 :   Bank          : 0x01
  13:00:39:961 :   Address       : 0x1ffff800
  13:00:39:961 :   Size          : 16 Bytes
  13:00:39:962 : Reading data...
  13:00:39:962 : r ap 0 @0x1FFFF800 0x00000010 bytes Data 0xFFFF5AA5
  13:00:39:962 : UPLOADING ...
  13:00:39:962 :   Size          : 1024 Bytes
  13:00:39:963 :   Address       : 0x8000000
  13:00:39:963 : Read progress:
  13:00:39:963 : Reading data...
  13:00:39:964 : r ap 0 @0x08000000 0x00000400 bytes Data 0x20005000
  13:00:39:964 : Data read successfully
  13:00:39:964 : Time elapsed during the read operation is: 00:00:00.007

What is the problem with STLINK-V3MINIE?

How to make it work?

It's pretty frustrating that clone works and genuine debugger not.

[AScha.3]

OK, but power has to come from same outlet.

So try it.. to prove, it's not a problem with some high frequency stray in.

And no other ground connections on this PC.

[Carl_G]

I don't think power needs to come from the same outlet. As long as the MINNIE shares a GND with the power source and also the MINNIE is correctly measuring the MCU voltage I think the power system is working. Sure there could be some ground loop noise since the power source for the board is isolated. Especially so if the USB cable is shielded and connected on both ends. So attempting with a non-isolated source couldn't hurt.

[Chupacabras]

I tried to power the target by laboratory power supply. A notebook runs on battery (power brick disconnected).

Problem still persists.

It doesn't seem to be related to ground loop.

[AScha.3]

Ok, this has to be tested.

But then only possible : your wires are puzzled (gnd+gnd.detect, swd, swc, vcc) - connect only this, check it - again.

And try with CubeProgrammer to connect.

If still nothing...look with a scope, whats on swd /swc . You might damaged the st-link-V3.

[Carl_G]

Try with laptop plugged in wall. But really it just looks like a bad MINNIE. Did you try to update the MINNIE firmware?

[Chupacabras]

I looked into signals by oscilloscope. There was some activity, similar between STLINK2 clone and STLINK-V3MINIE.

Reset line had 1 pulse. SWCLK had proper clock signal,  SWDIO had some data.

Then I recorded communication with logic analyzer. Saleae Logic has luckily SWD protocol analyzer.

The communication is working at first glance.

First difference there is in length of reset pulse. In STLINK2 clone is very short, in STLINK-V3MINIE is much longer. STLINK2 first sends data, then sends short reset pulse. STLINK-V3MINIE holds reset line down and communicate with reset line down. I have no idea if it plays a role.

Then I compared data itself. I'm not familiar with SWD protocol.

I see first difference in WData at time -43.7ms (STLINK2) and +2.3ms (STLINK-V3MINIE) (time is relative to start of reset line trigger). Where is some "reg IDR" value.

In STLINK2: 0x13030410

In STLINK-V3MINIE: 0x00000000

[Chupacabras]

I tried different versions of MINNIE firmware. I have the latest one currently.

[AScha.3]

Wow, thats really strange, until now i had 3 possible ways for st-link connection:

1. connect - fine. ok.

2. connect - then error ; typical for some ground loop , long wires or stray in /noise.

3. no connect - no power, wires puzzled, or defective st-link or damaged target.

here: connect - begins communication - but then . nothing ? error. Thats new.

Please show pic , what CubeProgrammer telling after "connect"...i like to see.

[Chupacabras]

Console output is in first post.

STM32CubeProgrammer just gives error message. Error message is same as the one in console.

[Andrew Neil]

---

@Chupacabras wrote:

The target device is STM32F103C8T6.

---

Are you sure that this device is genuine?

Does the V3MINIE work with any other targets?