NVIDIA Announces Jetson AGX Xavier

External Media

NVIDIA is pleased to announce Jetson AGX Xavier, the latest addition to the Jetson platform with greater than 10x the energy efficiency and more than 20x the performance of it’s predecessor, Jetson TX2. It’s an AI computer for autonomous machines, delivering the performance of a GPU workstation in an embedded module under 30W. With multiple operating modes at 10W, 15W, and 30W, Jetson Xavier has a peak performance of more than an incredible 30 TOPS (teraops) of mixed-precision FP32/FP16/INT8 performance. Please refer to the FAQ for further information.

Check out our latest blog, and to order see here.

Technical Specs

  • GPU — 512-core Volta GPU with Tensor Cores
  • DL/ML Accelerator — (2x) NVIDIA Deep Learning Accelerator (DLA) Engines (NVDLA.org)
  • CPU — 8-core ARMv8.2 64-bit CPU, 8MB L2 + 4MB L3
  • Memory — 16GB 256-bit LPDDR4x | 137 GB/s
  • Storage — 32GB eMMC 5.1
  • Vision Accelerator — 7-way VLIW processor
  • Video Encode — (2x) 4Kp60 | HEVC
  • Video Decode — (2x) 4Kp60 | 12-bit support
  • Mechanical — 100mm x 87mm with 16mm Z-height (699-pin board-to-board connector)


  • Display — 3x eDP/DP/HDMI at 4Kp60 | HDMI 2.0, DP HBR3
  • Camera — 16x CSI-2 Lanes (40 Gbps in D-PHY V1.2 or 109 GBps in CPHY v1.1) 8x SLVS-EC lanes (up to 18.4 Gbps) Up to 16 simultaneous cameras
  • PCIe — 5x 16GT/s gen4 controllers | 1x8, 1x4, 1x2, 2x1 (3x) Root Port + Endpoint (2x) Root Port
  • USB — (3x) USB 3.1 (10GT/s) (4x) USB 2.0 Ports
  • Ethernet — Gigabit Ethernet-AVB over RGMII
  • Other I/Os — UFS, I2S, I2C, SPI, CAN, GPIO, UART, SD

Jetson Xavier Developer Kit

The Jetson Xavier Developer Kit is currently able to be ordered from the NVIDIA webstore in the following countries:

  • US, Canada, UK, France, Germany, Italy, Poland, Spain, and China

Additionally, orders can be placed through distributors for:

  • Japan, Europe, Israel, and Turkey (other regions to follow soon)

Initial orders will be fulfilled on a first-come first-served basis within an estimated six-week time period beginning early September 2018.
The price of the devkit for Registered Developers is $1,299 (limit 1 unit per Registered Developer, prices vary by region). Anyone can qualify for the special price by registering an account at developer.nvidia.com. Additional units are available in quantities 1-10 at $2,499 and quantities >10 are $1,599.

Documentation & Resources

FAQ — https://developer.nvidia.com/embedded/jetson-xavier-faq
Blog — https://news.developer.nvidia.com/nvidia-jetson-agx_xavier-developer-kit-now-available/
Order — https://developer.nvidia.com/embedded/buy/jetson-xavier-devkit?ncid=so-int-jnxrpr-57255

Is this correct?

PCIe — 5x 16GT/s gen<b>4</b> controllers

…that would be astonishing…that amount of throughput would exceed any desktop PC currently out…current PCs only go to gen3. I’ve not seen anything other than demo technology for this so far, so that would mean this Jetson will probably be the first practical device to support this (someone else might come out with gen4 before then…we’ll have to wait and see).

Indeed it is gen4. :)

Some of it’s PCIe controllers even support endpoint mode in addition to root complex, so you can more easily tie multiple devices together over PCIe.

“Mechanical — 100mm x 87mm with 16mm Z-height”

Can it be confirmed that the module sits flush with the carrier PCB - i.e. the top of the module is 16mm above the PCB when the 669-circuit connector is mated?

Also, while early access starts in August, when will more complete documentation for the module itself become available - NDA access?


Yes, and including the height of the thermal transfer plate on top of the module.

Preliminary documentation will be available starting at the time of Early Access.

I am very excited about this. I am wondering whether VisionWorks will be supported in this board or not. Could you please let us know about the plans of NVIDIA to support VisionWorks and other SDKs that has been previously supported in TX2 and TX1 in this new platform?

Hi hmd88, yes VisionWorks will be available as well as other JetPack components like with TX1/TX2.

I need to connect 16 12MP cameras like this one: VLXT-123C.I | Industrial cameras / LX series | Baumer Italy. The connection is a 10gig ethernet. Each generate a stream of 8Gb/s

I have 3 questions:

  1. can the interface provided manage at least 8 of them? So I’d put 2 Xavier in parallel to manage them all. Maybe I might use the PCIs, using two 4 ports ethernet PCI cards…

  2. Xavier boasts (2x) 4Kp60 | HEVC video decoding. 4k is too little for 12MP…can I split the 8 cameras video stream in 2, and encode the upper and lower part of the images in 2 separate videos, leveraging the HW encoder?

  3. Can it encode 16 video streams (2x8) at the same time? The camera stream is at 64fps. I might lower it to 60 so that it fits Xavier’s 60Hz limit.

Thank you!

Hi sergio.negri, yes the 16-lane CSI interface can handle eight 2-lane cameras, not sure if your 12MP camera will operate in x2.

You can encode more independent streams, as long as you don’t exceed the total pixel-per-second limit (resolution * FPS) of dual 4Kp60.

UPDATE: devkit I/O specs have been posted here: [b][url]https://developer.nvidia.com/jetson-xavier-devkit[/url][/b]

Hi Dustin,

Can you clarify how many USB ports are exposed on the Xavier’s DevKit? Looking at videos from Computex, it looks like there’re two USB type C connectors on the same side as 40pin header, and there’s another USB type C connector on the opposite side? Does it mean it has only three USB connectors? Of course, there’s a PCIe slot which can be used by various PCIe USB cards… Also, where is M.2 Key M connector located? Is it sandwiched between Xavier module and DevKit carrier board?


Regarding the USB ports on the devkit, there are:

  • 2x USB-C 3.1, one of which can be used for flashing & power delivery (and normal operation too)
  • 1x USB 3.0 / eSATAp hybrid
  • 1x micro-USB 2.0

Technically the M.2 key-E also provides USB 2.0, if you have an M.2 breakout board that can access it (instead of using for wireless/WiFi).

Yes, the M.2 is sandwiched between the module and the carrier. You can fit an M.2 SSD/NVMe module in there.

I am curious…of the USB3 and USB3.1 ports, do they all have their own root HUBs?

Great! Hopefully something like this will work for adding an extra USB2 port and PCIe 1x slot:


And then we can add something like this for additional 4 USB3.0 ports:



1 Like

The two USB-C 3.1’s are root ports. The USB3 from the hybrid USB/eSATAp port is implemented as a hub over PCIe, so it’s essentially a root port too.

1 Like

PCIe cards that have up-to-date driver support for recent Linux kernels, that build without issue on ARM architectures, should work just fine.

Hey guys, want to take a closer look at the devkit? Check out our walkthrough video with Jetson Program Manager, Phil Lawrence!

[url]NVIDIA Jetson AGX Xavier Developer Kit - Introduction - YouTube

I am curious about the SPDI connector which looks like a micro-USB connector. Does this actually use USB (e.g., serial UART) for audio data, or is it perhaps customized and passes a balanced AES3 signal directly through (meaning an alternate connector versus what is usually scene, but still equivalent to the larger pro studio connector)? For reference on the normal AES3 style connector:
[url]AES3 - Wikipedia
[url]AES3 - Wikipedia

I think you mean the FTDI port — this is via the only micro-USB connector.

The high-def audio signals are broken out on a pin header on the underside of the carrier board.

At around 2:23 into the video he shows the micro-USB connector, and this is what I heard:
“…and this micro-USB connector is actually an SPDI serial connection.”

So…he was really saying “FTDI” instead of “SPDI”…I should have known! Makes much more sense. On the other hand, I was rather excited that special support might be added for audio. This is one of my original interests, but limitations on the TK1/TX1/TX2 i2s channels limited options. Incidentally though, is there more than one i2s or other capability to go beyond two channel digital audio?