R36.4.3 l4t_initrd_flash.sh error

Use ORIN 32G,


See README_initrd_flash

Workflow 7: Initrd Massflash
First, generate massflash package

BOARDID=3701 BOARDSKU=0004 FAB=500 BOARDREV=L.0 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 5 --network usb0 jetson-agx-orin-devkit mmcblk0p1

Second,
Put the device in recovery mode again

Run this command:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --flash-only --massflash 5 --network usb0


Use R35.5.0 is OK

R3550_flash_1-11_0_20250909-164114.log (39.0 KB)

Use R36.4.3 is ERROR , show

Waiting for target to boot-up…
Timeout

R3643_202509041_beta_err.log (9.5 KB)

Are the processes for the two SDKs different? Why are the results different?

Hi,

Please retrive the serial log during flashing to debug further.

NVIDIA Jetson Orin AGX - In Board - Getting in Board - Serial Console

Thanks

R3643_202509041_flash_err_board_message.log (24.5 KB)
ORIN Board message
(Use ORIN 64G to re-run the backup and restore process)

Reference URL (R36.4.3 l4t_initrd_flash.sh --no-flash 烧录问题)
use chkbdinfo
BOARDID=3701
BOARDSKU=0005
FAB=501
BOARDREV=G.0
CHIP_SKU=00:00:00:D0
RAMCODE_ID=00:00:00:03
RAMCODE=3

Is this still an issue to support? Any result can be shared?

Hi,

Please try flashing commands without BOARDREV

Just use below

BOARDID=3701
BOARDSKU=0005
FAB=501

Or put the device in recovery mode and do online massflash.

Thanks

The configuration in p3701.conf.common contains an error, using the outdated version 35.5.0 instead of 36.4.3, pending recompilation and testing.

flash_1-6_0_20250925-152301.log (17.9 KB)

0925_RCM_term_ERR.log (43.7 KB)

use command:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only jetson-agx-orin-devkit mmcblkp01

Still failed

Hi,

We noticed some typos in your commands.

Please replace mmcblkp01 with mmcblk0p1 or internal, as instructed in README_initrd_flash.txt.

Thanks

Use CMD

./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-agx-orin-devkit internal
./tools/kernel_flash/l4t_initrd_flash.sh --flash-only jetson-agx-orin-devkit internal
Find error message …
No known UDC device found

flash-only-oem-cmd-err.log (10.8 KB)

flash-only-oem-tty-err.log (61.3 KB)

I found similar questions

Use flash command is ok:

./flash.sh jetson-agx-orin-devkit internal

flash-oem-cmd-ok.log (105.2 KB)

flash-oem-tty-ok.log (110.4 KB)

There is a difference between the flashing USB port of my board and the EVK.
my board flashing USB port(USB 2.0_0) directly connected to USB type C ..

so dts disable CYPRESS_CCG_EN

tegra234-p3737-0000+p3701-0000.zip (2.8 KB)

Is this still an issue to support? Any result can be shared?

The problem still exists…dts has also been modified accordingly USB changes but the problem still exists

Hi,

Please share your original DTS file along with the diff for our review.
Also, try running the following command to verify if the l4t_initrd_flash tool is functioning correctly:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh jetson-agx-orin-devkit mmcblk0p1

Thank you.

1103_runtime_full.dts.txt (335.1 KB)

usb2-0_tty_devices.txt (74.7 KB)

usb2-0_cmd_devices.txt (249.7 KB)

Which Ubuntu OS version on you host machine?

“Ubuntu 22.04.5 LTS”

Hi,

The “UDC not found” error indicates that USB device mode is not activated.
What differences exist between your USB hardware and our developer kit?
Also, did you follow our adaptation guide to modify your configuration?

Thanks

主要新增這個設定 就可以直接轉為usb2.0 device

usb2-0 {

  mode = "peripheral";

  vbus-supply = <&vdd_5v0_sys>;

  status = "okay";

  usb-role-switch;

  role-switch-default-mode = "peripheral";

};

use command:

sudo ./flash.sh jetson-agx-orin-devkit internal

燒錄OK

燒錄成功後
插拔燒錄USB線 顯示

# dmesg -c

[2435069.741137] usb 1-4: USB disconnect, device number 79

[2435069.741910] rndis_host 1-4:1.0 enxca01b8df4340: unregister ‘rndis_host’ usb-0000:00:14.0-4, RNDIS device

[2435069.801503] cdc_ncm 1-4:1.5 enxca01b8df4342: unregister ‘cdc_ncm’ usb-0000:00:14.0-4, CDC NCM (NO ZLP)

[2435071.482493] usb 1-4: new high-speed USB device number 80 using xhci_hcd

[2435071.609617] usb 1-4: New USB device found, idVendor=0955, idProduct=7020, bcdDevice= 0.02

[2435071.609636] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[2435071.609645] usb 1-4: Product: Linux for Tegra

[2435071.609652] usb 1-4: Manufacturer: NVIDIA

[2435071.609658] usb 1-4: SerialNumber: 1422125066918

[2435071.616301] rndis_host 1-4:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-4, RNDIS device, ca:01:b8:df:43:40

[2435071.618271] cdc_acm 1-4:1.2: ttyACM0: USB ACM device

[2435071.619968] usb-storage 1-4:1.4: USB Mass Storage device detected

[2435071.620453] scsi host6: usb-storage 1-4:1.4

[2435071.644535] cdc_ncm 1-4:1.5: MAC-Address: ca:01:b8:df:43:42

[2435071.645086] cdc_ncm 1-4:1.5 usb1: register ‘cdc_ncm’ at usb-0000:00:14.0-4, CDC NCM (NO ZLP), ca:01:b8:df:43:42

[2435071.659403] cdc_ncm 1-4:1.5 enxca01b8df4342: renamed from usb1

[2435071.665409] rndis_host 1-4:1.0 enxca01b8df4340: renamed from usb0

[2435072.636297] scsi 6:0:0:0: Direct-Access     Linux    File-Stor Gadget 0515 PQ: 0 ANSI: 2

[2435072.637133] sd 6:0:0:0: Attached scsi generic sg2 type 0

[2435072.637354] sd 6:0:0:0: Power-on or device reset occurred

[2435072.637874] sd 6:0:0:0: [sdc] 32768 512-byte logical blocks: (16.8 MB/16.0 MiB)

[2435072.638023] sd 6:0:0:0: [sdc] Write Protect is on

[2435072.638032] sd 6:0:0:0: [sdc] Mode Sense: 0f 00 80 00

[2435072.638208] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA

[2435072.641033]  sdc:

[2435072.641335] sd 6:0:0:0: [sdc] Attached SCSI removable disk

——-

root@iei-Z370P-D3:/home/iei# ip addr show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host

   valid_lft forever preferred_lft forever

2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

link/ether e0:d5:5e:43:24:20 brd ff:ff:ff:ff:ff:ff

inet 10.10.50.46/23 brd 10.10.51.255 scope global dynamic noprefixroute enp6s0

   valid_lft 1192727sec preferred_lft 1192727sec

inet6 fe80::2e8:309b:2dc0:5f7c/64 scope link noprefixroute

   valid_lft forever preferred_lft forever

3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

link/ether 4e:bf:b2:41:f6:64 brd ff:ff:ff:ff:ff:ff

inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

   valid_lft forever preferred_lft forever

65: enxca01b8df4340: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000

link/ether ca:01:b8:df:43:40 brd ff:ff:ff:ff:ff:ff

inet 192.168.55.100/24 brd 192.168.55.255 scope global dynamic noprefixroute enxca01b8df4340

   valid_lft 13sec preferred_lft 13sec

inet6 fe80::a0ba:7e41:f1b9:f86a/64 scope link noprefixroute

   valid_lft forever preferred_lft forever

66: enxca01b8df4342: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

link/ether ca:01:b8:df:43:42 brd ff:ff:ff:ff:ff:ff

inet6 fe80::7078:4c62:1c96:6949/64 scope link noprefixroute

   valid_lft forever preferred_lft forever

使用 l4t_initrd_flash 燒錄 LOG 1215l4t_initrd_flash_flashonly.txt
./tools/kernel_flash/l4t_initrd_flash.sh --flash-only jetson-agx-orin-devkit mmcblk0p1

顯示錯誤

Formatting APP parition done

Formatting APP partition /dev/mmcblk0p1 …

tar --checkpoint-action=“ttyout=Hit %s checkpoint #%u%*\r” -x -I ‘zstd -T0’ -pf /mnt/internal/system.img  --warning=no-timestamp --numeric-owner --xattrs --xattrs-include=*  -C  /tmp/ci-uGtm0cRJRV

writing item=78, 1:3:secondary_gpt, 61203267072, 16896, gpt_secondary_1_3.bin, 16896, fixed–0, 3ccddddb468ecc830ac193341ca075bdd798771f

[ 214]: l4t_flash_from_kernel: Successfully flash the emmc

[ 214]: l4t_flash_from_kernel: The device size indicated in the partition layout xml is smaller than the actual size. This utility will try to fix the GPT.

[ 214]: l4t_flash_from_kernel: Error flashing qspi

Flash failure

Either the device cannot mount the NFS server on the host or a flash command has failed. Check your network setting (VPN, firewall,…) to make sure the device can mount NFS server. Debug log saved to /tmp/tmp.lqabRl7eiZ. You can access the target’s terminal through “sshpass -p root ssh root@fc00:1:1:0::2”

Cleaning up…

確認usb0裝置

[2438811.676237] NFSD: Using nfsdcld client tracking operations.

[2438811.676247] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)

[2438812.468114] NFSD: Using nfsdcld client tracking operations.

[2438812.468124] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)

[2438821.210563] usb 1-4: USB disconnect, device number 86

[2438834.383051] usb 1-4: new high-speed USB device number 87 using xhci_hcd

[2438834.514818] usb 1-4: New USB device found, idVendor=0955, idProduct=7035, bcdDevice= 0.01

[2438834.514822] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[2438834.514824] usb 1-4: Product: Linux for Tegra

[2438834.514825] usb 1-4: Manufacturer: NVIDIA

[2438834.514826] usb 1-4: SerialNumber: 1422125066918

[2438834.517541] rndis_host 1-4:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-4, RNDIS device, 56:fa:6e:52:cb:c1

[2438834.542515] rndis_host 1-4:1.0 enx56fa6e52cbc1: renamed from usb0
# ip addr show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host

   valid_lft forever preferred_lft forever

2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

link/ether e0:d5:5e:43:24:20 brd ff:ff:ff:ff:ff:ff

inet 10.10.50.46/23 brd 10.10.51.255 scope global dynamic noprefixroute enp6s0

   valid_lft 1189327sec preferred_lft 1189327sec

inet6 fe80::2e8:309b:2dc0:5f7c/64 scope link noprefixroute

   valid_lft forever preferred_lft forever

3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

link/ether 4e:bf:b2:41:f6:64 brd ff:ff:ff:ff:ff:ff

inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

   valid_lft forever preferred_lft forever

67: enx56fa6e52cbc1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000

link/ether 56:fa:6e:52:cb:c1 brd ff:ff:ff:ff:ff:ff

inet6 fc00:1:1::1/64 scope global

   valid_lft forever preferred_lft forever

inet6 fe80::54fa:6eff:fe52:cbc1/64 scope link

   valid_lft forever preferred_lft forever

inet6 fe80::2/64 scope link

   valid_lft forever preferred_lft forever

確認最基本的連通性:使用 ping6 測試 : 可以連線

# ping6 fc00:1:1:0::2

PING fc00:1:1:0::2(fc00:1:1::2) 56 data bytes

64 bytes from fc00:1:1::2: icmp_seq=1 ttl=64 time=0.299 ms

64 bytes from fc00:1:1::2: icmp_seq=2 ttl=64 time=0.349 ms

64 bytes from fc00:1:1::2: icmp_seq=3 ttl=64 time=0.355 ms

64 bytes from fc00:1:1::2: icmp_seq=4 ttl=64 time=0.320 ms

^C

-– fc00:1:1:0::2 ping statistics —

4 packets transmitted, 4 received, 0% packet loss, time 3049ms

rtt min/avg/max/mdev = 0.299/0.330/0.355/0.022 ms

改用SSH指令 指定IP為不壓縮的完整形式 連接:可以連到ORIN

# ssh root@fc00:0001:0001:0000:0000:0000:0000:0002

The authenticity of host ‘fc00:1:1::2 (fc00:1:1::2)’ can’t be established.

ED25519 key fingerprint is SHA256:kaPwbA4ELCm+EgzZARfRRp5pUG/vdheLDQzx9LStsN8.

This key is not known by any other names

Are you sure you want to continue connecting (yes/no/[fingerprint])? yes

Warning: Permanently added ‘fc00:1:1::2’ (ED25519) to the list of known hosts.


root@fc00:1:1::2’s password:

-bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

-bash-5.1#

-bash-5.1# exit

logout

Connection to fc00:1:1::2 closed.

重新用 sshpass -p root ssh root@fc00:1:1:0::2 可連線成功

# sshpass -p root ssh root@fc00:1:1:0::2

-bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

-bash-5.1#

-bash-5.1# exit

logout

Connection to fc00:1:1::2 closed.

再次執行 ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only jetson-agx-orin-devkit mmcblk0p1 燒錄
還是失敗
但確認 sshpass -p root ssh root@fc00:1:1:0::2 是可以連線的

確認HOST PC是否有問題
使用 sdkmanager 版本 JetPack_6.2.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra

測試指令
sudo ./tools/kernel_flash/l4t_initrd_flash.sh jetson-agx-orin-devkit mmcblk0p1
是可以正常燒錄

I think you should be using flash.sh script for flashing onboard eMMC. Use l4t_initrd_flash.sh to flash external NVMe. just check on this.

Regarding USB timeout error, might be USB cable issue some times…

I think you should be using flash.sh script for flashing onboard eMMC. Use l4t_initrd_flash.sh to flash external NVMe. just check on this.

flash.sh and l4t_initrd_flash.sh can both flash eMMC and NVMe, right?