24.4.4.5.1 Broadcast CCC Write Transfers

Figure 24-16. Broadcast CCC Transfer

The Broadcast CCC Write transfers are initiated on the bus based on the I3CxCMDQUE settings, as shown in Table 24-9.

Table 24-9. Broadcast CCC Write Transfer Required Programming Values
Command AttributeBit FieldProgrammed ValueDescription

Transfer Command

CP

1

Indicates to the controller to consider the CMD field.

CMD[14]

0

Indicates to the controller that the transfer is a Broadcast CCC transfer.

CMD[13:7]

0x0 – 0x7F

Indicates the CCC command to be transferred.

DEV_INDX

NA

This field is not used since the transfer is a Broadcast CCC.

SPEED

0 (SDR0) or 7 (I2C FM)
Indicates to the Controller that the transfer should go in SDR0 Speed/Mode or I2C FM Speed.
Note: All CCC transfers are initiated with SDR0 Speed in I3C bus topology. CCC transfers can be either initiated with SDR0 or I2C FM speed based on the context of the bus in JEDEC bus topology.

DBP

0 or 1

Indicates whether the defining byte is present for Broadcast CCC transfer or not.

1: Defining byte is present

0: Defining byte is not present

SDAP

0 or 1

1: Indicates the Controller to consider the transmit data from the command if RnW is set to 0.

0: Indicates to consider the transmit data from

the Transmit FIFO if RnW is set to 0.

RnW

0

Indicates whether the transfer is a write or read transfer.

1: Read Transfer

0: Write Transfer

TGT_RST

0 or 1

Indicates whether the Controller should generate

Target Reset Pattern at the end of the Broadcast

RSTACT CCC transfer.

1: Target Reset Pattern is generated.

0: Target Reset Pattern is not generated.

PEC

0 or 1

Indicates whether Packet Error Check is enabled

for Broadcast CCC transfer.

1: PEC check is enabled.

0: PEC check is disabled.

Transfer Argument (SDAP=0)

DATA_LENGTH

0 - 65535

Indicates the transfer length of the transfer.

Short Data Argument (SDAP=1)

BYTE_STRB

0, 1, 3,7

Indicates that the respective data bytes of the Immediate command are valid.

Note:
  1. The data in Tx-FIFO (Transfer Argument) or Data Bytes (Short Data Argument) are not required for some broadcast CCCs which do not have payload data indicated through Data Length (Transfer Argument) or BYTE_STRB (Short Data Argument). If the Broadcast CCC does not consist of a payload, then you must indicate it with zero in either the Data Length or BYTE_STRB fields based on the command issued.
  2. The Controller halts in case of receiving a NACK (no I3C device on the bus) for the address header of the Broadcast CCC transfer. The Controller updates the ‘ERR_STS’ field with appropriate error information in the Response status (I3CxRESPQUE), halts the Controller, and gives back control to the application to resume the operation of the Controller by writing ‘1’ to the I3CxCNTRL [RESUME] bit after taking suitable action.