HomeChiplets & UCIeDay 2
DAY 2 · PHASE 1 — FOUNDATIONS

Die-to-Die Interconnect Fundamentals
Bandwidth, Latency, Power per Bit

By EcrioniX · Updated July 2026

A chiplet package is only as good as the wires connecting the chiplets. Day 2 covers how die-to-die (D2D) interconnect actually works, the three metrics engineers optimize for, and the verified numbers from the UCIe 1.1 specification — the standard this course builds toward.

Die-to-Die Interconnect Is Not "Just a Wire"

Inside a monolithic die, wires connecting two blocks are essentially free — they're part of the same manufacturing step, extremely short, and extremely cheap in area and power. The moment you split a design into chiplets, every signal that used to cross an on-die wire now has to cross a package boundary: through a bump, across a substrate or interposer, and into another die's receiver. That boundary crossing has to solve three hard problems simultaneously: move enough data, don't burn too much power doing it, and reach far enough to physically connect the chiplets as placed.

The Three Metrics That Matter

📊
Bandwidth DensityData rate per millimeter of die edge (Tbps/mm) — edge length is limited, so density matters more than raw bandwidth
Energy EfficiencyPicojoules per bit (pJ/bit) transferred — directly determines how much of your power budget the interconnect itself consumes
📏
ReachMaximum distance the link can drive reliably — depends entirely on the packaging technology, not just the transceiver design

These three trade off against each other. A link that reaches further generally needs more drive strength, which costs more energy per bit and more area per lane — which lowers bandwidth density. This is exactly why UCIe defines two distinct packaging categories instead of one.

UCIe Layered Stack Protocol Layer PCIe · CXL · Streaming (raw) Die-to-Die Adapter Layer Link management · protocol arbitration · CRC + retry Physical Layer Mainband (TX/RX AFE) + Sideband (params, negotiation) Link training · calibration · repair

Mainband and Sideband — Two Separate Channels

UCIe's Physical Layer carries two logically distinct channels:

This separation matters practically: if the high-speed mainband fails to train correctly, the sideband is still there to report status and enable debug, rather than the whole link going dark with no diagnostic path.

Link Training — Three Stages

  1. Sideband detection & initialization — the two dies first establish the low-speed sideband link
  2. Mainband training — parameter exchange over sideband, then lane repair and training of the high-speed mainband itself
  3. Protocol parameter exchange — final negotiation over sideband before the link is handed off to the Protocol Layer above

UCIe Standard Package vs Advanced Package — Verified Numbers

UCIe 1.1 defines two packaging categories with genuinely different targets, not just two configuration options of the same thing:

ParameterStandard PackageAdvanced Package
Target substrateOrganic package substrateSilicon interposer / bridge
Bump pitch100–130 µm25–55 µm
Link reachUp to 25 mm (terminated)Up to 2 mm (unterminated)
Energy efficiency target0.5 pJ/bit0.25 pJ/bit
Lanes per module16 TX + 16 RX64 TX + 64 RX
Bandwidth per module (example)~0.25 Tbps at 16 GT/s per pin~1 Tbps at 16 GT/s per pin
Aggregate bandwidth density~0.9 Tbps/mm~5.2 Tbps/mm

Figures per the UCIe 1.1 specification (released August 2023) and UCIe Consortium technical materials.

Worked Example — Where the Bandwidth Number Comes From

The "~1 Tbps per module" figure for Advanced Package isn't arbitrary — it comes directly from lane count × per-pin data rate:

Bandwidth calculation — Advanced Package module
64 lanes  ×  16 GT/s per lane  =  1,024 Gbps  ≈  1 Tbps (per direction)

At the Standard Package's 16-lane width, the same per-pin rate gives:
16 lanes  ×  16 GT/s per lane  =  256 Gbps  ≈  0.25 Tbps (per direction)

This is why Advanced Package delivers roughly 4× the per-module bandwidth of Standard Package at the same per-pin data rate — it simply has 4× the lane count, packed into a much finer bump pitch.

Per-Pin Data Rate Options

UCIe 1.1 defines a family of supported per-pin data rates: 4, 8, 12, 16, 24, and 32 GT/s. A designer picks a rate based on the reach required, the power budget available, and how much signal integrity margin the chosen packaging technology can support — a Standard Package link driving 25mm typically can't push the same per-pin rate as an Advanced Package link driving 2mm at the same power and error-rate target.

Why Reach and Bandwidth Density Trade Off

A finer bump pitch packs more lanes into the same edge length, directly raising bandwidth density — but finer pitch and shorter, unterminated links only work reliably over very short distances (a few millimeters), which is exactly what a silicon interposer or bridge provides. An organic substrate can't achieve that fine a pitch or that short a distance between arbitrary chiplets, so Standard Package trades bandwidth density for the ability to reach much further (up to 25mm) using a cheaper, more common packaging technology.

Die-to-Die Adapter Layer — What It Actually Does

Sitting above the Physical Layer, the Die-to-Die Adapter Layer handles:

🎯 Day 2 Key Takeaways

Frequently Asked Questions

What are the three metrics that matter most for die-to-die interconnect?
Bandwidth density (how much data rate you get per millimeter of die edge, since edge length is limited), energy efficiency measured in picojoules per bit (pJ/bit), and reach — the maximum distance the link can drive reliably, which depends on the packaging technology used.
What is the difference between UCIe Standard Package and Advanced Package?
Standard Package targets organic substrates with a 100-130 micron bump pitch, up to 25mm reach, and a 0.5 pJ/bit energy efficiency target. Advanced Package targets silicon interposers or bridges with a much finer 25-55 micron bump pitch, shorter 2mm reach, and a better 0.25 pJ/bit energy efficiency target, trading reach for much higher bandwidth density.
What are UCIe mainband and sideband channels?
The mainband is the high-speed data bus itself — up to 64 transmit and 64 receive lanes per module in Advanced Package, or 16 and 16 in Standard Package — plus forwarded clock and framing signals. The sideband is a separate, always-available low-speed channel used for parameter exchange, link negotiation, and register access, including during initial bring-up before the mainband is trained.
What are the three layers of the UCIe protocol stack?
Physical Layer (the electrical transmitter/receiver and sideband, plus link training and calibration logic), Die-to-Die Adapter Layer (link management, protocol arbitration, and optional CRC-based error correction with retry), and Protocol Layer (the actual protocol riding on top, such as PCIe, CXL, or a raw streaming mode).
What data rates does UCIe 1.1 support?
UCIe 1.1 defines per-pin data rates of 4, 8, 12, 16, 24, and 32 GT/s (gigatransfers per second), letting designers trade off raw per-pin speed against power and signal integrity margin depending on the packaging technology used.