2021-07-20 03:13 AM
Hi,
According to this article, https://community.st.com/s/article/FAQ-STM32MP1-Bring-up-procedure , the devicetree files generated by STM32CubeMX are incomplete.
We have created a CubeMX project for our stm32mp151c and made some modifications and generated device tree files. However, these device tree files can not be used to compile the tf-a and u-boot components with the developer package. Therefore, we have tried to follow the Lab-BringUpFromPartNumber (from the article above). However, the lab compares the bring up device trees with the mx DK2 board using the stm32mp157c. In our case, there is no board with the stm32mp151c, which means that we can't generate default device trees to compare and merge the missing nodes to our device trees.
Is it possible to compare and merge our device trees (that are created for stm32mp151c) with the default device trees for the DK2 board with stm32mp157c exactly as Lab-BringUpFromPartNumber describes? If not, how should we know exactly what to add to our device trees to be able to compile them with the developer package?