Difference between revisions of "STLink"

From PaparazziUAV
Jump to: navigation, search
m (spelling)
 
(34 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{| align=right
+
<div style="float: right; width: 20%">
 +
<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Firmware Flashing</categorytree>
 +
</div>
 +
 
 +
<div style="float: right; width: 60%">
 +
[[Image:St-link.jpg|right|450px]]
 +
</div>
 +
__TOC__
 +
 
 +
 
 +
Every STM discovery / eval board comes with a [http://www.st.com/web/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 ST-Link V2] on board, with one exception; the STM32VL version comes with a ST-Link V1.
 +
 
 +
==SWD Header==
 +
 
 +
[[Image:swd_header_discovery_board.png|250px|Pinout with Apogee connector]]
 +
 
 +
==Install Software==
 +
 
 +
The ''st-flash'' and ''st-util'' tools are needed, provided by [https://github.com/texane/stlink texane]
 +
 
 +
Download and compile
 +
$ cd /opt
 +
$ git clone git://github.com/texane/stlink.git stlink
 +
$ cd stlink
 +
$ ./autogen.sh
 +
$ ./configure
 +
$ make
 +
 
 +
Set environment variable
 +
$ exportline="PATH=$PATH:/opt/stlink"
 +
$ if grep -Fxq "$exportline" ~/.profile; then echo nothing to do ; else echo $exportline >> ~/.profile; fi
 +
$ source ~/.profile
 +
 
 +
Add udev rules
 +
$ sudo cp /opt/stlink/49-stlinkv*.rules /etc/udev/rules.d
 +
$ sudo udevadm control --reload-rules
 +
 
 +
ST-LinkV1 requires a bit different treatment, read the [https://github.com/texane/stlink/blob/master/README Readme.txt]
 +
 
 +
==Airframe.xml setup==
 +
 
 +
Connect the ST-Link to the MCU.
 +
If a complete STM32Fx-Discovery board is used, CN3 jumpers need to be set. To program a external MCU, remove CN3 jumpers and connect the external MCU with the SWD header.
 +
 
 +
To use SWD via STLink as default:<br/>
 +
Set '''FLASH_MODE=STLINK'''<br/>
 +
 
 +
==Update the ST-Link to blackmagic probe==
 +
 
 +
The STM32F103 (STLink MCU) can be flashed with the blackmagic's firmware.<br/>
 +
 
 +
===Two STLinkV2 Method===
 +
 
 +
Use one STLink to flash another
 +
 
 +
Hardware Setup:
 +
One STLinkV2 (connected via USB) is programming the other one. Change the 4 Solder jumpers on the bottom of the target STLinkV2 from "DEFAULT" to "REVERSED".<br/>
 +
 
 +
Connections between the two STLinks
 +
{|border="1"  cellspacing="0" style="text-align:center" cellpadding="6"
 +
|+'''Connections [Header-Pin]'''
 +
!''Use''!!''From Programmer''!!''To Target''
 +
|-
 +
|5V||P2-5V||P2-5V
 +
|-
 +
|SWDIO||CN2-4||CN3-2
 +
|-
 +
|SWDCLK||CN2-2||CN3-3
 
|-
 
|-
|<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Firmware Flashing</categorytree>
+
|GND||CN2-3||CN3-4
 
|}
 
|}
  
__TOC__
+
Download and build the Firmware
 +
git clone https://github.com/blacksphere/blackmagic
 +
cd blackmagic
 +
git submodule init
 +
git submodule update
 +
make
 +
cd src
 +
make clean
 +
make PROBE_HOST=stlink
 +
 
 +
Remove the readout protection, erase and flash
 +
openocd -f interface/stlink-v2.cfg -f target/stm32f1x_stlink.cfg -c "init" -c "halt" -c "stm32f1x unlock 0" -c "shutdown"
 +
st-flash erase
 +
st-flash --reset write blackmagic.bin 0x8002000
 +
st-flash write blackmagic_dfu.bin 0x8000000
 +
 
 +
====Documentation====
 +
 
 +
[http://esden.net/2014/12/29/black-magic-discovery Black Magic Discovery from Esden] <-- This also describes how to remove the read out protection. <br/>
 +
[http://embdev.net/articles/STM_Discovery_as_Black_Magic_Probe embdev.net page]
 +
 
 +
===BMP Method===
 +
 
 +
Use a BMP to flash a STLink
 +
 
 +
Transfer the solder jumpers from "Default" to "Reversed" and build the firmware as described above.<br/>
 +
Connect the BMP to the CN2 header (see Pinout above).
 +
 
 +
Start gdb, erase the option bytes and flash BMP
 +
(gdb) target extended-remote /dev/ttyACM0
 +
(gdb) mon swdp_scan
 +
(gdb) att 1
 +
(gdb) mon option erase
 +
(gdb) load /dir/to/blackmagic
 +
(gdb) load /dir/to/blackmagic_dfu
 +
(gdb) detach
 +
 
 +
The option bytes do not cover the Readout Protection (RDP), but the RDP is disabled anyhow...
 +
 
 +
'''Error at loading a new image after removing RDP'''
 +
 
 +
Error erasing flash with vFlashErase packet
 +
If this occurs powercycle the target (disconnect and reconnect the 3V3 connection), swd scan, attach and try loading the image again. Usually the reset of the RDP requires a flash erase (done by mon option erase) and reset.
 +
 
 +
Probably this can also be done via gdb.
 +
 
 +
==Clones==
 +
 
 +
There are also a lot of different Chinese clones out there. Most with an identical MCU as the original STLinkV2, some with an STM32F101.
 +
 
 +
It seems that each clone has its own programming pinout, so better double check (continuity tester) than to release the magic smoke...
 +
 
 +
Most (all?) should work with the "stlink" target from Blackmagic Probe, since they probably use the same firmware from the original STLinkV2.
 +
 
 +
===Red PCB===
 +
 
 +
Seems to work with the standard stlink BMP image.
 +
 
 +
[[Image:stlinkv2_clone_red_front.jpg|250px]]
 +
[[Image:stlinkv2_clone_red_back.jpg|250px]]
 +
 
 +
* STM32F103C8T6
  
[[Image:St-link.jpg|right|300px|ST-LinkV2 (stm32f4-Discovery)]]
+
Programming header (1.27mm, populated on the images) from the Mini USB to the Pin header (right to left on the image), used for programming the onboard MCU.
[http://www.arm.com/products/system-ip/debug-trace/coresight-soc-components/serial-wire-debug.php SWD] can be used to upload the firmware to stm32fx MCU.  
 
  
A ST-Link is needed, any stm32-discovery board has a ST-LinkV2 on it (starts @ 8€). stm32vl discovery has a ST-LinkV1.
+
# SWDIO
 +
# GND
 +
# SWDCLK
 +
# 3V3
  
A standard ST-Link costs from 17€
+
Some Images and details about this hardware can be found at[https://www.mikrocontroller.net/articles/IRMP_auf_STM32_-_Bauanleitung]
  
==Needed Tools==
+
===Blue PCB===
st-flash and st-util are needed [https://github.com/texane/stlink Tools from texane]
+
NOT TESTED YET
 +
[[Image:stlinkv2_clone_blue_front.jpg|250px]]
 +
[[Image:stlinkv2_clone_blue_back.jpg|250px]]
  
download and compile
+
* STM32F103C8T6
git clone git://github.com/texane/stlink.git stlink
 
cd stlink
 
./autogen.sh
 
./configure
 
make
 
  
copy in the suitable directory
+
Programming header (2.54mm, unpopulated on the images) from the USB to the Pin header (left to the right on the images), used for programming the onboard MCU.
sudo cp st-flash /usr/bin
 
sudo cp st-util /usr/bin
 
  
add udev rules (replace user with your username)
+
# GND
sudo cp /home/user/stlink/49-stlinkv*.rules /etc/udev/rules.d
+
# 5V
sudo udevadm control --reload-rules
+
# USART1 RX (PA10)
 +
# USART1 TX (PA9)
  
 +
Bootloader header (2.54mm, unpopulated on the images), from the USB to the Pin header (left to the right on the images), used for USART bootloader activation
  
For ST-LinkV1 take a look at the readme.txt !
+
# 3V3
 +
# BOOT0 (pin 44)
  
==Test it==
+
The 3V3/5V switch selects the input voltage for the onboard MCU.
To copy the file from the MCU
 
st-flash read ~/STM32F4-Discovery.bin 0x8000000 0x100000
 
LED LD1 will flash alternatly green and red.
 
  
Output
+
===Aluminium housing===
INFO src/stlink-usb.c: -- exit_dfu_mode
+
NOT TESTED YET
INFO src/stlink-common.c: Loading device parameters....
+
[[Image:stlinkv2_clone_aluminium.jpg|250px]]
src/stlink-common.c: Device connected is: F4 device, id 0x10016413
+
[[Image:stlinkv2_clone_aluminium_front.jpg|250px]]
INFO src/stlink-common.c: SRAM size: 0x30000 bytes (192 KiB), Flash: 0x100000 bytes (1024 KiB) in pages of 16384 bytes
+
[[Image:stlinkv2_clone_aluminium_back.jpg|250px]]
  
 +
* STM32F101C8T6
  
stm32f4-discovery shoud be found at /dev/stlinkv2_2
+
Programming header (1.27mm, unpopulated on the images) from the USB to the Pin header (left to the right on the images), used for programming the onboard MCU.
'''how can that be tested ? please fix me :)'''
 
  
usb device
+
# SWDIO (PA13)
lsusb
+
# GND
Bus 002 Device 007: ID 0483:3748 SGS Thomson Microelectronics ST-LINK/V2
+
# SWDCLK(PA14)
 +
# VDD, VBAT
  
==Howto==
+
To disassemble pull the aluminium housing towards the USB connector.
  
Connect the ST-Link to the MCU.
+
This has not the same hardware as https://github.com/blacksphere/blackmagic/issues/62 , but the same MCU, seems that this has just an other PCB.
If a complete stm32fx-discovery board is used, CN3 jumpers need to be set. To program a external MCU, remove CN3 jumpers and connect the external MCU with the SWD header.
 
  
To use SWD
+
[[Category:Firmware Flashing]] [[Category:Developer_Documentation]]
:<source lang="xml"><configure name="FLASH_MODE" value="SWD"/></source>
 
To use stlink (requires line above)
 
:<source lang="xml"><configure name="STLINK" value="y"/></source>
 
[[Category:Firmware Flashing]]
 

Latest revision as of 06:14, 8 June 2016

St-link.jpg


Every STM discovery / eval board comes with a ST-Link V2 on board, with one exception; the STM32VL version comes with a ST-Link V1.

SWD Header

Pinout with Apogee connector

Install Software

The st-flash and st-util tools are needed, provided by texane

Download and compile

$ cd /opt
$ git clone git://github.com/texane/stlink.git stlink
$ cd stlink
$ ./autogen.sh
$ ./configure
$ make

Set environment variable

$ exportline="PATH=$PATH:/opt/stlink"
$ if grep -Fxq "$exportline" ~/.profile; then echo nothing to do ; else echo $exportline >> ~/.profile; fi
$ source ~/.profile

Add udev rules

$ sudo cp /opt/stlink/49-stlinkv*.rules /etc/udev/rules.d
$ sudo udevadm control --reload-rules

ST-LinkV1 requires a bit different treatment, read the Readme.txt

Airframe.xml setup

Connect the ST-Link to the MCU. If a complete STM32Fx-Discovery board is used, CN3 jumpers need to be set. To program a external MCU, remove CN3 jumpers and connect the external MCU with the SWD header.

To use SWD via STLink as default:
Set FLASH_MODE=STLINK

Update the ST-Link to blackmagic probe

The STM32F103 (STLink MCU) can be flashed with the blackmagic's firmware.

Two STLinkV2 Method

Use one STLink to flash another

Hardware Setup: One STLinkV2 (connected via USB) is programming the other one. Change the 4 Solder jumpers on the bottom of the target STLinkV2 from "DEFAULT" to "REVERSED".

Connections between the two STLinks

Connections [Header-Pin]
Use From Programmer To Target
5V P2-5V P2-5V
SWDIO CN2-4 CN3-2
SWDCLK CN2-2 CN3-3
GND CN2-3 CN3-4

Download and build the Firmware

git clone https://github.com/blacksphere/blackmagic
cd blackmagic
git submodule init
git submodule update
make
cd src
make clean
make PROBE_HOST=stlink

Remove the readout protection, erase and flash

openocd -f interface/stlink-v2.cfg -f target/stm32f1x_stlink.cfg -c "init" -c "halt" -c "stm32f1x unlock 0" -c "shutdown"
st-flash erase
st-flash --reset write blackmagic.bin 0x8002000
st-flash write blackmagic_dfu.bin 0x8000000

Documentation

Black Magic Discovery from Esden <-- This also describes how to remove the read out protection.
embdev.net page

BMP Method

Use a BMP to flash a STLink

Transfer the solder jumpers from "Default" to "Reversed" and build the firmware as described above.
Connect the BMP to the CN2 header (see Pinout above).

Start gdb, erase the option bytes and flash BMP

(gdb) target extended-remote /dev/ttyACM0
(gdb) mon swdp_scan
(gdb) att 1 
(gdb) mon option erase
(gdb) load /dir/to/blackmagic
(gdb) load /dir/to/blackmagic_dfu
(gdb) detach

The option bytes do not cover the Readout Protection (RDP), but the RDP is disabled anyhow...

Error at loading a new image after removing RDP

Error erasing flash with vFlashErase packet

If this occurs powercycle the target (disconnect and reconnect the 3V3 connection), swd scan, attach and try loading the image again. Usually the reset of the RDP requires a flash erase (done by mon option erase) and reset.

Probably this can also be done via gdb.

Clones

There are also a lot of different Chinese clones out there. Most with an identical MCU as the original STLinkV2, some with an STM32F101.

It seems that each clone has its own programming pinout, so better double check (continuity tester) than to release the magic smoke...

Most (all?) should work with the "stlink" target from Blackmagic Probe, since they probably use the same firmware from the original STLinkV2.

Red PCB

Seems to work with the standard stlink BMP image.

Stlinkv2 clone red front.jpg Stlinkv2 clone red back.jpg

  • STM32F103C8T6

Programming header (1.27mm, populated on the images) from the Mini USB to the Pin header (right to left on the image), used for programming the onboard MCU.

  1. SWDIO
  2. GND
  3. SWDCLK
  4. 3V3

Some Images and details about this hardware can be found at[1]

Blue PCB

NOT TESTED YET Stlinkv2 clone blue front.jpg Stlinkv2 clone blue back.jpg

  • STM32F103C8T6

Programming header (2.54mm, unpopulated on the images) from the USB to the Pin header (left to the right on the images), used for programming the onboard MCU.

  1. GND
  2. 5V
  3. USART1 RX (PA10)
  4. USART1 TX (PA9)

Bootloader header (2.54mm, unpopulated on the images), from the USB to the Pin header (left to the right on the images), used for USART bootloader activation

  1. 3V3
  2. BOOT0 (pin 44)

The 3V3/5V switch selects the input voltage for the onboard MCU.

Aluminium housing

NOT TESTED YET Stlinkv2 clone aluminium.jpg Stlinkv2 clone aluminium front.jpg Stlinkv2 clone aluminium back.jpg

  • STM32F101C8T6

Programming header (1.27mm, unpopulated on the images) from the USB to the Pin header (left to the right on the images), used for programming the onboard MCU.

  1. SWDIO (PA13)
  2. GND
  3. SWDCLK(PA14)
  4. VDD, VBAT

To disassemble pull the aluminium housing towards the USB connector.

This has not the same hardware as https://github.com/blacksphere/blackmagic/issues/62 , but the same MCU, seems that this has just an other PCB.