I have one question about finding more easy, more efficient method than the following my approach.
At JetPack 4.2.2 we modified usb and audio related dtsi file and flashed one compiled dtb file to kernel-dtb region by using the following command.
(We have our target board which uses three I2S channels all.)
sudo ./flash.sh -r -k kernel-dtb jetson-xavier mmcblk0p1 ------ flashing command 1
There has been no problem with this usage.
However lately when we upgraded to JetPack 4.3, we met the one problem that I2S2 port is set as gpio at default.
After some time, I found that the problem can be cured by jetson-io tool, but
jetson-io tool seems to make from /boot/dtb/tegra194-p2888-0001-p2822-0000.dtb to /boot/tegra194-p2888-0001-p2822-0000-user-custom.dtb file.
Disappointedly, according to experiment the flashing command 1 (above) does not update /boot/dtb/~.dtb into my custom dtb file.
It seems that /boot/dtb/~.dtb is replaced by kernel flashing command (sudo ./flash.sh jetson-xavier mmcblk0p1).
After flashing kernel, all sdk component (cuda, ai, etc) is erased, so I must install them again, including my work codes as well.
By any chance, is there any easier and more efficent method for changing dtb file when using my custom dtb and jetson-io touched dtb together?