ST STM32L4+ Series Reference Manual page 969

RM0432
DSI host interrupt
Bit
& Status register
0 18
0 17
0 16
0 15
0 14
0 13
0 12
DSI Host (DSIHOST) applied to STM32L4R9xx and STM32L4S9xx only
Table 209. Error causes and recovery (continued)
Name Cause of the error
The D-PHY reports the False
Control Error.
PE2 The D-PHY detects an incorrect
line state sequence in lane 0
lines.
The D-PHY reports the LPDT
Error.
PE1 The D-PHY detects that the
LDPT did not match a multiple
of 8 bits.
The D-PHY reports the Escape
Entry Error.
PE0 The D-PHY does not recognize
the received Escape Entry
Code.
This error is directly retrieved
from Acknowledge with Error
AE15 packet.
The Device detected a protocol
violation in the reception.
The Acknowledge with Error
packet contains this error.
AE14
The Device chooses to use this
bit for error report.
The Acknowledge with Error
packet contains this error.
AE13 The Device reports that the
transmission length does not
match the packet length.
The Acknowledge with Error
packet contains this error.
AE12 The Device does not recognize
the VC ID in at least one of the
received packets.
RM0432 Rev 6
Recommended method
of handling the error
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.
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.
The D-PHY Host does not recognize the
Escape Entry Code. The Transmission is
ignored. The D-PHY Host recovers but the
system should repeat the RX 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.
Refer to the Device documentation
regarding possible reasons for this error
and take appropriate actions.
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, carefully analyze the connectivity
between the Host and the Device.
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, carefully analyze the connectivity
between the Host and the Device.
969/2301
1044