ATmega16/32/64M1 - Complete

8-bit Atmel megaAVR Microcontroller
ATmega16M1 / ATmega32M1 / ATmega64M1
Features
•
•
•
•
•
•
•
•
•
•
•
•
High performance, low power Atmel® AVR® 8-bit microcontroller
Advanced RISC architecture
– 131 powerful instructions - most single clock cycle execution
– 32 × 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
– 16/32/64KBytes flash of in-system programmable program memory
– 512B/1K/2KBytes of in-system programmable EEPROM
– 1/2/4KBytes internal SRAM
– Write/erase cycles: 10,000 flash/ 100,000 EEPROM
– Data retention: 20 years at 85°C/ 100 years at 25°C (1)
– Optional boot code section with independent lock bits
In-system programming by on-chip boot program
True read-while-write operation
– Programming lock for flash program and EEPROM data security
On-chip debug interface (debugWIRE)
CAN 2.0A/B with six message objects - ISO 16845 certified
LIN 2.1 and 1.3 controller or 8-bit UART
One 12-bit high speed PSC (power stage controller)
– 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 three fully differential ADC channel pairs
Programmable gain (5×, 10×, 20×, 40×) 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 ±2% current source (LIN node identification)
– Interrupt and wake-up on pin change
– Programmable watchdog timer with separate on-chip oscillator
– On-chip temperature 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 (16MHz)
– Internal calibrated RC oscillator (8MHz)
– On-chip PLL for fast PWM (32MHz, 64MHz) and CPU (16MHz)
Operating voltage: 2.7V - 5.5V
Extended operating temperature:
– -40°C to +85°C
Core speed grade:
– 0 - 8MHz @ 2.7 - 4.5V
– 0 - 16MHz @ 4.5 - 5.5V
8209E–AVR–11/2012
1. Pin configurations
PB7 (ADC4/PSCOUT0B/SCK/PCINT7)
PB6 (ADC7/PSCOUT1B/PCINT6)
PB5 (ADC6/INT2/ACMPN1/AMP2-/PCINT5)
PC7 (D2A/AMP2+/PCINT15)
PD0 (PCINT16/PSCOUT0A)
PC0(PCINT8/INT3/PSCOUT1A)
32
31
30
29
28
27
26
25
PE0 (PCINT24/RESET/OCD)
Atmel ATmega16M1/32M1/64M1 TQFP32/QFN32 (7mm × 7mm) package.
PD1(PCINT17/PSCIN0/CLKO)
Figure 1-1.
24
23
22
21
20
19
18
17
PB4 (AMP0+/PCINT4)
PB3 (AMP0-/PCINT3)
PC6 (ADC10/ACMP1/PCINT14)
AREF(ISRC)
AGND
AVCC
PC5 (ADC9/ACMP3/AMP1+/PCINT13)
PC4 (ADC8/ACMPN3/AMP1-/PCINT12)
9
10
11
12
13
14
15
16
1
2
3
4
5
6
7
8
(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
(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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
2
1.1
Pin descriptions
Table 1-1.
Pinout 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, and 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)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
3
Table 1-1.
Pinout description. (Continued)
QFN32 pin
number
Mnemonic
Type
Name, function, and 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)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
4
Table 1-1.
Pinout description. (Continued)
QFN32 pin
number
Mnemonic
Type
Name, function, and 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 Atmel Atmega32M1/64M1.
2. On the engineering samples, the ACMPN3 alternate function is not located on PC4. It is located on PE2.
2. Overview
The Atmel ATmega16M1/32M1/64M1 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 ATmega16M1/32M1/64M1
achieves throughputs approaching 1 MIPS per MHz allowing the system designer to optimize power consumption
versus processing speed.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
5
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
Indirect addressing
Control lines
Watchdog
timer
Four analog
comparators
Instruction
decoder
Direct addressing
2.1
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.
The Atmel ATmega16M1/32M1/64M1 provides the following features: 16/32/64Kbytes of In-System Programmable
Flash with Read-While-Write capabilities, 512B/1K/2Kbytes EEPROM, 1/2/4Kbytes 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
6
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 the Atmel 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
ATmega16M1/32M1/64M1 is a powerful microcontroller that provides a highly flexible and cost effective solution to
many embedded control applications.
The Atmel ATmega16M1/32M1/64M1 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
Pin descriptions
2.2.1
VCC
Digital supply voltage.
2.2.2
GND
Ground.
2.2.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 ATmega16M1/32M1/64M1 as listed on page 67.
2.2.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 ATmega16M1/32M1/64M1 as listed on page 70.
2.2.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 Atmel ATmega16M1/32M1/64M1 as listed on
page 73.
2.2.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
7
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
“System and reset characteristics” on page 297. Shorter pulses are not guaranteed to generate a Reset.
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 76 and “Clock systems and their distribution” on page 26.
2.2.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 lowpass filter.
2.2.8
AREF
This is the analog reference pin for the A/D Converter.
3. Resources
A comprehensive set of development tools, application notes and datasheets are available for download on
http://www.atmel.com/avr.
4. About code examples
This documentation contains simple code examples that briefly show how to use various parts of the device. 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.
These code examples assume that the part specific header file is included before compilation. 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".
Note:
1. See for details
5. Data retention
Reliability Qualification results show that the projected data retention failure rate is much less than 1ppm over 20
years at 85°C or 100 years at 25°C.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
8
6. AVR CPU core
Overview
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.
Figure 6-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
Instruction
decoder
Control lines
Indirect addressing
Instruction
register
Direct addressing
6.1
Interrupt
unit
SPI
unit
Watchdog
timer
ALU
Analog
Comparator
c
I/O module 1
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.
The fast-access Register File contains 32 × 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
9
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-bit 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 ATmega16M1/32M1/64M1 has Extended I/O space from 0x60 - 0xFF in
SRAM where only the ST/STS/STD and LD/LDS/LDD instructions can be used.
6.2
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 bitfunctions. 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.
6.3
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
10
6.3.1
SREG – AVR Status Register
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 summary” on page 319 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 summary” on page 319 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 summary” on page 319 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 summary” on page 319 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 summary” on
page 319 for detailed information.
• Bit 0 – C: Carry Flag
The Carry Flag C indicates a carry in an arithmetic or logic operation. See the “Instruction set summary” on page
319 for detailed information.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
11
6.4
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 6-2 shows the structure of the 32 general purpose working registers in the CPU.
Figure 6-2.
AVR CPU general purpose working registers.
7
0
Addr.
R0
0x00
R1
0x01
R2
0x02
…
R13
0x0D
R14
0x0E
Purpose
R15
0x0F
Working
R16
0x10
Registers
R17
0x11
General
…
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 6-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.
6.4.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 6-3 on page 13.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
12
Figure 6-3.
The X-, Y-, and Z-registers.
15
X-register
XH
7
XL
0
R27 (0x1B)
15
Y-register
0
R26 (0x1A)
YH
7
YL
0
R29 (0x1D)
Z-register
0
7
0
7
0
R28 (0x1C)
15
ZH
7
0
R31 (0x1F)
ZL
7
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 summary” on page 319 for details).
6.5
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. Note that the Stack is implemented as growing from higher to lower memory
locations. The Stack Pointer Register always points to the top of the Stack. The Stack Pointer points to the data
SRAM Stack area where the Subroutine and Interrupt Stacks are located. A Stack PUSH command will decrease
the Stack Pointer.
The Stack in the data SRAM must be defined by the program before any subroutine calls are executed or interrupts
are enabled. Initial Stack Pointer value equals the last address of the internal SRAM and the Stack Pointer must be
set to point above start of the SRAM, see Figure 7-2 on page 18.
See Table 6-1 for Stack Pointer details.
Table 6-1.
Stack pointer instructions.
Instruction
Stack pointer
Description
PUSH
Decremented by 1
Data is pushed onto the stack
CALL
ICALL
RCALL
Decremented by 2
Return address is pushed onto the stack with a subroutine call or
interrupt
POP
Incremented by 1
Data is popped from the stack
RET
RETI
Incremented by 2
Return address is popped from the stack with return from
subroutine or return from interrupt
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
13
6.5.1
SPH and SPL – Stack Pointer High and Stack Pointer Low Register
Bit
Read/write
Initial value
6.6
15
14
13
12
11
10
9
SP15
SP14
SP13
SP12
SP11
SP10
SP9
8
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
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 6-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 6-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 6-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 6-5.
Single cycle ALU operation.
T1
T2
T3
T4
clkCPU
Total Execution Time
Register Operands Fetch
ALU Operation Execute
Result Write Back
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
14
6.7
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 274 for details.
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 50. 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 50 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” on page 258.
6.7.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
15
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) */
6.7.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
16
7. Memories
7.1
Overview
This section describes the different memories in the Atmel ATmega16M1/32M1/64M1. The AVR architecture has
two main memory spaces, the Data Memory and the Program Memory space. In addition, the
ATmega16M1/32M1/64M1 features an EEPROM Memory for data storage. All three memory spaces are linear
and regular.
7.2
In-system reprogrammable flash program memory
The ATmega16M1/32M1/64M1 contains 16/32/64K bytes On-chip In-System Reprogrammable Flash memory for
program storage. Since all AVR instructions are 16 bits or 32 bits wide, the Flash is organized as 16K × 16 / 32K ×
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 ATmega16M1/32M1/64M1 Program Counter (PC) is 14 bits wide, thus addressing the 16K 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” on page 258. “Memory programming” on page 274 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 14.
Figure 7-1.
Program memory map.
Program memory
0x0000
Application flash section
Boot flash section
0x1FFF/0x3FFF/0x7FFF
7.3
SRAM data memory
Figure 7-2 shows how the Atmel ATmega16M1/32M1/64M1 SRAM memory is organized.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
17
The ATmega16M1/32M1/64M1 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 1/2/4K 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-register
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 1/2/4K bytes of
internal data SRAM in the ATmega16M1/32M1/64M1 are all accessible through all these addressing modes. The
Register File is described in “General purpose register file” on page 12.
Figure 7-2.
Data memory map1/2/4K.
Data memory
32 registers
64 I/O registers
160 ext I/O reg.
0x0000 - 0x001F
0x0020 - 0x005F
0x0060 - 0x00FF
0x0100
Internal SRAM
(1024/2048/4096 x 8)
0x04FF/0x08FF/0x10FF
7.3.1
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 7-3 on page 19.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
18
Figure 7-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
7.4
Next instruction
EEPROM data memory
The Atmel ATmega16M1/32M1/64M1 contains 512B/1K/2K 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
289 , and “Parallel programming parameters, pin mapping, and commands” on page 278 respectively.
7.4.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 7-2 on page 23. 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 19 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.
7.4.2
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:
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
19
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.
7.5
I/O Memory
The I/O space definition of the Atmel ATmega16M1/32M1/64M1 is shown in “Register summary” on page 315.
All ATmega16M1/32M1/64M1 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 ATmega16M1/32M1/64M1 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.
7.6
General purpose I/O registers
The ATmega16M1/32M1/64M1 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. See “Register
description” on page 21 for details.
The General Purpose I/O Registers, within the address range 0x00 - 0x1F, are directly bit-accessible using the
SBI, CBI, SBIS, and SBIC instructions.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
20
7.7
Register description
7.7.1
EEARH and EEARL – The EEPROM Address Registers
Bit
Read/write
Initial value
15
14
13
12
11
10
9
8
–
–
–
–
–
-
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
0
0
X
X
X
X
X
X
X
X
X
• Bits 15:10 – Res: Reserved
These bits are reserved and will always read as zero.
• Bits 9:0 – EEAR[8:0]: EEPROM Address
The EEPROM Address Registers – EEARH and EEARL specify the EEPROM address in the 512B/1K/2Kbytes
EEPROM space. The EEPROM data bytes are addressed linearly between 0 and 1023. The initial value of EEAR
is undefined. A proper value must be written before the EEPROM may be accessed.
7.7.2
EEDR – The EEPROM Data Register
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 – EEDR[7: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.
7.7.3
EECR – The EEPROM Control Register
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 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 7-1 on page 22. 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
21
Table 7-1.
EEPROM mode bits.
EEPM1
EEPM0
Programming
time
0
0
3.4ms
Erase and write in one operation (atomic operation)
0
1
1.8ms
Erase only
1
0
1.8ms
Write only
1
1
–
Operation
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” on page 258 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
22
• 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 7-2 lists the typical programming time for
EEPROM access from the CPU.
Table 7-2.
EEPROM programming time.
Symbol
EEPROM write
(from CPU)
Number of calibrated RC oscillator cycles
Typ programming time
26368
3.3ms
The following code examples show one assembly and one C function for writing to the EEPROM. The examples
assume that interrupts are controlled (for example 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
23
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);
}
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
24
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;
}
7.7.4
GPIOR0 – General Purpose I/O Register 0
Bit
7
6
5
4
3
2
1
0
GPIOR07
GPIOR06
GPIOR05
GPIOR04
GPIOR03
GPIOR02
GPIOR01
GPIOR00
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.7.5
GPIOR0
GPIOR1 – General Purpose I/O Register 1
Bit
7
6
5
4
3
2
1
0
GPIOR17
GPIOR16
GPIOR15
GPIOR14
GPIOR13
GPIOR12
GPIOR11
GPIOR10
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.7.6
GPIOR1
GPIOR2 – General Purpose I/O Register 2
Bit
7
6
5
4
3
2
1
0
GPIOR27
GPIOR26
GPIOR25
GPIOR24
GPIOR23
GPIOR22
GPIOR21
GPIOR20
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
25
8. System clock and their distribution
8.1
Clock systems and their distribution
Figure 8-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 35. The clock systems are
detailed below.
Figure 8-1.
Clock distribution.
Fast
peripherals
General I/O
modules
CLK PLL
ADC
CPU core
Flash and
EEPROM
RAM
clkADC
PLL
clkI/O
clkCPU
AVR clock
control unit
clkFLASH
Reset logic
Source Clock
Clock
multiplexer
External clock
Watchdog timer
Watchdog Clock
Watchdog
oscillator
(Crystal
oscillator)
Calibrated RC
oscillator
8.1.1
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.
8.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.
8.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.
8.1.4
PLL Clock – clkPLL
The PLL clock allows the fast peripherals to be clocked directly from a 64/32MHz clock. A 16MHz clock is also
derived for the CPU.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
26
8.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.
8.2
Clock sources
The device has the following clock source options, selectable by Flash Fuse bits as illustrated in Table 8-1. The
clock from the selected source is input to the AVR clock generator, and routed to the appropriate modules.
Device clocking options select (1).
Table 8-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 : 16MHz / PLL driven by external
crystal/ceramic resonator
Ext osc
Ext osc
0100
PLL output divided by 4 : 16MHz / 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 : 16MHz
PLL/4
RC osc
0011
Calibrated internal RC oscillator
RC osc
RC osc
0010
PLL output divided by 4 : 16MHz / 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 realtime part of the start-up time. The number of WDT Oscillator cycles used for each time-out is shown in Table 8-2 on
page 27. The frequency of the Watchdog Oscillator is voltage dependent as shown in TBD.
Table 8-2.
8.3
Number of watchdog oscillator cycles.
Typical time-out (VCC = 5.0V)
Typical time-out (VCC = 3.0V)
Number of cycles
4.1ms
4.3ms
4K (4,096)
65ms
69ms
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 eight. This
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
27
default setting ensures that all users can make their desired clock source setting using an In-System or Parallel
programmer.
8.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 8-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 8-3 on page 28. 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 8-2.
Crystal oscillator connections.
C2
XTAL2
C1
XTAL1
GND
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 8-3 on page 28.
Table 8-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 8-4.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
28
Table 8-4.
Start-up times for the oscillator clock selection
CKSEL0
SUT1..0
Start-up time from
power-down and
power-save
0
00
258 CK (1)
14CK + 4.1ms
Ceramic resonator, fast
rising power
0
01
258 CK (1)
14CK + 65ms
Ceramic resonator, slowly
rising power
0
10
1K CK (2)
14CK
Ceramic resonator, BOD
enabled
0
11
1K CK (2)
14CK + 4.1ms
Ceramic resonator, fast
rising power
1
00
1K CK (2)
14CK + 65ms
Ceramic resonator, slowly
rising power
1
01
16K CK
14CK
Crystal oscillator, BOD
enabled
1
10
16K CK
14CK + 4.1ms
Crystal oscillator, fast
rising power
1
11
16K CK
14CK + 65ms
Crystal oscillator, slowly
rising power
Notes:
Additional delay
from reset
(VCC = 5.0V)
Recommended usage
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.
8.5
Calibrated internal RC oscillator
By default, the internal RC oscillator provides an approximate 8.0MHz 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 32 for more details.
This clock may be selected as the system clock by programming the CKSEL Fuses as shown in Table 8-1 on page
27. 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 28-1 on page 296.
By changing the OSCCAL register from SW, see “OSCCAL – Oscillator Calibration Register” on page 33, 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 296.
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.
Table 8-5.
Notes:
Internal calibrated RC oscillator operating modes (1)(2).
Frequency range [MHz]
CKSEL3..0
7.3 - 8.1
0010
1. The device is shipped with this option selected.
2. If 8MHz frequency exceeds the specification of the device (depends on VCC), the CKDIV8 Fuse can be programmed in order to divide the internal frequency by eight.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
29
When this oscillator is selected, start-up times are determined by the SUT Fuses as shown in Table 8-6.
Table 8-6.
Start-up times for the internal calibrated RC oscillator clock selection.
Start-up time from powerdown and power-save
Power conditions
Additional delay from
reset (VCC = 5.0V)
14CK
(1)
SUT1..0
00
BOD enabled
6 CK
Fast rising power
6 CK
14CK + 4.1ms
01
Slowly rising power
6 CK
14CK + 65ms (2)
10
Reserved
Notes:
11
1. If the RSTDISBL fuse is programmed, this start-up time will be increased to
14CK + 4.1ms to ensure programming mode can be entered.
2. The device is shipped with this option selected.
8.6
PLL
8.6.1
Internal PLL
The internal PLL in Atmel ATmega16M1/32M1/64M1 generates a clock frequency that is 64× multiplied from nominally 1MHz input. The source of the 1MHz PLL input clock is the output of the internal RC Oscillator which is
divided down to 1MHz. See the Figure 8-3 on page 31.
The PLL is locked on the RC Oscillator and adjusting the RC Oscillator via OSCCAL Register will adjust the fast
peripheral clock at the same time. However, even if the possibly divided RC Oscillator is taken to a higher frequency than 1MHz, the fast peripheral clock frequency saturates at 70MHz (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 the RC Oscillator
clock.
Therefore it is recommended not to take the OSCCAL adjustments to a higher frequency than 1MHz 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 1MHz RC Oscillator and PLL are switched off in Power-down and Standby sleep modes.
Table 8-7.
Start-up times when the PLL is selected as system clock.
CKSEL
3..0
0011
RC Osc
0101
Ext Osc
0001
Ext Clk
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 + 4ms
10
1K CK
14CK + 64ms
11
16K CK
14CK
00
1K CK
14CK
01
1K CK
14CK + 4ms
10
16K CK
14CK + 4ms
11
16K CK
14CK + 64ms
00
6 CK (1)
14CK
01
6 CK
(1)
14CK + 4ms
6 CK
(1)
14CK + 64ms
10
11
Reserved
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
30
Note:
1. This value do not provide a proper restart ; do not use PD in this clock scheme.
Figure 8-3.
PCK clocking system.
OSCCAL
PLLF
PLLE
PLOCK
Lock
Detector
DIVIDE
BY 8
RC OSCILLATOR 8 MHz
PLL
64x
DIVIDE
BY 2
CLK PLL
DIVIDE
BY 4
CK SOURCE
XTAL1
XTAL2
8.7
OSCILLATORS
128kHz internal oscillator
The 128kHz internal oscillator is a low power oscillator providing a clock of 128kHz. The frequency is nominal at 3V
and 25C. This clock is used by the Watchdog Oscillator.
8.8
External clock
To drive the device from an external clock source, XTAL1 should be driven as shown in Figure 8-4. To run the
device on an external clock, the CKSEL Fuses must be programmed to “0000”.
Figure 8-4.
External clock drive configuration.
NC
XTAL2
External
Clock
Signal
XTAL1
GND
Table 8-8.
External clock frequency.
CKSEL3..0
Frequency range
0000
0 - 16MHz
When this clock source is selected, start-up times are determined by the SUT Fuses as shown in Table 8-9.
Table 8-9.
Start-up times for the external clock selection.
SUT1..0
Start-up time from powerdown and power-save
Additional delay from
reset (VCC = 5.0V)
00
6 CK
14CK
01
6 CK
14CK + 4.1ms
Fast rising power
10
6 CK
14CK + 65ms
Slowly rising power
11
Recommended usage
BOD enabled
Reserved
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
31
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 32 for details.
8.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).
8.10
System clock prescaler
The Atmel ATmega16M1/32M1/64M1 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 8-10 on page 34.
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, two active clock edges are produced. Here, T1 is the previous clock period, and T2 is the period corresponding
to the new prescaler setting.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
32
8.11
8.11.1
Register description
OSCCAL – Oscillator Calibration Register
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. A pre-programmed calibration value is automatically written to this register
during chip reset, giving the Factory calibrated frequency as specified in Table 28-1 on page 296. The application
software can write this register to change the oscillator frequency. The oscillator can be calibrated to frequencies
as specified in Table 28-1 on page 296. 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.8MHz. 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.
8.11.2
PLLCSR – PLL Control and Status Register
Bit
7
6
5
4
3
2
1
0
–
–
–
–
–
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 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 100ms for the PLL to lock.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
33
8.11.3
CLKPR – Clock Prescaler Register
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 8-10 on page 34.
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 eight 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.
Table 8-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
34
9. Power management and sleep modes
9.1
Overview
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.
9.2
Sleep modes
Figure 8-1 on page 26 presents the different clock systems in the Atmel ATmega16M1/32M1/64M1, and their distribution. The figure is helpful in selecting an appropriate sleep mode. Table 9-1 shows the different sleep modes
and their wake-up sources.
Table 9-1.
Active clock domains and wake-up sources in the different sleep modes.
clkPLL
Main clock
source enabled
INT3..0
PSC
SPM/EEPROM
ready
ADC
WDT
Other I/O
X
X
X
X
X
X
X
X
X
X
X
X
X
X (2)
X
X
X
X
Sleep mode
Idle
ADC noise
reduction
Power-down
Standby (1)
Notes:
Wake-up sources
clkADC
Oscillators
clkIO
clkFLASH
clkCPU
Active clock domains
X
X (2)
X
X (2)
X
1. Only recommended with external crystal or resonator selected as clock source.
2. Only level interrupt.
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 9-2 on
page 38 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.
9.3
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
35
9.4
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.
9.5
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 55 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 27.
9.6
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.
9.7
Power Reduction Register
The Power Reduction Register (PRR), see “PRR – Power Reduction Register” on page 38, 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 predictable behavior 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.
9.8
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
36
9.8.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 “ADC – Analog to Digital Converter” on page 214 for details on ADC operation.
9.8.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 “AC – analog comparator” on page 243 for details on how to configure the Analog Comparator.
9.8.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 42 for details on how to configure the Brown-out Detector.
9.8.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 43 for details on the start-up time.
9.8.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 43 for details on
how to configure the Watchdog Timer.
9.8.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 60 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 “DIDR1 – Digital Input Disable Register 1” and
“DIDR0 – Digital Input Disable Register 0” on page 250 and page 235 for details.
9.8.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
37
9.9
Register description
9.9.1
SMCR – Sleep Mode Control Register
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 7:4 - Res: Reserved
These bits are reserved and will always read as zero.
• Bits 3:1 – SM[2:0]: Sleep Mode Select Bits 2, 1, and 0
These bits select between the five available sleep modes as shown in Table 9-2.
Table 9-2.
Note:
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
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.
9.9.2
PRR – Power Reduction Register
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
This bit is reserved 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
38
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
39
10. System control and reset
10.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 10-1 on page 40 shows the
reset logic. “System and reset characteristics” on page 297 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 27.
Reset sources
The Atmel ATmega16M1/32M1/64M1 has four sources of reset:
• 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
Figure 10-1. Reset logic.
DATA BUS
MCU Status
Register (MCUSR)
PORF
BORF
EXTRF
WDRF
10.2
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]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
40
10.2.1
Power-on reset
A Power-on Reset (POR) pulse is generated by an On-chip detection circuit. The detection level is defined in “System and reset characteristics” on page 297. 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.
Figure 10-2. MCU start-up, RESET tied to VCC.
V CCRR
VCC
VPORMAX
VPORMIN
RESET
VRST
tTOUT
TIME-OUT
INTERNAL
RESET
Figure 10-3. MCU start-up, RESET extended externally.
VCC
RESET
TIME-OUT
VPOT
VRST
tTOUT
INTERNAL
RESET
10.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 “System and reset characteristics” on page 297) 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
41
Figure 10-4. External Reset During Operation
CC
10.2.3
Brown-out detection
Atmel ATmega16M1/32M1/64M1 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.
When the BOD is enabled, and VCC decreases to a value below the trigger level (VBOT- in Figure 10-5 on page 42),
the Brown-out Reset is immediately activated. When VCC increases above the trigger level (VBOT+ in Figure 10-5 on
page 42), 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 “System and reset characteristics” on page 297.
Figure 10-5. Brown-out reset during operation.
VCC
VBOT-
VBOT+
RESET
TIME-OUT
tTOUT
INTERNAL
RESET
10.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 43 for details on operation of the
Watchdog Timer.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
42
Figure 10-6. Watchdog reset during operation.
CC
CK
10.3
Internal voltage reference
Atmel ATmega16M1/32M1/64M1 features an internal bandgap reference. This reference is used for Brown-out
Detection, 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.
10.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 “System and reset characteristics” on page 297. 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.
10.4
Watchdog timer
10.4.1
Features
• Clocked from separate on-chip oscillator
• Three 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
10.4.2
Overview
The Atmel ATmega16M1/32M1/64M1 has an Enhanced Watchdog Timer (WDT). The WDT is a timer counting
cycles of a separate on-chip 128kHz 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
43
Figure 10-7. Watchdog timer.
OSC/8K
OSC/2K
OSC/4K
128kHz
OSCILLATOR
WDP3
MCU RESET
WDIF
INTERRUPT
WDIE
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.
The following code example shows one assembly and one C function for turning off the Watchdog Timer. The
example assumes that interrupts are controlled (for example by disabling interrupts globally) so that no interrupts
will occur during the execution of these functions.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
44
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.
The following code example shows one assembly and one C function for changing the time-out value of the Watchdog Timer.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
45
Assembly code example (1)
WDT_Prescaler_Change:
; Turn off global interrupt
cli
; Reset Watchdog Timer
wdr
; Start timed sequence
lds r16, WDTCSR
ori
r16, (1<<WDCE) | (1<<WDE)
sts WDTCSR, r16
; --
Got four cycles to set the new values from here -
; Set new prescaler(time-out) value = 64K cycles (~0.5 s)
ldi
r16, (1<<WDE) | (1<<WDP2) | (1<<WDP0)
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
46
10.5
Register description
10.5.1
MCUSR – MCU Status Register
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.
• 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.
10.5.2
WDTCSR – Watchdog Timer Control Register
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
47
of the Watchdog System Reset mode. If the interrupt is not executed before the next time-out, a System Reset will
be applied.
Table 10-1.
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 - WDP[3: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 10-2 on page 49.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
48
.
Table 10-2.
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
16ms
0
0
0
1
4K (4096) cycles
32ms
0
0
1
0
8K (8192) cycles
64ms
0
0
1
1
16K (16384) cycles
0.125s
0
1
0
0
32K (32768) cycles
0.25s
0
1
0
1
64K (65536) cycles
0.5s
0
1
1
0
128K (131072) cycles
1.0s
0
1
1
1
256K (262144) cycles
2.0s
1
0
0
0
512K (524288) cycles
4.0s
1
0
0
1
1024K (1048576) cycles
8.0s
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
49
11. Interrupts
This section describes the specifics of the interrupt handling as performed in Atmel ATmega16M1/32M1/64M1. For
a general explanation of the AVR interrupt handling, refer to “Reset and interrupt handling” on page 15.
11.1
Interrupt vectors in ATmega16M1/32M1/64M1
Table 11-1.
Reset and interrupt vectors.
Vector
no.
Program
address
Source
Interrupt definition
1
0x0000
RESET
External pin, power-on reset, brown-out reset,
watchdog reset, and emulation AVR reset
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
PSC FAULT
PSC fault
7
0x000C
PSC EC
PSC end of cycle
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
50
Table 11-1.
Reset and interrupt vectors. (Continued)
Vector
no.
Program
address
29
Source
Interrupt definition
0x0038
WDT
Watchdog time-out interrupt
30
0x003A
EE READY
EEPROM ready
31
0x003C
SPM READY
Store program memory ready
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” on page 258.
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.
Table 11-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 11-2.
Reset and interrupt vectors placement in Atmel ATmega16M1/32M1/64M1 (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 26-4 on page 262. 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
ATmega16M1/32M1/64M1 is:
Address Labels Code
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
51
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
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
r16, low(RAMEND)
;
0x041
0x042
out
sei
0x043
...
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 2Kbytes 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 Atmel ATmega16M1/32M1/64M1 is:
Address Labels Code
Comments
0x000
RESET: ldi
0x001
out
SPH,r16
r16,high(RAMEND); Main program start
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
52
When the BOOTRST Fuse is programmed and the Boot section size set to 2Kbytes, the most typical and general
program setup for the Reset and Interrupt Vector Addresses in Atmel ATmega16M1/32M1/64M1 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)
0xC03
0xC04
out
sei
SPL,r16
0xC05
<instr>
; Set Stack Pointer to top of RAM
; Enable interrupts
xxx
When the BOOTRST Fuse is programmed, the Boot section size set to 2Kbytes 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 ATmega16M1/32M1/64M1 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
;
11.1.1
0xC3E
RESET: ldi
0xC3F
out
SPH,r16
r16,high(RAMEND); Main program start
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
53
11.2
11.2.1
Register description
MCUCR – MCU Control Register
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” on page 258 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.
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” on page 258 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 the 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);
}
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
54
12. 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 26. 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 26.
12.1
Pin change interrupt timing
An example of timing of a pin change interrupt is schown in Figure 12-1.
Figure 12-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
55
12.2
12.2.1
Register description
EICRA – External Interrupt Control Register A
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 – ISC3[1:0] - ISC0[1:0]: Interrupt Sense Control 3 to 0, Bit 1 and Bit 0
The External Interrupts 3, 2, 1 and 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 12-1. Edges on INT3:0 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 12-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:
12.2.2
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.
EIMSK – External Interrupt Mask Register
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
These bits are reserved and will always read as zero.
• Bit 3:0 – INT[3:0]: External Interrupt Request 3:0 Enable
When an INT3:0 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
56
12.2.3
EIFR – External Interrupt Flag Register
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
These bits are reserved and will always read as zero.
• Bit 3:0 – INTF[3:0]: 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 Ibit 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.
12.2.4
PCICR – Pin Change Interrupt Control Register
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
These bits are reserved 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 PCINT14:8 pin will cause an interrupt. The corresponding interrupt of Pin
Change Interrupt Request is executed from the PCI1 Interrupt Vector. PCINT14: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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
57
12.2.5
PCIFR – Pin Change Interrupt Flag Register
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
These bits are reserved 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.
12.2.6
PCMSK3 – Pin Change Mask Register 3
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
These bits are reserved 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
58
12.2.7
PCMSK2 – Pin Change Mask Register 2
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.
12.2.8
PCMSK1 – Pin Change Mask Register 1
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
This bit is reservedand 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.
12.2.9
PCMSK0 – Pin Change Mask Register 0
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 – PCINT[7: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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
59
13. I/O-ports
13.1
Overview
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 13-1.
Refer to “Electrical characteristics” on page 293 for a complete list of parameters.
Figure 13-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”.
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 65. 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
60
13.2
Ports as general digital I/O
The ports are bi-directional I/O ports with optional internal pull-ups. Figure 13-2 shows a functional description of
one I/O-port pin, here generically called Pxn.
Figure 13-2. General digital I/O (1).
PUD
D
Q
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:
13.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” on
page 78, 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.
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).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
61
13.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.
13.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 tristate ({DDxn, PORTxn} = 0b00) or the output high state ({DDxn, PORTxn} = 0b11) as an intermediate step.
Table 13-1 summarizes the control signals for the pin value.
Table 13-1.
13.2.4
Port pin configurations.
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 13-2 on page 61, 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 13-3 on page 62 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.
Figure 13-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
62
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 13-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 one system clock period.
Figure 13-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
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
63
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:
13.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 13-2 on page 61, the digital input signal can be clamped to ground at the input of the schmitttrigger. The signal denoted SLEEP in the figure, is set by the MCU Sleep Controller in Power-down mode, Powersave 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 65.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
64
Alternate port functions
Most port pins have alternate functions in addition to being general digital I/Os. Figure 13-5 shows how the port pin
control signals from the simplified Figure 13-2 on page 61 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 13-5. Alternate port functions (1).
PUOExn
PUOVxn
1
PUD
0
DDOExn
DDOVxn
1
Q D
DDxn
0
Q CLR
WDx
PVOExn
RESET
RDx
PVOVxn
1
1
Pxn
Q
0
D
0
PORTxn
PTOExn
Q CLR
DIEOExn
DATA BUS
13.3
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
PUD: PULLUP DISABLE
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:
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 13-2 on page 66 summarizes the function of the overriding signals. The pin and port indexes from Figure 135 are not shown in the succeeding tables. The overriding signals are generated internally in the modules having the
alternate function.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
65
Table 13-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 bidirectionally
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
66
13.3.1
Alternate functions of Port B
The Port B pins with alternate functions are shown in Table 13-3 on page 67.
Table 13-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.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
67
• 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.
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
68
Table 13-4 and Table 13-5 relates the alternate functions of Port B to the overriding signals shown in Figure 13-5
on page 65.
Table 13-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
+ PSCout01 •
PSCen01 • SPIPS
PSCOUT11
0
0
DIEOE
ADC4D
ADC7D
ADC6D + In2en
AMP0ND
DIEOV
0
0
In2en
0
DI
SCKin • SPIPS •
ireset
ICP1B
INT2
AIO
ADC4
ADC7
ADC6
Table 13-5.
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
• ireset
MISO_IN • SPIPS
• ireset
ADC5
–
–
DI
AIO
AMP0-
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
69
13.3.2
Alternate functions of Port C
The Port C pins with alternate functions are shown in Table 13-6.
Table 13-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)
1. 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.
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
70
• 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 pullup 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.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
71
Table 13-7 and Table 13-8 on page 72 relate the alternate functions of Port C to the overriding signals shown in
Figure 13-5 on page 65.
Table 13-7.
Overriding signals for alternate functions in PC7..PC4.
Signal name
PC7/D2A/AMP2+/
PCINT15
PC6/ADC10/
ACMP1/
PCINT14
PC5/ADC9/
AMP1+/ACMP3/
PCINT13
PC4/ADC8/
AMP1-/ACMPN3/
PCINT12
PUOE
0
0
0
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 13-8.
Overriding signals for alternate functions in PC3..PC0.
Signal name
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
72
13.3.3
Alternate functions of Port D
The Port D pins with alternate functions are shown in Table 13-9.
Table 13-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.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
73
• 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.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
74
• 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 13-10 and Table 13-11 on page 76 relates the alternate functions of Port D to the overriding signals shown in
Figure 13-5 on page 65.
Table 13-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
75
Table 13-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
13.3.4
Alternate functions of Port E
The Port E pins with alternate functions are shown in Table 13-12.
Table 13-12. Port E pins alternate functions.
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:
1. On the engineering samples (parts marked AT90PWM324), the ACMPN3 alternate function is not located on PC4.
It is located on PE2.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
76
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 13-13 relates the alternate functions of Port E to the overriding signals shown in Figure 13-5 on page 65.
Table 13-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
77
13.4
Register description
13.4.1
MCUCR – MCU Control Register
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). See “Configuring the pin” on page 61 for more
details on this feature.
13.4.2
PORTB – Port B Data Register
Bit
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
13.4.3
PORTB
DDRB – Port B Data Direction Register
Bit
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
13.4.4
DDRB
PINB – Port B Input Pins Address
Bit
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
13.4.5
PINB
PORTC – Port C Data Register
Bit
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
13.4.6
PORTC
DDRC – Port C Data Direction Register
Bit
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
13.4.7
DDRC
PINC – Port C Input Pins Address
Bit
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
PINC
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
78
13.4.8
PORTD – Port D Data Register
Bit
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
13.4.9
PORTD
DDRD – Port D Data Direction Register
Bit
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
13.4.10
DDRD
PIND – Port D Input Pins Address
Bit
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
13.4.11
PIND
PORTE – Port E Data Register
Bit
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
13.4.12
PORTE
DDRE – Port E Data Direction Register
Bit
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
13.4.13
DDRE
PINE – Port E Input Pins Address
Bit
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
PINE
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
79
14. 8-bit Timer/Counter0 with PWM
14.1
Features
•
•
•
•
•
•
•
14.2
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
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 generating.
A simplified block diagram of the 8-bit Timer/Counter is shown in Figure 14-1. For the actual placement of I/O pins,
refer to “Pin descriptions” on page 7. 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 “Register description” on page 91.
The PRTIM0 bit in “Power Reduction Register” on page 36 must be written to zero to enable Timer/Counter0
module.
Figure 14-1. 8-bit timer/counter block diagram.
Count
TOVn
(Int.req.)
Clear
Control logic
Direction
Clock select
clk Tn
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
14.2.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
80
Unit A or Compare Unit B. However, when using the register or bit defines in a program, the precise form must be
used, that is, TCNT0 for accessing Timer/Counter0 counter value and so on.
The definitions in Table 14-1 are also used extensively throughout the document.
Table 14-1.
14.2.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 107.
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.
14.3
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 124.
14.4
Counter unit
The main part of the 8-bit Timer/Counter is the programmable bi-directional counter unit. Figure 14-2 on page 81
shows a block diagram of the counter and its surroundings.
Figure 14-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
81
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
(clk T0 ). clk T0 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
generating, see “Modes of operation” on page 85.
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.
14.5
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 85).
Figure 14-3 on page 83 shows a block diagram of the Output Compare unit.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
82
Figure 14-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.
14.5.1
Force output compare
In non-PWM waveform generating 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).
14.5.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.
14.5.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 generating. Similarly, do not write the TCNT0 value equal to BOTTOM
when the counter is down counting.
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 Generating modes.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
83
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.
14.6
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 14-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 14-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 Generating 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 “Register description” on
page 91.
14.6.1
Compare output mode and waveform generating
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 14-2 on page 91. For
fast PWM mode, refer to Table 14-3 on page 91, and for phase correct PWM refer to Table 14-4 on page 91.
A change of the COM0x1:0 bits state will have effect at the first compare match after the bits are written. For nonPWM modes, the action can be forced to have immediate effect by using the FOC0x strobe bits.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
84
14.7
Modes of operation
The mode of operation, that is, the behavior of the Timer/Counter and the Output Compare pins, is defined by the
combination of the Waveform Generating mode (WGM02:0) and Compare Output mode (COM0x1:0) bits. The
Compare Output mode bits do not affect the counting sequence, while the Waveform Generating 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 84).
For detailed timing information refer to “Timer/Counter timing diagrams” on page 89.
14.7.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 8bit 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.
14.7.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 14-5 on page 85. The counter value (TCNT0) increases
until a compare match occurs between TCNT0 and OCR0A, and then counter (TCNT0) is cleared.
Figure 14-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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
85
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.
14.7.3
Fast PWM mode
The fast Pulse Width Modulation or fast PWM mode (WGM02:0 = 3 or 7) provides a high frequency PWM waveform generating 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.
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 14-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 14-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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
86
In fast PWM mode, the compare unit allows generating 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 14-6 on page 92). 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).
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.
14.7.4
Phase correct PWM mode
The phase correct PWM mode (WGM02:0 = 1 or 5) provides a high resolution phase correct PWM waveform generating 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 in Figure 14-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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
87
Figure 14-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.
In phase correct PWM mode, the compare unit allows generating 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 14-7 on page 92). 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 14-7 on page 88 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 14-7 on page 88. 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
88
14.8
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 14-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 14-8. Timer/Counter timing diagram, no prescaling.
clkI/O
clkTn
(clkI/O /1)
TCNTn
MAX - 1
MAX
BOTTOM
BOTTOM + 1
TOVn
Figure 14-9 shows the same timing data, but with the prescaler enabled.
Figure 14-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 14-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 14-10. Timer/Counter timing diagram, setting of OCF0x, with prescaler (fclk_I/O/8).
clkI/O
clkTn
(clkI/O /8)
TCNTn
OCRnx
OCRnx - 1
OCRnx
OCRnx + 1
OCRnx + 2
OCRnx Value
OCFnx
Figure 14-11 shows the setting of OCF0A and the clearing of TCNT0 in CTC mode and fast PWM mode where
OCR0A is TOP.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
89
Figure 14-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)
OCRnx
TOP - 1
TOP
BOTTOM
BOTTOM + 1
TOP
OCFnx
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
90
14.9
14.9.1
Register description
TCCR0A – Timer/Counter Control Register A
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 14-2 shows the COM0A1:0 bit functionality when the WGM02:0 bits are set to a normal or CTC mode (nonPWM).
Table 14-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 14-3 shows the COM0A1:0 bit functionality when the WGM01:0 bits are set to fast PWM mode.
Table 14-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 86 for more details.
Table 14-4 shows the COM0A1:0 bit functionality when the WGM02:0 bits are set to phase correct PWM mode.
Table 14-4.
Compare Output mode, phase correct PWM mode (1).
COM0A1
COM0A0
Description
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
91
Note:
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 111 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 14-5 shows the COM0B1:0 bit functionality when the WGM02:0 bits are set to a normal or CTC mode (nonPWM).
Table 14-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 14-6 shows the COM0B1:0 bit functionality when the WGM02:0 bits are set to fast PWM mode.
Table 14-6.
Compare Output mode, fast PWM mode(1).
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:
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 86 for more details.
Table 14-7 shows the COM0B1:0 bit functionality when the WGM02:0 bits are set to phase correct PWM mode.
Table 14-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 87 for more details.
• Bits 3, 2 – Res: Reserved Bits
These bits are reserved and will always read as zero.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
92
• Bits 1:0 – WGM01:0: Waveform Generating 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 generating to be used, see
Table 14-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 85).
Table 14-8.
Waveform Generating 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.
14.9.2
TCCR0B – Timer/Counter Control Register B
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 Generating 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 Generating unit. The OC0B output is changed according to its COM0B1:0 bits setting. Note that the
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
93
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 and will always read as zero.
• Bit 3 – WGM02: Waveform Generating mode
See the description in the “TCCR0A – Timer/Counter Control Register A” on page 91.
• Bits 2:0 – CS02:0: Clock Select
The three Clock Select bits select the clock source to be used by the Timer/Counter.
Table 14-9.
Clock Select bit description.
CS02
CS01
CS00
Description
0
0
0
No clock source (Timer/Counter stopped)
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
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.
14.9.3
TCNT0 – Timer/Counter Register
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.
14.9.4
OCR0A – Output Compare Register A
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
94
14.9.5
OCR0B – Output Compare Register B
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.
14.9.6
TIMSK0 – Timer/Counter Interrupt Mask Register
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
These bits are reserved 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,
that is, when the OCF0B bit is set in the “TIFR0 – Timer/Counter 0 Interrupt Flag Register” .
• 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, that is, when the OCF0A bit is set in the “TIFR0 – Timer/Counter 0 Interrupt Flag Register” .
• 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, that is, when the
TOV0 bit is set in the “TIFR0 – Timer/Counter 0 Interrupt Flag Register” .
14.9.7
TIFR0 – Timer/Counter 0 Interrupt Flag Register
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 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 Register B” on page 95. 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
95
• 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 Register A” on page 94. 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 14-8, “Waveform Generating mode
bit description.” on page 93.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
96
15. 16-bit Timer/Counter1 with PWM
15.1
Features
•
•
•
•
•
•
•
•
•
•
•
•
15.2
True 16-bit design (that is, 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
The 16-bit Timer/Counter unit allows accurate program execution timing (event management), wave generating,
and signal timing measurement.
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, that is, TCNT1 for accessing Timer/Counter1
counter value and so on.
A simplified block diagram of the 16-bit Timer/Counter is shown in Figure 15-1 on page 98. For the actual placement of I/O pins, refer to “Pin descriptions” on page 3. 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 “Register description” on
page 117.
The PRTIM1 bit in “Power Reduction Register” on page 36 must be written to zero to enable Timer/Counter1
module.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
97
Figure 15-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
AC1ICE
ICFn (Int.req.)
ICRn
TCCRnA
Note:
15.2.1
OCnB
Edge
detector
TCCRnB
ICPSEL1
ICPnA
0
Noise
canceler
1
ICPnB
Analog Comparator 1
interrupt
1. Refer to Table 1-1 on page 3 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 99. 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 105. The compare match event will
also set the Compare Match Flag (OCFnx) which can be used to generate an Output Compare interrupt request.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
98
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.
15.2.2
Definitions
The following definitions are used extensively throughout the section:
Table 15-1.
15.3
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
99
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
100
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
101
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.
15.3.1
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.
15.4
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 124.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
102
15.5
Counter unit
The main part of the 16-bit Timer/Counter is the programmable 16-bit bi-directional counter unit. Figure 15-2 shows
a block diagram of the counter and its surroundings.
Figure 15-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 Generating 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 generating, see “16-bit Timer/Counter1 with PWM” on
page 97.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
103
15.6
Input Capture unit
The Timer/Counter incorporates an Input Capture unit that can capture external events and give them a timestamp 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 15-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 15-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.
The ICRn Register can only be written when using a Waveform Generating mode that utilizes the ICRn Register for
defining the counter’s TOP value. In these cases the Waveform Generating 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 99.
The ICF1 output can be used to retrigger the timer counter. It has the same effect than the TOP signal.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
104
15.6.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 (see Figure 16-1 on page
124). 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 Generating mode
that uses ICRn to define TOP.
An Input Capture can be triggered by software by controlling the port of the ICPn pin.
15.6.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.
15.6.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.
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).
15.6.4
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.
15.7
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 Generating mode (WGMn3:0) bits and Compare Output mode
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
105
(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 97.
A special feature of Output Compare unit A allows it to define the Timer/Counter TOP value (that is, counter resolution). In addition to the counter resolution, the TOP value defines the period time for waveforms generated by the
Waveform Generator.
Figure 15-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.
Figure 15-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 99.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
106
15.7.1
Force output compare
In non-PWM Waveform Generating 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).
15.7.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.
15.7.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 generating. 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 Generating 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.
15.8
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 15-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”.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
107
Figure 15-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 Generating mode, but there are some exceptions. Refer to Table 15-2 on page 117, Table 15-3 on page 118
and Table 15-4 on page 118 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 “Register description” on
page 117.
The COMnx1:0 bits have no effect on the Input Capture unit.
15.8.1
Compare Output Mode and Waveform Generating
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 15-2 on page 117. For
fast PWM mode refer to Table 15-3 on page 118, and for phase correct and phase and frequency correct PWM
refer to Table 15-4 on page 118.
A change of the COMnx1:0 bits state will have effect at the first compare match after the bits are written. For nonPWM modes, the action can be forced to have immediate effect by using the FOCnx strobe bits.
15.9
Modes of operation
The mode of operation, that is, the behavior of the Timer/Counter and the Output Compare pins, is defined by the
combination of the Waveform Generating mode (WGMn3:0) and Compare Output mode (COMnx1:0) bits. The
Compare Output mode bits do not affect the counting sequence, while the Waveform Generating 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 107.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
108
For detailed timing information refer to “Timer/Counter timing diagrams” on page 115.
15.9.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.
15.9.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 15-6 on page 109. The counter value (TCNTn) increases
until a compare match occurs with either OCRnA or ICRn, and then counter (TCNTn) is cleared.
Figure 15-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
109
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.
15.9.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 generating 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.
The PWM resolution for fast PWM can be fixed to 8-bit, 9-bit, 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 15-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 15-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
110
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. 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 generating 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 118). 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.
15.9.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 generating 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 BOT-
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
111
TOM (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.
The PWM resolution for the phase correct PWM mode can be fixed to 8-bit, 9-bit, 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 15-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 15-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
112
masked to zero when any of the OCRnx Registers are written. As the third period shown in Figure 15-8 illustrates,
changing the 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 generating 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 15-4 on page 118). 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.
15.9.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 generating 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 15-8 on page 112 and Figure 15-9 on page
114).
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
113
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 15-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 15-9. Phase and frequency correct PWM mode, timing diagram.
OCnA interrupt flag set
or ICFn interrupt flag set
(interrupt on TOP)
OCRnx/TOP update and
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.
As Figure 15-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 generating 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 15-4 on page 118). 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
114
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.
15.10 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 15-10 shows a
timing diagram for the setting of OCFnx.
Figure 15-10. Timer/Counter timing diagram, setting of OCFnx, no prescaling.
clkI/O
clkTn
(clkI/O /1)
TCNTn
OCRnx
OCRnx - 1
OCRnx
OCRnx + 1
OCRnx + 2
OCRnx value
OCFnx
Figure 15-11 on page 116 shows the same timing data, but with the prescaler enabled.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
115
Figure 15-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
Figure 15-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 15-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 15-13 on page 117 shows the same timing data, but with the prescaler enabled.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
116
Figure 15-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
Old OCRnx value
(update at TOP)
New OCRnx value
15.11 Register description
15.11.1
TCCR1A – Timer/Counter1 Control Register A
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 15-2 shows the COMnx1:0 bit functionality when the WGMn3:0 bits are set to a Normal or a CTC
mode (non-PWM).
Table 15-2.
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)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
117
Table 15-3 shows the COMnx1:0 bit functionality when the WGMn3:0 bits are set to the fast PWM mode.
Table 15-3.
Compare Output mode, fast PWM (1).
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:
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 110 for more details.
Table 15-4 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 15-4.
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 upcounting. Set OCnA/OCnB on Compare Match when
downcounting
1
1
Set OCnA/OCnB on Compare Match when upcounting. 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 111 for more details.
• Bit 1:0 – WGMn1:0: Waveform Generating 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 generating to be used, see
Table 15-5 on page 119. 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 “16bit Timer/Counter1 with PWM” on page 97.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
118
Waveform Generating mode bit description (1).
Table 15-5.
Mode
WGMn3
WGMn2
(CTCn)
WGMn1
(PWMn1)
WGMn0
(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
1
PWM, phase correct, 8-bit
0x00FF
TOP
BOTTOM
2
0
0
1
0
PWM, phase correct, 9-bit
0x01FF
TOP
BOTTOM
3
0
0
1
1
PWM, phase correct, 10-bit
0x03FF
TOP
BOTTOM
4
0
1
0
0
CTC
OCRnA
Immediate
MAX
5
0
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
ICRn
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:
15.11.2
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.
TCCR1B – Timer/Counter1 Control Register B
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
119
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 Generating 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 15-10 on page 115
and Figure 15-11 on page 116.
Table 15-6.
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
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.
15.11.3
TCCR1C – Timer/Counter1 Control Register C
Bit
7
6
5
4
3
2
1
0
FOC1A
FOC1B
–
–
–
–
–
–
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 Generating 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
120
15.11.4
TCNT1H and TCNT1L – Timer/Counter1
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 99.
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.
15.11.5
OCR1AH and OCR1AL – Output Compare Register 1 A
Bit
7
6
5
4
3
2
1
0
OCR1A[15:8]
OCR1AH
OCR1A[7:0]
15.11.6
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
2
1
0
OCR1BH and OCR1BL – Output Compare Register 1 B
Bit
7
6
5
4
3
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 99.
15.11.7
ICR1H and ICR1L – Input Capture Register 1
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
121
(TEMP). This temporary register is shared by all the other 16-bit registers. See “Accessing 16-bit registers” on
page 99.
15.11.8
TIMSK1 – Timer/Counter1 Interrupt Mask Register
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
These bits are reserved 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 (see “Interrupt vectors in
ATmega16M1/32M1/64M1” on page 50) is executed when the ICF1 Flag, located in TIFR1, is set.
• Bit 4, 3 – Res: Reserved
These bits are reserved 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 (see “Interrupt
vectors in ATmega16M1/32M1/64M1” on page 50) is executed when the OCF1B Flag, located in TIFR1, is set.
• 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 (see “Interrupt
vectors in ATmega16M1/32M1/64M1” on page 50) 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 (see “Interrupt vectors in
ATmega16M1/32M1/64M1” on page 50) is executed when the TOV1 Flag, located in TIFR1, is set.
15.11.9
TIFR1 – Timer/Counter1 Interrupt Flag Register
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
These bits are reserved 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
122
• Bit 4, 3 – Res: Reserved
These bits are reserved 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 15-5 on page 119 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
123
16. Timer/Counter0 and Timer/Counter1 prescalers
The “8-bit Timer/Counter0 with PWM” on page 80 and the “16-bit Timer/Counter1 with PWM” on page 97 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.
16.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 (f CLK_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.
16.2
Prescaler reset
The prescaler is free running, that is, 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.
16.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 16-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 16-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.
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
124
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 16-2. Prescaler for Timer/Counter0 and Timer/Counter1 (1).
clk I/O
Clear
PSRSYNC
T0
Synchronization
T1
Synchronization
clkT1
Note:
16.4
16.4.1
clkT0
1. The synchronization logic on the input pins (Tn) is shown in Figure 16-1 on page 124.
Register description
GTCCR – General Timer/Counter Control Register
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.
• 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 16-1.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
125
Table 16-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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
126
17. PSC – power stage controller
17.1
Features
• PWM waveform generating function with six complementary programmable outputs (able to control three half•
•
•
•
•
•
•
17.2
bridges)
Programmable dead time control
PWM up to 12-bit resolution
PWM clock frequency up to 64MHz (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
The Power Stage Controller is a high performance waveform controller.
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, that is, 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, that is, 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 three 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 three 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.
17.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
127
PSC description
Figure 17-1. Power Stage Controller, block diagram.
PSC Counter
CLKIO
Prescaler
CLKPLL
POCR_RB
=
module 0
POCR0SB
DATABUS
17.4
Waveform
generator B
=
PSCOUT0B
(Analog Comparator 0 output)
AC0O
POCR0RA
Overlap
protection
=
PSC Input 0
PSCIN0
PISEL0
POCR0SA
Waveform
generator A
=
PSCOUT0A
module 1
POCR1SB
Waveform
generator B
=
PSCOUT1B
(Analog Comparator 1 output)
AC1O
POCR1RA
Overlap
protection
=
PSC Input 1
PSCIN1
PISEL1
POCR1SA
Waveform
generator A
=
PSCOUT1A
module 2
POCR2SB
Waveform
generator B
=
PSCOUT2B
(Analog Comparator 2 output)
AC2O
POCR2RA
Overlap
protection
=
PSC Input 2
PSCIN2
PISEL2
POCR2SA
Waveform
generator A
=
PSCOUT2A
PSOCn
PCNFn
PCTLn
PFRCnB
PFRCnA
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
128
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 17-1 on page 128, the PSC is composed of three modules.
Each of the three 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.
17.5
Functional description
17.5.1
Generating control waveforms
In general, the drive of a 3-phase motor requires generating six 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
three voltage lines (trapezoidal, sinusoidal, and so on).
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, and so on.
17.5.2
Waveform cycles
Each of the three modules has two 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 subcycle 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 17-2. Cycle presentation in One Ramp mode.
One PSC cycle
Sub-cycle A
Sub-cycle B
PSC counter value
UPDATE
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
129
Figure 17-3. Cycle presentation in Centered mode.
One PSC cycle
PSC counter value
UPDATE
Figure 17-2 on page 129 and Figure 17-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.
17.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 three PSCOUTnB outputs are edge-aligned and the three 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 six PSC outputs are aligned at the center of the period. Except when
using the same duty cycles on the three 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 as slow as in One Ramp mode
17.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
130
Figure 17-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
Note:
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.
Figure 17-5. Controlled start and stop mechanism in One-Ramp mode.
POCRnRB
POCRnSB
POCRnRA
POCRnSA
PSC counter
0
Run
PSCOUTnA
PSCOUTnB
Note:
See “PCTL – PSC Control Register” on page 143. (PCCYC = 1).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
131
17.5.3.2
Center Aligned mode
In center aligned mode, the center of PSCOUTnA and PSCOUTnB signals are centered.
Figure 17-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
Note:
Minimal value for PSC Cycle = 2 × 1/Fclkpsc.
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 138.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
132
Figure 17-7. Controlled start and stop mechanism in Centered mode.
POCRnRB
POCRnSB
POCRnSA
PSC counter
0
Run
PSCOUTnA
PSCOUTnB
Note:
See “PCTL – PSC Control Register” on page 143.(PCCYC = 1).
17.6
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 17-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.
17.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 142.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
133
17.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).
17.8
Signal description
Figure 17-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
17.8.1
PSCASY
Input description
Table 17-1. Internal inputs.
Name
Description
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
134
Name
Analog Comparator 0 Output
Signal
AC1O
Analog Comparator 1 Output
Signal
AC2O
Analog Comparator 2 Output
Signal
Name
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
Output description
Table 17-3. Block outputs.
Name
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
Table 17-4.
Name
IRQPSCn
PSCASY
Note:
17.9
Type width
AC0O
Table 17-2.
17.8.2
Description
Internal Outputs
Description
Type width
PSC interrupt request: two souces, overflow, fault
ADC synchronization (+ Amplifier Syncho)
(1)
Signal
Signal
1. See “Analog synchronization” on page 138.
PSC input
For detailed information on the PSC, please refer to Application Note ‘AVR138: ATmega32M1 family 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 “PMICn – PSC Module n Input Control Register” on page 144. 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).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
135
Figure 17-10. PSC input module.
PAOCnA
(PAOCnB)
0
PSCINn
Analog
Comparator
n output
0
Digital
filter
1
1
CLK PSC
PFLTEnA
(PFLTEnB)
PISELnA
(PISELnB)
PELEVnA / PCAEnA
(PELEVnB) (PCAEnB)
PRFMnA3:0
(PRFMnB3:0)
2
4
Input
processing
(retriggering ...)
CLK PSC
MPSC core
(counter,
waveform
generator, ...)
Control
of the
six outputs
PSCOUTnA
PSCOUTnB
CLK PSC
17.9.1
PSC input configuration
The PSC input configuration is done by programming bits in configuration registers.
17.9.1.1
Filter enable
If the “Filter Enable” bit is set, a digital filter of four 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
136
Figure 17-11. PSC input filtering.
CLKPSC
Digital
filter
4 x CLK PSC
PSC input
module X
PSC Module n input
Ouput
stage
PSCOUTnX
PIN
17.9.1.2
Signal polarity
One can select the active edge (edge modes) or the active level (level modes). See PELEVnx bit description in
Section "PMICn – PSC Module n Input Control Register", page 144.
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
17.9.1.3
Input mode operation
Thanks to four configuration bits (PRFM3:0), it is possible to define the mode of the PSC inputs.
Table 17-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
Note: All following examples are given with rising edge or high level active inputs.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
137
17.10 PSC input modes 001b to 10xb: Deactivate outputs without changing timing
Figure 17-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 17-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.
17.11 PSC Input Mode 11xb: Halt PSC and wait for software action
Figure 17-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:
1. Software action is the setting of the PRUNn bit in PCTLn register.
Used in fault mode 7, PSCn Input A or PSCn Input B act indifferently on On-Time0/Dead-Time0 or on OnTime1/Dead-Time1.
17.12 Analog synchronization
Each PSC module generates a signal to synchronize the ADC sample and hold; synchronisation is mandatory for
measurements.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
138
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.
17.13 Interrupt handling
As each PSC module can be dedicated for one function, each PSC has its own interrupt system.
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
17.14 PSC clock sources
Each PSC has two clock inputs:
• CLK PLL from the PLL
• CLK I/O
Figure 17-15. Clock selection.
CLK
1
PLL
CK
CK
CK/4
CK/32
CK/256
01
10
11
0
I/O
00
CLK
PRESCALER
PCLKSEL
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.
Table 17-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
139
17.15 Interrupts
This section describes the specifics of the interrupt handling as performed in Atmel ATmega16M1/32M1/64M1.
17.15.1
Interrupt vector
PSC provides two 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
17.15.2
PSC interrupt vectors in ATmega16M1/32M1/64M1
Table 17-7.
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
-
-
17.16 Register description
Registers are explained for PSC module 0. They are identical for module 1 and module 2.
17.16.1
POC – PSC Output Configuration
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:6 – Res: Reserved
These bits are reserved and will always read as zero.
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
140
• 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.
17.16.2
PSYNC – PSC Synchro Configuration
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:6 – Res: Reserved
These bits are reserved and will always read as zero.
• Bit 5:4 – PSYNC2[1: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 – PSYNC1[1: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 – PSYNC0[1: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 17-8.
Synchronization source description in One Ramp mode.
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)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
141
Table 17-9.
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
17.16.3
POCRnSAH and POCRnSAL – PSC Output Compare SA Register
Bit
7
6
5
4
–
–
–
–
3
2
1
0
POCRnSA[11:8]
POCRnSAH
POCRnSA[7:0]
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
17.16.4
POCRnRAH and POCRnRAL – PSC Output Compare RA Register
Bit
7
6
5
4
–
–
–
–
3
2
1
0
POCRnRA[11:8]
POCRnRAH
POCRnRA[7:0]
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
1
0
17.16.5
POCRnSBH and POCRnSBL – PSCOutput Compare SB Register
Bit
7
6
5
4
–
–
–
–
3
2
POCRnSB[11:8]
POCRnSBH
POCRnSB[7:0]
POCRnSBL
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
17.16.6
POCRnRBH and POCRnRBL – PSC Output Compare RB Register
Bit
7
6
5
4
–
–
–
–
3
2
1
0
POCRnRB[11:8]
POCRnRBH
POCRnRB[7:0]
POCRnRBL
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 16-bit 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.
17.16.7
PCNF – PSC Configuration Register
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
142
• Bit 7:6 – Res: Reserved
These bits are reserved and will always read as zero.
• 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.
• Bit 4 – PMODE PSC Mode
Select the mode of PSC.
Table 17-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 – Res: Reserved
These bits are reserved and will always read as zero.
17.16.8
PCTL – PSC Control Register
Bit
7
6
5
4
3
2
1
0
PPRE1
PPRE0
PCLKSEL
-
-
-
PCCYC
PRUN
Read/write
R/W
R/W
R/W
R
R
R
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 17-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).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
143
• Bit 4:2 – Res: Reserved
These bits are reserved and will always read as zero.
• 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.
17.16.9
PMICn – PSC Module n Input Control Register
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 two PSC’s Retrigger/Fault block A & B. The two 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 “Overlap Protection” on page 134.
• 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 136.
• Bit 2:0 – PRFMn2:0: PSC Module n Input Mode
These three bits define the mode of operation of the PSC inputs.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
144
Table 17-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
17.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 – Res: Reserved
These bits are reserved and will always read as zero.
• 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 – PEVE: 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.
17.16.11 PIFR – PSC Interrupt Flag Register
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 – Res: Reserved
These bits are reserved and will always read as zero.
• 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).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
145
• 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 – PEV: 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).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
146
18. SPI – Serial Peripheral Interface
18.1
Features
•
•
•
•
•
•
•
•
Overview
The Serial Peripheral Interface (SPI) allows high-speed synchronous data transfer between the Atmel
ATmega16M1/32M1/64M1 and peripheral devices or between several AVR devices.
Figure 18-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
SS
SPI2X
SS_A
SPI2X
18.2
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
Note:
1. Refer to Figure 1-1 on page 2, and Table 13-3 on page 67 for SPI pin placement.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
147
The interconnection between Master and Slave CPUs with SPI is shown in Figure 18-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 18-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.
When the SPI is enabled, the data direction of the MOSI, MISO, SCK, and SS pins is overridden according to
Table 18-1. For more details on automatic port overrides, refer to “Alternate port functions” on page 65.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
148
Table 18-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 67 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. For example,
if MOSI is placed on pin PB2, replace DD_MOSI with DDB2 and DDR_SPI with DDRB.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
149
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
150
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:
1. The example code assumes that the part specific header file is included.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
151
18.3
SS pin functionality
18.3.1
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.
18.3.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.
18.4
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 18-3 on page 153 and Figure 18-4 on
page 153. 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 18-3 on page 154 and Table 18-4 on page 155,
as done below:
Table 18-2.
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
152
Figure 18-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
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
Figure 18-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
153
18.5
Register description
18.5.1
MCUCR – MCU Control Register
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 is always located on alternate SPI port.
18.5.2
SPCR – SPI Control Register
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 18-3 on page 153 and Figure 18-4 on page 153 for an example. The CPOL functionality is summarized
below:
Table 18-3.
CPOL functionality.
CPOL
Leading edge
Trailing edge
0
Rising
Falling
1
Falling
Rising
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
154
• 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 18-3 on page 153 and Figure 18-4 on page 153 for an example. The CPOL functionality is
summarized below:
Table 18-4.
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
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 18-5.
18.5.3
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
SPSR – SPI Status Register
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
These bits are reserved and will always read as zero.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
155
• 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 18-5). 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 Atmel ATmega16M1/32M1/64M1 is also used for program memory and EEPROM downloading or uploading. See “Serial programming algorithm” on page 289 for serial programming and verification.
18.5.4
SPDR – SPI Data Register
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
156
19. CAN – Controller Area Network
19.1
Features
• Full CAN controller
• Fully compliant with CAN standard rev 2.0 A and rev 2.0 B
• Six 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)
– Eight bytes data buffer (static allocation)
– Tx, Rx, frame buffer or automatic reply configuration
– Time stamping
• 1Mbit/s maximum transfer rate at 8MHz
• TTC timer
• Listening mode (for spying or autobaud)
19.2
Overview
The Controller Area Network (CAN) protocol is a real-time, serial, broadcast protocol with a very high level of security. The Atmel ATmega16M1/32M1/64M1 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
1Mbit/s.
19.3
CAN protocol
The CAN protocol is an international standard defined in the ISO 11898 for high speed and ISO 11519-2 for low
speed.
19.3.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.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
157
19.3.2
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.
19.3.2.1
CAN standard frame
Figure 19-1. CAN standard frames.
Data frame
Bus Idle
SOF
11-bit identifier
ID10..0
RTR IDE
Arbitration
Field
Interframe
Space
r0
4-bit DLC
DLC4..0
15-bit CRC
0 - 8 bytes
Control
Field
Data
Field
CRC
ACK
del. ACK del.
CRC
Field
Intermission
3 bits
7 bits
ACK
Field
Bus Idle
(Indefinite)
Interframe
Space
End of
Frame
Remote frame
Bus Idle
SOF
Interframe
pace
11-bit identifier
ID10..0
RTR IDE
Arbitration
Field
r0
4-bit DLC
DLC4..0
15-bit CRC
Control
Field
CRC
ACK
del. ACK del.
CRC
Field
7 bits
ACK
Field
Intermission
3 bits
Bus Idle
(Indefinite)
Interframe
Space
End of
Frame
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.
19.3.2.2
CAN extended frame
Figure 19-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.
7 bits
ACK
Field
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
Arbitration
Field
RTR r1
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
158
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.
19.3.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
19.3.3
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.
19.3.3.1
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.
Figure 19-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
19.3.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.
19.3.3.3
Propagation time segment
This segment is used to compensate for signal delays across the network.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
159
This is necessary to compensate for signal propagation delays on the bus line and through the transceivers of the
bus nodes.
19.3.3.4
Phase Segment 1
Phase Segment 1 is used to compensate for edge phase errors.
This segment may be lengthened during re-synchronization.
19.3.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).
19.3.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.
19.3.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.
19.3.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.
19.3.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.
19.3.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.
19.3.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
160
19.3.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.
19.3.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.
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 19-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
19.3.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:
19.3.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.
19.3.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
161
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.
19.3.5.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.
19.4
CAN controller
The CAN controller implemented into Atmel ATmega16M1/32M1/64M1 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 (for example 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 baud rates and high bus loads with many messages can be handled.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
162
Figure 19-5. CAN controller structure.
Control
Status
IDtag+IDmask
Time stamp
Buffer MOb i
Low priority
MOb i
Size = 120 Bytes
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
Mailbox
19.5
CAN channel
19.5.1
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
163
• Listening mode
This mode is transparent for the CAN channel:
– 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 19-6. Listening mode.
internal
TxCAN
PD5
TXCAN
PD6
RXCAN
LISTEN
19.5.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 19-7. Sample and transmission point.
Bit timing
PRS (3-bit length)
PHS1 (3-bit length)
CLK
IO
Prescaler BRP
Sample
point
Fcan (Tscl)
Time quantum
PHS2 (3-bit length)
Transmission
point
SJW (2-bit length)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
164
Figure 19-8. General Structure of a bit period.
1
/CLK IO
CLK
IO
Tscl (TQ)
Bit rate
prescaler
F
CAN
One nominal bit
Data
Tsyns(5)
Notes: 1.
2.
3.
4.
5.
Tprs
Phase error < 0
Phase error > 0
Phase error > 0
Phase error < 0
Synchronization segment: SYNS
Tsyns = 1 x Tscl (fixed)
Tphs1 (1)
or
Tphs1+Tsjw (3)
Tphs2 (2)
or
Tphs2+Tsjw (4)
Tbit
Sample
point
19.5.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 × Tscl = (BRP[5..0] + 1)/clkIO (= 1TQ)
2. Tprs = (1 to 8) × Tscl = (PRS[2..0] + 1) × Tscl
3. Tphs1 = (1 to 8) × Tscl = (PHS1[2..0] + 1) × Tscl
4. Tphs2 = (1 to 8) × Tscl = (PHS2[2..0] (2)+ 1) × Tscl
5. Tsjw = (1 to 4) × Tscl = (SJW[1..0] + 1) × 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.
19.5.4
Fault confinement
(C.f. Section 19.8 “Error management” on page 170).
19.5.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
165
Figure 19-9. Overload frame.
Instructions
Resetting OVRQ bit
Setting OVRQ bit
OVRQ bit
OVFG bit
RXCDAN
Ident "A"
Cmd
Message Data "A"
CRC
A
Interframe
TXCDAN
19.6
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
19.6.1
Number of MObs
This device has six MObs, they are numbered from 0 up to 5 (i = 5).
19.6.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 19-1.
MOb configuration.
MOb configuration
0
0
0
1
1
0
Reply valid
RTR tag
x
x
Disabled
x
0
Tx data frame
x
1
Tx remote frame
x
0
Rx data frame
0
Operating mode
Rx remote frame
1
1
1
1
x
Rx remote frame then, Tx data frame (reply)
x
Frame Buffer Receive mode
19.6.2.1
Disabled
In this mode, the MOb is “free”.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
166
19.6.2.2
Tx data and 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.
19.6.2.3
Rx data and 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.
19.6.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 19.6.2.3 “Rx data and remote
frame” on page 167.
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.
19.6.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
167
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.
19.6.3
Acceptance filter
Upon a reception hit (that is, 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).
Figure 19-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
IDMSK
CANIDT registers & CANCDMOB (MOb[i])
Note:
13(31)
RTRMSK
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
19.6.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
168
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 19-14 on page 172).
19.6.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, ...
19.7
CAN timer
A programmable 16-bit timer is used for message stamping and time trigger communication (TTC).
Figure 19-11. CAN timer block diagram.
clk
IO
8
ENFG
CANTCON
clk CANTIM
TTC
OVRTIM
overrun
SYNCTTC
CANTIM
TXOK[i]
"EOF "
"SOF "
RXOK[i]
CANSTM[i]
19.7.1
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)
19.7.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).
19.7.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
169
19.7.4
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).
19.8
Error management
19.8.1
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 19-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:
19.8.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:
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
170
– CRC delimiter
– acknowledgement delimiter
– end-of-frame
– error delimiter
– overload delimiter
• AERR: Acknowledgment error (Tx only). No detection of the dominant bit in the acknowledge slot
Figure 19-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
19.8.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.
19.9
Interrupts
19.9.1
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
171
Figure 19-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]
ENRX
ENERR
CANSIT 1/2
SIT[i]
CANIE 1/2
IEMOB[i]
0
CANGIT.7
i
CANSTMOB.1
FERR[i]
CANSTMOB.0
AERR[i]
CANGIT.4
BXOK
CANGIT.3
SERG
CANGIT.2
CERG
CANGIT.1
FERG
CANGIT.0
AERG
CANIT
CANGIE.2 CANGIE.1 CANGIE.6
CANGIE.7
ENERG
ENIT
ENBX
ENBOFF
CAN IT
CANGIE.0
19.9.2
CANGIT.6
BOFFI
CANGIT.5
OVRTIM
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
172
19.10 Register description
Figure 19-15. Registers organization.
AVR
VR 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
sage
Data Index
es
+1) M
(i
cts
Obje
MOb(i) - MOb Status
MOb(i) - MOb Ctrl & DLC
MOb(i) - ID Tag 4
Page MOb
MOb Status
MOb Control & DLC
MOb0 - MOb Status
MOb0 - MOb Ctrl & DLC
ID Tag 4
ID Tag 3
ID Tag 2
ID Tag 1
MOb0 - ID Tag 4
MOb0 - ID Tag 3
MOb0 - ID Tag 2
MOb0 - ID Tag 1
ID Mask 4
ID Mask 3
ID Mask 2
ID Mask 1
MOb0 - ID Mask 4
MOb0 - ID Mask 3
MOb0 - ID Mask 2
MOb0 - ID Mask 1
Time Stamp Low
Time Stamp High
MOb0 - Time Stamp Low
MOb0 - Time Stamp High
Message Data
MOb0 - Mess. Data - byte 0
MOb(i) - ID Tag 3
MOb(i) - ID Tag 2
MOb(i) - ID Tag 1
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
MOb(i) - Time Stamp High
MOb(i) - Mess. Data - byte 0
8 bytes
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
173
19.10.1
CANGCON – CAN General Control Register
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 19-9 on page 166).
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
174
– 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
19.10.2
CANGSTA – CAN General Status Register
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 – Res: Reserved
This bit is reserved and will always read as zero.
• 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 – Res: Reserved
This bit is reserved and will always read as zero.
• 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
• Bit 2 – ENFG: Enable Flag
This flag does not generate an interrupt.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
175
– 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
19.10.3
CANGIT – CAN General Interrupt Register
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
• 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
176
• 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
19.10.4
CANGIE – CAN General Interrupt Enable Register
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
• 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
177
• 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
19.10.5
CANEN2 and CANEN1 – CAN Enable MOb Registers
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 - ENMOB[5:0]: Enable MOb
This bit provides the availability of the MOb.
It is set to one when the MOb is enabled (that is, 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 – Res: Reserved
These bits are reserved and will always read as zero.
19.10.6
CANIE2 and CANIE1 – CAN Enable Interrupt MOb Registers
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 - IEMOB[5:0]: Interrupt Enable by MOb
– 0 - interrupt disabled
– 1 - MOb interrupt enabled
Note:
Example: CANIE2 = 0000 1100b : enable of interrupts on MOb 2 and 3
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
178
• Bit 15:6 –Res: Reserved
These bits are reserved for future use. For compatibility with future devices, it must be written to zero when
CANIE1 & CANIE2 are written.
19.10.7
CANSIT2 and CANSIT1 – CAN Status Interrupt MOb Registers
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
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 - SIT[5:0]: Status of Interrupt by MOb
– 0 - no interrupt
– 1- MOb interrupt
Note:
Example: CANSIT2 = 0010 0001b : MOb 0 and 5 interrupts
• Bit 15:6 – Res: Reserved
These bits are reserved and will always read as zero.
19.10.8
CANBT1 – CAN Bit Timing Register 1
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– Res: Reserved
This bit is reserved for future use. For compatibility with future devices, it must be written to zero when CANBT1 is
written.
• Bit 6:1 – BRP[5: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 =
clkIO frequency
If ‘BRP[5..0]=0’, see Section 19.5.3 “Baud rate” on page 165 and Bit 0 – SMP: Sample Point(s) on page 181.
• Bit 0 – Res: Reserved
This bit is reserved for future use. For compatibility with future devices, it must be written to zero when CANBT1 is
written.
19.10.9
CANBT2 – CAN Bit Timing Register 2
Bit
7
6
5
4
3
2
1
0
-
SJW1
SJW0
-
PRS2
PRS1
PRS0
-
Read/write
-
R/W
R/W
-
R/W
R/W
R/W
-
Initial value
-
0
0
-
0
0
0
-
CANBT2
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
179
• Bit 7– Res: Reserved
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 – SJW[1: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 – Res: Reserved
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 – PRS[2: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 – Res: Reserved
This bit is reserved for future use. For compatibility with future devices, it must be written to zero when CANBT2 is
written.
19.10.10 CANBT3 – CAN Bit Timing Register 3
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– Res: Reserved
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 – PHS2[2: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 19.3.3 “CAN bit timing” on page 159 and
Section 19.5.3 “Baud rate” on page 165).
Tphs2 = Tscl × (PHS2 [2:0] + 1)
• Bit 3:1 – PHS1[2: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 × (PHS1 [2:0] + 1)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
180
• 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.
19.10.11 CANTCON – CAN Timer Control Register
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 – TPRSC[7: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 × 8 × (CANTCON [7:0] + 1)
19.10.12 CANTIML and CANTIMH – CAN Timer Registers
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 - CANTIM[15:0]: CAN Timer Count
CAN timer counter range 0 to 65,535.
19.10.13 CANTTCL and CANTTCH – CAN TTC Timer Registers
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 - TIMTTC[15:0]: TTC Timer Count
CAN TTC timer counter range 0 to 65,535.
19.10.14 CANTEC – CAN Transmit Error Counter Register
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 – TEC[7:0]: Transmit Error Count
CAN transmit error counter range 0 to 255.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
181
19.10.15 CANREC – CAN Receive Error Counter Register
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 – REC[7:0]: Receive Error Count
CAN receive error counter range 0 to 255.
19.10.16 CANHPMOB – CAN Highest Priority MOb Register
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 – HPMOB[3: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 166.
• Bit 3:0 – CGP[3:0]: CAN General Purpose Bits
These bits can be pre-programmed to match with the wanted configuration of the CANPAGE register (that is, AINC
and INDX2:0 setting).
19.10.17 CANPAGE – CAN Page MOb Register
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 – INDX[2:0]: FIFO CAN Data Buffer Index
Byte location of the CAN data byte into the FIFO for the defined MOb.
19.11 MOb registers
The MOb registers has no initial (default) value after RESET.
19.11.1
CANSTMOB – CAN MOb Status Register
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
182
• 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.
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
183
No detection of the dominant bit in the acknowledge slot.
19.11.2
CANCDMOB – CAN MOb Control and DLC Register
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 – CONMOB[1: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
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 – DLC[3: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.
19.11.3
CANIDT1, CANIDT2, CANIDT3, and CANIDT4 – CAN Identifier Tag Registers
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
184
V2.0 part B
Bit
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
V2.0
part A
• Bit 31:21 – IDT[10: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 – Res: Reserved
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 – IDT[28: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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
185
• 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.
19.11.4
CANIDM1, CANIDM2, CANIDM3, and CANIDM4 – CAN Identifier Mask Registers
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
CANIDM4
IDMSK12
IDMSK11
IDMSK10
IDMSK9
IDMSK8
IDMSK7
IDMSK6
IDMSK5
CANIDM3
IDMSK20
IDMSK19
IDMSK18
IDMSK17
IDMSK16
IDMSK15
IDMSK14
IDMSK13
CANIDM2
IDMSK28
IDMSK27
IDMSK26
IDMSK25
IDMSK24
IDMSK23
IDMSK22
IDMSK21
CANIDM1
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
-
-
-
-
-
-
-
-
V2.0
part A
• Bit 31:21 – IDMSK[10:0]: Identifier Mask
– 0 - comparison true forced - See “Acceptance filter” on page 168.
– 1 - bit comparison enabled - See “Acceptance filter” on page 168.
• 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 – Res: Reserved
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
186
V2.0
part B
• Bit 31:3 – IDMSK[28:0]: Identifier Mask
– 0 - comparison true forced - See “Acceptance filter” on page 168.
– 1 - bit comparison enabled - See “Acceptance filter” on page 168.
• 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
19.11.5
CANSTML and CANSTMH – CAN Time Stamp Registers
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 - TIMSTM[15:0]: Time Stamp Count
CAN time stamp counter range 0 to 65,535.
19.11.6
CANMSG – CAN Data Message Register
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 – MSG[7: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,...).
19.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 164 and “Baud rate” on page 165 for timing description and page 179 to page 180 for
“CAN Bit Timing Registers”).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
187
Table 19-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%
1000
63% (1)
16.000
12.000
500
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
x
- - - no
data- - -
0.125
8
3
2
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
250
75%
200
75%
125
75%
100
75%
8.000
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
188
Table 19-2.
fCLKIO
[MHz]
Examples of CAN baud rate settings for commonly frequencies. (Continued)
CAN
rate
[Kbps]
Description
Sampling
point
TQ
[µs]
Segments
Tbit
[TQ]
1000
6.000
67% (1)
250
75%
200
80%
125
75%
100
75%
0.166666
12
4.000
Note:
5
Tsjw
[TQ]
CANBT1
CANBT2
CANBT3
0x00
0x08
0x24 (2)
applicable- - 3
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)
Tph2
[TQ]
x
1000
250
Tph1
[TQ]
- - - not
500
500
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 19.5.3 “Baud rate” on page 165
2. See Section • “Bit 0 – SMP: Sample Point(s)” on page 181
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
189
20. LIN / UART - Local Interconnect Network Controller or UART
20.1
Features
20.1.1
LIN
• Hardware implementation of LIN 2.1 (LIN 1.3 Compatibility)
• Small, CPU efficient and independent Master/Slave routines based on “LIN Work Flow Concept” of LIN 2.1
•
•
•
•
•
•
•
specification
Automatic LIN header handling and filtering of irrelevant LIN frames
Automatic LIN response handling
Extended LIN error detection and signalling
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 eight data bits, odd/even/no parity bit, and one stop bit frames
Data over-run and framing error detection
20.1.2
20.2
UART
Overview
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 20Kbit/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).
20.3
LIN protocol
20.3.1
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
190
Figure 20-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.
20.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 20-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 20-3. Structure of a LIN frame.
FRAME SLOT
HEADER
RESPONSE
PROTECTED
IDENTIFIER
SYNC
BREAK
Field
Break delimiter
Field
Field
Response space
DATA-0
DATA-n
Field
CHECKSUM
Field
Inter-byte space
Field
Inter-frame space
Each byte field is transmitted as a serial byte, LSB first.
20.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
191
20.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.
20.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 (for example the LIN1.3 master does not support
the enhanced checksum).
The LIN 2.1 physical layer is backwards compatible with the LIN1.3 physical layer. But not the other way around.
The LIN 2.1 physical layer sets greater requirements, that is, a master node using the LIN 2.1 physical layer can
operate in a LIN 1.3 cluster.
20.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.
20.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
20.3.4 on page 192). The Atmel ATmega16M1/32M1/64M1 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
192
• LERR: LIN Error(s)
The wake-up management can be automated using the UART wake-up capability and a node sending a minimum
of five 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.
20.4.2
20.4.3
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.
LIN/UART controller structure
Figure 20-4. LIN/UART controller block diagram.
CLK IO
RxD
Prescaler
Sample/bit
Get byte
RX
Finite State Machine
FSM
BAUD_RATE
Frame time-out
Put byte
TX
TxD
Synchronization
Monitoring
Data FIFO
BUFFER
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
193
20.4.4
LIN/UART command overview
Figure 20-5. LIN/UART command dependencies.
Tx
response
Tx header
IDOK
TXOK
Rx header
or
LIN abort
Tx
response
RXOK
Automatic
return
LIN
Recommended
way
DISABLE
UART
Possible
way
Byte
transfer
Rx
byte
Full
duplex
Tx
byte
Table 20-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
20.4.5
Comment
no CRC, no time-out
LTXDL=LRXDL=0
(LINDLR: read only register)
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
194
20.4.6
LIN commands
Clearing the LCMD[2] bit in LINCR register enables LIN commands.
As shown in Table 20-1, four functions controlled by the LCMD[1..0] bits of LINCR register are available (c.f. Figure
20-5 on page 194).
20.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 (that is 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
20.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 (that is,
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
20.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
195
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 (that
is 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.
20.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 205).
Note that LRXDL[3..0] and LTXDL[3..0] are not linked to the data access.
20.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 20-1 on page 194.
• 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 20-5 on page 194).
20.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.
20.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
196
considers that the in-coming character is irrelevant without reading it, he directly can clear the flag (see specific flag
management described in Section 20.6.2 on page 208).
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.
20.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 “LINSIR – LIN Status and Interrupt Register” on page 208).
There is no transmit buffering.
No error is detected by this service.
20.5
LIN / UART description
20.5.1
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 20-2.
Table 20-2.
Reset of LIN/UART registers.
Register
Name
Reset Value
LSWRES value
0000 0000 b
LIN control reg.
LINCR
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
20.5.2
Clock
The I/O clock signal (clki/o) also clocks the LIN/UART controller. It is its unique clock.
20.5.3
LIN protocol selection
LIN13 bit in LINCR register is used to select the LIN protocol:
Comment
x=unknown
u=unchanged
• 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 195.
This bit is irrelevant for UART commands.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
197
20.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 20-3):
Table 20-3.
Configuration table versus mode.
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 20-6. Listening mode.
internal
Tx LIN
TXLIN
LISTEN
20.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.
20.5.5.1
Busy signal in LIN mode
Figure 20-7. Busy signal in LIN mode.
FRAME SLOT
HEADER
LIN bus
1) LBUSY
RESPONSE
PROTECTED
IDENTIFIER
SYNC
BREAK
Field
Field
Field
DATA-0
DATA-n
Field
CHECKSUM
Field
Field
Node providing the master task
Node providing a slave task
2) LBUSY
Node providing neither the master task, neither a slave task
3) LBUSY
LCMD=Tx header
LIDOK
LCMD=Tx or Rx response
LTXOK or LRXOK
When the busy signal is set, some registers are locked, user writing is not allowed:
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
198
• “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.
20.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.
20.5.6
Bit timing
20.5.6.1
Baud rate generator
The baud rate is defined to be the transfer rate in bits per second (bps):
• BAUD: Baud rate (in bps)
• clki/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.
20.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
199
20.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 eight 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 20-8).
Figure 20-8. Handling LBT[5:0].
Write in LINBTR register
=1
LENA ?
(LINCR bit 4)
=0
=1
LDISR
to write
=0
LBT[5..0] = LBT[5..0] to write
LBT[5..0] forced to 0x20
LDISR forced to 0
Enable re-synch. in LIN mode
20.5.7
(LBT[5..0]min=8)
LDISR forced to 1
Disable re-synch. in LIN mode
Data length
Section 20.4.6 “LIN commands” on page 195 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.
20.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 eight after the command setting and before sending or
receiving of the first byte
20.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
200
20.5.7.3
Data length in Rx Response
Figure 20-9. LIN2.1 - Rx Response - no error.
LIDOK
LRXOK
LIN bus
LRXDL (*)
4
LTXDL (*)
?
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
LCMD2..0=000b
LCMD=Rx Response
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)
20.5.7.4
Data length in Tx Response
Figure 20-10. LIN1.3 - Tx Response - no error.
LIDOK
LIN bus
LRXDL (*)
4
LTXDL (*)
4
LTXOK
1st Byte
2 nd Byte
3 rd Byte
4 th Byte
DATA-0
DATA-1
DATA-2
DATA-3
0
1
2
3
CHECKSUM
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)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
201
20.5.7.5
Data length after error
Figure 20-11. Tx Response - error.
LERR
LIN bus
1st Byte
2 nd Byte
3 rd Byte
DATA-0
DATA-1
DATA-2
ERROR
LRXDL
4
LTXDL
4
0
1
2
LBUSY
LCMD2..0=000b
LCMD=Tx Response
Note:
20.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
20.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 20.5.13 “Interrupts” on page 204).
20.5.9
xxERR flags
LERR bit of the LINSIR register is an logical ‘OR’ of all the bits of LINERR register (see Section 20.5.13 “Interrupts” on page 204). 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
202
• 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 20.6.8 “LINIDR – LIN Identifier Register” on page 212). 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 “Frame
time out” ).
• 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 20-11 on page 202.
Writing 1 in LERR of LINSIR register resets LERR bit and all the bits of the LINERR register.
20.5.10
Frame time out
According to the LIN protocol, a frame time-out error is flagged if: T
mented in the LIN/UART controller.
Frame
>T
Frame_Maximum.
This feature is imple-
Figure 20-12. LIN timing and frame time-out.
T Frame
T Header
T Response
PROTECTED
IDENTIFIER
SYNC
BREAK
Field
Field
DATA-0
Field
DATA-n
Field
CHECKSUM
Field
Field
Nominal
T Header_Nominal
T Response_Nominal
T Frame_Nominal
T Bit
=
34 x
=
10 ( Number_of_Data + 1 ) x
=
T Header_Nominal
+
T Bit
T Response_Nominal
Maximum
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
203
20.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 (that is, LBERR in case of Tx Response or LFERR in case of Rx
Response). Information on data error is also available, refer to Section "Data length after error", page 202.
• 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.
20.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.
20.5.13
Interrupts
As shown in Figure 20-13, 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 20.5.8 “xxOK flags” on page 202 and Section 20.5.9 “xxERR flags” on page 202.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
204
Figure 20-13. LIN interrupt mapping.
LINERR.7
LABORT
LINERR.6
LTOERR
LINERR.5
LOVERR
LINSIR.3
LINERR.4
LFERR
LIN ERR
LERR
LINERR.3
LSERR
LINENIR.3
LINENIR.2
LINENIR.1
LINENIR.0
LINERR.2
LPERR
LINERR.1
LENERR
LCERR
LINSIR.2
LBERR
LINSIR.1
LINERR.0
LENIDOK
LENTXOK
LENRXOK
LIDOK
LIN IT
LTXOK
LINSIR.0
LRXOK
20.5.14
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 20-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).
20.5.15
Data management
20.5.15.1
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
205
20.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.
20.5.16
OCD support
This chapter describes the behavior of the LIN/UART controller stopped by the OCD (that is I/O view behavior in
AVR Studio®).
1. LINCR:
- LINCR[6..0] are R/W accessible
- LSWRES always is a self-reset bit (needs one 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:
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
206
20.6
20.6.1
Register description
LINCR – LIN Control Register
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
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
The configuration settings for LIN and UART mode are shown in Table 20-5 and Table 20-6.
Table 20-5.
LIN mode configuration.
LCONF[1:0]
Mode
00 (1)
LIN Standard configuration (listen mode “off”, CRC “on” & Frame_Time_Out
“on”
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”)
Note:
1. Default.
Table 20-6.
UART mode configuration.
LCONF[1:0]
Mode
00 (1)
8-bit, no parity (listen mode “off”)
01
8-bit, even parity (listen mode “off”)
10
10 = 8-bit, odd parity (listen mode “off”)
11
Listening mode, 8-bit, no parity
Note:
1. Default.
• 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, and is set according to Table 20-7.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
207
Table 20-7.
20.6.2
LIN commands.
LCMD[2:0]
Mode
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
LINSIR – LIN Status and Interrupt Register
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
The LIN Identifier status is set according to Table 20-8.
Table 20-8.
LIN identifier status
LIDST[2:0]
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)
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
208
• 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.
20.6.3
LINENIR – LIN Enable Interrupt Register
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 - Res: Reserved
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
• 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
209
20.6.4
LINERR – LIN Error Register
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.
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
210
20.6.5
LINBTR – LIN Bit Timing Register
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 ) × (LDIV[11..0] + 1)
Default value: LBT[6:0]=32 — Min. value: LBT[6:0]=8 — Max. value: LBT[6:0]=63
20.6.6
LINBRR – LIN Baud Rate Register
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.
20.6.7
LINDLR – LIN Data Length Register
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
211
20.6.8
LINIDR – LIN Identifier Register
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.
20.6.9
LINSEL – LIN Data Buffer Selection Register
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 - Res: Reserved
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
212
• 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.
20.6.10
LINDAT – LIN Data Register
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
213
21. ADC – Analog to Digital Converter
21.1
Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
10-bit resolution
0.5 LSB integral non-linearity
±2 LSB absolute accuracy
8µs - 250µs conversion time
Up to 120ksps at maximum resolution
11 multiplexed single ended input channels
Three differential input channels with accurate (5%) programmable gain 5, 10, 20 and 40
Optional left adjustment for ADC result readout
0 - VCC ADC input voltage range
Selectable 2.56V 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 Atmel ATmega16M1/32M1/64M1 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 three differential voltage input amplifiers which are equipped with a programmable gain
stage, providing amplification steps of 14dB (5×), 20dB (10×), 26dB (20×), or 32dB (40×) 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 21-1 on page 215.
The ADC has a separate analog supply voltage pin, AVCC. AVCC must not differ more than ±0.3V from VCC. See
Section “ADC noise canceler” on page 220 for 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
214
Figure 21-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
+
+
CONTROL
AMP0CSR
REFS0
ADLAR
MUX3
MUX2
MUX1
MUX0
ADC CONVERSION
COMPLETE IRQ
-
Edge
Detector
-
PRESCALER
ADASCR
ADEN
ADSC
ADATE
ADIF
ADIE
ADPS2
ADPS1
ADPS0
ADCSRA
ADMUX
-
ADCL
AMP1CSR
MUX4
Sources
REFS1
10
CKADC CKADC
CK
AMP2CSR
ADCH
+
+
AMP2+
GND
Bandgap
Temp Sensor
VCC/4
ISRC
10
SAR
ADTS3
ADATE
ADTS2
ADTS1
ADTS0
ADCSRB
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
215
21.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.
21.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
216
Figure 21-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.
Prescaling and conversion timing
Figure 21-3. ADC prescaler.
ADEN
START
Reset
7-BIT ADC PRESCALER
CK/64
CK/128
CK/32
CK/8
CK/16
CK/4
CK
CK/2
21.4
ADPS0
ADPS1
ADPS2
ADC CLOCK SOURCE
By default, the successive approximation circuitry requires an input clock frequency between 50kHz and 2MHz to
get maximum resolution. If a lower resolution than 10 bits is needed, the input clock frequency to the ADC can be
higher than 2MHz to get a higher sample rate.
The ADC module contains a prescaler, which generates an acceptable ADC clock frequency from any CPU frequency above 100kHz. 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.
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 219 for details on
differential conversion timing.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
217
A normal conversion takes 13 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 21-1 on page 219.
Figure 21-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
26
27
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 and hold
Figure 21-5. ADC timing diagram, single conversion.
One conversion
Cycle number
1
2
3
4
5
6
7
8
Next conversion
10
11
12
13
14
1
2
3
ADC clock
ADSC
ADIF
ADCH
Sign and MSB of result
ADCL
LSB of result
Sample and hold
MUX and REFS
update
Conversion
complete
MUX and REFS
update
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
218
Figure 21-6. ADC timing diagram, auto triggered conversion.
One conversion
1
Cycle number
2
3
4
5
6
7
8
Next conversion
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 and
hold
Prescaler
reset
Conversion
complete
MUX and REFS
update
Figure 21-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 and hold
Conversion
complete
Table 21-1.
ADC conversion time.
Condition
Sample & Hold
(Cycles from Start of Conversion)
Conversion Time
(Cycles)
21.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.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
219
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.
21.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
21.5.2
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 impedance voltmeter.
Note that VREF is a high impedance source, and only a capacitive load should be connected to the 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 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 “ADCSRB –
ADC Control and Status Register B”, page 233.
If differential channels are used, the selected reference should not be closer to AVCC than indicated in Table 28-8
on page 302.
21.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:
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
220
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.
21.6.1
Analog input circuitry
The analog input circuitry for single ended channels is illustrated in Figure 21-8 on page 221 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 10k 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 impedance sources with slowly varying signals, since this minimizes the required charge
transfer to the S/H capacitor.
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 21-8. Analog input circuitry.
IIH
ADCn
1..100kΩ
CS/H= 14pF
IIL
VCC/2
21.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:
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
221
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 LC network as
shown in Figure 21-9.
3. Use the ADC noise canceler function to reduce induced noise from the CPU.
4. If any ADC port pins are used as digital outputs, it is essential that these do not switch while a conversion
is in progress.
Figure 21-9. ADC power connections.
VCC
GND
(ACMPN3/ADC0) PE2
(ADC1) PD4
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
PB7(ADC4)
PB6 (ADC7)
PB5 (ADC6/ACMPN1/AMP2-)
PC7 (D2A/AMP2+)
PB4 (AMP0+)
PB3 (AMP0-)
PC6 (ADC10/ACMP1)
AREF (ISRC)
AGND
AVCC
PC5 (ADC9/ACMP3/AMP1+)
PC4 (ADC8/AMP1-)
PB2 (ADC5/ACMPN0)
PD7 (ACMP0)
PD6 (ADC3/ACMPN2)
PD5 (ADC2/ACMP2)
10μH
100nF
Analog ground plane
21.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 “AMP0CSR – Amplifier 0 Control and Status register” on
page 235, “AMP1CSR – Amplifier 1 Control and Status register” on page 237, and “AMP1CSR – Amplifier 1 Control and Status register” on page 237). 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.
21.6.4
ADC accuracy definitions
An n-bit single-ended ADC converts a voltage linearly between GND and VREF in 2n 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
222
Figure 21-10. 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 21-11. 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
223
Figure 21-12. 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 21-13. 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 (1LSB wide) will code to the same value. Always ±0.5LSB
• 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.5LSB.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
224
21.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 21-4 on page
231 and Table 21-5 on page 232). 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 21-14 on page 225 shows the decoding of the differential input range.
Table 21-2 on page 226 shows the resulting output codes if the differential input channel pair (ADCn - ADCm) is
selected with a reference voltage of VREF.
Figure 21-14. Differential measurement range.
Output code
0x1FF
0x000
- VREF /Gain
0x3FF
0
VREF/Gain Differential Input
voltage (Volts)
0x200
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
225
Table 21-2.
Correlation between input voltage and output codes.
VADCn
Read code
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
...
...
...
VADCm - 0.999 VREF /GAIN
0x201
-511
VADCm - VREF /GAIN
0x200
-512
Example 1:
– ADMUX = 0xED (ADC3 - ADC2, 10× gain, 2.56V reference, left adjusted result)
– Voltage on ADC3 is 300mV, voltage on ADC2 is 500mV
– 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, 1× gain, 2.56V reference, left adjusted result)
– Voltage on ADC3 is 300mV, voltage on ADC2 is 500mV
– 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.
21.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.
The measured voltage has a linear relationship to the temperature as described in Table 21-3 The sensitivity is
approximately 2.5mV/C and the accuracy depends on the method of user calibration. Typically, the measurement
accuracy after a single temperature calibration is ±10°C, assuming calibration at room temperature. Better
accuracies are achieved by using two temperature points for calibration.
Table 21-3.
Temperature vs. sensor output voltage (typical case): Example ADC values.
Temperature
–40°C
+25°C
+85°C
Voltage
600mV
762mV
912mV
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
226
The values described in Table 21-3 are typical values. However, due to 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. The sofware calibration can be done using the formula:
T = k × [(ADCH << 8) | ADCL] + TOS
where ADCH and ADCL are the ADC data registers, T is temperature in Kelvin, k is the fixed slope coefficient and
TOS is the temperature sensor offset. Typically, k is very close to 1.0 and in single-point calibration the coefficient
may be omitted. Where higher accuracy is required the slope coefficient should be evaluated based on measurements at two temperatures.
21.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.
21.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 266.
The calibration values are determined from values measured during test at hot temperature which is approximately
+85°C.
The temperature in Celsius degrees can be calculated utilizing the formula:
T = {[(ADCH << 8) | ADCL] × TSGAIN} + TSOFFSET - 273
Where:
a. ADCH & ADCL are the ADC data registers.
21.9
b.
TSGAIN is the temperature sensor gain (constant 1, or unsigned fixed point number, 0x80 = decimal
1.0).
c.
TSOFFSET is the temperature sensor offset correction term (2. complement signed byte).
Amplifier
The Atmel ATmega16M1/32M1/64M1 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 four Amplifier synchronization clock periods.
To ensure an accurate result, the amplifier input needs to have a quite stable input value at the sampling point during at least four amplifier synchronization clock periods.
Amplified conversions can be synchronized to PSC events (see “Synchronization source description in One Ramp
mode.” on page 141 and “Synchronization source description in Centered mode.” on page 142) or to the internal
clock CKADC 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 (that is, 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
227
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 21-5 on page 232.
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 21-15 on page 228 and Figure 21-16 on page 229.
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 21-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
Amplifier
block
Amplifier sample
enable
Amplifier hold
value
Valid sample
ADSC
ADC
ADC
activity
ADC
conv
ADC
sampling
ADC result
ready
ADC
conv
ADC
sampling
ADC result
ready
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
228
Figure 21-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
Amplifier
block
Amplifier sample
enable
Amplifier hold
value
Valid sample
ADSC
ADC
ADC
activity
ADC
conv
ADC
sampling
ADC
sampling
aborted
ADC
conv
ADC
sampling
ADC result
ready
ADC result
ready
In order to have a better understanding of the functioning of the amplifier synchronization, a timing diagram example is shown in Figure 21-15 on page 236.
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.
The block diagram of the two amplifiers is shown on Figure 21-17 on page 230.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
229
Figure 21-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
230
21.10 Register description
The ADC of the Atmel ATmega16M1/32M1/64M1 is controlled through three 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 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.
21.10.1
ADMUX – ADC Multiplexer Register
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 – REFS[1:0]: ADC VREF Selection Bits
These two bits determine the voltage reference for the ADC.
The different setting are shown in Table 21-4.
Table 21-4.
ADC voltage reference selection.
AREFEN
ISRCEN
REFS[1:0]
Description
1
0
00
External VREF on AREF pin, Internal VREF is switched off
1
0
01
AVCC with external capacitor connected on the AREF pin
0
0
01
AVCC (no external capacitor connected on the AREF pin)
1
0
10
Reserved
1
0
11
Internal 2.56V reference voltage with external capacitor
connected on the AREF pin
0
x
11
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 “ADCH and
ADCL – ADC Result Data Registers” on page 234.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
231
21.10.2
Bit 4:0 – MUX[4:0]: ADC Channel Selection Bits
These four bits determine which analog inputs are connected to the ADC input. The different settings are shown in
Table 21-5.
Table 21-5.
ADC input channel selection.
MUX[4:0]
Description
00000
ADC0
00001
ADC1
00010
ADC2
00011
ADC3
00100
ADC4
00101
ADC5
00110
ADC6
00111
ADC7
01000
ADC8
01001
ADC9
01010
ADC10
01011
Temperature sensor
01100
VCC/4
01101
ISRC
01110
AMP0
01111
AMP1 (- is ADC8, + is ADC9)
10000
AMP2 (- is ADC6)
10001
Bandgap
10010
GND
10011
Reserved
101xx
Reserved
1xxxx
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).
21.10.3
ADCSRA – ADC Control and Status Register A
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
232
• 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 21-7 on
page 234.
• 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:0 – ADPS[2:0]: ADC Prescaler Selection Bits
These three bits determine the division factor between the system clock frequency and input clock of the ADC.
The different setting are shown in Table 21-6.
Table 21-6.
21.10.4
ADC prescaler selection.
ADPS[2:0]
Division factor
000
2
001
2
010
4
011
8
100
16
101
32
110
64
111
128
ADCSRB – ADC Control and Status Register B
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.
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
233
• 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
This bit is reserved and will always read as zero.
• Bit 3:0– ADTS[3:0]: 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 21-7, these three 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 21-7.
21.10.5
ADC auto trigger source selection.
ADTS[3:0]
Description
0000
Free Running mode
0001
External interrupt request 0
0010
Timer/Counter0 compare match
0011
Timer/Counter0 overflow
0100
Timer/Counter1 compare Match B
0101
Timer/Counter1 overflow
0110
Timer/Counter1 capture event
0111
PSC Module 0 synchronization signal
1000
PSC Module 1 synchronization signal
1001
PSC Module 2 synchronization signal
1010
Analog comparator 0
1011
Analog comparator 1
1100
Analog comparator 2
1101
Analog comparator 3
1110
Reserved
1111
Reserved
ADCH and ADCL – ADC Result Data Registers
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
234
21.10.5.1
ADLAR = 0
Bit
7
6
5
4
3
2
1
0
-
-
-
-
-
-
ADC9
ADC8
ADCH
ADC7
ADC6
ADC5
ADC4
ADC3
ADC2
ADC1
ADC0
ADCL
Read/write
Initial value
21.10.5.2
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
21.10.6
R
R
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
DIDR0 – Digital Input Disable Register 0
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.
21.10.7
DIDR1 – Digital Input Disable Register 1
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.
21.10.8
AMP0CSR – Amplifier 0 Control and Status register
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
235
• 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 – AMP0G[1:0]: Amplifier 0 Gain Selection Bits
These two bits determine the gain of the amplifier 0.
The different setting are shown in Table 21-8.
Table 21-8.
Amplifier 0 gain selection.
AMP0G[1:0]
Description
00
Gain 5
01
Gain 10
10
Gain 20
11
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 four 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 adapted to the amplifier clock and AMP0TS[2:0] bits have no effect.
Clear this bit to normally use the Amplifier 0.
• Bit 2:0 – AMP0TS[2:0]: Amplifier 0 Clock Source Selection Bits
In accordance with the Table 21-9 on page 236, these three 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.
Table 21-9.
AMP0 clock source selection.
AMP0TS[2:0]
Clock source
000
ADC Clock/8
001
Timer/Counter0 compare match
010
Timer/Counter0 overflow
011
Timer/Counter1 compare Match B
100
Timer/Counter1 overflow
101
PSC Module 0 synchronization signal (PSS0)
110
PSC Module 1 synchronization signal (PSS1)
111
PSC Module 2 synchronization signal (PSS2)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
236
21.10.9
AMP1CSR – Amplifier 1 Control and Status register
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 – AMP1G[1:0]: Amplifier 1 Gain Selection Bits
These two bits determine the gain of the Amplifier 1.
The different setting are shown in Table 21-10.
Table 21-10. Amplifier 1 gain selection.
AMP1G[1:0]
Description
00
Gain 5
01
Gain 10
10
Gain 20
11
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 four amplifier synchronization clock periods.
• 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 adapted to the amplifier clock and AMP1TS2,AMP1TS1, AMP1TS0 bits have no effect.
Clear this bit to normally use the Amplifier 1.
• Bit 2:0 – AMP1TS[2:0]: Amplifier 1 Clock Source Selection Bits
In accordance with the Table 21-11, these three 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 21-11. AMP1 clock source selection .
AMP1TS[2:0]
Clock source
000
ADC Clock/8
001
Timer/Counter0 compare match
010
Timer/Counter0 overflow
011
Timer/Counter1 compare Match B
100
Timer/Counter1 overflow
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
237
Table 21-11. AMP1 clock source selection (Continued).
AMP1TS[2:0]
Clock source
101
PSC Module 0 synchronization signal (PSS0)
110
PSC Module 1 synchronization signal (PSS1)
111
PSC Module 2 synchronization signal (PSS2)
21.10.10 AMP2CSR – Amplifier 2 Control and Status register
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 – AMP2G[1:0]: Amplifier 2 Gain Selection Bits
These two bits determine the gain of the Amplifier 2.
The different setting are shown in Table 21-12 on page 238.
Table 21-12. Amplifier 2 gain selection.
AMP2G[1:0]
Description
00
Gain 5
01
Gain 10
10
Gain 20
11
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 four 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 adapted to the amplifier clock and AMP2TS2, AMP2TS1, AMP2TS0 bits have no effect.
Clear this bit to normally use the Amplifier 2.
• Bit 2:0 – AMP2TS[2:0]: Amplifier 2 Clock Source Selection Bits
In accordance with the Table 21-13, these three 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
238
Table 21-13. AMP1 clock source selection.
AMP2TS[2:0]
Clock source
000
ADC Clock/8
001
Timer/Counter0 compare match
010
Timer/Counter0 overflow
011
Timer/Counter1 compare Match B
100
Timer/Counter1 overflow
101
PSC Module 0 synchronization signal (PSS0)
110
PSC Module 1 synchronization signal (PSS1)
111
PSC Module 2 synchronization signal (PSS2)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
239
22. ISRC - current source
22.1
Features
• 100µA constant current source
• ±2% absolute accuracy
The Atmel ATmega16M1/32M1/64M1 features a 100µA ±2% 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 22-1. Current source block diagram.
AVCC
100uA
ISRCEN
AREF / ISRC
AREF internal circuit
AREFEN
External
resistor
ADC input
22.2
Typical applications
22.2.1
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.
Atmel ATmega16M1/32M1/64M1 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
240
In automotive applications, distributed voltages are very disturbed. The internal Current Source solution of
ATmega16M1/32M1/64M1 immunizes the address detection against any kind of voltage variations.
Table 22-1.
Physical
address
Resistor value
Rload [Ohm]
Minimum voltage
measured [V]
Typical voltage
measured [V]
0
1 000
0.1
1
2 200
0.22
2
3 300
0.33
3
4 700
0.47
4
6 800
0.68
5
10 000
1
6
15 000
1.5
7
22 000
2.2
Table 22-2.
Physical
address
Maximum voltage
measured [V]
Example of resistor values (±1%) for a 16-address system (AVCC = 5V (1)).
Resistor value
Rload [Ohm]
Minimum voltage
measured [V]
Typical voltage
measured [V]
0
2 000
0.2
1
2 400
0.24
2
2 700
0.27
3
3 300
0.33
4
3 900
0.39
5
4 700
0.47
6
5 600
0.56
7
6 800
0.68
8
8 200
0.82
9
9 100
0.91
10
11 000
1.1
11
13 000
1.3
12
16 000
1.6
13
18 000
1.8
14
20 000
2
15
24 000
2.4
Note:
22.2.2
Example of resistor values (±5%) for a 8-address system (AVCC = 5V (1)).
Maximum voltage
measured [V]
1. 5V range: Max. Rload 30K.
3V range: Max. Rload 15K.
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 22-2 on page 241 gives an example of voltage references using standard values of resistors.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
241
22.2.3
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 “AC – analog comparator” on page 243). 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 22-2 on page 241 gives an example of
threshold references using standard values of resistors.
22.3
Register description
22.3.1
ADCSRB – ADC Control and Status Register B
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
242
23. AC – analog comparator
23.1
Features
•
•
•
•
•
23.2
Four analog comparators
High speed clocked comparators
±30mV hysteresis
Four reference levels
Generating configurable interrupts
Overview
The Atmel ATmega16M1/32M1/64M1 features four fast analog comparators. The Analog Comparator compares
the input values on the positive pin ACMPx and negative pin ACMPM or ACMPMx.
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 four 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. A new comparison is done on the falling edge of CLKI/O or CLKI/O/2.
Depending on ACCKDIV fit of ACSR register, see “ACSR – Analog Comparator Status Register” on page 249
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 23-1 on page 244.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
243
Figure 23-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
CLK I/O (/2)
AC1IF
+
ACMP1
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
CLK I/O (/2)
AC2IF
+
ACMP2
Interrupt sensitivity control
ACMPN2
Analog Comparator 2 Interrupt
+
AMP2
AC2IE
AC2EN
-
AC2IS1
AC2IS0
AMPCMP2
AMPCMP2
ADC
AC3O
AC2M
2 1 0
CLK I/O (/2)
AC3IF
+
ACMP3
Interrupt sensitivity control
ACMPN3
Analog Comparator 3 Interrupt
AC3IE
AC3EN
AC3IS1
AC3IS0
DAC
result
Bandgap
AC3M
2 1 0
Aref
AVcc
/1.60
Internal 2.56V
reference
REFS1
REFS0
Notes:
/2.13
/3.20
/6.40
1. ADC multiplexer output: see Table 21-5 on page 232.
2. Refer to Figure 1-1 on page 2 and for analog comparator pin placement.
3. The voltage on VREF is defined in 21-4 “ADC voltage reference selection.” on page 231.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
244
23.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 adapted to the Amplifier 0 clock. See “AMP0CSR – Amplifier 0 Control and Status register” on page 235.
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 adapted to the Amplifier 1 clock. See “AMP1CSR – Amplifier 1 Control and Status register” on page 237.
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 adapted to the Amplifier 2 clock. See “AMP1CSR – Amplifier 1 Control and Status register” on page 237.
23.4
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 four analog comparators.
23.4.1
AC0CON – Analog Comparator 0 Control Register
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 – AC0IS[1:0]: Analog Comparator 0 Interrupt Select bit
These two bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 23-1.
Table 23-1.
Interrupt sensitivity selection.
AC0IS[1:0]
Description
00
Comparator Interrupt on output toggle
01
Reserved
10
Comparator interrupt on output falling edge
11
Comparator interrupt on output rising edge
• Bit 3 – ACCKSEL: Analog Comparator Clock Select
Set this bit to use the PLL output as comparator clock.
Clear this bit to use the CLKIO as comparator clock.
• Bit 2:0 – AC0M[2:0]: Analog Comparator 0 Multiplexer register
These three bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 23-2 on page 246.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
245
Table 23-2.
23.4.2
Analog Comparator 0 negative input selection.
AC0M[2:0]
Description
000
“VREF”/6.40
001
“VREF”/3.20
010
“VREF”/2.13
000
“VREF”/1.60
111
Bandgap (1.1V)
101
DAC result
110
Analog comparator negative input (ACMPM pin)
111
Reserved
AC1CON – Analog Comparator 1 Control Register
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– AC1IS[1:0]: Analog Comparator 1 Interrupt Select bit
These two bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 23-3.
Table 23-3.
Interrupt sensitivity selection.
AC1IS[1:0]
Description
00
Comparator Interrupt on output toggle
01
Reserved
10
Comparator interrupt on output falling edge
11
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 (see “TCCR1B – Timer/Counter1 Control Register B” on page 119) 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
246
Clear this bit to disable this function. In this case, no connection between the analog comparator and the input capture function exists.
• Bit 2:0 – AC1M[2:0]: Analog Comparator 1 Multiplexer register
These three bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 23-4.
Table 23-4.
23.4.3
Analog Comparator 1 negative input selection.
AC1M[2:0]
Description
000
“VREF”/6.40
001
“VREF”/3.20
010
“VREF”/2.13
011
“VREF”/1.60
100
Bandgap (1.1V)
101
DAC result
110
Analog comparator negative input (ACMPM pin)
111
Reserved
AC2CON – Analog Comparator 2 Control Register
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 – AC2IS[1:0]: Analog Comparator 2 Interrupt Select bit
These two bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 23-5 on page 247.
Table 23-5.
Interrupt sensitivity selection.
AC2IS[1:0]
Description
00
Comparator interrupt on output toggle
01
Reserved
10
Comparator interrupt on output falling edge
11
Comparator interrupt on output rising edge
• Bit 3 – Res: Reserved
This bit is reserved and will always read as zero.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
247
• Bit 2:0– AC2M[2:0]: Analog Comparator 2 Multiplexer register
These three bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 23-6.
Table 23-6.
23.4.4
Analog Comparator 2 negative input selection.
AC2M[2:0]
Description
000
“VREF”/6.40
001
“VREF”/3.20
010
“VREF”/2.13
011
“VREF”/1.60
100
Bandgap (1.1V)
101
DAC result
110
Analog comparator negative input (ACMPM pin)
111
Reserved
AC3CON – Analog Comparator 3 Control Register
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– AC3IS[1:0]: Analog Comparator 3 Interrupt Select bit
These two bits determine the sensitivity of the interrupt trigger.
The different setting are shown in Table 23-7 on page 248.
Table 23-7.
Interrupt sensitivity selection.
AC3IS[1:0]
Description
00
Comparator Interrupt on output toggle
01
Reserved
10
Comparator interrupt on output falling edge
11
Comparator interrupt on output rising edge
• Bit 3 – Res: Reserved
This bit is reserved and will always read as zero.
• Bit 2:0 – AC3M[2:0]: Analog Comparator 3 Multiplexer register
These three bits determine the input of the negative input of the analog comparator.
The different setting are shown in Table 23-8.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
248
Table 23-8.
23.4.5
Analog Comparator 3 negative input selection.
AC3M[2:0]
Description
000
“VREF”/6.40
001
“VREF”/3.20
010
“VREF”/2.13
011
“VREF”/1.60
100
Bandgap (1.1V)
101
DAC result
110
Analog comparator negative input (ACMPM pin)
111
Reserved
ACSR – Analog Comparator Status Register
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
249
• 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.
23.4.6
DIDR0 – Digital Input Disable Register 0
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.
23.4.7
DIDR1 – Digital Input Disable Register 1
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
250
24. DAC – digital to analog converter
24.1
Features
•
•
•
•
•
•
24.2
10-bits resolution
8-bits linearity
±0.5LSB accuracy between 100mV and AVCC - 100mV
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 100Ohm. So the driver is able to load a 1nF capacitance in parallel with
a resistor higher than 33K with a time constant around 1µs
Overview
The Atmel ATmega16M1/32M1/64M1 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
Section “ADC noise canceler” on page 220 for how to connect this pin.
The reference voltage is the same as the one used for the ADC, See “ADMUX – ADC Multiplexer Register” on
page 231. 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
251
Figure 24-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
24.3
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.
24.4
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
252
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. 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.
24.4.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 impedance voltmeter.
Note that VREF is a high impedance 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.
24.5
Register description
The DAC is controlled via three dedicated registers, the DACON register which is used for DAC configuration, and
the DACH and DACL which are used to set the value to be converted.
24.5.1
DACON – Digital to Analog Conversion Control Register
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 – DATS[2:0]: 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
253
In accordance with the Table 24-1, these three 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 24-1.
DAC auto trigger source selection.
DATS[2:0]
Description
000
Analog Comparator 0
001
Analog Comparator 1
010
External Interrupt Request 0
011
Timer/Counter0 compare Match
100
Timer/Counter0 Overflow
101
Timer/Counter1 compare Match B
110
Timer/Counter1 overflow
111
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.
24.5.2
DACH and DACL – Digital to Analog Converter input Register
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 eight bits, there is the possibility to left adjust the input value. Like this it is sufficient
to write DACH to update the DAC value.
24.5.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
254
24.5.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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
255
25. debugWIRE on-chip debug system
25.1
Features
•
•
•
•
•
•
•
•
•
•
25.2
Complete program flow control
Emulates all nn-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.
25.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 25-1. The debugWIRE setup.
1.8V - 5.5V
VCC
dW
dW(RESET)
GND
Figure 25-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.
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
256
• Capacitors connected to the RESET pin must be disconnected when using debugWire
• All external reset sources must be disconnected
25.4
Software break points
debugWIRE supports program memory break points by the AVR Break instruction. Setting a Break Point in Atmel
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.
25.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, that is, 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.
25.6
25.6.1
Register description
DWDR – debugWire Data Register
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
257
26. Boot loader support – read-while-write self-programming
•
•
•
•
•
•
•
•
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:
26.1
1. A page is a section in the flash consisting of several bytes (see Table 27-9 on page 278) used during programming.
The page organization does not affect normal operation.
Overview
In Atmel ATmega16M1/32M1/64M1, 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.
26.2
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 26-2 on page 261). The size of the different sections is configured by the BOOTSZ Fuses as shown in Table
26-10 on page 270 and Figure 26-2 on page 261. These two sections can have different level of protection since
they have different sets of Lock bits.
26.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 26-2 on
page 262. The Application section can never store any Boot Loader code since the SPM instruction is disabled
when executed from the Application section.
26.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 26-3 on page 262.
26.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 26-11 on page 270 and Figure 26-2 on page 261. The main differences between the two sections
are:
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
258
• 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.
26.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 (that is, 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 “Addressing the flash during self-programming” on page 263 for details on
how to clear RWWSB.
26.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 26-1.
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
259
Figure 26-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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
260
Figure 26-2. Memory sections.
Program memory
BOOTSZ = '10'
Program memory
BOOTSZ = '11'
0x0000
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
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'
0x0000
Note:
26.4
Read-While-Write section
Application flash section
End RWW
Start NRWW
Application flash section
End application
Start boot loader
Boot Loader flash section
Flashend
No Read-While-Write section
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 26-10 on page 270.
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 26-2 on page 262 and Table 26-3 on page 262 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
261
Table 26-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
1
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
4
Note:
0
0
Protection
1. “1” means unprogrammed, “0” means programmed.
Table 26-3.
Boot Lock Bit1 protection modes (boot loader section) (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
Note:
26.5
Boot Lock Bit0 protection modes (application section) (1).
0
0
Protection
1. “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 26-4.
BOOTRST
Note:
Boot reset fuse (1).
Reset address
1
Reset Vector = Application reset (address 0x0000)
0
Reset Vector = Boot Loader reset (see Table 26-10 on page 270)
1. “1” means unprogrammed, “0” means programmed.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
262
26.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 27-9 on page 278), 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 is shown in Figure 26-3 on page 263. 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 Zpointer 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.
Figure 26-3. Addressing the flash during SPM (1).
BIT
15
ZPCMSB
ZPAGEMSB
Z - REGISTER
1 0
0
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:
26.7
1. The different variables used in Figure 26-3 are listed in Table 26-12 on page 270.
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:
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
263
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 267 for an assembly code example.
26.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
26.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.
26.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
26.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
Section “Moving interrupts between application and boot space” on page 53.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
264
26.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.
26.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 Chapter “Interrupts” on page 50, 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 Section “Simple assembly code example for a boot loader” on page
267 for an example.
26.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 26-2 on page 262 and Table 26-3 on page 262 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.
26.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 (EEPE) in the EECR Register and verifies that the bit is cleared before writing to the SPMCSR
Register.
26.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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
265
value of the Fuse Low byte (FLB) will be loaded in the destination register as shown below. Refer to Table 27-4 on
page 275 for a detailed description and mapping of the Fuse Low byte.
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 27-6 on page 277 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 27-4 on page 275 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.
26.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 26-5
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.
Table 26-5.
Signature Row addressing.
Signature byte
Device Signature Byte 1
0x0000
Device Signature Byte 2
0x0002
Device Signature Byte 3
0x0004
RC Oscillator Calibration Byte
0x0001
Note:
26.7.11
Z-pointer address
All other addresses are reserved for future use.
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):
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
266
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.
26.7.12
Programming time for flash when using SPM
The calibrated RC oscillator is used to time Flash accesses. Table 26-6 shows the typical programming time for
Flash accesses from the CPU.
Table 26-6.
26.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.7ms
4.5ms
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
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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
267
subi
sbci
ldi
call
ZL, low(PAGESIZEB)
;restore pointer
ZH, high(PAGESIZEB)
;not required for PAGESIZEB<=256
spmcrval, (1<<PGWRT) | (1<<SPMEN)
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
; 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
268
26.7.14 Atmel ATmega16M1 - 16K - flash boot loader parameters
In Table 26-10 on page 270 through Table 26-12 on page 270, the parameters used in the description of the self programming are given.
Table 26-7.
BOOTSZ1
Boot size configuration, ATmega16M1 (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 26-2 on page 261.
2. One word equals two bytes.
Table 26-8.
Read-While-Write limit.
Section
Pages
Address
Read-While-Write section (RWW)
96
0x0000 - 0x17FF
No Read-While-Write section (NRWW)
32
0x3800 - 0x1FFF
For details about these two section, see “NRWW – No Read-While-Write Section” on page 259 and “RWW – Read-WhileWrite Section” on page 259.
Table 26-9.
Explanation of different variables used in Figure 26-3 on page 263 and the mapping to the Z-pointer.
Corresponding
Z-value (1)
Variable
PCMSB
12
PAGEMSB
5
Most significant bit in the Program Counter (the Program Counter is 13 bits PC[12:0])
Most significant bit which is used to address the words within one page (64 words in a page
requires six bits PC [5:0])
ZPCMSB
Z13
ZPAGEMSB
Z6
PCPAGE
PC[12:6]
Z13:Z7
PCWORD
PC[5:0]
Z6:Z1
Note:
Description
Bit in Z-register that is mapped to PCMSB. Because Z0 is not used, the ZPCMSB equals
PCMSB + 1
Bit in Z-register that is mapped to PAGEMSB. Because Z0 is not used, the ZPAGEMSB
equals PAGEMSB + 1
Program counter page address: Page select, for page erase and page write
Program counter word address: Word select, for filling temporary buffer (must be zero
during page write operation)
1. 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 263 for details about the use of Z-pointer during SelfProgramming.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
269
26.7.15 Atmel ATmega32M1 - 32K - flash boot loader parameters
In Table 26-10 through Table 26-12, the parameters used in the description of the self programming are given.
Table 26-10. Boot size configuration, ATmega32M1 (32K product).
BOOTSZ1
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
Notes:
1. The different BOOTSZ Fuse configurations are shown in Figure 26-2 on page 261.
2. One word equals two bytes.
Table 26-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 259 and “RWW – Read-WhileWrite Section” on page 259.
Table 26-12. Explanation of different variables used in Figure 26-3 on page 263 and the mapping to the Z-pointer.
Corresponding
Z-value(1)
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 six bits PC [5:0])
ZPCMSB
Z14
ZPAGEMSB
Z6
PCPAGE
PC[13:6]
Z14:Z7
PCWORD
PC[5:0]
Z6:Z1
Note:
Description
Bit in Z-register that is mapped to PCMSB. Because Z0 is not used, the ZPCMSB equals
PCMSB + 1
Bit in Z-register that is mapped to PAGEMSB. Because Z0 is not used, the ZPAGEMSB
equals PAGEMSB + 1
Program counter page address: Page select, for page erase and page write
Program counter word address: Word select, for filling temporary buffer (must be zero
during page write operation)
1. 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 263 for details about the use of Z-pointer during SelfProgramming.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
270
26.7.16 Atmel ATmega64M1 - 64K - flash boot loader parameters
In Table 26-10 on page 270 through Table 26-12 on page 270, the parameters used in the description of the self programming are given.
Table 26-13. Boot size configuration, ATmega64M1 (64K product).
BOOTSZ1
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
Notes:
1. The different BOOTSZ Fuse configurations are shown in Figure 26-2 on page 261.
2. One word equals two bytes.
Table 26-14. Read-While-Write limit.
Section
Pages
Address
Read-While-Write section (RWW)
224
0x0000 - 0x6FFF
No Read-While-Write section (NRWW)
32
0x7000 - 0x7FFF
For details about these two section, see “NRWW – No Read-While-Write Section” on page 259 and “RWW – Read-WhileWrite Section” on page 259.
Table 26-15. Explanation of different variables used in Figure 26-3 on page 263 and the mapping to the Z-pointer.
Corresponding
Z-value (1)
Variable
PCMSB
14
PAGEMSB
7
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 (64 words in a page
requires seven bits PC [6:0])
ZPCMSB
Z15
ZPAGEMSB
Z8
PCPAGE
PC[14:7]
Z15:Z8
PCWORD
PC[6:0]
Z7:Z1
Note:
Description
Bit in Z-register that is mapped to PCMSB. Because Z0 is not used, the ZPCMSB equals
PCMSB + 1
Bit in Z-register that is mapped to PAGEMSB. Because Z0 is not used, the ZPAGEMSB
equals PAGEMSB + 1
Program counter page address: Page select, for page erase and page write
Program counter word address: Word select, for filling temporary buffer (must be zero
during page write operation)
1. 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 263 for details about the use of Z-pointer during SelfProgramming.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
271
26.8
Register description
26.8.1
SPMCSR – Store Program Memory Control and Status Register
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
266 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 265 for details.
• 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 Zpointer. 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
272
• 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
273
27. Memory programming
27.1
Program and data memory Lock bits
The Atmel ATmega16M1/32M1/64M1 provides six Lock bits, which can be left unprogrammed (“1”) or can be programmed (“0”) to obtain the additional features listed in Table 27-2. The Lock bits can only be erased to “1” with the
Chip Erase command.
Table 27-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)
Note:
Bit no.
1. “1” means unprogrammed, “0” means programmed.
Table 27-2.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
274
Table 27-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.
27.2
Fuse bits
The Atmel ATmega16M1/32M1/64M1 has three Fuse bytes. Table 27-4 to Table 27-7 on page 277 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.
Table 27-4.
Extended Fuse byte.
Extended Fuse byte
Bit no.
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)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
275
Table 27-4.
Extended Fuse byte. (Continued)
Extended Fuse byte
Description
Default value
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:
27.3
Bit no.
1. See Table 28-4 on page 297 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 27-4 on page 275).
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 “POC – PSC
Output Configuration” on page 140.
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.
Table 27-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
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)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
276
Table 27-6.
Fuse High byte.
High Fuse byte
Description
Default value
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)
RSTDISBL
Note:
(1)
Bit no.
1. See “Alternate functions of Port C” on page 70 for description of RSTDISBL Fuse.
2. The SPIEN Fuse is not accessible in serial programming mode.
3. See “Watchdog timer configuration.” on page 48 for details.
4. The default value of BOOTSZ1..0 results in maximum Boot Size. See Table 27-11 on page 279 for details.
.
Table 27-7.
Fuse Low byte.
Low Fuse byte
Description
Default value
7
Divide clock by 8
0 (programmed)
CKOUT (3)
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)
CKDIV8
Notes:
(4)
Bit no.
1. The default value of SUT1..0 results in maximum start-up time for the default clock source. See Table 8-9 on page
31 for details.
2. The default setting of CKSEL3..0 results in internal RC Oscillator @ 8MHz. See Table 8-9 on page 31 for details.
3. The CKOUT Fuse allows the system clock to be output on PORTB0. See “Clock output buffer” on page 32 for
details.
4. See “System clock prescaler” on page 32 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.
27.3.1
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
277
27.4
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.
For the Atmel ATmega16M1/32M1/64M1 the signature bytes are given in Table 27-8.
Table 27-8.
Signature bytes.
Signature bytes address
27.5
Part
0x000
0x001
0x002
ATmega16M1
0x1E
0x94
0x84
ATmega32M1
0x1E
0x95
0x84
ATmega64M1
0x1E
0x95
0x84
Calibration byte
The ATmega16M1/32M1/64M1 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.
27.6
Page size
Table 27-9.
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
16K words
(32K bytes)
64 words
(128 bytes)
PC[5:0]
256
PC[13:6]
13
ATmega64M1
32K words
(64K bytes)
128 words
(256 bytes)
PC[6:0]
256
PC[14:7]
14
Table 27-10. No. of words in a page and no. of pages in the EEPROM.
Device
27.7
EEPROM size
Page size
PCWORD
No. of pages
PCPAGE
EEAMSB
ATmega16M1
512 bytes
4 bytes
EEA[1:0]
128
EEA[8:2]
9
ATmega32M1
1024 bytes
4 bytes
EEA[1:0]
256
EEA[9:2]
9
ATmega64M1
2048 bytes
8 bytes
EEA[2:0]
256
EEA[9:2]
9
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 ATmega16M1/32M1/64M1. Pulses are assumed to be at least 250ns unless
otherwise noted.
27.7.1
Signal names
In this section, some pins of the Atmel ATmega16M1/32M1/64M1 are referenced by signal names describing their
functionality during parallel programming, see Figure 27-1 and Table 27-11. Pins not described in the following
table are referenced by pin names.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
278
The XA1/XA0 pins determine the action executed when the XTAL1 pin is given a positive pulse. The bit coding is
shown in Table 27-13 on page 280.
When pulsing WR or OE, the command loaded determines the action executed. The different Commands are
shown in Table 27-14 on page 280.
Figure 27-1. Parallel programming.
+ 5V
RDY/BSY
PD1
OE
PD2
WR
PD3
BS1
PD4
XA0
PD5
XA1
PD6
PAGEL
PD7
VCC
+12V
+5V
AVCC
PB[7:0]
DATA
RESET
PE2
BS2
XTAL1
GND
Table 27-11. 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
Bi-directional Data bus (Output when OE is low)
Table 27-12. 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
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
279
Table 27-13. 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 27-14. Command byte bit coding.
Command byte
27.8
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
Serial programming pin mapping
Table 27-15. Pin mapping serial programming.
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
27.9
Parallel programming
27.9.1
Enter programming mode
The following algorithm puts the device in Parallel (High-voltage) > Programming mode:
1. Set Prog_enable pins listed in Table 27-12 on page 279 to “0000”, RESET pin to “0” and VCC to 0V.
2. Apply 4.5V - 5.5V between VCC and GND. Ensure that VCC reaches at least 1.8V within the next 20µs.
3. Wait 20µs - 60µs, and apply 11.5V - 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
280
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 27-12 on page 279 to “0000”, RESET pin to “0” and VCC to 0V.
2. Apply 4.5V - 5.5V between VCC and GND.
3. Monitor VCC, and as soon as VCC reaches 0.9V - 1.1V, apply 11.5V - 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.5V - 5.5V before giving any parallel programming commands.
6. Exit Programming mode by power the device down or by bringing RESET pin to 0V.
27.9.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
27.9.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.
27.9.4
Programming the flash
The Flash is organized in pages, see Table 27-9 on page 278. 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
281
C. Load Data Low Byte
1. Set XA1, XA0 to “01”. This enables data loading.
2. Set DATA = Data low byte (0x00 - 0xFF).
3. 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 27-3 on page 283 for signal
waveforms.
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 27-2 on page 283. 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 27-3 on page 283 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
282
Figure 27-2. Addressing the flash, which is organized in pages (1).
PCMSB
PROGRAM
COUNTER
PAGEMSB
PCPAGE
PCWORD
PAGE ADDRESS
WITHIN THE FLASH
WORD ADDRESS
WITHIN A PAGE
PROGRAM MEMORY
PAGE
PAGE
PCWORD[PAGEMSB:0]:
00
INSTRUCTION WORD
01
02
PAGEEND
Note:
1. PCPAGE and PCWORD are listed in Table 27-9 on page 278.
Figure 27-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:
27.9.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 27-10 on page 278. 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 281
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).
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
283
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 27-4 on page 284 for signal waveforms).
Figure 27-4. Programming the EEPROM waveforms.
K
DATA
A
G
0x11
ADDR. HIGH
B
ADDR. LOW
C
E
DATA
XX
B
C
ADDR. LOW
DATA
E
L
XX
XA1
XA0
BS1
XTAL1
WR
RDY/BSY
RESET +12V
OE
PAGEL
BS2
27.9.6
Reading the flash
The algorithm for reading the flash memory is as follows (refer to “Programming the flash” on page 281 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”.
27.9.7
Reading the EEPROM
The algorithm for reading the EEPROM memory is as follows (refer to “Programming the flash” on page 281 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”.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
284
27.9.8
Programming the Fuse Low bits
The algorithm for programming the Fuse Low bits is as follows (refer to “Programming the flash” on page 281 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.
27.9.9
Programming the Fuse High bits
The algorithm for programming the Fuse High bits is as follows (refer to “Programming the flash” on page 281 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.
27.9.10
Programming the Extended Fuse bits
The algorithm for programming the Extended Fuse bits is as follows (refer to “Programming the flash” on page 281
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 27-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
27.9.11
Programming the Lock bits
The algorithm for programming the Lock bits is as follows (refer to “Programming the flash” on page 281 for details
on Command and Data loading):
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
285
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.
27.9.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 281 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 27-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
27.9.13
Reading the Signature bytes
The algorithm for reading the Signature bytes is as follows (refer to “Programming the flash” on page 281 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”.
27.9.14
Reading the Calibration byte
The algorithm for reading the Calibration byte is as follows (refer to “Programming the flash” on page 281 for
details on Command and Address loading):
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
286
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”.
27.9.15
Parallel programming characteristics
Figure 27-7. Parallel programming timing, including some general timing requirements.
tXLWL
tXHXL
XTAL1
tDVXH
tXLDX
Data and control
(DATA, XA0/1, BS1, BS2)
tPLBX t BVWL
tBVPH
PAGEL
tWLBX
tPHPL
tWLWH
WR
tPLWL
WLRL
RDY/BSY
tWLRH
Figure 27-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 27-7 (that is, tDVXH, tXHXL, and tXLDX) also apply to loading operation.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
287
Figure 27-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)
ADDR1 (Low byte)
DATA (High byte)
DATA (Low byte)
XA0
XA1
Note:
1. The timing requirements shown in Figure 27-7 on page 287 (that is, tDVXH, tXHXL, and tXLDX) also apply to reading
operation.
Table 27-16. 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
67
tXLXH
XTAL1 Low to XTAL1 High
200
tXHXL
XTAL1 Pulse Width High
150
tXLDX
Data and Control Hold after XTAL1 Low
67
tXLWL
XTAL1 Low to WR Low
0
tXLPH
XTAL1 Low to PAGEL high
0
tPLXH
PAGEL low to XTAL1 high
150
tBVPH
BS1 Valid before PAGEL High
67
tPHPL
PAGEL Pulse Width High
150
tPLBX
BS1 Hold after PAGEL Low
67
tWLBX
BS2/1 Hold after WR Low
67
tPLWL
PAGEL Low to WR Low
67
tBVWL
BS1 Valid to WR Low
67
tWLWH
WR Pulse Width Low
150
tWLRL
WR Low to RDY/BSY Low
tWLRH
tWLRH_CE
Typ.
Max.
Units
12.5
V
250
A
ns
WR Low to RDY/BSY High
(1)
WR Low to RDY/BSY High for Chip Erase
(2)
0
1
3.7
4.5
7.5
9
s
ms
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
288
Table 27-16. Parallel programming characteristics, VCC = 5V ±10%. (Continued)
Symbol
Parameter
tXLOL
XTAL1 Low to OE Low
0
tBVDV
BS1 Valid to DATA valid
0
tOLDV
OE Low to DATA Valid
250
Typ.
Max.
OE High to DATA Tri-stated
250
Units
250
ns
tOHDZ
Notes:
Min.
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.
27.10 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 27-15 on page 280, the pin mapping for SPI programming is listed. Not all parts use the SPI pins
dedicated for the internal SPI interface.
Figure 27-10. Serial programming and verify (1).
+1.8V - 5.5V
VCC
+1.8V - 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.8V - 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 < 12MHz, 3 CPU clock cycles for fck >= 12MHz
High: >2 CPU clock cycles for fck < 12MHz, 3 CPU clock cycles for fck >= 12MHz
27.10.1
Serial programming algorithm
When writing serial data to the Atmel ATmega16M1/32M1/64M1, data is clocked on the rising edge of SCK.
When reading data from the ATmega16M1/32M1/64M1, data is clocked on the falling edge of SCK. See Figure 2711 on page 291 for timing details.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
289
To program and verify the ATmega16M1/32M1/64M1 in the serial programming mode, the following sequence is
recommended (see the four byte instruction formats in Table 27-18 on page 291):
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 20ms 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 6LSB 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 8MSB of the address. If polling is not used, the user must wait at least tWD_FLASH before issuing
the next page (see Table 27-17 on page 291). 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 27-17 on page 291). 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
27.10.2
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 27-17 for tWD_FLASH value.
27.10.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-
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
290
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 27-17 for tWD_EEPROM value.
Table 27-17. Minimum wait delay before writing the next flash or EEPROM location.
Symbol
Minimum wait delay
tWD_FLASH
4.5ms
tWD_EEPROM
3.6ms
tWD_ERASE
9.0ms
Figure 27-11. Serial programming waveforms.
SERIAL DATA INPUT
(MOSI)
MSB
LSB
SERIAL DATA OUTPUT
(MISO)
MSB
LSB
SERIAL CLOCK INPUT
(SCK)
SAMPLE
Table 27-18. Serial programming instruction set.
Instruction format
Instruction
Programming Enable
Chip Erase
Read Program Memory
Byte 1
Byte 2
Byte 3
Byte 4
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
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
Load Program Memory Page
Write Program Memory Page
Read EEPROM Memory
Write EEPROM Memory
Load EEPROM Memory
Page (page access)
Write EEPROM Memory
Page (page access)
Read Lock bits
Operation
Write EEPROM page at address a:b
Read Lock bits. “0” = programmed, “1”
= unprogrammed. See Table 27-1 on
page 274 for details
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
291
Table 27-18. Serial programming instruction set. (Continued)
Instruction format
Instruction
Byte 1
Byte 2
Byte 3
Byte 4
1010 1100
111x xxxx
xxxx xxxx
11ii iiii
Write Lock bits. Set bits = “0” to
program Lock bits. See Table 27-1 on
page 274 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 27-14 on page
280 for details
1010 1100
1010 1000
xxxx xxxx
iiii iiii
Set bits = “0” to program, “1” to
unprogram. See Table 27-6 on page
277 for details
1010 1100
1010 0100
xxxx xxxx
xxxx xxii
Set bits = “0” to program, “1” to
unprogram. See Table 27-4 on page
275 for details
0101 0000
0000 0000
xxxx xxxx
oooo oooo
Read Fuse bits. “0” = programmed, “1”
= unprogrammed. See Table 27-14 on
page 280 for details
0101 1000
0000 1000
xxxx xxxx
oooo oooo
Read Fuse High bits. “0” = programmed, “1” = unprogrammed. See
Table 27-6 on page 277 for details
0101 0000
0000 1000
xxxx xxxx
oooo oooo
Read Extended Fuse bits. “0” = programmed, “1” = unprogrammed. See
Table 27-4 on page 275 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
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
Operation
Note:
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.
27.10.4
SPI serial programming characteristics
For characteristics of the SPI module, see Section “SPI timing characteristics” on page 298.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
292
28. Electrical characteristics
28.1
Absolute maximum ratings*
Operating temperature..................................... -40C to +85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.0mA
DC current VCC and GND pins .................................. 200.0mA
28.2
DC characteristics
TA = -40C to +85C, VCC = 2.7V to 5.5V (unless otherwise noted).
Symbol
Parameter
Condition
Min.
Typ.
Max.
VIL
Input Low Voltage
Port B, C & D and XTAL1,
XTAL2 pins as I/O
-0.5
0.2VCC (1)
VIH
Input High Voltage
Port B, C & D and XTAL1,
XTAL2 pins as I/O
0.6VCC (2)
VCC+0.5
VIL1
Input Low Voltage
XTAL1 pin , external clock
selected
-0.5
0.1VCC (1)
VIH1
Input High Voltage
XTAL1 pin , external clock
selected
0.7VCC (2)
VCC+0.5
VIL2
Input Low Voltage
RESET pin
-0.5
0.2VCC (1)
VIH2
Input High Voltage
RESET pin
0.9VCC (2)
VCC+0.5
VIL3
Input Low Voltage
RESET pin as I/O
-0.5
0.2VCC (1)
VIH3
Input High Voltage
RESET pin as I/O
0.8VCC (2)
VCC+0.5
Units
V
(3)
VOL
Output Low Voltage
(Port B, C & D and
XTAL1, XTAL2 pins as
I/O)
IOL = 10mA, VCC = 5V
IOL = 6mA, VCC = 3V
VOH
Output High Voltage (4)
(Port B, C & D and
XTAL1, XTAL2 pins as
I/O)
IOH = -10mA, VCC = 5V
IOH = -8mA, VCC = 3V
VOL3
Output Low Voltage (3)
(RESET pin as I/O)
IOL = 2.1mA, VCC = 5V
IOL = 0.8mA, VCC = 3V
VOH3
Output High Voltage (4)
(RESET pin as I/O)
IOH = -0.6mA, VCC = 5V
IOH = -0.4mA, VCC = 3V
0.7
0.5
4.2
2.3
0.9
0.7
3.8
2.2
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
293
TA = -40C to +85C, VCC = 2.7V to 5.5V (unless otherwise noted). (Continued)
Symbol
Parameter
Condition
Min.
Typ.
Max.
IIL
Input Leakage
Current I/O Pin
VCC = 5.5V, pin low
(absolute value)
50
IIH
Input Leakage
Current I/O Pin
VCC = 5.5V, pin high
(absolute value)
50
RRST
Reset Pull-up Resistor
30
200
Rpu
I/O Pin Pull-up Resistor
20
50
Units
nA
k
Active 8MHz, VCC = 3V,
RC osc, PRR = 0xFF
3.8
8
Active 16MHz, VCC = 5V,
Ext Clock, PRR = 0xFF
14
30
Power Supply Current
ICC
Power-down mode
(5)
mA
Idle 8MHz, VCC = 3V,
RC Osc
1.5
4
Idle 16MHz, VCC = 5V,
Ext Clock
5.5
15
WDT enabled, VCC = 3V
t0 < 90°C
5
15
WDT enabled, VCC = 3V
t0 < 105°C
9
90
µA
WDT disabled, VCC = 3V
t0 < 90°C
2
10
WDT disabled, VCC = 3V
t0 < 105°C
5
80
25
-35
70
mV
mV
50
nA
Analog Comparator
Hysteresis Voltage
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
Vhysr
Notes:
-100
-50
(6)
(6)
ns
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 (10mA at VCC = 5V, 6mA 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 70mA
2] The sum of all IOL, for ports B6 - B7, C0 - C1, D0 -D3, E0 should not exceed 70mA
3] The sum of all IOL, for ports B2 - B5, C4 - C7, D5 - D7 should not exceed 70mA
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 (10mA at VCC = 5V, 8mA 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 100mA
2] The sum of all IOH, for ports B6 - B7, C0 - C1, D0 -D3, E0 should not exceed 100mA
3] The sum of all IOH, for ports B2 - B5, C4 - C7, D5 - D7 should not exceed 100mA
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.
5. Minimum VCC for power-down is 2.5V.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
294
6. The Analog Comparator Propogation Delay equals one comparator clock plus 30nS. See “AC – analog comparator” on page
243 for comparator clock definition.
28.3
Speed grades
Maximum frequency is depending on VCC. As shown in Figure 28-1, the maximum frequency vs. VCC is linear
between 2.7V and 4.5V.
Figure 28-1. Maximum frequency vs. VCC.
16MHz
8MHz
Safe operating area
2.7V
4.5V
5.5V
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
295
28.4
28.4.1
Clock characteristics
Calibrated internal RC oscillator accuracy
Table 28-1.
Calibration accuracy of internal RC oscillator.
Frequency
VCC
Temperature
Calibration accuracy
8.0MHz
3V
25C
±1%
7.3MHz - 8.1MHz
2.7V - 5.5V
-40C to +85C
±10%
Factory calibration
User calibration
28.5
External clock drive characteristics
Figure 28-2. External clock drive waveforms.
V IH1
V IL1
Table 28-2.
External clock drive.
VCC = 2.7V - 5.5V
VCC = 4.5V - 5.5V
Symbol
Parameter
1/tCLCL
Oscillator Frequency
tCLCL
Clock Period
125
62.5
tCHCX
High Time
50
25
tCLCX
Low Time
50
25
tCLCH
Rise Time
1.6
0.5
tCHCL
Fall Time
1.6
0.5
tCLCL
Change in period from one clock cycle
to the next
2
2
Min.
Max.
Min.
Max.
Units
0
8
0
16
MHz
ns
s
%
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
296
28.6
System and reset characteristics
Table 28-3.
Symbol
VPOT
Reset, brown-out (1) and internal voltage (1) characteristics.
Parameter
Min
Typ
Max
Power-on Reset Threshold Voltage (rising)
1.1
1.4
1.7
Power-on Reset Threshold Voltage (falling) (2)
0.8
0.9
1.6
Units
VPORMAX
VCC maximum start voltage to ensure internal
Power-on Reset signal
VPORMIN
VCC minimum start voltage to ensure internal
Power-on Reset signal
-0.1
VCCRR
VCC Rise Rate to ensure Power-on Reset
0.01
VRST
RESET Pin Threshold Voltage
VHYST
Brown-out Detector Hysteresis
50
mV
tBOD
Min Pulse Width on Brown-out Reset
2
µs
VBG
Bandgap reference voltage
1.1
V
tBG
Bandgap reference start-up time
40
µs
IBG
Bandgap reference current consumption
15
µA
Notes:
0.4
V
V/ms
0.1VCC
0.9VCC
V
1. Values are guidelines only.
2. Before rising, the supply has to be between VPORMIN and VPORMAX to ensure a reset.
Table 28-4.
Notes:
BODLEVEL fuse coding (1)(2).
BODLEVEL 2..0 fuses
Typ VBOT
111
Disabled
110
4.5
011
4.4
100
4.3
010
4.2
001
2.8
101
2.7
000
2.6
Units
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
297
28.7
PLL characteristics
Table 28-5.
Symbol
Parameter
PLLIF
Input frequency
PLLF
PLL factor
PLLLT
Lock-in time
Note:
28.8
PLL characteristics - VCC = 2.7V to 5.5V (unless otherwise noted).
Min.
Typ.
Max.
Units
0.5
1
2
MHz
64
µS
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...).
SPI timing characteristics
See Figure 28-3 on page 299 and Figure 28-4 on page 299 for details.
Table 28-6.
Description
Mode
1
SCK period
Master
See Table 18-5 on
page 155
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
Slave
2 × tck
11
Note:
SPI timing parameters.
SCK high/low
(1)
Min.
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
Typ.
Max.
Units
ns
1600
15
20
10
20
1. In SPI Programming mode the minimum SCK high/low period is:
- 2 tCLCL for fCK <12MHz
- 3 tCLCL for fCK >12MHz
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
298
Figure 28-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
Figure 28-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
17
15
MISO
(Data Output)
MSB
...
LSB
X
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
299
28.9
ADC characteristics
Table 28-7.
Symbol
TUE
INL
DNL
ADC characteristics - TA = -40C to +85C, VCC = 2.7V to 5.5V (unless otherwise noted).
Parameter
Condition
Resolution
Single Ended Conversion
10
VCC = 5V, VREF = 2.56V, ADC clock = 1MHz
3.2
5.0
VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
3.2
5.0
VCC = 5V, VREF = 2.56V, ADC clock = 1MHz
0.7
1.5
VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.8
2.0
VCC = 5V, VREF = 2.56V, ADC clock = 1MHz
0.5
0.8
VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.6
1.2
Absolute accuracy
Integral non-linearity
Differential non-linearity
Gain error
Offset error
VREF
INL
DNL
Absolute accuracy
Integral non-linearity
Differential non-linearity
Gain error
Offset error
VREF
Reference voltage
Typ.
Max.
Units
Bits
LSB
VCC = 5V, VREF = 2.56V, ADC clock = 1MHz
-8.0
-5.0
0.0
VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
-8.0
-5.0
0.0
VCC = 5V, VREF = 2.56V, ADC clock = 1MHz
-2.0
2.5
6.0
VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
-2.0
2.5
6.0
Reference voltage
Resolution
TUE
Min.
2.56
Differential conversion, temp. = -40..85°C
AVCC
8
V
Bits
Gain = 5×, 10×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
1.5
3.5
Gain = 20×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
1.5
4.0
Gain = 40×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
1.5
4.5
Gain = 5×, 10×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.1
1.5
Gain = 20×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.2
2.5
Gain = 40×, VCC = 5V, VREF = 2.56V, ADC clock = 1MHz
0.3
3.5
Gain = 40×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.7
4.5
Gain = 5×, 10×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.1
1.0
Gain = 20×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.2
1.5
Gain = 40×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
0.3
2.5
LSB
Gain = 5×, 10×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
-3.0
3.0
Gain = 20×, 40×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
-3.0
3.0
Gain = 5×, 10×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
-3.0
3.0
Gain = 20×, 40×, VCC = 5V, VREF = 2.56V, ADC clock = 2MHz
-4.0
4.0
2.56
AVCC
-0.5
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
V
300
28.10 Parallel programming characteristics
Figure 28-5. Parallel programming timing, including some general timing requirements.
tXLWL
tXHXL
XTAL1
tDVXH
tXLDX
Data and control
(DATA, XA0/1, BS1, BS2)
tPLBX t BVWL
tBVPH
PAGEL
tWLBX
tPHPL
tWLWH
WR
tPLWL
WLRL
RDY/BSY
tWLRH
Figure 28-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:
1. The timing requirements shown in Figure 28-5 (that is, tDVXH, tXHXL, and tXLDX) also apply to loading operation.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
301
Figure 28-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)
ADDR1 (Low byte)
DATA (High byte)
DATA (Low byte)
XA0
XA1
Note:
1. The timing requirements shown in Figure 28-5 on page 301 (that is, tDVXH, tXHXL, and tXLDX) also apply to reading operation.
Table 28-8.
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
67
tXLXH
XTAL1 Low to XTAL1 High
200
tXHXL
XTAL1 Pulse Width High
150
tXLDX
Data and Control Hold after XTAL1 Low
67
tXLWL
XTAL1 Low to WR Low
0
tXLPH
XTAL1 Low to PAGEL high
0
tPLXH
PAGEL low to XTAL1 high
150
tBVPH
BS1 Valid before PAGEL High
67
tPHPL
PAGEL Pulse Width High
150
tPLBX
BS1 Hold after PAGEL Low
67
tWLBX
BS2/1 Hold after WR Low
67
tPLWL
PAGEL Low to WR Low
67
tBVWL
BS1 Valid to WR Low
67
tWLWH
WR Pulse Width Low
150
tWLRL
WR Low to RDY/BSY Low
tWLRH
WR Low to RDY/BSY High (1)
tWLRH_CE
Typ.
Max.
Units
12.5
V
250
A
ns
WR Low to RDY/BSY High for Chip Erase
(2)
0
1
3.7
5
7.5
10
s
ms
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
302
Table 28-8.
Parallel programming characteristics, VCC = 5V ±10%. (Continued)
Symbol
Parameter
tXLOL
XTAL1 Low to OE Low
0
tBVDV
BS1 Valid to DATA valid
0
tOLDV
OE Low to DATA Valid
250
Typ.
Max.
OE High to DATA Tri-stated
250
Units
250
ns
tOHDZ
Notes:
Min.
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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
303
29. Typical characteristics
Pin pull-up
Figure 29-1. I/O pin pull-up resistor current versus input voltage.
VCC = 5V.
140
120
I OP [µA]
100
80
60
40
20
0
0
0.5
1.0
1.5
2.0
2.5
3.0
3.5
4.0
4.5
-40°C
85°C
25°C
5.0
VOP [V]
Figure 29-2. I/O pin pull-up resistor current versus input voltage.
VCC = 2.7V.
80
70
60
50
IOP [µA]
29.1
40
30
20
10
0
0
0.2
0.4
0.6
0.8
1.0
1.2
1.4
1.6
1.8
2.0
2.2
2.4
-40°C
85°C
25°C
2.6
VOP [V]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
304
Pin driver strength
Figure 29-3. I/O pin low output voltage versus sink current.
VCC = 5V.
1.0
85°C
0.9
0.8
25°C
VOL [V]
0.7
-40°C
0.6
0.5
0.4
0.3
0.2
0.1
0
0
2
4
6
8
10
I OL [mA]
12
14
16
18
20
Figure 29-4. I/O pin low output voltage versus sink current.
VCC = 3V.
0.7
85°C
0.6
25°C
0.5
VOL [V]
29.2
-40°C
0.4
0.3
0.2
0.1
0
0
1
2
3
4
5
6
7
8
9
10
IOL [V]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
305
Figure 29-5. I/O pin output voltage versus source current.
VOH [V]
VCC = 5V.
4.9
4.8
4.7
4.6
4.5
4.4
4.3
4.2
4.1
4.0
3.9
3.8
-40°C
25°C
85°C
0
2
4
6
8
10
IOH [mA]
12
14
16
18
20
Figure 29-6. I/O pin output voltage versus source current.
VCC = 3V.
3.0
2.9
VOH [V]
2.8
2.7
2.6
2.5
-40°C
2.4
25°C
2.3
85°C
2.2
0
1
2
3
4
5
6
7
8
9
10
IOH [mA]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
306
Pin thresholds and hysteresis
Figure 29-7. I/O pin input threshold voltage versus VCC.
VIH, I/O pin read as '1'.
3.0
85°C
25°C
-40°C
2.8
Threshold [V]
2.6
2.4
2.2
2.0
1.8
1.6
1.4
1.2
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
Figure 29-8. I/O pin input threshold voltage versus VCC.
VIL, I/O pin read as '0'.
2.6
85°C
25°C
-40°C
2.4
2.2
Threshold [V]
29.3
2.0
1.8
1.6
1.4
1.2
1.0
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
307
Figure 29-9. I/O pin input hysteresis versus VCC.
0.45
85°C
25°C
-40°C
Input hysteresis [mV]
0.43
0.41
0.39
0.37
0.35
0.33
0.31
0.29
0.27
0.25
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
Figure 29-10. Reset input threshold voltage versus VCC.
VIH, I/O pin read as '1'.
2.4
85°C
25°C
-40°C
2.2
Threshold [V]
2.0
1.8
1.6
1.4
1.2
1.0
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
308
Figure 29-11. Reset input threshold voltage versus VCC.
VIL, I/O pin read as '0'.
-40°C
85°C
25°C
2.4
Threshold [V]
2.2
2.0
1.8
1.6
1.4
1.2
1.0
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
Figure 29-12. Reset pull-up resistor current versus reset pin voltage.
VCC = 5V.
120
100
IRESET [µA]
80
60
40
20
0
0
0.5
1.0
1.5
2.0
2.5
3.0
3.5
4.0
4.5
85°C
-40°C
25°C
5.0
VRESET [V]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
309
Figure 29-13. Reset pull-up resistor current versus reset pin voltage.
VCC = 2.7V.
60
50
IRESET [µA]
40
30
20
10
0
0
0.2
0.4
0.6
0.8
1.0
1.2
1.4
1.6
1.8
2.0
2.2
2.4
85°C
-40°C
25°C
2.6
VRESET [V]
Figure 29-14. XTAL1 input threshold voltage versus VCC.
VIL, XTAL1 pin read as '0'.
2.8
-40°C
25°C
85°C
2.6
Threshold [V]
2.4
2.2
2.0
1.8
1.6
1.4
1.2
1.0
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
310
Figure 29-15. XTAL1 input threshold voltage versus VCC.
VIL, XTAL1 pin read as '1'.
4.0
-40°C
25°C
85°C
Threshold [V]
3.5
3.0
2.5
2.0
1.5
1.0
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
BOD thresholds and analog comparator hysterisis
Figure 29-16. BOD thresholds versus temperature.
BODLEVEL is 2.7V.
2.800
1
2.775
2.750
Threshold [V]
29.4
0
2.725
2.700
2.675
2.650
2.625
-40
-30
-20
-10
0
10
20
30
40
50
60
70
80
90
Temperature [°C]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
311
Internal oscillator speed
Frequency [kHz]
Figure 29-17. Watchdog oscillator frequency versus VCC.
131
130
129
128
127
126
-40°C
125
124
123
122
121
120
2.5
25°C
3.0
3.5
4.0
4.5
85°C
5.5
5.0
VCC [V]
Figure 29-18. Watchdog oscillator frequency versus temperature.
130
129
128
Frequency [kHz]
29.5
127
126
125
124
123
2.7 V
122
3.3 V
4.0 V
4.5 V
5.0 V
5.5 V
90
121
120
-40
-30
-20
-10
0
10
20
30
40
50
60
70
80
Temperature [°C]
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
312
Figure 29-19. Calibrated 8MHz oscillator frequency versus VCC.
8.15
85°C
Frequency [MHz]
8.10
25°C
8.05
8.00
7.95
-40°C
7.90
7.85
7.80
7.75
2.5
3.0
3.5
4.0
4.5
5.0
5.5
VCC [V]
Figure 29-20. Calibrated 8MHz oscillator frequency versus osccal value.
16
25°C
85°C
-40°C
Frequency [MHz]
14
12
10
8
6
4
0
32
64
96
128
160
192
224
256
OSCCAL (X1)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
313
29.6
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 36 for details.
Table 29-1.
Additional current consumption (percentage) in active and idle mode.
Typical ICC [µA]
Percent of added consumption
VCC = 5.0V, 16Mhz
VCC = 3.0V, 8Mhz
PRCAN
13
12
PRPSC
8
7.5
PRTIM1
2
2
PRTIM0
1
1
PRSPI
2
2
PRLIN
5.5
5
PRADC
5
4.5
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
314
30. Register summary
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Page
(0xFF)
Reserved
–
–
–
–
–
–
–
–
(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
187
(0xF9)
CANSTMPH
TIMSTM15
TIMSTM14
TIMSTM13
TIMSTM12
TIMSTM11
TIMSTM10
TIMSTM9
TIMSTM8
187
(0xF8)
CANSTMPL
TIMSTM7
TIMSTM6
TIMSTM5
TIMSTM4
TIMSTM3
TIMSTM2
TIMSTM1
TIMSTM0
187
(0xF7)
CANIDM1
IDMSK28
IDMSK27
IDMSK26
IDMSK25
IDMSK24
IDMSK23
IDMSK22
IDMSK21
186
(0xF6)
CANIDM2
IDMSK20
IDMSK19
IDMSK18
IDMSK17
IDMSK16
IDMSK15
IDMSK14
IDMSK13
186
(0xF5)
CANIDM3
IDMSK12
IDMSK11
IDMSK10
IDMSK9
IDMSK8
IDMSK7
IDMSK6
IDMSK5
186
(0xF4)
CANIDM4
IDMSK4
IDMSK3
IDMSK2
IDMSK1
IDMSK0
RTRMSK
–
IDEMSK
186
(0xF3)
CANIDT1
IDT28
IDT27
IDT26
IDT25
IDT24
IDT23
IDT22
IDT21
184
(0xF2)
CANIDT2
IDT20
IDT19
IDT18
IDT17
IDT16
IDT15
IDT14
IDT13
184
(0xF1)
CANIDT3
IDT12
IDT11
IDT10
IDT9
IDT8
IDT7
IDT6
IDT5
184
(0xF0)
CANIDT4
IDT4
IDT3
IDT2
IDT1
IDT0
RTRTAG
RB1TAG
RB0TAG
184
(0xEF)
CANCDMOB
CONMOB1
CONMOB0
RPLV
IDE
DLC3
DLC2
DLC1
DLC0
184
(0xEE)
CANSTMOB
DLCW
TXOK
RXOK
BERR
SERR
CERR
FERR
AERR
182
(0xED)
CANPAGE
MOBNB3
MOBNB2
MOBNB1
MOBNB0
AINC
INDX2
INDX1
INDX0
182
(0xEC)
CANHPMOB
HPMOB3
HPMOB2
HPMOB1
HPMOB0
CGP3
CGP2
CGP1
CGP0
182
(0xEB)
CANREC
REC7
REC6
REC5
REC4
REC3
REC2
REC1
REC0
182
(0xEA)
CANTEC
TEC7
TEC6
TEC5
TEC4
TEC3
TEC2
TEC1
TEC0
181
(0xE9)
CANTTCH
TIMTTC15
TIMTTC14
TIMTTC13
TIMTTC12
TIMTTC11
TIMTTC10
TIMTTC9
TIMTTC8
181
(0xE8)
CANTTCL
TIMTTC7
TIMTTC6
TIMTTC5
TIMTTC4
TIMTTC3
TIMTTC2
TIMTTC1
TIMTTC0
181
(0xE7)
CANTIMH
CANTIM15
CANTIM14
CANTIM13
CANTIM12
CANTIM11
CANTIM10
CANTIM9
CANTIM8
181
(0xE6)
CANTIML
CANTIM7
CANTIM6
CANTIM5
CANTIM4
CANTIM3
CANTIM2
CANTIM1
CANTIM0
181
(0xE5)
CANTCON
TPRSC7
TPRSC6
TPRSC5
TPRSC4
TPRSC3
TPRSC2
TRPSC1
TPRSC0
181
(0xE4)
CANBT3
–
PHS22
PHS21
PHS20
PHS12
PHS11
PHS10
SMP
180
(0xE3)
CANBT2
–
SJW1
SJW0
–
PRS2
PRS1
PRS0
–
179
(0xE2)
CANBT1
–
BRP5
BRP4
BRP3
BRP2
BRP1
BRP0
–
179
(0xE1)
CANSIT1
–
–
–
–
–
–
–
–
179
(0xE0)
CANSIT2
–
–
SIT5
SIT4
SIT3
SIT2
SIT1
SIT0
179
(0xDF)
CANIE1
–
–
–
–
–
–
–
–
178
(0xDE)
CANIE2
–
–
IEMOB5
IEMOB4
IEMOB3
IEMOB2
IEMOB1
IEMOB0
178
(0xDD)
CANEN1
–
–
–
–
–
–
–
–
178
(0xDC)
CANEN2
–
–
ENMOB5
ENMOB4
ENMOB3
ENMOB2
ENMOB1
ENMOB0
178
(0xDB)
CANGIE
ENIT
ENBOFF
ENRX
ENTX
ENERR
ENBX
ENERG
ENOVRT
177
(0xDA)
CANGIT
CANIT
BOFFIT
OVRTIM
BXOK
SERG
CERG
FERG
AERG
176
(0xD9)
CANGSTA
–
OVRG
–
TXBSY
RXBSY
ENFG
BOFF
ERRP
175
(0xD8)
CANGCON
ABRQ
OVRQ
TTC
SYNTTC
LISTEN
TEST
ENA/STB
SWRES
174
(0xD7)
Reserved
–
–
–
–
–
–
–
–
(0xD6)
Reserved
–
–
–
–
–
–
–
–
(0xD5)
Reserved
–
–
–
–
–
–
–
–
(0xD4)
Reserved
–
–
–
–
–
–
–
–
(0xD3)
Reserved
–
–
–
–
–
–
–
–
(0xD2)
LINDAT
LDATA7
LDATA6
LDATA5
LDATA4
LDATA3
LDATA2
LDATA1
LDATA0
213
(0xD1)
LINSEL
–
–
–
–
/LAINC
LINDX2
LINDX1
LINDX0
212
(0xD0)
LINIDR
LP1
LP0
LID5 / LDL1
LID4 / LDL0
LID3
LID2
LID1
LID0
212
(0xCF)
LINDLR
LTXDL3
LTXDL2
LTXDL1
LTXDL0
LRXDL3
LRXDL2
LRXDL1
LRXDL0
211
(0xCE)
LINBRRH
–
–
–
–
LDIV11
LDIV10
LDIV9
LDIV8
211
(0xCD)
LINBRRL
LDIV7
LDIV6
LDIV5
LDIV4
LDIV3
LDIV2
LDIV1
LDIV0
211
(0xCC)
LINBTR
LDISR
–
LBT5
LBT4
LBT3
LBT2
LBT1
LBT0
211
(0xCB)
LINERR
LABORT
LTOERR
LOVERR
LFERR
LSERR
LPERR
LCERR
LBERR
210
(0xCA)
LINENIR
–
–
–
–
LENERR
LENIDOK
LENTXOK
LENRXOK
209
(0xC9)
LINSIR
LIDST2
LIDST1
LIDST0
LBUSY
LERR
LIDOK
LTXOK
LRXOK
208
(0xC8)
LINCR
LSWRES
LIN13
LCONF1
LCONF0
LENA
LCMD2
LCMD1
LCMD0
207
(0xC7)
Reserved
–
–
–
–
–
–
–
–
(0xC6)
Reserved
–
–
–
–
–
–
–
–
(0xC5)
Reserved
–
–
–
–
–
–
–
–
(0xC4)
Reserved
–
–
–
–
–
–
–
–
(0xC3)
Reserved
–
–
–
–
–
–
–
–
(0xC2)
Reserved
–
–
–
–
–
–
–
–
(0xC1)
Reserved
–
–
–
–
–
–
–
–
(0xC0)
Reserved
–
–
–
–
–
–
–
–
(0xBF)
Reserved
–
–
–
–
–
–
–
–
(0xBE)
Reserved
–
–
–
–
–
–
–
–
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
315
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
(0xBD)
Reserved
–
–
–
–
–
–
–
–
Page
(0xBC)(5)
PIFR
–
–
–
–
PEV2
PEV1
PEV0
PEOP
145
(0xBB)(5)
PIM
–
–
–
–
PEVE2
PEVE1
PEVE0
PEOPE
145
(0xBA)(5)
PMIC2
POVEN2
PISEL2
PELEV2
PFLTE2
PAOC2
PRFM22
PRFM21
PRFM20
144
(0xB9)(5)
PMIC1
POVEN1
PISEL1
PELEV1
PFLTE1
PAOC1
PRFM12
PRFM11
PRFM10
144
(0xB8)(5)
PMIC0
POVEN0
PISEL0
PELEV0
PFLTE0
PAOC0
PRFM02
PRFM01
PRFM00
144
(0xB7)(5)
PCTL
PPRE1
PPRE0
PCLKSEL
–
–
–
PCCYC
PRUN
143
(0xB6)(5)
POC
–
–
POEN2B
POEN2A
POEN1B
POEN1A
POEN0B
POEN0A
140
(0xB5)(5)
PCNF
–
–
PULOCK
PMODE
POPB
POPA
–
–
142
(0xB4)(5)
PSYNC
–
–
PSYNC21
PSYNC20
PSYNC11
PSYNC10
PSYNC01
PSYNC00
141
(0xB3)(5)
POCR_RBH
–
–
–
–
POCR_RB11
POCR_RB10
POCR_RB9
POCR_RB8
142
(0xB2)(5)
POCR_RBL
POCR_RB7
POCR_RB6
POCR_RB5
POCR_RB4
POCR_RB3
POCR_RB2
POCR_RB1
POCR_RB0
142
(0xB1)(5)
POCR2SBH
–
–
–
–
POCR2SB11
POCR2SB10
POCR2SB9
POCR2SB8
142
(0xB0)(5)
POCR2SBL
POCR2SB7
POCR2SB6
POCR2SB5
POCR2SB4
POCR2SB3
POCR2SB2
POCR2SB1
POCR2SB0
142
(0xAF)(5)
POCR2RAH
–
–
–
–
POCR2RA11
POCR2RA10
POCR2RA9
POCR2RA8
142
(0xAE)(5)
POCR2RAL
POCR2RA7
POCR2RA6
POCR2RA5
POCR2RA4
POCR2RA3
POCR2RA2
POCR2RA1
POCR2RA0
142
(0xAD)(5)
POCR2SAH
–
–
–
–
POCR2SA11
POCR2SA10
POCR2SA9
POCR2SA8
142
(0xAC)(5)
POCR2SAL
POCR2SA7
POCR2SA6
POCR2SA5
POCR2SA4
POCR2SA3
POCR2SA2
POCR2SA1
POCR2SA0
142
(0xAB)(5)
POCR1SBH
–
–
–
–
POCR1SB11
POCR1SB10
POCR1SB9
POCR1SB8
142
(0xAA)(5)
POCR1SBL
POCR1SB7
POCR1SB6
POCR1SB5
POCR1SB4
POCR1SB3
POCR1SB2
POCR1SB1
POCR1SB0
142
(0xA9)(5)
POCR1RAH
–
–
–
–
POCR1RA11
POCR1RA10
POCR1RA9
POCR1RA8
142
(0xA8)(5)
POCR1RAL
POCR1RA7
POCR1RA6
POCR1RA5
POCR1RA4
POCR1RA3
POCR1RA2
POCR1RA1
POCR1RA0
142
(0xA7)(5)
POCR1SAH
–
–
–
–
POCR1SA11
POCR1SA10
POCR1SA9
POCR1SA8
142
(0xA6)(5)
POCR1SAL
POCR1SA7
POCR1SA6
POCR1SA5
POCR1SA4
POCR1SA3
POCR1SA2
POCR1SA1
POCR1SA0
142
(0xA5)(5)
POCR0SBH
–
–
–
–
POCR0SB11
POCR0SB10
POCR0SB9
POCR0SB8
142
(0xA4)(5)
POCR0SBL
POCR0SB7
POCR0SB6
POCR0SB5
POCR0SB4
POCR0SB3
POCR0SB2
POCR0SB1
POCR0SB0
142
(0xA3)(5)
POCR0RAH
–
–
–
–
POCR0RA11
POCR0RA10
POCR0RA9
POCR0RA8
142
(0xA2)(5)
POCR0RAL
POCR0RA7
POCR0RA6
POCR0RA5
POCR0RA4
POCR0RA3
POCR0RA2
POCR0RA1
POCR0RA0
142
(0xA1)(5)
POCR0SAH
–
–
–
–
POCR0SA11
POCR0SA10
POCR0SA9
POCR0SA8
142
(0xA0)(5)
POCR0SAL
POCR0SA7
POCR0SA6
POCR0SA5
POCR0SA4
POCR0SA3
POCR0SA2
POCR0SA1
POCR0SA0
142
(0x9F)
Reserved
–
–
–
–
–
–
–
–
(0x9E)
Reserved
–
–
–
–
–
–
–
–
(0x9D)
Reserved
–
–
–
–
–
–
–
–
(0x9C)
Reserved
–
–
–
–
–
–
–
–
(0x9B)
Reserved
–
–
–
–
–
–
–
–
(0x9A)
Reserved
–
–
–
–
–
–
–
–
(0x99)
Reserved
–
–
–
–
–
–
–
–
(0x98)
Reserved
–
–
–
–
–
–
–
–
(0x97)
AC3CON
AC3EN
AC3IE
AC3IS1
AC3IS0
–
AC3M2
AC3M1
AC3M0
247
(0x96)
AC2CON
AC2EN
AC2IE
AC2IS1
AC2IS0
–
AC2M2
AC2M1
AC2M0
247
(0x95)
AC1CON
AC1EN
AC1IE
AC1IS1
AC1IS0
AC1ICE
AC1M2
AC1M1
AC1M0
246
(0x94)
AC0CON
AC0EN
AC0IE
AC0IS1
AC0IS0
ACCKSEL
AC0M2
AC0M1
AC0M0
245
(0x93)
Reserved
–
–
–
–
–
–
–
–
(0x92)
DACH
- / DAC9
- / DAC8
- / DAC7
- / DAC6
- / DAC5
- / DAC4
DAC9 / DAC3
DAC8 / DAC2
254
(0x91)
DACL
DAC7 / DAC1
DAC6 /DAC0
DAC5 / -
DAC4 / -
DAC3 / -
DAC2 / -
DAC1 / -
DAC0 /
254
(0x90)
DACON
DAATE
DATS2
DATS1
DATS0
–
DALA
DAOE
DAEN
253
(0x8F)
Reserved
–
–
–
–
–
–
–
–
(0x8E)
Reserved
–
–
–
–
–
–
–
–
(0x8D)
Reserved
–
–
–
–
–
–
–
–
(0x8C)
Reserved
–
–
–
–
–
–
–
–
(0x8B)
OCR1BH
OCR1B15
OCR1B14
OCR1B13
OCR1B12
OCR1B11
OCR1B10
OCR1B9
OCR1B8
121
(0x8A)
OCR1BL
OCR1B7
OCR1B6
OCR1B5
OCR1B4
OCR1B3
OCR1B2
OCR1B1
OCR1B0
121
(0x89)
OCR1AH
OCR1A15
OCR1A14
OCR1A13
OCR1A12
OCR1A11
OCR1A10
OCR1A9
OCR1A8
121
(0x88)
OCR1AL
OCR1A7
OCR1A6
OCR1A5
OCR1A4
OCR1A3
OCR1A2
OCR1A1
OCR1A0
121
(0x87)
ICR1H
ICR115
ICR114
ICR113
ICR112
ICR111
ICR110
ICR19
ICR18
121
(0x86)
ICR1L
ICR17
ICR16
ICR15
ICR14
ICR13
ICR12
ICR11
ICR10
121
(0x85)
TCNT1H
TCNT115
TCNT114
TCNT113
TCNT112
TCNT111
TCNT110
TCNT19
TCNT18
121
(0x84)
TCNT1L
TCNT17
TCNT16
TCNT15
TCNT14
TCNT13
TCNT12
TCNT11
TCNT10
121
(0x83)
Reserved
–
–
–
–
–
–
–
–
(0x82)
TCCR1C
FOC1A
FOC1B
–
–
–
–
–
–
120
(0x81)
TCCR1B
ICNC1
ICES1
–
WGM13
WGM12
CS12
CS11
CS10
119
(0x80)
TCCR1A
COM1A1
COM1A0
COM1B1
COM1B0
–
–
WGM11
WGM10
117
(0x7F)
DIDR1
–
AMP2PD
ACMP0D
AMP0PD
AMP0ND
ADC10D
ADC9D
ADC8D
235
(0x7E)
DIDR0
ADC7D
ADC6D
ADC5D
ADC4D
ADC3D
ADC2D
ADC1D
ADC0D
235
(0x7D)
Reserved
–
–
–
–
–
–
–
–
(0x7C)
ADMUX
REFS1
REFS0
ADLAR
–
MUX3
MUX2
MUX1
MUX0
231
(0x7B)
ADCSRB
ADHSM
ISRCEN
AREFEN
–
ADTS3
ADTS2
ADTS1
ADTS0
233
(0x7A)
ADCSRA
ADEN
ADSC
ADATE
ADIF
ADIE
ADPS2
ADPS1
ADPS0
232
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
316
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
(0x79)
ADCH
- / ADC9
- / ADC8
- / ADC7
- / ADC6
- / ADC5
- / ADC4
ADC9 / ADC3
ADC8 / ADC2
Page
234
(0x78)
ADCL
ADC7 / ADC1
ADC6 / ADC0
ADC5 / -
ADC4 / -
ADC3 / -
ADC2 / -
ADC1 / -
ADC0 /
234
(0x77)
AMP2CSR
AMP2EN
AMP2IS
AMP2G1
AMP2G0
AMPCMP2
AMP2TS2
AMP2TS1
AMP2TS0
237
(0x76)
AMP1CSR
AMP1EN
AMP1IS
AMP1G1
AMP1G0
AMPCMP1
AMP1TS2
AMP1TS1
AMP1TS0
237
(0x75)
AMP0CSR
AMP0EN
AMP0IS
AMP0G1
AMP0G0
AMPCMP0
AMP0TS2
AMP0TS1
AMP0TS0
235
(0x74)
Reserved
–
–
–
–
–
–
–
–
(0x73)
Reserved
–
–
–
–
–
–
–
–
(0x72)
Reserved
–
–
–
–
–
–
–
–
(0x71)
Reserved
–
–
–
–
–
–
–
–
(0x70)
Reserved
–
–
–
–
–
–
–
–
(0x6F)
TIMSK1
–
–
ICIE1
–
–
OCIE1B
OCIE1A
TOIE1
122
(0x6E)
TIMSK0
–
–
–
–
–
OCIE0B
OCIE0A
TOIE0
95
(0x6D)
PCMSK3
–
–
–
–
–
PCINT26
PCINT25
PCINT24
58
(0x6C)
PCMSK2
PCINT23
PCINT22
PCINT21
PCINT20
PCINT19
PCINT18
PCINT17
PCINT16
59
(0x6B)
PCMSK1
PCINT15
PCINT14
PCINT13
PCINT12
PCINT11
PCINT10
PCINT9
PCINT8
59
(0x6A)
PCMSK0
PCINT7
PCINT6
PCINT5
PCINT4
PCINT3
PCINT2
PCINT1
PCINT0
59
(0x69)
EICRA
ISC31
ISC30
ISC21
ISC20
ISC11
ISC10
ISC01
ISC00
56
(0x68)
PCICR
–
–
–
–
PCIE3
PCIE2
PCIE1
PCIE0
57
(0x68)
Reserved
–
–
–
–
–
–
–
–
(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
34
(0x60)
WDTCSR
WDIF
WDIE
WDP3
WDCE
WDE
WDP2
WDP1
WDP0
47
0x3F (0x5F)
SREG
I
T
H
S
V
N
Z
C
10
0x3E (0x5E)
SPH
SP15
SP14
SP13
SP12
SP11
SP10
SP9
SP8
13
0x3D (0x5D)
SPL
SP7
SP6
SP5
SP4
SP3
SP2
SP1
SP0
13
0x3C (0x5C)
Reserved
–
–
–
–
–
–
–
–
0x3B (0x5B)
Reserved
–
–
–
–
–
–
–
–
0x3A (0x5A)
Reserved
–
–
–
–
–
–
–
–
0x39 (0x59)
Reserved
–
–
–
–
–
–
–
–
0x38 (0x58)
Reserved
–
–
–
–
–
–
–
–
0x37 (0x57)
SPMCSR
SPMIE
RWWSB
–
RWWSRE
BLBSET
PGWRT
PGERS
SPMEN
0x36 (0x56)
Reserved
–
–
–
–
–
–
–
–
33
38
263
0x35 (0x55)
MCUCR
SPIPS
–
–
PUD
–
–
IVSEL
IVCE
54 & 78
0x34 (0x54)
MCUSR
–
–
–
–
WDRF
BORF
EXTRF
PORF
47
0x33 (0x53)
SMCR
–
–
–
–
SM2
SM1
SM0
SE
0x32 (0x52)
MSMCR
0x31 (0x51)
MONDR
0x30 (0x50)
ACSR
AC3IF
AC2IF
AC1IF
AC0IF
AC3O
AC2O
AC1O
AC0O
0x2F (0x4F)
Reserved
–
–
–
–
–
–
–
–
Monitor Stop Mode Control Register
35
reserved
Monitor Data Register
reserved
249
0x2E (0x4E)
SPDR
SPD7
SPD6
SPD5
SPD4
SPD3
SPD2
SPD1
SPD0
156
0x2D (0x4D)
SPSR
SPIF
WCOL
–
–
–
–
–
SPI2X
155
0x2C (0x4C)
SPCR
SPIE
SPE
DORD
MSTR
CPOL
CPHA
SPR1
SPR0
154
0x2B (0x4B)
Reserved
–
–
–
–
–
–
–
–
0x2A (0x4A)
Reserved
–
–
–
–
–
–
–
–
0x29 (0x49)
PLLCSR
-
-
-
-
-
PLLF
PLLE
PLOCK
33
0x28 (0x48)
OCR0B
OCR0B7
OCR0B6
OCR0B5
OCR0B4
OCR0B3
OCR0B2
OCR0B1
OCR0B0
95
0x27 (0x47)
OCR0A
OCR0A7
OCR0A6
OCR0A5
OCR0A4
OCR0A3
OCR0A2
OCR0A1
OCR0A0
94
0x26 (0x46)
TCNT0
TCNT07
TCNT06
TCNT05
TCNT04
TCNT03
TCNT02
TCNT01
TCNT00
94
0x25 (0x45)
TCCR0B
FOC0A
FOC0B
–
–
WGM02
CS02
CS01
CS00
93
0x24 (0x44)
TCCR0A
COM0A1
COM0A0
COM0B1
COM0B0
–
–
WGM01
WGM00
91
0x23 (0x43)
GTCCR
TSM
ICPSEL1
–
–
–
–
–
PSRSYNC
125
0x22 (0x42)
EEARH
–
–
–
–
–
–
EEAR9
EEAR8
21
0x21 (0x41)
EEARL
EEAR7
EEAR6
EEAR5
EEAR4
EEAR3
EEAR2
EEAR1
EEAR0
21
0x20 (0x40)
EEDR
EEDR7
EEDR6
EEDR5
EEDR4
EEDR3
EEDR2
EEDR1
EEDR0
21
0x1F (0x3F)
EECR
–
–
–
–
EERIE
EEMWE
EEWE
EERE
21
0x1E (0x3E)
GPIOR0
GPIOR07
GPIOR06
GPIOR05
GPIOR04
GPIOR03
GPIOR02
GPIOR01
GPIOR00
25
0x1D (0x3D)
EIMSK
–
–
–
–
INT3
INT2
INT1
INT0
56
0x1C (0x3C)
EIFR
–
–
–
–
INTF3
INTF2
INTF1
INTF0
57
0x1B (0x3B)
PCIFR
–
–
–
–
PCIF3
PCIF2
PCIF1
PCIF0
58
0x1A (0x3A)
GPIOR2
GPIOR27
GPIOR26
GPIOR25
GPIOR24
GPIOR23
GPIOR22
GPIOR21
GPIOR20
25
0x19 (0x39)
GPIOR1
GPIOR17
GPIOR16
GPIOR15
GPIOR14
GPIOR13
GPIOR12
GPIOR11
GPIOR10
25
0x18 (0x38)
Reserved
–
–
–
–
–
–
–
–
0x17 (0x37)
Reserved
–
–
–
–
–
–
–
–
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
317
Address
Name
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Page
0x16 (0x36)
TIFR1
–
–
ICF1
–
–
OCF1B
OCF1A
TOV1
122
0x15 (0x35)
TIFR0
–
–
–
–
–
OCF0B
OCF0A
TOV0
95
0x14 (0x34)
Reserved
–
–
–
–
–
–
–
–
0x13 (0x33)
Reserved
–
–
–
–
–
–
–
–
0x12 (0x32)
Reserved
–
–
–
–
–
–
–
–
0x11 (0x31)
Reserved
–
–
–
–
–
–
–
–
0x10 (0x30)
Reserved
–
–
–
–
–
–
–
–
0x0F (0x2F)
Reserved
–
–
–
–
–
–
–
–
0x0E (0x2E)
PORTE
–
–
–
–
–
PORTE2
PORTE1
PORTE0
79
0x0D (0x2D)
DDRE
–
–
–
–
–
DDE2
DDE1
DDE0
79
0x0C (0x2C)
PINE
–
–
–
–
–
PINE2
PINE1
PINE0
79
0x0B (0x2B)
PORTD
PORTD7
PORTD6
PORTD5
PORTD4
PORTD3
PORTD2
PORTD1
PORTD0
79
0x0A (0x2A)
DDRD
DDD7
DDD6
DDD5
DDD4
DDD3
DDD2
DDD1
DDD0
79
0x09 (0x29)
PIND
PIND7
PIND6
PIND5
PIND4
PIND3
PIND2
PIND1
PIND0
79
0x08 (0x28)
PORTC
PORTC7
PORTC6
PORTC5
PORTC4
PORTC3
PORTC2
PORTC1
PORTC0
78
0x07 (0x27)
DDRC
DDC7
DDC6
DDC5
DDC4
DDC3
DDC2
DDC1
DDC0
78
0x06 (0x26)
PINC
PINC7
PINC6
PINC5
PINC4
PINC3
PINC2
PINC1
PINC0
78
0x05 (0x25)
PORTB
PORTB7
PORTB6
PORTB5
PORTB4
PORTB3
PORTB2
PORTB1
PORTB0
78
0x04 (0x24)
DDRB
DDB7
DDB6
DDB5
DDB4
DDB3
DDB2
DDB1
DDB0
78
0x03 (0x23)
PINB
PINB7
PINB6
PINB5
PINB4
PINB3
PINB2
PINB1
PINB0
78
0x02 (0x22)
Reserved
–
–
–
–
–
–
–
–
0x01 (0x21)
Reserved
–
–
–
–
–
–
–
–
0x00 (0x20)
Reserved
–
–
–
–
–
–
–
–
Note:
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 Atmel
ATmega16M1/32M1/64M1 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.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
318
31. Instruction set summary
Mnemonics
Operands
Description
Operation
Flags
#Clocks
ARITHMETIC AND LOGIC INSTRUCTIONS
ADD
Rd, Rr
Add two Registers
Rd  Rd + Rr
Z, C, N, V, H
1
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
1
SBCI
Rd, K
Subtract with Carry Constant from Reg.
Rd  Rd - K - C
Z, C, N, V, H
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
EOR
Rd, Rr
Exclusive OR Registers
Rd  Rd  Rr
Z, N, V
1
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
SBR
Rd,K
Set Bit(s) in Register
Rd  Rd v K
Z, N, V
1
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
RJMP
k
2
BRANCH INSTRUCTIONS
IJMP
Relative Jump
PC PC + k + 1
None
Indirect Jump to (Z)
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
4
ICALL
CALL(*)
k
RET
Subroutine Return
PC  STACK
None
RETI
Interrupt Return
PC  STACK
I
4
Compare, Skip if Equal
if (Rd = Rr) PC PC + 2 or 3
None
1/2/3
CPSE
Rd,Rr
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
BRID
k
Branch if Interrupt Disabled
if (I = 0) then PC  PC + k + 1
None
1/2
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
319
Mnemonics
Operands
Description
Operation
Flags
#Clocks
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
BCLR
s
Flag Clear
SREG(s)  0
SREG(s)
1
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
1
SEC
Set Carry
C1
C
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
DATA TRANSFER INSTRUCTIONS
MOV
Rd, Rr
Move Between Registers
1
Rd, Rr
Copy Register Word
Rd  Rr
Rd+1:Rd  Rr+1:Rr
None
MOVW
None
1
LDI
Rd, K
Load Immediate
Rd  K
None
1
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
LD
Rd, Y+
Load Indirect and Post-Inc.
Rd  (Y), Y  Y + 1
None
2
2
LD
Rd, - Y
Load Indirect and Pre-Dec.
Y  Y - 1, Rd  (Y)
None
LDD
Rd,Y+q
Load Indirect with Displacement
Rd  (Y + q)
None
2
LD
Rd, Z
Load Indirect
Rd  (Z)
None
2
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
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
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
None
1
None
1
MCU CONTROL INSTRUCTIONS
NOP
No Operation
SLEEP
Sleep
(see specific descr. for Sleep function)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
320
Mnemonics
WDR
BREAK
Note:
Operands
Description
Operation
Flags
#Clocks
Watchdog Reset
Break
(see specific descr. for WDR/timer)
For On-chip Debug Only
None
None
1
N/A
1. These Instructions are only available in “16K and 32K parts”
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
321
32. Errata
32.1
Errata Atmel ATmega16M1
The revision letter in this section refers to revisions of the ATmega16M1 device.
32.1.1
Rev. A
Not sampled.
32.2
Errata Atmel ATmega32M1
The revision letter in this section refers to revisions of the ATmega32M1 device.
32.2.1
Rev. A
Not sampled.
32.3
Errata Atmel ATmega64M1
The revision letter in this section refers to revisions of the ATmega64M1 device.
32.3.1
Rev. A
Not sampled.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
322
33. Ordering information
33.1
Note:
Atmel ATmega16M1
Speed
Power supply
16MHz
2.7V - 5.5V
Ordering code
Package
ATmega16M1 - AU
32A
ATmega16M1 - MU
PV
Operation range
Industrial
(-40C to 85C)
All packages are Pb free, fully LHF.
Package type
32A
32-lead, thin (1.0mm) plastic quad flat package (TQFP)
PV
PV, 32-lead, 7.0mm × 7.0mm body, 0.65mm pitch quad flat no lead package (QFN)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
323
33.2
Note:
Atmel ATmega32M1
Speed
Power supply
16MHz
2.7V - 5.5V
Ordering code
Package
ATmega32M1 - AU
32A
ATmega32M1 - MU
PV
Operation range
Industrial
(-40C to 85C)
All packages are Pb free, fully LHF.
Package type
32A
32-lead, thin (1.0mm) plastic quad flat package (TQFP)
PV
PV, 32-lead, 7.0mm × 7.0mm body, 0.65mm pitch quad flat no lead package (QFN)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
324
33.3
Note:
Atmel ATmega64M1
Speed
Power supply
16MHz
2.7V - 5.5V
Ordering code
Package
ATmega64M1 - AU
32A
ATmega64M1 - MU
PV
Operation range
Industrial
(-40C to 85C)
All packages are Pb free, fully LHF.
Package type
32A
32-lead, thin (1.0mm) plastic quad flat package (TQFP)
PV
PV, 32-lead, 7.0mm × 7.0mm body, 0.65mm pitch quad flat no lead package (QFN)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
325
34. Packaging information
34.1
32A
PIN 1 IDENTIFIER
PIN 1
e
B
E1
E
D1
D
C
0°~7°
A1
A2
A
L
COMMON DIMENSIONS
(Unit of measure = mm)
MIN
NOM
MAX
A
–
–
1.20
A1
0.05
–
0.15
A2
0.95
1.00
1.05
D
8.75
9.00
9.25
D1
6.90
7.00
7.10
E
8.75
9.00
9.25
E1
6.90
7.00
7.10
B
0.30
–
0.45
C
0.09
–
0.20
L
0.45
–
0.75
SYMBOL
Notes:
1. This package conforms to JEDEC reference MS-026, Variation ABA.
2. Dimensions D1 and E1 do not include mold protrusion. Allowable
protrusion is 0.25mm per side. Dimensions D1 and E1 are maximum
plastic body size dimensions including mold mismatch.
3. Lead coplanarity is 0.10mm maximum.
e
NOTE
Note 2
Note 2
0.80 TYP
2010-10-20
R
2325 Orchard Parkway
San Jose, CA 95131
TITLE
32A, 32-lead, 7 x 7mm body size, 1.0mm body thickness,
0.8mm lead pitch, thin profile plastic quad flat package (TQFP)
DRAWING NO.
REV.
32A
C
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
326
34.2
PV
PV, 32 - lead 7.0mm x 7.0mm body, 0.65mm pitch
quad flat no lead package (QFN)
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
327
35. Datasheet revision history
Please note that the referring page numbers in this section are referred to this document. The referring revision in
this section are referring to the document revision.
35.1
35.2
35.3
35.4
35.5
8209E – 11/2012
1.
Electrical characteristics added
2.
Updated the whole content with Atmel new logo
3.
Content editing updates
8209D – 11/10
1.
Updated footnote 1in “Features” on page 1.
2.
Removed the chapter “Disclaimer” from the datasheet.
3.
Updated the table Table 27-18 on page 305 with a correct reference for Read Fuse bits.
4.
Updated “SPI Serial Programming Characteristics” on page 306 with correct link.
5.
Added typical values for RAIN and CAIN (both “single ended input” and “differential inputs”) in Table
28-7 on page 314.
6.
Added “PCICR” in “Register Summary” on page 320.
7.
Content editing updates.
8.
Updated the last page according to Atmel new brand style guide.
8209C – 05/10
1.
Replaced 32M1-A package information drawing with PV drawing on page 334.
2.
Updated ordering information with correct info on PV package.
8209B – 10/09
1.
Updated “Temperature Measurement” on page 236.
2.
Updated “Manufacturing Calibration” on page 237.
8209A – 08/09
1.
Initial revision.
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
328
Table of Contents
Features ..................................................................................................... 1
1
Pin configurations .................................................................................... 2
1.1
2
Pin descriptions .................................................................................................3
Overview ................................................................................................... 5
2.1
Block diagram ....................................................................................................6
2.2
Pin descriptions .................................................................................................7
3
Resources ................................................................................................. 8
4
About code examples .............................................................................. 8
5
Data retention ........................................................................................... 8
6
AVR CPU core ........................................................................................... 9
7
8
6.1
Overview ............................................................................................................9
6.2
ALU – Arithmetic Logic Unit .............................................................................10
6.3
Status Register ................................................................................................10
6.4
General purpose register file ...........................................................................12
6.5
Stack Pointer ...................................................................................................13
6.6
Instruction execution timing .............................................................................14
6.7
Reset and interrupt handling ...........................................................................15
Memories ................................................................................................. 17
7.1
Overview ..........................................................................................................17
7.2
In-system reprogrammable flash program memory .........................................17
7.3
SRAM data memory ........................................................................................17
7.4
EEPROM data memory ...................................................................................19
7.5
I/O Memory ......................................................................................................20
7.6
General purpose I/O registers .........................................................................20
7.7
Register description .........................................................................................21
System clock and their distribution ..................................................... 26
8.1
Clock systems and their distribution ................................................................26
8.2
Clock sources ..................................................................................................27
8.3
Default clock source ........................................................................................27
8.4
Low power crystal oscillator .............................................................................28
8.5
Calibrated internal RC oscillator ......................................................................29
8.6
PLL ..................................................................................................................30
8.7
128kHz internal oscillator ................................................................................31
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
i
9
8.8
External clock ..................................................................................................31
8.9
Clock output buffer ..........................................................................................32
8.10
System clock prescaler ....................................................................................32
8.11
Register description .........................................................................................33
Power management and sleep modes ................................................. 35
9.1
Overview ..........................................................................................................35
9.2
Sleep modes ....................................................................................................35
9.3
Idle mode .........................................................................................................35
9.4
ADC Noise Reduction mode ............................................................................36
9.5
Power-down mode ...........................................................................................36
9.6
Standby mode .................................................................................................36
9.7
Power Reduction Register ...............................................................................36
9.8
Minimizing power consumption .......................................................................36
9.9
Register description .........................................................................................38
10 System control and reset ...................................................................... 40
10.1
Resetting the AVR ...........................................................................................40
10.2
Reset sources ..................................................................................................40
10.3
Internal voltage reference ................................................................................43
10.4
Watchdog timer ...............................................................................................43
10.5
Register description .........................................................................................47
11 Interrupts ................................................................................................. 50
11.1
Interrupt vectors in ATmega16M1/32M1/64M1 ...............................................50
11.2
Register description .........................................................................................54
12 External interrupts ................................................................................. 55
12.1
Pin change interrupt timing ..............................................................................55
12.2
Register description .........................................................................................56
13 I/O-ports .................................................................................................. 60
13.1
Overview ..........................................................................................................60
13.2
Ports as general digital I/O ..............................................................................61
13.3
Alternate port functions ....................................................................................65
13.4
Register description .........................................................................................78
14 8-bit Timer/Counter0 with PWM ............................................................ 80
14.1
Features ..........................................................................................................80
14.2
Overview ..........................................................................................................80
14.3
Timer/Counter clock sources ...........................................................................81
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
ii
14.4
Counter unit .....................................................................................................81
14.5
Output compare unit ........................................................................................82
14.6
Compare Match Output Unit ............................................................................84
14.7
Modes of operation ..........................................................................................85
14.8
Timer/Counter timing diagrams .......................................................................89
14.9
Register description .........................................................................................91
15 16-bit Timer/Counter1 with PWM .......................................................... 97
15.1
Features ..........................................................................................................97
15.2
Overview ..........................................................................................................97
15.3
Accessing 16-bit registers ...............................................................................99
15.4
Timer/Counter clock sources .........................................................................102
15.5
Counter unit ...................................................................................................103
15.6
Input Capture unit ..........................................................................................104
15.7
Output Compare units ...................................................................................105
15.8
Compare Match Output unit ..........................................................................107
15.9
Modes of operation ........................................................................................108
15.10
Timer/Counter timing diagrams .....................................................................115
15.11
Register description .......................................................................................117
16 Timer/Counter0 and Timer/Counter1 prescalers ............................... 124
16.1
Internal clock source ......................................................................................124
16.2
Prescaler reset ..............................................................................................124
16.3
External clock source ....................................................................................124
16.4
Register description .......................................................................................125
17 PSC – power stage controller ............................................................. 127
17.1
Features ........................................................................................................127
17.2
Overview ........................................................................................................127
17.3
Accessing 16-bit registers .............................................................................127
17.4
PSC description .............................................................................................128
17.5
Functional description ....................................................................................129
17.6
Update of values ............................................................................................133
17.7
Overlap Protection .........................................................................................134
17.8
Signal description ..........................................................................................134
17.9
PSC input ......................................................................................................135
17.10
PSC input modes 001b to 10xb: Deactivate outputs without changing timing 138
17.11
PSC Input Mode 11xb: Halt PSC and wait for software action ......................138
17.12
Analog synchronization .................................................................................138
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
iii
17.13
Interrupt handling ...........................................................................................139
17.14
PSC clock sources ........................................................................................139
17.15
Interrupts .......................................................................................................140
17.16
Register description .......................................................................................140
18 SPI – Serial Peripheral Interface ......................................................... 147
18.1
Features ........................................................................................................147
18.2
Overview ........................................................................................................147
18.3
SS pin functionality ........................................................................................152
18.4
Data modes ...................................................................................................152
18.5
Register description .......................................................................................154
19 CAN – Controller Area Network .......................................................... 157
19.1
Features ........................................................................................................157
19.2
Overview ........................................................................................................157
19.3
CAN protocol .................................................................................................157
19.4
CAN controller ...............................................................................................162
19.5
CAN channel .................................................................................................163
19.6
Message objects ............................................................................................166
19.7
CAN timer ......................................................................................................169
19.8
Error management .........................................................................................170
19.9
Interrupts .......................................................................................................171
19.10
Register description .......................................................................................173
19.11
MOb registers ................................................................................................182
19.12
Examples of CAN baud rate setting ..............................................................187
20 LIN / UART - Local Interconnect Network Controller or UART ........ 190
20.1
Features ........................................................................................................190
20.2
Overview ........................................................................................................190
20.3
LIN protocol ...................................................................................................190
20.4
LIN / UART controller ....................................................................................192
20.5
LIN / UART description ..................................................................................197
20.6
Register description .......................................................................................207
21 ADC – Analog to Digital Converter ..................................................... 214
21.1
Features ........................................................................................................214
21.2
Operation .......................................................................................................216
21.3
Starting a conversion .....................................................................................216
21.4
Prescaling and conversion timing ..................................................................217
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
iv
21.5
Changing channel or reference selection ......................................................219
21.6
ADC noise canceler .......................................................................................220
21.7
ADC conversion result ...................................................................................225
21.8
Temperature measurement ...........................................................................226
21.9
Amplifier .........................................................................................................227
21.10
Register description .......................................................................................231
22 ISRC - current source .......................................................................... 240
22.1
Features ........................................................................................................240
22.2
Typical applications .......................................................................................240
22.3
Register description .......................................................................................242
23 AC – analog comparator ...................................................................... 243
23.1
Features ........................................................................................................243
23.2
Overview ........................................................................................................243
23.3
Use of ADC amplifiers ...................................................................................245
23.4
Register description .......................................................................................245
24 DAC – digital to analog converter ....................................................... 251
24.1
Features ........................................................................................................251
24.2
Overview ........................................................................................................251
24.3
Operation .......................................................................................................252
24.4
Starting a conversion .....................................................................................252
24.5
Register description .......................................................................................253
25 debugWIRE on-chip debug system .................................................... 256
25.1
Features ........................................................................................................256
25.2
Overview ........................................................................................................256
25.3
Physical interface ..........................................................................................256
25.4
Software break points ....................................................................................257
25.5
Limitations of debugWIRE .............................................................................257
25.6
Register description .......................................................................................257
26 Boot loader support – read-while-write self-programming .............. 258
26.1
Overview ........................................................................................................258
26.2
Application and boot loader flash sections ....................................................258
26.3
Read-while-write and no read-while-write flash sections ...............................258
26.4
Boot loader lock bits ......................................................................................261
26.5
Entering the boot loader program ..................................................................262
26.6
Addressing the flash during self-programming ..............................................263
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
v
26.7
Self-programming the flash ...........................................................................263
26.8
Register description .......................................................................................272
27 Memory programming ......................................................................... 274
27.1
Program and data memory Lock bits .............................................................274
27.2
Fuse bits ........................................................................................................275
27.3
PSC output behavior during reset .................................................................276
27.4
Signature bytes ..............................................................................................278
27.5
Calibration byte ..............................................................................................278
27.6
Page size .......................................................................................................278
27.7
Parallel programming parameters, pin mapping, and commands .................278
27.8
Serial programming pin mapping ...................................................................280
27.9
Parallel programming ....................................................................................280
27.10
Serial downloading ........................................................................................289
28 Electrical characteristics ..................................................................... 293
28.1
Absolute maximum ratings* ...........................................................................293
28.2
DC characteristics .........................................................................................293
28.3
Speed grades ................................................................................................295
28.4
Clock characteristics ......................................................................................296
28.5
External clock drive characteristics ................................................................296
28.6
System and reset characteristics ...................................................................297
28.7
PLL characteristics ........................................................................................298
28.8
SPI timing characteristics ..............................................................................298
28.9
ADC characteristics ......................................................................................300
28.10
Parallel programming characteristics .............................................................301
29 Typical characteristics ......................................................................... 304
29.1
Pin pull-up ......................................................................................................304
29.2
Pin driver strength .........................................................................................305
29.3
Pin thresholds and hysteresis ........................................................................307
29.4
BOD thresholds and analog comparator hysterisis .......................................311
29.5
Internal oscillator speed .................................................................................312
29.6
Using the power reduction register ................................................................314
30 Register summary ................................................................................ 315
31 Instruction set summary ...................................................................... 319
32 Errata ..................................................................................................... 322
32.1
Errata Atmel ATmega16M1 ...........................................................................322
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
vi
32.2
Errata Atmel ATmega32M1 ...........................................................................322
32.3
Errata Atmel ATmega64M1 ...........................................................................322
33 Ordering information ........................................................................... 323
33.1
Atmel ATmega16M1 ......................................................................................323
33.2
Atmel ATmega32M1 ......................................................................................324
33.3
Atmel ATmega64M1 ......................................................................................325
34 Packaging information ......................................................................... 326
34.1
32A ................................................................................................................326
34.2
PV ..................................................................................................................327
35 Datasheet revision history .................................................................. 328
35.1
8209E – 11/2012 ...........................................................................................328
35.2
8209D – 11/10 ...............................................................................................328
35.3
8209C – 05/10 ...............................................................................................328
35.4
8209B – 10/09 ...............................................................................................328
35.5
8209A – 08/09 ...............................................................................................328
Table of Contents ....................................................................................... i
ATmega16M1/32M1/64M1 [DATASHEET]
8209E–AVR–11/2012
vii
Atmel Corporation
1600 Technology Drive
Atmel Asia Limited
Unit 01-5 & 16, 19F
Atmel Munich GmbH
Business Campus
Atmel Japan G.K.
16F Shin-Osaki Kangyo Bldg
San Jose, CA 95110
BEA Tower, Millennium City 5
Parkring 4
1-6-4 Osaki, Shinagawa-ku
USA
418 Kwun Tong Roa
D-85748 Garching b. Munich
Tokyo 141-0032
Tel: (+1) (408) 441-0311
Kwun Tong, Kowloon
GERMANY
JAPAN
Fax: (+1) (408) 487-2600
HONG KONG
Tel: (+49) 89-31970-0
Tel: (+81) (3) 6417-0300
www.atmel.com
Tel: (+852) 2245-6100
Fax: (+49) 89-3194621
Fax: (+81) (3) 6417-0370
Fax: (+852) 2722-1369
© 2012 Atmel Corporation. All rights reserved. / Rev.: 8209E–AVR–11/2012
Atmel®, Atmel logo and combinations thereof, Enabling Unlimited Possibilities®, and others are registered trademarks or trademarks of Atmel Corporation or its
subsidiaries. Other terms and product names may be trademarks of others.
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 THE ATMEL TERMS AND CONDITIONS OF SALES LOCATED ON THE ATMEL WEBSITE, 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 AND 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 products 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 products are not intended, authorized, or warranted for use as components in applications intended to support or sustain life.