STM32CubeProgrammer ported to Arm Linux: unlocks automated flashing
Engineering and validation teams building automated test infrastructure have a simple challenge. Automated flashing has traditionally meant relying on a general-purpose x86 PC to run the programming tool.
But for a dedicated process that needs to run the same way thousands of times, a more purpose-built approach can make a difference.
This is where our ST partner, Blue Clover, comes in.
Blue Clover builds the Production Line Tool (PLT), an Arm Linux device that connects to PLTcloud for remote orchestration. One PLT sits at each test station, and PLTcloud coordinates the fleet across a customer’s line.
PLT works alongside Test Agent, a second Arm Linux device purpose-built to host third-party software directly at the point of test. It replaces the general-purpose x86 PC with something simpler and more reliable, built for exactly this job.
Because much of the hardware Blue Clover and its customers build is based on STM32 microcontrollers, including the STM32L0 Cat.5 family, STM32CubeProgrammer’s CLI (STM32_Programmer_CLI) has always been core to how Test Agent programs and validates hardware during bring-up and test.
The gap: Until recently, STM32_Programmer_CLI had no native aarch64 Linux build. Blue Clover’s workaround was OpenOCD: functional, but not the ST-validated tool built for STM32 targets, and not something the team wanted to depend on long term.
The fix: Linux Arm 64-bit support in STM32CubeProgrammer. With the 2.23 release package, the footprint was slimmed down specifically for constrained targets such as SBC/SD card deployments. That matters when the host is a single-board computer on a test fixture, not a workstation.
Note: STM32CubeProgrammer is intended by ST for development and pre-production use. Blue Clover uses it accordingly in its engineering, bring-up, and validation workflows, rather than as a high-volume production programming tool.
What this unlocks
- A purpose-built machine, not a general-purpose one
- STM32_Programmer_CLI now runs directly on Test Agent, the Arm Linux device hosting the test sequence at the point of test, alongside PLT. Flashing runs on hardware designed for the job, not on a repurposed desktop PC.
- Native, ST-validated tooling
- Programming and verification now run on the official STM32CubeProgrammer CLI, instead of a general-purpose workaround.
- More reliable automation
- A purpose-built Arm device runs the same job the same way every time, instead of relying on a general-purpose PC with its own OS quirks, updates, and drivers to manage.
- Faster bring-up for STM32-based products
- Every station coordinated by PLTcloud, including Blue Clover’s own hardware and any STM32-based product it supports, benefits directly from this in future test and validation station builds.
- Every station coordinated by PLTcloud, including Blue Clover’s own hardware and any STM32-based product it supports, benefits directly from this in future test and validation station builds.
What’s next
The Linux Arm 64-bit package for STM32CubeProgrammer continues to evolve, and Blue Clover’s Production Line Tool and Test Agent are one example of what it enables for teams building automated, Arm-based test and validation infrastructure around STM32.
If you’re working on something similar, or have feedback on the package itself, let us know in the comments below.
First published on Oct 08, 2026
