ATtiny167 Atmel Corporation, ATtiny167 Datasheet - Page 165

• Manufacturer Part Number: ATtiny167
• Manufacturer: Atmel Corporation

Specifications of ATtiny167

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

15.4.1
15.4.2
8265B–AVR–09/10
LIN Overview
UART Overview
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 tasks and one master task (c.f.
forms to this perspective. The only link between the master task and the slave task will be at
the cross-over point where the interrupt routine is called once a new identifier is available.
Thus, in a master node, housing both master and slave task, the Tx LIN Header function will
alert the slave task of an identifier presence. In the same way, in a slave node, the Rx LIN
Header function will alert the slave task of an identifier presence.
When the slave task is warned of an identifier presence, it has first to analyze it to know what
to do with the response. Hardware flags identify the presence of one of the specific identifiers
from 60 (0x3C) up to 63 (0x3F).
For LIN communication, only four interrupts need to be managed:
The wake-up management can be automated using the UART wake-up capability and a node
sending a minimum of 5 low bits (0xF0) for LIN 2.1 and 8 low bits (0x80) for LIN 1.3. Pin
change interrupt on LIN wake-up signal can be also used to exit the device of one of its sleep
modes.
Extended frame identifiers 62 (0x3E) and 63 (0x3F) are reserved to allow the embedding of
user-defined message formats and future LIN formats. The byte transfer mode offered by the
UART will ensure the upwards compatibility of LIN slaves with accommodation of the LIN
protocol.
The LIN/UART controller can also function as a conventional UART. By default, the UART
operates as a full duplex controller. It has local loop back circuitry for test purposes. The UART
has the ability to buffer one character for transmit and two for receive. The receive buffer is
made of one 8-bit serial register followed by one 8-bit independent buffer register. Automatic
flag management is implemented when the application puts or gets characters, thus reducing
the software overhead. Because transmit and receive services are independent, the user can
save one device pin when one of the two services is not used. The UART has an enhanced
baud rate generator providing a maximum error of 2% whatever the clock frequency and the
targeted baud rate.
• LIDOK: New LIN identifier available,
• LRXOK: LIN response received,
• LTXOK: LIN response transmitted,
• LERR: LIN Error(s).
Section 15.3.4 on page
164). The ATtiny87/167 con-
165