If you’ve ever flashed, then you will have a directory “~/nvidia/nvidia_sdk/JetPack_...version info.../Linux_for_Tegra/
”. In terms of flashing, everything will be in that directory or a subdirectory. For example, you should be able to find:
~/nvidia/nvidia_sdk/JetPack_...version info.../Linux_for_Tegra/kernel/dtb/
# Which has several dtb files. One is:
~/nvidia/nvidia_sdk/JetPack_...version info.../Linux_for_Tegra/kernel/dtb/tegra194-p3668-all-p3509-0000.dtb
Also, if you look in the docs for kernel build or kernel customization, then most device trees are also a build target there. If you were to configure the kernel source to match your running system, and then build the kernel target for “make dtbs
”, this would result in a lot of “.dtb
” files being generated. Presumably, " tegra194-p3668-all-p3509-0000.dtb
" would be one of them.
Note that dtb files can be reverse compiled, examined, edited, and recompiled. A typical reverse compile would go something like this:
dtc -I dtb -O dts -o reversed_tegra194-p3668-all-p3509-0000.dts tegra194-p3668-all-p3509-0000.dtb
# You could then examine tegra194-p3668-all-p3509-0000.dts, edit, and rebuild:
dtc -I dts -O dtb -o reversed_tegra194-p3668-all-p3509-0000.dtb reversed_tegra194-p3668-all-p3509-0000.dts
(I preppended the name “reversed_” to generated files, but you can name them anything you want).