Nvidia Jetson Nano Manual
  1. Manuals
  2. Brands
  3. Nvidia Manuals
  4. Microcontrollers
  5. JETSON NANO
  6. Manual

Nvidia Jetson Nano Manual

Platform adaptation and bring-up
Hide thumbs Also See for Jetson Nano:
Table of Contents

Advertisement

Quick Links

JETSON NANO PLATFORM
ADAPTATION AND BRING-UP
GUIDE
July 2, 2019
DA_09361-002 |
L4T Driver Package

Advertisement

Table of Contents
loading

Related Manuals for Nvidia Jetson Nano

Summary of Contents for Nvidia Jetson Nano

  • Page 1 JETSON NANO PLATFORM ADAPTATION AND BRING-UP GUIDE July 2, 2019 DA_09361-002 | L4T Driver Package...
  • Page 2 Platform Adaptation and Bring-Up Document Change History DA_09361-002 Version Date Authors Description of Change v1.0 18 Mar 2019 jsachs Initial release v1.1 2 Jul 2019 jsachs Corrected initial release Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | ii...

  • Page 3: Table Of Contents

    USB 3.0 ..................30 HDMI ..................30 Audio ..................30 UART ..................30 SD Card (SDMMC1) ................. 31 Fan .................... 31 Sensors I2C: General ............... 31 Sensors I2C: Touch Screen (Optional) ............ 31 Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | iii...
  • Page 4 Table 1. Available outputs for the P3449 carrier board ........10 Table 2. UPHY lane assignment use cases ............ 10 Table 3. GPIO states and corresponding output cable states ....... 19 Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | iv...

  • Page 5: Platform Adaptation And Bring-Up

    Nano Developer Kit (P3450) that can serve as an example. Board Configuration The Jetson Nano Developer Kit consists of a P3448 System on Module (SOM) connected to a P3449 carrier board. The number P3450 designates the complete Jetson Nano Developer Kit. The SOM and carrier board each has an EEPROM where the board ID is saved.

  • Page 6: Board Naming

    Platform Adaptation and Bring-Up 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...

  • Page 7: Root Filesystem Configuration

    Linux_for_Tegra/apply_binaries.sh. Pinmux Changes If your board schematic differs from that for Jetson Nano Developer Kit carrier board, you must change the pinmux configuration applied by the software. To define your board’s pinmux configuration, you must obtain Jetson_Nano_customer_pinmux_release.xlsm from NVIDIA and customize it...

  • Page 8: Exporting Pinmux For U-Boot

    “SECURITY WARNING,” click Enable Editing or Enable Content, so that you can save your changes to the new file. 5. Rename the Jetson Nano Configuration tab based on the name of your board: 1. Right click the Jetson Nano Configuration tab at the bottom of the window.
  • Page 9 Linux system. 2. Enter the following command to generate the U-Boot pinmux header file: $ ./board-to-uboot.py <board> > pinmux-config-<board>.h Later you will copy pinmux-config-<board>.h into the U-Boot source tree. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 5...

  • Page 10: Accessing Gpios Via "Gpio" Device Labels

    #define CONFIG_TEGRA_BOARD_STRING "NVIDIA P3450-Porg" 3. Copy arch/arm/dts/tegra210-p3450-porg.dts to arch/arm/dts/tegra210-<board>.dts. 4. Edit the set of enabled devices and their parameters (e.g. GPIO and IRQ IDs) in tegra210-<board>.dts as appropriate for your board. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 6...

  • Page 11: Porting The Linux Kernel

    If you are replacing the P3449 with your own carrier board, look out for "P3449" strings in the DTB and make sure you understand them and replace them according on your needs. 2. Copy the generated DTB to the following directory for flashing: Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 7...
  • Page 12 4. Edit SYSBOOTFILE in <config>.conf to refer to your board. For the detailed information about .dts files, refer to the documentation at Documentation/devicetree/bindings in the NVIDIA released Linux kernel source package. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 8...

  • Page 13: Porting Usb

    Platform Adaptation and Bring-Up Porting USB Jetson Nano can support up to three SuperSpeed USB ports. In some implementations not all of these ports can be used because of UPHY lane sharing among PCIE and XUSB. The Jetson P3449 carrier board is designed and verified for one USB 3.0 port. If you...

  • Page 14: Table 1. Available Outputs For The P3449 Carrier Board

    Nano Product Design Guide for further information before you design your custom board. (Note that Tegra X1 Technical Reference Manual applies to Jetson Nano as well as Jetson TX1.) Lane assignment can be defined by the PCIe subnode under xusb_padctl in the corresponding device tree file.
  • Page 15 { status = "okay" nvidia,function = "xusb"; UPHY lane 0 and UPHY lane 5 are not exposed, and can only be assigned to the Note: pcie-x1 and xusb functions. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 11...

  • Page 16: Required Device Tree Changes

    Required Device Tree Changes This section gives step-by-step guidance for checking schematics and configuring USB ports in the device tree. All of the examples are based on the design of the Jetson Nano P3449 carrier board. For a Host-Only Port This section uses U27, a USB 3.0 Realtek SuperSpeed on-board hub, as an example of a...
  • Page 17 A string containing the name of the function to mux to the pin or group. Must be xusb. The ports Subnode mode • A string that describes USB port capability. A port for USB2 must have this property. It must be one of these values: Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 13...
  • Page 18 U27 based on the device tree structure described above: xusb_padctl: xusb_padctl@7009f000 { pads { usb2 { status = "okay"; lanes { usb2-1 { nvidia,function = "xusb"; status = "okay"; Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 14...
  • Page 19 { nvidia,usb2-companion = <1>; status = "okay"; Under the xusb Node The Jetson Nano xHCI controller complies with xHCI specifications, which support both USB 2.0 HighSpeed/FullSpeed/LowSpeed and USB 3.0 SuperSpeed protocols. • phys Must contain an entry for each entry in phy-names.

  • Page 20: For An Otg (On-The-Go) Port

    Type B plug inserted becomes a B-device (device). Figure 1. An OTG port connector Because its ID pin is floating, J28 is fixed in the device role in the Jetson Nano Note: Developer Kit. It cannot function as a host, e.g. to connect a flash drive, keyboard, or mouse.
  • Page 21 (xHCI) and device driver (xUDC), and can be defined by the state of the ID pin and the VBUS_DETECT pin. Because its ID pin is floating, J28 is fixed in the device role in the Jetson Nano Note: Developer Kit. It cannot function as a host, e.g. to connect a flash drive, keyboard, or mouse.

  • Page 22: Figure 2. Example Of An Otg Port's General Design

    OTG port is operating in the host role. 2. Create a table of GPIO states and their corresponding output cable states like the one in Table 3. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 18...

  • Page 23: Table 3. Gpio States And Corresponding Output Cable States

    GPIO states and their corresponding output cable states. The value is an array of byte values. Each even-numbered byte is a GPIO state, and the following odd- numbered byte is the corresponding output cable state. cable-connected-on-boot • Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 19...
  • Page 24 The USB 2.0 Micro B connector, J28, has the connector’s ID pin floating and the VBUS_DETECT pin of the connector wired out to GPIO00, which corresponds to GPIO_PCC4. Hence J28 can only function in the device role. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 20...
  • Page 25 This is the extcon device node and property list based on the device tree structure described above and the table of GPIO states and corresponding output cable states for GPIO_PCC4, customized for Jetson Nano, where the ID pin is floating the port is fixed in the device role: vbus_id_gpio_extcon: usb_otg { compatible = "extcon-gpio-states";...
  • Page 26 OTG support. Must contain a pointer to the extcon-cable entry for the USB ID pin. When the extcon cable state is 0, the OTG port transitions to the host role. extcon-cable-names • Must be id. #extcon-cells • Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 22...
  • Page 27 = "usb2-0"; nvidia,xusb-padctl = <&xusb_padctl>; status = "okay"; Under the xUDC Node The Jetson Nano xUDC controller supports both USB 2.0 HighSpeed/FullSpeed and USB 3.0 SuperSpeed protocols. These are the device tree node properties that apply to the xUDC node: extcon-cables •...
  • Page 28 Recognized values are: 21-20 0x03 UPHY_LANE4 • 0: PCIE_X1 19-18 0x03 UPHY_LANE3 • 1: USB3_SS 17-16 0x03 UPHY_LANE2 • 3: PCIE_X4 15-14 0x03 UPHY_LANE1 13-0 — Reserved Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 24...

  • Page 29: Fan Speed Control Mapping Table

    140000 150000 160000 170000 180000>; active_hysteresis = <0 15000 9000 9000 10000 0 0 0 0 0>; The fan cooling states are defined by the active_pwm property in the file: hardware/nvidia/platform/t210/porg/kernel-dts/porg-platforms/tegra210- porg-pwm-fan.dtsi Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 25...

  • Page 30: Other Considerations When Porting

    Use a lightweight window manager like LXDE. LXDE takes 3 to 4 seconds to bring • up the desktop after login. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 26...

  • Page 31: Kernel

    • disable it from Kernel Config. If you want to change secondary boot storage to EMMC, you must specify the size of • the EMMC in the appropriate configuration file: Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 27...

  • Page 32: Before Power-On

    Before Power-On Make sure that the Jetson Nano board is connected to the BTB connector correctly and  securely. Verify that power supplies are not shorted to ground or to other power supplies.

  • Page 33: Power

    Using USB-IF procedures, verify that signals meet requirements (correct EYE  height/width, etc). If USB signals do not meet requirements, use the Tegra USB Tuning Guide to adjust  settings until requirements are met. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 29...

  • Page 34: Usb 3.0

    Verify that the processor’s TX/RX/CTS/RTS lines connect to the device’s  RX/TX/RTS/CTS lines for each UART used. Verify that signal quality is acceptable. Look for excessive over/undershoot and  glitches on signal edges. Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 30...

  • Page 35: Sd Card (Sdmmc1)

    PEX (Optional) Verify proper connectivity by checking lanes.  Verify that any implemented PEX interfaces transition to the lowest power state in  Deep Sleep (LP0) and Suspend (LP1). Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 31...

  • Page 36: Embedded Display(S) (Optional)

    Probe MCLK output at recommended test points and verify that signal quality is  acceptable. Look for excessive over/undershoot and glitches on signal edges. Look for excessive over/undershoot and glitches on signal edges.  Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 32...

  • Page 37: Software Bring-Up Checklist

    Platform Adaptation and Bring-Up Software Bring-Up Checklist This section provides a checklist for the software bring-up process. Preparation Verify board BCT.  Verify operation eMMC with the NVIDIA Diagnostic Tool.  Obtain board schematics and component data sheets.  Verify power tree. ...

  • Page 38: System Power And Clocks

     CPU/CORE EDP  GPU EDP  System EDP (containing current monitor and voltage comparator)  Power off  LP0 (optional)  CPU power down (LP2)  BCT, full-speed  Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 34...
  • Page 39 NVIDIA Corporation. Trademarks NVIDIA, the NVIDIA logo, Tegra, Jetson, and Jetson Nano 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.

Table of Contents