Jetpack5.1.2 use A/B rootfs，UEFI（version 4.1-33958178 built on 2023-08-01T19:34:02+00:00） cannot enter the kernel

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

AGX orin adopts JETPACK5.1.2 and uses A/B rootfs to create images. After burning the image in AGX orin, there is an abnormal situation where UEFI is unable to boot the kernel during a soft reboot or hard reboot (power outage).
The basic information is as follows:

  1. Jetpack 5.1.2
  2. Jetson UEFI firmware (version 4.1-33958178 build on 2023-08-01T19:34:02+00:00)
  3. Starting with Direct Boot
  4. Scenario 1, stuck here and not moving
    image
  5. Scenario 2, stuck here and not moving
    image
    image874×90 4.26 KB

    URFI无法引导启动内核超时会有切换到备份根文件系统情况.txt (36.6 KB)
3

Hi 1712127445,

Are you using the devkit or custom board for AGX Orin?

Do you hit the boot issue in UEFI only with the rootfs a/b enabled?

How do you flash the board? Could your share the full flash log for further check?

4

1、use AGX orin custom device，but jetpack use 5.1.2.
2、Our requirement is to use an A/B file system, so it is unknown whether this fault occurs in a single file system. The probability of this problem occurring when using the A/B root file system at the same time is low, and the probability is high only when adding disk, GPU, and CPU stress tests on the EMMC.
3、flash the board:
sudo BOARDID=3701 FAB=TS4 BOARDSKU=0000 BOARDREV=A.0 ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 32 jetson-agx-orin-devkit mmcblk0p1

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 1

flash logSee Attachment。
flash_3-2.2_0_20231117-153212.log (40.3 KB)

5

Could you try if you would hit the same issue if you use the folllowing command to flash the board?

$ sudo ./flash jetson-agx-orin-devkit mmcblk0p1

Since you boot failed at UEFI, I would suggest you could use the debug UEFI binary to get more messages in UEFI.
You could refer to the following instruction to build UEFI binary.
Build without docker · NVIDIA/edk2-nvidia Wiki · GitHub

6

After L4T 35.2.1, access and burning of QSPI Flash through modprobe mtdblock were restricted in rootfs. Debugging UEFI requires entering RCM and re burning, which increases debugging costs.
Is there any other way to access QSPI flash under rootfs in Jetpack 5.1.2
Mtd devices not visible with NVIDIA Jetson Linux 35.2.1 - Jetson & Embedded Systems / Jetson Xavier NX - NVIDIA Developer Forums

7

You could just use the following command to update UEFI binary only to prevent flash other partitions to reduce the time of debug.

$ sudo ./flash.sh -r -k A_cpu-bootloader jetson-agx-orin-devkit mmcblk0p1

As stated from the topic you shared, you could not access the QSPI flash from linux.

9

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