ATMEL ATmega32C1 8-bit microcontroller with 16k/32k/64k bytes in-system programmable flash Datasheet

Features
• High Performance, Low Power AVR® 8-bit Microcontroller
• Advanced RISC Architecture
•
•
•
•
•
•
•
•
•
1.
– 131 Powerful Instructions - Most Single Clock Cycle Execution
– 32 x 8 General Purpose Working Registers
– Fully Static Operation
– Up to 1 MIPS throughput per MHz
– On-chip 2-cycle Multiplier
Data and Non-Volatile Program Memory
– 16K/32K/64K Bytes Flash of In-System Programmable Program Memory
• Endurance: 10,000 Write/Erase Cycles
– Optional Boot Code Section with Independent Lock Bits
– In-System Programming by On-chip Boot Program
• True Read-While-Write Operation
– 512/1024/2048 Bytes of In-System Programmable EEPROM
• Endurance: 100,000 Write/Erase Cycles
Programming Lock for Flash Program and EEPROM Data Security
1024/2048/4096 Bytes Internal SRAM
On Chip Debug Interface (debugWIRE)
CAN 2.0A/B with 6 Message Objects - ISO 16845 Certified (1)
LIN 2.1 and 1.3 Controller or 8-Bit UART
One 12-bit High Speed PSC (Power Stage Controller) (only ATmega16/32/64M1)
• Non Overlapping Inverted PWM Output Pins With Flexible Dead-Time
• Variable PWM duty Cycle and Frequency
• Synchronous Update of all PWM Registers
• Auto Stop Function for Emergency Event
Peripheral Features
– One 8-bit General purpose Timer/Counter with Separate Prescaler, Compare Mode
and Capture Mode
– One 16-bit General purpose Timer/Counter with Separate Prescaler, Compare
Mode and Capture Mode
– One Master/Slave SPI Serial Interface
– 10-bit ADC
• Up To 11 Single Ended Channels and 3 Fully Differential ADC Channel Pairs
• Programmable Gain (5x, 10x, 20x, 40x) on Differential Channels
• Internal Reference Voltage
• Direct Power Supply Voltage Measurement
– 10-bit DAC for Variable Voltage Reference (Comparators, ADC)
– Four Analog Comparators with Variable Threshold Detection
– 100µA ±6% Current Source (LIN Node Identification)
– Interrupt and Wake-up on Pin Change
– Programmable Watchdog Timer with Separate On-Chip Oscillator
– On-chipTemperature Sensor
Special Microcontroller Features
– Low Power Idle, Noise Reduction, and Power Down Modes
– Power On Reset and Programmable Brown Out Detection
– In-System Programmable via SPI Port
– High Precision Crystal Oscillator for CAN Operations (16 MHz)
See certification on Atmel® web site and note on “Baud Rate” on page 177.
8-bit
Microcontroller
with
16K/32K/64K
Bytes In-System
Programmable
Flash
ATmega16M1
ATmega32M1
ATmega64M1
ATmega32C1
ATmega64C1
Automotive
7647F–AVR–04/09
– Internal Calibrated RC Oscillator (8 MHz)
– On-chip PLL for fast PWM (32 MHz, 64 MHz) and CPU (16 MHz)
• Operating Voltage:
– 2.7V - 5.5V
• Extended Operating Temperature:
– -40°C to +125°C
• Core Speed Grade:
– 0 - 8 MHz @ 2.7 - 4.5V
– 0 - 16 MHz @ 4.5 - 5.5V
ATmega32/64/M1/C1 Product Line-up
Part Number
ATmega32C1
ATmega64C1
ATmega16M1
ATmega32M1
ATmega64M1
Flash Size
32 Kbyte
64 Kbyte
16 Kbyte
32 Kbyte
64 Kbyte
RAM Size
2048 bytes
4096 bytes
1024 bytes
2048 bytes
4096 bytes
EEPROM Size
1024 bytes
2048 bytes
512 bytes
1024 bytes
2048 bytes
8-bit Timer
Yes
16-bit Timer
Yes
PSC
No
Yes
PWM Outputs
4
4
10
10
10
Fault Inputs (PSC)
0
0
3
3
3
PLL
32/64 MHz
10-bit ADC Channels
11 single
3 Differential
10-bit DAC
Yes
Analog Comparators
4
Current Source
Yes
CAN
Yes
LIN/UART
Yes
On-Chip Temp. Sensor
Yes
SPI Interface
Yes
2
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
1. Pin Configurations
ATmega16/32/64M1 TQFP32/QFN32 (7*7 mm) Package.
PD0 (PCINT16/PSCOUT0A)
PC0(PCINT8/INT3/PSCOUT1A)
PE0 (PCINT24/RESET/OCD)
32
31
30
29
28
27
26
25
PD1(PCINT17/PSCIN0/CLKO)
ATmega32/64M1 TQFP32/QFN32
PB7 (ADC4/PSCOUT0B/SCK/PCINT7)
PB6 (ADC7/PSCOUT1B/PCINT6)
PB5 (ADC6/INT2/ACMPN1/AMP2-/PCINT5)
PC7 (D2A/AMP2+/PCINT15)
Figure 1-1.
24
23
22
21
20
19
18
17
1
2
3
4
5
6
7
8
PB4 (AMP0+/PCINT4)
PB3 (AMP0-/PCINT3)
PC6 (ADC10/ACMP1/PCINT14)
AREF(ISRC)
AGND
AVCC
PC5 (ADC9/ACMP3/AMP1+/PCINT13)
PC4 (ADC8/ACMPN3/AMP1-/PCINT12)
(PCINT1/MOSI/PSCOUT2B) PB1
(PCINT25/OC0B/XTAL1) PE1
(PCINT26/ADC0/XTAL2) PE2
(PCINT20/ADC1/RXD/RXLIN/ICP1A/SCK_A) PD4
(ADC2/ACMP2/PCINT21) PD5
(ADC3/ACMPN2/INT0/PCINT22) PD6
(ACMP0/PCINT23) PD7
(ADC5/INT1/ACMPN0/PCINT2) PB2
9
10
11
12
13
14
15
16
(PCINT18/PSCIN2/OC1A/MISO_A) PD2
(PCINT19/TXD/TXLIN/OC0A/SS/MOSI_A) PD3
(PCINT9/PSCIN1/OC1B/SS_A) PC1
VCC
GND
(PCINT10/T0/TXCAN) PC2
(PCINT11/T1/RXCAN/ICP1B) PC3
(PCINT0/MISO/PSCOUT2A) PB0
Note:
On the engineering samples (Parts marked AT90PWM324), the ACMPN3 alternate function is not
located on PC4. It is located on PE2.
3
7647F–AVR–04/09
ATmega32/64C1 TQFP32/QFN32 (7*7 mm) Package
PD0 (PCINT16)
PC0(PCINT8/INT3)
PE0 (PCINT24/RESET/OCD)
32
31
30
29
28
27
26
25
PD1(PCINT17/CLKO)
ATmega32/64C1 TQFP32/QFN32
PB7 (ADC4/SCK/PCINT7)
PB6 (ADC7PCINT6)
PB5 (ADC6/INT2/ACMPN1/AMP2-/PCINT5)
PC7 (D2A/AMP2+/PCINT15)
Figure 1-2.
24
23
22
21
20
19
18
17
1
2
3
4
5
6
7
8
PB4 (AMP0+/PCINT4)
PB3 (AMP0-/PCINT3)
PC6 (ADC10/ACMP1/PCINT14)
AREF(ISRC)
AGND
AVCC
PC5 (ADC9/ACMP3/AMP1+/PCINT13)
PC4 (ADC8/ACMPN3/AMP1-/PCINT12)
(PCINT1/MOSI) PB1
(PCINT25/OC0B/XTAL1) PE1
(PCINT26/ADC0/XTAL2) PE2
(PCINT20/ADC1/RXD/RXLIN/ICP1A/SCK_A) PD4
(ADC2/ACMP2/PCINT21) PD5
(ADC3/ACMPN2/INT0/PCINT22) PD6
(ACMP0/PCINT23) PD7
(ADC5/INT1/ACMPN0/PCINT2) PB2
9
10
11
12
13
14
15
16
(PCINT18/OC1A/MISO_A) PD2
(PCINT19/TXD/TXLIN/OC0A/SS/MOSI_A) PD3
(PCINT9/OC1B/SS_A) PC1
VCC
GND
(PCINT10/T0/TXCAN) PC2
(PCINT11/T1/RXCAN/ICP1B) PC3
(PCINT0/MISO) PB0
Note:
4
On the first engineering samples (Parts marked AT90PWM324), the ACMPN3 alternate function is
not located on PC4. It is located on PE2.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
1.1
Pin Descriptions
:
Table 1-1.
Pin out description
QFN32 Pin
Number
Mnemonic
Type
5
GND
Power
Ground: 0V reference
20
AGND
Power
Analog Ground: 0V reference for analog part
4
VCC
Power
Power Supply
19
AVCC
Power
Analog Power Supply: This is the power supply voltage for analog
part
Name, Function & Alternate Function
For a normal use this pin must be connected.
21
AREF
Power
Analog Reference : reference for analog converter . This is the
reference voltage of the A/D converter. As output, can be used by
external analog
ISRC (Current Source Output)
MISO (SPI Master In Slave Out)
8
PB0
I/O
PSCOUT2A(1) (PSC Module 2 Output A)
PCINT0 (Pin Change Interrupt 0)
MOSI (SPI Master Out Slave In)
9
PB1
I/O
PSCOUT2B(1) (PSC Module 2 Output B)
PCINT1 (Pin Change Interrupt 1)
ADC5 (Analog Input Channel 5 )
16
PB2
I/O
INT1 (External Interrupt 1 Input)
ACMPN0 (Analog Comparator 0 Negative Input)
PCINT2 (Pin Change Interrupt 2)
23
PB3
I/O
24
PB4
I/O
AMP0- (Analog Differential Amplifier 0 Negative Input)
PCINT3 (Pin Change Interrupt 3)
AMP0+ (Analog Differential Amplifier 0 Positive Input)
PCINT4 (Pin Change Interrupt 4)
ADC6 (Analog Input Channel 6)
INT2 (External Interrupt 2 Input)
26
PB5
I/O
ACMPN1 (Analog Comparator 1 Negative Input)
AMP2- (Analog Differential Amplifier 2 Negative Input)
PCINT5 (Pin Change Interrupt 5)
ADC7 (Analog Input Channel 7)
27
PB6
I/O
PSCOUT1B(1) (PSC Module 1 Output A)
PCINT6 (Pin Change Interrupt 6)
ADC4 (Analog Input Channel 4)
28
PB7
I/O
PSCOUT0B(1) (PSC Module 0 Output B)
SCK (SPI Clock)
PCINT7 (Pin Change Interrupt 7)
PSCOUT1A(1) (PSC Module 1 Output A)
30
PC0
I/O
INT3 (External Interrupt 3 Input)
PCINT8 (Pin Change Interrupt 8)
5
7647F–AVR–04/09
Table 1-1.
QFN32 Pin
Number
Pin out description (Continued)
Mnemonic
Type
Name, Function & Alternate Function
PSCIN1 (PSC Digital Input 1)
3
PC1
I/O
OC1B (Timer 1 Output Compare B)
SS_A (Alternate SPI Slave Select)
PCINT9 (Pin Change Interrupt 9)
T0 (Timer 0 clock input)
6
PC2
I/O
TXCAN (CAN Transmit Output)
PCINT10 (Pin Change Interrupt 10)
T1 (Timer 1 clock input)
7
PC3
I/O
RXCAN (CAN Receive Input)
ICP1B (Timer 1 input capture alternate B input)
PCINT11 (Pin Change Interrupt 11)
ADC8 (Analog Input Channel 8)
17
PC4
I/O
AMP1- (Analog Differential Amplifier 1 Negative Input)
ACMPN3 (Analog Comparator 3 Negative Input)
PCINT12 (Pin Change Interrupt 12)
ADC9 (Analog Input Channel 9)
18
PC5
I/O
AMP1+ (Analog Differential Amplifier 1 Positive Input)
ACMP3 (Analog Comparator 3 Positive Input)
PCINT13 (Pin Change Interrupt 13)
ADC10 (Analog Input Channel 10)
22
PC6
I/O
ACMP1 (Analog Comparator 1 Positive Input)
PCINT14 (Pin Change Interrupt 14)
D2A (DAC output)
25
PC7
I/O
AMP2+ (Analog Differential Amplifier 2 Positive Input)
PCINT15 (Pin Change Interrupt 15)
29
PD0
I/O
32
PD1
I/O
PSCOUT0A(1) (PSC Module 0 Output A)
PCINT16 (Pin Change Interrupt 16)
PSCIN0 (PSC Digital Input 0)
CLKO (System Clock Output)
PCINT17 (Pin Change Interrupt 17)
OC1A (Timer 1 Output Compare A)
1
PD2
I/O
PSCIN2 (PSC Digital Input 2)
MISO_A (Programming & alternate SPI Master In Slave Out)
PCINT18 (Pin Change Interrupt 18)
TXD (UART Tx data)
TXLIN (LIN Transmit Output)
2
PD3
I/O
OC0A (Timer 0 Output Compare A)
SS (SPI Slave Select)
MOSI_A (Programming & alternate Master Out SPI Slave In)
PCINT19 (Pin Change Interrupt 19)
6
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 1-1.
QFN32 Pin
Number
Pin out description (Continued)
Mnemonic
Type
Name, Function & Alternate Function
ADC1 (Analog Input Channel 1)
RXD (UART Rx data)
12
PD4
I/O
RXLIN (LIN Receive Input)
ICP1A (Timer 1 input capture alternate A input)
SCK_A (Programming & alternate SPI Clock)
PCINT20 (Pin Change Interrupt 20)
ADC2 (Analog Input Channel 2)
13
PD5
I/O
ACMP2 (Analog Comparator 2 Positive Input)
PCINT21 (Pin Change Interrupt 21)
ADC3 (Analog Input Channel 3)
14
PD6
I/O
ACMPN2 (Analog Comparator 2 Negative Input)
INT0 (External Interrupt 0 Input)
PCINT22 (Pin Change Interrupt 22)
15
PD7
I/O
31
PE0
I/O or I
ACMP0 (Analog Comparator 0 Positive Input)
PCINT23 (Pin Change Interrupt 23)
RESET (Reset Input)
OCD (On Chip Debug I/O)
PCINT24 (Pin Change Interrupt 24)
XTAL1 (XTAL Input)
10
PE1
I/O
OC0B (Timer 0 Output Compare B)
PCINT25 (Pin Change Interrupt 25)
XTAL2 (XTAL Output)
11
PE2
I/O
ADC0 (Analog Input Channel 0)
PCINT26 (Pin Change Interrupt 26)
Note:
1. Only for ATmega32/64M1.
2. On the first engineering samples (Parts marked AT90PWM324), the ACMPN3 alternate function is not located on PC4. It is located on PE2.
7
7647F–AVR–04/09
2. Overview
The ATmega16/32/64/M1/C1 is a low-power CMOS 8-bit microcontroller based on the AVR
enhanced RISC architecture. By executing powerful instructions in a single clock cycle, the
ATmega16/32/64/M1/C1 achieves throughputs approaching 1 MIPS per MHz allowing the system designer to optimize power consumption versus processing speed.
2.1
Block Diagram
Figure 2-1.
Block Diagram
Data Bus 8-bit
Flash Program
Memory
Program
Counter
Status
and Control
Interrupt
Unit
SPI
Unit
32 x 8
General
Purpose
Registrers
Instruction
Register
Direct Addressing
Indirect Addressing
4 Analog
Comparators
Instruction
Decoder
Control Lines
Watchdog
Timer
ALU
HW LIN/UART
Timer 0
Timer 1
Data
SRAM
ADC
EEPROM
DAC
I/O Lines
MPSC
Current Source
CAN
The AVR core combines a rich instruction set with 32 general purpose working registers. All the
32 registers are directly connected to the Arithmetic Logic Unit (ALU), allowing two independent
registers to be accessed in one single instruction executed in one clock cycle. The resulting
architecture is more code efficient while achieving throughputs up to ten times faster than conventional CISC microcontrollers.
8
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The ATmega16/32/64/M1/C1 provides the following features: 16K/32K/64K bytes of In-System
Programmable Flash with Read-While-Write capabilities, 512/1024/2048 bytes EEPROM,
1024/2048/4096 bytes SRAM, 27 general purpose I/O lines, 32 general purpose working registers, one Motor Power Stage Controller, two flexible Timer/Counters with compare modes and
PWM, one UART with HW LIN, an 11-channel 10-bit ADC with two differential input stages with
programmable gain, a 10-bit DAC, a programmable Watchdog Timer with Internal Individual
Oscillator, an SPI serial port, an On-chip Debug system and four software selectable power saving modes.
The Idle mode stops the CPU while allowing the SRAM, Timer/Counters, SPI ports, CAN,
LIN/UART and interrupt system to continue functioning. The Power-down mode saves the register contents but freezes the Oscillator, disabling all other chip functions until the next interrupt or
Hardware Reset. The ADC Noise Reduction mode stops the CPU and all I/O modules except
ADC, to minimize switching noise during ADC conversions. In Standby mode, the Crystal/Resonator Oscillator is running while the rest of the device is sleeping. This allows very fast start-up
combined with low power consumption.
The device is manufactured using Atmel’s high-density nonvolatile memory technology. The
On-chip ISP Flash allows the program memory to be reprogrammed in-system through an SPI
serial interface, by a conventional nonvolatile memory programmer, or by an On-chip Boot program running on the AVR core. The boot program can use any interface to download the
application program in the application Flash memory. Software in the Boot Flash section will
continue to run while the Application Flash section is updated, providing true Read-While-Write
operation. By combining an 8-bit RISC CPU with In-System Self-Programmable Flash on a
monolithic chip, the Atmel ATmega16/32/64/M1/C1 is a powerful microcontroller that provides a
highly flexible and cost effective solution to many embedded control applications.
The ATmega16/32/64/M1/C1 AVR is supported with a full suite of program and system development tools including: C compilers, macro assemblers, program debugger/simulators, in-circuit
emulators, and evaluation kits.
2.2
Automotive Quality Grade
The ATmega16/32/64/M1/C1 have been developed and manufactured according to the most
stringent requirements of the international standard ISO-TS-16949. This data sheet contains
limit values extracted from the results of extensive characterization (Temperature and Voltage).
The quality and reliability of the ATmega16/32/64/M1/C1 have been verified during regular product qualification as per AEC-Q100 grade 1.
As indicated in the ordering information paragraph, the products are available in only one temperature grade.
Table 2-1.
Temperature Grade Identification for Automotive Products
Temperature
-40 ; +125
Temperature Identifier
Z
Comments
Full AutomotiveTemperature Range
9
7647F–AVR–04/09
2.3
2.3.1
Pin Descriptions
VCC
Digital supply voltage.
2.3.2
GND
Ground.
2.3.3
Port B (PB7..PB0)
Port B is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The
Port B output buffers have symmetrical drive characteristics with both high sink and source
capability. As inputs, Port B pins that are externally pulled low will source current if the pull-up
resistors are activated. The Port B pins are tri-stated when a reset condition becomes active,
even if the clock is not running.
Port B also serves the functions of various special features of the ATmega16/32/64/M1/C1 as
listed on page 69.
2.3.4
Port C (PC7..PC0)
Port C is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The
Port C output buffers have symmetrical drive characteristics with both high sink and source
capability. As inputs, Port C pins that are externally pulled low will source current if the pull-up
resistors are activated. The Port C pins are tri-stated when a reset condition becomes active,
even if the clock is not running.
Port C also serves the functions of special features of the ATmega16/32/64/M1/C1 as listed on
page 72.
2.3.5
Port D (PD7..PD0)
Port D is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The
Port D output buffers have symmetrical drive characteristics with both high sink and source
capability. As inputs, Port D pins that are externally pulled low will source current if the pull-up
resistors are activated. The Port D pins are tri-stated when a reset condition becomes active,
even if the clock is not running.
Port D also serves the functions of various special features of the ATmega16/32/64/M1/C1 as
listed on page 75.
2.3.6
Port E (PE2..0) RESET/ XTAL1/ XTAL2
Port E is an 3-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The
Port E output buffers have symmetrical drive characteristics with both high sink and source
capability. As inputs, Port E pins that are externally pulled low will source current if the pull-up
resistors are activated. The Port E pins are tri-stated when a reset condition becomes active,
even if the clock is not running.
If the RSTDISBL Fuse is programmed, PE0 is used as an I/O pin. Note that the electrical characteristics of PE0 differ from those of the other pins of Port E.
If the RSTDISBL Fuse is unprogrammed, PE0 is used as a Reset input. A low level on this pin
for longer than the minimum pulse length will generate a Reset, even if the clock is not running.
The minimum pulse length is given in Table 7-1 on page 47. Shorter pulses are not guaranteed
to generate a Reset.
10
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Depending on the clock selection fuse settings, PE1 can be used as input to the inverting Oscillator amplifier and input to the internal clock operating circuit.
Depending on the clock selection fuse settings, PE2 can be used as output from the inverting
Oscillator amplifier.
The various special features of Port E are elaborated in “Alternate Functions of Port E” on page
78 and “Clock Systems and their Distribution” on page 29.
2.3.7
AVCC
AVCC is the supply voltage pin for the A/D Converter, D/A Converter, Current source. It should
be externally connected to VCC, even if the ADC, DAC are not used. If the ADC is used, it should
be connected to VCC through a low-pass filter (see Section 18.6.2 “Analog Noise Canceling
Techniques” on page 238).
2.3.8
AREF
This is the analog reference pin for the A/D Converter.
2.4
About Code Examples
This documentation contains simple code examples that briefly show how to use various parts of
the device. These code examples assume that the part specific header file is included before
compilation. Be aware that not all C compiler vendors include bit definitions in the header files
and interrupt handling in C is compiler dependent. Please confirm with the C compiler documentation for more details.
11
7647F–AVR–04/09
3. AVR CPU Core
3.1
Introduction
This section discusses the AVR core architecture in general. The main function of the CPU core
is to ensure correct program execution. The CPU must therefore be able to access memories,
perform calculations, control peripherals, and handle interrupts.
3.2
Architectural Overview
Figure 3-1.
Block Diagram of the AVR Architecture
Data Bus 8-bit
Flash
Program
Memory
Program
Counter
Status
and Control
32 x 8
General
Purpose
Registrers
Control Lines
Direct Addressing
Instruction
Decoder
Indirect Addressing
Instruction
Register
Interrupt
Unit
SPI
Unit
Watchdog
Timer
ALU
Analog
Comparator
I/O Module1
Data
SRAM
I/O Module 2
I/O Module n
EEPROM
I/O Lines
In order to maximize performance and parallelism, the AVR uses a Harvard architecture – with
separate memories and buses for program and data. Instructions in the program memory are
executed with a single level pipelining. While one instruction is being executed, the next instruction is pre-fetched from the program memory. This concept enables instructions to be executed
in every clock cycle. The program memory is In-System Reprogrammable Flash memory.
12
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The fast-access Register File contains 32 x 8-bit general purpose working registers with a single
clock cycle access time. This allows single-cycle Arithmetic Logic Unit (ALU) operation. In a typical ALU operation, two operands are output from the Register File, the operation is executed,
and the result is stored back in the Register File – in one clock cycle.
Six of the 32 registers can be used as three 16-bit indirect address register pointers for Data
Space addressing – enabling efficient address calculations. One of the these address pointers
can also be used as an address pointer for look up tables in Flash program memory. These
added function registers are the 16-bit X-, Y-, and Z-register, described later in this section.
The ALU supports arithmetic and logic operations between registers or between a constant and
a register. Single register operations can also be executed in the ALU. After an arithmetic operation, the Status Register is updated to reflect information about the result of the operation.
Program flow is provided by conditional and unconditional jump and call instructions, able to
directly address the whole address space. Most AVR instructions have a single 16-bit word format. Every program memory address contains a 16- or 32-bit instruction.
Program Flash memory space is divided in two sections, the Boot Program section and the
Application Program section. Both sections have dedicated Lock bits for write and read/write
protection. The SPM (Store Program Memory) instruction that writes into the Application Flash
memory section must reside in the Boot Program section.
During interrupts and subroutine calls, the return address Program Counter (PC) is stored on the
Stack. The Stack is effectively allocated in the general data SRAM, and consequently the Stack
size is only limited by the total SRAM size and the usage of the SRAM. All user programs must
initialize the SP in the Reset routine (before subroutines or interrupts are executed). The Stack
Pointer (SP) is read/write accessible in the I/O space. The data SRAM can easily be accessed
through the five different addressing modes supported in the AVR architecture.
The memory spaces in the AVR architecture are all linear and regular memory maps.
A flexible interrupt module has its control registers in the I/O space with an additional Global
Interrupt Enable bit in the Status Register. All interrupts have a separate Interrupt Vector in the
Interrupt Vector table. The interrupts have priority in accordance with their Interrupt Vector position. The lower the Interrupt Vector address, the higher is the priority.
The I/O memory space contains 64 addresses for CPU peripheral functions as Control Registers, SPI, and other I/O functions. The I/O Memory can be accessed directly, or as the Data
Space locations following those of the Register File, 0x20 - 0x5F. In addition, the
ATmega16/32/64/M1/C1 has Extended I/O space from 0x60 - 0xFF in SRAM where only the
ST/STS/STD and LD/LDS/LDD instructions can be used.
3.3
ALU – Arithmetic Logic Unit
The high-performance AVR ALU operates in direct connection with all the 32 general purpose
working registers. Within a single clock cycle, arithmetic operations between general purpose
registers or between a register and an immediate are executed. The ALU operations are divided
into three main categories – arithmetic, logical, and bit-functions. Some implementations of the
architecture also provide a powerful multiplier supporting both signed/unsigned multiplication
and fractional format. See the “Instruction Set” section for a detailed description.
13
7647F–AVR–04/09
3.4
Status Register
The Status Register contains information about the result of the most recently executed arithmetic instruction. This information can be used for altering program flow in order to perform
conditional operations. Note that the Status Register is updated after all ALU operations, as
specified in the Instruction Set Reference. This will in many cases remove the need for using the
dedicated compare instructions, resulting in faster and more compact code.
The Status Register is not automatically stored when entering an interrupt routine and restored
when returning from an interrupt. This must be handled by software.
The AVR Status Register – SREG – is defined as:
Bit
7
6
5
4
3
2
1
0
I
T
H
S
V
N
Z
C
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
SREG
• Bit 7 – I: Global Interrupt Enable
The Global Interrupt Enable bit must be set to enabled the interrupts. The individual interrupt
enable control is then performed in separate control registers. If the Global Interrupt Enable
Register is cleared, none of the interrupts are enabled independent of the individual interrupt
enable settings. The I-bit is cleared by hardware after an interrupt has occurred, and is set by
the RETI instruction to enable subsequent interrupts. The I-bit can also be set and cleared by
the application with the SEI and CLI instructions, as described in the instruction set reference.
• Bit 6 – T: Bit Copy Storage
The Bit Copy instructions BLD (Bit LoaD) and BST (Bit STore) use the T-bit as source or destination for the operated bit. A bit from a register in the Register File can be copied into T by the
BST instruction, and a bit in T can be copied into a bit in a register in the Register File by the
BLD instruction.
• Bit 5 – H: Half Carry Flag
The Half Carry Flag H indicates a Half Carry in some arithmetic operations. Half Carry Is useful
in BCD arithmetic. See the “Instruction Set Description” for detailed information.
• Bit 4 – S: Sign Bit, S = N ⊕ V
The S-bit is always an exclusive or between the negative flag N and the Two’s Complement
Overflow Flag V. See the “Instruction Set Description” for detailed information.
• Bit 3 – V: Two’s Complement Overflow Flag
The Two’s Complement Overflow Flag V supports two’s complement arithmetics. See the
“Instruction Set Description” for detailed information.
• Bit 2 – N: Negative Flag
The Negative Flag N indicates a negative result in an arithmetic or logic operation. See the
“Instruction Set Description” for detailed information.
• Bit 1 – Z: Zero Flag
The Zero Flag Z indicates a zero result in an arithmetic or logic operation. See the “Instruction
Set Description” for detailed information.
14
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 0 – C: Carry Flag
The Carry Flag C indicates a carry in an arithmetic or logic operation. See the “Instruction Set
Description” for detailed information.
3.5
General Purpose Register File
The Register File is optimized for the AVR Enhanced RISC instruction set. In order to achieve
the required performance and flexibility, the following input/output schemes are supported by the
Register File:
• One 8-bit output operand and one 8-bit result input
• Two 8-bit output operands and one 8-bit result input
• Two 8-bit output operands and one 16-bit result input
• One 16-bit output operand and one 16-bit result input
Figure 3-2 shows the structure of the 32 general purpose working registers in the CPU.
Figure 3-2.
AVR CPU General Purpose Working Registers
7
0
Addr.
R0
0x00
R1
0x01
R2
0x02
…
General
R13
0x0D
R14
0x0E
Purpose
R15
0x0F
Working
R16
0x10
R17
0x11
Registers
…
R26
0x1A
X-register Low Byte
R27
0x1B
X-register High Byte
R28
0x1C
Y-register Low Byte
R29
0x1D
Y-register High Byte
R30
0x1E
Z-register Low Byte
R31
0x1F
Z-register High Byte
Most of the instructions operating on the Register File have direct access to all registers, and
most of them are single cycle instructions.
As shown in Figure 3-2, each register is also assigned a data memory address, mapping them
directly into the first 32 locations of the user Data Space. Although not being physically implemented as SRAM locations, this memory organization provides great flexibility in access of the
registers, as the X-, Y- and Z-pointer registers can be set to index any register in the file.
3.5.1
The X-register, Y-register, and Z-register
The registers R26..R31 have some added functions to their general purpose usage. These registers are 16-bit address pointers for indirect addressing of the data space. The three indirect
address registers X, Y, and Z are defined as described in Figure 3-3.
15
7647F–AVR–04/09
Figure 3-3.
The X-, Y-, and Z-registers
15
X-register
XH
XL
7
0
R27 (0x1B)
YH
YL
7
0
R29 (0x1D)
Z-register
0
R26 (0x1A)
15
Y-register
0
7
0
7
0
R28 (0x1C)
15
ZH
7
0
ZL
7
R31 (0x1F)
0
0
R30 (0x1E)
In the different addressing modes these address registers have functions as fixed displacement,
automatic increment, and automatic decrement (see the instruction set reference for details).
3.6
Stack Pointer
The Stack is mainly used for storing temporary data, for storing local variables and for storing
return addresses after interrupts and subroutine calls. The Stack Pointer Register always points
to the top of the Stack. Note that the Stack is implemented as growing from higher memory locations to lower memory locations. This implies that a Stack PUSH command decreases the Stack
Pointer.
The Stack Pointer points to the data SRAM Stack area where the Subroutine and Interrupt
Stacks are located. This Stack space in the data SRAM must be defined by the program before
any subroutine calls are executed or interrupts are enabled. The Stack Pointer must be set to
point above 0x100. The Stack Pointer is decremented by one when data is pushed onto the
Stack with the PUSH instruction, and it is decremented by two when the return address is
pushed onto the Stack with subroutine call or interrupt. The Stack Pointer is incremented by one
when data is popped from the Stack with the POP instruction, and it is incremented by two when
data is popped from the Stack with return from subroutine RET or return from interrupt RETI.
The AVR Stack Pointer is implemented as two 8-bit registers in the I/O space. The number of
bits actually used is implementation dependent. Note that the data space in some implementations of the AVR architecture is so small that only SPL is needed. In this case, the SPH Register
will not be present.
Bit
Read/Write
Initial Value
16
15
14
13
12
11
10
9
8
SP15
SP14
SP13
SP12
SP11
SP10
SP9
SP8
SPH
SP7
SP6
SP5
SP4
SP3
SP2
SP1
SP0
SPL
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
3.7
Instruction Execution Timing
This section describes the general access timing concepts for instruction execution. The AVR
CPU is driven by the CPU clock clkCPU, directly generated from the selected clock source for the
chip. No internal clock division is used.
Figure 3-4 shows the parallel instruction fetches and instruction executions enabled by the Harvard architecture and the fast-access Register File concept. This is the basic pipelining concept
to obtain up to 1 MIPS per MHz with the corresponding unique results for functions per cost,
functions per clocks, and functions per power-unit.
Figure 3-4.
The Parallel Instruction Fetches and Instruction Executions
T1
T2
T3
T4
clkCPU
1st Instruction Fetch
1st Instruction Execute
2nd Instruction Fetch
2nd Instruction Execute
3rd Instruction Fetch
3rd Instruction Execute
4th Instruction Fetch
Figure 3-5 shows the internal timing concept for the Register File. In a single clock cycle an ALU
operation using two register operands is executed, and the result is stored back to the destination register.
Figure 3-5.
Single Cycle ALU Operation
T1
T2
T3
T4
clkCPU
Total Execution Time
Register Operands Fetch
ALU Operation Execute
Result Write Back
3.8
Reset and Interrupt Handling
The AVR provides several different interrupt sources. These interrupts and the separate Reset
Vector each have a separate program vector in the program memory space. All interrupts are
assigned individual enable bits which must be written logic one together with the Global Interrupt
Enable bit in the Status Register in order to enable the interrupt. Depending on the Program
Counter value, interrupts may be automatically disabled when Boot Lock bits BLB02 or BLB12
are programmed. This feature improves software security. See the section “Memory Programming” on page 296 for details.
17
7647F–AVR–04/09
The lowest addresses in the program memory space are by default defined as the Reset and
Interrupt Vectors. The complete list of vectors is shown in “Interrupts” on page 57. The list also
determines the priority levels of the different interrupts. The lower the address the higher is the
priority level. RESET has the highest priority, and next is ANACOMP0 – the Analog Comparator
0 Interrupt. The Interrupt Vectors can be moved to the start of the Boot Flash section by setting
the IVSEL bit in the MCU Control Register (MCUCR). Refer to “Interrupts” on page 57 for more
information. The Reset Vector can also be moved to the start of the Boot Flash section by programming the BOOTRST Fuse, see “Boot Loader Support – Read-While-Write
Self-Programming ATmega16/32/64/M1/C1” on page 279.
3.8.1
Interrupt Behavior
When an interrupt occurs, the Global Interrupt Enable I-bit is cleared and all interrupts are disabled. The user software can write logic one to the I-bit to enable nested interrupts. All enabled
interrupts can then interrupt the current interrupt routine. The I-bit is automatically set when a
Return from Interrupt instruction – RETI – is executed.
There are basically two types of interrupts. The first type is triggered by an event that sets the
interrupt flag. For these interrupts, the Program Counter is vectored to the actual Interrupt Vector
in order to execute the interrupt handling routine, and hardware clears the corresponding interrupt flag. Interrupt flags can also be cleared by writing a logic one to the flag bit position(s) to be
cleared. If an interrupt condition occurs while the corresponding interrupt enable bit is cleared,
the interrupt flag will be set and remembered until the interrupt is enabled, or the flag is cleared
by software. Similarly, if one or more interrupt conditions occur while the Global Interrupt Enable
bit is cleared, the corresponding interrupt flag(s) will be set and remembered until the Global
Interrupt Enable bit is set, and will then be executed by order of priority.
The second type of interrupts will trigger as long as the interrupt condition is present. These
interrupts do not necessarily have interrupt flags. If the interrupt condition disappears before the
interrupt is enabled, the interrupt will not be triggered.
When the AVR exits from an interrupt, it will always return to the main program and execute one
more instruction before any pending interrupt is served.
Note that the Status Register is not automatically stored when entering an interrupt routine, nor
restored when returning from an interrupt routine. This must be handled by software.
When using the CLI instruction to disable interrupts, the interrupts will be immediately disabled.
No interrupt will be executed after the CLI instruction, even if it occurs simultaneously with the
CLI instruction. The following example shows how this can be used to avoid interrupts during the
timed EEPROM write sequence.
18
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Assembly Code Example
in r16, SREG
; store SREG value
cli
; disable interrupts during timed sequence
sbi EECR, EEMWE
; start EEPROM write
sbi EECR, EEWE
out SREG, r16
; restore SREG value (I-bit)
C Code Example
char cSREG;
cSREG = SREG;
/* store SREG value */
/* disable interrupts during timed sequence */
_CLI();
EECR |= (1<<EEMWE); /* start EEPROM write */
EECR |= (1<<EEWE);
SREG = cSREG;
/* restore SREG value (I-bit) */
When using the SEI instruction to enable interrupts, the instruction following SEI will be executed before any pending interrupts, as shown in this example.
Assembly Code Example
sei
; set Global Interrupt Enable
sleep; enter sleep, waiting for interrupt
; note: will enter sleep before any pending
; interrupt(s)
C Code Example
_SEI(); /* set Global Interrupt Enable */
_SLEEP(); /* enter sleep, waiting for interrupt */
/* note: will enter sleep before any pending interrupt(s) */
3.8.2
Interrupt Response Time
The interrupt execution response for all the enabled AVR interrupts is four clock cycles minimum. After four clock cycles the program vector address for the actual interrupt handling routine
is executed. During this four clock cycle period, the Program Counter is pushed onto the Stack.
The vector is normally a jump to the interrupt routine, and this jump takes three clock cycles. If
an interrupt occurs during execution of a multi-cycle instruction, this instruction is completed
before the interrupt is served. If an interrupt occurs when the MCU is in sleep mode, the interrupt
execution response time is increased by four clock cycles. This increase comes in addition to the
start-up time from the selected sleep mode.
A return from an interrupt handling routine takes four clock cycles. During these four clock
cycles, the Program Counter (two bytes) is popped back from the Stack, the Stack Pointer is
incremented by two, and the I-bit in SREG is set.
19
7647F–AVR–04/09
4. Memories
This section describes the different memories in the ATmega16/32/64/M1/C1. The AVR architecture has two main memory spaces, the Data Memory and the Program Memory space. In
addition, the ATmega16/32/64/M1/C1 features an EEPROM Memory for data storage. All three
memory spaces are linear and regular.
4.1
In-System Reprogrammable Flash Program Memory
The ATmega16/32/64/M1/C1 contains 16K/32K/64K bytes On-chip In-System Reprogrammable
Flash memory for program storage. Since all AVR instructions are 16 or 32 bits wide, the Flash
is organized as 8K x 16, 16K x 16 , 32K x 16. For software security, the Flash Program memory
space is divided into two sections, Boot Program section and Application Program section.
The Flash memory has an endurance of at least 10,000 write/erase cycles. The
ATmega16/32/64/M1/C1 Program Counter (PC) is 14/15 bits wide, thus addressing the
8K/16K/32K program memory locations. The operation of Boot Program section and associated
Boot Lock bits for software protection are described in detail in “Boot Loader Support –
Read-While-Write Self-Programming ATmega16/32/64/M1/C1” on page 279. “Memory Programming” on page 296 contains a detailed description on Flash programming in SPI or Parallel
programming mode.
Constant tables can be allocated within the entire program memory address space (see the LPM
– Load Program Memory.
Timing diagrams for instruction fetch and execution are presented in “Instruction Execution Timing” on page 17.
Figure 4-1.
Program Memory Map
Program Memory
0x0000
Application Flash Section
Boot Flash S
ection
0x1FFF/0x3FFF/0x7F
20
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
4.2
SRAM Data Memory
Figure 4-2 shows how the ATmega16/32/64/M1/C1 SRAM Memory is organized.
The ATmega16/32/64/M1/C1 is a complex microcontroller with more peripheral units than can
be supported within the 64 locations reserved in the Opcode for the IN and OUT instructions. For
the Extended I/O space from 0x60 - 0xFF in SRAM, only the ST/STS/STD and LD/LDS/LDD
instructions can be used.
The lower 2304 data memory locations address both the Register File, the I/O memory,
Extended I/O memory, and the internal data SRAM. The first 32 locations address the Register
File, the next 64 location the standard I/O memory, then 160 locations of Extended I/O memory,
and the next 1024/2048/4096 locations address the internal data SRAM.
The five different addressing modes for the data memory cover: Direct, Indirect with Displacement, Indirect, Indirect with Pre-decrement, and Indirect with Post-increment. In the Register
File, registers R26 to R31 feature the indirect addressing pointer registers.
The direct addressing reaches the entire data space.
The Indirect with Displacement mode reaches 63 address locations from the base address given
by the Y- or Z-register.
When using register indirect addressing modes with automatic pre-decrement and post-increment, the address registers X, Y, and Z are decremented or incremented.
The 32 general purpose working registers, 64 I/O Registers, 160 Extended I/O Registers, and
the 1024/2048/4096 bytes of internal data SRAM in the ATmega16/32/64/M1/C1 are all accessible through all these addressing modes. The Register File is described in “General Purpose
Register File” on page 15.
Figure 4-2.
Data Memory Map for 1024/2048/4096 Internal SRAM
Data Memory
32 Registers
64 I/O Registers
160 Ext I/O Reg.
Internal SRAM
(1024x8)
(2048x8)
(4096x8)
4.2.1
0x0000 - 0x001F
0x0020 - 0x005F
0x0060 - 0x00FF
0x0100
0x04FF/0x08FF/0x10FF
SRAM Data Access Times
This section describes the general access timing concepts for internal memory access.
The internal data SRAM access is performed in two clkCPU cycles as described in Figure 4-3 on
page 22.
21
7647F–AVR–04/09
Figure 4-3.
On-chip Data SRAM Access Cycles
T1
T2
T3
clkCPU
Address
Compute Address
Address valid
Write
Data
WR
Read
Data
RD
Memory Access Instruction
4.3
Next Instruction
EEPROM Data Memory
The ATmega16/32/64/M1/C1 contains 512/1024/2048 bytes of data EEPROM memory. It is
organized as a separate data space, in which single bytes can be read and written. The
EEPROM has an endurance of at least 100,000 write/erase cycles. The access between the
EEPROM and the CPU is described in the following, specifying the EEPROM Address Registers, the EEPROM Data Register, and the EEPROM Control Register.
For a detailed description of SPI and Parallel data downloading to the EEPROM, see “Serial
Downloading” on page 313 , and “Parallel Programming Parameters, Pin Mapping, and Commands” on page 301 respectively.
4.3.1
EEPROM Read/Write Access
The EEPROM Access Registers are accessible in the I/O space.
The write access time for the EEPROM is given in Table 4-2. A self-timing function, however,
lets the user software detect when the next byte can be written. If the user code contains instructions that write the EEPROM, some precautions must be taken. In heavily filtered power
supplies, VCC is likely to rise or fall slowly on power-up/down. This causes the device for some
period of time to run at a voltage lower than specified as minimum for the clock frequency used.
See “Preventing EEPROM Corruption” on page 27.for details on how to avoid problems in these
situations.
In order to prevent unintentional EEPROM writes, a specific write procedure must be followed.
Refer to the description of the EEPROM Control Register for details on this.
When the EEPROM is read, the CPU is halted for four clock cycles before the next instruction is
executed. When the EEPROM is written, the CPU is halted for two clock cycles before the next
instruction is executed.
22
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
4.3.2
The EEPROM Address Registers – EEARH and EEARL
Bit
Read/Write
Initial Value
15
14
13
12
11
10
9
8
–
–
–
–
–
EEAR10
EEAR9
EEAR8
EEARH
EEAR7
EEAR6
EEAR5
EEAR4
EEAR3
EEAR2
EEAR1
EEAR0
EEARL
7
6
5
4
3
2
1
0
R
R
R
R
R
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
X
X
X
X
X
X
X
X
X
X
X
• Bits 15.11 – Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and will always read as zero.
• Bits 9..0 – EEAR10..0: EEPROM Address
The EEPROM Address Registers – EEARH and EEARL specify the EEPROM address in the
512/1024/2048 bytes EEPROM space. The EEPROM data bytes are addressed linearly
between 0 and 511/1023/2047. The initial value of EEAR is undefined. A proper value must be
written before the EEPROM may be accessed.
4.3.3
The EEPROM Data Register – EEDR
Bit
7
6
5
4
3
2
1
0
EEDR7
EEDR6
EEDR5
EEDR4
EEDR3
EEDR2
EEDR1
EEDR0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
EEDR
• Bits 7..0 – EEDR7.0: EEPROM Data
For the EEPROM write operation, the EEDR Register contains the data to be written to the
EEPROM in the address given by the EEAR Register. For the EEPROM read operation, the
EEDR contains the data read out from the EEPROM at the address given by EEAR.
4.3.4
The EEPROM Control Register – EECR
Bit
7
6
5
4
3
2
1
0
–
–
EEPM1
EEPM0
EERIE
EEMWE
EEWE
EERE
Read/Write
R
R
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
X
X
0
0
X
0
EECR
• Bits 7..6 – Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and will always read as zero.
• Bits 5..4 – EEPM1 and EEPM0: EEPROM Programming Mode Bits
The EEPROM Programming mode bit setting defines which programming action that will be triggered when writing EEWE. It is possible to program data in one atomic operation (erase the old
value and program the new value) or to split the Erase and Write operations in two different
operations. The Programming times for the different modes are shown in Table 4-1 on page 24.
23
7647F–AVR–04/09
While EEWE is set, any write to EEPMn will be ignored. During reset, the EEPMn bits will be
reset to 0b00 unless the EEPROM is busy programming.
Table 4-1.
EEPROM Mode Bits
EEPM1
EEPM0
Programming Time
Operation
0
0
3.4 ms
Erase and Write in one operation (Atomic Operation)
0
1
1.8 ms
Erase Only
1
0
1.8 ms
Write Only
1
1
–
Reserved for future use
• Bit 3 – EERIE: EEPROM Ready Interrupt Enable
Writing EERIE to one enables the EEPROM Ready Interrupt if the I bit in SREG is set. Writing
EERIE to zero disables the interrupt. The EEPROM Ready interrupt generates a constant interrupt when EEWE is cleared. The interrupt will not be generated during EEPROM write or SPM.
• Bit 2 – EEMWE: EEPROM Master Write Enable
The EEMWE bit determines whether setting EEWE to one causes the EEPROM to be written.
When EEMWE is set, setting EEWE within four clock cycles will write data to the EEPROM at
the selected address If EEMWE is zero, setting EEWE will have no effect. When EEMWE has
been written to one by software, hardware clears the bit to zero after four clock cycles. See the
description of the EEWE bit for an EEPROM write procedure.
• Bit 1 – EEWE: EEPROM Write Enable
The EEPROM Write Enable Signal EEWE is the write strobe to the EEPROM. When address
and data are correctly set up, the EEWE bit must be written to one to write the value into the
EEPROM. The EEMWE bit must be written to one before a logical one is written to EEWE, otherwise no EEPROM write takes place. The following procedure should be followed when writing
the EEPROM (the order of steps 3 and 4 is not essential):
1. Wait until EEWE becomes zero.
2. Wait until SPMEN (Store Program Memory Enable) in SPMCSR (Store Program Memory
Control and Status Register) becomes zero.
3. Write new EEPROM address to EEAR (optional).
4. Write new EEPROM data to EEDR (optional).
5. Write a logical one to the EEMWE bit while writing a zero to EEWE in EECR.
6. Within four clock cycles after setting EEMWE, write a logical one to EEWE.
The EEPROM can not be programmed during a CPU write to the Flash memory. The software
must check that the Flash programming is completed before initiating a new EEPROM write.
Step 2 is only relevant if the software contains a Boot Loader allowing the CPU to program the
Flash. If the Flash is never being updated by the CPU, step 2 can be omitted. See “Boot Loader
Support – Read-While-Write Self-Programming ATmega16/32/64/M1/C1” on page 279 for
details about Boot programming.
Caution: An interrupt between step 5 and step 6 will make the write cycle fail, since the
EEPROM Master Write Enable will time-out. If an interrupt routine accessing the EEPROM is
interrupting another EEPROM access, the EEAR or EEDR Register will be modified, causing the
interrupted EEPROM access to fail. It is recommended to have the Global Interrupt Flag cleared
during all the steps to avoid these problems.
When the write access time has elapsed, the EEWE bit is cleared by hardware. The user software can poll this bit and wait for a zero before writing the next byte. When EEWE has been set,
the CPU is halted for two cycles before the next instruction is executed.
24
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 0 – EERE: EEPROM Read Enable
The EEPROM Read Enable Signal EERE is the read strobe to the EEPROM. When the correct
address is set up in the EEAR Register, the EERE bit must be written to a logic one to trigger the
EEPROM read. The EEPROM read access takes one instruction, and the requested data is
available immediately. When the EEPROM is read, the CPU is halted for four cycles before the
next instruction is executed.
The user should poll the EEWE bit before starting the read operation. If a write operation is in
progress, it is neither possible to read the EEPROM, nor to change the EEAR Register.
The calibrated Oscillator is used to time the EEPROM accesses. Table 4-2 lists the typical programming time for EEPROM access from the CPU.
Table 4-2.
EEPROM Programming Time.
Symbol
EEPROM write
(from CPU)
Number of Calibrated RC Oscillator Cycles
Typ Programming Time
26368
3.3 ms
The following code examples show one assembly and one C function for writing to the
EEPROM. The examples assume that interrupts are controlled (e.g. by disabling interrupts globally) so that no interrupts will occur during execution of these functions. The examples also
assume that no Flash Boot Loader is present in the software. If such code is present, the
EEPROM write function must also wait for any ongoing SPM command to finish.
25
7647F–AVR–04/09
Assembly Code Example
EEPROM_write:
; Wait for completion of previous write
sbic EECR,EEWE
rjmp EEPROM_write
; Set up address (r18:r17) in address register
out EEARH, r18
out EEARL, r17
; Write data (r16) to data register
out EEDR,r16
; Write logical one to EEMWE
sbi EECR,EEMWE
; Start eeprom write by setting EEWE
sbi EECR,EEWE
ret
C Code Example
void EEPROM_write (unsigned int uiAddress, unsigned char ucData)
{
/* Wait for completion of previous write */
while(EECR & (1<<EEWE))
;
/* Set up address and data registers */
EEAR = uiAddress;
EEDR = ucData;
/* Write logical one to EEMWE */
EECR |= (1<<EEMWE);
/* Start eeprom write by setting EEWE */
EECR |= (1<<EEWE);
}
26
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The next code examples show assembly and C functions for reading the EEPROM. The examples assume that interrupts are controlled so that no interrupts will occur during execution of
these functions.
Assembly Code Example
EEPROM_read:
; Wait for completion of previous write
sbic EECR,EEWE
rjmp EEPROM_read
; Set up address (r18:r17) in address register
out EEARH, r18
out EEARL, r17
; Start eeprom read by writing EERE
sbi EECR,EERE
; Read data from data register
in
r16,EEDR
ret
C Code Example
unsigned char EEPROM_read(unsigned int uiAddress)
{
/* Wait for completion of previous write */
while(EECR & (1<<EEWE))
;
/* Set up address register */
EEAR = uiAddress;
/* Start eeprom read by writing EERE */
EECR |= (1<<EERE);
/* Return data from data register */
return EEDR;
}
4.3.5
Preventing EEPROM Corruption
During periods of low VCC, the EEPROM data can be corrupted because the supply voltage is
too low for the CPU and the EEPROM to operate properly. These issues are the same as for
board level systems using EEPROM, and the same design solutions should be applied.
An EEPROM data corruption can be caused by two situations when the voltage is too low. First,
a regular write sequence to the EEPROM requires a minimum voltage to operate correctly. Secondly, the CPU itself can execute instructions incorrectly, if the supply voltage is too low.
EEPROM data corruption can easily be avoided by following this design recommendation:
Keep the AVR RESET active (low) during periods of insufficient power supply voltage. This can
be done by enabling the internal Brown-out Detector (BOD). If the detection level of the internal
BOD does not match the needed detection level, an external low VCC reset Protection circuit can
be used. If a reset occurs while a write operation is in progress, the write operation will be completed provided that the power supply voltage is sufficient.
27
7647F–AVR–04/09
4.4
I/O Memory
The I/O space definition of the ATmega16/32/64/M1/C1 is shown in “Register Summary” on
page 347.
All ATmega16/32/64/M1/C1 I/Os and peripherals are placed in the I/O space. All I/O locations
may be accessed by the LD/LDS/LDD and ST/STS/STD instructions, transferring data between
the 32 general purpose working registers and the I/O space. I/O registers within the address
range 0x00 - 0x1F are directly bit-accessible using the SBI and CBI instructions. In these registers, the value of single bits can be checked by using the SBIS and SBIC instructions. Refer to
the instruction set section for more details. When using the I/O specific commands IN and OUT,
the I/O addresses 0x00 - 0x3F must be used. When addressing I/O registers as data space
using LD and ST instructions, 0x20 must be added to these addresses. The
ATmega16/32/64/M1/C1 is a complex microcontroller with more peripheral units than can be
supported within the 64 location reserved in Opcode for the IN and OUT instructions. For the
Extended I/O space from 0x60 - 0xFF in SRAM, only the ST/STS/STD and LD/LDS/LDD instructions can be used.
For compatibility with future devices, reserved bits should be written to zero if accessed.
Reserved I/O memory addresses should never be written.
Some of the status flags are cleared by writing a logical one to them. Note that, unlike most other
AVR’s, the CBI and SBI instructions will only operate on the specified bit, and can therefore be
used on registers containing such status flags. The CBI and SBI instructions work with registers
0x00 to 0x1F only.
The I/O and peripherals control registers are explained in later sections.
4.5
General Purpose I/O Registers
The ATmega16/32/64/M1/C1 contains four General Purpose I/O Registers. These registers can
be used for storing any information, and they are particularly useful for storing global variables
and status flags.
The General Purpose I/O Registers, within the address range 0x00 - 0x1F, are directly
bit-accessible using the SBI, CBI, SBIS, and SBIC instructions.
4.5.1
General Purpose I/O Register 0 – GPIOR0
Bit
7
6
5
4
3
2
1
0
GPIOR07 GPIOR06 GPIOR05 GPIOR04 GPIOR03 GPIOR02 GPIOR01 GPIOR00
4.5.2
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
5
4
3
2
1
0
General Purpose I/O Register 1 – GPIOR1
Bit
7
6
GPIOR17 GPIOR16 GPIOR15 GPIOR14 GPIOR13 GPIOR12 GPIOR11 GPIOR10
4.5.3
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
5
4
3
2
1
0
GPIOR1
General Purpose I/O Register 2 – GPIOR2
Bit
7
6
GPIOR27 GPIOR26 GPIOR25 GPIOR24 GPIOR23 GPIOR22 GPIOR21 GPIOR20
28
GPIOR0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
GPIOR2
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
5. System Clock
5.1
Clock Systems and their Distribution
Figure 5-1 presents the principal clock systems in the AVR and their distribution. All of the clocks
need not be active at a given time. In order to reduce power consumption, the clocks to unused
modules can be halted by using different sleep modes, as described in “Power Management and
Sleep Modes” on page 40. The clock systems are detailed below.
Figure 5-1.
Fast Peripherals
CLK
Clock Distribution
General I/O
Modules
ADC
CPU Core
Flash and
EEPROM
RAM
clk ADC
PLL
PLL
clk I/O
clk CPU
AVR Clock
Control Unit
clk FLASH
Reset Logic
Source Clock
PLL Input
Multiplexer
Clock
Multiplexer
External Clock
5.1.1
Watchdog Timer
Watchdog Clock
Watchdog
Oscillator
(Crystal
Oscillator)
Calibrated RC
Oscillator
CPU Clock – clkCPU
The CPU clock is routed to parts of the system concerned with operation of the AVR core.
Examples of such modules are the General Purpose Register File, the Status Register and the
data memory holding the Stack Pointer. Halting the CPU clock inhibits the core from performing
general operations and calculations.
5.1.2
I/O Clock – clkI/O
The I/O clock is used by the majority of the I/O modules, like Timer/Counters, SPI, UART. The
I/O clock is also used by the External Interrupt module, but note that some external interrupts
are detected by asynchronous logic, allowing such interrupts to be detected even if the I/O clock
is halted.
29
7647F–AVR–04/09
5.1.3
Flash Clock – clkFLASH
The Flash clock controls operation of the Flash interface. The Flash clock is usually active simultaneously with the CPU clock.
5.1.4
PLL Clock – clkPLL
The PLL clock allows the fast peripherals to be clocked directly from a 64/32 MHz clock. A 16
MHz clock is also derived for the CPU.
5.1.5
ADC Clock – clkADC
The ADC is provided with a dedicated clock domain. This allows halting the CPU and I/O clocks
in order to reduce noise generated by digital circuitry. This gives more accurate ADC conversion
results.
5.2
Clock Sources
The device has the following clock source options, selectable by Flash Fuse bits as illustrated
Table 5-1. The clock from the selected source is input to the AVR clock generator, and routed to
the appropriate modules.
Table 5-1.
Device Clocking Options Select(1)
Device Clocking Option
System
Clock
PLL Input
CKSEL3..0
External Crystal/Ceramic Resonator
Ext Osc
RC Osc
1111 - 1000
PLL output divided by 4 : 16 MHz / PLL driven by External
Crystal/Ceramic Resonator
Ext Osc
Ext Osc
0100
PLL output divided by 4 : 16 MHz / PLL driven by External
Crystal/Ceramic Resonator
PLL / 4
Ext Osc
0101
Reserved
N/A
N/A
0110
Reserved
N/A
N/A
0111
PLL output divided by 4 : 16 MHz
PLL / 4
RC Osc
0011
Calibrated Internal RC Oscillator
RC Osc
RC Osc
0010
PLL output divided by 4 : 16 MHz / PLL driven by External
clock
PLL / 4
Ext Clk
0001
External Clock
Ext Clk
RC Osc
0000
Note:
1. For all fuses “1” means unprogrammed while “0” means programmed.
2. Ext Osc : External Osc
3. RC Osc : Internal RC Oscillator
4. Ext Clk : External Clock Input
The various choices for each clocking option is given in the following sections. When the CPU
wakes up from Power-down or Power-save, the selected clock source is used to time the
start-up, ensuring stable Oscillator operation before instruction execution starts. When the CPU
starts from reset, there is an additional delay allowing the power to reach a stable level before
starting normal operation. The Watchdog Oscillator is used for timing this real-time part of the
start-up time. The number of WDT Oscillator cycles used for each time-out is shown in Table
5-2. The frequency of the Watchdog Oscillator is voltage dependent as shown in “Watchdog
Oscillator Frequency versus VCC” on page 342.
30
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 5-2.
5.3
Number of Watchdog Oscillator Cycles
Typ Time-out (VCC = 5.0V)
Typ Time-out (VCC = 3.0V)
Number of Cycles
4.1 ms
4.3 ms
4K (4,096)
65 ms
69 ms
64K (65,536)
Default Clock Source
The device is shipped with CKSEL = “0010”, SUT = “10”, and CKDIV8 programmed. The default
clock source setting is the Internal RC Oscillator with longest start-up time and an initial system
clock prescaling of 8. This default setting ensures that all users can make their desired clock
source setting using an In-System or Parallel programmer.
5.4
Low Power Crystal Oscillator
XTAL1 and XTAL2 are input and output, respectively, of an inverting amplifier which can be configured for use as an On-chip Oscillator, as shown in Figure 5-2. Either a quartz crystal or a
ceramic resonator may be used.
This Crystal Oscillator is a low power oscillator, with reduced voltage swing on the XTAL2 output. It gives the lowest power consumption, but is not capable of driving other clock inputs.
C1 and C2 should always be equal for both crystals and resonators. The optimal value of the
capacitors depends on the crystal or resonator in use, the amount of stray capacitance, and the
electromagnetic noise of the environment. Some initial guidelines for choosing capacitors for
use with crystals are given in Table 5-3. For ceramic resonators, the capacitor values given by
the manufacturer should be used. For more information on how to choose capacitors and other
details on Oscillator operation, refer to the Multi-purpose Oscillator Application Note.
Figure 5-2.
Crystal Oscillator Connections
C2
C1
XTAL2
XTAL1
GND
31
7647F–AVR–04/09
The Oscillator can operate in three different modes, each optimized for a specific frequency
range. The operating mode is selected by the fuses CKSEL3..1 as shown in Table 5-3.
Table 5-3.
Crystal Oscillator Operating Modes
CKSEL3..1
Frequency Range (MHz)
Recommended Range for Capacitors C1 and
C2 for Use with Crystals (pF)
100(1)
0.4 - 0.9
–
101
0.9 - 3.0
12 - 22
110
3.0 - 8.0
12 - 22
111
8.0 -16.0
12 - 22
Notes:
1. This option should not be used with crystals, only with ceramic resonators.
The CKSEL0 Fuse together with the SUT1..0 Fuses select the start-up times as shown in Table
5-4.
Table 5-4.
CKSEL0
SUT1..0
Start-up Time from
Power-down and
Power-save
0
00
258 CK(1)
14CK + 4.1 ms
Ceramic resonator, fast
rising power
0
01
258 CK(1)
14CK + 65 ms
Ceramic resonator, slowly
rising power
0
10
1K CK(2)
14CK
Ceramic resonator, BOD
enabled
0
11
1K CK(2)
14CK + 4.1 ms
Ceramic resonator, fast
rising power
1
00
1K CK(2)
14CK + 65 ms
Ceramic resonator, slowly
rising power
1
01
16K CK
14CK
Crystal Oscillator, BOD
enabled
1
10
16K CK
14CK + 4.1 ms
Crystal Oscillator, fast
rising power
1
Notes:
32
Start-up Times for the Oscillator Clock Selection
Additional Delay
from Reset
(VCC = 5.0V)
Recommended Usage
Crystal Oscillator, slowly
rising power
1. These options should only be used when not operating close to the maximum frequency of the
device, and only if frequency stability at start-up is not important for the application. These
options are not suitable for crystals.
2. These options are intended for use with ceramic resonators and will ensure frequency stability
at start-up. They can also be used with crystals when not operating close to the maximum frequency of the device, and if frequency stability at start-up is not important for the application.
11
16K CK
14CK + 65 ms
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
5.5
Calibrated Internal RC Oscillator
By default, the Internal RC OScillator provides an approximate 8.0 MHz clock. Though voltage
and temperature dependent, this clock can be very accurately calibrated by the user. The device
is shipped with the CKDIV8 Fuse programmed. See “System Clock Prescaler” on page 37 for
more details.
This clock may be selected as the system clock by programming the CKSEL Fuses as shown in
Table 5-1 on page 30. If selected, it will operate with no external components. During reset,
hardware loads the pre-programmed calibration value into the OSCCAL Register and thereby
automatically calibrates the RC Oscillator. The accuracy of this calibration is shown as Factory
calibration in Table 26-1 on page 319.
By changing the OSCCAL register from SW, see “Oscillator Calibration Register – OSCCAL” on
page 34, it is possible to get a higher calibration accuracy than by using the factory calibration.
The accuracy of this calibration is shown as User calibration in “Clock Characteristics” on page
319.
When this Oscillator is used as the chip clock, the Watchdog Oscillator will still be used for the
Watchdog Timer and for the Reset Time-out. For more information on the pre-programmed calibration value, see the section.
Internal Calibrated RC Oscillator Operating Modes(1)(2)
Table 5-5.
Notes:
Frequency Range (MHz)
CKSEL3..0
7.3 - 8.1
0010
1. The device is shipped with this option selected.
2. If 8 MHz frequency exceeds the specification of the device (depends on VCC), the CKDIV8
Fuse can be programmed in order to divide the internal frequency by 8.
When this Oscillator is selected, start-up times are determined by the SUT Fuses as shown in
Table 5-6 on page 33.
Table 5-6.
Start-up times for the internal calibrated RC Oscillator clock selection
Start-up Time from
Power-down and Power-save
Additional Delay from
Reset (VCC = 5.0V)
SUT1..0
BOD enabled
6 CK
14CK(1)
00
Fast rising power
6 CK
14CK + 4.1 ms
Power Conditions
Slowly rising power
6 CK
14CK + 65 ms
(2)
Reserved
Note:
01
10
11
1. If the RSTDISBL fuse is programmed, this start-up time will be increased to
14CK + 4.1 ms to ensure programming mode can be entered.
2. The device is shipped with this option selected.
33
7647F–AVR–04/09
5.5.1
Oscillator Calibration Register – OSCCAL
Bit
Read/Write
7
6
5
4
3
2
1
0
CAL7
CAL6
CAL5
CAL4
CAL3
CAL2
CAL1
CAL0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
OSCCAL
Device Specific Calibration Value
• Bits 7..0 – CAL7..0: Oscillator Calibration Value
The Oscillator Calibration Register is used to trim the Calibrated Internal RC Oscillator to
remove process variations from the oscillator frequency. The factory-calibrated value is automatically written to this register during chip reset, giving an oscillator frequency of 8.0 MHz at 25°C.
The application software can write this register to change the oscillator frequency. The oscillator
can be calibrated to any frequency in the range 7.3 - 8.1 MHz within ±1% accuracy. Calibration
outside that range is not guaranteed.
Note that this oscillator is used to time EEPROM and Flash write accesses, and these write
times will be affected accordingly. If the EEPROM or Flash are written, do not calibrate to more
than 8.8 MHz. Otherwise, the EEPROM or Flash write may fail.
The CAL7 bit determines the range of operation for the oscillator. Setting this bit to 0 gives the
lowest frequency range, setting this bit to 1 gives the highest frequency range. The two frequency ranges are overlapping, in other words a setting of OSCCAL = 0x7F gives a higher
frequency than OSCCAL = 0x80.
The CAL6..0 bits are used to tune the frequency within the selected range. A setting of 0x00
gives the lowest frequency in that range, and a setting of 0x7F gives the highest frequency in the
range. Incrementing CAL6..0 by 1 will give a frequency increment of less than 2% in the frequency range 7.3 - 8.1 MHz.
5.6
5.6.1
PLL
Internal PLL
The internal PLL in ATmega16/32/64/M1/C1 generates a clock frequency that is 64x multiplied
from its nominal 1 MHz input. The source of the 1 MHz PLL input clock can be:
• the output of the internal RC Oscillator divided by 8
• the output of the Crystal Oscillator divided by 8
• the external clock divided by 8
See the Figure 5-3 on page 35.
When the PLL is locked on the RC Oscillator, adjusting the RC Oscillator via OSCCAL Register,
will also modify the PLL clock output. However, even if the possibly divided RC Oscillator is
taken to a higher frequency than 8 MHz, the PLL output clock frequency saturates at 70 MHz
(worst case) and remains oscillating at the maximum frequency. It should be noted that the PLL
in this case is not locked any more with its 1MHz source clock.
Therefore it is recommended not to take the OSCCAL adjustments to a higher frequency than 8
MHz in order to keep the PLL in the correct operating range.
The internal PLL is enabled only when the PLLE bit in the register PLLCSR is set. The bit
PLOCK from the register PLLCSR is set when PLL is locked.
Both internal 8 MHz RC Oscillator, Crystal Oscillator and PLL are switched off in Power-down
and Standby sleep modes.04/09
34
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 5-7.
CKSEL
3..0
0011
RC Osc
0101
Ext Osc
0001
Ext Clk
Start-up Times when the PLL is selected as system clock
SUT1..0
Start-up Time from Power-down
and Power-save
Additional Delay from Reset
(VCC = 5.0V)
00
1K CK
14CK
01
1K CK
14CK + 4 ms
10
1K CK
14CK + 64 ms
11
16K CK
14CK
00
1K CK
14CK
01
1K CK
14CK + 4 ms
10
16K CK
14CK + 4 ms
11
16K CK
14CK + 64 ms
00
6 CK
(1)
01
6 CK (2)
14CK + 4 ms
10
6 CK (3)
14CK + 64 ms
14CK
11
Figure 5-3.
Reserved
1.
This value do not provide a proper restart ; do not use PD in this clock scheme
2.
This value do not provide a proper restart ; do not use PD in this clock scheme
3.
This value do not provide a proper restart ; do not use PD in this clock scheme
PLL Clocking System
OSCCAL
PLLF
PLLE
CKSEL3..0
PLOCK
Lock
Detector
RC OSCILLATOR
8 MHz
DIVIDE
BY 8
PLL
64x
DIVIDE
BY 2
CLK PLL
DIVIDE
BY 4
CK SOURCE
XTAL1
XTAL2
OSCILLATORS
35
7647F–AVR–04/09
5.6.2
PLL Control and Status Register – PLLCSR
Bit
7
6
5
4
3
2
1
0
$29 ($29)
–
–
–
–
–
PLLF
PLLE
PLOCK
Read/Write
R
R
R
R
R
R/W
R/W
R
Initial Value
0
0
0
0
0
0
0/1
0
PLLCSR
• Bit 7..3 – Res: Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and always read as zero.
• Bit 2 – PLLF: PLL Factor
The PLLF bit is used to select the division factor of the PLL.
If PLLF is set, the PLL output is 64MHz.
If PLLF is clear, the PLL output is 32MHz.
• Bit 1 – PLLE: PLL Enable
When the PLLE is set, the PLL is started and if not yet started the internal RC Oscillator is
started as PLL reference clock. If PLL is selected as a system clock source the value for this bit
is always 1.
• Bit 0 – PLOCK: PLL Lock Detector
When the PLOCK bit is set, the PLL is locked to the reference clock, and it is safe to enable
CLKPLL for Fast Peripherals. After the PLL is enabled, it takes about 100 ms for the PLL to lock.
5.7
128 kHz Internal Oscillator
The 128 kHz internal Oscillator is a low power Oscillator providing a clock of 128 kHz. The frequency is nominal at 3V and 25° C. This clock is used by the Watchdog Oscillator.
5.8
External Clock
To drive the device from an external clock source, XTAL1 should be driven as shown in Figure
5-4. To run the device on an external clock, the CKSEL Fuses must be programmed to “0000”.
Figure 5-4.
External Clock Drive Configuration
NC
XTAL2
External
Clock
Signal
XTAL1
GND
Table 5-8.
36
External Clock Frequency
CKSEL3..0
Frequency Range
0000
0 - 16 MHz
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
When this clock source is selected, start-up times are determined by the SUT Fuses as shown in
Table 5-9.
Table 5-9.
Start-up Times for the External Clock Selection
SUT1..0
Start-up Time from
Power-down and Power-save
Additional Delay from
Reset (VCC = 5.0V)
00
6 CK
14CK
01
6 CK
14CK + 4.1 ms
Fast rising power
10
6 CK
14CK + 65 ms
Slowly rising power
11
Recommended Usage
BOD enabled
Reserved
When applying an external clock, it is required to avoid sudden changes in the applied clock frequency to ensure stable operation of the MCU. A variation in frequency of more than 2% from
one clock cycle to the next can lead to unpredictable behavior. It is required to ensure that the
MCU is kept in Reset during such changes in the clock frequency.
Note that the System Clock Prescaler can be used to implement run-time changes of the internal
clock frequency while still ensuring stable operation. Refer to “System Clock Prescaler” on page
37 for details.
5.9
Clock Output Buffer
When the CKOUT Fuse is programmed, the system Clock will be output on CLKO. This mode is
suitable when chip clock is used to drive other circuits on the system. The clock will be output
also during reset and the normal operation of I/O pin will be overridden when the fuse is programmed. Any clock source, including internal RC Oscillator, can be selected when CLKO
serves as clock output. If the System Clock Prescaler is used, it is the divided system clock that
is output (CKOUT Fuse programmed).
5.10
System Clock Prescaler
The ATmega16/32/64/M1/C1 system clock can be divided by setting the Clock Prescale Register – CLKPR. This feature can be used to decrease power consumption when the requirement
for processing power is low. This can be used with all clock source options, and it will affect the
clock frequency of the CPU and all synchronous peripherals. clkI/O, clkADC, clkCPU, and clkFLASH
are divided by a factor as shown in Table 5-10.
When switching between prescaler settings, the System Clock Prescaler ensures that no
glitches occurs in the clock system. It also ensures that no intermediate frequency is higher than
neither the clock frequency corresponding to the previous setting, nor the clock frequency corresponding to the new setting. The ripple counter that implements the prescaler runs at the
frequency of the undivided clock, which may be faster than the CPU's clock frequency. Hence, it
is not possible to determine the state of the prescaler - even if it were readable, and the exact
time it takes to switch from one clock division to the other cannot be exactly predicted. From the
time the CLKPS values are written, it takes between T1 + T2 and T1 + 2 * T2 before the new
clock frequency is active. In this interval, 2 active clock edges are produced. Here, T1 is the previous clock period, and T2 is the period corresponding to the new prescaler setting.
37
7647F–AVR–04/09
To avoid unintentional changes of clock frequency, a special write procedure must be followed
to change the CLKPS bits:
1. Write the Clock Prescaler Change Enable (CLKPCE) bit to one and all other bits in
CLKPR to zero.
2. Within four cycles, write the desired value to CLKPS while writing a zero to CLKPCE.
Interrupts must be disabled when changing prescaler setting to make sure the write procedure is
not interrupted.
5.10.1
Clock Prescaler Register – CLKPR
Bit
7
6
5
4
3
2
1
0
CLKPCE
–
–
–
CLKPS3
CLKPS2
CLKPS1
CLKPS0
Read/Write
R/W
R
R
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
CLKPR
See Bit Description
• Bit 7 – CLKPCE: Clock Prescaler Change Enable
The CLKPCE bit must be written to logic one to enable change of the CLKPS bits. The CLKPCE
bit is only updated when the other bits in CLKPR are simultaniosly written to zero. CLKPCE is
cleared by hardware four cycles after it is written or when CLKPS bits are written. Rewriting the
CLKPCE bit within this time-out period does neither extend the time-out period, nor clear the
CLKPCE bit.
• Bits 3..0 – CLKPS3..0: Clock Prescaler Select Bits 3 - 0
These bits define the division factor between the selected clock source and the internal system
clock. These bits can be written run-time to vary the clock frequency to suit the application
requirements. As the divider divides the master clock input to the MCU, the speed of all synchronous peripherals is reduced when a division factor is used. The division factors are given in
Table 5-10.
The CKDIV8 Fuse determines the initial value of the CLKPS bits. If CKDIV8 is unprogrammed,
the CLKPS bits will be reset to “0000”. If CKDIV8 is programmed, CLKPS bits are reset to
“0011”, giving a division factor of 8 at start up. This feature should be used if the selected clock
source has a higher frequency than the maximum frequency of the device at the present operating conditions. Note that any value can be written to the CLKPS bits regardless of the CKDIV8
Fuse setting. The Application software must ensure that a sufficient division factor is chosen if
the selcted clock source has a higher frequency than the maximum frequency of the device at
the present operating conditions. The device is shipped with the CKDIV8 Fuse programmed.
38
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 5-10.
Clock Prescaler Select
CLKPS3
CLKPS2
CLKPS1
CLKPS0
Clock Division Factor
0
0
0
0
1
0
0
0
1
2
0
0
1
0
4
0
0
1
1
8
0
1
0
0
16
0
1
0
1
32
0
1
1
0
64
0
1
1
1
128
1
0
0
0
256
1
0
0
1
Reserved
1
0
1
0
Reserved
1
0
1
1
Reserved
1
1
0
0
Reserved
1
1
0
1
Reserved
1
1
1
0
Reserved
1
1
1
1
Reserved
39
7647F–AVR–04/09
6. Power Management and Sleep Modes
Sleep modes enable the application to shut down unused modules in the MCU, thereby saving
power. The AVR provides various sleep modes allowing the user to tailor the power consumption to the application’s requirements.
To enter any of the five sleep modes, the SE bit in SMCR must be written to logic one and a
SLEEP instruction must be executed. The SM2, SM1, and SM0 bits in the SMCR Register select
which sleep mode (Idle, ADC Noise Reduction, Power-down, Power-save, or Standby) will be
activated by the SLEEP instruction. See Table 6-1 for a summary. If an enabled interrupt occurs
while the MCU is in a sleep mode, the MCU wakes up. The MCU is then halted for four cycles in
addition to the start-up time, executes the interrupt routine, and resumes execution from the
instruction following SLEEP. The contents of the register file and SRAM are unaltered when the
device wakes up from sleep. If a reset occurs during sleep mode, the MCU wakes up and executes from the Reset Vector.
Figure 5-1 on page 29 presents the different clock systems in the ATmega16/32/64/M1/C1, and
their distribution. The figure is helpful in selecting an appropriate sleep mode.
6.1
6.1.1
Sleep Mode Control Register
Sleep Mode Control Register – SMCR
The Sleep Mode Control Register contains control bits for power management.
Bit
7
6
5
4
3
2
1
0
–
–
–
–
SM2
SM1
SM0
SE
Read/Write
R
R
R
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
SMCR
• Bits 3..1 – SM2..0: Sleep Mode Select Bits 2, 1, and 0
These bits select between the five available sleep modes as shown in Table 6-1.
Table 6-1.
Sleep Mode Select
SM2
SM1
SM0
Sleep Mode
0
0
0
Idle
0
0
1
ADC Noise Reduction
0
1
0
Power-down
0
1
1
Reserved
1
0
0
Reserved
1
0
1
Reserved
1
1
0
Standby(1)
1
1
1
Reserved
Note: 1. Standby mode is only recommended for use with external crystals or resonators.
• Bit 1 – SE: Sleep Enable
The SE bit must be written to logic one to make the MCU enter the sleep mode when the SLEEP
instruction is executed. To avoid the MCU entering the sleep mode unless it is the programmer’s
purpose, it is recommended to write the Sleep Enable (SE) bit to one just before the execution of
the SLEEP instruction and to clear it immediately after waking up.
40
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
6.2
Idle Mode
When the SM2..0 bits are written to 000, the SLEEP instruction makes the MCU enter Idle
mode, stopping the CPU but allowing SPI, UART, Analog Comparator, ADC, Timer/Counters,
Watchdog, and the interrupt system to continue operating. This sleep mode basically halt clkCPU
and clkFLASH, while allowing the other clocks to run.
Idle mode enables the MCU to wake up from external triggered interrupts as well as internal
ones like the Timer Overflow and UART Transmit Complete interrupts. If wake-up from the Analog Comparator interrupt is not required, the Analog Comparator can be powered down by
setting the ACD bit in the Analog Comparator Control and Status Register – ACSR. This will
reduce power consumption in Idle mode. If the ADC is enabled, a conversion starts automatically when this mode is entered.
6.3
ADC Noise Reduction Mode
When the SM2..0 bits are written to 001, the SLEEP instruction makes the MCU enter ADC
Noise Reduction mode, stopping the CPU but allowing the ADC, the External Interrupts,
Timer/Counter (if their clock source is external - T0 or T1) and the Watchdog to continue
operating (if enabled). This sleep mode basically halts clkI/O, clkCPU, and clkFLASH, while allowing
the other clocks to run.
This improves the noise environment for the ADC, enabling higher resolution measurements. If
the ADC is enabled, a conversion starts automatically when this mode is entered. Apart from the
ADC Conversion Complete interrupt, only an External Reset, a Watchdog Reset, a Brown-out
Reset, a Timer/Counter interrupt, an SPM/EEPROM ready interrupt, an External Level Interrupt
on INT3:0 can wake up the MCU from ADC Noise Reduction mode.
6.4
Power-down Mode
When the SM2..0 bits are written to 010, the SLEEP instruction makes the MCU enter
Power-down mode. In this mode, the External Oscillator is stopped, while the External Interrupts
and the Watchdog continue operating (if enabled). Only an External Reset, a Watchdog Reset, a
Brown-out Reset, a PSC Interrupt, an External Level Interrupt on INT3:0 can wake up the MCU.
This sleep mode basically halts all generated clocks, allowing operation of asynchronous modules only.
Note that if a level triggered interrupt is used for wake-up from Power-down mode, the changed
level must be held for some time to wake up the MCU. Refer to “External Interrupts” on page 82
for details.
When waking up from Power-down mode, there is a delay from the wake-up condition occurs
until the wake-up becomes effective. This allows the clock to restart and become stable after
having been stopped. The wake-up period is defined by the same CKSEL fuses that define the
Reset Time-out period, as described in “Clock Sources” on page 30.
41
7647F–AVR–04/09
6.5
Standby Mode
When the SM2..0 bits are 110 and an external crystal/resonator clock option is selected, the
SLEEP instruction makes the MCU enter Standby mode. This mode is identical to Power-down
with the exception that the Oscillator is kept running. From Standby mode, the device wakes up
in six clock cycles.
Table 6-2.
Active Clock Domains and Wake-up Sources in the Different Sleep Modes.
Oscillator
s
clkADC
clkPLL
Main Clock
Source Enabled
INT3..0
PSC
SPM/EEPROM
Ready
ADC
WDT
OtherI/O
Idle
Wake-up Sources
clkIO
Sleep
Mode
clkFLASH
clkCPU
Active Clock Domains
X
X
X
X
X
X
X
X
X
X
X
X
X
X(2)
X
X
X
X
ADC
Noise
Reduction
Power-do
wn
X(2)
X
Standby(1)
X
X(2)
Notes: 1. Only recommended with external crystal or resonator selected as clock source.
2. Only level interrupt.
6.6
X
Power Reduction Register
The Power Reduction Register, PRR, provides a method to stop the clock to individual peripherals to reduce power consumption. The current state of the peripheral is frozen and the I/O
registers can not be read or written. Resources used by the peripheral when stopping the clock
will remain occupied, hence the peripheral should in most cases be disabled before stopping the
clock. Waking up a module, which is done by clearing the bit in PRR, puts the module in the
same state as before shutdown.
A full predictible behaviour of a peripheral is not guaranteed during and after a cycle of stopping
and starting of its clock. So its recommended to stop a peripheral before stopping its clock with
PRR register.
Module shutdown can be used in Idle mode and Active mode to significantly reduce the overall
power consumption. In all other sleep modes, the clock is already stopped.
42
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
6.6.1
Power Reduction Register - PRR
Bit
7
6
5
4
3
2
1
0
-
PRCAN
PRPSC
PRTIM1
PRTIM0
PRSPI
PRLIN
PRADC
Read/Write
R
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PRR
• Bit 7 - Res: Reserved Bit
This bit is unused bit in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 6 - PRCAN: Power Reduction CAN
Writing a logic one to this bit reduces the consumption of the CAN by stopping the clock to this
module. When waking up the CAN again, the CAN should be re initialized to ensure proper
operation.
• Bit 5 - PRPSC: Power Reduction PSC
Writing a logic one to this bit reduces the consumption of the PSC by stopping the clock to this
module. When waking up the PSC again, the PSC should be re initialized to ensure proper
operation.
• Bit 4 - PRTIM1: Power Reduction Timer/Counter1
Writing a logic one to this bit reduces the consumption of the Timer/Counter1 module. When the
Timer/Counter1 is enabled, operation will continue like before the setting of this bit.
• Bit 3 - PRTIM0: Power Reduction Timer/Counter0
Writing a logic one to this bit reduces the consumption of the Timer/Counter0 module. When the
Timer/Counter0 is enabled, operation will continue like before the setting of this bit.
• Bit 2 - PRSPI: Power Reduction Serial Peripheral Interface
Writing a logic one to this bit reduces the consumption of the Serial Peripheral Interface by stopping the clock to this module. When waking up the SPI again, the SPI should be re initialized to
ensure proper operation.
• Bit 1 - PRLIN: Power Reduction LIN
Writing a logic one to this bit reduces the consumption of the UART controller by stopping the
clock to this module. When waking up the UART controller again, the UART controller should be
re initialized to ensure proper operation.
• Bit 0 - PRADC: Power Reduction ADC
Writing a logic one to this bit reduces the consumption of the ADC by stopping the clock to this
module. The ADC must be disabled before using this function. The analog comparator cannot
use the ADC input MUX when the clock of ADC is stopped.
43
7647F–AVR–04/09
6.7
Minimizing Power Consumption
There are several issues to consider when trying to minimize the power consumption in an AVR
controlled system. In general, sleep modes should be used as much as possible, and the sleep
mode should be selected so that as few as possible of the device’s functions are operating. All
functions not needed should be disabled. In particular, the following modules may need special
consideration when trying to achieve the lowest possible power consumption.
6.7.1
Analog to Digital Converter
If enabled, the ADC will be enabled in all sleep modes. To save power, the ADC should be disabled before entering any sleep mode. When the ADC is turned off and on again, the
next conversion will be an extended conversion. Refer to “Analog to Digital Converter - ADC” on
page 230 for details on ADC operation.
6.7.2
Analog Comparator
When entering Idle mode, the Analog Comparator should be disabled if not used. When entering
ADC Noise Reduction mode, the Analog Comparator should be disabled. In other sleep modes,
the Analog Comparator is automatically disabled. However, if the Analog Comparator is set up
to use the Internal Voltage Reference as input, the Analog Comparator should be disabled in all
sleep modes. Otherwise, the Internal Voltage Reference will be enabled, independent of sleep
mode. Refer to “Analog Comparator” on page 262 for details on how to configure the Analog
Comparator.
6.7.3
Brown-out Detector
If the Brown-out Detector is not needed by the application, this module should be turned off. If
the Brown-out Detector is enabled by the BODLEVEL Fuses, it will be enabled in all sleep
modes, and hence, always consume power. In the deeper sleep modes, this will contribute significantly to the total current consumption. Refer to “Brown-out Detection” on page 49 for details
on how to configure the Brown-out Detector.
6.7.4
Internal Voltage Reference
The Internal Voltage Reference will be enabled when needed by the Brown-out Detection, the
Analog Comparator or the ADC. If these modules are disabled as described in the sections
above, the internal voltage reference will be disabled and it will not be consuming power. When
turned on again, the user must allow the reference to start up before the output is used. If the
reference is kept on in sleep mode, the output can be used immediately. Refer to “Internal Voltage Reference” on page 51 for details on the start-up time.
6.7.5
Watchdog Timer
If the Watchdog Timer is not needed in the application, the module should be turned off. If the
Watchdog Timer is enabled, it will be enabled in all sleep modes, and hence, always consume
power. In the deeper sleep modes, this will contribute significantly to the total current consumption. Refer to “Watchdog Timer” on page 52 for details on how to configure the Watchdog Timer.
44
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
6.7.6
Port Pins
When entering a sleep mode, all port pins should be configured to use minimum power. The
most important is then to ensure that no pins drive resistive loads. In sleep modes where both
the I/O clock (clkI/O) and the ADC clock (clkADC) are stopped, the input buffers of the device will
be disabled. This ensures that no power is consumed by the input logic when not needed. In
some cases, the input logic is needed for detecting wake-up conditions, and it will then be
enabled. Refer to the section “I/O-Ports” on page 62 for details on which pins are enabled. If the
input buffer is enabled and the input signal is left floating or have an analog signal level close to
VCC/2, the input buffer will use excessive power.
For analog input pins, the digital input buffer should be disabled at all times. An analog signal
level close to VCC/2 on an input pin can cause significant current even in active mode. Digital
input buffers can be disabled by writing to the Digital Input Disable Registers (DIDR1 and
DIDR0). Refer to “Digital Input Disable Register 1– DIDR1” and “Digital Input Disable Register 0
– DIDR0” on page 269 and page 249 for details.
6.7.7
On-chip Debug System
If the On-chip debug system is enabled by OCDEN Fuse and the chip enter sleep mode, the
main clock source is enabled, and hence, always consumes power. In the deeper sleep modes,
this will contribute significantly to the total current consumption.
45
7647F–AVR–04/09
7. System Control and Reset
7.1
Resetting the AVR
During reset, all I/O Registers are set to their initial values, and the program starts execution
from the Reset Vector. The instruction placed at the Reset Vector must be a JMP – Absolute
Jump – instruction to the reset handling routine. If the program never enables an interrupt
source, the Interrupt Vectors are not used, and regular program code can be placed at these
locations. This is also the case if the Reset Vector is in the Application section while the Interrupt
Vectors are in the Boot section or vice versa. The circuit diagram in Figure 7-1 on page 47
shows the reset logic. Table 7-1 on page 47 defines the electrical parameters of the reset
circuitry.
The I/O ports of the AVR are immediately reset to their initial state when a reset source goes
active. This does not require any clock source to be running.
After all reset sources have gone inactive, a delay counter is invoked, stretching the internal
reset. This allows the power to reach a stable level before normal operation starts. The time-out
period of the delay counter is defined by the user through the SUT and CKSEL Fuses. The different selections for the delay period are presented in “Clock Sources” on page 30.
7.2
Reset Sources
The ATmega16/32/64/M1/C1 has four sources of reset:
46
•
Power-on Reset. The MCU is reset when the supply voltage is below the Power-on Reset
threshold (VPOT).
•
External Reset. The MCU is reset when a low level is present on the RESET pin for longer
than the minimum pulse length.
•
Watchdog Reset. The MCU is reset when the Watchdog Timer period expires and the
Watchdog is enabled.
•
Brown-out Reset. The MCU is reset when the supply voltage VCC is below the Brown-out
Reset threshold (VBOT) and the Brown-out Detector is enabled.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 7-1.
Reset Logic
DATA BUS
PORF
BORF
EXTRF
WDRF
MCU Status
Register (MCUSR)
Power-on Reset
Circuit
Brown-out
Reset Circuit
BODLEVEL [2..0]
Pull-up Resistor
Spike
Filter
Watchdog
Oscillator
Clock
Generator
CK
Delay Counters
TIMEOUT
CKSEL[3:0]
SUT[1:0]
Table 7-1.
Symbol
VPOT
Parameter
Min
Typ
Max
Units
Power-on Reset Threshold Voltage (rising)
1.1
1.4
1.7
V
Power-on Reset Threshold Voltage (falling)(1)
0.8
0.9
1.6
V
0.4
V
VPORMAX
VCC Max. start voltage to ensure internal
Power-on Reset signal
VPORMIN
VCC Min. start voltage to ensure internal
Power-on Reset signal
-0.1
V
VCCRR
VCC Rise Rate to ensure Power-on Reset
0.01
V/ms
VRST
RESET Pin Threshold Voltage
Note:
7.2.1
Reset Characteristics
0.1 VCC
0.9VCC
V
1. Before rising, the supply has to be between VPORMIN and VPORMAX to ensure a Reset.
Power-on Reset
A Power-on Reset (POR) pulse is generated by an On-chip detection circuit. The detection level
is defined in Table 7-1. The POR is activated whenever VCC is below the detection level. The
POR circuit can be used to trigger the start-up Reset, as well as to detect a failure in supply
voltage.
A Power-on Reset (POR) circuit ensures that the device is reset from Power-on. Reaching the
Power-on Reset threshold voltage invokes the delay counter, which determines how long the
device is kept in RESET after VCC rise. The RESET signal is activated again, without any delay,
when VCC decreases below the detection level.
47
7647F–AVR–04/09
Figure 7-2.
MCU Start-up, RESET Tied to VCC
V CCRR
VCC
VPORMAX
VPORMIN
RESET
VRST
tTOUT
TIME-OUT
INTERNAL
RESET
Figure 7-3.
MCU Start-up, RESET Extended Externally
VCC
VPOT
RESET
TIME-OUT
VRST
tTOUT
INTERNAL
RESET
7.2.2
External Reset
An External Reset is generated by a low level on the RESET pin. Reset pulses longer than the
minimum pulse width (see Table 7-1) will generate a reset, even if the clock is not running.
Shorter pulses are not guaranteed to generate a reset. When the applied signal reaches the
Reset Threshold Voltage – VRST – on its positive edge, the delay counter starts the MCU after
the Time-out period – tTOUT – has expired.
Figure 7-4.
External Reset During Operation
CC
48
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
7.2.3
Brown-out Detection
ATmega16/32/64/M1/C1 has an On-chip Brown-out Detection (BOD) circuit for monitoring the
VCC level during operation by comparing it to a fixed trigger level. The trigger level for the BOD
can be selected by the BODLEVEL Fuses. The trigger level has a hysteresis to ensure spike
free Brown-out Detection. The hysteresis on the detection level should be interpreted as VBOT+ =
VBOT + VHYST/2 and VBOT- = VBOT - VHYST/2.
Table 7-2.
Notes:
BODLEVEL Fuse Coding(1)(2)
BODLEVEL 2..0 Fuses
Typ VBOT
Units
111
Disabled
110
4.5
V
011
4.4
V
100
4.3
V
010
4.2
V
001
2.8
V
101
2.7
V
000
2.6
V
1. VBOT may be below nominal minimum operating voltage for some devices. For devices where
this is the case, the device is tested down to VCC = VBOT during the production test. This guarantees that a Brown-Out Reset will occur before VCC drops to a voltage where correct
operation of the microcontroller is no longer guaranteed. The test is performed using
BODLEVEL = 010 for Low Operating Voltage and BODLEVEL = 101 for High Operating Voltage .
2. Values are guidelines only.
Table 7-3.
Brown-out Characteristics(1)
Symbol
Parameter
VHYST
Brown-out Detector Hysteresis
80
mV
tBOD
Min Pulse Width on Brown-out Reset
2
µs
Notes:
Min.
Typ.
Max.
Units
1. Values are guidelines only.
When the BOD is enabled, and VCC decreases to a value below the trigger level (VBOT- in Figure
7-5 on page 50), the Brown-out Reset is immediately activated. When VCC increases above the
trigger level (V BOT+ in Figure 7-5 on page 50), the delay counter starts the MCU after the
Time-out period tTOUT has expired.
The BOD circuit will only detect a drop in VCC if the voltage stays below the trigger level for longer than tBOD given in Table 7-3.
49
7647F–AVR–04/09
Figure 7-5.
Brown-out Reset During Operation
VCC
VBOT+
VBOT-
RESET
tTOUT
TIME-OUT
INTERNAL
RESET
7.2.4
Watchdog Reset
When the Watchdog times out, it will generate a short reset pulse of one CK cycle duration. On
the falling edge of this pulse, the delay timer starts counting the Time-out period tTOUT. Refer to
page 52 for details on operation of the Watchdog Timer.
Figure 7-6.
Watchdog Reset During Operation
CC
CK
7.2.5
MCU Status Register – MCUSR
The MCU Status Register provides information on which reset source caused an MCU reset.
Bit
7
6
5
4
3
2
1
0
–
–
–
–
WDRF
BORF
EXTRF
PORF
Read/Write
R
R
R
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
MCUSR
See Bit Description
• Bit 3 – WDRF: Watchdog Reset Flag
This bit is set if a Watchdog Reset occurs. The bit is reset by a Power-on Reset, or by writing a
logic zero to the flag.
• Bit 2 – BORF: Brown-out Reset Flag
This bit is set if a Brown-out Reset occurs. The bit is reset by a Power-on Reset, or by writing a
logic zero to the flag.
50
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 1 – EXTRF: External Reset Flag
This bit is set if an External Reset occurs. The bit is reset by a Power-on Reset, or by writing a
logic zero to the flag.
• Bit 0 – PORF: Power-on Reset Flag
This bit is set if a Power-on Reset occurs. The bit is reset only by writing a logic zero to the flag.
To make use of the Reset flags to identify a reset condition, the user should read and then reset
the MCUSR as early as possible in the program. If the register is cleared before another reset
occurs, the source of the reset can be found by examining the reset flags.
7.3
Internal Voltage Reference
ATmega16/32/64/M1/C1 features an internal bandgap reference. This reference is used for
Brown-out DetectionDetection, and it can be used as an input to the Analog Comparators or the
ADC. The VREF 2.56V reference to the ADC, DAC or Analog Comparators is generated from the
internal bandgap reference.
7.3.1
Voltage Reference Enable Signals and Start-up Time
The voltage reference has a start-up time that may influence the way it should be used. The
start-up time is given in Table 7-4. To save power, the reference is not always turned on. The
reference is on during the following situations:
1. When the BOD is enabled (by programming the BODLEVEL [2..0] Fuse).
2. When the bandgap reference is connected to the Analog Comparator (by setting the
ACBG bit in ACSR).
3. When the ADC is enabled.
4. When the DAC is enabled.
Thus, when the BOD is not enabled, after setting the ACBG bit or enabling the ADC or the DAC,
the user must always allow the reference to start up before the output from the Analog Comparator or ADC or DAC is used. To reduce power consumption in Power-down mode, the user can
avoid the three conditions above to ensure that the reference is turned off before entering
Power-down mode.
7.3.2
Voltage Reference Characteristics
Table 7-4.
Symbol
Internal Voltage Reference Characteristics(1)
Parameter
Condition
Min.
Typ.
Max.
Units
VBG
Bandgap reference voltage
1.1
V
tBG
Bandgap reference start-up time
40
µs
IBG
Bandgap reference current
consumption
15
µA
Note:
1. Values are guidelines only.
51
7647F–AVR–04/09
7.4
Watchdog Timer
ATmega16/32/64/M1/C1 has an Enhanced Watchdog Timer (WDT). The main features are:
• Clocked from separate On-chip Oscillator
• 3 Operating modes
– Interrupt
– System Reset
– Interrupt and System Reset
• Selectable Time-out period from 16ms to 8s
• Possible Hardware fuse Watchdog always on (WDTON) for fail-safe mode
Figure 7-7.
Watchdog Timer
OSC/8K
OSC/2K
OSC/4K
128 KHz
OSCILLATOR
WDP3
MCU RESET
WDIF
INTERRUPT
WDIE
The Watchdog Timer (WDT) is a timer counting cycles of a separate on-chip 128 kHz oscillator.
The WDT gives an interrupt or a system reset when the counter reaches a given time-out value.
In normal operation mode, it is required that the system uses the WDR - Watchdog Timer Reset
- instruction to restart the counter before the time-out value is reached. If the system doesn't
restart the counter, an interrupt or system reset will be issued.
In Interrupt mode, the WDT gives an interrupt when the timer expires. This interrupt can be used
to wake the device from sleep-modes, and also as a general system timer. One example is to
limit the maximum time allowed for certain operations, giving an interrupt when the operation
has run longer than expected. In System Reset mode, the WDT gives a reset when the timer
expires. This is typically used to prevent system hang-up in case of runaway code. The third
mode, Interrupt and System Reset mode, combines the other two modes by first giving an interrupt and then switch to System Reset mode. This mode will for instance allow a safe shutdown
by saving critical parameters before a system reset.
The “Watchdog Timer Always On” (WDTON) fuse, if programmed, will force the Watchdog Timer
to System Reset mode. With the fuse programmed the System Reset mode bit (WDE) and Interrupt mode bit (WDIE) are locked to 1 and 0 respectively. To further ensure program security,
alterations to the Watchdog set-up must follow timed sequences. The sequence for clearing
WDE and changing time-out configuration is as follows:
1. In the same operation, write a logic one to the Watchdog change enable bit (WDCE) and
WDE. A logic one must be written to WDE regardless of the previous value of the WDE
bit.
2. Within the next four clock cycles, write the WDE and Watchdog prescaler bits (WDP) as
desired, but with the WDCE bit cleared. This must be done in one operation.
52
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The following code example shows one assembly and one C function for turning off the Watchdog Timer. The example assumes that interrupts are controlled (e.g. by disabling interrupts
globally) so that no interrupts will occur during the execution of these functions.
Assembly Code Example(1)
WDT_off:
; Turn off global interrupt
cli
; Reset Watchdog Timer
wdr
; Clear WDRF in MCUSR
in
r16, MCUSR
andi
r16, (0xff & (0<<WDRF))
out
MCUSR, r16
; Write logical one to WDCE and WDE
; Keep old prescaler setting to prevent unintentional time-out
lds r16, WDTCSR
ori
r16, (1<<WDCE) | (1<<WDE)
sts WDTCSR, r16
; Turn off WDT
ldi
r16, (0<<WDE)
sts WDTCSR, r16
; Turn on global interrupt
sei
ret
C Code Example(1)
void WDT_off(void)
{
__disable_interrupt();
__watchdog_reset();
/* Clear WDRF in MCUSR */
MCUSR &= ~(1<<WDRF);
/* Write logical one to WDCE and WDE */
/* Keep old prescaler setting to prevent unintentional time-out */
WDTCSR |= (1<<WDCE) | (1<<WDE);
/* Turn off WDT */
WDTCSR = 0x00;
__enable_interrupt();
}
Note:
1. The example code assumes that the part specific header file is included.
Note: If the Watchdog is accidentally enabled, for example by a runaway pointer or brown-out
condition, the device will be reset and the Watchdog Timer will stay enabled. If the code is not
set up to handle the Watchdog, this might lead to an eternal loop of time-out resets. To avoid this
situation, the application software should always clear the Watchdog System Reset Flag
(WDRF) and the WDE control bit in the initialisation routine, even if the Watchdog is not in use.
53
7647F–AVR–04/09
The following code example shows one assembly and one C function for changing the time-out
value of the Watchdog Timer.
Assembly Code Example(1)
WDT_Prescaler_Change:
; Turn off global interrupt
cli
; Reset Watchdog Timer
wdr
; Start timed sequence
lds r16, WDTCSR
r16, (1<<WDCE) | (1<<WDE)
ori
sts WDTCSR, r16
; --
Got four cycles to set the new values from here -
; Set new prescaler(time-out) value = 64K cycles (~0.5 s)
r16, (1<<WDE) | (1<<WDP2) | (1<<WDP0)
ldi
sts WDTCSR, r16
; --
Finished setting new values, used 2 cycles -
; Turn on global interrupt
sei
ret
C Code Example(1)
void WDT_Prescaler_Change(void)
{
__disable_interrupt();
__watchdog_reset();
/* Start timed
equence */
WDTCSR |= (1<<WDCE) | (1<<WDE);
/* Set new prescaler(time-out) value = 64K cycles (~0.5 s) */
WDTCSR
= (1<<WDE) | (1<<WDP2) | (1<<WDP0);
__enable_interrupt();
}
Note:
1. The example code assumes that the part specific header file is included.
Note: The Watchdog Timer should be reset before any change of the WDP bits, since a change
in the WDP bits can result in a time-out when switching to a shorter time-out period;
54
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
7.4.1
Watchdog Timer Control Register - WDTCSR
Bit
7
6
5
4
3
2
1
0
WDIF
WDIE
WDP3
WDCE
WDE
WDP2
WDP1
WDP0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
X
0
0
0
WDTCSR
• Bit 7 - WDIF: Watchdog Interrupt Flag
This bit is set when a time-out occurs in the Watchdog Timer and the Watchdog Timer is configured for interrupt. WDIF is cleared by hardware when executing the corresponding interrupt
handling vector. Alternatively, WDIF is cleared by writing a logic one to the flag. When the I-bit in
SREG and WDIE are set, the Watchdog Time-out Interrupt is executed.
• Bit 6 - WDIE: Watchdog Interrupt Enable
When this bit is written to one and the I-bit in the Status Register is set, the Watchdog Interrupt is
enabled. If WDE is cleared in combination with this setting, the Watchdog Timer is in Interrupt
Mode, and the corresponding interrupt is executed if time-out in the Watchdog Timer occurs.
If WDE is set, the Watchdog Timer is in Interrupt and System Reset Mode. The first time-out in
the Watchdog Timer will set WDIF. Executing the corresponding interrupt vector will clear WDIE
and WDIF automatically by hardware (the Watchdog goes to System Reset Mode). This is useful for keeping the Watchdog Timer security while using the interrupt. To stay in Interrupt and
System Reset Mode, WDIE must be set after each interrupt. This should however not be done
within the interrupt service routine itself, as this might compromise the safety-function of the
Watchdog System Reset mode. If the interrupt is not executed before the next time-out, a System Reset will be applied.
Table 7-5.
WDTON
Note:
(1)
Watchdog Timer Configuration
WDE
WDIE
Mode
Action on Time-out
0
0
0
Stopped
None
0
0
1
Interrupt Mode
Interrupt
0
1
0
System Reset Mode
Reset
0
1
1
Interrupt and System Reset
Mode
Interrupt, then go to System
Reset Mode
1
x
x
System Reset Mode
Reset
1. For the WDTON Fuse “1” means unprogrammed while “0” means programmed.
• Bit 4 - WDCE: Watchdog Change Enable
This bit is used in timed sequences for changing WDE and prescaler bits. To clear the WDE bit,
and/or change the prescaler bits, WDCE must be set.
Once written to one, hardware will clear WDCE after four clock cycles.
• Bit 3 - WDE: Watchdog System Reset Enable
WDE is overridden by WDRF in MCUSR. This means that WDE is always set when WDRF is
set. To clear WDE, WDRF must be cleared first. This feature ensures multiple resets during conditions causing failure, and a safe start-up after the failure.
• Bit 5, 2..0 - WDP3..0: Watchdog Timer Prescaler 3, 2, 1 and 0
The WDP3..0 bits determine the Watchdog Timer prescaling when the Watchdog Timer is running. The different prescaling values and their corresponding time-out periods are shown in
Table 7-6 on page 56.
55
7647F–AVR–04/09
.
Table 7-6.
Watchdog Timer Prescale Select
WDP3
WDP2
WDP1
WDP0
Number of WDT Oscillator
Cycles
Typical Time-out at
VCC = 5.0V
0
0
0
0
2K (2048) cycles
16 ms
0
0
0
1
4K (4096) cycles
32 ms
0
0
1
0
8K (8192) cycles
64 ms
0
0
1
1
16K (16384) cycles
0.125 s
0
1
0
0
32K (32768) cycles
0.25 s
0
1
0
1
64K (65536) cycles
0.5 s
0
1
1
0
128K (131072) cycles
1.0 s
0
1
1
1
256K (262144) cycles
2.0 s
1
0
0
0
512K (524288) cycles
4.0 s
1
0
0
1
1024K (1048576) cycles
8.0 s
1
0
1
0
1
0
1
1
1
1
0
0
1
1
0
1
1
1
1
0
1
1
1
1
Reserved
56
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
8. Interrupts
This section describes the specifics of the interrupt handling as performed in
ATmega16/32/64/M1/C1. For a general explanation of the AVR interrupt handling, refer to
“Reset and Interrupt Handling” on page 17.
8.1
Interrupt Vectors in ATmega16/32/64/M1/C1
Table 8-1.
Reset and Interrupt Vectors
Vector
No.
Program
Address
1
0x0000
2
0x0002
ANACOMP 0
Analog Comparator 0
3
0x0004
ANACOMP 1
Analog Comparator 1
4
0x0006
ANACOMP 2
Analog Comparator 2
5
0x0008
ANACOMP 3
Analog Comparator 3
6
0x000A
Source
Interrupt Definition
RESET
PSC FAULT
(3)
(3)
External Pin, Power-on Reset, Brown-out Reset,
Watchdog Reset, and Emulation AVR Reset
PSC Fault
PSC End of Cycle
7
0x000C
PSC EC
8
0x000E
INT0
External Interrupt Request 0
9
0x0010
INT1
External Interrupt Request 1
10
0x0012
INT2
External Interrupt Request 2
11
0x0014
INT3
External Interrupt Request 3
12
0x0016
TIMER1 CAPT
Timer/Counter1 Capture Event
13
0x0018
TIMER1 COMPA
Timer/Counter1 Compare Match A
14
0x001A
TIMER1 COMPB
Timer/Counter1 Compare Match B
15
0x001C
TIMER1 OVF
Timer/Counter1 Overflow
16
0x001E
TIMER0 COMPA
Timer/Counter0 Compare Match A
17
0x0020
TIMER0 COMPB
Timer/Counter0 Compare Match B
18
0x0022
TIMER0 OVF
Timer/Counter0 Overflow
19
0x0024
CAN INT
CAN MOB, Burst, General Errors
20
0x0026
CAN TOVF
CAN Timer Overflow
21
0x0028
LIN TC
LIN Transfer Complete
22
0x002A
LIN ERR
LIN Error
23
0x002C
PCINT0
Pin Change Interrupt Request 0
24
0x002E
PCINT1
Pin Change Interrupt Request 1
25
0x0030
PCINT2
Pin Change Interrupt Request 2
26
0x0032
PCINT3
Pin Change Interrupt Request 3
27
0x0034
SPI, STC
SPI Serial Transfer Complete
28
0x0036
ADC
ADC Conversion Complete
29
0x0038
WDT
Watchdog Time-Out Interrupt
30
0x003A
EE READY
EEPROM Ready
31
0x003C
SPM READY
Store Program Memory Ready
57
7647F–AVR–04/09
Notes:
1. When the BOOTRST Fuse is programmed, the device will jump to the Boot Loader address at
reset,
see
“Boot
Loader
Support
–
Read-While-Write
Self-Programming
ATmega16/32/64/M1/C1” on page 279.
2. When the IVSEL bit in MCUCR is set, Interrupt Vectors will be moved to the start of the Boot
Flash Section. The address of each Interrupt Vector will then be the address in this table
added to the start address of the Boot Flash Section.
3. These vectors are not used by ATmega32/64C1.
Table 8-2 shows reset and Interrupt Vectors placement for the various combinations of
BOOTRST and IVSEL settings. If the program never enables an interrupt source, the Interrupt
Vectors are not used, and regular program code can be placed at these locations. This is also
the case if the Reset Vector is in the Application section while the Interrupt Vectors are in the
Boot section or vice versa.
Table 8-2.
Reset and Interrupt Vectors Placement in ATmega16/32/64/M1/C1(1)
BOOTRST
IVSEL
1
Note:
Reset Address
Interrupt Vectors Start Address
0
0x000
0x001
1
1
0x000
Boot Reset Address + 0x002
0
0
Boot Reset Address
0x001
0
1
Boot Reset Address
Boot Reset Address + 0x002
1. The Boot Reset Address is shown in Table 24-4 on page 283. For the BOOTRST Fuse “1”
means unprogrammed while “0” means programmed.
The most typical and general program setup for the Reset and Interrupt Vector Addresses in
ATmega16/32/64/M1/C1 is:
Address Labels Code
58
Comments
0x000
jmp
RESET
; Reset Handler
0x002
jmp
ANA_COMP_0
; Analog Comparator 0 Handler
0x004
jmp
ANA_COMP_1
; Analog Comparator 1 Handler
0x006
jmp
ANA_COMP_2
; Analog Comparator 2 Handler
0x008
jmp
ANA_COMP_3
; Analog Comparator 3 Handler
0x00A
jmp
PSC_FAULT
; PSC Fault Handler
0x00C
jmp
PSC_EC
; PSC End of Cycle Handler
0x00E
jmp
EXT_INT0
; IRQ0 Handler
0x010
jmp
EXT_INT1
; IRQ1 Handler
0x012
jmp
EXT_INT2
; IRQ2 Handler
0x014
jmp
EXT_INT3
; IRQ3 Handler
0x016
jmp
TIM1_CAPT
; Timer1 Capture Handler
0x018
jmp
TIM1_COMPA
; Timer1 Compare A Handler
0x01A
jmp
TIM1_COMPB
; Timer1 Compare B Handler
0x01C
jmp
TIM1_OVF
; Timer1 Overflow Handler
0x01E
jmp
TIM0_COMPA
; Timer0 Compare A Handler
0x020
jmp
TIM0_COMPB
; Timer0 Compare B Handler
0x022
jmp
TIM0_OVF
; Timer0 Overflow Handler
0x024
jmp
CAN_INT
; CAN MOB,Burst,General Errors Handler
0x026
jmp
CAN_TOVF
; CAN Timer Overflow Handler
0x028
jmp
LIN_TC
; LIN Transfer Complete Handler
0x02A
jmp
LIN_ERR
; LIN Error Handler
0x02C
jmp
PCINT0
; Pin Change Int Request 0 Handler
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
0x02E
jmp
PCINT1
; Pin Change Int Request 1 Handler
0x030
jmp
PCINT2
; Pin Change Int Request 2 Handler
0x032
jmp
PCINT3
; Pin Change Int Request 3 Handler
0x034
jmp
SPI_STC
; SPI Transfer Complete Handler
0x036
jmp
ADC
; ADC Conversion Complete Handler
0x038
jmp
WDT
; Watchdog Timer Handler
0x03A
jmp
EE_RDY
; EEPROM Ready Handler
0x03C
jmp
SPM_RDY
; Store Program Memory Ready Handler
0x03ERESET:
ldi
r16, high(RAMEND); Main program start
0x03F
out
SPH,r16
;
0x040
ldi
0x041
0x042
out
sei
0x043
...
r16, low(RAMEND)
SPL,r16
; Enable interrupts
<instr>
...
...
; Set Stack Pointer to top of RAM
xxx
...
When the BOOTRST Fuse is unprogrammed, the Boot section size set to 2K bytes and the
IVSEL bit in the MCUCR Register is set before any interrupts are enabled, the most typical and
general program setup for the Reset and Interrupt Vector Addresses in ATmega16/32/64/M1/C1
is:
Address Labels Code
Comments
0x000
RESET: ldi
0x001
out
r16,high(RAMEND); Main program start
SPH,r16
0x002
ldi
r16,low(RAMEND)
0x003
0x004
out
sei
SPL,r16
0x005
<instr>
; Set Stack Pointer to top of RAM
; Enable interrupts
xxx
;
.org 0xC02
0xC02
jmp
ANA_COMP_0
; Analog Comparator 0 Handler
0xC04
jmp
ANA_COMP_1
; Analog Comparator 1 Handler
...
...
...
;
0xC3C
jmp
SPM_RDY
; Store Program Memory Ready Handler
When the BOOTRST Fuse is programmed and the Boot section size set to 2K bytes, the most
typical and general program setup for the Reset and Interrupt Vector Addresses in
ATmega16/32/64/M1/C1 is:
Address Labels Code
Comments
.org 0x002
0x002
jmp
ANA_COMP_0
; Analog Comparator 0 Handler
0x004
jmp
ANA_COMP_1
; Analog Comparator 1 Handler
...
...
...
;
0x03C
jmp
SPM_RDY
; Store Program Memory Ready Handler
;
.org 0xC00
0xC00
RESET: ldi
r16,high(RAMEND); Main program start
0xC01
out
SPH,r16
0xC02
ldi
r16,low(RAMEND)
; Set Stack Pointer to top of RAM
59
7647F–AVR–04/09
0xC03
0xC04
out
sei
SPL,r16
0xC05
<instr>
; Enable interrupts
xxx
When the BOOTRST Fuse is programmed, the Boot section size set to 2K bytes and the IVSEL
bit in the MCUCR Register is set before any interrupts are enabled, the most typical and general
program setup for the Reset and Interrupt Vector Addresses in ATmega16/32/64/M1/C116/32 is:
Address Labels Code
Comments
;
.org 0xC00
0xC00
jmp
RESET
; Reset handler
0xC02
jmp
ANA_COMP_0
; Analog Comparator 0 Handler
0xC04
jmp
ANA_COMP_1
; Analog Comparator 1 Handler
...
...
...
;
0xC3C
jmp
SPM_RDY
; Store Program Memory Ready Handler
;
8.1.1
0xC3E
RESET: ldi
r16,high(RAMEND); Main program start
0xC3F
out
SPH,r16
0xC40
ldi
r16,low(RAMEND)
0xC41
0xC42
out
sei
SPL,r16
0xC43
<instr>
; Set Stack Pointer to top of RAM
; Enable interrupts
xxx
Moving Interrupts Between Application and Boot Space
The MCU Control Register controls the placement of the Interrupt Vector table.
8.1.2
MCU Control Register – MCUCR
Bit
7
6
5
4
3
2
1
0
SPIPS
–
–
PUD
–
–
IVSEL
IVCE
Read/Write
R/W
R
R
R/W
R
R
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
MCUCR
• Bit 1 – IVSEL: Interrupt Vector Select
When the IVSEL bit is cleared (zero), the Interrupt Vectors are placed at the start of the Flash
memory. When this bit is set (one), the Interrupt Vectors are moved to the beginning of the Boot
Loader section of the Flash. The actual address of the start of the Boot Flash Section is determined by the BOOTSZ Fuses. Refer to the section “Boot Loader Support – Read-While-Write
Self-Programming ATmega16/32/64/M1/C1” on page 279 for details. To avoid unintentional
changes of Interrupt Vector tables, a special write procedure must be followed to change the
IVSEL bit:
1. Write the Interrupt Vector Change Enable (IVCE) bit to one.
2. Within four cycles, write the desired value to IVSEL while writing a zero to IVCE.
Interrupts will automatically be disabled while this sequence is executed. Interrupts are disabled
in the cycle IVCE is set, and they remain disabled until after the instruction following the write to
IVSEL. If IVSEL is not written, interrupts remain disabled for four cycles. The I-bit in the Status
Register is unaffected by the automatic disabling.
60
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Note:
If Interrupt Vectors are placed in the Boot Loader section and Boot Lock bit BLB02 is programmed,
interrupts are disabled while executing from the Application section. If Interrupt Vectors are placed
in the Application section and Boot Lock bit BLB12 is programed, interrupts are disabled while
executing from the Boot Loader section. Refer to the section “Boot Loader Support –
Read-While-Write Self-Programming ATmega16/32/64/M1/C1” on page 279 for details on Boot
Lock bits.
• Bit 0 – IVCE: Interrupt Vector Change Enable
The IVCE bit must be written to logic one to enable change of the IVSEL bit. IVCE is cleared by
hardware four cycles after it is written or when IVSEL is written. Setting the IVCE bit will disable
interrupts, as explained in the IVSEL description above. See Code Example below.
Assembly Code Example
Move_interrupts:
; Enable change of Interrupt Vectors
ldi r16, (1<<IVCE)
out MCUCR, r16
; Move interrupts to Boot Flash section
ldi r16, (1<<IVSEL)
out MCUCR, r16
ret
C Code Example
void Move_interrupts(void)
{
/* Enable change of Interrupt Vectors */
MCUCR = (1<<IVCE);
/* Move interrupts to Boot Flash section */
MCUCR = (1<<IVSEL);
}
61
7647F–AVR–04/09
9. I/O-Ports
9.1
Introduction
All AVR ports have true Read-Modify-Write functionality when used as general digital I/O ports.
This means that the direction of one port pin can be changed without unintentionally changing
the direction of any other pin with the SBI and CBI instructions. The same applies when changing drive value (if configured as output) or enabling/disabling of pull-up resistors (if configured as
input). Each output buffer has symmetrical drive characteristics with both high sink and source
capability. All port pins have individually selectable pull-up resistors with a supply-voltage invariant resistance. All I/O pins have protection diodes to both VCC and Ground as indicated in Figure
9-1. Refer to “Electrical Characteristics” on page 317 for a complete list of parameters.
Figure 9-1.
I/O Pin Equivalent Schematic
Rpu
Pxn
Logic
Cpin
See Figure
"General Digital I/O" for
Details
All registers and bit references in this section are written in general form. A lower case “x” represents the numbering letter for the port, and a lower case “n” represents the bit number. However,
when using the register or bit defines in a program, the precise form must be used. For example,
PORTB3 for bit no. 3 in Port B, here documented generally as PORTxn. The physical I/O Registers and bit locations are listed in “Register Description for I/O-Ports”.
Three I/O memory address locations are allocated for each port, one each for the Data Register
– PORTx, Data Direction Register – DDRx, and the Port Input Pins – PINx. The Port Input Pins
I/O location is read only, while the Data Register and the Data Direction Register are read/write.
However, writing a logic one to a bit in the PINx Register, will result in a toggle in the corresponding bit in the Data Register. In addition, the Pull-up Disable – PUD bit in MCUCR disables the
pull-up function for all pins in all ports when set.
Using the I/O port as General Digital I/O is described in “Ports as General Digital I/O”. Most port
pins are multiplexed with alternate functions for the peripheral features on the device. How each
alternate function interferes with the port pin is described in “Alternate Port Functions” on page
67. Refer to the individual module sections for a full description of the alternate functions.
Note that enabling the alternate function of some of the port pins does not affect the use of the
other pins in the port as general digital I/O.
62
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
9.2
Ports as General Digital I/O
The ports are bi-directional I/O ports with optional internal pull-ups. Figure 9-2 shows a functional description of one I/O-port pin, here generically called Pxn.
Figure 9-2.
General Digital I/O(1)
PUD
Q
D
DDxn
Q CLR
WDx
RESET
1
Q
Pxn
D
0
PORTxn
Q CLR
WPx
DATA BUS
RDx
RESET
WRx
RRx
SLEEP
SYNCHRONIZER
D
Q
L
Q
D
RPx
Q
PINxn
Q
clk I/O
PUD: PULLUP DISABLE
SLEEP: SLEEP CONTROL
clkI/O : I/O CLOCK
Note:
9.2.1
WDx:
RDx:
WRx:
RRx:
RPx:
WPx:
WRITE DDRx
READ DDRx
WRITE PORTx
READ PORTx REGISTER
READ PORTx PIN
WRITE PINx REGISTER
1. WRx, WPx, WDx, RRx, RPx, and RDx are common to all pins within the same port. clkI/O,
SLEEP, and PUD are common to all ports.
Configuring the Pin
Each port pin consists of three register bits: DDxn, PORTxn, and PINxn. As shown in “Register
Description for I/O-Ports” on page 80, the DDxn bits are accessed at the DDRx I/O address, the
PORTxn bits at the PORTx I/O address, and the PINxn bits at the PINx I/O address.
The DDxn bit in the DDRx Register selects the direction of this pin. If DDxn is written logic one,
Pxn is configured as an output pin. If DDxn is written logic zero, Pxn is configured as an input
pin.
If PORTxn is written logic one when the pin is configured as an input pin, the pull-up resistor is
activated. To switch the pull-up resistor off, PORTxn has to be written logic zero or the pin has to
be configured as an output pin
The port pins are tri-stated when reset condition becomes active, even if no clocks are running.
63
7647F–AVR–04/09
If PORTxn is written logic one when the pin is configured as an output pin, the port pin is driven
high (one). If PORTxn is written logic zero when the pin is configured as an output pin, the port
pin is driven low (zero).
9.2.2
Toggling the Pin
Writing a logic one to PINxn toggles the value of PORTxn, independent on the value of DDRxn.
Note that the SBI instruction can be used to toggle one single bit in a port.
9.2.3
Switching Between Input and Output
When switching between tri-state ({DDxn, PORTxn} = 0b00) and output high ({DDxn, PORTxn}
= 0b11), an intermediate state with either pull-up enabled {DDxn, PORTxn} = 0b01) or output
low ({DDxn, PORTxn} = 0b10) must occur. Normally, the pull-up enabled state is fully acceptable, as a high-impedant environment will not notice the difference between a strong high driver
and a pull-up. If this is not the case, the PUD bit in the MCUCR Register can be set to disable all
pull-ups in all ports.
Switching between input with pull-up and output low generates the same problem. The user
must use either the tri-state ({DDxn, PORTxn} = 0b00) or the output high state ({DDxn, PORTxn}
= 0b11) as an intermediate step.
Table 9-1 summarizes the control signals for the pin value.
Table 9-1.
Port Pin Configurations
9.2.4
DDxn
PORTxn
PUD
(in MCUCR)
I/O
Pull-up
0
0
X
Input
No
Default configuration after Reset.
Tri-state (Hi-Z)
0
1
0
Input
Yes
Pxn will source current if ext. pulled low.
0
1
1
Input
No
Tri-state (Hi-Z)
1
0
X
Output
No
Output Low (Sink)
1
1
X
Output
No
Output High (Source)
Comment
Reading the Pin Value
Independent of the setting of Data Direction bit DDxn, the port pin can be read through the
PINxn Register bit. As shown in Figure 9-2, the PINxn Register bit and the preceding latch constitute a synchronizer. This is needed to avoid metastability if the physical pin changes value
near the edge of the internal clock, but it also introduces a delay. Figure 9-3 shows a timing diagram of the synchronization when reading an externally applied pin value. The maximum and
minimum propagation delays are denoted tpd,max and tpd,min respectively.
64
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 9-3.
Synchronization when Reading an Externally Applied Pin value
SYSTEM CLK
INSTRUCTIONS
XXX
XXX
in r17, PINx
SYNC LATCH
PINxn
r17
0x00
0xFF
t pd, max
t pd, min
Consider the clock period starting shortly after the first falling edge of the system clock. The latch
is closed when the clock is low, and goes transparent when the clock is high, as indicated by the
shaded region of the “SYNC LATCH” signal. The signal value is latched when the system clock
goes low. It is clocked into the PINxn Register at the succeeding positive clock edge. As indicated by the two arrows tpd,max and tpd,min, a single signal transition on the pin will be delayed
between ½ and 1½ system clock period depending upon the time of assertion.
When reading back a software assigned pin value, a nop instruction must be inserted as indicated in Figure 9-4. The out instruction sets the “SYNC LATCH” signal at the positive edge of
the clock. In this case, the delay tpd through the synchronizer is 1 system clock period.
Figure 9-4.
Synchronization when Reading a Software Assigned Pin Value
SYSTEM CLK
r16
INSTRUCTIONS
0xFF
out PORTx, r16
nop
in r17, PINx
SYNC LATCH
PINxn
r17
0x00
0xFF
t pd
65
7647F–AVR–04/09
The following code example shows how to set port B pins 0 and 1 high, 2 and 3 low, and define
the port pins from 4 to 7 as input with pull-ups assigned to port pins 6 and 7. The resulting pin
values are read back again, but as previously discussed, a nop instruction is included to be able
to read back the value recently assigned to some of the pins.
Assembly Code Example(1)
...
; Define pull-ups and set outputs high
; Define directions for port pins
ldi
r16, (1<<PB7)|(1<<PB6)|(1<<PB1)|(1<<PB0)
ldi
r17, (1<<DDB3)|(1<<DDB2)|(1<<DDB1)|(1<<DDB0)
out
PORTB, r16
out
DDRB, r17
; Insert nop for synchronization
nop
; Read port pins
in
r16, PINB
...
C Code Example
unsigned char i;
...
/* Define pull-ups and set outputs high */
/* Define directions for port pins */
PORTB = (1<<PB7)|(1<<PB6)|(1<<PB1)|(1<<PB0);
DDRB = (1<<DDB3)|(1<<DDB2)|(1<<DDB1)|(1<<DDB0);
/* Insert nop for synchronization*/
_NOP();
/* Read port pins */
i = PINB;
...
Note:
9.2.5
1. For the assembly program, two temporary registers are used to minimize the time from
pull-ups are set on pins 0, 1, 6, and 7, until the direction bits are correctly set, defining bit 2 and
3 as low and redefining bits 0 and 1 as strong high drivers.
Digital Input Enable and Sleep Modes
As shown in Figure 9-2, the digital input signal can be clamped to ground at the input of the
schmitt-trigger. The signal denoted SLEEP in the figure, is set by the MCU Sleep Controller in
Power-down mode, Power-save mode, and Standby mode to avoid high power consumption if
some input signals are left floating, or have an analog signal level close to VCC/2.
SLEEP is overridden for port pins enabled as external interrupt pins. If the external interrupt
request is not enabled, SLEEP is active also for these pins. SLEEP is also overridden by various
other alternate functions as described in “Alternate Port Functions” on page 67.
If a logic high level (“one”) is present on an Asynchronous External Interrupt pin configured as
“Interrupt on Rising Edge, Falling Edge, or Any Logic Change on Pin” while the external interrupt
is not enabled, the corresponding External Interrupt Flag will be set when resuming from the
above mentioned sleep modes, as the clamping in these sleep modes produces the requested
logic change.
66
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
9.3
Alternate Port Functions
Most port pins have alternate functions in addition to being general digital I/Os. Figure 9-5 shows
how the port pin control signals from the simplified Figure 9-2 can be overridden by alternate
functions. The overriding signals may not be present in all port pins, but the figure serves as a
generic description applicable to all port pins in the AVR microcontroller family.
Figure 9-5.
Alternate Port Functions(1)
PUOExn
PUOVxn
1
PUD
0
DDOExn
DDOVxn
1
Q D
DDxn
0
Q CLR
WDx
PVOExn
RESET
RDx
1
1
Pxn
Q
0
D
0
PORTxn
PTOExn
Q CLR
DIEOExn
DATA BUS
PVOVxn
WPx
DIEOVxn
RESET
WRx
1
0
RRx
SLEEP
SYNCHRONIZER
D
SET
Q
RPx
Q
D
PINxn
L
CLR
Q
CLR
Q
clk I/O
DIxn
AIOxn
PUOExn: Pxn PULL-UP OVERRIDE ENABLE
PUOVxn:
DDOExn:
DDOVxn:
PVOExn:
PVOVxn:
DIEOExn:
Pxn PULL-UP OVERRIDE VALUE
Pxn DATA DIRECTION OVERRIDE ENABLE
Pxn DATA DIRECTION OVERRIDE VALUE
Pxn PORT VALUE OVERRIDE ENABLE
Pxn PORT VALUE OVERRIDE VALUE
Pxn DIGITAL INPUT-ENABLE OVERRIDE ENABLE
DIEOVxn: Pxn DIGITAL INPUT-ENABLE OVERRIDE VALUE
SLEEP: SLEEP CONTROL
PTOExn: Pxn, PORT TOGGLE OVERRIDE ENABLE
Note:
PUD: PULLUP DISABLE
WDx:
RDx:
RRx:
WRx:
RPx:
WPx:
clkI/O:
DIxn:
AIOxn:
WRITE DDRx
READ DDRx
READ PORTx REGISTER
WRITE PORTx
READ PORTx PIN
WRITE PINx
I/O CLOCK
DIGITAL INPUT PIN n ON PORTx
ANALOG INPUT/OUTPUT PIN n ON PORTx
1. WRx, WPx, WDx, RRx, RPx, and RDx are common to all pins within the same port. clkI/O,
SLEEP, and PUD are common to all ports. All other signals are unique for each pin.
Table 9-2 summarizes the function of the overriding signals. The pin and port indexes from Figure 9-5 are not shown in the succeeding tables. The overriding signals are generated internally
in the modules having the alternate function.
67
7647F–AVR–04/09
Table 9-2.
Generic Description of Overriding Signals for Alternate Functions
Signal Name
Full Name
Description
PUOE
Pull-up Override
Enable
If this signal is set, the pull-up enable is controlled by the PUOV
signal. If this signal is cleared, the pull-up is enabled when
{DDxn, PORTxn, PUD} = 0b010.
PUOV
Pull-up Override
Value
If PUOE is set, the pull-up is enabled/disabled when PUOV is
set/cleared, regardless of the setting of the DDxn, PORTxn,
and PUD Register bits.
DDOE
Data Direction
Override Enable
If this signal is set, the Output Driver Enable is controlled by the
DDOV signal. If this signal is cleared, the Output driver is
enabled by the DDxn Register bit.
DDOV
Data Direction
Override Value
If DDOE is set, the Output Driver is enabled/disabled when
DDOV is set/cleared, regardless of the setting of the DDxn
Register bit.
PVOE
Port Value
Override Enable
If this signal is set and the Output Driver is enabled, the port
value is controlled by the PVOV signal. If PVOE is cleared, and
the Output Driver is enabled, the port Value is controlled by the
PORTxn Register bit.
PVOV
Port Value
Override Value
If PVOE is set, the port value is set to PVOV, regardless of the
setting of the PORTxn Register bit.
PTOE
Port Toggle
Override Enable
If PTOE is set, the PORTxn Register bit is inverted.
DIEOE
Digital Input
Enable Override
Enable
If this bit is set, the Digital Input Enable is controlled by the
DIEOV signal. If this signal is cleared, the Digital Input Enable
is determined by MCU state (Normal mode, sleep mode).
DIEOV
Digital Input
Enable Override
Value
If DIEOE is set, the Digital Input is enabled/disabled when
DIEOV is set/cleared, regardless of the MCU state (Normal
mode, sleep mode).
DI
Digital Input
This is the Digital Input to alternate functions. In the figure, the
signal is connected to the output of the schmitt trigger but
before the synchronizer. Unless the Digital Input is used as a
clock source, the module with the alternate function will use its
own synchronizer.
AIO
Analog
Input/Output
This is the Analog Input/output to/from alternate functions. The
signal is connected directly to the pad, and can be used
bi-directionally.
The following subsections shortly describe the alternate functions for each port, and relate the
overriding signals to the alternate function. Refer to the alternate function description for further
details.
68
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
9.3.1
MCU Control Register – MCUCR
Bit
7
6
5
4
3
2
1
0
SPIPS
–
–
PUD
–
–
IVSEL
IVCE
Read/Write
R/W
R
R
R/W
R
R
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
MCUCR
• Bit 4 – PUD: Pull-up Disable
When this bit is written to one, the pull-ups in the I/O ports are disabled even if the DDxn and
PORTxn Registers are configured to enable the pull-ups ({DDxn, PORTxn} = 0b01). Se
9.3.2
Alternate Functions of Port B
The Port B pins with alternate functions are shown in Table 9-3.
Table 9-3.
Port Pin
Port B Pins Alternate Functions
Alternate Functions
PB7
PSCOUT0B (PSC output 0B)
ADC4 (Analog Input Channel 4)
SCK (SPI Bus Serial Clock)
PCINT7 (Pin Change Interrupt 7)
PB6
ADC7 (Analog Input Channel 7)
PSCOUT1B (PSC output 1B)
PCINT6 (Pin Change Interrupt 6)
PB5
ADC6 (Analog Input Channel 6)
INT2 (External Interrupt 2)
ACMPN1 (Analog Comparator 1 Negative Input)
AMP2- (Analog Differential Amplicator 2 Negative Input)
PCINT5 (Pin Change Interrupt 5)
PB4
AMP0+ (Analog Differential Amplifier 0 Positive Input)
PCINT4 (Pin Change Interrupt 4)
PB3
AMP0- (Analog Differential Amplifier 0 Negative Input)
PCINT3 (Pin Change Interrupt 3)
PB2
ADC5 (Analog Input Channel5 )
INT1 (External Interrupt 1)
ACMPN0 (Analog Comparator 0 Negative Input)
PCINT2 (Pin Change Interrupt 2)
PB1
MOSI (SPI Master Out Slave In)
PSCOUT2B (PSC output 2B)
PCINT1 (Pin Change Interrupt 1)
PB0
MISO (SPI Master In Slave Out)
PSCOUT2A (PSC output 2A)
PCINT0 (Pin Change Interrupt 0)
The alternate pin configuration is as follows:
• ADC4/PSCOUT0B/SCK/PCINT7 – Bit 7
PSCOUT0B, Output 0B of PSC.
69
7647F–AVR–04/09
ADC4, Analog to Digital Converter, input channel 4.
SCK, Master Clock output, Slave Clock input pin for SPI channel. When the SPI is enabled as a
slave, this pin is configured as an input regardless of the setting of DDB7. When the SPI is
enabled as a master, the data direction of this pin is controlled by DDB7. When the pin is forced
to be an input, the pull-up can still be controlled by the PORTB7 bit.
PCINT7, Pin Change Interrupt 7.
• ADC7/PSCOUT1B/PCINT6 – Bit 6
ADC7, Analog to Digital Converter, input channel 7.
PSCOUT1B, Output 1B of PSC.
PCINT6, Pin Change Interrupt 6.
• ADC6/INT2/ACMPN1/AMP2-/PCINT5 – Bit 5
ADC6, Analog to Digital Converter, input channel 6.
INT2, External Interrupt source 2. This pin can serve as an External Interrupt source to the MCU.
ACMPN1, Analog Comparator 1 Negative Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
PCINT5, Pin Change Interrupt 5.
• APM0+/PCINT4 – Bit 4
AMP0+, Analog Differential Amplifier 0 Positive Input Channel.
PCINT4, Pin Change Interrupt 4.
• AMP0-/PCINT3 – Bit 3
AMP0-, Analog Differential Amplifier 0 Negative Input Channel. Configure the port pin as input
with the internal pull-up switched off to avoid the digital port function from interfering with the
function of the Analog Amplifier.
PCINT3, Pin Change Interrupt 3.
• ADC5/INT1/ACMPN0/PCINT2 – Bit 2
ADC5, Analog to Digital Converter, input channel 5.
INT1, External Interrupt source 1. This pin can serve as an external interrupt source to the MCU.
ACMPN0, Analog Comparator 0 Negative Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
PCINT2, Pin Change Interrupt 2.
• PCINT1/MOSI/PSCOUT2B – Bit 1
MOSI: SPI Master Data output, Slave Data input for SPI channel. When the SPI is enabled as a
slave, this pin is configured as an input regardless of the setting of DDB1 When the SPI is
enabled as a master, the data direction of this pin is controlled by DDB1. When the pin is forced
to be an input, the pull-up can still be controlled by the PORTB1 and PUD bits.
PSCOUT2B, Output 2B of PSC.
PCINT1, Pin Change Interrupt 1.
70
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• PCINT0/MISO/PSCOUT2A – Bit 0
MISO, Master Data input, Slave Data output pin for SPI channel. When the SPI is enabled as a
master, this pin is configured as an input regardless of the setting of DDB0. When the SPI is
enabled as a slave, the data direction of this pin is controlled by DDB0. When the pin is forced to
be an input, the pull-up can still be controlled by the PORTB0 and PUD bits.
PSCOUT2A, Output 2A of PSC.
PCINT0, Pin Change Interrupt 0.
Table 9-4 and Table 9-5 relates the alternate functions of Port B to the overriding signals shown
in Figure 9-5 on page 67.
Table 9-4.
Overriding Signals for Alternate Functions in PB7..PB4
Signal Name
PB7/ADC4/
PSCOUT0B/SCK/
PCINT7
PB6/ADC7/
PSCOUT1B/
PCINT6
PB5/ADC6/
INT2/ACMPN1/
AMP2-/PCINT5
PB4/AMP0+/
PCINT4
PUOE
SPE • MSTR • SPIPS
0
0
0
PUOV
PB7 • PUD • SPIPS
0
0
0
DDOE
SPE • MSTR • SPIPS
+ PSCen01
PSCen11
0
0
DDOV
PSCen01
1
0
0
PVOE
SPE • MSTR • SPIPS
PSCen11
0
0
PVOV
PSCout01 • SPIPS +
PSCout01 • PSCen01 •
SPIPS
PSCOUT11
+ PSCout01 •
PSCen01 • SPIPS
0
0
DIEOE
ADC4D
ADC7D
ADC6D + In2en
AMP0ND
DIEOV
0
0
In2en
0
DI
SCKin • SPIPS • ireset ICP1B
INT2
AIO
ADC4
ADC6
Table 9-5.
ADC7
AMP0+
Overriding Signals for Alternate Functions in PB3..PB0
Signal Name
PB3/AMP0-/
PCINT3
PB2/ADC5/INT1/
ACMPN0/PCINT2
PB1/MOSI/
PSCOUT2B/
PCINT1
PB0/MISO/
PSCOUT2A/
PCINT0
PUOE
0
0
–
–
PUOV
0
0
–
–
DDOE
0
0
–
–
DDOV
0
0
–
–
PVOE
0
0
–
–
PVOV
0
0
–
–
DIEOE
AMP0ND
ADC5D + In1en
0
0
DIEOV
0
In1en
0
0
INT1
MOSI_IN • SPIPS • MISO_IN • SPIPS •
ireset
ireset
ADC5
–
DI
AIO
AMP0-
–
71
7647F–AVR–04/09
9.3.3
Alternate Functions of Port C
The Port C pins with alternate functions are shown in Table 9-6.
Table 9-6.
Port C Pins Alternate Functions
Port Pin
Note:
Alternate Function
PC7
D2A (DAC output )
AMP2+ (Analog Differential Amplifier 2 Positive Input)
PCINT15 (Pin Change Interrupt 15)
PC6
ADC10 (Analog Input Channel 10)
ACMP1 (Analog Comparator 1 Positive Input )
PCINT14 (Pin Change Interrupt 14)
PC5
ADC9 (Analog Input Channel 9)
AMP1+ (Analog Differential Amplifier 1 Input Channel )
ACMP3 (Analog Comparator 3 Positive Input )
PCINT13 (Pin Change Interrupt 13)
PC4
ADC8 (Analog Input Channel 8)
AMP1- (Analog Differential Amplifier 1 Input Channel )
ACMPN3 (Analog Comparator 3 Negative Input)
PCINT12 (Pin Change Interrupt 12)
PC3
T1 (Timer 1 clock input)
RXCAN (CAN Rx Data)
ICP1B (Timer 1 input capture alternate input)
PCINT11 (Pin Change Interrupt 11)
PC2
T0 (Timer 0 clock input)
TXCAN (CAN Tx Data)
PCINT10 (Pin Change Interrupt 10)
PC1
PSCIN1 (PSC 1 Digital Input)
OC1B (Timer 1 Output Compare B)
SS_A (Alternate SPI Slave Select)
PCINT9 (Pin Change Interrupt 9)
PC0
PSCOUT1A (PSC output 2A)
INT3 (External Interrupt 3)
PCINT8 (Pin Change Interrupt 8)
On the engineering samples (Parts marked AT90PWM324), the ACMPN3 alternate function is not
located on PC4. It is located on PE2.
The alternate pin configuration is as follows:
• D2A/AMP2+/PCINT15 – Bit 7
D2A, Digital to Analog output
AMP2+, Analog Differential Amplifier 2 Positive Input. Configure the port pin as input with the
internal pull-up switched off to avoid the digital port function from interfering with the function of
the Amplifier.
PCINT15, Pin Change Interrupt 15.
72
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• ADC10/ACMP1/PCINT14 – Bit 6
ADC10, Analog to Digital Converter, input channel 10.
ACMP1, Analog Comparator 1 Positive Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
PCINT14, Pin Change Interrupt 14.
• ADC9/ACMP3/AMP1+/PCINT13 – Bit 5
ADC9, Analog to Digital Converter, input channel 9.
ACMP3, Analog Comparator 3 Positive Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
AMP1+, Analog Differential Amplifier 1 Positive Input Channel. Configure the port pin as input
with the internal pull-up switched off to avoid the digital port function from interfering with the
function of the Analog Amplifier.
PCINT13, Pin Change Interrupt 13.
• ADC8/AMP1-/ACMPN3/PCINT12 – Bit 4
ADC8, Analog to Digital Converter, input channel 8.
AMP1-, Analog Differential Amplifier 1 Negative Input Channel. Configure the port pin as input
with the internal pull-up switched off to avoid the digital port function from interfering with the
function of the Analog Amplifier.
ACMPN3, Analog Comparator 3 Negative Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
PCINT12, Pin Change Interrupt 12.
• PCINT11/T1/RXCAN/ICP1B – Bit 3
T1, Timer/Counter1 counter source.
RXCAN, CAN Rx Data.
ICP1B, Input Capture Pin: The PC3 pin can act as an Input Capture Pin for Timer/Counter1.
PCINT11, Pin Change Interrupt 11.
• PCINT10/T0/TXCAN – Bit 2
T0, Timer/Counter0 counter source.
TXCAN, CAN Tx Data.
PCINT10, Pin Change Interrupt 10.
• PCINT9/PSCIN1/OC1B/SS_A – Bit 1
PCSIN1, PSC 1 Digital Input.
OC1B, Output Compare Match B output: This pin can serve as an external output for the
Timer/Counter1 Output Compare B. The pin has to be configured as an output (DDC1 set “one”)
to serve this function. This pin is also the output pin for the PWM mode timer function.
73
7647F–AVR–04/09
SS_A: Slave Port Select input. When the SPI is enabled as a slave, this pin is configured as an
input regardless of the setting of DDD0. As a slave, the SPI is activated when this pin is driven
low. When the SPI is enabled as a master, the data direction of this pin is controlled by DDD0.
When the pin is forced to be an input, the pull-up can still be controlled by the PORTD0 bit.
PCINT9, Pin Change Interrupt 9.
• PCINT8/PSCOUT1A/INT3 – Bit 0
PSCOUT1A, Output 1A of PSC.
INT3, External Interrupt source 3: This pin can serve as an external interrupt source to the MCU.
PCINT8, Pin Change Interrupt 8.
Table 9-7 and Table 9-8 relate the alternate functions of Port C to the overriding signals shown
in Figure 9-5 on page 67.
Table 9-7.
Overriding Signals for Alternate Functions in PC7..PC4
Signal Name
PC7/D2A/AMP2+/
PCINT15
PC6/ADC10/
ACMP1/
PCINT14
PC5/ADC9/
AMP1+/ACMP3/
PCINT13
PUOE
0
0
0
PC4/ADC8/
AMP1-/ACMPN3/
PCINT12
PUOV
0
0
0
DDOE
DAEN
0
0
0
DDOV
0
0
0
0
PVOE
0
0
0
–
PVOV
0
0
0
–
DIEOE
DAEN
ADC10D
ADC9D
ADC8D
DIEOV
0
0
0
0
–
ADC10 Amp1
ADC9 Amp1+
ADC8 Amp1ACMPN3
DI
AIO
Table 9-8.
Signal Name
Overriding Signals for Alternate Functions in PC3..PC0
PC3/T1/RXCAN/
ICP1B/PCINT11
PC2/T0/TXCAN/
PCINT10
PC1/PSCIN1/
OC1B/SS_A/
PCINT9
PC0/INT3/
PSCOUT1A/
PCINT8
PUOE
0
0
0
0
PUOV
0
0
0
0
0
PSCen10
0
1
PVOE
OC1Ben
PSCen10
PVOV
OC1B
PSCout10
DDOE
DDOV
1
1
DIEOE
In3en
DIEOV
In3en
DI
T1
T0
PSCin1
SS_A
INT3
AIO
74
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
9.3.4
Alternate Functions of Port D
The Port D pins with alternate functions are shown in Table 9-9.
Table 9-9.
Port Pin
Port D Pins Alternate Functions
Alternate Function
PD7
ACMP0 (Analog Comparator 0 Positive Input )
PCINT23 (Pin Change Interrupt 23)
PD6
ADC3 (Analog Input Channel 3 )
ACMPN2 (Analog Comparator 2 Negative Input)
INT0 (External Interrupt 0)
PCINT22 (Pin Change Interrupt 22)
PD5
ADC2 (Analog Input Channel 2)
ACMP2 (Analog Comparator 2 Positive Input )
PCINT21 (Pin Change Interrupt 21)
PD4
ADC1 (Analog Input Channel 1)
RXD/RXLIN (LIN/UART Rx data)
ICP1A (Timer 1 input capture)
SCK_A (Programming & alternate SPI Clock)
PCINT20 (Pin Change Interrupt 20)
PD3
TXD/TXLIN (LIN/UART Tx data)
OC0A (Timer 0 Output Compare A)
SS (SPI Slave Select)
MOSI_A (Programming & alternate SPI Master Out Slave In)
PCINT19 (Pin Change Interrupt 19)
PD2
PSCIN2 (PSC Digital Input 2)
OC1A (Timer 1 Output Compare A)
MISO_A (Programming & alternate Master In SPI Slave Out)
PCINT18 (Pin Change Interrupt 18)
PD1
PSCIN0 (PSC Digital Input 0)
CLKO (System Clock Output)
PCINT17 (Pin Change Interrupt 17)
PD0
PSCOUT0A (PSC output 0A)
PCINT16 (Pin Change Interrupt 16)
The alternate pin configuration is as follows:
• ACMP0/PCINT23 – Bit 7
ACMP0, Analog Comparator 0 Positive Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
PCINT23, Pin Change Interrupt 23.
• ADC3/ACMPN2/INT0/PCINT22 – Bit 6
ADC3, Analog to Digital Converter, input channel 3.
75
7647F–AVR–04/09
ACMPN2, Analog Comparator 2 Negative Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
INT0, External Interrupt source 0. This pin can serve as an external interrupt source to the MCU.
PCINT22, Pin Change Interrupt 23.
• ADC2/ACMP2/PCINT21 – Bit 5
ADC2, Analog to Digital Converter, input channel 2.
ACMP2, Analog Comparator 1 Positive Input. Configure the port pin as input with the internal
pull-up switched off to avoid the digital port function from interfering with the function of the Analog Comparator.
PCINT21, Pin Change Interrupt 21.
• PCINT20/ADC1/RXD/RXLIN/ICP1/SCK_A – Bit 4
ADC1, Analog to Digital Converter, input channel 1.
RXD/RXLIN, LIN/UART Receive Pin. Receive Data (Data input pin for the LIN/UART). When the
LIN/UART receiver is enabled this pin is configured as an input regardless of the value of
DDRD4. When the UART forces this pin to be an input, a logical one in PORTD4 will turn on the
internal pull-up.
ICP1, Input Capture Pin1: This pin can act as an input capture pin for Timer/Counter1.
SCK_A: Master Clock output, Slave Clock input pin for SPI channel. When the SPI is enabled as
a slave, this pin is configured as an input regardless of the setting of DDD4. When the SPI is
enabled as a master, the data direction of this pin is controlled by DDD4. When the pin is forced
to be an input, the pull-up can still be controlled by the PORTD4 bit.
PCINT20, Pin Change Interrupt 20.
• PCINT19/TXD/TXLIN/OC0A/SS/MOSI_A, Bit 3
TXD/TXLIN, LIN/UART Transmit pin. Data output pin for the LIN/UART. When the LIN/UART
Transmitter is enabled, this pin is configured as an output regardless of the value of DDD3.
OC0A, Output Compare Match A output: This pin can serve as an external output for the
Timer/Counter0 Output Compare A. The pin has to be configured as an output (DDD3 set “one”)
to serve this function. The OC0A pin is also the output pin for the PWM mode
SS: Slave Port Select input. When the SPI is enabled as a slave, this pin is configured as an
input regardless of the setting of DDD3. As a slave, the SPI is activated when this pin is driven
low. When the SPI is enabled as a master, the data direction of this pin is controlled by DDD3.
When the pin is forced to be an input, the pull-up can still be controlled by the PORTD3 bit.
MOSI_A: SPI Master Data output, Slave Data input for SPI channel. When the SPI is enabled as
a slave, this pin is configured as an input regardless of the setting of DDD3 When the SPI is
enabled as a master, the data direction of this pin is controlled by DDD3. When the pin is forced
to be an input, the pull-up can still be controlled by the PORTD3 bit.
PCINT19, Pin Change Interrupt 19.
• PCINT18/PSCIN2/OC1A/MISO_A, Bit 2
PCSIN2, PSC Digital Input 2.
OC1A, Output Compare Match A output: This pin can serve as an external output for the
Timer/Counter1 Output Compare A. The pin has to be configured as an output (DDD2 set “one”)
to serve this function. The OC1A pin is also the output pin for the PWM mode timer function.
76
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
MISO_A: Master Data input, Slave Data output pin for SPI channel. When the SPI is enabled as
a master, this pin is configured as an input regardless of the setting of DDD2. When the SPI is
enabled as a slave, the data direction of this pin is controlled by DDD2. When the pin is forced to
be an input, the pull-up can still be controlled by the PORTD2 bit.
PCINT18, Pin Change Interrupt 18.
• PCINT17/PSCIN0/CLKO – Bit 1
PCSIN0, PSC Digital Input 0.
CLKO, Divided System Clock: The divided system clock can be output on this pin. The divided
system clock will be output if the CKOUT Fuse is programmed, regardless of the PORTD1 and
DDD1 settings. It will also be output during reset.
PCINT17, Pin Change Interrupt 17.
• PCINT16/PSCOUT0A – Bit 0
PSCOUT0A: Output 0 of PSC 0.
PCINT16, Pin Change Interrupt 16.
Table 9-10 and Table 9-11 relates the alternate functions of Port D to the overriding signals
shown in Figure 9-5 on page 67.
Table 9-10.
Overriding Signals for Alternate Functions PD7..PD4
Signal Name
PD7/
ACMP0/
PCINT23
PD6/ADC3/
ACMPN2/INT0/
PCINT22
PD5/ADC2/
ACMP2/PCINT21
PD4/ADC1/RXD/
RXLIN/ICP1A/
SCK_A/PCINT20
PUOE
0
0
0
RXEN + SPE •
MSTR • SPIPS
PUOV
0
0
0
PD4 •
PUD
DDOE
0
0
0
RXEN + SPE •
MSTR • SPIPS
DDOV
0
0
0
0
PVOE
0
0
0
SPE • MSTR •
SPIPS
PVOV
0
0
0
–
DIEOE
ACMP0D
ADC3D + In0en
ADC2D
ADC1D
DIEOV
0
In0en
0
0
DI
–
INT0
AIO
ACOMP0
ADC3
ACMPM
ICP1A
ADC2
ACOMP2
ADC1
77
7647F–AVR–04/09
Table 9-11.
Overriding Signals for Alternate Functions in PD3..PD0
PD3/TXD/TXLIN/
OC0A/SS/MOSI_A/
PCINT19
PD2/PSCIN2/
OC1A/MISO_A/
PCINT18
PD1/PSCIN0/
CLKO/
PCINT17
PUOE
TXEN + SPE •
MSTR • SPIPS
–
0
SPE •
MSTR • SPIPS
PUOV
TXEN • SPE • MSTR
• SPIPS • PD3 • PUD
–
0
PD0 • PUD
DDOE
TXEN + SPE •
MSTR • SPIPS
–
0
PSCen00 + SPE •
MSTR • SPIPS
DDOV
TXEN
0
0
PSCen00
PVOE
TXEN + OC0en +
SPE •
MSTR • SPIPS
–
0
PSCen00 + UMSEL
PVOV
TXEN • TXD + TXEN
• (OC0en • OC0 +
OC0en • SPIPS •
MOSI)
–
0
–
DIEOE
0
0
0
0
DIEOV
0
0
0
0
DI
SS
MOSI_Ain
Signal Name
PD0/PSCOUT0A/
XCK/PCINT16
AIO
9.3.5
Alternate Functions of Port E
The Port E pins with alternate functions are shown in Table 9-12.
Table 9-12.
Port Pin
Alternate Function
PE2
XTAL2 (XTAL Output)
ADC0 (Analog Input Channel 0)
PCINT26 (Pin Change Interrupt 26)
PE1
XTAL1 (XTAL Input)
OC0B (Timer 0 Output Compare B)
PCINT25 (Pin Change Interrupt 25)
PE0
RESET# (Reset Input)
OCD (On Chip Debug I/O)
PCINT24 (Pin Change Interrupt 24)
Note:
78
Port E Pins Alternate Functions
On the engineering samples (Parts marked AT90PWM324), the ACMPN3 alternate function is not
located on PC4. It is located on PE2.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The alternate pin configuration is as follows:
• PCINT26/XTAL2/ADC0 – Bit 2
XTAL2: Chip clock Oscillator pin 2. Used as clock pin for crystal Oscillator or Low-frequency
crystal Oscillator. When used as a clock pin, the pin can not be used as an I/O pin.
ADC0, Analog to Digital Converter, input channel 0.
PCINT26, Pin Change Interrupt 26.
• PCINT25/XTAL1/OC0B – Bit 1
XTAL1: Chip clock Oscillator pin 1. Used for all chip clock sources except internal calibrated RC
Oscillator. When used as a clock pin, the pin can not be used as an I/O pin.
OC0B, Output Compare Match B output: This pin can serve as an external output for the
Timer/Counter0 Output Compare B. The pin has to be configured as an output (DDE1 set “one”)
to serve this function. This pin is also the output pin for the PWM mode timer function.
PCINT25, Pin Change Interrupt 25.
• PCINT24/RESET/OCD – Bit 0
RESET, Reset pin: When the RSTDISBL Fuse is programmed, this pin functions as a normal I/O
pin, and the part will have to rely on Power-on Reset and Brown-out Reset as its reset sources.
When the RSTDISBL Fuse is unprogrammed, the reset circuitry is connected to the pin, and the
pin can not be used as an I/O pin.
If PE0 is used as a reset pin, DDE0, PORTE0 and PINE0 will all read 0.
PCINT24, Pin Change Interrupt 24.
Table 9-13 relates the alternate functions of Port E to the overriding signals shown in Figure 9-5
on page 67.
Table 9-13.
Overriding Signals for Alternate Functions in PE2..PE0
Signal Name
PE2/ADC0/XTAL2/
PCINT26
PE1/XTAL1/OC0B/
PCINT25
PE0/RESET/
OCD/PCINT24
PUOE
0
0
0
PUOV
0
0
0
DDOE
0
0
0
DDOV
0
0
0
PVOE
0
OC0Ben
0
PVOV
0
OC0B
0
DIEOE
ADC0D
0
0
DIEOV
0
0
0
Osc Output
ADC0
Osc / Clock input
DI
AIO
79
7647F–AVR–04/09
9.4
9.4.1
Register Description for I/O-Ports
Port B Data Register – PORTB
Bit
9.4.2
7
6
5
4
3
2
1
0
PORTB7
PORTB6
PORTB5
PORTB4
PORTB3
PORTB2
PORTB1
PORTB0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
Port B Data Direction Register – DDRB
Bit
9.4.3
7
6
5
4
3
2
1
0
DDB7
DDB6
DDB5
DDB4
DDB3
DDB2
DDB1
DDB0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
7
6
5
4
3
2
1
0
PINB7
PINB6
PINB5
PINB4
PINB3
PINB2
PINB1
PINB0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
7
6
5
4
3
2
1
0
PORTC7
PORTC6
PORTC5
PORTC4
PORTC3
PORTC2
PORTC1
PORTC0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
7
6
5
4
3
2
1
0
DDC7
DDC6
DDC5
DDC4
DDC3
DDC2
DDC1
DDC0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
7
6
5
4
3
2
1
0
PINC7
PINC6
PINC5
PINC4
PINC3
PINC2
PINC1
PINC0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
7
6
5
4
3
2
1
0
PORTD7
PORTD6
PORTD5
PORTD4
PORTD3
PORTD2
PORTD1
PORTD0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PORTD
Port D Data Direction Register – DDRD
Bit
80
PINC
Port D Data Register – PORTD
Bit
9.4.8
DDRC
Port C Input Pins Address – PINC
Bit
9.4.7
PORTC
Port C Data Direction Register – DDRC
Bit
9.4.6
PINB
Port C Data Register – PORTC
Bit
9.4.5
DDRB
Port B Input Pins Address – PINB
Bit
9.4.4
PORTB
7
6
5
4
3
2
1
0
DDD7
DDD6
DDD5
DDD4
DDD3
DDD2
DDD1
DDD0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
DDRD
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
9.4.9
Port D Input Pins Address – PIND
Bit
9.4.10
7
6
5
4
3
2
1
0
PIND7
PIND6
PIND5
PIND4
PIND3
PIND2
PIND1
PIND0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
7
6
5
4
3
2
1
0
–
–
–
–
–
PORTE2
PORTE1
PORTE0
Read/Write
R
R
R
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
7
6
5
4
3
2
1
0
–
–
–
–
–
DDE2
DDE1
DDE0
Read/Write
R
R
R
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
7
6
5
4
3
2
1
0
–
–
–
–
–
PINE2
PINE1
PINE0
Read/Write
R
R
R
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
N/A
N/A
N/A
Port E Data Register – PORTE
Bit
9.4.11
PORTE
Port E Data Direction Register – DDRE
Bit
9.4.12
PIND
DDRE
Port E Input Pins Address – PINE
Bit
PINE
81
7647F–AVR–04/09
10. External Interrupts
The External Interrupts are triggered by the INT3:0 pins or any of the PCINT23..0 pins. Observe
that, if enabled, the interrupts will trigger even if the INT3:0 or PCINT23..0 pins are configured as
outputs. This feature provides a way of generating a software interrupt. The pin change interrupt
PCI2 will trigger if any enabled PCINT23..16 pin toggles. The pin change interrupt PCI1 will trigger if any enabled PCINT14..8 pin toggles. The pin change interrupt PCI0 will trigger if any
enabled PCINT7..0 pin toggles. The PCMSK3, PCMSK2, PCMSK1 and PCMSK0 Registers
control which pins contribute to the pin change interrupts. Pin change interrupts on PCINT26..0
are detected asynchronously. This implies that these interrupts can be used for waking the part
also from sleep modes other than Idle mode.
The INT3:0 interrupts can be triggered by a falling or rising edge or a low level. This is set up as
indicated in the specification for the External Interrupt Control Register A – EICRA. When the
INT3:0 interrupts are enabled and are configured as level triggered, the interrupts will trigger as
long as the pin is held low. Note that recognition of falling or rising edge interrupts on INT3:0
requires the presence of an I/O clock, described in “Clock Systems and their Distribution” on
page 29. Low level interrupt on INT3:0 is detected asynchronously. This implies that this interrupt can be used for waking the part also from sleep modes other than Idle mode. The I/O clock
is halted in all sleep modes except Idle mode.
Note that if a level triggered interrupt is used for wake-up from Power-down, the required level
must be held long enough for the MCU to complete the wake-up to trigger the level interrupt. If
the level disappears before the end of the Start-up Time, the MCU will still wake up, but no interrupt will be generated. The start-up time is defined by the SUT and CKSEL Fuses as described
in “Clock Systems and their Distribution” on page 29.
10.1
Pin Change Interrupt Timing
An example of timing of a pin change interrupt is schown in Figure 10-1.
Figure 10-1. Timing of a pin change interrupts
0
PCINT[i]
pin
D
Q
pin_lat
D
Q
pin_sync
LE
PCINT[i] bit
(of PCMSKn)
clk
pcint_sync
pcint_in[i]
D
7
Q
pcint_set/flag
D
Q
D
Q
PCIFn
(interrupt
flag)
clk
clk
PCINT[i] pin
pin_lat
pin_sync
pcint_in[i]
pcint_syn
pcint_set/flag
PCIFn
82
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
10.2
External Interrupt Control Register A – EICRA
The External Interrupt Control Register A contains control bits for interrupt sense control.
Bit
7
6
5
4
3
2
1
0
ISC31
ISC30
ISC21
ISC20
ISC11
ISC10
ISC01
ISC00
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
EICRA
• Bit 7..0 – ISC31, ISC30 - ISC01, ISC00: Interrupt Sense Control 0 Bit 1 and Bit 0
The External Interrupts 3 - 0 are activated by the external pins INT3:0 if the SREG I-flag and the
corresponding interrupt mask in the EIMSK is set. The level and edges on the external pins that
activate the interrupt are defined in Table 10-1. Edges on INT3..INT0 are registered asynchronously. The value on the INT3:0 pins are sampled before detecting edges. If edge or toggle
interrupt is selected, pulses that last longer than one clock period will generate an interrupt.
Shorter pulses are not guaranteed to generate an interrupt. Observe that CPU clock frequency
can be lower than XTAL frequency if the XTAL divider is enabled. If low level interrupt is
selected, the low level must be held until the completion of the currently executing instruction to
generate an interrupt. If enabled, a level triggered interrupt will generate an interrupt request as
long as the pin is held low.
Table 10-1.
ISCn1
ISCn0
0
0
The low level of INTn generates an interrupt request.
0
1
Any logical change on INTn generates an interrupt request.
1
0
The falling edge between two samples of INTn generates an interrupt request.
1
1
The rising edge between two samples of INTn generates an interrupt request.
Note:
10.2.1
Interrupt Sense Control(1)
Description
1. n = 3, 2, 1 or 0.
When changing the ISCn1/ISCn0 bits, the interrupt must be disabled by clearing its Interrupt
Enable bit in the EIMSK Register. Otherwise an interrupt can occur when the bits are changed.
External Interrupt Mask Register – EIMSK
Bit
7
6
5
4
3
2
1
0
–
–
–
–
INT3
INT2
INT1
INT0
Read/Write
R
R
R
R
R
R
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
EIMSK
• Bit 7..4 – Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 3..0 – INT3 - 0: External Interrupt Request 3:0 Enable
When an INT3 – INT0 bit is written to one and the I-bit in the Status Register (SREG) is set
(one), the corresponding external pin interrupt is enabled. The Interrupt Sense Control bits in the
External Interrupt Control Register A - EICRA defines whether the external interrupt is activated
on rising or falling edge or level sensed. Activity on any of these pins will trigger an interrupt
request even if the pin is enabled as an output. This provides a way of generating a software
interrupt.
83
7647F–AVR–04/09
10.2.2
External Interrupt Flag Register – EIFR
Bit
7
6
5
4
3
2
1
0
–
–
–
–
INTF3
INTF2
INTF1
INTF0
Read/Write
R
R
R
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
EIFR
• Bit 7..4 – Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 3..0 – INTF3 - INTF0: External Interrupt Flag 3 - 0
When an edge or logic change on the INT3:0 pin triggers an interrupt request, INTF3:0 becomes
set (one). If the I-bit in SREG and the corresponding interrupt enable bit INT3:0 in EIMSK, are
set (one), the MCU will jump to the interrupt vector. The flag is cleared when the interrupt routine
is executed. Alternatively, the flag can be cleared by writing a logical one to it. These flags are
always cleared when INT3:0 are configured as a level interrupt.
10.2.3
Pin Change Interrupt Control Register - PCICR
Bit
7
6
5
4
3
2
1
0
–
–
–
–
PCIE3
PCIE2
PCIE1
PCIE0
Read/Write
R
R
R
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PCICR
• Bit 7..4 - Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 3 - PCIE3: Pin Change Interrupt Enable 3
When the PCIE3 bit is set (one) and the I-bit in the Status Register (SREG) is set (one), pin
change interrupt 3 is enabled. Any change on any enabled PCINT26..24 pin will cause an interrupt. The corresponding interrupt of Pin Change Interrupt Request is executed from the PCI3
Interrupt Vector. PCINT26..24 pins are enabled individually by the PCMSK3 Register.
• Bit 2 - PCIE2: Pin Change Interrupt Enable 2
When the PCIE2 bit is set (one) and the I-bit in the Status Register (SREG) is set (one), pin
change interrupt 2 is enabled. Any change on any enabled PCINT23..16 pin will cause an interrupt. The corresponding interrupt of Pin Change Interrupt Request is executed from the PCI2
Interrupt Vector. PCINT23..16 pins are enabled individually by the PCMSK2 Register.
• Bit 1 - PCIE1: Pin Change Interrupt Enable 1
When the PCIE1 bit is set (one) and the I-bit in the Status Register (SREG) is set (one), pin
change interrupt 1 is enabled. Any change on any enabled PCINT15..8 pin will cause an interrupt. The corresponding interrupt of Pin Change Interrupt Request is executed from the PCI1
Interrupt Vector. PCINT15..8 pins are enabled individually by the PCMSK1 Register.
• Bit 0 - PCIE0: Pin Change Interrupt Enable 0
When the PCIE0 bit is set (one) and the I-bit in the Status Register (SREG) is set (one), pin
change interrupt 0 is enabled. Any change on any enabled PCINT7..0 pin will cause an interrupt.
The corresponding interrupt of Pin Change Interrupt Request is executed from the PCI0 Interrupt Vector. PCINT7..0 pins are enabled individually by the PCMSK0 Register.
84
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
10.2.4
Pin Change Interrupt Flag Register - PCIFR
Bit
7
6
5
4
3
2
1
0
–
–
–
–
PCIF3
PCIF2
PCIF1
PCIF0
Read/Write
R
R
R
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PCIFR
• Bit 7..4 - Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 3 - PCIF3: Pin Change Interrupt Flag 3
When a logic change on any PCINT26..24 pin triggers an interrupt request, PCIF3 becomes set
(one). If the I-bit in SREG and the PCIE3 bit in PCICR are set (one), the MCU will jump to the
corresponding Interrupt Vector. The flag is cleared when the interrupt routine is executed. Alternatively, the flag can be cleared by writing a logical one to it.
• Bit 2 - PCIF2: Pin Change Interrupt Flag 2
When a logic change on any PCINT23..16 pin triggers an interrupt request, PCIF2 becomes set
(one). If the I-bit in SREG and the PCIE2 bit in PCICR are set (one), the MCU will jump to the
corresponding Interrupt Vector. The flag is cleared when the interrupt routine is executed. Alternatively, the flag can be cleared by writing a logical one to it.
• Bit 1 - PCIF1: Pin Change Interrupt Flag 1
When a logic change on any PCINT15..8 pin triggers an interrupt request, PCIF1 becomes set
(one). If the I-bit in SREG and the PCIE1 bit in PCICR are set (one), the MCU will jump to the
corresponding Interrupt Vector. The flag is cleared when the interrupt routine is executed. Alternatively, the flag can be cleared by writing a logical one to it.
• Bit 0 - PCIF0: Pin Change Interrupt Flag 0
When a logic change on any PCINT7..0 pin triggers an interrupt request, PCIF0 becomes set
(one). If the I-bit in SREG and the PCIE0 bit in PCICR are set (one), the MCU will jump to the
corresponding Interrupt Vector. The flag is cleared when the interrupt routine is executed. Alternatively, the flag can be cleared by writing a logical one to it.
10.2.5
Pin Change Mask Register 3 – PCMSK3
Bit
7
6
5
4
3
2
1
0
-
-
-
-
-
PCINT26
PCINT25
PCINT24
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PCMSK3
• Bit 7..3 – Res: Reserved Bit
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 2..0 – PCINT26..24: Pin Change Enable Mask 26..24
Each PCINT26..24-bit selects whether pin change interrupt is enabled on the corresponding I/O
pin. If PCINT26..24 is set and the PCIE3 bit in PCICR is set, pin change interrupt is enabled on
the corresponding I/O pin. If PCINT23..24 is cleared, pin change interrupt on the corresponding
I/O pin is disabled.
85
7647F–AVR–04/09
10.2.6
Pin Change Mask Register 2 – PCMSK2
Bit
7
6
5
4
3
2
1
0
PCINT23
PCINT22
PCINT21
PCINT20
PCINT19
PCINT18
PCINT17
PCINT16
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PCMSK2
• Bit 7..0 – PCINT23..16: Pin Change Enable Mask 23..16
Each PCINT23..16-bit selects whether pin change interrupt is enabled on the corresponding I/O
pin. If PCINT23..16 is set and the PCIE2 bit in PCICR is set, pin change interrupt is enabled on
the corresponding I/O pin. If PCINT23..16 is cleared, pin change interrupt on the corresponding
I/O pin is disabled.
10.2.7
Pin Change Mask Register 1 – PCMSK1
Bit
7
6
5
4
3
2
1
0
PCINT15
PCINT14
PCINT13
PCINT12
PCINT11
PCINT10
PCINT9
PCINT8
Read/Write
R
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PCMSK1
• Bit 7 – Res: Reserved Bit
This bit is an unused bit in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 7..0 – PCINT15..8: Pin Change Enable Mask 15..8
Each PCINT15..8-bit selects whether pin change interrupt is enabled on the corresponding I/O
pin. If PCINT15..8 is set and the PCIE1 bit in PCICR is set, pin change interrupt is enabled on
the corresponding I/O pin. If PCINT15..8 is cleared, pin change interrupt on the corresponding
I/O pin is disabled.
10.2.8
Pin Change Mask Register 0 – PCMSK0
Bit
7
6
5
4
3
2
1
PCINT7
PCINT6
PCINT5
PCINT4
PCINT3
PCINT2
PCINT1
0
PCINT0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PCMSK0
• Bit 7..0 – PCINT7..0: Pin Change Enable Mask 7..0
Each PCINT7..0 bit selects whether pin change interrupt is enabled on the corresponding I/O
pin. If PCINT7..0 is set and the PCIE0 bit in PCICR is set, pin change interrupt is enabled on the
corresponding I/O pin. If PCINT7..0 is cleared, pin change interrupt on the corresponding I/O pin
is disabled.
86
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
11. Timer/Counter0 and Timer/Counter1 Prescalers
Timer/Counter1 and Timer/Counter0 share the same prescaler module, but the Timer/Counters
can have different prescaler settings. The description below applies to both Timer/Counter1 and
Timer/Counter0.
11.1
Internal Clock Source
The Timer/Counter can be clocked directly by the system clock (by setting the CSn2:0 = 1). This
provides the fastest operation, with a maximum Timer/Counter clock frequency equal to system
clock frequency (fCLK_I/O). Alternatively, one of four taps from the prescaler can be used as a
clock source. The prescaled clock has a frequency of either fCLK_I/O/8, fCLK_I/O/64, fCLK_I/O/256, or
fCLK_I/O/1024.
11.2
Prescaler Reset
The prescaler is free running, i.e., operates independently of the Clock Select logic of the
Timer/Counter, and it is shared by Timer/Counter1 and Timer/Counter0. Since the prescaler is
not affected by the Timer/Counter’s clock select, the state of the prescaler will have implications
for situations where a prescaled clock is used. One example of prescaling artifacts occurs when
the timer is enabled and clocked by the prescaler (6 > CSn2:0 > 1). The number of system clock
cycles from when the timer is enabled to the first count occurs can be from 1 to N+1 system
clock cycles, where N equals the prescaler divisor (8, 64, 256, or 1024).
It is possible to use the prescaler reset for synchronizing the Timer/Counter to program execution. However, care must be taken if the other Timer/Counter that shares the same prescaler
also uses prescaling. A prescaler reset will affect the prescaler period for all Timer/Counters it is
connected to.
11.3
External Clock Source
An external clock source applied to the Tn pin can be used as Timer/Counter clock (clkT1/clkT0).
The Tn pin is sampled once every system clock cycle by the pin synchronization logic. The synchronized (sampled) signal is then passed through the edge detector. Figure 11-1 shows a
functional equivalent block diagram of the Tn/T0 synchronization and edge detector logic. The
registers are clocked at the positive edge of the internal system clock (clkI/O). The latch is transparent in the high period of the internal system clock.
The edge detector generates one clkT1/clkT0 pulse for each positive (CSn2:0 = 7) or negative
(CSn2:0 = 6) edge it detects.
Figure 11-1. Tn Pin Sampling
Tn
D
Q
D
Q
D
Tn_sync
(To Clock
Select Logic)
Q
LE
clk I/O
Synchronization
Edge Detector
The synchronization and edge detector logic introduces a delay of 2.5 to 3.5 system clock cycles
from an edge has been applied to the Tn/T0 pin to the counter is updated.
87
7647F–AVR–04/09
Enabling and disabling of the clock input must be done when Tn/T0 has been stable for at least
one system clock cycle, otherwise it is a risk that a false Timer/Counter clock pulse is generated.
Each half period of the external clock applied must be longer than one system clock cycle to
ensure correct sampling. The external clock must be guaranteed to have less than half the system clock frequency (fExtClk < fclk_I/O/2) given a 50/50% duty cycle. Since the edge detector uses
sampling, the maximum frequency of an external clock it can detect is half the sampling frequency (Nyquist sampling theorem). However, due to variation of the system clock frequency
and duty cycle caused by Oscillator source (crystal, resonator, and capacitors) tolerances, it is
recommended that maximum frequency of an external clock source is less than fclk_I/O/2.5.
An external clock source can not be prescaled.
Figure 11-2. Prescaler for Timer/Counter0 and Timer/Counter1(1)
clk I/O
Clear
PSRSYNC
T0
Synchronization
T1
Synchronization
clkT1
Note:
11.3.1
clkT0
1. The synchronization logic on the input pins (Tn) is shown in Figure 11-1.
General Timer/Counter Control Register – GTCCR
Bit
7
6
5
4
3
2
1
0
TSM
ICPSEL1
–
–
–
–
–
PSRSYNC
Read/Write
R/W
R/W
R
R
R
R
R
R/W
Initial Value
0
0
0
0
0
0
0
0
GTCCR
• Bit 7 – TSM: Timer/Counter Synchronization Mode
Writing the TSM bit to one activates the Timer/Counter Synchronization mode. In this mode, the
value that is written to the PSRSYNC bit is kept, hence keeping the corresponding prescaler
reset signals asserted. This ensures that the corresponding Timer/Counters are halted and can
be configured to the same value without the risk of one of them advancing during configuration.
When the TSM bit is written to zero, the PSRSYNC bit is cleared by hardware, and the
Timer/Counters start counting simultaneously.
88
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit6 – ICPSEL1: Timer 1 Input Capture selection
Timer 1 capture function has two possible inputs ICP1A (PD4) and ICP1B (PC3). The selection
is made thanks to ICPSEL1 bit as described in Table 11-1.
Table 11-1.
ICPSEL1
ICPSEL1
Description
0
Select ICP1A as trigger for timer 1 input capture
1
Select ICP1B as trigger for timer 1 input capture
• Bit 0 – PSRSYNC: Prescaler Reset
When this bit is one, Timer/Counter1 and Timer/Counter0 prescaler will be Reset. This bit is normally cleared immediately by hardware, except if the TSM bit is set. Note that Timer/Counter1
and Timer/Counter0 share the same prescaler and a reset of this prescaler will affect both
timers.
89
7647F–AVR–04/09
12. 8-bit Timer/Counter0 with PWM
Timer/Counter0 is a general purpose 8-bit Timer/Counter module, with two independent Output
Compare Units, and with PWM support. It allows accurate program execution timing (event management) and wave generation. The main features are:
•
•
•
•
•
•
•
12.1
Two Independent Output Compare Units
Double Buffered Output Compare Registers
Clear Timer on Compare Match (Auto Reload)
Glitch Free, Phase Correct Pulse Width Modulator (PWM)
Variable PWM Period
Frequency Generator
Three Independent Interrupt Sources (TOV0, OCF0A, and OCF0B)
Overview
A simplified block diagram of the 8-bit Timer/Counter is shown in Figure 12-1. For the actual
placement of I/O pins, refer to “Pin Descriptions” on page 10. CPU accessible I/O Registers,
including I/O bits and I/O pins, are shown in bold. The device-specific I/O Register and bit locations are listed in the “8-bit Timer/Counter Register Description” on page 101.
The PRTIM0 bit in “Power Reduction Register” on page 42 must be written to zero to enable
Timer/Counter0 module.
Figure 12-1. 8-bit Timer/Counter Block Diagram
count
TOVn
(Int.Req.)
clear
Control Logic
direction
clk Tn
Clock Select
Edge
Detector
DATA BUS
TOP
Tn
BOTTOM
( From Prescaler )
Timer/Counter
TCNTn
=
=0
OCnA
(Int.Req.)
Waveform
Generation
=
OCRnx
OCnB
(Int.Req.)
Fixed
TOP
Values
=
OCnA
Waveform
Generation
OCnB
OCRnx
TCCRnA
12.1.1
TCCRnB
Definitions
Many register and bit references in this section are written in general form. A lower case “n”
replaces the Timer/Counter number, in this case 0. A lower case “x” replaces the Output Compare Unit, in this case Compare Unit A or Compare Unit B. However, when using the register or
bit defines in a program, the precise form must be used, i.e., TCNT0 for accessing
Timer/Counter0 counter value and so on.
90
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The definitions in Table 12-1 are also used extensively throughout the document.
Table 12-1.
12.1.2
Definitions
BOTTOM
The counter reaches the BOTTOM when it becomes 0x00.
MAX
The counter reaches its MAXimum when it becomes 0xFF (decimal 255).
TOP
The counter reaches the TOP when it becomes equal to the highest value in the
count sequence. The TOP value can be assigned to be the fixed value 0xFF
(MAX) or the value stored in the OCR0A Register. The assignment is dependent on the mode of operation.
Registers
The Timer/Counter (TCNT0) and Output Compare Registers (OCR0A and OCR0B) are 8-bit
registers. Interrupt request (abbreviated to Int.Req. in the figure) signals are all visible in the
Timer Interrupt Flag Register (TIFR0). All interrupts are individually masked with the Timer Interrupt Mask Register (TIMSK0). TIFR0 and TIMSK0 are not shown in the figure.
The Timer/Counter can be clocked internally, via the prescaler, or by an external clock source on
the T0 pin. The Clock Select logic block controls which clock source and edge the Timer/Counter
uses to increment (or decrement) its value. The Timer/Counter is inactive when no clock source
is selected. The output from the Clock Select logic is referred to as the timer clock (clkT0).
The double buffered Output Compare Registers (OCR0A and OCR0B) are compared with the
Timer/Counter value at all times. The result of the compare can be used by the Waveform Generator to generate a PWM or variable frequency output on the Output Compare pins (OC0A and
OC0B). See “Using the Output Compare Unit” on page 118. for details. The compare match
event will also set the Compare Flag (OCF0A or OCF0B) which can be used to generate an Output Compare interrupt request.
12.2
Timer/Counter Clock Sources
The Timer/Counter can be clocked by an internal or an external clock source. The clock source
is selected by the Clock Select logic which is controlled by the Clock Select (CS02:0) bits
located in the Timer/Counter Control Register (TCCR0B). For details on clock sources and prescaler, see “Timer/Counter0 and Timer/Counter1 Prescalers” on page 87.
12.3
Counter Unit
The main part of the 8-bit Timer/Counter is the programmable bi-directional counter unit. Figure
12-2 shows a block diagram of the counter and its surroundings.
Figure 12-2. Counter Unit Block Diagram
TOVn
(Int.Req.)
DATA BUS
Clock Select
count
TCNTn
clear
Control Logic
clkTn
Edge
Detector
Tn
direction
( From Prescaler )
bottom
top
91
7647F–AVR–04/09
Signal description (internal signals):
count
Increment or decrement TCNT0 by 1.
direction
Select between increment and decrement.
clear
Clear TCNT0 (set all bits to zero).
clkTn
Timer/Counter clock, referred to as clkT0 in the following.
top
Signalize that TCNT0 has reached maximum value.
bottom
Signalize that TCNT0 has reached minimum value (zero).
Depending of the mode of operation used, the counter is cleared, incremented, or decremented
at each timer clock (clkT0). clkT0 can be generated from an external or internal clock source,
selected by the Clock Select bits (CS02:0). When no clock source is selected (CS02:0 = 0) the
timer is stopped. However, the TCNT0 value can be accessed by the CPU, regardless of
whether clkT0 is present or not. A CPU write overrides (has priority over) all counter clear or
count operations.
The counting sequence is determined by the setting of the WGM01 and WGM00 bits located in
the Timer/Counter Control Register (TCCR0A) and the WGM02 bit located in the Timer/Counter
Control Register B (TCCR0B). There are close connections between how the counter behaves
(counts) and how waveforms are generated on the Output Compare outputs OC0A and OC0B.
For more details about advanced counting sequences and waveform generation, see “Modes of
Operation” on page 95.
The Timer/Counter Overflow Flag (TOV0) is set according to the mode of operation selected by
the WGM02:0 bits. TOV0 can be used for generating a CPU interrupt.
12.4
Output Compare Unit
The 8-bit comparator continuously compares TCNT0 with the Output Compare Registers
(OCR0A and OCR0B). Whenever TCNT0 equals OCR0A or OCR0B, the comparator signals a
match. A match will set the Output Compare Flag (OCF0A or OCF0B) at the next timer clock
cycle. If the corresponding interrupt is enabled, the Output Compare Flag generates an Output
Compare interrupt. The Output Compare Flag is automatically cleared when the interrupt is executed. Alternatively, the flag can be cleared by software by writing a logical one to its I/O bit
location. The Waveform Generator uses the match signal to generate an output according to
operating mode set by the WGM02:0 bits and Compare Output mode (COM0x1:0) bits. The max
and bottom signals are used by the Waveform Generator for handling the special cases of the
extreme values in some modes of operation (“Modes of Operation” on page 95).
Figure 12-3 shows a block diagram of the Output Compare unit.
92
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 12-3. Output Compare Unit, Block Diagram
DATA BUS
OCRnx
TCNTn
= (8-bit Comparator )
OCFnx (Int.Req.)
top
bottom
Waveform Generator
OCnx
FOCn
WGMn1:0
COMnx1:0
The OCR0x Registers are double buffered when using any of the Pulse Width Modulation
(PWM) modes. For the normal and Clear Timer on Compare (CTC) modes of operation, the double buffering is disabled. The double buffering synchronizes the update of the OCR0x Compare
Registers to either top or bottom of the counting sequence. The synchronization prevents the
occurrence of odd-length, non-symmetrical PWM pulses, thereby making the output glitch-free.
The OCR0x Register access may seem complex, but this is not case. When the double buffering
is enabled, the CPU has access to the OCR0x Buffer Register, and if double buffering is disabled the CPU will access the OCR0x directly.
12.4.1
Force Output Compare
In non-PWM waveform generation modes, the match output of the comparator can be forced by
writing a one to the Force Output Compare (FOC0x) bit. Forcing compare match will not set the
OCF0x Flag or reload/clear the timer, but the OC0x pin will be updated as if a real compare
match had occurred (the COM0x1:0 bits settings define whether the OC0x pin is set, cleared or
toggled).
12.4.2
Compare Match Blocking by TCNT0 Write
All CPU write operations to the TCNT0 Register will block any compare match that occur in the
next timer clock cycle, even when the timer is stopped. This feature allows OCR0x to be initialized to the same value as TCNT0 without triggering an interrupt when the Timer/Counter clock is
enabled.
12.4.3
Using the Output Compare Unit
Since writing TCNT0 in any mode of operation will block all compare matches for one timer clock
cycle, there are risks involved when changing TCNT0 when using the Output Compare Unit,
independently of whether the Timer/Counter is running or not. If the value written to TCNT0
equals the OCR0x value, the compare match will be missed, resulting in incorrect waveform
generation. Similarly, do not write the TCNT0 value equal to BOTTOM when the counter is
downcounting.
93
7647F–AVR–04/09
The setup of the OC0x should be performed before setting the Data Direction Register for the
port pin to output. The easiest way of setting the OC0x value is to use the Force Output Compare (FOC0x) strobe bits in Normal mode. The OC0x Registers keep their values even when
changing between Waveform Generation modes.
Be aware that the COM0x1:0 bits are not double buffered together with the compare value.
Changing the COM0x1:0 bits will take effect immediately.
12.5
Compare Match Output Unit
The Compare Output mode (COM0x1:0) bits have two functions. The Waveform Generator uses
the COM0x1:0 bits for defining the Output Compare (OC0x) state at the next compare match.
Also, the COM0x1:0 bits control the OC0x pin output source. Figure 12-4 shows a simplified
schematic of the logic affected by the COM0x1:0 bit setting. The I/O Registers, I/O bits, and I/O
pins in the figure are shown in bold. Only the parts of the general I/O port control registers (DDR
and PORT) that are affected by the COM0x1:0 bits are shown. When referring to the OC0x
state, the reference is for the internal OC0x Register, not the OC0x pin. If a system reset occur,
the OC0x Register is reset to “0”.
Figure 12-4. Compare Match Output Unit, Schematic
COMnx1
COMnx0
FOCn
Waveform
Generator
D
Q
1
OCnx
DATA BUS
D
0
OCnx
Pin
Q
PORT
D
Q
DDR
clk I/O
The general I/O port function is overridden by the Output Compare (OC0x) from the Waveform
Generator if either of the COM0x1:0 bits are set. However, the OC0x pin direction (input or output) is still controlled by the Data Direction Register (DDR) for the port pin. The Data Direction
Register bit for the OC0x pin (DDR_OC0x) must be set as output before the OC0x value is visible on the pin. The port override function is independent of the Waveform Generation mode.
The design of the Output Compare pin logic allows initialization of the OC0x state before the output is enabled. Note that some COM0x1:0 bit settings are reserved for certain modes of
operation. See “8-bit Timer/Counter Register Description” on page 101.
94
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
12.5.1
Compare Output Mode and Waveform Generation
The Waveform Generator uses the COM0x1:0 bits differently in Normal, CTC, and PWM modes.
For all modes, setting the COM0x1:0 = 0 tells the Waveform Generator that no action on the
OC0x Register is to be performed on the next compare match. For compare output actions in the
non-PWM modes refer to Table 12-2 on page 101. For fast PWM mode, refer to Table 12-3 on
page 101, and for phase correct PWM refer to Table 12-4 on page 102.
A change of the COM0x1:0 bits state will have effect at the first compare match after the bits are
written. For non-PWM modes, the action can be forced to have immediate effect by using the
FOC0x strobe bits.
12.6
Modes of Operation
The mode of operation, i.e., the behavior of the Timer/Counter and the Output Compare pins, is
defined by the combination of the Waveform Generation mode (WGM02:0) and Compare Output
mode (COM0x1:0) bits. The Compare Output mode bits do not affect the counting sequence,
while the Waveform Generation mode bits do. The COM0x1:0 bits control whether the PWM output generated should be inverted or not (inverted or non-inverted PWM). For non-PWM modes
the COM0x1:0 bits control whether the output should be set, cleared, or toggled at a compare
match (See “Compare Match Output Unit” on page 94.).
For detailed timing information refer to “Timer/Counter Timing Diagrams” on page 99.
12.6.1
Normal Mode
The simplest mode of operation is the Normal mode (WGM02:0 = 0). In this mode the counting
direction is always up (incrementing), and no counter clear is performed. The counter simply
overruns when it passes its maximum 8-bit value (TOP = 0xFF) and then restarts from the bottom (0x00). In normal operation the Timer/Counter Overflow Flag (TOV0) will be set in the same
timer clock cycle as the TCNT0 becomes zero. The TOV0 Flag in this case behaves like a ninth
bit, except that it is only set, not cleared. However, combined with the timer overflow interrupt
that automatically clears the TOV0 Flag, the timer resolution can be increased by software.
There are no special cases to consider in the Normal mode, a new counter value can be written
anytime.
The Output Compare unit can be used to generate interrupts at some given time. Using the Output Compare to generate waveforms in Normal mode is not recommended, since this will
occupy too much of the CPU time.
12.6.2
Clear Timer on Compare Match (CTC) Mode
In Clear Timer on Compare or CTC mode (WGM02:0 = 2), the OCR0A Register is used to
manipulate the counter resolution. In CTC mode the counter is cleared to zero when the counter
value (TCNT0) matches the OCR0A. The OCR0A defines the top value for the counter, hence
also its resolution. This mode allows greater control of the compare match output frequency. It
also simplifies the operation of counting external events.
The timing diagram for the CTC mode is shown in Figure 12-5. The counter value (TCNT0)
increases until a compare match occurs between TCNT0 and OCR0A, and then counter
(TCNT0) is cleared.
95
7647F–AVR–04/09
Figure 12-5. CTC Mode, Timing Diagram
OCnx Interrupt Flag Set
TCNTn
OCn
(Toggle)
Period
(COMnx1:0 = 1)
1
2
3
4
An interrupt can be generated each time the counter value reaches the TOP value by using the
OCF0A Flag. If the interrupt is enabled, the interrupt handler routine can be used for updating
the TOP value. However, changing TOP to a value close to BOTTOM when the counter is running with none or a low prescaler value must be done with care since the CTC mode does not
have the double buffering feature. If the new value written to OCR0A is lower than the current
value of TCNT0, the counter will miss the compare match. The counter will then have to count to
its maximum value (0xFF) and wrap around starting at 0x00 before the compare match can
occur.
For generating a waveform output in CTC mode, the OC0A output can be set to toggle its logical
level on each compare match by setting the Compare Output mode bits to toggle mode
(COM0A1:0 = 1). The OC0A value will not be visible on the port pin unless the data direction for
the pin is set to output. The waveform generated will have a maximum frequency of fOC0 =
fclk_I/O/2 when OCR0A is set to zero (0x00). The waveform frequency is defined by the following
equation:
f clk_I/O
f OCnx = -----------------------------------------------------2 ⋅ N ⋅ ( 1 + OCRnx )
The N variable represents the prescale factor (1, 8, 64, 256, or 1024).
As for the Normal mode of operation, the TOV0 Flag is set in the same timer clock cycle that the
counter counts from MAX to 0x00.
12.6.3
96
Fast PWM Mode
The fast Pulse Width Modulation or fast PWM mode (WGM02:0 = 3 or 7) provides a high frequency PWM waveform generation option. The fast PWM differs from the other PWM option by
its single-slope operation. The counter counts from BOTTOM to TOP then restarts from BOTTOM. TOP is defined as 0xFF when WGM2:0 = 3, and OCR0A when WGM2:0 = 7. In
non-inverting Compare Output mode, the Output Compare (OC0x) is cleared on the compare
match between TCNT0 and OCR0x, and set at BOTTOM. In inverting Compare Output mode,
the output is set on compare match and cleared at BOTTOM. Due to the single-slope operation,
the operating frequency of the fast PWM mode can be twice as high as the phase correct PWM
mode that use dual-slope operation. This high frequency makes the fast PWM mode well suited
for power regulation, rectification, and DAC applications. High frequency allows physically small
sized external components (coils, capacitors), and therefore reduces total system cost.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
In fast PWM mode, the counter is incremented until the counter value matches the TOP value.
The counter is then cleared at the following timer clock cycle. The timing diagram for the fast
PWM mode is shown in Figure 12-6. The TCNT0 value is in the timing diagram shown as a histogram for illustrating the single-slope operation. The diagram includes non-inverted and
inverted PWM outputs. The small horizontal line marks on the TCNT0 slopes represent compare
matches between OCR0x and TCNT0.
Figure 12-6. Fast PWM Mode, Timing Diagram
OCRnx Interrupt Flag Set
OCRnx Update and
TOVn Interrupt Flag Set
TCNTn
OCn
(COMnx1:0 = 2)
OCn
(COMnx1:0 = 3)
Period
1
2
3
4
5
6
7
The Timer/Counter Overflow Flag (TOV0) is set each time the counter reaches TOP. If the interrupt is enabled, the interrupt handler routine can be used for updating the compare value.
In fast PWM mode, the compare unit allows generation of PWM waveforms on the OC0x pins.
Setting the COM0x1:0 bits to two will produce a non-inverted PWM and an inverted PWM output
can be generated by setting the COM0x1:0 to three: Setting the COM0A1:0 bits to one allows
the OC0A pin to toggle on Compare Matches if the WGM02 bit is set. This option is not available
for the OC0B pin (see Table 12-6 on page 102). The actual OC0x value will only be visible on
the port pin if the data direction for the port pin is set as output. The PWM waveform is generated by setting (or clearing) the OC0x Register at the compare match between OCR0x and
TCNT0, and clearing (or setting) the OC0x Register at the timer clock cycle the counter is
cleared (changes from TOP to BOTTOM).
The PWM frequency for the output can be calculated by the following equation:
f clk_I/O
f OCnxPWM = -------------------N ⋅ 256
The N variable represents the prescale factor (1, 8, 64, 256, or 1024).
The extreme values for the OCR0A Register represents special cases when generating a PWM
waveform output in the fast PWM mode. If the OCR0A is set equal to BOTTOM, the output will
be a narrow spike for each MAX+1 timer clock cycle. Setting the OCR0A equal to MAX will result
in a constantly high or low output (depending on the polarity of the output set by the COM0A1:0
bits.)
97
7647F–AVR–04/09
A frequency (with 50% duty cycle) waveform output in fast PWM mode can be achieved by setting OC0x to toggle its logical level on each compare match (COM0x1:0 = 1). The waveform
generated will have a maximum frequency of fOC0 = fclk_I/O/2 when OCR0A is set to zero. This
feature is similar to the OC0A toggle in CTC mode, except the double buffer feature of the Output Compare unit is enabled in the fast PWM mode.
12.6.4
Phase Correct PWM Mode
The phase correct PWM mode (WGM02:0 = 1 or 5) provides a high resolution phase correct
PWM waveform generation option. The phase correct PWM mode is based on a dual-slope
operation. The counter counts repeatedly from BOTTOM to TOP and then from TOP to BOTTOM. TOP is defined as 0xFF when WGM2:0 = 1, and OCR0A when WGM2:0 = 5. In
non-inverting Compare Output mode, the Output Compare (OC0x) is cleared on the compare
match between TCNT0 and OCR0x while upcounting, and set on the compare match while
downcounting. In inverting Output Compare mode, the operation is inverted. The dual-slope
operation has lower maximum operation frequency than single slope operation. However, due to
the symmetric feature of the dual-slope PWM modes, these modes are preferred for motor control applications.
In phase correct PWM mode the counter is incremented until the counter value matches TOP.
When the counter reaches TOP, it changes the count direction. The TCNT0 value will be equal
to TOP for one timer clock cycle. The timing diagram for the phase correct PWM mode is shown
on Figure 12-7. The TCNT0 value is in the timing diagram shown as a histogram for illustrating
the dual-slope operation. The diagram includes non-inverted and inverted PWM outputs. The
small horizontal line marks on the TCNT0 slopes represent compare matches between OCR0x
and TCNT0.
Figure 12-7. Phase Correct PWM Mode, Timing Diagram
OCnx Interrupt Flag Set
OCRnx Update
TOVn Interrupt Flag Set
TCNTn
OCnx
(COMnx1:0 = 2)
OCnx
(COMnx1:0 = 3)
Period
1
2
3
The Timer/Counter Overflow Flag (TOV0) is set each time the counter reaches BOTTOM. The
Interrupt Flag can be used to generate an interrupt each time the counter reaches the BOTTOM
value.
98
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
In phase correct PWM mode, the compare unit allows generation of PWM waveforms on the
OC0x pins. Setting the COM0x1:0 bits to two will produce a non-inverted PWM. An inverted
PWM output can be generated by setting the COM0x1:0 to three: Setting the COM0A0 bits to
one allows the OC0A pin to toggle on Compare Matches if the WGM02 bit is set. This option is
not available for the OC0B pin (see Table 12-7 on page 103). The actual OC0x value will only be
visible on the port pin if the data direction for the port pin is set as output. The PWM waveform is
generated by clearing (or setting) the OC0x Register at the compare match between OCR0x and
TCNT0 when the counter increments, and setting (or clearing) the OC0x Register at compare
match between OCR0x and TCNT0 when the counter decrements. The PWM frequency for the
output when using phase correct PWM can be calculated by the following equation:
f clk_I/O
f OCnxPCPWM = -------------------N ⋅ 510
The N variable represents the prescale factor (1, 8, 64, 256, or 1024).
The extreme values for the OCR0A Register represent special cases when generating a PWM
waveform output in the phase correct PWM mode. If the OCR0A is set equal to BOTTOM, the
output will be continuously low and if set equal to MAX the output will be continuously high for
non-inverted PWM mode. For inverted PWM the output will have the opposite logic values.
At the very start of period 2 in Figure 12-7 OCnx has a transition from high to low even though
there is no Compare Match. The point of this transition is to guarantee symmetry around BOTTOM. There are two cases that give a transition without Compare Match.
• OCRnx changes its value from MAX, like in Figure 12-7. When the OCR0A value is MAX the
OCn pin value is the same as the result of a down-counting Compare Match. To ensure
symmetry around BOTTOM the OCnx value at MAX must correspond to the result of an
up-counting Compare Match.
• The timer starts counting from a value higher than the one in OCRnx, and for that reason
misses the Compare Match and hence the OCnx change that would have happened on the
way up.
12.7
Timer/Counter Timing Diagrams
The Timer/Counter is a synchronous design and the timer clock (clkT0) is therefore shown as a
clock enable signal in the following figures. The figures include information on when interrupt
flags are set. Figure 12-8 contains timing data for basic Timer/Counter operation. The figure
shows the count sequence close to the MAX value in all modes other than phase correct PWM
mode.
Figure 12-8. Timer/Counter Timing Diagram, no Prescaling
clkI/O
clkTn
(clkI/O /1)
TCNTn
MAX - 1
MAX
BOTTOM
BOTTOM + 1
TOVn
99
7647F–AVR–04/09
Figure 12-9 shows the same timing data, but with the prescaler enabled.
Figure 12-9. Timer/Counter Timing Diagram, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
TCNTn
MAX - 1
MAX
BOTTOM
BOTTOM + 1
TOVn
Figure 12-10 shows the setting of OCF0B in all modes and OCF0A in all modes except CTC
mode and PWM mode, where OCR0A is TOP.
Figure 12-10. Timer/Counter Timing Diagram, Setting of OCF0x, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
TCNTn
OCRnx - 1
OCRnx
OCRnx + 1
OCRnx + 2
OCRnx Value
OCRnx
OCFnx
Figure 12-11 shows the setting of OCF0A and the clearing of TCNT0 in CTC mode and fast
PWM mode where OCR0A is TOP.
Figure 12-11. Timer/Counter Timing Diagram, Clear Timer on Compare Match mode, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
TCNTn
(CTC)
TOP - 1
OCRnx
TOP
BOTTOM
BOTTOM + 1
TOP
OCFnx
100
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
12.8
8-bit Timer/Counter Register Description
12.8.1
Timer/Counter Control Register A – TCCR0A
Bit
7
6
5
4
3
2
1
0
COM0A1
COM0A0
COM0B1
COM0B0
–
–
WGM01
WGM00
Read/Write
R/W
R/W
R/W
R/W
R
R
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TCCR0A
• Bits 7:6 – COM0A1:0: Compare Match Output A Mode
These bits control the Output Compare pin (OC0A) behavior. If one or both of the COM0A1:0
bits are set, the OC0A output overrides the normal port functionality of the I/O pin it is connected
to. However, note that the Data Direction Register (DDR) bit corresponding to the OC0A pin
must be set in order to enable the output driver.
When OC0A is connected to the pin, the function of the COM0A1:0 bits depends on the
WGM02:0 bit setting. Table 12-2 shows the COM0A1:0 bit functionality when the WGM02:0 bits
are set to a normal or CTC mode (non-PWM).
Table 12-2.
Compare Output Mode, non-PWM Mode
COM0A1
COM0A0
Description
0
0
Normal port operation, OC0A disconnected.
0
1
Toggle OC0A on Compare Match
1
0
Clear OC0A on Compare Match
1
1
Set OC0A on Compare Match
Table 12-3 shows the COM0A1:0 bit functionality when the WGM01:0 bits are set to fast PWM
mode.
Table 12-3.
Compare Output Mode, Fast PWM Mode(1)
COM0A1
COM0A0
0
0
Normal port operation, OC0A disconnected.
0
1
WGM02 = 0: Normal Port Operation, OC0A Disconnected.
WGM02 = 1: Toggle OC0A on Compare Match.
1
0
Clear OC0A on Compare Match, set OC0A at TOP
1
1
Set OC0A on Compare Match, clear OC0A at TOP
Note:
Description
1. A special case occurs when OCR0A equals TOP and COM0A1 is set. In this case, the Compare Match is ignored, but the set or clear is done at TOP. See “Fast PWM Mode” on page 96
for more details.
101
7647F–AVR–04/09
Table 12-4 shows the COM0A1:0 bit functionality when the WGM02:0 bits are set to phase correct PWM mode.
Table 12-4.
Compare Output Mode, Phase Correct PWM Mode(1)
COM0A1
COM0A0
0
0
Normal port operation, OC0A disconnected.
0
1
WGM02 = 0: Normal Port Operation, OC0A Disconnected.
WGM02 = 1: Toggle OC0A on Compare Match.
1
0
Clear OC0A on Compare Match when up-counting. Set OC0A on
Compare Match when down-counting.
1
1
Set OC0A on Compare Match when up-counting. Clear OC0A on
Compare Match when down-counting.
Note:
Description
1. A special case occurs when OCR0A equals TOP and COM0A1 is set. In this case, the Compare Match is ignored, but the set or clear is done at TOP. See “Phase Correct PWM Mode” on
page 123 for more details.
• Bits 5:4 – COM0B1:0: Compare Match Output B Mode
These bits control the Output Compare pin (OC0B) behavior. If one or both of the COM0B1:0
bits are set, the OC0B output overrides the normal port functionality of the I/O pin it is connected
to. However, note that the Data Direction Register (DDR) bit corresponding to the OC0B pin
must be set in order to enable the output driver.
When OC0B is connected to the pin, the function of the COM0B1:0 bits depends on the
WGM02:0 bit setting. Table 12-5 shows the COM0B1:0 bit functionality when the WGM02:0 bits
are set to a normal or CTC mode (non-PWM).
Table 12-5.
Compare Output Mode, non-PWM Mode
COM0B1
COM0B0
Description
0
0
Normal port operation, OC0B disconnected.
0
1
Toggle OC0B on Compare Match
1
0
Clear OC0B on Compare Match
1
1
Set OC0B on Compare Match
Table 12-6 shows the COM0B1:0 bit functionality when the WGM02:0 bits are set to fast PWM
mode.
Table 12-6.
COM0B1
COM0B0
0
0
Normal port operation, OC0B disconnected.
0
1
Reserved
1
0
Clear OC0B on Compare Match, set OC0B at TOP
1
1
Set OC0B on Compare Match, clear OC0B at TOP
Note:
102
Compare Output Mode, Fast PWM Mode(1)
Description
1. A special case occurs when OCR0B equals TOP and COM0B1 is set. In this case, the Compare Match is ignored, but the set or clear is done at TOP. See “Fast PWM Mode” on page 96
for more details.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 12-7 shows the COM0B1:0 bit functionality when the WGM02:0 bits are set to phase correct PWM mode.
Table 12-7.
Compare Output Mode, Phase Correct PWM Mode(1)
COM0B1
COM0B0
0
0
Normal port operation, OC0B disconnected.
0
1
Reserved
1
0
Clear OC0B on Compare Match when up-counting. Set OC0B on
Compare Match when down-counting.
1
1
Set OC0B on Compare Match when up-counting. Clear OC0B on
Compare Match when down-counting.
Note:
Description
1. A special case occurs when OCR0B equals TOP and COM0B1 is set. In this case, the Compare Match is ignored, but the set or clear is done at TOP. See “Phase Correct PWM Mode” on
page 98 for more details.
• Bits 3, 2 – Res: Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and will always read as zero.
• Bits 1:0 – WGM01:0: Waveform Generation Mode
Combined with the WGM02 bit found in the TCCR0B Register, these bits control the counting
sequence of the counter, the source for maximum (TOP) counter value, and what type of waveform generation to be used, see Table 12-8. Modes of operation supported by the Timer/Counter
unit are: Normal mode (counter), Clear Timer on Compare Match (CTC) mode, and two types of
Pulse Width Modulation (PWM) modes (see “Modes of Operation” on page 95).
Table 12-8.
Waveform Generation Mode Bit Description
Timer/Counter
Mode of
Operation
TOP
Update of
OCRx at
TOV Flag
Set on(1)(2)
Mode
WGM02
WGM01
WGM00
0
0
0
0
Normal
0xFF
Immediate
MAX
1
0
0
1
PWM, Phase
Correct
0xFF
TOP
BOTTOM
2
0
1
0
CTC
OCRA
Immediate
MAX
3
0
1
1
Fast PWM
0xFF
TOP
MAX
4
1
0
0
Reserved
–
–
–
5
1
0
1
PWM, Phase
Correct
OCRA
TOP
BOTTOM
6
1
1
0
Reserved
–
–
–
7
1
1
1
Fast PWM
OCRA
TOP
TOP
Notes:
1. MAX
= 0xFF
2. BOTTOM = 0x00
103
7647F–AVR–04/09
12.8.2
Timer/Counter Control Register B – TCCR0B
Bit
7
6
5
4
3
2
1
0
FOC0A
FOC0B
–
–
WGM02
CS02
CS01
CS00
Read/Write
W
W
R
R
R
R
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TCCR0B
• Bit 7 – FOC0A: Force Output Compare A
The FOC0A bit is only active when the WGM bits specify a non-PWM mode.
However, for ensuring compatibility with future devices, this bit must be set to zero when
TCCR0B is written when operating in PWM mode. When writing a logical one to the FOC0A bit,
an immediate Compare Match is forced on the Waveform Generation unit. The OC0A output is
changed according to its COM0A1:0 bits setting. Note that the FOC0A bit is implemented as a
strobe. Therefore it is the value present in the COM0A1:0 bits that determines the effect of the
forced compare.
A FOC0A strobe will not generate any interrupt, nor will it clear the timer in CTC mode using
OCR0A as TOP.
The FOC0A bit is always read as zero.
• Bit 6 – FOC0B: Force Output Compare B
The FOC0B bit is only active when the WGM bits specify a non-PWM mode.
However, for ensuring compatibility with future devices, this bit must be set to zero when
TCCR0B is written when operating in PWM mode. When writing a logical one to the FOC0B bit,
an immediate Compare Match is forced on the Waveform Generation unit. The OC0B output is
changed according to its COM0B1:0 bits setting. Note that the FOC0B bit is implemented as a
strobe. Therefore it is the value present in the COM0B1:0 bits that determines the effect of the
forced compare.
A FOC0B strobe will not generate any interrupt, nor will it clear the timer in CTC mode using
OCR0B as TOP.
The FOC0B bit is always read as zero.
• Bits 5:4 – Res: Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and will always read as zero.
• Bit 3 – WGM02: Waveform Generation Mode
See the description in the “Timer/Counter Control Register A – TCCR0A” on page 101.
• Bits 2:0 – CS02:0: Clock Select
The three Clock Select bits select the clock source to be used by the Timer/Counter.
Table 12-9.
104
Clock Select Bit Description
CS02
CS01
CS00
0
0
0
No clock source (Timer/Counter stopped)
Description
0
0
1
clkI/O/(No prescaling)
0
1
0
clkI/O/8 (From prescaler)
0
1
1
clkI/O/64 (From prescaler)
1
0
0
clkI/O/256 (From prescaler)
1
0
1
clkI/O/1024 (From prescaler)
1
1
0
External clock source on T0 pin. Clock on falling edge.
1
1
1
External clock source on T0 pin. Clock on rising edge.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
If external pin modes are used for the Timer/Counter0, transitions on the T0 pin will clock the
counter even if the pin is configured as an output. This feature allows software control of the
counting.
12.8.3
Timer/Counter Register – TCNT0
Bit
7
6
5
4
3
2
1
0
TCNT0[7:0]
TCNT0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
The Timer/Counter Register gives direct access, both for read and write operations, to the
Timer/Counter unit 8-bit counter. Writing to the TCNT0 Register blocks (removes) the Compare
Match on the following timer clock. Modifying the counter (TCNT0) while the counter is running,
introduces a risk of missing a Compare Match between TCNT0 and the OCR0x Registers.
12.8.4
Output Compare Register A – OCR0A
Bit
7
6
5
4
3
2
1
0
OCR0A[7:0]
OCR0A
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
The Output Compare Register A contains an 8-bit value that is continuously compared with the
counter value (TCNT0). A match can be used to generate an Output Compare interrupt, or to
generate a waveform output on the OC0A pin.
12.8.5
Output Compare Register B – OCR0B
Bit
7
6
5
4
3
2
1
0
OCR0B[7:0]
OCR0B
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
The Output Compare Register B contains an 8-bit value that is continuously compared with the
counter value (TCNT0). A match can be used to generate an Output Compare interrupt, or to
generate a waveform output on the OC0B pin.
12.8.6
Timer/Counter Interrupt Mask Register – TIMSK0
Bit
7
6
5
4
3
2
1
0
–
–
–
–
–
OCIE0B
OCIE0A
TOIE0
Read/Write
R
R
R
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TIMSK0
• Bits 7..3 – Res: Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and will always read as zero.
• Bit 2 – OCIE0B: Timer/Counter Output Compare Match B Interrupt Enable
When the OCIE0B bit is written to one, and the I-bit in the Status Register is set, the
Timer/Counter Compare Match B interrupt is enabled. The corresponding interrupt is executed if
a Compare Match in Timer/Counter occurs, i.e., when the OCF0B bit is set in the Timer/Counter
Interrupt Flag Register – TIFR0.
105
7647F–AVR–04/09
• Bit 1 – OCIE0A: Timer/Counter0 Output Compare Match A Interrupt Enable
When the OCIE0A bit is written to one, and the I-bit in the Status Register is set, the
Timer/Counter0 Compare Match A interrupt is enabled. The corresponding interrupt is executed
if a Compare Match in Timer/Counter0 occurs, i.e., when the OCF0A bit is set in the
Timer/Counter 0 Interrupt Flag Register – TIFR0.
• Bit 0 – TOIE0: Timer/Counter0 Overflow Interrupt Enable
When the TOIE0 bit is written to one, and the I-bit in the Status Register is set, the
Timer/Counter0 Overflow interrupt is enabled. The corresponding interrupt is executed if an
overflow in Timer/Counter0 occurs, i.e., when the TOV0 bit is set in the Timer/Counter 0 Interrupt Flag Register – TIFR0.
12.8.7
Timer/Counter 0 Interrupt Flag Register – TIFR0
Bit
7
6
5
4
3
2
1
0
–
–
–
–
–
OCF0B
OCF0A
TOV0
Read/Write
R
R
R
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TIFR0
• Bits 7..3 – Res: Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and will always read as zero.
• Bit 2 – OCF0B: Timer/Counter 0 Output Compare B Match Flag
The OCF0B bit is set when a Compare Match occurs between the Timer/Counter and the data in
OCR0B – Output Compare Register0 B. OCF0B is cleared by hardware when executing the corresponding interrupt handling vector. Alternatively, OCF0B is cleared by writing a logic one to
the flag. When the I-bit in SREG, OCIE0B (Timer/Counter Compare B Match Interrupt Enable),
and OCF0B are set, the Timer/Counter Compare Match Interrupt is executed.
• Bit 1 – OCF0A: Timer/Counter 0 Output Compare A Match Flag
The OCF0A bit is set when a Compare Match occurs between the Timer/Counter0 and the data
in OCR0A – Output Compare Register0. OCF0A is cleared by hardware when executing the corresponding interrupt handling vector. Alternatively, OCF0A is cleared by writing a logic one to
the flag. When the I-bit in SREG, OCIE0A (Timer/Counter0 Compare Match Interrupt Enable),
and OCF0A are set, the Timer/Counter0 Compare Match Interrupt is executed.
• Bit 0 – TOV0: Timer/Counter0 Overflow Flag
The bit TOV0 is set when an overflow occurs in Timer/Counter0. TOV0 is cleared by hardware
when executing the corresponding interrupt handling vector. Alternatively, TOV0 is cleared by
writing a logic one to the flag. When the SREG I-bit, TOIE0 (Timer/Counter0 Overflow Interrupt
Enable), and TOV0 are set, the Timer/Counter0 Overflow interrupt is executed.
The setting of this flag is dependent of the WGM02:0 bit setting. Refer to Table 12-8, “Waveform
Generation Mode Bit Description” on page 103.
106
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
13. 16-bit Timer/Counter1 with PWM
The 16-bit Timer/Counter unit allows accurate program execution timing (event management),
wave generation, and signal timing measurement. The main features are:
•
•
•
•
•
•
•
•
•
•
•
•
13.1
True 16-bit Design (i.e., Allows 16-bit PWM)
Two independent Output Compare Units
Double Buffered Output Compare Registers
One Input Capture Unit
Input Capture Noise Canceler
Retriggering Function by External Signal (ICP1A or ICP1B)
Clear Timer on Compare Match (Auto Reload)
Glitch-free, Phase Correct Pulse Width Modulator (PWM)
Variable PWM Period
Frequency Generator
External Event Counter
Four independent interrupt Sources (TOV1, OCF1A, OCF1B, and ICF1)
Overview
Most register and bit references in this section are written in general form. A lower case “n”
replaces the Timer/Counter number, and a lower case “x” replaces the Output Compare unit
channel. However, when using the register or bit defines in a program, the precise form must be
used, i.e., TCNT1 for accessing Timer/Counter1 counter value and so on.
A simplified block diagram of the 16-bit Timer/Counter is shown in Figure 13-1. For the actual
placement of I/O pins, refer to “Pin Descriptions” on page 5. CPU accessible I/O Registers,
including I/O bits and I/O pins, are shown in bold. The device-specific I/O Register and bit locations are listed in the “16-bit Timer/Counter Register Description” on page 130.
The PRTIM1 bit in “Power Reduction Register” on page 42 must be written to zero to enable
Timer/Counter1 module.
107
7647F–AVR–04/09
Figure 13-1. 16-bit Timer/Counter Block Diagram(1)
Count
Clear
Direction
TOVn
(Int.Req.)
Control Logic
Clock Select
clkTn
Edge
Detector
Tn
RTG
TOP
BOTTOM
( From Prescaler )
Timer/Counter
TCNTn
=
=0
OCnA
(Int.Req.)
Waveform
Generation
=
OCnA
DATA BUS
OCRnA
OCnB
(Int.Req.)
Fixed
TOP
Values
Waveform
Generation
=
OCRnB
ICFn (Int.Req.)
ICRn
TCCRnA
Note:
13.1.1
OCnB
Edge
Detector
TCCRnB
Noise
Canceler
AC1ICE
ICPSEL1
ICPnA
0
1
ICPnB
Analog Comparator 1
Interrupt
1. Refer to Table on page 5 for Timer/Counter1 pin placement and description.
Registers
The Timer/Counter (TCNTn), Output Compare Registers (OCRnx), and Input Capture Register
(ICRn) are all 16-bit registers. Special procedures must be followed when accessing the 16-bit
registers. These procedures are described in the section “Accessing 16-bit Registers” on page
109. The Timer/Counter Control Registers (TCCRnx) are 8-bit registers and have no CPU
access restrictions. Interrupt requests (abbreviated to Int.Req. in the figure) signals are all visible
in the Timer Interrupt Flag Register (TIFRn). All interrupts are individually masked with the Timer
Interrupt Mask Register (TIMSKn). TIFRn and TIMSKn are not shown in the figure.
The Timer/Counter can be clocked internally, via the prescaler, or by an external clock source on
the Tn pin. The Clock Select logic block controls which clock source and edge the Timer/Counter
uses to increment (or decrement) its value. The Timer/Counter is inactive when no clock source
is selected. The output from the Clock Select logic is referred to as the timer clock (clkTn).
The double buffered Output Compare Registers (OCRnx) are compared with the Timer/Counter
value at all time. The result of the compare can be used by the Waveform Generator to generate
a PWM or variable frequency output on the Output Compare pin (OCnx). See “Output Compare
Units” on page 116. The compare match event will also set the Compare Match Flag (OCFnx)
which can be used to generate an Output Compare interrupt request.
108
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The Input Capture Register can capture the Timer/Counter value at a given external (edge triggered) event on either the Input Capture pin (ICPn). The Input Capture unit includes a digital
filtering unit (Noise Canceler) for reducing the chance of capturing noise spikes.
The TOP value, or maximum Timer/Counter value, can in some modes of operation be defined
by either the OCRnA Register, the ICRn Register, or by a set of fixed values. When using
OCRnA as TOP value in a PWM mode, the OCRnA Register can not be used for generating a
PWM output. However, the TOP value will in this case be double buffered allowing the TOP
value to be changed in run time. If a fixed TOP value is required, the ICRn Register can be used
as an alternative, freeing the OCRnA to be used as PWM output.
13.1.2
Definitions
The following definitions are used extensively throughout the section:
13.2
BOTTOM
The counter reaches the BOTTOM when it becomes 0x0000.
MAX
The counter reaches its MAXimum when it becomes 0xFFFF (decimal 65535).
TOP
The counter reaches the TOP when it becomes equal to the highest value in the count
sequence. The TOP value can be assigned to be one of the fixed values: 0x00FF, 0x01FF,
or 0x03FF, or to the value stored in the OCRnA or ICRn Register. The assignment is
dependent of the mode of operation.
Accessing 16-bit Registers
The TCNTn, OCRnx, and ICRn are 16-bit registers that can be accessed by the AVR CPU via
the 8-bit data bus. The 16-bit register must be byte accessed using two read or write operations.
Each 16-bit timer has a single 8-bit register for temporary storing of the high byte of the 16-bit
access. The same temporary register is shared between all 16-bit registers within each 16-bit
timer. Accessing the low byte triggers the 16-bit read or write operation. When the low byte of a
16-bit register is written by the CPU, the high byte stored in the temporary register, and the low
byte written are both copied into the 16-bit register in the same clock cycle. When the low byte of
a 16-bit register is read by the CPU, the high byte of the 16-bit register is copied into the temporary register in the same clock cycle as the low byte is read.
Not all 16-bit accesses uses the temporary register for the high byte. Reading the OCRnx 16-bit
registers does not involve using the temporary register.
To do a 16-bit write, the high byte must be written before the low byte. For a 16-bit read, the low
byte must be read before the high byte.
The following code examples show how to access the 16-bit Timer Registers assuming that no
interrupts updates the temporary register. The same principle can be used directly for accessing
the OCRnx and ICRn Registers. Note that when using “C”, the compiler handles the 16-bit
access.
109
7647F–AVR–04/09
Assembly Code Examples(1)
...
; Set TCNTn to 0x01FF
ldi r17,0x01
ldi r16,0xFF
out TCNTnH,r17
out TCNTnL,r16
; Read TCNTn into r17:r16
in r16,TCNTnL
in r17,TCNTnH
...
C Code Examples(1)
unsigned int i;
...
/* Set TCNTn to 0x01FF */
TCNTn = 0x1FF;
/* Read TCNTn into i */
i = TCNTn;
...
Note:
1. The example code assumes that the part specific header file is included.
For I/O Registers located in extended I/O map, “IN”, “OUT”, “SBIS”, “SBIC”, “CBI”, and “SBI”
instructions must be replaced with instructions that allow access to extended I/O. Typically
“LDS” and “STS” combined with “SBRS”, “SBRC”, “SBR”, and “CBR”.
The assembly code example returns the TCNTn value in the r17:r16 register pair.
It is important to notice that accessing 16-bit registers are atomic operations. If an interrupt
occurs between the two instructions accessing the 16-bit register, and the interrupt code
updates the temporary register by accessing the same or any other of the 16-bit Timer Registers, then the result of the access outside the interrupt will be corrupted. Therefore, when both
the main code and the interrupt code update the temporary register, the main code must disable
the interrupts during the 16-bit access.
110
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The following code examples show how to do an atomic read of the TCNTn Register contents.
Reading any of the OCRnx or ICRn Registers can be done by using the same principle.
Assembly Code Example(1)
TIM16_ReadTCNTn:
; Save global interrupt flag
in r18,SREG
; Disable interrupts
cli
; Read TCNTn into r17:r16
in r16,TCNTnL
in r17,TCNTnH
; Restore global interrupt flag
out SREG,r18
ret
C Code Example(1)
unsigned int TIM16_ReadTCNTn( void )
{
unsigned char sreg;
unsigned int i;
/* Save global interrupt flag */
sreg = SREG;
/* Disable interrupts */
_CLI();
/* Read TCNTn into i */
i = TCNTn;
/* Restore global interrupt flag */
SREG = sreg;
return i;
}
Note:
1. The example code assumes that the part specific header file is included.
For I/O Registers located in extended I/O map, “IN”, “OUT”, “SBIS”, “SBIC”, “CBI”, and “SBI”
instructions must be replaced with instructions that allow access to extended I/O. Typically
“LDS” and “STS” combined with “SBRS”, “SBRC”, “SBR”, and “CBR”.
The assembly code example returns the TCNTn value in the r17:r16 register pair.
111
7647F–AVR–04/09
The following code examples show how to do an atomic write of the TCNTn Register contents.
Writing any of the OCRnx or ICRn Registers can be done by using the same principle.
Assembly Code Example(1)
TIM16_WriteTCNTn:
; Save global interrupt flag
in r18,SREG
; Disable interrupts
cli
; Set TCNTn to r17:r16
out TCNTnH,r17
out TCNTnL,r16
; Restore global interrupt flag
out SREG,r18
ret
C Code Example(1)
void TIM16_WriteTCNTn( unsigned int i )
{
unsigned char sreg;
unsigned int i;
/* Save global interrupt flag */
sreg = SREG;
/* Disable interrupts */
_CLI();
/* Set TCNTn to i */
TCNTn = i;
/* Restore global interrupt flag */
SREG = sreg;
}
Note:
1. The example code assumes that the part specific header file is included.
For I/O Registers located in extended I/O map, “IN”, “OUT”, “SBIS”, “SBIC”, “CBI”, and “SBI”
instructions must be replaced with instructions that allow access to extended I/O. Typically
“LDS” and “STS” combined with “SBRS”, “SBRC”, “SBR”, and “CBR”.
The assembly code example requires that the r17:r16 register pair contains the value to be written to TCNTn.
13.2.1
13.3
Reusing the Temporary High Byte Register
If writing to more than one 16-bit register where the high byte is the same for all registers written,
then the high byte only needs to be written once. However, note that the same rule of atomic
operation described previously also applies in this case.
Timer/Counter Clock Sources
The Timer/Counter can be clocked by an internal or an external clock source. The clock source
is selected by the Clock Select logic which is controlled by the Clock Select (CSn2:0) bits
located in the Timer/Counter control Register B (TCCRnB). For details on clock sources and
prescaler, see “Timer/Counter0 and Timer/Counter1 Prescalers” on page 87.
112
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
13.4
Counter Unit
The main part of the 16-bit Timer/Counter is the programmable 16-bit bi-directional counter unit.
Figure 13-2 shows a block diagram of the counter and its surroundings.
Figure 13-2. Counter Unit Block Diagram
DATA BUS (8-bit)
TOVn
(Int.Req.)
TEMP (8-bit)
Clock Select
Count
TCNTnH (8-bit)
TCNTnL (8-bit)
TCNTn (16-bit Counter)
Clear
Direction
Control Logic
clkTn
Edge
Detector
Tn
( From Prescaler )
RTG
TOP BOTTOM
Signal description (internal signals):
Count
Increment or decrement TCNTn by 1.
Direction
Select between increment and decrement.
Clear
Clear TCNTn (set all bits to zero).
clkTn
Timer/Counter clock.
TOP
Signalize that TCNTn has reached maximum value.
BOTTOM
Signalize that TCNTn has reached minimum value (zero).
RTG
An external event (ICP1A or ICP1B) asks for a TOP like action.
The 16-bit counter is mapped into two 8-bit I/O memory locations: Counter High (TCNTnH) containing the upper eight bits of the counter, and Counter Low (TCNTnL) containing the lower eight
bits. The TCNTnH Register can only be indirectly accessed by the CPU. When the CPU does an
access to the TCNTnH I/O location, the CPU accesses the high byte temporary register (TEMP).
The temporary register is updated with the TCNTnH value when the TCNTnL is read, and
TCNTnH is updated with the temporary register value when TCNTnL is written. This allows the
CPU to read or write the entire 16-bit counter value within one clock cycle via the 8-bit data bus.
It is important to notice that there are special cases of writing to the TCNTn Register when the
counter is counting that will give unpredictable results. The special cases are described in the
sections where they are of importance.
Depending on the mode of operation used, the counter is cleared, incremented, or decremented
at each timer clock (clkTn). The clkTn can be generated from an external or internal clock source,
selected by the Clock Select bits (CSn2:0). When no clock source is selected (CSn2:0 = 0) the
timer is stopped. However, the TCNTn value can be accessed by the CPU, independent of
whether clkTn is present or not. A CPU write overrides (has priority over) all counter clear or
count operations.
The counting sequence is determined by the setting of the Waveform Generation mode bits
(WGMn3:0) located in the Timer/Counter Control Registers A and B (TCCRnA and TCCRnB).
There are close connections between how the counter behaves (counts) and how waveforms
are generated on the Output Compare outputs OCnx. For more details about advanced counting
sequences and waveform generation, see “16-bit Timer/Counter1 with PWM” on page 107.
113
7647F–AVR–04/09
The Timer/Counter Overflow Flag (TOVn) is set according to the mode of operation selected by
the WGMn3:0 bits. TOVn can be used for generating a CPU interrupt.
13.5
Input Capture Unit
The Timer/Counter incorporates an Input Capture unit that can capture external events and give
them a time-stamp indicating time of occurrence. The external signal indicating an event, or multiple events, can be applied via the ICPn pin or alternatively, via the analog-comparator unit. The
time-stamps can then be used to calculate frequency, duty-cycle, and other features of the signal applied. Alternatively the time-stamps can be used for creating a log of the events.
The Input Capture unit is illustrated by the block diagram shown in Figure 13-3. The elements of
the block diagram that are not directly a part of the Input Capture unit are gray shaded. The
small “n” in register and bit names indicates the Timer/Counter number.
Figure 13-3. Input Capture Unit Block Diagram
DATA BUS
(8-bit)
TEMP (8-bit)
ICRnH (8-bit)
WRITE
ICRnL (8-bit)
TCNTnH (8-bit)
ICRn (16-bit Register)
TCNTnL (8-bit)
TCNTn (16-bit Counter)
Analog Comparator 1 Interrupt
ICPSEL1
AC1ICE
ICNC
ICES
Noise
Canceler
Edge
Detector
ICPnA
ICFn (Int.Req.)
ICPnB
When a change of the logic level (an event) occurs on the Input Capture pin (ICPn), alternatively
on the Analog Comparator output (ACO), and this change confirms to the setting of the edge
detector, a capture will be triggered. When a capture is triggered, the 16-bit value of the counter
(TCNTn) is written to the Input Capture Register (ICRn). The Input Capture Flag (ICFn) is set at
the same system clock as the TCNTn value is copied into ICRn Register. If enabled (ICIEn = 1),
the Input Capture Flag generates an Input Capture interrupt. The ICFn Flag is automatically
cleared when the interrupt is executed. Alternatively the ICFn Flag can be cleared by software
by writing a logical one to its I/O bit location.
Reading the 16-bit value in the Input Capture Register (ICRn) is done by first reading the low
byte (ICRnL) and then the high byte (ICRnH). When the low byte is read the high byte is copied
into the high byte temporary register (TEMP). When the CPU reads the ICRnH I/O location it will
access the TEMP Register.
114
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The ICRn Register can only be written when using a Waveform Generation mode that utilizes
the ICRn Register for defining the counter’s TOP value. In these cases the Waveform Generation mode (WGMn3:0) bits must be set before the TOP value can be written to the ICRn
Register. When writing the ICRn Register the high byte must be written to the ICRnH I/O location
before the low byte is written to ICRnL.
For more information on how to access the 16-bit registers refer to “Accessing 16-bit Registers”
on page 109.
The ICF1 output can be used to retrigger the timer counter. It has the same effect than the TOP
signal.
13.5.1
Input Capture Trigger Source
The trigger sources for the Input Capture unit arethe Input Capture pin (ICP1A & ICP1B).
Be aware that changing trigger source can trigger a capture. The Input Capture Flag must therefore be cleared after the change.
The Input Capture pin (ICPn) IS sampled using the same technique as for the Tn pin (Figure
11-1 on page 87). The edge detector is also identical. However, when the noise canceler is
enabled, additional logic is inserted before the edge detector, which increases the delay by four
system clock cycles. Note that the input of the noise canceler and edge detector is always
enabled unless the Timer/Counter is set in a Waveform Generation mode that uses ICRn to
define TOP.
An Input Capture can be triggered by software by controlling the port of the ICPn pin.
13.5.2
Noise Canceler
The noise canceler improves noise immunity by using a simple digital filtering scheme. The
noise canceler input is monitored over four samples, and all four must be equal for changing the
output that in turn is used by the edge detector.
The noise canceler is enabled by setting the Input Capture Noise Canceler (ICNCn) bit in
Timer/Counter Control Register B (TCCRnB). When enabled the noise canceler introduces additional four system clock cycles of delay from a change applied to the input, to the update of the
ICRn Register. The noise canceler uses the system clock and is therefore not affected by the
prescaler.
13.5.3
Using the Input Capture Unit
The main challenge when using the Input Capture unit is to assign enough processor capacity
for handling the incoming events. The time between two events is critical. If the processor has
not read the captured value in the ICRn Register before the next event occurs, the ICRn will be
overwritten with a new value. In this case the result of the capture will be incorrect.
When using the Input Capture interrupt, the ICRn Register should be read as early in the interrupt handler routine as possible. Even though the Input Capture interrupt has relatively high
priority, the maximum interrupt response time is dependent on the maximum number of clock
cycles it takes to handle any of the other interrupt requests.
Using the Input Capture unit in any mode of operation when the TOP value (resolution) is
actively changed during operation, is not recommended.
115
7647F–AVR–04/09
Measurement of an external signal’s duty cycle requires that the trigger edge is changed after
each capture. Changing the edge sensing must be done as early as possible after the ICRn
Register has been read. After a change of the edge, the Input Capture Flag (ICFn) must be
cleared by software (writing a logical one to the I/O bit location). For measuring frequency only,
the clearing of the ICFn Flag is not required (if an interrupt handler is used).
13.5.4
13.6
Using the Input Capture Unit as TCNT1 Retrigger Input
TCNT1 counts from BOTTOM to TOP. The TOP value can be a fixed value, ICR1, or OCR1A.
When enabled the Retrigger Input forces to reach the TOP value. It means that ICF1 output is
ored with the TOP signal.
Output Compare Units
The 16-bit comparator continuously compares TCNTn with the Output Compare Register
(OCRnx). If TCNT equals OCRnx the comparator signals a match. A match will set the Output
Compare Flag (OCFnx) at the next timer clock cycle. If enabled (OCIEnx = 1), the Output Compare Flag generates an Output Compare interrupt. The OCFnx Flag is automatically cleared
when the interrupt is executed. Alternatively the OCFnx Flag can be cleared by software by writing a logical one to its I/O bit location. The Waveform Generator uses the match signal to
generate an output according to operating mode set by the Waveform Generation mode
(WGMn3:0) bits and Compare Output mode (COMnx1:0) bits. The TOP and BOTTOM signals
are used by the Waveform Generator for handling the special cases of the extreme values in
some modes of operation (See “16-bit Timer/Counter1 with PWM” on page 107.)
A special feature of Output Compare unit A allows it to define the Timer/Counter TOP value (i.e.,
counter resolution). In addition to the counter resolution, the TOP value defines the period time
for waveforms generated by the Waveform Generator.
Figure 13-4 shows a block diagram of the Output Compare unit. The small “n” in the register and
bit names indicates the device number (n = n for Timer/Counter n), and the “x” indicates Output
Compare unit (x). The elements of the block diagram that are not directly a part of the Output
Compare unit are gray shaded.
116
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 13-4. Output Compare Unit, Block Diagram
DATA BUS
(8-bit)
TEMP (8-bit)
OCRnxH Buf. (8-bit)
OCRnxL Buf. (8-bit)
TCNTnH (8-bit)
OCRnx Buffer (16-bit Register)
OCRnxH (8-bit)
TCNTnL (8-bit)
TCNTn (16-bit Counter)
OCRnxL (8-bit)
OCRnx (16-bit Register)
= (16-bit Comparator )
OCFnx (Int.Req.)
TOP
BOTTOM
Waveform Generator
WGMn3:0
OCnx
COMnx1:0
The OCRnx Register is double buffered when using any of the twelve Pulse Width Modulation
(PWM) modes. For the Normal and Clear Timer on Compare (CTC) modes of operation, the
double buffering is disabled. The double buffering synchronizes the update of the OCRnx Compare Register to either TOP or BOTTOM of the counting sequence. The synchronization
prevents the occurrence of odd-length, non-symmetrical PWM pulses, thereby making the output glitch-free.
The OCRnx Register access may seem complex, but this is not case. When the double buffering
is enabled, the CPU has access to the OCRnx Buffer Register, and if double buffering is disabled the CPU will access the OCRnx directly. The content of the OCR1x (Buffer or Compare)
Register is only changed by a write operation (the Timer/Counter does not update this register
automatically as the TCNT1 and ICR1 Register). Therefore OCR1x is not read via the high byte
temporary register (TEMP). However, it is a good practice to read the low byte first as when
accessing other 16-bit registers. Writing the OCRnx Registers must be done via the TEMP Register since the compare of all 16 bits is done continuously. The high byte (OCRnxH) has to be
written first. When the high byte I/O location is written by the CPU, the TEMP Register will be
updated by the value written. Then when the low byte (OCRnxL) is written to the lower eight bits,
the high byte will be copied into the upper 8-bits of either the OCRnx buffer or OCRnx Compare
Register in the same system clock cycle.
For more information of how to access the 16-bit registers refer to “Accessing 16-bit Registers”
on page 109.
13.6.1
Force Output Compare
In non-PWM Waveform Generation modes, the match output of the comparator can be forced by
writing a one to the Force Output Compare (FOCnx) bit. Forcing compare match will not set the
OCFnx Flag or reload/clear the timer, but the OCnx pin will be updated as if a real compare
match had occurred (the COMn1:0 bits settings define whether the OCnx pin is set, cleared or
toggled).
117
7647F–AVR–04/09
13.6.2
Compare Match Blocking by TCNTn Write
All CPU writes to the TCNTn Register will block any compare match that occurs in the next timer
clock cycle, even when the timer is stopped. This feature allows OCRnx to be initialized to the
same value as TCNTn without triggering an interrupt when the Timer/Counter clock is enabled.
13.6.3
Using the Output Compare Unit
Since writing TCNTn in any mode of operation will block all compare matches for one timer clock
cycle, there are risks involved when changing TCNTn when using any of the Output Compare
channels, independent of whether the Timer/Counter is running or not. If the value written to
TCNTn equals the OCRnx value, the compare match will be missed, resulting in incorrect waveform generation. Do not write the TCNTn equal to TOP in PWM modes with variable TOP
values. The compare match for the TOP will be ignored and the counter will continue to 0xFFFF.
Similarly, do not write the TCNTn value equal to BOTTOM when the counter is downcounting.
The setup of the OCnx should be performed before setting the Data Direction Register for the
port pin to output. The easiest way of setting the OCnx value is to use the Force Output Compare (FOCnx) strobe bits in Normal mode. The OCnx Register keeps its value even when
changing between Waveform Generation modes.
Be aware that the COMnx1:0 bits are not double buffered together with the compare value.
Changing the COMnx1:0 bits will take effect immediately.
13.7
Compare Match Output Unit
The Compare Output mode (COMnx1:0) bits have two functions. The Waveform Generator uses
the COMnx1:0 bits for defining the Output Compare (OCnx) state at the next compare match.
Secondly the COMnx1:0 bits control the OCnx pin output source. Figure 13-5 shows a simplified
schematic of the logic affected by the COMnx1:0 bit setting. The I/O Registers, I/O bits, and I/O
pins in the figure are shown in bold. Only the parts of the general I/O Port Control Registers
(DDR and PORT) that are affected by the COMnx1:0 bits are shown. When referring to the
OCnx state, the reference is for the internal OCnx Register, not the OCnx pin. If a system reset
occur, the OCnx Register is reset to “0”.
118
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 13-5. Compare Match Output Unit, Schematic
COMnx1
COMnx0
FOCnx
Waveform
Generator
D
Q
1
OCnx
DATA BUS
D
0
OCnx
Pin
Q
PORT
D
Q
DDR
clk I/O
The general I/O port function is overridden by the Output Compare (OCnx) from the Waveform
Generator if either of the COMnx1:0 bits are set. However, the OCnx pin direction (input or output) is still controlled by the Data Direction Register (DDR) for the port pin. The Data Direction
Register bit for the OCnx pin (DDR_OCnx) must be set as output before the OCnx value is visible on the pin. The port override function is generally independent of the Waveform Generation
mode, but there are some exceptions. Refer to Table 13-1, Table 13-2 and Table 13-3 for
details.
The design of the Output Compare pin logic allows initialization of the OCnx state before the output is enabled. Note that some COMnx1:0 bit settings are reserved for certain modes of
operation. See “16-bit Timer/Counter Register Description” on page 130.
The COMnx1:0 bits have no effect on the Input Capture unit.
13.7.1
Compare Output Mode and Waveform Generation
The Waveform Generator uses the COMnx1:0 bits differently in normal, CTC, and PWM modes.
For all modes, setting the COMnx1:0 = 0 tells the Waveform Generator that no action on the
OCnx Register is to be performed on the next compare match. For compare output actions in the
non-PWM modes refer to Table 13-1 on page 130. For fast PWM mode refer to Table 13-2 on
page 130, and for phase correct and phase and frequency correct PWM refer to Table 13-3 on
page 131.
A change of the COMnx1:0 bits state will have effect at the first compare match after the bits are
written. For non-PWM modes, the action can be forced to have immediate effect by using the
FOCnx strobe bits.
119
7647F–AVR–04/09
13.8
Modes of Operation
The mode of operation, i.e., the behavior of the Timer/Counter and the Output Compare pins, is
defined by the combination of the Waveform Generation mode (WGMn3:0) and Compare Output
mode (COMnx1:0) bits. The Compare Output mode bits do not affect the counting sequence,
while the Waveform Generation mode bits do. The COMnx1:0 bits control whether the PWM output generated should be inverted or not (inverted or non-inverted PWM). For non-PWM modes
the COMnx1:0 bits control whether the output should be set, cleared or toggle at a compare
match (See “Compare Match Output Unit” on page 118.)
For detailed timing information refer to “Timer/Counter Timing Diagrams” on page 128.
13.8.1
Normal Mode
The simplest mode of operation is the Normal mode (WGMn3:0 = 0). In this mode the counting
direction is always up (incrementing), and no counter clear is performed. The counter simply
overruns when it passes its maximum 16-bit value (MAX = 0xFFFF) and then restarts from the
BOTTOM (0x0000). In normal operation the Timer/Counter Overflow Flag (TOVn) will be set in
the same timer clock cycle as the TCNTn becomes zero. The TOVn Flag in this case behaves
like a 17th bit, except that it is only set, not cleared. However, combined with the timer overflow
interrupt that automatically clears the TOVn Flag, the timer resolution can be increased by software. There are no special cases to consider in the Normal mode, a new counter value can be
written anytime.
The Input Capture unit is easy to use in Normal mode. However, observe that the maximum
interval between the external events must not exceed the resolution of the counter. If the interval
between events are too long, the timer overflow interrupt or the prescaler must be used to
extend the resolution for the capture unit.
The Output Compare units can be used to generate interrupts at some given time. Using the
Output Compare to generate waveforms in Normal mode is not recommended, since this will
occupy too much of the CPU time.
13.8.2
Clear Timer on Compare Match (CTC) Mode
In Clear Timer on Compare or CTC mode (WGMn3:0 = 4 or 12), the OCRnA or ICRn Register
are used to manipulate the counter resolution. In CTC mode the counter is cleared to zero when
the counter value (TCNTn) matches either the OCRnA (WGMn3:0 = 4) or the ICRn (WGMn3:0 =
12). The OCRnA or ICRn define the top value for the counter, hence also its resolution. This
mode allows greater control of the compare match output frequency. It also simplifies the operation of counting external events.
The timing diagram for the CTC mode is shown in Figure 13-6. The counter value (TCNTn)
increases until a compare match occurs with either OCRnA or ICRn, and then counter (TCNTn)
is cleared.
120
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 13-6. CTC Mode, Timing Diagram
OCnA Interrupt Flag Set
or ICFn Interrupt Flag Set
(Interrupt on TOP)
TCNTn
OCnA
(Toggle)
Period
(COMnA1:0 = 1)
1
2
3
4
An interrupt can be generated at each time the counter value reaches the TOP value by either
using the OCFnA or ICFn Flag according to the register used to define the TOP value. If the
interrupt is enabled, the interrupt handler routine can be used for updating the TOP value. However, changing the TOP to a value close to BOTTOM when the counter is running with none or a
low prescaler value must be done with care since the CTC mode does not have the double buffering feature. If the new value written to OCRnA or ICRn is lower than the current value of
TCNTn, the counter will miss the compare match. The counter will then have to count to its maximum value (0xFFFF) and wrap around starting at 0x0000 before the compare match can occur.
In many cases this feature is not desirable. An alternative will then be to use the fast PWM mode
using OCRnA for defining TOP (WGMn3:0 = 15) since the OCRnA then will be double buffered.
For generating a waveform output in CTC mode, the OCnA output can be set to toggle its logical
level on each compare match by setting the Compare Output mode bits to toggle mode
(COMnA1:0 = 1). The OCnA value will not be visible on the port pin unless the data direction for
the pin is set to output (DDR_OCnA = 1). The waveform generated will have a maximum frequency of fOCnA = fclk_I/O/2 when OCRnA is set to zero (0x0000). The waveform frequency is
defined by the following equation:
f clk_I/O
f OCnA = ------------------------------------------------------2 ⋅ N ⋅ ( 1 + OCRnA )
The N variable represents the prescaler factor (1, 8, 64, 256, or 1024).
As for the Normal mode of operation, the TOVn Flag is set in the same timer clock cycle that the
counter counts from MAX to 0x0000.
13.8.3
Fast PWM Mode
The fast Pulse Width Modulation or fast PWM mode (WGMn3:0 = 5, 6, 7, 14, or 15) provides a
high frequency PWM waveform generation option. The fast PWM differs from the other PWM
options by its single-slope operation. The counter counts from BOTTOM to TOP then restarts
from BOTTOM. In non-inverting Compare Output mode, the Output Compare (OCnx) is set on
the compare match between TCNTn and OCRnx, and cleared at TOP. In inverting Compare
Output mode output is cleared on compare match and set at TOP. Due to the single-slope operation, the operating frequency of the fast PWM mode can be twice as high as the phase correct
and phase and frequency correct PWM modes that use dual-slope operation. This high frequency makes the fast PWM mode well suited for power regulation, rectification, and DAC
applications. High frequency allows physically small sized external components (coils, capacitors), hence reduces total system cost.
121
7647F–AVR–04/09
The PWM resolution for fast PWM can be fixed to 8-, 9-, or 10-bit, or defined by either ICRn or
OCRnA. The minimum resolution allowed is 2-bit (ICRn or OCRnA set to 0x0003), and the maximum resolution is 16-bit (ICRn or OCRnA set to MAX). The PWM resolution in bits can be
calculated by using the following equation:
log ( TOP + 1 )
R FPWM = ----------------------------------log ( 2 )
In fast PWM mode the counter is incremented until the counter value matches either one of the
fixed values 0x00FF, 0x01FF, or 0x03FF (WGMn3:0 = 5, 6, or 7), the value in ICRn (WGMn3:0 =
14), or the value in OCRnA (WGMn3:0 = 15). The counter is then cleared at the following timer
clock cycle. The timing diagram for the fast PWM mode is shown in Figure 13-7. The figure
shows fast PWM mode when OCRnA or ICRn is used to define TOP. The TCNTn value is in the
timing diagram shown as a histogram for illustrating the single-slope operation. The diagram
includes non-inverted and inverted PWM outputs. The small horizontal line marks on the TCNTn
slopes represent compare matches between OCRnx and TCNTn. The OCnx Interrupt Flag will
be set when a compare match occurs.
Figure 13-7. Fast PWM Mode, Timing Diagram
OCRnx/TOP Update and
TOVn Interrupt Flag Set and
OCnA Interrupt Flag Set
or ICFn Interrupt Flag Set
(Interrupt on TOP)
TCNTn
OCnx
(COMnx1:0 = 2)
OCnx
(COMnx1:0 = 3)
Period
1
2
3
4
5
6
7
8
The Timer/Counter Overflow Flag (TOVn) is set each time the counter reaches TOP. In addition
the OCnA or ICFn Flag is set at the same timer clock cycle as TOVn is set when either OCRnA
or ICRn is used for defining the TOP value. If one of the interrupts are enabled, the interrupt handler routine can be used for updating the TOP and compare values.
When changing the TOP value the program must ensure that the new TOP value is higher or
equal to the value of all of the Compare Registers. If the TOP value is lower than any of the
Compare Registers, a compare match will never occur between the TCNTn and the OCRnx.
Note that when using fixed TOP values the unused bits are masked to zero when any of the
OCRnx Registers are written.
The procedure for updating ICRn differs from updating OCRnA when used for defining the TOP
value. The ICRn Register is not double buffered. This means that if ICRn is changed to a low
value when the counter is running with none or a low prescaler value, there is a risk that the new
ICRn value written is lower than the current value of TCNTn. The result will then be that the
counter will miss the compare match at the TOP value. The counter will then have to count to the
MAX value (0xFFFF) and wrap around starting at 0x0000 before the compare match can occur.
The OCRnA Register however, is double buffered.
122
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
This feature allows the OCRnA I/O location to be written anytime. When the OCRnA I/O location
is written the value written will be put into the OCRnA Buffer Register.
The OCRnA Compare Register will then be updated with the value in the Buffer Register at the
next timer clock cycle the TCNTn matches TOP. The update is done at the same timer clock
cycle as the TCNTn is cleared and the TOVn Flag is set.
Using the ICRn Register for defining TOP works well when using fixed TOP values. By using
ICRn, the OCRnA Register is free to be used for generating a PWM output on OCnA. However,
if the base PWM frequency is actively changed (by changing the TOP value), using the OCRnA
as TOP is clearly a better choice due to its double buffer feature.
In fast PWM mode, the compare units allow generation of PWM waveforms on the OCnx pins.
Setting the COMnx1:0 bits to two will produce a non-inverted PWM and an inverted PWM output
can be generated by setting the COMnx1:0 to three (see Table on page 130). The actual OCnx
value will only be visible on the port pin if the data direction for the port pin is set as output
(DDR_OCnx). The PWM waveform is generated by setting (or clearing) the OCnx Register at
the compare match between OCRnx and TCNTn, and clearing (or setting) the OCnx Register at
the timer clock cycle the counter is cleared (changes from TOP to BOTTOM).
The PWM frequency for the output can be calculated by the following equation:
f clk_I/O
f OCnxPWM = ------------------------------------N ⋅ ( 1 + TOP )
The N variable represents the prescaler divider (1, 8, 64, 256, or 1024).
The extreme values for the OCRnx Register represents special cases when generating a PWM
waveform output in the fast PWM mode. If the OCRnx is set equal to BOTTOM (0x0000) the output will be a narrow spike for each TOP+1 timer clock cycle. Setting the OCRnx equal to TOP
will result in a constant high or low output (depending on the polarity of the output set by the
COMnx1:0 bits.)
A frequency (with 50% duty cycle) waveform output in fast PWM mode can be achieved by setting OCnA to toggle its logical level on each compare match (COMnA1:0 = 1). This applies only
if OCR1A is used to define the TOP value (WGM13:0 = 15). The waveform generated will have
a maximum frequency of fOCnA = fclk_I/O/2 when OCRnA is set to zero (0x0000). This feature is
similar to the OCnA toggle in CTC mode, except the double buffer feature of the Output Compare unit is enabled in the fast PWM mode.
13.8.4
Phase Correct PWM Mode
The phase correct Pulse Width Modulation or phase correct PWM mode (WGMn3:0 = 1, 2, 3,
10, or 11) provides a high resolution phase correct PWM waveform generation option. The
phase correct PWM mode is, like the phase and frequency correct PWM mode, based on a
dual-slope operation. The counter counts repeatedly from BOTTOM (0x0000) to TOP and then
from TOP to BOTTOM. In non-inverting Compare Output mode, the Output Compare (OCnx) is
cleared on the compare match between TCNTn and OCRnx while upcounting, and set on the
compare match while downcounting. In inverting Output Compare mode, the operation is
inverted. The dual-slope operation has lower maximum operation frequency than single slope
operation. However, due to the symmetric feature of the dual-slope PWM modes, these modes
are preferred for motor control applications.
123
7647F–AVR–04/09
The PWM resolution for the phase correct PWM mode can be fixed to 8-, 9-, or 10-bit, or defined
by either ICRn or OCRnA. The minimum resolution allowed is 2-bit (ICRn or OCRnA set to
0x0003), and the maximum resolution is 16-bit (ICRn or OCRnA set to MAX). The PWM resolution in bits can be calculated by using the following equation:
log ( TOP + 1 )
R PCPWM = ----------------------------------log ( 2 )
In phase correct PWM mode the counter is incremented until the counter value matches either
one of the fixed values 0x00FF, 0x01FF, or 0x03FF (WGMn3:0 = 1, 2, or 3), the value in ICRn
(WGMn3:0 = 10), or the value in OCRnA (WGMn3:0 = 11). The counter has then reached the
TOP and changes the count direction. The TCNTn value will be equal to TOP for one timer clock
cycle. The timing diagram for the phase correct PWM mode is shown on Figure 13-8. The figure
shows phase correct PWM mode when OCRnA or ICRn is used to define TOP. The TCNTn
value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. The
diagram includes non-inverted and inverted PWM outputs. The small horizontal line marks on
the TCNTn slopes represent compare matches between OCRnx and TCNTn. The OCnx Interrupt Flag will be set when a compare match occurs.
Figure 13-8. Phase Correct PWM Mode, Timing Diagram
OCRnx/TOP Update and
OCnA Interrupt Flag Set
or ICFn Interrupt Flag Set
(Interrupt on TOP)
TOVn Interrupt Flag Set
(Interrupt on Bottom)
TCNTn
OCnx
(COMnx1:0 = 2)
OCnx
(COMnx1:0 = 3)
Period
1
2
3
4
The Timer/Counter Overflow Flag (TOVn) is set each time the counter reaches BOTTOM. When
either OCRnA or ICRn is used for defining the TOP value, the OCnA or ICFn Flag is set accordingly at the same timer clock cycle as the OCRnx Registers are updated with the double buffer
value (at TOP). The Interrupt Flags can be used to generate an interrupt each time the counter
reaches the TOP or BOTTOM value.
When changing the TOP value the program must ensure that the new TOP value is higher or
equal to the value of all of the Compare Registers. If the TOP value is lower than any of the
Compare Registers, a compare match will never occur between the TCNTn and the OCRnx.
Note that when using fixed TOP values, the unused bits are masked to zero when any of the
OCRnx Registers are written. As the third period shown in Figure 13-8 illustrates, changing the
124
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
TOP actively while the Timer/Counter is running in the phase correct mode can result in an
unsymmetrical output.
The reason for this can be found in the time of update of the OCRnx Register. Since the OCRnx
update occurs at TOP, the PWM period starts and ends at TOP. This implies that the length of
the falling slope is determined by the previous TOP value, while the length of the rising slope is
determined by the new TOP value. When these two values differ the two slopes of the period will
differ in length. The difference in length gives the unsymmetrical result on the output.
It is recommended to use the phase and frequency correct mode instead of the phase correct
mode when changing the TOP value while the Timer/Counter is running. When using a static
TOP value there are practically no differences between the two modes of operation.
In phase correct PWM mode, the compare units allow generation of PWM waveforms on the
OCnx pins. Setting the COMnx1:0 bits to two will produce a non-inverted PWM and an inverted
PWM output can be generated by setting the COMnx1:0 to three (See Table on page 131). The
actual OCnx value will only be visible on the port pin if the data direction for the port pin is set as
output (DDR_OCnx). The PWM waveform is generated by setting (or clearing) the OCnx Register at the compare match between OCRnx and TCNTn when the counter increments, and
clearing (or setting) the OCnx Register at compare match between OCRnx and TCNTn when
the counter decrements. The PWM frequency for the output when using phase correct PWM can
be calculated by the following equation:
f clk_I/O
f OCnxPCPWM = --------------------------------2 ⋅ N ⋅ TOP
The N variable represents the prescaler divider (1, 8, 64, 256, or 1024).
The extreme values for the OCRnx Register represent special cases when generating a PWM
waveform output in the phase correct PWM mode. If the OCRnx is set equal to BOTTOM the
output will be continuously low and if set equal to TOP the output will be continuously high for
non-inverted PWM mode. For inverted PWM the output will have the opposite logic values. If
OCR1A is used to define the TOP value (WGM13:0 = 11) and COM1A1:0 = 1, the OC1A output
will toggle with a 50% duty cycle.
13.8.5
Phase and Frequency Correct PWM Mode
The phase and frequency correct Pulse Width Modulation, or phase and frequency correct PWM
mode (WGMn3:0 = 8 or 9) provides a high resolution phase and frequency correct PWM waveform generation option. The phase and frequency correct PWM mode is, like the phase correct
PWM mode, based on a dual-slope operation. The counter counts repeatedly from BOTTOM
(0x0000) to TOP and then from TOP to BOTTOM. In non-inverting Compare Output mode, the
Output Compare (OCnx) is cleared on the compare match between TCNTn and OCRnx while
upcounting, and set on the compare match while downcounting. In inverting Compare Output
mode, the operation is inverted. The dual-slope operation gives a lower maximum operation frequency compared to the single-slope operation. However, due to the symmetric feature of the
dual-slope PWM modes, these modes are preferred for motor control applications.
The main difference between the phase correct, and the phase and frequency correct PWM
mode is the time the OCRnx Register is updated by the OCRnx Buffer Register, (see Figure
13-8 and Figure 13-9).
125
7647F–AVR–04/09
The PWM resolution for the phase and frequency correct PWM mode can be defined by either
ICRn or OCRnA. The minimum resolution allowed is 2-bit (ICRn or OCRnA set to 0x0003), and
the maximum resolution is 16-bit (ICRn or OCRnA set to MAX). The PWM resolution in bits can
be calculated using the following equation:
log ( TOP + 1 )
R PFCPWM = ----------------------------------log ( 2 )
In phase and frequency correct PWM mode the counter is incremented until the counter value
matches either the value in ICRn (WGMn3:0 = 8), or the value in OCRnA (WGMn3:0 = 9). The
counter has then reached the TOP and changes the count direction. The TCNTn value will be
equal to TOP for one timer clock cycle. The timing diagram for the phase correct and frequency
correct PWM mode is shown on Figure 13-9. The figure shows phase and frequency correct
PWM mode when OCRnA or ICRn is used to define TOP. The TCNTn value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. The diagram includes
non-inverted and inverted PWM outputs.
The small horizontal line marks on the TCNTn slopes represent compare matches between
OCRnx and TCNTn. The OCnx Interrupt Flag will be set when a compare match occurs.
Figure 13-9. Phase and Frequency Correct PWM Mode, Timing Diagram
OCnA Interrupt Flag Set
or ICFn Interrupt Flag Set
(Interrupt on TOP)
OCRnx/TOP Updateand
TOVn Interrupt Flag Set
(Interrupt on Bottom)
TCNTn
OCnx
(COMnx1:0 = 2)
OCnx
(COMnx1:0 = 3)
Period
1
2
3
4
The Timer/Counter Overflow Flag (TOVn) is set at the same timer clock cycle as the OCRnx
Registers are updated with the double buffer value (at BOTTOM). When either OCRnA or ICRn
is used for defining the TOP value, the OCnA or ICFn Flag is set when TCNTn has reached
TOP. The Interrupt Flags can then be used to generate an interrupt each time the counter
reaches the TOP or BOTTOM value.
When changing the TOP value the program must ensure that the new TOP value is higher or
equal to the value of all of the Compare Registers. If the TOP value is lower than any of the
Compare Registers, a compare match will never occur between the TCNTn and the OCRnx.
126
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
As Figure 13-9 shows the output generated is, in contrast to the phase correct mode, symmetrical in all periods. Since the OCRnx Registers are updated at BOTTOM, the length of the rising
and the falling slopes will always be equal. This gives symmetrical output pulses and is therefore
frequency correct.
Using the ICRn Register for defining TOP works well when using fixed TOP values. By using
ICRn, the OCRnA Register is free to be used for generating a PWM output on OCnA. However,
if the base PWM frequency is actively changed by changing the TOP value, using the OCRnA as
TOP is clearly a better choice due to its double buffer feature.
In phase and frequency correct PWM mode, the compare units allow generation of PWM waveforms on the OCnx pins. Setting the COMnx1:0 bits to two will produce a non-inverted PWM and
an inverted PWM output can be generated by setting the COMnx1:0 to three (See Table on
page 131). The actual OCnx value will only be visible on the port pin if the data direction for the
port pin is set as output (DDR_OCnx). The PWM waveform is generated by setting (or clearing)
the OCnx Register at the compare match between OCRnx and TCNTn when the counter increments, and clearing (or setting) the OCnx Register at compare match between OCRnx and
TCNTn when the counter decrements. The PWM frequency for the output when using phase
and frequency correct PWM can be calculated by the following equation:
f clk_I/O
f OCnxPFCPWM = --------------------------------2 ⋅ N ⋅ TOP
The N variable represents the prescaler divider (1, 8, 64, 256, or 1024).
The extreme values for the OCRnx Register represents special cases when generating a PWM
waveform output in the phase correct PWM mode. If the OCRnx is set equal to BOTTOM the
output will be continuously low and if set equal to TOP the output will be set to high for
non-inverted PWM mode. For inverted PWM the output will have the opposite logic values. If
OCR1A is used to define the TOP value (WGM13:0 = 9) and COM1A1:0 = 1, the OC1A output
will toggle with a 50% duty cycle.
127
7647F–AVR–04/09
13.9
Timer/Counter Timing Diagrams
The Timer/Counter is a synchronous design and the timer clock (clkTn) is therefore shown as a
clock enable signal in the following figures. The figures include information on when Interrupt
Flags are set, and when the OCRnx Register is updated with the OCRnx buffer value (only for
modes utilizing double buffering). Figure 13-10 shows a timing diagram for the setting of OCFnx.
Figure 13-10. Timer/Counter Timing Diagram, Setting of OCFnx, no Prescaling
clkI/O
clkTn
(clkI/O /1)
TCNTn
OCRnx - 1
OCRnx
OCRnx
OCRnx + 1
OCRnx + 2
OCRnx Value
OCFnx
Figure 13-11 shows the same timing data, but with the prescaler enabled.
Figure 13-11. Timer/Counter Timing Diagram, Setting of OCFnx, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
TCNTn
OCRnx - 1
OCRnx
OCRnx
OCRnx + 1
OCRnx + 2
OCRnx Value
OCFnx
128
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 13-12 shows the count sequence close to TOP in various modes. When using phase and
frequency correct PWM mode the OCRnx Register is updated at BOTTOM. The timing diagrams
will be the same, but TOP should be replaced by BOTTOM, TOP-1 by BOTTOM+1 and so on.
The same renaming applies for modes that set the TOVn Flag at BOTTOM.
Figure 13-12. Timer/Counter Timing Diagram, no Prescaling
clkI/O
clkTn
(clkI/O /1)
TCNTn
(CTC and FPWM)
TCNTn
(PC and PFC PWM)
TOP - 1
TOP
BOTTOM
BOTTOM + 1
TOP - 1
TOP
TOP - 1
TOP - 2
TOVn (FPWM)
and ICFn (if used
as TOP)
OCRnx
(Update at TOP)
Old OCRnx Value
New OCRnx Value
Figure 13-13 shows the same timing data, but with the prescaler enabled.
Figure 13-13. Timer/Counter Timing Diagram, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O/8)
TCNTn
(CTC and FPWM)
TCNTn
(PC and PFC PWM)
TOP - 1
TOP
BOTTOM
BOTTOM + 1
TOP - 1
TOP
TOP - 1
TOP - 2
TOVn (FPWM)
and ICF n (if used
as TOP)
OCRnx
(Update at TOP)
Old OCRnx Value
New OCRnx Value
129
7647F–AVR–04/09
13.10 16-bit Timer/Counter Register Description
13.10.1
Timer/Counter1 Control Register A – TCCR1A
Bit
7
6
5
4
3
2
1
0
COM1A1
COM1A0
COM1B1
COM1B0
–
–
WGM11
WGM10
Read/Write
R/W
R/W
R/W
R/W
R
R
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TCCR1A
• Bit 7:6 – COMnA1:0: Compare Output Mode for Channel A
• Bit 5:4 – COMnB1:0: Compare Output Mode for Channel B
The COMnA1:0 and COMnB1:0 control the Output Compare pins (OCnA and OCnB respectively) behavior. If one or both of the COMnA1:0 bits are written to one, the OCnA output
overrides the normal port functionality of the I/O pin it is connected to. If one or both of the
COMnB1:0 bit are written to one, the OCnB output overrides the normal port functionality of the
I/O pin it is connected to. However, note that the Data Direction Register (DDR) bit corresponding to the OCnA or OCnB pin must be set in order to enable the output driver.
When the OCnA or OCnB is connected to the pin, the function of the COMnx1:0 bits is dependent of the WGMn3:0 bits setting. Table 13-1 shows the COMnx1:0 bit functionality when the
WGMn3:0 bits are set to a Normal or a CTC mode (non-PWM).
Table 13-1.
Compare Output Mode, non-PWM
COMnA1/COMnB1
COMnA0/COMnB0
Description
0
0
Normal port operation, OCnA/OCnB disconnected.
0
1
Toggle OCnA/OCnB on Compare Match.
1
0
Clear OCnA/OCnB on Compare Match (Set output to
low level).
1
1
Set OCnA/OCnB on Compare Match (Set output to
high level).
Table 13-2 shows the COMnx1:0 bit functionality when the WGMn3:0 bits are set to the fast
PWM mode.
Table 13-2.
COMnA1/COMnB1
COMnA0/COMnB0
0
0
Normal port operation, OCnA/OCnB disconnected.
0
1
WGMn3:0 = 14 or 15: Toggle OC1A on Compare
Match, OC1B disconnected (normal port operation).
For all other WGM1 settings, normal port operation,
OC1A/OC1B disconnected.
1
0
Clear OCnA/OCnB on Compare Match, set
OCnA/OCnB at TOP
1
1
Set OCnA/OCnB on Compare Match, clear
OCnA/OCnB at TOP
Note:
130
Compare Output Mode, Fast PWM(1)
Description
1. A special case occurs when OCRnA/OCRnB equals TOP and COMnA1/COMnB1 is set. In
this case the compare match is ignored, but the set or clear is done at TOP. See “Fast PWM
Mode” on page 121. for more details.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 13-3 shows the COMnx1:0 bit functionality when the WGMn3:0 bits are set to the phase
correct or the phase and frequency correct, PWM mode.
Table 13-3.
Compare Output Mode, Phase Correct and Phase and Frequency Correct
PWM(1)
COMnA1/COMnB1
COMnA0/COMnB0
0
0
Normal port operation, OCnA/OCnB disconnected.
0
1
WGMn3:0 = 8, 9 10 or 11: Toggle OCnA on Compare
Match, OCnB disconnected (normal port operation).
For all other WGM1 settings, normal port operation,
OC1A/OC1B disconnected.
1
0
Clear OCnA/OCnB on Compare Match when
up-counting. Set OCnA/OCnB on Compare Match
when downcounting.
1
1
Set OCnA/OCnB on Compare Match when
up-counting. Clear OCnA/OCnB on Compare Match
when downcounting.
Note:
Description
1. A special case occurs when OCRnA/OCRnB equals TOP and COMnA1/COMnB1 is set. See
“Phase Correct PWM Mode” on page 123. for more details.
• Bit 1:0 – WGMn1:0: Waveform Generation Mode
Combined with the WGMn3:2 bits found in the TCCRnB Register, these bits control the counting
sequence of the counter, the source for maximum (TOP) counter value, and what type of waveform generation to be used, see Table 13-4. Modes of operation supported by the Timer/Counter
unit are: Normal mode (counter), Clear Timer on Compare match (CTC) mode, and three types
of Pulse Width Modulation (PWM) modes. (See “16-bit Timer/Counter1 with PWM” on page
107.).
Waveform Generation Mode Bit Description(1)
Table 13-4.
Mode
WGMn3
WGMn2
(CTCn)
WGMn1 WGMn0
(PWMn1) (PWMn0) Timer/Counter Mode of Operation
TOP
Update of
OCRnx at
TOVn Flag
Set on
0
0
0
0
0
Normal
0xFFFF
Immediate
MAX
1
0
0
0
2
0
0
1
1
PWM, Phase Correct, 8-bit
0x00FF
TOP
BOTTOM
0
PWM, Phase Correct, 9-bit
0x01FF
TOP
BOTTOM
3
0
0
1
1
PWM, Phase Correct, 10-bit
0x03FF
TOP
BOTTOM
4
0
5
0
1
0
0
CTC
OCRnA
Immediate
MAX
1
0
1
Fast PWM, 8-bit
0x00FF
TOP
TOP
6
0
1
1
0
Fast PWM, 9-bit
0x01FF
TOP
TOP
7
0
1
1
1
Fast PWM, 10-bit
0x03FF
TOP
TOP
8
1
0
0
0
PWM, Phase and Frequency Correct ICRn
BOTTOM
BOTTOM
9
1
0
0
1
PWM, Phase and Frequency Correct OCRnA
BOTTOM
BOTTOM
10
1
0
1
0
PWM, Phase Correct
TOP
BOTTOM
11
1
0
1
1
PWM, Phase Correct
OCRnA
TOP
BOTTOM
12
1
1
0
0
CTC
ICRn
Immediate
MAX
13
1
1
0
1
(Reserved)
–
–
–
14
1
1
1
0
Fast PWM
ICRn
TOP
TOP
15
1
1
1
1
Fast PWM
OCRnA
TOP
TOP
Note:
ICRn
1. The CTCn and PWMn1:0 bit definition names are obsolete. Use the WGMn2:0 definitions. However, the functionality and
location of these bits are compatible with previous versions of the timer.
131
7647F–AVR–04/09
13.10.2
Timer/Counter1 Control Register B – TCCR1B
Bit
7
6
5
4
3
2
1
0
ICNC1
ICES1
RTGEN
WGM13
WGM12
CS12
CS11
CS10
Read/Write
R/W
R/W
R
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TCCR1B
• Bit 7 – ICNCn: Input Capture Noise Canceler
Setting this bit (to one) activates the Input Capture Noise Canceler. When the noise canceler is
activated, the input from the Input Capture pin (ICPn) is filtered. The filter function requires four
successive equal valued samples of the ICPn pin for changing its output. The Input Capture is
therefore delayed by four Oscillator cycles when the noise canceler is enabled.
• Bit 6 – ICESn: Input Capture Edge Select
This bit selects which edge on the Input Capture pin (ICPn) that is used to trigger a capture
event. When the ICESn bit is written to zero, a falling (negative) edge is used as trigger, and
when the ICESn bit is written to one, a rising (positive) edge will trigger the capture.
When a capture is triggered according to the ICESn setting, the counter value is copied into the
Input Capture Register (ICRn). The event will also set the Input Capture Flag (ICFn), and this
can be used to cause an Input Capture Interrupt, if this interrupt is enabled.
When the ICRn is used as TOP value (see description of the WGMn3:0 bits located in the
TCCRnA and the TCCRnB Register), the ICPn is disconnected and consequently the Input Capture function is disabled.
• Bit 5 – RTGEN
Set this bit to enable the ICP1A as a timer/counter retrigger input.
(This bit is reserved for future use. For ensuring compatibility with future devices, this bit must be
written to zero when TCCRnB is written.)
• Bit 4:3 – WGMn3:2: Waveform Generation Mode
See TCCRnA Register description.
• Bit 2:0 – CSn2:0: Clock Select
The three Clock Select bits select the clock source to be used by the Timer/Counter, see Figure
13-10 and Figure 13-11.
Table 13-5.
132
Clock Select Bit Description
CSn2
CSn1
CSn0
Description
0
0
0
No clock source (Timer/Counter stopped).
0
0
1
clkI/O/1 (No prescaling)
0
1
0
clkI/O/8 (From prescaler)
0
1
1
clkI/O/64 (From prescaler)
1
0
0
clkI/O/256 (From prescaler)
1
0
1
clkI/O/1024 (From prescaler)
1
1
0
External clock source on Tn pin. Clock on falling edge.
1
1
1
External clock source on Tn pin. Clock on rising edge.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
If external pin modes are used for the Timer/Countern, transitions on the Tn pin will clock the
counter even if the pin is configured as an output. This feature allows software control of the
counting.
13.10.3
Timer/Counter1 Control Register C – TCCR1C
Bit
7
6
5
4
3
2
1
FOC1A
FOC1B
–
–
–
–
–
0
–
Read/Write
R/W
R/W
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
TCCR1C
• Bit 7 – FOCnA: Force Output Compare for Channel A
• Bit 6 – FOCnB: Force Output Compare for Channel B
The FOCnA/FOCnB bits are only active when the WGMn3:0 bits specifies a non-PWM mode.
However, for ensuring compatibility with future devices, these bits must be set to zero when
TCCRnA is written when operating in a PWM mode. When writing a logical one to the
FOCnA/FOCnB bit, an immediate compare match is forced on the Waveform Generation unit.
The OCnA/OCnB output is changed according to its COMnx1:0 bits setting. Note that the
FOCnA/FOCnB bits are implemented as strobes. Therefore it is the value present in the
COMnx1:0 bits that determine the effect of the forced compare.
A FOCnA/FOCnB strobe will not generate any interrupt nor will it clear the timer in Clear Timer
on Compare match (CTC) mode using OCRnA as TOP.
The FOCnA/FOCnB bits are always read as zero.
13.10.4
Timer/Counter1 – TCNT1H and TCNT1L
Bit
7
6
5
4
3
2
1
0
TCNT1[15:8]
TCNT1H
TCNT1[7:0]
TCNT1L
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
The two Timer/Counter I/O locations (TCNTnH and TCNTnL, combined TCNTn) give direct
access, both for read and for write operations, to the Timer/Counter unit 16-bit counter. To
ensure that both the high and low bytes are read and written simultaneously when the CPU
accesses these registers, the access is performed using an 8-bit temporary High Byte Register
(TEMP). This temporary register is shared by all the other 16-bit registers. See “Accessing 16-bit
Registers” on page 109.
Modifying the counter (TCNTn) while the counter is running introduces a risk of missing a compare match between TCNTn and one of the OCRnx Registers.
Writing to the TCNTn Register blocks (removes) the compare match on the following timer clock
for all compare units.
13.10.5
Output Compare Register 1 A – OCR1AH and OCR1AL
Bit
7
6
5
4
3
2
1
0
OCR1A[15:8]
OCR1AH
OCR1A[7:0]
OCR1AL
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
133
7647F–AVR–04/09
13.10.6
Output Compare Register 1 B – OCR1BH and OCR1BL
Bit
7
6
5
4
3
2
1
0
OCR1B[15:8]
OCR1BH
OCR1B[7:0]
OCR1BL
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
The Output Compare Registers contain a 16-bit value that is continuously compared with the
counter value (TCNTn). A match can be used to generate an Output Compare interrupt, or to
generate a waveform output on the OCnx pin.
The Output Compare Registers are 16-bit in size. To ensure that both the high and low bytes are
written simultaneously when the CPU writes to these registers, the access is performed using an
8-bit temporary High Byte Register (TEMP). This temporary register is shared by all the other
16-bit registers. See “Accessing 16-bit Registers” on page 109.
13.10.7
Input Capture Register 1 – ICR1H and ICR1L
Bit
7
6
5
4
3
2
1
0
ICR1[15:8]
ICR1H
ICR1[7:0]
ICR1L
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
The Input Capture is updated with the counter (TCNTn) value each time an event occurs on the
ICPn pin (or optionally on the Analog Comparator output for Timer/Counter1). The Input Capture
can be used for defining the counter TOP value.
The Input Capture Register is 16-bit in size. To ensure that both the high and low bytes are read
simultaneously when the CPU accesses these registers, the access is performed using an 8-bit
temporary High Byte Register (TEMP). This temporary register is shared by all the other 16-bit
registers. See “Accessing 16-bit Registers” on page 109.
13.10.8
Timer/Counter1 Interrupt Mask Register – TIMSK1
Bit
7
6
5
4
3
2
1
0
–
–
ICIE1
–
–
OCIE1B
OCIE1A
TOIE1
Read/Write
R
R
R/W
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TIMSK1
• Bit 7, 6 – Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 5 – ICIE1: Timer/Counter1, Input Capture Interrupt Enable
When this bit is written to one, and the I-flag in the Status Register is set (interrupts globally
enabled), the Timer/Counter1 Input Capture interrupt is enabled. The corresponding Interrupt
Vector (Table 8-2 on page 58) is executed when the ICF1 Flag, located in TIFR1, is set.
• Bit 4, 3 – Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 2 – OCIE1B: Timer/Counter1, Output Compare B Match Interrupt Enable
When this bit is written to one, and the I-flag in the Status Register is set (interrupts globally
enabled), the Timer/Counter1 Output Compare B Match interrupt is enabled. The corresponding
Interrupt Vector (Table 8-2 on page 58) is executed when the OCF1B Flag, located in TIFR1, is
set.
134
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 1 – OCIE1A: Timer/Counter1, Output Compare A Match Interrupt Enable
When this bit is written to one, and the I-flag in the Status Register is set (interrupts globally
enabled), the Timer/Counter1 Output Compare A Match interrupt is enabled. The corresponding
Interrupt Vector (Table 8-2 on page 58) is executed when the OCF1A Flag, located in TIFR1, is
set.
• Bit 0 – TOIE1: Timer/Counter1, Overflow Interrupt Enable
When this bit is written to one, and the I-flag in the Status Register is set (interrupts globally
enabled), the Timer/Counter1 Overflow interrupt is enabled. The corresponding Interrupt Vector
(Table 8-2 on page 58) is executed when the TOV1 Flag, located in TIFR1, is set.
13.10.9
Timer/Counter1 Interrupt Flag Register – TIFR1
Bit
7
6
5
4
3
2
1
0
–
–
ICF1
–
–
OCF1B
OCF1A
TOV1
Read/Write
R
R
R/W
R
R
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
TIFR1
• Bit 7, 6 – Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 5 – ICF1: Timer/Counter1, Input Capture Flag
This flag is set when a capture event occurs on the ICP1 pin. When the Input Capture Register
(ICR1) is set by the WGMn3:0 to be used as the TOP value, the ICF1 Flag is set when the counter reaches the TOP value.
ICF1 is automatically cleared when the Input Capture Interrupt Vector is executed. Alternatively,
ICF1 can be cleared by writing a logic one to its bit location.
• Bit 4, 3 – Res: Reserved Bits
These bits are unused bits in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 2 – OCF1B: Timer/Counter1, Output Compare B Match Flag
This flag is set in the timer clock cycle after the counter (TCNT1) value matches the Output
Compare Register B (OCR1B).
Note that a Forced Output Compare (FOC1B) strobe will not set the OCF1B Flag.
OCF1B is automatically cleared when the Output Compare Match B Interrupt Vector is executed. Alternatively, OCF1B can be cleared by writing a logic one to its bit location.
• Bit 1 – OCF1A: Timer/Counter1, Output Compare A Match Flag
This flag is set in the timer clock cycle after the counter (TCNT1) value matches the Output
Compare Register A (OCR1A).
Note that a Forced Output Compare (FOC1A) strobe will not set the OCF1A Flag.
OCF1A is automatically cleared when the Output Compare Match A Interrupt Vector is executed. Alternatively, OCF1A can be cleared by writing a logic one to its bit location.
• Bit 0 – TOV1: Timer/Counter1, Overflow Flag
The setting of this flag is dependent of the WGMn3:0 bits setting. In Normal and CTC modes,
the TOV1 Flag is set when the timer overflows. Refer to Table 13-4 on page 131 for the TOV1
Flag behavior when using another WGMn3:0 bit setting.
TOV1 is automatically cleared when the Timer/Counter1 Overflow Interrupt Vector is executed.
Alternatively, TOV1 can be cleared by writing a logic one to its bit location.
135
7647F–AVR–04/09
14. Power Stage Controller – (PSC) (only ATmega16/32/64M1)
The Power Stage Controller is a high performance waveform controller.
14.1
Features
• PWM waveform generation function with 6 complementary programmable outputs (able to
•
•
•
•
•
•
•
14.2
control 3 half-bridges)
Programmable dead time control
PWM up to 12 bit resolution
PWM clock frequency up to 64 MHz (via PLL)
Programmable ADC trigger
Automatic Overlap protection
Failsafe emergency inputs - 3 (to force all outputs to high impedance or in inactive state - fuse
configurable)
Center aligned and edge aligned modes synchronization
Overview
Many register and bit references in this section are written in general form.
• A lower case “n” replaces the PSC module number, in this case 0, 1 or 2. However, when
using the register or bit defines in a program, the precise form must be used, i.e.,
POCR0SAH for accessing module 0 POCRnSAH register and so on.
• A lower case “x” replaces the PSC part , in this case A or B. However, when using the register
or bit defines in a program, the precise form must be used, i.e., OCR0SAH for accessing part
A OCR0SxH register and so on.
The purpose of the Power Stage Controller (PSC) is to control an external power interface. It has
six outputs to drive for example a 3 half-bridge. This feature allows you to generate three phase
waveforms for applications such as Asynchronous or BLDC motor drives, lighting systems...
The PSC also has 3 inputs, the purpose of which is to provide fast emergency stop capability.
The PSC outputs are programmable as “active high” or “active low”. All the timing diagrams in
the following examples are given in the “active high” polarity.
14.3
Accessing 16-bit Registers
Some PSC registers are 16-bit registers. These registers can be accessed by the AVR CPU via
the 8-bit data bus. The 16-bit registers must be byte accessed using two read or write operations. The PSC has a single 8-bit register for temporary storing of the high byte of the 16-bit
access. The same temporary register is shared between all PSC 16-bit registers. Accessing the
low byte triggers the 16-bit read or write operation. When the low byte of a 16-bit register is written by the CPU, the high byte stored in the temporary register, and the low byte written are both
copied into the 16-bit register in the same clock cycle. When the low byte of a 16-bit register is
read by the CPU, the high byte of the 16-bit register is copied into the temporary register in the
same clock cycle as the low byte is read.
To do a 16-bit write, the high byte must be written before the low byte. For a 16-bit read, the low
byte must be read before the high byte.
136
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
14.4
PSC Description
Figure 14-1. Power Stage Controller Block Diagram
PSC Counter
CLKIO
Prescaler
CLKPLL
POCR0RB
=
module 0
DATABUS
POCR0SB
POCR0RA
POCR0SA
Waveform
Generator B
=
Overlap
Protection
=
PSCOUT0B
(Analog Comparator 0 Ouput)
AC0O
PSC Input 0
PSCIN0
Waveform
Generator A
=
PISEL0
PSCOUT0A
module 1
POCR1SB
POCR1RA
POCR1SA
Waveform
Generator B
=
Overlap
Protection
=
PSCOUT1B
(Analog Comparator 1 Ouput)
AC1O
PSC Input 1
PSCIN1
Waveform
Generator A
=
PISEL1
PSCOUT1A
module 2
POCR2SB
POCR2RA
POCR2SA
Waveform
Generator B
=
Overlap
Protection
=
PSCOUT2B
(Analog Comparator 2 Ouput)
AC2O
PSC Input 2
PSCIN2
Waveform
Generator A
=
PISEL2
PSCOUT2A
PSOCn
PCNFn
PCTLn
PFRCnB
PFRCnA
137
7647F–AVR–04/09
The PSC is based on the use of a free-running 12-bit counter (PSC counter). This counter is
able to count up to a top value determined by the contents of POCR_RB register and then
according to the selected running mode, count down or reset to zero for another cycle.
As can be seen from the block diagram Figure 14-1, the PSC is composed of 3 modules.
Each of the 3 PSC modules can be seen as two symetrical entities. One entity named part A
which generates the output PSCOUTnA and the second one named part B which generates the
PSCOUTnB output.
Each module has its own PSC Input circuitry which manages the corresponding input.
14.5
14.5.1
Functional Description
Generation of Control Waveforms
In general, the drive of a 3 phase motor requires the generation of 6 PWM signals. The duty
cycle of these signals must be independently controlled to adjust the speed or torque of the
motor or to produce the wanted waveform on the 3 voltage lines (trapezoidal, sinusoidal...)
In case of cross conduction or overtemperature, having inputs which can immediately disable
the waveform generator’s outputs is desirable.
These considerations are common for many systems which require PWM signals to drive power
systems such as lighting, DC/DC converters...
14.5.2
Waveform Cycles
Each of the 3 modules has 2 waveform generators which jointly compose the output signal.
The first part of the waveform is relative to part A or PSCOUTnA output. This waveform corresponds to sub-cycle A in the following figure.
The second part of the waveform is relative to part B or PSCOUTnB output. This waveform corresponds to sub-cycle B in the following figure.
The complete waveform is terminated at the end of the sub-cycle B, whereupon any changes to
the settings of the waveform generator registers will be implemented, for the next cycle.
The PSC can be configured in one of two modes (1Ramp Mode or Centered Mode). This configuration will affect the operation of all the waveform generators.
Figure 14-2. Cycle Presentation in One Ramp Mode
One PSC Cycle
Sub-Cycle A
Sub-Cycle B
PSC Counter Value
UPDATE
138
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 14-3. Cycle Presentation in Centered Mode
One PSC Cycle
PSC Counter Value
UPDATE
Figure 14-2 and Figure 14-3 graphically illustrate the values held in the PSC counter. Centered
Mode is like One Ramp Mode which counts down and then up.
Notice that the update of the waveform generator registers is done regardless of ramp Mode at
the end of the PSC cycle.
14.5.3
Operation Mode Descriptions
Waveforms and duration of output signals are determined by parameters held in the registers
(POCRnSA, POCRnRA, POCRnSB, POCR_RB) and by the running mode. Two modes are possible :
• One Ramp Mode. In this mode, all the 3 PSCOUTnB outputs are edge-aligned and the 3
PSCOUTnA can be also edge-aligned when setting the same values in the dedicated
registers.
In this mode, the PWM frequency is twice the Center Aligned Mode PWM frequency.
• Center Aligned Mode. In this mode, all the 6 PSC outputs are aligned at the center of the
period. Except when using the same duty cycles on the 3 modules, the edges of the outputs
are not aligned. So the PSC outputs do not commute at the same time, thus the system
which is driven by these outputs will generate less commutation noise.
In this mode, the PWM frequency is twice slower than in One Ramp Mode.
14.5.3.1
One Ramp Mode (Edge-Aligned)
The following figure shows the resultant outputs PSCOUTnA and PSCOUTnB operating in one
ramp mode over a PSC cycle.
139
7647F–AVR–04/09
Figure 14-4. PSCOUTnA & PSCOUTnB Basic Waveforms in One Ramp mode
POCRnRB
POCRnSB
POCRnRA
PSC Counter
POCRnSA
0
On-Time A
On-Time B
PSCOUTnA
PSCOUTnB
Dead-Time B
Dead-Time A
PSC Cycle
On-Time A = (POCRnRAH/L - POCRnSAH/L) * 1/Fclkpsc
On-Time B = (POCRnRBH/L - POCRnSBH/L) * 1/Fclkpsc
Dead-Time A = (POCRnSAH/L + 1) * 1/Fclkpsc
Dead-Time B = (POCRnSBH/L - POCRnRAH/L) * 1/Fclkpsc
Minimal value for Dead-Time A = 1/Fclkpsc
If the overlap protection is disabled, in One-Ramp mode, PSCOUTnA and PSCOUTnB outputs
can be configured to overlap each other, though in normal use this is not desirable.
140
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 14-5. Controlled Start and Stop Mechanism in One-Ramp Mode
POCRnRB
POCRnSB
POCRnRA
POCRnSA
PSC Counter
0
Run
PSCOUTnA
PSCOUTnB
Note:
14.5.3.2
See “PSC Control Register – PCTL” on page 154. (PCCYC = 1)
Center Aligned Mode
In center aligned mode, the center of PSCOUTnA and PSCOUTnB signals are centered.
Figure 14-6. PSCOUTnA & PSCOUTnB Basic Waveforms in Center Aligned Mode
POCRnRB
PSC Counter
POCRnSB
POCRnSA
0
On-Time 0
On-Time 1
On-Time 1
PSCOUTnA
PSCOUTnB
Dead-Time
Dead-Time
PSC Cycle
On-Time 0 = 2 * POCRnSAH/L * 1/Fclkpsc
On-Time 1 = 2 * (POCRnRBH/L - POCRnSBH/L + 1) * 1/Fclkpsc
Dead-Time = (POCRnSBH/L - POCRnSAH/L) * 1/Fclkpsc
PSC Cycle = 2 * (POCRnRBH/L + 1) * 1/Fclkpsc
Minimal value for PSC Cycle = 2 * 1/Fclkpsc
141
7647F–AVR–04/09
Note that in center aligned mode, POCRnRAH/L is not required (as it is in one-ramp mode) to
control PSC Output waveform timing. This allows POCRnRAH/L to be freely used to adjust ADC
synchronization (See “Analog Synchronization” on page 149.).
Figure 14-7. Controlled Start and Stop Mechanism in Centered Mode
POCRnRB
POCRnSB
POCRnSA
PSC Counter
0
Run
PSCOUTnA
PSCOUTnB
Note:
14.6
See “PSC Control Register – PCTL” on page 154.(PCCYC = 1)
Update of Values
To avoid unasynchronous and incoherent values in a cycle, if an update of one of several values
is necessary, all values are updated at the same time at the end of the cycle by the PSC. The
new set of values is calculated by sofware and the update is initiated by software.
Figure 14-8. Update at the end of complete PSC cycle.
Regulation Loop
Calculation
Writting in
PSC Registers
Software
Cycle
With Set i
Cycle
With Set i
Cycle
With Set i
Request for
an Update
Cycle
With Set i
PSC
Cycle
With Set j
End of Cycle
The software can stop the cycle before the end to update the values and restart a new PSC
cycle.
142
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
14.6.1
Value Update Synchronization
New timing values or PSC output configuration can be written during the PSC cycle. Thanks to
LOCK configuration bit, the new whole set of values can be taken into account after the end of
the PSC cycle.
When LOCK configuration bit is set, there is no update. The update of the PSC internal registers
will be done at the end of the PSC cycle if the LOCK bit is released to zero.
The registers which update is synchronized thanks to LOCK are POC, POM2, POCRnSAH/L,
POCRnRAH/L, POCRnSBH/L and POCRnRBH/L.
See these register’s description starting on page 153.
See “PSC Configuration Register – PCNF” on page 153.
14.7
Overlap Protection
Thanks to Overlap Protection two outputs on a same module cannot be active at the same time.
So it cannot generate cross conduction. This feature can be disactivated thanks to POVEn (PSC
Overlap Enable).
For ATmega16/64M1, and ATmega32M1 since rev C, the overlap protection is activated with
only one condition:
1. POVENn=0 (PSC Module n Overlap Enable)
Up to rev B of ATmega32M1, the overlap protection was activated with the 2 following
conditions:
2. POVENn=0 (PSC Module n Overlap Enable)
3. The two channels A and B of a pwm pair n must be activated (POENnA=POENnB= 1)
This difference can induce some behavior change between rev B & rev C of ATmega32M1,
when only one channel of a PWM pair output is active.
To avoid such behavior, it is recommended in case of using only one channel of a pwm pair, to
disable Overlap protection bit (POVENn =1).
143
7647F–AVR–04/09
14.8
Signal Description
Figure 14-9. PSC External Block View
CLK PLL
CLK I/O
POCRRB[11:0]
POCR0SB[11:0]
POCR0RA[11:0]
POCR0SA[11:0]
POCR1SB[11:0]
POCR1RA[11:0]
POCR1SA[11:0]
POCR2SB[11:0]
POCR2RA[11:0]
POCR2SA[11:0]
12
PSCOUT0A
12
PSCOUT0B
12
PSCOUT1A
PSCOUT1B
12
PSCOUT2A
12
PSCOUT2B
12
AC2O
12
AC1O
12
AC0O
12
PSCIN2
12
PSCIN1
PSCIN0
IRQ PSC
144
PSCASY
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
14.8.1
Input Description
Table 14-1.
Internal Inputs
Name
Type
Width
POCR_RB[11:0]
Compare Value which Reset Signal on Part B (PSCOUTnB)
Register
12 bits
POCRnSB[11:0]
Compare Value which Set Signal on Part B (PSCOUTnB)
Register
12 bits
POCRnRA[11:0]
Compare Value which Reset Signal on Part A (PSCOUTnA)
Register
12 bits
POCRnSA[11:0]
Compare Value which Set Signal on Part A (PSCOUTnA)
Register
12 bits
CLK I/O
Clock Input from I/O clock
Signal
CLK PLL
Clock Input from PLL
Signal
AC0O
Analog Comparator 0 Output
Signal
AC1O
Analog Comparator 1 Output
Signal
AC2O
Analog Comparator 2 Output
Signal
Table 14-2.
Block Inputs
Description
Type
Width
PSCIN0
Input 0 used for Fault function
Signal
PSCIN1
Input 1 used for Fault function
Signal
PSCIN2
Input 2 used for Fault function
Signal
Name
14.8.2
Description
Output Description
Table 14-3.
Block Outputs
Description
Type
Width
PSCOUT0A
PSC Module 0 Output A
Signal
PSCOUT0B
PSC Module 0 Output B
Signal
PSCOUT1A
PSC Module 1 Output A
Signal
PSCOUT1B
PSC Module 1 Output B
Signal
PSCOUT2A
PSC Module 2 Output A
Signal
PSCOUT2B
PSC Module 2 Output B
Signal
Name
Table 14-4.
Internal Outputs
Description
Type
Width
IRQPSCn
PSC Interrupt Request : two souces, overflow, fault
Signal
PSCASY
ADC Synchronization (+ Amplifier Syncho. )(1)
Signal
Name
Note:
1. See “Analog Synchronization” on page 149.
145
7647F–AVR–04/09
14.9
PSC Input
For detailed information on the PSC, please refer to Application Note ‘AVR138: PSC Cookbook’,
available on the Atmel web site.
Each module 0, 1 and 2 of PSC has its own system to take into account one PSC input. According to PSC Module n Input Control Register (See “PSC Module n Input Control Register –
PMICn” on page 155.), PSCINn input can act has a Retrigger or Fault input.
Each block A or B is also configured by this PSC Module n Input Control Register (PMICn).
Figure 14-10. PSC Input Module
PAOCnA
(PAOCnB)
0
PSCINn
Analog
Comparator
n Output
0
Digital
Filter
1
1
CLK PSC
PFLTEnA
(PFLTEnB)
PISELnA
(PISELnB)
PELEVnA /
(PELEVnB)
PCAEnA
(PCAEnB)
PRFMnA3:0
(PRFMnB3:0)
2
4
Input
Processing
(retriggering ...)
CLK PSC
PSC Core
(Counter,
Waveform
Generator, ...)
Control
of the
6 outputs
PSCOUTnA
PSCOUTnB
CLK PSC
14.9.1
14.9.1.1
PSC Input Configuration
The PSC Input Configuration is done by programming bits in configuration registers.
Filter Enable
If the “Filter Enable” bit is set, a digital filter of 4 cycles is inserted before evaluation of the signal.
The disable of this function is mainly needed for prescaled PSC clock sources, where the noise
cancellation gives too high latency.
Important: If the digital filter is active, the level sensitivity is true also with a disturbed PSC clock
to deactivate the outputs (emergency protection of external component). Likewise when used as
fault input, PSC Module n Input A or Input B have to go through PSC to act on PSCOUTn0/1/2
outputs. This way needs that CLKPSC is running. So thanks to PSC Asynchronous Output Control bit (PAOCnA/B), PSCINn input can desactivate directly the PSC outputs. Notice that in this
case, input is still taken into account as usually by Input Module System as soon as CLKPSC is
running.
146
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 14-11. PSC Input Filterring
CLKPSC
Digital
Filter
4 x CLK PSC
PSC Input
Module X
14.9.1.2
PSC Module n Input
Ouput
Stage
PSCOUTnX
PIN
Signal Polarity
One can select the active edge (edge modes) or the active level (level modes) See PELEVnx bit
description in Section "PSC Module n Input Control Register – PMICn", page 155.
If PELEVnx bit set, the significant edge of PSCn Input A or B is rising (edge modes) or the active
level is high (level modes) and vice versa for unset/falling/low
• In 2- or 4-ramp mode, PSCn Input A is taken into account only during Dead-Time0 and
On-Time0 period (respectively Dead-Time1 and On-Time1 for PSCn Input B).
• In 1-ramp-mode PSC Input A or PSC Input B act on the whole ramp.
14.9.1.3
Input Mode Operation
Thanks to 4 configuration bits (PRFM3:0), it’s possible to define the mode of the PSC inputs.
Table 14-5.
PSC Input Mode Operation
PRFMn2:0
Description
000b
No action, PSC Input is ignored
001b
Disactivate module n Outputs A
010b
Disactivate module n Output B
011b
Disactivate module n Output A & B
10x
Disactivate all PSC Output
11xb
Halt PSC and Wait for Software Action
Notice: All following examples are given with rising edge or high level active inputs.
147
7647F–AVR–04/09
14.10 PSC Input Modes 001b to 10xb: Deactivate outputs without changing timing.
Figure 14-12. PSC behaviour versus PSCn Input in Mode 001b to 10xb
DT0
OT0
DT1
OT1
DT0
OT0
DT1
OT1
DT0
OT0
DT1
OT1
PSCOUTnA
PSCOUTnB
PSCn Input
Figure 14-13. PSC behaviour versus PSCn Input A or Input B in Fault Mode 4
DT0
OT0
DT1
OT1
DT0
OT0
DT1
OT1
DT0
OT0
DT1
OT1
PSCOUTnA
PSCOUTnB
PSCn Input
PSCn Input acts indifferently on On-Time0/Dead-Time0 or on On-Time1/Dead-Time1.
14.11 PSC Input Mode 11xb: Halt PSC and Wait for Software Action
Figure 14-14. PSC behaviour versus PSCn Input A in Fault Mode 11xb
DT0
OT0
DT1
OT1
DT0 OT0
DT0
OT0
DT1
OT1
PSCOUTnA
PSCOUTnB
PSCn Input
Software Action (1)
Note:
148
Software action is the setting of the PRUNn bit in PCTLn register.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Used in Fault mode 7, PSCn Input A or PSCn Input B act indifferently on On-Time0/Dead-Time0
or on On-Time1/Dead-Time1.
14.12 Analog Synchronization
Each PSC module generates a signal to synchronize the ADC sample and hold; synchronisation
is mandatory for measurements.
This signal can be selected between all falling or rising edge of PSCOUTnA or PSCOUTnB
outputs.
In center aligned mode, OCRnRAH/L is not used, so it can be used to specified the synchronization of the ADC. It this case, it’s minimum value is 1.
14.13 Interrupt Handling
As each PSC module can be dedicated for one function, each PSC has its own interrupt system
(vector ...)
List of interrupt sources:
• Counter reload (end of On Time 1)
• PSC Input event (active edge or at the beginning of level configured event)
• PSC Mutual Synchronization Error
14.14 PSC Clock Sources
Each PSC has two clock inputs:
• CLK PLL from the PLL
• CLK I/O
Figure 14-15. Clock selection
CLK
PLL
1
CK
PCLKSEL
CK/4
CK/32
CK/256
01
10
11
0
CK
I/O
00
CLK
PRESCALER
PPREn1/0
CLK PSCn
PCLKSELn bit in PSC Control Register (PCTL) is used to select the clock source.
PPREn1/0 bits in PSC Control Register (PCTL) are used to select the divide factor of the clock.
149
7647F–AVR–04/09
Table 14-6.
Output Clock versus Selection and Prescaler
PCLKSELn
PPREn1
PPREn0
CLKPSCn output
0
0
0
CLK I/O
0
0
1
CLK I/O / 4
0
1
0
CLK I/O / 32
0
1
1
CLK I/O / 256
1
0
0
CLK PLL
1
0
1
CLK PLL / 4
1
1
0
CLK PLL / 32
1
1
1
CLK PLL / 256
14.15 Interrupts
This section describes the specifics of the interrupt handling as performed in
ATmega16/32/64/M1/C1.
14.15.1
Interrupt Vector
PSC provides 2 interrupt vectors:
• PSC_End (End of Cycle): When enabled and when a match with POCR_RB occurs
• PSC_Fault (Fault Event): When enabled and when a PSC input detects a Fault event.
14.15.2
PSC Interrupt Vectors in ATmega16/32/64/M1/C1
Table 14-7.
150
PSC Interrupt Vectors
Vector
No.
Program
Address
-
-
5
0x0004
PSC_Fault
PSC Fault event
6
0x0005
PSC_End
PSC End of Cycle
-
-
-
-
-
-
Source
Interrupt Definition
-
-
-
-
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
14.16 PSC Register Definition
Registers are explained for PSC module 0. They are identical for module 1 and module 2.
14.16.1
PSC Output Configuration – POC
Bit
7
6
5
4
3
2
1
0
-
-
POEN2B
POEN2A
POEN1B
POEN1A
POEN0B
POEN0A
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
POC
• Bit 7 – not use
not use
• Bit 6 – not use
not use
• Bit 5 – POEN2B: PSC Output 2B Enable
When this bit is clear, I/O pin affected to PSCOUT2B acts as a standard port.
When this bit is set, I/O pin affected to PSCOUT2B is connected to the PSC module 2 waveform
generator B output and is set and clear according to the PSC operation.
• Bit 4 – POEN2A: PSC Output 2A Enable
When this bit is clear, I/O pin affected to PSCOUT2A acts as a standard port.
When this bit is set, I/O pin affected to PSCOUT2A is connected to the PSC module 2 waveform
generator A output and is set and clear according to the PSC operation.
• Bit 3 – POEN1B: PSC Output 1B Enable
When this bit is clear, I/O pin affected to PSCOUT1B acts as a standard port.
When this bit is set, I/O pin affected to PSCOUT1B is connected to the PSC module 1 waveform
generator B output and is set and clear according to the PSC operation.
• Bit 2 – POEN1A: PSC Output 1A Enable
When this bit is clear, I/O pin affected to PSCOUT1A acts as a standard port.
When this bit is set, I/O pin affected to PSCOUT1A is connected to the PSC module 1 waveform
generator A output and is set and clear according to the PSC operation.
• Bit 1 – POEN0B: PSC Output 0B Enable
When this bit is clear, I/O pin affected to PSCOUT0B acts as a standard port.
When this bit is set, I/O pin affected to PSCOUT0B is connected to the PSC module 0 waveform
generator B output and is set and clear according to the PSC operation.
• Bit 0 – POEN0A: PSC Output 0A Enable
When this bit is clear, I/O pin affected to PSCOUT0A acts as a standard port.
When this bit is set, I/O pin affected to PSCOUT0A is connected to the PSC module 0 waveform
generator A output and is set and clear according to the PSC operation.
151
7647F–AVR–04/09
14.16.2
PSC Synchro Configuration – PSYNC
Bit
7
6
5
4
3
2
1
0
-
-
PSYNC21
PSYNC20
PSYNC11
PSYNC10
PSYNC01
PSYNC00
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PSYNC
• Bit 7 – not use
not use
• Bit 6 – not use
not use
• Bit 5:4 – PSYNC21:0: Synchronization Out for ADC Selection
Select the polarity and signal source for generating a signal which will be sent from module 2 to
the ADC for synchronization
• Bit 3:2 – PSYNC11:0: Synchronization Out for ADC Selection
Select the polarity and signal source for generating a signal which will be sent from module 1 to
the ADC for synchronization
• Bit 1:0 – PSYNC01:0: Synchronization Out for ADC Selection
Select the polarity and signal source for generating a signal which will be sent from module 0 to
the ADC for synchronization.
Table 14-8.
PSYNCn1
PSYNCn0
Description
0
0
Send signal on leading edge of PSCOUTnA(match with OCRnSA)
0
1
Send signal on trailing edge of PSCOUTnA(match with OCRnRA or
fault/retrigger on part A)
1
0
Send signal on leading edge of PSCOUTnB (match with OCRnSB)
1
1
Send signal on trailing edge of PSCOUTnB (match with OCRnRB or
fault/retrigger on part B)
Table 14-9.
152
Synchronization Source Description in One Ramp Mode
Synchronization Source Description in Centered Mode
PSYNCn1
PSYNCn0
Description
0
0
Send signal on match with OCRnRA (during counting down of PSC). The
min value of OCRnRA must be 1.
0
1
Send signal on match with OCRnRA (during counting up of PSC). The
min value of OCRnRA must be 1.
1
0
no synchronization signal
1
1
no synchronization signal
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
14.16.3
PSC Output Compare SA Register – POCRnSAH and POCRnSAL
Bit
7
6
5
4
–
–
–
–
3
2
1
0
POCRnSA[11:8]
POCRnSAH
POCRnSA[7:0]
14.16.4
POCRnSAL
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
2
1
0
PSC Output Compare RA Register – POCRnRAH and POCRnRAL
Bit
7
6
5
4
–
–
–
–
3
POCRnRA[11:8]
POCRnRAH
POCRnRA[7:0]
14.16.5
POCRnRAL
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
2
1
0
PSCOutput Compare SB Register – POCRnSBH and POCRnSBL
Bit
7
6
5
4
–
–
–
–
3
POCRnSB[11:8]
POCRnSBH
POCRnSB[7:0]
14.16.6
OCRnSBL
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
2
1
0
PSC Output Compare RB Register – POCR_RBH and POCR_RBL
Bit
7
6
5
4
–
–
–
–
3
POCRnRB[11:8]
POCR_RBH
POCRnRB[7:0]
POCR_RBL
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
Note:
n = 0 to 2 according to module number.
The Output Compare Registers RA, RB, SA and SB contain a 12-bit value that is continuously
compared with the PSC counter value. A match can be used to generate an Output Compare
interrupt, or to generate a waveform output on the associated pin.
The Output Compare Registers are 16bit and 12-bit in size. To ensure that both the high and low
bytes are written simultaneously when the CPU writes to these registers, the access is performed using an 8-bit temporary high byte register (TEMP). This temporary register is shared by
all the other 16-bit registers.
14.16.7
PSC Configuration Register – PCNF
Bit
7
6
5
4
3
2
1
-
-
PULOCK
PMODE
POPB
POPA
-
0
-
Read/Write
R
R
R/W
R/W
R/W
R/W
R
R
Initial Value
0
0
0
0
0
0
0
0
PCNF
• Bit 7:6 - not use
not use
• Bit 5 – PULOCK: PSC Update Lock
When this bit is set, the Output Compare Registers POCRnRA, POCRnSA, POCRnSB,
POCR_RB and the PSC Output Configuration Registers POC can be written without disturbing
the PSC cycles. The update of the PSC internal registers will be done if the PULOCK bit is
released to zero.
153
7647F–AVR–04/09
• Bit 4 – PMODE PSC Mode
Select the mode of PSC.
Table 14-10. PSC Mode Selection
PMODE
Description
0
One Ramp Mode (Edge Aligned)
1
Center Aligned Mode
• Bit 3 – POPB: PSC B Output Polarity
If this bit is cleared, the PSC outputs B are active Low.
If this bit is set, the PSC outputs B are active High.
• Bit 2 – POPA: PSC A Output Polarity
If this bit is cleared, the PSC outputs A are active Low.
If this bit is set, the PSC outputs A are active High.
• Bit 1:0 – not use
not use
14.16.8
PSC Control Register – PCTL
Bit
7
6
5
4
3
2
1
0
PPRE1
PPRE0
PCLKSEL
SWAP2
SWAP1
SWAP0
PCCYC
PRUN
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PCTL
• Bit 7:6 – PPRE1:0 : PSC Prescaler Select
This two bits select the PSC input clock division factor. All generated waveform will be modified
by this factor.
Table 14-11. PSC Prescaler Selection
PPRE1
PPRE0
Description
0
0
No divider on PSC input clock
0
1
Divide the PSC input clock by 4
1
0
Divide the PSC input clock by 32
1
1
Divide the PSC clock by 256
• Bit 5 – PCLKSEL: PSC Input Clock Select
This bit is used to select between CLKPLL or CLKIO clocks.
Set this bit to select the fast clock input (CLKPLL).
Clear this bit to select the slow clock input (CLKIO).
154
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 4:3:2 – SWAPn: SWAP Funtion Select (not implemented in ATmega32M1 up to
revision C)
When this bit is set; the channels PSCOUTnA and PSCOUTnB are exchanged. This allows to
invert the waveforms of both channels at one time.
• Bit 1 – PCCYC: PSC Complete Cycle
When this bit is set, the PSC completes the entire waveform cycle before halt operation
requested by clearing PRUN.
• Bit 0 – PRUN : PSC Run
Writing this bit to one starts the PSC.
14.16.9
PSC Module n Input Control Register – PMICn
Bit
7
6
5
4
3
2
1
0
POVENn
PISELn
PELEVn
PFLTEn
PAOCn
PRFMn2
PRFMn1
PRFMn0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PMICn
The Input Control Registers are used to configure the 2 PSC’s Retrigger/Fault block A & B. The
2 blocks are identical, so they are configured on the same way.
• Bit 7 – POVENn : PSC Module n Overlap Enable
Set this bit to disactivate the Overlap Protection. See the Section “Overlap Protection”,
page 143.
• Bit 6 – PISELn : PSC Module n Input Select
Clear this bit to select PSCINn as module n input.
Set this bit to select Comparator n output as module n input.
• Bit 5 –PELEVn : PSC Module n Input Level Selector
When this bit is clear, the low level of selected input generates the significative event for fault
function.
When this bit is set, the high level of selected input generates the significative event for fault
function.
• Bit 4 – PFLTEn : PSC Module n Input Filter Enable
Setting this bit (to one) activates the Input Noise Canceler. When the noise canceler is activated,
the input from the input pin is filtered. The filter function requires four successive equal valued
samples of the input pin for changing its output. The Input is therefore delayed by four oscillator
cycles when the noise canceler is enabled.
• Bit 3 – PAOCn : PSC Module n 0 Asynchronous Output Control
When this bit is clear, Fault input can act directly to PSC module n outputs A & B. See
Section “PSC Input Configuration”, page 146.
• Bit 2:0 – PRFMn2:0: PSC Module n Input Mode
These three bits define the mode of operation of the PSC inputs.
155
7647F–AVR–04/09
Table 14-12. Input Mode Operation
PRFMn2:0
Description
000b
No action, PSC Input is ignored
001b
Disactivate module n Outputs A
010b
Disactivate module n Output B
011b
Disactivate module n Output A & B
10x
Disactivate all PSC Output
11xb
Halt PSC and Wait for Software Action
14.16.10 PSC Interrupt Mask Register – PIM
Bit
7
6
5
4
3
2
1
0
-
-
-
-
PEVE2
PEVE1
PEVE0
PEOPE
Read/Write
R
R
R
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PIM
• Bit 7:4 – not use
not use.
• Bit 3 – PEVE2 : PSC External Event 2 Interrupt Enable
When this bit is set, an external event which can generates a a fault on module 2 generates also
an interrupt.
• Bit 2 – PEVE1 : PSC External Event 1 Interrupt Enable
When this bit is set, an external event which can generates a fault on module 1 generates also
an interrupt.
• Bit 1 – PEVE0 : PSC External Event 0 Interrupt Enable
When this bit is set, an external event which can generates a fault on module 0 generates also
an interrupt.
• Bit 0 – PEOPE : PSC End Of Cycle Interrupt Enable
When this bit is set, an interrupt is generated when PSC reaches the end of the whole cycle.
156
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
14.16.11 PSC Interrupt Flag Register – PIFR
Bit
7
6
5
4
3
2
1
0
-
-
-
-
PEV2
PEV1
PEV0
PEOP
Read/Write
R
R
R
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
PIFR
• Bit 7:4 – not use
not use.
• Bit 3 – PEV2 : PSC External Event 2 Interrupt
This bit is set by hardware when an external event which can generates a fault on module 2
occurs.
Must be cleared by software by writing a one to its location.
This bit can be read even if the corresponding interrupt is not enabled (PEVE2 bit = 0).
• Bit 2 – PEV1 : PSC External Event 1 Interrupt
This bit is set by hardware when an external event which can generates a fault on module 1
occurs.
Must be cleared by software by writing a one to its location.
This bit can be read even if the corresponding interrupt is not enabled (PEVE1 bit = 0).
• Bit 1 – PEV0 : PSC External Event 0 Interrupt
This bit is set by hardware when an external event which can generates a fault on module 0
occurs.
Must be cleared by software by writing a one to its location.
This bit can be read even if the corresponding interrupt is not enabled (PEVE0 bit = 0).
• Bit 0 – PEOP : PSC End Of Cycle Interrupt
This bit is set by hardware when an “end of PSC cycle” occurs.
Must be cleared by software by writing a one to its location.
This bit can be read even if the corresponding interrupt is not enabled (PEOPE bit = 0).
157
7647F–AVR–04/09
15. Serial Peripheral Interface – SPI
The Serial Peripheral Interface (SPI) allows high-speed synchronous data transfer between the
ATmega16/32/64/M1/C1 and peripheral devices or between several AVR devices.
The ATmega16/32/64/M1/C1 SPI includes the following features:
15.1
Features
•
•
•
•
•
•
•
•
Full-duplex, Three-wire Synchronous Data Transfer
Master or Slave Operation
LSB First or MSB First Data Transfer
Seven Programmable Bit Rates
End of Transmission Interrupt Flag
Write Collision Flag Protection
Wake-up from Idle Mode
Double Speed (CK/2) Master SPI Mode
Figure 15-1. SPI Block Diagram(1)
SPIPS
MISO
MISO
_A
clk IO
MOSI
MOSI
_A
DIVIDER
/2/4/8/16/32/64/128
SCK
SCK
_A
SPI2X
SS
SPI2X
SS_A
Note:
158
1. Refer to Figure 1-1 on page 3, and Table 9-3 on page 69 for SPI pin placement.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The interconnection between Master and Slave CPUs with SPI is shown in Figure 15-2. The system consists of two shift Registers, and a Master clock generator. The SPI Master initiates the
communication cycle when pulling low the Slave Select SS pin of the desired Slave. Master and
Slave prepare the data to be sent in their respective shift Registers, and the Master generates
the required clock pulses on the SCK line to interchange data. Data is always shifted from Master to Slave on the Master Out – Slave In, MOSI, line, and from Slave to Master on the Master In
– Slave Out, MISO, line. After each data packet, the Master will synchronize the Slave by pulling
high the Slave Select, SS, line.
When configured as a Master, the SPI interface has no automatic control of the SS line. This
must be handled by user software before communication can start. When this is done, writing a
byte to the SPI Data Register starts the SPI clock generator, and the hardware shifts the eight
bits into the Slave. After shifting one byte, the SPI clock generator stops, setting the end of
transmission flag (SPIF). If the SPI Interrupt Enable bit (SPIE) in the SPCR Register is set, an
interrupt is requested. The Master may continue to shift the next byte by writing it into SPDR, or
signal the end of packet by pulling high the Slave Select, SS line. The last incoming byte will be
kept in the Buffer Register for later use.
When configured as a Slave, the SPI interface will remain sleeping with MISO tri-stated as long
as the SS pin is driven high. In this state, software may update the contents of the SPI Data
Register, SPDR, but the data will not be shifted out by incoming clock pulses on the SCK pin
until the SS pin is driven low. As one byte has been completely shifted, the end of transmission
flag, SPIF is set. If the SPI Interrupt Enable bit, SPIE, in the SPCR Register is set, an interrupt is
requested. The Slave may continue to place new data to be sent into SPDR before reading the
incoming data. The last incoming byte will be kept in the Buffer Register for later use.
Figure 15-2. SPI Master-slave Interconnection
SHIFT
ENABLE
The system is single buffered in the transmit direction and double buffered in the receive direction. This means that bytes to be transmitted cannot be written to the SPI Data Register before
the entire shift cycle is completed. When receiving data, however, a received character must be
read from the SPI Data Register before the next character has been completely shifted in. Otherwise, the first byte is lost.
In SPI Slave mode, the control logic will sample the incoming signal of the SCK pin. To ensure
correct sampling of the clock signal, the frequency of the SPI clock should never exceed fclkio/4.
159
7647F–AVR–04/09
When the SPI is enabled, the data direction of the MOSI, MISO, SCK, and SS pins is overridden
according to Table 15-1. For more details on automatic port overrides, refer to “Alternate Port
Functions” on page 67.
Table 15-1.
Pin
SPI Pin Overrides(1)
Direction, Master SPI
Direction, Slave SPI
MOSI
User Defined
Input
MISO
Input
User Defined
SCK
User Defined
Input
SS
User Defined
Input
Note:
1. See “Alternate Functions of Port B” on page 69 for a detailed description of how to define the
direction of the user defined SPI pins.
The following code examples show how to initialize the SPI as a Master and how to perform a
simple transmission.
DDR_SPI in the examples must be replaced by the actual Data Direction Register controlling the
SPI pins. DD_MOSI, DD_MISO and DD_SCK must be replaced by the actual data direction bits
for these pins. E.g. if MOSI is placed on pin PB2, replace DD_MOSI with DDB2 and DDR_SPI
with DDRB.
160
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Assembly Code Example(1)
SPI_MasterInit:
; Set MOSI and SCK output, all others input
ldi
r17,(1<<DD_MOSI)|(1<<DD_SCK)
out
DDR_SPI,r17
; Enable SPI, Master, set clock rate fck/16
ldi
r17,(1<<SPE)|(1<<MSTR)|(1<<SPR0)
out
SPCR,r17
ret
SPI_MasterTransmit:
; Start transmission of data (r16)
out
SPDR,r16
Wait_Transmit:
; Wait for transmission complete
sbis SPSR,SPIF
rjmp Wait_Transmit
ret
C Code Example(1)
void SPI_MasterInit(void)
{
/* Set MOSI and SCK output, all others input */
DDR_SPI = (1<<DD_MOSI)|(1<<DD_SCK);
/* Enable SPI, Master, set clock rate fck/16 */
SPCR = (1<<SPE)|(1<<MSTR)|(1<<SPR0);
}
void SPI_MasterTransmit(char cData)
{
/* Start transmission */
SPDR = cData;
/* Wait for transmission complete */
while(!(SPSR & (1<<SPIF)))
;
}
Note:
1. The example code assumes that the part specific header file is included.
The following code examples show how to initialize the SPI as a Slave and how to perform a
simple reception.
161
7647F–AVR–04/09
Assembly Code Example(1)
SPI_SlaveInit:
; Set MISO output, all others input
ldi
r17,(1<<DD_MISO)
out
DDR_SPI,r17
; Enable SPI
ldi
r17,(1<<SPE)
out
SPCR,r17
ret
SPI_SlaveReceive:
; Wait for reception complete
sbis SPSR,SPIF
rjmp SPI_SlaveReceive
; Read received data and return
in
r16,SPDR
ret
C Code Example(1)
void SPI_SlaveInit(void)
{
/* Set MISO output, all others input */
DDR_SPI = (1<<DD_MISO);
/* Enable SPI */
SPCR = (1<<SPE);
}
char SPI_SlaveReceive(void)
{
/* Wait for reception complete */
while(!(SPSR & (1<<SPIF)))
;
/* Return data register */
return SPDR;
}
Note:
162
1. The example code assumes that the part specific header file is included.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
15.2
15.2.1
SS Pin Functionality
Slave Mode
When the SPI is configured as a Slave, the Slave Select (SS) pin is always input. When SS is
held low, the SPI is activated, and MISO becomes an output if configured so by the user. All
other pins are inputs. When SS is driven high, all pins are inputs, and the SPI is passive, which
means that it will not receive incoming data. Note that the SPI logic will be reset once the SS pin
is driven high.
The SS pin is useful for packet/byte synchronization to keep the slave bit counter synchronous
with the master clock generator. When the SS pin is driven high, the SPI slave will immediately
reset the send and receive logic, and drop any partially received data in the Shift Register.
15.2.2
Master Mode
When the SPI is configured as a Master (MSTR in SPCR is set), the user can determine the
direction of the SS pin.
If SS is configured as an output, the pin is a general output pin which does not affect the SPI
system. Typically, the pin will be driving the SS pin of the SPI Slave.
If SS is configured as an input, it must be held high to ensure Master SPI operation. If the SS pin
is driven low by peripheral circuitry when the SPI is configured as a Master with the SS pin
defined as an input, the SPI system interprets this as another master selecting the SPI as a
slave and starting to send data to it. To avoid bus contention, the SPI system takes the following
actions:
1. The MSTR bit in SPCR is cleared and the SPI system becomes a Slave. As a result of
the SPI becoming a Slave, the MOSI and SCK pins become inputs.
2. The SPIF flag in SPSR is set, and if the SPI interrupt is enabled, and the I-bit in SREG
is set, the interrupt routine will be executed.
Thus, when interrupt-driven SPI transmission is used in Master mode, and there exists a possibility that SS is driven low, the interrupt should always check that the MSTR bit is still set. If the
MSTR bit has been cleared by a slave select, it must be set by the user to re-enable SPI Master
mode.
15.2.3
MCU Control Register – MCUCR
Bit
7
6
5
4
3
2
1
0
SPIPS
–
–
PUD
–
–
IVSEL
IVCE
Read/Write
R/W
R
R
R/W
R
R
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
MCUCR
• Bit 7– SPIPS: SPI Pin Redirection
Thanks to SPIPS (SPI Pin Select) in MCUCR Sfr, SPI pins can be redirected.
• When the SPIPS bit is written to zero, the SPI signals are directed on pins MISO,MOSI, SCK
and SS.
• When the SPIPS bit is written to one,the SPI signals are directed on alternate SPI pins,
MISO_A, MOSI_A, SCK_A and SS_A.
Note that programming port are always located on alternate SPI port.
163
7647F–AVR–04/09
15.2.4
SPI Control Register – SPCR
Bit
7
6
5
4
3
2
1
0
SPIE
SPE
DORD
MSTR
CPOL
CPHA
SPR1
SPR0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
SPCR
• Bit 7 – SPIE: SPI Interrupt Enable
This bit causes the SPI interrupt to be executed if SPIF bit in the SPSR Register is set and the if
the Global Interrupt Enable bit in SREG is set.
• Bit 6 – SPE: SPI Enable
When the SPE bit is written to one, the SPI is enabled. This bit must be set to enable any SPI
operations.
• Bit 5 – DORD: Data Order
When the DORD bit is written to one, the LSB of the data word is transmitted first.
When the DORD bit is written to zero, the MSB of the data word is transmitted first.
• Bit 4 – MSTR: Master/Slave Select
This bit selects Master SPI mode when written to one, and Slave SPI mode when written logic
zero. If SS is configured as an input and is driven low while MSTR is set, MSTR will be cleared,
and SPIF in SPSR will become set. The user will then have to set MSTR to re-enable SPI Master mode.
• Bit 3 – CPOL: Clock Polarity
When this bit is written to one, SCK is high when idle. When CPOL is written to zero, SCK is low
when idle. Refer to Figure 15-3 and Figure 15-4 for an example. The CPOL functionality is summarized below:
Table 15-2.
CPOL Functionality
CPOL
Leading Edge
Trailing Edge
0
Rising
Falling
1
Falling
Rising
• Bit 2 – CPHA: Clock Phase
The settings of the Clock Phase bit (CPHA) determine if data is sampled on the leading (first) or
trailing (last) edge of SCK. Refer to Figure 15-3 and Figure 15-4 for an example. The CPOL
functionality is summarized below:
Table 15-3.
CPHA Functionality
CPHA
Leading Edge
Trailing Edge
0
Sample
Setup
1
Setup
Sample
• Bits 1, 0 – SPR1, SPR0: SPI Clock Rate Select 1 and 0
164
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
These two bits control the SCK rate of the device configured as a Master. SPR1 and SPR0 have
no effect on the Slave. The relationship between SCK and the clkIO frequency fclkio is shown in
the following table:
Table 15-4.
15.2.5
Relationship Between SCK and the Oscillator Frequency
SPI2X
SPR1
SPR0
0
0
0
0
0
1
0
1
0
0
1
1
1
0
0
1
0
1
1
1
0
1
1
1
SCK Frequency
fclkio/4
fclkio/16
fclkio/64
fclkio/128
fclkio/2
fclkio/8
fclkio/32
fclkio/64
SPI Status Register – SPSR
Bit
7
6
5
4
3
2
1
0
SPIF
WCOL
–
–
–
–
–
SPI2X
Read/Write
R
R
R
R
R
R
R
R/W
Initial Value
0
0
0
0
0
0
0
0
SPSR
• Bit 7 – SPIF: SPI Interrupt Flag
When a serial transfer is complete, the SPIF flag is set. An interrupt is generated if SPIE in
SPCR is set and global interrupts are enabled. If SS is an input and is driven low when the SPI is
in Master mode, this will also set the SPIF flag. SPIF is cleared by hardware when executing the
corresponding interrupt handling vector. Alternatively, the SPIF bit is cleared by first reading the
SPI Status Register with SPIF set, then accessing the SPI Data Register (SPDR).
• Bit 6 – WCOL: Write COLlision Flag
The WCOL bit is set if the SPI Data Register (SPDR) is written during a data transfer. The
WCOL bit (and the SPIF bit) are cleared by first reading the SPI Status Register with WCOL set,
and then accessing the SPI Data Register.
• Bit 5..1 – Res: Reserved Bits
These bits are reserved bits in the ATmega16/32/64/M1/C1 and will always read as zero.
• Bit 0 – SPI2X: Double SPI Speed Bit
When this bit is written logic one the SPI speed (SCK Frequency) will be doubled when the SPI
is in Master mode (see Table 15-4). This means that the minimum SCK period will be two CPU
clock periods. When the SPI is configured as Slave, the SPI is only guaranteed to work at fclkio/4
or lower.
The SPI interface on the ATmega16/32/64/M1/C1 is also used for program memory and
EEPROM downloading or uploading. See Serial Programming Algorithm313 for serial programming and verification.
165
7647F–AVR–04/09
15.2.6
SPI Data Register – SPDR
Bit
7
6
5
4
3
2
1
0
SPD7
SPD6
SPD5
SPD4
SPD3
SPD2
SPD1
SPD0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
X
X
X
X
X
X
X
X
SPDR
Undefined
• Bits 7:0 - SPD7:0: SPI Data
The SPI Data Register is a read/write register used for data transfer between the Register File
and the SPI Shift Register. Writing to the register initiates data transmission. Reading the register causes the Shift Register Receive buffer to be read.
15.3
Data Modes
There are four combinations of SCK phase and polarity with respect to serial data, which are
determined by control bits CPHA and CPOL. The SPI data transfer formats are shown in Figure
15-3 and Figure 15-4. Data bits are shifted out and latched in on opposite edges of the SCK signal, ensuring sufficient time for data signals to stabilize. This is clearly seen by summarizing
Table 15-2 and Table 15-3, as done below:
Table 15-5.
CPOL Functionality
Leading Edge
Trailing eDge
SPI Mode
CPOL=0, CPHA=0
Sample (Rising)
Setup (Falling)
0
CPOL=0, CPHA=1
Setup (Rising)
Sample (Falling)
1
CPOL=1, CPHA=0
Sample (Falling)
Setup (Rising)
2
CPOL=1, CPHA=1
Setup (Falling)
Sample (Rising)
3
Figure 15-3. SPI Transfer Format with CPHA = 0
SCK (CPOL = 0)
mode 0
SCK (CPOL = 1)
mode 2
SAMPLE I
MOSI/MISO
CHANGE 0
MOSI PIN
CHANGE 0
MISO PIN
SS
MSB first (DORD = 0) MSB
LSB first (DORD = 1) LSB
166
Bit 6
Bit 1
Bit 5
Bit 2
Bit 4
Bit 3
Bit 3
Bit 4
Bit 2
Bit 5
Bit 1
Bit 6
LSB
MSB
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 15-4. SPI Transfer Format with CPHA = 1
SCK (CPOL = 0)
mode 1
SCK (CPOL = 1)
mode 3
SAMPLE I
MOSI/MISO
CHANGE 0
MOSI PIN
CHANGE 0
MISO PIN
SS
MSB first (DORD = 0)
LSB first (DORD = 1)
MSB
LSB
Bit 6
Bit 1
Bit 5
Bit 2
Bit 4
Bit 3
Bit 3
Bit 4
Bit 2
Bit 5
Bit 1
Bit 6
LSB
MSB
167
7647F–AVR–04/09
16. Controller Area Network - CAN
The Controller Area Network (CAN) protocol is a real-time, serial, broadcast protocol with a very
high level of security. The ATmega16/32/64/M1/C1 CAN controller is fully compatible with the
CAN Specification 2.0 Part A and Part B. It delivers the features required to implement the kernel of the CAN bus protocol according to the ISO/OSI Reference Model:
• The Data Link Layer
- the Logical Link Control (LLC) sublayer
- the Medium Access Control (MAC) sublayer
• The Physical Layer
- the Physical Signalling (PLS) sublayer
- not supported - the Physical Medium Attach (PMA)
- not supported - the Medium Dependent Interface (MDI)
The CAN controller is able to handle all types of frames (Data, Remote, Error and Overload) and
achieves a bitrate of 1 Mbit/s.
16.1
Features
• Full Can Controller
• Fully Compliant with CAN Standard rev 2.0 A and rev 2.0 B
• 6 MOb (Message Object) with their own:
– 11 bits of Identifier Tag (rev 2.0 A), 29 bits of Identifier Tag (rev 2.0 B)
– 11 bits of Identifier Mask (rev 2.0 A), 29 bits of Identifier Mask (rev 2.0 B)
– 8 Bytes Data Buffer (Static Allocation)
– Tx, Rx, Frame Buffer or Automatic Reply Configuration
– Time Stamping
• 1 Mbit/s Maximum Transfer Rate at 8 MHz
• TTC Timer
• Listening Mode (for Spying or Autobaud)
16.2
CAN Protocol
The CAN protocol is an international standard defined in the ISO 11898 for high speed and ISO
11519-2 for low speed.
16.2.1
Principles
CAN is based on a broadcast communication mechanism. This broadcast communication is
achieved by using a message oriented transmission protocol. These messages are identified by
using a message identifier. Such a message identifier has to be unique within the whole network
and it defines not only the content but also the priority of the message.
The priority at which a message is transmitted compared to another less urgent message is
specified by the identifier of each message. The priorities are laid down during system design in
the form of corresponding binary values and cannot be changed dynamically. The identifier with
the lowest binary number has the highest priority.
168
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Bus access conflicts are resolved by bit-wise arbitration on the identifiers involved by each node
observing the bus level bit for bit. This happens in accordance with the "wired and" mechanism,
by which the dominant state overwrites the recessive state. The competition for bus allocation is
lost by all nodes with recessive transmission and dominant observation. All the "losers" automatically become receivers of the message with the highest priority and do not re-attempt
transmission until the bus is available again.
16.2.2
16.2.2.1
Message Formats
The CAN protocol supports two message frame formats, the only essential difference being in
the length of the identifier. The CAN standard frame, also known as CAN 2.0 A, supports a
length of 11 bits for the identifier, and the CAN extended frame, also known as CAN 2.0 B, supports a length of 29 bits for the identifier.
Can Standard Frame
Figure 16-1. CAN Standard Frames
Data Frame
Bus Idle
SOF
11-bit identifier
ID10..0
Arbitration
Field
Interframe
Space
RTR IDE r0
4-bit DLC
DLC4..0
15-bit CRC
0 - 8 bytes
Control
Field
Data
Field
CRC
ACK
del. ACK del.
CRC
Field
ACK
Field
7 bits
End of
Frame
Intermission
3 bits
Bus Idle
(Indefinite)
Interframe
Space
Remote Frame
Bus Idle
Interframe
Space
SOF
11-bit identifier
ID10..0
Arbitration
Field
RTR IDE r0
4-bit DLC
DLC4..0
Control
Field
15-bit CRC
CRC
Field
CRC
ACK
del. ACK del.
ACK
Field
7 bits
End of
Frame
Intermission
3 bits
Bus Idle
(Indefinite)
Interframe
Space
A message in the CAN standard frame format begins with the "Start Of Frame (SOF)", this is followed by the "Arbitration field" which consist of the identifier and the "Remote Transmission
Request (RTR)" bit used to distinguish between the data frame and the data request frame
called remote frame. The following "Control field" contains the "IDentifier Extension (IDE)" bit
and the "Data Length Code (DLC)" used to indicate the number of following data bytes in the
"Data field". In a remote frame, the DLC contains the number of requested data bytes. The "Data
field" that follows can hold up to 8 data bytes. The frame integrity is guaranteed by the following
"Cyclic Redundant Check (CRC)" sum. The "ACKnowledge (ACK) field" compromises the ACK
slot and the ACK delimiter. The bit in the ACK slot is sent as a recessive bit and is overwritten as
a dominant bit by the receivers which have at this time received the data correctly. Correct messages are acknowledged by the receivers regardless of the result of the acceptance test. The
end of the message is indicated by "End Of Frame (EOF)". The "Intermission Frame Space
(IFS)" is the minimum number of bits separating consecutive messages. If there is no following
bus access by any node, the bus remains idle.
169
7647F–AVR–04/09
16.2.2.2
CAN Extended Frame
Figure 16-2. CAN Extended Frames
Data Frame
Bus Idle
SOF
11-bit base identifier
IDT28..18
SRR IDE
18-bit identifier extension
ID17..0
RTR r1
Arbitration
Field
Interframe
Space
r0
4-bit DLC
DLC4..0
15-bit CRC
0 - 8 bytes
Control
Field
Data
Field
CRC
Field
CRC
ACK
del. ACK del.
ACK
Field
7 bits
End of
Frame
Intermission Bus Idle
3 bits
(Indefinite)
Interframe
Space
Remote Frame
Bus Idle
Interframe
Space
SOF
11-bit base identifier
IDT28..18
SRR IDE
18-bit identifier extension
ID17..0
RTR r1
Arbitration
Field
r0
4-bit DLC
DLC4..0
Control
Field
15-bit CRC
CRC
ACK
del. ACK del.
CRC
Field
ACK
Field
7 bits
End of
Frame
Intermission
3 bits
Bus Idle
(Indefinite)
Interframe
Space
A message in the CAN extended frame format is likely the same as a message in CAN standard
frame format. The difference is the length of the identifier used. The identifier is made up of the
existing 11-bit identifier (base identifier) and an 18-bit extension (identifier extension). The distinction between CAN standard frame format and CAN extended frame format is made by using
the IDE bit which is transmitted as dominant in case of a frame in CAN standard frame format,
and transmitted as recessive in the other case.
16.2.2.3
Format Co-existence
As the two formats have to co-exist on one bus, it is laid down which message has higher priority
on the bus in the case of bus access collision with different formats and the same identifier /
base identifier: The message in CAN standard frame format always has priority over the message in extended format.
There are three different types of CAN modules available:
– 2.0A - Considers 29 bit ID as an error
– 2.0B Passive - Ignores 29 bit ID messages
– 2.0B Active - Handles both 11 and 29 bit ID Messages
16.2.3
16.2.3.1
170
CAN Bit Timing
To ensure correct sampling up to the last bit, a CAN node needs to re-synchronize throughout
the entire frame. This is done at the beginning of each message with the falling edge SOF and
on each recessive to dominant edge.
Bit Construction
One CAN bit time is specified as four non-overlapping time segments. Each segment is constructed from an integer multiple of the Time Quantum. The Time Quantum or TQ is the smallest
discrete timing resolution used by a CAN node.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 16-3. CAN Bit Construction
CAN Frame
(producer)
Transmission Point
(producer)
Nominal CAN Bit Time
Time Quantum
(producer)
Segments
(producer)
SYNC_SEG
PROP_SEG
PHASE_SEG_1
PHASE_SEG_2
propagation
delay
Segments
(consumer)
SYNC_SEG
PROP_SEG
PHASE_SEG_1
PHASE_SEG_2
Sample Point
16.2.3.2
Synchronization Segment
The first segment is used to synchronize the various bus nodes.
On transmission, at the start of this segment, the current bit level is output. If there is a bit state
change between the previous bit and the current bit, then the bus state change is expected to
occur within this segment by the receiving nodes.
16.2.3.3
Propagation Time Segment
This segment is used to compensate for signal delays across the network.
This is necessary to compensate for signal propagation delays on the bus line and through the
transceivers of the bus nodes.
16.2.3.4
Phase Segment 1
Phase Segment 1 is used to compensate for edge phase errors.
This segment may be lengthened during re-synchronization.
16.2.3.5
Sample Point
The sample point is the point of time at which the bus level is read and interpreted as the value
of the respective bit. Its location is at the end of Phase Segment 1 (between the two Phase
Segments).
16.2.3.6
Phase Segment 2
This segment is also used to compensate for edge phase errors.
This segment may be shortened during re-synchronization, but the length has to be at least as
long as the Information Processing Time (IPT) and may not be more than the length of Phase
Segment 1.
171
7647F–AVR–04/09
16.2.3.7
Information Processing Time
It is the time required for the logic to determine the bit level of a sampled bit.
The IPT begins at the sample point, is measured in TQ and is fixed at 2TQ for the Atmel CAN.
Since Phase Segment 2 also begins at the sample point and is the last segment in the bit time,
PS2 minimum shall not be less than the IPT.
16.2.3.8
Bit Lengthening
As a result of resynchronization, Phase Segment 1 may be lengthened or Phase Segment 2
may be shortened to compensate for oscillator tolerances. If, for example, the transmitter oscillator is slower than the receiver oscillator, the next falling edge used for resynchronization may be
delayed. So Phase Segment 1 is lengthened in order to adjust the sample point and the end of
the bit time.
16.2.3.9
Bit Shortening
If, on the other hand, the transmitter oscillator is faster than the receiver one, the next falling
edge used for resynchronization may be too early. So Phase Segment 2 in bit N is shortened in
order to adjust the sample point for bit N+1 and the end of the bit time
16.2.3.10
Synchronization Jump Width
The limit to the amount of lengthening or shortening of the Phase Segments is set by the Resynchronization Jump Width.
This segment may not be longer than Phase Segment 2.
16.2.3.11
Programming the Sample Point
Programming of the sample point allows "tuning" of the characteristics to suit the bus.
Early sampling allows more Time Quanta in the Phase Segment 2 so the Synchronization Jump
Width can be programmed to its maximum. This maximum capacity to shorten or lengthen the
bit time decreases the sensitivity to node oscillator tolerances, so that lower cost oscillators such
as ceramic resonators may be used.
Late sampling allows more Time Quanta in the Propagation Time Segment which allows a
poorer bus topology and maximum bus length.
16.2.3.12
Synchronization
Hard synchronization occurs on the recessive-to-dominant transition of the start bit. The bit time
is restarted from that edge.
Re-synchronization occurs when a recessive-to-dominant edge doesn't occur within the Synchronization Segment in a message.
16.2.4
Arbitration
The CAN protocol handles bus accesses according to the concept called “Carrier Sense Multiple
Access with Arbitration on Message Priority”.
During transmission, arbitration on the CAN bus can be lost to a competing device with a higher
priority CAN Identifier. This arbitration concept avoids collisions of messages whose transmission was started by more than one node simultaneously and makes sure the most important
message is sent first without time loss.
172
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The bus access conflict is resolved during the arbitration field mostly over the identifier value. If a
data frame and a remote frame with the same identifier are initiated at the same time, the data
frame prevails over the remote frame (c.f. RTR bit).
Figure 16-4. Bus Arbitration
Arbitration lost
node A
TXCAN
Node A loses the bus
Node B wins the bus
node B
TXCAN
CAN bus
SOF ID10 ID9 ID8 ID7 ID6 ID5 ID4 ID3 ID2 ID1 ID0 RTR IDE
16.2.5
---------
Errors
The CAN protocol signals any errors immediately as they occur. Three error detection mechanisms are implemented at the message level and two at the bit level:
16.2.5.1
Error at Message Level
• Cyclic Redundancy Check (CRC)
The CRC safeguards the information in the frame by adding redundant check bits at the
transmission end. At the receiver these bits are re-computed and tested against the received
bits. If they do not agree there has been a CRC error.
• Frame Check
This mechanism verifies the structure of the transmitted frame by checking the bit fields
against the fixed format and the frame size. Errors detected by frame checks are designated
"format errors".
• ACK Errors
As already mentioned frames received are acknowledged by all receivers through positive
acknowledgement. If no acknowledgement is received by the transmitter of the message an
ACK error is indicated.
16.2.5.2
Error at Bit Level
• Monitoring
The ability of the transmitter to detect errors is based on the monitoring of bus signals. Each
node which transmits also observes the bus level and thus detects differences between the
bit sent and the bit received. This permits reliable detection of global errors and errors local to
the transmitter.
• Bit Stuffing
The coding of the individual bits is tested at bit level. The bit representation used by CAN is
"Non Return to Zero (NRZ)" coding, which guarantees maximum efficiency in bit coding. The
synchronization edges are generated by means of bit stuffing.
173
7647F–AVR–04/09
16.2.5.3
16.3
Error Signalling
If one or more errors are discovered by at least one node using the above mechanisms, the current transmission is aborted by sending an "error flag". This prevents other nodes accepting the
message and thus ensures the consistency of data throughout the network. After transmission
of an erroneous message that has been aborted, the sender automatically re-attempts
transmission.
CAN Controller
The CAN controller implemented into ATmega16/32/64/M1/C1 offers V2.0B Active.
This full-CAN controller provides the whole hardware for convenient acceptance filtering and
message management. For each message to be transmitted or received this module contains
one so called message object in which all information regarding the message (e.g. identifier,
data bytes etc.) are stored.
During the initialization of the peripheral, the application defines which messages are to be sent
and which are to be received. Only if the CAN controller receives a message whose identifier
matches with one of the identifiers of the programmed (receive-) message objects the message
is stored and the application is informed by interrupt. Another advantage is that incoming remote
frames can be answered automatically by the full-CAN controller with the corresponding data
frame. In this way, the CPU load is strongly reduced compared to a basic-CAN solution.
Using full-CAN controller, high baudrates and high bus loads with many messages can be
handled.
174
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 16-5. CAN Controller Structure
Buffer MOb i
MOb i
Size=120 Bytes
Low priority
Control
Status
IDtag+IDmask
Time Stamp
MOb
Scanning
Control
Status
IDtag+IDmask
Time Stamp
Buffer MOb2
Gen. Control
Gen. Status
Enable MOb
Interrupt
MOb2
Bit Timing
Line Error
CAN Timer
Control
Status
IDtag+IDmask
Time Stamp
Buffer MOb1
LCC
MAC
PLS
Internal
TxCAN
Internal
RxCAN
CAN Channel
MOb1
Control
Status
IDtag+IDmask
Time Stamp
Buffer MOb0
MOb0
CAN Data Buffers
Message Objets
High priority
Ma i l b o x
16.4
16.4.1
CAN Channel
Configuration
The CAN channel can be in:
• Enabled mode
In this mode:
– the CAN channel (internal TxCAN & RxCAN) is enabled,
– the input clock is enabled.
• Standby mode
In standby mode:
– the transmitter constantly provides a recessive level (on internal TxCAN) and the
receiver is disabled,
– input clock is enabled,
– the registers and pages remain accessible.
• Listening mode
This mode is transparent for the CAN channel:
175
7647F–AVR–04/09
– enables a hardware loop back, internal TxCAN on internal RxCAN
– provides a recessive level on TXCAN output pin
– does not disable RXCAN input pin
– freezes TEC and REC error counters
Figure 16-6. Listening Mode
internal
TxCAN
PD5
TXCAN
PD6
RXCAN
LISTEN
16.4.2
internal
1
RxCAN
0
Bit Timing
FSM’s (Finite State Machine) of the CAN channel need to be synchronous to the time quantum.
So, the input clock for bit timing is the clock used into CAN channel FSM’s.
Field and segment abbreviations:
• BRP: Baud Rate Prescaler.
• TQ: Time Quantum (output of Baud Rate Prescaler).
• SYNS: SYNchronization Segment is 1 TQ long.
• PRS: PRopagation time Segment is programmable to be 1, 2, ..., 8 TQ long.
• PHS1: PHase Segment 1 is programmable to be 1, 2, ..., 8 TQ long.
• PHS2: PHase Segment 2 is programmable to be ≤PHS1 and ≥ INFORMATION
PROCESSING TIME.
• INFORMATION PROCESSING TIME is 2 TQ.
• SJW: (Re) Synchronization Jump Width is programmable between 1 and min(4, PHS1).
The total number of TQ in a bit time has to be programmed at least from 8 to 25.
Figure 16-7. Sample and Transmission Point
Bit Timing
PRS (3-bit length)
PHS1 (3-bit length)
CLK
IO
Prescaler BRP
Fcan (Tscl)
Time Quantum
PHS2 (3-bit length)
Sample
Point
Transmission
Point
SJW (2-bit length)
176
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 16-8. General Structure of a Bit Period
1
/CLK IO
CLK
IO
Bit Rate Prescaler
Tscl (TQ)
F
CAN
one nominal bit
Data
Tsyns(5)
Notes: 1.
2.
3.
4.
5.
Phase error < 0
Phase error > 0
Phase error > 0
Phase error < 0
Synchronization Segment: SYNS
Tsyns=1xTscl (fixed)
Tprs
Tphs1 (1)
or
Tphs1+Tsjw (3)
Tphs2 (2)
or
Tphs2+Tsjw (4)
Tbit
Sample
Point
16.4.3
Transmission
Point
Baud Rate
With no baud rate prescaler (BRP[5..0]=0) the sampling point comes one time quantum too
early. This leads to a fail according the ISO16845 Test plan. It is necessary to lengthen the
Phase Segment 1 by one time quantum and to shorten the Phase Segment 2 by one time quantum to compensate.
The baud rate selection is made by Tbit calculation:
Tbit(1) = Tsyns + Tprs + Tphs1 + Tphs2
1. Tsyns = 1 x Tscl = (BRP[5..0]+ 1)/clkIO (= 1TQ)
2. Tprs = (1 to 8) x Tscl = (PRS[2..0]+ 1) x Tscl
3. Tphs1 = (1 to 8) x Tscl = (PHS1[2..0]+ 1) x Tscl
4. Tphs2 = (1 to 8) x Tscl = (PHS2[2..0](2)+ 1) x Tscl
5. Tsjw = (1 to 4) x Tscl = (SJW[1..0]+ 1) x Tscl
Notes:
1. The total number of Tscl (Time Quanta) in a bit time must be from 8 to 25.
2. PHS2[2..0] 2 is programmable to be ≤PHS1[2..0] and ≥ 1.
16.4.4
Fault Confinement
(c.f. Section 16.7 “Error Management” on page 183).
16.4.5
Overload Frame
An overload frame is sent by setting an overload request (OVRQ). After the next reception, the
CAN channel sends an overload frame in accordance with the CAN specification. A status or
flag is set (OVRF) as long as the overload frame is sent.
177
7647F–AVR–04/09
Figure 16-9. Overload Frame
Setting OVRQ bit
Instructions
Resetting OVRQ bit
OVRQ bit
OVFG bit
RXCDAN
Ident "A"
Cmd
Message Data "A"
CRC
A
Interframe
TXCDAN
16.5
Overload Frame
Ident "B"
Overload Frame
Message Objects
The MOb is a CAN frame descriptor. It contains all information to handle a CAN frame. This
means that a MOb has been outlined to allow to describe a CAN message like an object. The set
of MObs is the front end part of the “mailbox” where the messages to send and/or to receive are
pre-defined as well as possible to decrease the work load of the software.
The MObs are independent but priority is given to the lower one in case of multi matching. The
operating modes are:
– Disabled mode
– Transmit mode
– Receive mode
– Automatic reply
– Frame buffer receive mode
16.5.1
Number of MObs
This device has 6 MObs, they are numbered from 0 up to 5 (i=5).
16.5.2
Operating Modes
There is no default mode after RESET.
Every MOb has its own fields to control the operating mode. Before enabling the CAN peripheral, each MOb must be configured (ex: disabled mode - CONMOB=00).
Table 16-1.
MOb Configuration
MOb Configuration
0
0
0
1
1
Reply Valid
RTR Tag
x
x
Disabled
x
0
Tx Data Frame
x
1
Tx Remote Frame
x
0
Rx Data Frame
0
0
Operating Mode
Rx Remote Frame
1
1
1
16.5.2.1
1
x
Rx Remote Frame then, Tx Data Frame (reply)
x
Frame Buffer Receive Mode
Disabled
In this mode, the MOb is “free”.
178
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
16.5.2.2
Tx Data & Remote Frame
1. Several fields must be initialized before sending:
– Identifier tag (IDT)
– Identifier extension (IDE)
– Remote transmission request (RTRTAG)
– Data length code (DLC)
– Reserved bit(s) tag (RBnTAG)
– Data bytes of message (MSG)
2. The MOb is ready to send a data or a remote frame when the MOb configuration is set
(CONMOB).
3. Then, the CAN channel scans all the MObs in Tx configuration, finds the MOb having
the highest priority and tries to send it.
4. When the transmission is completed the TXOK flag is set (interrupt).
5. All the parameters and data are available in the MOb until a new initialization.
16.5.2.3
Rx Data & Remote Frame
1. Several fields must be initialized before receiving:
– Identifier tag (IDT)
– Identifier mask (IDMSK)
– Identifier extension (IDE)
– Identifier extension mask (IDEMSK)
– Remote transmission request (RTRTAG)
– Remote transmission request mask (RTRMSK)
– Data length code (DLC)
– Reserved bit(s) tag (RBnTAG)
2. The MOb is ready to receive a data or a remote frame when the MOb configuration is
set (CONMOB).
3. When a frame identifier is received on CAN network, the CAN channel scans all the
MObs in receive mode, tries to find the MOb having the highest priority which is
matching.
4. On a hit, the IDT, the IDE and the DLC of the matched MOb are updated from the
incoming (frame) values.
5. Once the reception is completed, the data bytes of the received message are stored
(not for remote frame) in the data buffer of the matched MOb and the RXOK flag is set
(interrupt).
6. All the parameters and data are available in the MOb until a new initialization.
179
7647F–AVR–04/09
16.5.2.4
Automatic Reply
A reply (data frame) to a remote frame can be automatically sent after reception of the expected
remote frame.
1. Several fields must be initialized before receiving the remote frame:
– Reply valid (RPLV) in a identical flow to the one described in Section 16.5.2.3 “Rx
Data & Remote Frame” on page 179.
2. When a remote frame matches, automatically the RTRTAG and the reply valid bit
(RPLV) are reset. No flag (or interrupt) is set at this time. Since the CAN data buffer has
not been used by the incoming remote frame, the MOb is then ready to be in transmit
mode without any more setting. The IDT, the IDE, the other tags and the DLC of the
received remote frame are used for the reply.
3. When the transmission of the reply is completed the TXOK flag is set (interrupt).
4. All the parameters and data are available in the MOb until a new initialization.
16.5.2.5
Frame Buffer Receive Mode
This mode is useful to receive multi frames. The priority between MObs offers a management for
these incoming frames. One set MObs (including non-consecutive MObs) is created when the
MObs are set in this mode. Due to the mode setting, only one set is possible. A frame buffer
completed flag (or interrupt) - BXOK - will rise only when all the MObs of the set will have
received their dedicated CAN frame.
1.
MObs in frame buffer receive mode need to be initialized as MObs in standard receive mode.
2. The MObs are ready to receive data (or a remote) frames when their respective configurations are set (CONMOB).
3. When a frame identifier is received on CAN network, the CAN channel scans all the
MObs in receive mode, tries to find the MOb having the highest priority which is
matching.
4. On a hit, the IDT, the IDE and the DLC of the matched MOb are updated from the
incoming (frame) values.
5. Once the reception is completed, the data bytes of the received message are stored (not
for remote frame) in the data buffer of the matched MOb and the RXOK flag is set
(interrupt).
6. When the reception in the last MOb of the set is completed, the frame buffer completed
BXOK flag is set (interrupt). BXOK flag can be cleared only if all CONMOB fields of the
set have been re-written before.
7. All the parameters and data are available in the MObs until a new initialization.
16.5.3
180
Acceptance Filter
Upon a reception hit (i.e., a good comparison between the ID + RTR + RBn + IDE received and an
IDT+ RTRTAG + RBnTAG + IDE specified while taking the comparison mask into account) the IDT
+ RTRTAG + RBnTAG + IDE received are updated in the MOb (written over the registers).
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 16-10. Acceptance Filter Block Diagram
internal RxDcan
Rx Shift Register (internal)
ID & RB
RTR
IDE
14(33)
RB excluded
=
Hit MOb[i]
13(31)
Write
Enable
14(33)
ID & RB
1
13(31) - RB excluded
RTRTAG
IDE
13(31)
CANIDT Registers & CANCDMOB (MOb[i])
Note:
RTRMSK
IDMSK
IDEMSK
CANIDM Registers (MOb[i])
Examples:
Full filtering: to accept only ID = 0x317 in part A.
- ID MSK = 111 1111 1111 b
- ID TAG = 011 0001 0111 b
Partiel filtering: to accept ID from 0x310 up to 0x317 in part A.
- ID MSK = 111 1111 1000 b
- ID TAG = 011 0001 0xxx b
No filtering: to accept all ID’s from 0x000 up to 0x7FF in part A.
- ID MSK = 000 0000 0000 b
- ID TAG = xxx xxxx xxxx b
16.5.4
MOb Page
Every MOb is mapped into a page to save place. The page number is the MOb number. This
page number is set in CANPAGE register. The other numbers are reserved for factory tests.
CANHPMOB register gives the MOb having the highest priority in CANSIT registers. It is formatted to provide a direct entry for CANPAGE register. Because CANHPMOB codes CANSIT
registers, it will be only updated if the corresponding enable bits (ENRX, ENTX, ENERR) are
enabled (c.f. Figure 16-14).
16.5.5
CAN Data Buffers
To preserve register allocation, the CAN data buffer is seen such as a FIFO (with address
pointer accessible) into a MOb selection.This also allows to reduce the risks of un-controlled
accesses.
There is one FIFO per MOb. This FIFO is accessed into a MOb page thanks to the CAN message register.
The data index (INDX) is the address pointer to the required data byte. The data byte can be
read or write. The data index is automatically incremented after every access if the AINC* bit is
reset. A roll-over is implemented, after data index=7 it is data index=0.
The first byte of a CAN frame is stored at the data index=0, the second one at the data index=1,
...
181
7647F–AVR–04/09
16.6
CAN Timer
A programmable 16-bit timer is used for message stamping and time trigger communication
(TTC).
Figure 16-11. CAN Timer Block Diagram
clk
IO
8
ENFG
CANTCON
clk CANTIM
OVRTIM
overrun
TTC
CANTIM
TXOK[i]
"EOF "
"SOF "
RXOK[i]
CANSTM[i]
16.6.1
SYNCTTC
CANTTC
Prescaler
An 8-bit prescaler is initialized by CANTCON register. It receives the clkIO frequency divided by
8. It provides clkCANTIM frequency to the CAN Timer if the CAN controller is enabled.
TclkCANTIM = TclkIO x 8 x (CANTCON [7:0] + 1)
16.6.2
16-bit Timer
This timer starts counting from 0x0000 when the CAN controller is enabled (ENFG bit). When
the timer rolls over from 0xFFFF to 0x0000, an interrupt is generated (OVRTIM).
16.6.3
Time Triggering
Two synchronization modes are implemented for TTC (TTC bit):
– synchronization on Start of Frame (SYNCTTC=0),
– synchronization on End of Frame (SYNCTTC=1).
In TTC mode, a frame is sent once, even if an error occurs.
16.6.4
182
Stamping Message
The capture of the timer value is done in the MOb which receives or sends the frame. All managed MOb are stamped, the stamping of a received (sent) frame occurs on RxOk (TXOK).
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
16.7
16.7.1
Error Management
Fault Confinement
The CAN channel may be in one of the three following states:
• Error active (default):
The CAN channel takes part in bus communication and can send an active error frame when
the CAN macro detects an error.
• Error passive:
The CAN channel cannot send an active error frame. It takes part in bus communication, but
when an error is detected, a passive error frame is sent. Also, after a transmission, an error
passive unit will wait before initiating further transmission.
• Bus off:
The CAN channel is not allowed to have any influence on the bus.
For fault confinement, a transmit error counter (TEC) and a receive error counter (REC) are
implemented. BOFF and ERRP bits give the information of the state of the CAN channel. Setting
BOFF to one may generate an interrupt.
Figure 16-12. Line Error Mode
Reset
ERRP = 0
BOFF = 0
Error
Active
TEC > 127 or
REC > 127
128 occurrences
of 11 consecutive
recessive bit
TEC < 127 and
REC < 127
ERRP = 1
BOFF = 0
ERRP = 0
BOFF = 1
Bus
Off
Error
Passive
TEC > 255
interrupt - BOFFIT
Note:
16.7.2
More than one REC/TEC change may apply during a given message transfer.
Error Types
• BERR: Bit error. The bit value which is monitored is different from the bit value sent.
Note:
Exceptions:
- Recessive bit sent monitored as dominant bit during the arbitration field and the acknowledge slot.
- Detecting a dominant bit during the sending of an error frame.
• SERR: Stuff error. Detection of more than five consecutive bit with the same polarity.
• CERR: CRC error (Rx only). The receiver performs a CRC check on every destuffed received
message from the start of frame up to the data field. If this checking does not match with the
destuffed CRC field, an CRC error is set.
• FERR: Form error. The form error results from one (or more) violations of the fixed form of
the following bit fields:
– CRC delimiter
– acknowledgement delimiter
183
7647F–AVR–04/09
– end-of-frame
– error delimiter
– overload delimiter
• AERR: Acknowledgment error (Tx only). No detection of the dominant bit in the acknowledge
slot.
Figure 16-13. Error Detection Procedures in a Data Frame
Arbitration
Bit error
Stuff error
Form error
Tx
ACK error
SOF
Rx
Identifier
RTR
Control
Message Data
CRC
CRC ACK ACK
del.
del.
EOF
inter.
Bit error
Stuff error
Form error
CRC error
16.7.3
Error Setting
The CAN channel can detect some errors on the CAN network.
• In transmission:
The error is set at MOb level.
• In reception:
- The identified has matched:
The error is set at MOb level.
- The identified has not or not yet matched:
The error is set at general level.
After detecting an error, the CAN channel sends an error frame on network. If the CAN channel
detects an error frame on network, it sends its own error frame.
16.8
16.8.1
Interrupts
Interrupt organization
The different interrupts are:
• Interrupt on receive completed OK,
• Interrupt on transmit completed OK,
• Interrupt on error (bit error, stuff error, CRC error, form error, acknowledge error),
• Interrupt on frame buffer full,
• Interrupt on “Bus Off” setting,
• Interrupt on overrun of CAN timer.
The general interrupt enable is provided by ENIT bit and the specific interrupt enable for CAN
timer overrun is provided by ENORVT bit.
184
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 16-14. CAN Controller Interrupt Structure
CANGIE.4 CANGIE.5 CANGIE.3
ENTX
CANSTMOB.6
TXOK[i]
CANSTMOB.5
RXOK[i]
CANSTMOB.4
BERR[i]
CANSTMOB.3
SERR[i]
CANSTMOB.2
CERR[i]
CANSTMOB.1
FERR[i]
CANSTMOB.0
AERR[i]
CANGIT.4
BXOK
CANGIT.3
SERG
CANGIT.2
CERG
CANGIT.1
FERG
CANGIT.0
AERG
CANGIT.6
BOFFI
CANGIT.5
OVRTIM
ENRX
ENERR
CANSIT 1/2
SIT[i]
CANIE 1/2
IEMOB[i]
0
CANGIT.7
i
CANIT
CANGIE.2 CANGIE.1 CANGIE.6
CANGIE.7
ENERG
ENIT
ENBX
ENBOFF
CAN IT
CANGIE.0
16.8.2
ENOVRT
OVR IT
Interrupt Behavior
When an interrupt occurs, an interrupt flag bit is set in the corresponding MOb-CANSTMOB register or in the general CANGIT register. If in the CANIE register, ENRX / ENTX / ENERR bit are
set, then the corresponding MOb bit is set in the CANSITn register.
To acknowledge a MOb interrupt, the corresponding bits of CANSTMOB register (RXOK,
TXOK,...) must be cleared by the software application. This operation needs a read-modify-write
software routine.
To acknowledge a general interrupt, the corresponding bits of CANGIT register (BXOK, BOFFIT,...) must be cleared by the software application. This operation is made writing a logical one
in these interrupt flags (writing a logical zero doesn’t change the interrupt flag value).
OVRTIM interrupt flag is reset as the other interrupt sources of CANGIT register and is also
reset entering in its dedicated interrupt handler.
When the CAN node is in transmission and detects a Form Error in its frame, a bit Error will also
be raised. Consequently, two consecutive interrupts can occur, both due to the same error.
When a MOb error occurs and is set in its own CANSTMOB register, no general error is set in
CANGIT register.
185
7647F–AVR–04/09
16.9
CAN Register Description
Figure 16-15. Registers Organization
AVR Registers
Registers in Pages
General Control
General Status
General Interrupt
Bit Timing 1
Bit Timing 2
Bit Timing 3
Enable MOb 2
Enable MOb 1
Enable Interrupt
Enable Interrupt MOb 2
Enable Interrupt MOb 1
Status Interrupt MOb 2
Status Interrupt MOb 1
CAN Timer Control
CAN Timer Low
CAN Timer High
CAN TTC Low
CAN TTC High
TEC Counter
REC Counter
Hightest Priority MOb
Page MOb
MOb Number
Data Index
sage
es
1) M
(i+
cts
Obje
MOb(i) - MOb Status
MOb(i) - MOb Ctrl & DLC
MOb(i) - ID Tag 4
MOb(i) - ID Tag 3
Page MOb
MOb(i) - ID Tag 2
MOb(i) - ID Tag 1
MOb Status
MOb0 - MOb Status
MOb Control & DLC
MOb0 - MOb Ctrl & DLC
ID Tag 4
MOb0 - ID Tag 4
ID Tag 3
ID Tag 2
MOb0 - ID Tag 3
MOb0 - ID Tag 2
ID Tag 1
MOb0 - ID Tag 1
ID Mask 4
ID Mask 3
ID Mask 2
ID Mask 1
MOb0 - ID Mask 4
MOb0 - ID Mask 3
MOb(i) - Time Stamp High
MOb0 - ID Mask 2
MOb0 - ID Mask 1
MOb(i) - Mess. Data - byte 0
Time Stamp Low
MOb0 - Time Stamp Low
Time Stamp High
MOb0 - Time Stamp High
Message Data
MOb0 - Mess. Data - byte 0
MOb(i) - ID Mask 4
MOb(i) - ID Mask 3
MOb(i) - ID Mask 2
MOb(i) - ID Mask 1
MOb(i) - Time Stamp Low
8 bytes
186
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
16.10 General CAN Registers
16.10.1
CAN General Control Register - CANGCON
Bit
7
6
5
4
3
2
1
0
ABRQ
OVRQ
TTC
SYNTTC
LISTEN
TEST
ENA/STB
SWRES
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
CANGCON
• Bit 7 – ABRQ: Abort Request
This is not an auto resettable bit.
– 0 - no request.
– 1 - abort request: a reset of CANEN1 and CANEN2 registers is done. The pending
communications are immediately disabled and the on-going one will be normally
terminated, setting the appropriate status flags.
Note that CANCDMOB register remain unchanged.
• Bit 6 – OVRQ: Overload Frame Request
This is not an auto resettable bit.
– 0 - no request.
– 1 - overload frame request: send an overload frame after the next received frame.
The overload frame can be traced observing OVFG in CANGSTA register (c.f. Figure 16-9 on
page 178).
• Bit 5 – TTC: Time Trigger Communication
– 0 - no TTC.
– 1 - TTC mode.
• Bit 4 – SYNTTC: Synchronization of TTC
This bit is only used in TTC mode.
– 0 - the TTC timer is caught on SOF.
– 1 - the TTC timer is caught on the last bit of the EOF.
• Bit 3 – LISTEN: Listening Mode
– 0 - no listening mode.
– 1 - listening mode.
• Bit 2 – TEST: Test Mode
– 0 - no test mode
– 1 - test mode: intend for factory testing and not for customer use.
Note:
CAN may malfunction if this bit is set.
• Bit 1 – ENA/STB: Enable / Standby Mode
Because this bit is a command and is not immediately effective, the ENFG bit in CANGSTA register gives the true state of the chosen mode.
187
7647F–AVR–04/09
– 0 - standby mode: The on-going transmission (if exists) is normally terminated and the
CAN channel is frozen (the CONMOB bits of every MOb do not change). The transmitter
constantly provides a recessive level. In this mode, the receiver is not enabled but all the
registers and mailbox remain accessible from CPU. In this mode, the receiver is not
enabled but all the registers and mailbox remain accessible from CPU.
Note:A standby mode applied during a reception may corrupt the on-going reception or set the
controller in a wrong state. The controller will restart correctly from this state if a software
reset (SWRES) is applied. If no reset is considered, a possible solution is to wait for a
lake of a receiver busy (RXBSY) before to enter in stand-by mode. The best solution is
first to apply an abort request command (ABRQ) and then wait for the lake of the receiver
busy (RXBSY) before to enter in stand-by mode. In any cases, this standby mode behavior has no effect on the CAN bus integrity.
– 1 - enable mode: The CAN channel enters in enable mode once 11 recessive bits
has been read.
• Bit 0 – SWRES: Software Reset Request
This auto resettable bit only resets the CAN controller.
– 0 - no reset
– 1 - reset: this reset is “ORed” with the hardware reset.
16.10.2
CAN General Status Register - CANGSTA
Bit
7
6
5
4
3
2
1
0
-
OVRG
-
TXBSY
RXBSY
ENFG
BOFF
ERRP
Read/Write
-
R
-
R
R
R
R
R
Initial Value
-
0
-
0
0
0
0
0
CANGSTA
• Bit 7 – Reserved Bit
This bit is reserved for future use.
• Bit 6 – OVRG: Overload Frame Flag
This flag does not generate an interrupt.
– 0 - no overload frame.
– 1 - overload frame: set by hardware as long as the produced overload frame is sent.
• Bit 5 – Reserved Bit
This bit is reserved for future use.
• Bit 4 – TXBSY: Transmitter Busy
This flag does not generate an interrupt.
– 0 - transmitter not busy.
– 1 - transmitter busy: set by hardware as long as a frame (data, remote, overload or
error frame) or an ACK field is sent. Also set when an inter frame space is sent.
• Bit 3 – RXBSY: Receiver Busy
This flag does not generate an interrupt.
– 0 - receiver not busy
– 1 - receiver busy: set by hardware as long as a frame is received or monitored.
188
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 2 – ENFG: Enable Flag
This flag does not generate an interrupt.
– 0 - CAN controller disable: because an enable/standby command is not immediately
effective, this status gives the true state of the chosen mode.
– 1 - CAN controller enable.
• Bit 1 – BOFF: Bus Off Mode
BOFF gives the information of the state of the CAN channel. Only entering in bus off mode generates the BOFFIT interrupt.
– 0 - no bus off mode.
– 1 - bus off mode.
• Bit 0 – ERRP: Error Passive Mode
ERRP gives the information of the state of the CAN channel. This flag does not generate an
interrupt.
– 0 - no error passive mode.
– 1 - error passive mode.
16.10.3
CAN General Interrupt Register - CANGIT
Bit
7
6
5
4
3
2
1
0
CANIT
BOFFIT
OVRTIM
BXOK
SERG
CERG
FERG
AERG
Read/Write
R
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
CANGIT
• Bit 7 – CANIT: General Interrupt Flag
This is a read only bit.
– 0 - no interrupt.
– 1 - CAN interrupt: image of all the CAN controller interrupts except for OVRTIM
interrupt. This bit can be used for polling method.
• Bit 6 – BOFFIT: Bus Off Interrupt Flag
Writing a logical one resets this interrupt flag. BOFFIT flag is only set when the CAN enters in
bus off mode (coming from error passive mode).
– 0 - no interrupt.
– 1 - bus off interrupt when the CAN enters in bus off mode.
• Bit 5 – OVRTIM: Overrun CAN Timer
Writing a logical one resets this interrupt flag. Entering in CAN timer overrun interrupt handler
also reset this interrupt flag
– 0 - no interrupt.
– 1 - CAN timer overrun interrupt: set when the CAN timer switches from 0xFFFF to 0.
189
7647F–AVR–04/09
• Bit 4 – BXOK: Frame Buffer Receive Interrupt
Writing a logical one resets this interrupt flag. BXOK flag can be cleared only if all CONMOB
fields of the MOb’s of the buffer have been re-written before.
– 0 - no interrupt.
– 1 - burst receive interrupt: set when the frame buffer receive is completed.
• Bit 3 – SERG: Stuff Error General
Writing a logical one resets this interrupt flag.
– 0 - no interrupt.
– 1 - stuff error interrupt: detection of more than 5 consecutive bits with the same
polarity.
• Bit 2 – CERG: CRC Error General
Writing a logical one resets this interrupt flag.
– 0 - no interrupt.
– 1 - CRC error interrupt: the CRC check on destuffed message does not fit with the
CRC field.
• Bit 1 – FERG: Form Error General
Writing a logical one resets this interrupt flag.
– 0 - no interrupt.
– 1 - form error interrupt: one or more violations of the fixed form in the CRC delimiter,
acknowledgment delimiter or EOF.
• Bit 0 – AERG: Acknowledgment Error General
Writing a logical one resets this interrupt flag.
– 0 - no interrupt.
– 1 - acknowledgment error interrupt: no detection of the dominant bit in acknowledge
slot.
16.10.4
CAN General Interrupt Enable Register - CANGIE
Bit
7
6
5
4
3
2
1
0
ENIT
ENBOFF
ENRX
ENTX
ENERR
ENBX
ENERG
ENOVRT
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
CANGIE
• Bit 7 – ENIT: Enable all Interrupts (Except for CAN Timer Overrun Interrupt)
– 0 - interrupt disabled.
– 1- CANIT interrupt enabled.
• Bit 6 – ENBOFF: Enable Bus Off Interrupt
– 0 - interrupt disabled.
– 1- bus off interrupt enabled.
190
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 5 – ENRX: Enable Receive Interrupt
– 0 - interrupt disabled.
– 1- receive interrupt enabled.
• Bit 4 – ENTX: Enable Transmit Interrupt
– 0 - interrupt disabled.
– 1- transmit interrupt enabled.
• Bit 3 – ENERR: Enable MOb Errors Interrupt
– 0 - interrupt disabled.
– 1- MOb errors interrupt enabled.
• Bit 2 – ENBX: Enable Frame Buffer Interrupt
– 0 - interrupt disabled.
– 1- frame buffer interrupt enabled.
• Bit 1 – ENERG: Enable General Errors Interrupt
– 0 - interrupt disabled.
– 1- general errors interrupt enabled.
• Bit 0 – ENOVRT: Enable CAN Timer Overrun Interrupt
– 0 - interrupt disabled.
– 1- CAN timer interrupt overrun enabled.
16.10.5
CAN Enable MOb Registers - CANEN2 and CANEN1
Bit
7
6
5
4
3
2
1
0
-
-
ENMOB5
ENMOB4
ENMOB3
ENMOB2
ENMOB1
ENMOB0
CANEN2
-
-
-
-
-
-
-
-
CANEN1
Bit
15
14
13
12
11
10
9
8
R
Read/Write
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
• Bits 5:0 - ENMOB5:0: Enable MOb
This bit provides the availability of the MOb.
It is set to one when the MOb is enabled (i.e. CONMOB1:0 of CANCDMOB register).
Once TXOK or RXOK is set to one (TXOK for automatic reply), the corresponding ENMOB is
reset. ENMOB is also set to zero configuring the MOb in disabled mode, applying abortion or
standby mode.
– 0 - message object disabled: MOb available for a new transmission or reception.
– 1 - message object enabled: MOb in use.
• Bit 15:6 – Reserved Bits
These bits are reserved for future use.
191
7647F–AVR–04/09
16.10.6
CAN Enable Interrupt MOb Registers - CANIE2 and CANIE1
Bit
7
6
5
4
3
2
1
0
-
-
IEMOB5
IEMOB4
IEMOB3
IEMOB2
IEMOB1
IEMOB0
CANIE2
-
-
-
-
-
-
-
-
CANIE1
Bit
15
14
13
12
11
10
9
8
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
Read/Write
R
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
• Bits 5:0 - IEMOB5:0: Interrupt Enable by MOb
– 0 - interrupt disabled.
– 1 - MOb interrupt enabled
Note:
Example: CANIE2 = 0000 1100b : enable of interrupts on MOb 2 & 3.
• Bit 15:6 – Reserved Bits
These bits are reserved for future use. For compatibility with future devices, it must be written to
zero when CANIE1 & CANIE2 are written.
16.10.7
CAN Status Interrupt MOb Registers - CANSIT2 and CANSIT1
Bit
7
6
5
4
3
2
1
0
-
-
SIT5
SIT4
SIT3
SIT2
SIT1
SIT0
CANSIT2
-
-
-
-
-
-
-
-
CANSIT1
Bit
15
14
13
12
11
10
9
8
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
• Bits 5:0 - SIT5:0: Status of Interrupt by MOb
– 0 - no interrupt.
– 1- MOb interrupt.
Note:
Example: CANSIT2 = 0010 0001b : MOb 0 & 5 interrupts.
• Bit 15:6 – Reserved Bits
These bits are reserved for future use.
16.10.8
CAN Bit Timing Register 1 - CANBT1
Bit
7
6
5
4
3
2
1
0
-
BRP5
BRP4
BRP3
BRP2
BRP1
BRP0
-
Read/Write
-
R/W
R/W
R/W
R/W
R/W
R/W
-
Initial Value
-
0
0
0
0
0
0
-
CANBT1
• Bit 7– Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANBT1 is written.
192
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 6:1 – BRP5:0: Baud Rate Prescaler
The period of the CAN controller system clock Tscl is programmable and determines the individual bit timing.
BRP[5:0] + 1 Tscl = -------------------------------------clk IO frequency
If ‘BRP[5..0]=0’, see Section 16.4.3 “Baud Rate” on page 177 and Section • “Bit 0 – SMP: Sample Point(s)” on page 194.
• Bit 0 – Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANBT1 is written.
16.10.9
CAN Bit Timing Register 2 - CANBT2
Bit
7
6
5
4
3
2
1
-
SJW1
SJW0
-
PRS2
PRS1
PRS0
0
-
Read/Write
-
R/W
R/W
-
R/W
R/W
R/W
-
Initial Value
-
0
0
-
0
0
0
-
CANBT2
• Bit 7– Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANBT2 is written.
• Bit 6:5 – SJW1:0: Re-Synchronization Jump Width
To compensate for phase shifts between clock oscillators of different bus controllers, the controller must re-synchronize on any relevant signal edge of the current transmission.
The synchronization jump width defines the maximum number of clock cycles. A bit period may
be shortened or lengthened by a re-synchronization.
Tsjw = Tscl × ( SJW[1:0] + 1 )
• Bit 4 – Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANBT2 is written.
• Bit 3:1 – PRS2:0: Propagation Time Segment
This part of the bit time is used to compensate for the physical delay times within the network. It
is twice the sum of the signal propagation time on the bus line, the input comparator delay and
the output driver delay.
Tprs = Tscl × ( PRS[2:0] + 1 )
• Bit 0 – Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANBT2 is written.
193
7647F–AVR–04/09
16.10.10 CAN Bit Timing Register 3 - CANBT3
Bit
7
6
5
4
3
2
1
0
-
PHS22
PHS21
PHS20
PHS12
PHS11
PHS10
SMP
Read/Write
-
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
0
0
0
0
0
0
0
CANBT3
• Bit 7– Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANBT3 is written.
• Bit 6:4 – PHS22:0: Phase Segment 2
This phase is used to compensate for phase edge errors. This segment may be shortened by
the re-synchronization jump width. PHS2[2..0] shall be ≥1 and ≤PHS1[2..0] (c.f. Section 16.2.3
“CAN Bit Timing” on page 170 and Section 16.4.3 “Baud Rate” on page 177).
Tphs2 = Tscl x (PHS2 [2:0] + 1)
• Bit 3:1 – PHS12:0: Phase Segment 1
This phase is used to compensate for phase edge errors. This segment may be lengthened by
the re-synchronization jump width.
Tphs1 = Tscl x (PHS1 [2:0] + 1)
• Bit 0 – SMP: Sample Point(s)
This option allows to filter possible noise on TxCAN input pin.
– 0 - the sampling will occur once at the user configured sampling point - SP.
– 1 - with three-point sampling configuration the first sampling will occur two TclkIO
clocks before the user configured sampling point - SP, again at one TclkIO clock
before SP and finally at SP. Then the bit level will be determined by a majority vote of
the three samples.
‘SMP=1’ configuration is not compatible with ‘BRP[5:0]=0’ because TQ = TclkIO.
If BRP = 0, SMP must be cleared.
16.10.11 CAN Timer Control Register - CANTCON
Bit
7
6
5
4
3
2
1
0
TPRSC7
TPRSC6
TPRSC5
TPRSC4
TPRSC3
TPRSC2
TRPSC1
TPRSC0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
CANTCON
• Bit 7:0 – TPRSC7:0: CAN Timer Prescaler
Prescaler for the CAN timer upper counter range 0 to 255. It provides the clock to the CAN timer
if the CAN controller is enabled.
TclkCANTIM = TclkIO x 8 x (CANTCON [7:0] + 1)
194
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
16.10.12 CAN Timer Registers - CANTIML and CANTIMH
Bit
7
6
5
4
3
2
1
0
CANTIM7
CANTIM6
CANTIM5
CANTIM4
CANTIM3
CANTIM2
CANTIM1
CANTIM0
CANTIML
CANTIM15
CANTIM14
CANTIM13
CANTIM12
CANTIM11
CANTIM10
CANTIM9
CANTIM8
CANTIMH
Bit
15
14
13
12
11
10
9
8
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
• Bits 15:0 - CANTIM15:0: CAN Timer Count
CAN timer counter range 0 to 65,535.
16.10.13 CAN TTC Timer Registers - CANTTCL and CANTTCH
Bit
7
6
5
4
3
2
1
0
TIMTTC7
TIMTTC6
TIMTTC5
TIMTTC4
TIMTTC3
TIMTTC2
TIMTTC1
TIMTTC0
CANTTCL
TIMTTC15
TIMTTC14
TIMTTC13
TIMTTC12
TIMTTC11
TIMTTC10
TIMTTC9
TIMTTC8
CANTTCH
Bit
15
14
13
12
11
10
9
8
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
• Bits 15:0 - TIMTTC15:0: TTC Timer Count
CAN TTC timer counter range 0 to 65,535.
16.10.14 CAN Transmit Error Counter Register - CANTEC
Bit
7
6
5
4
3
2
1
0
TEC7
TEC6
TEC5
TEC4
TEC3
TEC2
TEC1
TEC0
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
CANTEC
• Bit 7:0 – TEC7:0: Transmit Error Count
CAN transmit error counter range 0 to 255.
16.10.15 CAN Receive Error Counter Register - CANREC
Bit
7
6
5
4
3
2
1
0
REC7
REC6
REC5
REC4
REC3
REC2
REC1
REC0
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
CANREC
• Bit 7:0 – REC7:0: Receive Error Count
CAN receive error counter range 0 to 255.
16.10.16 CAN Highest Priority MOb Register - CANHPMOB
Bit
7
6
5
4
3
2
1
0
HPMOB3
HPMOB2
HPMOB1
HPMOB0
CGP3
CGP2
CGP1
CGP0
Read/Write
R
R
R
R
R/W
R/W
R/W
R/W
Initial Value
1
1
1
1
0
0
0
0
CANHPMOB
• Bit 7:4 – HPMOB3:0: Highest Priority MOb Number
MOb having the highest priority in CANSIT registers.
If CANSIT = 0 (no MOb), the return value is 0xF.
Note:
Do not confuse “MOb priority” and “Message ID priority”- See “Message Objects” on page 178.
195
7647F–AVR–04/09
• Bit 3:0 – CGP3:0: CAN General Purpose Bits
These bits can be pre-programmed to match with the wanted configuration of the CANPAGE
register (i.e., AINC and INDX2:0 setting).
16.10.17 CAN Page MOb Register - CANPAGE
Bit
7
6
5
4
3
2
1
0
MOBNB3
MOBNB2
MOBNB1
MOBNB0
AINC
INDX2
INDX1
INDX0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
CANPAGE
• Bit 7:4 – MOBNB3:0: MOb Number
Selection of the MOb number, the available numbers are from 0 to 5.
Note:
MOBNB3 always must be written to zero for compatibility with all AVR CAN devices.
• Bit 3 – AINC: Auto Increment of the FIFO CAN Data Buffer Index (Active Low)
– 0 - auto increment of the index (default value).
– 1- no auto increment of the index.
• Bit 2:0 – INDX2:0: FIFO CAN Data Buffer Index
Byte location of the CAN data byte into the FIFO for the defined MOb.
16.11 MOb Registers
The MOb registers has no initial (default) value after RESET.
16.11.1
CAN MOb Status Register - CANSTMOB
Bit
7
6
5
4
3
2
1
0
DLCW
TXOK
RXOK
BERR
SERR
CERR
FERR
AERR
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
-
-
-
-
CANSTMOB
• Bit 7 – DLCW: Data Length Code Warning
The incoming message does not have the DLC expected. Whatever the frame type, the DLC
field of the CANCDMOB register is updated by the received DLC.
• Bit 6 – TXOK: Transmit OK
This flag can generate an interrupt. It must be cleared using a read-modify-write software routine
on the whole CANSTMOB register.
The communication enabled by transmission is completed. TxOK rises at the end of EOF field.
When the controller is ready to send a frame, if two or more message objects are enabled as
producers, the lower MOb index (0 to 14) is supplied first.
• Bit 5 – RXOK: Receive OK
This flag can generate an interrupt. It must be cleared using a read-modify-write software routine
on the whole CANSTMOB register.
The communication enabled by reception is completed. RxOK rises at the end of the 6th bit of
EOF field. In case of two or more message object reception hits, the lower MOb index (0 to 14)
is updated first.
196
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 4 – BERR: Bit Error (Only in Transmission)
This flag can generate an interrupt. It must be cleared using a read-modify-write software routine
on the whole CANSTMOB register.
The bit value monitored is different from the bit value sent.
Exceptions: the monitored recessive bit sent as a dominant bit during the arbitration field and the
acknowledge slot detecting a dominant bit during the sending of an error frame.
• Bit 3 – SERR: Stuff Error
This flag can generate an interrupt. It must be cleared using a read-modify-write software routine
on the whole CANSTMOB register.
Detection of more than five consecutive bits with the same polarity. This flag can generate an
interrupt.
• Bit 2 – CERR: CRC Error
This flag can generate an interrupt. It must be cleared using a read-modify-write software routine
on the whole CANSTMOB register.
The receiver performs a CRC check on every de-stuffed received message from the start of
frame up to the data field. If this checking does not match with the de-stuffed CRC field, a CRC
error is set.
• Bit 1 – FERR: Form Error
This flag can generate an interrupt. It must be cleared using a read-modify-write software routine
on the whole CANSTMOB register.
The form error results from one or more violations of the fixed form in the following bit fields:
• CRC delimiter.
• Acknowledgment delimiter.
• EOF
• Bit 0 – AERR: Acknowledgment Error
This flag can generate an interrupt. It must be cleared using a read-modify-write software routine
on the whole CANSTMOB register.
No detection of the dominant bit in the acknowledge slot.
16.11.2
CAN MOb Control and DLC Register - CANCDMOB
Bit
7
6
5
4
3
2
1
0
CONMOB1
CONMOB0
RPLV
IDE
DLC3
DLC2
DLC1
DLC0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
-
-
-
-
CANCDMOB
• Bit 7:6 – CONMOB1:0: Configuration of Message Object
These bits set the communication to be performed (no initial value after RESET).
– 00 - disable.
– 01 - enable transmission.
– 10 - enable reception.
– 11 - enable frame buffer reception
197
7647F–AVR–04/09
These bits are not cleared once the communication is performed. The user must re-write the
configuration to enable a new communication.
• This operation is necessary to be able to reset the BXOK flag.
• This operation also set the corresponding bit in the CANEN registers.
• Bit 5 – RPLV: Reply Valid
Used in the automatic reply mode after receiving a remote frame.
– 0 - reply not ready.
– 1 - reply ready and valid.
• Bit 4 – IDE: Identifier Extension
IDE bit of the remote or data frame to send.
This bit is updated with the corresponding value of the remote or data frame received.
– 0 - CAN standard rev 2.0 A (identifiers length = 11 bits).
– 1 - CAN standard rev 2.0 B (identifiers length = 29 bits).
• Bit 3:0 – DLC3:0: Data Length Code
Number of Bytes in the data field of the message.
DLC field of the remote or data frame to send. The range of DLC is from 0 up to 8. If DLC field >8
then effective DLC=8.
This field is updated with the corresponding value of the remote or data frame received. If the
expected DLC differs from the incoming DLC, a DLC warning appears in the CANSTMOB
register.
16.11.3
CAN Identifier Tag Registers CANIDT1, CANIDT2, CANIDT3, and CANIDT4
V2.0 part A
Bit
15/7
14/6
13/5
12/4
11/3
10/2
9/1
8/0
-
-
-
-
-
RTRTAG
-
RB0TAG
-
-
-
-
-
-
-
-
CANIDT3
IDT2
IDT1
IDT0
-
-
-
-
-
CANIDT2
CANIDT1
IDT10
IDT9
IDT8
IDT7
IDT6
IDT5
IDT4
IDT3
Bit
31/23
30/22
29/21
28/20
27/19
26/18
25/17
24/16
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
-
-
-
-
CANIDT4
V2.0 part B
Bit
198
15/7
14/6
13/5
12/4
11/3
10/2
9/1
8/0
IDT4
IDT3
IDT2
IDT1
IDT0
RTRTAG
RB1TAG
RB0TAG
IDT12
IDT11
IDT10
IDT9
IDT8
IDT7
IDT6
IDT5
CANIDT3
IDT20
IDT19
IDT18
IDT17
IDT16
IDT15
IDT14
IDT13
CANIDT2
CANIDT1
IDT28
IDT27
IDT26
IDT25
IDT24
IDT23
IDT22
IDT21
Bit
31/23
30/22
29/21
28/20
27/19
26/18
25/17
24/16
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
-
-
-
-
CANIDT4
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
V2.0 part A
• Bit 31:21 – IDT10:0: Identifier Tag
Identifier field of the remote or data frame to send.
This field is updated with the corresponding value of the remote or data frame received.
• Bit 20:3 – Reserved Bits
These bits are reserved for future use. For compatibility with future devices, they must be written
to zero when CANIDTn are written.
When a remote or data frame is received, these bits do not operate in the comparison but they
are updated with un-predicted values.
• Bit 2 – RTRTAG: Remote Transmission Request Tag
RTR bit of the remote or data frame to send.
This tag is updated with the corresponding value of the remote or data frame received. In case
of Automatic Reply mode, this bit is automatically reset before sending the response.
• Bit 1 – Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANIDTn are written.
When a remote or data frame is received, this bit does not operate in the comparison but it is
updated with un-predicted values.
• Bit 0 – RB0TAG: Reserved Bit 0 Tag
RB0 bit of the remote or data frame to send.
This tag is updated with the corresponding value of the remote or data frame received.
V2.0 part B
• Bit 31:3 – IDT28:0: Identifier Tag
Identifier field of the remote or data frame to send.
This field is updated with the corresponding value of the remote or data frame received.
• Bit 2 – RTRTAG: Remote Transmission Request Tag
RTR bit of the remote or data frame to send.
This tag is updated with the corresponding value of the remote or data frame received. In case
of Automatic Reply mode, this bit is automatically reset before sending the response.
• Bit 1 – RB1TAG: Reserved Bit 1 Tag
RB1 bit of the remote or data frame to send.
This tag is updated with the corresponding value of the remote or data frame received.
• Bit 0 – RB0TAG: Reserved Bit 0 Tag
RB0 bit of the remote or data frame to send.
This tag is updated with the corresponding value of the remote or data frame received.
199
7647F–AVR–04/09
16.11.4
CAN Identifier Mask Registers CANIDM1, CANIDM2, CANIDM3, and CANIDM4
V2.0 part A
Bit
15/7
14/6
13/5
12/4
11/3
10/2
9/1
8/0
-
-
-
-
-
RTRMSK
-
IDEMSK
-
-
-
-
-
-
-
-
CANIDM3
IDMSK2
IDMSK1
IDMSK0
-
-
-
-
-
CANIDM2
CANIDM1
IDMSK10
IDMSK9
IDMSK8
IDMSK7
IDMSK6
IDMSK5
IDMSK4
IDMSK3
Bit
31/23
30/22
29/21
28/20
27/19
26/18
25/17
24/16
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
-
-
-
-
CANIDM4
V2.0 part B
Bit
15/7
14/6
13/5
12/4
11/3
10/2
9/1
8/0
IDMSK4
IDMSK3
IDMSK2
IDMSK1
IDMSK0
RTRMSK
-
IDEMSK
IDMSK12
IDMSK11
IDMSK10
IDMSK9
IDMSK8
IDMSK7
IDMSK6
IDMSK5
CANIDM3
IDMSK20
IDMSK19
IDMSK18
IDMSK17
IDMSK16
IDMSK15
IDMSK14
IDMSK13
CANIDM2
CANIDM1
IDMSK28
IDMSK27
IDMSK26
IDMSK25
IDMSK24
IDMSK23
IDMSK22
IDMSK21
Bit
31/23
30/22
29/21
28/20
27/19
26/18
25/17
24/16
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
-
-
-
-
CANIDM4
V2.0 part A
• Bit 31:21 – IDMSK10:0: Identifier Mask
– 0 - comparison true forced - See “Acceptance Filter” on page 180.
– 1 - bit comparison enabled - See “Acceptance Filter” on page 180.
• Bit 20:3 – Reserved Bits
These bits are reserved for future use. For compatibility with future devices, they must be written
to zero when CANIDMn are written.
• Bit 2 – RTRMSK: Remote Transmission Request Mask
– 0 - comparison true forced
– 1 - bit comparison enabled.
• Bit 1 – Reserved Bit
This bit is reserved for future use. For compatibility with future devices, it must be written to zero
when CANIDTn are written.
• Bit 0 – IDEMSK: Identifier Extension Mask
– 0 - comparison true forced
– 1 - bit comparison enabled.
V2.0 part B
• Bit 31:3 – IDMSK28:0: Identifier Mask
– 0 - comparison true forced - See “Acceptance Filter” on page 180.
– 1 - bit comparison enabled. - See “Acceptance Filter” on page 180.
200
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 2 – RTRMSK: Remote Transmission Request Mask
– 0 - comparison true forced
– 1 - bit comparison enabled.
• Bit 1 – Reserved Bit
Writing zero in this bit is recommended.
• Bit 0 – IDEMSK: Identifier Extension Mask
– 0 - comparison true forced
– 1 - bit comparison enabled.
16.11.5
CAN Time Stamp Registers - CANSTML and CANSTMH
Bit
7
6
5
4
3
2
1
0
TIMSTM7
TIMSTM6
TIMSTM5
TIMSTM4
TIMSTM3
TIMSTM2
TIMSTM1
TIMSTM0
CANSTML
TIMSTM15 TIMSTM14 TIMSTM13 TIMSTM12 TIMSTM11 TIMSTM10
TIMSTM9
TIMSTM8
CANSTMH
Bit
15
14
13
12
11
10
9
8
Read/Write
R
R
R
R
R
R
R
R
Initial Value
-
-
-
-
-
-
-
-
• Bits 15:0 - TIMSTM15:0: Time Stamp Count
CAN time stamp counter range 0 to 65,535.
16.11.6
CAN Data Message Register - CANMSG
Bit
7
6
5
4
3
2
1
0
MSG 7
MSG 6
MSG 5
MSG 4
MSG 3
MSG 2
MSG 1
MSG 0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
-
-
-
-
CANMSG
• Bit 7:0 – MSG7:0: Message Data
This register contains the CAN data byte pointed at the page MOb register.
After writing in the page MOb register, this byte is equal to the specified message location of the
pre-defined identifier + index. If auto-incrementation is used, at the end of the data register writing or reading cycle, the index is auto-incremented.
The range of the counting is 8 with no end of loop (0, 1,..., 7, 0,...).
201
7647F–AVR–04/09
16.12 Examples of CAN Baud Rate Setting
The CAN bus requires very accurate timing especially for high baud rates. It is recommended to
use only an external crystal for CAN operations.
(Refer to “Bit Timing” on page 176 and “Baud Rate” on page 177 for timing description and page
192 to page 194 for “CAN Bit Timing Registers”).
Table 16-2.
fCLKIO
(MHz)
Examples of CAN Baud Rate Settings for Commonly Frequencies
CAN
Rate
(Kbps)
1000
Description
Sampling
Point
69 %
(1)
75 %
500
75 %
250
75 %
200
75 %
125
75 %
100
75 %
1000
67 % (1)
500
75 %
250
75 %
200
75 %
125
75 %
100
75 %
16.000
12.000
202
Segments
Registers
TQ
(µs)
Tbit
(TQ)
Tprs
(TQ)
Tph1
(TQ)
Tph2
(TQ)
Tsjw
(TQ)
CANBT1
CANBT2
CANBT3
0.0625
16
7
4
4
1
0x00
0x0C
0x36 (2)
0.125
8
3
2
2
1
0x02
0x04
0x13
0.125
16
7
4
4
1
0x02
0x0C
0x37
0.250
8
3
2
2
1
0x06
0x04
0x13
0.250
16
7
4
4
1
0x06
0x0C
0x37
0.500
8
3
2
2
1
0x0E
0x04
0x13
0.3125
16
7
4
4
1
0x08
0x0C
0x37
0.625
8
3
2
2
1
0x12
0x04
0x13
0.500
16
7
4
4
1
0x0E
0x0C
0x37
1.000
8
3
2
2
1
0x1E
0x04
0x13
0.625
16
7
4
4
1
0x12
0x0C
0x37
1.250
8
3
2
2
1
0x26
0x04
0x13
0.083333
12
5
3
3
1
0x00
0x08
0x24 (2)
x
- - - no
data- - -
0.166666
12
5
3
3
1
0x02
0x08
0x25
0.250
8
3
2
2
1
0x04
0x04
0x13
0.250
16
7
4
4
1
0x04
0x0C
0x37
0.500
8
3
2
2
1
0x0A
0x04
0x13
0.250
20
8
6
5
1
0x04
0x0E
0x4B
0.416666
12
5
3
3
1
0x08
0x08
0x25
0.500
16
7
4
4
1
0x0A
0x0C
0x37
1.000
8
3
2
2
1
0x16
0x04
0x13
0.500
20
8
6
5
1
0x0A
0x0E
0x4B
0.833333
12
5
3
3
1
0x12
0x08
0x25
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 16-2.
fCLKIO
(MHz)
Examples of CAN Baud Rate Settings for Commonly Frequencies (Continued)
CAN
Rate
(Kbps)
1000
500
Description
Sampling
Point
63 % (1)
TQ
(µs)
Segments
Tbit
(TQ)
x
CANBT2
CANBT3
data- - -
2
1
0x00
0x04
0x12 (2)
69 % (1)
0.125
16
7
4
4
1
0x00
0x0C
0x36 (2)
75 %
0.250
8
3
2
2
1
0x02
0x04
0x13
0.250
16
7
4
4
1
0x02
0x0C
0x37
0.500
8
3
2
2
1
0x06
0x04
0x13
0.250
20
8
6
5
1
0x02
0x0E
0x4B
0.625
8
3
2
2
1
0x08
0x04
0x13
0.500
16
7
4
4
1
0x06
0x0C
0x37
1.000
8
3
2
2
1
0x0E
0x04
0x13
0.625
16
7
4
4
1
0x08
0x0C
0x37
1.250
8
3
2
2
1
0x12
0x04
0x13
0x00
0x08
0x24 (2)
200
75 %
125
75 %
100
75 %
- - - not
500
67 % (1)
250
75 %
200
80 %
125
75 %
100
75 %
0.166666
12
5
applicable- - 3
1
- - - no
data- - -
0.333333
12
5
3
3
1
0x02
0x08
0x25
0.500
8
3
2
2
1
0x04
0x04
0x13
0.333333
15
7
4
3
1
0x02
0x0C
0x35
0.500
10
4
3
2
1
0x04
0x06
0x23
0.500
16
7
4
4
1
0x04
0x0C
0x37
1.000
8
3
2
2
1
0x0A
0x04
0x13
0.500
20
8
6
5
1
0x04
0x0E
0x4B
0.833333
12
5
3
3
1
0x08
0x08
0x25
- - - not
63 % (1)
3
x
1000
Note:
- - - no
CANBT1
2
1000
4.000
Tsjw
(TQ)
3
75 %
250
Tph2
(TQ)
8
250
500
Tph1
(TQ)
0.125
8.000
6.000
Tprs
(TQ)
Registers
applicable- - -
x
- - - no
data- - -
0.250
8
3
2
2
1
0x00
0x04
0x12 (2)
69 % (1)
0.250
16
7
4
4
1
0x00
0x0C
0x36 (2)
75 %
0.500
8
3
2
2
1
0x02
0x04
0x13
0.250
20
8
6
5
1
0x00
0x0E
0x4A (2)
200
70 % (1)
125
75 %
100
75 %
x
- - - no
data- - -
0.500
16
7
4
4
1
0x02
0x0C
0x37
1.000
8
3
2
2
1
0x06
0x04
0x13
0.500
20
8
6
5
1
0x02
0x0E
0x4B
1.250
8
3
2
2
1
0x08
0x04
0x13
1. See Section 16.4.3 “Baud Rate” on page 177.
2. See Section • “Bit 0 – SMP: Sample Point(s)” on page 194
203
7647F–AVR–04/09
17. LIN / UART - Local Interconnect Network Controller or UART
The LIN (Local Interconnect Network) is a serial communications protocol which efficiently supports the control of mechatronics nodes in distributed automotive applications. The main
properties of the LIN bus are:
•
•
•
•
•
•
Single master with multiple slaves concept
Low cost silicon implementation based on common UART/SCI interface
Self synchronization in slave node
Deterministic signal transmission with signal propagation time computable in advance
Low cost single-wire implementation
Speed up to 20 Kbit/s.
LIN provides a cost efficient bus communication where the bandwidth and versatility of CAN are
not required. The specification of the line driver/receiver needs to match the ISO9141
NRZ-standard.
If LIN is not required, the controller alternatively can be programmed as Universal Asynchronous
serial Receiver and Transmitter (UART).
17.1
LIN Features
• Hardware Implementation of LIN 2.1 (LIN 1.3 Compatibility)
• Small, CPU Efficient and Independent Master/Slave Routines Based on “LIN Work Flow Concept”
•
•
•
•
•
•
•
17.2
UART Features
•
•
•
•
•
204
of LIN 2.1 Specification
Automatic LIN Header Handling and Filtering of Irrelevant LIN Frames
Automatic LIN Response Handling
Extended LIN Error Detection and Signaling
Hardware Frame Time-out Detection
“Break-in-data” Support Capability
Automatic Re-synchronization to Ensure Proper Frame Integrity
Fully Flexible Extended Frames Support Capabilities
Full Duplex Operation (Independent Serial Receive and Transmit Processes)
Asynchronous Operation
High Resolution Baud Rate Generator
Hardware Support of 8 Data Bits, Odd/Even/No Parity Bit, 1 Stop Bit Frames
Data Over-Run and Framing Error Detection
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.3
17.3.1
LIN Protocol
Master and Slave
A LIN cluster consists of one master task and several slave tasks. A master node contains the
master task as well as a slave task. All other nodes contain a slave task only.
Figure 17-1. LIN cluster with one master node and “n” slave nodes
master node
master task
slave node
1
slave node
n
slave task
slave task
slave task
LIN bus
The master task decides when and which frame shall be transferred on the bus. The slave tasks
provide the data transported by each frame. Both the master task and the slave task are parts of
the Frame handler
17.3.2
Frames
A frame consists of a header (provided by the master task) and a response (provided by a slave
task).
The header consists of a BREAK and SYNC pattern followed by a PROTECTED IDENTIFIER.
The identifier uniquely defines the purpose of the frame. The slave task appointed for providing
the response associated with the identifier transmits it. The response consists of a DATA field
and a CHECKSUM field.
Figure 17-2. Master and slave tasks behavior in LIN frame
Master Task
HEADER
HEADER
RESPONSE
Slave Task 1
RESPONSE
Slave Task 2
The slave tasks waiting for the data associated with the identifier receives the response and
uses the data transported after verifying the checksum.
Figure 17-3. Structure of a LIN frame
FRAME SLOT
HEADER
BREAK
Field
Break Delimiter
SYNC
RESPONSE
Field
PROTECTED
IDENTIFIER
Field
Response Space
DATA-0
Field
DATA-n
Field
CHECKSUM
Inter-Byte Space
Field
Inter-Frame Space
Each byte field is transmitted as a serial byte, LSB first.
205
7647F–AVR–04/09
17.3.3
Data Transport
Two types of data may be transported in a frame; signals or diagnostic messages.
• Signals
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
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.
17.3.4
Schedule Table
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.
17.3.5
Compatibility with LIN 1.3
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:
• Enhanced checksum,
• Re-configuration and diagnostics,
• Automatic baud rate detection,
• "Response error" status monitoring.
LIN 2.1 slave nodes can not operate with a LIN 1.3 master node (e.g. 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, i.e. a master node
using the LIN 2.1 physical layer can operate in a LIN 1.3 cluster.
17.4
LIN / UART Controller
The LIN/UART controller is divided in three main functions:
• Tx LIN Header function,
• Rx LIN Header function,
• LIN Response function.
These functions mainly use two services:
• Rx service,
• Tx service.
Because these two services are basically UART services, the controller is also able to switch
into an UART function.
206
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.4.1
LIN Overview
The LIN/UART controller is designed to match as closely as possible to the LIN software application structure. The LIN software application is developed as independent tasks, several slave
tasks and one master task (c.f. Section 17.3.4 on page 206). The ATmega16/32/64/M1/C1 conforms 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:
• LIDOK: New LIN identifier available,
• LRXOK: LIN response received,
• LTXOK: LIN response transmitted,
• LERR: LIN Error(s).
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.
17.4.2
UART Overview
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.
207
7647F–AVR–04/09
17.4.3
LIN/UART Controller Structure
Figure 17-4. LIN/UART Controller Block Diagram
CLK IO
RxD
Finite State Machine
Prescaler
Sample /bit
FSM
BAUD_RATE
Get Byte
RX
Put Byte
TX
Frame Time-out
TxD
Synchronization
Monitoring
Data FIFO
17.4.4
BUFFER
LIN/UART Command Overview
Figure 17-5. LIN/UART Command Dependencies
Tx
Response
Tx Header
IDOK
TXOK
Rx Header
or
LIN Abort
Rx
Response
RXOK
Automatic
Return
Recommended
Way
LIN
DISABLE
UART
Possible
Way
Byte
Transfer
Rx
Byte
Full
Duplex
Tx
Byte
208
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 17-1.
LIN/UART Command List
LENA
LCMD[2]
LCMD[1]
LCMD[0]
Command
0
x
x
x
Disable peripheral
0
Rx Header - LIN abort
LIN withdrawal
1
Tx Header
LCMD[2..0]=000 after Tx
0
Rx Response
LCMD[2..0]=000 after Rx
1
Tx Response
LCMD[2..0]=000 after Tx
0
0
Byte transfer
1
0
Rx Byte
0
1
Tx Byte
1
1
Full duplex
0
0
1
1
1
Comment
no CRC, no Time out
LTXDL=LRXDL=0
(LINDLR: read only register)
17.4.5
Enable / Disable
Setting the LENA bit in LINCR register enables the LIN/UART controller. To disable the
LIN/UART controller, LENA bit must be written to 0. No wait states are implemented, so, the disable command is taken into account immediately.
17.4.6
LIN Commands
Clearing the LCMD[2] bit in LINCR register enables LIN commands.
As shown in Table 17-1 on page 209, four functions controlled by the LCMD[1..0] bits of LINCR
register are available (c.f. Figure 17-5 on page 208).
17.4.6.1
Rx Header / LIN Abort Function
This function (or state) is mainly the withdrawal mode of the controller.
When the controller has to execute a master task, this state is the start point before enabling a
Tx Header command.
When the controller has only to execute slave tasks, LIN header detection/acquisition is enabled
as background function. At the end of such an acquisition (Rx Header function), automatically
the appropriate flags are set, and in LIN 1.3, the LINDLR register is set with the uncoded length
value.
This state is also the start point before enabling the Tx or the Rx Response command.
A running function (i.e. Tx Header, Tx or Rx Response) can be aborted by clearing LCMD[1..0]
bits in LINCR register. In this case, an abort flag - LABORT - in LINERR register will be set to
inform the other software tasks. No wait states are implemented, so, the abort command is taken
into account immediately.
Rx Header function is responsible for:
• The BREAK field detection,
• The hardware re-synchronization analyzing the SYNCH field,
• The reception of the PROTECTED IDENTIFIER field, the parity control and the update of the
LINDLR register in case of LIN 1.3,
• The starting of the Frame_Time_Out,
• The checking of the LIN communication integrity.
209
7647F–AVR–04/09
17.4.6.2
Tx Header Function
In accordance with the LIN protocol, only the master task must enable this function. The header
is sent in the appropriate timed slots at the programmed baud rate (c.f. LINBRR & LINBTR
registers).
The controller is responsible for:
• The transmission of the BREAK field - 13 dominant bits,
• The transmission of the SYNCH field - character 0x55,
• The transmission of the PROTECTED IDENTIFIER field. It is the full content of the LINIDR
register (automatic check bits included).
At the end of this transmission, the controller automatically returns to Rx Header / LIN Abort
state (i.e. LCMD[1..0] = 00) after setting the appropriate flags. This function leaves the controller
in the same setting as after the Rx Header function. This means that, in LIN 1.3, the LINDLR
register is set with the uncoded length value at the end of the Tx Header function.
During this function, the controller is also responsible for:
• The starting of the Frame_Time_Out,
• The checking of the LIN communication integrity.
17.4.6.3
Rx & TX Response Functions
These functions are initiated by the slave task of a LIN node. They must be used after sending
an header (master task) or after receiving an header (considered as belonging to the slave task).
When the TX Response order is sent, the transmission begins. A Rx Response order can be
sent up to the reception of the last serial bit of the first byte (before the stop-bit).
In LIN 1.3, the header slot configures the LINDLR register. In LIN 2.1, the user must configure
the LINDLR register, either LRXDL[3..0] for Rx Response either LTXDL[3..0] for Tx Response.
When the command starts, the controller checks the LIN13 bit of the LINCR register to apply the
right rule for computing the checksum. Checksum calculation over the DATA bytes and the
PROTECTED IDENTIFIER byte is called enhanced checksum and it is used for communication
with LIN 2.1 slaves. Checksum calculation over the DATA bytes only is called classic checksum
and it is used for communication with LIN 1.3 slaves. Note that identifiers 60 (0x3C) to 63 (0x3F)
shall always use classic checksum.
At the end of this reception or transmission, the controller automatically returns to Rx Header /
LIN Abort state (i.e. LCMD[1..0] = 00) after setting the appropriate flags.
If an LIN error occurs, the reception or the transmission is stopped, the appropriate flags are set
and the LIN bus is left to recessive state.
During these functions, the controller is responsible for:
• The initialization of the checksum operator,
• The transmission or the reception of ‘n’ data with the update of the checksum calculation,
• The transmission or the checking of the CHECKSUM field,
• The checking of the Frame_Time_Out,
• The checking of the LIN communication integrity.
While the controller is sending or receiving a response, BREAK and SYNCH fields can be
detected and the identifier of this new header will be recorded. Of course, specific errors on the
previous response will be maintained with this identifier reception.
210
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.4.6.4
Handling Data of LIN response
A FIFO data buffer is used for data of the LIN response. After setting all parameters in the LINSEL register, repeated accesses to the LINDAT register perform data read or data write (c.f.
“Data Management” on page 221).
Note that LRXDL[3..0] and LTXDL[3..0] are not linked to the data access.
17.4.7
UART Commands
Setting the LCMD[2] bit in LINENR register enables UART commands.
Tx Byte and Rx Byte services are independent as shown in Table 17-1 on page 209.
• Byte Transfer: the UART is selected but both Rx and Tx services are disabled,
• Rx Byte: only the Rx service is enable but Tx service is disabled,
• Tx Byte: only the Tx service is enable but Rx service is disabled,
• Full Duplex: the UART is selected and both Rx and Tx services are enabled.
This combination of services is controlled by the LCMD[1..0] bits of LINENR register (c.f. Figure
17-5 on page 208).
17.4.7.1
Data Handling
The FIFO used for LIN communication is disabled during UART accesses. LRXDL[3..0] and
LTXDL[3..0] values of LINDLR register are then irrelevant. LINDAT register is then used as data
register and LINSEL register is not relevant.
17.4.7.2
Rx Service
Once this service is enabled, the user is warned of an in-coming character by the LRXOK flag of
LINSIR register. Reading LINDAT register automatically clears the flag and makes free the second stage of the buffer. If the user considers that the in-coming character is irrelevant without
reading it, he directly can clear the flag (see specific flag management described in Section
17.6.2 on page 224).
The intrinsic structure of the Rx service offers a 2-byte buffer. The fist one is used for serial to
parallel conversion, the second one receives the result of the conversion. This second buffer
byte is reached reading LINDAT register. If the 2-byte buffer is full, a new in-coming character
will overwrite the second one already recorded. An OVRERR error in LINERR register will then
accompany this character when read.
A FERR error in LINERR register will be set in case of framing error.
17.4.7.3
Tx Service
If this service is enabled, the user sends a character by writing in LINDAT register. Automatically
the LTXOK flag of LINSIR register is cleared. It will rise at the end of the serial transmission. If
no new character has to be sent, LTXOK flag can be cleared separately (see specific flag management described in Section 17.6.2 on page 224).
There is no transmit buffering.
No error is detected by this service.
211
7647F–AVR–04/09
17.5
17.5.1
LIN / UART Description
Reset
The AVR core reset logic signal also resets the LIN/UART controller. Another form of reset
exists, a software reset controlled by LSWRES bit in LINCR register. This self-reset bit performs
a partial reset as shown in Table 17-2.
Table 17-2.
Reset of LIN/UART Registers
Register
17.5.2
Name
Reset Value
LSWRES Value
LIN Control Reg.
LINCR
0000 0000 b
0000 0000 b
LIN Status & Interrupt Reg.
LINSIR
0000 0000 b
0000 0000 b
LIN Enable Interrupt Reg.
LINENIR
0000 0000 b
xxxx 0000 b
LIN Error Reg.
LINERR
0000 0000 b
0000 0000 b
LIN Bit Timing Reg.
LINBTR
0010 0000 b
0010 0000 b
LIN Baud Rate Reg. Low
LINBRRL
0000 0000 b
uuuu uuuu b
LIN Baud Rate Reg. High
LINBRRH
0000 0000 b
xxxx uuuu b
LIN Data Length Reg.
LINDLR
0000 0000 b
0000 0000 b
LIN Identifier Reg.
LINIDR
1000 0000 b
1000 0000 b
LIN Data Buffer Selection
LINSEL
0000 0000 b
xxxx 0000 b
LIN Data
LINDAT
0000 0000 b
0000 0000 b
Comment
x=unknown
u=unchanged
Clock
The I/O clock signal (clki/o) also clocks the LIN/UART controller. It is its unique clock.
17.5.3
LIN Protocol Selection
LIN13 bit in LINCR register is used to select the LIN protocol:
• LIN13 = 0 (default): LIN 2.1 protocol,
• LIN13 = 1: LIN 1.3 protocol.
The controller checks the LIN13 bit in computing the checksum (enhanced checksum in LIN2.1 /
classic checksum in LIN 1.3). See “Rx & TX Response Functions” on page 210.
This bit is irrelevant for UART commands.
212
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.5.4
Configuration
Depending on the mode (LIN or UART), LCONF[1..0] bits of the LINCR register set the controller
in the following configuration (Table 17-3):
Table 17-3.
Mode
Configuration Table versus Mode
LCONF[1..0]
Configuration
00 b
LIN standard configuration (default)
01 b
No CRC field detection or transmission
10 b
Frame_Time_Out disable
11 b
Listening mode
00 b
8-bit data, no parity & 1 stop-bit
01 b
8-bit data, even parity & 1 stop-bit
10 b
8-bit data, odd parity & 1 stop-bit
11 b
Listening mode, 8-bit data, no parity & 1 stop-bit
LIN
UART
The LIN configuration is independent of the programmed LIN protocol.
The listening mode connects the internal Tx LIN and the internal Rx LIN together. In this mode,
the TXLIN output pin is disabled and the RXLIN input pin is always enabled. The same scheme
is available in UART mode.
Figure 17-6. Listening Mode
internal
Tx LIN
TXLIN
LISTEN
17.5.5
internal
1
Rx LIN
0
RXLIN
Busy Signal
LBUSY bit flag in LINSIR register is the image of the BUSY signal. It is set and cleared by hardware. It signals that the controller is busy with LIN or UART communication.
17.5.5.1
Busy Signal in LIN Mode
Figure 17-7. Busy Signal in LIN Mode
FRAME SLOT
HEADER
LIN bus
1) LBUSY
BREAK
Field
SYNC
RESPONSE
Field
PROTECTED
IDENTIFIER
Field
DATA-0
DATA-n
Field
Field
CHECKSUM
Field
Node providing the master task
2) LBUSY
Node providing a slave task
Node providing neither the master task, neither a slave task
3) LBUSY
LCMD=Tx Header
LIDOK
LCMD=Tx or Rx Response
LTXOK or LRXOK
213
7647F–AVR–04/09
When the busy signal is set, some registers are locked, user writing is not allowed:
• “LIN Control Register” - LINCR - except LCMD[2..0], LENA & LSWRES,
• “LIN Baud Rate Registers” - LINBRRL & LINBRRH,
• “LIN Data Length Register” - LINDLR,
• “LIN Identifier Register” - LINIDR,
• “LIN Data Register” - LINDAT.
If the busy signal is set, the only available commands are:
• LCMD[1..0] = 00 b, the abort command is taken into account at the end of the byte,
• LENA = 0 and/or LCMD[2] = 0, the kill command is taken into account immediately,
• LSWRES = 1, the reset command is taken into account immediately.
Note that, if another command is entered during busy signal, the new command is not validated
and the LOVRERR bit flag of the LINERR register is set. The on-going transfer is not
interrupted.
17.5.5.2
Busy Signal in UART Mode
During the byte transmission, the busy signal is set. This locks some registers from being
written:
• “LIN Control Register” - LINCR - except LCMD[2..0], LENA & LSWRES,
• “LIN Data Register” - LINDAT.
The busy signal is not generated during a byte reception.
17.5.6
17.5.6.1
Bit Timing
Baud rate Generator
The baud rate is defined to be the transfer rate in bits per second (bps):
• BAUD: Baud rate (in bps),
• fclki/o: System I/O clock frequency,
• LDIV[11..0]: Contents of LINBRRH & LINBRRL registers - (0-4095), the pre-scaler receives
clki/o as input clock.
• LBT[5..0]: Least significant bits of - LINBTR register- (0-63) is the number of samplings in a
LIN or UART bit (default value 32).
Equation for calculating baud rate:
BAUD = fclki/o / LBT[5..0] x (LDIV[11..0] + 1)
Equation for setting LINDIV value:
LDIV[11..0] = ( fclki/o / LBT[5..0] x BAUD ) - 1
Note that in reception a majority vote on three samplings is made.
214
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.5.6.2
Re-synchronization in LIN Mode
When waiting for Rx Header, LBT[5..0] = 32 in LINBTR register. The re-synchronization begins
when the BREAK is detected. If the BREAK size is not in the range (11 bits min., 28 bits max. —
13 bits nominal), the BREAK is refused. The re-synchronization is done by adjusting LBT[5..0]
value to the SYNCH field of the received header (0x55). Then the PROTECTED IDENTIFIER is
sampled using the new value of LBT[5..0]. The re-synchronization implemented in the controller
tolerates a clock deviation of ±20% and adjusts the baud rate in a ±2% range.
The new LBT[5..0] value will be used up to the end of the response. Then, the LBT[5..0] will be
reset to 32 for the next header.
The LINBTR register can be used to re-calibrate the clock oscillator.
The re-synchronization is not performed if the LIN node is enabled as a master.
17.5.6.3
Handling LBT[5..0]
LDISR bit of LINBTR register is used to:
• To enable the setting of LBT[5..0] (to manually adjust the baud rate especially in the case of
UART mode). A minimum of 8 is required for LBT[5..0] due to the sampling operation.
• Disable the re-synchronization in LIN Slave Mode for test purposes.
Note that the LENA bit of LINCR register is important for this handling (see Figure 17-8 on page
215).
Figure 17-8. Handling LBT[5..0]
Write in LINBTR register
=1
LENA ?
(LINCR bit 4)
=0
LDISR
to write
=1
=0
LBT[5..0] forced to 0x20
LDISR forced to 0
Enable re-synch. in LIN mode
17.5.7
LBT[5..0] = LBT[5..0] to write
(LBT[5..0]min=8)
LDISR forced to 1
Disable re-synch. in LIN mode
Data Length
Section 17.4.6 “LIN Commands” on page 209 describes how to set or how are automatically set
the LRXDL[3..0] or LTXDL[3..0] fields of LINDLR register before receiving or transmitting a
response.
In the case of Tx Response the LRXDL[3..0] will be used by the hardware to count the number of
bytes already successfully sent.
In the case of Rx Response the LTXDL[3..0] will be used by the hardware to count the number of
bytes already successfully received.
If an error occurs, this information is useful to the programmer to recover the LIN messages.
215
7647F–AVR–04/09
17.5.7.1
Data Length in LIN 2.1
• If LTXDL[3..0]=0 only the CHECKSUM will be sent,
• If LRXDL[3..0]=0 the first byte received will be interpreted as the CHECKSUM,
• If LTXDL[3..0] or LRXDL[3..0] >8, values will be forced to 8 after the command setting and
before sending or receiving of the first byte.
17.5.7.2
Data Length in LIN 1.3
• LRXDL and LTXDL fields are both hardware updated before setting LIDOK by decoding the
data length code contained in the received PROTECTED IDENTIFIER (LRXDL = LTXDL).
• Via the above mechanism, a length of 0 or >8 is not possible.
17.5.7.3
Data Length in Rx Response
Figure 17-9. LIN2.1 - Rx Response - No error
LIDOK
LIN bus
LRXDL (*)
4
LTXDL (*)
?
LRXOK
1st Byte
2 nd Byte
3 rd Byte
4 th Byte
DATA-0
DATA-1
DATA-2
DATA-3
CHECKSUM
1
2
3
4
0
LBUSY
LCMD=Rx Response
LCMD2..0=000b
LINDLR=0x?4
(*) : LRXDL & LTXDL updated by user
• The user initializes LRXDL field before setting the Rx Response command,
• After setting the Rx Response command, LTXDL is reset by hardware,
• LRXDL field will remain unchanged during Rx (during busy signal),
• LTXDL field will count the number of received bytes (during busy signal),
• If an error occurs, Rx stops, the corresponding error flag is set and LTXDL will give the
number of received bytes without error,
• If no error occurs, LRXOK is set after the reception of the CHECKSUM, LRXDL will be
unchanged (and LTXDL = LRXDL).
216
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.5.7.4
Data Length in Tx Response
Figure 17-10. LIN1.3 - Tx Response - No error
LIDOK
LIN bus
LRXDL (*)
4
LTXDL (*)
4
1st Byte
2 nd Byte
3 rd Byte
4 th Byte
DATA-0
DATA-1
DATA-2
DATA-3
0
1
2
LTXOK
CHECKSUM
3
4
LBUSY
LCMD2..0=000b
LCMD=Tx Response
(*) : LRXDL & LTXDL updated by Rx Response or Tx Response task
• The user initializes LTXDL field before setting the Tx Response command,
• After setting the Tx Response command, LRXDL is reset by hardware,
• LTXDL will remain unchanged during Tx (during busy signal),
• LRXDL will count the number of transmitted bytes (during busy signal),
• If an error occurs, Tx stops, the corresponding error flag is set and LRXDL will give the
number of transmitted bytes without error,
• If no error occurs, LTXOK is set after the transmission of the CHECKSUM, LTXDL will be
unchanged (and LRXDL = LTXDL).
17.5.7.5
Data Length after Error
Figure 17-11. Tx Response - Error
LIN bus
1st Byte
2 nd Byte
DATA-0
DATA-1
3 rd Byte
LERR
DATA-2
ERROR
LRXDL
4
LTXDL
4
0
1
2
LBUSY
LCMD2..0=000b
LCMD=Tx Response
Note:
17.5.7.6
Information on response (ex: error on byte) is only available at the end of the serialization/de-serialization of the byte.
Data Length in UART Mode
• The UART mode forces LRXDL and LTXDL to 0 and disables the writing in LINDLR register,
• Note that after reset, LRXDL and LTXDL are also forced to 0.
217
7647F–AVR–04/09
17.5.8
xxOK Flags
There are three xxOK flags in LINSIR register:
• LIDOK: LIN IDentifier OK
It is set at the end of the header, either by the Tx Header function or by the Rx Header. In LIN
1.3, before generating LIDOK, the controller updates the LRXDL & LTXDL fields in LINDLR
register.
It is not driven in UART mode.
• LRXOK: LIN RX response complete
It is set at the end of the response by the Rx Response function in LIN mode and once a
character is received in UART mode.
• LTXOK: LIN TX response complete
It is set at the end of the response by the Tx Response function in LIN mode and once a
character has been sent in UART mode.
These flags can generate interrupts if the corresponding enable interrupt bit is set in the LINENIR register (see Section 17.5.13 “Interrupts” on page 220).
17.5.9
xxERR Flags
LERR bit of the LINSIR register is an logical ‘OR’ of all the bits of LINERR register (see Section
17.5.13 “Interrupts” on page 220). There are eight flags:
• LBERR = LIN Bit ERRor.
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.
• LCERR = LIN Checksum ERRor.
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.
• LPERR = LIN Parity ERRor (identifier).
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 Section 17.6.8 “LIN Identifier Register
- LINIDR” on page 228). A LIN slave application does not distinguish between corrupted
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.
• LSERR = LIN Synchronization ERRor.
A LIN synchronization error will be flagged if a slave detects the edges of the SYNCH field
outside the given tolerance.
• LFERR = LIN Framing ERRor.
A framing error will be flagged if dominant STOP bit is sampled.
Same function in UART mode.
• LTOERR = LIN Time Out ERRor.
A time-out error will be flagged if the MESSAGE frame is not fully completed within the
maximum length T Frame_Maximum by any slave task upon transmission of the SYNCH and
IDENTIFIER fields (see Section 17.5.10 “Frame Time Out” on page 219).
218
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• LOVERR = LIN OVerrun ERRor.
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.
• LABORT
LIN abort transfer reflects a previous LIN Abort command (LCMD[2..0] = 000) while ‘Busy
signal’ is present.
After each LIN error, the LIN controller stops its previous activity and returns to its withdrawal
mode (LCMD[2..0] = 000 b) as illustrated in Figure 17-11 on page 217.
Writing 1 in LERR of LINSIR register resets LERR bit and all the bits of the LINERR register.
17.5.10
Frame Time Out
According to the LIN protocol, a frame time-out error is flagged if: T Frame > T Frame_Maximum. This
feature is implemented in the LIN/UART controller.
Figure 17-12. LIN timing and frame time-out
T Frame
T Header
BREAK
SYNC
Field
T Response
PROTECTED
IDENTIFIER
Field
DATA-0
Field
DATA-n
Field
Field
CHECKSUM
Field
Nominal
T Header_Nominal
T Response_Nominal
T Frame_Nominal
=
34 x
T Bit
T Bit
T Response_Nominal
=
10 ( Number_of_Data + 1 ) x
=
T Header_Nominal
+
Maximun
T Header_Maximum
T Response_Maximum
T Frame_Maximum
=
=
=
before Time-out
T Header_Nominal
1.4 x T Response_Nominal
T Header_Maximum + T Response_Maximum
1.4 x
219
7647F–AVR–04/09
17.5.11
Break-in-data
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 slave node(s), an error is generated (i.e. LBERR in case of Tx Response or LFERR in
case of Rx Response). Information on data error is also available, refer to the Section
17.5.7.5.
• On master node, the user (code) is responsible for this aborting of frame. To do this, the
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.
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.
17.5.12
Checksum
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.
n
n
⎞
⎞
⎛⎛
⎞
⎛⎛⎛
⎞
⎞⎞
⎛
CHECKSUM = 255 – ⎜ unsigned char ⎜ ⎜ ∑DATA n⎟ + PROTECTED ID.⎟ + unsigned char ⎜ ⎜ ⎜ ∑DATA n⎟ + PROTECTED ID.⎟ » 8⎟ ⎟
⎟
⎟
⎜⎜
⎟
⎜⎜⎜
⎟
⎟⎟
⎜
⎠
⎠
⎝⎝ 0
⎠
⎝⎝⎝ 0
⎠
⎠⎠
⎝
In LIN 1.3, the checksum contains the inverted eight bit sum with carry over all data bytes. This
calculation is called classic checksum.
⎛
⎛n
⎞
⎛⎛ n
⎞
⎞⎞
⎜
⎜
⎟
CHECKSUM = 255 – unsigned char ∑DATA n + unsigned char ⎜ ⎜ ∑DATA n⎟ » 8⎟ ⎟
⎜
⎜
⎟
⎜⎜
⎟
⎟⎟
⎝
⎝0
⎠
⎝⎝ 0
⎠
⎠⎠
Frame identifiers 60 (0x3C) to 61 (0x3D) shall always use classic checksum
17.5.13
Interrupts
As shown in Figure 17-13 on page 221, the four communication flags of the LINSIR register are
combined to drive two interrupts. Each of these flags have their respective enable interrupt bit in
LINENIR register.
(see Section 17.5.8 “xxOK Flags” on page 218 and Section 17.5.9 “xxERR Flags” on page 218).
220
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 17-13. LIN Interrupt Mapping
LINERR.7
LINERR.6
LINERR.5
LINERR.4
LINERR.3
LINERR.2
LINERR.1
LINERR.0
LABORT
LTOERR
LOVERR
LINSIR.3
LFERR
LSERR
LINENIR.3
LPERR
LENERR
LCERR
LINSIR.2
LBERR
LINSIR.1
LINSIR.0
17.5.14
LIN ERR
LERR
LINENIR.2
LENIDOK
LINENIR.1
LENTXOK
LINENIR.0
LENRXOK
LIDOK
LIN IT
LTXOK
LRXOK
Message Filtering
Message filtering based upon the whole identifier is not implemented. Only a status for frame
headers having 0x3C, 0x3D, 0x3E and 0x3F as identifier is available in the LINSIR register.
Table 17-4.
Frame Status
LIDST[2..0]
Frame Status
0xx b
No specific identifier
100 b
60 (0x3C) identifier
101 b
61 (0x3D) identifier
110 b
62 (0x3E) identifier
111 b
63 (0x3F) identifier
The LIN protocol says that a message with an identifier from 60 (0x3C) up to 63 (0x3F) uses a
classic checksum (sum over the data bytes only). Software will be responsible for switching correctly the LIN13 bit to provide/check this expected checksum (the insertion of the ID field in the
computation of the CRC is set - or not - just after entering the Rx or Tx Response command).
17.5.15
17.5.15.1
Data Management
LIN FIFO Data Buffer
To preserve register allocation, the LIN data buffer is seen as a FIFO (with address pointer
accessible). This FIFO is accessed via the LINDX[2..0] field of LINSEL register through the LINDAT register.
LINDX[2..0], the data index, is the address pointer to the required data byte. The data byte can
be read or written. The data index is automatically incremented after each LINDAT access if the
LAINC (active low) bit is cleared. A roll-over is implemented, after data index=7 it is data
index=0. Otherwise, if LAINC bit is set, the data index needs to be written (updated) before each
LINDAT access.
The first byte of a LIN frame is stored at the data index=0, the second one at the data index=1,
and so on. Nevertheless, LINSEL must be initialized by the user before use.
221
7647F–AVR–04/09
17.5.15.2
UART Data Register
The LINDAT register is the data register (no buffering - no FIFO). In write access, LINDAT will be
for data out and in read access, LINDAT will be for data in.
In UART mode the LINSEL register is unused.
17.5.16
OCD Support
This section describes the behavior of the LIN/UART controller stopped by the OCD (i.e. I/O
view behavior in AVR Studio)
1. LINCR:
- LINCR[6..0] are R/W accessible,
- LSWRES always is a self-reset bit (needs 1 micro-controller cycle to execute)
2. LINSIR:
- LIDST[2..0] and LBUSY are always Read accessible,
- LERR & LxxOK bit are directly accessible (unlike in execution, set or cleared directly
by writing 1 or 0).
- Note that clearing LERR resets all LINERR bits and setting LERR sets all LINERR
bits.
3. LINENR:
- All bits are R/W accessible.
4. LINERR:
- All bits are R/W accessible,
- Note that LINERR bits are ORed to provide the LERR interrupt flag of LINSIR.
5. LINBTR:
- LBT[5..0] are R/W access only if LDISR is set,
- If LDISR is reset, LBT[5..0] are unchangeable.
6. LINBRRH & LINBRRL:
- All bits are R/W accessible.
7. LINDLR:
- All bits are R/W accessible.
8. LINIDR:
- LID[5..0] are R/W accessible,
- LP[1..0] are Read accessible and are always updated on the fly.
9. LINSEL:
- All bits are R/W accessible.
10. LINDAT:
- All bits are in R/W accessible,
- Note that LAINC has no more effect on the auto-incrementation and the access to the
full FIFO is done setting LINDX[2..0] of LINSEL.
Note:
222
When a debugger break occurs, the state machine of the LIN/UART controller is stopped
(included frame time-out) and further communication may be corrupted.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.6
LIN / UART Register Description
Table 17-5.
LIN/UART Register Bits Summary
Name
Bit 7
LSWRES
LINCR
0
R/W
0
R
0
R
0
0
R
0
0
LINBRRL
LINBRRH
R/W
R
0
R/W
R
0
0
R
0
0
R/W
1
0
R
0
R
0
0
R/W
R
R/W
0
R/W
LID4/LDL0
0
0
R/W
R/W
—
R
0
R
0
0
0
R/W
0
R/W
R/W
0
R/W
R/W
0
R/W
R/W
0
R/W
R/(W)
0
R/W
0
0
R/W
0
R/W
0
R/W
0
R/W
LINDX0
R/W
0
LDATA1
0
R/W
LID0
LINDX1
0
R/W
LRXDL0
LID1
0
R/W
LDIV8
LRXDL1
0
R/(W)
LDIV0
R/W
0
R
LBT0
LDIV9
LDATA2
R/W
0
LDIV1
0
R/W
LBERR
R
0
LINDX2
LDATA3
0
LBT1
LID2
R/W
0
R/W
0
R/Wone
LENRXOK
LCERR
LRXDL2
LID3
0
R/W
0
LENTXOK
0
R/W
LRXOK
R/Wone
LDIV10
LRXDL3
0
R/(W)
0
LTXOK
0
LDIV2
LAINC
R
0
0
R/W
0
R
LCMD0
R/W
LBT2
R/(W)
0
LDATA4
R/W
0
LDIV3
—
LDATA5
R/W
R
0
R/W
Bit 0
LCMD1
0
LPERR
LDIV11
R
0
0
LBT3
0
R/Wone
LENIDOK
R/W
0
LTXDL0
R/W
0
LSERR
—
LID5/LDL1
LDATA6
0
R/(W)
0
R
0
0
R/W
LIDOK
R/Wone
LDIV4
LTXDL1
R/W
0
LDATA7
LINDAT
0
LP0
0
0
R/W
—
R
R
—
LTXDL2
—
LINSEL
R/(W)
0
LERR
LBT4
LDIV5
R/W
LP1
LINIDR
1
LDIV6
LTXDL3
LINDLR
0
0
LENERR
R
Bit 1
LCMD2
R/W
0
LFERR
R
—
R
0
LBT5
—
0
R
—
LOVERR
R
LDIV7
0
0
Bit 2
LENA
0
LBUSY
R
LDISR
LINBTR
R/W
—
LTOERR
0
0
LIDST0
R
Bit 3
LCONF0
R/W
—
LABORT
LINERR
0
LIDST1
0
Bit 4
LCONF1
R/W
—
LINENIR
Bit 5
LIN13
0
LIDST2
LINSIR
17.6.1
Bit 6
R/W
LDATA0
R/W
0
R/W
LIN Control Register - LINCR
Bit
7
6
5
4
3
2
1
0
LSWRES
LIN13
LCONF1
LCONF0
LENA
LCMD2
LCMD1
LCMD0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
LINCR
• Bit 7 - LSWRES: Software Reset
– 0 = No action,
– 1 = Software reset (this bit is self-reset at the end of the reset procedure).
• Bit 6 - LIN13: LIN 1.3 mode
– 0 = LIN 2.1 (default),
– 1 = LIN 1.3.
• Bit 5:4 - LCONF[1:0]: Configuration
a.
LIN mode (default = 00):
– 00 = LIN Standard configuration (listen mode “off”, CRC “on” & Frame_Time_Out
“on”,
223
7647F–AVR–04/09
– 01 = No CRC, no Time out (listen mode “off”),
– 10 = No Frame_Time_Out (listen mode “off” & CRC “on”),
– 11 = Listening mode (CRC “on” & Frame_Time_Out “on”).
b.
UART mode (default = 00):
– 00 = 8-bit, no parity (listen mode “off”),
– 01 = 8-bit, even parity (listen mode “off”),
– 10 = 8-bit, odd parity (listen mode “off”),
– 11 = Listening mode, 8-bit, no parity.
• Bit 3 - LENA: Enable
– 0 = Disable (both LIN and UART modes),
– 1 = Enable (both LIN and UART modes).
• Bit 2:0 - LCMD[2..0]: Command and mode
The command is only available if LENA is set.
–000 = LIN Rx Header - LIN abort,
– 001 = LIN Tx Header,
– 010 = LIN Rx Response,
– 011 = LIN Tx Response,
– 100 = UART Rx & Tx Byte disable,
– 11x = UART Rx Byte enable,
– 1x1 = UART Tx Byte enable.
17.6.2
LIN Status and Interrupt Register - LINSIR
Bit
7
6
5
4
3
2
1
0
LIDST2
LIDST1
LIDST0
LBUSY
LERR
LIDOK
LTXOK
LRXOK
Read/Write
R
R
R
R
R/Wone
R/Wone
R/Wone
R/Wone
Initial Value
0
0
0
0
0
0
0
0
LINSIR
• Bits 7:5 - LIDST[2:0]: Identifier Status
– 0xx = no specific identifier,
– 100 = Identifier 60 (0x3C),
– 101 = Identifier 61 (0x3D),
– 110 = Identifier 62 (0x3E),
– 111 = Identifier 63 (0x3F).
• Bit 4 - LBUSY: Busy Signal
– 0 = Not busy,
– 1 = Busy (receiving or transmitting).
224
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 3 - LERR: Error Interrupt
It is a logical OR of LINERR register bits. This bit generates an interrupt if its respective
enable bit - LENERR - is set in LINENIR.
– 0 = No error,
– 1 = An error has occurred.
The user clears this bit by writing 1 in order to reset this interrupt. Resetting LERR also
resets all LINERR bits.
In UART mode, this bit is also cleared by reading LINDAT.
• Bit 2 - LIDOK: Identifier Interrupt
This bit generates an interrupt if its respective enable bit - LENIDOK - is set in LINENIR.
– 0 = No identifier,
– 1 = Slave task: Identifier present, master task: Tx Header complete.
The user clears this bit by writing 1, in order to reset this interrupt.
• Bit 1 - LTXOK: Transmit Performed Interrupt
This bit generates an interrupt if its respective enable bit - LENTXOK - is set in LINENIR.
– 0 = No Tx,
– 1 = Tx Response complete.
The user clears this bit by writing 1, in order to reset this interrupt.
In UART mode, this bit is also cleared by writing LINDAT.
• Bit 0 - LRXOK: Receive Performed Interrupt
This bit generates an interrupt if its respective enable bit - LENRXOK - is set in LINENIR.
– 0 = No Rx
– 1 = Rx Response complete.
The user clears this bit by writing 1, in order to reset this interrupt.
In UART mode, this bit is also cleared by reading LINDAT.
17.6.3
LIN Enable Interrupt Register - LINENIR
Bit
7
6
5
4
3
2
1
0
-
-
-
-
LENERR
LENIDOK
LENTXOK
LENRXOK
Read/Write
R
R
R
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
LINENIR
• Bits 7:4 - Reserved Bits
These bits are reserved for future use. For compatibility with future devices, they must be
written to zero when LINENIR is written.
• Bit 3 - LENERR: Enable Error Interrupt
– 0 = Error interrupt masked,
– 1 = Error interrupt enabled.
225
7647F–AVR–04/09
• Bit 2 - LENIDOK: Enable Identifier Interrupt
– 0 = Identifier interrupt masked,
– 1 = Identifier interrupt enabled.
• Bit 1 - LENTXOK: Enable Transmit Performed Interrupt
– 0 = Transmit performed interrupt masked,
– 1 = Transmit performed interrupt enabled.
• Bit 0 - LENRXOK: Enable Receive Performed Interrupt
– 0 = Receive performed interrupt masked,
– 1 = Receive performed interrupt enabled.
17.6.4
LIN Error Register - LINERR
Bit
7
6
5
4
3
2
1
0
LABORT
LTOERR
LOVERR
LFERR
LSERR
LPERR
LCERR
LBERR
Read/Write
R
R
R
R
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
LINERR
• Bit 7 - LABORT: Abort Flag
– 0 = No warning,
– 1 = LIN abort command occurred.
This bit is cleared when LERR bit in LINSIR is cleared.
• Bit 6 - LTOERR: Frame_Time_Out Error Flag
– 0 = No error,
– 1 = Frame_Time_Out error.
This bit is cleared when LERR bit in LINSIR is cleared.
• Bit 5 - LOVERR: Overrun Error Flag
– 0 = No error,
– 1 = Overrun error.
This bit is cleared when LERR bit in LINSIR is cleared.
• Bit 4 - LFERR: Framing Error Flag
– 0 = No error,
– 1 = Framing error.
This bit is cleared when LERR bit in LINSIR is cleared.
• Bit 3 - LSERR: Synchronization Error Flag
– 0 = No error,
– 1 = Synchronization error.
This bit is cleared when LERR bit in LINSIR is cleared.
226
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 2 - LPERR: Parity Error Flag
– 0 = No error,
– 1 = Parity error.
This bit is cleared when LERR bit in LINSIR is cleared.
• Bit 1 - LCERR: Checksum Error Flag
– 0 = No error,
– 1 = Checksum error.
This bit is cleared when LERR bit in LINSIR is cleared.
• Bit 0 - LBERR: Bit Error Flag
– 0 = no error,
– 1 = Bit error.
This bit is cleared when LERR bit in LINSIR is cleared.
17.6.5
LIN Bit Timing Register - LINBTR
Bit
7
6
5
4
3
2
1
0
LDISR
-
LBT5
LBT4
LBT3
LBT2
LBT1
LBT0
Read/Write
R/W
R
R/(W)
R/(W)
R/(W)
R/(W)
R/(W)
R/(W)
Initial Value
0
0
1
0
0
0
0
0
LINBTR
• Bit 7 - LDISR: Disable Bit Timing Re synchronization
– 0 = Bit timing re-synchronization enabled (default),
– 1 = Bit timing re-synchronization disabled.
• Bits 5:0 - LBT[5:0]: LIN Bit Timing
Gives the number of samples of a bit.
sample-time = (1 / fclki/o ) x (LDIV[11..0] + 1)
Default value: LBT[6:0]=32 — Min. value: LBT[6:0]=8 — Max. value: LBT[6:0]=63
17.6.6
LIN Baud Rate Register - LINBRR
Bit
Bit
7
6
5
4
3
2
1
0
LDIV7
LDIV6
LDIV5
LDIV4
LDIV3
LDIV2
LDIV1
LDIV0
LINBRRL
-
-
-
-
LDIV11
LDIV10
LDIV9
LDIV8
LINBRRH
15
14
13
12
11
10
9
8
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
• Bits 15:12 - Reserved Bits
These bits are reserved for future use. For compatibility with future devices, they must be
written to zero when LINBRR is written.
• Bits 11:0 - LDIV[11:0]: Scaling of clki/o Frequency
The LDIV value is used to scale the entering clki/o frequency to achieve appropriate LIN or
UART baud rate.
227
7647F–AVR–04/09
17.6.7
LIN Data Length Register - LINDLR
Bit
7
6
5
4
3
2
1
0
LTXDL3
LTXDL2
LTXDL1
LTXDL0
LRXDL3
LRXDL2
LRXDL1
LRXDL0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
LINDLR
• Bits 7:4 - LTXDL[3:0]: LIN Transmit Data Length
In LIN mode, this field gives the number of bytes to be transmitted (clamped to 8 Max).
In UART mode this field is unused.
• Bits 3:0 - LRXDL[3:0]: LIN Receive Data Length
In LIN mode, this field gives the number of bytes to be received (clamped to 8 Max).
In UART mode this field is unused.
17.6.8
LIN Identifier Register - LINIDR
Bit
7
6
5
4
3
2
1
0
LP1
LP0
LID5 / LDL1
LID4 / LDL0
LID3
LID2
LID1
LID0
Read/Write
R
R
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
LINIDR
• Bits 7:6 - LP[1:0]: Parity
In LIN mode:
LP0 = LID4 ^ LID2 ^ LID1 ^ LID0
LP1 = ! ( LID1 ^ LID3 ^ LID4 ^ LID5 )
In UART mode this field is unused.
• Bits 5:4 - LDL[1:0]: LIN 1.3 Data Length
In LIN 1.3 mode:
– 00 = 2-byte response,
– 01 = 2-byte response,
– 10 = 4-byte response,
– 11 = 8-byte response.
In UART mode this field is unused.
• Bits 3:0 - LID[3:0]: LIN 1.3 Identifier
In LIN 1.3 mode: 4-bit identifier.
In UART mode this field is unused.
• Bits 5:0 - LID[5:0]: LIN 2.1 Identifier
In LIN 2.1 mode: 6-bit identifier (no length transported).
In UART mode this field is unused.
228
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
17.6.9
LIN Data Buffer Selection Register - LINSEL
Bit
7
6
5
4
3
2
1
0
-
-
Read/Write
-
-
-
-
LAINC
LINDX2
LINDX1
LINDX0
-
-
R/W
R/W
R/W
R/W
Initial Value
-
-
-
-
0
0
0
0
LINSEL
• Bits 7:4 - Reserved Bits
These bits are reserved for future use. For compatibility with future devices, they must be
written to zero when LINSEL is written.
• Bit 3 - LAINC: Auto Increment of Data Buffer Index
In LIN mode:
– 0 = Auto incrementation of FIFO data buffer index (default),
– 1 = No auto incrementation.
In UART mode this field is unused.
• Bits 2:0 - LINDX 2:0: FIFO LIN Data Buffer Index
In LIN mode: location (index) of the LIN response data byte into the FIFO data buffer. The
FIFO data buffer is accessed through LINDAT.
In UART mode this field is unused.
17.6.10
LIN Data Register - LINDAT
Bit
7
6
5
4
3
2
1
0
LDATA7
LDATA6
LDATA5
LDATA4
LDATA3
LDATA2
LDATA1
LDATA0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
LINDAT
• Bits 7:0 - LDATA[7:0]: LIN Data In / Data out
In LIN mode: FIFO data buffer port.
In UART mode: data register (no data buffer - no FIFO).
– In Write access, data out.
– In Read access, data in.
229
7647F–AVR–04/09
18. Analog to Digital Converter - ADC
18.1
Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
10-bit Resolution
0.8 LSB Integral Non-linearity (at 2 Mhz)
±3.2 LSB Absolute Accuracy
8- 250 µs Conversion Time
Up to 125 kSPS at Maximum Resolution
11 Multiplexed Single Ended Input Channels
3 Differential input channels with programmable gain 5, 10, 20 and 40
Optional Left Adjustment for ADC Result Readout
0 - VCC ADC Input Voltage Range
Selectable 2.56 V ADC Reference Voltage
Free Running or Single Conversion Mode
ADC Start Conversion by Auto Triggering on Interrupt Sources
Interrupt on ADC Conversion Complete
Sleep Mode Noise Canceler
Temperature Sensor
LiN Address Sense (ISRC Voltage Measurement)
Vcc Voltage Measurement
The ATmega16/32/64/M1/C1 features a 10-bit successive approximation ADC. The ADC is connected to an 15-channel Analog Multiplexer which allows eleven single-ended input. The
single-ended voltage inputs refer to 0V (GND).
The device also supports 3 differential voltage input amplifiers which are equipped with a programmable gain stage, providing amplification steps of 14dB (5x), 20 dB (10x), 26 dB (20x), or
32dB (40x) on the differential input voltage before the A/D conversion. On the amplified channels, 8-bit resolution can be expected.
The ADC contains a Sample and Hold circuit which ensures that the input voltage to the ADC is
held at a constant level during conversion. A block diagram of the ADC is shown in Figure 18-1.
The ADC has a separate analog supply voltage pin, AVCC. AVCC must not differ more than ±0.3V
from VCC. See the paragraph “ADC Noise Canceler” on page 237 on how to connect this pin.
Internal reference voltages of nominally 2.56V or AVCC are provided On-chip. The voltage reference may be externally decoupled at the AREF pin by a capacitor for better noise performance.
230
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 18-1. Analog to Digital Converter Block Schematic
Current
Source
ISRCEN
AREF / ISRC
ISRC
AREFEN
AVCC
Internal 2.56V
Reference
REFS0
ADC0
ADC1
ADC2
ADC3
ADC4
ADC5
AMP2-/ADC6
ADC7
AMP1-/ADC8
AMP1+/ADC9
ADC10
AMP0AMP0+
REFS1
Coarse/Fine DAC
10
+
+
REFS1
CONTROL
AMP0CSR
REFS0
ADLAR
MUX4
Sources
-
ADCL
ADC CONVERSION
COMPLETE IRQ
MUX3
MUX2
MUX1
MUX0
ADASCR
ADEN
ADSC
ADATE
ADIF
ADIE
ADPS2
ADPS1
ADPS0
ADCSRA
Edge
Detector
-
PRESCALER
AMP1CSR
ADMUX
-
10
CKADC CKADC
CK
AMP2CSR
ADCH
+
+
AMP2+
GND
Bandgap
Temp Sensor
VCC/4
ISRC
10
SAR
ADTS3
ADATE
ADTS2
ADTS1
ADTS0
ADCSRB
231
7647F–AVR–04/09
18.2
Operation
The ADC converts an analog input voltage to a 10-bit digital value through successive approximation. The minimum value represents GND and the maximum value represents the voltage on
the AREF pin minus 1 LSB. Optionally, AVCC or an internal 2.56V reference voltage may be connected to the AREF pin by writing to the REFSn bits in the ADMUX Register. The internal
voltage reference may thus be decoupled by an external capacitor at the AREF pin to improve
noise immunity.
The analog input channel are selected by writing to the MUX bits in ADMUX. Any of the ADC
input pins, as well as GND and a fixed bandgap voltage reference, can be selected as single
ended inputs to the ADC.
The ADC is enabled by setting the ADC Enable bit, ADEN in ADCSRA. Voltage reference is set
by the REFS1 and REFS0 bits in ADMUX register, whatever the ADC is enabled or not. The
ADC does not consume power when ADEN is cleared, so it is recommended to switch off the
ADC before entering power saving sleep modes.
The ADC generates a 10-bit result which is presented in the ADC Data Registers, ADCH and
ADCL. By default, the result is presented right adjusted, but can optionally be presented left
adjusted by setting the ADLAR bit in ADMUX.
If the result is left adjusted and no more than 8-bit precision is required, it is sufficient to read
ADCH. Otherwise, ADCL must be read first, then ADCH, to ensure that the content of the Data
Registers belongs to the same conversion. Once ADCL is read, ADC access to Data Registers
is blocked. This means that if ADCL has been read, and a conversion completed before ADCH
is read, neither register is updated and the result from the conversion is lost. When ADCH is
read, ADC access to the ADCH and ADCL Registers is re-enabled.
The ADC has its own interrupt which can be triggered when a conversion completes. The ADC
access to the Data Registers is prohibited between reading of ADCH and ADCL, the interrupt
will trigger even if the result is lost.
18.3
Starting a Conversion
A single conversion is started by writing a logical one to the ADC Start Conversion bit, ADSC.
This bit stays high as long as the conversion is in progress and will be cleared by hardware
when the conversion is completed. If a different data channel is selected while a conversion is in
progress, the ADC will finish the current conversion before performing the channel change.
Alternatively, a conversion can be triggered automatically by various sources. Auto Triggering is
enabled by setting the ADC Auto Trigger Enable bit, ADATE in ADCSRA. The trigger source is
selected by setting the ADC Trigger Select bits, ADTS in ADCSRB (See description of the ADTS
bits for a list of the trigger sources). When a positive edge occurs on the selected trigger signal,
the ADC prescaler is reset and a conversion is started. This provides a method of starting conversions at fixed intervals. If the trigger signal is still set when the conversion completes, a new
conversion will not be started. If another positive edge occurs on the trigger signal during conversion, the edge will be ignored. Note that an interrupt flag will be set even if the specific
interrupt is disabled or the Global Interrupt Enable bit in SREG is cleared. A conversion can thus
be triggered without causing an interrupt. However, the interrupt flag must be cleared in order to
trigger a new conversion at the next interrupt event.
232
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 18-2. ADC Auto Trigger Logic
ADTS[2:0]
PRESCALER
START
CLKADC
ADATE
ADIF
SOURCE 1
.
.
.
.
CONVERSION
LOGIC
EDGE
DETECTOR
SOURCE n
ADSC
Using the ADC Interrupt Flag as a trigger source makes the ADC start a new conversion as soon
as the ongoing conversion has finished. The ADC then operates in Free Running mode, constantly sampling and updating the ADC Data Register. The first conversion must be started by
writing a logical one to the ADSC bit in ADCSRA. In this mode the ADC will perform successive
conversions independently of whether the ADC Interrupt Flag, ADIF is cleared or not. The free
running mode is not allowed on the amplified channels.
If Auto Triggering is enabled, single conversions can be started by writing ADSC in ADCSRA to
one. ADSC can also be used to determine if a conversion is in progress. The ADSC bit will be
read as one during a conversion, independently of how the conversion was started.
18.4
Prescaling and Conversion Timing
Figure 18-3. ADC Prescaler
ADEN
START
Reset
7-BIT ADC PRESCALER
CK/64
CK/128
CK/32
CK/8
CK/16
CK/4
CK/2
CK
ADPS0
ADPS1
ADPS2
ADC CLOCK SOURCE
By default, the successive approximation circuitry requires an input clock frequency between 50
kHz and 2 MHz to get maximum resolution. If a lower resolution than 10 bits is needed, the input
clock frequency to the ADC can be higher than 2 MHz to get a higher sample rate.
The ADC module contains a prescaler, which generates an acceptable ADC clock frequency
from any CPU frequency above 100 kHz. The prescaling is set by the ADPS bits in ADCSRA.
The prescaler starts counting from the moment the ADC is switched on by setting the ADEN bit
in ADCSRA. The prescaler keeps running for as long as the ADEN bit is set, and is continuously
reset when ADEN is low.
233
7647F–AVR–04/09
When initiating a single ended conversion by setting the ADSC bit in ADCSRA, the conversion
starts at the following rising edge of the ADC clock cycle. See “Changing Channel or Reference
Selection” on page 235 for details on differential conversion timing.
A normal conversion takes 15.5 ADC clock cycles. The first conversion after the ADC is
switched on (ADEN in ADCSRA is set) takes 25 ADC clock cycles in order to initialize the analog
circuitry.
The actual sample-and-hold takes place 3.5 ADC clock cycles after the start of a normal conversion and 13.5 ADC clock cycles after the start of an first conversion. When a conversion is
complete, the result is written to the ADC Data Registers, and ADIF is set. In Single Conversion
mode, ADSC is cleared simultaneously. The software may then set ADSC again, and a new
conversion will be initiated on the first rising ADC clock edge.
When Auto Triggering is used, the prescaler is reset when the trigger event occurs. This assures
a fixed delay from the trigger event to the start of conversion. In this mode, the sample-and-hold
takes place two ADC clock cycles after the rising edge on the trigger source signal. Three additional CPU clock cycles are used for synchronization logic.
In Free Running mode, a new conversion will be started immediately after the conversion completes, while ADSC remains high. For a summary of conversion times, see Table 18-1.
Figure 18-4. ADC Timing Diagram, First Conversion (Single Conversion Mode)
Next
Conversion
First Conversion
Cycle Number
1
2
12
13
14
15
16
22
23
24
25
27
26
28
1
2
3
ADC Clock
ADEN
ADSC
ADIF
Sign and MSB of Result
ADCH
LSB of Result
ADCL
MUX and REFS
Update
MUX
and REFS
Update
Conversion
Complete
Sample & Hold
Figure 18-5. ADC Timing Diagram, Single Conversion
One Conversion
Cycle Number
1
2
3
4
5
6
7
8
10
Next Conversion
11
12
13
14
1
2
3
ADC Clock
ADSC
ADIF
ADCH
Sign and MSB of Result
ADCL
LSB of Result
Sample & Hold
MUX and REFS
Update
234
Conversion
Complete
MUX and REFS
Update
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 18-6. ADC Timing Diagram, Auto Triggered Conversion
One Conversion
Cycle Number
1
2
3
4
5
6
7
Next Conversion
8
11
12
13
14
1
2
ADC Clock
Trigger
Source
ADATE
ADIF
ADCH
Sign and MSB of Result
ADCL
LSB of Result
Prescaler
Reset
Sample &
Hold
Prescaler
Reset
Conversion
Complete
MUX and REFS
Update
Figure 18-7. ADC Timing Diagram, Free Running Conversion
One Conversion
Cycle Number
12
13
Next Conversion
14
1
2
3
4
5
ADC Clock
ADSC
ADIF
ADCH
Sign and MSB of Result
ADCL
LSB of Result
Sample & Hold
Conversion
Complete
Table 18-1.
ADC Conversion Time
Condition
Sample & Hold
(Cycles from Start of Conversion)
Conversion Time
(Cycles)
18.5
MUX and REFS
Update
First Conversion
Normal
Conversion,
Single Ended
Auto Triggered
Conversion
13.5
3.5
2
25
15.5
16
Changing Channel or Reference Selection
The MUXn and REFS1:0 bits in the ADMUX Register are single buffered through a temporary
register to which the CPU has random access. This ensures that the channels and reference
selection only takes place at a safe point during the conversion. The channel and reference
selection is continuously updated until a conversion is started. Once the conversion starts, the
channel and reference selection is locked to ensure a sufficient sampling time for the ADC. Continuous updating resumes in the last eight ADC clock cycle before the conversion completes
(ADIF in ADCSRA is set). Note that the conversion starts on the second following rising CPU
clock edge after ADSC is written. The user is thus advised not to write new channel or reference
selection values to ADMUX until two ADC clock cycle after ADSC is written.
235
7647F–AVR–04/09
If Auto Triggering is used, the exact time of the triggering event can be indeterministic. Special
care must be taken when updating the ADMUX Register, in order to control which conversion
will be affected by the new settings.
If both ADATE and ADEN is written to one, an interrupt event can occur at any time. If the
ADMUX Register is changed in this period, the user cannot tell if the next conversion is based
on the old or the new settings. ADMUX can be safely updated in the following ways:
1. When ADATE or ADEN is cleared.
2. During conversion, with taking care of the trigger source event, when it is possible.
3. After a conversion, before the interrupt flag used as trigger source is cleared.
When updating ADMUX in one of these conditions, the new settings will affect the next ADC
conversion.
18.5.1
ADC Input Channels
When changing channel selections, the user should observe the following guidelines to ensure
that the correct channel is selected:
• In Single Conversion mode, always select the channel before starting the conversion. The
channel selection may be changed one ADC clock cycle after writing one to ADSC. However,
the simplest method is to wait for the conversion to complete before changing the channel
selection.
• In Free Running mode, always select the channel before starting the first conversion. The
channel selection may be changed one ADC clock cycle after writing one to ADSC. However,
the simplest method is to wait for the first conversion to complete, and then change the
channel selection. Since the next conversion has already started automatically, the next
result will reflect the previous channel selection. Subsequent conversions will reflect the new
channel selection.
• In Free Running mode, because the amplifier clear the ADSC bit at the end of an amplified
conversion, it is not possible to use the free running mode, unless ADSC bit is set again by
soft at the end of each conversion.
Note:
18.5.2
When The ADC and COMPARATOR share the same channel (Possible configuration for AMP1+,
AMP1- and AMP2-), up to revision B of ATmega32M1 the comparator is disconnected during the
sampling of the ADC. For ATmega16/64 and ATmega32 revision C, the COMPARATOR is always
connected.
ADC Voltage Reference
The reference voltage for the ADC (VREF) indicates the conversion range for the ADC. Single
ended channels that exceed VREF will result in codes close to 0x3FF. VREF can be selected as
either AVCC, internal 2.56V reference, or external AREF pin.
AVCC is connected to the ADC through a passive switch. The internal 2.56V reference is generated from the internal bandgap reference (VBG) through an internal amplifier. In either case, the
external AREF pin is directly connected to the ADC, and the reference voltage can be made
more immune to noise by connecting a capacitor between the AREF pin and ground. VREF can
also be measured at the AREF pin with a high impedant voltmeter. Note that VREF is a high
impedant source, and only a capacitive load should be connected in a system.
236
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
If the user has a fixed voltage source connected to the AREF pin, the user may not use the other
reference voltage options in the application, as they will be shorted to the external voltage. If no
external voltage is applied to the AREF pin, the user may switch between AVCC and 2.56V as
reference selection. The first ADC conversion result after switching reference voltage source
may be inaccurate, and the user is advised to discard this result.
AREF pin is alternate function with ISRC Current Source output. When current source is
selected, the AREF pin is not connected to the internal reference voltage network. See AREFEN
and ISRCEN bits in Section “ADC Control and Status Register B– ADCSRB”, page 247.
If differential channels are used, the selected reference should not be closer to AVCC than indicated in Table 26-5 on page 322.
18.6
ADC Noise Canceler
The ADC features a noise canceler that enables conversion during sleep mode to reduce noise
induced from the CPU core and other I/O peripherals. The noise canceler can be used with ADC
Noise Reduction and Idle mode. To make use of this feature, the following procedure should be
used:
a. Make sure the ADATE bit is reset.
b.
Make sure that the ADC is enabled and is not busy converting. Single Conversion
mode must be selected and the ADC conversion complete interrupt must be
enabled.
c.
Enter ADC Noise Reduction mode (or Idle mode). The ADC will start a conversion
once the CPU has been halted.
d. If no other interrupts occur before the ADC conversion completes, the ADC interrupt will wake up the CPU and execute the ADC Conversion Complete interrupt
routine. If another interrupt wakes up the CPU before the ADC conversion is complete, that interrupt will be executed, and an ADC Conversion Complete interrupt
request will be generated when the ADC conversion completes. The CPU will
remain in active mode until a new sleep command is executed.
Note that the ADC will not be automatically turned off when entering other sleep modes than Idle
mode and ADC Noise Reduction mode. The user is advised to write zero to ADEN before entering such sleep modes to avoid excessive power consumption.
If the ADC is enabled in such sleep modes and the user wants to perform differential conversions, the user is advised to switch the ADC off and on after waking up from sleep to prompt an
extended conversion to get a valid result.
18.6.1
Analog Input Circuitry
The analog input circuitry for single ended channels is illustrated in Figure 18-8. An analog
source applied to ADCn is subjected to the pin capacitance and input leakage of that pin, regardless of whether that channel is selected as input for the ADC. When the channel is selected, the
source must drive the S/H capacitor through the series resistance (combined resistance in the
input path).
The ADC is optimized for analog signals with an output impedance of approximately 10 kΩ or
less. If such a source is used, the sampling time will be negligible. If a source with higher impedance is used, the sampling time will depend on how long time the source needs to charge the
S/H capacitor, with can vary widely. The user is recommended to only use low impedant sources
with slowly varying signals, since this minimizes the required charge transfer to the S/H
capacitor.
237
7647F–AVR–04/09
If differential gain channels are used, the input circuitry looks somewhat different, although
source impedances of a few hundred kΩ or less is recommended.
Signal components higher than the Nyquist frequency (fADC/2) should not be present for either
kind of channels, to avoid distortion from unpredictable signal convolution. The user is advised
to remove high frequency components with a low-pass filter before applying the signals as
inputs to the ADC.
Figure 18-8. Analog Input Circuitry
IIH
ADCn
1..100 kΩ
CS/H= 14 pF
IIL
VCC/2
18.6.2
Analog Noise Canceling Techniques
Digital circuitry inside and outside the device generates EMI which might affect the accuracy of
analog measurements. If conversion accuracy is critical, the noise level can be reduced by
applying the following techniques:
1. Keep analog signal paths as short as possible. Make sure analog tracks run over the
analog ground plane, and keep them well away from high-speed switching digital
tracks.
2. The AVCC pin on the device should be connected to the digital VCC supply voltage via
an RC network (R = 10Ω max, C = 100 nF).
3. Use the ADC noise canceler function to reduce induced noise from the CPU.
4. If any ADC port pins (PB[7:2], PC[7:4], PD[6:4], PE[2]) are used as digital outputs, it is
essential that these do not switch while a conversion is in progress.
18.6.3
Offset Compensation Schemes
The gain stage has a built-in offset cancellation circuitry that nulls the offset of differential measurements as much as possible. The remaining offset in the analog path can be measured
directly by shortening both differential inputs using the AMPxIS bit with both inputs unconnected.
(See “Amplifier 0 Control and Status register – AMP0CSR” on page 254., See “Amplifier 1 Control and Status register – AMP1CSR” on page 255.and See “Amplifier 1 Control and Status
register – AMP1CSR” on page 255.). This offset residue can be then subtracted in software from
the measurement results. Using this kind of software based offset correction, offset on any channel can be reduced below one LSB.
18.6.4
ADC Accuracy Definitions
An n-bit single-ended ADC converts a voltage linearly between GND and V REF in 2 n steps
(LSBs). The lowest code is read as 0, and the highest code is read as 2n-1.
Several parameters describe the deviation from the ideal behavior:
• Offset: The deviation of the first transition (0x000 to 0x001) compared to the ideal transition
(at 0.5 LSB). Ideal value: 0 LSB.
238
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 18-9. Offset Error
Output Code
Ideal ADC
Actual ADC
Offset
Error
VREF Input Voltage
• Gain Error: After adjusting for offset, the Gain Error is found as the deviation of the last
transition (0x3FE to 0x3FF) compared to the ideal transition (at 1.5 LSB below maximum).
Ideal value: 0 LSB
Figure 18-10. Gain Error
Output Code
Gain
Error
Ideal ADC
Actual ADC
VREF Input Voltage
• Integral Non-linearity (INL): After adjusting for offset and gain error, the INL is the maximum
deviation of an actual transition compared to an ideal transition for any code. Ideal value: 0
LSB.
239
7647F–AVR–04/09
Figure 18-11. Integral Non-linearity (INL)
Output Code
INL
Ideal ADC
Actual ADC
VREF
Input Voltage
• Differential Non-linearity (DNL): The maximum deviation of the actual code width (the interval
between two adjacent transitions) from the ideal code width (1 LSB). Ideal value: 0 LSB.
Figure 18-12. Differential Non-linearity (DNL)
Output Code
0x3FF
1 LSB
DNL
0x000
0
VREF Input Voltage
• Quantization Error: Due to the quantization of the input voltage into a finite number of codes,
a range of input voltages (1 LSB wide) will code to the same value. Always ± 0.5 LSB.
• Absolute Accuracy: The maximum deviation of an actual (unadjusted) transition compared to
an ideal transition for any code. This is the compound effect of offset, gain error, differential
error, non-linearity, and quantization error. Ideal value: ± 0.5 LSB.
240
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
18.7
ADC Conversion Result
After the conversion is complete (ADIF is high), the conversion result can be found in the ADC
Result Registers (ADCL, ADCH).
For single ended conversion, the result is:
V IN ⋅ 1023
ADC = ---------------------------V REF
where VIN is the voltage on the selected input pin and VREF the selected voltage reference (see
Table 18-4 on page 245 and Table 18-5 on page 246). 0x000 represents analog ground, and
0x3FF represents the selected reference voltage.
If differential channels are used, the result is:
( V POS – V NEG ) ⋅ GAIN ⋅ 512
ADC = ----------------------------------------------------------------------------V REF
where VPOS is the voltage on the positive input pin, VNEG the voltage on the negative input pin,
GAIN the selected gain factor and VREF the selected voltage reference. The result is presented
in two’s complement form, from 0x200 (-512d) through 0x1FF (+511d). Note that if the user
wants to perform a quick polarity check of the result, it is sufficient to read the MSB of the result
(ADC9 in ADCH). If the bit is one, the result is negative, and if this bit is zero, the result is positive. Figure 18-13 shows the decoding of the differential input range.
Table 82 shows the resulting output codes if the differential input channel pair (ADCn - ADCm) is
selected with a reference voltage of VREF.
241
7647F–AVR–04/09
Figure 18-13. Differential Measurement Range
Output Code
0x1FF
0x000
- VREF /Gain
0x3FF
0
VREF/Gain Differential Input
Voltage (Volts)
0x200
Table 18-2.
Correlation Between Input Voltage and Output Codes
VADCn
Corresponding decimal value
VADCm + VREF /GAIN
0x1FF
511
VADCm + 0.999 VREF /GAIN
0x1FF
511
VADCm + 0.998 VREF /GAIN
0x1FE
510
...
...
...
VADCm + 0.001 VREF /GAIN
0x001
1
VADCm
0x000
0
VADCm - 0.001 VREF /GAIN
0x3FF
-1
...
...
...
242
Read code
VADCm - 0.999 VREF /GAIN
0x201
-511
VADCm - VREF /GAIN
0x200
-512
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Example 1:
ADMUX = 0xED (ADC3 - ADC2, 10x gain, 2.56V reference, left adjusted result)
– Voltage on ADC3 is 300 mV, voltage on ADC2 is 500 mV.
– ADCR = 512 * 10 * (300 - 500) / 2560 = -400 = 0x270
– ADCL will thus read 0x00, and ADCH will read 0x9C.
Writing zero to ADLAR right adjusts the result: ADCL = 0x70, ADCH = 0x02.
Example 2:
– ADMUX = 0xFB (ADC3 - ADC2, 1x gain, 2.56V reference, left adjusted result)
– Voltage on ADC3 is 300 mV, voltage on ADC2 is 500 mV.
– ADCR = 512 * 1 * (300 - 500) / 2560 = -41 = 0x029.
– ADCL will thus read 0x40, and ADCH will read 0x0A.
Writing zero to ADLAR right adjusts the result: ADCL = 0x00, ADCH = 0x29.
18.8
Temperature Measurement
The temperature measurement is based on an on-chip temperature sensor that is coupled to a
single ended ADC input. MUX[4..0] bits in ADMUX register enables the temperature sensor. The
internal 2.56V voltage reference must also be selected for the ADC voltage reference source in
the temperature sensor measurement. When the temperature sensor is enabled, the ADC converter can be used in single conversion mode to measure the voltage over the temperature
sensor.
As shown Figure 18-14, the temperature sensor is followed by a driver. This driver is enabled
when ADMUX value selects the temperature sensor as ADC input See “ADC Input Channel
Selection” on page 246. The propagation delay of this driver is approximatively 2µS. Therefore
two successive conversions are required. The correct temperature measurement will be the second one.
One can also reduce this timing to one conversion by setting the ADMUX during the previous
conversion. Indeed the ADMUX can be programmed to select the temperature sensor just after
the beginning of the previous conversion start event and then the driver will be enabled 2 µS
before sampling and hold phase of temperature sensor measurement. See “Changing Channel
or Reference Selection” on page 235.
Figure 18-14. Temperature Sensor Block Diagram
ADC
Input
Multiplexer
to sampling
and hold
Temperature
Sensor
G=1
Enable when
ADMUX = Temp. Sensor input
ADMUX
243
7647F–AVR–04/09
The measured voltage has a linear relationship to the temperature as described in Table 18-3 on
page 244. The voltage sensitivity is approximately 2.5 mV/° C and the accuracy of the temperature measurement is +/- 10°C after bandgap calibration.
Table 18-3.
Temperature vs. Sensor Output Voltage (Typical Case)
Temperature / °C
-40°C
+25°C
+125°C
Voltage / mV
600 mV
762 mv
1012 mV
The values described in Table 18-3 on page 244 are typical values. However, due to the process
variation the temperature sensor output voltage varies from one chip to another. To be capable
of achieving more accurate results, the temperature measurement can be calibrated in the application software.
18.8.1
User Calibration
The software calibration requires that a calibration value is measured and stored in a register or
EEPROM for each chip. The software calibration can be done utilizing the formula:
T = { [ (ADCH << 8) | ADCL ] - TOS } / k
where ADCH & ADCL are the ADC data registers, k is a fixed coefficient and TOS is the temperature sensor offset value determined and stored into EEPROM.
18.8.2
Manufacturing Calibration
One can also use the calibration values available in the signature row See “Reading the Signature Row from Software” on page 289.
The calibration values are determined from values measured during test at room temperature
which is approximatively +25°C and during test at hot temperature which is approximatively
+125°C. Calibration measures are done at V CC = 3V and with ADC in internal Vref (2.56V)
mode.
There are two algorithms for determining the Centigrade Temperature
formula 1 for ATmega32 up to rev B
formula 2 for ATmega16/64 and ATmega32 rev C.
formula 1: Temp_C = (((ADC_ts - 273)* TS_Gain) / 128) + TS_Offset [Applicable to devices with
0xFF or 0x42 ('B') in the signature memory at address 0x003F]
formula 2: Temp_C = ((((ADC_ts -(298 - TS_Offset)) * TS_Gain) / 128) + 25 [Applicable to
devices with 0x43 ('C') in the signature memory at address 0x003F]
Where :
Temp_C is the result temperature in degrees centigrade.
ADC_ts is the 10 bit result the ADC returns from reading the temperature sensor.
TS_Gain is the unsigned fixed point 8-bit temperature sensor gain factor in 1/128th units stored
as previously in the signature row at address 0x0007.
TS_Offset is the signed twos complement 7-bit temperature sensor offset reading stored as previously in the signature row at address 0x0005.
244
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
A new parameter has also been stored into the signature row at address (0x003A[Low Byte] 0x003B [High Byte]) which is the 10-bit ADC reading of the temperature sensor during Hot testing (+155C in Grade0 or +130C in Grade1).
See section 27.7.10 in the ATmega32M1 Automotive datasheet for details of reading the Signature Row.
18.9
ADC Register Description
The ADC of the ATmega16/32/64/M1/C1 is controlled through 3 different registers. The ADCSRA and The ADCSRB registers which are the ADC Control and Status registers, and the
ADMUX which allows to select the Vref source and the channel to be converted.
The conversion result is stored on ADCH and ADCL register which contain respectively the most
significant bits and the less significant bits.
18.9.1
ADC Multiplexer Register – ADMUX
Bit
7
6
5
4
3
2
1
0
REFS1
REFS0
ADLAR
MUX4
MUX3
MUX2
MUX1
MUX0
Read/Write
R/W
R/W
R/W
-
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
ADMUX
• Bit 7, 6 – REFS1, 0: ADC Vref Selection Bits
These 2 bits determine the voltage reference for the ADC.
The different setting are shown in Table 18-4.
Table 18-4.
ADC Voltage Reference Selection
AREFEN
ISRCEN
REFS1
REFS0
Description
1
0
0
0
External Vref on AREF pin, Internal Vref is switched off
1
0
0
1
AVcc with external capacitor connected on the AREF pin
0
0
0
1
AVcc (no external capacitor connected on the AREF pin)
1
0
1
0
Reserved
1
0
1
1
Internal 2.56V Reference voltage with external capacitor
connected on the AREF pin
0
x
1
1
Internal 2.56V Reference voltage
If bits REFS1 and REFS0 are changed during a conversion, the change will not take effect until
this conversion is complete (it means while the ADIF bit in ADCSRA register is set).
In case the internal Vref is selected, it is turned ON as soon as an analog feature needed it is
set.
• Bit 5 – ADLAR: ADC Left Adjust Result
Set this bit to left adjust the ADC result.
Clear it to right adjust the ADC result.
The ADLAR bit affects the configuration of the ADC result data registers. Changing this bit
affects the ADC data registers immediately regardless of any on going conversion. For a complete description of this bit, see Section “ADC Result Data Registers – ADCH and ADCL”,
page 249.
245
7647F–AVR–04/09
• Bit 4, 2, 1, 0 – MUX4, MUX3, MUX2, MUX1, MUX0: ADC Channel Selection Bits
These 4 bits determine which analog inputs are connected to the ADC input. The different setting are shown in Table 18-5.
Table 18-5.
ADC Input Channel Selection
MUX4
MUX3
MUX2
MUX1
MUX0
Description
0
0
0
0
0
ADC0
0
0
0
0
1
ADC1
0
0
0
1
0
ADC2
0
0
0
1
1
ADC3
0
0
1
0
0
ADC4
0
0
1
0
1
ADC5
0
0
1
1
0
ADC6
0
0
1
1
1
ADC7
0
1
0
0
0
ADC8
0
1
0
0
1
ADC9
0
1
0
1
0
ADC10
0
1
0
1
1
Temp Sensor
0
1
1
0
0
VCC/4
0
1
1
0
1
ISRC
0
1
1
1
0
AMP0
0
1
1
1
1
AMP1 (- is ADC8, + is ADC9)
1
0
0
0
0
AMP2 (- is ADC6)
1
0
0
0
1
Bandgap
1
0
0
1
0
GND
1
0
0
1
1
Reserved
1
0
1
x
x
Reserved
1
1
x
x
x
Reserved
If these bits are changed during a conversion, the change will not take effect until this conversion
is complete (it means while the ADIF bit in ADCSRA register is set).
18.9.2
ADC Control and Status Register A – ADCSRA
Bit
7
6
5
4
3
2
1
0
ADEN
ADSC
ADATE
ADIF
ADIE
ADPS2
ADPS1
ADPS0
Read/Write
R/W
R/W
R/W
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
ADCSRA
• Bit 7 – ADEN: ADC Enable Bit
Set this bit to enable the ADC.
Clear this bit to disable the ADC.
Clearing this bit while a conversion is running will take effect at the end of the conversion.
246
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 6– ADSC: ADC Start Conversion Bit
Set this bit to start a conversion in single conversion mode or to start the first conversion in free
running mode.
Cleared by hardware when the conversion is complete. Writing this bit to zero has no effect.
The first conversion performs the initialization of the ADC.
• Bit 5 – ADATE: ADC Auto trigger Enable Bit
Set this bit to enable the auto triggering mode of the ADC.
Clear it to return in single conversion mode.
In auto trigger mode the trigger source is selected by the ADTS bits in the ADCSRB register.
See Table 18-7 on page 248.
• Bit 4– ADIF: ADC Interrupt Flag
Set by hardware as soon as a conversion is complete and the Data register are updated with the
conversion result.
Cleared by hardware when executing the corresponding interrupt handling vector.
Alternatively, ADIF can be cleared by writing it to logical one.
• Bit 3– ADIE: ADC Interrupt Enable Bit
Set this bit to activate the ADC end of conversion interrupt.
Clear it to disable the ADC end of conversion interrupt.
• Bit 2, 1, 0– ADPS2, ADPS1, ADPS0: ADC Prescaler Selection Bits
These 3 bits determine the division factor between the system clock frequency and input clock of
the ADC.
The different setting are shown in Table 18-6.
Table 18-6.
18.9.3
ADC Prescaler Selection
ADPS2
ADPS1
ADPS0
Division Factor
0
0
0
2
0
0
1
2
0
1
0
4
0
1
1
8
1
0
0
16
1
0
1
32
1
1
0
64
1
1
1
128
ADC Control and Status Register B– ADCSRB
Bit
7
6
5
4
3
2
1
0
ADHSM
ISRCEN
AREFEN
-
ADTS3
ADTS2
ADTS1
ADTS0
Read/Write
R/W
R/W
R/W
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
ADCSRB
• Bit 7 – ADHSM: ADC High Speed Mode
Writing this bit to one enables the ADC High Speed mode. Set this bit if you wish to convert with
an ADC clock frequency higher than 200KHz.
Clear this bit to reduce the power consumption of the ADC when the ADC clock frequency is
lower than 200KHz.
247
7647F–AVR–04/09
• Bit 6 – ISRCEN: Current Source Enable
Set this bit to source a 100µA current to the AREF pin.
Clear this bit to use AREF pin as Analog Reference pin.
• Bit 5 – AREFEN: Analog Reference pin Enable
Set this bit to connect the internal AREF circuit to the AREF pin.
Clear this bit to disconnect the internal AREF circuit from the AREF pin.
• Bit 4 – Res: Reserved Bit
This bit is unused bit in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 3, 2, 1, 0– ADTS3:ADTS0: ADC Auto Trigger Source Selection Bits
These bits are only necessary in case the ADC works in auto trigger mode. It means if ADATE
bit in ADCSRA register is set.
In accordance with the Table 18-7, these 3 bits select the interrupt event which will generate the
trigger of the start of conversion. The start of conversion will be generated by the rising edge of
the selected interrupt flag whether the interrupt is enabled or not. In case of trig on PSCnASY
event, there is no flag. So in this case a conversion will start each time the trig event appears
and the previous conversion is completed..
Table 18-7.
248
ADC Auto Trigger Source Selection
ADTS3
ADTS2
ADTS1
ADTS0
Description
0
0
0
0
Free Running Mode
0
0
0
1
External Interrupt Request 0
0
0
1
0
Timer/Counter0 Compare Match
0
0
1
1
Timer/Counter0 Overflow
0
1
0
0
Timer/Counter1 Compare Match B
0
1
0
1
Timer/Counter1 Overflow
0
1
1
0
Timer/Counter1 Capture Event
0
1
1
1
PSC Module 0 Synchronization Signal
1
0
0
0
PSC Module 1 Synchronization Signal
1
0
0
1
PSC Module 2 Synchronization Signal
1
0
1
0
Analog comparator 0
1
0
1
1
Analog comparator 1
1
1
0
0
Analog comparator 2
1
1
0
1
Analog comparator 3
1
1
1
0
Reserved
1
1
1
1
Reserved
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
18.9.4
ADC Result Data Registers – ADCH and ADCL
When an ADC conversion is complete, the conversion results are stored in these two result data
registers.
When the ADCL register is read, the two ADC result data registers can’t be updated until the
ADCH register has also been read.
Consequently, in 10-bit configuration, the ADCL register must be read first before the ADCH.
Nevertheless, to work easily with only 8-bit precision, there is the possibility to left adjust the
result thanks to the ADLAR bit in the ADCSRA register. Like this, it is sufficient to only read
ADCH to have the conversion result.
18.9.4.1
ADLAR = 0
Bit
Read/Write
Initial Value
18.9.4.2
6
5
4
3
2
1
0
-
-
-
-
-
-
ADC9
ADC8
ADCH
ADC7
ADC6
ADC5
ADC4
ADC3
ADC2
ADC1
ADC0
ADCL
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
ADLAR = 1
Bit
Read/Write
Initial Value
18.9.5
7
7
6
5
4
3
2
1
0
ADC9
ADC8
ADC7
ADC6
ADC5
ADC4
ADC3
ADC2
ADCH
ADC1
ADC0
-
-
-
-
-
-
ADCL
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Digital Input Disable Register 0 – DIDR0
Bit
7
ADC7D
6
5
ADC6D
ADC5D
ACMPN1D ACMPN0D
AMP2ND
4
3
2
1
0
ADC4D
ADC3D
ACMPN2D
ADC2D
ACMP2D
ADC1D
ADC0D
ACMPN3D
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
DIDR0
• Bit 7:0 – ADC7D..ADC0D, ACMPN0D, ACMPN1D, ACMPN2D, ACMPN3D, ACMP2D,
AMP2ND:
ADC7:0, ACMPN0, ACMPN1, ACMPN2, ACMPN3, ACMP2, AMP2N Digital Input Disable
When this bit is written logic one, the digital input buffer on the corresponding ADC pin is disabled. The corresponding PIN Register bit will always read as zero when this bit is set. When an
analog signal is applied to the ADC7..0 pin and the digital input from this pin is not needed, this
bit should be written logic one to reduce power consumption in the digital input buffer.
249
7647F–AVR–04/09
18.9.6
Digital Input Disable Register 1– DIDR1
Bit
7
6
5
4
3
2
1
0
-
AMP2PD
ACMP0D
AMP0PD
AMP0ND
ADC10D
ACMP1D
ADC9D
AMP1PD
ACMP3D
ADC8D
AMP1ND
Read/Write
-
-
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
DIDR1
• Bit 6:0 – ADC10D..8D, ACMP0D, ACMP1D, ACMP3D, AMP0PD, AMP0ND, AMP1PD,
AMP1ND, AMP2PD:
ADC10..8, ACMP0, ACMP1, ACMP3, AMP0P, AMP0N, AMP1P, AMP1N, AMP2P Digital
Input Disable
When this bit is written logic one, the digital input buffer on the corresponding ADC pin is disabled. The corresponding PIN Register bit will always read as zero when this bit is set. When an
analog signal is applied to an analog pin and the digital input from this pin is not needed, this bit
should be written logic one to reduce power consumption in the digital input buffer.
18.10 Amplifier
The ATmega16/32/64/M1/C1 features three differential amplified channels with programmable
5, 10, 20, and 40 gain stage.
Because the amplifiers are switching capacitor amplifiers, they need to be clocked by a synchronization signal called in this document the amplifier synchronization clock. To ensure an
accurate result, the amplifier input needs to have a quite stable input value during at least 4
Amplifier synchronization clock periods. The amplifiers can run with a clock frequency of up to
250 kHz (typical value).
To ensure an accurate result, the amplifier input needs to have a quite stable input value at the
sampling point during at least 4 amplifier synchronization clock periods.
Amplified conversions can be synchronized to PSC events (See “Synchronization Source
Description in One Ramp Mode” on page 152 and “Synchronization Source Description in Centered Mode” on page 152) or to the internal clock CK ADC equal to eighth the ADC clock
frequency. In case the synchronization is done the ADC clock divided by 8, this synchronization
is done automatically by the ADC interface in such a way that the sample-and-hold occurs at a
specific phase of CKADC2. A conversion initiated by the user (i.e., all single conversions, and the
first free running conversion) when CKADC2 is low will take the same amount of time as a single
ended conversion (13 ADC clock cycles from the next prescaled clock cycle). A conversion initiated by the user when CKADC2 is high will take 14 ADC clock cycles due to the synchronization
mechanism.
The normal way to use the amplifier is to select a synchronization clock via the AMPxTS1:0 bits
in the AMPxCSR register. Then the amplifier can be switched on, and the amplification is done
on each synchronization event.
In order to start an amplified Analog to Digital Conversion on the amplified channel, the ADMUX
must be configured as specified on Table 18-5 on page 246.
The ADC starting requirement is done by setting the ADSC bit of the ADCSRA Register.
Until the conversion is not achieved, it is not possible to start a conversion on another channel.
In order to have a better understanding of the functioning of the amplifier synchronization, two
timing diagram examples are shown Figure 18-15 and Figure 18-16.
250
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
As soon as a conversion is requested thanks to the ADSC bit, the Analog to Digital Conversion
is started. In case the amplifier output is modified during the sample phase of the ADC, the
on-going conversion is aborted and restarted as soon as the output of the amplifier is stable.
This ensure a fast response time. The only precaution to take is to be sure that the trig signal
(PSC) frequency is lower than ADCclk/4.
Figure 18-15. Amplifier synchronization timing diagram
With change on analog input signal
Delta V
4th stable sample
Signal to be
measured
PSC
Block
PSCn_ASY
AMPLI_clk
(Sync Clock)
CK ADC
Valid sample
ADSC
ADC
ADC
Activity
ADC
Conv
ADC
Sampling
ADC
Conv
ADC
Sampling
ADCResult
Ready
ADCResult
Ready
251
7647F–AVR–04/09
Figure 18-16. Amplifier synchronization timing diagram
ADSC is set when the amplifier output is changing due to the amplifier clock
switch
Signal to be
measured
PSC
Block
PSCn_ASY
AMPLI_clk
(Sync Clock)
CK ADC
Valid sample
ADSC
ADC
ADC
Activity
ADC
Conv
ADC
Sampling
ADC
Sampling
Aborted
ADC
Conv
ADC
Sampling
ADCResult
Ready
ADCResult
Ready
In order to have a better understanding of the functioning of the amplifier synchronization, a timing diagram example is shown Figure 18-15.
It is also possible to auto trigger conversion on the amplified channel. In this case, the conversion is started at the next amplifier clock event following the last auto trigger event selected
thanks to the ADTS bits in the ADCSRB register. In auto trigger conversion, the free running
mode is not possible unless the ADSC bit in ADCSRA is set by soft after each conversion.
252
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
The block diagram of the two amplifiers is shown on Figure 18-17.
Figure 18-17. Amplifiers block diagram
+
SAMPLING
AMP0+
AMP0-
Toward ADC MUX
(AMP0)
00
01
10
01
Amplifier 0
Clock
AMP0EN
AMP0IS
AMP0G1
ADCK/8
Timer 0 Compare Match
Timer 0 Overflow
Timer 1 Compare Match
Timer 1 Overflow
PSS0
PSS1
PSS2
AMP0G0 AMPCMP0 AMP0TS2 AMP0TS1 AMP0TS0
AMP0CSR
+
SAMPLING
AMP1+
AMP1-
Toward ADC MU
(AMP1)
00
01
10
01
Amplifier 1
Clock
AMP1EN
AMP1IS
AMP1G1
ADCK/8
Timer 0 Compare Match
Timer 0 Overflow
Timer 1 Compare Match
Timer 1 Overflow
PSS0
PSS1
PSS2
AMP1G0 AMPCMP1 AMP1TS2 AMP1TS1 AMP1TS0
AMP1CSR
+
SAMPLING
AMP2+
AMP2-
Toward ADC MU
(AMP2)
-
ADCK/8
Timer 0 Compare Match
Timer 0 Overflow
Timer 1 Compare Match
Timer 1 Overflow
PSS0
PSS1
PSS2
Amplifier 2
Clock
AMP2EN
AMP2IS
AMP2G1
AMP2G0 AMPCMP2 AMP2TS2 AMP2TS1 AMP2TS0
AMP2CSR
253
7647F–AVR–04/09
18.11 Amplifier Control Registers
The configuration of the amplifiers are controlled via two dedicated registers AMP0CSR and
AMP1CSR. Then the start of conversion is done via the ADC control and status registers.
The conversion result is stored on ADCH and ADCL register which contain respectively the most
significant bits and the less significant bits.
18.11.1
Amplifier 0 Control and Status register – AMP0CSR
Bit
7
6
5
4
3
2
1
0
AMP0EN
AMP0IS
AMP0G1
AMP0G0
AMPCMP0
AMP0TS2
AMP0TS1
AMP0TS0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
AMP0CSR
• Bit 7 – AMP0EN: Amplifier 0 Enable Bit
Set this bit to enable the Amplifier 0.
Clear this bit to disable the Amplifier 0.
Clearing this bit while a conversion is running will take effect at the end of the conversion.
Warning: Always clear AMP0TS0:1 when clearing AMP0EN.
• Bit 6 – AMP0IS: Amplifier 0 Input Shunt
Set this bit to short-circuit the Amplifier 0 input.
Clear this bit to normally use the Amplifier 0.
• Bit 5, 4 – AMP0G1, 0: Amplifier 0 Gain Selection Bits
These 2 bits determine the gain of the amplifier 0.
The different setting are shown in Table 18-8.
Table 18-8.
Amplifier 0 Gain Selection
AMP0G1
AMP0G0
Description
0
0
Gain 5
0
1
Gain 10
1
0
Gain 20
1
1
Gain 40
To ensure an accurate result, after the gain value has been changed, the amplifier input needs
to have a quite stable input value during at least 4 Amplifier synchronization clock periods.
• Bit 3 – AMPCMP0: Amplifier 0 - Comparator 0 connection
Set this bit to connect the amplifier 0 to the comparator 0 positive input. In this configuration the
comparator clock is twice the amplifier clock.
Clear this bit to normally use the Amplifier 0.
• Bit 2:0 – AMP0TS2,AMP0TS1,AMP0TS0: Amplifier 0 Clock Source Selection Bits
In accordance with the Table 18-9, these 3 bits select the event which will generate the clock for
the amplifier 0. This clock source is necessary to start the conversion on the amplified channel.
254
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 18-9.
18.11.2
AMP0 Clock Source Selection
AMP0TS2
AMP0TS1
AMP0TS0
Clock Source
0
0
0
ADC Clock/8
0
0
1
Timer/Counter0 Compare Match
0
1
0
Timer/Counter0 Overflow
0
1
1
Timer/Counter1 Compare Match B
1
0
0
Timer/Counter1 Overflow
1
0
1
PSC Module 0 Synchronization Signal (PSS0)
1
1
0
PSC Module 1 Synchronization Signal (PSS1)
1
1
1
PSC Module 2 Synchronization Signal (PSS2)
Amplifier 1 Control and Status register – AMP1CSR
Bit
7
6
5
4
3
2
1
0
AMP1EN
AMP1IS
AMP1G1
AMP1G0
AMPCMP1
AMP1TS2
AMP1TS1
AMP1TS0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
AMP1CSR
• Bit 7 – AMP1EN: Amplifier 1 Enable Bit
Set this bit to enable the Amplifier 1.
Clear this bit to disable the Amplifier 1.
Clearing this bit while a conversion is running will take effect at the end of the conversion.
Warning: Always clear AMP1TS0:1 when clearing AMP1EN.
• Bit 6 – AMP1IS: Amplifier 1 Input Shunt
Set this bit to short-circuit the Amplifier 1 input.
Clear this bit to normally use the Amplifier 1.
• Bit 5, 4 – AMP1G1, 0: Amplifier 1 Gain Selection Bits
These 2 bits determine the gain of the amplifier 1.
The different setting are shown in Table 18-10.
Table 18-10. Amplifier 1 Gain Selection
AMP1G1
AMP1G0
Description
0
0
Gain 5
0
1
Gain 10
1
0
Gain 20
1
1
Gain 40
To ensure an accurate result, after the gain value has been changed, the amplifier input needs
to have a quite stable input value during at least 4 Amplifier synchronization clock periods.
255
7647F–AVR–04/09
• Bit 3 – AMPCMP1: Amplifier 1 - Comparator 1 connection
Set this bit to connect the amplifier 1 to the comparator 1 positive input. In this configuration the
comparator clock is twice amplifier clock.
Clear this bit to normally use the Amplifier 1.
• Bit 2:0 – AMP1TS2,AMP1TS1, AMP1TS0: Amplifier 1 Clock Source Selection Bits
In accordance with the Table 18-11, these 3 bits select the event which will generate the clock
for the amplifier 1. This clock source is necessary to start the conversion on the amplified
channel.
Table 18-11. AMP1 Clock Source Selection
18.11.3
AMP1TS2
AMP1TS1
AMP1TS0
Clock Source
0
0
0
ADC Clock/8
0
0
1
Timer/Counter0 Compare Match
0
1
0
Timer/Counter0 Overflow
0
1
1
Timer/Counter1 Compare Match B
1
0
0
Timer/Counter1 Overflow
1
0
1
PSC Module 0 Synchronization Signal (PSS0)
1
1
0
PSC Module 1 Synchronization Signal (PSS1)
1
1
1
PSC Module 2 Synchronization Signal (PSS2)
Amplifier 2 Control and Status register – AMP2CSR
Bit
7
6
5
4
3
2
1
0
AMP2EN
AMP2IS
AMP2G1
AMP2G0
AMPCMP2
AMP2TS2
AMP2TS1
AMP2TS0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
AMP2CSR
• Bit 7 – AMP2EN: Amplifier 2 Enable Bit
Set this bit to enable the Amplifier 2.
Clear this bit to disable the Amplifier 2.
Clearing this bit while a conversion is running will take effect at the end of the conversion.
Warning: Always clear AMP2TS0:1 when clearing AMP2EN.
• Bit 6 – AMP2IS: Amplifier 2 Input Shunt
Set this bit to short-circuit the Amplifier 2 input.
Clear this bit to normally use the Amplifier 2.
• Bit 5, 4 – AMP2G1, 0: Amplifier 2 Gain Selection Bits
These 2 bits determine the gain of the amplifier 2.
The different setting are shown in Table 18-12.
256
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 18-12. Amplifier 2 Gain Selection
AMP2G1
AMP2G0
Description
0
0
Gain 5
0
1
Gain 10
1
0
Gain 20
1
1
Gain 40
To ensure an accurate result, after the gain value has been changed, the amplifier input needs
to have a quite stable input value during at least 4 Amplifier synchronization clock periods.
• Bit 3 – AMPCMP2: Amplifier 2 - Comparator 2 connection
Set this bit to connect the amplifier 2 to the comparator 2 positive input. In this configuration the
comparator clock is twice the amplifier clock.
Clear this bit to normally use the Amplifier 2.
• Bit 2:0 – AMP2TS2,AMP2TS1, AMP2TS0: Amplifier 2 Clock Source Selection Bits
In accordance with the Table 18-13, these 3 bits select the event which will generate the clock
for the amplifier 1. This clock source is necessary to start the conversion on the amplified
channel.
Table 18-13. AMP1 Clock Source Selection
AMP2TS2
AMP2TS1
AMP2TS0
Clock Source
0
0
0
ADC Clock/8
0
0
1
Timer/Counter0 Compare Match
0
1
0
Timer/Counter0 Overflow
0
1
1
Timer/Counter1 Compare Match B
1
0
0
Timer/Counter1 Overflow
1
0
1
PSC Module 0 Synchronization Signal (PSS0)
1
1
0
PSC Module 1 Synchronization Signal (PSS1)
1
1
1
PSC Module 2 Synchronization Signal (PSS2)
257
7647F–AVR–04/09
19. ISRC - Current Source
19.1
Features
• 100µA Constant current source
• ±6% Absolute Accuracy
The ATmega16/32/64/M1/C1 features a 100µA ±5% Current Source. After RESET or up on
request, the current is flowing through an external resistor. The voltage can be measured on the
dedicated pin shared with the ADC. Using a resistor in serie with a ≤≤ 0.5% tolerance is recommended. To protect the device against big values, the ADC must be configured with AVcc as
internal reference to perform the first measurement. Afterwards, another internal reference can
be chosen according to the previous measured value to refine the result.
When ISRCEN bit is set, the ISRC pin sources 100µA. Otherwise this pin keeps its initial
function.
Figure 19-1. Current Source Block Diagram
AVCC
100 uA
ISRCEN
AREF / ISRC
AREF Internal Circuit
AREFEN
External
Resistor
ADC Input
258
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
19.2
19.2.1
Typical applications
LIN Current Source
During the configuration of a LIN node in a cluster, it may be necessary to attribute dynamically
an unique physical address to every cluster node. The way to do it is not described in the LIN
protocol.
The Current Source offers an excellent solution to associate a physical address to the application supported by the LIN node. A full dynamic node configuration can be used to set-up the LIN
nodes in a cluster.
ATmega16/32/64/M1/C1 proposes to have an external resistor used in conjunction with the Current Source. The device measures the voltage to the boundaries of the resistance via the Analog
to Digital converter. The resulting voltage defines the physical address that the communication
handler will use when the node will participate in LIN communication.
In automotive applications, distributed voltages are very disturbed. The internal Current Source
solution of ATmega16/32/64/M1/C1 immunizes the address detection against any kind of voltage variations.
Table 19-1.
Example of Resistor Values(±5%) for a 8-address System (AVCC = 5V(1))
Typical
Measured
Voltage (V)
Minimum
Reading with
a 2.56V ref
Typical
Reading with
a 2.56V ref
Physical
Address
Resistor Value
Rload (Ohm)
0
1 000
0.1
40
1
2 200
0.22
88
2
3 300
0.33
132
3
4 700
0.47
188
4
6 800
0.68
272
5
10 000
1
400
6
15 000
1.5
600
7
22 000
2.2
880
Maximum
Reading with
a 2.56V ref
259
7647F–AVR–04/09
Table 19-2.
Physical
Address
Typical
Measured
Voltage (V)
Resistor Value
Rload (Ohm)
Minimum
Reading
with a 2.56V
ref
Typical
Reading
with a 2.56V
ref
Miximum
Reading
with a 2.56V
ref
0
1 000
0.1
38
40
45
1
1 200
0.12
46
48
54
2
1500
0.15
57
60
68
3
1800
0.18
69
72
81
4
2200
0.22
84
88
99
5
2700
0.27
104
108
122
6
3300
0.33
127
132
149
7
4700
0.47
181
188
212
8
6 800
0.68
262
272
306
9
8 200
0.82
316
328
369
10
10 000
1.0
386
400
450
11
12 000
1.2
463
480
540
12
15 000
1.5
579
600
675
13
18 000
1.8
694
720
810
14
22 000
2.2
849
880
989
15
27 000
2.7
1023
1023
1023
Note:
19.2.2
Example of Resistor Values(±1%) for a 16-address System (AVCC = 5V(1))
1. 5V range: Max Rload 30KΩ
3V range: Max Rload 15KΩ
Current Source for Low Cost Traducer
An external transducer based on variable resistor can be connected to the Current Source. This
ca be for instance:
• A thermistor, or temperature-sensitive resistor, used as a temperature sensor
• A CdS photoconductive cell, or luminosity-sensitivity resistor, used as a luminosity sensor.
Using the Current Source with this type of transducer eliminates the need for additional parts
otherwise required in resistor network or Wheatstone bridge.
19.2.3
260
Voltage Reference for External Devices
An external resistor used in conjunction with the Current Source can be used as voltage reference for external devices. Using a resistor in serie with a lower tolerance than the Current
Source accuracy (≤2%) is recommended. Table 19-2 gives an example of voltage references
using standard values of resistors.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
19.2.4
19.3
19.3.1
Threshold Reference for Internal Analog Comparator
An external resistor used in conjunction with the Current Source can be used as threshold reference for internal Analog Comparator (See ”Analog Comparator” on page 262.). This can be
connected to AIN0 (negative Analog Compare input pin) as well as AIN1 (positive Analog Compare input pin). Using a resistor in serie with a lower tolerance than the Current Source accuracy
(≤2%) is recommended. Table 19-2 gives an example of threshold references using standard values of resistors.
Control Register
ADC Control and Status Register B– ADCSRB
Bit
7
6
5
4
3
2
1
0
ADHSM
ISRCEN
AREFEN
-
ADTS3
ADTS2
ADTS1
ADTS0
Read/Write
R/W
R/W
R/W
R
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
ADCSRB
• Bit 6 – ISRCEN: Current Source Enable
Set this bit to source a 100µA current to the AREF pin.
Clear this bit to disconnect .
• Bit 5 – AREFEN: Analog Reference pin Enable
Set this bit to connect the internal AREF circuit to the AREF pin.
Clear this bit to disconnect the internal AREF circuit from the AREF pin.
261
7647F–AVR–04/09
20. Analog Comparator
The Analog Comparator compares the input values on the positive pin ACMPx and negative pin
ACMPM or ACMPMx.
20.1
Features
•
•
•
•
20.2
4 Analog Comparators
High Speed Clocked Comparators
4 reference levels
Generation of Configurable Interrupts
Overview
The ATmega16/32/64/M1/C1 features 4 fast analog comparators.
Each comparator has a dedicated input on the positive input, and the negative input of each
comparator can be configured as:
• a steady value among the 4 internal reference levels defined by the Vref selected thanks to
the REFS1:0 bits in ADMUX register.
• a value generated from the internal DAC
• an external analog input ACMPMx.
When the voltage on the positive ACMPn pin is higher than the voltage selected by the ACnM
multiplexer on the negative input, the Analog Comparator output, ACnO, is set.
The comparator is a clocked comparator. The comparators can run with a clock frequency of up
to 16MHz (typical value) when the supply voltage is in the 4.5V-5.5V range and with a clock frequency of up to 8MHz (typical value) otherwise.
Each comparator can trigger a separate interrupt, exclusive to the Analog Comparator. In addition, the user can select Interrupt triggering on comparator output rise, fall or toggle.
The interrupt flags can also be used to synchronize ADC or DAC conversions.
Moreover, the comparator’s output of the comparator 1 can be set to trigger the Timer/Counter1
Input Capture function.
A block diagram of the four comparators and their surrounding logic is shown in Figure 20-1.
262
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 20-1. Analog Comparator Block Diagram(1)(2)
AC0O
CLK I/O (/2)
AC0IF
ACMP0
+
Interrupt Sensitivity Control
ACMPN0
Analog Comparator 0 Interrupt
+
AMP0
AC0IE
AC0EN
-
AC0IS1
AC0IS0
AMPCMP0
AMPCMP0
ADC
AC1O
AC0M
2 1 0
ACMP1
CLK I/O (/2)
AC1IF
+
Interrupt Sensitivity Control
ACMPN1
Analog Comparator 1 Interrupt
+
AMP1
AC1IE
AC1EN
-
AC1IS1
AC1IS0
T1 Capture Trigger
AMPCMP1
AMPCMP1
AC1ICE
ADC
AC2O
AC1M
2 1 0
ACMP2
CLK I/O (/2)
AC2IF
+
Interrupt Sensitivity Control
ACMPN2
Analog Comparator 2 Interrupt
+
AMP2
AC2IE
AC2EN
-
AC2IS1
AC2IS0
AMPCMP2
AMPCMP2
ADC
AC3O
AC2M
2 1 0
ACMP3
CLK I/O (/2)
AC3IF
+
Interrupt Sensitivity Control
ACMPN3
Analog Comparator 3 Interrupt
AC3IE
AC3EN
AC3IS1
AC3IS0
DAC
Result
Bandgap
AC3M
2 1 0
Aref
AVcc
Internal 2.56V
Reference
REFS1
REFS0
Notes:
/1.60
/2.13
/3.20
/6.40
1. ADC multiplexer output: see Table 18-5 on page 246.
2. Refer to Figure 1-1 on page 3 and for Analog Comparator pin placement.
3. The voltage on Vref is defined in 18-4 “ADC Voltage Reference Selection” on page 245
20.3
Use of ADC Amplifiers
Thanks to AMPCMP0 configuration bit, Comparator 0 positive input can be connected to Amplifier O output. In that case, the clock of comparator 0 is twice the amplifier 0 clock. See “Amplifier
0 Control and Status register – AMP0CSR” on page 254.
Thanks to AMPCMP1 configuration bit, Comparator 1 positive input can be connected to Amplifier 1 output. In that case, the clock of comparator 1 is twice the amplifier 1 clock. See “Amplifier
1 Control and Status register – AMP1CSR” on page 255.
Thanks to AMPCMP2 configuration bit, Comparator 2 positive input can be connected to Amplifier 2 output. In that case, the clock of comparator 2 is twice the amplifier 2 clock. See “Amplifier
1 Control and Status register – AMP1CSR” on page 255.
263
7647F–AVR–04/09
20.4
Analog Comparator Register Description
Each analog comparator has its own control register.
A dedicated register has been designed to consign the outputs and the flags of the 4 analog
comparators.
20.4.1
Analog Comparator 0 Control Register – AC0CON
Bit
7
6
5
4
3
2
1
0
AC0EN
AC0IE
AC0IS1
AC0IS0
ACCKSEL
AC0M2
AC0M1
AC0M0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
AC0CON
• Bit 7– AC0EN: Analog Comparator 0 Enable Bit
Set this bit to enable the analog comparator 0.
Clear this bit to disable the analog comparator 0.
• Bit 6– AC0IE: Analog Comparator 0 Interrupt Enable bit
Set this bit to enable the analog comparator 0 interrupt.
Clear this bit to disable the analog comparator 0 interrupt.
• Bit 5, 4– AC0IS1, AC0IS0: Analog Comparator 0 Interrupt Select bit
These 2 bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 18-7.
Table 20-1.
Interrupt sensitivity selection
AC0IS1
AC0IS0
Description
0
0
Comparator Interrupt on output toggle
0
1
Reserved
1
0
Comparator interrupt on output falling edge
1
1
Comparator interrupt on output rising edge
• Bit 3 – ACCKSEL: Analog Comparator Clock Select
Set this bit to use the 16MHz PLL output as comparator clock.
Clear this bit to use the CLKIO as comparator clock.
• Bit 2, 1, 0– AC0M2, AC0M1, AC0M0: Analog Comparator 0 Multiplexer register
These 3 bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 20-2.
264
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 20-2.
20.4.2
Analog Comparator 0 negative input selection
AC0M2
AC0M1
AC0M0
Description
0
0
0
“Vref”/6.40
0
0
1
“Vref”/3.20
0
1
0
“Vref”/2.13
0
1
1
“Vref”/1.60
1
0
0
Bandgap (1.1V)
1
0
1
DAC result
1
1
0
Analog Comparator Negative Input (ACMPM pin)
1
1
1
Reserved
Analog Comparator 1Control Register – AC1CON
Bit
7
6
5
4
3
2
1
0
AC1EN
AC1IE
AC1IS1
AC1IS0
AC1ICE
AC1M2
AC1M1
AC1M0
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
AC1CON
• Bit 7– AC1EN: Analog Comparator 1 Enable Bit
Set this bit to enable the analog comparator 1.
Clear this bit to disable the analog comparator 1.
• Bit 6– AC1IE: Analog Comparator 1 Interrupt Enable bit
Set this bit to enable the analog comparator 1 interrupt.
Clear this bit to disable the analog comparator 1 interrupt.
• Bit 5, 4– AC1IS1, AC1IS0: Analog Comparator 1 Interrupt Select bit
These 2 bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 18-7.
Table 20-3.
Interrupt sensitivity selection
AC1IS1
AC1IS0
Description
0
0
Comparator Interrupt on output toggle
0
1
Reserved
1
0
Comparator interrupt on output falling edge
1
1
Comparator interrupt on output rising edge
• Bit 3– AC1ICE: Analog Comparator 1 Interrupt Capture Enable bit
Set this bit to enable the input capture of the Timer/Counter1 on the analog comparator event.
The comparator output is in this case directly connected to the input capture front-end logic,
making the comparator utilize the noise canceler and edge select features of the
Timer/Counter1 Input Capture interrupt. To make the comparator trigger the Timer/Counter1
Input Capture interrupt, the ICIE1 bit in the Timer Interrupt Mask Register (TIMSK1) must be set.
In case ICES1 bit (“Timer/Counter1 Control Register B – TCCR1B” on page 132) is set high, the
rising edge of AC1O is the capture/trigger event of the Timer/Counter1, in case ICES1 is set to
zero, it is the falling edge which is taken into account.
265
7647F–AVR–04/09
Clear this bit to disable this function. In this case, no connection between the Analog Comparator and the input capture function exists.
• Bit 2, 1, 0– AC1M2, AC1M1, AC1M0: Analog Comparator 1 Multiplexer register
These 3 bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 20-4.
Table 20-4.
20.4.3
Analog Comparator 1 negative input selection
AC1M2
AC1M1
AC1M0
Description
0
0
0
“Vref”/6.40
0
0
1
“Vref”/3.20
0
1
0
“Vref”/2.13
0
1
1
“Vref”/1.60
1
0
0
Bandgap (1.1V)
1
0
1
DAC result
1
1
0
Analog Comparator Negative Input (ACMPM pin)
1
1
1
Reserved
Analog Comparator 2 Control Register – AC2CON
Bit
7
6
5
4
3
2
1
0
AC2EN
AC2IE
AC2IS1
AC2IS0
-
AC2M2
AC2M1
AC2M0
Read/Write
R/W
R/W
R/W
R/W
-
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
AC2CON
• Bit 7– AC2EN: Analog Comparator 2 Enable Bit
Set this bit to enable the analog comparator 2.
Clear this bit to disable the analog comparator 2.
• Bit 6– AC2IE: Analog Comparator 2 Interrupt Enable bit
Set this bit to enable the analog comparator 2 interrupt.
Clear this bit to disable the analog comparator 2 interrupt.
• Bit 5, 4– AC2IS1, AC2IS0: Analog Comparator 2 Interrupt Select bit
These 2 bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 18-7.
Table 20-5.
Interrupt sensitivity selection
AC2IS1
AC2IS0
Description
0
0
Comparator Interrupt on output toggle
0
1
Reserved
1
0
Comparator interrupt on output falling edge
1
1
Comparator interrupt on output rising edge
Bit 3 – Res: Reserved Bit
This bit is an unused bit in the ATmega16/32/64/M1/C1, and will always read as zero.
266
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 2, 1, 0– AC2M2, AC2M1, AC2M0: Analog Comparator 2 Multiplexer register
These 3 bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 20-6.
Table 20-6.
20.4.4
Analog Comparator 2 negative input selection
AC2M2
AC2M1
AC2M0
Description
0
0
0
“Vref”/6.40
0
0
1
“Vref”/3.20
0
1
0
“Vref”/2.13
0
1
1
“Vref”/1.60
1
0
0
Bandgap (1.1V)
1
0
1
DAC result
1
1
0
Analog Comparator Negative Input (ACMPM pin)
1
1
1
Reserved
Analog Comparator 3 Control Register – AC3CON
Bit
7
6
5
4
3
2
1
0
AC3EN
AC3IE
AC3IS1
AC3IS0
-
AC3M2
AC3M1
AC3M0
Read/Write
R/W
R/W
R/W
R/W
-
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
AC3CON
• Bit 7– AC3EN: Analog Comparator 3 Enable Bit
Set this bit to enable the analog comparator 3.
Clear this bit to disable the analog comparator 3.
• Bit 6– AC3IE: Analog Comparator 3 Interrupt Enable bit
Set this bit to enable the analog comparator 3 interrupt.
Clear this bit to disable the analog comparator 3 interrupt.
• Bit 5, 4– AC3IS1, AC3IS0: Analog Comparator 3 Interrupt Select bit
These 2 bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 18-7.
Table 20-7.
Interrupt sensitivity selection
AC3IS1
AC3IS0
Description
0
0
Comparator Interrupt on output toggle
0
1
Reserved
1
0
Comparator interrupt on output falling edge
1
1
Comparator interrupt on output rising edge
• Bit 3 – Res: Reserved Bit
This bit is an unused bit in the ATmega16/32/64/M1/C1, and will always read as zero.
• Bit 2, 1, 0– AC3M2, AC3M1, AC3M0: Analog Comparator 3 Multiplexer register
These 3 bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 20-6.
267
7647F–AVR–04/09
Table 20-8.
20.4.5
Analog Comparator 3 negative input selection
AC3M2
AC3M1
AC3M0
Description
0
0
0
“Vref”/6.40
0
0
1
“Vref”/3.20
0
1
0
“Vref”/2.13
0
1
1
“Vref”/1.60
1
0
0
Bandgap (1.1V)
1
0
1
DAC result
1
1
0
Analog Comparator Negative Input (ACMPM pin)
1
1
1
Reserved
Analog Comparator Status Register – ACSR
Bit
7
6
5
4
3
2
1
0
AC3IF
AC2IF
AC1IF
AC0IF
AC3O
AC2O
AC1O
AC0O
Read/Write
R/W
R/W
R/W
R/W
R
R
R
R
Initial Value
0
0
0
0
0
0
0
0
ACSR
• Bit 7– AC3IF: Analog Comparator 3 Interrupt Flag Bit
This bit is set by hardware when comparator 3 output event triggers off the interrupt mode
defined by AC3IS1 and AC3IS0 bits in AC2CON register.
This bit is cleared by hardware when the corresponding interrupt vector is executed in case the
AC3IE in AC3CON register is set. Anyway, this bit is cleared by writing a logical one on it.
This bit can also be used to synchronize ADC or DAC conversions.
• Bit 6– AC2IF: Analog Comparator 2 Interrupt Flag Bit
This bit is set by hardware when comparator 2 output event triggers off the interrupt mode
defined by AC2IS1 and AC2IS0 bits in AC2CON register.
This bit is cleared by hardware when the corresponding interrupt vector is executed in case the
AC2IE in AC2CON register is set. Anyway, this bit is cleared by writing a logical one on it.
This bit can also be used to synchronize ADC or DAC conversions.
• Bit 5– AC1IF: Analog Comparator 1 Interrupt Flag Bit
This bit is set by hardware when comparator 1 output event triggers off the interrupt mode
defined by AC1IS1 and AC1IS0 bits in AC1CON register.
This bit is cleared by hardware when the corresponding interrupt vector is executed in case the
AC1IE in AC1CON register is set. Anyway, this bit is cleared by writing a logical one on it.
This bit can also be used to synchronize ADC or DAC conversions.
• Bit 4– AC0IF: Analog Comparator 0 Interrupt Flag Bit
This bit is set by hardware when comparator 0 output event triggers off the interrupt mode
defined by AC0IS1 and AC0IS0 bits in AC0CON register.
This bit is cleared by hardware when the corresponding interrupt vector is executed in case the
AC0IE in AC0CON register is set. Anyway, this bit is cleared by writing a logical one on it.
This bit can also be used to synchronize ADC or DAC conversions.
268
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 3– AC3O: Analog Comparator 3 Output Bit
AC3O bit is directly the output of the Analog comparator 2.
Set when the output of the comparator is high.
Cleared when the output comparator is low.
• Bit 2– AC2O: Analog Comparator 2 Output Bit
AC2O bit is directly the output of the Analog comparator 2.
Set when the output of the comparator is high.
Cleared when the output comparator is low.
• Bit 1– AC1O: Analog Comparator 1 Output Bit
AC1O bit is directly the output of the Analog comparator 1.
Set when the output of the comparator is high.
Cleared when the output comparator is low.
• Bit 0– AC0O: Analog Comparator 0 Output Bit
AC0O bit is directly the output of the Analog comparator 0.
Set when the output of the comparator is high.
Cleared when the output comparator is low.
20.4.6
Digital Input Disable Register 0 – DIDR0
Bit
7
ADC7D
6
5
ADC6D
ADC5D
ACMPN1D ACMPN0D
AMP2ND
4
3
2
1
0
ADC4D
ADC3D
ACMPN2D
ADC2D
ACMP2D
ADC1D
ADC0D
ACMPN3D
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
DIDR0
• Bit 6, 5, 3, 2, 0 – ACMPN1D, ACMPN0D, ACMPN2D, ACMP2D and ACMPN3D:
ACMPN1, ACMPN0, ACMPN2, ACMP2 and ACMPN3 Digital Input Disable
When this bit is written logic one, the digital input buffer on the corresponding Analog pin is disabled. The corresponding PIN Register bit will always read as zero when this bit is set. When an
analog signal is applied to one of these pins and the digital input from this pin is not needed, this
bit should be written logic one to reduce power consumption in the digital input buffer.
20.4.7
Digital Input Disable Register 1– DIDR1
Bit
7
6
5
4
3
2
1
0
-
AMP2PD
ACMP0D
AMP0PD
AMP0ND
ADC10D
ACMP1D
ADC9D
AMP1PD
ACMP3D
ADC8D
AMP1ND
Read/Write
-
-
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
DIDR1
• Bit 5, 2, 1: ACMP0D, ACMP1PD, ACMP3PD:
ACMP0, ACMP1P, ACMP3P Digital Input Disable
When this bit is written logic one, the digital input buffer on the corresponding analog pin is disabled. The corresponding PIN Register bit will always read as zero when this bit is set. When an
analog signal is applied to one of these pins and the digital input from this pin is not needed, this
bit should be written logic one to reduce power consumption in the digital input buffer.
269
7647F–AVR–04/09
21. Digital to Analog Converter - DAC
21.1
Features
•
•
•
•
•
10 bits resolution
8 bits linearity
+/- 0.5 LSB accuracy between 150mV and AVcc-150mV
Vout = DAC*Vref/1023
The DAC could be connected to the negative inputs of the analog comparators and/or to a
dedicated output driver.
• The output impedance of the driver is around 100 Ohms. So the driver is able to load a 1nF
capacitance in parallel with a resistor higher than 33K with a time constant around 1us.
The ATmega16/32/64/M1/C1 features a 10-bit Digital to Analog Converter. This DAC can be
used for the analog comparators and/or can be output on the D2A pin of the microcontroller via
a dedicated driver.
The DAC has a separate analog supply voltage pin, AVCC. AVCC must not differ more than ±0.3V
from VCC. See the paragraph “ADC Noise Canceler” on page 237 on how to connect this pin.
The reference voltage is the same as the one used for the ADC, See “Clock Prescaler Register
– CLKPR” on page 38.. These nominally 2.56V Vref or AVCC are provided On-chip. The voltage
reference may be externally decoupled at the AREF pin by a capacitor for better noise
performance.
270
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 21-1. Digital to Analog Converter Block Schematic
DAC
Result
D2A pin
VRef
DAC
Output
Driver
10
1
0
10
10
DAC High bits
DAC Low bits
Sources
DACH
Update DAC
Trigger
Edge
Detector
DAATE
DACL
DATS2
DATS1
DATS0
-
DALA
DAOE
DAEN
DACON
21.2
Operation
The Digital to Analog Converter generates an analog signal proportional to the value of the DAC
registers value.
In order to have an accurate sampling frequency control, there is the possibility to update the
DAC input values through different trigger events.
21.3
Starting a Conversion
The DAC is configured thanks to the DACON register. As soon as the DAEN bit in DACON register is set, the DAC converts the value present on the DACH and DACL registers in accordance
with the register DACON setting.
Alternatively, a conversion can be triggered automatically by various sources. Auto Triggering is
enabled by setting the DAC Auto Trigger Enable bit, DAATE in DACON. The trigger source is
selected by setting the DAC Trigger Select bits, DATS in DACON (See description of the DATS
bits for a list of the trigger sources). When a positive edge occurs on the selected trigger signal,
the DAC converts the value present on the DACH and DACL registers in accordance with the
register DACON setting. This provides a method of starting conversions at fixed intervals. If the
trigger signal is still set when the conversion completes, a new conversion will not be started. If
another positive edge occurs on the trigger signal during conversion, the edge will be ignored.
271
7647F–AVR–04/09
Note that an interrupt flag will be set even if the specific interrupt is disabled or the Global Interrupt Enable bit in SREG is cleared. A conversion can thus be triggered without causing an
interrupt. However, the interrupt flag must be cleared in order to trigger a new conversion at the
next interrupt event.
21.3.1
DAC Voltage Reference
The reference voltage for the ADC (VREF) indicates the conversion range for the DAC. VREF can
be selected as either AVCC, internal 2.56V reference, or external AREF pin.
AVCC is connected to the DAC through a passive switch. The internal 2.56V reference is generated from the internal bandgap reference (VBG) through an internal amplifier. In either case, the
external AREF pin is directly connected to the DAC, and the reference voltage can be made
more immune to noise by connecting a capacitor between the AREF pin and ground. VREF can
also be measured at the AREF pin with a high impedant voltmeter. Note that VREF is a high
impedant source, and only a capacitive load should be connected in a system.
If the user has a fixed voltage source connected to the AREF pin, the user may not use the other
reference voltage options in the application, as they will be shorted to the external voltage. If no
external voltage is applied to the AREF pin, the user may switch between AVCC and 2.56V as
reference selection. The first DAC conversion result after switching reference voltage source
may be inaccurate, and the user is advised to discard this result.
21.4
DAC Register Description
The DAC is controlled via three dedicated registers:
• The DACON register which is used for DAC configuration
• DACH and DACL which are used to set the value to be converted.
21.4.1
Digital to Analog Conversion Control Register – DACON
Bit
7
6
5
4
3
2
1
0
DAATE
DATS2
DATS1
DATS0
-
DALA
DAOE
DAEN
Read/Write
R/W
R/W
R/W
R/W
-
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
DACON
Bit 7 – DAATE: DAC Auto Trigger Enable bit
Set this bit to update the DAC input value on the positive edge of the trigger signal selected with
the DACTS2-0 bit in DACON register.
Clear it to automatically update the DAC input when a value is written on DACH register.
Bit 6:4 – DATS2, DATS1, DATS0: DAC Trigger Selection bits
These bits are only necessary in case the DAC works in auto trigger mode. It means if DAATE
bit is set.
272
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
In accordance with the Table 18-7, these 3 bits select the interrupt event which will generate the
update of the DAC input values. The update will be generated by the rising edge of the selected
interrupt flag whether the interrupt is enabled or not.
Table 21-1.
DAC Auto Trigger source selection
DATS2
DATS1
DATS0
Description
0
0
0
Analog comparator 0
0
0
1
Analog comparator 1
0
1
0
External Interrupt Request 0
0
1
1
Timer/Counter0 Compare Match
1
0
0
Timer/Counter0 Overflow
1
0
1
Timer/Counter1 Compare Match B
1
1
0
Timer/Counter1 Overflow
1
1
1
Timer/Counter1 Capture Event
• Bit 2 – DALA: Digital to Analog Left Adjust
Set this bit to left adjust the DAC input data.
Clear it to right adjust the DAC input data.
The DALA bit affects the configuration of the DAC data registers. Changing this bit affects the
DAC output on the next DACH writing.
• Bit 1 – DAOE: Digital to Analog Output Enable bit
Set this bit to output the conversion result on D2A,
Clear it to use the DAC internally.
• Bit 0 – DAEN: Digital to Analog Enable bit
Set this bit to enable the DAC,
Clear it to disable the DAC.
21.4.2
Digital to Analog Converter input Register – DACH and DACL
DACH and DACL registers contain the value to be converted into analog voltage.
Writing the DACL register prohibits the update of the input value until DACH has not been written too. So the normal way to write a 10-bit value in the DAC register is firstly to write DACL the
DACH.
In order to work easily with only 8 bits, there is the possibility to left adjust the input value. Like
this it is sufficient to write DACH to update the DAC value.
21.4.2.1
DALA = 0
Bit
Read/Write
Initial Value
7
6
5
4
3
2
1
0
-
-
-
-
-
-
DAC9
DAC8
DACH
DAC7
DAC6
DAC5
DAC4
DAC3
DAC2
DAC1
DAC0
DACL
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
273
7647F–AVR–04/09
21.4.2.2
DALA = 1
Bit
Read/Write
Initial Value
7
6
5
4
3
2
1
0
DAC9
DAC8
DAC7
DAC6
DAC5
DAC4
DAC3
DAC2
DACH
DAC1
DAC0
-
-
-
-
-
-
DACL
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
To work with the 10-bit DAC, two registers have to be updated. In order to avoid intermediate
value, the DAC input values which are really converted into analog signal are buffered into
unreachable registers. In normal mode, the update of the shadow register is done when the register DACH is written.
In case DAATE bit is set, the DAC input values will be updated on the trigger event selected
through DATS bits.
In order to avoid wrong DAC input values, the update can only be done after having written
respectively DACL and DACH registers. It is possible to work on 8-bit configuration by only writing the DACH value. In this case, update is done each trigger event.
In case DAATE bit is cleared, the DAC is in an automatic update mode. Writing the DACH register automatically update the DAC input values with the DACH and DACL register values.
It means that whatever is the configuration of the DAATE bit, changing the DACL register has no
effect on the DAC output until the DACH register has also been updated. So, to work with 10
bits, DACL must be written first before DACH. To work with 8-bit configuration, writing DACH
allows the update of the DAC.
274
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
22. Analog Feature Considerations
22.1
Purpose
The ATmega16/32/64/M1/C1 features several analog features such as ADC, DAC, Amplifiers,
Comparators...
The purpose of this section is to describe the interaction between these features. This section
explains how to set the specific registers to get the system running.
Particularly the different peripheral clocks can interfere together, so special care has to be
considered.
22.2
Use of an Amplifier as Comparator Input
The internal amplifiers provide differential amplification for ADC converter. To allow signed result
with the ADC, the output level of the amplifiers is shifted up with a Vref/2 voltage.
For this reason, when used with a comparator, a Vref/2 voltage is added to the voltage of the
amplifier outputs.
Figure 22-1. Amplifier and Comparator
Comparator
Clock
ACMPx
+
Amplifier
Clock
AMPx+
AMPx-
+
AMPx
Analog Comparator
Negative Input
-
Analog Comparator
Output
ACxEN
AMPCMPx
The amplifier Clock comes from the ADC and is equal to the ADC Clock divided by 8.
22.3
Use of an Amplifier as Comparator Input and ADC Input
The amplifier can be used as ADC input while it is used as comparator input. In that case, each
time the amplifier is selected as ADC input, the sampling and hold circuit of the ADC loads the
amplifier output. It results a decrease of the amplifier output voltage which can toggle the comparator output.
275
7647F–AVR–04/09
Figure 22-2. Amplifier, Comparator and ADC
Comparator
Clock
ACMPx
+
Amplifier
Clock
AMPx+
AMPx-
+
-
AMPx
Analog Comparator
Negative Input
-
Analog Comparator
Output
ACxEN
AMPCMPx
ADC
Sampling
& Hold
ADC Multiplexer
22.4
22.4.1
Analog Peripheral Clock Sources
ADC Clock
The ADC clock comes from the clock system (CLKio) and it is divided by the ADC Prescaler.
See “ADC Prescaler Selection” on page 247. The bits described in the ADC Prescaler Selection
determine the division factor between the system clock frequency and input clock of the ADC.
See “Prescaling and Conversion Timing” on page 233. for a complete description of the ADC
clock system.
22.4.2
Comparator Clock
While it is not connected to an amplifier, a comparator is clocked by the comparator clock which
is configured thanks to the ACCKSEL bit in AC0CON register See “Analog Comparator 0 Control Register – AC0CON” on page 264. One can select between the 16MHz PLL output and the
CLKio.
When it is connected to an amplifier, a comparator is clock by twice the amplifier clock.
22.4.3
Amplifier Clock
When the Amplifier uses the ADC clock, this clock is divided by 8. This insures a maximum frequency of 250kHz for the amplifier when the ADC clock is 2MHz. When the ADC is clocked with
a frequency higher than 2MHz the amplifier cannot be clocked by the ADC clock.
See “Amplifier” on page 250. for a complete description of the Amplifier clock system.
276
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
23. debugWIRE On-chip Debug System
23.1
Features
•
•
•
•
•
•
•
•
•
•
23.2
Complete Program Flow Control
Emulates All On-chip Functions, Both Digital and Analog, except RESET Pin
Real-time Operation
Symbolic Debugging Support (Both at C and Assembler Source Level, or for Other HLLs)
Unlimited Number of Program Break Points (Using Software Break Points)
Non-intrusive Operation
Electrical Characteristics Identical to Real Device
Automatic Configuration System
High-Speed Operation
Programming of Non-volatile Memories
Overview
The debugWIRE On-chip debug system uses a One-wire, bi-directional interface to control the
program flow, execute AVR instructions in the CPU and to program the different non-volatile
memories.
23.3
Physical Interface
When the debugWIRE Enable (DWEN) Fuse is programmed and Lock bits are unprogrammed,
the debugWIRE system within the target device is activated. The RESET port pin is configured
as a wire-AND (open-drain) bi-directional I/O pin with pull-up enabled and becomes the communication gateway between target and emulator.
Figure 23-1. The debugWIRE Setup
1.8 - 5.5V
VCC
dW
dW(RESET)
GND
Figure 23-1 shows the schematic of a target MCU, with debugWIRE enabled, and the emulator
connector. The system clock is not affected by debugWIRE and will always be the clock source
selected by the CKSEL Fuses.
277
7647F–AVR–04/09
When designing a system where debugWIRE will be used, the following observations must be
made for correct operation:
• Pull-up resistors on the dW/(RESET) line must not be smaller than 10kΩ. The pull-up resistor
is not required for debugWIRE functionality.
• Connecting the RESET pin directly to VCC will not work.
• Capacitors connected to the RESET pin must be disconnected when using debugWire.
• All external reset sources must be disconnected.
23.4
Software Break Points
debugWIRE supports Program memory Break Points by the AVR Break instruction. Setting a
Break Point in AVR Studio® will insert a BREAK instruction in the Program memory. The instruction replaced by the BREAK instruction will be stored. When program execution is continued, the
stored instruction will be executed before continuing from the Program memory. A break can be
inserted manually by putting the BREAK instruction in the program.
The Flash must be re-programmed each time a Break Point is changed. This is automatically
handled by AVR Studio through the debugWIRE interface. The use of Break Points will therefore
reduce the Flash Data retention. Devices used for debugging purposes should not be shipped to
end customers.
23.5
Limitations of debugWIRE
The debugWIRE communication pin (dW) is physically located on the same pin as External
Reset (RESET). An External Reset source is therefore not supported when the debugWIRE is
enabled.
The debugWIRE system accurately emulates all I/O functions when running at full speed, i.e.,
when the program in the CPU is running. When the CPU is stopped, care must be taken while
accessing some of the I/O Registers via the debugger (AVR Studio).
A programmed DWEN Fuse enables some parts of the clock system to be running in all sleep
modes. This will increase the power consumption while in sleep. Thus, the DWEN Fuse should
be disabled when debugWire is not used.
23.6
debugWIRE Related Register in I/O Memory
The following section describes the registers used with the debugWire.
23.6.1
debugWire Data Register – DWDR
Bit
7
6
5
4
3
2
1
0
DWDR[7:0]
DWDR
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
The DWDR Register provides a communication channel from the running program in the MCU
to the debugger. This register is only accessible by the debugWIRE and can therefore not be
used as a general purpose register in the normal operations.
278
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
24. Boot Loader Support – Read-While-Write Self-Programming
ATmega16/32/64/M1/C1
In ATmega16/32/64/M1/C1, the Boot Loader Support provides a real Read-While-Write
Self-Programming mechanism for downloading and uploading program code by the MCU itself.
This feature allows flexible application software updates controlled by the MCU using a
Flash-resident Boot Loader program. The Boot Loader program can use any available data
interface and associated protocol to read code and write (program) that code into the Flash
memory, or read the code from the program memory. The program code within the Boot Loader
section has the capability to write into the entire Flash, including the Boot Loader memory. The
Boot Loader can thus even modify itself, and it can also erase itself from the code if the feature
is not needed anymore. The size of the Boot Loader memory is configurable with fuses and the
Boot Loader has two separate sets of Boot Lock bits which can be set independently. This gives
the user a unique flexibility to select different levels of protection.
24.1
Boot Loader Features
•
•
•
•
•
•
•
Read-While-Write Self-Programming
Flexible Boot Memory Size
High Security (Separate Boot Lock Bits for a Flexible Protection)
Separate Fuse to Select Reset Vector
Optimized Page(1) Size
Code Efficient Algorithm
Efficient Read-Modify-Write Support
Note:
24.2
1. A page is a section in the Flash consisting of several bytes (see Table 25-12 on page 303)
used during programming. The page organization does not affect normal operation.
Application and Boot Loader Flash Sections
The Flash memory is organized in two main sections, the Application section and the Boot
Loader section (see Figure 24-2). The size of the different sections is configured by the
BOOTSZ Fuses as shown in Table 24-7 on page 292 and Figure 24-2. These two sections can
have different level of protection since they have different sets of Lock bits.
24.2.1
Application Section
The Application section is the section of the Flash that is used for storing the application code.
The protection level for the Application section can be selected by the application Boot Lock bits
(Boot Lock bits 0), see Table 24-2 on page 283. The Application section can never store any
Boot Loader code since the SPM instruction is disabled when executed from the Application
section.
24.2.2
BLS – Boot Loader Section
While the Application section is used for storing the application code, the The Boot Loader software must be located in the BLS since the SPM instruction can initiate a programming when
executing from the BLS only. The SPM instruction can access the entire Flash, including the
BLS itself. The protection level for the Boot Loader section can be selected by the Boot Loader
Lock bits (Boot Lock bits 1), see Table 24-3 on page 283.
279
7647F–AVR–04/09
24.3
Read-While-Write and No Read-While-Write Flash Sections
Whether the CPU supports Read-While-Write or if the CPU is halted during a Boot Loader software update is dependent on which address that is being programmed. In addition to the two
sections that are configurable by the BOOTSZ Fuses as described above, the Flash is also
divided into two fixed sections, the Read-While-Write (RWW) section and the No
Read-While-Write (NRWW) section. The limit between the RWW- and NRWW sections is given
in Table 24-8 on page 292 and Figure 24-2 on page 282. The main difference between the two
sections is:
• When erasing or writing a page located inside the RWW section, the NRWW section can be
read during the operation.
• When erasing or writing a page located inside the NRWW section, the CPU is halted during
the entire operation.
Note that the user software can never read any code that is located inside the RWW section during a Boot Loader software operation. The syntax “Read-While-Write section” refers to which
section that is being programmed (erased or written), not which section that actually is being
read during a Boot Loader software update.
24.3.1
RWW – Read-While-Write Section
If a Boot Loader software update is programming a page inside the RWW section, it is possible
to read code from the Flash, but only code that is located in the NRWW section. During an
on-going programming, the software must ensure that the RWW section never is being read. If
the user software is trying to read code that is located inside the RWW section (i.e., by a
call/jmp/lpm or an interrupt) during programming, the software might end up in an unknown
state. To avoid this, the interrupts should either be disabled or moved to the Boot Loader section. The Boot Loader section is always located in the NRWW section. The RWW Section Busy
bit (RWWSB) in the Store Program Memory Control and Status Register (SPMCSR) will be read
as logical one as long as the RWW section is blocked for reading. After a programming is completed, the RWWSB must be cleared by software before reading code located in the RWW
section. See “Store Program Memory Control and Status Register – SPMCSR” on page 284. for
details on how to clear RWWSB.
24.3.2
NRWW – No Read-While-Write Section
The code located in the NRWW section can be read when the Boot Loader software is updating
a page in the RWW section. When the Boot Loader code updates the NRWW section, the CPU
is halted during the entire Page Erase or Page Write operation.
Table 24-1.
280
Read-While-Write Features
Which Section does the Z-pointer
Address During the Programming?
Which Section Can
be Read During
Programming?
Is the CPU
Halted?
Read-While-Write
Supported?
RWW Section
NRWW Section
No
Yes
NRWW Section
None
Yes
No
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 24-1. Read-While-Write vs. No Read-While-Write
Read-While-Write
(RWW) Section
Z-pointer
Addresses RWW
Section
Z-pointer
Addresses NRWW
Section
No Read-While-Write
(NRWW) Section
CPU is Halted
During the Operation
Code Located in
NRWW Section
Can be Read During
the Operation
281
7647F–AVR–04/09
Figure 24-2. Memory Sections
Program Memory
BOOTSZ = '10'
Program Memory
BOOTSZ = '11'
0x0000
No Read-While-Write Section
Read-While-Write Section
Application Flash Section
End RWW
Start NRWW
Application Flash Section
Boot Loader Flash Section
End Application
Start Boot Loader
Flashend
No Read-While-Write Section
Read-While-Write Section
0x0000
Program Memory
BOOTSZ = '01'
Application Flash Section
End RWW
Start NRWW
Application Flash Section
End Application
Start Boot Loader
Boot Loader Flash Section
Flashend
Program Memory
BOOTSZ = '00'
24.4
Read-While-Write Section
Application Flash Section
No Read-While-Write Section
Note:
0x0000
End RWW
Start NRWW
Application Flash Section
End Application
Start Boot Loader
Boot Loader Flash Section
Flashend
No Read-While-Write Section
Read-While-Write Section
0x0000
Application Flash Section
End RWW, End Application
Start NRWW, Start Boot Loader
Boot Loader Flash Section
Flashend
1. The parameters in the figure above are given in Table 24-7 on page 292.
Boot Loader Lock Bits
If no Boot Loader capability is needed, the entire Flash is available for application code. The
Boot Loader has two separate sets of Boot Lock bits which can be set independently. This gives
the user a unique flexibility to select different levels of protection.
The user can select:
• To protect the entire Flash from a software update by the MCU.
• To protect only the Boot Loader Flash section from a software update by the MCU.
• To protect only the Application Flash section from a software update by the MCU.
• Allow software update in the entire Flash.
See Table 24-2 and Table 24-3 for further details. The Boot Lock bits can be set in software and
in Serial or Parallel Programming mode, but they can be cleared by a Chip Erase command
only. The general Write Lock (Lock Bit mode 2) does not control the programming of the Flash
memory by SPM instruction. Similarly, the general Read/Write Lock (Lock Bit mode 1) does not
control reading nor writing by LPM/SPM, if it is attempted.
282
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 24-2.
BLB0 Mode
BLB02
BLB01
1
1
1
No restrictions for SPM or LPM accessing the Application
section.
2
1
0
SPM is not allowed to write to the Application section.
0
SPM is not allowed to write to the Application section, and LPM
executing from the Boot Loader section is not allowed to read
from the Application section. If Interrupt Vectors are placed in
the Boot Loader section, interrupts are disabled while executing
from the Application section.
3
Note:
0
Protection
LPM executing from the Boot Loader section is not allowed to
read from the Application section. If Interrupt Vectors are placed
4
0
1
in the Boot Loader section, interrupts are disabled while
executing from the Application section.
1. “1” means unprogrammed, “0” means programmed
Table 24-3.
Boot Lock Bit1 Protection Modes (Boot Loader Section)(Note:)
BLB1 Mode
BLB12
BLB11
1
1
1
No restrictions for SPM or LPM accessing the Boot Loader
section.
2
1
0
SPM is not allowed to write to the Boot Loader section.
0
SPM is not allowed to write to the Boot Loader section, and LPM
executing from the Application section is not allowed to read
from the Boot Loader section. If Interrupt Vectors are placed in
the Application section, interrupts are disabled while executing
from the Boot Loader section.
1
LPM executing from the Application section is not allowed to
read from the Boot Loader section. If Interrupt Vectors are
placed in the Application section, interrupts are disabled while
executing from the Boot Loader section.
3
4
Note:
24.5
Boot Lock Bit0 Protection Modes (Application Section)(1)
0
0
Protection
“1” means unprogrammed, “0” means programmed
Entering the Boot Loader Program
Entering the Boot Loader takes place by a jump or call from the application program. This may
be initiated by a trigger such as a command received via UART, or SPI interface. Alternatively,
the Boot Reset Fuse can be programmed so that the Reset Vector is pointing to the Boot Flash
start address after a reset. In this case, the Boot Loader is started after a reset. After the application code is loaded, the program can start executing the application code. Note that the fuses
cannot be changed by the MCU itself. This means that once the Boot Reset Fuse is programmed, the Reset Vector will always point to the Boot Loader Reset and the fuse can only be
changed through the serial or parallel programming interface.
Table 24-4.
BOOTRST
Note:
Boot Reset Fuse(1)
Reset Address
1
Reset Vector = Application Reset (address 0x0000)
0
Reset Vector = Boot Loader Reset (see Table 24-7 on page 292)
1. “1” means unprogrammed, “0” means programmed
283
7647F–AVR–04/09
24.5.1
Store Program Memory Control and Status Register – SPMCSR
The Store Program Memory Control and Status Register contains the control bits needed to control the Boot Loader operations.
Bit
7
6
5
4
3
2
1
0
SPMIE
RWWSB
SIGRD
RWWSRE
BLBSET
PGWRT
PGERS
SPMEN
Read/Write
R/W
R
R
R/W
R/W
R/W
R/W
R/W
Initial Value
0
0
0
0
0
0
0
0
SPMCSR
• Bit 7 – SPMIE: SPM Interrupt Enable
When the SPMIE bit is written to one, and the I-bit in the Status Register is set (one), the SPM
ready interrupt will be enabled. The SPM ready Interrupt will be executed as long as the SPMEN
bit in the SPMCSR Register is cleared.
• Bit 6 – RWWSB: Read-While-Write Section Busy
When a Self-Programming (Page Erase or Page Write) operation to the RWW section is initiated, the RWWSB will be set (one) by hardware. When the RWWSB bit is set, the RWW section
cannot be accessed. The RWWSB bit will be cleared if the RWWSRE bit is written to one after a
Self-Programming operation is completed. Alternatively the RWWSB bit will automatically be
cleared if a page load operation is initiated.
• Bit 5 – SIGRD: Signature Row Read
If this bit is written to one at the same time as SPMEN, the next LPM instruction within three
clock cycles will read a byte from the signature row into the destination register. see “Reading
the Signature Row from Software” on page 289 for details. An SPM instruction within four cycles
after SIGRD and SPMEN are set will have no effect. This operation is reserved for future use
and should not be used.
• Bit 4 – RWWSRE: Read-While-Write Section Read Enable
When programming (Page Erase or Page Write) to the RWW section, the RWW section is
blocked for reading (the RWWSB will be set by hardware). To re-enable the RWW section, the
user software must wait until the programming is completed (SPMEN will be cleared). Then, if
the RWWSRE bit is written to one at the same time as SPMEN, the next SPM instruction within
four clock cycles re-enables the RWW section. The RWW section cannot be re-enabled while
the Flash is busy with a Page Erase or a Page Write (SPMEN is set). If the RWWSRE bit is written while the Flash is being loaded, the Flash load operation will abort and the data loaded will
be lost.
• Bit 3 – BLBSET: Boot Lock Bit Set
If this bit is written to one at the same time as SPMEN, the next SPM instruction within four clock
cycles sets Boot Lock bits and Memory Lock bits, according to the data in R0. The data in R1
and the address in the Z-pointer are ignored. The BLBSET bit will automatically be cleared upon
completion of the Lock bit set, or if no SPM instruction is executed within four clock cycles.
An LPM instruction within three cycles after BLBSET and SPMEN are set in the SPMCSR Register, will read either the Lock bits or the Fuse bits (depending on Z0 in the Z-pointer) into the
destination register. See “Reading the Fuse and Lock Bits from Software” on page 288 for
details.
284
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
• Bit 2 – PGWRT: Page Write
If this bit is written to one at the same time as SPMEN, the next SPM instruction within four clock
cycles executes Page Write, with the data stored in the temporary buffer. The page address is
taken from the high part of the Z-pointer. The data in R1 and R0 are ignored. The PGWRT bit
will auto-clear upon completion of a Page Write, or if no SPM instruction is executed within four
clock cycles. The CPU is halted during the entire Page Write operation if the NRWW section is
addressed.
• Bit 1 – PGERS: Page Erase
If this bit is written to one at the same time as SPMEN, the next SPM instruction within four clock
cycles executes Page Erase. The page address is taken from the high part of the Z-pointer. The
data in R1 and R0 are ignored. The PGERS bit will auto-clear upon completion of a Page Erase,
or if no SPM instruction is executed within four clock cycles. The CPU is halted during the entire
Page Write operation if the NRWW section is addressed.
• Bit 0 – SPMEN: Self Programming Enable
This bit enables the SPM instruction for the next four clock cycles. If written to one together with
either RWWSRE, BLBSET, PGWRT or PGERS, the following SPM instruction will have a special meaning, see description above. If only SPMEN is written, the following SPM instruction will
store the value in R1:R0 in the temporary page buffer addressed by the Z-pointer. The LSB of
the Z-pointer is ignored. The SPMEN bit will auto-clear upon completion of an SPM instruction,
or if no SPM instruction is executed within four clock cycles. During Page Erase and Page Write,
the SPMEN bit remains high until the operation is completed.
Writing any other combination than “10001”, “01001”, “00101”, “00011” or “00001” in the lower
five bits will have no effect.
24.6
Addressing the Flash During Self-Programming
The Z-pointer is used to address the SPM commands.
Bit
15
14
13
12
11
10
9
8
ZH (R31)
Z15
Z14
Z13
Z12
Z11
Z10
Z9
Z8
ZL (R30)
Z7
Z6
Z5
Z4
Z3
Z2
Z1
Z0
7
6
5
4
3
2
1
0
Since the Flash is organized in pages (see Table 25-12 on page 303), the Program Counter can
be treated as having two different sections. One section, consisting of the least significant bits, is
addressing the words within a page, while the most significant bits are addressing the pages.
This is1 shown in Figure 24-3. Note that the Page Erase and Page Write operations are
addressed independently. Therefore it is of major importance that the Boot Loader software
addresses the same page in both the Page Erase and Page Write operation. Once a programming operation is initiated, the address is latched and the Z-pointer can be used for other
operations.
The only SPM operation that does not use the Z-pointer is Setting the Boot Loader Lock bits.
The content of the Z-pointer is ignored and will have no effect on the operation. The LPM
instruction does also use the Z-pointer to store the address. Since this instruction addresses the
Flash byte-by-byte, also the LSB (bit Z0) of the Z-pointer is used.
285
7647F–AVR–04/09
Figure 24-3. Addressing the Flash During SPM(1)
BIT
15
ZPCMSB
ZPAGEMSB
Z - REGISTER
1 0
0
PCMSB
PROGRAM
COUNTER
PAGEMSB
PCPAGE
PCWORD
PAGE ADDRESS
WITHIN THE FLASH
PROGRAM MEMORY
PAGE
WORD ADDRESS
WITHIN A PAGE
PAGE
INSTRUCTION WORD
PCWORD[PAGEMSB:0]:
00
01
02
PAGEEND
Note:
24.7
1. The different variables used in Figure 24-3 are listed in Table 24-9 on page 293.
Self-Programming the Flash
The program memory is updated in a page by page fashion. Before programming a page with
the data stored in the temporary page buffer, the page must be erased. The temporary page buffer is filled one word at a time using SPM and the buffer can be filled either before the Page
Erase command or between a Page Erase and a Page Write operation:
Alternative 1, fill the buffer before a Page Erase
• Fill temporary page buffer
• Perform a Page Erase
• Perform a Page Write
Alternative 2, fill the buffer after Page Erase
• Perform a Page Erase
• Fill temporary page buffer
• Perform a Page Write
If only a part of the page needs to be changed, the rest of the page must be stored (for example
in the temporary page buffer) before the erase, and then be rewritten. When using alternative 1,
the Boot Loader provides an effective Read-Modify-Write feature which allows the user software
to first read the page, do the necessary changes, and then write back the modified data. If alternative 2 is used, it is not possible to read the old data while loading since the page is already
erased. The temporary page buffer can be accessed in a random sequence. It is essential that
the page address used in both the Page Erase and Page Write operation is addressing the same
page. See “Simple Assembly Code Example for a Boot Loader” on page 290 for an assembly
code example.
286
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
24.7.1
Performing Page Erase by SPM
To execute Page Erase, set up the address in the Z-pointer, write “X0000011” to SPMCSR and
execute SPM within four clock cycles after writing SPMCSR. The data in R1 and R0 is ignored.
The page address must be written to PCPAGE in the Z-register. Other bits in the Z-pointer will
be ignored during this operation.
• Page Erase to the RWW section: The NRWW section can be read during the Page Erase.
• Page Erase to the NRWW section: The CPU is halted during the operation.
24.7.2
Filling the Temporary Buffer (Page Loading)
To write an instruction word, set up the address in the Z-pointer and data in R1:R0, write
“00000001” to SPMCSR and execute SPM within four clock cycles after writing SPMCSR. The
content of PCWORD in the Z-register is used to address the data in the temporary buffer. The
temporary buffer will auto-erase after a Page Write operation or by writing the RWWSRE bit in
SPMCSR. It is also erased after a system reset. Note that it is not possible to write more than
one time to each address without erasing the temporary buffer.
If the EEPROM is written in the middle of an SPM Page Load operation, all data loaded will be
lost.
24.7.3
Performing a Page Write
To execute Page Write, set up the address in the Z-pointer, write “X0000101” to SPMCSR and
execute SPM within four clock cycles after writing SPMCSR. The data in R1 and R0 is ignored.
The page address must be written to PCPAGE. Other bits in the Z-pointer must be written to
zero during this operation.
• Page Write to the RWW section: The NRWW section can be read during the Page Write.
• Page Write to the NRWW section: The CPU is halted during the operation.
24.7.4
Using the SPM Interrupt
If the SPM interrupt is enabled, the SPM interrupt will generate a constant interrupt when the
SPMEN bit in SPMCSR is cleared. This means that the interrupt can be used instead of polling
the SPMCSR Register in software. When using the SPM interrupt, the Interrupt Vectors should
be moved to the BLS section to avoid that an interrupt is accessing the RWW section when it is
blocked for reading. How to move the interrupts is described in XXXXXXXX.
24.7.5
Consideration While Updating BLS
Special care must be taken if the user allows the Boot Loader section to be updated by leaving
Boot Lock bit11 unprogrammed. An accidental write to the Boot Loader itself can corrupt the
entire Boot Loader, and further software updates might be impossible. If it is not necessary to
change the Boot Loader software itself, it is recommended to program the Boot Lock bit11 to
protect the Boot Loader software from any internal software changes.
287
7647F–AVR–04/09
24.7.6
Prevent Reading the RWW Section During Self-Programming
During Self-Programming (either Page Erase or Page Write), the RWW section is always
blocked for reading. The user software itself must prevent that this section is addressed during
the self programming operation. The RWWSB in the SPMCSR will be set as long as the RWW
section is busy. During Self-Programming the Interrupt Vector table should be moved to the BLS
as described in XXXXXXX, or the interrupts must be disabled. Before addressing the RWW section after the programming is completed, the user software must clear the RWWSB by writing
the RWWSRE. See “Simple Assembly Code Example for a Boot Loader” on page 290 for an
example.
24.7.7
Setting the Boot Loader Lock Bits by SPM
To set the Boot Loader Lock bits, write the desired data to R0, write “X0001001” to SPMCSR
and execute SPM within four clock cycles after writing SPMCSR. The only accessible Lock bits
are the Boot Lock bits that may prevent the Application and Boot Loader section from any software update by the MCU.
Bit
7
6
5
4
3
2
1
0
R0
1
1
BLB12
BLB11
BLB02
BLB01
1
1
See Table 24-2 and Table 24-3 for how the different settings of the Boot Loader bits affect the
Flash access.
If bits 5..2 in R0 are cleared (zero), the corresponding Boot Lock bit will be programmed if an
SPM instruction is executed within four cycles after BLBSET and SPMEN are set in SPMCSR.
The Z-pointer is don’t care during this operation, but for future compatibility it is recommended to
load the Z-pointer with 0x0001 (same as used for reading the lOck bits). For future compatibility it
is also recommended to set bits 7, 6, 1, and 0 in R0 to “1” when writing the Lock bits. When programming the Lock bits the entire Flash can be read during the operation.
24.7.8
EEPROM Write Prevents Writing to SPMCSR
Note that an EEPROM write operation will block all software programming to Flash. Reading the
Fuses and Lock bits from software will also be prevented during the EEPROM write operation. It
is recommended that the user checks the status bit (EEWE) in the EECR Register and verifies
that the bit is cleared before writing to the SPMCSR Register.
24.7.9
Reading the Fuse and Lock Bits from Software
It is possible to read both the Fuse and Lock bits from software. To read the Lock bits, load the
Z-pointer with 0x0001 and set the BLBSET and SPMEN bits in SPMCSR. When an LPM instruction is executed within three CPU cycles after the BLBSET and SPMEN bits are set in SPMCSR,
the value of the Lock bits will be loaded in the destination register. The BLBSET and SPMEN
bits will auto-clear upon completion of reading the Lock bits or if no LPM instruction is executed
within three CPU cycles or no SPM instruction is executed within four CPU cycles. When BLBSET and SPMEN are cleared, LPM will work as described in the Instruction set Manual.
Bit
7
6
5
4
3
2
1
0
Rd
–
–
BLB12
BLB11
BLB02
BLB01
LB2
LB1
The algorithm for reading the Fuse Low byte is similar to the one described above for reading
the Lock bits. To read the Fuse Low byte, load the Z-pointer with 0x0000 and set the BLBSET
and SPMEN bits in SPMCSR. When an LPM instruction is executed within three cycles after the
BLBSET and SPMEN bits are set in the SPMCSR, the value of the Fuse Low byte (FLB) will be
loaded in the destination register as shown below. Refer to Table 25-4 on page 298 for a
detailed description and mapping of the Fuse Low byte.
288
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Bit
7
6
5
4
3
2
1
0
Rd
FLB7
FLB6
FLB5
FLB4
FLB3
FLB2
FLB1
FLB0
Similarly, when reading the Fuse High byte, load 0x0003 in the Z-pointer. When an LPM instruction is executed within three cycles after the BLBSET and SPMEN bits are set in the SPMCSR,
the value of the Fuse High byte (FHB) will be loaded in the destination register as shown below.
Refer to Table 25-6 on page 299 for detailed description and mapping of the Fuse High byte.
Bit
7
6
5
4
3
2
1
0
Rd
FHB7
FHB6
FHB5
FHB4
FHB3
FHB2
FHB1
FHB0
When reading the Extended Fuse byte, load 0x0002 in the Z-pointer. When an LPM instruction
is executed within three cycles after the BLBSET and SPMEN bits are set in the SPMCSR, the
value of the Extended Fuse byte (EFB) will be loaded in the destination register as shown below.
Refer to Table 25-4 on page 298 for detailed description and mapping of the Extended Fuse
byte.
Bit
7
6
5
4
3
2
1
0
Rd
–
–
–
–
EFB3
EFB2
EFB1
EFB0
Fuse and Lock bits that are programmed, will be read as zero. Fuse and Lock bits that are
unprogrammed, will be read as one.
24.7.10
Reading the Signature Row from Software
To read the Signature Row from software, load the Z-pointer with the signature byte address
given in Table 24-5 on page 289 and set the SIGRD and SPMEN bits in SPMCSR. When an
LPM instruction is executed within three CPU cycles after the SIGRD and SPMEN bits are set in
SPMCSR, the signature byte value will be loaded in the destination register. The SIGRD and
SPMEN bits will auto-clear upon completion of reading the Signature Row Lock bits or if no LPM
instruction is executed within three CPU cycles. When SIGRD and SPMEN are cleared, LPM will
work as described in the Instruction set Manual.
Note:
Before attempting to set SPMEN it is important to test this bit is cleared showing that the hardware
is ready for a new operation.
Table 24-5.
Signature Row Addressing
Signature Byte
Z-Pointer Address
Device Signature Byte 1
0x0000
Device Signature Byte 2
0x0002
Device Signature Byte 3
0x0004
RC Oscillator Calibration Byte
0x0001
TSOFFSET Temp Sensor Offset
0x0005
TSGAIN Temp Sensor Gain
0x0007
Note:
All other addresses are reserved for future use.
289
7647F–AVR–04/09
24.7.11
Preventing Flash Corruption
During periods of low VCC, the Flash program can be corrupted because the supply voltage is
too low for the CPU and the Flash to operate properly. These issues are the same as for board
level systems using the Flash, and the same design solutions should be applied.
A Flash program corruption can be caused by two situations when the voltage is too low. First, a
regular write sequence to the Flash requires a minimum voltage to operate correctly. Secondly,
the CPU itself can execute instructions incorrectly, if the supply voltage for executing instructions
is too low.
Flash corruption can easily be avoided by following these design recommendations (one is
sufficient):
1. If there is no need for a Boot Loader update in the system, program the Boot Loader
Lock bits to prevent any Boot Loader software updates.
2. Keep the AVR RESET active (low) during periods of insufficient power supply voltage.
This can be done by enabling the internal Brown-out Detector (BOD) if the operating
voltage matches the detection level. If not, an external low VCC reset protection circuit
can be used. If a reset occurs while a write operation is in progress, the write operation
will be completed provided that the power supply voltage is sufficient.
3. Keep the AVR core in Power-down sleep mode during periods of low VCC. This will prevent the CPU from attempting to decode and execute instructions, effectively protecting
the SPMCSR Register and thus the Flash from unintentional writes.
24.7.12
Programming Time for Flash when Using SPM
The calibrated RC Oscillator is used to time Flash accesses. Table 24-6 shows the typical programming time for Flash accesses from the CPU.
Table 24-6.
24.7.13
SPM Programming Time
Symbol
Min Programming Time
Max Programming Time
Flash write (Page Erase, Page Write, and
write Lock bits by SPM)
3.7 ms
4.5 ms
Simple Assembly Code Example for a Boot Loader
;-the routine writes one page of data from RAM to Flash
; the first data location in RAM is pointed to by the Y pointer
; the first data location in Flash is pointed to by the Z-pointer
;-error handling is not included
;-the routine must be placed inside the Boot space
; (at least the Do_spm sub routine). Only code inside NRWW section can
; be read during Self-Programming (Page Erase and Page Write).
;-registers used: r0, r1, temp1 (r16), temp2 (r17), looplo (r24),
; loophi (r25), spmcrval (r20)
; storing and restoring of registers is not included in the routine
; register usage can be optimized at the expense of code size
;-It is assumed that either the interrupt table is moved to the Boot
; loader section or that the interrupts are disabled.
.equ PAGESIZEB = PAGESIZE*2
;PAGESIZEB is page size in BYTES, not words
.org SMALLBOOTSTART
Write_page:
; Page Erase
ldi spmcrval, (1<<PGERS) | (1<<SPMEN)
call Do_spm
; re-enable the RWW section
290
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
ldi spmcrval, (1<<RWWSRE) | (1<<SPMEN)
call Do_spm
; transfer data from RAM to Flash page buffer
ldi looplo, low(PAGESIZEB)
;init loop variable
ldi loophi, high(PAGESIZEB) ;not required for PAGESIZEB<=256
Wrloop:
ld
r0, Y+
ld
r1, Y+
ldi spmcrval, (1<<SPMEN)
call Do_spm
adiw ZH:ZL, 2
sbiw loophi:looplo, 2
;use subi for PAGESIZEB<=256
brne Wrloop
; execute Page Write
subi ZL, low(PAGESIZEB)
;restore pointer
sbci ZH, high(PAGESIZEB)
;not required for PAGESIZEB<=256
ldi spmcrval, (1<<PGWRT) | (1<<SPMEN)
call Do_spm
; re-enable the RWW section
ldi spmcrval, (1<<RWWSRE) | (1<<SPMEN)
call Do_spm
; read back and check, optional
ldi looplo, low(PAGESIZEB)
;init loop variable
ldi loophi, high(PAGESIZEB) ;not required for PAGESIZEB<=256
subi YL, low(PAGESIZEB)
;restore pointer
sbci YH, high(PAGESIZEB)
Rdloop:
lpm r0, Z+
ld
r1, Y+
cpse r0, r1
jmp Error
sbiw loophi:looplo, 1
;use subi for PAGESIZEB<=256
brne Rdloop
; return to RWW section
; verify that RWW section is safe to read
Return:
in
temp1, SPMCSR
sbrs temp1, RWWSB
; If RWWSB is set, the RWW section is not ready yet
ret
; re-enable the RWW section
ldi spmcrval, (1<<RWWSRE) | (1<<SPMEN)
call Do_spm
rjmp Return
Do_spm:
; check for previous SPM complete
Wait_spm:
in
temp1, SPMCSR
sbrc temp1, SPMEN
rjmp Wait_spm
; input: spmcrval determines SPM action
; disable interrupts if enabled, store status
in
temp2, SREG
cli
291
7647F–AVR–04/09
; check that no EEPROM write access is present
Wait_ee:
sbic EECR, EEPE
rjmp Wait_ee
; SPM timed sequence
out SPMCSR, spmcrval
spm
; restore SREG (to enable interrupts if originally enabled)
out SREG, temp2
ret
24.7.14
ATmega16/32/64/M1/C1 - 16K -Flash Boot Loader Parameters
In Table 24-7 through Table 24-9, the parameters used in the description of the self programming are given.
Table 24-7.
BOOTSZ1
Boot Size Configuration, ATmega16/32/64/M1/C1 (16K product)
BOOTSZ0
Boot
Size(2)
Pages
Application
Flash
Section
Boot
Loader
Flash
Section
End
Application
Section
Boot Reset
Address
(Start Boot
Loader
Section)
1
1
256
words
4
0x0000 0x1EFF
0x1F00 0x1FFF
0x1EFF
0x1F00
1
0
512
words
8
0x0000 0x1DFF
0x1E00 0x1FFF
0x1DFF
0x1E00
0
1
1024
words
16
0x0000 0x1BFF
0x1C00 0x1FFF
0x1BFF
0x1C00
0
0
2048
words
32
0x0000 0x17FF
0x1800 0x1FFF
0x17FF
0x1800
Notes:
1. The different BOOTSZ Fuse configurations are shown in Figure 24-2.
2. 1 word equals 2 bytes.
Table 24-8.
Read-While-Write Limit
Section
Pages
Address
Read-While-Write section (RWW)
96
0x0000 - 0x17FF
No Read-While-Write section (NRWW)
32
0x1800 - 0x1FFF
For details about these two section, see “NRWW – No Read-While-Write Section” on page 280
and “RWW – Read-While-Write Section” on page 280.
292
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 24-9.
Explanation of Different Variables used in Figure 24-3 and the Mapping to the
Z-pointer
Corresponding
Z-value(Note:)
Variable
PCMSB
12
PAGEMSB
5
Most significant bit in the Program Counter. (The Program
Counter is 13 bits PC[2:0])
Most significant bit which is used to address the words within
one page (64 words in a page requires 6 bits PC [5:0]).
ZPCMSB
Z13
Bit in Z-register that is mapped to PCMSB. Because Z0 is not
used, the ZPCMSB equals PCMSB + 1.
ZPAGEMSB
Z6
Bit in Z-register that is mapped to PAGEMSB. Because Z0 is
not used, the ZPAGEMSB equals PAGEMSB + 1.
PCPAGE
PC[12:6]
Z13:Z7
Program counter page address: Page select, for page erase
and page write
PCWORD
PC[5:0]
Z6:Z1
Program counter word address: Word select, for filling
temporary buffer (must be zero during page write operation)
Note:
24.7.15
Description
Z15:Z13: always ignored
Z0: should be zero for all SPM commands, byte select for the LPM instruction.
See “Addressing the Flash During Self-Programming” on page 285 for details about the use of
Z-pointer during Self-Programming.
ATmega16/32/64/M1/C1 - 32K -Flash Boot Loader Parameters
In Table 24-7 through Table 24-9, the parameters used in the description of the self programming are given.
Table 24-10. Boot Size Configuration, ATmega16/32/64/M1/C1 (32K product)
BOOTSZ1
Note:
BOOTSZ0
Boot
Size(2)
Pages
Application
Flash
Section
Boot
Loader
Flash
Section
End
Application
Section
Boot Reset
Address
(Start Boot
Loader
Section)
1
1
256
words
4
0x0000 0x3EFF
0x3F00 0x3FFF
0x3EFF
0x3F00
1
0
512
words
8
0x0000 0x3DFF
0x3E00 0x3FFF
0x3DFF
0x3E00
0
1
1024
words
16
0x0000 0x3BFF
0x3C00 0x3FFF
0x3BFF
0x3C00
0
0
2048
words
32
0x0000 0x37FF
0x3800 0x3FFF
0x37FF
0x3800
1. The different BOOTSZ Fuse configurations are shown in Figure 24-2.
2. 1 word equals 2 bytes.
Table 24-11. Read-While-Write Limit
Section
Pages
Address
Read-While-Write section (RWW)
224
0x0000 - 0x37FF
No Read-While-Write section (NRWW)
32
0x3800 - 0x3FFF
For details about these two section, see “NRWW – No Read-While-Write Section” on page 280
and “RWW – Read-While-Write Section” on page 280.
293
7647F–AVR–04/09
Table 24-12. Explanation of Different Variables used in Figure 24-3 and the Mapping to the
Z-pointer
Corresponding
Z-value(Note:)
Variable
PCMSB
13
PAGEMSB
5
Most significant bit in the Program Counter. (The Program
Counter is 14 bits PC[13:0])
Most significant bit which is used to address the words within
one page (64 words in a page requires 6 bits PC [5:0]).
ZPCMSB
Z14
Bit in Z-register that is mapped to PCMSB. Because Z0 is not
used, the ZPCMSB equals PCMSB + 1.
ZPAGEMSB
Z6
Bit in Z-register that is mapped to PAGEMSB. Because Z0 is
not used, the ZPAGEMSB equals PAGEMSB + 1.
PCPAGE
PC[13:6]
Z14:Z7
Program counter page address: Page select, for page erase
and page write
PCWORD
PC[5:0]
Z6:Z1
Program counter word address: Word select, for filling
temporary buffer (must be zero during page write operation)
Note:
24.7.16
Description
Z15:Z13: always ignored
Z0: should be zero for all SPM commands, byte select for the LPM instruction.
See “Addressing the Flash During Self-Programming” on page 285 for details about the use of
Z-pointer during Self-Programming.
ATmega16/32/64/M1/C1 - 64K - Flash Boot Loader Parameters
In Table 24-7 through Table 24-9, the parameters used in the description of the self programming are given.
Table 24-13. Boot Size Configuration, ATmega16/32/64/M1/C1 (64K product)
BOOTSZ1
Note:
BOOTSZ0
Boot
Size(2)
Pages
Application
Flash
Section
Boot
Loader
Flash
Section
End
Application
Section
Boot Reset
Address
(Start Boot
Loader
Section)
1
1
512
words
4
0x0000 0x7DFF
0x7E00 0x7FFF
0x7DFF
0x7E00
1
0
1024
words
8
0x0000 0x7BFF
0x7C00 0x7FFF
0x7BFF
0x7C00
0
1
2048
words
16
0x0000 0x77FF
0x7800 0x7FFF
0x77FF
0x7800
0
0
4096
words
32
0x0000 0x6FFF
0x7000 0x7FFF
0x6FFF
0x7000
1. The different BOOTSZ Fuse configurations are shown in Figure 24-2.
2. 1 word equals 2 bytes.
Table 24-14. Read-While-Write Limit
Section
294
Pages
Address
Read-While-Write section (RWW)
224
0x0000 - 0x6FFF
No Read-While-Write section (NRWW)
32
0x7000 - 0x7FFF
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
For details about these two section, see “NRWW – No Read-While-Write Section” on page 280
and “RWW – Read-While-Write Section” on page 280.
Table 24-15. Explanation of Different Variables used in Figure 24-3 and the Mapping to the
Z-pointer
Corresponding
Z-value(Note:)
Variable
PCMSB
14
PAGEMSB
7
Description
Most significant bit in the Program Counter. (The Program
Counter is 15 bits PC[14:0])
Most significant bit which is used to address the words within
one page (128 words in a page requires seven bits PC [6:0]).
ZPCMSB
Z15
Bit in Z-register that is mapped to PCMSB. Because Z0 is not
used, the ZPCMSB equals PCMSB + 1.
ZPAGEMSB
Z8
Bit in Z-register that is mapped to PAGEMSB. Because Z0 is
not used, the ZPAGEMSB equals PAGEMSB + 1.
PCPAGE
PC[14:7]
Z15:Z8
Program counter page address: Page select, for page erase
and page write
PCWORD
PC[6:0]
Z7:Z1
Program counter word address: Word select, for filling
temporary buffer (must be zero during page write operation)
Note:
Z15:Z13: always ignored
Z0: should be zero for all SPM commands, byte select for the LPM instruction.
See “Addressing the Flash During Self-Programming” on page 285 for details about the use of
Z-pointer during Self-Programming.
295
7647F–AVR–04/09
25. Memory Programming
25.1
Program And Data Memory Lock Bits
The ATmega16/32/64/M1/C1 provides six Lock bits which can be left unprogrammed (“1”) or can
be programmed (“0”) to obtain the additional features listed in Table 25-2. The Lock bits can only
be erased to “1” with the Chip Erase command.
Table 25-1.
Lock Bit Byte(1)
Lock Bit Byte
Description
Default Value
7
–
1 (unprogrammed)
6
–
1 (unprogrammed)
BLB12
5
Boot Lock bit
1 (unprogrammed)
BLB11
4
Boot Lock bit
1 (unprogrammed)
BLB02
3
Boot Lock bit
1 (unprogrammed)
BLB01
2
Boot Lock bit
1 (unprogrammed)
LB2
1
Lock bit
1 (unprogrammed)
LB1
0
Lock bit
1 (unprogrammed)
Notes:
1. “1” means unprogrammed, “0” means programmed.
Table 25-2.
Bit No
Lock Bit Protection Modes(1)(2)
Memory Lock Bits
Protection Type
LB Mode
LB2
LB1
1
1
1
No memory lock features enabled.
2
1
0
Further programming of the Flash and EEPROM is disabled in
Parallel and Serial Programming mode. The Fuse bits are
locked in both Serial and Parallel Programming mode.(1)
0
Further programming and verification of the Flash and
EEPROM is disabled in Parallel and Serial Programming mode.
The Boot Lock bits and Fuse bits are locked in both Serial and
Parallel Programming mode.(1)
3
Notes:
0
1. Program the Fuse bits and Boot Lock bits before programming the LB1 and LB2.
2. “1” means unprogrammed, “0” means programmed
296
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 25-3.
Lock Bit Protection Modes(1)(2).
BLB0 Mode
BLB02
BLB01
1
1
1
No restrictions for SPM or LPM accessing the Application
section.
2
1
0
SPM is not allowed to write to the Application section.
0
SPM is not allowed to write to the Application section, and LPM
executing from the Boot Loader section is not allowed to read
from the Application section. If Interrupt Vectors are placed in
the Boot Loader section, interrupts are disabled while executing
from the Application section.
LPM executing from the Boot Loader section is not allowed to
read from the Application section. If Interrupt Vectors are placed
in the Boot Loader section, interrupts are disabled while
executing from the Application section.
3
0
4
0
1
BLB1 Mode
BLB12
BLB11
1
1
1
No restrictions for SPM or LPM accessing the Boot Loader
section.
2
1
0
SPM is not allowed to write to the Boot Loader section.
0
SPM is not allowed to write to the Boot Loader section, and LPM
executing from the Application section is not allowed to read
from the Boot Loader section. If Interrupt Vectors are placed in
the Application section, interrupts are disabled while executing
from the Boot Loader section.
1
LPM executing from the Application section is not allowed to
read from the Boot Loader section. If Interrupt Vectors are
placed in the Application section, interrupts are disabled while
executing from the Boot Loader section.
3
4
Notes:
0
0
1. Program the Fuse bits and Boot Lock bits before programming the LB1 and LB2.
2. “1” means unprogrammed, “0” means programmed
25.2
Fuse Bits
The ATmega16/32/64/M1/C1 has three Fuse bytes. Table 25-4 - Table 25-7 describe briefly the
functionality of all the fuses and how they are mapped into the Fuse bytes. Note that the fuses
are read as logical zero, “0”, if they are programmed.
297
7647F–AVR–04/09
Table 25-4.
Extended Fuse Byte
Extended Fuse Byte
Description
Default Value
-
7
-
1 (unprogrammed)
-
6
-
1 (unprogrammed)
PSCRB
5
PSC Reset Behaviour
1 (unprogrammed)
PSCRVA
4
PSCOUTnA Reset Value
1 (unprogrammed)
PSCRVB
3
PSCOUTnB Reset Value
1 (unprogrammed)
BODLEVEL2(1)
2
Brown-out Detector trigger
level
1 (unprogrammed)
BODLEVEL1(1)
1
Brown-out Detector trigger
level
1 (unprogrammed)
BODLEVEL0(1)
0
Brown-out Detector trigger
level
1 (unprogrammed)
Note:
25.3
Bit No
1. See Table 7-2 on page 49 for BODLEVEL Fuse decoding.
PSC Output Behavior During Reset
For external component safety reason, the state of PSC outputs during Reset can be programmed by fuses PSCRB, PSCARV & PSCBRV.
These fuses are located in the Extended Fuse Byte ( see Table 25-4)
If PSCRB fuse equals 1 (unprogrammed), all PSC outputs keep a standard port behaviour. If
PSC0RB fuse equals 0 (programmed), all PSC outputs are forced at reset to low level or high
level according to PSCARV and PSCBRV fuse bits. In this second case, the PSC outputs keep
the forced state until POC register is written. See “Clock Prescaler Register – CLKPR” on page
38.
PSCARV (PSCOUTnA Reset Value) gives the state low or high which will be forced on
PSCOUT0A, PSCOUT1A and PSCOUT2A outputs when PSCRB is programmed. If PSCARV
fuse equals 0 (programmed), the PSCOUT0A, PSCOUT1A and PSCOUT2A outputs will be
forced to high state. If PSCRV fuse equals 1 (unprogrammed), the PSCOUT0A, PSCOUT1A
and PSCOUT2A outputs will be forced to low state.
PSCBRV (PSCOUTnB Reset Value) gives the state low or high which will be forced on
PSCOUT0B, PSCOUT1B and PSCOUT2B outputs when PSCRB is programmed. If PSCBRV
fuse equals 0 (programmed), the PSCOUT0B, PSCOUT1B and PSCOUT2B outputs will be
forced to high state. If PSCRV fuse equals 1 (unprogrammed), the PSCOUT0B, PSCOUT1B
and PSCOUT2B outputs will be forced to low state.
298
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 25-5.
PSC Output Behavior During and after Reset until POC register is written
PSCRB
PSCARV
PSCBRV
PSCOUTnA
PSCOUTnB
X
X
normal port
normal port
programmed
unprogrammed
unprogrammed
forced low
forced low
programmed
unprogrammed
programmed
forced low
forced high
programmed
programmed
unprogrammed
forced high
forced low
programmed
programmed
programmed
forced high
forced high
BODLEVEL2(1)
2
Brown-out
Detector
trigger level
1
(unprogramme
d)
BODLEVEL1(1)
1
Brown-out
Detector
trigger level
1
(unprogramme
d)
BODLEVEL0(1)
0
Brown-out
Detector
trigger level
1
(unprogramme
d)
unprogrammed
Table 25-6.
Fuse High Byte
High Fuse Byte
Bit No
Description
Default Value
RSTDISBL(1)
7
External Reset Disable
1 (unprogrammed)
DWEN
6
debugWIRE Enable
1 (unprogrammed)
SPIEN(2)
5
Enable Serial Program and
Data Downloading
0 (programmed, SPI
programming enabled)
WDTON(3)
4
Watchdog Timer Always On
1 (unprogrammed)
EESAVE
3
EEPROM memory is
preserved through the Chip
Erase
1 (unprogrammed), EEPROM
not reserved
BOOTSZ1
2
Select Boot Size
(see Table 113 for details)
0 (programmed)(4)
BOOTSZ0
1
Select Boot Size
(see Table 113 for details)
0 (programmed)(4)
BOOTRST
0
Select Reset Vector
1 (unprogrammed)
Note:
1. See “Alternate Functions of Port C” on page 72 for description of RSTDISBL Fuse.
2. The SPIEN Fuse is not accessible in serial programming mode.
3. See “Watchdog Timer Configuration” on page 55 for details.
4. The default value of BOOTSZ1..0 results in maximum Boot Size. See Table 25-8 on page 302
for details
299
7647F–AVR–04/09
.
Table 25-7.
Fuse Low Byte
Low Fuse Byte
Description
Default Value
7
Divide clock by 8
0 (programmed)
6
Clock output
1 (unprogrammed)
SUT1
5
Select start-up time
1 (unprogrammed)(1)
SUT0
4
Select start-up time
0 (programmed)(1)
CKSEL3
3
Select Clock source
0 (programmed)(2)
CKSEL2
2
Select Clock source
0 (programmed)(2)
CKSEL1
1
Select Clock source
1 (unprogrammed)(2)
CKSEL0
0
Select Clock source
0 (programmed)(2)
(4)
(3)
Bit No
CKDIV8
CKOUT
Notes:
1. The default value of SUT1..0 results in maximum start-up time for the default clock source.
See Table 5-9 on page 37 for details.
2. The default setting of CKSEL3..0 results in internal RC Oscillator @ 8 MHz. See Table 5-9 on
page 37 for details.
3. The CKOUT Fuse allows the system clock to be output on PORTB0. See “Clock Output Buffer”
on page 37 for details.
4. See “System Clock Prescaler” on page 37 for details.
The status of the Fuse bits is not affected by Chip Erase. Note that the Fuse bits are locked if
Lock bit1 (LB1) is programmed. Program the Fuse bits before programming the Lock bits.
25.3.1
25.4
Latching of Fuses
The fuse values are latched when the device enters programming mode and changes of the
fuse values will have no effect until the part leaves Programming mode. This does not apply to
the EESAVE Fuse which will take effect once it is programmed. The fuses are also latched on
Power-up in Normal mode.
Signature Bytes
All Atmel microcontrollers have a three-byte signature code which identifies the device. This
code can be read in both serial and parallel mode, also when the device is locked. The three
bytes reside in a separate address space.
25.4.1
Signature Bytes
For the ATmega16M1 the signature bytes are:
1. 0x000: 0x1E (indicates manufactured by Atmel).
2. 0x001: 0x94 (indicates 16KB Flash memory).
3. 0x002: 0x84 (indicates ATmega16M1 device when 0x001 is 0x94).
For the ATmega32M1 the signature bytes are:
1. 0x000: 0x1E (indicates manufactured by Atmel).
2. 0x001: 0x95 (indicates 32KB Flash memory).
3. 0x002: 0x84 (indicates ATmega32M1 device when 0x001 is 0x95).
300
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
For the ATmega64M1 the signature bytes are:
1. 0x000: 0x1E (indicates manufactured by Atmel).
2. 0x001: 0x96 (indicates 64KB Flash memory).
3. 0x002: 0x84 (indicates ATmega64M1 device when 0x001 is 0x96).
For the ATmega32C1 the signature bytes are:
1. 0x000: 0x1E (indicates manufactured by Atmel).
2. 0x001: 0x95 (indicates 32KB Flash memory).
3. 0x002: 0x86 (indicates ATmega32C1 device when 0x001 is 0x95).
For the ATmega64C1 the signature bytes are:
1. 0x000: 0x1E (indicates manufactured by Atmel).
2. 0x001: 0x96 (indicates 32KB Flash memory).
3. 0x002: 0x86 (indicates ATmega64C1 device when 0x001 is 0x96).
25.5
Calibration Byte
The ATmega16/32/64/M1/C1 has a byte calibration value for the internal RC Oscillator. This
byte resides in the high byte of address 0x000 in the signature address space. During reset, this
byte is automatically written into the OSCCAL Register to ensure correct frequency of the calibrated RC Oscillator.
25.6
Parallel Programming Parameters, Pin Mapping, and Commands
This section describes how to parallel program and verify Flash Program memory, EEPROM
Data memory, Memory Lock bits, and Fuse bits in the ATmega16/32/64/M1/C1. Pulses are
assumed to be at least 250 ns unless otherwise noted.
25.6.1
Signal Names
In this section, some pins of the ATmega16/32/64/M1/C1 are referenced by signal names
describing their functionality during parallel programming, see Figure 25-1 and Table 25-8. Pins
not described in the following table are referenced by pin names.
The XA1/XA0 pins determine the action executed when the XTAL1 pin is given a positive pulse.
The bit coding is shown in Table 25-10.
When pulsing WR or OE, the command loaded determines the action executed. The different
Commands are shown in Table 25-11.
301
7647F–AVR–04/09
Figure 25-1. Parallel Programming
+ 5V
RDY/BSY
PD1
OE
PD2
WR
PD3
BS1
PD4
XA0
PD5
VCC
XA1
PAGEL
+ 12 V
+ 5V
AVCC
PB[7:0]
PD6
DATA
PD7
RESET
BS2
PE2
XTAL1
GND
Table 25-8.
Pin Name Mapping
Signal Name in
Programming Mode
Pin Name
I/O
Function
RDY/BSY
PD1
O
0: Device is busy programming, 1: Device is
ready for new command
OE
PD2
I
Output Enable (Active low)
WR
PD3
I
Write Pulse (Active low)
BS1
PD4
I
Byte Select 1 (“0” selects Low byte, “1” selects
High byte)
XA0
PD5
I
XTAL Action Bit 0
XA1
PD6
I
XTAL Action Bit 1
PAGEL
PD7
I
Program memory and EEPROM Data Page
Load
BS2
PE2
I
Byte Select 2 (“0” selects Low byte, “1” selects
2’nd High byte)
DATA
PB[7:0]
I/O
Table 25-9.
302
Bi-directional Data bus (Output when OE is
low)
Pin Values Used to Enter Programming Mode
Pin
Symbol
Value
PAGEL
Prog_enable[3]
0
XA1
Prog_enable[2]
0
XA0
Prog_enable[1]
0
BS1
Prog_enable[0]
0
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 25-10. XA1 and XA0 Coding
XA1
XA0
Action when XTAL1 is Pulsed
0
0
Load Flash or EEPROM Address (High or low address byte determined by
BS1).
0
1
Load Data (High or Low data byte for Flash determined by BS1).
1
0
Load Command
1
1
No Action, Idle
Table 25-11. Command Byte Bit Coding
Command Byte
Command Executed
1000 0000
Chip Erase
0100 0000
Write Fuse bits
0010 0000
Write Lock bits
0001 0000
Write Flash
0001 0001
Write EEPROM
0000 1000
Read Signature Bytes and Calibration byte
0000 0100
Read Fuse and Lock bits
0000 0010
Read Flash
0000 0011
Read EEPROM
Table 25-12. No. of Words in a Page and No. of Pages in the Flash
Device
Flash Size
Page Size
PCWORD
No. of
Pages
PCPAGE
PCMSB
ATmega16M1
8K words
(16K bytes)
64 words
(128 bytes)
PC[5:0]
128
PC[12:6]
12
ATmega32M1/C1
16K words
(32K bytes)
64 words
(128 bytes)
PC[5:0]
256
PC[13:6]
13
ATmega64M1/C1
32K words
(64K bytes)
128 words
(256 bytes)
PC[6:0]
256
PC[14:7]
14
Table 25-13. No. of Words in a Page and No. of Pages in the EEPROM
Device
EEPROM
Size
Page
Size
PCWORD
No. of
Pages
PCPAGE
EEAMSB
ATmega16M1
512 bytes
4 bytes
EEA[1:0]
128
EEA[8:2]
9
ATmega32M1/C1
1024 bytes
4 bytes
EEA[1:0]
256
EEA[9:2]
9
ATmega64M1/C1
2048 bytes
8 bytes
EEA[2:0]
256
EEA[9:2]
9
303
7647F–AVR–04/09
25.7
Serial Programming Pin Mapping
Table 25-14. Pin Mapping Serial Programming
25.8
25.8.1
Symbol
Pins
I/O
Description
MOSI_A
PD3
I
Serial Data in
MISO_A
PD2
O
Serial Data out
SCK_A
PD4
I
Serial Clock
Parallel Programming
Enter Programming Mode
The following algorithm puts the device in Parallel (High-voltage) > Programming mode:
1. Set Prog_enable pins listed in Table 25-9. to “0000”, RESET pin to “0” and VCC to 0V.
2. Apply 4.5 - 5.5V between VCC and GND. Ensure that VCC reaches at least 1.8V within
the next 20µs.
3. Wait 20 - 60µs, and apply 11.5 - 12.5V to RESET.
4. Keep the Prog_enable pins unchanged for at least 10µs after the High-voltage has
been applied to ensure the Prog_enable Signature has been latched.
5. Wait at least 300µs before giving any parallel programming commands.
6. Exit Programming mode by power the device down or by bringing RESET pin to 0V.
If the rise time of the VCC is unable to fulfill the requirements listed above, the following alternative algorithm can be used.
1. Set Prog_enable pins listed in Table 25-9. to “0000”, RESET pin to “0” and VCC to 0V.
2. Apply 4.5 - 5.5V between VCC and GND.
3. Monitor VCC, and as soon as VCC reaches 0.9 - 1.1V, apply 11.5 - 12.5V to RESET.
4. Keep the Prog_enable pins unchanged for at least 10µs after the High-voltage has
been applied to ensure the Prog_enable Signature has been latched.
5. Wait until VCC actually reaches 4.5 -5.5V before giving any parallel programming
commands.
6. Exit Programming mode by power the device down or by bringing RESET pin to 0V.
25.8.2
Considerations for Efficient Programming
The loaded command and address are retained in the device during programming. For efficient
programming, the following should be considered.
• The command needs only be loaded once when writing or reading multiple memory
locations.
• Skip writing the data value 0xFF, that is the contents of the entire EEPROM (unless the
EESAVE Fuse is programmed) and Flash after a Chip Erase.
• Address high byte needs only be loaded before programming or reading a new 256 word
window in Flash or 256 byte EEPROM. This consideration also applies to Signature bytes
reading.
304
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
25.8.3
Chip Erase
The Chip Erase will erase the Flash and EEPROM(1) memories plus Lock bits. The Lock bits are
not reset until the program memory has been completely erased. The Fuse bits are not
changed. A Chip Erase must be performed before the Flash and/or EEPROM are
reprogrammed.
Note:
1. The EEPRPOM memory is preserved during Chip Erase if the EESAVE Fuse is programmed.
Load Command “Chip Erase”
1. Set XA1, XA0 to “10”. This enables command loading.
2. Set BS1 to “0”.
3. Set DATA to “1000 0000”. This is the command for Chip Erase.
4. Give XTAL1 a positive pulse. This loads the command.
5. Give WR a negative pulse. This starts the Chip Erase. RDY/BSY goes low.
6. Wait until RDY/BSY goes high before loading a new command.
25.8.4
Programming the Flash
The Flash is organized in pages, see Table 25-12 on page 303. When programming the Flash,
the program data is latched into a page buffer. This allows one page of program data to be programmed simultaneously. The following procedure describes how to program the entire Flash
memory:
A. Load Command “Write Flash”
1. Set XA1, XA0 to “10”. This enables command loading.
2. Set BS1 to “0”.
3. Set DATA to “0001 0000”. This is the command for Write Flash.
4. Give XTAL1 a positive pulse. This loads the command.
B. Load Address Low byte
1. Set XA1, XA0 to “00”. This enables address loading.
2. Set BS1 to “0”. This selects low address.
3. Set DATA = Address low byte (0x00 - 0xFF).
4. Give XTAL1 a positive pulse. This loads the address low byte.
C. Load Data Low Byte
5. Set XA1, XA0 to “01”. This enables data loading.
6. Set DATA = Data low byte (0x00 - 0xFF).
7. Give XTAL1 a positive pulse. This loads the data byte.
D. Load Data High Byte
1. Set BS1 to “1”. This selects high data byte.
2. Set XA1, XA0 to “01”. This enables data loading.
3. Set DATA = Data high byte (0x00 - 0xFF).
4. Give XTAL1 a positive pulse. This loads the data byte.
E. Latch Data
1. Set BS1 to “1”. This selects high data byte.
2. Give PAGEL a positive pulse. This latches the data bytes. (See Figure 25-3 for signal
waveforms)
305
7647F–AVR–04/09
F. Repeat B through E until the entire buffer is filled or until all data within the page is loaded.
While the lower bits in the address are mapped to words within the page, the higher bits address
the pages within the FLASH. This is illustrated in Figure 25-2 on page 306. Note that if less than
eight bits are required to address words in the page (pagesize < 256), the most significant bit(s)
in the address low byte are used to address the page when performing a Page Write.
G. Load Address High byte
1. Set XA1, XA0 to “00”. This enables address loading.
2. Set BS1 to “1”. This selects high address.
3. Set DATA = Address high byte (0x00 - 0xFF).
4. Give XTAL1 a positive pulse. This loads the address high byte.
H. Program Page
1. Give WR a negative pulse. This starts programming of the entire page of data.
RDY/BSY goes low.
2. Wait until RDY/BSY goes high (See Figure 25-3 for signal waveforms).
I. Repeat B through H until the entire Flash is programmed or until all data has been
programmed.
J. End Page Programming
1. 1. Set XA1, XA0 to “10”. This enables command loading.
2. Set DATA to “0000 0000”. This is the command for No Operation.
3. Give XTAL1 a positive pulse. This loads the command, and the internal write signals
are reset.
Figure 25-2. Addressing the Flash Which is Organized in Pages(1)
PCMSB
PROGRAM
COUNTER
PAGEMSB
PCPAGE
PAGE ADDRESS
WITHIN THE FLASH
PROGRAM MEMORY
PAGE
PCWORD
WORD ADDRESS
WITHIN A PAGE
PAGE
INSTRUCTION WORD
PCWORD[PAGEMSB:0]:
00
01
02
PAGEEND
Note:
306
1. PCPAGE and PCWORD are listed in Table 25-12 on page 303.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 25-3. Programming the Flash Waveforms(1)
F
DATA
A
B
0x10
ADDR. LOW
C
DATA LOW
D
E
DATA HIGH
XX
B
ADDR. LOW
C
D
DATA LOW
DATA HIGH
E
XX
G
ADDR. HIGH
H
XX
XA1
XA0
BS1
XTAL1
WR
RDY/BSY
RESET +12V
OE
PAGEL
BS2
Note:
25.8.5
1. “XX” is don’t care. The letters refer to the programming description above.
Programming the EEPROM
The EEPROM is organized in pages, see Table 25-13 on page 303. When programming the
EEPROM, the program data is latched into a page buffer. This allows one page of data to be
programmed simultaneously. The programming algorithm for the EEPROM data memory is as
follows (refer to “Programming the Flash” on page 305 for details on Command, Address and
Data loading):
1. A: Load Command “0001 0001”.
2. G: Load Address High Byte (0x00 - 0xFF).
3. B: Load Address Low Byte (0x00 - 0xFF).
4. C: Load Data (0x00 - 0xFF).
5. E: Latch data (give PAGEL a positive pulse).
K: Repeat 3 through 5 until the entire buffer is filled.
L: Program EEPROM page
1. Set BS1 to “0”.
2. Give WR a negative pulse. This starts programming of the EEPROM page. RDY/BSY
goes low.
3. Wait until to RDY/BSY goes high before programming the next page (See Figure 25-4
for signal waveforms).
307
7647F–AVR–04/09
Figure 25-4. Programming the EEPROM Waveforms
K
DATA
A
G
0x11
ADDR. HIGH
B
ADDR. LOW
C
DATA
E
XX
B
ADDR. LOW
C
DATA
E
L
XX
XA1
XA0
BS1
XTAL1
WR
RDY/BSY
RESET +12V
OE
PAGEL
BS2
25.8.6
Reading the Flash
The algorithm for reading the Flash memory is as follows (refer to “Programming the Flash” on
page 305 for details on Command and Address loading):
1. A: Load Command “0000 0010”.
2. G: Load Address High Byte (0x00 - 0xFF).
3. B: Load Address Low Byte (0x00 - 0xFF).
4. Set OE to “0”, and BS1 to “0”. The Flash word low byte can now be read at DATA.
5. Set BS1 to “1”. The Flash word high byte can now be read at DATA.
6. Set OE to “1”.
25.8.7
Reading the EEPROM
The algorithm for reading the EEPROM memory is as follows (refer to “Programming the Flash”
on page 305 for details on Command and Address loading):
1. A: Load Command “0000 0011”.
2. G: Load Address High Byte (0x00 - 0xFF).
3. B: Load Address Low Byte (0x00 - 0xFF).
4. Set OE to “0”, and BS1 to “0”. The EEPROM Data byte can now be read at DATA.
5. Set OE to “1”.
25.8.8
Programming the Fuse Low Bits
The algorithm for programming the Fuse Low bits is as follows (refer to “Programming the Flash”
on page 305 for details on Command and Data loading):
1. A: Load Command “0100 0000”.
2. C: Load Data Low Byte. Bit n = “0” programs and bit n = “1” erases the Fuse bit.
3. Give WR a negative pulse and wait for RDY/BSY to go high.
308
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
25.8.9
Programming the Fuse High Bits
The algorithm for programming the Fuse High bits is as follows (refer to “Programming the
Flash” on page 305 for details on Command and Data loading):
1. A: Load Command “0100 0000”.
2. C: Load Data Low Byte. Bit n = “0” programs and bit n = “1” erases the Fuse bit.
3. Set BS1 to “1” and BS2 to “0”. This selects high data byte.
4. Give WR a negative pulse and wait for RDY/BSY to go high.
5. Set BS1 to “0”. This selects low data byte.
25.8.10
Programming the Extended Fuse Bits
The algorithm for programming the Extended Fuse bits is as follows (refer to “Programming the
Flash” on page 305 for details on Command and Data loading):
1. A: Load Command “0100 0000”.
2. C: Load Data Low Byte. Bit n = “0” programs and bit n = “1” erases the Fuse bit.
3. Set BS1 to “0” and BS2 to “1”. This selects extended data byte.
4. Give WR a negative pulse and wait for RDY/BSY to go high.
5. Set BS2 to “0”. This selects low data byte.
Figure 25-5. Programming the FUSES Waveforms
Write Fuse Low byte
DATA
A
C
0x40
DATA
XX
Write Fuse high byte
A
C
0x40
DATA
XX
Write Extended Fuse byte
A
C
0x40
DATA
XX
XA1
XA0
BS1
BS2
XTAL1
WR
RDY/BSY
RESET +12V
OE
PAGEL
309
7647F–AVR–04/09
25.8.11
Programming the Lock Bits
The algorithm for programming the Lock bits is as follows (refer to “Programming the Flash” on
page 305 for details on Command and Data loading):
1. A: Load Command “0010 0000”.
2. C: Load Data Low Byte. Bit n = “0” programs the Lock bit. If LB mode 3 is programmed
(LB1 and LB2 is programmed), it is not possible to program the Boot Lock bits by any
External Programming mode.
3. Give WR a negative pulse and wait for RDY/BSY to go high.
The Lock bits can only be cleared by executing Chip Erase.
25.8.12
Reading the Fuse and Lock Bits
The algorithm for reading the Fuse and Lock bits is as follows (refer to “Programming the Flash”
on page 305 for details on Command loading):
1. A: Load Command “0000 0100”.
2. Set OE to “0”, BS2 to “0” and BS1 to “0”. The status of the Fuse Low bits can now be
read at DATA (“0” means programmed).
3. Set OE to “0”, BS2 to “1” and BS1 to “1”. The status of the Fuse High bits can now be
read at DATA (“0” means programmed).
4. Set OE to “0”, BS2 to “1”, and BS1 to “0”. The status of the Extended Fuse bits can now
be read at DATA (“0” means programmed).
5. Set OE to “0”, BS2 to “0” and BS1 to “1”. The status of the Lock bits can now be read at
DATA (“0” means programmed).
6. Set OE to “1”.
Figure 25-6. Mapping Between BS1, BS2 and the Fuse and Lock Bits During Read
Fuse Low Byte
0
Extended Fuse Byte
1
0
DATA
BS2
0
Lock Bits
1
Fuse High Byte
1
BS1
BS2
25.8.13
Reading the Signature Bytes
The algorithm for reading the Signature bytes is as follows (refer to “Programming the Flash” on
page 305 for details on Command and Address loading):
1. A: Load Command “0000 1000”.
2. B: Load Address Low Byte (0x00 - 0x02).
3. Set OE to “0”, and BS1 to “0”. The selected Signature byte can now be read at DATA.
4. Set OE to “1”.
310
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
25.8.14
Reading the Calibration Byte
The algorithm for reading the Calibration byte is as follows (refer to “Programming the Flash” on
page 305 for details on Command and Address loading):
1. A: Load Command “0000 1000”.
2. B: Load Address Low Byte, 0x00.
3. Set OE to “0”, and BS1 to “1”. The Calibration byte can now be read at DATA.
4. Set OE to “1”.
25.8.15
Parallel Programming Characteristics
Figure 25-7. Parallel Programming Timing, Including some General Timing Requirements
tXLWL
tXHXL
XTAL1
tDVXH
tXLDX
Data & Contol
(DATA, XA0/1, BS1, BS2)
tPLBX t BVWL
tBVPH
PAGEL
tWLBX
tPHPL
tWLWH
WR
tPLWL
WLRL
RDY/BSY
tWLRH
Figure 25-8. Parallel Programming Timing, Loading Sequence with Timing Requirements(1)
LOAD ADDRESS
(LOW BYTE)
LOAD DATA LOAD DATA
(HIGH BYTE)
LOAD DATA
(LOW BYTE)
t XLXH
tXLPH
LOAD ADDRESS
(LOW BYTE)
tPLXH
XTAL1
BS1
PAGEL
DATA
ADDR0 (Low Byte)
DATA (Low Byte)
DATA (High Byte)
ADDR1 (Low Byte)
XA0
XA1
Note:
1. The timing requirements shown in Figure 25-7 (i.e., tDVXH, tXHXL, and tXLDX) also apply to loading operation.
311
7647F–AVR–04/09
Figure 25-9. Parallel Programming Timing, Reading Sequence (within the Same Page) with
Timing Requirements(1)
LOAD ADDRESS
(LOW BYTE)
READ DATA
(LOW BYTE)
READ DATA
(HIGH BYTE)
LOAD ADDRESS
(LOW BYTE)
tXLOL
XTAL1
tBVDV
BS1
tOLDV
OE
DATA
tOHDZ
ADDR0 (Low Byte)
DATA (Low Byte)
ADDR1 (Low Byte)
DATA (High Byte)
XA0
XA1
Note:
1. The timing requirements shown in Figure 25-7 (i.e., tDVXH, tXHXL, and tXLDX) also apply to reading operation.
Table 25-15. Parallel Programming Characteristics, VCC = 5V ±10%
Symbol
Parameter
Min
VPP
Programming Enable Voltage
11.5
IPP
Programming Enable Current
tDVXH
Data and Control Valid before XTAL1 High
tXLXH
tXHXL
Max
Units
12.5
V
250
μA
67
ns
XTAL1 Low to XTAL1 High
200
ns
XTAL1 Pulse Width High
150
ns
tXLDX
Data and Control Hold after XTAL1 Low
67
ns
tXLWL
XTAL1 Low to WR Low
0
ns
tXLPH
XTAL1 Low to PAGEL high
0
ns
tPLXH
PAGEL low to XTAL1 high
150
ns
tBVPH
BS1 Valid before PAGEL High
67
ns
tPHPL
PAGEL Pulse Width High
150
ns
tPLBX
BS1 Hold after PAGEL Low
67
ns
tWLBX
BS2/1 Hold after WR Low
67
ns
tPLWL
PAGEL Low to WR Low
67
ns
tBVWL
BS1 Valid to WR Low
67
ns
tWLWH
WR Pulse Width Low
150
ns
tWLRL
WR Low to RDY/BSY Low
0
1
μs
tWLRH
WR Low to RDY/BSY High(1)
3.7
4.5
ms
tWLRH_CE
WR Low to RDY/BSY High for Chip Erase(2)
7.5
9
ms
tXLOL
XTAL1 Low to OE Low
0
tBVDV
BS1 Valid to DATA valid
0
tOLDV
OE Low to DATA Valid
250
ns
tOHDZ
OE High to DATA Tri-stated
250
ns
Notes:
312
Typ
ns
250
1.
tWLRH is valid for the Write Flash, Write EEPROM, Write Fuse bits and Write Lock bits
commands.
2.
tWLRH_CE is valid for the Chip Erase command.
ns
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
25.9
Serial Downloading
Both the Flash and EEPROM memory arrays can be programmed using the serial SPI bus while
RESET is pulled to GND. The serial interface consists of pins SCK, MOSI (input) and MISO (output). After RESET is set low, the Programming Enable instruction needs to be executed first
before program/erase operations can be executed. NOTE, in Table 25-14 on page 304, the pin
mapping for SPI programming is listed. Not all parts use the SPI pins dedicated for the internal
SPI interface.
Figure 25-10. Serial Programming and Verify(1)
+1.8 - 5.5V
VCC
+1.8 - 5.5V(2)
MOSI_A
AVCC
MISO_A
SCK_A
XTAL1
RESET
GND
Notes:
1. If the device is clocked by the internal Oscillator, it is no need to connect a clock source to the
XTAL1 pin.
2. VCC - 0.3V < AVCC < VCC + 0.3V, however, AVCC should always be within 1.8 - 5.5V
When programming the EEPROM, an auto-erase cycle is built into the self-timed programming
operation (in the Serial mode ONLY) and there is no need to first execute the Chip Erase
instruction. The Chip Erase operation turns the content of every memory location in both the
Program and EEPROM arrays into 0xFF.
Depending on CKSEL Fuses, a valid clock must be present. The minimum low and high periods
for the serial clock (SCK) input are defined as follows:
Low: > 2 CPU clock cycles for fck < 12 MHz, 3 CPU clock cycles for fck >= 12 MHz
High: > 2 CPU clock cycles for fck < 12 MHz, 3 CPU clock cycles for fck >= 12 MHz
25.9.1
Serial Programming Algorithm
When writing serial data to the ATmega16/32/64/M1/C1, data is clocked on the rising edge of
SCK.
When reading data from the ATmega16/32/64/M1/C1, data is clocked on the falling edge of
SCK. See Figure 25-11 for timing details.
313
7647F–AVR–04/09
To program and verify the ATmega16/32/64/M1/C1 in the serial programming mode, the following sequence is recommended (See four byte instruction formats in Table 25-17):
1. Power-up sequence:
Apply power between VCC and GND while RESET and SCK are set to “0”. In some systems, the programmer can not guarantee that SCK is held low during power-up. In this
case, RESET must be given a positive pulse of at least two CPU clock cycles duration
after SCK has been set to “0”.
2. Wait for at least 20 ms and enable serial programming by sending the Programming
Enable serial instruction to pin MOSI.
3. The serial programming instructions will not work if the communication is out of synchronization. When in sync. the second byte (0x53), will echo back when issuing the
third byte of the Programming Enable instruction. Whether the echo is correct or not, all
four bytes of the instruction must be transmitted. If the 0x53 did not echo back, give
RESET a positive pulse and issue a new Programming Enable command.
4. The Flash is programmed one page at a time. The memory page is loaded one byte at
a time by supplying the 6 LSB of the address and data together with the Load Program
Memory Page instruction. To ensure correct loading of the page, the data low byte must
be loaded before data high byte is applied for a given address. The Program Memory
Page is stored by loading the Write Program Memory Page instruction with the 8 MSB
of the address. If polling is not used, the user must wait at least tWD_FLASH before issuing
the next page. (See Table 25-16.) Accessing the serial programming interface before
the Flash write operation completes can result in incorrect programming.
5. The EEPROM array is programmed one byte at a time by supplying the address and
data together with the appropriate Write instruction. An EEPROM memory location is
first automatically erased before new data is written. If polling is not used, the user must
wait at least tWD_EEPROM before issuing the next byte. (See Table 25-16.) In a chip
erased device, no 0xFFs in the data file(s) need to be programmed.
6. Any memory location can be verified by using the Read instruction which returns the
content at the selected address at serial output MISO.
7. At the end of the programming session, RESET can be set high to commence normal
operation.
8. Power-off sequence (if needed):
Set RESET to “1”.
Turn VCC power off.
25.9.2
314
Data Polling Flash
When a page is being programmed into the Flash, reading an address location within the page
being programmed will give the value 0xFF. At the time the device is ready for a new page, the
programmed value will read correctly. This is used to determine when the next page can be written. Note that the entire page is written simultaneously and any address within the page can be
used for polling. Data polling of the Flash will not work for the value 0xFF, so when programming
this value, the user will have to wait for at least tWD_FLASH before programming the next page. As
a chip-erased device contains 0xFF in all locations, programming of addresses that are meant to
contain 0xFF, can be skipped. See Table 25-16 for tWD_FLASH value.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
25.9.3
Data Polling EEPROM
When a new byte has been written and is being programmed into EEPROM, reading the
address location being programmed will give the value 0xFF. At the time the device is ready for
a new byte, the programmed value will read correctly. This is used to determine when the next
byte can be written. This will not work for the value 0xFF, but the user should have the following
in mind: As a chip-erased device contains 0xFF in all locations, programming of addresses that
are meant to contain 0xFF, can be skipped. This does not apply if the EEPROM is re-programmed without chip erasing the device. In this case, data polling cannot be used for the value
0xFF, and the user will have to wait at least tWD_EEPROM before programming the next byte. See
Table 25-16 for tWD_EEPROM value.
Table 25-16. Minimum Wait Delay Before Writing the Next Flash or EEPROM Location
Symbol
Minimum Wait Delay
tWD_FLASH
4.5 ms
tWD_EEPROM
3.6 ms
tWD_ERASE
9.0 ms
Figure 25-11. Serial Programming Waveforms
SERIAL DATA INPUT
(MOSI)
MSB
LSB
SERIAL DATA OUTPUT
(MISO)
MSB
LSB
SERIAL CLOCK INPUT
(SCK)
SAMPLE
Table 25-17. Serial Programming Instruction Set
Instruction Format
Instruction
Programming Enable
Chip Erase
Read Program Memory
Byte 1
Byte 2
Byte 3
Byte4
1010 1100
0101 0011
xxxx xxxx
xxxx xxxx
Enable Serial Programming after
RESET goes low.
1010 1100
100x xxxx
xxxx xxxx
xxxx xxxx
Chip Erase EEPROM and Flash.
0010 H000
000a aaaa
bbbb bbbb
oooo oooo
Read H (high or low) data o from
Program memory at word address a:b.
0100 H000
000x xxxx
xxbb bbbb
iiii iiii
Write H (high or low) data i to Program
Memory page at word address b. Data
low byte must be loaded before Data
high byte is applied within the same
address.
0100 1100
000a aaaa
bbxx xxxx
xxxx xxxx
Write Program Memory Page at
address a:b.
1010 0000
000x xxaa
bbbb bbbb
oooo oooo
Read data o from EEPROM memory at
address a:b.
Load Program Memory Page
Write Program Memory Page
Read EEPROM Memory
Operation
315
7647F–AVR–04/09
Table 25-17. Serial Programming Instruction Set (Continued)
Instruction Format
Instruction
Write EEPROM Memory
Load EEPROM Memory
Page (page access)
Write EEPROM Memory
Page (page access)
Byte 1
Byte 2
Byte 3
Byte4
1100 0000
000x xxaa
bbbb bbbb
iiii iiii
Write data i to EEPROM memory at
address a:b.
1100 0001
0000 0000
0000 00bb
iiii iiii
Load data i to EEPROM memory page
buffer. After data is loaded, program
EEPROM page.
1100 0010
00xx xxaa
bbbb bb00
xxxx xxxx
0101 1000
0000 0000
xxxx xxxx
xxoo oooo
Read Lock bits. “0” = programmed, “1”
= unprogrammed. See Table 25-1 on
page 296 for details.
1010 1100
111x xxxx
xxxx xxxx
11ii iiii
Write Lock bits. Set bits = “0” to
program Lock bits. See Table 25-1 on
page 296 for details.
0011 0000
000x xxxx
xxxx xxbb
oooo oooo
Read Signature Byte o at address b.
1010 1100
1010 0000
xxxx xxxx
iiii iiii
Set bits = “0” to program, “1” to
unprogram. See Table XXX on page
XXX for details.
1010 1100
1010 1000
xxxx xxxx
iiii iiii
Set bits = “0” to program, “1” to
unprogram. See Table 25-6 on page
299 for details.
1010 1100
1010 0100
xxxx xxxx
xxxx xxii
Set bits = “0” to program, “1” to
unprogram. See Table 25-4 on page
298 for details.
0101 0000
0000 0000
xxxx xxxx
oooo oooo
Read Fuse bits. “0” = programmed, “1”
= unprogrammed. See Table XXX on
page XXX for details.
0101 1000
0000 1000
xxxx xxxx
oooo oooo
Read Fuse High bits. “0” =
pro-grammed, “1” = unprogrammed.
See Table 25-6 on page 299 for
details.
0101 0000
0000 1000
xxxx xxxx
oooo oooo
Read Extended Fuse bits. “0” =
pro-grammed, “1” = unprogrammed.
See Table 25-4 on page 298 for
details.
0011 1000
000x xxxx
0000 0000
oooo oooo
Read Calibration Byte
1111 0000
0000 0000
xxxx xxxx
xxxx xxxo
If o = “1”, a programming operation is
still busy. Wait until this bit returns to
“0” before applying another command.
Read Lock bits
Write Lock bits
Read Signature Byte
Write Fuse bits
Write Fuse High bits
Write Extended Fuse Bits
Read Fuse bits
Read Fuse High bits
Read Extended Fuse Bits
Read Calibration Byte
Poll RDY/BSY
Note:
25.9.4
316
Operation
Write EEPROM page at address a:b.
a = address high bits, b = address low bits, H = 0 - Low byte, 1 - High Byte, o = data out, i = data in, x = don’t care
SPI Serial Programming Characteristics
For characteristics of the SPI module see “SPI Serial Programming Characteristics” on page
316.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
26. Electrical Characteristics
All DC/AC characteristics contained in this datasheet are based on simulations and characterization of similar devices in the same process and design methods. These values are
preliminary representing design targets, and will be updated after characterization of actual
automotive silicon data.
26.1
Absolute Maximum Ratings*
Operating Temperature .................................-40° C to +125° C
*NOTICE:
Storage Temperature......................................-65°C to +150°C
Voltage on any Pin except RESET
with respect to Ground ................................ -0.5V to VCC+0.5V
Voltage on RESET with respect to Ground ..... -0.5V to +13.0V
Stresses beyond those listed under “Absolute Maximum Ratings” may cause permanent damage to
the device. This is a stress rating only and functional operation of the device at these or other conditions beyond those indicated in the operational
sections of this specification is not implied. Exposure to absolute maximum rating conditions for
extended periods may affect device reliability.
Maximum Operating Voltage .............................................6.0V
DC Current per I/O Pin ................................................40.0 mA
DC Current VCC and GND Pins ................................200.0 mA
26.2
DC Characteristics
TA = -40° C to +125° C, VCC = 2.7V to 5.5V (unless otherwise noted)
Symbol
Parameter
Condition
Min.
VIL
Input Low Voltage
Port B, C & D and XTAL1,
XTAL2 pins as I/O
VIH
Input High Voltage
VIL1
Max.
Units
-0.5
0.2VCC(1)
V
Port B, C & D and XTAL1,
XTAL2 pins as I/O
0.6VCC(2)
VCC+0.5
V
Input Low Voltage
XTAL1 pin , External Clock
Selected
-0.5
0.1VCC(1)
V
VIH1
Input High Voltage
XTAL1 pin , External Clock
Selected
0.8VCC(2)
VCC+0.5
V
VIL2
Input Low Voltage
RESET pin
-0.5
0.2VCC(1)
V
RESET pin
0.9VCC(2)
VCC+0.5
V
VIH2
Input High Voltage
VIL3
Input Low Voltage
RESET pin as I/O
-0.5
VIH3
Input High Voltage
RESET pin as I/O
0.8VCC(2)
VOL
Output Low Voltage(3)
(Port B, C & D and XTAL1,
XTAL2 pins as I/O)
IOL = 10 mA, VCC = 5V
IOL = 6 mA, VCC = 3V
VOH
Output High Voltage(4)
(Port B, C & D and XTAL1,
XTAL2 pins as I/O)
IOH = -10 mA, VCC = 5V
IOH = -8 mA, VCC = 3V
VOL3
Output Low Voltage(3)
(RESET pin as I/O)
IOL = 2.1 mA, VCC = 5V
IOL = 0.8 mA, VCC = 3V
VOH3
Output High Voltage(4)
(RESET pin as I/O)
IOH = -0.6 mA, VCC = 5V
IOH = -0.2 mA, VCC = 3V
Typ.
(1)
V
VCC+0.5
V
0.7
0.5
V
V
0.2VCC
4.2
2.2
V
V
0.9
0.7
3.8
1.8
V
V
V
V
317
7647F–AVR–04/09
TA = -40° C to +125° C, VCC = 2.7V to 5.5V (unless otherwise noted) (Continued)
Symbol
Parameter
Condition
IIL
Input Leakage
Current I/O Pin
IIH
Input Leakage
Current I/O Pin
RRST
Reset Pull-up Resistor
Rpu
I/O Pin Pull-up Resistor
Power Supply Current
ICC
Power-down mode
(5)
Max.
Units
VCC = 5.5V, pin low
(absolute value), except Port E
50
nA
VCC = 5.5V, pin high
(absolute value), except Port E
50
nA
30
200
kΩ
20
50
kΩ
3.8
8
mA
Active 16 MHz, VCC = 5V, Ext
Clock, PRR = 0xFF
14
30
mA
Idle (16K and 32K devices)
VCC = 3V, F = 8 MHz
VCC = 5V, F = 16MHz
1.1
4.0
8
15
mA
mA
Idle (64K devices only)
VCC = 3V, F = 8 MHz
VCC = 5V, F = 16MHz
1.5
5.8
8
15
mA
mA
WDT enabled, VCC = 5V
t0 < 85°C
8
30
µA
WDT enabled, VCC = 5V
85°C < t0 < 125°C
21
120
µA
WDT disabled, VCC = 5V
t0 < 85°C
2
25
µA
WDT disabled, VCC = 5V
85°C < t0 < 125°C
16
100
µA
25
-35
70
mV
mV
+50
nA
VCC = 5V, Vin = 3V
Rising Edge
Falling Edge
IACLK
Analog Comparator
Input Leakage Current
VCC = 5V
Vin = VCC/2
tACID
Analog Comparator
Propagation Delay
VCC = 2.7V
VCC = 5.0V
ISRC
Current Source Value
VCC = 5V: Max Rload 30 KΩ
VCC = 3V: Max Rload 15 KΩ
Note:
Typ.
Active 8 MHz, VCC = 3V, RC
osc, PRR = 0xFF
Analog Comparator
Hysteresis Voltage
Vhysr
Min.
-100
-50
(6)
(6)
95
100
ns
105
µA
1. “Max” means the highest value where the pin is guaranteed to be read as low
2. “Min” means the lowest value where the pin is guaranteed to be read as high
3. Although each I/O port can sink more than the test conditions (10 mA at VCC = 5V, 6 mA at VCC = 3V) under steady state
conditions (non-transient), the following must be observed:
1] The sum of all IOL, for ports B0 - B1, C2 - C3, D4, E1 - E2 should not exceed 70 mA.
2] The sum of all IOL, for ports B6 - B7, C0 - C1, D0 -D3, E0 should not exceed 70 mA.
3] The sum of all IOL, for ports B2 - B5, C4 - C7, D5 - D7 should not exceed 70 mA.
If IOL exceeds the test condition, VOL may exceed the related specification. Pins are not guaranteed to sink current greater
than the listed test condition.
4. Although each I/O port can source more than the test conditions (10 mA at VCC = 5V, 8 mA at VCC = 3V) under steady state
conditions (non-transient), the following must be observed:
1] The sum of all IOH, for ports B0 - B1, C2 - C3, D4, E1 - E2 should not exceed 100 mA.
2] The sum of all IOH, for ports B6 - B7, C0 - C1, D0 -D3, E0 should not exceed 100 mA.
3] The sum of all IOH, for ports B2 - B5, C4 - C7, D5 - D7 should not exceed 100 mA.
If IOH exceeds the test condition, VOH may exceed the related specification. Pins are not guaranteed to source current
greater than the listed test condition.
318
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
5. Minimum VCC for Power-down is 2.5V.
6. The Analog Comparator Propogation Delay equals 1 comparator clock plus 30 nS. See “Analog Comparator” on page 262.
for comparator clock definition.
26.3
26.3.1
Clock Characteristics
Calibrated Internal RC Oscillator Accuracy
Table 26-1.
Calibration Accuracy of Internal RC Oscillator
Frequency
VCC
Temperature
Calibration Accuracy
8.0 MHz
3V
25° C
±2%
Factory
Calibration
26.4
External Clock Drive Characteristics
Figure 26-1. External Clock Drive Waveforms
V IH1
V IL1
Table 26-2.
External Clock Drive
VCC = 2.7 - 5.5V
VCC = 4.5 - 5.5V
Min.
Max.
Min.
Max.
Units
0
8
0
16
MHz
Symbol
Parameter
1/tCLCL
Oscillator Frequency
tCLCL
Clock Period
125
62.5
ns
tCHCX
High Time
50
25
ns
tCLCX
Low Time
50
25
ns
tCLCH
Rise Time
1.6
0.5
µs
tCHCL
Fall Time
1.6
0.5
µs
ΔtCLCL
Change in period from one clock cycle
to the next
2
2
%
319
7647F–AVR–04/09
26.5
Maximum Speed vs. VCC
Maximum frequency is depending on VCC. As shown in Figure 26-2 , the Maximum Frequency
equals 8MHz when VCC is between 2.7V and 4.5V and equals 16MHz when VCC is between 4.5V
and 5.5V.
Figure 26-2. Maximum Frequency vs. VCC, ATmega16/32/64/M1/C1
16Mhz
8Mhz
Safe Operating Area
2.7V
26.6
4.5V
5.5V
PLL Characteristics
.
Table 26-3.
Symbol
Parameter
Min.
Typ.
Max.
Units
PLLIF
Input Frequency
0.5
1
2
MHz
PLLF
PLL Factor
PLLLT
Lock-in Time
80
µS
Note:
320
PLL Characteristics - VCC = 2.7V to 5.5V (unless otherwise noted)
64
While connected to external clock or external oscillator, PLL Input Frequency must be selected to
provide outputs with frequency in accordance with driven parts of the circuit (CPU core, PSC...)
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
26.7
SPI Timing Characteristics
See Figure 26-3 and Figure 26-4 for details.
Table 26-4.
SPI Timing Parameters
Description
Mode
1
SCK period
Master
See Table 15-4
2
SCK high/low
Master
50% duty cycle
3
Rise/Fall time
Master
3.6
4
Setup
Master
10
5
Hold
Master
10
6
Out to SCK
Master
0.5 • tsck
7
SCK to out
Master
10
8
SCK to out high
Master
10
9
SS low to out
Slave
15
10
SCK period
Slave
4 • tck
11
SCK high/low (1)
Slave
2 • tck
12
Rise/Fall time
Slave
13
Setup
Slave
10
14
Hold
Slave
tck
15
SCK to out
Slave
16
SCK to SS high
Slave
17
SS high to tri-state
Slave
18
SS low to SCK
Slave
Note:
Min.
Typ.
Max.
ns
1600
15
20
10
20
In SPI Programming mode the minimum SCK high/low period is:
- 2 tCLCL for fCK < 12 MHz
- 3 tCLCL for fCK >12 MHz
Figure 26-3. SPI Interface Timing Requirements (Master Mode)
SS
6
1
SCK
(CPOL = 0)
2
2
SCK
(CPOL = 1)
4
MISO
(Data Input)
5
3
MSB
...
LSB
7
MOSI
(Data Output)
MSB
8
...
LSB
321
7647F–AVR–04/09
Figure 26-4. SPI Interface Timing Requirements (Slave Mode)
SS
10
9
16
SCK
(CPOL = 0)
11
11
SCK
(CPOL = 1)
13
MOSI
(Data Input)
14
12
MSB
...
LSB
15
MISO
(Data Output)
26.8
Symbol
INL
DNL
LSB
Parameter
Condition
Resolution
Single Ended Conversion
10
VCC = 5V, VREF = 2.56V
ADC clock = 1 MHz
3.2
VCC = 5V, VREF = 2.56V
ADC clock = 2 MHz
3.2
5.0
VCC = 5V, VREF = 2.56V
ADC clock = 1 MHz
0.7
1.5
VCC = 5V, VREF = 2.56V
ADC clock = 2 MHz
0.8
2.0
VCC = 5V, VREF = 2.56V
ADC clock = 1 MHz
0.5
0.8
VCC = 5V, VREF = 2.56V
ADC clock = 2 MHz
0.6
1.4
-5.0
0.0
Absolute accuracy
Integral Non-linearity
Differential Non-linearity
Offset error
322
...
X
ADC Characteristics in single ended mode - TA = -40°C to +125°C, VCC = 2.7V to 5.5V
(unless otherwise noted)
Gain error
VREF
MSB
ADC Characteristics
Table 26-5.
TUE
17
Min
Typ
Max
Bits
5.0
LSB
LSB
LSB
VCC = 5V, VREF = 2.56V
ADC clock = 1 MHz
-9.0
VCC = 5V, VREF = 2.56V
ADC clock = 2 MHz
-9.0
-5.0
0.0
VCC = 5V, VREF = 2.56V
ADC clock = 1 MHz
-2.0
+2.5
+5.0
VCC = 5V, VREF = 2.56V
ADC clock = 2 MHz
-2.0
+2.5
+5.0
Ref voltage
Units
LSB
LSB
2.56
AVCC
V
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Table 26-6.
Symbol
ADC Characteristics in differential mode - TA = -40°C to +125°C, VCC = 2.7V to 5.5V
(unless otherwise noted)
Parameter
Resolution
TUE
INL
DNL
Absolute accuracy
Integral Non-linearity
Differential Non-linearity
Gain error
Offset error
VREF
Ref voltage
Condition
Min
Typ
Max
Differential conversion, gain = 5x
8
Differential conversion, gain = 10x
8
Differential conversion, gain = 20x
8
Differential conversion, gain = 40x
8
Gain = 5x, 10x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
1.5
3.5
Gain = 20x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
1.5
4.0
Gain = 40x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
1.5
4.5
Gain = 5x, 10x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
0.1
1.5
Gain = 20x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
0.2
2.5
Gain = 40x, VCC = 5V,
VREF = 2.56V, ADC clock = 1 MHz
0.3
3.5
Gain = 40x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
0.7
4.5
Gain = 5x, 10x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
0.1
1.0
Gain = 20x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
0.2
1.5
Gain = 40x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
0.3
2.5
Units
Bits
LSB
LSB
Gain = 5x, 10x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
-3.0
+3.0
Gain = 20x, 40x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
-3.0
+3.0
Gain = 5x, 10x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
-3.0
+3.0
Gain = 20x, 40x, VCC = 5V,
VREF = 2.56V, ADC clock = 2 MHz
-4.0
+4.0
2.56
AVCC - 0.5
LSB
LSB
LSB
V
323
7647F–AVR–04/09
26.9
Parallel Programming Characteristics
Figure 26-5. Parallel Programming Timing, Including some General Timing Requirements
tXLWL
tXHXL
XTAL1
tDVXH
tXLDX
Data & Contol
(DATA, XA0/1, BS1, BS2)
tPLBX t BVWL
tBVPH
PAGEL
tWLBX
tPHPL
tWLWH
WR
tPLWL
WLRL
RDY/BSY
tWLRH
Figure 26-6. Parallel Programming Timing, Loading Sequence with Timing Requirements(1)
LOAD ADDRESS
(LOW BYTE)
LOAD DATA LOAD DATA
(HIGH BYTE)
LOAD DATA
(LOW BYTE)
t XLXH
tXLPH
LOAD ADDRESS
(LOW BYTE)
tPLXH
XTAL1
BS1
PAGEL
DATA
ADDR0 (Low Byte)
DATA (Low Byte)
DATA (High Byte)
ADDR1 (Low Byte)
XA0
XA1
Note:
324
1. The timing requirements shown in Figure 25-7 (i.e., tDVXH, tXHXL, and tXLDX) also apply to loading operation.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 26-7. Parallel Programming Timing, Reading Sequence (within the Same Page) with
Timing Requirements(1)
LOAD ADDRESS
(LOW BYTE)
READ DATA
(LOW BYTE)
READ DATA
(HIGH BYTE)
LOAD ADDRESS
(LOW BYTE)
tXLOL
XTAL1
tBVDV
BS1
tOLDV
OE
DATA
tOHDZ
ADDR0 (Low Byte)
DATA (Low Byte)
DATA (High Byte)
ADDR1 (Low Byte)
XA0
XA1
Note:
1. ggThe timing requirements shown in Figure 25-7 (i.e., tDVXH, tXHXL, and tXLDX) also apply to
reading operation.
325
7647F–AVR–04/09
Table 26-7.
Symbol
Parameter
Min.
VPP
Programming Enable Voltage
11.5
IPP
Programming Enable Current
tDVXH
Data and Control Valid before XTAL1 High
67
ns
tXLXH
XTAL1 Low to XTAL1 High
200
ns
tXHXL
XTAL1 Pulse Width High
150
ns
tXLDX
Data and Control Hold after XTAL1 Low
67
ns
tXLWL
XTAL1 Low to WR Low
0
ns
tXLPH
XTAL1 Low to PAGEL high
0
ns
tPLXH
PAGEL low to XTAL1 high
150
ns
tBVPH
BS1 Valid before PAGEL High
67
ns
tPHPL
PAGEL Pulse Width High
150
ns
tPLBX
BS1 Hold after PAGEL Low
67
ns
tWLBX
BS2/1 Hold after WR Low
67
ns
tPLWL
PAGEL Low to WR Low
67
ns
tBVWL
BS1 Valid to WR Low
67
ns
tWLWH
WR Pulse Width Low
150
ns
tWLRL
WR Low to RDY/BSY Low
WR Low to RDY/BSY High
tWLRH
(1)
(2)
Typ.
Max.
Units
12.5
V
250
μA
0
1
μs
3.7
5
ms
7.5
10
ms
tWLRH_CE
WR Low to RDY/BSY High for Chip Erase
tXLOL
XTAL1 Low to OE Low
0
tBVDV
BS1 Valid to DATA valid
0
tOLDV
tOHDZ
Notes:
326
Parallel Programming Characteristics, VCC = 5V ±10%
ns
250
ns
OE Low to DATA Valid
250
ns
OE High to DATA Tri-stated
250
ns
1.
tWLRH is valid for the Write Flash, Write EEPROM, Write Fuse bits and Write Lock bits
commands.
2. tWLRH_CE is valid for the Chip Erase command.
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
27. ATmega16/32/64/M1/C1 Typical Characteristics
All DC characteristics contained in this datasheet are based on simulations and characterization
of similar devices in the same process and design methods. These values are preliminary representing design targets, and will be updated after characterization of actual automotive silicon
data.
The following charts show typical behavior. These figures are not tested during manufacturing.
All current consumption measurements are performed with all I/O pins configured as inputs and
with internal pull-ups enabled. A sine wave generator with rail-to-rail output is used as clock
source.
All Active- and Idle current consumption measurements are done with all bits in the PRR register
set and thus, the corresponding I/O modules are turned off. Also the Analog Comparator is disabled during these measurements. Table 27-1 on page 332 shows the additional current
consumption compared to ICC Active and ICC Idle for every I/O module controlled by the Power
Reduction Register. See “Power Reduction Register” on page 37 for details.
The power consumption in Power-down mode is independent of clock selection.
The current consumption is a function of several factors such as: operating voltage, operating
frequency, loading of I/O pins, switching rate of I/O pins, code executed and ambient temperature. The dominating factors are operating voltage and frequency.
The current drawn from capacitive loaded pins may be estimated (for one pin) as CL*VCC*f where
CL = load capacitance, VCC = operating voltage and f = average switching frequency of I/O pin.
The parts are characterized at frequencies higher than test limits. Parts are not guaranteed to
function properly at frequencies higher than the ordering code indicates.
The difference between current consumption in Power-down mode with Watchdog Timer
enabled and Power-down mode with Watchdog Timer disabled represents the differential current drawn by the Watchdog Timer.
327
7647F–AVR–04/09
27.1
Active Supply Current
Figure 27-1. Active Supply Current versus Frequency (0.1 - 1.0 MHz)
Figure 27-2. Active Supply Current versus Frequency (1 - 24 MHz)
328
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 27-3. Active Supply Current versus VCC (Internal RC Oscillator, 8 MHz)
Figure 27-4. Active Supply Current versus VCC (Internal PLL Oscillator, 16 MHz)
329
7647F–AVR–04/09
27.2
Idle Supply Current
Figure 27-5. Idle Supply Current versus Frequency (0.1 - 1.0 MHz)
Figure 27-6. Idle Supply Current versus Frequency (1 - 24 MHz)
330
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 27-7. IIdle Supply Current versus VCC (Internal RC Oscillator, 8 MHz)
Figure 27-8. Idle Supply Current versus VCC (Internal PLL Oscillator, 16 MHz)
331
7647F–AVR–04/09
27.2.1
Using the Power Reduction Register
The tables and formulas below can be used to calculate the additional current consumption for
the different I/O modules in Idle mode. The enabling or disabling of the I/O modules are controlled by the Power Reduction Register. See “Power Reduction Register” on page 42 for details.
Table 27-1.
Additional Current Consumption (Percentage) in Active and Idle Mode
Typical ICC (µA)
Percent of Added Consumption
27.3
VCC = 5.0V, 16 Mhz
VCC = 3.0V, 8 Mhz
PRCAN
13
12
PRPSC
8
7.5
PRTIM1
2
2
PRTIM0
1
1
PRSPI
2
2
PRLIN
5.5
5
PRADC
5
4.5
Power-Down Supply Current
Figure 27-9. Power-Down Supply Current versus VCC (Watchdog Timer Disabled)
332
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 27-10. Power-Down Supply Current versus VCC (Watchdog Timer Enabled)
27.4
Pin Pull-up
Figure 27-11. I/O Pin Pull-Up Resistor Current versus Input Voltage (VCC = 5V)
333
7647F–AVR–04/09
Figure 27-12. I/O Pin Pull-Up Resistor Current versus Input Voltage (VCC = 2.7V)
Figure 27-13. Reset Pull-Up Resistor Current versus Reset Pin Voltage (VCC = 5V)
Figure 27-14. Reset Pull-Up Resistor Current versus Reset Pin Voltage (VCC = 2.7V)
334
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
27.5
Pin Driver Strength
Figure 27-15. I/O Pin Output Voltage versus Source Current (VCC = 5V)
Figure 27-16. I/O Pin Output Voltage versus Source Current (VCC = 3V)
335
7647F–AVR–04/09
Figure 27-17. I/O Pin Low Output Voltage versus Source Current (VCC = 5V)
Figure 27-18. I/O Pin Low Output Voltage versus Source Current (VCC = 3V)
336
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
27.6
Pin Thresholds and Hysteresis
Figure 27-19. I/O Pin Input Threshold Voltage versus VCC (VIH, I/O Pin Read As '1')
Figure 27-20. I/O Pin Input Threshold Voltage versus VCC (VIL, I/O Pin Read As '0')
337
7647F–AVR–04/09
Figure 27-21. I/O Pin Input HysteresisVoltage versus VCC
Figure 27-22. Reset Input Threshold Voltage versus VCC (VIH, Reset Pin Read As '1')
338
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 27-23. Reset Input Threshold Voltage versus VCC (VIL, Reset Pin Read As '0')
Figure 27-24. XTAL1 Input Threshold Voltage versus VCC (XTAL1 Pin Read As '1')
339
7647F–AVR–04/09
Figure 27-25. XTAL1 Input Threshold Voltage versus VCC (XTAL1 Pin Read As '0')
27.7
BOD Thresholds and Analog Comparator Hysterisis
Figure 27-26. BOD Thresholds versus Temperature (BODLEVEL Is 4.3V)
340
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 27-27. BOD Thresholds versus Temperature (BODLEVEL Is 2.7V)
Figure 27-28. TypicalAnalog Comparator Hysterisis Average Thresholds versus Common Mode
Voltage
40.00E-3
30.00E-3
20.00E-3
threshold value (V)
10.00E-3
000.00E+0
0.5
1
1.35
1.5
2
2.5
2.6
2.75
3
3.5
4
4.5
5
5.4
-10.00E-3
-20.00E-3
-30.00E-3
-40.00E-3
-50.00E-3
-60.00E-3
Common voltage (v)
341
7647F–AVR–04/09
27.8
Analog Reference
Figure 27-29. AREF Voltage versus VCC
Figure 27-30. AREF Voltage versus Temperature
27.9
Internal Oscillator Speed
Figure 27-31. Watchdog Oscillator Frequency versus VCC
342
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Figure 27-32. Calibrated 8 MHz RC Oscillator Frequency verus Temperature
Figure 27-33. Calibrated 8 MHz RC Oscillator Frequency versus VCC
Figure 27-34. Calibrated 8 MHz RC Oscillator Frequency versus Osccal Value
343
7647F–AVR–04/09
28. Instruction Set Summary
Mnemonics
Operands
Description
Operation
Flags
#Clocks
1
ARITHMETIC AND LOGIC INSTRUCTIONS
ADD
Rd, Rr
Add two Registers
Rd ←Rd + Rr
Z,C,N,V,H
ADC
Rd, Rr
Add with Carry two Registers
Rd ←Rd + Rr + C
Z,C,N,V,H
1
ADIW
Rdl,K
Add Immediate to Word
Rdh:Rdl ←Rdh:Rdl + K
Z,C,N,V,S
2
SUB
Rd, Rr
Subtract two Registers
Rd ←Rd - Rr
Z,C,N,V,H
1
SUBI
Rd, K
Subtract Constant from Register
Rd ←Rd - K
Z,C,N,V,H
1
SBC
Rd, Rr
Subtract with Carry two Registers
Rd ←Rd - Rr - C
Z,C,N,V,H
1
SBCI
Rd, K
Subtract with Carry Constant from Reg.
Rd ←Rd - K - C
Z,C,N,V,H
1
SBIW
Rdl,K
Subtract Immediate from Word
Rdh:Rdl ←Rdh:Rdl - K
Z,C,N,V,S
2
AND
Rd, Rr
Logical AND Registers
Rd ←Rd • Rr
Z,N,V
1
ANDI
Rd, K
Logical AND Register and Constant
Rd ←Rd • K
Z,N,V
1
OR
Rd, Rr
Logical OR Registers
Rd ←Rd v Rr
Z,N,V
1
ORI
Rd, K
Logical OR Register and Constant
Rd ←Rd v K
Z,N,V
1
1
EOR
Rd, Rr
Exclusive OR Registers
Rd ←Rd ⊕ Rr
Z,N,V
COM
Rd
One’s Complement
Rd ←0xFF - Rd
Z,C,N,V
1
NEG
Rd
Two’s Complement
Rd ←0x00 - Rd
Z,C,N,V,H
1
1
SBR
Rd,K
Set Bit(s) in Register
Rd ←Rd v K
Z,N,V
CBR
Rd,K
Clear Bit(s) in Register
Rd ←Rd · (0xFF - K)
Z,N,V
1
INC
Rd
Increment
Rd ←Rd + 1
Z,N,V
1
DEC
Rd
Decrement
Rd ←Rd - 1
Z,N,V
1
TST
Rd
Test for Zero or Minus
Rd ←Rd • Rd
Z,N,V
1
CLR
Rd
Clear Register
Rd ←Rd ⊕ Rd
Z,N,V
1
SER
Rd
Set Register
Rd ←0xFF
None
1
MUL
Rd, Rr
Multiply Unsigned
R1:R0 ←Rd x Rr
Z,C
2
MULS
Rd, Rr
Multiply Signed
R1:R0 ←Rd x Rr
Z,C
2
MULSU
Rd, Rr
Multiply Signed with Unsigned
R1:R0 ←Rd x Rr
Z,C
2
FMUL
Rd, Rr
Fractional Multiply Unsigned
R1:R0 ←(Rd x Rr) << 1
Z,C
2
FMULS
Rd, Rr
Fractional Multiply Signed
R1:R0 ←(Rd x Rr) << 1
Z,C
2
FMULSU
Rd, Rr
Fractional Multiply Signed with Unsigned
R1:R0 ←(Rd x Rr) << 1
Z,C
2
2
BRANCH INSTRUCTIONS
RJMP
k
IJMP
PC ←PC + k + 1
None
PC ←Z
None
2
JMP(*)
k
Direct Jump
PC ←k
None
3
RCALL
k
Relative Subroutine Call
PC ←PC + k + 1
None
3
Indirect Call to (Z)
PC ←Z
None
3
Direct Subroutine Call
PC ←k
None
4
RET
Subroutine Return
PC ←STACK
None
4
RETI
Interrupt Return
PC ←STACK
I
4
1/2/3
ICALL
CALL(*)
344
Relative Jump
Indirect Jump to (Z)
k
CPSE
Rd,Rr
Compare, Skip if Equal
if (Rd = Rr) PC ←PC + 2 or 3
None
CP
Rd,Rr
Compare
Rd - Rr
Z, N,V,C,H
1
CPC
Rd,Rr
Compare with Carry
Rd - Rr - C
Z, N,V,C,H
1
CPI
Rd,K
Compare Register with Immediate
Rd - K
Z, N,V,C,H
1
SBRC
Rr, b
Skip if Bit in Register Cleared
if (Rr(b)=0) PC ←PC + 2 or 3
None
1/2/3
SBRS
Rr, b
Skip if Bit in Register is Set
if (Rr(b)=1) PC ←PC + 2 or 3
None
1/2/3
SBIC
P, b
Skip if Bit in I/O Register Cleared
if (P(b)=0) PC ←PC + 2 or 3
None
1/2/3
SBIS
P, b
Skip if Bit in I/O Register is Set
if (P(b)=1) PC ←PC + 2 or 3
None
1/2/3
BRBS
s, k
Branch if Status Flag Set
if (SREG(s) = 1) then PC←PC+k + 1
None
1/2
BRBC
s, k
Branch if Status Flag Cleared
if (SREG(s) = 0) then PC←PC+k + 1
None
1/2
BREQ
k
Branch if Equal
if (Z = 1) then PC ←PC + k + 1
None
1/2
BRNE
k
Branch if Not Equal
if (Z = 0) then PC ←PC + k + 1
None
1/2
BRCS
k
Branch if Carry Set
if (C = 1) then PC ←PC + k + 1
None
1/2
BRCC
k
Branch if Carry Cleared
if (C = 0) then PC ←PC + k + 1
None
1/2
BRSH
k
Branch if Same or Higher
if (C = 0) then PC ←PC + k + 1
None
1/2
BRLO
k
Branch if Lower
if (C = 1) then PC ←PC + k + 1
None
1/2
BRMI
k
Branch if Minus
if (N = 1) then PC ←PC + k + 1
None
1/2
BRPL
k
Branch if Plus
if (N = 0) then PC ←PC + k + 1
None
1/2
BRGE
k
Branch if Greater or Equal, Signed
if (N ⊕ V= 0) then PC ←PC + k + 1
None
1/2
BRLT
k
Branch if Less Than Zero, Signed
if (N ⊕ V= 1) then PC ←PC + k + 1
None
1/2
BRHS
k
Branch if Half Carry Flag Set
if (H = 1) then PC ←PC + k + 1
None
1/2
BRHC
k
Branch if Half Carry Flag Cleared
if (H = 0) then PC ←PC + k + 1
None
1/2
BRTS
k
Branch if T Flag Set
if (T = 1) then PC ←PC + k + 1
None
1/2
BRTC
k
Branch if T Flag Cleared
if (T = 0) then PC ←PC + k + 1
None
1/2
BRVS
k
Branch if Overflow Flag is Set
if (V = 1) then PC ←PC + k + 1
None
1/2
BRVC
k
Branch if Overflow Flag is Cleared
if (V = 0) then PC ←PC + k + 1
None
1/2
BRIE
k
Branch if Interrupt Enabled
if ( I = 1) then PC ←PC + k + 1
None
1/2
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Mnemonics
Operands
Description
Operation
Flags
#Clocks
BRID
k
Branch if Interrupt Disabled
if ( I = 0) then PC ←PC + k + 1
None
1/2
BIT AND BIT-TEST INSTRUCTIONS
SBI
P,b
Set Bit in I/O Register
I/O(P,b) ←1
None
2
CBI
P,b
Clear Bit in I/O Register
I/O(P,b) ←0
None
2
LSL
Rd
Logical Shift Left
Rd(n+1) ←Rd(n), Rd(0) ←0
Z,C,N,V
1
LSR
Rd
Logical Shift Right
Rd(n) ←Rd(n+1), Rd(7) ←0
Z,C,N,V
1
ROL
Rd
Rotate Left Through Carry
Rd(0)←C,Rd(n+1)←Rd(n),C←Rd(7)
Z,C,N,V
1
ROR
Rd
Rotate Right Through Carry
Rd(7)←C,Rd(n)←Rd(n+1),C←Rd(0)
Z,C,N,V
1
ASR
Rd
Arithmetic Shift Right
Rd(n) ←Rd(n+1), n=0..6
Z,C,N,V
1
SWAP
Rd
Swap Nibbles
Rd(3..0)←Rd(7..4),Rd(7..4)←Rd(3..0)
None
1
BSET
s
Flag Set
SREG(s) ←1
SREG(s)
1
1
BCLR
s
Flag Clear
SREG(s) ←0
SREG(s)
BST
Rr, b
Bit Store from Register to T
T ←Rr(b)
T
1
BLD
Rd, b
Bit load from T to Register
Rd(b) ←T
None
1
SEC
Set Carry
C ←1
C
1
CLC
Clear Carry
C ←0
C
1
SEN
Set Negative Flag
N ←1
N
1
CLN
Clear Negative Flag
N ←0
N
1
SEZ
Set Zero Flag
Z ←1
Z
1
CLZ
Clear Zero Flag
Z ←0
Z
1
SEI
Global Interrupt Enable
I ←1
I
1
CLI
Global Interrupt Disable
I ←0
I
1
SES
Set Signed Test Flag
S ←1
S
1
CLS
Clear Signed Test Flag
S ←0
S
1
SEV
Set Twos Complement Overflow.
V ←1
V
1
CLV
Clear Twos Complement Overflow
V ←0
V
1
SET
Set T in SREG
T ←1
T
1
CLT
Clear T in SREG
T ←0
T
1
SEH
CLH
Set Half Carry Flag in SREG
Clear Half Carry Flag in SREG
H ←1
H ←0
H
H
1
1
Rd ←Rr
Rd+1:Rd ←Rr+1:Rr
None
1
None
1
1
DATA TRANSFER INSTRUCTIONS
MOV
Rd, Rr
Move Between Registers
MOVW
Rd, Rr
Copy Register Word
LDI
Rd, K
Load Immediate
Rd ←K
None
LD
Rd, X
Load Indirect
Rd ←(X)
None
2
LD
Rd, X+
Load Indirect and Post-Inc.
Rd ←(X), X ←X + 1
None
2
LD
Rd, - X
Load Indirect and Pre-Dec.
X ←X - 1, Rd ←(X)
None
2
LD
Rd, Y
Load Indirect
Rd ←(Y)
None
2
2
LD
Rd, Y+
Load Indirect and Post-Inc.
Rd ←(Y), Y ←Y + 1
None
LD
Rd, - Y
Load Indirect and Pre-Dec.
Y ←Y - 1, Rd ←(Y)
None
2
LDD
Rd,Y+q
Load Indirect with Displacement
Rd ←(Y + q)
None
2
2
LD
Rd, Z
Load Indirect
Rd ←(Z)
None
LD
Rd, Z+
Load Indirect and Post-Inc.
Rd ←(Z), Z ←Z+1
None
2
LD
Rd, -Z
Load Indirect and Pre-Dec.
Z ←Z - 1, Rd ←(Z)
None
2
LDD
Rd, Z+q
Load Indirect with Displacement
Rd ←(Z + q)
None
2
LDS
Rd, k
Load Direct from SRAM
Rd ←(k)
None
2
ST
X, Rr
Store Indirect
(X) ←Rr
None
2
ST
X+, Rr
Store Indirect and Post-Inc.
(X) ←Rr, X ←X + 1
None
2
ST
- X, Rr
Store Indirect and Pre-Dec.
X ←X - 1, (X) ←Rr
None
2
ST
Y, Rr
Store Indirect
(Y) ←Rr
None
2
ST
Y+, Rr
Store Indirect and Post-Inc.
(Y) ←Rr, Y ←Y + 1
None
2
2
ST
- Y, Rr
Store Indirect and Pre-Dec.
Y ←Y - 1, (Y) ←Rr
None
STD
Y+q,Rr
Store Indirect with Displacement
(Y + q) ←Rr
None
2
ST
Z, Rr
Store Indirect
(Z) ←Rr
None
2
ST
Z+, Rr
Store Indirect and Post-Inc.
(Z) ←Rr, Z ←Z + 1
None
2
ST
-Z, Rr
Store Indirect and Pre-Dec.
Z ←Z - 1, (Z) ←Rr
None
2
STD
Z+q,Rr
Store Indirect with Displacement
(Z + q) ←Rr
None
2
STS
k, Rr
Store Direct to SRAM
(k) ←Rr
None
2
Load Program Memory
R0 ←(Z)
None
3
LPM
Rd, Z
Load Program Memory
Rd ←(Z)
None
3
LPM
Rd, Z+
Load Program Memory and Post-Inc
Rd ←(Z), Z ←Z+1
None
3
Store Program Memory
(Z) ←R1:R0
None
-
In Port
Rd ←P
None
1
1
LPM
SPM
IN
Rd, P
OUT
P, Rr
Out Port
P ←Rr
None
PUSH
Rr
Push Register on Stack
STACK ←Rr
None
2
POP
Rd
Pop Register from Stack
Rd ←STACK
None
2
345
7647F–AVR–04/09
Mnemonics
Operands
Description
Operation
Flags
#Clocks
MCU CONTROL INSTRUCTIONS
NOP
No Operation
None
1
SLEEP
Sleep
(see specific descr. for Sleep function)
None
1
WDR
BREAK
Watchdog Reset
Break
(see specific descr. for WDR/timer)
For On-chip Debug Only
None
None
1
N/A
Note:
346
1. These Instructions are only available in “16K and 32K parts”
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
29. Register Summary
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
(0xFF)
Reserved
–
–
–
–
–
–
–
–
Page
(0xFE)
Reserved
–
–
–
–
–
–
–
–
(0xFD)
Reserved
–
–
–
–
–
–
–
–
(0xFC)
Reserved
–
–
–
–
–
–
–
–
(0xFB)
Reserved
–
–
–
–
–
–
–
–
(0xFA)
CANMSG
MSG 7
MSG 6
MSG 5
MSG 4
MSG 3
MSG 2
MSG 1
MSG 0
page 201
(0xF9)
CANSTMPH
TIMSTM15
TIMSTM14
TIMSTM13
TIMSTM12
TIMSTM11
TIMSTM10
TIMSTM9
TIMSTM8
page 201
(0xF8)
CANSTMPL
TIMSTM7
TIMSTM6
TIMSTM5
TIMSTM4
TIMSTM3
TIMSTM2
TIMSTM1
TIMSTM0
page 201
(0xF7)
CANIDM1
IDMSK28
IDMSK27
IDMSK26
IDMSK25
IDMSK24
IDMSK23
IDMSK22
IDMSK21
page 200
(0xF6)
CANIDM2
IDMSK20
IDMSK19
IDMSK18
IDMSK17
IDMSK16
IDMSK15
IDMSK14
IDMSK13
page 200
(0xF5)
CANIDM3
IDMSK12
IDMSK11
IDMSK10
IDMSK9
IDMSK8
IDMSK7
IDMSK6
IDMSK5
page 200
(0xF4)
CANIDM4
IDMSK4
IDMSK3
IDMSK2
IDMSK1
IDMSK0
RTRMSK
–
IDEMSK
page 200
(0xF3)
CANIDT1
IDT28
IDT27
IDT26
IDT25
IDT24
IDT23
IDT22
IDT21
page 198
(0xF2)
CANIDT2
IDT20
IDT19
IDT18
IDT17
IDT16
IDT15
IDT14
IDT13
page 198
(0xF1)
CANIDT3
IDT12
IDT11
IDT10
IDT9
IDT8
IDT7
IDT6
IDT5
page 198
(0xF0)
CANIDT4
IDT4
IDT3
IDT2
IDT1
IDT0
RTRTAG
RB1TAG
RB0TAG
page 198
(0xEF)
CANCDMOB
CONMOB1
CONMOB0
RPLV
IDE
DLC3
DLC2
DLC1
DLC0
page 197
(0xEE)
CANSTMOB
DLCW
TXOK
RXOK
BERR
SERR
CERR
FERR
AERR
page 196
(0xED)
CANPAGE
MOBNB3
MOBNB2
MOBNB1
MOBNB0
AINC
INDX2
INDX1
INDX0
page 196
(0xEC)
CANHPMOB
HPMOB3
HPMOB2
HPMOB1
HPMOB0
CGP3
CGP2
CGP1
CGP0
page 195
(0xEB)
CANREC
REC7
REC6
REC5
REC4
REC3
REC2
REC1
REC0
page 195
(0xEA)
CANTEC
TEC7
TEC6
TEC5
TEC4
TEC3
TEC2
TEC1
TEC0
page 195
(0xE9)
CANTTCH
TIMTTC15
TIMTTC14
TIMTTC13
TIMTTC12
TIMTTC11
TIMTTC10
TIMTTC9
TIMTTC8
page 195
(0xE8)
CANTTCL
TIMTTC7
TIMTTC6
TIMTTC5
TIMTTC4
TIMTTC3
TIMTTC2
TIMTTC1
TIMTTC0
page 195
(0xE7)
CANTIMH
CANTIM15
CANTIM14
CANTIM13
CANTIM12
CANTIM11
CANTIM10
CANTIM9
CANTIM8
page 195
(0xE6)
CANTIML
CANTIM7
CANTIM6
CANTIM5
CANTIM4
CANTIM3
CANTIM2
CANTIM1
CANTIM0
page 195
(0xE5)
CANTCON
TPRSC7
TPRSC6
TPRSC5
TPRSC4
TPRSC3
TPRSC2
TRPSC1
TPRSC0
page 194
(0xE4)
CANBT3
–
PHS22
PHS21
PHS20
PHS12
PHS11
PHS10
SMP
page 194
(0xE3)
CANBT2
–
SJW1
SJW0
–
PRS2
PRS1
PRS0
–
page 193
(0xE2)
CANBT1
–
BRP5
BRP4
BRP3
BRP2
BRP1
BRP0
–
page 192
(0xE1)
CANSIT1
–
–
–
–
–
–
–
–
page 192
(0xE0)
CANSIT2
–
–
SIT5
SIT4
SIT3
SIT2
SIT1
SIT0
page 192
(0xDF)
CANIE1
–
–
–
–
–
–
–
–
page 192
(0xDE)
CANIE2
–
–
IEMOB5
IEMOB4
IEMOB3
IEMOB2
IEMOB1
IEMOB0
page 192
(0xDD)
CANEN1
–
–
–
–
–
–
–
–
page 191
(0xDC)
CANEN2
–
–
ENMOB5
ENMOB4
ENMOB3
ENMOB2
ENMOB1
ENMOB0
page 191
(0xDB)
CANGIE
ENIT
ENBOFF
ENRX
ENTX
ENERR
ENBX
ENERG
ENOVRT
page 190
(0xDA)
CANGIT
CANIT
BOFFIT
OVRTIM
BXOK
SERG
CERG
FERG
AERG
page 189
(0xD9)
CANGSTA
–
OVRG
–
TXBSY
RXBSY
ENFG
BOFF
ERRP
page 188
(0xD8)
CANGCON
ABRQ
OVRQ
TTC
SYNTTC
LISTEN
TEST
ENA/STB
SWRES
page 187
(0xD7)
Reserved
–
–
–
–
–
–
–
–
(0xD6)
Reserved
–
–
–
–
–
–
–
–
(0xD5)
Reserved
–
–
–
–
–
–
–
–
(0xD4)
Reserved
–
–
–
–
–
–
–
–
(0xD3)
Reserved
–
–
–
–
–
–
–
–
(0xD2)
LINDAT
LDATA7
LDATA6
LDATA5
LDATA4
LDATA3
LDATA2
LDATA1
LDATA0
page 229
(0xD1)
LINSEL
–
–
–
–
/LAINC
LINDX2
LINDX1
LINDX0
page 229
(0xD0)
LINIDR
LP1
LP0
LID5 / LDL1
LID4 / LDL0
LID3
LID2
LID1
LID0
page 228
(0xCF)
LINDLR
LTXDL3
LTXDL2
LTXDL1
LTXDL0
LRXDL3
LRXDL2
LRXDL1
LRXDL0
page 228
(0xCE)
LINBRRH
–
–
–
–
LDIV11
LDIV10
LDIV9
LDIV8
page 227
(0xCD)
LINBRRL
LDIV7
LDIV6
LDIV5
LDIV4
LDIV3
LDIV2
LDIV1
LDIV0
page 227
(0xCC)
LINBTR
LDISR
–
LBT5
LBT4
LBT3
LBT2
LBT1
LBT0
page 227
(0xCB)
LINERR
LABORT
LTOERR
LOVERR
LFERR
LSERR
LPERR
LCERR
LBERR
page 226
(0xCA)
LINENIR
–
–
–
–
LENERR
LENIDOK
LENTXOK
LENRXOK
page 225
(0xC9)
LINSIR
LIDST2
LIDST1
LIDST0
LBUSY
LERR
LIDOK
LTXOK
LRXOK
page 224
(0xC8)
LINCR
LSWRES
LIN13
LCONF1
LCONF0
LENA
LCMD2
LCMD1
LCMD0
page 223
(0xC7)
Reserved
–
–
–
–
–
–
–
–
(0xC6)
Reserved
–
–
–
–
–
–
–
–
(0xC5)
Reserved
–
–
–
–
–
–
–
–
(0xC4)
Reserved
–
–
–
–
–
–
–
–
(0xC3)
Reserved
–
–
–
–
–
–
–
–
(0xC2)
Reserved
–
–
–
–
–
–
–
–
(0xC1)
Reserved
–
–
–
–
–
–
–
–
(0xC0)
Reserved
–
–
–
–
–
–
–
–
(0xBF)
Reserved
–
–
–
–
–
–
–
–
347
7647F–AVR–04/09
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
(0xBE)
Reserved
–
–
–
–
–
–
–
–
Page
(0xBD)
Reserved
–
–
–
–
–
–
–
–
(0xBC)(5)
PIFR
–
–
–
–
PEV2
PEV1
PEV0
PEOP
page 157
(0xBB)(5)
PIM
–
–
–
–
PEVE2
PEVE1
PEVE0
PEOPE
page 156
(0xBA)(5)
PMIC2
POVEN2
PISEL2
PELEV2
PFLTE2
PAOC2
PRFM22
PRFM21
PRFM20
page 155
(0xB9)(5)
PMIC1
POVEN1
PISEL1
PELEV1
PFLTE1
PAOC1
PRFM12
PRFM11
PRFM10
page 155
(0xB8)(5)
PMIC0
POVEN0
PISEL0
PELEV0
PFLTE0
PAOC0
PRFM02
PRFM01
PRFM00
page 155
(0xB7)(5)
PCTL
PPRE1
PPRE0
PCLKSEL
–
–
–
PCCYC
PRUN
page 154
(0xB6)(5)
POC
–
–
POEN2B
POEN2A
POEN1B
POEN1A
POEN0B
POEN0A
page 38
(0xB5)(5)
PCNF
–
–
PULOCK
PMODE
POPB
POPA
–
–
page 153
(0xB4)(5)
PSYNC
–
–
PSYNC21
PSYNC20
PSYNC11
PSYNC10
PSYNC01
PSYNC00
page 152
(0xB3)(5)
POCR_RBH
–
–
–
–
POCR_RB11
POCR_RB10
POCR_RB9
POCR_RB8
page 153
(0xB2)(5)
POCR_RBL
POCR_RB7
POCR_RB6
POCR_RB5
POCR_RB4
POCR_RB3
POCR_RB2
POCR_RB1
POCR_RB0
page 153
(0xB1)(5)
POCR2SBH
–
–
–
–
POCR2SB11
POCR2SB10
POCR2SB9
POCR2SB8
page 153
(0xB0)(5)
POCR2SBL
POCR2SB7
POCR2SB6
POCR2SB5
POCR2SB4
POCR2SB3
POCR2SB2
POCR2SB1
POCR2SB0
page 153
(0xAF)(5)
POCR2RAH
–
–
–
–
POCR2RA11
POCR2RA10
POCR2RA9
POCR2RA8
page 153
(0xAE)(5)
POCR2RAL
POCR2RA7
POCR2RA6
POCR2RA5
POCR2RA4
POCR2RA3
POCR2RA2
POCR2RA1
POCR2RA0
page 153
(0xAD)(5)
POCR2SAH
–
–
–
–
POCR2SA11
POCR2SA10
POCR2SA9
POCR2SA8
page 153
(0xAC)(5)
POCR2SAL
POCR2SA7
POCR2SA6
POCR2SA5
POCR2SA4
POCR2SA3
POCR2SA2
POCR2SA1
POCR2SA0
page 153
(0xAB)(5)
POCR1SBH
–
–
–
–
POCR1SB11
POCR1SB10
POCR1SB9
POCR1SB8
page 153
(0xAA)(5)
POCR1SBL
POCR1SB7
POCR1SB6
POCR1SB5
POCR1SB4
POCR1SB3
POCR1SB2
POCR1SB1
POCR1SB0
page 153
(0xA9)(5)
POCR1RAH
–
–
–
–
POCR1RA11
POCR1RA10
POCR1RA9
POCR1RA8
page 153
(0xA8)(5)
POCR1RAL
POCR1RA7
POCR1RA6
POCR1RA5
POCR1RA4
POCR1RA3
POCR1RA2
POCR1RA1
POCR1RA0
page 153
(0xA7)(5)
POCR1SAH
–
–
–
–
POCR1SA11
POCR1SA10
POCR1SA9
POCR1SA8
page 153
(0xA6)(5)
POCR1SAL
POCR1SA7
POCR1SA6
POCR1SA5
POCR1SA4
POCR1SA3
POCR1SA2
POCR1SA1
POCR1SA0
page 153
(0xA5)(5)
POCR0SBH
–
–
–
–
POCR0SB11
POCR0SB10
POCR0SB9
POCR0SB8
page 153
(0xA4)(5)
POCR0SBL
POCR0SB7
POCR0SB6
POCR0SB5
POCR0SB4
POCR0SB3
POCR0SB2
POCR0SB1
POCR0SB0
page 153
(0xA3)(5)
POCR0RAH
–
–
–
–
POCR0RA11
POCR0RA10
POCR0RA9
POCR0RA8
page 153
(0xA2)(5)
POCR0RAL
POCR0RA7
POCR0RA6
POCR0RA5
POCR0RA4
POCR0RA3
POCR0RA2
POCR0RA1
POCR0RA0
page 153
(0xA1)(5)
POCR0SAH
–
–
–
–
POCR0SA11
POCR0SA10
POCR0SA9
POCR0SA8
page 153
(0xA0)(5)
POCR0SAL
POCR0SA7
POCR0SA6
POCR0SA5
POCR0SA4
POCR0SA3
POCR0SA2
POCR0SA1
POCR0SA0
page 153
(0x9F)
Reserved
–
–
–
–
–
–
–
–
348
(0x9E)
Reserved
–
–
–
–
–
–
–
–
(0x9D)
Reserved
–
–
–
–
–
–
–
–
(0x9C)
Reserved
–
–
–
–
–
–
–
–
(0x9B)
Reserved
–
–
–
–
–
–
–
–
(0x9A)
Reserved
–
–
–
–
–
–
–
–
(0x99)
Reserved
–
–
–
–
–
–
–
–
(0x98)
Reserved
–
–
–
–
–
–
–
–
(0x97)
AC3CON
AC3EN
AC3IE
AC3IS1
AC3IS0
–
AC3M2
AC3M1
AC3M0
page 266
(0x96)
AC2CON
AC2EN
AC2IE
AC2IS1
AC2IS0
–
AC2M2
AC2M1
AC2M0
page 266
(0x95)
AC1CON
AC1EN
AC1IE
AC1IS1
AC1IS0
AC1ICE
AC1M2
AC1M1
AC1M0
page 265
(0x94)
AC0CON
AC0EN
AC0IE
AC0IS1
AC0IS0
ACCKSEL
AC0M2
AC0M1
AC0M0
page 264
(0x93)
Reserved
–
–
–
–
–
–
–
–
(0x92)
DACH
- / DAC9
- / DAC8
- / DAC7
- / DAC6
- / DAC5
- / DAC4
DAC9 / DAC3
DAC8 / DAC2
page 273
(0x91)
DACL
DAC7 / DAC1
DAC6 /DAC0
DAC5 / -
DAC4 / -
DAC3 / -
DAC2 / -
DAC1 / -
DAC0 /
page 273
(0x90)
DACON
DAATE
DATS2
DATS1
DATS0
–
DALA
DAOE
DAEN
page 272
(0x8F)
Reserved
–
–
–
–
–
–
–
–
(0x8E)
Reserved
–
–
–
–
–
–
–
–
(0x8D)
Reserved
–
–
–
–
–
–
–
–
(0x8C)
Reserved
–
–
–
–
–
–
–
–
(0x8B)
OCR1BH
OCR1B15
OCR1B14
OCR1B13
OCR1B12
OCR1B11
OCR1B10
OCR1B9
OCR1B8
page 133
(0x8A)
OCR1BL
OCR1B7
OCR1B6
OCR1B5
OCR1B4
OCR1B3
OCR1B2
OCR1B1
OCR1B0
page 134
(0x89)
OCR1AH
OCR1A15
OCR1A14
OCR1A13
OCR1A12
OCR1A11
OCR1A10
OCR1A9
OCR1A8
page 133
(0x88)
OCR1AL
OCR1A7
OCR1A6
OCR1A5
OCR1A4
OCR1A3
OCR1A2
OCR1A1
OCR1A0
page 133
page 134
(0x87)
ICR1H
ICR115
ICR114
ICR113
ICR112
ICR111
ICR110
ICR19
ICR18
(0x86)
ICR1L
ICR17
ICR16
ICR15
ICR14
ICR13
ICR12
ICR11
ICR10
page 134
(0x85)
TCNT1H
TCNT115
TCNT114
TCNT113
TCNT112
TCNT111
TCNT110
TCNT19
TCNT18
page 133
(0x84)
TCNT1L
TCNT17
TCNT16
TCNT15
TCNT14
TCNT13
TCNT12
TCNT11
TCNT10
page 133
(0x83)
Reserved
–
–
–
–
–
–
–
–
(0x82)
TCCR1C
FOC1A
FOC1B
–
–
–
–
–
–
(0x81)
TCCR1B
ICNC1
ICES1
–
WGM13
WGM12
CS12
CS11
CS10
page 133
page 132
(0x80)
TCCR1A
COM1A1
COM1A0
COM1B1
COM1B0
–
–
WGM11
WGM10
page 130
(0x7F)
DIDR1
–
AMP2PD
ACMP0D
AMP0PD
AMP0ND
ADC10D
ADC9D
ADC8D
page 250
(0x7E)
DIDR0
ADC7D
ADC6D
ADC5D
ADC4D
ADC3D
ADC2D
ADC1D
ADC0D
page 249
(0x7D)
Reserved
–
–
–
–
–
–
–
–
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Page
(0x7C)
ADMUX
REFS1
REFS0
ADLAR
–
MUX3
MUX2
MUX1
MUX0
page 38
(0x7B)
ADCSRB
ADHSM
ISRCEN
AREFEN
–
ADTS3
ADTS2
ADTS1
ADTS0
page 247
(0x7A)
ADCSRA
ADEN
ADSC
ADATE
ADIF
ADIE
ADPS2
ADPS1
ADPS0
page 246
(0x79)
ADCH
- / ADC9
- / ADC8
- / ADC7
- / ADC6
- / ADC5
- / ADC4
ADC9 / ADC3
ADC8 / ADC2
page 249
(0x78)
ADCL
ADC7 / ADC1
ADC6 / ADC0
ADC5 / -
ADC4 / -
ADC3 / -
ADC2 / -
ADC1 / -
ADC0 /
page 249
page 255
(0x77)
AMP2CSR
AMP2EN
AMP2IS
AMP2G1
AMP2G0
AMPCMP2
AMP2TS2
AMP2TS1
AMP2TS0
(0x76)
AMP1CSR
AMP1EN
AMP1IS
AMP1G1
AMP1G0
AMPCMP1
AMP1TS2
AMP1TS1
AMP1TS0
page 255
(0x75)
AMP0CSR
AMP0EN
AMP0IS
AMP0G1
AMP0G0
AMPCMP0
AMP0TS2
AMP0TS1
AMP0TS0
page 254
(0x74)
Reserved
–
–
–
–
–
–
–
–
(0x73)
Reserved
–
–
–
–
–
–
–
–
(0x72)
Reserved
–
–
–
–
–
–
–
–
(0x71)
Reserved
–
–
–
–
–
–
–
–
(0x70)
Reserved
–
–
–
–
–
–
–
–
(0x6F)
TIMSK1
–
–
ICIE1
–
–
OCIE1B
OCIE1A
TOIE1
page 134
(0x6E)
TIMSK0
–
–
–
–
–
OCIE0B
OCIE0A
TOIE0
page 105
(0x6D)
PCMSK3
–
–
–
–
–
PCINT26
PCINT25
PCINT24
page 85
(0x6C)
PCMSK2
PCINT23
PCINT22
PCINT21
PCINT20
PCINT19
PCINT18
PCINT17
PCINT16
page 86
(0x6B)
PCMSK1
PCINT15
PCINT14
PCINT13
PCINT12
PCINT11
PCINT10
PCINT9
PCINT8
page 86
(0x6A)
PCMSK0
PCINT7
PCINT6
PCINT5
PCINT4
PCINT3
PCINT2
PCINT1
PCINT0
page 86
(0x69)
EICRA
ISC31
ISC30
ISC21
ISC20
ISC11
ISC10
ISC01
ISC00
page 83
(0x68)
PCICR
–
–
–
–
PCIE3
PCIE2
PCIE1
PCIE0
page 84
(0x67)
Reserved
–
–
–
–
–
–
–
–
(0x66)
OSCCAL
–
CAL6
CAL5
CAL4
CAL3
CAL2
CAL1
CAL0
(0x65)
Reserved
–
–
–
–
–
–
–
–
(0x64)
PRR
–
PRCAN
PRPSC
PRTIM1
PRTIM0
PRSPI
PRLIN
PRADC
(0x63)
Reserved
–
–
–
–
–
–
–
–
(0x62)
Reserved
–
–
–
–
–
–
–
–
(0x61)
CLKPR
CLKPCE
–
–
–
CLKPS3
CLKPS2
CLKPS1
CLKPS0
page 38
(0x60)
WDTCSR
WDIF
WDIE
WDP3
WDCE
WDE
WDP2
WDP1
WDP0
page 55
0x3F (0x5F)
SREG
I
T
H
S
V
N
Z
C
page 14
0x3E (0x5E)
SPH
SP15
SP14
SP13
SP12
SP11
SP10
SP9
SP8
page 16
0x3D (0x5D)
SPL
SP7
SP6
SP5
SP4
SP3
SP2
SP1
SP0
page 16
0x3C (0x5C)
Reserved
–
–
–
–
–
–
–
–
0x3B (0x5B)
Reserved
–
–
–
–
–
–
–
–
0x3A (0x5A)
Reserved
–
–
–
–
–
–
–
–
0x39 (0x59)
Reserved
–
–
–
–
–
–
–
–
0x38 (0x58)
Reserved
–
–
–
–
–
–
–
–
0x37 (0x57)
SPMCSR
SPMIE
RWWSB
SIGRD
RWWSRE
BLBSET
PGWRT
PGERS
SPMEN
0x36 (0x56)
Reserved
–
–
–
–
–
–
–
–
page 34
page 43
page 284
0x35 (0x55)
MCUCR
SPIPS
–
–
PUD
–
–
IVSEL
IVCE
page 60 & page 69
0x34 (0x54)
MCUSR
–
–
–
–
WDRF
BORF
EXTRF
PORF
page 50
0x33 (0x53)
SMCR
–
–
–
–
SM2
SM1
SM0
SE
0x32 (0x52)
MSMCR
0x31 (0x51)
MONDR
0x30 (0x50)
ACSR
Monitor Stop Mode Control Register
Monitor Data Register
AC3IF
AC2IF
AC1IF
AC0IF
AC3O
page 40
reserved
reserved
AC2O
AC1O
AC0O
page 268
0x2F (0x4F)
Reserved
–
–
–
–
–
–
–
–
0x2E (0x4E)
SPDR
SPD7
SPD6
SPD5
SPD4
SPD3
SPD2
SPD1
SPD0
0x2D (0x4D)
SPSR
SPIF
WCOL
–
–
–
–
–
SPI2X
page 165
0x2C (0x4C)
SPCR
SPIE
SPE
DORD
MSTR
CPOL
CPHA
SPR1
SPR0
page 164
0x2B (0x4B)
Reserved
–
–
–
–
–
–
–
–
0x2A (0x4A)
Reserved
–
–
–
–
–
–
–
–
0x29 (0x49)
PLLCSR
-
-
-
-
-
PLLF
PLLE
PLOCK
page 36
0x28 (0x48)
OCR0B
OCR0B7
OCR0B6
OCR0B5
OCR0B4
OCR0B3
OCR0B2
OCR0B1
OCR0B0
page 105
page 166
0x27 (0x47)
OCR0A
OCR0A7
OCR0A6
OCR0A5
OCR0A4
OCR0A3
OCR0A2
OCR0A1
OCR0A0
page 105
0x26 (0x46)
TCNT0
TCNT07
TCNT06
TCNT05
TCNT04
TCNT03
TCNT02
TCNT01
TCNT00
page 105
0x25 (0x45)
TCCR0B
FOC0A
FOC0B
–
–
WGM02
CS02
CS01
CS00
page 104
0x24 (0x44)
TCCR0A
COM0A1
COM0A0
COM0B1
COM0B0
–
–
WGM01
WGM00
page 101
0x23 (0x43)
GTCCR
TSM
ICPSEL1
–
–
–
–
–
PSRSYNC
page 88
0x22 (0x42)
EEARH
–
–
–
–
–
–
EEAR9
EEAR8
page 23
0x21 (0x41)
EEARL
EEAR7
EEAR6
EEAR5
EEAR4
EEAR3
EEAR2
EEAR1
EEAR0
page 23
0x20 (0x40)
EEDR
EEDR7
EEDR6
EEDR5
EEDR4
EEDR3
EEDR2
EEDR1
EEDR0
page 23
0x1F (0x3F)
EECR
–
–
–
–
EERIE
EEMWE
EEWE
EERE
page 23
0x1E (0x3E)
GPIOR0
GPIOR07
GPIOR06
GPIOR05
GPIOR04
GPIOR03
GPIOR02
GPIOR01
GPIOR00
page 28
0x1D (0x3D)
EIMSK
–
–
–
–
INT3
INT2
INT1
INT0
page 83
0x1C (0x3C)
EIFR
–
–
–
–
INTF3
INTF2
INTF1
INTF0
page 84
349
7647F–AVR–04/09
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Page
0x1B (0x3B)
PCIFR
–
–
–
–
PCIF3
PCIF2
PCIF1
PCIF0
page 85
0x1A (0x3A)
GPIOR2
GPIOR27
GPIOR26
GPIOR25
GPIOR24
GPIOR23
GPIOR22
GPIOR21
GPIOR20
page 28
0x19 (0x39)
GPIOR1
GPIOR17
GPIOR16
GPIOR15
GPIOR14
GPIOR13
GPIOR12
GPIOR11
GPIOR10
page 28
0x18 (0x38)
Reserved
–
–
–
–
–
–
–
–
0x17 (0x37)
Reserved
–
–
–
–
–
–
–
–
0x16 (0x36)
TIFR1
–
–
ICF1
–
–
OCF1B
OCF1A
TOV1
page 135
0x15 (0x35)
TIFR0
–
–
–
–
–
OCF0B
OCF0A
TOV0
page 106
0x14 (0x34)
Reserved
–
–
–
–
–
–
–
–
0x13 (0x33)
Reserved
–
–
–
–
–
–
–
–
0x12 (0x32)
Reserved
–
–
–
–
–
–
–
–
0x11 (0x31)
Reserved
–
–
–
–
–
–
–
–
0x10 (0x30)
Reserved
–
–
–
–
–
–
–
–
0x0F (0x2F)
Reserved
–
–
–
–
–
–
–
–
0x0E (0x2E)
PORTE
–
–
–
–
–
PORTE2
PORTE1
PORTE0
page 81
0x0D (0x2D)
DDRE
–
–
–
–
–
DDE2
DDE1
DDE0
page 81
0x0C (0x2C)
PINE
–
–
–
–
–
PINE2
PINE1
PINE0
page 81
0x0B (0x2B)
PORTD
PORTD7
PORTD6
PORTD5
PORTD4
PORTD3
PORTD2
PORTD1
PORTD0
page 80
0x0A (0x2A)
DDRD
DDD7
DDD6
DDD5
DDD4
DDD3
DDD2
DDD1
DDD0
page 80
0x09 (0x29)
PIND
PIND7
PIND6
PIND5
PIND4
PIND3
PIND2
PIND1
PIND0
page 81
0x08 (0x28)
PORTC
PORTC7
PORTC6
PORTC5
PORTC4
PORTC3
PORTC2
PORTC1
PORTC0
page 80
0x07 (0x27)
DDRC
DDC7
DDC6
DDC5
DDC4
DDC3
DDC2
DDC1
DDC0
page 80
0x06 (0x26)
PINC
PINC7
PINC6
PINC5
PINC4
PINC3
PINC2
PINC1
PINC0
page 80
0x05 (0x25)
PORTB
PORTB7
PORTB6
PORTB5
PORTB4
PORTB3
PORTB2
PORTB1
PORTB0
page 80
0x04 (0x24)
DDRB
DDB7
DDB6
DDB5
DDB4
DDB3
DDB2
DDB1
DDB0
page 80
page 80
0x03 (0x23)
PINB
PINB7
PINB6
PINB5
PINB4
PINB3
PINB2
PINB1
PINB0
0x02 (0x22)
Reserved
–
–
–
–
–
–
–
–
0x01 (0x21)
Reserved
–
–
–
–
–
–
–
–
0x00 (0x20)
Reserved
–
–
–
–
–
–
–
–
Notes:
1. For compatibility with future devices, reserved bits should be written to zero if accessed. Reserved I/O memory addresses
should never be written.
2. I/O Registers within the address range 0x00 - 0x1F are directly bit-accessible using the SBI and CBI instructions. In these
registers, the value of single bits can be checked by using the SBIS and SBIC instructions.
3. Some of the status flags are cleared by writing a logical one to them. Note that, unlike most other AVRs, the CBI and SBI
instructions will only operate on the specified bit, and can therefore be used on registers containing such status flags. The
CBI and SBI instructions work with registers 0x00 to 0x1F only.
4. When using the I/O specific commands IN and OUT, the I/O addresses 0x00 - 0x3F must be used. When addressing I/O
Registers as data space using LD and ST instructions, 0x20 must be added to these addresses. The
ATmega16/32/64/M1/C1 is a complex microcontroller with more peripheral units than can be supported within the 64 location reserved in Opcode for the IN and OUT instructions. For the Extended I/O space from 0x60 - 0xFF in SRAM, only the
ST/STS/STD and LD/LDS/LDD instructions can be used.
5. These registers are only available on ATmega32/64M1. For other products described in this datasheet, these locations are
reserved.
350
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
30. Errata
30.1
30.1.1
Errata Summary
ATmega32M1/C1 Rev. C (Mask Revision)
• The AMPCMPx bits return 0
30.1.2
ATmega32M1/C1 Rev. B (Mask Revision)
• The AMPCMPx bits return 0
• No comparison when amplifier is used as comparator input and ADC input
• CRC calculation of diagnostic frames in LIN 2.x.
• Wrong TSOFFSET manufacturing calibration value
• PD0-PD3 set to outputs and PD4 pulled down following power-on with external reset active.
30.1.3
ATmega32M1/C1 Rev. A (Mask Revision)
• Inopportune reset of the CANIDM registers.
• The AMPCMPx bits return 0
• No comparison when amplifier is used as comparator input and ADC input
• CRC calculation of diagnostic frames in LIN 2.x.
• PD0-PD3 set to outputs and PD4 pulled down following power-on with external reset active.
30.1.4
Errata Description
1. Inopportune reset of the CANIDM registers
After the reception of a CAN frame in a MOb, the ID mask registers are reset.
Problem fix / workaround
Before enabling a MOb in reception, re-initialize the ID mask registers - CANIDM[4..1].
2. The AMPCMPx bits return 0
When they are read the AMPCMPx bits in AMPxCSR registers return 0.
Problem fix / workaround
If the reading of the AMPCMPx bits is required, store the AMPCMPx value in a variable in
memory before writing in the AMPxCSR register and read the variable when necessary.
3. No comparison when amplifier is used as comparator input and ADC input
When it is selected as ADC input, an amplifier receives no clock signal when the ADC is
stopped. In that case, if the amplifier is also used as comparator input, no analog signal is
propagated and no comparison is done.
Problem fix / workaround
Select another ADC channel rather than the working amplified channel.
4. CRC calculation of diagnostic frames in LIN 2.x.
Diagnostic frames of LIN 2.x use “classic checksum” calculation. Unfortunately, the setting
of the checksum model is enabled when the HEADER is transmitted/received. Usually, in
LIN 2.x the LIN/UART controller is initialized to process “enhanced checksums” and a slave
task does not know what kind of frame it will work on before checking the ID.
Problem fix / workaround
This workaround is to be implemented only in case of transmission/reception of diagnostics
frames.
351
7647F–AVR–04/09
a. Slave task of master node:
Before enabling the HEADER, the master must set the appropriate LIN13 bit value in
LINCR register.
b.
For slaves nodes, the workaround is in 2 parts:
– Before enabling the RESPONSE, use the following function:
void lin_wa_head(void) {
unsigned char temp;
temp = LINBTR;
LINCR = 0x00;
// It is not a RESET !
LINBTR = (1<<LDISR)|temp;
LINCR = (1<<LIN13)|(1<<LENA)|(0<<LCMD2)|(0<<LCMD1)|(0<<LCMD0);
LINDLR = 0x88;
// If it isn't already done
}
– Once the RESPONSE is received or sent (having RxOK or TxOK as well as
LERR), use the following function:
void lin_wa_tail(void) {
LINCR = 0x00;
// It is not a RESET !
LINBTR = 0x00;
LINCR = (0<<LIN13)|(1<<LENA)|(0<<LCMD2)|(0<<LCMD1)|(0<<LCMD0);
}
The time-out counter is disabled during the RESPONSE when the workaround is set.
5. Wrong TSOFFSET manufacturing calibration value.
Erroneous value of TSOFFSET programmed in signature byte.
(TSOFFSET was introduced from REVB silicon).
Problem fix / workaround
To identify RevB with wrong TSOFFSET value, check device signature byte at address
0X3F if value is not 0X42 (Ascii code ‘B’) then use the following formula.
TS_OFFSET(True) = (150*(1-TS_GAIN))+TS_OFFSET.
6. PD0-PD3 set to outputs and PD4 pulled down following power-on with external reset
active.
At power-on with the external reset signal active the four I/O lines PD0-PD3 may be forced
into an output state. Normally these lines should be in an input state. PD4 may be pulled
down with internal 220 kOhm resistor. Following release of the reset line (whatever is the
startup time) with the clock running the I/Os PD0-PD4 will adopt their intended input state.
Problem fix / workaround
None
352
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
31. Ordering Information
Table 31-1.
ATmega16/32/64/M1/C1 Ordering Codes
Memory Size
PSC
Power Supply
Ordering Code
Package
16K
Yes
2.7 - 5.5V
MEGA16M1-15AZ
MA
-40°C to 125°C
16K
Yes
2.7 - 5.5V
MEGA16M1-15MZ
PV
-40°C to 125°C
32K
No
2.7 - 5.5V
MEGA32C1-15AZ
MA
-40°C to 125°C
32K
No
2.7 - 5.5V
MEGA32C1-15MZ
PV
-40°C to 125°C
32K
Yes
2.7 - 5.5V
MEGA32M1-15AZ
MA
-40°C to 125°C
32K
Yes
2.7 - 5.5V
MEGA32M1-15MZ
PV
-40°C to 125°C
32K
Yes
2.7 - 5.5V
MEGA32M1-ESAZ
MA
Engineering Samples
32K
Yes
2.7 - 5.5V
MEGA32M1-ESMZ
PV
Engineering Samples
64K
No
2.7 - 5.5V
MEGA64C1-15AZ
MA
-40°C to 125°C
Note:
Operation Range
64K
No
2.7 - 5.5V
MEGA64C1-15MZ
PV
-40°C to 125°C
64K
No
2.7 - 5.5V
MEGA64C1-ESAZ
MA
Engineering Samples
64K
No
2.7 - 5.5V
MEGA64C1-ESMZ
PV
Engineering Samples
64K
Yes
2.7 - 5.5V
MEGA64M1-15AZ
MA
-40°C to 125°C
64K
Yes
2.7 - 5.5V
MEGA64M1-15MZ
PV
-40°C to 125°C
64K
Yes
2.7 - 5.5V
MEGA64M1-ESAZ
MA
Engineering Samples
64K
Yes
2.7 - 5.5V
MEGA64M1-ESMZ
PV
Engineering Samples
All packages are Pb free, fully LHF
32. Package Information
Package Type
MA
MA, 32 - Lead, 7x7 mm Body Size, 1.0 mm Body Thickness
0.8 mm Lead Pitch, Thin Profile Plastic Quad Flat Package (TQFP)
PV
PV, 32-Lead, 7.0x7.0 mm Body, 0.65 mm Pitch
Quad Flat No Lead Package (QFN)
353
7647F–AVR–04/09
32.1
354
TQFP32
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
32.2
QFN32
355
7647F–AVR–04/09
33. Datasheet Revision History for ATmega16/32/64/M1/C1
Please note that the following page numbers referred to in this section refer to the specific revision mentioned, not to this document.
33.1
7647A
1. First document revision
33.2
7647B
1. Give the good signature for the CAN only product See “Signature Bytes” on page 300.
2. Provide the PCICR address in the “Register Summary” on page 347
3. Locate the SIGRD bit in SPMCSR in the “Register Summary” on page 347
4. Give the maximum clock of amplifiers See “Amplifier” on page 250.
5. Add ADHSM description. See “ADC Control and Status Register B– ADCSRB” on page
247.
6. Give the frequency value selected with the ACCKSEL bit. See “Analog Comparator 0
Control Register – AC0CON” on page 264.
7. Add some analog feature consideration See “Analog Feature Considerations” on page
275.
8. Add errata 2, 3 and 4. See “Errata Description” on page 351.
9. Update the Current Source resistor table See “LIN Current Source” on page 259.
33.3
7647C
1. Added ATmega16M1 product offering.
2. Modified Clock Distribution diagram, Figure 5-1 on page 29.
3. Modified PLL Clocking Sytem diagram, Figure 5-3 on page 35.
4. Modified Section 5.6.1 “Internal PLL” on page 34.
5. Updated Analog Comparator Hysteresis Voltage, Section 26.2 “DC Characteristics” on
page 317.
6. Updated Current Source Value, Section 26.2 “DC Characteristics” on page 317.
7. Updated Table 25-12 on page 303.
8. Updated Table 25-13 on page 303.
9. Added PCICR definition “Register Summary” on page 347.
33.4
7647D
1. Manufacturing Calibration update.
2. Errata update
356
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
33.5
7647E
1. Flash Boot Loader Parameters updated
2. DC Characteristics updated
3. ISRC - Current Source updated
4. Analog Comparator updated
5. Clock Characteristics updated
6. ADC noise canceller updated
7. Brown-out Detection updated
8. Ordering Information updated
9. ADC Characteristics updated
10. Typical Characteristics updated
33.6
7647F
1. Package Information updated
357
7647F–AVR–04/09
34. Table of Contents
Features ..................................................................................................... 1
1
Pin Configurations ................................................................................... 3
1.1
2
3
4
5
358
Pin Descriptions .................................................................................................5
Overview ................................................................................................... 8
2.1
Block Diagram ...................................................................................................8
2.2
Automotive Quality Grade .................................................................................9
2.3
Pin Descriptions ...............................................................................................10
2.4
About Code Examples .....................................................................................11
AVR CPU Core
.................................................................................... 12
3.1
Introduction ......................................................................................................12
3.2
Architectural Overview .....................................................................................12
3.3
ALU – Arithmetic Logic Unit .............................................................................13
3.4
Status Register ................................................................................................14
3.5
General Purpose Register File ........................................................................15
3.6
Stack Pointer ...................................................................................................16
3.7
Instruction Execution Timing ...........................................................................17
3.8
Reset and Interrupt Handling ...........................................................................17
Memories ................................................................................................ 20
4.1
In-System Reprogrammable Flash Program Memory .....................................20
4.2
SRAM Data Memory ........................................................................................21
4.3
EEPROM Data Memory ..................................................................................22
4.4
I/O Memory ......................................................................................................28
4.5
General Purpose I/O Registers .......................................................................28
System Clock ......................................................................................... 29
5.1
Clock Systems and their Distribution ...............................................................29
5.2
Clock Sources .................................................................................................30
5.3
Default Clock Source .......................................................................................31
5.4
Low Power Crystal Oscillator ...........................................................................31
5.5
Calibrated Internal RC Oscillator .....................................................................33
5.6
PLL ..................................................................................................................34
5.7
128 kHz Internal Oscillator ..............................................................................36
5.8
External Clock .................................................................................................36
5.9
Clock Output Buffer .........................................................................................37
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
5.10
6
7
8
Power Management and Sleep Modes ................................................ 40
6.1
Sleep Mode Control Register ..........................................................................40
6.2
Idle Mode .........................................................................................................41
6.3
ADC Noise Reduction Mode ............................................................................41
6.4
Power-down Mode ...........................................................................................41
6.5
Standby Mode .................................................................................................42
6.6
Power Reduction Register ...............................................................................42
6.7
Minimizing Power Consumption ......................................................................44
System Control and Reset .................................................................... 46
7.1
Resetting the AVR ...........................................................................................46
7.2
Reset Sources .................................................................................................46
7.3
Internal Voltage Reference ..............................................................................51
7.4
Watchdog Timer ..............................................................................................52
Interrupts ................................................................................................ 57
8.1
9
System Clock Prescaler ..................................................................................37
Interrupt Vectors in ATmega16/32/64/M1/C1 ..................................................57
I/O-Ports .................................................................................................. 62
9.1
Introduction ......................................................................................................62
9.2
Ports as General Digital I/O .............................................................................63
9.3
Alternate Port Functions ..................................................................................67
9.4
Register Description for I/O-Ports ....................................................................80
10 External Interrupts ................................................................................. 82
10.1
Pin Change Interrupt Timing ............................................................................82
10.2
External Interrupt Control Register A – EICRA ................................................83
11 Timer/Counter0 and Timer/Counter1 Prescalers ................................ 87
11.1
Internal Clock Source ......................................................................................87
11.2
Prescaler Reset ...............................................................................................87
11.3
External Clock Source .....................................................................................87
12 8-bit Timer/Counter0 with PWM ............................................................ 90
12.1
Overview ..........................................................................................................90
12.2
Timer/Counter Clock Sources .........................................................................91
12.3
Counter Unit ....................................................................................................91
12.4
Output Compare Unit .......................................................................................92
12.5
Compare Match Output Unit ............................................................................94
359
7647F–AVR–04/09
12.6
Modes of Operation .........................................................................................95
12.7
Timer/Counter Timing Diagrams .....................................................................99
12.8
8-bit Timer/Counter Register Description ......................................................101
13 16-bit Timer/Counter1 with PWM ........................................................ 107
13.1
Overview ........................................................................................................107
13.2
Accessing 16-bit Registers ............................................................................109
13.3
Timer/Counter Clock Sources .......................................................................112
13.4
Counter Unit ..................................................................................................113
13.5
Input Capture Unit .........................................................................................114
13.6
Output Compare Units ...................................................................................116
13.7
Compare Match Output Unit ..........................................................................118
13.8
Modes of Operation .......................................................................................120
13.9
Timer/Counter Timing Diagrams ...................................................................128
13.10
16-bit Timer/Counter Register Description ....................................................130
14 Power Stage Controller – (PSC) (only ATmega16/32/64M1) ............. 136
14.1
Features ........................................................................................................136
14.2
Overview ........................................................................................................136
14.3
Accessing 16-bit Registers ............................................................................136
14.4
PSC Description ............................................................................................137
14.5
Functional Description ...................................................................................138
14.6
Update of Values ...........................................................................................142
14.7
Overlap Protection .........................................................................................143
14.8
Signal Description ..........................................................................................144
14.9
PSC Input ......................................................................................................146
14.10
PSC Input Modes 001b to 10xb: Deactivate outputs without changing
timing. ............................................................................................................148
14.11
PSC Input Mode 11xb: Halt PSC and Wait for Software Action ....................148
14.12
Analog Synchronization .................................................................................149
14.13
Interrupt Handling ..........................................................................................149
14.14
PSC Clock Sources .......................................................................................149
14.15
Interrupts .......................................................................................................150
14.16
PSC Register Definition 151
15 Serial Peripheral Interface – SPI ......................................................... 158
360
15.1
Features ........................................................................................................158
15.2
SS Pin Functionality ......................................................................................163
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
15.3
Data Modes ...................................................................................................166
16 Controller Area Network - CAN ........................................................... 168
16.1
Features ........................................................................................................168
16.2
CAN Protocol .................................................................................................168
16.3
CAN Controller ..............................................................................................174
16.4
CAN Channel .................................................................................................175
16.5
Message Objects ...........................................................................................178
16.6
CAN Timer .....................................................................................................182
16.7
Error Management .........................................................................................183
16.8
Interrupts .......................................................................................................184
16.9
CAN Register Description ..............................................................................186
16.10
General CAN Registers .................................................................................187
16.11
MOb Registers ...............................................................................................196
16.12
Examples of CAN Baud Rate Setting ............................................................202
17 LIN / UART - Local Interconnect Network Controller or UART ........ 204
17.1
LIN Features ..................................................................................................204
17.2
UART Features ..............................................................................................204
17.3
LIN Protocol ...................................................................................................205
17.4
LIN / UART Controller ....................................................................................206
17.5
LIN / UART Description .................................................................................212
17.6
LIN / UART Register Description ..................................................................223
18 Analog to Digital Converter - ADC ..................................................... 230
18.1
Features ........................................................................................................230
18.2
Operation .......................................................................................................232
18.3
Starting a Conversion ....................................................................................232
18.4
Prescaling and Conversion Timing ................................................................233
18.5
Changing Channel or Reference Selection ...................................................235
18.6
ADC Noise Canceler .....................................................................................237
18.7
ADC Conversion Result .................................................................................241
18.8
Temperature Measurement ...........................................................................243
18.9
ADC Register Description ..............................................................................245
18.10
Amplifier .........................................................................................................250
18.11
Amplifier Control Registers ............................................................................254
361
7647F–AVR–04/09
19 ISRC - Current Source ......................................................................... 258
19.1
Features ........................................................................................................258
19.2
Typical applications .......................................................................................259
19.3
Control Register .............................................................................................261
20 Analog Comparator ............................................................................. 262
20.1
Features ........................................................................................................262
20.2
Overview ........................................................................................................262
20.3
Use of ADC Amplifiers ...................................................................................263
20.4
Analog Comparator Register Description ......................................................264
21 Digital to Analog Converter - DAC ..................................................... 270
21.1
Features ........................................................................................................270
21.2
Operation .......................................................................................................271
21.3
Starting a Conversion ....................................................................................271
21.4
DAC Register Description ..............................................................................272
22 Analog Feature Considerations........................................................... 275
22.1
Purpose .........................................................................................................275
22.2
Use of an Amplifier as Comparator Input ......................................................275
22.3
Use of an Amplifier as Comparator Input and ADC Input ..............................275
22.4
Analog Peripheral Clock Sources ..................................................................276
23 debugWIRE On-chip Debug System .................................................. 277
23.1
Features ........................................................................................................277
23.2
Overview ........................................................................................................277
23.3
Physical Interface ..........................................................................................277
23.4
Software Break Points ...................................................................................278
23.5
Limitations of debugWIRE .............................................................................278
23.6
debugWIRE Related Register in I/O Memory ................................................278
24 Boot Loader Support – Read-While-Write Self-Programming
ATmega16/32/64/M1/C1 ....................................................................... 279
362
24.1
Boot Loader Features ....................................................................................279
24.2
Application and Boot Loader Flash Sections .................................................279
24.3
Read-While-Write and No Read-While-Write Flash Sections ........................280
24.4
Boot Loader Lock Bits ...................................................................................282
24.5
Entering the Boot Loader Program ................................................................283
24.6
Addressing the Flash During Self-Programming ...........................................285
ATmega16/32/64/M1/C1
7647F–AVR–04/09
ATmega16/32/64/M1/C1
24.7
Self-Programming the Flash ..........................................................................286
25 Memory Programming ......................................................................... 296
25.1
Program And Data Memory Lock Bits ...........................................................296
25.2
Fuse Bits ........................................................................................................297
25.3
PSC Output Behavior During Reset ..............................................................298
25.4
Signature Bytes .............................................................................................300
25.5
Calibration Byte .............................................................................................301
25.6
Parallel Programming Parameters, Pin Mapping, and Commands ...............301
25.7
Serial Programming Pin Mapping ..................................................................304
25.8
Parallel Programming ....................................................................................304
25.9
Serial Downloading ........................................................................................313
26 Electrical Characteristics .................................................................... 317
26.1
Absolute Maximum Ratings* .........................................................................317
26.2
DC Characteristics .........................................................................................317
26.3
Clock Characteristics .....................................................................................319
26.4
External Clock Drive Characteristics .............................................................319
26.5
Maximum Speed vs. VCC ...............................................................................320
26.6
PLL Characteristics .......................................................................................320
26.7
SPI Timing Characteristics ............................................................................321
26.8
ADC Characteristics ......................................................................................322
26.9
Parallel Programming Characteristics ...........................................................324
27 ATmega16/32/64/M1/C1 Typical Characteristics ............................... 327
27.1
Active Supply Current ....................................................................................328
27.2
Idle Supply Current ........................................................................................330
27.3
Power-Down Supply Current .........................................................................332
27.4
Pin Pull-up .....................................................................................................333
27.5
Pin Driver Strength ........................................................................................335
27.6
Pin Thresholds and Hysteresis ......................................................................337
27.7
BOD Thresholds and Analog Comparator Hysterisis ....................................340
27.8
Analog Reference ..........................................................................................342
27.9
Internal Oscillator Speed ...............................................................................342
28 Instruction Set Summary .................................................................... 344
29 Register Summary ............................................................................... 347
363
7647F–AVR–04/09
30 Errata ..................................................................................................... 351
30.1
Errata Summary ............................................................................................351
31 Ordering Information ........................................................................... 353
32 Package Information ............................................................................ 353
32.1
TQFP32 .........................................................................................................354
32.2
QFN32 ...........................................................................................................355
33 Datasheet Revision History for ATmega16/32/64/M1/C1 .................. 356
34 Table of Contents ................................................................................. 357
364
ATmega16/32/64/M1/C1
7647F–AVR–04/09
Headquarters
International
Atmel Corporation
2325 Orchard Parkway
San Jose, CA 95131
USA
Tel: 1(408) 441-0311
Fax: 1(408) 487-2600
Atmel Asia
Unit 1-5 & 16, 19/F
BEA Tower, Millennium City 5
418 Kwun Tong Road
Kwun Tong, Kowloon
Hong Kong
Tel: (852) 2245-6100
Fax: (852) 2722-1369
Atmel Europe
Le Krebs
8, Rue Jean-Pierre Timbaud
BP 309
78054
Saint-Quentin-en-Yvelines Cedex
France
Tel: (33) 1-30-60-70-00
Fax: (33) 1-30-60-71-11
Atmel Japan
9F, Tonetsu Shinkawa Bldg.
1-24-8 Shinkawa
Chuo-ku, Tokyo 104-0033
Japan
Tel: (81) 3-3523-3551
Fax: (81) 3-3523-7581
Technical Support
[email protected]
Sales Contact
www.atmel.com/contacts
Product Contact
Web Site
www.atmel.com
Literature Requests
www.atmel.com/literature
Disclaimer: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise, to any
intellectual property right is granted by this document or in connection with the sale of Atmel products. EXCEPT AS SET FORTH IN ATMEL’S TERMS AND CONDITIONS OF SALE LOCATED ON ATMEL’S WEB SITE, ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY
WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF
THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Atmel makes no
representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications
and product descriptions at any time without notice. Atmel does not make any commitment to update the information contained herein. Unless specifically provided
otherwise, Atmel products are not suitable for, and shall not be used in, automotive applications. Atmel’s products are not intended, authorized, or warranted for use
as components in applications intended to support or sustain life.
© 2009 Atmel Corporation. All rights reserved. Atmel®, Atmel logo and combinations thereof, AVR ®, AVR® logo, AVR Studio ® and others are registered trademarks or trademarks of Atmel Corporation or its subsidiaries. Other terms and product names may be trademarks of others.
7647F–AVR–04/09