Flash failure when flashing to multiple Jetson devices

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hi,
I am trying to flash my custom BSP(based on Jetson Linux 35.5.0) to two identical custom boards(based on Xavier NX) at the same time by using the method in the developer guide:Flashing to Multiple Jetson Devices. Now assume that the name of my custom board is “custom_board”.
1.Run the following command:

sudo BOARDID=3668 FAB=301 BOARDSKU=0001 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --network usb0 -massflash 5 custom_board mmcblk0p1

2.Connect the two custom Jetson devices to the flashing hosts(Ubuntu18.04).
3.Ensure that the two custom devices have the identical hardware revision.
I have checked the /etc/nv_boot_control.conf on the two custom boards and they are completely identical:

TNSPEC 3668-301-0001-G.0-1-2-custom_board-
COMPATIBLE_SPEC 3668-301---1--custom_board-
TEGRA_LEGACY_UPDATE false
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

4.Place all of the connected Jetson devices into RCM mode.
5.Run the following command:

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

However, the two boards got stuck in the same error.
board1:

......
Waiting for target to boot-up...
Unknown device, absolute path in /dev/ or /sys expected.
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
...RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
mount: /mnt/proc: mount point does not exist.
Flash failure
Cleaning up...

board2:

......
Waiting for target to boot-up...
Unknown device, absolute path in /dev/ or /sys expected.
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
...RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:1::2
SSH ready
mount: /mnt/proc: mount point does not exist.
Flash failure
Cleaning up...

How can I solve this problem? Thanks very much.

3

Hi qian.yuan,

Have you tried using initrd to flash one board independantly?

Could you use --massflash 2 in your case?

Please also share the full flash log as file here for further check.

4

board 1 full flash log:
flash_1-10_0_20241101-161959.log (9.6 KB)
board 2 full flash log:
flash_1-1_1_20241101-161959.log (9.6 KB)

Yes, I have tried using initrd to flash one board independantly.
When I use this command, the board can be flashed successfully:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh custom_board mmcblk0p1

But when I use the following command, I encountered the same error:

sudo BOARDID=3668 FAB=301 BOARDSKU=0001 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --network usb0 -massflash 5 custom_board mmcblk0p1
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 1

And this is the full flash log:
flash_1-10_0_20241104-143203.log (9.5 KB)

After using --massflash 2, I still encountered the same error.

5

Please share the full flash log when you use initrd script to flash the board successfully.

I would also like to check the log when you run this command to generate mass flash package.

6

flash_one_board_independently_1-10_0_20241104-140211.log (42.0 KB)

MobaXterm_10.5.82.30_20241106_154938 (copy).log (11.4 MB)

7 
SSH ready
mount: /mnt/proc: mount point does not exist.
Flash failure
Cleaning up...

When you are using mfi package to flash the board, the mount point can not be found.

I can not find any helpful message in current log.

Could you reproduce the similar issue on the devkit?
Or have you also verified with the latest JP5.1.4(R35.6.0)?

8

After reading some scripts related to l4t_initrd_flash.sh, I rechecked my customized BSP and customized rootfs, and found that three folders were missing in my customized rootfs: /proc, /sys, /dev. Therefore, I added these three folders to my rootfs, and the problem was solved.
Thank you all the same. Really appreciate your support.

9

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