| 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 2023/08/23

== Using the STM32CubeMX Configuration file==This page details how 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 created. The process is generated starting from a STM32CubeMX Configuration file as illustrated in the following image.

The first step consists consisted of creating a <code>.ioc</code> file with the help of the [https://www.st.com/en/development-tools/stm32cubemx.html STM32CubeMX tool]. The file name is named the model version of the hardware platforms it is associated with. For instance, the file <code>DCSB5000DD1R.ioc</code> because it is strictly associated with refers to the hardware configuration model of the SBC ETRA included in the evaluation kit, whose (for more details about model version is indeed and serial numbers, please see [https://wiki.dave.eu/index.php/Product_serial_number%7CDCSB5000DD1R DCSB5000DD1Rthis page]).

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]].

The starting ===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> files are instead available file can be imported in a separated repositorythe [https://www.st.com/en/development-tools/stm32cubeide.html STM32CubeIDE] to start one's own project. TBD insert link