Flashing Zedbox Orin

Hi,

I’ve been trying to flash my ZEDBox for a while and have run into multiple issues, which I’ve raised with support.

I’m posting here in case somebody from the community can shed some light on what’s going on.

At the moment, I get this message at the end of the flashing process, both after flashing directly from a host PC and also after rebooting using a flashed usb-drive.

Does anybody have any suggestions for what to do?

Really appreciate the help!

tar: Read checkpoint 660000
tar: Read checkpoint 670000
writing item=17, 9:0:secondary_gpt, 61203267072, 16896, gpt_secondary_9_0.bin, 16896, fixed--0, d14ef2f285992e35ccef71d658241fa895fc70c
[ 142]: l4t_flash_from_kernel: Successfully flash the external device
[ 142]: 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.
[ 142]: l4t_flash_from_kernel: Error flashing qspi
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.JJ4hGYCOEW. You can access the target’s terminal through “sshpass -p root ssh root@fc00:1:1:0::2”
Cleaning up…
FLASH FAILED.

Hi Jose,

Can you confirm that you have followed the steps from this documentation page before having this error? https://www.stereolabs.com/docs/embedded/zed-box-orin/reset-update

Best,

Gabriel Enzo
Stereolabs Support

Our ZEDBOX orin also soft-bricked itself somehow, and our only way out was to reset it. I followed the instructions but ran into the exact same issue “Error flashing qspi”.

Now our device is completely bricked and wouldn’t even show up in the device list despite booting with the OTG cable connected. Power light doesn’t come on either.

@system Would greatly appreciate if you could help fix this.

1 Like

Hi @sourza

Welcome to the Stereolabs community.

Please send an email to support@stereolabs.com. Add all the details regarding this problem.

Hi @Myzhar , @sourza , @yosue

I’m trying to flash my device but I’m hitting the same issue: the device only boots when USB is connected — it will not boot successfully without USB. I’m attaching the host machine logs and device screenshots below.

Host machine log (relevant excerpts)

Writing qspi_bootblob_ver.txt (parittion: B_VER) into /dev/mtd0
Sha1 checksum matched for /mnt/internal/qspi_bootblob_ver.txt
Writing /mnt/internal/qspi_bootblob_ver.txt (109 bytes) into  /dev/mtd0:66912256
Copied 109 bytes from /mnt/internal/qspi_bootblob_ver.txt to address 0x03fd0000 in flash
Writing qspi_bootblob_ver.txt (parittion: A_VER) into /dev/mtd0
Sha1 checksum matched for /mnt/internal/qspi_bootblob_ver.txt
Writing /mnt/internal/qspi_bootblob_ver.txt (109 bytes) into  /dev/mtd0:66977792
Copied 109 bytes from /mnt/internal/qspi_bootblob_ver.txt to address 0x03fe0000 in flash
Writing gpt_secondary_3_0.bin (parittion: secondary_gpt) into /dev/mtd0
Sha1 checksum matched for /mnt/internal/gpt_secondary_3_0.bin
Writing /mnt/internal/gpt_secondary_3_0.bin (16896 bytes) into  /dev/mtd0:67091968
Copied 16896 bytes from /mnt/internal/gpt_secondary_3_0.bin to address 0x03ffbe00 in flash
[ 265]: l4t_flash_from_kernel: Successfully flash the qspi
done                            
Creating filesystem with 499718409 4k blocks and 124936192 inodes
Filesystem UUID: a419b20f-803d-4e62-837d-83a32a7f93a6
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-TYiHqJuXt9: special device /dev/nvme0n1p1 does not exist.
[ 760]: l4t_flash_from_kernel: Failed to mount APP partition /dev/nvme0n1p1
[ 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: Failed to write to APP
[ 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.Ec32b6NjUi. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2" 
Cleaning up...
FLASH FAILED.

Device screenshots



Any detailed steps or commands to try would really help me debug and solve this.
FYI, i have tried sudo ufw disable to diasble firewall
Thank you so much for your support!

Best regards,
Karthik A.

Hi @karthikreddy157
You must reflash the device because the file system looks corrupted.

Hi @Myzhar

But the flashing is failing as i mentioned above

mount: /tmp/ci-TYiHqJuXt9: special device /dev/nvme0n1p1 does not exist.
[ 760]: l4t_flash_from_kernel: Failed to mount APP partition /dev/nvme0n1p1
[ 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: Failed to write to APP
[ 760]: l4t_flash_from_kernel: Error flashing external device

Please read my reply to the other thread.