were those all identical Orin platforms? please check your target since you’ve assign board info in the command-line.
how about have device connected, by running this in online mode.
please see-also Topic 229129 for sample command-line to massflash Jetson devices.
we have tested this locally,
we’re able to perform initrd_flash on Orin DevKit with ROOTFS_AB enabled.
for example, $ sudo BOARDID=3701 FAB=500 BOARDSKU=0000 BOARDREV=J.0 ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 1 jetson-agx-orin-devkit mmcblk0p1 $ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 1
could you please refer to above commands, update the board info accordingly to test again.
may I know what’s your host environment setups,
please also share the failure rate since you mentioned this happened sometimes,
Please look at my log file. I think the problem is caused by tar unpacking. Is it possible that the USB is unstable? If the machine fails to be rebooted, it cannot be rebooted even if the USB of the device is re plugged or the host is restarted.
which topic? r35.1 release note it’s talking about massfuse…
please refer to our test results in comment #12. we’re able to perform initrd_flash to create massflash blobs for Orin DevKit with ROOTFS_AB enabled.