R36.4.3 l4t_initrd_flash.sh error

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

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?

5

Hi,

Please retrive the serial log during flashing to debug further.

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

Thanks

6

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

7

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

8

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

9

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

10

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.

11

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

12

Hi,

We noticed some typos in your commands.

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

Thanks

13

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)

14

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

15

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

17

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.

18

1103_runtime_full.dts.txt (335.1 KB)

usb2-0_tty_devices.txt (74.7 KB)

usb2-0_cmd_devices.txt (249.7 KB)