Jetson Nano L4T32.5.2 extlinux.conf APPEND does not work

Hello everyone,

Before adding FDT to extlinux.conf, everything is normal APPEND can work normally, but when I add FDT to extlinux.conf, APPEND does not work, even if I use the default dtb in the /boot directory, it does not work.

nano without FDT.txt (20.9 KB)
nano with boot FDT.txt (78.4 KB)

run cat /proc/cmdline:
without FDT:

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=1125 core_edp_ma=4000 gpt tegra_fbmem=0x140000@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/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:3 net.ifnames=0

with FDT:

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=1125 core_edp_ma=4000 gpt tegra_fbmem=0x140000@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 

You can see that the cmdline after adding FDT is missing the part added by extlinux.confg.

Any ideas?

please upgrade to latest release.

Added note: There are errors in your “added FDT” case:

DT property /chosen/nvidia,bluetooth-mac missing in source; can't copy
DT property /chosen/nvidia,wifi-mac missing in source; can't copy
DT property /psci/nvidia,system-lp0-disable missing in source; can't copy

This error does not exist in the case of “without” FDT. I am guessing the suggestion to upgrade would include a fix to device tree if an earlier release had a device tree issue. On the other hand, if you created the device tree, then perhaps there is an error somewhere in the edits to the default tree.

Thank you for your reply,
The system cannot be upgraded due to some reasons, can you tell me what caused this? Is there a solution?
By the way, I found that some Nanos can still work (same settings) even after modifying the FDT, and some can’t

Thank you for your reply,
Even if I use the default dtb in the /boot directory (in the SD image), it is the same problem.
Using the source code provided by Nvidia to compile, there is a problem even if it is not modified.

What did you add to your “APPEND” and get missed here?

Also, need to confirm that what is your method to install jetpack (l4t 32.5.2) to all these boards? I don’t think it would be “working for some and not work for the rest” would happen if they are same SKU of jetson nano.

In fact, I did not add anything extra, I just modified some parameters.
Default:

APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 

After edited:

APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:3 net.ifnames=0 

Just simply modify fbcon=map:0 to fbcon=map:3

As you can see from my previous post, once I added the FDT, all the parameters from the start of quiet to the end were not added to the cmdline correctly.

We use the SD Card Image installation system, all modules are official Jetson Nano development boards,
The ones that don’t work are brand new, and the working Nano is used for development. They have been flashed many times (using flash.sh or SDKManger). From the log, it seems that their bootloader versions are different. I’m not sure if this has any effect.

It is not possible that “bootloader versions are different” if you really flash your board correctly with sdkmanager.

That kind of problem should only happen with pure sdcard image. Thus, please make sure your boards are all got flashed by sdkm correctly first.

My purpose of upgrading the version is due to there were really some issues with FDT before. And they shall be resolved already.

Yes, this is exactly the point I want to express. The brand new nano is installed using pure SD Card Image, and the Nano used for development has been re-flashed, causing their versions to be different.
I will try to install them using SDKManger.
Thanks.

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