OTA upgrade on custom board

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hi all,

I am using L4T 32.4.2 on our custom board.

We are able to do a apt upgrade and the L4T and jetpack are upgraded to 32.4.4. and 4.4.1 respectively.
But while trying to use “apt dist-upgrade”, the L4T and jetpack version remain same.

Is there a way that I can do a “apt dist-upgrade” for custom board to latest version?

Thanks
Deepika.S

3

Can you tell more about the scenario? What is the jetpack release on your board when you run apt dist-upgrade?

We just tried apt dist-upgrade on our board and it can work.

4

Thanks for your response @WayneWWW

The L4T version is 32.4.2 and Jetpack version is 4.4 DP on our custom board

We have kept some L4T packages on hold : nvidia-l4t-bootloader, nvidia-l4t-kernel, nvidia-l4t-kernel-dtbs, nvidia-l4t-kernel-headers so that the custom boards kernel and dtb is not over written.

On using “apt upgrade” - the L4T version and jetpack version are upgraded to 32.4.4 and 4.4.1 respectively.
But on using “apt dist-upgrade”, the version of L4T and jetpack remains same and also hdmi issue is noted.

5

Hi @WayneWWW ,

Any updates on the query?
Could you please revert with a solution for upgrading the L4T to the latest version in custom boards?
Waiting for reply…

Thanks and Regards,
Deepika S

6

Hi,

Could you share your commands to hold those?

7

Thanks for your response @WayneWWW

apt-mark hold nvidia-l4t-bootloader nvidia-l4t-kernel nvidia-l4t-kernel-dtbs nvidia-l4t-kernel-headers

We are using this command so that our kernel and dtb is not overwritten.

Thanks and Regards,
Deepika S

8

Hi @WayneWWW ,

Any updates on the query?

Thanks and Regards,
Deepika S

9

Hi deepika.s,

We can’t reproduce your issue on Xavier-NX devkit.
List our test steps for you reference:

  1. Flash JP-4.4 DP (r32.4.2)
    $ head -1 /etc/nv_tegra_release
    R32 (release), REVISION: 4.2, GCID: 20074772, BOARD: t186ref, EABI: aarch64, DATE: Thu Apr 9 01:26:40 UTC 2020
  2. Run below commands to upgrade:
$ sudo apt-mark hold nvidia-l4t-bootloader nvidia-l4t-kernel nvidia-l4t-kernel-dtbs nvidia-l4t-kernel-headers
$ sudo apt dist-upgrade
  1. After upgrade completed and check:
    $ head -1 /etc/nv_tegra_release
    R32 (release), REVISION: 4.4, GCID: 23942405, BOARD: t186ref, EABI: aarch64, DATE: Fri Oct 16 19:37:08 UTC 2020
10

Thanks for your response @carolyuu ,
I want to upgrade from L4T 32.4.2 to latest L4T 32.5.
Followed the Jetson Linux Developer Guide to upgrade from 32.4.2 to 32.5 .

steps followed:

  • Flash JP-4.4 DP (r32.4.2)
    $ head -1 /etc/nv_tegra_release
    # R32 (release), REVISION: 4.2, GCID: 20074772, BOARD: t186ref, EABI: aarch64, DATE: Thu Apr 9 01:26:40 UTC 2020

  • Run the below commands to hold the packages:
    $ sudo apt-mark hold nvidia-l4t-bootloader nvidia-l4t-kernel nvidia-l4t-kernel-dtbs nvidia-l4t-kernel-headers

  • edited nvidia-l4t-apt-source.list file for 32.5

    $ cat /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
    deb https://repo.download.nvidia.com/jetson/common r32.5 main
    deb https://repo.download.nvidia.com/jetson/t194 r32.5 main

  • upgrade command:

    $ sudo apt update

    $ sudo apt dist-upgrade

Both in devkit and custom board, the L4T version was not upgraded also hdmi issue on the next boot was observed on both the boards.

11

Hi deepika.s,

Please share the “apt dist-upgrade” logs and uart logs.
Thanks!

12

Hi @carolyuu ,
I have attached the uart logs and logs obtained during “apt dist-upgrade”

dmesg.txt (67.2 KB)
dist_upgrade_log.txt (191.0 KB)

Please check and let me know how to proceed.
Thanks in advance…

Regards,
Deepika S

14

Hi,

Maybe you can compare the log between dist-upgrade and upgrade.

I see following log from your dist-upgrade log.

the following packages have been kept back:
nvidia-l4t-apt-source nvidia-l4t-bootloader nvidia-l4t-configs nvidia-l4t-core nvidia-l4t-firmware nvidia-l4t-init nvidia-l4t-initrd nvidia-l4t-kernel nvidia-l4t-kernel-dtbs nvidia-l4t-kernel-headers
nvidia-l4t-multimedia-utils nvidia-l4t-oem-config nvidia-l4t-tools nvidia-l4t-wayland nvidia-l4t-weston nvidia-l4t-x11 nvidia-l4t-xusb-firmware

Since the difference between dist-upgrade and upgrade is dist-upgrade would handle the dependencies issue, once you hold some debian package, it may cause nvidia-l4t-core not upgrade either. And most of packages depend on l4t-core.

15

Thanks for your response @WayneWWW ,

I tried to do a upgrade to 32.5 using “apt-get update and apt-get upgrade”. Still I face the same issue.
I checked the logs , the same packages are kept back.
Is there a way to hold the packages and upgrade L4T and jetpack ?

Thanks in advance…

Regards,
Deepika S

16

Why you suddenly have same issue even on apt-get update?

Didn’t you say you can see update when you run apt-get upgrade in the beginning of this post?

17

Hi @WayneWWW ,

I mentioned that I am able to do a upgrade from 32.4.2 to 32.4.4 using" apt-get upgrade"
But I want to upgrade from 32.4.2 to 32.5. I followed the steps mentioned in Jetson Linux Developer Guide along with hold packages to upgrade from 32.4.2 to 32.5 - in this steps “apt dist-upgrade” is used. The L4T and jetpack version was not upgraded and HDMI issue was noticed.

As suggested in your previous reply , along with the steps to upgrade from 32.4.2 to 32.4.5, I used “apt-get update” instead of “apt dist-upgrade” and I reported that I face the same issue.

Regards,
Deepika S

18

If even upgrade does not work, then the dependencies just not allow you to do that.
Let’s make it easy to understand. Our OTA method does not support any customized case.

For example, if you want to hold anything in old release, then that is one of customization so you may get what you want.

Thus, please do not hold any package. We also don’t guarantee rel-32.4.x kernel could work with other rel- 32.5 packages.