For 2, the dtb would appear in rootfs after your first flash. If you didn’t flash the board before, then modifying the 2 files present on your side would be sufficient.
For 3, please update the dtb file mentioned in the title. Forget about that dts name in the patch. That dts does not exit.
Thanks for replay.
I flashed many times, the dtb file does’t appear .Is that a problem? or i could just modify the 2 files in my code?
And, how to build the dtb? After I finish modifying these, Can I just execute “sudo ./l4t_initrd_flash.sh jetson-agx-thor-devkit internal”?
Yes, you could modify just those 2 files.
Actually, what I want to know is: Let’s take a simple example. If I want to disable a certain interface (for instance, i2c1), which dts file should I modify? What is the subsequent process? Is there a quick way to flash?
Modify the one in kernel/dtb/ would resolve most of interface enable/disable problem because that one is in use for the kernel part setting.
Also, actually the most correct way to modify device tree is to download the source code from our website and modify dtsi files and then rebuild dtb out.
I do download the source code by “./source_sync.sh -k -t jetson_38.4“, but how to rebuild dtb out? what’s the cmd?
One way to decompile, then edit, then compile:
If ‘which dtc’ doesn’t find dts, then: ‘sudo apt install device-tree-compiler’
BPMP=bootloader/generic/tegra264-bpmp-3834-0008-4071-xxxx.dtb
dtc -I dtb -O dts -o bpmp.dts “$BPMP”
Edit bpmp.dts to change to your values
Rebuild dtb and cp it as you noted above in this post.
dtc -I dts -O dtb -o tegra264-bpmp-3834-0008-4071-xxxx.dtb bpmp.dts
