Repository files navigation

This guide was written for (and on) Linux Arch, Ubuntu, Mint. I have not tested the procedure on other Linux architectures or distros, Users of other distros may find that some of the instructions don't work verbatim. Adapt as needed.

STM8 Series of micro-controllers by ST Microelectronics are dirt cheap and powerful at the same time. Their processing power is nothing short as of Arduino, while at the same time their power consumption is much less. These properties makes STM8 micros a great choice for many hobby and serious projects. This tutorial you will learn how to setup a developing and programming environment for STM8 on Linux based systems.

Here are the required tools that I used in this tutorial:

• VS-Code ( Visual Studio Code ) advanced text editor.
• SDCC Compiler v3.7.0 or higher.
• STM8 Standard Peripherals Library [SPL], patched for SDCC.
• ST-LINK / STM8FLASH to write your compiled code into the micro-controller.
• STM8-GDB / OPENOCD for debugging.
• ST’s STM8 Evaluation board or you can get away with el-cheapo chinese boards which are going for around 2$ including shipping!.

Visual Studio Code is a cross-platform, free and open-source (licensed under the MIT License) text editor developed by Microsoft and is extensible using extensions, which can be browsed from within the text editor itself (via its extension gallery) or from https://marketplace.visualstudio.com/VSCode. While open-source, a proprietary build (licensed under an End-User License Agreement) provided by Microsoft is available and used as the basis for the visual-studio-code-bin [AUR] package (for an explanation of the mixed licensing, see this GitHub comment).

Installation

# Arch linux$ yaourt -S visual-studio-code-bin# Ubuntu and Mint linux$ wget https://go.microsoft.com/fwlink/?LinkID=760868 -O vscode.deb$ sudo dpkg -i vscode.deb

Usege

$ code

Add extention

press ( Ctrl + Shift + X ) then search and install the folowing extention:

• C/C++ for Visual Studio Code
• C++ Intellisense
• hexdump for VSCode
• vscode-devdocs

SDCC is a retargettable, optimizing Standard C (ANSI C89, ISO C99, ISO C11) compiler suite that targets the STMicroelectronics STM8.
Download and install SDCC v3.7.0 or higher. Snapshot Builds for more optimisation fromSourceForge

## download the latest version$ wget https://sourceforge.net/projects/sdcc/files/snapshot_builds/amd64-unknown-linux2.5/sdcc-snapshot-amd64-unknown-linux2.5-20210621-12488.tar.bz2$ tar -xjf ./sdcc-snapshot-amd64-unknown-linux2.5-20210621-12488.tar.bz2$ sudo mv sdcc /opt$echo"export PATH=\$PATH:/opt/sdcc/bin">>~/.bashrc$source~/.bashrc## to check if sdcc is correctly installed$ sdcc -vSDCC: mcs51/z80/z180/r2k/r2ka/r3ka/gbz80/tlcs90/ez80_z80/z80n/ds390/pic16/pic14/TININative/ds400/hc08/s08/stm8/pdk13/pdk14/pdk15 4.1.6#12488 (Linux)published under GNU General Public License (GPL)

SDCC SourceForgeDocumentation SDCC ManualPDF

SDCC supports STM8, but for licensing reasons (booo, ST!), theStandard Peripheral Library (SPL) is missing.

Someone developed a patch that makes the SPL compatible with SDCC, available here:SPL_2.2.0_SDCC_patch.

ST-Link programmer or clone used to write your compiled code ( Firmware ) into the micro-controller.For the programmer, you need one that support SWIM (Single Wire Interface Module) mode. You can (recommended) go with the original debugger of STMicroelectronics which is ST-Link V2 (you can get this one second hand as low as 20$) or if you are really want to go economical, you can get away with the fake ones wich cost you under 10$ (please note that these cheap debuggers only support software mode, which works fine, and do not give you full functionality and speed of the genuine debuggers of ST itself). or you can build your own Open source Stlink Tools.

ST-LINK/V2-1 firmware upgradeSTSW-LINK007.

Open source version of the STMicroelectronics Stlink Toolshere

Black Magic Probe, Open Source JTAG & SWD GNU Debugger and Programmerhere .

it was the only program that's able to communicate through the SWIM interface of ST-LINKs to upload compiled code ( Firmware ) into the micro-controller.

libusb-1.0-0-dev is required to compile stm8flash

Installstm8flash from [AUR] package

## Arch linux$ yaourt -S aur/stm8flash-git## Ubuntu, Mint Linux## Install from src git repo$ git clone https://github.com/vdudouyt/stm8flash.git$cd stm8flash$ make$ sudo make install

GitHub opensource software distributed onvdudouyt/stm8flash

To solve USB device acquring write access problem

libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/003/004: Permission deniedlibusb: error [_get_usbfs_fd] libusb requires write access to USB device nodes.Could not open USB device.

create files with content:

# stm32 discovery boards, with onboard st/linkv1# ie, STM32VL.SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3744", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv1_%n"

# stm32 discovery boards, with onboard st/linkv2# ie, STM32L, STM32F4.SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3748", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv2_%n"

# stm32 nucleo boards, with onboard st/linkv2-1# ie, STM32F0, STM32F4.SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374b", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv2-1_%n"SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3752", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv2-1_%n"

# stlink-v3 boards (standalone and embedded) in usbloader mode and standard (debug) modeSUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374d", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv3loader_%n"SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374e", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv3_%n"SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374f", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv3_%n"SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3753", \    MODE="660", GROUP="plugdev", TAG+="uaccess", \    SYMLINK+="stlinkv3_%n"

Create49-stlinkv1.rules,49-stlinkv2.rules,49-stlinkv2-1.rules,49-stlinkv3.rules and copy it in/etc/udev/rules.d/, Then reloadudevadm

$ sudo mv*.rules /etc/udev/rules.d/$ sudo udevadm control --reload-rules&& sudo udevadm trigger

Note that a file is provided for ST-Link/V1 (idProduct=3744) despite most toolsets do not support it.

The STM8S-DISCOVERY helps you to discover the STM8S features and to develop and share your own application. In my case i use STM8S003F3P6 STM8S Minimum System Development Board Module. It's about $1-$5 fromAliExpress

Usually the first step toward learning development on a micro-controller is  simply blinking a LED, as an analog to “Hello, world!” example used on PC programming languages. This time we will have a look into how to start programming and development on STMicroelectronics STM8 series of micro-controllers.

At this point you should have a working dev environment and can start experimenting with the board.

STM8S Reference Manual

#include"stm8l.h"#defineLed_Init GPIO_Init(GPIOD, GPIO_PIN_1, GPIO_MODE_OUT_PP_LOW_FAST)#defineLed_ON   GPIO_WriteHigh    (GPIOD,GPIO_PIN_1)#defineLed_OFF  GPIO_WriteLow     (GPIOD,GPIO_PIN_1)#defineLed_TOG  GPIO_WriteReverse (GPIOD,GPIO_PIN_1)voidmain(void) {// Init LED Port, PinLed_Init;// Set LED ONLed_ON;// Loopwhile(1){// Toggle LED ON/OFFLed_TOG;// White momentfor(uint16_td=0;d<19000;d++){for(uint8_tc=0;c<5;c++);      }   }}

$ sdcc -lstm8 -mstm8 --opt-code-size --std-sdcc99 --nogcse --all-callee-saves --debug --verbose --stack-auto --fverbose-asm --float-reent --no-peep -I./ -I./STM8S_StdPeriph_Driver/inc -D STM8S003 ./stm8_blinky.c

Out of the factory, each board is flashed with a blinking demo, so you should see it start blinking as soon as you connect the USB. We won't be using the USB though, so unplugit again and prepare your ST-Link and the connection cable that came with it.

You'll also need to solder some headers to your STM8 board, at the very least the programming header (opposite of the USB). Both the dongle pins and the programming header are clearly labeled, so you shouldn't have any issues.

If you use clone st-link programmer, don't connect the 3V3 line from the dongle to the boardwhile powering the board from USB. Technically nothing bad should happen, but you're connecting two LDOs in parallel and that's just a bad idea.

Simply leave the 3V3 pin of the programming header unconnected in this case.

The board should start blinking immediately. The first step though will be to wipe the chip, since the factory-loaded firmware is read-protected and you can't do anything while it's locked down.

To unlock the chip, use the-u flasher option (for more info, runstm8flash -h):

$ stm8flash -c stlinkv2 -p stm8s003f3 -uDetermine OPT areaUnlocked device. Option bytes reset to default state.Bytes written: 11

The board will stop flashing, you just bricked it. Oh no! But we'll fix that promptly.

You can now upload your own firmware using make flash, or if you downloaded the HEX file manually:

$ stm8flash -c stlinkv2 -p stm8s003f3 -s flash -w stm8_blinky.ihxDetermine FLASH areaWriting Intel hex file 655 bytes at 0x8000... OKBytes written: 655

GDB offers extensive facilities for tracing and altering the execution of programs. The user can monitor and modify the values of programs' internal variables, and even call functions independently of the program's normal behavior.

Installopenocd fromgithub.com/sysprogs/openocd for latest update to useSTM8 devices

$ git clone git@github.com:sysprogs/openocd.gitor$ git clone git@github.com:ntfreak/openocd.git$cd openocd$ ./bootstrap$ ./configure$ make$ sudo make install

SourceForgeOpenOCD.

Download the latest stm8 binutils-gsb sources fromOfficial site or direct fromSourceForge.

Building the binaries is basically the process of downloading the sources and applying the patches. There are helper scripts to assist with the process.

$ wget https://sourceforge.net/projects/stm8-binutils-gdb/files/stm8-binutils-gdb-sources-2020-03-22.tar.gz/download -O stm8-binutils-gdb-sources-2018-03-04.tar.gz$ tar -xf stm8-binutils-gdb-sources-2020-03-22.tar.gz$cd stm8-binutils-gdb-sources$ ./patch_binutils.sh$ ./configure_binutils.sh

Also note you need some libraries for TUI mode to work. Among those are ncursesw.

Next step is the regular building and install:

$cd binutils-2.30$ make$ sudo make install

SourceForgestm8-binutils-gdb.

Compiling and generateelf file with--out-fmt-elf arg

$ sdcc -mstm8 led.c --out-fmt-elf --all-callee-saves --debug --verbose --stack-auto --fverbose-asm  --float-reent --no-peep

launch openocd in a second shell:

$ openocd -f interface/stlink.cfg -f target/stm8s105.cfg -c"init" -c"reset halt"

or if you prefer the generic stm8s configuration (for medium size flash stm8s) replacestm8s105.cfg bystm8s.cfg

Currently config files for stm8s003, stm8s105 and stm8l152 are available.

Then start gdb:

$ stm8-gdb test.elf --tuistart

or if you prefer to load manually:

$ stm8-gdb test.elf --tuitarget extended-remote localhost:3333loadbreak maincontinue

Goto [Debug > Add Confeguration ...]

{"name":"STM8-gdb","type":"cppdbg","request":"launch","program":"${workspaceRoot}/build/main.elf","args": [],"stopAtEntry":true,"cwd":"${workspaceRoot}","environment": [],"externalConsole":false,"MIMode":"gdb","miDebuggerPath":"stm8-gdb","setupCommands": [        {"description":"connect to target","text":"-target-select extended-remote localhost:3333","ignoreFailures":true        },    ],"logging": {"moduleLoad":true,"trace":true,"engineLogging":true,"programOutput":true,"exceptions":true    },}

Then [Debug > Start Debugging] or pressF5