![NXP Semiconductors MPC5605BK Reference Manual Download Page 459](http://html.mh-extra.com/html/nxp-semiconductors/mpc5605bk/mpc5605bk_reference-manual_1721852459.webp)
Chapter 23 LIN Controller (LINFlex)
MPC5606BK Microcontroller Reference Manual, Rev. 2
Freescale Semiconductor
459
During reception, a Framing Error leads LINFlex to discard the current frame. LINFlex returns
immediately to idle state. An interrupt is generated if LINIER[FEIE] = 1.
During reception, a Checksum Error leads LINFlex to discard the received frame. LINFlex returns to idle
state. An interrupt is generated if LINIER[CEIE] = 1.
During header reception, a Break Delimiter error, an Inconsistent Synch Field or a Timeout error leads
LINFlex to discard the header. An interrupt is generated if LINIER[HEIE] = 1. LINFlex returns to idle
state.
23.8.2.2.6
Valid header
A received header is considered as valid when it has been received correctly according to the LIN protocol.
If a valid Break Field and Break Delimiter come before the end of the current header or at any time during
a data field, the current header or data is discarded and the state machine synchronizes on this new break.
23.8.2.2.7
Valid message
A received or transmitted message is considered as valid when the data has been received or transmitted
without error according to the LIN protocol.
23.8.2.2.8
Overrun
Once the message buffer is full, the next valid message reception leads to an overrun and a message is lost.
The hardware sets the BOF bit in the LINSR to signal the overrun condition. Which message is lost
depends on the configuration of the RX message buffer:
•
If the buffer lock function is disabled (LINCR1[RBLM] = 0), the last message stored in the buffer
is overwritten by the new incoming message. In this case the latest message is always available to
the application.
•
If the buffer lock function is enabled (LINCR1[RBLM] = 0), the most recent message is discarded
and the previous message is available in the buffer.
23.8.2.3
Slave mode with identifier filtering
In the LIN protocol the identifier of a message is not associated with the address of a node but related to
the content of the message. Consequently a transmitter broadcasts its message to all receivers. On header
reception a slave node decides
—
depending on the identifier value
—
whether the software needs to receive
or send a response. If the message does not target the node, it must be discarded without software
intervention.
To fulfill this requirement, the LINFlex controller provides configurable filters in order to request software
intervention only if needed. This hardware filtering saves CPU resources that would otherwise be needed
by software for filtering.
Summary of Contents for MPC5605BK
Page 2: ...This page is intentionally left blank...
Page 20: ...MPC5606BK Microcontroller Reference Manual Rev 2 20 Freescale Semiconductor...
Page 103: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 103 Clocks and power...
Page 645: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 643 Timers...
Page 715: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 713 ADC system...
Page 787: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 787 Memory...
Page 893: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 893 Integrity...
Page 943: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 943 Debug...