Introduction¶
This document describes the open source I3C Basic controller developed as part of the Caliptra project within CHIPS Alliance. .
The scope of the project includes:
Secondary Controller Mode
Active Controller Mode
Extended Capabilities from the Specification for I3C Vendor-Specific Extended Capabilities
Note
Secondary Controller Mode with generic TX/RX transfers can serve the same role as an I3C Target Device with support for Legacy I2C communication.
Reference documents¶
The I3C Core provides a Controller Interface which is developed in compliance with:
- I3C basic spec¶
MIPI Alliance Specification for I3C Basic, Version 1.1.1
- I3C HCI spec¶
MIPI Alliance Specification for I3C HCI, Version 1.2
- I3C TCRI spec¶
MIPI Alliance Specification for I3C TCRI, Version 1.0
The specification documents can be obtained directly from the MIPI website, however, a login with a MIPI Alliance account is required.
Some terminology of the MIPI Alliance Specifications carry over to this documentation and requires additional context:
Active Controller Mode
is the mode in which the I3C Core initiates transfers on the I3C bus and is primarily responsible for bus initialization and managementSecondary Controller Mode
is the mode, in which the I3C Core joins the I3C Bus as a Target Device and is conditionally responsible for specific bus management tasksSecondary Controller Mode
andStandby Controller Mode
are used interchangeablyController Interface
andHost Controller Interface
are used interchangeablyController Interface
is the Register Interface provided by the I3C Core