Difference between revisions of "DESK-MP1-L/Development/Using the STM32CubeMX Configuration file (.ioc)"
(Tag: Visual edit) |
|||
| Line 20: | Line 20: | ||
The first step consists 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 is named <code>DCSB5000DD1R.ioc</code> because it is strictly associated with the hardware configuration of the SBC ETRA included in the evaluation kit, whose model version is indeed [https://wiki.dave.eu/index.php/Product_serial_number%7CDCSB5000DD1R DCSB5000DD1R]. | The first step consists 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 is named <code>DCSB5000DD1R.ioc</code> because it is strictly associated with the hardware configuration of the SBC ETRA included in the evaluation kit, whose model version is indeed [https://wiki.dave.eu/index.php/Product_serial_number%7CDCSB5000DD1R DCSB5000DD1R]. | ||
| − | 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 | + | 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 also used by Yocto to build the BSP. |
| + | |||
| + | The starting <code>.ioc</code> files are instead available in a separated repository. TBD insert link | ||
Revision as of 10:00, 3 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 | ||
This page details how the U-Boot/Linux Device Tree (DT) files are created. The process is illustrated in the following image.
The first step consists of creating a .ioc file with the help of the https://www.st.com/en/development-tools/stm32cubemx.html STM32CubeMX tool. The file is named DCSB5000DD1R.ioc because it is strictly associated with the hardware configuration of the SBC ETRA included in the evaluation kit, whose model version is indeed DCSB5000DD1R.
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 also used by Yocto to build the BSP.
The starting .ioc files are instead available in a separated repository. TBD insert link
