Changes

| 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" |{{oldid|TBD|TBD}}| 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" |19/07/August 2023

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 stuff definitions that it is not possible to handle with STM32CubeMX. The final DTs, along with other files, are eventually pushed to the GitLab repositories accessible by the customers.