Skip to content

GitLab

W
wiki

Home

Last edited by Frank Bauernoeppel
Page history

"We are stuck with technology when what we really want is just stuff that works."

Douglas Adams, "The Salmon of Doubt".

All content in this project group is licensed under the terms of the unlicense unless otherwise noted.

I am not affiliated in any way with ST Microelectronics, but I like their STM32 MCUs.

Development Tools

STM32CubeIDE

For first contact with STM32 MCUs, use the vendor's free Eclipse based fully integrated IDE: STM32CubeIDE

Getting started:

  1. Video "How to use STM32CubeIDE" and STM32 youtube channel
  2. Read the docs, especially
  3. MOOC - STM32CubeIDE basics
  4. STM Education

Note that STM32CubeIDE suggests generating a HAL (hardware abstraction layer) or LL (low level) code skeleton from a graphical MCU configuration tool (formerly known as STM32CubeMX). But, you can write the complete code yourself at any level, say register level, as well. The fully integrated IDE conveniently supports code browsing, source and instruction level debugging, inspection of peripheral registers, debugging by tracing etc.. So, give it a try, at least for the first projects to familiarize yourself with the hardware.

GNU arm-none-eabi toolchain with Makefile

These tools are also used by STM32CubeIDE under the hood. It may be worthwhile to study the use of these command line tools (compiler flags, linker scripts, debugger integration, ...) from STM32CubeIDE sample projects. STM32CubeMX can also generate Makefile projects. The toolchain comes already bundled with STM32CubeIDE, check for the plugin folders. You may also install and use them independently. See Makefile Blinky example.

STM Nucleo Boards

Having a known-good reference board is a must for development. There are many low priced STM Nucleo boards available, the examples mostly use the

  1. 32-pin NUCLEO-F042K6
  2. 64-pin NUCLEO-F446RE

All newer boards contain the STLINK/V2.1 debug interface over USB. The debug interface on the larger boards can be used separately for debugging custom hardware. Besides the SWD debug interface, the USB connection integrates

  1. the power supply for the board
  2. a USB VCP (virtual COM port) for board communication
  3. a USB MSC (mass storage class) device (USB drive) for easy flashing (programming) the board by simply copying a .bin file to the USB drive

For each board you have, you should read (at least: browse) the docs

Logic Analyzer

Lab equipment is always helpful. A low-cost USB logic analyzer helps detecting issues and verifying assumptions.

Software Development

Blinky - The embedded "Hello World"

  1. HAL Blinky (STM Hardware Abstraction Layer)
  2. Register-Level Blinky (ARM CMSIS)
  3. Bare-Metal Assembler Blinky
  4. Makefile Blinky using command line tools

Debugging Techniques

The STM AN4989 Application note "STM32 microcontroller debug toolbox" gives a very good and complete overview.

Some topics are covered under Debugging.

Programming the STM32 Peripherals

Finding Examples

HAL Drivers (Firmware) and Example Projects

The firmware contains:

  • Drivers
    • STM32Fxxx_HAL_Driver: the firmware (chip level driver) sources for two abstration levels: HAL and LL
    • CMSIS: ARM vendor-independent hardware abstraction layer, see also below
    • BSP (board support packages): board level hardware abstraction for LEDs, buttons, and more components like MEMS.
  • Projects: per board examples
  • documentation at Documentation/STM32CubeFxGettingStarted.pdf

online:

  1. STM32F0: https://github.com/STMicroelectronics/STM32CubeF0
  2. STM32F4: https://github.com/STMicroelectronics/STM32CubeF4
  3. STM32F7: https://github.com/STMicroelectronics/STM32CubeF7
  4. STM32L4: https://github.com/STMicroelectronics/STM32CubeL4
  5. STM32L5: https://github.com/STMicroelectronics/STM32CubeL5
  6. STM32G0: https://github.com/STMicroelectronics/STM32CubeG0
  7. STM32G4: https://github.com/STMicroelectronics/STM32CubeG4

The firmware packages are also downloaded and managed by the STM32Cube tools. For a default installation, check:

  • Windows: %userprofile%/STM32Cube/Repository
  • Linux: $HOME/STM32Cube/Repository/

CMSIS Drivers

ARM vendor-independent hardware abstraction layer

online: https://github.com/ARM-software/CMSIS_5/releases

Other Libraries and Blogs

How to handle 5V peripherals/interfaces

The STM32 has many 5V tolerant IO pads. See STM Application note AN 4899 "STM32 GPIO configuration for hardware settings and low-power consumption"

STM32 Peripheral Examples

ADC

  1. Timer triggered ADC with DMA output

GPIO

  1. Timer triggered DMA with GPIO output (pattern generator)

Timer

PWM Generation

  1. variable duty cycle PWM by using a DMA buffer

PWM Input Mode

  1. measuring PWM period and duty cycle by timer hardware

USART

  1. using HAL_UART_Receive_IT for parsing NMEA GPS telegrams
  2. advanced UART receiving using DMA and idle interrupt

I2C

  1. I2C slave using HAL_I2C_EnableListen_IT and callbacks

SPI

  1. w25qxx SPI flash Library for STM32 by Nima Askari: https://github.com/nimaltd/w25qxx
  2. STM AN4678 Application note "Full duplex SPI emulation for STM32F4 microcontrollers"
  3. Trigger SPI DMA transfer from Timer https://community.st.com/s/question/0D50X0000C4MPwQSQW/trigger-spi-dma-transfer-from-timer-directly

Ethernet / lwIP

see Piranha's post https://community.st.com/s/question/0D50X0000BOtfhnSQB/how-to-make-ethernet-and-lwip-working-on-stm32

Hardware (Board) Development

Read the STM "Getting started with STM32xx Series hardware development" app notes carefully. Read the schematics and layout of a related STM Nucleo or Discovery Board for reference. Consider letting the following pins be accessible:

  • BOOT mode pin(s)
  • NRST (reset)
  • SWD (serial wire debug) including SWO if present
  • a peripheral interface that is capable to load (program), the flash via the built-in bootloader, see STM AN2606 Application note "STM32 microcontroller system memory boot mode"
  • a serial port for logging?

STM32CubeProgrammer

Getting Help

  1. STM32 MCU Website
  2. ST Community Forum