ATMEGA16M1-MU Atmel, ATMEGA16M1-MU Datasheet - Page 213

• Manufacturer Part Number: ATMEGA16M1-MU
• Description: IC MCU AVR 16K FLASH 32VQFN
• Manufacturer: Atmel
• Series: AVR® ATmegar

Specifications of ATMEGA16M1-MU

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

Figure 20-12. LIN timing and frame time-out
20.5.11
20.5.12
8209D–AVR–11/10
T
T
T
Header_Nominal
Response_Nominal
Frame_Nominal
Break-in-data
Checksum
BREAK
CHECKSUM
Field
=
255
=
=
=
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 available
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.
The last field of a frame is the checksum.
In LIN 2.1, the checksum contains the inverted eight bit sum with carry over all data bytes and
the protected identifier. This calculation is called enhanced checksum.
In LIN 1.3, the checksum contains the inverted eight bit sum with carry over all data bytes. This
calculation is called classic checksum.
Frame identifiers 60 (0x3C) to 61 (0x3D) shall always use classic checksum.
T
• On slave node(s), an error is generated (that is, 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
34 x
10 ( Number_of_Data + 1 ) x
T
–
Header
case of Rx Response). Information on data error is also available, refer to the
20.5.7.5
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
⎛
⎜
⎜
⎝
Header_Nominal +
SYNC
unsigned char
T
Bit
CHECKSUM
Field
⎛
⎜
⎜
⎝
⎛
⎜
⎜
⎝
∑
n
0
PROTECTED
IDENTIFIER
T
DATA n
=
Response_Nominal
255
T
–
⎞
⎟
⎟
⎠
Bit
⎛
⎜
⎜
⎝
Field
+
unsigned char
T
T
T
PROTECTED ID.
T
Nominal
Header_Maximum
Response_Maximum
Frame_Maximum
Frame
⎛
⎜
⎜
⎝
DATA-0
∑
n
0
DATA n
⎞
⎟
⎟
⎠
+
unsigned char
ATmega16M1/32M1/64M1
Field
⎞
⎟
⎟
⎠
=
=
=
+
1.4 x
1.4 x
T
unsigned char
Header_Maximum +
T
T
⎛
⎜
⎜
⎝
T
⎛
⎜
⎜
⎝
Header_Nominal
Response_Nominal
⎛
⎜
⎜
⎝
Response
∑
n
0
DATA-n
DATA n
⎛
⎜
⎜
⎝
⎛
⎜
⎜
⎝
∑
n
0
DATA n
⎞
⎟
⎟
⎠
Field
+
T
PROTECTED ID.
Response_Maximum
⎞
⎟
⎟
⎠
Maximun
»
8
CHECKSUM
⎞
⎟
⎟
⎠
⎞
⎟
⎟
⎠
Section
before Time-out
⎞
⎟
⎟
⎠
Field
»
8
⎞
⎟
⎟
⎠
⎞
⎟
⎟
⎠
213