- 1 BSP environment:
jetpack 5.0.2 L4T R35.1 kernel 5.10 aarch64
agx orin 32g - 2 Background:
on custom board
recompile dtbs
add the /boot/dtb/kernel_tegra235-p3701-0004-p3737-0000.dtb to extlinux.conf, but it does not work.
but the /boot/Image works well. - 3 Problems:
root@tegra:/home/nvidia# cat /etc/nv_tegra_release
# R35 (release), REVISION: 1.0, GCID: 31250864, BOARD: t186ref, EABI: aarch64, DATE: Thu Aug 11 03:40:29 UTC 2022
nvidia@tegra:/boot$ cat extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
FDT /boot/dtb/kernel_tegra234-p3701-0004-p3737-0000.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 console=tty0 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
LABEL backup
#LABEL primary
MENU LABEL backup kernel
LINUX /boot/Image.b
FDT /boot/dtb/kernel_tegra235-p3701-0004-p3737-0000.dtb.b
INITRD /boot/initrd
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 console=tty0 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# FDT /boot/dtb/kernel_tegra234-p3701-0004-p3737-0000.dtb
# INITRD /boot/initrd
# APPEND ${cbootargs}
FYI
dmesg:
d.log (95.4 KB)