NVIDIA Tegra Jetson Xavier NX

The official Mender documentation explains how Mender works. This is a board-specific complement to the official documentation.

Device description

NVIDIA Xavier NX hardware with computer vision, GPU and multimedia support.

URL: https://www.nvidia.com/en-us/autonomous-machines/embedded-systems-dev-kits-modules/
Wiki: https://elinux.org/Jetson_Xavier_NX

Support level

Yocto Project Build Runtime
dunfell (3.1) :test_works: :test_works:


  • A supported Linux distribution and dependencies installed on your workstation/laptop as described in the Yocto Mega Manual
    • NOTE. Instructions depend on which Yocto version you intend to use.

Setup Yocto Environment

Use the tegra-demo-distro to demonstrate a working mender configuration.

Please use the setup-env script in tegra-demo-distro to setup and configure the tegrademo-mender distribution. Use the branch corresponding to the yocto version you plan to target. For instance, for the dunfell branch and NVIDIA L4T release 32.4.3, use these commands from the root of the cloned tree:

git submodule update --init
git checkout dunfell-l4t-r32.4.3

Then use

source ./setup-env --distro tegrademo-mender --machine jetson-xavier-nx-devkit

To setup your build environment for the Jetson AGX Xavier development kit.

See the OE4T/meta-tegra wiki for more information about the meta-tegra project.

Setup build environment

Initialize the build environment:

source ./setup-env --distro tegrademo-mender --machine jetson-xavier-nx-devkit

or if you’ve already setup your initial environment you can use the simpler option:

source ./setup-env

Building the image

You can now proceed with building an image:

bitbake demo-image-base

Using the build output

After a successful build, the images and build artifacts are placed in tmp/deploy/images/jetson-xavier-nx-devkit.

The disk image package for Jetson has a name like demo-image-base-jetson-xavier-nx-devkit.tegraflash.tar.gz. This file can be used along with recovery mode to initially provision the device. To enter recovery mode:

  • Power cycle
  • Hold down the RST button and REC button.
  • Release the RST button while continuing to hold the REC button.
  • Wait two seconds, then release the REC BUTTON.

You should see your NVIDIA device listed in the lsusb device output.

Next, extract the .tar.gz file and then run the ./doflash.sh script inside to flash the build to the device. The script at repos/meta-mender-community/meta-mender-tegra/scripts/deploy.sh can be customized to automate this step if desired. See the instructions on the OE4T wiki for additional details.

On the other hand, if you already have Mender running on your device and want to deploy a rootfs update using this build, you should use the Mender Artifact files, which have .mender suffix. You can either deploy this Artifact in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client standalone mode.


  • meta-tegra: The base BSP layer with support for NVIDIA tegra.
  • meta-mender-tegra layer in meta-mender-community: Customization for mender on tegra, including u-boot and partitioning. See OE4T layer at this link for any changes or to file issues against mender and NVIDIA support.
  • The official Mender documentation explains how Mender works. This is simply a board-specific complement to the official documentation.

Known issues

Let us know if you find one!

1 Like

I have integrated the meta-mender and meta-mender-community in my Yocto build. It works for the Jetson Nano, but when I try to build for the Xavier I get following error when flashing the build using the doflash.sh script:
End sector for APP_b, expected at: 30777310, actual: 59729703

Do you have any idea what the problem could possibly be?

You might be seeing the same issue discussed on the meta-tegra issues forum, see https://github.com/OE4T/tegra-demo-distro/wiki/Customization-of-Storage-Size-on-Mender-Builds and https://github.com/OE4T/meta-tegra/issues/453