Jetson Linux 36.3: Orin Nano device tree updates

[logicbloomlabs]

Our platform uses the following machine jetson-orin-nano-devkit-nvme. We are exploring use of Yocto as the build system for our target. We are following this resource: GitHub - OE4T/tegra-demo-distro: Reference/demonstration distro for meta-tegra, checking out the scarthgap branch.

When inspecting the kernel and Tegra sources provided by Jetpack 6.0 release, we noticed that the following device tree(s) are no longer present in the available source tree fetched:

error: platform/t23x/p3768/kernel-dts/cvb/tegra234-p3509-a02-pcie.dtsi: does not exist in index
error: platform/t23x/p3768/kernel-dts/cvb/tegra234-p3509-a02.dtsi: does not exist in index
error: platform/t23x/p3768/kernel-dts/cvb/tegra234-p3768-0000-a0-pcie.dtsi: does not exist in index
error: platform/t23x/p3768/kernel-dts/cvb/tegra234-p3768-0000-a0.dtsi: does not exist in index
error: platform/t23x/p3768/kernel-dts/cvb/tegra234-p3768-camera-rbpcv2-imx219.dtsi: does not exist in index

We apply patches to the above device tree(s) for our platform and now the patch no longer applies gracefully due to missing device tree sources.

Any ideas where the device tree(s) could be found? If they have been updated / removed / modified, what should the target device tree(s) be for our machine?

Thanks!

[kayccc]

For Yocto build related issue, suggest to get contact with Ridgerun to get the support.
Yocto Support for NVIDIA Jetson Platforms - Yocto Support for NVIDIA Jetson Platforms - Setting up Yocto (ridgerun.com)

[logicbloomlabs]

Hi there,

This is not a Yocto build related issue. This is related to the new BSP / Jetson Linux 36.3 source and the deprecation / modification of preexisting device tree(s). With the new JetPack 6.0 release, we notice that the aforementioned device tree(s) no longer exist. So, we are trying to gather more information about this (since our patches no longer apply to non-existent device trees).

[WayneWWW]

Hi,

The actual problem here is
→ Yes, these device tree are indeed not there anymore.
→ Next question is why you still need them.

Those device tree are only used in old jetpack5 release. It is common that device trees are different when such major release version upgrade.

[logicbloomlabs]

Hello,

Thanks for the information!

Next question is why you still need them.

We have patches that apply against these device tree(s). It is okay for us to transition to the newer device tree(s).

So if the major release version upgrade resulted in:

device tree A → device tree B, where can we find the information about this transition and what our target device tree should be relative to what we were patching / modifying before?

Thanks!

[WayneWWW]

There is no rule to say there must be a new device tree mapping to the old one.

For example, there was tegra234-p3768-0000-a0-pcie.dtsi as a dedicated one for PCIe. But it could be gone on rel-36 now and no one guarantee there must be a similar DT to write this on rel-36. They could be in anywhere inside the hardware directory. You should try to trace it the code.

[logicbloomlabs]

Understood, thanks for the info!