5 data length after error, 6 data length in uart mode, 8 xxok flags – Rainbow Electronics ATmega64C1 User Manual
Page 215: 9 xxerr flags
215
7647A–AVR–02/08
ATmega32/64/M1/C1
17.5.7.5
Data Length after Error
Figure 17-11. Tx Response - Error
Note:
Information on response (ex: error on byte) is only available at the end of the serialization/de-seri-
alization of the byte.
17.5.7.6
Data Length in UART Mode
•
The UART mode forces LRXDL and LTXDL to 0 and disables the writing in LINDLR register,
•
Note that after reset, LRXDL and LTXDL are also forced to 0.
17.5.8
xxOK Flags
There are three xxOK flags in LINSIR register:
•
LIDOK: LIN IDentifier OK
It is set at the end of the header, either by the Tx Header function or by the Rx Header. In
LIN 1.3, before generating LIDOK, the controller updates the LRXDL & LTXDL fields in
LINDLR register.
It is not driven in UART mode.
•
LRXOK: LIN RX response complete
It is set at the end of the response by the Rx Response function in LIN mode and once a
character is received in UART mode.
•
LTXOK: LIN TX response complete
It is set at the end of the response by the Tx Response function in LIN mode and once a
character has been sent in UART mode.
These flags can generate interrupts if the corresponding enable interrupt bit is set in the LINE-
NIR register (see
Section 17.5.13 “Interrupts” on page 217
).
17.5.9
xxERR Flags
LERR bit of the LINSIR register is an logical ‘OR’ of all the bits of LINERR register (see
17.5.13 “Interrupts” on page 217
). There are eight flags:
•
LBERR = LIN Bit ERRor.
A unit that is sending a bit on the bus also monitors the bus. A LIN bit error will be flagged
when the bit value that is monitored is different from the bit value that is sent. After detection
of a LIN bit error the transmission is aborted.
•
LCERR = LIN Checksum ERRor.
A LIN checksum error will be flagged if the inverted modulo-256 sum of all received data
bytes (and the protected identifier in LIN 2.1) added to the checksum does not result in 0xFF.
•
LPERR = LIN Parity ERRor (identifier).
A LIN parity error in the IDENTIFIER field will be flagged if the value of the parity bits does
not match with the identifier value. (See LP[1:0] bits in
Section 17.6.8 “LIN Identifier Register
). A LIN slave application does not distinguish between corrupted par-
ity bits and a corrupted identifier. The hardware does not undertake any correction. How-
DATA-0
DATA-1
LCMD2..0=000
b
LIN bus
LBUSY
1
st
Byte
2
nd
Byte
3
rd
Byte
LERR
1
4
0
LRXDL
2
LCMD=Tx Response
LTXDL
4
DATA-2
ERROR