Contact Us

Universal Chiplet Interconnect Express continues to evolve as semiconductor teams move toward more modular multi-die architectures. For teams already developing around UCIe 2.x or evaluating newer chiplet platforms, one of the key questions is what changes when moving to UCIe 3.x.

The most visible difference is performance. SmartDV’s UCIe 2.x Controller IP supports die-to-die operation through 32 GT/s, while the UCIe 3.x Controller IP extends support through 64 GT/s.

But the move from UCIe 2.x to 3.x is not only about a higher maximum data rate. UCIe 3.x also introduces additional capabilities for link management, sideband communication, power-efficient operation, and runtime behavior that can affect how future chiplet systems are architected, integrated, and verified.

For teams building a broader UCIe platform, these changes should be considered alongside the controller, bridge, and verification architecture. SmartDV’s UCIe IP for Next-Generation Chiplet Designs brings these pieces together for multi-die SoC development.

Why the Move from UCIe 2.x to UCIe 3.x Matters

Chiplet architectures increasingly need to move large volumes of data between processors, accelerators, memory-facing logic, and other functional die. As those systems scale, the bandwidth and behavior of the die-to-die interconnect become increasingly important.

UCIe 2.x already provides a standards-based foundation for high-speed chiplet communication. SmartDV’s UCIe 2.x Controller IP supports UCIe v2.0, with backward compatibility to UCIe v1.1 and v1.0, across 16-, 32-, and 64-lane configurations at speeds from 4 GT/s through 32 GT/s.

UCIe 3.x extends that foundation. SmartDV’s UCIe 3.x Controller IP supports UCIe v3.0 and remains backward compatible with UCIe v2.0, v1.1, and v1.0 while increasing supported operation through 64 GT/s.

That makes UCIe 3.x particularly relevant for future AI, HPC, data center, and other bandwidth-intensive multi-die architectures where the amount of communication between chiplets continues to increase.

SmartDV UCIe 2.x vs. UCIe 3.x Controller IP at a Glance

The comparison below reflects SmartDV’s current UCIe 2.x and UCIe 3.x Controller IP products rather than universal minimums defined by the UCIe specification itself.

Capability SmartDV UCIe 2.x Controller IP SmartDV UCIe 3.x Controller IP
Supported UCIe Revision UCIe v2.0 UCIe v3.0
Backward Compatibility UCIe v1.1 and v1.0 UCIe v2.0, v1.1, and v1.0
Maximum Supported Data Rate 32 GT/s 64 GT/s
Lane Configurations 16, 32, and 64 lanes 16, 32, and 64 lanes
UCIe Clock Range 500 MHz to 4 GHz 500 MHz to 8 GHz
Standard and Advanced Package Support Yes Yes
Protocol Connectivity PCIe, CXL, AXI, CXS, CHI PCIe, CXL, AXI, CXS, CHI
Runtime Recalibration — Supported
Priority Sideband Messaging — Supported
Power-Saving Enhancements — Runtime recalibration and L2 optimization

64 GT/s Expands Die-to-Die Bandwidth

The most significant performance change between SmartDV’s UCIe 2.x and UCIe 3.x Controller IP is the maximum supported data rate.

The UCIe 2.x Controller IP supports speeds from 4 GT/s through 32 GT/s. The UCIe 3.x Controller IP extends that range through 48 GT/s and 64 GT/s.

This doubles the maximum supported die-to-die rate compared with UCIe 2.x.

For architectures moving increasingly large data sets between compute, accelerator, memory, or other chiplets, this additional bandwidth can become an important part of system planning. Higher link performance can also affect surrounding design decisions involving lane configuration, traffic behavior, power, timing, and the protocol interfaces feeding the UCIe connection.

UCIe 3.x Adds New Link-Management Capabilities

Higher bandwidth is only one part of the UCIe 3.x change.

The UCIe 3.0 specification itself expands further, adding extended sideband reach, continuous-transmission protocol mappings in Raw Mode, standardized early firmware download, priority sideband packets, fast throttle and emergency shutdown signaling, and open-drain pin support. SmartDV’s UCIe 3.x Controller IP incorporates a set of these UCIe 3.0 capabilities, including runtime recalibration, priority sideband messaging, and power-saving enhancements such as L2 optimization.

Runtime Recalibration

Runtime recalibration extends the link-management capabilities available during system operation. Instead of treating link configuration only as an initialization concern, UCIe 3.x provides additional mechanisms for managing the connection while the system is operating.

For system architects and verification teams, this means runtime link behavior becomes another part of the implementation and validation plan.

Priority Sideband Messaging

The sideband path supports management and control communication that operates alongside the UCIe mainband data path.

UCIe 3.x adds priority sideband messaging, giving the architecture additional control over important sideband traffic. This expands the set of conditions that controller implementations and verification environments may need to exercise.

Power-Saving and L2 Optimization

UCIe 3.x also introduces power-saving enhancements built around L2 optimization, complementing the runtime recalibration capability described above. As chiplet architectures scale in complexity, power management increasingly needs to be considered across both the primary data path and the supporting management infrastructure.

For designs targeting power-sensitive applications or large multi-die systems, these capabilities become another consideration when evaluating the appropriate UCIe generation.

What Remains Common Across UCIe 2.x and UCIe 3.x?

The transition to UCIe 3.x does not replace every element of the UCIe architecture.

SmartDV’s UCIe 2.x and UCIe 3.x Controller IP both support:

  • 16-, 32-, and 64-lane configurations
  • Standard and Advanced Package configurations
  • PCIe and CXL protocol connectivity
  • Streaming protocols including AXI, CXS, and CHI
  • Multiple UCIe Flit formats
  • Flit retry, CRC, and parity functionality
  • Sideband messaging and Sideband Mailbox support
  • UCIe Retimer support
  • Multi-Stack protocol configurations
  • Configurable implementations for ASIC and FPGA designs

This continuity matters because teams moving to UCIe 3.x are building on an established architecture rather than starting with an entirely different interconnect model.

Protocol Connectivity Still Depends on the Surrounding Chiplet Architecture

Moving from UCIe 2.x to UCIe 3.x does not eliminate the need to consider how the UCIe controller connects to the protocol environment inside each chiplet.

SmartDV’s controller architecture supports PCIe, CXL, AXI, CXS, and CHI through dedicated protocol bridge interfaces.

If the distinction between these components is important to your architecture, see UCIe Controller IP vs. UCIe Bridge IP: What Does a Chiplet Design Need? for a closer look at how the controller and bridge layers work together.

For a deeper comparison of the available protocol-specific bridge options, see UCIe Bridge IP Explained: Connecting AXI, CHI, CXL, PCIe, and CXS Across Chiplets.

For teams planning the complete interconnect architecture, Building a Modular UCIe IP Stack for AI and HPC Chiplet Architectures explains how controller generation, protocol bridges, and UCIe Verification IP can be selected together around the requirements of the system.

Key Technical Challenges When Moving to UCIe 3.x

Supporting a newer UCIe generation expands the design space that engineering teams need to consider.

More Link Speeds and Operating Conditions

Support through 64 GT/s adds additional operating points beyond the UCIe 2.x range. Designs that support multiple generations may need to account for different negotiated speeds and operating configurations rather than assuming that every connection will use the maximum supported rate.

Backward Compatibility Expands the Configuration Matrix

SmartDV’s UCIe 3.x Controller IP is backward compatible with UCIe v2.0, v1.1, and v1.0.

That provides flexibility for systems that need to interact with multiple UCIe generations, but it also means design and verification planning should account for the actual combinations a product intends to support.

New Management Features Need System-Level Consideration

Runtime recalibration, priority sideband messaging, and power-saving enhancements such as L2 optimization introduce behavior that needs to work correctly alongside normal traffic.

These features should therefore be considered within the broader system architecture rather than validated only as isolated controller capabilities.

Protocol Bridges Add Another Layer

A UCIe controller frequently sits between a protocol-specific bridge and the physical die-to-die connection. The requirements of AXI, CHI, CXL, PCIe, or CXS still need to be maintained as traffic moves through that architecture.

This means upgrading the UCIe controller generation does not remove the need to validate the complete data path from the originating protocol domain through the bridge and across the UCIe connection.

How Verification Teams Should Approach UCIe 2.x and UCIe 3.x

Verification planning should begin with the UCIe revisions and features that the actual product claims to support.

A UCIe 3.x implementation with backward compatibility can require verification across more than one operating speed, protocol mapping, lane configuration, Flit format, package configuration, and feature combination.

Verification teams should consider:

  • Supported UCIe revisions and backward-compatible configurations
  • Operation across supported link speeds
  • Lane-width and package configurations
  • Link initialization and training
  • Flit formatting and data integrity
  • Retry and recovery behavior
  • Sideband messaging and mailbox operation
  • Runtime recalibration where implemented
  • Power-management behavior
  • Protocol bridge integration
  • Error injection and recovery scenarios
  • End-to-end traffic under normal and stressed conditions

SmartDV’s UCIe VIP supports verification across UCIe versions 1.0, 1.1, 2.0, and 3.0, providing a common verification foundation for designs that need to address current and backward-compatible configurations.

For a broader discussion of the system-level verification challenges associated with chiplet interconnects, see Why UCIe Verification Is Critical for Chiplet-Based SoC Design.

Related SmartDV UCIe Products and Resources

Article Summary

UCIe 3.x builds on the UCIe 2.x die-to-die architecture while expanding the capabilities available for next-generation chiplet systems.

SmartDV’s UCIe 2.x Controller IP supports operation through 32 GT/s, while the UCIe 3.x Controller IP extends the maximum supported rate to 64 GT/s. UCIe 3.x also adds capabilities including runtime recalibration, priority sideband messaging, and power-saving enhancements such as L2 optimization.

At the same time, important architectural elements remain consistent. Both SmartDV controller generations support Standard and Advanced Package configurations, multiple lane widths and Flit formats, PCIe and CXL connectivity, streaming protocols including AXI, CXS, and CHI, sideband infrastructure, retry mechanisms, and multi-stack configurations.

The decision between UCIe 2.x and UCIe 3.x should therefore consider more than maximum link speed. Teams should evaluate bandwidth requirements, backward compatibility, link-management needs, power requirements, protocol integration, and the verification matrix created by the features their product intends to support.

Frequently Asked Questions

What is the main difference between UCIe 2.x and UCIe 3.x?
One of the primary differences is maximum supported link speed. SmartDV’s UCIe 2.x Controller IP supports operation through 32 GT/s, while the UCIe 3.x Controller IP supports operation through 64 GT/s. UCIe 3.x also adds capabilities including runtime recalibration, priority sideband messaging, and power-saving enhancements such as L2 optimization.

Is UCIe 3.x backward compatible with UCIe 2.x?
SmartDV’s UCIe 3.x Controller IP supports UCIe v3.0 and is backward compatible with UCIe v2.0, v1.1, and v1.0.

Does UCIe 3.x support different protocols than UCIe 2.x?
SmartDV’s UCIe 2.x and UCIe 3.x Controller IP both support PCIe, CXL, and streaming protocol connectivity including AXI, CXS, and CHI through dedicated bridge interfaces.

Does moving to UCIe 3.x eliminate the need for UCIe Bridge IP?
No. The UCIe controller and protocol bridge perform different functions. The controller implements the UCIe stack, while protocol-specific Bridge IP connects the UCIe infrastructure to interfaces such as AXI, CHI, CXL, PCIe, or CXS.

How should UCIe 3.x be verified?
Verification should cover the UCIe features and configurations implemented by the design, including supported link speeds, lane configurations, Flit formats, initialization, sideband operation, retries, error recovery, power-management behavior, runtime features, backward compatibility, and protocol bridge integration.

Prepare Your Chiplet Architecture for the Next Generation of UCIe

SmartDV provides UCIe 2.x and UCIe 3.x Controller IP, protocol-specific Bridge IP, and UCIe Verification IP to support current and next-generation multi-die architectures.

Explore SmartDV UCIe IP for Next-Generation Chiplet Designs to learn more about controller, bridge, and verification solutions for your chiplet-based SoC, ASIC, or FPGA project.

See All Chiplets & Die-to-Die Interconnects