How ve3wwg/stm32f103c8t6 works
Project type and purpose
• This is an embedded‐firmware “monorepo” of STM32F103 Cortex-M3 examples, drawn from the book “Beginning STM32: Developing with FreeRTOS, libopencm3 and GCC.”
• It provides both bare-metal demos (e.g. miniblink, uart, uarthwfc) and FreeRTOS-based demos (under rtos/) using libopencm3 as HAL and FreeRTOS as RTOS.
• Purpose: give end-to-end build+flash environment and multiple peripheral demos for learning and reference.
File structure
• Top‐level directories:
• libopencm3 (git submodule → hardware‐abstraction layer)
• miniblink, uart, uarthwfc, hse, hsi, mco_pll2, stlink (bare-metal example apps)
• rtos/ (FreeRTOS projects)
• Makefile, Makefile.incl (build orchestrator)
• Under rtos/:
• Project.mk, Makefile.rtos (RTOS project generator + build rules)
• src/ (templates for new projects)
• FreeRTOSv10.x subdirectory (external RTOS source; not compiled in place)
• One folder per demo (blinky, can, i2c-pcf8574, usbcdc, winbond, oled, etc.), each containing:
– main.c (application entry)
– Makefile (application build)
– rtos/ (copied-in FreeRTOS port files)
• Build flow: top‐level Makefile → builds libopencm3 → static libs → builds each example → arm-none-eabi-gcc → .elf/.bin → st‐link flash.
Insights from README
• Emphasizes open-source toolchain (arm-none-eabi-gcc, make, st-link)
• Outlines environment setup (git submodule update, unzip FreeRTOS, setting PREFIX/FREERTOS vars)
• Describes separation between libopencm3‐only projects and FreeRTOS projects.
Capturing essential elements
• Two core libraries (libopencm3, FreeRTOS) and how they integrate with applications.
• Both build and runtime flows to give a complete architectural picture.