Platform Adaptation and Bring-Up
Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 2
Board Naming
To support a Jetson Nano module together with your carrier board in L4T, you must
choose a simple lower-case, alphanumeric name for your board, possibly including
dashes (-) or underscores (_), but no spaces. Following are some examples of valid board
names:
jetson-nano
jetson-tx1
p3450
The name you choose will appear in file names and path names in U-Boot and Linux
kernel source code and in user-visible device tree file names, and will be exposed to the
user via the U-Boot command prompt and various Linux kernel /proc files.
You must also choose a similarly constructed vendor name. The same character set rules
apply, as in this example:
nvidia
In this document:
• <board> represents your board name.
• <vendor> represents your vendor name.
Note:
Do not simply re-use and modify the existing Jetson Nano Developer
Kit code without choosing and using your own board name. If you do
not use your own board name it will not be obvious to Jetson Nano
users whether modified source code supports your board or the
original Jetson Nano Developer Kit carrier board.
Placeholders in the Porting Instructions
The sections below refer to filenames and pathnames that contain the following
placeholders. Substitute an appropriate value for each placeholder when you enter the
commands.
• <function> is a functional module name, such as power-tree, pinmux, sdmmc-
drv, keys, comm (Wi-Fi/Bluetooth
®
), camera, etc.
• <board> is a name you have chosen to represent your carrier board with Jetson
Nano module. For example, p3450 could represent the carrier board from a Jetson
Nano Developer Kit with a Jetson Nano module. Note that NVIDIA <board> names
use lower case letters only.
• <som> is a System on a Module (SOM) board name, such as p3448.
To Next Page
General
