Learn

New to STM32? Start here.

Each guide gets one thing working on the STM32H750B-DK and links every step to the exact page of the manual that explains it. Follow the links, not only the code: the real skill is learning where to look.

Beginner≈ 20 min

Start here: the board and its documents

You know what is on the board, which of the seven PDFs answers which question, and how to go from "I want to use X" to the right register.

Start →

Not new to STM32, but new to one peripheral? Open its topic page: what it is, what to read in which order, and the registers to learn first.

I want to…

How the documents fit together

Almost every question goes through these five documents in this order. Every guide follows the same chain, so after a few guides you will do it on your own.

The learning path

  1. Pins: in and out
  2. Blink an LED

    The green user LED LD7 blinks, and you know which document told you each line of the code.

    Beginner≈ 30 min · 6 steps
    2
  3. Read the user button

    Pressing the blue user button B1 toggles the green LED LD7, first by polling the pin and then from an interrupt, and you know why a press must be debounced.

    Beginner≈ 40 min · 6 steps
    3
  4. Talking to things
  5. Print to your PC over the virtual COM port

    Your program sends text with printf, and it appears in a terminal program on your PC, one line per second.

    Beginner≈ 45 min · 7 steps
    4
  6. Pins: in and out
  7. Precise timing and PWM

    An LED on Arduino pin D3 fades in and out smoothly, driven by a timer, and you have a 1 ms tick and a timer interrupt you can trust.

    Intermediate≈ 60 min · 7 steps
    5
  8. Read an analog voltage

    You turn a potentiometer on Arduino pin A0 and see a number from 0 to 65535, and the same value in millivolts, printed on your PC every 200 ms.

    Intermediate≈ 75 min · 7 steps
    6
  9. Under the hood
  10. Clocks: from 64 MHz to 480 MHz

    The CPU runs at 480 MHz from the 25 MHz oscillator through PLL1, with the voltage, flash wait states and bus dividers set in the right order, and you can say where every number came from.

    Intermediate≈ 45 min · 7 steps
    7
  11. Where your code and data live

    You can read the memory map, say which RAM suits which job, explain why a big program has to run from the external Quad-SPI flash, and read a linker script and a cache-coherence problem without panic.

    Intermediate≈ 40 min · 7 steps
    8
  12. Screen and touch
  13. Get started with the display

    The 4.3" screen is lit and shows your own picture: coloured rectangles and a line drawn from your code into a frame buffer, with one rectangle filled by the DMA2D instead of the CPU.

    Advanced≈ 90 min · 7 steps
    9
  14. Read the touch screen (I2C)

    You read the finger position from the touch controller over I2C4 and draw a dot on the screen where you touch it.

    Intermediate≈ 60 min · 6 steps
    10

Bigger parts of the board

No step-by-step guide yet, but here is exactly where to start reading for each one.

Audio: codec, jacks, microphone

A WM8994 codec on SAI2 plays and records through the green/blue jacks and speaker headers. It is configured over the same I2C4 bus as the touch panel. A MEMS microphone uses the PDM input.

USB OTG full-speed (CN13)

The micro-AB connector CN13 can act as USB device or host (e.g. a virtual COM port of your own, a USB stick). LD1 shows VBUS, LD5 overcurrent.

Ethernet (LAN8740 PHY, RJ45)

10/100 Mbit Ethernet through a LAN8740A PHY on the MII interface. Typical stack: LwIP from STM32Cube. Note the solder bridges shared with Quad-SPI.

FDCAN (two CAN ports)

Two FDCAN controllers with transceivers on headers CN10/CN11, for automotive and industrial buses.

eMMC storage (4 GB)

A 4 GB eMMC chip on SDMMC1 for files and big assets. Usually used with the FatFs file system from STM32Cube.

Arduino and STMod+ headers

Expansion headers for shields and modules. Each header pin maps to an MCU pin; check the schematic before using one, since some are shared with on-board parts.

Words you will meet

All 76 terms in the glossary →