Why jetson nano can't power on while adding FDT in /boot/extlinux/extlinux.conf?

Autonomous Machines Jetson & Embedded Systems Jetson Nano
,
1

dear sirs:
There is a puzzling issue，please help me.

only add FDT cmd to /boot/extlinux/extlinux.conf in SSD disk, the jetson nano can’t power on successfully.
but delete the FDT cmd，the system power on successfully.

the modify info is following:

TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
FDT /boot/tegra210-p3448-0000-p3449-0000-b00.dtb
INITRD /boot/initrd
#FDT /boot/tegra210-p3448-0000-p3449-0000-b00.dtb
APPEND ${cbootargs} quiet root=/dev/sda1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 loglevel=3

the SDK version is R32.5.1

Does anyone have the same problem as me? Hope to get your help，tks

3
4

the board is NVIDIA Development kits jetson nano（tegra210-p3448-0000-p3449-0000-b00）
and the system is Ubuntu 18.04.5 LTS (GNU/Linux 4.9.201-tegra aarch64 while downloading the url（https://developer.nvidia.com/jetson-nano-sd-card-image）

and only used SSD disk

5

The purpose I posted that link is to ask you dump the boot log.

6

dear WayneWWW：
I am glad to get your reply in time.thank you.
I am a new user to develop jetson nano platform and can’t open uboot and kernel log through serial port. I find no log out from uart port(pin8 & pin9).
but there are much info out from LCD screen.
the log crash that ERROR:mmcblk0p1 not found (I power on SSD disk,it need to /sda1 ，not mmcblk0pi in sdcard )

微信图片_20210819145334
微信图片_202108191453341920×1440 248 KB

7

I guess it is just setup problem. It is not possible that the uart is not able to dump log while monitor side can.

The picture you shared here only tells us that the kernel is trying to mount the file system from your sd but not the ssd. It finds nothing and then crashed.

However, the reason behind this is unknown. Only the Uart console can tell.

8

dear WayneWWW:
Yes，I find the real uart port under the core board.

I only add FDT cmd to load /boot/tegra210-p3448-0000-p3449-0000-b00.dtb，when I delete FDT cmd，the jetson nano can power on successfully.
the whole log is attached，please help to check it.
serial_2021-08-19_15_46_55.log (155.3 KB)

9

Can you also share the content of your dtb?

Your log has the “/dev/sda1” in the beginning. But later it got disappeared and it is mmcblk0p1 again.

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 no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 gpt tegra_fbmem=0x800000@0x92ca9000 is_hdmi_initialised=1 earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet root=/dev/sda1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0

[ 0.000000] Kernel command line: 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 no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 gpt tegra_fbmem=0x800000@0x92ca9000 is_hdmi_initialised=1 earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0

10

dear WayneWWW：
thank your reply. the attached files are DTB and extLinux.conf.

tegra210-p3448-0000-p3449-0000-b00.dtb (239.5 KB)
extlinux.conf (895 Bytes)

11

The dtb seems no problem. Not sure why the kernel command line gets overwritten.

Can you give me a log that does not put FDT in your extlinux.conf? Thanks.

12

Hmm. It looks like duplicated with this topic.

It is a uboot bug. Should be fixed on rel-32.6.1. Can you move to 32.6.1?

13

dear WayneWWW:
ok，I will download the laest verson 32.6.1 to try this issue. If there is a result, I will tell you in time.

thanks!

14

dear WayneWWW:
Can you help to confirm the latest img (https://developer.download.nvidia.cn/embedded/L4T/r32_Release_v6.1/Jeston_Nano/jetson-nano-jp46-sd-card-image.zip) includes this fix patch in uboot?
If included,I will download this img to verify this issue.

tks

15

Yes, I see the patch is merged.

16

dear WayneWWW:
I use the laest img,there is the same issue.and I change the uboot cbootargs to /boot/sda1,but the kernel alse use /dev/mmcblk0p1.

tksserial_2021-08-20_9_21_53.log (153.1 KB)

17

It is weird.

Can you help me do a test that

  1. Using pure sdcard (no ssd connected)

  2. Again, set a FDT inside your extlinux.conf over your sdcard to let it load the device tree from file system.

  3. Add a arbitrary string to the kernel command line. For example, add “test”.

  4. Reboot the device and share the serial log.

Not sure if external ssd is the problem here.

18

dear WayneWWW:
the log in sdcard is attached,the extlinux.conf add testsdcard in append cbootargs，but the kernel cmd line is not this string.
sdcard-dft.log (156.8 KB)

extlinux
extlinux927×569 20.8 KB

19

Thanks for test. We will check.

21

thanks，If you have any news, please tell me ASAP.

22

Hi,

I tried on my emmc and sdcard jetson nano. But both of them can see the new kernel command line I added in extlinux.conf.

Can you flash your sdcard with sdkmanager again to make sure all the components on the board is updated to latest version?