DRIVE AGX Thor and Orin Cable, Connector and Harness Solutions
DRIVE AGX Thor and DRIVE AGX Orin developer kits drive multi-camera perception, automotive Ethernet, lidar, radar and CAN networks at the same time. The cables, adapters and vehicle harnesses connecting them decide whether a bring-up succeeds the first time. This guide covers what the kits expose, what cabling each interface requires, and when a custom assembly is the right answer.
- DRIVE AGX Thor Developer Kit ships in two SKUs: SKU 10 for bench development, SKU 12 for in-vehicle development.
- Thor automotive I/O includes 16x GMSL2 + 2x GMSL3 camera ports and 3x 100/1000/10G-T1 automotive Ethernet on H-MTD connectors (per NVIDIA).
- DRIVE AGX Orin exposes 16 GMSL camera ports and multiple automotive Ethernet interfaces, with NVIDIA listing up to 30 Gb/s of total Ethernet data transmission.
- The three cable categories that matter: GMSL camera cables, H-MTD Ethernet (with optional H-MTD-to-RJ45 adapter), and a routed vehicle harness.
- Length, shielding and connector mating are the variables most likely to break a first-time bring-up.
Definition: A DRIVE AGX cable and harness solution is the set of GMSL camera cables, H-MTD or RJ45 automotive Ethernet cables, power cables and vehicle harnesses used to connect an NVIDIA DRIVE AGX Thor or Orin developer kit to cameras, sensors and vehicle networks during ADAS and autonomous driving development.
📋 Contents
Why DRIVE AGX Cabling Is Different from Standard Embedded Wiring
DRIVE AGX developer kits are not lab evaluation boards. They drive multi-camera perception, lidar, radar and CAN networks at the same time, often inside a moving test vehicle.
A typical DRIVE AGX bring-up involves a large number of camera links, multiple automotive Ethernet branches and a vehicle-side power and CAN connection. Any single cable that fails on impedance, shielding or mating tolerance can show up later as a dropped frame, a lost sensor packet or a CAN bus error during a test drive.
For this reason, DRIVE AGX cable design has to balance three things at once: high-speed signal integrity for GMSL and automotive Ethernet, automotive-grade mechanical durability against vibration and sealing requirements, and vehicle routing constraints such as length, bend radius and harness branching.
MATE-AX x4 to FAKRA Splitter - GMSL Camera Breakout
Rear Panel Connectors - In-Vehicle Developer System
DRIVE AGX Thor: Interface Map and Cable Requirements
DRIVE AGX Thor is NVIDIA's production-class autonomous vehicle compute platform. NVIDIA's DRIVE AGX page lists two developer kit SKUs that serve different stages of the development cycle.
Thor SKU 10 vs SKU 12
| Item | SKU 10 (Bench) | SKU 12 (In-Vehicle) |
|---|---|---|
| Use case (per NVIDIA) | Bench development | In-vehicle development |
| Camera ports | 16x GMSL2 + 2x GMSL3 | 16x GMSL2 + 2x GMSL3 |
| Automotive Ethernet | 3x 100/1000/10G-T1, H-MTD (quad and 6-port) | 3x 100/1000/10G-T1, H-MTD (quad and 6-port) |
| Display | 1x DisplayPort up to 4K@60Hz | 1x DisplayPort up to 4K@60Hz |
| Typical cabling focus | Adapter cables, short bench leads, lab-side connectivity | Sealed vehicle harness, routed trunks, vehicle power and CAN |
I/O list per NVIDIA DRIVE AGX official page (developer.nvidia.com/drive/agx).
For Thor, three cable categories cover most projects:
Camera Cables
Thor camera ports use the GMSL family. GMSL2 (Analog Devices) operates at up to 6 Gbps on the forward channel and 187.5 Mbps on the reverse channel; GMSL3 operates at 12 Gbps forward and 187.5 Mbps reverse, using PAM4 encoding. Connector choice on the kit side and camera side is typically Fakra (single coax) or Mini-Fakra / MATE-AX (multi-channel in one shell). The exact connector pairing depends on the camera module being used.
Automotive Ethernet Cables
Thor exposes 100BASE-T1, 1000BASE-T1 and 10GBASE-T1 over H-MTD connectors. For lab use, an H-MTD-to-RJ45 adapter cable is typically needed to talk to standard switches and test equipment, often paired with a media converter on the higher-speed links.
Vehicle Harness
A Thor SKU 12 vehicle harness usually bundles vehicle power, ignition signal, CAN/CAN-FD, multiple H-MTD Ethernet branches and the GMSL camera trunk into a single routed assembly with grommets and mounting brackets. The exact branch count and length is project-specific.
DRIVE AGX Orin: Interface Map and Cable Requirements
DRIVE AGX Orin remains widely deployed and is still the primary compute platform for many active ADAS programs. NVIDIA's DRIVE AGX page lists Orin with 16 GMSL camera ports and multiple automotive Ethernet interfaces, with up to 30 Gb/s of total Ethernet data transmission.
| Item | DRIVE AGX Orin Developer Kit |
|---|---|
| Camera ports | 16 GMSL camera ports (per NVIDIA) |
| Automotive Ethernet | Multiple interfaces, up to 30 Gb/s total data transmission (per NVIDIA) |
| Vehicle interfaces | CAN; vehicle harness accessory available |
| Typical cabling focus | GMSL camera cable, H-MTD-to-RJ45 adapter, vehicle harness |
Orin camera cables are most often used for surround-view, front-view and side-view multi-camera setups. Because GMSL serial links carry control and Power-over-Coax (PoC) on the same cable, both signal integrity and DC behavior of the cable matter.
For Ethernet, an Orin H-MTD-to-RJ45 adapter cable is the standard way to bridge the kit to a lab Ethernet switch, a data logger or an automotive Ethernet media converter. Specific adapter selection depends on which Ethernet interface on the kit is being used and what target test equipment is on the other end.
Camera Cable Design Notes for DRIVE AGX
Camera cabling is where most DRIVE AGX bring-ups either pass or fail on day one. Five engineering parameters drive the result.
- Impedance. GMSL coax cables are designed around 50 Ω nominal characteristic impedance. Using a 75 Ω cable in a 50 Ω system is a common procurement mistake and will cause link instability.
- Shielding. Double-shielded coax (foil + braid) is the typical choice for in-vehicle GMSL cables, both for signal integrity and EMC. Single-shielded variants may be used only for short bench cables.
- Bend radius. Mini-Fakra and MATE-AX assemblies have manufacturer-specified minimum bend radii; tight zip-tying near the connector shell is one of the more frequent root causes of intermittent links. Always check the connector vendor's datasheet for the specific minimum.
- PoC behavior. GMSL2 and GMSL3 links typically carry PoC to power the camera module. The actual PoC voltage and current depend on the camera and the ser/des design, not on the cable alone. The cable's DC resistance and the PoC inductor on each end must be specified together with the system, not chosen in isolation.
- Connector mating cycles. Automotive RF connectors (Fakra, Mini-Fakra/HFM, H-MTD) have a specified mating cycle limit defined by the connector vendor's datasheet. Bench projects that repeatedly plug and unplug should track this against the spec to avoid contact wear.
⚠️ Field experience: When a GMSL link drops frames intermittently, the three most common root causes are: wrong cable impedance (75 Ω instead of 50 Ω), violation of the connector's minimum bend radius near the shell, and PoC inductor mismatch at the cable interface. Check these three before suspecting the camera or the developer kit.
Ethernet and Adapter Cable Options
DRIVE AGX Ethernet cabling has two distinct use modes.
In-Vehicle Automotive Ethernet (H-MTD to H-MTD)
Used between the developer kit and vehicle switches, lidar units, radar sensors or other ECUs. The cable is typically shielded twisted pair, 100 Ω differential, supporting BASE-T1 variants per IEEE 802.3bp (1000BASE-T1) and IEEE 802.3ch (Multi-Gig Automotive Ethernet, including 10GBASE-T1).
Lab Ethernet (H-MTD-to-RJ45 Adapter)
Used to connect the kit to a standard office or lab switch, a PC NIC or a logging server. A common procurement mistake: ordering an H-MTD-to-RJ45 cable for a 10GBASE-T1 port and expecting it to link with an RJ45 port on a standard 10GBASE-T switch. RJ45 ports on standard switches do not natively understand BASE-T1 framing, so a passive adapter cable alone will not establish the link at multi-gig speeds; an active media converter is normally required.
⚠️ Important: Always confirm the target Ethernet speed (100 / 1000 / 10G BASE-T1) before specifying an adapter. A passive H-MTD-to-RJ45 cable that works at 100BASE-T1 with a media converter will not transparently bridge a 10GBASE-T1 port to a 10GBASE-T RJ45 switch.
Vehicle Harness: Bench vs In-Vehicle
The harness changes character completely between bench and vehicle environments. Specifying a bench-style harness for a vehicle install is one of the most expensive mistakes in this category.
| Requirement | Bench Harness | In-Vehicle Harness |
|---|---|---|
| Length | Short, project-specific | Project-specific, vehicle-routed |
| Sealing | Typically none | Sealing required at vehicle penetration points |
| Strain relief | Optional | Required at every branch |
| Power | Bench PSU pigtail | Fused, ignition-switched vehicle power |
| CAN | Single drop typical | Multi-drop with proper termination |
| Mounting | Loose | Brackets, grommets, P-clips |
A well-designed in-vehicle harness for DRIVE AGX Thor SKU 12 typically routes the GMSL camera trunk along structural pillars or the roof liner, the H-MTD Ethernet through the center console area, and the power and CAN branch toward the OBD area or a dedicated fuse tap. The exact routing is always vehicle-specific.
When to Order a Custom Cable Assembly
A custom assembly makes sense when at least one of these is true:
- Length and routing. Cable length needs to be cut and terminated to a vehicle-specific routing path. This is the single most common driver.
- Cross-standard connector pairing. For example MATE-AX on the camera side mating to Fakra or HSD on a legacy sensor side.
- Tighter EMC or shielding spec. For vehicles with sensitive RF environments or strict OEM EMC requirements.
- Fleet traceability. The project needs labeled, serialized harnesses for fleet deployment and field service.
Custom DRIVE AGX cable assembly orders are quoted against three inputs: an interface list (which Thor or Orin ports, which sensor/host on the other side), a length and routing diagram, and a target shielding or EMC class.
📩 What to Send With Your RFQ
Interface list (Thor/Orin port + sensor/host port) · Cable lengths and routing notes · Required shielding/EMC class · Sealing class (if in-vehicle) · Quantity and target delivery window. Premier Cable returns a quoted assembly drawing and material list against this input.
Typical Applications
DRIVE AGX cable and harness solutions are used across the ADAS development cycle. The hardware does not change much between use cases - what changes is harness length, sealing class and the ratio of bench adapters to vehicle-grade connectors.
- ADAS domain controller bring-up - Lab-side cable kits for software bring-up and unit-level test.
- Multi-camera perception bench testing - GMSL2/3 camera cable kits with bench-grade connectors.
- Surround-view and front/side-view validation - Coordinated camera trunk routing across multiple GMSL ports.
- Radar and lidar data link verification - Automotive Ethernet between sensors and the DRIVE AGX kit.
- Automotive Ethernet conformance testing - H-MTD-to-RJ45 adapter cables paired with media converters.
- In-vehicle data collection fleets - Serialized, sealed harnesses for fleet deployment and service.
- HIL and SIL setups - Bench harnesses for hardware/software-in-the-loop test rigs.
- Prototype vehicle integration - Vehicle-routed harness combining power, CAN, Ethernet and camera trunks.
H-MTD x4 Splitter - Quad-Port Automotive Ethernet
H-MTD x6 Splitter - 6-Port Automotive Ethernet
Frequently Asked Questions
What cables does DRIVE AGX Thor use for cameras?
According to NVIDIA, Thor exposes 16 GMSL2 ports plus 2 GMSL3 ports. GMSL2 and GMSL3 are Analog Devices' high-speed automotive serial link technologies, typically running over 50 Ω coax. The exact connector (Fakra, Mini-Fakra or MATE-AX) depends on the camera module selected.
What is an H-MTD-to-RJ45 adapter cable used for?
It is used to connect a DRIVE AGX kit's automotive Ethernet H-MTD port to a standard lab switch, PC or data logger that uses RJ45. Note that BASE-T1 to RJ45 normally requires an active media converter on multi-gig links, not just a passive adapter cable.
What is the cabling difference between Thor SKU 10 and SKU 12?
SKU 10 is bench-oriented and is usually paired with short, unsealed adapter cables and a lab power supply. SKU 12 is intended for in-vehicle development and typically needs a full sealed harness with vehicle power, CAN, multiple H-MTD Ethernet branches and routed GMSL camera trunks.
Can custom cables be made for DRIVE AGX Thor and Orin?
Yes. Custom GMSL camera cables, H-MTD Ethernet cables and full vehicle harnesses can be built to project-specific length, shielding and connector pairing. A typical quote starts from the interface list, the vehicle routing diagram and the EMC or sealing class required.
Why does my GMSL camera link drop frames intermittently?
The most common root causes seen in the field are wrong cable impedance (75 Ω instead of 50 Ω), violation of the connector's minimum bend radius near the shell, and PoC design issues at the cable / inductor interface. Check these three first before suspecting the camera or the developer kit.
📚 Authority References
- NVIDIA - DRIVE AGX Developer Kits (Thor SKU 10 / SKU 12; 16x GMSL2 + 2x GMSL3; 3x 100/1000/10G-T1 H-MTD; Orin GMSL ports and Ethernet data transmission)
- Analog Devices AN-2585 - GMSL3 Channel Specification (12 Gbps forward, 187.5 Mbps reverse, PAM4 encoding)
- Analog Devices MAX9671x / MAX9679x family datasheets (GMSL2 forward link rates of 3 Gbps or 6 Gbps, 187.5 Mbps reverse)
- IEEE 802.3bp (1000BASE-T1) and IEEE 802.3ch (Multi-Gig Automotive Ethernet, 10GBASE-T1)
Need a Custom DRIVE AGX Cable, Adapter or Vehicle Harness?
Send us your interface list (Thor/Orin port + sensor/host port), cable lengths and routing notes, shielding/EMC class, sealing class, quantity and target delivery window. Our engineering team will reply with a quoted assembly drawing and material list.
- Not sure which connector fits your sensor side? Send the camera/sensor model and we will recommend.
- Need an H-MTD-to-RJ45 adapter for a specific lab switch? We will confirm whether a passive cable or a media converter is needed before quoting.
- Building a fleet harness? We support labeling, serialization and per-unit traceability.
Source DRIVE AGX Thor & Orin Cable Assemblies
Premier Cable manufactures GMSL camera cables, H-MTD automotive Ethernet cables, H-MTD-to-RJ45 adapters and full vehicle harnesses for DRIVE AGX Thor and Orin development programs. Standard and custom assemblies available. Contact our engineering team for specification support or quotation.
