Datasheet

613
32117D–AVR-01/12
AT32UC3C
25.6.10 LIN Errors
25.6.10.1 Bit Error
This error is generated when USART is transmitting and if the transmitted value on the Tx line is
different from the value sampled on the Rx line. If a bit error is detected, the transmission is
aborted at the next byte border.
This error is reported by LINBE in the Channel Status Register (CSR).
25.6.10.2 Inconsistent Synch Field Error
This error is generated if the Synch Field character received is other than 0x55.
This error is reported by CSR.LINISFE
25.6.10.3 Identifier Parity Error
This error is generated if the parity of the identifier is wrong. This error can be generated only if
the parity feature is enabled (PARDIS = 0).
This error is reported by CSR.LINIPE
25.6.10.4 Checksum Error
This error is generated if the received checksum is wrong. Error bit is set to 1 only if the check-
sum feature is enabled (CHKDIS = 0).
This error is reported by CSR.LINCE
25.6.10.5 Slave Not Responding Error
This error is generated when the USART expects a response from another node (NACT = SUB-
SCRIBE) but no valid message appears on the bus within the time frame given by the maximum
length of the message frame, TFrame_Maximum (see Section 25.6.9.13). This error is disabled
if the USART does not expect any message (NACT = PUBLISH or NACT = IGNORE).
This error is reported by CSR.LINSNRE
25.6.10.6 Synch Tolerance Error
This error is generated if after the clock synchronization procedure it appears that the computed
baudrate deviation compared to the initial baudrate is superior to the maximum tolerance
FToI_Unsynch (+/- 15%).
This error is reported by CSR.LINSTE
25.6.10.7 Header Time-out Error
This error is generated if the Header is not entirely received within the time given by the maxi-
mum length of the Header, THeader_Maximum.
This error is reported by CSR.LINHTE