Context Byte Value

Context Group

Context Description

0

None

Reserved, do not use

1 – 63

MIPI I3C Specification v1.Y Minor Version

Bits[7:6]: 2’b00

Bit[5]: I3C Specification Editorial Revision (within Minor Version)
     1’b0: Version 1.Y.0
     1’b1: Version 1.Y.1 or greater

Bit[4]: I3C Specification Family
     1’b0: MIPI I3C Specification
     Note: An I3C Master that supports the I3C Basic Specification shall not use the value 1’b0 in this field.
     1’b1: MIPI I3C Basic Specification

Bits[3:0]: I3C Specification Minor Version (v1.Y)
     4’b0000: Illegal, do not use (see Note below)
     (It would encode v1.0, but SETBUSCON was not available in I3C Basic v1.0)
     4’b0001 – 4’b1111: Version 1.1 – Version 1.15

Examples:  Bit[5]  Bit[4]   Bits[3:0]
     I3C Basic v1.1.0:  1’b0 || 1’b1 || 4’b0001 or 8’b00010001
     I3C Basic v1.1.1:  1’b1 || 1’b1 || 4’b0001 or 8’b00110001
     I3C Basic v1.2.0:  1’b0 || 1’b1 || 4’b0010 or 8’b00010010

64 – 127

Other MIPI Working Groups

Reserved for higher-level protocols defined by other MIPI Alliance specifications that use MIPI I3C for communications

128 – 191

Other Standards Organizations

128: MCTP for system manageability (conforming to the content protocol defined in the MCTP I3C Transport Binding Specification, released by DMTF, version 1.0 or newer)
129 – 191: Reserved for higher-level protocols defined by other standards developing organizations. The values are assigned by MIPI Alliance I3C WG

192 – 255

Vendor Custom

Available for private, per-vendor use (not tracked by MIPI Alliance)
 

Note:

An I3C Master that supports version 1.1 or greater of the full I3C Specification might emit the SETBUSCON CCC with Bit[4] set to 1’b0. In that case, an I3C Slave that supports version 1.1 or greater of the I3C Basic Specification should ignore Bit[4].

An I3C Master that supports any version of the I3C Basic Specification shall not emit the SETBUSCON CCC with Bit[4] set to 1’b0; for an I3C Basic Master, 1’b1 is the only valid value for Bit[4].