Zedbox Orin Flashing Issues

Hardware ZED Box
1

Hi all,

I’m having trouble flashing my ZED Box Orin and could use some help. I’m running Ubuntu 22.04 Jammy from a persistent Live USB, and I’ve tried both the direct flashing method and the Live USB flashing method from the Stereolabs guide. Flash your ZED Box Orin - Stereolabs

My BSP appears to be fully built — Linux_for_Tegra/rootfs contains the complete filesystem, and apply_binaries.sh finishes without errors. But the actual flash step keeps failing, regardless of cable, port, or recovery-mode attempts.

I’ll attach the specific error messages and logs in a follow-up comment.

Below are 2 screen captures. The first is from trying to flash a USB to follow the Live USB booting and the second is from flashing by connecting the Zedbox to my PC via the USB cable.

IMG_D2F0A391-7A30-4791-8F92-B646E0CCE846
IMG_D2F0A391-7A30-4791-8F92-B646E0CCE8461920×2560 464 KB

image
image1920×2560 402 KB

If anyone has experience flashing ZED Box Orin from a Live USB environment or knows common causes for this issue, I’d appreciate any suggestions.

Thanks!

1 Like
2

Hi @RenWarRen9
Welcome to the Stereolabs community.

The first thing to check is if the ZED Box has started in Flash Recovery mode:

I recommend you follow the instructions in the troubleshooting guide:

3

Thank you. I have been following both guides for the past few weeks with no success. The Zedbox does seem to go into recovery mode (I can see it when using lsusb) but keeps failing. The only issue I could see is that I am using a persistent bootable drive to run Ubuntu, as I do not have a host PC that runs Linux. Perhaps the flashing does not work well with this setup, but I have not seen any information that outright says this would be an issue (if there is I must have missed it).

4

In this case, the only possible problem is with the USB connection to the OTG port of the ZED Box.
Try to:

  • change the port
  • use a shorter cable
  • do not use USB hubs
  • anything other that can make the USB connection more stable
5

I will try using a different cable and USB port. As far as the flashing, the procedure takes upwards of 3 hours starting fresh. Is there anyway to cut down this time if the bsp file already exists or does a fresh flash need to happen every time?

6

I believe this is because you are using a slow USB key.
I recommend you change the method and install Ubuntu 22.04 on a PC to improve the process.

7

I would need to partition at least 80GB for that correct?

8

Yes, that’s correct.

9

Got you. I was a bit wary of messing with partitions but I will go ahead and try that.

10

I went ahead and did the operation and it seemed to work. There was an error in the terminal that I unfortunately did not take a screenshot of, but the zed seems to boot fine now. I will try and get a hold of the debug log.

11

I found the Zedbox was not properly flashed so I went ahead to try again but got this error. I also noticed that the Zedbox went out of recovery mode at some point during the flashing (light on and not showing up on lsusb).

IMG_7493
IMG_74931920×2560 296 KB

12

Is the power stable? Are you using the original power supply?

13

I think the power should be stable but if there is a way to confirm that would be helpful. And yes, I am using the original power supply.

14

Please retry the procedure until it’s successful.
I still suspect this is a problem of USB communication stability.

15

I ran the flash a few times and it flashed successfully. However when trying to install chrony (sudo apt install chrony) I was met with a long error message of multiple dpkg package files missing. I’m not sure if this is another issue or if it is linked to the flashing.

16

For this type of issues, I recommend you ask to the NVIDIA Developers Forum to get in touch with NVIDIA’s engineers who worked on the Jetson BSP.