Hello, Anybody
Check the /boot directory in jp4.6.1 (l4t R32.7.1)
What is difference following two dtbs?
kernel_tegra210-p3448-0002-p3449-0000-b00.dtb
tegra210-p3448-0002-p3449-0000-b00.dtb
Thank you.
Hello, Anybody
Check the /boot directory in jp4.6.1 (l4t R32.7.1)
What is difference following two dtbs?
kernel_tegra210-p3448-0002-p3449-0000-b00.dtb
tegra210-p3448-0002-p3449-0000-b00.dtb
Thank you.
You can use dtc tool to dump both and check the diff between them.
Hell0, are there any introductory documents related to all device trees in jetpack32.5.1, such as device tree functions, USB-related device trees, etc.
Thank you !!
This isn’t what you are asking, but if you want to explore the plain text version of a binary tree (you might need to “sudo apt-get install device-tree-compiler
”):
dtc -I dtb -O dts -o extracted.dts some_binary_tree.dtb
At that point, with two different trees, you can just examine them to see how they differ.
Is there a difference between building DTC using this command and building DTC from source.
All our dtb files are built from sources. Basically, the content needs to be same.
In theory the total content is the same either way. The dtc
decompile command just creates source from binary content, and the forward compile creates binary content from source content. The logical content should be the same regardless of how many times you cycle between binary->source->binary.
However, the kernel build does combine smaller blocks/snippets of device tree source code depending on what features are enabled during the build. I don’t know if the order of the original blocks would be preserved, but since it is a tree structure, you can expect the logical content to remain constant.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.