MIPI I3C IP Cores
Controller, Target and Host Controller IP for MIPI I3C® Basic v1.2, I3C v1.1 and I3C HCI v1.2. SystemVerilog RTL for AMBA® APB and AXI systems.
Three families built on one I3C engine. I3C Basic covers the Controller and Target roles with the SDR and HDR modes of I3C Basic. I3C Full adds HDR ternary, synchronous timing control, device-to-device tunneling and Multi-Lane in SDR and HDR-DDR. I3C HCI puts the Controller behind the standard Host Controller Interface, so Linux drives it with its own upstream driver. An autonomous Target-to-AMBA bridge completes the family for devices with no processor.
Peak data rates during the data phase at 12.5 MHz SCL.
Product family
All are synthesizable SystemVerilog RTL with a self-checking test bench, an independent I3C bus monitor and drivers.
I3C Full Controller / Target
Everything in I3C Basic, plus the features of the full I3C specification. Each full-specification feature is a build option, and a Basic-only build comes from the same RTL.
- HDR ternary: HDR-TSP and HDR-TSL, about 33 Mbps, Controller and Target
- Synchronous Timing Control, and Async Mode 0 time stamps
- Device-to-Device Tunneling; Monitoring Device Early Termination
- Multi-Lane x2 / x4 in SDR and HDR-DDR, as well as HDR-BT
- I3C v1.1 by default; I3C Basic v1.2 behavior selectable by register
I3C Basic Controller / Target
The I3C Basic engine in three configurations: dual-role Controller / Target, Controller-only and Target-only. The single-role versions drop the other role’s logic for a smaller footprint.
- SDR 12.5 Mbps; HDR-DDR and HDR-BT 25 Mbps; HDR-BT Multi-Lane x2 / x4 up to 100 Mbps
- Secondary Controller: Controller role hand-off, with pull-up and keeper control
- Device table, static and group addressing, In-Band Interrupts with payload, Hot-Join
- Error recovery engine; controller clock stalling; Async Mode 0 time stamps
- I3C Basic v1.1.1 behavior selectable by register for mixed-version buses
I3C HCI Host Controller
An I3C Controller with the standard MIPI Host Controller Interface register model. Standard HCI software, such as the Linux mipi-i3c-hci driver, runs it with no custom driver.
- Standard capability, Device Address Table and Device Characteristics Table registers
- Programmed I/O through an APB or AXI4-Lite register port
- DMA option: command and response rings and scatter-gather data buffers through an AXI4 manager
- Address assignment, IBI, Hot-Join, Target Reset and bus recovery in hardware
- SDR and HDR-DDR; HDR-BT and Multi-Lane through a Digital Blocks extended capability
I3C Target-to-AMBA Bridge
An autonomous I3C Target that lets an external I3C Controller read and write the registers and memory of a device directly. Identity comes from input straps, so the bridge works at power-up with no local processor and no configuration.
Bridge features
- APB or AXI4-Lite manager port, with byte strobes for partial-word writes
- 1- to 4-byte register address, auto-increment and read prefetch
- Interrupt input raises an In-Band Interrupt; Target Reset output
- SCL-clocked protocol engine: quiet between transfers
Side-by-side comparison
I3C Full and I3C Basic share one register model and drivers; a Full core built without its full-specification options is an I3C Basic device.
| I3C FullDB-I3C-FULL-MS / -M / -S | I3C BasicDB-I3C-BASIC-MS / -M / -S | I3C HCIDB-I3C-HCI | Target-to-AMBA BridgeDB-I3C-Target-Bridge | |
|---|---|---|---|---|
| Specification | I3C v1.1; Basic v1.2 behavior selectable | I3C Basic v1.2; v1.1.1 behavior selectable | I3C HCI v1.2; bus per I3C Basic v1.2 | I3C Basic v1.2, SDR Target |
| Roles | Controller / Target, Controller, or Target | Controller / Target, Controller, or Target | Controller (Host Controller) | Target |
| System interface | APB or AXI4-Lite registers and FIFOs | APB or AXI4-Lite registers and FIFOs | HCI registers on APB or AXI4-Lite; AXI4 manager for DMA | APB or AXI4-Lite manager; no registers to program |
| Software | Bare-metal C and Linux drivers, including HDR ternary | Bare-metal C and Linux drivers | Upstream Linux mipi-i3c-hci driver; bare-metal C driver | None required |
| Bus modes (peak at 12.5 MHz SCL) | ||||
| SDR | 12.5 Mbps | 12.5 Mbps | 12.5 Mbps | 12.5 Mbps |
| HDR-DDR | 25 Mbps | 25 Mbps | 25 Mbps | — |
| HDR-BT | 25 Mbps | 25 Mbps | Extended capability | — |
| HDR-BT Multi-Lane | x2 / x4: 50 / 100 Mbps | x2 / x4: 50 / 100 Mbps | Extended capability | — |
| HDR ternary (TSP / TSL) | ≈ 33 Mbps | — | — | — |
| SDR and HDR-DDR Multi-Lane | x2 / x4 | — | — | — |
| Legacy I2C devices | On the same bus | On the same bus | On the same bus | Acts as an I2C Target at a static address |
| Bus management | ||||
| Address assignment | ENTDAA, SETDASA, SETAASA; group addressing | ENTDAA, SETDASA, SETAASA; group addressing | ENTDAA and SETDASA from the Device Address Table | ENTDAA, SETNEWDA, RSTDAA |
| In-Band Interrupts, Hot-Join | With payload; Pending Read | With payload; Pending Read | Handled in hardware, with auto-reject | IBI from an input pin; Hot-Join |
| Secondary Controller | Role hand-off | Role hand-off (Controller / Target build; the Controller-only build passes the role) | — | — |
| Timing control | Synchronous mode and Async Mode 0 | Async Mode 0 | — | — |
| Device-to-Device Tunneling | Yes | — | — | — |
| Monitoring Device Early Termination | Yes | — | — | — |
| Error recovery | All error types; bus-recovery engine | All Basic v1.2 error types; bus-recovery engine | Halt on error and resume; bus recovery in hardware | Bus-manager errors reported in GETSTATUS; Target Reset |
Data rates by bus mode
Peak data rate during the data phase at the standard 12.5 MHz SCL. HDR ternary transfers data on both wires; Multi-Lane adds up to three data lanes beside SDA.
| Bus mode | Mbps | Cores |
|---|---|---|
| SDR | 12.5 | All |
| HDR-DDR | 25 | Basic, Full, HCI |
| HDR-BT | 25 | Basic, Full |
| HDR-TSP (ternary) | ≈ 33 | Full |
| SDR Multi-Lane x2 / x4 | 25 / 50 | Full |
| HDR-BT Multi-Lane x2 / x4 | 50 / 100 | Basic, Full |
| HDR-DDR Multi-Lane x2 / x4 | 50 / 100 | Full |
Raw rate during the data phase. Headers, commands and bus turnarounds reduce sustained throughput. The HCI core reaches HDR-BT and Multi-Lane through a Digital Blocks extended capability; the Target-to-AMBA Bridge uses SDR.
Every role on the bus
One I3C bus can carry the whole family: an HCI Host Controller under Linux as the Active Controller, a Controller / Target that can take the bus over, Targets with and without a processor, and legacy I2C devices on the same two wires.
Blue boxes are Digital Blocks IP.
Common features
I3C Basic and I3C Full share one Controller / Target engine; the HCI Host Controller runs the same Controller engine behind the standard HCI registers.
Transfers in hardware
Private reads and writes, broadcast and direct CCCs run from the FIFOs as whole frames, START to STOP, including CCCs in HDR-DDR and HDR-BT with flow control and early termination.
Bus configuration
Dynamic address assignment, static-address assignment (SETDASA, SETAASA), a parameterized device table, group addressing, In-Band Interrupts with payload, Pending Read, Hot-Join, and Target Reset with reset actions.
Error detection and recovery
Every I3C Basic v1.2 Controller and Target error type, a bus-recovery engine for stuck SDA, forced STOP and HDR Exit, and HDR parity and CRC checks with per-message status and error counters.
Specification versions
One netlist serves mixed-version buses: I3C Basic v1.1.1 behavior is selectable by register in I3C Basic, bus-wide or per Target, and I3C Full can run with I3C Basic v1.2 behavior.
Pads and clocks
Separate input, drive-low and push-pull enables for each line connect to standard I/O cells. Programmable open-drain and push-pull SCL rates; HDR ternary receive uses an always-on sampling clock of 100 MHz or more.
Implementation
Synthesizable SystemVerilog with no gated clocks and no internal tri-states, DFT scan-mode reset control, and APB or AXI4-Lite from the same RTL. Build options remove unused modes and roles from the gate count.
Verification and compliance
Which one do I need?
Deliverables
- Synthesizable SystemVerilog RTL for APB or AXI4-Lite, or an FPGA netlist
- Synopsys Design Constraints, filelists and lint scripts
- Self-checking test bench: AMBA bus models, I3C bus monitor, fault injection, MIPI I3C CTS tests and expected results
- C++ model
- Bare-metal C and Linux drivers; for HCI, a Linux device-tree fragment and integration note for the upstream driver
- Data sheet, Technical Reference Manual, Integration Guide, coverage report and CTS compliance report
Learn more about the I3C Controllers
Contact Digital Blocks for technical details, pricing and evaluation options.
More MIPI and serial interface IP
- DPI or DBI pixel input; 1 to 4 data lanes
- QQVGA to QSXGA, including FHD and QXGA
- AMBA APB, AHB or AXI4-Lite register interface
