Small cross-platform Python app that can create and update PlatformIO projects from STM32CubeMX .ioc files.
It uses STM32CubeMX to generate a HAL-framework-based code and alongside creates PlatformIO project with compatible parameters to stick them both together.
- Start the new complete project in a single directory using only an
.iocfile - Update an existing project after changing hardware options in CubeMX
- Clean-up the project (WARNING: it deletes ALL content of project path except the
.iocfile!) - Get the status information
- [optional] Automatically run your favorite editor in the end
- [optional] Automatically make an initial build of the project
- [optional] GUI version (beta) (see stm32pio-gui sub-folder for the dedicated README)
- For this app:
- Python 3.6 and above
platformio
- For usage:
- macOS, Linux, Windows
- STM32CubeMX with desired downloaded frameworks (F0, F1, etc.)
- Java CLI (JRE) (likely is already installed if the STM32CubeMX is working)
- PlatformIO CLI (already presented if you have installed PlatformIO via some package manager or need to be installed as the "command line extension" from IDE)
A general recommendation there would be to test both CubeMX (code generation) and PlatformIO ( 8000 project creation, building) at least once before using stm32pio to make sure that all tools work properly even without any "glue".
You can run the app in a portable way by downloading or cloning the snapshot of the repository and invoking the main script or Python module:
$ python3 stm32pio/app.py
$ # or
$ python3 -m stm32pio(we assume python3 and pip3 hereinafter). It is possible to run the app like this from anywhere.
However, it's handier to install the utility to be able to run stm32pio from anywhere. Use
stm32pio-repo/ $ pip3 install .command to launch the setup process. Now you can simply type 'stm32pio' in the terminal to run the utility in any directory.
Finally, the PyPI distribution (starting from v0.95) is available:
$ pip install stm32pioTo uninstall in both cases run
$ pip uninstall stm32pioBasically, you need to follow such a pattern:
- Create CubeMX project (.ioc file), set-up your hardware configuration, save
- Run the stm32pio that automatically invokes CubeMX to generate the code, creates PlatformIO project, patches a
platformio.inifile and so on - Work on the project in your editor as usual, compile/upload/debug etc.
- Edit the configuration in CubeMX when necessary, then run stm32pio to re-generate the code.
Refer to Example section on more detailed steps. If you face off with some error try to enable a verbose output to get more information about a problem:
$ stm32pio -v [command] [options]On the first run stm32pio will create a config file stm32pio.ini, syntax of which is similar to the platformio.ini. You can also create this config without any following operations by initializing the project:
$ stm32pio init -d path/to/projectIt may be useful to tweak some parameters before proceeding. The structure of the config is separated in two sections: app and project. Options of the first one is related to the global settings such as commands to invoke different instruments though they can be adjusted on the per-project base while the second section contains of project-related parameters. See comments in the settings.py file for parameters description.
You can always run
$ python3 app.py --helpto see help on available commands.
Note, that the patch operation (which takes the CubeMX code and PlatformIO project to the compliance) erases all the comments (lines starting with ;) inside the platformio.ini file. They are not required anyway, in general, but if you need them for some reason please consider to save the information somewhere else.
For those who want to modify the patch (default one is at settings.py, project one in a config file stm32pio.ini): it can has a general-form .INI content so it is possible to specify several sections and apply composite patches. This works totally fine for the most cases except, perhaps, some really big complex patches involving, say, the parameters interpolation feature. It is turned off for both platformio.ini and user's patch parsing by default. If there are some problems you've met due to a such behavior please modify the source code to match the parameters interpolation kind for the configs you need to. Seems like platformio.ini uses ExtendedInterpolation for its needs, by the way.
You can also use stm32pio as an ordinary Python package and embed it in your own application. Take a look at the CLI (app.py) or GUI versions to see some possible ways of implementing this. Basically, you need to import stm32pio.lib module (where the main Stm32pio class resides), (optionally) set up a logger and you are good to go. If you prefer higher-level API similar to the CLI version, use main() function in app.py passing the same CLI arguments to it (except the actual script name).
- Run CubeMX, choose MCU/board, do all necessary tweaking
- Select
Project Manager -> Projecttab, specify "Project Name", choose "Other Toolchains (GPDSC)". InCode Generatortab check "Copy only the necessary library files" and "Generate periphery initialization as a pair of '.c/.h' files per peripheral" options
- Back in the first tab (Project) copy the "Toolchain Folder Location" string (you maybe not be able to copy it in modern CubeMX versions so use terminal or file manager to do this). Save the project, close CubeMX
- Use a copied string as a
-dargument for stm32pio. So it is assumed that the name of the project folder matches the name of.iocfile. (-dargument can be omitted if your current working directory is already a project directory) - Run
platformio boards(pio boards) or go to boards to list all supported devices. Pick one and use its ID as a-bargument (for example,nucleo_f031k6) - All done! You can now run
to trigger the code generation, compile the project and start the VSCode editor with opened folder (last 2 options are given as an example and they are not required). Make sure you have all the tools in PATH (
$ stm32pio new -d path/to/cubemx/project/ -b nucleo_f031k6 --start-editor=code --with-build
java(or set its path instm32pio.ini),platformio,python, editor). You can use a slightly shorter form if you are already located in the project directory:path/to/cubemx/project/ $ stm32pio new -b nucleo_f031k6
- To get the information about the current state of the project use
statuscommand. - If you will be in need to update hardware configuration in the future, make all the necessary stuff in CubeMX and run
generatecommand in a similar way:$ stm32pio generate -d /path/to/cubemx/project
- To clean-up the folder and keep only the
.iocfile runcleancommand.
There are some tests in file test.py (based on the unittest module). Run
stm32pio-repo/ $ python3 -m unittest -b -vor
stm32pio-repo/ $ python3 -m stm32pio.tests.test -b -vto test the app. It uses STM32F0 framework to generate and build a code from the test stm32pio-test-project.ioc project file. Please make sure that the test project folder is clean (i.e. contains only an .ioc file) before running the test otherwise it can lead to some cases failing.
For the specific test suite or case you can use
stm32pio-repo/ $ python3 -m unittest stm32pio.tests.test.TestIntegration -b -v
stm32pio-repo/ $ python3 -m unittest stm32pio.tests.test.TestCLI.test_verbose -b -v- The tool doesn't check for different parameters compatibility, e.g. CPU frequency, memory sizes and so on. It simply eases your workflow with these 2 programs (PlatformIO and STM32CubeMX) a little bit.
- CubeMX middlewares are not supported yet because it's hard to be prepared for every possible configuration. You need to manually adjust them to build appropriately. For example, FreeRTOS can be added via PlatformIO'
libfeature or be directly compiled in its own directory usinglib_extra_dirsoption:You also need to move alllib_extra_dirs = Middlewares/Third_Party/FreeRTOS.c/.hfiles to the appropriate folders respectively. See PlatformIO documentation for more information. - The project folder, once instantiated, is not portable i.e. if you move it at some other place and invoke stm32pio it will report you an error. This because
stm32pio.iniconfig is currently stores absolute paths instead of relative.