I have a jetson nano developer kit model P3450 and 2 validated SD cards. One is flashed with jetpack 4.4, the other one has jetpack 4.6.1.
The nano boots fine with the jetpack 4.4 image but doesn’t boot with the 4.6.1 image.
I reflashed the nano using the Nvidia SDK manager ( jetpack 4.6.1 and 4.6.2) and it still doesn’t boot. Jetpack 4.4 still boots without any error.
How can I make the device boot on jetpack 4.6.1?
Thank you,
The serial logs are the following:
34484232 bytes read in 2920 ms (11.3 MiB/s)
append: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb
## Flattened Device Tree blob at 83100000
Booting using the fdt blob at 0x83100000
ERROR: reserving fdt memory region failed (addr=0 size=0)
ERROR: reserving fdt memory region failed (addr=0 size=0)
Using Device Tree in place at 0000000083100000, end 000000008317ced3
copying carveout for /host1x@50000000/dc@54200000...
copying carveout for /host1x@50000000/dc@54240000...
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.253-tegra (buildbrain@mobile-u64-5434-d8000) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0e2
[ 0.000000] Boot CPU: AArch64 Processor [411fd071]
[ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 32,
[ 0.000000] OF: fdt: - 80000000 , 7ee00000
[ 0.000000] OF: fdt: - 100000000 , 7f200000
[ 0.000000] Found tegra_fbmem: 00800000@92ca9000
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options '')
[ 0.000000] bootconsole [uart8250] enabled
[ 1.160917] tegradc tegradc.1: dpd enable lookup fail:-19
[ 1.340059] imx219 7-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.340127] imx219 7-0010: board setup failed
[ 1.364018] imx219 8-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.364110] imx219 8-0010: board setup failed
Thank you for your response, you’ll see the full logs in the text file attached.
Jetpack 4.4 is not available in the SDK manager. Is there a way to make it available?
Do you have a monitor or something else connected on the board?
Could we clarify does “pcie_aspm=off” or the "root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 " that makes your device “bootable”?
yes, i have a screen connected to the board for the debugging.
The extlinux.conf with pcie_aspm=off make the device boot ok on jetpack 4.4 but not on jetpack 4.6
Hi, thank you for your response. Let me rephrase then,
The device boots ok on jetpack 4.6 with this extlinux conf:
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet
The device does boot on jetpack 4.4 but not with jetpack 4.6 with the following extlinux conf:
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet pcie_aspm=off
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
I am open to putting any configuration, what would be your recommendation?
I am assuming that this file is stored in the Nano and not on the SD card, is that correct?
I have the following devices connected: keyboard, mouse, and desktop for the debugging and a zed camera and a google TPU the rest of the time.
Before replying any of your question, I just hope to clarify it more clearly…
Your comment
The device boots ok on jetpack 4.6 with this extlinux conf:
Ok. Looks good.
The device does boot on jetpack 4.4 but not with jetpack 4.6 with the following extlinux conf:
Ok, so which one is causing jp4.6 failure here? The pcie aspm or the whole cmd after “quiet”. Which one is causing the boot failure here?
If you just added “pcie_aspm=off” to your jp4.6 “fine configuration”, then it will fail to boot too? Is that what you want to say?