Hi Team,
I’m trying to flash my Zed Box by following the provided documentation, but I’m encountering an error during the process.
Here’s what I did:
Booted into recovery mode from USB after performing the USB live flash.
Followed the documented steps.
Encountered an error (please see the attached screenshots for details).
I’m not sure what’s causing this issue. Could you please help me understand what might be going wrong?
Thank you for your support!
Why are you performing this step? Can’t you force the recovery mode by using the OTG port?
HI @Myzhar ,
Actually i tried but the result was same.
Copied 16896 bytes from /mnt/internal/gpt_secondary_3_0.bin to address 0x03ffbe00 in flash
[ 268]: l4t_flash_from_kernel: Successfully flash the qspi
done
Creating filesystem with 499718409 4k blocks and 124936192 inodes
Filesystem UUID: 1557fc32-09c1-4f9f-98fb-9fccbf153669
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: mkfs.ext4: Input/output error while writing out and closing file system
Formatting APP parition done
mount: /tmp/ci-C5hidF7tUf: special device /dev/nvme0n1p1 does not exist.
[ 760]: l4t_flash_from_kernel: Failed to mount APP partition /dev/nvme0n1p1
[ 760]: l4t_flash_from_kernel: Failed to write to APP
[ 760]: l4t_flash_from_kernel: The device size indicated in the partition layout xml is smaller than the actual size. This utility will try to fix the GPT.
[ 760]: l4t_flash_from_kernel: Error flashing external device
Flash failure
Either the device cannot mount the NFS server on the host or a flash command has failed. Check your network setting (VPN, firewall,...) to make sure the device can mount NFS server. Debug log saved to /tmp/tmp.VHcSVRkUDp. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2"
Cleaning up...
FLASH FAILED.
Here something that observed strange, when i followed same procedure again along with same hardware(host device, cable, port) i am getting different error ERROR: might be timeout in USB write..
but when i checked with lsusb its in recovery mode only.
spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3768-0000+p3767-0000-nv.dtb" --bct_backup
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
Entering RCM boot
[ 0.0319 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[ 0.0319 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[ 0.0319 ] rcm boot with presigned binaries
[ 0.0324 ] tegrarcm_v2 --instance 1-3 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 0.0328 ] BR_CID: 0x80012344705DF2DF1000000019020080
[ 0.0456 ] Sending bct_br
[ 0.0571 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-3 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
Cleaning up...
FLASH FAILED.
saartha@saartha-dual:~/Downloads$ lsusb -d '0955:7323'
Bus 001 Device 017: ID 0955:7323 NVIDIA Corp. APX
saartha@saartha-dual:~/Downloads$ lsusb -d '0955:7323'
is these known behaviour
Have you tried to replace the USB cable with one shorter and to change the USB port?
Yes, we have tried multiple USB cables.
Please write an email to support@stereolabs.com to open an RMA.
Add a link to this thread.