I3C (bus)

Uses your system voice; voice and rate in settings.

Snapshot

≈ 13 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

I3C or I³C, also known as SenseWire, is a specification to enable communication between microchips by defining the electrical connection between the chips and signaling patterns to be used. Short for Improved Inter-Integrated Circuit, the standard defines the electrical connection between the chips to be a two wire, shared (multidrop), serial data bus, one wire ( SCL ) being used as a clock to define the sampling times, the other wire ( SDA ) being used as a data line whose voltage can be sampled.

The standard defines a signaling protocol in which multiple chips can control communication and thereby act as the bus controller. The I3C specification takes its name from, uses the same electrical connections as, and allows some backward compatibility with, the I²C bus, a de facto standard for inter-chip communication, widely used for low-speed peripherals and sensors in electronic devices.

The I3C standard is designed to retain some backward compatibility with the I²C system, notably allowing designs where existing I²C devices can be connected to an I3C bus but still have the bus able to switch to a higher data rate for communication at higher speeds between compliant I3C devices.…

I3C or I³C, also known as SenseWire, is a specification to enable communication between microchips by defining the electrical connection between the chips and signaling patterns to be used. Short for Improved Inter-Integrated Circuit, the standard defines the electrical connection between the chips to be a two wire, shared (multidrop), serial data bus, one wire ( SCL ) being used as a clock to define the sampling times, the other wire ( SDA ) being used as a data line whose voltage can be sampled.

The standard defines a signaling protocol in which multiple chips can control communication and thereby act as the bus controller. The I3C specification takes its name from, uses the same electrical connections as, and allows some backward compatibility with, the I²C bus, a de facto standard for inter-chip communication, widely used for low-speed peripherals and sensors in electronic devices.

The I3C standard is designed to retain some backward compatibility with the I²C system, notably allowing designs where existing I²C devices can be connected to an I3C bus but still have the bus able to switch to a higher data rate for communication at higher speeds between compliant I3C devices. The I3C standard thereby combines the advantage of the simple, two wire I²C architecture with the higher communication speeds common to higher pin count buses such as the Serial Peripheral Interface (SPI).

The I3C standard was developed as a collaborative effort between electronics and computer-related companies under the auspices of the MIPI Alliance. The I3C standard was first released to the public at the end of 20171, although access requires the disclosure of private information. Google and Intel have backed I3C as a sensor interface standard for Internet of things (IoT) devices.

History

Goals of the MIPI Sensor Working Group effort were first announced in November 2014 at the MEMS Executive Congress in Scottsdale, Arizona, United States. Electronic design automation tool vendors including Cadence, Synopsys and Silvaco have released controller IP blocks and associated verification software for the implementation of the I3C bus in new integrated circuit designs.

In December 20161, Lattice Semiconductor integrated I3C support into its new FPGA known as an iCE40 UltraPlus. In 2017, Qualcomm announced the Snapdragon 845 mobile SOC with integrated I3C controller support. In December 2017, the I3C 1.0 specification was released for public review.

Around same time, a Linux kernel patch introducing support for I3C was proposed by Boris Brezillon. In 20211, DDR5 adopted I3C for its serial presence detect functions. In June 2022, Renesas Electronics introduced the first I3C Intelligent switch products.

SNIA's Enterprise and Data Center Standard Form Factor version 3.1 (January 2023) describes the use of I3C Basic in managing PCI Express devices. NVM Express 2.1 (August 2024) is reworded to allow the use of I3C, "to match the new conventions used by SNIA SFF TA's EDSFF and PCI-SIG specifications for I3C".

Goals

Prior to public release of the specification, a substantial amount of general information about it was published in the form of slides from the 2016 MIPI DevCon. The goals for this interface were based on a survey of MIPI member organizations and MEMS Industry Group (MIG) members. The results of this survey have been made public.

I3C v1.0

The initial I3C design sought to improve over I²C in the following ways: Two-pin interface that is a superset of the I²C standard. Legacy I²C target devices can be connected to the newer bus. Low-power and space-efficient design intended for mobile devices (smartphones and IoT devices.)

In-band interrupts over the serial bus rather than requiring separate pins. In I²C, interrupts from peripheral devices typically require an additional non-shared pin per package. Single data rate (SDR) throughput between 10 and using CMOS I/O levels.

High data rate (HDR) modes permitting multiple bits per clock cycle. These support throughput comparable to SPI while requiring only a fraction of I²C Fast Mode power.

A standardized set of common command codes Command queue support Error Detection and Recovery (parity check in SDR mode and 5 bit CRC for HDR modes) Dynamic address assignment (DAA) for I3C targets, while still supporting static addresses for I²C legacy devices I3C traffic is invisible for legacy I²C devices when equipped with I²C spike filters, achieved by SCL HIGH times of less than 50 ns Hot-join (some devices on the bus may be powered on/off during operation) Multi-controller operation with a well-defined protocol for hand-off between controllers

I3C Basic Specification

After making the I3C 1.0 standard publicly accessible, the organization subsequently published the I3C Basic specification, a subset intended to be implementable by non-member organizations under a RAND-Z license. I3C Basic allows royalty-free implementation of I3C, and is intended for organizations that may view MIPI membership as a barrier for adoption.

The basic version includes many of the protocol innovations in I3C 1.0, but lacks some of the potentially more difficult-to-implement ones such as the optional high data rate (HDR) modes like DDR. None the less the default SDR mode at up to is a major speed/capacity improvement over I²C.

I3C v1.1

Published in December 20191, this specification is only available to MIPI members.

I3C v1.1.1

Published in June 2021, it has deprecated the terms "master/slave" and now uses the updated normative terms "controller/target." The technical definitions of such devices, and their roles on an I3C bus, remain unchanged.

Signal pins

I3C uses the same two signal pins as I²C, referred to as SCL (serial clock) and SDA (serial data). The primary difference is that I²C operates them as open-drain outputs at all times, so its speed is limited by the resultant slow signal rise time.

I3C uses open-drain mode when necessary for compatibility, but switches to push-pull outputs whenever possible, and includes protocol changes to make it possible more often than in I²C. SCL is a conventional digital clock signal, driven with a push-pull output by the current bus controller during data transfers. (Clock stretching, a rarely used I²C feature, is not supported.)

In transactions involving I²C target devices, this clock signal generally has a duty cycle of approximately 50%, but when communicating with known I3C targets, the bus controller may switch to a higher frequency and/or alter the duty cycle so the SCL high period is limited to at most 40 ns. SDA carries the serial data stream, which may be driven by either controller or target, but is driven at a rate determined by the controller's SCL signal.

For compatibility with the I²C protocol, each transaction begins with SDA operating as an open-drain output, which limits the transmission speed. For messages addressed to an I3C target, the SDA driver mode switches to push-pull after the first few bits in the transaction, allowing the clock to be further increased up to 12.5 MHz.

This medium-speed feature is called single data rate (SDR) mode. Generally, SDA is changed just after the falling edge of SCL, and the resultant value is received on the following rising edge. When the controller hands SDA over to the target, it likewise does so on the falling edge of SCL.

However, when an I3C target is handing back control of SDA to the controller (e.g. after acknowledging its address before a write), it releases SDA on the rising edge of SCL, and the controller is responsible for holding the received value (re-driving a copy of the target's bit) for the duration of SCL high. Because the controller drives SCL, it will see the rising edge first, so there will be a brief period of overlap when both are driving SDA, but as they are both driving the same value, no bus contention occurs.

HDR-DDR (double data rate) mode

The HDR-DDR mode uses double data rate signaling on the SDA line with a 12.5 MHz clock to achieve a raw data rate ( effective). This requires changing the SDA line while SCK is high, a violation of the I²C protocol, but as the high-going pulse is only 40 ns long, I²C devices will ignore it and thus not notice the violation.

HDR-DDR accompanies each 16-bit data word with a 2-bit preamble and a 2-bit odd parity postamble, making 20 bits. Each word starts with a rising edge on SCK. The preamble has three possible states: 01: Command word (before data) or CRC word (after data) follows.

10: First data word follows. Abort by controller if seen subsequently. 11: Subsequent data word follows.

NACK by target if seen initially. If a controller sees a preamble of "11" immediately after a command, that indicates that no target is responding and is treated the same as a NACK in SDR mode. To ensure the SDA line will be seen high if no target responds, the extra bit in the command and address word is set so that the final parity bit sent by the controller is 1.

For subsequent words during read operations (from target to controller), the target drives the first preamble bit high, but releases the bus (allowing the pull-up resistors to maintain SDA high) for the second bit. The controller may drive SDA low during the second bit time (the falling edge of SCL) to request the read be aborted.

If not aborted, a message is terminated with a 13-bit CRC word. This has a preamble of 01, a fixed pattern of 1100 (other patterns are reserved for future use), then a 5-bit cyclic redundancy check on the full message (including the command/address word, but not the preamble or parity bits, or any part of the CRC word), and two "1" bits (the first driven, the second passively held high so the controller can take over).

This leaves the bus with both SCK and SDA high, after which the controller must generate an HDR restart or exit.

HDR ternary symbol modes

The HDR-TSP and HDR-TSL modes use one of three symbols as ternary digits (trits): Two bytes plus two even parity bits (18 bits total) are broken into six 3-bit triplets, and each triplet is encoded as two trits. (The 3 bits are taken msbit-first to produce a value from 0–7, which is then converted to two trits using the numeric values in the list above, and sent most significant trit first.)

Sent at , this achieves a effective data rate. The trit pair 22 consisting of two transitions of SDA only is not used to encode data, and is instead used to encode the HDR restart and HDR exit sequences which terminate a message.

Although this limits the maximum time between SCL transitions to three trit times, that exceeds the 50 ns limit for legacy I²C devices, so HDR-TSP (ternary symbol, pure) mode may only be used on a bus without legacy I²C devices. To permit buses including I²C devices (with a spike filter), the HDR-TSL (ternary symbol, legacy) mode must be used.

This maintains I²C compatibility by trit stuffing: after any rising edge on SCL, if the following trit is not 0, a 1 trit (transition on SCL only) is inserted by the sender, and ignored by the receiver. This ensures that SCL is never high for more than one trit time, but at the cost of transmitting 2.67 trits per 3 bits of payload, a effective data rate (assuming random data).

In ternary symbol mode, the controller finishes a read command by leaving the SDA and SCL lines high, after which the target drives both of them at whatever rate it wishes. There is no provision for the controller to interrupt the read operation; if the controller does not trust the target to stop on time, it must choose a different transmission mode.

When it is done transmitting, the target hands the bus back to the controller as follows: The target sets SDA high and SCL low. If the bus was not already in this state, the transition will be interpreted by the controller as a trit, but it will be ignored as is it not part of a 12-trit group.

The target toggles SDA three times (trit 2), leaving both SDA and SCL low, then releases (ceases to drive) the bus within one trit time (half-clock cycle) As soon as the controller sees the third SDA-only edge, it takes over driving SDA and SCL low. After at least one trit time (half-clock cycle), it then drives SDA high, and continues to complete either an HDR restart (by driving SCL high) or an HDR exit (by toggling SDA three more times, then driving SCL high), as it wishes.

Note that ternary data mode does not include a CRC.

I3C specification MIPI

Text derived from https://en.wikipedia.org/w/index.php?oldid=1362889212 under CC BY-SA 4.0; modifications have been made.

References

  1. ↩Wikipedia “I3C (bus)” revision 1362889212 · retrieved 2026-10-20 publication date (×4) · confidence 0.95 revision URL