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 ON-INFRINGEMENT, ARE HEREBY
EXCLUDED TO THE MAXIMUM EXTENT PERMITTED BY LAW.
Information furnished is believed to be accurate and reliabl e. How ever, NVIDIA Corporation ass umes no responsibility for the consequences of use
of such information or for any infring ement 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 and Tegra 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.
Copyright
The NVIDIA® TX1 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 TX1 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 NVIDIAs complete development tool chain.
The board exposes many standard hardware interfaces, enabling a highly flexible and extensible
platform.
Go to http://developer.nvidia.com/embedded-computing
developer SDK supporting the OS image and host development platform that you want to use. The SDK
includes an OS image that you will load onto your device, developer tools, supporting documentation,
and code samples to help you get started.
for access to software updates and the
Getting Started
Individual development efforts will vary and may result in modifications to the system configuration. It
is recommended that you begin with the basic system configuration (as shipped) to ensure proper
system operation prior to any further development.
Assumptions
> You have a Tegra Developer System, equipped with the NVIDIA® Tegra® TX1 processor.
> Your developer system should 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. (To setup serial console on the Linux host.)
(Not included in the developer kit) To connect USB peripherals such as keyboard, mouse, and
[optional] USB/Ethernet adapter (for network connection), a USB hub should be connected to
the working USB port on the system.
An HDMI cable plugged into the target which is connected to an external HDMI display.
An Ethernet cable plugged into the on board Ethernet port.
Powering Up the Tegra Device
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 kit.
4. Plug the power adapter into an appropriately rated electrical outlet.
5. They system should power on. If not, press and release the power button on the device.
To update your system, you will need to be in Force USB Recovery Mode so you can transfer system
software to the developer board. When in Force USB Recovery Mode, you are able to update system
software and write the boot loader, boot configuration table (BCT), and partition configuration to the
Tegra device.
See the Developer SDK documentation for OS specific instructions when updating system software on
your developer board.
To place system in Force USB Recovery Mode:
1. Power down the device . If co nn ecte d, remove the AC adapter from the device. The
device MUST be powered OFF, 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 [4] 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 release the POWER button, if necessary; press
and hold the RECOVERY FORCE button; while depressing the RECOVERY FORCE button,
press and release the RESET button; wait two seconds and release the RECOVERY
FORCE button.
This section describes the steps required to flash and boot the target Tegra device. It also
provides usage information for the
Flash Procedure
First, flash the board with the boot loader and kernel, and, optionally, flash the rootfs to
internal eMMC.
Prerequisites
The following directories must be present:
• /bootloader—boot loader plus flashing tools (NvFlash, CFG, BCTs, etc.)
• /kernel—a kernel zImage /vmlinux.uimg, DTB files, and kernel modules
• /rootfs—the root file system that you download (This directory starts empty and you
populate it with the sample file system.)
• /nv_tegra—NVIDIA
®
Tegra® user space binaries and sample applications
flash.sh helper script.
You must also have the USB cable connected to the recovery port prior to running the
commands listed in the procedure. For more information, see the Requirements
this section.
To flash the boot loader and kernel
1. Put the target board into reset/recovery mode. Do so by first powering on the board
and then holding the recovery button, and then pressing the reset button as
described in the Quick Start Guide for the board.
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 (
$ 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
Note: 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
topic in
jetson-TX1) for the root file system:
• 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-TX1.
The above examples are for u-boot. For fastboot, add the following argument:
from fastboot. In case of NFS booting, this script adds NFS booting
fastboot.bin
initrd
initrd
u-boot.bin
<my IP addr>:/my/exported/nfs/rootfs
User Guide
related arguments if the -i option is omitted.
-F <flasher>
-I <initrd>
Specifies the flash server, such as
Specifies
file. Null
.
is the default.
-K <kernel> Specifies the kernel image, such as zImage.
-L
<bootloader>
-P
<end_of_PPT_p
Specifies the full path to the boot loader, such as fastboot.bin or
.
Specifies the sum of the primary GPT start address, the size of PPT,
plus 1.
lus_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. 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.
This section is intended to help you get familiar with installing the Developer Pack (JetPack TX1), using
the tools and running sample code.
Before you Begin
> You have a Tegra Developer Kit equipped with the NVIDIA Tegra TX1 processor.
> You have a host machine that is running Linux.
> Your developer system is cabled as follows:
Serial cable plugged into the serial port J1A2 UART4 on the target connected to your Linux
host directly or through a s eria l -to-USB converter. (To setup serial console on the Linux host.)
USB Micro-B cable connecting (J1E1 USB0) to your Linux host for flashing.
(Not included in the developer kit) To connect USB peripherals such as keyboard, mouse, and
[optional] USB/Ethernet adapter (for network connection), a USB hub should be connected to
the working USB port (J1C2 USB2) on the system.
An HDMI cable plugged into "J1C1 HDMI1" on the target which is connected to an external
HDMI display.
An Ethernet cable plugged into the J1D1 on board Ethernet port.
> Download latest JetPack TX1
The latest version of the Development Pack (JetPack TX1) is available at NVIDIA Develo per
All available JetPack TX1 downloads here.
Installing JetPack TX1
The following instructions assume you have downloaded the latest JetPack version, JetPack${VERSION}.run, where ${VERSION} refers to the version string for the installer you have.
1. Add exec permissions for the JetPack-${VERSION}.run
5. The JetPack installer will pop up a window to ask for permission to use during the
installation process; you will need to enter your sudo password here.
6. The Component Manage r opens, which allows you t o cus to mi ze w hich component s t o ins t al l.
Select the Jetson Developer Kit you would like to develop for to customize the installation
components for each device. Jetson TK1 Developer Kit, Jetson TX1 Developer Kit, and
Jetson TX1 Developer Kit support are available.
NOTE: To run a standalone Ubuntu install, deselect Jetson target specific entries.
7. Accept the license agreement for the selected components.
8. The Component Manager will proceed with the installation. Once the host installation steps
are completed, click the Next button to continue with the installation of target
components.
NOTE: JetPack will now proceed with setting up the Jetson Developer Kit target, if the
corresponding components were selected (i.e., flashing the OS and pushing components to
the Jetson Developer Kit target).
9. If you deselected Flash OS in the Component Manager, you will need to enter the IP
address, user name, and password to set up an ssh connection to the target device.
After you enter the required information and click Next, JetPack will begin installing
components on the target device.
12. 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 is to be used for Internet access, and
which is to be used for the target interface.
13. A pop-up window will instruct you to put your device into Force USB Recovery Mode, so you
can flash the OS.
14. Next, you will be prompted to install components on the specific target machine, and to
JetPack TX1 automatically compiles all samples if “Compile Samples” was checked during components
selection. If you selected CUDA components, CUDA samples will be found in the following directory:
Run them by calling them in terminal, or double-clicking on them in the file browser. For example,
when you run the oceanFFT sample, the following screen will be displayed.
1. ensuring that the end-user has no manual instructions to remove or install module
2. the FCC compliance requirement of the end product, which integrates this module.
3. Appropriate measurements (e.g. 15 B compliance) and if applicable additional equipment authorizations (e.g.
Verification, Doc) of the host device to be addressed by the integrator/manufacturer.
4. The separate approval is required for all other operating configurations, including portable configurations with
respect to Part 2.1093 and different antenna configurations
Guidance to the Host Manufacturer:
We hereby acknowledge our responsibility to provide guidance to the host manufacturer in the event that
they require assistance for ensuring compliance with the Part 15 Subpart B requirements.
The user manual of the end product should include
1. Any changes or modifications not expressly approved by the party responsible for compliance could void the
user's authority to operate this equipment.
2. the restriction of operating this device in indoor could void the user’s authority to operate the equipment.
3. This device and its antenna(s) must not be co-located or operating in conjunction with any other antenna or
transmitter.
4. This equipment should be installed and operated with minimum distance 20cm between the radiator & your
body.
5. The FCC part 15.19 statement: 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 interference that may cause undesired operation.
Label of the end product:
The final end product must be labeled in a visible area with the following " Contains TX FCC ID: LDKNVTX11697
".
The end product shall bear the following 15.19 statement: 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 interference that may cause undesired
operation.
If the labelling area is considered too small and therefore it is impractical (smaller than the palm of the hand)
to display the compliance statement, then the statement may be placed in the user manual or product
packaging.
Underwriters Laboratories (UL)
UL Listed Product Logo for Jetson TX1 Developer Kit, model name P2597.
I.T.E E204896
UL Recognized Component Logo for Embedded System Module, model name P2180.
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.
This radio transmitter [IC: 2461N-NVTX11697] has been approved by Innovation, Science and Economic
Development Canada to operate with the antenna types listed below, with the maximum permissible
gain indicated. Antenna types not included in this list that have a gain greater than the maximum gain
indicated for any type listed are strictly prohibited for use with this device.
Le présent émetteur radio [IC: 2461N-NVTX11697] a été approuvé par Innovation, Sciences et
Développement économique Canada pour fonctionner avec les types d'antenne énumérés ci-dessous et
ayant un gain admissible maximal. Les types d'antenne non inclus dans cette liste, et dont le gain est
supérieur au gain maximal indiqué pour tout type figurant sur la liste, sont strictement interdits pour
l'exploitation de l'émetteur.