ATMEGA16M1-MU Atmel, ATMEGA16M1-MU Datasheet - Page 212

• 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: -

20.5.9
20.5.10
212
ATmega16M1/32M1/64M1
xxERR Flags
Frame Time Out
LERR bit of the LINSIR register is an logical ‘OR’ of all the bits of LINERR register (see
20.5.13 “Interrupts” on page
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
feature is implemented in the LIN/UART controller.
• LBERR = LIN Bit ERRor
• LCERR = LIN Checksum ERRor
• LPERR = LIN Parity ERRor (identifier)
• LSERR = LIN Synchronization ERRor
• LFERR = LIN Framing ERRor.
• LTOERR = LIN Time Out ERRor.
• LOVERR = LIN OVerrun ERRor.
• LABORT
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.
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.
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
Register” on page
parity bits and a corrupted identifier. 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
A LIN synchronization error will be flagged if a slave detects the edges of the SYNCH field
outside the given tolerance.
A framing error will be flagged if dominant STOP bit is sampled.
Same function in UART mode.
A time-out error will be flagged if the MESSAGE frame is not fully completed within the
maximum length T
IDENTIFIER fields (see
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.
221). A LIN slave application does not distinguish between corrupted
Frame_Maximum
b
) as illustrated in
Section 20.5.10 “Frame Time Out” on page
214). There are eight flags:
by any slave task upon transmission of the SYNCH and
Figure 20-11 on page
Section 20.6.8 “LINIDR – LIN Identifier
211.
Frame
212).
> T
Frame_Maximum
8209D–AVR–11/10
Section
. This