I am migrating from 35.4.1 to 36.3.0 and need guidance on kernel/device-tree workflows. Previously, in 35.4.1, I successfully:
Modified device tree sources and drivers.
Replaced /boot/Image and /boot/dtb/kernel_tegra234-p3701-000-p3737-000.dtb directly.
Now with 36.3.0, I have the following questions:
After modifying the DTB and driver files, can I still directly execute ./nvbuild.sh as before?
How can I locate the modified Image file and DTB file? I noticed that the DTB filename has changed in the system (now kernel_tegra234-p3737-0000+p3701-0005-nv.dtb).
I don’t get the question in (1). Why does updating dtb and drivers have anything to do with nvbuild.sh? Whether you can run nvbuild.sh has nothing to do with whether the system has new dtb or drivers loaded.
What does that mean “locate” the modified image? The image and dtb are all built by you. Why you cannot locate them?
Perhaps my description has caused some confusion. I am performing cross-compilation on another machine, then replacing the compiled files on the Jetson AGX for verification. Due to version changes, I am currently compiling the new original code without any modifications. I’m not entirely sure where the newly compiled Image file and dtb file are located in the new version, but I have found dtb files and Image files in multiple directories within kernel_out. As a result, I’m unsure which directory’s files I should use.
