Jetson agx orin 64G boot failed after Camera Driver Porting(35.2.1->36.3)on custom board

I am trying to port my sensor driver keeping tegra234-p3737-0000-camera-imx185-a00.dtsi as reference.

first,I enclose the previous dts statement with some following sentences:

fragment-camera@0 {
target-path = “/”;
overlay {

fragment-camera-yuv@0 {
target-path = “/bus@0”;
overlay {

(and add “status = “disabled”;” in every module,However, I have tried adding or not adding the phrase ,boot still failed)

then,I could see that tegra234-p3737-0000+p3701-0000-dynamic.dts has an include to the above dtsi file. So i replaced that with my driver

//include “tegra234-p3737-camera-modules.dtsi”
include “tegra234-p3737-0000-yuv-camera.dtsi”

Finally decompile dts:
tegra234-p3737-0000+p3701-0000-dynamic.dts.txt (38.2 KB)

after flash,it boot failed:

Jetson System firmware version 36.3.0-gcid-36191598 date 2024-05-06T16:58:59+00:
00
ESC to enter Setup.
F11 to enter Boot Manager Menu.
Enter to continue boot.

Failed to validate rootfs status: Load Error
L4TLauncher: Attempting GRUB Boot
L4TLauncher: Attempting Direct Boot
EFI stub: Booting Linux Kernel…
EFI stub: ERROR: Invalid header detected on UEFI supplied FDT, ignoring …
EFI stub: Generating empty DTB
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services…

All serial port logs:
all log.txt (225.4 KB)

The dts works fine in 35.2.1 and Orin can boot before porting, so I suspect the problem may lie in some new features of 36.3 that I am not aware of。

flash command:
sudo ./flash.sh jetson-agx-orin-devkit internal
(jetson-agx-orin-devkit has no any modifications)

Please help check the DTS and logs,Any advices would be appreciated. Thanks

hello solo_wh,

here’s failure reported, it seems your root file system has corrupted.

as you may know… JP-5’s kernel version 5.10 is replaced by kernel version 5.15 in JP-6.
hence… please refer to Camera Driver Porting to examine your sensor driver,
besides, you may see-also r36.3 release note for [4.2. Device Registration] section, it’s now using a device tree overlay to register the camera module.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.