Devicetree entry does not boot properly in grub

[sean.pan]

System: Jetson Linux R36.4.3, Core board: jetson nano 4g.

When I configure grub as shown in the attachment, the system cannot boot normally, and the error message is as follows:

grub.zip (3.2 KB)

Could you tell me why this is?
Note: When I remove the devicetree entry, the system boots fine

[DavidDDD]

Hi,

How do you remove the devicetree entry?
Could you describe in detail (commands, file you modified)?

Thanks

[sean.pan]

@DavidDDD

Could you describe in detail (commands, file you modified)?

Yes, I just modify the /etc/grub.d/40_custom as follows:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Jetson Linux' {
        echo "Booting Jetson Linux..."
        linux   /boot/Image root=PARTUUID=${ACTIVE_ROOTFS_PARTUUID} rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 bl_prof_dataptr=2031616@0x171E10000 bl_prof_ro_ptr=65536@0x171E00000
        initrd  /boot/initrd
}
menuentry "System restart" {
        echo "System rebooting..."
        reboot
}

And then using commands to apply:

sudo su -c "grub-mkconfig > /boot/grub/grub.cfg"	
sudo su -c "update-grub"

After that, it can be work(because it use the default UEFI dtb, not mine dtb).

But if I modify /etc/grub.d/40_custom as follows:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Jetson Linux' {
    echo "Booting Jetson Linux..."
    linux   /boot/Image root=PARTUUID=${ACTIVE_ROOTFS_PARTUUID} rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 bl_prof_dataptr=2031616@0x171E10000 bl_prof_ro_ptr=65536@0x171E00000
    initrd  /boot/initrd
    devicetree  /boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb

}
menuentry "System restart" {
        echo "System rebooting..."
        reboot
}

it can not start normally, and the error shown in the figure above occurred.
Note: The /boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb file exists in the root file system and uses the same device tree file as the native file.

So I’m wondering how can I make it work properly if I use my own dtb?

[DavidDDD]

Hi,

Please add your own dtb in /boot/extlinux/extlinux.conf

Thanks

[sean.pan]

@DavidDDD

Please add your own dtb in /boot/extlinux/extlinux.conf

But I use grub instead of l4tlauncher, do I need to add FDT entries in extlinux.conf? Do I also need to add devicetree entries in the grub configuration file?

[WayneWWW]

maybe refer to this post first.

Jetpack 6.1 GRUB not booting

Do you mean that these 2 DTB files are the same? or the result in R36.4.3 is the same as in R36.4.0? I’ve verified that Grub working on my Orin Nano devkit+super board config with JP6.2. Currently, I boot from NVMe SSD and I didn’t add devicetree entry in grub.cfg. Please let me share my /boot/grub/grub.cfg and /etc/default/grub and /etc/grub.d/40_custom as following for your reference. grub.cfg (4.3 KB) grub (1.2 KB) 40_custom (750 Bytes) Why you want to specify this?

[sean.pan]

@WayneWWW

Do you mean that these 2 DTB files are the same? or the result in R36.4.3 is the same as in R36.4.0? I’ve verified that Grub working on my Orin Nano devkit+super board config with JP6.2. Currently, I boot from NVMe SSD and I didn’t add devicetree entry in grub.cfg. Please let me share my /boot/grub/grub.cfg and /etc/default/grub and /etc/grub.d/40_custom as following for your reference. grub.cfg (4.3 KB) grub (1.2 KB) 40_custom (750 Bytes) Why you want to specify this?

I refer this topic to set up my GRUB configuration file, but when I added the device tree entry, the system failed to boot. If I removed the device tree, it could boot normally.

[sean.pan]

@WayneWWW @DavidDDD Could you please help me find out why the devicetree configuration in grub cannot start normally? The device tree is /boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb

[KevinFFF]

@sean.pan

grub.zip (3.2 KB)

Your grub configurations look good to me.

@sean.pan

but when I added the device tree entry, the system failed to boot.

Could you share the full serial console log as file when it fails to boot?

@sean.pan

/boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb

Please also share this DTB from your board for further check.

[sean.pan]

@KevinFFF

Please also share this DTB from your board for further check.

The full serial console log as follows:
serial-console-log.txt (40.5 KB)
DTB in my board (kernel_tegra234-p3768-0000+p3767-0004-nv.dtb):
kernel_tegra234-p3768-0000+p3767-0004-nv.zip (37.9 KB)

[KevinFFF]

Could you try updating the following lines in /etc/grub.d/40_custom to check if it could help for your case?

menuentry 'Jetson Linux' {
    echo "Booting Jetson Linux..."
-    linux   /boot/Image root=PARTUUID=${ACTIVE_ROOTFS_PARTUUID} rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 bl_prof_dataptr=2031616@0x171E10000 bl_prof_ro_ptr=65536@0x171E00000
+    linux   /boot/Image root=PARTUUID=${ACTIVE_ROOTFS_PARTUUID} rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 bl_prof_dataptr=2031616@0x171E10000 bl_prof_ro_ptr=65536@0x171E00000 devicetree=/boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb
    initrd  /boot/initrd
-    devicetree  /boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb

}

[sean.pan]

@KevinFFF

Please also share this DTB from your board for further check.

@KevinFFF I tried to modify it and it did work, but the device tree still uses uefi’s instead of mine. Could you tell me why?

The serial output as follows:
serial-messages.txt (87.4 KB)

[KevinFFF]

Processing "Tegra234 p3768-0000+p3767-xxxx Dynamic Overlay" DTB overlay
Failed to apply device tree overlay. Error Code = -3
UpdatePcieControllersWithGpuDevice: failed to enumerate GPU device handles: Not Found
LocateChildGopHandle: failed to enumerate graphics output device handles: Not Found
fdt_check_header: Entry. FDT address: 258140000
fdt_check_header: Checking magic... Magic: 0xFFFFFFFF
fdt_check_header: Entry. FDT address: 258140000
fdt_check_header: Checking magic... Magic: 0xFFFFFFFF
EFI stub: Booting Linux Kernel...
EFI stub: ERROR: Invalid header detected on UEFI supplied FDT, ignoring ...
EFI stub: Generating empty DTB
EFI stub: Exiting boot services...
Link didn't transition to L2 state
Link didn't go to detect state as well
PROGRESS CODE: V03101019 I0 D6A2CB7F-6A18-4E2F-B43B-9920A733700A

From above log, it seems it has been passed to kernel.

[    0.000000] Unknown kernel command line parameters "BOOT_IMAGE=/boot/Image mminit_loglevel=4 bl_prof_dataptr=2031616@0x171E10000 bl_prof_ro_ptr=65536@0x171E00000 devicetree=/boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb", will be passed to user space.

But the kernel image can not recognize this devicetree option so that it skip to load the dtb.

I can reproduce the similar issue as yours.
I’ve also used debug UEFI binary to debug further.

fdt_check_header: Entry. FDT address: 258140000
fdt_check_header: Checking magic... Magic: 0xFFFFFFFF
fdt_check_header: Entry. FDT address: 258140000
fdt_check_header: Checking magic... Magic: 0xFFFFFFFF
EFI stub: Booting Linux Kernel...
EFI stub: ERROR: Invalid header detected on UEFI supplied FDT, ignoring ...
EFI stub: Generating empty DTB
EFI stub: Exiting boot services...
Link didn't transition to L2 state
Link didn't go to detect state as well
PROGRESS CODE: V03101019 I0 D6A2CB7F-6A18-4E2F-B43B-9920A733700A

The magic number is not expected, which may be caused from the compatibility issue for using grub on Jetson. If you want to load dtb from rootfs, we would suggest using L4TLauncher with FDT, OVERLAYS specified in extlinux.conf.

[sean.pan]

@KevinFFF

/Image mminit_loglevel=4 bl_prof_dataptr=2031616@0x171E10000 bl_prof_ro_ptr=65536@0x171E00000 devicetree=/boot/dtb/kernel_tegra234-p3768-0000+p3767-0004-nv.dtb", will be passed to user space.

But the kernel image can not recognize this devicetree option so t

@KevinFFF Thanks for your help. By the way, will this problem be fixed in subsequent versions of Jetson Linux BSP?

[KevinFFF]

Sorry that we don’t have the plan to update UEFI/Kernel to support this option currently.

[ritesh-kumar]

@sean.pan ,
you can try this, I am sure that it will work for you as well.

The system fails to boot with a custom DTB with Jetpack 5.1.4 & 6.2

Hi @KevinFFF, I’ve figured out the root cause of the issue — it originates from the Jetson UEFI firmware. When using a custom device tree and specifying it in the boot configuration file like this: devicetree /tegra234-p3768-0000+p3767-0005-nv.dtb the system correctly uses the specified DTB during boot. However, applying the overlay DTBOs fails with the following error: UpdateFdt: Applying overlays from firmware media. Processing "L4T Configuration Settings" DTB overlay Processing "Tegra2…

Thanks,
Ritesh