[问答]

我可以删除这部分并创建一个 ***.pinctrl.dtsi 文件吗？

问答对人有帮助，内容完整，我也想知道答案 0 在STM32mp157c-ed1.dts中，MPU的pin设置是写在stm32mp15-pinctrl.dtsi文件中的，但是在CubeMX中，会在生成的.dts文件中创建一个名为@pinctrl的节点，并写入其中。为什么？我可以删除这部分并创建一个 ***.pinctrl.dtsi 文件吗？ 0
2022-12-6 09:08:56　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × wang21cj 该类别下有 44 个回答。邀请回答新星之火12138 该类别下有 41 个回答。邀请回答 chm5 该类别下有 39 个回答。邀请回答 hgimtk 该类别下有 33 个回答。邀请回答 HengDu 该类别下有 30 个回答。邀请回答 hwp0415229 该类别下有 28 个回答。邀请回答 jghgfdssas 该类别下有 28 个回答。邀请回答可口可甜该类别下有 26 个回答。邀请回答 kingnet6688 该类别下有 26 个回答。邀请回答颜刚YanG 该类别下有 26 个回答。邀请回答 zyh34997 该类别下有 25 个回答。邀请回答柱子图宁该类别下有 25 个回答。邀请回答 kingnet9999 该类别下有 25 个回答。邀请回答 jenny042 该类别下有 25 个回答。邀请回答 andyfly7 该类别下有 25 个回答。邀请回答麻酱该类别下有 25 个回答。邀请回答成长的小师弟该类别下有 24 个回答。邀请回答 gXDhn 该类别下有 24 个回答。邀请回答 jiangwenwen 该类别下有 24 个回答。邀请回答哼小曲该类别下有 24 个回答。邀请回答举报王锦霞相关推荐 • 如何通过配置dtsi文件来使触摸屏功能工作？ 187 • 如何将zephyr移植到MCIMX7U5 cm4？ 248 • 如何设置一个路径创建文件并写入数据？ 2130 • 如何在CubeIDE项目中创建文件树并删除Src Inc文件夹？ 278 • 可以在同一个设备中使用USB-OTG和USART1吗？ 158 • 是否有任何指南可以为任何板创建一个带有CubeMX的项目？ 240 • 是否可以删除第一个对象之后创建的其他对象？ 696 • 如何编写一个dts文件以将16ch TDM与“simple-audio-card”一起使用？ 334 • 我如何确定创建的BIN文件处于正确顺序呢？ 165 • 如何在设备树中创建UART接口？ 211 2个回答

答案对人有帮助，有参考价值 0 为Starter包提供的设备树结构和CubeMx生成的设备树结构略有不同。

2022-12-6 14:10:56 评论举报陈强

1 Purpose and scope↑

This article shows the structure of the device tree files as it is implemented in OpenSTLinux for Linux® kernel, U-Boot, TF-A and OP-TEE.
The purpose of this article is not to explain the device tree concept and the device tree configuration supported by STM32MP1 Series. A good knowledge of the concept is a prerequisite before reading this article. The articles regarding the configuration can be read afterwards.
2 Device tree structure↑

The device tree files are used during boot time by the FSBL (TF-A), the secure OS (OP-TEE), the SSBL (U-Boot) and, at run time, by the Linux kernel.

These files are stored in different github repositories (one for each first level bullet below), but source code reuse is maximized from one repository to another:

The initial device tree files supporting STM32MP1 Series are created in the Linux kernel.
- The source code path is arch/arm/boot/dts/stm32mp1*.
In U-Boot, Linux files are copied and overloaded with U-Boot properties.
- The source code path is arch/arm/dts/stm32mp1*.
- The U-Boot add-ons file, "-u-boot.dtsi", is automatically included at the end of ".dts" during device tree compilation: this is a generic U-Boot Makefile behavior, see binman.rst.
In TF-A, Linux files are copied, completed with the security configuration (firewalling) and the DDR configuration. TF-A BL2 is applying some 'delete-property' on useless nodes, to lighten the final dtb file.
- The source code path is fdts/stm32mp1*.
In OP-TEE, Linux files are reused.
- The source code path is core/arch/arm/dts/stm32mp1*.

The figure below shows the device tree files structure for Linux, U-Boot, TF-A and OP-TEE:

Information

The board level device tree file completes and/or overloads the default peripherals nodes configuration, defined in the included SoC dtsi file.
The above figure reflects the current implementation on github and may be somehow in advance compare to the upstreamed version for all parts that are still under review.
For the sake of simplicity, the figure only shows the dtsi & dts files structure, without showing the h files that are also included.
The dtb files, resulting from the compilation with the dtc compiler, may be named differently when the compilation is launched with the Distribution Package.

3 STM32CubeMX generated device tree↑

STM32CubeMX can help to generate the device tree files for a given project, for the various software components:

TF-A: STM32CubeMX generates three files:

- 'stm32mp15-mx.dtsi' is equivalent to 'stm32mp1*-.dtsi' in the diagram above, embedding DDR settings
- 'stm32mp1*--mx.dts' is the board device tree file, that includes all dtsi files (directly or not)
- 'stm32mp1*--mx-fw-config.dts' file corresponds to the TF-A firmware configuration and is out of the file structure shown in the previous paragraph

U-Boot:

- 'stm32mp1*--mx.dts' is the board device tree file, that includes all dtsi files (directly or not)
- 'stm32mp1*--mx-u-boot.dts' is equivalent to the '-u-boot.dtsi' file in the diagram above

Linux:

- 'stm32mp1*--mx.dts' is the board device tree file, that includes all dtsi files (directly or not)

OP-TEE:

- 'stm32mp1*--mx.dts' is the board device tree file, that includes all dtsi files (directly or not)

The device tree files generated by STM32CubeMX can be built with the Developer Package or Distribution Package:

Use the Developer Package to store the STM32CubeMX-generated files in the folder of your choice. Then, manually copy or link them into Linux, U-Boot and TF-A device tree folders (see Device tree structure). Do not forget to add your device tree file name in ../Makefile.sdk (for TF-A SDK and U-Boot SDK) and in arch/arm/boot/dts/Makefile (for Linux kernel SDK), before compiling them as explained in How to cross-compile with the Developer Package.
Use the Distribution Package to store the STM32CubeMX-generated files in meta-st/meta-st-stm32mp-addons/mx, as explained in the How to create your own machine article. This article also describes how to build the complete image. Examples of Linux (device tree), U-Boot and TF-A individual compiling can be found in the How to cross-compile with the Distribution Package article.