hello 2309200691,
Jetson AGX Thor Developer Kit using below board configuration.
$ ll jetson-agx-thor-devkit.conf
jetson-agx-thor-devkit.conf -> p3834-0008-p4071-0000-nvme.conf
please also refer to below..
$public_sources/kernel_src/hardware/nvidia/t264/nv-public/overlay/tegra264-p3971-0000+p3834-xxxx-csi.dts
overlay-name = "Jetson AGX CSI Connector";
compatible = "nvidia,p3971-0050+p3834-0005", "nvidia,p3971-0080+p3834-0008", "nvidia,p3971-0089+p3834-0008";
as you can see.. you should flash your target with the those SKUs (i.e. p3971) to enable CSI configuration.
see-also Jetson_Linux_Release_Notes_r38.4.pdf for section [7. Implementation Details] to have implementation.
Hi JerryChang
We had a similar issue, but we directly used the existing dtbo file under /boot for our experiment. We tried to overwrite the dtbo file by modifying extlinux.conf, but after rebooting, the dtbo content wasn’t updated in /proc/device-tree.
We used tegra264-p3971-camera-imx185-overlay.dtbo for our experiment.
We’ve confirmed that replacing Device-tree with FDT works, but adding dtbo using OVETLAYS doesn’t change the dtbo content.
The image below shows our extlinux.conf file.
Best regards
Jack.lan
hello jack_lan,
please refer to my previous post #22, you’ll need to load the device tree with the those SKUs (i.e. p3971) to enable CSI configuration.
Hi JerryChang
We follow post #22 modify dtbo , however overlays still not work .
Can help me check this status?
Best regards
Jack.lan
it’s strange, I got access denied by downloading that attachment.
it might be the file naming issue (i.e. *.dtbo.zip) could you please try rename it for testing?
Hi JerryChang
Thanks~
dtbo.zip (1.5 KB)
Best regards
Jack.lan
hello jack_lan,
as mentioned earlier, Jetson AGX Thor Developer Kit using below board configuration.
jetson-agx-thor-devkit.conf -> p3834-0008-p4071-0000-nvme.conf
you may double check cat /etc/nv_boot_control.conf for confirmation.
for instance,
$ cat /etc/nv_boot_control.conf
TNSPEC 3834-400-0008-G.5-1-1-jetson-agx-thor-devkit-
COMPATIBLE_SPEC 3834-000-0008--1--jetson-agx-thor-devkit-
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_CHIPID 0x26
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
hence..
the FDT entry within your extlinux.conf doesn’t include the property settings to enable CSI configuration.
i.e. FDT /boot/dtb/kernel_tegra264-p4071-0000+p3834-0008-nv.dtb
please refer to above post #9,
please works with HSB camera via QSFP slot, or USB camera on Jetson AGX Thor Developer Kit.
Hi JerryChang
That is my nv_boot_control.conf
I think maybe need use string “3834-000-0008” , We updated compatible to “nvidia,p4071-0000+p3834-0000”, “nvidia,p3834-0000”, “nvidia,p4071-0000+p3834-0008”, “nvidia,p3834-0008”, “nvidia,tegra264”
But DTBO still hasn’t taken effect…
The updated DTBO DTS is attached.
dtbo_2.zip (1.4 KB)
Best regards
Jack.lan
hello jack_lan,
it’s a bad practice to add compatible string since Jetson-IO doesn’t support with p3834.
besides.. it’s loading device tree via partition instead of root file system.
Hi JerryChang
I’ve also tried removing the compatible option, but dtbo still doesn’t work. Do you have a dtbo version that works with Thor that we can test?
Best regards
Jack.lan
hello jack_lan,
Jetson AGX Thor did not use the dtbo approach,
please download Driver Package (BSP) for the r38.4 kernel sources,
see-also developer guide Building the DTBs.
Hi JerryChang
I’d like to confirm something. From the older Xavier series to the Orin series, many features relied on DTBO to partially override the device-tree, enabling dynamic switching of device-tree functionality.
Do you mean that starting with Jetson Thor, DTBO will no longer be supported, and we’ll have to replace the entire device-tree using FDT?
Best regards
Jack.lan
hello jack_lan,
it’s due to the device tree blob of Thor has no camera nodes included, that’s why overlay did not take effected.
you may give it a try to dump device tree into dts formats for checking.
for instance,
$ sudo dtc -I dtb -O dts -o temp.dts /boot/dtb/kernel_tegra264-p4071-0000+p3834-0008-nv.dtb
nevertheless, you may have modification for loading the entire device-tree via FDT.
