Yes. AXI, CHI, CXL, PCIe, and CXS can all be supported in a UCIe-based chiplet architecture. Depending on the protocol and implementation, connectivity may use UCIe-defined protocol mappings or protocol-specific Bridge IP. UCIe provides the die-to-die interconnect foundation, while bridge logic connects that infrastructure to the protocol environment already used inside a processor, accelerator, coherent fabric, memory subsystem, I/O block, or other chiplet subsystem.
SmartDV provides dedicated Bridge IP for all five protocol families:
- 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
If you are new to the role of the bridge itself, start with What Is UCIe Bridge IP?
Why Are Protocol Bridges Needed with UCIe?
A chiplet does not necessarily use UCIe as the native protocol for all communication inside the die.
Existing SoC subsystems may already be designed around AXI, CHI, CXL, PCIe, or CXS. Bridge IP provides a way to connect those protocol domains to the UCIe die-to-die path without requiring the internal subsystem architecture to be replaced.
A simplified architecture can look like:
AXI / CHI / CXL / PCIe / CXS → UCIe Bridge IP → UCIe Controller IP → Die-to-Die Link
The UCIe Controller and Bridge therefore perform different but complementary functions. See What Is the Difference Between UCIe Controller IP and UCIe Bridge IP? for the concise comparison.
How Can AXI Be Used with UCIe?
AXI is widely used for data movement within SoCs, processors, accelerators, and other subsystem architectures.
SmartDV’s AXI to UCIe Bridge IP connects an AMBA AXI environment to UCIe die-to-die infrastructure.
The current IP supports AMBA AXI5 with backward compatibility to AXI4 and AXI3. It supports AXI data-bus widths from 8 to 1024 bits, UCIe lane configurations of 16, 32, and 64 lanes, and UCIe operation through 64 GT/s.
This makes AXI-to-UCIe connectivity applicable to systems where an AXI-based accelerator or other SoC subsystem needs to communicate with another chiplet across the package.
How Can CHI Be Used with UCIe?
CHI is relevant to coherent processor and cache-based architectures that need to extend coherent communication across chiplet boundaries.
SmartDV’s CHI to UCIe Bridge IP connects AMBA 5 CHI protocol traffic to UCIe.
The implementation supports Request Nodes (RN-F, RN-D, RN-I), Home Nodes (HN-F, HN-I), Miscellaneous Nodes (MN), and Slave Nodes (SN-F, SN-I). It also supports CHI Protocol, Network, and Link layer behavior across the bridge.
This allows coherent CHI-based subsystems to participate in a UCIe multi-die architecture while maintaining the CHI behavior required by the surrounding system.
How Can CXL Be Used with UCIe?
CXL is particularly relevant to AI, HPC, memory, and accelerator architectures requiring coherent communication.
SmartDV’s CXL to UCIe Bridge IP supports CXL.io, CXL.cache, and CXL.mem traffic across a UCIe die-to-die connection.
The current bridge supports CXL 2.0, 3.0, 3.1, and 3.2 and UCIe operation through 64 GT/s across 16-, 32-, and 64-lane configurations.
For multi-die systems that use CXL for coherent processor, accelerator, or memory connectivity, the bridge allows that protocol environment to be carried through the UCIe chiplet infrastructure.
How Can PCIe Be Used with UCIe?
PCI Express remains important for accelerators, networking, storage, and other high-speed I/O functions.
SmartDV’s PCIe to UCIe Bridge IP provides protocol bridging between PCI Express and a UCIe die-to-die interconnect.
The current IP supports PCIe 6.0 Root Complex and Endpoint functionality along with UCIe v3.0 operation through 64 GT/s. It also supports Standard and Advanced Package configurations and multiple UCIe Flit formats.
This allows PCIe-oriented functions to participate in chiplet-based systems while UCIe provides the package-level die-to-die connection.
How Can CXS Be Used with UCIe?
AMBA CXS provides streaming communication that can be relevant to high-bandwidth accelerator and HPC architectures.
SmartDV’s CXS to UCIe Bridge IP connects CXS streaming traffic to UCIe.
The bridge supports functionality including credit exchange, link activation and deactivation, configurable credit control, continuous packet delivery, Flit placement and control, and error injection and detection.
Like SmartDV’s other current UCIe bridge products, the CXS bridge supports UCIe operation through 64 GT/s across 16-, 32-, and 64-lane configurations.
Which UCIe Bridge Should a Chiplet Design Use?
The appropriate bridge depends on the protocol architecture of the subsystem connecting to UCIe.
| Protocol | Typical Architectural Role | SmartDV UCIe Bridge |
|---|---|---|
| AXI | SoC and accelerator data paths | AXI to UCIe Bridge IP |
| CHI | Coherent processor and cache fabrics | CHI to UCIe Bridge IP |
| CXL | Coherent accelerator and memory connectivity | CXL to UCIe Bridge IP |
| PCIe | High-speed I/O-oriented connectivity | PCIe to UCIe Bridge IP |
| CXS | High-bandwidth streaming communication | CXS to UCIe Bridge IP |
A heterogeneous architecture may use more than one of these bridges. Different chiplets can retain different internal protocol environments while using UCIe as the common die-to-die interconnect.
For the expanded discussion of where each bridge fits, read UCIe Bridge IP Explained: Connecting AXI, CHI, CXL, PCIe, and CXS Across Chiplets.
Can Multiple Protocols Be Used in the Same UCIe Architecture?
Yes. A multi-die architecture can include different protocol domains according to the function of each chiplet or subsystem.
For example, an AI or HPC package could combine an AXI-based accelerator, a CHI-based coherent compute subsystem, CXL-oriented memory connectivity, and PCIe-based I/O. Each subsystem can use the bridge appropriate to its own architecture while participating in the broader UCIe system.
This is one of the reasons a modular approach can be useful for complex chiplet platforms. See Building a Modular UCIe IP Stack for AI and HPC Chiplet Architectures for a more detailed example.
Do the Bridges Work with UCIe 2.x and UCIe 3.x?
SmartDV’s current AXI, CHI, CXL, PCIe, and CXS to UCIe Bridge IP products support UCIe v3.0 and are backward compatible with UCIe v2.0, v1.1, and v1.0.
SmartDV also provides separate UCIe 2.x Controller IP and UCIe 3.x Controller IP.
For the controller-generation differences, see What Is the Difference Between UCIe 2.x and UCIe 3.x Controller IP?
How Should Protocol-to-UCIe Integration Be Verified?
Verification should cover the complete path rather than validating only the UCIe link or the source protocol independently.
Depending on the architecture, this can include protocol transactions, ordering, flow control, UCIe Flit behavior, link initialization, sideband communication, reset and recovery, error handling, and end-to-end data integrity across the bridge and controller.
SmartDV’s UCIe Verification IP provides protocol-aware verification infrastructure for UCIe versions 1.0, 1.1, 2.0, and 3.0.
For the broader chiplet verification discussion, see Why UCIe Verification Is Critical for Chiplet-Based SoC Design.
Explore SmartDV UCIe Bridge IP
SmartDV provides UCIe Controller IP, protocol-specific Bridge IP for AXI, CHI, CXL, PCIe, and CXS, and UCIe Verification IP for configurable chiplet and multi-die architectures.
Explore SmartDV UCIe IP for Next-Generation Chiplet Designs to review the complete UCIe controller, bridge, and verification portfolio.
» Contact SmartDV to discuss AXI, CHI, CXL, PCIe, CXS, or other UCIe integration requirements for your project.