Cube.MX CMSIS-PACK
Impulses can be deployed as a CMSIS-PACK for STM32. This packages all your signal processing blocks, configuration and learning blocks up into a single package. You can include this package in any STM32 project with a single function call. The CMSIS-PACK uses EON to run any neural network, and CMSIS-DSP for all signal processing code - ensuring that models run as fast and efficiently as possible. In this tutorial, you'll export an impulse, import the impulse into STM32CubeMX, and then integrate it in your STM32 project to classify sensor data.
Using this CMSIS-PACK is currently only supported from C++ applications using STM32CubeIDE, on all Cortex-M MCUs.
Prerequisites
Make sure you followed the Continuous motion recognition tutorial, and have a trained impulse. Also install the following software:
Make sure you have a C++ project configured that compiles for your target. You can convert an existing project to C++ by right-clicking on your project and selecting Convert to C++.
Enabling the CRC
The CRC needs to be enabled for your target. Open your .ioc
file, then:
Go to Pinout & Configuration.
Select Computing > CRC.
Enable the Activated checkbox.
Adding the CMSIS-PACK
Head over to your Edge Impulse project, and go to Deployment. From here you can create the full library which contains the impulse and all external required libraries. Select Cube.MX CMSIS-PACK and click Build to create the library.
To add the CMSIS-PACK library to your project, open your .ioc
file, then:
Go to Help > Manage embedded software packages.
Select From Local ... and select the
.pack
file you just downloaded.Accept the license agreement, and the pack will be installed. The version number is automatically updated whenever you export the pack.
Go back to your
.ioc
file, and go to Pinout & Configuration.Click Software packs > Select components.
Select your project, expand the pack, and add a checkbox under 'Selection'.
Click OK to close the window.
Under Pinout & Configuration, select 'Additional software', and click on your project name. Place a checkbox next under 'Mode'.
Click in the 'Project explorer' so the
.ioc
file loses focus.Click
CTRL+S
orCMD+S
to save the workspace. This will regenerate the code. Afterward you should have a 'Middleware' folder in your project with your impulse and all required libraries.
The code generator always generates a new
main.c
file, even for C++ projects. If you have both amain.c
and amain.cpp
file now, remove themain.c
file.
Configuring printf
printf
To log debug information the CMSIS-PACK uses the (weak defined) ei_printf
function. You need to override this function in your main.cpp
(if you only have a main.c
rename it) to log to your UART port. E.g. this is how you set this up on the ST B-L475E-IOT01A. Under USER CODE BEGIN 0
add:
Running the impulse
With the CMSIS-PACK included, and the UART set up, it's time to verify that the application works. Head back to the studio and click on Live classification. Then load a validation sample, and click on a row under 'Detailed result'.
To verify that the local application classifies the same, we need the raw features for this timestamp. To do so click on the 'Copy to clipboard' button next to 'Raw features'. This will copy the raw values from this validation file, before any signal processing or inferencing happened.
Open main.cpp
(if you only have a main.c
rename it) and add the following code under USER CODE BEGIN Includes
(replace the features
array with the data you just copied):
Then, under USER CODE BEGIN Init
, add:
And, under USER CODE BEGIN WHILE
, add:
Then build and flash the application to your development board, via Project > Build All and Run > Debug.
Issues flashing through STM32CubeIDE?
If you have issues flashing through the IDE, right click on your project name, select Properties > Resources, and note the location of your project under 'Location'. In this folder you'll find a Debug
and/or a Release
folder with the built binaries (end with .bin
). Many ST boards mount as a mass-storage device (e.g. the ST IoT Discovery Kit and virtually all NUCLEO boards), and you can also flash by dragging the binary file to this mass storage device.
Seeing the output
To see the output of the impulse, connect to the development board over a serial port on baud rate 115,200 and reset the board (e.g. by pressing the black button on the ST B-L475E-IOT01A. You can do this with your favourite serial monitor or with the Edge Impulse CLI:
This will run the signal processing pipeline, and then classify the output:
Which matches the values we just saw in the studio. You now have your impulse running on your STM32 development board!
Upgrading the CMSIS-PACK
To upgrade your CMSIS-PACK do this:
Download the new version of the CMSIS-PACK from Edge Impulse.
Open your
.ioc
file, go to Pinout & Configuration > Additional software and select the CMSIS-PACK.De-select the checkbox under 'Mode'.
Click in the 'Project explorer' so the
.ioc
file loses focus, and pressCTRL+S
orCMD+S
. This will generate some new code.Remove the 'Middlewares/Third_party' folder.
Go back to the
.ioc
file, select Help > Manage embedded software packages and add the new CMSIS-PACK.On the
.ioc
page, click Software Packs > Select Components.Find your CMSIS-PACK, and expand the line. If the 'Selection' checkbox is selected, uncheck this first.
Change the Version dropdown to the new CMSIS-PACK version.
Expand the item again, and enable the 'Selection' toggle. Press OK to exit the modal.
Find the new CMSIS-PACK version under 'Additional software' in the item list, click on it (there are now probably multiple CMSIS-PACKs listed here for some reason), and set a new checkbox under 'Mode'.
Click in the 'Project explorer' so the
.ioc
file loses focus, and pressCTRL+S
orCMD+S
. This will generate some new code.Remove
main.c
as it will be generated again.You now have a new CMSIS-PACK version!
Last updated