It uses the STM32CubeMX to generate a HAL-framework-based code and alongside creates the PlatformIO project with compatible parameters to glue them both together.
The GUI version is available, too (but read this main introduction first, please).
OS: Linux, macOS, Windows (few latest versions of 7, and above)
The app introduces zero dependencies by itself. Of course, you need to have all necessary tools installed on your machine in order to perform the operations:
STM32CubeMX. All recent versions are fine (5.x, 6.x).
CubeMX is written in Java, so Java Runtime Environment (JRE) is required. For CubeMX versions starting from 6.3.0 it is included in the installation bundle (of CubeMX). If you are using older versions of CubeMX, either upgrade or install JRE manually.
STM32CubeMX CLI (which is used by stm32pio) can be invoked directly (by calling the executable file) or through the Java. First case is obviously simpler, and it is a default way of operating for UNIX and macOS. On Windows, however, the latter case is the only working one (for some reason), so Java executable (whether command or path) should be specified. As mentioned above, a method of its obtaining differs depending on CubeMX version, but default settings doing their best to figure out an appropriate setup and most likely all will just work out of the box.
CubeMX embedded software packages of your choice (F0, F1, etc.) should be added into CubeMX. In case of their absence or versions mismatches you will probably be prompted by CubeMX during the code generation stage.
For more information on how STM32CubeMX functions please refer to its manual (that is shipped with the installation bundle) or community forum.
PlatformIO CLI. Its presence in your system depends on how you're using it:
choco, etc. most likely the
platformiocommand is already in your
PATHenvironment variable, and you're able to start it through a command line. In this case you're good to go.
Either way, for every tool listed above, a simple direct path to the according executable can be specified just in case you cannot or don't want to register them in your
PATH. Check the config reference to see all possible ways of telling stm32pio where the tools are residing on your machine.
The most straightforward way is to get the PyPI distribution:
pip install stm32pio
To uninstall run
pip uninstall stm32pio
As a normal Python package, the app can be run completely portable. Simply download or clone this repository and launch the main script:
stm32pio-repo/ $ python stm32pio/cli/app.py # call the file... stm32pio-repo/ $ python -m stm32pio.cli # ...or run as Python module stm32pio-repo/ $ python -m stm32pio.cli.app any-path/ $ python path/to/stm32pio-repo/stm32pio/cli/app.py # the script can be invoked from anywhere
You can always run
to see help on available commands.
Essentially, you need to follow such a workflow:
Refer to the example guide which basically explains same concepts just in more details and illustrates with some screenshots/command snippets.
See the commands reference providing the complete help about available commands/options. On the first run in your project, stm32pio will create a config file
stm32pio.ini, syntax of which is similar to
platformio.ini. You can also create such config without any following operations by initializing the project:
path/to/project $ stm32pio init
Might be useful to tweak some parameters before proceeding. See the config reference showing meanings for every key.
If you've encountered a problem and basic logs doesn't clear the situation, try the following:
This will unlock extra logs helping to clarify what's wrong
stm32pio -v ...
This will print a small report about the current setup according to your config
stm32pio new -h # "new" command manual
libfeature or be directly compiled in its own directory using
You also need to move all
lib_extra_dirs = Middlewares/Third_Party/FreeRTOS
.hsources into according directories. See PlatformIO documentation for more information.