Jetson Nano not starting

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

Hi,
i have made a simple Carrier board with minimal connections, the same module can’t start on my carrier board, but it’s working on Dev Kit, it’s broken when starting kernel :

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
224 bytes read in 100 ms (2 KiB/s)
1:	Poky (Yocto Project Rgference Distro)
Retrieving file: /boot/extlinux/../initrd
1970569 bytes read in 211 ms (8.9 MiB/s)
Retrieving file: /boot/extlinux/../Image
34117640 bytes read in 1622 ms (20.1 MiB/s)
append: tegraid=21.1.2.0.0$ddr_die=4096M@2048M section=512M memtype=0 vpr_resiz} 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,1152p0n8 debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000`maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 tegra_fbmem=0x140000@0x92cb7000 is_hdmi_initialised=1  console=ttyS0,115200 console=tty0 fbcon=map:0 net.ifnames=0 root=/dev/mmcblk�p1 rw rootwait  
## Flattened Device Tree blob at 83100000
   Booting using the fdt blob at 0x83100000
   reserving fdt memory region: addr=80000000 size=20000
   Using Device Tree in place at 0000000083100000, end 00000000831778ef

Starting kernel ...

<hit enter to activate fiq debugger>

i dont know if i miss something on my carrier board, any idea?

Thanks

2

I would have to wonder if the initrd was actually valid, but the “APPEND” of your extlinux.conf has another issue, as shown above. It should be “mmcblk0p1”, but the “0” has some alternate character showing up. Maybe this is just some artifact of logging or posting in the forum, but it seems that extlinux.conf was found and read, and this is very likely on eMMC (assuming you don’t have an SD card inserted). After this it just stops, as if either the kernel did not load, or else as if the root filesystem is not found. The original kernel comes from an initrd it seems, but the final rootfs is from the extlinux.conf APPEND entry. Can you check if your extlinux.conf APPEND actually has a “0” for “mmcblk0p1”, or if this character is something else, perhaps from some odd character set? I could see the possibility that editing this from a non-en_US character set could have placed something only resembling a “0” in its place.

3

Hi,
root=/dev/mmcblk�p1
it’s only serial debugging which not connect to GND. i think that i found the issue and it’s linked to HDMI, so i disabled hdmi form DTC and now i can start the kernel.

Thanks again for you response.