Board description
NVIDIA Jetson Nano developer kit hardware booting from SD-card:
URL: https://developer.nvidia.com/embedded/jetson-nano-developer-kit
Wiki: https://elinux.org/Jetson_Nano
Test results
The Yocto Project releases in the table below have been tested by the Mender community. Please update it if you have tested this integration on other Yocto Project releases:
| Yocto Project | Build | Runtime |
|---|---|---|
| warrior (2.7) |  |
|
| zeus (3.0) | |
|
Build Means that the Yocto Project build using this Mender integration completes without errors and outputs images.
Runtime Means that Mender has been verified to work on the board. For U-Boot-based boards, the integration checklist has been verified.
Getting started
Prerequisites
- 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.
- Google repo tool installed and in your
PATH.
Setup Yocto environment
Set the Yocto Project branch you are building for:
# set to your branch, make sure it is supported (see table above)
export BRANCH="zeus"
Create a directory for your mender-tegra setup to live in and clone the
meta information.
mkdir mender-tegra && cd mender-tegra
Initialize repo manifest:
repo init -u https://github.com/mendersoftware/meta-mender-community \
-m meta-mender-tegra/scripts/manifest-tegra.xml \
-b ${BRANCH}
Fetch layers in manifest:
repo sync
Setup build environment
Initialize the build environment:
source setup-environment tegra
Building the image
You can now proceed with building an image:
MACHINE=jetson-nano bitbake core-image-base
Replace core-image-base with your desired image target here and in the sections below.
Using the build output
After a successful build, the images and build artifacts are placed in tmp/deploy/images/jetson-nano.
The sd-card image package for Jetson Nano has a name like core-image-base-jetson-nano.sdcard. This file can be used to initially provision the sd-card using dd (replace /dev/sdc with the location of your sd-card):
sudo dd bs=4M status=progress if=tmp/deploy/images/jetson-nano/core-image-base-jetson-nano.sdcard of=/dev/sdc conv=fsync
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 only in Standalone deployments.
See additional notes below about standalone updates on warrior and later branches.
References
- meta-tegra: The base BSP layer with support for NVIDIA tegra. See completed pull request here for modifications to support Mender.
- meta-mender-tegra layer in meta-mender-community: Customization for mender on tegra, including u-boot and partitioning. See completed pull request here for initial modifications to support NVIDIA Jetson-tx2 (pull request for Jetson-Nano here).
- The official Mender documentation explains how Mender works. This is simply a board-specific complement to the official documentation.
Standalone Updates and Bootloader Components
Updates of bootloader components as referenced on the TX2 mender hub page are not supported yet on Jetson-Nano, due to the lack of support from Nvidia for redundant boot on this platform. Nvidia may add support in the future. This means standalone updates do not use the mender-install-manual script as done on TX2 but use standard mender -install. It also means mender upgrades across meta-tegra yocto branches are unlikely to work properly, given possible dependencies between boot components and root filesystem components.
Known issues
- The Jetson-Nano production module is not supported.
If this post was useful to you, please press like, or leave a thank you note to the contributor who put valuable time into this and made it available to you. It will be much appreciated!
.