Help with st-link

So I didn’t look hard enough for the ‘Connect Under Reset’ option, found it but still had no luck…

11:40:51 : Can not connect to target!
If you're trying to connect to an STM32W1xx device, please select Normal or HotPlug mode from Target->Settings menu.
If you're trying to connect to a low frequency application , please select a lower SWD Frequency mode from Target->Settings menu.
11:40:53 : No target connected


PS, unfortunately the st-link clone only came with 4 dupont leads so I can’t power the board from it just yet – hence why USB power.

Found this russian posts which says reset isn’t needed. http://nuzhen-sovet.ru/content/podklyuc … k-v2-kitay

Removed reset, and powered the board from the st-link, still no leds light on the board and cant connect.

Tried my working board, the leds flash, but still can’t connect.

I’m clearly doing something wrong. I’ve tried a few different frequencies too – default was 4mhz.

btw, just a tip if you like working with electronics: at least make sure you’ve got the basic stuff like the wires .
i’ve got tons of dupont wires (male-male, female-female & female-male) just for the reason you just mentioned: it’s so stupid to not have them when you need them. especially when it costs next to nothing .

And the last time i had issues with flashing, flashing under reset did work, but i don’t know what exactly i had to do to get it to work. i also fiddled with it until it worked . (but i did have 5 cables :p )

i’ve added a reference to this thread to http://www.stm32duino.com/viewtopic.php?f=10&t=1740
hopefully something on how to unbrick will emerge
stephen

racemaniac wrote:btw, just a tip if you like working with electronics: at least make sure you’ve got the basic stuff like the wires .

Unbricking from Linux…

https://github.com/rogerclarkmelbourne/ … from-Linux

… for what its worth, when I wrote that, I only used 3 “du-pont” wires… It shows how to connect to a Bluepill and the “Uggly board” but it should work with pretty much any stm32fXXX board, so the mm will work too. The version of Linux is not important. So long as the version of openocd is fairly recent you should be fine.

Connecting under reset with openocd will unbrick pretty much any screwup that doesn’t actually result in smoke.

Pinout for stm32f103 is

Programmer -> Target

Ground (Green) -> GND

SWDIO (Blue) -> PA13

SWCLK (Yellow) -> PA14

(Colour of wire is up to you of course )

If still dead, unplug the maple mini USB and connect the 3v3 pin from the programmer to 3v3 on the mm and try again.

Thanks, gave that a try but neither board responds.


Open On-Chip Debugger 0.10.0+dev-00001-g0ecee83 (2017-01-27-13:59)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v27 API v2 SWIM v6 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.233618
Error: init mode failed (unable to connect to the target)
in procedure 'init'
in procedure 'ocd_bouncer'


The other possibility of course is that the st-link v2 clone is faulty.

Have you updated the V2 firmware?
https://www.youtube.com/watch?v=DC5tlE6XOIg

stevestrong wrote:Have you updated the V2 firmware?
https://www.youtube.com/watch?v=DC5tlE6XOIg

Can you connect the STlink to the target with the STlink utility?

stevestrong wrote:Can you connect the STlink to the target with the STlink utility?

BennehBoy wrote:stevestrong wrote:Can you connect the STlink to the target with the STlink utility?

Are you sure I should power the target with USB AND 3.3 from the st-link? I thought this would result in magic smoke?

Tried with the settings you supplied (used these earlier too), failed. Tried resetting the board, still fails.

For fear of destroying the board I _did not_ also connect it via USB whilst 3.3 was being supplied to the VCC pin.

Here’s a photo of the wiring:
Image

BennehBoy wrote:Are you sure I should power the target with USB AND 3.3 from the st-link? I thought this would result in magic smoke?

It’s steadfastly refusing to connect.

I think this st-link clone hardware must be garbage. I can feel a stamping frenzy coming on.

I continuity checked the dupont leads just for peace of mind, all are good.

BennehBoy wrote:It’s steadfastly refusing to connect.

I think this st-link clone hardware must be garbage. I can feel a stamping frenzy coming on.

I continuity checked the dupont leads just for peace of mind, all are good.

racemaniac wrote:
And it’s a good advice that Roger likes to repeat on this forum: always have 2 of whatever you’re working on. it’s cheap chinese stuff, something will be broken or break, and if you then have to wait a month for the replacement to arrive…