MIPI I3C v1.1.1 is an editorial update of MIPI I3C v1.1 that contains no new features or capabilities, but resolves issues, clarifies, and improves on the I3C v1.1 specification.

MIPI I3C v1.1.1 includes:

  • Fixes for inconsistencies and other issues that were technical errors in MIPI I3C v1.1 (including
  • all issues resolved by Errata 01)
  • Clarifications to the requirements and procedures used for Dynamic Address Assignment, Hot-Join Requests and In-Band Interrupts
  • Clarifications to Target Error Types TE0, TE5, and TE6
  • Improved clarity and fixes for issues in the sections that define CCC flows in HDR Modes (generic as well as HDR Mode–specific)
  • Additional clarifications and explanations in some sections that did not fully explain new features and capabilities introduced with I3C v1.1
  • Better explanations of I3C Devices that support advanced features, such as composite I3C Devices that present multiple I3C Target roles (i.e., Virtual Targets)
  • Additional clarifications concerning the intersection of several of these new features and capabilities when implemented together (i.e., when used in concert in the same I3C Bus with I3C Devices that choose to support several or all such features or capabilities concurrently)
  • Limited allowances for flexibility in how certain new features and capabilities could be applied, or which of these new features and capabilities might be regarded as required, optional, or conditionally required per use case
  • Improved descriptions for Multi-Lane Device configuration, including clarified requirements for I3C Devices that present multiple Dynamic Addresses and/or support Group Addressing
  • Additional diagrams for HDR-BT Mode, including the 1-Lane forms of the structured protocol elements (i.e., Blocks) that are used in HDR-BT transfers, as well as an example of an HDR-BT transfer
  • Improved descriptions of error detection and recovery methods, such as Error Type TE0 and Error Type DBR (Dead Bus Recovery)
  • Changes to the Multi-Lane signaling of the Header Byte in SDR Mode
FAQ Type: