ATtiny167 Automotive Atmel Corporation, ATtiny167 Automotive Datasheet - Page 177

no-image

ATtiny167 Automotive

Manufacturer Part Number
ATtiny167 Automotive
Description
Manufacturer
Atmel Corporation

Specifications of ATtiny167 Automotive

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 150
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
3
Input Capture Channels
1
Pwm Channels
9
32khz Rtc
Yes
Calibrated Rc Oscillator
Yes
15.5.10
15.5.11
15.5.12
7728G–AVR–06/10
T
T
T
Header_Nominal
Response_Nominal
Frame_Nominal
Frame Time Out
Break-in-data
Checksum
BREAK
CHECKSUM
Field
=
=
=
=
255
T
34 x
10 ( Number_of_Data + 1 ) x
T
According to the LIN protocol, a frame time-out error is flagged if: T
This feature is implemented in the LIN/UART controller.
Figure 15-12. LIN timing and frame time-out
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.
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.
Header
• 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
case of Rx Response). Information on data error is also available, refer to the
15.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.
unsigned char
T
Bit
Field
n
0
PROTECTED
IDENTIFIER
T
DATA n
Response_Nominal
T
Bit
Field
+
T
T
T
PROTECTED ID.
T
Nominal
Header_Maximum
Response_Maximum
Frame_Maximum
Frame
DATA-0
+
unsigned char
Field
=
=
=
1.4 x
1.4 x
T
Header_Maximum +
T
T
ATtiny87/ATtiny167
T
Header_Nominal
Response_Nominal
Response
n
0
DATA n
DATA-n
Frame
Field
+
T
PROTECTED ID.
Response_Maximum
> T
Maximun
Frame_Maximum
CHECKSUM
before Time-out
Section
»
Field
8
.
177

Related parts for ATtiny167 Automotive