Skip to content

Latest commit

 

History

History
125 lines (97 loc) · 4.87 KB

Programming.md

File metadata and controls

125 lines (97 loc) · 4.87 KB
Raw

Programmer

Get a cheap ST-Link clones (around $4), refer to the schematics for the SWD pinout.
There's no support for custom bootloaders.

Connection

Usually the board will have a connector with pins named "G V C D" (GND, VDD, SWCLK, SWDIO).
If not named, just use a multimeter and check which pins goes where.
Then connection is as follows.
Connect VDD only if not being powered by station power supply!

Clone detection

A lot of sellers started using relabeled STM32 clones, making detection hard.
Thankfully, most can be easily detected by checking their CPU ID (DBGMCU_ID) code by folowing the procedure:

  • Connect the ST-Link,
  • Write 0xE0042000 in "Address" field,
  • Write 0x8 in "Size" field,
  • Click "Connect to target" button.

A genuine STM32F101/102/103Cx/Rx should have any of these codes:

00006410
20006410
20016410
20036410


Another test is to read the Flash Size register:
  • Write 0x1FFFF7E0 in "Address" field,
  • Write 0x4 in "Size" field,
  • Click "Connect to target" button.

A genuine STM32F101/102/103Cx/Rx should have any of these values:

FFFF0040 (64KB)
FFFF0080 (128KB)
FFFF0100 (256KB)
FFFF0200 (512KB)

If you get FFFFFFFF or a strange value, then it's 100% fake. First 4 digits must be FFFF!

Programming with STM32 ST-LINK Utility

Download the binary for your station from Releases, and flash it using ST-Link.

Coming from original firmware

Usually the STM32 comes read-protected. Follow this workflow to program it.
(Click for bigger picture)

Upgrading

Just open and program the new binary.
Because this firmware stores the settings in the flash, don't make a full chip erase!

In any case, the firmware will check the settings and reset them if not valid.

STM32 not recognized error

Some STM32 have their debug port disabled, in this case the only way to access is connecting nRST pin to the ST-Link.
There're several ST-Link clones with a flaw in nRST pin, which is wired wrong by design, and won't able to connect.
Temporaly short nRST (STM32 pin 7) to GND, click "Connect to target" button, wait 1-2 seconds and release the nRST short. Now it should recognice it.
Usually on the controller board nRST pin is connected to a capacitor, only requiring to short the capacitor as showed in this picture:

Temporary short nRST pin (STM32 pin 7) to GND

Programming with OpenOCD

  1. Download the binary for your station from Releases and rename it to fw.bin
  2. Install OpenOCD
    If running Ubuntu/Debian install with $ sudo apt install openocd
  3. Create a file with the following content or download it 
    source [find interface/stlink.cfg]
source [find target/stm32f1x.cfg]

# Set RDP to level 0

init
reset halt
stm32f1x unlock 0
reset halt

#Program
program fw.bin 0x08000000
exit
  4. Connect the ST-Link programmer
  5. From the console run $ openocd -f ocd-program.cfg. Here is a sample output: 
    Open On-Chip Debugger 0.11.0-rc2
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
Info : clock speed 1000 kHz
Info : STLINK V2J37S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.232297
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for stm32f1x.cpu on 3333
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x080033f0 msp: 0x20002800
Info : device id = 0x20036410
Warn : STM32 flash size failed, probe inaccurate - assuming 128k flash
Info : flash size = 128kbytes
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x080033f0 msp: 0x20002800
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x080033f0 msp: 0x20002800
** Programming Started **
** Programming Finished **
** Verify Started **
** Verified OK **