bootfromUSB not working after install Arducam driver

You can add it to same line after that “APPEND”. Those parameters shall appear in kernel cmdline…

Ahh… and your kernel cmdline is still being cut… not full one. I just checked my jetson nano…

This is full log.

[ 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
[ 0.022439] kmemleak: Kernel memory leak detector disabled

Again, this is yours…

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

How about you use other uart tool like picocom…?

not showing in cmdline.
this Nano maybe using other file.

If you remove that cboot args from file, will the cmdline change?

Nano_UsbBoot_13.txt (79.7 KB)
Nano_UsbBoot_14.txt (76.6 KB)
it is really full log i think.
cmdline is showing by sdcard, not usb.

Both your log have the correct cmdline now… I am not sure if you really read them before sending them out…

But that one from usb boot does not take effect even with UUID.

Could you remove the FDT line and let kernel read device tree from partition?

Nano_UsbBoot_15.txt (80.1 KB)
it works. thank you.
but, not recog camera. it maybe other problem.

I remember there was some issue similar to yours. Could you move to latest jetpack release? Your log indicate you are not using jeptack4.6.

Confirmed this issue should be resolved in rel-32.6.

Below uboot patch is for this issue.

diff --git a/include/configs/tegra186-common.h b/include/configs/tegra186-common.h
index dc6d360..0574e3d 100644
--- a/include/configs/tegra186-common.h
+++ b/include/configs/tegra186-common.h
@@ -62,7 +62,6 @@
 	"fdt_copy_prop_paths=" \
 		"/bpmp/carveout-start:" \
 		"/bpmp/carveout-size:" \
-		"/chosen/bootargs:" \
 		"/chosen/nvidia,bluetooth-mac:" \
 		"/chosen/nvidia,ether-mac:" \
 		"/chosen/nvidia,wifi-mac:" \
diff --git a/include/configs/tegra210-common.h b/include/configs/tegra210-common.h
index 0467231..dcd7685 100644
--- a/include/configs/tegra210-common.h
+++ b/include/configs/tegra210-common.h
@@ -69,7 +69,6 @@
 	"fdt_copy_prop_paths=" \
 		"/bpmp/carveout-start:" \
 		"/bpmp/carveout-size:" \
-		"/chosen/bootargs:" \
 		"/chosen/eks_info:" \
 		"/chosen/nvidia,bluetooth-mac:" \
 		"/chosen/nvidia,ethernet-mac:" \

Jetpack 4.6 maybe had some problems. i will retry then reply you.

After changing Jetpack 4.6, it can be boot.
Thank you.

1 Like

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