JetPack 4.64/L4t 32.7.4 Jetson xavier NX

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
,
1

Hi

I have a custom board based on DevKit p3668/p53509.I have to customize the L4T to support lontium lt6911uxc csi driver and dts,I already customised the same lt6911uxc driver and dts at jetson nano and it works.Now , I did the customise at platform jakku.I rebuild the kernel with the driver and also update the dts files.
Before changing the changes I flashed withn SDKManager the JetPack 4.6.4[l4T 32.7.4] and it boot ok and I also got the ubuntu screen well.
While I loaded the Image and dtb/dtbo I encounter failure with exception.I have a log file of the printing to console.
I see the following issues:

I see problems with Validating kernel and dtb, but it seems validation failed because the .sig not replaced.Anyway it print that it ignored.
I see that it failed to load ramdisk initrd.
The problem is that I changed extlinux.conf and editing with vi entered error in the name of initrd to /boot/initrD with cap letter D instead of initrd…
Here is a snapshot from the log (log is attached) at Line number 8750
I> Loading ramdisk from rootfs …
[0019.145] I> Loading ramdisk binary from rootfs …
[0019.150] I> rootfs path: /sdmmc_user/boot/initrD
This caused exception and panic with
[0019.343]HALT: spinning forever…
I want to ask how to recover from this situation that kernal is stuck due to error in extlinux.cont ?
I want to avoid flash from the SDKManger of the whole long process and build the customization again…
Is there a way to use recovery mode and flash just extlinuxconf or just the dtb and kernel? I have jetson with eMMC.

I attached the log
XAVIER_FAILED_ON_BOOT_DTB_AUTHENTIC.txt (406.8 KB)

Regards

Yehuda

3

Does the extlinux.conf have backup entry?

4

Hi
No.
The extlinux is as originally supplied at the jetpack 4.6.4 which the backup label is in comment.
I thought to use the flash script from sdkmanager in ~/nvidia/nvidia_sdk/jetpack_4.6.4_Linux_JETSON_XAVIER_NX_TARGETS/
Can the flash script flash the original file system and image and may resolve the extlinux wrong line
of initrD instead initrd?
regards
yehuda

5

Maybe try to backup the system image and reflash the device then to restore it.

7

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