Difference between revisions of "DESK-MP1-L/Development/Using the STM32CubeMX Configuration file (.ioc)"
m (U0001 moved page DESK-MP1-L/Development/Generating Device Trees with STM32CubeMX to DESK-MP1-L/Development/Using the STM32CubeMX Configuration file (.ioc) without leaving a redirect) |
|||
| Line 10: | Line 10: | ||
|- | |- | ||
|} | |} | ||
| − | <section end="History" /> | + | <section end="History" />__FORCETOC__<section begin="Body" /> |
| − | __FORCETOC__ | ||
| − | <section begin="Body" /> | ||
| − | This page | + | == Introduction == |
| + | 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 [here]. TBD insert link | ||
| + | |||
| + | == 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. | ||
[[File:DESK-MP1-L-device-trees-generation.png|center|thumb|800x800px]] | [[File:DESK-MP1-L-device-trees-generation.png|center|thumb|800x800px]] | ||
| − | The first step | + | The first step 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 the model version of the hardware platforms it is associated with. For instance, the file <code>DCSB5000DD1R.ioc</code> refers to the model of the SBC ETRA included in the evaluation kit (for more details about model version and serial numbers, please see [https://wiki.dave.eu/index.php/Product_serial_number%7CDCSB5000DD1R this 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 used by Yocto to build the BSP. | + | 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. | ||
Revision as of 15:15, 4 August 2023
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Issue Date | Notes | ||
| August 2023 | DESK-MP1-L-1.0.0 release | ||
Contents
Introduction[edit | edit source]
This page explains the role of the STM32CubeMX Configuration file (.ioc) in the context of the DESK-MP1-L. Each hardware platform supported by the DESK-MP1-L has a specific .ioc file. For customers' convenience, these files are available in a dedicated repository available [here]. TBD insert link
Generating the Device Tree files[edit | edit source]
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.
The first step consisted of creating a .ioc file with the help of the STM32CubeMX tool. The file name is the model version of the hardware platforms it is associated with. For instance, the file DCSB5000DD1R.ioc refers to the model of the SBC ETRA included in the evaluation kit (for more details about model version and serial numbers, please see this 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 to build the Linux BSP.
Developing applications for the ARM Cortex M4[edit | edit source]
Another typical usage of the STM32CubeMX Configuration file is related to the development of applications for the ARM Cortex M4. In this case, the .ioc file can be imported in the STM32CubeIDE to start one's own project.
