# sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 1 --showlogs --keep
Waiting for device to expose ssh ......Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
blockdev: cannot open /dev/mmcblk0boot0: No such file or directory
[ 0]: l4t_flash_from_kernel: Serial Number: 1421224247652
[ 0]: l4t_flash_from_kernel: Starting to create gpt for emmc
Active index file is /mnt/internal/flash.idx
Number of lines is 79
max_index=78
writing item=62, 6:0:primary_gpt, 512, 19968, gpt_primary_6_0.bin, 16896, fixed-<reserved>-0, 2b8885a93986dae4574894c82a1c77b4318f0a17
Error: Could not stat device /dev/mmcblk0 - No such file or directory.
Flash failure
Either the device cannot mount the NFS server on the host or a flash command has failed. Debug log saved to /tmp/tmp.KiGBV8pn30. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2"
Cleaning up...
Keeping working dir at /home/firmware/orin/Linux_for_Tegra/temp_initrdflash/bootloader0 and /tmp/tmp.rfzNfgr53s
Why script try to use /dev/mmcblk0 with error instaed of NVMe ?
Could you connect the board in force recovery state w/o specifying its BOARD ID/SKU/FAB and generate mfi package from host?
Yes, I tried with same problem.
Orin NX is in FRM:
root@srvts1:/home/firmware/orin/Linux_for_Tegra# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 019: ID 0955:7423 NVIDIA Corp. APX
Error: Could not stat device /dev/mmcblk0 - No such file or directory.
Flash failure
Either the device cannot mount the NFS server on the host or a flash command has failed. Debug log saved to /tmp/tmp.dE563AwgFf. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2"
Cleaning up...
Could you help to compare these 2 logs (failed with massflash, passed wiht initrd flash) for any difference?
massflash should have similar logic as initrd flash to flash the board.
You can also add the following line in l4t_flash_from_kernel.sh before running massflash to capture more logs.
# Usage: ./l4t_flash_from_kernel.sh
# This script flashes the target from the Network File Systems on the target or
# from the host using the images inside the flash package generated by
# l4t_create_flash_image_in_nfs
set -e
+ set -x
Do you have other SoM to reproduce the similar issue to clarify if the issue is specific to current SoM?
I added set -e and set -x to l4t_flash_from_kernel.sh
# Usage: ./l4t_flash_from_kernel.sh
# This script flashes the target from the Network File Systems on the target or
# from the host using the images inside the flash package generated by
# l4t_create_flash_image_in_nfs
set -e
set -x
set -eo pipefail