Help with st-link

User avatar
BennehBoy
Posts: 418
Joined: Thu Jan 05, 2017 8:21 pm
Location: Yorkshire
Contact:

Re: Help with st-link

Postby BennehBoy » Fri Jan 27, 2017 5:12 pm

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...


I bought 3.

One turned up dead - misaligned st chip and solder bridges.

One worked, then I decided to upload bootloader v2 to it using victors sketch - it bricked (think I tried this just before victor updated it to check for page locking).

So I still have 1 good board - this is on my breadboard.

I'm trying to recover the bricked one so I can build a stripboard prototype to go into my project vehicle to replace the Nano that's currently running the system that I'm building. See here -> https://github.com/BennehBoy/LRDuino

The gpio and memory requirements have grown beyond at328.
-------------------------------------
https://github.com/BennehBoy

victor_pv
Posts: 1228
Joined: Mon Apr 27, 2015 12:12 pm

Re: Help with st-link

Postby victor_pv » Fri Jan 27, 2017 5:51 pm

BennehBoy wrote:
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...


I bought 3.

One turned up dead - misaligned st chip and solder bridges.

One worked, then I decided to upload bootloader v2 to it using victors sketch - it bricked (think I tried this just before victor updated it to check for page locking).

So I still have 1 good board - this is on my breadboard.

I'm trying to recover the bricked one so I can build a stripboard prototype to go into my project vehicle to replace the Nano that's currently running the system that I'm building. See here -> https://github.com/BennehBoy/LRDuino

The gpio and memory requirements have grown beyond at328.


Can you check if the stlink works on the other boards? I would test even of the faulty mini.
If it can connect to the mcu in any of the other boards, you know the stlink is good.
If you have a usb to serial adapter, you can reflash the bootloader with that. The instructions I think are in the wiki (wiki.stm32duino.com)

Btw, I have one of those stlinks too, I think almost everyone here got one of those in a color or another, but I don't think they normally fail often, I rather doubt the maple mini clone, since you already confirmed 1 of 3 was faulty. Perhaps one of the solders for SWD pins in the mcu is bad?
You can test continuity between the header and the MCU pin to confirm.
Should be enough to just add some flux and a quick pass with a clean soldering iron.

User avatar
BennehBoy
Posts: 418
Joined: Thu Jan 05, 2017 8:21 pm
Location: Yorkshire
Contact:

Re: Help with st-link

Postby BennehBoy » Fri Jan 27, 2017 6:18 pm

I tried both the bricked board and the working one, neither connects.

Just checked continuity and it's good.

:(

I hope I'm just doing something stupid...
-------------------------------------
https://github.com/BennehBoy

User avatar
BennehBoy
Posts: 418
Joined: Thu Jan 05, 2017 8:21 pm
Location: Yorkshire
Contact:

Re: Help with st-link

Postby BennehBoy » Fri Jan 27, 2017 6:25 pm

Checked the pins against a schematic and it's deffo PA13 SWDIO (pin 22) & PA14 SWCLK (pin 21) so it's not some bizarre pinout change by the manufacturer.
-------------------------------------
https://github.com/BennehBoy

victor_pv
Posts: 1228
Joined: Mon Apr 27, 2015 12:12 pm

Re: Help with st-link

Postby victor_pv » Fri Jan 27, 2017 6:40 pm

Open up the stlink clone and check it out, perhaps the bad solder is there.
The swdio and swdclk pins in the MCU should match the schematics for the stlinks in the nucleo boards, which are widely available. Check continuity on those, gnd, etc.
And it's possibly about time to order another one of those stlinks ;)

User avatar
BennehBoy
Posts: 418
Joined: Thu Jan 05, 2017 8:21 pm
Location: Yorkshire
Contact:

Re: Help with st-link

Postby BennehBoy » Fri Jan 27, 2017 7:05 pm

So there looks to be a solder bridge between the bottom two right hand pins of RP1 in this image... Guess would be it's not supposed to be there?

Image
-------------------------------------
https://github.com/BennehBoy

User avatar
BennehBoy
Posts: 418
Joined: Thu Jan 05, 2017 8:21 pm
Location: Yorkshire
Contact:

Re: Help with st-link

Postby BennehBoy » Fri Jan 27, 2017 7:20 pm

No change with it removed :(
-------------------------------------
https://github.com/BennehBoy

User avatar
BennehBoy
Posts: 418
Joined: Thu Jan 05, 2017 8:21 pm
Location: Yorkshire
Contact:

Re: Help with st-link

Postby BennehBoy » Fri Jan 27, 2017 7:27 pm

Seller contacted, fingers crossed they put another (working!) one in the post.
-------------------------------------
https://github.com/BennehBoy

infrared
Posts: 1
Joined: Mon Jan 30, 2017 8:53 pm

Re: Help with st-link

Postby infrared » Mon Jan 30, 2017 9:12 pm

I'm not sure if this is related, but I recently experienced strange behavior from my st-link v2 interface. I have been using a cheap st-link v2 dongle to program/debug stm32f103c8 blue pill boards, and CubeMX to generate the chip configuration and app framework.

Last night, I upgraded my HAL libraries to STM32Cube_FW_F1_V1.4.0, migrated one of my projects via CubeMX, and Openocd programmed the target one time. Openocd managed to get the new firmware into the target, but immediately lost connection with the target. I was never able to establish connection with that target again.

Today, to see if my st-link dongle was dead, I attempted the same thing with a different target. I experienced exactly the same problem... Firmware was downloaded into the target one time, connection was immediately lost, and I am unable to re-establish connection.

User avatar
ahull
Posts: 1456
Joined: Mon Apr 27, 2015 11:04 pm
Location: Sunny Scotland
Contact:

Re: Help with st-link

Postby ahull » Mon Jan 30, 2017 9:28 pm

I managed to bork a couple of boards by compiling binaries for the wrong processor. This seems to lock things up quite nicely, however connecting the ST-Link v2 under reset has so far always managed to resurrect them.
- Andy Hull -


Return to “Maple mini”

Who is online

Users browsing this forum: No registered users and 1 guest