NVIDIA DRIVE AGX Orin and Thor Developer Kit Cables Guide
NVIDIA DRIVE AGX Orin and DRIVE AGX Thor Developer Kits use a wide range of USB, power, automotive Ethernet, camera splitter, adapter and vehicle harness cables. This guide helps developers identify each cable, understand where it connects on the rear panel, and choose the right cable set for bench development or in-vehicle integration.
- NVIDIA uses the official product names DRIVE AGX Orin Developer Kit and DRIVE AGX Thor Developer Kit.
- Orin cable sets commonly include AC power, Micro USB, USB Type-A to Type-C, USB Type-C to Type-C, MATE-AX camera splitter, H-MTD splitter, MATEnet splitter and 1GbE adapter cables.
- DRIVE AGX Thor should be shown as two product configurations: SKU 10 for bench development and SKU 12 for in-vehicle development.
- The most important cable groups are USB debug/flashing cables, H-MTD automotive Ethernet cables, MATE-AX/FAKRA camera cables and vehicle harness cables.
- For real projects, always match the cable to the exact rear-panel port, target sensor, Ethernet speed, power input and development scenario.
Definition: A DRIVE AGX developer kit cable solution is the complete set of power cables, USB debug and flashing cables, GMSL camera splitter cables, H-MTD or RJ45 Ethernet adapters, and vehicle harnesses used to connect an NVIDIA DRIVE AGX Orin or Thor Developer Kit to host PCs, displays, networks, cameras, sensors and vehicle systems.
📋 Contents
How to Use This Cable Guide
When engineers first receive a DRIVE AGX Orin or Thor Developer Kit, the most common setup question is simple: which cable is this, and where does it connect? The answer depends on three factors: the developer kit model, the rear-panel port, and the development scenario.
For bench development, the essential cables are usually power, USB, DisplayPort and network adapters. For camera bring-up, MATE-AX, FAKRA and GMSL-related splitter cables become more important. For in-vehicle work, the vehicle harness is the center of the system because it combines power, CAN, Ethernet and sensor routing into a vehicle-ready assembly.
Practical tip: Start from the rear panel, not from the cable box. Identify the target port first, then select the matching cable. This avoids most connection mistakes during first-time bring-up.
Rear Panel Overview: Match the Cable to the Port First
The rear panel is the best starting point for cable identification. DRIVE AGX systems expose standard development interfaces such as USB and DisplayPort together with automotive interfaces such as H-MTD, MATE-AX, MATEnet and FAKRA-related camera connections.
Figure 1. DRIVE AGX Orin Rear Panel Connector Layout
Figure 2. DRIVE AGX Thor SKU 10 Rear Panel Connector Layout
Figure 2. DRIVE AGX Thor SKU12 Rear Panel Connector Layout
In practical terms, every cable in this guide belongs to one of six connection groups: power input, USB debug/flashing, display output, Ethernet/networking, camera/sensor input and vehicle harness integration.
DRIVE AGX Orin Developer Kit Cable Set
Note: Cable and accessory contents may vary by developer kit version, region and NVIDIA accessory availability. Always verify the exact kit BOM before ordering or publishing a final parts list.
The DRIVE AGX Orin Developer Kit is commonly used for bench development. For in-vehicle development, a separate vehicle accessory kit or vehicle harness may be required depending on the project configuration.
| Cable / Adapter | Typical Function | Developer Notes |
|---|---|---|
| AC Power Cable | Main power input | Availability can depend on developer kit version and region. |
| USB Type-A to Micro-USB Cable | Debug / console access | Used for low-level bring-up, logging and setup tasks. |
| USB Type-A to Type-C Cable | Host connection / flashing workflow | Connects the developer system to an Ubuntu host PC. |
| USB Type-C to Type-C Cable | Host connection | Useful when the host PC supports USB-C directly. |
| MATE-AX Camera Splitter Cable | GMSL camera breakout | Often used to break out camera channels to FAKRA-style camera-side connectors. |
| Dual H-MTD Splitter Cable | Automotive Ethernet breakout | Used for H-MTD-based network connections. |
| Quad H-MTD Splitter Cable | Multi-port automotive Ethernet breakout | Useful when multiple Ethernet links are required in a bench setup. |
| MATEnet Splitter Cable | 100BASE-T1 style automotive Ethernet breakout | Used for vehicle-network-oriented Ethernet connections. |
| 1GbE NIC Adapter | H-MTD / automotive Ethernet to RJ45 development access | Helps connect the kit to standard lab Ethernet equipment. |
Note: Cable and accessory contents may vary by developer kit version, region and NVIDIA accessory availability. Always verify the exact kit BOM before ordering or publishing a final parts list.
DRIVE AGX Thor Developer Kit Cable Set: SKU 10 and SKU 12
DRIVE AGX Thor should not be treated as a single generic product in a cable guide. It has two important developer kit configurations: DRIVE AGX Thor Developer Kit SKU 10 for bench development and DRIVE AGX Thor Developer Kit SKU 12 for in-vehicle development. For cabling, this distinction matters because SKU 10 focuses on lab setup, while SKU 12 requires vehicle-oriented power and harness planning.
Thor SKU 10 vs SKU 12
| Item | SKU 10 - Bench Development | SKU 12 - In-Vehicle Development |
|---|---|---|
| Development environment | Lab bench, desk setup, software bring-up | Prototype vehicle, sensor vehicle, in-vehicle validation |
| Power input | AC power input | DC power input |
| USB cables | Type-A to Type-C and/or Type-C to Type-C | Type-A to Type-C and/or Type-C to Type-C |
| Ethernet adapter | 1GbE H-MTD to RJ45 adapter for lab networking | 1GbE adapter plus vehicle-side Ethernet branches |
| Vehicle harness | Normally not the focus | Required for vehicle power, CAN, Ethernet and sensor routing |
| Typical cable priority | Debug, flashing, display, Ethernet lab access | Vehicle harness, sealed routing, strain relief, sensor trunks |
Thor rear-panel USB ports are important during first-time setup. A common workflow uses one USB Type-C connection for the DEBUG port and another USB Type-C connection for the U2 port used in recovery-mode flashing.
USB Debug and Flashing Cables
USB cables are usually the first cables used during bring-up. They connect the DRIVE AGX developer system to an Ubuntu host PC for console access, debugging, flashing or recovery-mode operations.
| USB Cable | Used With | Main Use |
|---|---|---|
| USB Type-A to Micro-USB | Primarily Orin | Debug console and early bring-up access. |
| USB Type-A to Type-C | Orin / Thor | Host PC connection, debug access or flashing workflow depending on the target port. |
| USB Type-C to Type-C | Orin / Thor | Direct USB-C connection between host PC and developer kit when supported. |
Setup Note
Do not treat all USB-C ports as interchangeable. On Thor, the port labeled DEBUG and the port labeled U2 serve different setup roles. Always follow the rear-panel label and the hardware quick start guide for the specific kit.
Automotive Ethernet Cables and Adapters
Automotive Ethernet cabling is one of the main differences between a standard embedded development board and a DRIVE AGX developer platform. DRIVE AGX systems may expose H-MTD and MATEnet automotive Ethernet interfaces in addition to standard RJ45 Ethernet ports.
H-MTD Splitter Cables
H-MTD splitter cables break out multi-port automotive Ethernet connectors into individual Ethernet branches. They are used when connecting the developer kit to automotive Ethernet sensors, media converters, test equipment, switches or vehicle network branches.
1GbE H-MTD to RJ45 Adapter
A 1GbE H-MTD to RJ45 adapter is useful for lab development because it allows a DRIVE AGX automotive Ethernet port to connect into a more familiar RJ45-based development environment. This is commonly used for bench networking, data logging, software bring-up and connection to existing lab infrastructure.
Important: Confirm the exact Ethernet speed and physical layer before ordering an adapter. A cable or adapter intended for 1GbE development should not be assumed to work for 10GBASE-T1 without the correct active conversion and matching equipment.
Camera and Sensor Interface Cables
Camera cabling is central to DRIVE AGX development. Orin supports multi-camera GMSL development, while Thor expands the I/O ecosystem for next-generation sensor workloads. Camera cables are usually the most visually distinctive cables in the kit because they often fan out from a high-density connector to multiple FAKRA-style camera connectors.
| Cable Type | Typical Connector Direction | Use Case |
|---|---|---|
| MATE-AX Camera Splitter Cable | Developer kit high-density port to multiple camera connectors | GMSL camera bring-up and multi-camera testing. |
| MATE-AX x4 to FAKRA Cable | MATE-AX on system side, FAKRA on camera side | Camera module connection, sensor validation and ADAS perception testing. |
| Custom Camera Harness | Project-specific sensor connectors and lengths | Prototype vehicle routing, roof/bumper camera trunks and fleet builds. |
- Connector matching. Match MATE-AX, Mini-Fakra, FAKRA or other camera-side connectors to the exact sensor module.
- Cable length. Bench cables can be short; vehicle camera trunks must follow the actual vehicle routing path.
- Shielding and EMC. Camera cables should be specified with shielding appropriate for the bench, chamber or vehicle environment.
- Mechanical strain relief. Avoid tight bends and unsupported branches close to the connector shell.
Field note: If a camera link is unstable, check the cable part number, connector mating, bend radius, shielding and PoC-related design before replacing the camera or developer kit.
Power and Vehicle Harness: Bench vs In-Vehicle
Power and vehicle harness requirements change significantly between bench and vehicle use. A bench setup normally uses a simple AC power cable, USB cables and short adapters. A vehicle installation must consider DC power, ignition behavior, CAN access, Ethernet routing, sensor cable trunks, mechanical retention and serviceability.
| Requirement | Bench Cable Set | In-Vehicle Harness |
|---|---|---|
| Power | AC input or bench power setup | Vehicle DC input, fuse strategy and ignition behavior |
| Cable length | Short, easy to replace | Vehicle-routed and measured from actual installation points |
| Sealing | Usually not required | Required at vehicle penetration points and exposed areas |
| Strain relief | Recommended | Required for each branch and connector exit |
| Service labels | Optional | Strongly recommended for fleet debugging and replacement |
| Typical users | Software, platform and lab engineers | Vehicle integration, sensor, validation and fleet teams |
For Thor SKU 12 or vehicle-oriented Orin projects, the harness should be treated as an engineered assembly rather than a bundle of individual cables. The best RFQ package includes an interface list, vehicle routing diagram, cable length table, sealing requirement, shielding requirement and quantity forecast.
Quick Comparison: Orin vs Thor Cable Planning
| Planning Item | DRIVE AGX Orin Developer Kit | DRIVE AGX Thor Developer Kit |
|---|---|---|
| Best starting point | Bench setup and existing ADAS development programs | Next-generation bench and in-vehicle development |
| USB focus | Micro-USB plus USB-C cables depending on workflow | USB-C ports for DEBUG and recovery-mode flashing workflows |
| Camera cabling | MATE-AX camera splitter and GMSL camera connections | MATE-AX x4 and FAKRA-style high-density camera cable planning |
| Ethernet cabling | H-MTD, MATEnet and RJ45 adapter-oriented bench networking | H-MTD quad / 6-port Ethernet and 1GbE adapter workflows |
| Vehicle harness | Usually accessory-dependent | Central to SKU 12 in-vehicle development |
Recommended Images to Add to This Guide
For best SEO and readability, place one image close to the paragraph where the cable is explained. Use descriptive image filenames and alt text instead of generic names such as IMG_001.
- Orin rear panel image: use near the rear panel overview section.
- Thor rear panel image: use near the SKU 10 / SKU 12 discussion.
- USB cable images: use in the debug and flashing cable section.
- H-MTD splitter images: use in the automotive Ethernet section.
- MATE-AX / FAKRA images: use in the camera and sensor interface section.
- Vehicle harness image: use in the bench vs in-vehicle harness section.
Frequently Asked Questions
What is the correct product name: DRIVE AGX Orin Developer or DRIVE AGX Orin Developer Kit?
The correct product-style wording is NVIDIA DRIVE AGX Orin Developer Kit. The same naming pattern applies to NVIDIA DRIVE AGX Thor Developer Kit.
What cables are most important for first-time DRIVE AGX setup?
The first cables to identify are the power cable, USB debug cable, USB flashing cable, optional DisplayPort cable and Ethernet adapter. After the system is running, camera and vehicle harness cables become more important.
What is the difference between Thor SKU 10 and SKU 12 from a cabling perspective?
SKU 10 is for bench development and uses an AC power input. SKU 12 is for in-vehicle development and uses a DC power input, so vehicle harness planning becomes much more important.
What is an H-MTD to RJ45 adapter used for?
It is used to connect an automotive Ethernet interface on the DRIVE AGX system to RJ45-based lab infrastructure. Before ordering, confirm the target Ethernet speed and whether active media conversion is required.
Can custom cables be made for DRIVE AGX Orin and Thor?
Yes. Common custom assemblies include MATE-AX to FAKRA camera cables, H-MTD Ethernet cables, H-MTD to RJ45 adapter cables and full vehicle harnesses with project-specific length, labeling, shielding and branch layout.
📚 Authority References
- NVIDIA - DRIVE AGX Developer Kits - Official DRIVE AGX Orin and Thor Developer Kit overview, I/O and accessory information.
- NVIDIA DRIVE AGX Orin Developer Kit Hardware Quick Start Guide - Orin hardware list, accessory list and rear-panel setup guidance.
- NVIDIA DRIVE AGX Thor Developer Kit Hardware Quick Start Guide - Thor SKU, power input, USB setup and rear-panel setup guidance.
- NVIDIA DRIVE Documentation - Product documentation page for DRIVE AGX platforms, DriveOS and developer resources.
Need a Custom DRIVE AGX Cable, Adapter or Vehicle Harness?
Send us your interface list, developer kit model, cable lengths, routing notes, shielding requirement, sealing requirement, quantity and target delivery window. A good RFQ should identify both sides of each cable: the DRIVE AGX port and the sensor, host, switch, display or vehicle-side connector.
- Not sure which connector fits your sensor side? Send the camera, radar, lidar or ECU model number.
- Need an H-MTD to RJ45 adapter? Confirm the target Ethernet speed and whether a media converter is required.
- Building an in-vehicle harness? Provide routing sketches, branch lengths and labeling requirements.
Source DRIVE AGX Orin & Thor Cable Assemblies
Premier Cable supports GMSL camera cables, MATE-AX to FAKRA cables, H-MTD automotive Ethernet cables, H-MTD to RJ45 adapters and custom vehicle harness assemblies for DRIVE AGX Orin and Thor development programs. Standard and custom assemblies are available for bench testing, prototype integration and in-vehicle validation.
