
4
Software implementation
The
The firmware package is based on the
ecosystem. Starting from the
peripherals and pins used are activated and configured according to the basic project.
The application firmware is supported and tested using
, IAR, and Keil development
environments.
After the development, the MCU can be programmed through the IDE or
To monitor and control the application, you can use a GUI based on
.
The firmware described in this documentation development is based on the STM32CubeG4 firmware package
v1.3.0.
Figure 49.
STM32Cube ecosystem development flow
An extensive range of generic and specific firmware modules is available to support the digital power conversion.
The figure below shows the generic development flow to get the power conversion used for the
Figure 50.
DPC development flow
This workflow starts from power conversion requirements. This information is then reinterpreted in the application
specs that contain information linked to the MCU peripheral and the DPC application configuration.
On the basis of this information, an
project, properly configured and initialized, is provided. Then,
the needed DPC module is included and configured.
UM2975
Software implementation
UM2975
-
Rev 1
page 29/63