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)
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:
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”
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.