When burning multiple boards simultaneously, errors is reported

with JP5.1.2 ,sdk 35.4.1,AGX orin 32GB, i flash taget ,with “tools/kernel_flash/README_initrd_flash.txt”, the “Workflow 7” .
I did the following:
step 1 : I made image with “sudo BOARDID=3701 FAB=TS4 BOARDSKU=0004 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 5 --network usb0 jetson-agx-orin-devkit mmcblk0p1”
step 2: Put all of connected Jetsons into RCM mode.
step 3:cd mfi_jetson-agx-orin-devkit
step 4:“sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --flash-only --massflash 5 --network usb0”

but with error,
root@sensoro:/data2/R35.4.1/Linux_for_Tegra/mfi_jetson-agx-orin-devkit# sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --flash-only --massflash 5 --network usb0 /data2/R35.4.1/Linux_for_Tegra/mfi_jetson-agx-orin-devkit/tools/kernel_flash/l4t_initrd_flash_internal.sh --network usb0 --usb-instance 3-10.3 --device-instance 0 --flash-only --network usb0 jetson-agx-orin-devkit mmcblk0p1
Start flashing device: 3-10.3, rcm instance: 0, PID: 2222706
Log will be saved to Linux_for_Tegra/initrdlog/flash_3-10.3_0_20230808-161223.log
/data2/R35.4.1/Linux_for_Tegra/mfi_jetson-agx-orin-devkit/tools/kernel_flash/l4t_initrd_flash_internal.sh --network usb0 --usb-instance 3-10.1 --device-instance 1 --flash-only --network usb0 jetson-agx-orin-devkit mmcblk0p1
Start flashing device: 3-10.1, rcm instance: 1, PID: 2222709
Log will be saved to Linux_for_Tegra/initrdlog/flash_3-10.1_1_20230808-161223.log
/data2/R35.4.1/Linux_for_Tegra/mfi_jetson-agx-orin-devkit/tools/kernel_flash/l4t_initrd_flash_internal.sh --network usb0 --usb-instance 3-10.2 --device-instance 2 --flash-only --network usb0 jetson-agx-orin-devkit mmcblk0p1
Start flashing device: 3-10.2, rcm instance: 2, PID: 2222712
Log will be saved to Linux_for_Tegra/initrdlog/flash_3-10.2_2_20230808-161223.log
Flash complete (WITH FAILURES)
The log is attached.
flash_3-10.3_0_20230808-161223.log (3.9 KB)

Hi,

what host OS version do you use? Please use Ubuntu 18.04 in case it’s 20.04/22.04.
Try with different USB cable/ports, and flash the device one-by-one to see which one will trigger the timeout error.
You may also do this on the host PC:

sudo -s
echo -1 > /sys/module/usbcore/parameters/autosuspend

Hi @DaveYYY
My host is 20.04,and when i flash only one device,log is attached.
flash_3-10_0_20230808-163856.log (7.2 KB)

What’s the flash command you used this time?
Can you reboot your host PC and try again?

If the USB timeout error keeps happening, please try with 18.04 and also this command:

Hi:
On the Xavier nx board, the 18.04 system is used.
on nx system to flash the orin.


flash_1-2.2_0_20230808-181655.log (3.0 KB)

Hi:
Can i use docker image 18.04?

You cannot use a Jetson device to flash another Jetson device.
Please use a x86 host PC instead.

Hi:
I installed ubuntu18.04 on a virtual machine, but the problem still exists.
i run command “sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 5 --network usb0”

Please do not use virtual machines. They are unstable and not verified by us.
Use a real Ubuntu 18.04 host PC.

Hi:
我使用了虚拟机,然后在我 执行了解压 Tegra_Linux_Sample-Root-Filesystem_R35.4.1_aarch64.tbz2,到 mfi_jetson-agx-orin-devkit/rootfs 下之后,在烧写,就可以正常烧写多个模块了。
我不太明白,为什么还和mfi_jetson-agx-orin-devkit/rootfs 这个目录有关系,和mfi_jetson-agx-orin-devkit/rootfs/mnt这个目录也有关系。而烧写进板子里的文件系统,并不是mfi_jetson-agx-orin-devkit/rootfs里的内容。
Hi:
I used a virtual machine and then performed decompression Tegra_ Linux_ Sample Root Filesystem_ R35.4.1_ Aarch64.tbz2, to mfi_ After running Jetson Agx Orin devkit/rootfs, multiple modules can be burned and written normally.
I don’t quite understand why you’re still with mfi_ The directory jetson agx orin devkit/rootfs is related to mfi_ The directory Jetson agx orin devkit/rootfs/mnt is also relevant. And the file system burned into the board is not mfi_ The content in Jetson agx orin devkit/rootfs.

所以你現在的問題是什麼?
燒進板子裡的是什麼東西?

可能只是一開始你的檔案沒有解壓縮完全,有缺少東西所以失敗而已。

還有其實你可以說中文就好,你下面那一段的英文不知道是不是用翻譯的,看起來很不通順…

烧进板子里的,是我真正制作的rootfs,因为这时我已经用我真正的rootfs制作出来了system.img,而不是我解压的Tegra_Linux_Sample-Root-Filesystem_R35.4.1_aarch64.tbz2这个基础文件。 很有可能是因为rootfs不全,但是,我不明白已经有了system.img,为什么还要有rootfs这个目录呢,这样会导致,制作出来的mfi_jetson-agx-orin-devkit.tar.gz会很大。

MFI的package本來就會把system.img和rootfs目錄一起包進去
但是實際壓縮之後應該是不會佔到兩倍的容量的

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