Auvidea Jn30d Carrier Board For Nvidia Jetson Nano Owner's Manual

AUVIDEA JN30D Carrier Board for NVIDIA Jetson Nano

Document revisions and changes

Product revisions and changes

Overview

 Jetson compute module
This new JN30D carrier board has been designed primarily for the Jetson Nano compute modules. When using other modules like the Jetson NX power limits may be exceeded as the USB C power supply only supplies up to 3A. More power may be supplied to the board via the two 5V pins on the GPIO header. In this case the USB supply should not be connected.

JN30D 

• Easy integration into passively cooled systems
• Optionally available as a complete system in a passively cooled enclosure
• Easy flashing: just connect a USB OTG cable (Auto Flash)
• High-performance storage: M.2 NVME PCIe x4

Model pictures

The 40-pin GPIO header is included (but not soldered in).

JN30D features and comparison

Technical specifications

Power consumption

Options

• Flexible design and manufacturing
• designed and manufactured in Germany
• in-house fully automated production line with 3D AOI
• special configuration possible with minimum purchase quantity (display port, M.2, PoE, 48V power in, super cap option, 2 RPi camera module connectors, SPI, I2C, switches, etc.)
• design services: you architect your custom carrier board and Auvidea designs and produces it
  • please ask for a quote

Features

GPIO-Header
A 40-pin 2.54mm header for GPIO, I2C, I2S and UART. Die pinout is similar to the GPIO header on the NVIDIA dev kits and on the Raspberry Pi. Please note that all signals (except I2C) have uni-directional level shifters. In other boards, some of these signals may be bi-directional which may cause compatibility issues. Auvidea does not guarantee compatibility to any specific add-on boards. Please check the compatibility yourself. Some signals are 5V tolerant inputs and therefore may be driven from 5V logic outputs.

The 40 pin GPIO header is included (but not soldered in).

Crypto chip
The crypto chip has been added to support software licensing and copy protection. Please check the datasheet of the manufacturer for details.

Model: ATSHA204A-MAHCZ-T
https://ww1.microchip.com/downloads/en/DeviceDoc/ATSHA204A-Data-Sheet-40002025A.pdf

MCU
An MCU for additional power management and watchdog functions is optional. It is standard on some of the extended versions of the JN30D.

Pinout description

Please note that the software GPIO number differs from the socket pin number. This software GPIO number must be computed with a special formula and differs between the various compute modules. Please see appendix B for details.

J3 – Ethernet (GbE)
Standard RJ45 pinout with PoE capable magnetics class 3 and 4 (PD or PSE). Connected to the Ethernet controller on the compute module.

J4 – M.2 PCIEx4 NVME SSDs
Please note that only NVME SSDs are supported. SATA SSDs are not supported. We recommend the 128GB Transcend SSDs (TS128GMTE110S). This SSD is standard in some of the Auvidea development system offerings.

J5 – CSI-2 CD
22 pin 0.5mm pitch FPC connector

J8 – USB 2.0
JST-GH 1.25mm

Internal USB 2.0 JST-GH connector to connect to internal USB 2.0 add-on modules (like U100, U110, U120, etc).

J9 – HDMI 

Standard pinout
CEC is not supported (pin 13 of HDMI connector) Power pin 18 is current limited by PTC fuse (5V 50mA)

J10 – CSI-2 AB
22 pin 0.5mm pitch FPC connector

See further details in the J5 description.

J11 – USB 3.0 – 3.1 

• USB 3.0 Type A standard pinout
• In Rev 1: power control is always on (5V 1A)
• In Rev 2 and up: Controllable with GPIO pin 126 power on[0]/off[1] (default on[0]) (5V 1A)

J12 – USB-C

• Main power input to the carrier board with the 5V 3A USB C power supply.
• Connected with USB 2.0 speed (USB0 bus of the compute module
• Supports device mode and can be used to flash the compute module.
• No overcurrent and no reverse voltage protection were implemented. Power is limited by the USB power supply.
• Alternative 5V powering via the two 5V pins of the GPIO header.

J14 – UART connector
JST-GH 1.25mm

Unidirectional directional 1.8V to 3.3V level shifters and 10 Ohm series resistance (plus ESD protection).

J32 – Button and LED header

CAM_LED: open drain output to drive the cathode of the camera LED.

Controlled by 3 signals which are OR ‘red together:

• J5 pin 5 (CSI CD camera)
• J10 pin 5 (CSI AB camera)
• Compute module GPIO_12: pin 218 (0: LED off, 1: LED on, float: LED on)

CAM_LED flash signal can be used to control the external camera LED. When using external LED please limit currently with an external resistor. Connect the cathode to this pin and anode to 3.3V to 12V power. Maximum current 2A.

J36 – Fan connector
Pico blade 1.5mm

P11 – PoE connector
This connects to the 4 center pins of the ethernet magnetics on the cable side to extract or inject PoE power. This connector may be used for PoE addon solutions.

P12 – GPIO header

Please use any Raspberry Pi hats with care and carefully check compatibility as compatibility was in mind but cannot be guaranteed for all modules.
All GPIO signals are unidirectional (input or output).

U10 – Crypto chip

• Model: ATSHA204A

Integrated for software protection and licensing.
Datasheet Link:
https://ww1.microchip.com/downloads/en/DeviceDoc/ATSHA204A-Data-Sheet-40002025A.pdf.

LED – M.2
Shows M.2 activity.

LED – Eth
Shows Ethernet activity on Socket pin 194 – on[0]/off[1], default: off At own risk resistor can be moved to control Eth-LED via socket pin 188 (link LED)

LED – PWR
Connected to 3.3V power rail. This LED is always on when 3.3V is present on the power rail.

Disclaimer

• Thank you for reading this manual. If you have found any typos or errors in this document, please let us know.
• This is the preliminary version of this data sheet. Please treat all specifications with caution as there may be any typos or errors.
• The Auvidea Team

Copyright notice

Trademarks
NVIDIA, the NVIDIA logo, CUDA, Jetson, Maxwell, Tegra, Nano and VisionWorks are registered trademarks and/or 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.

© Auvidea GmbH 2021

All Rights Reserved
No part of this document or any of its contents may be reproduced, copied, modified or adapted, without the prior written consent of the author, unless otherwise indicated for stand-alone materials.

You may share this document by any of the following means: this PDF file may be distributed freely if no changes or modifications to the document are made. For any other mode of sharing, please contact the author at the email below. [email protected] Commercial use and distribution of the contents of this document is not allowed without express and prior written consent of Auvidea GmbH.

Appendix

Appendix A [CSI-Cameras]

Camera connection example
CSI cameras can connect to J5-CSI-2-CD and J19–CSI-2-AB connectors as shown below.

Appendix B [GPIO]

GPIO control
This example shows how to set and read out GPIO 414. For different GPIO numbers replace 414 accordingly.

Export GPIO 

• nvidia@nvidia-desktop:~$ echo 414 > /sys/class/gpio/export
• nvidia@nvidia-desktop:~$

Change direction to in

• nvidia@nvidia-desktop:~$ echo in > /sys/class/gpio/gpio414/direction
• nvidia@nvidia-desktop:~$

Change direction to out

• nvidia@nvidia-desktop:~$ echo out > /sys/class/gpio/gpio414/direction
• nvidia@nvidia-desktop:~$

Set GPIO low

• nvidia@nvidia-desktop:~$ echo 0 > /sys/class/gpio/gpio414/value
• nvidia@nvidia-desktop:~$

Set GPIO high

• nvidia@nvidia-desktop:~$ echo 1 > /sys/class/gpio/gpio414/value
• nvidia@nvidia-desktop:~$

Readout GPIO value

• nvidia@nvidia-desktop:~$ cat /sys/class/gpio/gpio414/value
  0
• nvidia@nvidia-desktop:~$ cat /sys/class/gpio/gpio414/value
  1

Pin to GPIO reference sheet for Xavier-NX/Nano/TX2-NX

This information is provided as is from Auvidea. Auvidea does not guarantee correctness but believes the numbers are correct. If you see any wrong information, please let us know so we can correct the documentation.

How to calculate GPIOs
The above list should include every GPIO there is. This “how to” may help you find errors we did in our documentation ore to calculate GPIOs for upcoming models as the NVIDIA Jetson Orin.

GPIOnumber
The basic formula:

• GPIOnumber = GPIOletter + 8 +GPIOdigit + GPI0offset

GPIOletter
The GPIOletter is located between [GPIO3_P] and [.digit]

• This letter needs to be referenced to a number.
• This number is individual to every Jetson module and can be found in the “tegra-gpio.h” (name may differ depending on the module).
• Pleas also see the example table shown in GPIOoffset

GPIOdigit
The GPIOdigit is easiest to get and can be extracted directly from the name. GPIO3_PO.[GPIOdigit]

GPIOoffset
The offset is connected to the GPIOletter. The same GPIOletter has always the same GPIOoffset for one specific module and only differs for AON cores. GPIOoffsets are listed later in the table.

Example
Calculating GPIO number GPIO3_PO.01 for Jetson Xavier NX:

• GPIOnumber = GPIOletter * 8+ GPIOdigit +GPIOoffset
• GPIOnumber = 401 = 14 *8 + 1+ 288

Appendix C [I2C]

I2C device bus
I2C Examples of configurations and how to use.

I2C usage of devices and registers
List i2c devices on a specific bus

• Syntax: i2cdetect [options] <busNr>

Dump i2c device registers
Syntax: i2cdump [options] <busNr> <deviceAddress>

Set register value:
Syntax: i2cset [options] <busNr> <deviceAddress> <register> <address> <value>

• test@test-desktop:~$ sudo i2cset -y -f 8 0x76 0x06 0x00
• test@test-desktop:~$

Set register value:
Syntax: i2cset [options] <busNr> <deviceAddress> <register> <address> <value>

• test@test-desktop:~$ sudo i2cset -y -f 8 0x76 0x06 0x00
• test@test-desktop:~$

Read register value:
Syntax: i2cget [options] <busNr> <deviceAddress> <register> <address>

• test@test-desktop:~$ sudo i2cget -y -f 8 0x76 0x06 0x00
• test@test-desktop:~$

Test IMX219 camera stream
The parameter `sensor-id=` describes the camera target. This id can be found by using `ls /dev/`. If the camera is correctly plugged in then there should be a device called `/dev/videoX`, where X is the camera id.

• test@test-desktop:~$ gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! ‘video/x-raw(memory:NVMM), width=(int)1280, height=(int)720, format=(string)NV12, framerate=(fraction)30/1’ ! nvvidconv! queue! xvimagesink