Cannot flash image to SSD

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

Hi There,

I am using L4T 36.3
I have a Jetson Orin Nano custom board with HDMI output and no EEPROM.

This is the file of nano.conf

source “${LDK_DIR}/p3768-0000-p3767-0000-a0.conf”

PINMUX_CONFIG=“tegra234-nano-pinmux-p3767-hdmi.dtsi”;
PMC_CONFIG=“tegra234-nano-padvoltage-p3767-hdmi.dtsi”;

EMMC_CFG=“flash_t234_qspi_nvme.xml”;
ODMDATA=“gbe-uphy-config-9,hsstp-lane-map-3,hsio-uphy-config-0”;

if [ “${UPHYLANE}” = “c7x1” ]; then
      UPHYLANE_CONFIG=“tegra234-mb1-bct-uphylane-si-c7x1.dtsi”;
      EMMC_CFG=“flash_t234_qspi_nvme_c7.xml”;
elif [ “${UPHYLANE}” = “c7x2” ]; then
      UPHYLANE_CONFIG=“tegra234-mb1-bct-uphylane-si-c7x2.dtsi”;
      EMMC_CFG=“flash_t234_qspi_nvme_c7.xml”;
fi

I use the following command to flash images to the SSD.

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p "-c ./bootloade
r/generic/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 nano nvme0n1p1

It is unable to write image to the SSD.
After flashing the system boot up with initrd.

bash-5.1# cat /proc/cmdline
root=/dev/initrd rw rootwait mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 bl_pr
of_dataptr=2031616@0x271E10000 bl_prof_ro_ptr=65536@0x271E00000

But if I use the following command, it can flash image to the SSD successfully.
Then the system boot up with rootfs on the SSD.

sudo ./flash.sh nano internal

root@nano:~# cat /proc/cmdline
root=PARTUUID=e92dad79-2264-455d-913f-fc3776eac9c6 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 bl_prof_dataptr=2031616@0x271E10000 bl_prof_ro_ptr=65536@0x271E00000

How to flash image to SSD with l4t_initrd_flash.sh?
Thanks.
flash.log (270.0 KB)

2

Device failed to boot to the initrd flash kernel. Please retrive the serial log during flashing to debug further.

Get the log as requested.

3

Here you are.
serial.log (124.1 KB)

4

Check your USB schematic first.
tegra-xudc driver is not up so it fails to create SSH connection over RNDIS and hence times out.

5

I can flash successfully with following command.

$ sudo ./flash.sh nano internal

Is this doesn’t means USB hardware is OK？

6

flash.sh does not care anything about your hardware design at all…
Saying flash.sh works helps nothing in identifying the root cause.

7

Hi Dave,
The flashing of the USB schematic is copied from the Orin Nano dev kit.
After flashing，I can see the usb0 ethernet interface on the custom board
and nothing happens on the host (Ubuntu 22.04) but Waiting for target to boot-up... timeout.

Could you give me some hints or documents on how to debug?
Thanks a lot.

8

https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html#porting-universal-serial-bus

You should also check the serial console log during flashing.

This helps nothing.

9

What are requirements for flashing on a host PC?
E.g. NFS server? DHCP server?

10

RNDIS, for establishing SSH connection, and NFS server, for mounting file systems, are required.

11

I can use L4T 35.5 to flash with initrd successfully but L4T 36.3.
Could you check it for me? Thanks.

12

Please do this.

13

What is your dmesg after your “boot up” case with usb0 appeared?

I guess this is just another “actually your board is not copy orin nano devkit” case which we have seen a lot from other users…

You don’t need to dump rel-35.5 cases. They do not matter. Just dump your rel-36.3 boot up case with your so-called “usb0” appeared case log out.

14

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