Bureaucrats, dave_user, Administrators
8,226
edits
Changes
no edit summary
! style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white" |Notes
|-
| style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000" |August {{oldid|18391|23/08/2023}}
| style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000" |DESK-MP1-L-1.0.0 release
|-
|}
<section end="History" />__FORCETOC__<section begin="Body" />
== Introduction Using the STM32CubeMX Configuration file==
This page explains the role of the STM32CubeMX Configuration file (<code>.ioc</code>) in the context of the DESK-MP1-L. Each hardware platform supported by the DESK-MP1-L has a specific <code>.ioc</code> file. For customers' convenience, these files are available in a dedicated repository available named [[DESK-MP1-L/Development/Synchronizing_git_repositories#Synchronizing_the_git_repositories|stm32cubemx.git]].
=== Generating the Device Tree files ===
U-Boot/Linux Device Tree (DT) files provided by the DESK-MX1-L are generated starting from a STM32CubeMX Configuration file as illustrated in the following image.
STM32CubeMX is then used for exporting a set of intermediate files including the Device Trees. These DTs are subsequently tweaked by hand to add further hardware-specific definitions that it is not possible to handle with STM32CubeMX. The final DTs, along with other files, are eventually pushed to GitLab repositories accessible by the customers. These repositories are the same ones used by Yocto [[DESK-MP1-L/Development/Building_the_Yocto_BSP|to build the Linux BSP]].
===Developing applications for the ARM Cortex M4 ===
Another typical usage of the STM32CubeMX Configuration file is related to the development of applications for the ARM Cortex M4. In this case, the <code>.ioc</code> file can be imported in the [https://www.st.com/en/development-tools/stm32cubeide.html STM32CubeIDE] to start one's own project.