Datasheet

The hardware does not undertake any correction. However, the LIN slave application has to solve
this as:
– known identifier (parity bits corrupted)
– or corrupted identifier to be ignored
– or new identifier
• LSERR = LIN Synchronization ERRor. A LIN synchronization error will be flagged if a slave detects
the edges of the SYNCH field outside the given tolerance.
• LFERR = LIN Framing ERRor. A framing error will be flagged if dominant STOP bit is sampled.
Same function in UART mode.
• LTOERR = LIN Time Out ERRor. A time-out error will be flagged if the MESSAGE frame is not fully
completed within the maximum length T
Frame_Maximum
by any slave task upon transmission of the
SYNCH and IDENTIFIER fields (see Section Frame time out).
• LOVERR = LIN OVerrun ERRor. Overrun error will be flagged if a new command (other than LIN
Abort) is entered while ‘Busy signal’ is present.
In UART mode, an overrun error will be flagged if a received byte overwrites the byte stored in the
serial input buffer.
• LABORT. LIN abort transfer reflects a previous LIN Abort command (LCMD[2..0] = 000) while ‘Busy
signal’ is present.
After each LIN error, the LIN controller stops its previous activity and returns to its withdrawal mode
(LCMD[2..0] = 000
b
) as illustrated in Figure 21-11.
Writing 1 in LERR of LINSIR register resets LERR bit and all the bits of the LINERR register.
21.5.10. Frame time out
According to the LIN protocol, a frame time-out error is flagged if: T
Frame
> T
Frame_Maximum
. This feature is
implemented in the LIN/UART controller.
Figure 21-12. LIN timing and frame time-out
BREAK
Field
SYNC
Field
CHECKSUM
Field
DATA-0
FieldField
IDENTIFIER
PROTECTED
DATA-n
Field
T Response T Header
T Frame
T Header_Maximum
T Header_Maximum + T Response_Maximum
1.4 x
T Header_Nominal
1.4 x
T Response_Nominal T Response_Maximum
T Frame_Maximum
=
=
=
Maximum before time-out
T Header_Nominal
T Header_Nominal + T Response_Nominal
34 x
T Bit
10 ( Number_of_Data + 1 ) x
T Bit T Response_Nominal
T Frame_Nominal
=
=
=
Nominal
21.5.11. Break-in-data
According to the LIN protocol, the LIN/UART controller can detect the BREAK/SYNC field sequence even
if the break is partially superimposed with a byte of the response. When a BREAK/SYNC field sequence
happens, the transfer in progress is aborted and the processing of the new frame starts.
• On slave node(s), an error is generated (that is, LBERR in case of Tx Response or LFERR in case
of Rx Response). Information on data error is also available, refer to Data length after error.
• On master node, the user (code) is responsible for this aborting of frame. To do this, the master
task has first to abort the on-going communication (clearing LCMD bits - LIN Abort command) and
then to apply the Tx Header command. In this case, the abort error flag - LABORT - is set
Atmel ATmega16M1/32M1/64M1 [DATASHEET]
Atmel-8209F-ATmega16M1/32M1/64M1_Datasheet_Complete-10/2016
286