Description

Solution

This is a known issue with the DisplayPort v2.1, 2.2, and 2.3 cores. This issue has been resolved in the DisplayPort v3.1 core.

To work around this issue, users will need to do the following using the write status command:

1. Issue a Write Command (any length from 1 to 16)
2. Irrespective of the response from Write (except NACK), issue a write_status with MOT command to the same device address.
3. Repeat the same write_status command until a NACK response is received or until the number of bytes written is one less than the requested length.
4. Issue a 1 byte EDID READ - this is a dummy command which will clear the state machine to IDLE state.
5. Continue normal operations 

1. Write Burst -> On NACK exit -> Else go to Step 2 ->
2. Repeat Write Status with MOT until NACK is received or the number of bytes written is one less than the requested length to the same IIC (I2C)->
3. Issue Read to EDID 1 byte ->
4. Continue

Linked Answer Records

Master Answer Records