The primary difference between UCIe Controller IP and UCIe Bridge IP is the role each component performs in the chiplet data path. UCIe Controller IP implements the UCIe functionality required for die-to-die communication, while UCIe Bridge IP connects an existing protocol environment such as AXI, CHI, CXL, PCIe, or CXS to that UCIe infrastructure.
In many chiplet architectures, these are not competing alternatives. They are complementary components that work together.
A simplified architecture looks like this:
Protocol Fabric → UCIe Bridge IP → UCIe Controller IP → Die-to-Die Link
For additional background on the bridge layer itself, see What Is UCIe Bridge IP?
What Does UCIe Controller IP Do?
UCIe Controller IP provides the controller functionality required to implement a Universal Chiplet Interconnect Express die-to-die connection.
SmartDV’s UCIe 2.x Controller IP and UCIe 3.x Controller IP implement the UCIe stack across the Protocol Layer, D2D Adapter Layer, and sideband infrastructure.
Depending on the controller generation and configuration, this includes functionality such as:
- UCIe protocol-layer operation
- D2D Adapter functionality
- Flit packing and retry
- CRC and parity handling
- Sideband messaging and mailbox functionality
- Link-management features
- Standard and Advanced Package configurations
- Multiple lane and Flit-format configurations
The controller therefore provides the core UCIe functionality that manages communication across the die-to-die connection.
What Does UCIe Bridge IP Do?
UCIe Bridge IP provides the connection between that UCIe infrastructure and the protocol used by the surrounding subsystem.
For example, if an accelerator communicates internally using AXI, the design can use AXI to UCIe Bridge IP to connect that AXI environment into the UCIe data path.
If the subsystem instead uses CXL, CHI, PCIe, or CXS, a corresponding protocol-specific bridge can be used.
SmartDV currently provides:
- AXI to UCIe Bridge IP
- CHI to UCIe Bridge IP
- CXL to UCIe Bridge IP
- PCIe to UCIe Bridge IP
- CXS to UCIe Bridge IP
See Can AXI, CHI, CXL, PCIe, and CXS Be Used with UCIe? for more detail on these protocol connections.
UCIe Controller IP vs. UCIe Bridge IP at a Glance
| Function | UCIe Controller IP | UCIe Bridge IP |
|---|---|---|
| Primary Role | Implements UCIe die-to-die protocol functionality | Connects another protocol domain to UCIe |
| Where It Sits | Within the UCIe die-to-die stack | Between the host protocol environment and UCIe infrastructure |
| Examples | UCIe 2.x Controller IP, UCIe 3.x Controller IP | AXI, CHI, CXL, PCIe, or CXS to UCIe Bridge IP |
| Protocol-Specific? | Provides the common UCIe controller foundation | Selected according to the protocol used by the subsystem |
| Can They Be Used Together? | Yes | Yes |
Does a UCIe Design Need Both a Controller and a Bridge?
That depends on the architecture. UCIe already defines protocol mappings for PCIe and CXL, so separate Bridge IP is not always necessary. Other subsystem protocols may require dedicated bridging or adaptation, depending on the implementation.
The UCIe controller provides the common die-to-die protocol infrastructure. The bridge provides the connection between that infrastructure and the protocol environment already used by the processor, accelerator, memory subsystem, I/O block, or other logic inside the chiplet.
For example:
AXI subsystem → AXI to UCIe Bridge → UCIe Controller → UCIe link
The same architectural pattern can be applied to CHI, CXL, PCIe, or CXS depending on the requirements of the subsystem.
For the expanded architectural discussion, read UCIe Controller IP vs. UCIe Bridge IP: What Does a Chiplet Design Need?
Can One UCIe Architecture Use Multiple Bridge Types?
Yes. A heterogeneous multi-die system may contain several protocol domains.
An AI or HPC platform, for example, could include an AXI-based accelerator, CHI-based coherent processing, CXL-oriented memory connectivity, and PCIe-oriented I/O. Different protocol bridges can connect those subsystems into the broader UCIe architecture.
This allows the UCIe connection to provide a common die-to-die foundation without requiring every chiplet to use the same internal protocol.
See UCIe Bridge IP Explained: Connecting AXI, CHI, CXL, PCIe, and CXS Across Chiplets for a closer look at the individual bridge options.
Where Do UCIe 2.x and UCIe 3.x Fit?
The controller generation determines which UCIe revision and associated controller capabilities are implemented.
SmartDV’s UCIe 2.x Controller IP supports UCIe v2.0 and operation through 32 GT/s. SmartDV’s UCIe 3.x Controller IP supports UCIe v3.0, remains backward compatible with earlier UCIe versions, and extends operation through 64 GT/s.
UCIe 3.x also introduces priority sideband messaging and power-saving enhancements such as runtime recalibration and L2 optimization.
For a direct comparison, see What Is the Difference Between UCIe 2.x and UCIe 3.x Controller IP?
The longer technical discussion is available in UCIe 2.x vs. UCIe 3.x: What Changed for Chiplet Interconnect Design?
How Do Controller IP, Bridge IP, and Verification IP Work Together?
Controller IP and Bridge IP become part of the implemented design. Verification IP provides the protocol-aware infrastructure used to validate UCIe link behavior, with protocol-specific checks added for the bridges and upper layers.
SmartDV’s UCIe Verification IP supports UCIe versions 1.0, 1.1, 2.0, and 3.0 and can be used to validate link behavior, Flit handling, sideband communication, error scenarios, recovery, and other UCIe functionality.
Verification should also consider the complete path through the protocol bridge and controller rather than validating each component only in isolation.
This relationship between controller, bridge, and verification technologies is explored further in Building a Modular UCIe IP Stack for AI and HPC Chiplet Architectures.
Explore SmartDV UCIe Controller and Bridge IP
SmartDV provides UCIe 2.x and UCIe 3.x Controller IP, protocol-specific Bridge IP for AXI, CHI, CXL, PCIe, and CXS, and UCIe Verification IP for multi-die SoC development.
Explore SmartDV UCIe IP for Next-Generation Chiplet Designs to review the complete controller, bridge, and verification portfolio.
» Contact SmartDV to discuss the UCIe architecture and protocol connectivity required for your project.