ATmega32M1 Atmel Corporation, ATmega32M1 Datasheet - Page 200

• Manufacturer Part Number: ATmega32M1
• Manufacturer: Atmel Corporation

Specifications of ATmega32M1

• Flash (kbytes): 32 Kbytes
• Pin Count: 32
• Max. Operating Frequency: 16 MHz
• Cpu: 8-bit AVR
• # Of Touch Channels: 12
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 27
• Ext Interrupts: 27
• Usb Speed: No
• Usb Interface: No
• Spi: 1
• Uart: 1
• Can: 1
• Lin: 1
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 11
• Adc Resolution (bits): 10
• Adc Speed (ksps): 125
• Analog Comparators: 4
• Resistive Touch Screen: No
• Dac Channels: 1
• Dac Resolution (bits): 10
• Temp. Sensor: Yes
• Crypto Engine: No
• Sram (kbytes): 2
• Eeprom (bytes): 1024
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: No
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 2.7 to 5.5
• Operating Voltage (vcc): 2.7 to 5.5
• Fpu: No
• Mpu / Mmu: no / no
• Timers: 2
• Output Compare Channels: 14
• Input Capture Channels: 1
• Pwm Channels: 10
• 32khz Rtc: No
• Calibrated Rc Oscillator: Yes

20.3.3
20.3.4
20.3.5
20.4
20.4.1
200
LIN / UART Controller
ATmega16M1/32M1/64M1
Data Transport
Schedule Table
Compatibility with LIN 1.3
LIN Overview
Two types of data may be transported in a frame; signals or diagnostic messages.
The master task (in the master node) transmits frame headers based on a schedule table. The
schedule table specifies the identifiers for each header and the interval between the start of a
frame and the start of the following frame. The master application may use different schedule
tables and select among them.
LIN 2.1 is a super-set of LIN 1.3.
A LIN 2.1 master node can handle clusters consisting of both LIN 1.3 slaves and/or LIN 2.1
slaves. The master will then avoid requesting the new LIN 2.1 features from a LIN 1.3 slave:
LIN 2.1 slave nodes can not operate with a LIN 1.3 master node (for example the LIN1.3 master
does not support the enhanced checksum).
The LIN 2.1 physical layer is backwards compatible with the LIN1.3 physical layer. But not the
other way around. The LIN 2.1 physical layer sets greater requirements, that is, a master node
using the LIN 2.1 physical layer can operate in a LIN 1.3 cluster.
The LIN/UART controller is divided in three main functions:
These functions mainly use two services:
Because these two services are basically UART services, the controller is also able to switch
into an UART function.
The LIN/UART controller is designed to match as closely as possible to the LIN software appli-
cation structure. The LIN software application is developed as independent tasks, several slave
• Signals
• Diagnostic messages
• Enhanced checksum
• Re-configuration and diagnostics
• Automatic baud rate detection
• "Response error" status monitoring
• Tx LIN Header function
• Rx LIN Header function
• LIN Response function
• Rx service
• Tx service
Signals are scalar values or byte arrays that are packed into the data field of a frame. A signal
is always present at the same position in the data field for all frames with the same identifier.
Diagnostic messages are transported in frames with two reserved identifiers. The
interpretation of the data field depends on the data field itself as well as the state of the
communicating nodes.
8209D–AVR–11/10