Clarification of OTA Update Process

Hi,
We have enabled OTA update from r32.7.x to r35.2.1. So the issue you are facing is your release is r32.3.1 and it cannot be upgraded to r32.7.x. This is possible since OTA update may not be working properly on r32.3.1. There are several releases between r32.3.1 and r32.7.x and certain issues may be reported and fixed in later releases.

Hi,
Per
https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3273/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/updating_jetson_and_host.html#wwpID0E05I0HA

Upgrading R32.3 to R32.7 should be supported. We will verify again on developer kit and update.

Hey Dane, thanks for getting back to me. Let me know how you get on testing the update.

Just to confirm, the documentation you’ve linked is to r32.7.3. So we should be testing with that and not r32.7.2 as in the other threads that I reference above?

Also, hoping to get some clarity about why the dist-upgrade method wouldn’t work for minor releases? Even if it’s just to something more stable than r32.3.1, such as r32.5.2. This method seems far more stable than the OTA for such an old release.

More than happy to go from r32.7.X to r35.Y.X through OTA, but the older releases seem to struggle with the updates. Keen to hear your thoughts.

Cheers,

Khan

Hi,
We try the commands and can upgrade from r32.3.1 to r32.7.3:

  1. Modify /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
deb https://repo.download.nvidia.com/jetson/common r32.7 main
deb https://repo.download.nvidia.com/jetson/t194 r32.7 main
  1. Run
$ sudo apt update
$ sudo apt dist-upgrade

The upgrade is successful and ethernet is good.

Do you hit the issue on developer kit or your own custom board? If you use developer kit, it is supposed to work.

This works for me also, but the issue is the upgrade that follows this. Even with the workaround mentioned before (and linked above and linked in the other post) I run into some serious failures. The device fails to boot, I end up in the boot loader and have to do some funky stuff to finally get the jetson into a state where I can re-flash it.

Edit: sorry forgot to mention its the dev kit

Hi,
If you can upgrade from r32.3.1 to r32.7.3, please do this first and then upgrade tor35.2.1.

I’ll test this at the start of next week and get back to you.

Thanks Dane

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.