OS Images............................................................................................................................................... 8
United States.......................................................................................................................................... 20
1.414 Feb 2017hlangApplies to release 27.0. Updates for
1.43 Mar 2017hlangUpdates for release 27.1 for
Note: Apparent hyperlinks in this document are a legacy of the HTML version and may not operate as expected
in the PDF version.
TX2.
exposure and compliance
statements.
3 | DA_07976-001Jetson TX2 Developer Kit
Page 4
Force Recovery Mode
Jetson TX2 Developer Kit
The NVIDIA® Jetson™ TX2 Developer Kit is a full-featured development platform for visual computing. It is ideal
for applications requiring high computational performance in a low power envelope. The Jetson TX2 Developer
Kit is designed to get you up and running quickly; it comes pre-flashed with a Linux environment, includes
support for many common APIs, and is supported by NVIDIA’s complete development tool chain. The board
exposes many standard hardware interfaces, enabling a highly flexible and extensible platform.
For software updates and the developer SDK supporting your OS image and host development platform, go to:
http://developer.nvidia.com/embedded-computing
The SDK includes an OS image for you to load onto your device, developer tools, supporting documentation, and
code samples to help you get started.
Individual development efforts vary and may result in modifications to the system configuration. NVIDIA
recommends that you begin with the basic system configuration (as shipped) to ensure proper system operation
prior to any further development.
Prerequisites
•A Jetson TX2 Developer Kit
•Your Jetson TX2 carrier board must be cabled as follows:
•Serial cable plugged into the serial port on the target connected to your Linux host directly or through a
serial-to-USB converter. This is required to setup serial console on the Linux host.
•An Ethernet cable is plugged into the on-board Ethernet port.
•An HDMI cable connects the carrier board to an external HDMI display.
•(Not included in the developer kit) To connect USB peripherals such as keyboard, mouse, and USB/
Ethernet adapter (for network connection), a USB hub must be connected to the working USB port on the
system.
Powering Up
1.Connect a USB keyboard to the USB Type A connector of your device.
2.Connect an HDMI-compatible display to the HDMI connector on your device.
3.Connect the AC adapter supplied in your kit to the power connector of your device. Use the supplied AC
adapter since it is appropriately rated for your device.
4.Plug the power adapter into an appropriately rated electrical outlet.
The system should power on. If not, press and release the power buon on the device.
5.When prompted, enter nvidia for both the user name and password.
Force Recovery Mode
To update your system, you must be in Force USB Recovery Mode so that you can transfer system software
Jetson TX2 Developer KitDA_07976-001| 4
Page 5
Flashing the Boot Loader and Kernel
to the Jetson TX2 module. When in Force USB Recovery Mode, you are able to update system software and
write to the boot loader, boot configuration table (BCT), and write partition configuration to the device.
For OS-specific instructions when updating system software on your Jetson TX2, see the Developer SDK
documentation.
To place system in Force USB Recovery Mode
1.
Power down the device. If connected, remove the AC adapter from the device. The device must be powered
OFF, and not in a suspend or sleep state.
2.Connect the Micro-B plug on the USB cable to the Recovery (USB Micro-B) Port on the device and the other
end to an available USB port on the host PC.
3.Connect the power adapter to the device.
4.With the system powered on:
•Press and hold the RECOVERY FORCE buon.
•While depressing the RECOVERY FORCE buon, press and release the RESET buon.
•Wait 2 seconds and release the RECOVERY FORCE buon.
Flashing the Boot Loader and Kernel
This topic describes the steps required for flashing and booting the target Tegra device. Usage information is also
provided for the flash.sh helper script.
For detailed information see Flashing the Boot Loader and Kernel.
The flashing procedure flashes the board with the boot loader and the kernel. Optionally, you can also flash the
rootfs to the internal eMMC.
Prerequisites
The following directories must be present:
•/bootloader—boot loader and flashing tools such as NvFlash, CFG, BCT, etc.
•/kernel—a kernel zImage /vmlinux.uimg, DTB files, and kernel modules.
•/rootfs—the root file system that you download. This directory is empty initially, you populate it with the
sample file system.
•/nv_tegra—NVIDIA® Tegra® user space binaries and sample applications.
Additionally, a USB cable is required and must be connected to the recovery port prior to running the flashing
commands.
To flash the target Tegra device
1.Put the target board into reset/recovery mode as follows:
•Power on the board.
•Hold the recovery buon and then press the reset buon
2.Run the flash.sh script that is in the top-level directory of this release.
The script must be supplied with the target board (jetson-tx2) for the root file system:
5 | DA_07976-001Jetson TX2 Developer Kit
Page 6
$ sudo ./flash.sh <platform> <rootdev>
•If the root file system will be on a USB disk, execute the script as follows:
$ sudo ./flash.sh <platform> sda1
•If a SATA device is connected, that device enumerates as sda1.
•If the root file system will be on an SD card, execute the script as follows:
$ sudo ./flash.sh <platform> mmcblk1p1
•If the root file system will be on the internal eMMC, execute the script as follows:
$ sudo ./flash.sh <platform> mmcblk0p1
Where <platform> is jetson-tx2.
The above examples are for u-boot. For fastboot, add the following argument:
-L <PATH_TO_FASTBOOT_BIN_FILE>
The boot loader and kernel will load.
For more information on U-Boot, see U-Boot Customization.
Flash Script Usage
Flash Script Usage
Detailed usage information is available by running the following command:
flash.sh –h
Usage
sudo ./flash.sh [options] <platform> <rootdev>
Where you specify the required parameters and one or more of the options shown in the following table.
ParametersDescription
<platform>Is jetson-tx2.
<rootdev>Is one of following:
mmcblk0p1Specifies internal eMMC.
mmcblk1p1Specifies external SDCARD.
sda1Specifies external USB device (such as, USB memory stick or
HDD).
eth0Specifies nfsroot via external USB Ethernet interface.
OptionsDescription
-hSpecifies to print this usage information.
Jetson TX2 Developer KitDA_07976-001| 6
Page 7
-b <bctfile>Specifies the NvFlash Boot Configuration Table (BCT) file.
-c <cfgfile>Specifies the NvFlash configuration file.
-d <dtbfile>Optionally specifies a device tree file to use instead of the default.
-e <emmc_file>Specifies the eMMC size of the target device.
-f <flashapp>Specifies the path to flash application: nvflash or tegra-rcm.
-iSpecifies to pass the user kernel command line to the kernel as-is.
-k <partition id>Specifies the kernel partition ID to be updated (minimum = 5).
-n <nfs args>Specifies the static NFS network assignments:
<Client IP>:<Server IP>:<Gateway IP>:<Netmask>
-o <odmdata>Specifies the ODM data value.
-pTotal eMMC HW boot partition size.
-rSpecifies to skip building and reuse existing system.img.
JetPack
-s <ubootscript>Specifies the boot script file for U-Boot.
-C <cmdline>Specifies the kernel command line. Warning: Each option in this kernel
command-line gets higher precedence over the same option from fastboot.
In case of NFS booting, this script adds NFS booting related arguments if
the -i option is omitted.
-F <flasher>Specifies the flash server, such as fastboot.bin.
-I <initrd>Specifies initrd file. Null initrd is the default.
-K <kernel>Specifies the kernel image, such as zImage.
-L <bootloader>Specifies the full path to the boot loader, such as fastboot.bin or u-boot.bin.
-P
<end_of_PPT_plus_1>
-R <rootfs dir>Specifies the sample rootfs directory.
-N <nfsroot>Specifies the nfsroot, for example:
-S <size>Specifies the rootfs size in bytes. This is valid only for internal rootdev.
Specifies the sum of the primary GPT start address, the size of PPT, plus 1.
<my IP addr>:/my/exported/nfs/rootfs
KiB, MiB, GiB style shorthand is allowed. For example, 1GiB signifies 1024 *
1024 * 1024 bytes.
-T <ITS file>ITS file name. Valid only for u-boot.
JetPack
The NVIDIA® Jetson™ Development Pack (JetPack) is an installer that automates installation of a development
7 | DA_07976-001Jetson TX2 Developer Kit
Page 8
Libraries
environment for the NVIDIA Jetson Embedded Platform, and makes it easy to flash your Jetson system with
the latest OS images. JetPack includes host and target tools, APIs, and packages (middleware, samples, and
documentation including help for compiling samples) to enable you to jumpstart your environment and begin
developing.
Supported Host Operating Systems
•Ubuntu Linux x64 (v14.04)
At least 10 GB of disk space is required for the complete installation of JetPack TX2.
Target Platform Requirements
•Jetson Tegra Developer Kit
•Connected as follows:
•Serial cable plugged into the serial port J1A2 UART4 on the target connected to your Linux host directly
or through a serial-to-USB converter. Required to setup serial console on the Linux host.
•A USB Micro-B cable connecting the Jetson system to your Linux host for flashing.
•(Not included in the Developer Kit) To connect USB peripherals such as a keyboard, mouse, and USB/
Ethernet adapter for network connection, a USB hub must be connected to the working USB port (J1C2
USB2) on the Jetson system.
•An HDMI cable is plugged into the Jetson system HDMI port, which is connected to an external HDMI
display.
•An Ethernet cable is plugged into the on-board Ethernet port.
JetPack Components
JetPack includes host (Ubuntu Desktop) and target (Jetson) development tools, APIs, and packages (OS images, tools,
middleware, samples, and documentation) for developing on the NVIDIA Jetson Embedded platform.
OS Images
JetPack includes a sample file system derived from Ubuntu.
Libraries
JetPack includes the following libraries:
•CUDA Toolkit for Ubuntu (with cross-development support)
•CUDA Toolkit for L4T
•OpenCV for Tegra
•VisionWorks
For more information, see:
https://developer.nvidia.com/embedded/visionworks
Jetson TX2 Developer KitDA_07976-001| 8
Page 9
Installing JetPack TX2
Developer Tools
JetPack includes the following developer tools:
Tegra Graphics Debugger
A console-grade tool that allows you to debug and profile OpenGL ES 2.0, OpenGL ES 3.0, OpenGL ES 3.1,
OpenGL 4.3, OpenGL 4.4 and OpenGL 4.5, enabling game and graphics developers to get the most out of
Tegra.
You must have downloaded the latest JetPack version, jetpack-${VERSION}.run. ${VERSION} refers to the
version string for your installer.
9 | DA_07976-001Jetson TX2 Developer Kit
Page 10
1.Add execute permissions for jetpack-${VERSION}.run:
chmod +x jetpack-${VERSION}.run
2.Run jetpack-${VERSION}.run in a terminal.
The JetPack installer indicates the installation directory.
Installing JetPack TX2
3.Select the development environment to setup.
Jetson TX2 Developer KitDA_07976-001| 10
Page 11
Installing JetPack TX2
4.The JetPack installer pop-up window displays and prompts for sudo permission to use during the
installation process. Enter your sudo password.
The Component Manager opens, allowing you to customize the components to install.
11 | DA_07976-001Jetson TX2 Developer Kit
Page 12
Installing JetPack TX2
5.Select the Jetson Developer Kit you are developing to customize the installation components. Jetson TK1
Developer Kit, Jetson TX1 Developer Kit, and Jetson TX2 Developer Kit support is available.
6.To run a standalone Ubuntu install, deselect Jetson target specific entries.
7.Accept the license agreement for the selected components.
Jetson TX2 Developer KitDA_07976-001| 12
Page 13
Installing JetPack TX2
The component manager proceeds with the installation.
8.Once the host installation steps are completed, click the Next buon to continue with the installation of the
target components.
13 | DA_07976-001Jetson TX2 Developer Kit
Page 14
Installing JetPack TX2
Jetpack proceeds with seing up the Jetson Developer Kit target if the corresponding components were
selected. For example, flashing the OS and pushing components to the Jetson Developer Kit target.
9.If you de-selected Flash OS in the component Manager, you must enter the IP address, user name, and
password to set up an ssh connection to the target device.
10.
After entering the required information click Next.
JetPack installs the components on the target device.
11.
If you selected Flash OS in the Component Manager, you must select the network layout for your specific
environment.
Jetson TX2 Developer KitDA_07976-001| 14
Page 15
Installing JetPack TX2
12.
If you selected the Device access Internet via router/switch layout, you must select which interface to use
for Internet access.
13.
If you selected the Device get IP assigned by DHCP server on host and access Internet via host machine
layout, you must select which interface to use for Internet access and which to use for the target interface.
15 | DA_07976-001Jetson TX2 Developer Kit
Page 16
Installing JetPack TX2
14. A pop-up window displays instructing you to put your device into Force USB Recovery Mode to flash the OS.
15. When prompted, install components on the specific target machine, and compile the samples.
Jetson TX2 Developer KitDA_07976-001| 16
Page 17
Compiling
16. After the post installation tasks are completed, the installation is complete.
Compiling
JetPack automatically compiles all samples if Compile Samples is checked during the components selection.
•If you selected CUDA components, CUDA samples are located at:
Run the samples at the command line or by double-clicking on them in the file browser. For example, when you
run the oceanFFT sample, the following screen is displayed.
Jetson TX2 Developer KitDA_07976-001| 18
Page 19
Running JetPack Samples
19 | DA_07976-001Jetson TX2 Developer Kit
Page 20
United States
Compliance
The NVIDIA® Jetson TX2 Developer Kit is compliant with the regulations listed in this section. Compliance
marks, including the FCC and IC ID numbers, can be found at:
http://developer.nvidia.com/embedded-computing
United States
Federal Communications Commission (FCC)
FCC ID: VOB-P3310
This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this
device may not cause harmful interference, and (2) this device must accept any interference received, including
any interference that may cause undesired operation of the device.
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part
15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference
in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference to radio communications.
However, there is no guarantee that interference will not occur in a particular installation.
If this equipment does cause harmful interference to radio or television reception, which can be determined by
turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the
following measures:
•Reorient or relocate the receiving antenna.
•Increase the separation between the equipment and receiver.
•Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
•Consult the dealer or an experienced radio/TV technician for help.
FCC Warning: The FCC requires that you be notified that any changes or modifications to this device not
expressly approved by the manufacturer could void the user’s authority to operate the equipment.
RF Radiation Exposure Statement
This equipment complies with FCC RF radiation exposure limits set forth for an uncontrolled environment. This
equipment should be installed and operated with a minimum distance of 20 centimeters between the radiator and
your body.
Only those antennas with same type and lesser/equal gain filed under this FCC ID number can be used with this
device.
Jetson TX2 Developer KitDA_07976-001| 20
Page 21
Underwriters Laboratories (UL)
UL Listed Product Logo for Jetson TX2 Developer Kit, model name P2597.
I.T.E E204896
UL Recognized Component Logo for Embedded System Module, model name P3310.
Canada
Canada
Industry Canada (IC)
IC: 7361A-P3310
CAN ICES-3(B)/NMB-3(B)
This device complies with Industry Canada’s licence-exempt RSSs of the Industry Canada Rules. Operation is subject
to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any
interference, including interference that may cause undesired operation of the device.
5150–5250 MHz is only for indoor use to reduce the potential for harmful interference to co-channel mobile
satellite systems;
Ce dispositif est conforme à la norme RSS-247 d'Industrie Canada applicable aux appareils radio exempts de
licence. Son fonctionnement est sujet aux deux conditions suivantes: (1) le dispositif ne doit pas produire de
brouillage préjudiciable, et (2) ce dispositif doit accepter tout brouillage reçu, y compris un brouillage susceptible
de provoquer un fonctionnement indésirable.
RF Radiation Exposure Statement:
Jetson Dev Kit has been tested and complies with IC RSS 102 RF radiation exposure limits set forth for an
uncontrolled environment when used with the NVIDIA accessories supplied or designated for this product. To
satisfy IC exposure requirements, a separation distance of at least 20 cm must be maintained between the antenna
of this device and persons during device operation. The use of any other accessories may not ensure compliance
with IC RSS 102RF exposure guidelines.
Déclaration d'exposition aux radiations:
La Jetson Dev Kit a ete testee conformemment aux normes d’exposition d’emission RF de la IC RSS 102 pour un
21 | DA_07976-001Jetson TX2 Developer Kit
Page 22
Australia and New Zealand
environement non controle lors d’utilisation avec les accessoires fournis or recommendes par NVIDIA. Pour
satisfaire aux exigences d'exposition IC, une distance de séparation d'au moins 20 cm doit être maintenue entre
l'antenne de cet appareil et des personnes pendant le fonctionnement de l'appareil. L’utilisation d’accessoires
autres que ceux recommendes par NVIDIA ne guarantis pas la compatibilite avec les normes d’emission RF de la
IC RSS 102.
European Union
European Conformity; Conformité Européenne (CE)
This device bears the CE mark and class-2 identifier in accordance with Directive 1999/5/EC.
This device complies with the following directives:
•R&TTE Directive for radio equipment
•Low Voltage Directive for electrical safety
•RoHS Directive for hazardous substances
A copy of the Declaration of Conformity to the essential requirements may be obtained directly from NVIDIA
GmbH (Floessergasse 2, 81369 Munich, Germany).
Australia and New Zealand
Australian Communications and Media Authority (RCM)
This product meets the applicable EMC requirements for Class B, I.T.E equipment and applicable radio
equipment requirements.
Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of
such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication
or otherwise under any patent or patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without
notice. This publication supersedes and replaces all information previously supplied. NVIDIA Corporation products are not authorized for use as
critical components in life support devices or systems without express written approval of NVIDIA Corporation.
Trademarks
NVIDIA and the NVIDIA logo are trademarks or registered trademarks of NVIDIA Corporation in the United States and other countries. Other company
and product names may be trademarks of the respective companies with which they are associated.
27 | DA_07976-001Jetson TX2 Developer Kit
Page 28
Legal Information
Legal Information
Notice
ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER
AND SEPARATELY, "MATERIALS") ARE BEING PROVIDED "AS IS." NVIDIA MAKES NO WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE
WITH RESPECT TO THE MATERIALS, AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
IMPLIED WARRANTY OR CONDITION OF TITLE, MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE AND ONINFRINGEMENT, ARE HEREBY EXCLUDED TO THE MAXIMUM EXTENT PERMITTED BY LAW.
Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the
consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use.
No license is granted by implication or otherwise under any patent or patent rights of NVIDIA Corporation. Specifications mentioned in
this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. NVIDIA
Corporation products are not authorized for use as critical components in life support devices or systems without express written approval
of NVIDIA Corporation.
Trademarks
NVIDIA, the NVIDIA logo, CUDA, DriveWorks, Jetson, Tegra, TensorRT, Vibrante, and VisionWorks are trademarks or registered trademarks
of NVIDIA Corporation in the United States and other countries. Other company and product names may be trademarks of the respective
companies with which they are associated.
The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the
Creative Commons 3.0 Attribution License.
HDMI, the HDMI logo, and High-Definition Multimedia Interface are trademarks or registered trademarks of HDMI Licensing LLC.
ARM, AMBA, and ARM Powered are registered trademarks of ARM Limited. Cortex, MPCore and Mali are trademarks of ARM Limited. All
other brands or product names are the property of their respective holders. "ARM" is used to represent ARM Holdings plc; its operating
company ARM Limited; and the regional subsidiaries ARM Inc.; ARM KK; ARM Korea Limited.; ARM Taiwan Limited; ARM France SAS; ARM
Consulting (Shanghai) Co. Ltd.; ARM Germany GmbH; ARM Embedded Technologies Pvt. Ltd.; ARM Norway, AS and ARM Sweden AB.