stm32-development-workflow

Build and flash STM32 firmware via command-line workflows.

24|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/EricSun787/stm32-development-workflow --skill stm32-development-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stm32-development-workflow
Source: https://github.com/EricSun787/stm32-development-workflow/tree/main
Command: npx skills add https://github.com/EricSun787/stm32-development-workflow --skill stm32-development-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many embedded developers need a reliable, IDE-free way to build, configure, and flash STM32 firmware from the command line; this Skill consolidates toolchain setup, HAL configuration, build automation, and ST-Link flashing procedures into guided steps and templates.

Core Features & Use Cases

  • Toolchain & Environment Setup: step-by-step guidance for installing STM32CubeCLT, arm-none-eabi GCC, and STM32CubeProgrammer/ST-Link drivers.
  • Build Automation & Scripts: ready-to-use build.sh template, recommended compiler and linker flags, and guidance on organizing HAL and CMSIS sources.
  • Flashing & Troubleshooting: CLI examples for STM32_Programmer_CLI and ST-Link, ST-Link firmware upgrade steps, and common compilation/linker error resolutions.
  • Use Case: Initialize an STM32F4 project, configure hal_conf.h, compile with the GCC toolchain, and flash the firmware over SWD without using an IDE.

Quick Start

Create a new STM32 project, configure hal_conf.h for your MCU, run the included build.sh template to produce the firmware, and flash the resulting binary using STM32_Programmer_CLI with SWD and verification enabled.

Frequently Asked Questions about stm32-development-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and flash STM32 firmware from the command line without an IDE?

To build and flash STM32 firmware from the command line, use arm-none-eabi GCC for compilation and STM32_Programmer_CLI for ST-Link SWD flashing. The workflow covers HAL configuration, linker scripts, build automation, and verification without requiring an IDE.

What do I need to configure in hal_conf.h when starting an STM32CubeCLT project?

Configuring hal_conf.h in an STM32CubeCLT project requires selecting the specific HAL modules for your target MCU. This ensures the firmware only includes required peripheral drivers, optimizing the compilation for STM32F1, STM32F4, or STM32H7 series.

Can I use arm-none-eabi GCC compiler flags for STM32F1, STM32F4, and STM32H7 series?

Yes, arm-none-eabi GCC compiler flags support STM32F1, STM32F4, and STM32H7 series builds. The workflow provides recommended compiler and linker flags tailored for these MCU architectures to ensure proper firmware compilation and memory mapping.

Why does STM32_Programmer_CLI fail to flash firmware over ST-Link SWD?

STM32_Programmer_CLI flashing failures over ST-Link SWD often stem from outdated ST-Link firmware or driver issues. The workflow includes ST-Link firmware upgrade steps and CLI troubleshooting examples to resolve common flashing and connection errors.

What is the best way to automate STM32 builds with GCC and linker scripts?

The best way to automate STM32 builds is using a build.sh template that integrates arm-none-eabi GCC options and linker scripts. This automates compilation of HAL and CMSIS sources, producing a binary ready for ST-Link SWD flashing.