Broadcast CCC Write Transfers
The Broadcast CCC Write transfers are initiated on the bus based on the COMMAND_PORT settings as shown in the following table.
| Command Attribute | Field Name | Programmed Value | Description |
|---|---|---|---|
| Transfer Command | CP | 1 | Indicates to the I3CC to consider the CMD field. |
| CMD[14] | 0 | Indicates to the I3CC that the transfer is Broadcast CCC transfer. | |
| CMD[13:7] | 0x0 – 0x7F | Indicates to the CCC command to be transferred. | |
| DEV_INDEX | NA | This field is not used since the transfer is Broadcast CCC. | |
| MODE | 0 (SDR0) | Indicates to the I3CC that the transfer must go in SDR mode. All CCC transfers are initiated with SDR0 Speed. | |
| CMD_ATTR | 0 or 1 | 0: Indicates to the I3CC to consider the transmit data from the Transmit FIFO if RnW is set to ‘0’. 1: Indicates to the I3CC to consider the transmit data from the command if RnW is set to ‘0’. | |
| RnW | 0 | Indicates the transfer is either write or read transfer. 0: Write Transfer 1: Read Transfer | |
| Regular Transfer (CMD_ATTR=0) | DATA_LENGTH | 0 - 65535 | Indicates the transfer length of the transfer. |
| Immediate Transfer (CMD_ATTR=1) | BYTE_CNT | 0 to 4 | Indicates the respective data bytes of Immediate command are valid. |
Data in the transmit FIFO (Regular transfer) or data bytes (Immediate Data Transfer) are not required for some broadcast CCCs which do not have payload data indicated through DATA_LENGTH (Regular transfer) or BYTE_CNT (Immediate transfer). If the Broadcast CCC does not consist of a payload, this must be indicated by a zero in either DATA_LENGTH or BYTE_CNT fields based on the command issued.
The I3CC halts if a NACK is received for the address header of the Broadcast CCC transfer. The I3CC updates ERR_STATUS in the Response Data structure with appropriate error information, halts the I3CC and gives back the control to the application to resume the operation of the I3CC through writing ‘1’ to I3CC_HC_CONTROL.RESUME.