Recompiling DeviceTree DTBS for Orin nano super dev kit

[a.dragoset]

Hi, I was able to setup a build environment on my Ubuntu machine natively and synch sources with the source code repo following the instructions found here Kernel Customization fore release jetson_36.4.

Additionally i was able to get through the compilation of the kernel as well as the out of stream modules and device tree dtb’s following some customization i made to the dtsi files.

My question revolves around the produced dtb files namely i was able to update the device tree in tegra234-p3768-0000.dtsi and have the changes persist into tegra234-p3768-0000+p3767-0005-nv.dtb. I was able to verify this by decompiling the produced dtb file. However I am running a orin nano 8gb super dev kit and the /boot/dtb is named kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb. I noticed that no tegra234-p3768-0000+p3767-0005-nv-super.dtb gets created by compiling the generic dtbs. So copying the generated ones to /Linux_for_Tegra/kernel/dtb/ and reflashing the kernel with sdkmanager wont actually update the device tree deployed to my devkit? Am i mistaken in my approach to making device tree edits to the jetson orin nano super dev kit?

[a.dragoset]

I think i may understand whats going on here. It seems like if you flash using sdk manager with the jetson-nano 8gb dev kit configuration sdkmanager downloads a custom kernel binaries and set of configuration files that are probably some pre release version of jetpack 6.1.1 which hasn’t been released yet. So most likely i will have to put modifying the device tree for my base board off until jetpack 6.1.1 and jetson for linux 36.4.x? sources become available. At which point hopefully the extra power profiles and any differences in the super configuration profiles are baked into the normal tegra234-p3768-0000.dtsi

[WayneWWW]

The source code for this new super mode update has not been released yet.