How to update TX2 dtb/Image with Jetpack 4.5?

Follow the link instructions to resolve the TX2I usb does not work.
I compiled the kernel and device tree.
In TX2 recovery mode,
sudo ./flash -r -k kernel-dtb jetson-tx2i mmcblk0p1
sudo ./flash -r -k kernel jetson-tx2i mmcblk0p1

No error is reported during the update process, indicating that the update is successful!!
*** The [kernel-dtb] has been updated successfully. ***
*** The [kernel] has been updated successfully. ***
However, through “uname - a”, it is found that the kernel compilation time and the compiled time are incorrect。
View the device tree through the dtc. It is found that the device tree has not been modified successfully.

Kernel is read from /boot/Image directly.

Thus, you don’t need to run -r -k kernel. Just put your new kernel image to that path of your device

However, your method to update device tree is correct. How did you check your device tree with dtc? Which file did you give to dtc?

Which file I should to dtc? /boot/tegra186-quill-p3489-1000-a00-00-ucm1.dtb?


This “/boot/tegra186-quill-p3489-1000-a00-00-ucm1.dtb” is not in use. Your device tree is flashing to “kernel-dtb” partition. So dtc this file of course will give you the old content. Whatever you found under your rootfs system is in “APP” partition, so they are not related.

You should go to /proc/device-tree and see if your change is added there… but not using dtc.

Is this update successful?

這裡可能要提醒你一下… 你從頭到尾都沒有提到你改了什麼…
所以你現在貼這邊問我有沒有更新成功 …我應該是不會知道的…

Just want to remind you that… you didn’t mention what you changed from the beginning…
So whether it is updated correctly or not… I won’t be able to know…

Sorry, I forgot to say that the device tree was modified. I modified the following content.

You should use “xxd” to check the node instead of “cat”.

Also, since this is hex value now, you need to check the phandle of battery_reg to know if this what you added.

I know how to do it, thank you very much!!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.