ATA6616-P3PW Atmel, ATA6616-P3PW Datasheet - Page 201

• Manufacturer Part Number: ATA6616-P3PW
• Description: TXRX MULTICHIP MOD LIN SIP 38QFN
• Manufacturer: Atmel
• Series: AVR® ATA66 LIN-SBCr

Specifications of ATA6616-P3PW

• Core Processor: AVR
• Core Size: 8-Bit
• Speed: 16MHz
• Connectivity: I²C, LIN, SPI, UART/USART, USI
• Peripherals: Brown-out Detect/Reset, POR, PWM, Temp Sensor, WDT
• Number Of I /o: 16
• Program Memory Size: 8KB (8K x 8)
• Program Memory Type: FLASH
• Eeprom Size: 512 x 8
• Ram Size: 512 x 8
• Voltage - Supply (vcc/vdd): 2.7 V ~ 5.5 V
• Data Converters: A/D 11x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 125°C
• Package / Case: 38-VQFN
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

4.16.5.10
Figure 4-79. LIN Timing and Frame Time-out
4.16.5.11
9132D–AUTO–12/10
T
T
T
Header_Nominal
Response_Nominal
Frame_Nominal
BREAK
Frame Time Out
Break-in-data
Field
=
=
=
T
34 x
10 ( Number_of_Data + 1 ) x
T
After each LIN error, the LIN controller stops its previous activity and returns to its withdrawal
mode (LCMD[2..0] = 000
Writing 1 in LERR of LINSIR register resets LERR bit and all the bits of the LINERR register.
According to the LIN protocol, a frame time-out error is flagged if: T
This feature is implemented in the LIN/UART controller.
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 the slave node, the BREAK detection is processed with the synchronization setting avail-
able when the LIN/UART controller processed the (aborted) response. But the
re-synchronization restarts as usual. Due to a possible difference of timing reference between
the BREAK field and the rest of the frame, the time-out values can be slightly inaccurate.
Header
• LOVERR = LIN OVerrun ERRor.
• LABORT
• On slave node(s), an error is generated (i.e. LBERR in case of Tx Response or LFERR in
• On master node, the user (code) is responsible for this aborting of frame. To do this, the
Header_Nominal +
SYNC
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.
LIN abort transfer reflects a previous LIN Abort command (LCMD[2..0] = 000) while ‘Busy
signal’ is present.
case of Rx Response). Information on data error is also available, refer to the
“Data Length after Error” on page
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.
T
Bit
Field
T
PROTECTED
IDENTIFIER
Response_Nominal
T
Bit
b
Field
) as illustrated in
T
T
T
Nominal
T
Header_Maximum
Response_Maximum
Frame_Maximum
Frame
199.
DATA-0
Figure 4-78 on page
Field
Atmel ATA6616/ATA6617
=
=
=
1.4 x
1.4 x
T
Header_Maximum +
T
T
T
Header_Nominal
Response_Nominal
Response
DATA-n
199.
Frame
Field
T
Response_Maximum
> T
Maximun
Frame_Maximum
CHECKSUM
before Time-out
Section
Field
.
201