Vendor: Digital Blocks, Inc. Category: I2C / I3C

I3C Full Controller / Target

AMBA APB MIPI I3C v1.1 Controller / Target

Controller I3C View all specifications

Overview

The Digital Blocks DB-I3C-FULL-MS-APB IP Core connects an embedded processor on the AMBA APB bus to an I3C bus, compliant with the MIPI I3C v1.1 specification. It builds on the Digital Blocks I3C Basic core and adds the features of the full I3C specification: the HDR Ternary modes HDR-TSP and HDR-TSL, Synchronous Timing Control, Device-to-Device Tunneling, Monitoring Device Early Termination, and Multi Lane for SDR and HDR-DDR.

The core implements both I3C roles – Controller and Target – selected at run time, with Secondary Controller hand-off. At 12.5 MHz SCL it reaches 12.5 Mbps in SDR, 25 Mbps in HDR-DDR and HDR-BT, about 33 Mbps in HDR-TSP, and up to 100 Mbps with Multi Lane x4.

Ternary receive needs a time reference, so the SoC supplies an always-on sampling clock of at least 100 MHz (200 MHz recommended) while HDR Ternary is enabled. Every full specification feature is a build option, and a Basic-only build of the same RTL is an I3C Basic v1.2 device.

Key features

The Digital Blocks DB-I3C-FULL-MS-APB IP Core connects an embedded processor on the AMBA APB bus to an I3C bus, compliant with the MIPI I3C v1.1 specification. It builds on the Digital Blocks I3C Basic core and adds the features of the full I3C specification: the HDR Ternary modes HDR-TSP and HDR-TSL, Synchronous Timing Control, Device-to-Device Tunneling, Monitoring Device Early Termination, and Multi Lane for SDR and HDR-DDR.

The core implements both I3C roles – Controller and Target – selected at run time, with Secondary Controller hand-off. At 12.5 MHz SCL it reaches 12.5 Mbps in SDR, 25 Mbps in HDR-DDR and HDR-BT, about 33 Mbps in HDR-TSP, and up to 100 Mbps with Multi Lane x4.

Ternary receive needs a time reference, so the SoC supplies an always-on sampling clock of at least 100 MHz (200 MHz recommended) while HDR Ternary is enabled. Every full specification feature is a build option, and a Basic-only build of the same RTL is an I3C Basic v1.2 device.

 

 

  • Dual-role MIPI I3C v1.1 Controller / Target, role selected at run time; Controller only and Target-only configurations
  • All DB-I3C-BASIC-MS-APB Rel 1.2.0 features: SDR, HDR-DDR, HDR-BT with Multi-Lane, Secondary Controller, device table, static and group addressing, error recovery, Asynchronous Timing Control Mode 0
  • Bus modes and data rates at 12.5 MHz SCL:
    • SDR – 12.5 Mbps; legacy I2C devices on the same bus
    • HDR-DDR – 25 Mbps
    • HDR-TSP / HDR-TSL (ternary) – about 33 Mbps
    • HDR-BT – 25 Mbps; Multi-Lane x2 / x4 – 50 / 100 Mbps
    • SDR and HDR-DDR Multi-Lane x2 / x4 – build option
  • HDR Ternary (HDR-TSP, and HDR-TSL for buses with legacy I2C devices):
    • Controller and Target, including CCCs and flow control in ternary mode
    • Target receive sampled by an always-on clock: 100 MHz minimum, 200 MHz or 100 MHz both-edge sampling recommended; decode window programmable
    • Clock tree gated inside the core until a ternary transfer starts (planned)
  • Timing Control:
    • Synchronous mode – Controller SYNC ticks and Target event time stamps
    • Asynchronous Mode 0 – time-stamped In-Band Interrupts
  • Device-to-Device Tunneling: Target-to-Target data through the Controller's tunneling CCC, with the core as source or receiver
  • Monitoring Device Early Termination: a monitoring device can stop a transfer in progress; Controller support for the resulting arbitration
  • Specification profile: I3C v1.1 by default, I3C Basic v1.2 behavior selectable by register on the same netlist
  • Separate TX and RX FIFOs, parameterized (256 bytes by default)
  • Integration:
    • APB, or AXI4-Lite from the same RTL
    • Single interrupt with per-source mask and status
    • Build options for each full-specification feature; Basic-only build
    • Synthesizable SystemVerilog; constraints supplied for the SCL, time-stamp and ternary sampling clock domains; DFT scan-mode reset control
    • Bare-metal C and Linux drivers, including HDR-DDR and HDR Ternary transfers in the Linux I3C subsystem
  • Compliance:
    • MIPI I3C Specification v1.1 (full), with v1.1.1 errata
    • MIPI I3C Basic v1.2 in the Basic-only build; MIPI I3C CTS
    • NXP I2C-bus specification UM10204; AMBA APB

Block Diagram

What’s Included?

The DB-I3C-FULL-MS-APB is available as synthesizable SystemVerilog RTL or an FPGA netlist, with Synopsys Design Constraints, the simulation test bench with expected results, a C++ model, bare-metal C and Linux drivers, and documentation: datasheet, Technical Reference Manual, Integration Guide, coverage report and compliance report.

Specifications

Identity

Part Number
DB-I3C-FULL-MS-APB
Vendor
Digital Blocks, Inc.
Type
Silicon IP
Controller / PHY
Controller

Standards & Interfaces

Protocol Support
I3C

Files

Note: some files may require an NDA depending on provider policy.

Provider

Learn more about I2C / I3C IP core

From I2C to I3C: Evolution of Two-Wire Communication in Embedded Systems

The I2C (Inter-Integrated Circuit) Bus invented in 1980 by Philips Semiconductors (NXP Semiconductors today) was a massive step forward in simplifying communications in embedded systems. It is a simple two-wire interface for synchronous, multi-master/multi-slave, single ended serial communication. Fast forward 45 years to today and it is still widely used for attaching low speed peripheral Integrated Circuits (ICs), processors and microcontrollers. But silicon today has changed...

Maximizing the Usability of Your Chip Development: Design with Flexibility for the Future

Early in my career selling chips for Motorola Semiconductor, the ability to spin derivative microcontroller chips for a customer’s specific requirement was relatively straightforward. If the volume looked reasonable, we would tape-out a new chip with a few added features because mask costs and wafers were relatively inexpensive at the larger process nodes. The customer won by getting an MCU tailored to their specific need, and Motorola won by gaining a more committed customer plus another SKU that could be sold to other customers – boosting ROI. With the migration to higher cost FinFET nodes, those times are long gone as the economics no longer work.

MIPI CCI over I3C: Faster Camera Control for SoC Architects

Imagine a camera subsystem that responds in microseconds, consumes less power, and offers a more straightforward route to time-to-market. For SoC architects and IP integration teams, that vision is increasingly possible with MIPI Camera Control Interface (CCI) over I3C.

Frequently asked questions about I2C / I3C IP cores

What is I3C Full Controller / Target?

I3C Full Controller / Target is a I2C / I3C IP core from Digital Blocks, Inc. listed on Semi IP Hub.

How should engineers evaluate this I2C / I3C?

Engineers should review the overview, key features, supported foundries and nodes, maturity, deliverables, and provider information before shortlisting this I2C / I3C IP.

Can this semiconductor IP be compared with similar products?

Yes. Buyers can compare this product with similar semiconductor IP cores or IP families based on category, provider, process options, and structured technical specifications.

×
Semiconductor IP