Debug problem with clone st-linkv2

[AnilKose]

Hi everyone!

I use stm32f103c8t6 and clone st-linkv2 when i try to debug my codes with stmcubeide i had a lot of errors. Like connection error or debug path etc. I cant solve it. When i use MDK-ARM code is working but i cant get any data. Please help!

[Andrew Neil]

I'm in the UK. I've never lived in a city here were I'd be able to just pop into a shop and buy something like an ST-Link off the shelf.

Surely, you must be able to find a distributor where you can order online for next-day delivery?

[AnilKose]

I will contact with the links below.

[Andreas Bolsch]

Indeed, it's not nice to use clones. But anyway as you're in a hurry: I came across a whole batch of clones which had 100 Ohms series resistors in SWCLK and SWDIO lines (a bit high, but not the primary obstacle) and with 1k2 Ohm pull-down and pull-up on SWCLK and SWDIO, respectively. Removing the 1k2 pull-down on SWCLK cured the problem.

https://www.mikrocontroller.net/topic/515218

The symptom was unreliable connection, sometimes ok for a few seconds, then breaking reapeatedly, parity errors ...

So, check for sensible resistor values.

[Andrew Neil]

Indeed, to be fair, I have used clones in the past and they have worked.

Another thing to beware of is that clones which look identical might have different pinouts!

Addendum:

See also: https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/tac-p/703663/highlight/true#M965 

And some users have reported that the RST (Reset) does not work for STM32 (only STM8):

https://community.st.com/t5/stm32-mcus-boards-and-hardware/no-swd-target-connection-with-stm32f103-on-custom-pcb/m-p/733016/highlight/true#M22028

[BarryWhit]

Clones (I mean of the type shown in the pictures andrew posted) also do not provide a SWO pin (without modding) needed for "Serial Wire Viewer" (SWV) debug functionality with CubeIDE, which is a very useful feature to have during development.