Getting started with Zephyr RTOS on BluePill board

Project Initialization

Create a new project using PlatformIO with the following settings:

• Board: BluePill F103C8 (Generic)
• Framework: Zephyr RTOS

Upload

Using ST-LINK

There are several ways to upload the firmware to this board but the default way is to use the ST-Link debugger.

In linux, you can use the following commands to install the ST-Link drivers:

sudo apt -y install stlink-tools
sudo systemctl restart udev

Modify platformio.ini file to set stlink as default upload method:

upload_protocol = stlink

Now you can Upload the firmware to the board using PlaformIO.

You can also use st-flash tool for programming using ST-Link in linux:

st-flash write firmware.bin 0x8000000

Using UART and Embedded Bootloader

All the STM32 microcontrollers come with built-in bootloaders that burned in during production.

A couple of special MCU pins has to be set-up to proper logical values to enter the bootloader. The pins are named BOOT0 and BOOT1 on the STM32 microcontroller. Boot pins can select several modes of bootloader operation:

As you can see, there are three cases:

• The first case is when the BOOT0 pin is tied to the ground, and BOOT1 is open or at a logical state of 0 after the reset program is executed from Main Flash Memory. Grounded BOOT pins are a standard configuration when executing programs in the field.
• The second case (BOOT1=0; BOOT0=1) means that after reset execution starts at System memory were built into bootloader resides. This is the case when we need to upload binaries via USART1.
• The third case means that program execution is performed in SRAM.

Read this article to understand how you can use UART1 for programming this board:

Supported Features in Zephyr

The stm32_min_dev board configuration supports the following hardware features:

Other hardware features are not supported by the Zephyr kernel.

Connections and IOs

Default Zephyr Peripheral Mapping:

• UART_1 TX/RX: PA9/PA10
• UART_2 TX/RX: PA2/PA3
• UART_3 TX/RX: PB10/PB11
• I2C_1 SCL/SDA : PB6/PB7
• I2C_2 SCL/SDA : PB10/PB11
• PWM_1_CH1: PA8
• SPI_1 NSS_OE/SCK/MISO/MOSI: PA4/PA5/PA6/PA7
• SPI_2 NSS_OE/SCK/MISO/MOSI: PB12/PB13/PB14/PB15
• USB_DC DM/DP: PA11/PA12
• ADC_1: PA0

System Clock

The on-board 8Mhz crystal is used to produce a 72Mhz system clock with PLL.

Serial Port

STM32 Minimum Development Board has 3 U(S)ARTs. The Zephyr console output is assigned to UART_1. Default settings are 115200 8N1.

On-Board LEDs

The board has one on-board LED that is connected to PC13.

Pinout

Schematics

USB to Serial Cable

USB to Serial (UART) cable is used to connect the board to a PC.

Access to Serial Port in Linux

In order to upload the compiled program to your board you should have access to serial ports. This is done by adding your user to dialout and tty groups:

sudo usermod -a -G dialout $USER
sudo usermod -a -G tty $USER

You can verify if your user is added to dialout and tty groups using this command:

groups $USER

Note: You should log out and log in or reboot your computer to apply the changes.

Resources

• Blue Pill - STM32F103C8T6
• Getting Started with STM32F103C8T6 Blue Pill
• PlatformIO BluePill F103CB
• Connecting ST-LINK debugger
• How to fix PlatformIO STM32 Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
• Zephyr for BluePill Documentation
• Zephyr Blinky Sample Application
• Zephyr Tutorial for Beginners
• IoT RTOS Zephyr on cheap STM32 Minimum Development Board
• Bootloader for STM32F103 boards, to use with the Arduino_STM32 repo and the Arduino IDE
• DFU Bootloader for STM32 chips
• AN2606 Application note: STM32 microcontroller system memory boot mode
• Accessing Devices without Sudo
• Programming STM32F103 Blue Pill using USB Bootloader and PlatformIO