5.5.6.7 Error Handling
The interrupts triggered by the Interrupt Status registers 0 and 1 (DSI_INT_ST0 and DSI_INT_ST1) are error conditions.
The two following tables provide the causes that trigger these interrupts and also explain how to recover from them.
Bit | Name | Cause of the Error | Recommended Method of Handling the Error |
---|---|---|---|
20 | DPHY_ERRORS_4 | The D-PHY reports the LP1 contention error. The D-PHY host detects the contention while trying to drive the line high. | Recover the D-PHYs from contention. Reset the DSI host and transmit the packets again. If this error is recurrent, analyze the connectivity between the host and the device carefully. |
19 | DPHY_ERRORS_3 | D-PHY reports the LP0 contention error. The D-PHY host detects the contention while trying to drive the line low. | Recover the D-PHYs from contention. Reset the DSI host and transmit the packets again. If this error is recurrent, analyze the connectivity between the host and the device carefully. |
18 | DPHY_ERRORS_2 | The D-PHY reports the False Control Error. The D-PHY detects an incorrect line state sequence in lane 0 lines. | Device does not behave as expected. Communication with the device is not properly established. This is an unrecoverable error. Reset the DSI host and the D-PHY. If this error is recurrent, analyze the behavior of the device. |
17 | DPHY_ERRORS_1 | The D-PHY reports the LPDT Error. The D-PHY detects that the LDPT did not match a multiple of 8 bits. | The data reception is not reliable. The D-PHY recovers but the received data from the device might not be reliable. It is recommended to reset the DSI host and repeat the RX transmission. |
16 | DPHY_ERRORS_0 | The D-PHY reports the Escape Entry Error. The D-PHY does not recognize the received Escape Entry Code. | The D-PHY does not recognize the Escape Entry Code. The Transmission is ignored. The D-PHY host recovers but the system should repeat the RX reception. |
15 | ACK_WITH_ERR_15 | This error is directly retrieved from Acknowledge with Error packet. The device detected a protocol violation in the reception. | Refer to the display documentation. When this error is active, the device should have another read-back command that reports additional information about this error. Read the additional information and take appropriate actions. |
14 | ACK_WITH_ERR_14 | The Acknowledge with Error packet contains this error. The device chooses to use this bit for error report. | Refer to the device documentation regarding possible reasons for this error and take appropriate actions. |
13 | ACK_WITH_ERR_13 | The Acknowledge with Error packet contains this error. The device reports that the transmission length does not match the packet length. | Possible reason for this is multiple errors present in the packet header (more than 2), so the error detection fails and the device does not discard the packet. In this case, the packet header is corrupt and can cause decoding mismatches. Transmit the packets again. If this error is recurrent, analyze the connectivity between the host and the device carefully. |
12 | ACK_WITH_ERR_12 | The Acknowledge with Error packet contains this error. The device does not recognize the VC ID in at least one of the received packets. | Check the device capabilities and configure the host to properly address the device VC ID. Repeat the transmission. |
11 | ACK_WITH_ERR_11 | The Acknowledge with Error packet contains this error. The device does not recognize the data type of at least one of the received packets. | Check the device capabilities. It is possible that there are some packets that are not supported by the device. Repeat the transmission. |
10 | ACK_WITH_ERR_10 | The Acknowledge with Error packet contains this error. The device detects the CRC errors in at least one of the received packets. | Some of the long packets, transmitted after the last Acknowledge request, might contain the CRC errors in the payload. If the payload content is critical, transmit the packets again. If this error is recurrent, analyze the connectivity between the host and the device carefully. |
9 | ACK_WITH_ERR_9 | The Acknowledge with Error packet contains this error. The device detects multi-bit ECC errors in at least one of the received packets. | The device does not interpret the packets transmitted after the last Acknowledge request. If the packets are critical, transmit the packets again. If this error is recurrent, analyze the connectivity between the host and the device carefully. |
8 | ACK_WITH_ERR_8 | The Acknowledge with Error packet contains this error. The device detects and corrects the 1 bit ECC error in at least one of the received packets | No action is required. The device acknowledges the packet. If this error is recurrent, analyze the signal integrity or the noise conditions of the link. |
7 | ACK_WITH_ERR_7 | The Acknowledge with Error packet contains this error. The device detects the Line Contention through LP0/LP1 detection. | This error might corrupt the low-power data reception and transmission. Ignore the packets and transmit them again. The device recovers automatically. If this error is recurrent, check the device capabilities and the connectivity between the host and device. |
6 | ACK_WITH_ERR_6 | The Acknowledge with Error packet contains this error. The device detects the False Control Error. | The device detects one of the following:
|
5 | ACK_WITH_ERR_5 | The Acknowledge with Error packet contains this error. The display timeout counters for a HS reception and LP transmission expire. | It is possible that the host and device timeout counters are not correctly configured. The device HS_TX timeout should be shorter than the host HS_RX timeout. Host LP_RX timeout should be longer than the device LP_TX timeout. Check and confirm that the host configuration is consistent with the device specifications. This error is automatically recovered, although there is no guarantee that all the packets in the transmission or reception are complete. |
4 | ACK_WITH_ERR_4 | The Acknowledge with Error packet contains this error. The device reports that the LPDT is not aligned in an 8-bit boundary | There is no guarantee that the device properly receives the packets. Transmit the packets again. |
3 | ACK_WITH_ERR_3 | The Acknowledge with Error packet contains this error. The device does not recognize the Escape Mode Entry command. | The device does not recognize the Escape Mode Entry code. Check the device capability. Repeat the transmission to the device. |
2 | ACK_WITH_ERR_2 | The Acknowledge with Error packet contains this error. The device detects the HS transmission did not end in an 8-bit boundary when the EoT sequence is detected. | There is no guarantee that the device properly received the packets. Re-transmission should be performed. Transmit the packets again. |
1 | ACK_WITH_ERR_1 | The Acknowledge with Error packet contains this error. The device detects that the SoT leader sequence is corrupted. | The device discards the incoming transmission. Re-transmission should be performed by the host. |
0 | ACK_WITH_ERR_0 | The Acknowledge with Error packet contains this error. The device reports that the SoT sequence is received with errors but synchronization can still be achieved. | The device is tolerant to single bit and some multi-bit errors in the SoT sequence. Yet, the packet correctness is compromised. If the packet content was important, transmit the packets again. |
Bit | NAME | Cause of the Error | Recommended Method of Handling the Error |
---|---|---|---|
12 | GEN_PLD_RECV_ERR | An overflow occurs in the Generic read FIFO. | The Read FIFO size is not correctly dimensioned for the maximum read-back packet size. Configure the device to return the read data with a suitable size for the host dimensioned FIFO. Data stored in the FIFOs is corrupted. Reset the DSI host and repeat the read procedure. |
11 | GEN_PLD_RD_ERR | An underflow occurs in the Generic read FIFO. | System does not wait for the read procedure to end and starts retrieving the data from the FIFO. The read data is requested before it is fully received. Data is corrupted. Reset the DSI host and repeat the read procedure. Check that the read procedure is completed before reading the data through the User interface. |
10 | GEN_PLD_SEND_ERR | An underflow occurs in the Generic write payload FIFO. | The system writes the packet header before the respective packet payload is completely loaded into the payload FIFO. This error is unrecoverable, the transmitted packet is corrupted. Reset the DSI host and repeat the write procedure. |
9 | GEN_PLD_WR_ERR | An overflow occurs in the Generic write payload FIFO. | The payload FIFO size is not correctly dimensioned to store the total payload of a long packet. Data stored in the FIFOs is corrupted. Reset the DSI host and repeat the write procedure. |
8 | GEN_CMD_WR_ERR | An overflow occurs in the Generic command FIFO. | The command FIFO size is not correctly dimensioned to store the total headers of a burst of packets. Data stored in the FIFOs is corrupted. Reset the DSI host and repeat the write procedure. |
7 | DPI_PLD_WR_ERR | An overflow occurs in the DPI pixel payload FIFO. | The controller FIFO dimensions are not correctly set up for the operating resolution. Check the Video Mode configuration registers. They should be consistent with the LCDC video resolution. The pixel data sequence is corrupted. Reset the DSI host and re-initiate the Video transmission. |
6 | EOPT_ERR | Host receives a transmission that does not end with an End of Transmission packet. | This error is not critical for the data integrity of the received packets. Check if the device supports the transmission of EoTp packets. |
5 | PKT_SIZE_ERR | Host receives a transmission that does not end in the expected by boundaries. | The integrity of the received data cannot be guaranteed. Reset the DSI host and repeat the read procedure. |
4 | CRC_ERR | Host reports that a received long packet has a CRC error in its payload. | The received payload data is corrupted. Reset the DSI host and repeat the read procedure. If this error is recurrent, check the DSI connectivity link for the noise levels. |
3 | ECC_MULTI_ERR | Host reports that a received packet contains multiple ECC errors. | The received packet is corrupted. The DSI host ignores all the following packets. The DSI host should repeat the read procedure. |
2 | ECC_SINGLE_ERR | Host reports that a received packet contains a single bit error. | This error is not critical because the DSI host can correct the error and properly decode the packet. If this error is recurrent, check the DSI connectivity link for signal integrity and noise levels. |
1 | TO_LP_RX | Host reports that the configured timeout counter for the low-power reception has expired. | Once the configured timeout counter ends, the DSI host automatically resets the controller side and recovers to normal operation. Packet transmissions happening during this event are lost. If this error is recurrent, check the timer configuration for any issue. This timer should be greater than the maximum low-power transmission generated by the device. |
0 | TO_HS_TX | Host reports that the configured timeout counter for the high-speed transmission has expired. | Once the configured timeout counter ends, the DSI host automatically resets the controller side and recovers to normal operation. Packet transmissions happening during this event are lost. If this error is recurrent, check the timer configuration for any issue. This timer should be greater than the maximum high-speed transmission bursts generated by the host. |