Atmega48Pb/88Pb/168Pb: Avr Microcontroller With Core Independent Peripherals and Picopower Technology
Atmega48Pb/88Pb/168Pb: Avr Microcontroller With Core Independent Peripherals and Picopower Technology
Introduction
ATmega48PB/88PB/168PB 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 ATmega48PB/88PB/
168PB achieves throughputs approaching 1MIPS/MHz, allowing the system designer to optimize power
consumption versus processing speed.
Features
• Advanced RISC architecture
– 131 instructions – most single clock cycle execution
– 32 x 8 general purpose working registers
– Fully static operation
– Up to 20MIPS throughput at 20MHz
– On-chip 2-cycle Multiplier
• High endurance non-volatile memory segments
– 4/8/16KBytes of in-system self-programmable Flash program memory
– 256/512/512Bytes EEPROM
– 512/1K/1KBytes internal SRAM
– Write/Erase cycles: 10,000 Flash/100,000 EEPROM
– Data retention: 20 years at 85°C/100 years at 25°C
– Optional boot code section with independent lock bits
• In-system programming by on-chip boot program
• True Read-While-Write (RWW) operation
– Programming lock for software security
• QTouch® library support
– Capacitive touch buttons, sliders and wheels
– QTouch and QMatrix® acquisition
– Up to 64 sense channels
• Peripheral Features
– Two 8-bit Timer/Counters (TC) with separate prescaler and compare mode
– 16-bit Timer/Counter with separate prescaler, compare mode, and capture mode
– Real Time Counter (RTC) with separate oscillator
– Six Pulse Width Modulation (PWM) channels
– 8-channel 10-bit Analog-to-Digital converter (ADC) with temperature measurement
– Programmable serial USART with start-of-frame detection
Introduction......................................................................................................................1
Features.......................................................................................................................... 1
1. Description.................................................................................................................9
2. Configuration Summary...........................................................................................10
3. Ordering Information................................................................................................ 11
3.1. ATmega48PB..............................................................................................................................11
3.2. ATmega88PB..............................................................................................................................11
3.3. ATmega168PB .......................................................................................................................... 12
4. Block Diagram......................................................................................................... 13
5. Pin Configurations................................................................................................... 14
5.1. Pin Descriptions......................................................................................................................... 15
6. I/O Multiplexing........................................................................................................18
8. Resources............................................................................................................... 20
9. Data Retention.........................................................................................................21
17. Interrupts................................................................................................................. 73
17.1. Interrupt Vectors in ATmega48PB.............................................................................................. 73
17.2. Interrupt Vectors in ATmega88PB.............................................................................................. 75
17.3. Interrupt Vectors in ATmega168PB............................................................................................ 80
17.4. Register Description................................................................................................................... 85
19. I/O-Ports.................................................................................................................. 94
23. TC2 - 8-bit Timer/Counter2 with PWM and Asynchronous Operation................... 172
23.1. Features................................................................................................................................... 172
23.2. Overview.................................................................................................................................. 172
23.3. Timer/Counter Clock Sources.................................................................................................. 174
23.4. Counter Unit............................................................................................................................. 174
23.5. Output Compare Unit............................................................................................................... 175
23.6. Compare Match Output Unit.....................................................................................................177
23.7. Modes of Operation..................................................................................................................178
23.8. Timer/Counter Timing Diagrams.............................................................................................. 182
23.9. Asynchronous Operation of Timer/Counter2............................................................................ 183
23.10. Timer/Counter Prescaler.......................................................................................................... 185
23.11. Register Description................................................................................................................. 185
39. Errata.....................................................................................................................404
39.1. Errata ATmega48PB................................................................................................................ 404
39.2. Errata ATmega88PB................................................................................................................ 405
39.3. Errata ATmega168PB.............................................................................................................. 407
Legal Notice.................................................................................................................414
Trademarks................................................................................................................. 414
1. Description
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 ATmega48PB/88PB/168PB provides the following features: 4/8/16Kbytes of In-System
Programmable Flash with Read-While-Write capabilities, 256/512/512 bytes EEPROM, 512/1K/1Kbytes
SRAM, 27 general purpose I/O lines, 32 general purpose working registers, three flexible Timer/Counters
with compare modes, internal and external interrupts, a serial programmable USART, a byte-oriented 2-
wire Serial Interface (I²C), an SPI serial port, a 6-channel 10-bit ADC (8 channels in TQFP and VFQFN
packages), a programmable Watchdog Timer with internal Oscillator, and six software selectable power
saving modes. The Idle mode stops the CPU while allowing the SRAM, Timer/Counters, USART, 2-wire
Serial Interface, SPI port, 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. In Power-save mode, the asynchronous timer continues to run, allowing the user to
maintain a timer base while the rest of the device is sleeping. The ADC Noise Reduction mode stops the
CPU and all I/O modules except asynchronous timer and 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.
It offers the QTouch® library for embedding capacitive touch buttons, sliders and wheels functionality into
AVR microcontrollers. The patented charge-transfer signal acquisition offers robust sensing and includes
fully debounced reporting of touch keys and includes Adjacent Key Suppression® (AKS®) technology for
unambiguous detection of key events. The easy-to-use QTouch Composer allows programers to explore,
develop and debug the their touch applications.
The device is manufactured using high density non-volatile 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 ATmega48PB/88PB/168PB is a powerful
microcontroller that provides a highly flexible and cost effective solution to many embedded control
applications.
The ATmega48PB/88PB/168PB is supported with a full suite of program and system development tools
including: C Compilers, Macro Assemblers, Program Debugger/Simulators, and Evaluation kits.
2. Configuration Summary
Table 2-1. Configuration Summary
3. Ordering Information
3.1 ATmega48PB
Speed [MHz](3) Power Supply [V] Ordering Code(2) Package(1) Operational Range
20 1.8 - 5.5 ATmega48PB-AU 32A Industrial
ATmega48PB-AUR(4) 32A (-40°C to +85°C)
ATmega48PB-MU 32MS1
ATmega48PB-MUR(4) 32MS1
ATmega48PB-AN 32A Industrial
ATmega48PB-ANR(4) 32A (-40°C to +105°C)
ATmega48PB-MN 32MS1
ATmega48PB-MNR(4) 32MS1
Note:
1. This device can also be supplied in wafer form. Contact your local sales office for detailed ordering
information and minimum quantities.
2. Pb-free packaging complies to the European Directive for Restriction of Hazardous Substances
(RoHS directive). Also Halide free and fully Green.
3. See ”Speed Grades” on page 304.
4. Tape & Reel.
Package Type
32A 32-lead, Thin (1.0mm) Plastic Quad Flat Package (TQFP)
32MS1 32-pad, 5.0x5.0x0.9mm body, Lead Pitch 0.50mm, Very-thin Fine pitch, Quad Flat No Lead
Package (VFQFN)
3.2 ATmega88PB
Speed Power Supply Ordering Code(2) Package(1) Operational Range
[MHz](3) [V]
20 1.8 - 5.5 ATmega88PB-AU 32A Industrial
ATmega88PB-AUR(4) 32A (-40°C to +85°C)
ATmega88PB-MU 32MS1
ATmega88PB-MUR(4) 32MS
ATmega88PB-AN 32A Industrial
ATmega88PB-ANR(4)ATmega88PB- 32A (-40°C to +105°C)
MN 32MS1
ATmega88PB-MNR(4) 32MS1
Note:
1. This device can also be supplied in wafer form. Contact your local sales office for detailed ordering
information and minimum quantities.
Package Type
32A 32-lead, Thin (1.0mm) Plastic Quad Flat Package (TQFP)
32MS1 32-pad, 5.0x5.0x0.9mm body, Lead Pitch 0.50mm, Very-thin Fine pitch, Quad Flat No Lead
Package (VFQFN)
3.3 ATmega168PB
Speed [MHz] Power Supply [V] Ordering Code(2) Package(1) Operational Range
20 1.8 - 5.5 ATmega168PB-AU 32A Industrial
ATmega168PB-AUR(3) 32A (-40°C to +85°C)
ATmega168PB-MU 32MS1
ATmega168PB-MUR(3) 32MS1
ATmega168PB-AN 32A Industrial
ATmega168PB-ANR(3) 32A (-40°C to +105°C)
ATmega168PB-MN 32MS1
ATmega168PB-MNR(3) 32MS1
Note:
1. This device can also be supplied in wafer form. Contact your local Atmel sales office for detailed
ordering information and minimum quantities.
2. Pb-free packaging complies to the European Directive for Restriction of Hazardous Substances
(RoHS directive).Also Halide free and fully Green.
3. Tape & Reel.
Package Type
32A 32-lead, Thin (1.0mm) Plastic Quad Flat Package (TQFP)
32MS1 32-pad, 5.0x5.0x0.9mm body, Lead Pitch 0.50mm, Very-thin Fine pitch, Quad Flat No Lead
Package (VFQFN)
4. Block Diagram
Figure 4-1. Block Diagram
SRAM
CPU
debugWire OCD
PARPROG
PB[7:0]
SPIPROG I/O PC[6:0]
I
N PORTS PD[7:0]
PE[3:0]
NVM FLASH /
XTAL1 / Clock generation
TOSC1 programming O
8MHz U
32.768kHz
Calib RC T GPIOR[2:0]
XOSC
XTAL2 / External D EEPROM D
TOSC2 clock Power A TC 0 OC0A
16MHz LP A OC0B
XOSC
128kHz int
management T T
(8-bit)
T0
osc and clock A A
B MISO
control B
EEPROMIF MOSI
U U SPI SCK
S S SS
VCC AIN0
Power Watchdog AIN1
AC
Supervision Timer ACO
RESET ADCMUX
POR/BOD & Internal
RESET Reference
GND
ADC[7:0]
AREF ADC EXTINT
INT[1:0]
PCINT[23:16], PCINT[14:0]
OC1A/B RxD
TC 1
T1
(16-bit) USART TxD
ICP1 XCK
OC2A TC 2 TWI
SDA
OC2B (8-bit async) SCL
5. Pin Configurations
Figure 5-1. 32 TQFP Pinout ATmega48PB/88PB/168PB
PC4 (ADC4/SDA/PCINT12)
PC5 (ADC5/SCL/PCINT13)
PC6 (RESET/PCINT14)
PC3 (ADC3/PCINT11)
PC2 (ADC2/PCINT10)
PD2 (INT0/PCINT18)
PD0 (RXD/PCINT16)
PD1 (TXD/PCINT17)
32
31
30
29
28
27
26
25
(PCINT19/OC2B/INT1) PD3 1 24 PC1 (ADC1/PCINT9)
(PCINT20/XCK/T0) PD4 2 23 PC0 (ADC0/PCINT8)
(ACO) PE0 3 22 PE3 (ADC7)
VCC 4 21 GND
GND 5 20 AREF
PE1 6 19 PE2 (ADC6)
(PCINT6/XTAL1/TOSC1) PB6 7 18 AVCC
(PCINT7/XTAL2/TOSC2) PB7 8 17 PB5 (SCK/PCINT5)
10
11
12
13
14
15
16
9
(PCINT21/OC0B/T1) PD5
(PCINT23/AIN1) PD7
(PCINT22/OC0A/AIN0) PD6
(PCINT3/MOSI/OC2A) PB3
(PCINT1/OC1A) PB1
(PCINT0/CLKO/ICP1) PB0
(PCINT2/SS/OC1B) PB2
(PCINT4/MISO) PB4
PC4 (ADC4/SDA/PCINT12)
PC5 (ADC5/SCL/PCINT13)
PC6 (RESET/PCINT14)
PC3 (ADC3/PCINT11)
PC2 (ADC2/PCINT10)
PD2 (INT0/PCINT18)
PD0 (RXD/PCINT16)
PD1 (TXD/PCINT17)
32
31
30
29
28
27
26
25
(PCINT19/OC2B/INT1) PD3 1 24 PC1 (ADC1/PCINT9)
(PCINT20/XCK/T0) PD4 2 23 PC0 (ADC0/PCINT8)
(ACO) PE0 3 22 PE3 (ADC7)
VCC 4 21 GND
GND 5 20 AREF
PE1 6 19 PE2 (ADC6)
(PCINT6/XTAL1/TOSC1) PB6 7 18 AVCC
(PCINT7/XTAL2/TOSC2) PB7 8 17 PB5 (SCK/PCINT5)
10
11
12
13
14
15
16
9
NOTE:
Bottom pad should be
(PCINT0/CLKO/ICP1) PB0
(PCINT1/OC1A) PB1
(PCINT3/MOSI/OC2A) PB3
(PCINT21/OC0B/T1) PD5
(PCINT23/AIN1) PD7
(PCINT2/SS/OC1B) PB2
(PCINT4/MISO) PB4
(PCINT22/OC0A/AIN0) PD6
soldered to ground
5.1.1 VCC
Digital supply voltage.
5.1.2 GND
Ground.
5.1.5 PC6/RESET
If the RSTDISBL Fuse is programmed, PC6 is used as an I/O pin. Note that the electrical characteristics
of PC6 differ from those of the other pins of Port C.
If the RSTDISBL Fuse is unprogrammed, PC6 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. Shorter pulses are
not guaranteed to generate a Reset.
The various special features of Port C are elaborated in the Alternate Functions of Port C section.
5.1.9 AREF
AREF is the analog reference pin for the A/D Converter.
6. I/O Multiplexing
Each pin is by default controlled by the PORT as a general purpose I/O and alternatively it can be
assigned to one of the peripheral functions.
The following table describes the peripheral signals multiplexed to the PORT I/O pins.
Table 6-1. PORT Function Multiplexing
No PAD EXTINT PCINT ADC/AC OSC T/C # 0 T/C # 1 USART I2C SPI
3 PE[0] ACO
4 VCC
5 GND
6 PE[1]
18 AVCC
19 PE[2] ADC6
20 AREF
21 GND
22 PE[3] ADC7
29 PC[6]/RESET PCINT14
8. Resources
A comprehensive set of development tools, application notes and datasheets are available for download
on http://www.microchip.com/design-centers/8-bit/microchip-avr-mcus.
9. Data Retention
Reliability Qualification results show that the projected data retention failure rate is much less than 1 PPM
over 20 years at 85°C or 100 years at 25°C.
12.1 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 12-1. Block Diagram of the AVR Architecture
Instruction
decode
Status
register ALU
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 x 8-bit general purpose working registers with a single clock
cycle access time. This allows single-cycle Arithmetic Logic Unit (ALU) operation. In a typical ALU
operation, two operands are output from the Register File, the operation is executed, and the result is
stored back in the Register File – in one clock cycle.
Six of the 32 registers can be used as three 16-bit indirect address register pointers for Data Space
addressing – enabling efficient address calculations. One of the these address pointers can also be used
as an address pointer for look up tables in Flash program memory. These added function registers are
the 16-bit X-, Y-, and Z-register, described later in this section.
Name: SREG
Offset: 0x5F
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x3F
Bit 7 6 5 4 3 2 1 0
I T H S V N Z C
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
7 0 Addr.
• One 8-bitR13
output operand and
0x0D one 8-bit result input
R27
Most of the instructions operating0x1B X-register High Byte
on the Register File have direct access to all registers, and most of
them are single cycle instructions. As shown in the figure,
R28 0x1C Y-register Low Byteeach register is also assigned a data memory
X-register 7 0 7 0
R27 R26
15 YH YL 0
Y-register 7 0 7 0
R29 R28
15 ZH ZL 0
Z-register 7 0 7 0
R31 R30
In the different addressing modes these address registers have functions as fixed displacement,
automatic increment, and automatic decrement (see the instruction set reference for details).
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.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Reset value of SPL is RAMEND.
Bit 7 6 5 4 3 2 1 0
SP[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 x
clkCPU
1st Instruction Fetch
1st Instruction Execute
2nd Instruction Fetch
2nd Instruction Execute
3rd Instruction Fetch
3rd Instruction Execute
4th Instruction Fetch
The following figure 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 12-5. Single Cycle ALU Operation
T1 T2 T3 T4
clkCPU
Total Execution Time
C Code Example
char cSREG;
cSREG = SREG; /* store SREG value */
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
C Code Example
Related Links
Interrupts
Memory Programming
Boot Loader Support – Read-While-Write Self-Programming
13.1 Overview
This section describes the different memory types in the device. The AVR architecture has two main
memory spaces, the Data Memory and the Program Memory space. In addition, the device features an
EEPROM Memory for data storage. All memory spaces are linear and regular.
0x0000
0x7FF
0x0000
Related Links
General Purpose Register File
clkCPU
Address Compute Address Address valid
Data
Write
WR
Data
Read
RD
The EEARL and EEARH register pair represents the 16-bit value, EEAR. The low byte [7:0] (suffix L) is
accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Bit 15 14 13 12 11 10 9 8
EEAR[9:8]
Access R/W R/W
Reset x x
Bit 7 6 5 4 3 2 1 0
EEAR[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset x x x x x x x x
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Bit 7 6 5 4 3 2 1 0
EEDR[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: EECR
Offset: 0x3F [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x1F
Bit 7 6 5 4 3 2 1 0
EEPM[1:0] EERIE EEMPE EEPE EERE
Access R/W R/W R/W R/W R/W R/W
Reset x x 0 0 x 0
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 EEPE bit is cleared by hardware. The user
software can poll this bit and wait for a zero before writing the next byte. When EEPE has been
set, the CPU is halted for two cycles before the next instruction is executed.
The following code examples show one assembly and one C function for writing to the EEPROM. The
examples assume that interrupts are controlled (e.g. by disabling interrupts globally) so that no interrupts
will occur during execution of these functions. The examples also assume that no Flash Boot Loader is
present in the software. If such code is present, the EEPROM write function must also wait for any
ongoing SPM command to finish.
Assembly Code Example(1)
EEPROM_write:
; Wait for completion of previous write
sbic EECR,EEPE
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 EEMPE
sbi EECR,EEMPE
; Start eeprom write by setting EEPE
sbi EECR,EEPE
ret
C Code Example(1)
void EEPROM_write(unsigned int uiAddress, unsigned char ucData)
{
/* Wait for completion of previous write */
while(EECR & (1<<EEPE))
;
/* Set up address and Data Registers */
EEAR = uiAddress;
EEDR = ucData;
/* Write logical one to EEMPE */
EECR |= (1<<EEMPE);
/* Start eeprom write by setting EEPE */
EECR |= (1<<EEPE);
}
EEPROM_read:
; Wait for completion of previous write
sbic EECR,EEPE
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(1)
Name: GPIOR2
Offset: 0x4B [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x2B
Bit 7 6 5 4 3 2 1 0
GPIOR2[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: GPIOR1
Offset: 0x4A [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x2A
Bit 7 6 5 4 3 2 1 0
GPIOR1[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: GPIOR0
Offset: 0x3E [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x1E
Bit 7 6 5 4 3 2 1 0
GPIOR0[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Read/Write R R R R R R R R
Watchdog
Oscillator
Related Links
Note: For all fuses, '1' means unprogrammed while '0' means programmed.
Main purpose of the delay is to keep the device in reset until it is supplied with minimum VCC. The delay
will not monitor the actual voltage, so it is required to select a delay longer than the VCC rise time. If this is
not possible, an internal or external Brown-Out Detection circuit should be used. A BOD circuit will ensure
sufficient VCC before it releases the reset, and the time-out delay can be disabled. Disabling the time-out
delay without utilizing a Brown-Out Detection circuit is not recommended.
The oscillator is required to oscillate for a minimum number of cycles before the clock is considered
stable. An internal ripple counter monitors the oscillator output clock, and keeps the internal reset active
for a given number of clock cycles. The reset is then released and the device will start to execute. The
recommended oscillator start-up time is dependent on the clock type, and varies from 6 cycles for an
externally applied clock to 32K cycles for a low frequency crystal.
The start-up sequence for the clock includes both the time-out delay and the start-up time when the
device starts up from reset. When starting up from Power-save or Power-down mode, VCC is assumed to
be at a sufficient level and only the start-up time is included.
Related Links
SCRST - System Control and Reset
C1
XTAL1
GND
where:
• Ce - is optional external capacitors. (= C1, C2 as shown in Figure 14-2)
• Ci - is the pin capacitance in Table 14-3.
• CL - is the load capacitance specified by the crystal vendor.
• CS - is the total stray capacitance for one XTAL pin.
Table 14-3. Internal capacitance of Low-Power Oscillator
The Low Power Oscillator can operate in three different modes, each optimized for a specific frequency
range. The operating mode is selected by the fuses CKSEL[3:1], as shown in the following table:
Table 14-4. Low Power Crystal Oscillator Operating Modes(1)
Note:
1. This is the recommended CKSEL settings for the difference frequency ranges.
2. This option should not be used with crystals, only with ceramic resonators.
Oscillator Source / Power Start-up Time from Additional Delay from CKSEL0 SUT[1:0]
Conditions Power-down and Reset
Power-save (VCC = 5.0V)
Ceramic resonator, fast rising 258 CK 19CK + 4ms(1) 0 00
power
Ceramic resonator, slowly rising 258 CK 19CK + 65ms(1) 0 01
power
Ceramic resonator, BOD 1K CK 19CK(2) 0 10
enabled
Ceramic resonator, fast rising 1K CK 19CK + 4ms(2) 0 11
power
Ceramic resonator, slowly rising 1K CK 19CK + 65ms(2) 1 00
power
Crystal Oscillator, BOD enabled 16K CK 19CK 1 01
Crystal Oscillator, fast rising 16K CK 19CK + 4ms 1 10
power
Crystal Oscillator, slowly rising 16K CK 19CK + 65ms 1 11
power
Note:
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.
Note:
1. Maximum ESR is typical value based on characterization.
The Low-frequency Crystal Oscillator provides an internal load capacitance at each TOSC pin:
Table 14-7. Capacitance for Low-Frequency Oscillator
32kHz Osc. Type Internal Pad Capacitance (XTAL1/ Internal Pad Capacitance (XTAL2/
TOSC1) TOSC2)
System Osc. 18pF 8pF
Timer Osc. 18pF 8pF
The capacitance (Ce+Ci) needed at each TOSC pin can be calculated by using:
�� + �� = 2�� − ��
where:
• Ce - is optional external capacitors. (= C1, C2 as shown in Figure 14-2)
• Ci - is the pin capacitance in Table 14-3.
• CL - is the load capacitance specified by the crystal vendor.
• CS - is the total stray capacitance for one XTAL pin.
Crystals specifying a load capacitance (CL) higher than 6pF require external capacitors applied as
described in Figure 14-2.
The Low-frequency Crystal Oscillator must be selected by setting the CKSEL Fuses to '0110' or
'0111',and Start-Up times are determined by the SUT Fuses, as shown in the following two tables.
Table 14-8. Start-Up Times for the Low-frequency Crystal Oscillator Clock Selection - SUT Fuses
Note:
1. This option should only be used if frequency stability at start-up is not important for the application.
Note:
1. 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 8.
2. The device is shipped with this option selected.
When this Oscillator is selected, start-up times are determined by the SUT Fuses:
Table 14-11. Start-Up Times for the Internal Calibrated RC Oscillator Clock Selection - SUT
Power Conditions Start-Up Time from Power-down Additional Delay from Reset SUT[1:0]
and Power-Save (VCC = 5.0V)
BOD enabled 6 CK 19CK(1) 00
Fast rising power 6 CK 19CK + 4.1ms 01
Slowly rising power 6 CK 19CK + 65ms(2) 10
Reserved 11
Note:
1. If the RSTDISBL fuse is programmed, this start-up time will be increased to
19CK + 4.1ms to ensure programming mode can be entered.
2. The device is shipped with this option selected.
By changing the OSCCAL register from SW, it is possible to get a higher calibration accuracy than by
using the factory calibration.
Note:
1. The 128kHz oscillator is a very low power clock source, and is not designed for high accuracy.
When this clock source is selected, startup times are determined by the SUT fuses:
Table 14-13. Startup Times for the 128kHz Internal Oscillator
Power Conditions Startup Time from Power-down Additional Delay from Reset SUT[1:0]
and Power-save
BOD enabled 6 CK 19CK(1) 00
Fast rising power 6 CK 19CK + 4ms 01
Slowly rising power 6 CK 19CK + 65ms 10
Reserved 11
Note:
1. If the RSTDISBL fuse is programmed, this startup time will be increased to
19CK + 4ms to ensure programming mode can be entered.
Frequency CKSEL[3:0]
0 - 20MHz 0000
PB7 XTAL2
EXTERNAL
CLOCK XTAL1
SIGNAL
GND
When this clock source is selected, start-up times are determined by the SUT Fuses:
Table 14-15. Start-Up Times for the External Clock Selection - SUT
Power Conditions Start-Up Time from Power-down Additional Delay from Reset SUT[1:0]
and Power-save (VCC = 5.0V)
BOD enabled 6 CK 19CK 00
Fast rising power 6 CK 19CK + 4.1ms 01
Slowly rising power 6 CK 19CK + 65ms 10
Reserved 11
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. If changes of more than 2% is required, ensure that the MCU is
kept in Reset during the changes.
The System Clock Prescaler can be used to implement run-time changes of the internal clock frequency
while still ensuring stable operation.
Name: OSCCAL
Offset: 0x66
Reset: Device Specific Calibration Value
Property: -
Name: CLKPR
Offset: 0x61
Reset: Refer to the bit description
Property: -
Bit 7 6 5 4 3 2 1 0
CLKPCE CLKPS [3:0]
Access R/W R/W R/W R/W R/W
Reset 0 x x x x
Idle Yes Yes Yes Yes Yes(2) Yes Yes Yes Yes Yes Yes Yes
ADC Noise Yes Yes Yes Yes(2) Yes(3) Yes Yes(2) Yes Yes Yes
Reduction
Extended Standby Yes(2) Yes Yes(2) Yes(3) Yes Yes Yes Yes
Note:
1. Only recommended with external crystal or resonator selected as clock source.
2. If Timer/Counter2 is running in asynchronous mode.
3. For INT1 and INT0, only level interrupt.
4. Start frame detection, only.
To enter any of the six sleep modes, the Sleep Enable bit in the Sleep Mode Control Register (SMCR.SE)
must be written to '1' and a SLEEP instruction must be executed. Sleep Mode Select bits
(SMCR.SM[2:0]) select which sleep mode (Idle, ADC Noise Reduction, Power-down, Power-save,
Standby, or Extended Standby) will be activated by the SLEEP instruction.
Note: The block diagram in the section System Clock and Clock Options provides an overview over the
different clock systems in the device, and their distribution. This figure is helpful in selecting an
appropriate sleep mode.
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.
Related Links
System Clock and Clock Options
The Sleep Mode Control Register contains control bits for power management.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: SMCR
Offset: 0x53
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x33
Bit 7 6 5 4 3 2 1 0
SM[2:0] SE
Access R/W R/W R/W R/W
Reset 0 0 0 0
Note:
1. Standby mode is only recommended for use with external crystals or resonators.
Bit 7 6 5 4 3 2 1 0
BODS BODSE PUD IVSEL IVCE
Access R/W R/W R/W R/W R/W
Reset 0 0 0 0 0
Move_interrupts:
; Get MCUCR
in r16, MCUCR
mov r17, r16
; Enable change of Interrupt Vectors
ori r16, (1<<IVCE)
out MCUCR, r16
; Move interrupts to Boot Flash section
ori r17, (1<<IVSEL)
out MCUCR, r17
ret
C Code Example
void Move_interrupts(void)
{
uchar temp;
/* GET MCUCR*/
temp = MCUCR;
/* Enable change of Interrupt Vectors */
MCUCR = temp|(1<<IVCE);
/* Move interrupts to Boot Flash section */
MCUCR = temp|(1<<IVSEL);
}
Name: PRR
Offset: 0x64
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
PRTWI PRTIM2 PRTIM0 PRTIM1 PRSPI PRUSART PRADC
Access R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0
VRST
RESET
tTOUT
TIME-OUT
INTERNAL
RESET
VRST
RESET
tTOUT
TIME-OUT
INTERNAL
RESET
Related Links
Fuse Bits
VCC VBOT+
VBOT-
RESET
TIME-OUT tTOUT
INTERNALRESET
Related Links
Fuse Bits
CK
Related Links
Watchdog Timer
16.8.1 Overview
The device 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 Watchdog Timer
Reset (WDR) 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.
Figure 16-7. Watchdog Timer
128kHz
OSCILLATOR
OSC/1024K
OSC/128K
OSC/256K
OSC/512K
OSC/16K
OSC/32K
OSC/64K
OSC/2K
OSC/4K
OSC/8K
WDP0
WDP1
WATCHDOG WDP2
RESET WDP3
WDE
MCU RESET
WDIF
INTERRUPT
WDIE
The following examples show a function for turning off the Watchdog Timer. The
examples assume that interrupts are controlled (e.g. by disabling interrupts globally) so
that no interrupts will occur during the execution of these functions.
Assembly Code Example
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 '1' 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
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;
The following code examples shows how to change the time-out value of the Watchdog
Timer.
Assembly Code Example
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
void WDT_Prescaler_Change(void)
{
__disable_interrupt();
__watchdog_reset();
/* Start timed sequence */
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: The Watchdog Timer should be reset before any change of the WDTCSR.WDP
bits, since a change in the WDTCSR.WDP bits can result in a time-out when switching to
a shorter time-out period.
Related Links
About Code Examples
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 offset
addresses.
Bit 7 6 5 4 3 2 1 0
WDRT BORF EXTRF PORF
Access R/W R/W R/W R/W
Reset x x x 0
Name: WDTCSR
Offset: 0x60 [ID-000004d0]
Reset: 0x00 / 0x08
Property: -
Bit 7 6 5 4 3 2 1 0
WDIF WDIE WDP [3] WDCE WDE WDP [2:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 x 0 0 0
Note:
1. WDTON Fuse set to '0' means programmed and '1' means unprogrammed.
17. Interrupts
This section describes the specifics of the interrupt handling of the device. For a general explanation of
the AVR interrupt handling, refer to the description of Reset and Interrupt Handling.
The interrupt vectors in ATmega48PB/88PB/168PB are generally the same, with the following differences:
• Each Interrupt Vector occupies two instruction words ATmega168PB ; and one instruction word in
ATmega48PB and ATmega88PB.
• ATmega48PB does not have a separate Boot Loader Section. In ATmega88PB and ATmega168PB
the Reset Vector is affected by the BOOTRST fuse, and the Interrupt Vector start address is
affected by the IVSEL bit in MCUCR
Related Links
Reset and Interrupt Handling
The most typical and general program setup for the Reset and Interrupt Vector Addresses in
ATmega48PB is:
Note:
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 chapter.
2. When the IVSEL bit in MCUCR (MCUCR.IVSEL) 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.
The following table shows reset and Interrupt Vectors placement for the various combinations of
BOOTRST and MCUCR.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 17-3. Reset and Interrupt Vectors Placement in ATmega88PB
Note: The Boot Reset Address is shown in Table. Boot Size Configuration, ATmega88PB in
ATmega88PB Boot Loader Parameters. 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
ATmega88PB is:
When the BOOTRST Fuse is unprogrammed, the Boot section size set to 2Kbytes and the IVSEL bit in
the MCUCR Register (MCUCR.IVSEL) is set before any interrupts are enabled, the most typical and
general program setup for the Reset and Interrupt Vector Addresses in ATmega88PB is:
When the BOOTRST Fuse is programmed, the Boot section size set to 2Kbytes and the IVSEL bit in the
MCUCR Register (MCUCR.IVSEL) is set before any interrupts are enabled, the most typical and general
program setup for the Reset and Interrupt Vector Addresses in ATmega88PB is:
Related Links
Boot Loader Support – Read-While-Write Self-Programming
ATmega88PB Boot Loader Parameters
Note:
1. When the BOOTRST Fuse is programmed, the device will jump to the Boot Loader address at
reset, please refer to Boot Loader Support – Read-While-Write Self-Programming chapter.
2. When the IVSEL bit in MCUCR (MCUCR.IVSEL) 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.
The following table 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 17-5. Reset and Interrupt Vectors Placement in ATmega168PB
Note: The Boot Reset Address is shown in Table. Boot Size Configuration, ATmega168PB in
ATmega168PB Boot Loader Parameters. 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
ATmega168PB is:
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 ATmega168PB is:
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 ATmega168PB is:
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 ATmega168PB is:
Related Links
Boot Loader Support – Read-While-Write Self-Programming
ATmega168PB Boot Loader Parameters
Name: MCUCR
Offset: 0x55
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x35
Bit 7 6 5 4 3 2 1 0
BODS BODSE PUD IVSEL IVCE
Access R/W R/W R/W R/W R/W
Reset 0 0 0 0 0
Move_interrupts:
; Get MCUCR
in r16, MCUCR
mov r17, r16
; Enable change of Interrupt Vectors
ori r16, (1<<IVCE)
out MCUCR, r16
; Move interrupts to Boot Flash section
ori r17, (1<<IVSEL)
out MCUCR, r17
ret
C Code Example
void Move_interrupts(void)
{
uchar temp;
/* GET MCUCR*/
temp = MCUCR;
/* Enable change of Interrupt Vectors */
MCUCR = temp|(1<<IVCE);
/* Move interrupts to Boot Flash section */
MCUCR = temp|(1<<IVSEL);
}
clk
PCINT[i] pin
pin_lat
pin_sync
pcint_in[i]
pcint_syn
pcint_set/flag
PCIFn
Related Links
System Control and Reset
The External Interrupt Control Register A contains control bits for interrupt sense control.
Name: EICRA
Offset: 0x69
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
ISC1 [1:0] ISC0 [1:0]
Access R/W R/W R/W R/W
Reset 0 0 0 0
Value Description
00 The low level of INT1 generates an interrupt request.
01 Any logical change on INT1 generates an interrupt request.
10 The falling edge of INT1 generates an interrupt request.
11 The rising edge of INT1 generates an interrupt request.
Value Description
00 The low level of INT0 generates an interrupt request.
01 Any logical change on INT0 generates an interrupt request.
10 The falling edge of INT0 generates an interrupt request.
11 The rising edge of INT0 generates an interrupt request.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: EIMSK
Offset: 0x3D
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x1D
Bit 7 6 5 4 3 2 1 0
INT1 INT0
Access R/W R/W
Reset 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: EIFR
Offset: 0x3C
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x1C
Bit 7 6 5 4 3 2 1 0
INTF1 INTF0
Access R/W R/W
Reset 0 0
Name: PCICR
Offset: 0x68
Reset: 0x00
Property: -
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PCIFR
Offset: 0x3B
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x1B
Bit 7 6 5 4 3 2 1 0
PCIF2 PCIF1 PCIF0
Access R/W R/W R/W
Reset 0 0 0
Name: PCMSK2
Offset: 0x6D
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
PCINT23 PCINT22 PCINT21 PCINT20 PCINT19 PCINT18 PCINT17 PCINT16
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: PCMSK1
Offset: 0x6C
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
PCINT14 PCINT13 PCINT12 PCINT11 PCINT10 PCINT9 PCINT8
Access R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
PCINT 7 PCINT 6 PCINT 5 PCINT 4 PCINT 3 PCINT 2 PCINT 1 PCINT 0
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
19. I/O-Ports
19.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. The pin driver is strong
enough to drive LED displays directly. 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 the following figure.
Figure 19-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.
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 '1'
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 next section. 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 section in this chapter. Refer to the individual module
sections for a full description of the alternate functions.
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.
PUD
Q D
DDxn
Q CLR
WDx
RESET
RDx
DATA BUS
1
Pxn Q D
PORTxn 0
Q CLR
RESET
WPx
WRx
SLEEP RRx
SYNCHRONIZER
RPx
D Q D Q
PINxn
L Q Q
clk I/O
SYSTEM CLK
SYNC LATCH
PINxn
t pd, max
t pd, min
Consider the clock period starting shortly after the first falling edge of the system clock. The latch is
closed when the clock is low, and goes transparent when the clock is high, as indicated by the shaded
SYSTEM CLK
r16 0xFF
SYNC LATCH
PINxn
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.
...
; 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
...
Note: 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.
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*/
__no_operation();
/* Read port pins */
PUOExn
PUOVxn
1
0
PUD
DDOExn
DDOVxn
1
0 Q D
DDxn
Q CLR
WDx
PVOExn RESET
RDx
PVOVxn
DATA BUS
1 1
Pxn
0 Q D 0
PORTxn
Q CLR
DIEOExn
WPx
DIEOVxn RESET
1 WRx
RRx
0 SLEEP
SYNCHRONIZER
RPx
SET
D Q D Q
PINxn
L CLR Q CLR Q
clk I/O
DIxn
AIOxn
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.
Note:
1. INTRC means that one of the internal RC Oscillators are selected (by the CKSEL fuses), EXTCK
means that external clock is selected (by the CKSEL fuses).
Table 19-5. Overriding Signals for Alternate Functions in PB3...PB0
AIO – – – –
PC0 MISO1
ADC0 (ADC Input Channel 0)
– PC1 can also be used as ADC input Channel 1. The ADC input channel 1 uses analog power.
– SCK1: Master Clock output, Slave Clock input pin for SPI1 channel. When the SPI1 is
enabled as a Slave, this pin is configured as an input regardless of the setting of DDB5. When
the SPI1 is enabled as a Master, the data direction of this pin is controlled by DDC1. When
the pin is forced by the SPI1 to be an input, the pull-up can still be controlled by the PORTC1
bit.
– PCINT9: Pin Change Interrupt source 9. The PC1 pin can serve as an external interrupt
source.
• ADC0/MISO1/PCINT8 – Port C, Bit 0
– PC0 can also be used as ADC input Channel 0. The ADC input channel 0 uses analog power.
– MISO1: Master1 Data input, Slave Data output pin for SPI1 channel. When the SPI1 is
enabled as a Master, this pin is configured as an input regardless of the setting of DDC0.
When the SPI1 is enabled as a Slave, the data direction of this pin is controlled by DDC0.
When the pin is forced by the SPI1 to be an input, the pull-up can still be controlled by the
PORTC0 bit.
– PCINT8: Pin Change Interrupt source 8. The PC0 pin can serve as an external interrupt
source.
The tables below relate the alternate functions of Port C to the overriding signals shown in Figure 19-5.
Table 19-7. Overriding Signals for Alternate Functions in PC6...PC4(1)
Note: 1. When enabled, the 2-wire Serial Interface enables slew-rate controls on the output pins PC4
and PC5. This is not shown in the figure. In addition, spike filters are connected between the AIO outputs
shown in the port figure and the digital logic of the TWI module.
Table 19-8. Overriding Signals for Alternate Functions in PC3...PC0
PE1
PE0 ACO (AC Output Channel)
Name: MCUCR
Offset: 0x55
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x35
Bit 7 6 5 4 3 2 1 0
BODS BODSE PUD IVSEL IVCE
Access R/W R/W R/W R/W R/W
Reset 0 0 0 0 0
Move_interrupts:
; Get MCUCR
in r16, MCUCR
mov r17, r16
; Enable change of Interrupt Vectors
ori r16, (1<<IVCE)
out MCUCR, r16
; Move interrupts to Boot Flash section
ori r17, (1<<IVSEL)
out MCUCR, r17
ret
C Code Example
void Move_interrupts(void)
{
uchar temp;
/* GET MCUCR*/
temp = MCUCR;
/* Enable change of Interrupt Vectors */
MCUCR = temp|(1<<IVCE);
/* Move interrupts to Boot Flash section */
MCUCR = temp|(1<<IVSEL);
}
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PORTB
Offset: 0x25
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x05
Bit 7 6 5 4 3 2 1 0
PORTB7 PORTB6 PORTB5 PORTB4 PORTB3 PORTB2 PORTB1 PORTB0
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Bit 7 6 5 4 3 2 1 0
DDRB7 DDRB6 DDRB5 DDRB4 DDRB3 DDRB2 DDRB1 DDRB0
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PINB
Offset: 0x23
Reset: N/A
Property: When addressing as I/O Register: address offset is 0x03
Bit 7 6 5 4 3 2 1 0
PINB7 PINB6 PINB5 PINB4 PINB3 PINB2 PINB1 PINB0
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset x x x x x x x x
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PORTC
Offset: 0x28
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x08
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: DDRC
Offset: 0x27
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x07
Bit 7 6 5 4 3 2 1 0
DDRC6 DDRC5 DDRC4 DDRC3 DDRC2 DDRC1 DDRC0
Access R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PINC
Offset: 0x26
Reset: N/A
Property: When addressing as I/O Register: address offset is 0x06
Bit 7 6 5 4 3 2 1 0
PINC6 PINC5 PINC4 PINC3 PINC2 PINC1 PINC0
Access R/W R/W R/W R/W R/W R/W R/W
Reset x x x x x x x
Name: PORTD
Offset: 0x2B
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x0B
Bit 7 6 5 4 3 2 1 0
PORTD7 PORTD6 PORTD5 PORTD4 PORTD3 PORTD2 PORTD1 PORTD0
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: DDRD
Offset: 0x2A
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x0A
Bit 7 6 5 4 3 2 1 0
DDRD7 DDRD6 DDRD5 DDRD4 DDRD3 DDRD2 DDRD1 DDRD0
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PIND
Offset: 0x29
Reset: N/A
Property: When addressing as I/O Register: address offset is 0x09
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PORTE
Offset: 0x2E
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x0E
Bit 7 6 5 4 3 2 1 0
PORTE3 PORTE2 PORTE1 PORTE0
Access R/W R/W R/W R/W
Reset 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: DDRE
Offset: 0x2D
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x0D
Bit 7 6 5 4 3 2 1 0
DDRE3 DDRE2 DDRE1 DDRE0
Access R/W R/W R/W R/W
Reset 0 0 0 0
Name: PINE
Offset: 0x2C
Reset: N/A
Property: When addressing as I/O Register: address offset is 0x0C
Bit 7 6 5 4 3 2 1 0
PINE3 PINE2 PINE1 PINE0
Access R/W R/W R/W R/W
Reset x x x x
20.1 Features
• 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)
20.2 Overview
Timer/Counter0 (TC0) is a general purpose 8-bit Timer/Counter module, with two independent Output
Compare Units, and PWM support. It allows accurate program execution timing (event management) and
wave generation.
A simplified block diagram of the 8-bit Timer/Counter is shown below. 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. For the actual placement of I/O pins, refer to the pinout diagram.
The TC0 is enabled by writing the PRTIM0 bit in ”Minimizing Power Consumption” to '0'.
The TC0 is enabled when the PRTIM0 bit in the Power Reduction Register (PRR.PRTIM0) is written to
'1'.
Edge
Tn
Detector
TOP BOTTOM
( From Prescaler )
Timer/Counter
TCNTn
= =0
OCnA
(Int.Req.)
Waveform
= Generation
OCnA
OCRnA
Fixed
OCnB
TOP
(Int.Req.)
Value
DATA BUS
Waveform
= Generation
OCnB
OCRnB
TCCRnA TCCRnB
Related Links
Minimizing Power Consumption
Register Description
Pin Configurations
20.2.1 Definitions
Many register and bit references in this section are written in general form:
• n=1 represents the Timer/Counter number
• x=A,B represents the Output Compare Unit A or B
However, when using the register or bit definitions in a program, the precise form must be used, i.e.,
TCNT1 for accessing Timer/Counter1 counter value.
The following definitions are used throughout the section:
Constant Description
BOTTOM The counter reaches the BOTTOM when it becomes zero (0x00 for 8-bit counters, or 0x0000
for 16-bit counters).
MAX The counter reaches its Maximum when it becomes 0xFF (decimal 255, for 8-bit counters) or
0xFFFF (decimal 65535, for 16-bit counters).
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 MAX or the value stored in
the OCR1A Register. The assignment is dependent on the mode of operation.
20.2.2 Registers
The Timer/Counter 0 register (TCNT0) and Output Compare TC0x registers (OCR0x) are 8-bit registers.
Interrupt request (abbreviated to Int.Req. in the block diagram) signals are all visible in the Timer Interrupt
Flag Register 0 (TIFR0). All interrupts are individually masked with the Timer Interrupt Mask Register 0
(TIMSK0). TIFR0 and TIMSK0 are not shown in the figure.
The TC 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 is used by the Timer/Counter to increment
(or decrement) its value. The TC 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
Output Compare Unit 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.
Clock Select
count Edge
Tn
clear clkTn Detector
TCNTn Control Logic
direction
( From Prescaler )
bottom top
Depending of the mode of operation used, the counter is cleared, incremented, or decremented at each
timer clock (clkT0). clkT0 can be generated from an external or internal clock source, selected by the Clock
Select bits (CS0[2:0]). When no clock source is selected (CS0=0x0) the timer is stopped. However, the
TCNT0 value can be accessed by the CPU, regardless of whether clkT0 is present or not. A CPU write
overrides (has priority over) all counter clear or count operations.
The counting sequence is determined by the setting of the WGM01 and WGM00 bits located in the Timer/
Counter Control Register (TCCR0A) and the WGM02 bit located in the Timer/Counter Control Register B
(TCCR0B). There are close connections between how the counter behaves (counts) and how waveforms
are generated on the Output Compare outputs OC0A and OC0B. For more details about advanced
counting sequences and waveform generation, see Modes of Operation.
The Timer/Counter Overflow Flag (TOV0) is set according to the mode of operation selected by the
WGM0[2:0] bits. TOV0 can be used for generating a CPU interrupt.
OCRnx TCNTn
=(8-bit Comparator )
OCFnx (Int.Req.)
top
bottom
Waveform Generator OCnx
FOCn
WGMn[1:0] COMnx[1:0]
Note: The “n” in the register and bit names indicates the device number (n = 0 for Timer/Counter 0), and
the “x” indicates Output Compare unit (A/B).
The OCR0x Registers are double buffered when using any of the Pulse Width Modulation (PWM) modes.
When double buffering is enabled, the CPU has access to the OCR0x Buffer Register. 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 double buffering is disabled for the normal and Clear Timer on Compare (CTC) modes of operation,
and the CPU will access the OCR0x directly.
Related Links
Modes of Operation
COMnx[1]
COMnx[0] Waveform
D Q
FOCnx Generator
1
OCnx
OCnx Pin
0
D Q
DATA BUS
PORT
D Q
DDR
clk I/O
Note: The “n” in the register and bit names indicates the device number (n = 0 for Timer/Counter 0), and
the “x” indicates Output Compare unit (A/B).
An interrupt can be generated each time the counter value reaches the TOP value by setting the OCFnA
Flag. If the interrupt is enabled, the interrupt handler routine can be used for updating the TOP value.
Note: Changing TOP to a value close to BOTTOM while the counter is running must be done with care,
since the CTC mode does not provide double buffering. If the new value written to OCRnA is lower than
the current value of TCNTn, the counter will miss the compare match. The counter will then count to its
maximum value (0xFF for a 8-bit counter, 0xFFFF for a 16-bit counter) and wrap around starting at 0x00
before the compare match will occur.
For generating a waveform output in CTC mode, the OCnA output can be set to toggle its logical level on
each compare match by writing the two least significant Compare Output mode bits in the Timer/Counter
Control Register A Control to toggle mode (TCCRnA.COMnA[1:0]=0x1). The OCnA value will only 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 fOCn = fclk_I/O/2 when OCRnA is written to 0x00. The waveform frequency
is defined by the following equation:
�clk_I/O
�OCnx =
2 ⋅ � ⋅ 1 + OCRnx
N represents the prescaler factor (1, 8, 64, 256, or 1024).
As for the Normal mode of operation, the Timer/Counter Overflow Flag TOVn is set in the same clock
cycle that the counter wraps from MAX to 0x00.
TCNTn
Period 1 2 3 4 5 6 7
The Timer/Counter Overflow Flag (TOV0) is set each time the counter reaches TOP. If the interrupt is
enabled, the interrupt handler routine can be used for updating the compare value.
In Fast PWM mode, the compare unit allows generation of PWM waveforms on the OC0x pins. Writing
the TCCR0A.COM0x[1:0] bits to 0x2 will produce a non-inverted PWM; TCCR0A.COM0x[1:0]=0x3 will
produce an inverted PWM output. Writing the TCCR0A.COM0A[1:0] bits to 0x1 allows the OC0A pin to
toggle on Compare Matches if the TCCRnB.WGMn2 bit is set. This option is not available for the OC0B
pin. 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:
�clk_I/O
�OCnxPWM =
� ⋅ 256
N represents the prescale divider (1, 8, 64, 256, or 1024).
The extreme values for the OCR0A register represents special cases for PWM waveform output in the
Fast PWM mode: If OCR0A is written equal to BOTTOM, the output will be a narrow spike for each MAX
+1 timer clock cycle. Writing OCR0A=MAX will result in a constantly high or low output (depending on the
polarity of the output set by the COM0A[1:0] bits.)
OCRnx Update
TCNTn
OCnx (COMnx[1:0] = 2)
OCnx (COMnx[1: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.
clkI/O
clkTn
(clkI/O /1)
TOVn
Note: The “n” in the register and bit names indicates the device number (n = 0 for Timer/Counter 0), and
the “x” indicates Output Compare unit (A/B).
The next figure shows the same timing data, but with the prescaler enabled.
Figure 20-9. Timer/Counter Timing Diagram, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
TOVn
Note: The “n” in the register and bit names indicates the device number (n = 0 for Timer/Counter 0), and
the “x” indicates Output Compare unit (A/B).
The next figure shows the setting of OCF0B in all modes and OCF0A in all modes (except CTC mode
and PWM mode where OCR0A is TOP).
Figure 20-10. Timer/Counter Timing Diagram, Setting of OCF0x, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
OCFnx
Note: The “n” in the register and bit names indicates the device number (n = 0 for Timer/Counter 0), and
the “x” indicates Output Compare unit (A/B).
clkI/O
clkTn
(clkI/O /8)
TCNTn
TOP - 1 TOP BOTTOM BOTTOM + 1
(CTC)
OCRnx TOP
OCFnx
Note: The “n” in the register and bit names indicates the device number (n = 0 for Timer/Counter 0), and
the “x” indicates Output Compare unit (A/B).
Name: TCCR0A
Offset: 0x44
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x24
Bit 7 6 5 4 3 2 1 0
COM0A [1:0] COM0B [1:0] WGM0 1 WGM0 0
Access R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0
The table below shows the COM0A[1:0] bit functionality when the WGM0[1:0] bits are set to fast PWM
mode.
Table 20-4. Compare Output Mode, Fast PWM(1)
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 BOTTOM. Refer to Fast PWM Mode for details.
The table below shows the COM0A[1:0] bit functionality when the WGM0[2:0] bits are set to phase
correct PWM mode.
Table 20-5. Compare Output Mode, Phase Correct PWM Mode(1)
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. Refer to Phase Correct PWM Mode for
details.
The table below shows the COM0B[1:0] bit functionality when the WGM0[2:0] bits are set to fast PWM
mode.
Table 20-7. Compare Output Mode, Fast PWM(1)
Note:
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. Refer to Fast PWM Mode for details.
The table below shows the COM0B[1:0] bit functionality when the WGM0[2:0] bits are set to phase
correct PWM mode.
Table 20-8. Compare Output Mode, Phase Correct PWM Mode(1)
Note:
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. Refer to Phase Correct PWM Mode for
details.
Note:
1. MAX = 0xFF
2. BOTTOM = 0x00
Name: TCCR0B
Offset: 0x45
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x25
Bit 7 6 5 4 3 2 1 0
FOC0A FOC0B WGM0 [2] CS0[2:0]
Access R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0
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.
Name: TIMSK0
Offset: 0x6E
Reset: 0x00
Property: -
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: GTCCR
Offset: 0x43
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x23
Bit 7 6 5 4 3 2 1 0
TSM PSRASY PSRSYNC
Access R/W R/W R/W
Reset 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: TCNT0
Offset: 0x46
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x26
Bit 7 6 5 4 3 2 1 0
TCNT0[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: OCR0A
Offset: 0x47
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x27
Bit 7 6 5 4 3 2 1 0
OCR0A[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: OCR0B
Offset: 0x48
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x28
Bit 7 6 5 4 3 2 1 0
OCR0B[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: TIFR0
Offset: 0x35
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x15
Bit 7 6 5 4 3 2 1 0
OCF0B OCF0A TOV0
Access R/W R/W R/W
Reset 0 0 0
21.1 Features
• True 16-bit Design (i.e., allows 16-bit PWM)
• Two independent Output Compare Units
• Double Buffered Output Compare Registers
• One Input Capture Unit
• Input Capture Noise Canceler
• Clear Timer on Compare Match (Auto Reload)
• Glitch-free, Phase Correct Pulse Width Modulator (PWM)
• Variable PWM Period
• Frequency Generator
• External Event Counter
• Independent interrupt Sources (TOV, OCFA, OCFB, and ICF)
21.2 Overview
The 16-bit Timer/Counter unit allows accurate program execution timing (event management), wave
generation, and signal timing measurement.
A block diagram of the 16-bit Timer/Counter is shown below. 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
Register Description. For the actual placement of I/O pins, refer to the Pin Configurations description.
21.2.1 Definitions
Many register and bit references in this section are written in general form:
• n=1 represents the Timer/Counter number
• x=A,B represents the Output Compare Unit A or B
However, when using the register or bit definitions in a program, the precise form must be used, i.e.,
TCNT1 for accessing Timer/Counter1 counter value.
The following definitions are used throughout the section:
Table 21-1. Definitions
Constant Description
BOTTOM The counter reaches the BOTTOM when it becomes zero (0x00 for 8-bit counters, or 0x0000
for 16-bit counters).
MAX The counter reaches its Maximum when it becomes 0xFF (decimal 255, for 8-bit counters) or
0xFFFF (decimal 65535, for 16-bit counters).
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 MAX or the value stored in
the OCR1A Register. The assignment is dependent on the mode of operation.
...
; Set TCNT1 to 0x01FF
ldi r17,0x01
ldi r16,0xFF
out TCNT1H,r17
out TCNT1L,r16
; Read TCNT1 into r17:r16
in r16,TCNT1L
in r17,TCNT1H
...
The assembly code example returns the TCNT1 value in the r17:r16 register pair.
C Code Example(1)
unsigned int i;
...
/* Set TCNT1 to 0x01FF */
TCNT1 = 0x1FF;
/* Read TCNT1 into i */
i = TCNT1;
...
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”.
Atomic Read
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.
The following code examples show how to perform an atomic read of the TCNT1 Register contents. The
OCR1A/B or ICR1 Registers can be ready by using the same principle.
TIM16_ReadTCNT1:
; Save global interrupt flag
in r18,SREG
; Disable interrupts
cli
; Read TCNT1 into r17:r16
in r16,TCNT1L
in r17,TCNT1H
; Restore global interrupt flag
out SREG,r18
ret
The assembly code example returns the TCNT1 value in the r17:r16 register pair.
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”.
Atomic Write
The following code examples show how to do an atomic write of the TCNT1 Register contents. Writing
any of the OCR1A/B or ICR1 Registers can be done by using the same principle.
TIM16_WriteTCNT1:
; Save global interrupt flag
in r18,SREG
; Disable interrupts
cli
; Set TCNT1 to r17:r16
out TCNT1H,r17
out TCNT1L,r16
; Restore global interrupt flag
out SREG,r18
ret
The assembly code example requires that the r17:r16 register pair contains the value to
be written to TCNT1.
C Code Example(1)
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
TEMP (8-bit)
Clock Select
Count Edge
Tn
TCNTnH (8-bit) TCNTnL (8-bit) Clear clkTn Detector
Control Logic
Direction
TCNTn (16-bit Counter)
( From Prescaler )
TOP BOTTOM
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
Table 21-2. Signal description (internal signals)
The 16-bit counter is mapped into two 8-bit I/O memory locations: Counter High (TCNT1H) containing the
upper eight bits of the counter, and Counter Low (TCNT1L) containing the lower eight bits. The TCNT1H
Register can only be accessed indirectly by the CPU. When the CPU does an access to the TCNT1H I/O
location, the CPU accesses the high byte temporary register (TEMP). The temporary register is updated
TEMP (8-bit)
Analog
Comparator Noise Edge
ICFn (Int.Req.)
Canceler Detector
ICPn
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
When a change of the logic level (an event) occurs on the Input Capture pin (ICP1), or alternatively on
the Analog Comparator output (ACO), and this change confirms to the setting of the edge detector, a
capture will be triggered: the 16-bit value of the counter (TCNT1) is written to the Input Capture Register
(ICR1). The Input Capture Flag (ICF) is set at the same system clock cycle as the TCNT1 value is copied
into the ICR1 Register. If enabled (TIMSK1.ICIE=1), the Input Capture Flag generates an Input Capture
interrupt. The ICF1 Flag is automatically cleared when the interrupt is executed. Alternatively the ICF Flag
can be cleared by software by writing '1' to its I/O bit location.
Reading the 16-bit value in the Input Capture Register (ICR1) is done by first reading the low byte
(ICR1L) and then the high byte (ICR1H). When the low byte is read form ICR1L, the high byte is copied
into the high byte temporary register (TEMP). When the CPU reads the ICR1H I/O location it will access
the TEMP Register.
The ICR1 Register can only be written when using a Waveform Generation mode that utilizes the ICR1
Register for defining the counter’s TOP value. In these cases the Waveform Generation mode bits
(WGM1[3:0]) must be set before the TOP value can be written to the ICR1 Register. When writing the
ICR1 Register, the high byte must be written to the ICR1H I/O location before the low byte is written to
ICR1L.
See also Accessing 16-bit Timer/Counter Registers.
TEMP (8-bit)
OCRnxH Buf. (8-bit) OCRnxL Buf. (8-bit) TCNTnH (8-bit) TCNTnL (8-bit)
= (16-bit Comparator )
OCFnx (Int.Req.)
TOP
Waveform Generator OCnx
BOTTOM
WGMn[3:0] COMnx[1:0]
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
The OCR1x 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 OCR1x 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.
When double buffering is enabled, the CPU has access to the OCR1x Buffer Register. When double
buffering is disabled, the CPU will access the OCR1x 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 good practice to read the low byte
first as when accessing other 16-bit registers. Writing the OCR1x Registers must be done via the TEMP
Register since the compare of all 16 bits is done continuously. The high byte (OCR1xH) 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 (OCR1xL) is written to the lower eight bits, the high byte will be
copied into the upper 8-bits of either the OCR1x buffer or OCR1x Compare Register in the same system
clock cycle.
COMnx[1]
COMnx[0] Waveform
D Q
FOCnx Generator
1
OCnx
OCnx Pin
0
D Q
DATA BUS
PORT
D Q
DDR
clk I/O
Note: The “n” in the register and bit names indicates the device number (n = 0 for Timer/Counter 0), and
the “x” indicates Output Compare unit (A/B).
The general I/O port function is overridden by the Output Compare (OC1x) from the Waveform Generator
if either of the COM1x[1:0] bits are set. However, the OC1x pin direction (input or output) is still controlled
by the Data Direction Register (DDR) for the port pin. In the Data Direction Register, the bit for the OC1x
pin (DDR.OC1x) must be set as output before the OC1x value is visible on the pin. The port override
function is independent of the Waveform Generation mode.
The design of the Output Compare pin logic allows initialization of the OC1x register state before the
output is enabled. Some TCCR1A.COM1x[1:0] bit settings are reserved for certain modes of operation.
The TCCR1A.COM1x[1:0] bits have no effect on the Input Capture unit.
Related Links
Modes of Operation
TCNTn
OCnA
(COMnA[1:0] = 0x1)
(Toggle)
Period 1 2 3 4
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
TCNTn
Period 1 2 3 4 5 6 7 8
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
The Timer/Counter Overflow Flag (TOV1) is set each time the counter reaches TOP. In addition, when
either OCR1A or ICR1 is used for defining the TOP value, the OC1A or ICF1 Flag is set at the same timer
clock cycle TOV1 is set. 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 TCNT1 and the OCR1x. Note that when using fixed TOP
values the unused bits are masked to zero when any of the OCR1x Registers are written.
The procedure for updating ICR1 differs from updating OCR1A when used for defining the TOP value.
The ICR1 Register is not double buffered. This means that if ICR1 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 ICR1 value written is
lower than the current value of TCNT1. As result, 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 OCR1A Register however, is double buffered. This
feature allows the OCR1A I/O location to be written anytime. When the OCR1A I/O location is written the
value written will be put into the OCR1A Buffer Register. The OCR1A Compare Register will then be
updated with the value in the Buffer Register at the next timer clock cycle the TCNT1 matches TOP. The
update is done at the same timer clock cycle as the TCNT1 is cleared and the TOV1 Flag is set.
Using the ICR1 Register for defining TOP works well when using fixed TOP values. By using ICR1, the
OCR1A Register is free to be used for generating a PWM output on OC1A. However, if the base PWM
frequency is actively changed (by changing the TOP value), using the OCR1A as TOP is clearly a better
choice due to its double buffer feature.
TCNTn
Period 1 2 3 4
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
The Timer/Counter Overflow Flag (TOV1) is set each time the counter reaches BOTTOM. When either
OCR1A or ICR1 is used for defining the TOP value, the OC1A or ICF1 Flag is set accordingly at the same
timer clock cycle as the OCR1x 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 TCNT1 and the OCR1x. Note that when using fixed TOP
values, the unused bits are masked to zero when any of the OCR1x registers is written. As illustrated by
the third period in the timing diagram, 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 OCR1x Register. Since the OCR1x update occurs at TOP, the PWM period starts and ends
at TOP. This implies that the length of the falling slope is determined by the previous TOP value, while the
length of the rising slope is determined by the new TOP value. When these two values differ the two
slopes of the period will differ in length. The difference in length gives the unsymmetrical result on the
output.
It is recommended to use the phase and frequency correct mode instead of the phase correct mode when
changing the TOP value while the Timer/Counter is running. When using a static TOP value, there are
practically no differences between the two modes of operation.
In Phase Correct PWM mode, the compare units allow generation of PWM waveforms on the OC1x pins.
Writing COM1x[1:0] bits to 0x2 will produce a non-inverted PWM. An inverted PWM output can be
generated by writing the COM1x[1:0] to 0x3. The actual OC1x value will only be visible on the port pin if
OCRnx/TOP Updateand
TOVn Interrupt Flag Set
(Interrupt on Bottom)
TCNTn
Period 1 2 3 4
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
The Timer/Counter Overflow Flag (TOV1) is set at the same timer clock cycle as the OCR1x Registers
are updated with the double buffer value (at BOTTOM). When either OCR1A or ICR1 is used for defining
the TOP value, the OC1A or ICF1 Flag set when TCNT1 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 TCNT1 and the OCR1x.
As shown in the timing diagram above, the output generated is, in contrast to the phase correct mode,
symmetrical in all periods. Since the OCR1x 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 ICR1 Register for defining TOP works well when using fixed TOP values. By using ICR1, the
OCR1A Register is free to be used for generating a PWM output on OC1A. However, if the base PWM
frequency is actively changed by changing the TOP value, using the OCR1A as TOP is clearly a better
choice due to its double buffer feature.
In phase and frequency correct PWM mode, the compare units allow generation of PWM waveforms on
the OC1x pins. Setting the COM1x[1:0] bits to 0x2 will produce a non-inverted PWM and an inverted
PWM output can be generated by setting the COM1x[1:0] to 0x3 (See description of TCCRA.COM1x).
The actual OC1x value will only be visible on the port pin if the data direction for the port pin is set as
output (DDR_OC1x). The PWM waveform is generated by setting (or clearing) the OC1x Register at the
compare match between OCR1x and TCNT1 when the counter increments, and clearing (or setting) the
OC1x Register at compare match between OCR1x and TCNT1 when the counter decrements. The PWM
frequency for the output when using phase and frequency correct PWM can be calculated by the
following equation:
�clk_I/O
�OCnxPFCPWM =
2 ⋅ � ⋅ TOP
clkI/O
clkTn
(clkI/O /1)
OCFnx
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
The next figure shows the same timing data, but with the prescaler enabled.
Figure 21-10. Timer/Counter Timing Diagram, Setting of OCF1x, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
OCFnx
clkI/O
clkTn
(clkI/O /1)
TCNTn
TOP - 1 TOP BOTTOM BOTTOM + 1
(CTC and FPWM)
TCNTn
TOP - 1 TOP TOP - 1 TOP - 2
(PC and PFC PWM)
TOVn (FPWM)
and ICFn (if used
as TOP)
OCRnx
Old OCRnx Value New OCRnx Value
(Update at TOP)
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
The next figure shows the same timing data, but with the prescaler enabled.
Figure 21-12. Timer/Counter Timing Diagram, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O/8)
TCNTn
TOP - 1 TOP BOTTOM BOTTOM + 1
(CTC and FPWM)
TOVn(FPWM)
and ICF n (if used
as TOP)
OCRnx
Old OCRnx Value New OCRnx Value
(Update at TOP)
Note: The “n” in the register and bit names indicates the device number (n = 1 for Timer/Counter 1), and
the “x” indicates Output Compare unit (A/B).
Name: TCCR1A
Offset: 0x80
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
COM1A[1:0] COM1B[1:0] WGM1[1:0]
Access R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0
Bits 4:5, 6:7 – COM1B, COM1A: Compare Output Mode for Channel
The COM1A[1:0] and COM1B[1:0] control the Output Compare pins (OC1A and OC1B respectively)
behavior. If one or both of the COM1A[1:0] bits are written to one, the OC1A output overrides the normal
port functionality of the I/O pin it is connected to. If one or both of the COM1B[1:0] bit are written to one,
the OC1B 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 OC1A or OC1B pin must be set in order
to enable the output driver.
When the OC1A or OC1B is connected to the pin, the function of the COM1x[1:0] bits is dependent of the
WGM1[3:0] bits setting. The table below shows the COM1x[1:0] bit functionality when the WGM1[3:0] bits
are set to a Normal or a CTC mode (non-PWM).
Table 21-3. Compare Output Mode, non-PWM
The table below shows the COM1x[1:0] bit functionality when the WGM1[3:0] bits are set to the fast PWM
mode.
Table 21-4. Compare Output Mode, Fast PWM
Note:
1. A special case occurs when OCR1A/OCR1B equals TOP and COM1A1/COM1B1 is set. In this
case the compare match is ignored, but the set or clear is done at BOTTOM. Refer to Fast PWM
Mode for details.
The table below shows the COM1x[1:0] bit functionality when the WGM1[3:0] bits are set to the phase
correct or the phase and frequency correct, PWM mode.
Table 21-5. Compare Output Mode, Phase Correct and Phase and Frequency Correct PWM
Note:
1. A special case occurs when OCR1A/OCR1B equals TOP and COM1A1/COM1B1 is set. Refer to
Phase Correct PWM Mode for details.
Note:
1. The CTC1 and PWM1[1:0] bit definition names are obsolete. Use the WGM1[3:0] definitions.
However, the functionality and location of these bits are compatible with previous versions of the
timer.
Name: TCCR1B
Offset: 0x81
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
ICNC1 ICES1 WGM1[3] WGM1[2] CS1[2:0]
Access R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0
Name: TCCR1C
Offset: 0x82
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
FOC1A FOC1B
Access R/W R/W
Reset 0 0
The TCNT1L and TCNT1H register pair represents the 16-bit value, TCNT1.The low byte [7:0] (suffix L) is
accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
Bit 15 14 13 12 11 10 9 8
TCNT1[15:8]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
TCNT1[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
The ICR1L and ICR1H register pair represents the 16-bit value, ICR1.The low byte [7:0] (suffix L) is
accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
Bit 7 6 5 4 3 2 1 0
ICR1[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
The OCR1AL and OCR1AH register pair represents the 16-bit value, OCR1A.The low byte [7:0] (suffix L)
is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
Bit 15 14 13 12 11 10 9 8
OCR1A[15:8]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
OCR1A[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
The OCR1BL and OCR1BH register pair represents the 16-bit value, OCR1B.The low byte [7:0] (suffix L)
is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
Bit 15 14 13 12 11 10 9 8
OCR1B[15:8]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
OCR1B[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: TIMSK1
Offset: 0x6F
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
ICIE1 OCIE1B OCIE1A TOIE1
Access R/W R/W R/W R/W
Reset 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: TIFR1
Offset: 0x36
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x16
Bit 7 6 5 4 3 2 1 0
ICF1 OCF1B OCF1A TOV1
Access R/W R/W R/W R/W
Reset 0 0 0 0
Tn D Q D Q D Q Tn_sync
(To Clock
Select Logic)
LE
clk I/O
CK/8
CK/64
CK/256
CK/1024
PSR10
OFF
Tn Synchronization
CSn0
CSn1
CSn2
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Bit 7 6 5 4 3 2 1 0
TSM PSRASY PSRSYNC
Access R/W R/W R/W
Reset 0 0 0
23.1 Features
• Single Channel Counter
• Clear Timer on Compare Match (Auto Reload)
• Glitch-free, Phase Correct Pulse Width Modulator (PWM)
• Frequency Generator
• 10-bit Clock Prescaler
• Overflow and Compare Match Interrupt Sources (TOV2, OCF2A, and OCF2B)
• Allows Clocking from External 32kHz Watch Crystal Independent of the I/O Clock
23.2 Overview
Timer/Counter2 (TC2) is a general purpose, single channel, 8-bit Timer/Counter module.
A simplified block diagram of the 8-bit Timer/Counter is shown below. 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 following Register Description. For the actual placement of I/O pins, refer to the pinout
diagram.
The TC2 is enabled when the PRTIM2 bit in the Power Reduction Register (PRR.PRTIM2) is written to
'1'.
Edge
Tn
Detector
TOP BOTTOM
( From Prescaler )
Timer/Counter
TCNTn
= =0
OCnA
(Int.Req.)
Waveform
= Generation
OCnA
OCRnA
Fixed
OCnB
TOP
(Int.Req.)
Value
DATA BUS
Waveform
= Generation
OCnB
OCRnB
TCCRnA TCCRnB
Related Links
Pin Configurations
23.2.1 Definitions
Many register and bit references in this section are written in general form:
• n=2 represents the Timer/Counter number
• x=A,B represents the Output Compare Unit A or B
However, when using the register or bit definitions in a program, the precise form must be used, i.e.,
TCNT2 for accessing Timer/Counter2 counter value.
The following definitions are used throughout the section:
Constant Description
BOTTOM The counter reaches the BOTTOM when it becomes zero (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 OCR2A Register. The assignment is dependent on the mode of operation.
23.2.2 Registers
The Timer/Counter (TCNT2) and Output Compare Register (OCR2A and OCR2B) are 8-bit registers.
Interrupt request (shorten as Int.Req.) signals are all visible in the Timer Interrupt Flag Register (TIFR2).
All interrupts are individually masked with the Timer Interrupt Mask Register (TIMSK2). TIFR2 and
TIMSK2 are not shown in the figure.
The Timer/Counter can be clocked internally, via the prescaler, or asynchronously clocked from the
TOSC1/2 pins, as detailed later in this section. The asynchronous operation is controlled by the
Asynchronous Status Register (ASSR). The Clock Select logic block controls which clock source he
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 (clkT2).
The double buffered Output Compare Register (OCR2A and OCR2B) 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 (OC2A and OC2B). See
Output Compare Unit for details. The compare match event will also set the Compare Flag (OCF2A or
OCF2B) which can be used to generate an Output Compare interrupt request.
TOSC1
count
T/C
clear clk Tn
TCNTn Control Logic Prescaler Oscillator
direction
TOSC2
Depending on the mode of operation used, the counter is cleared, incremented, or decremented at each
timer clock (clkT2). clkT2 can be generated from an external or internal clock source, selected by the Clock
Select bits (CS2[2:0]). When no clock source is selected (CS2[2:0]=0x0) the timer is stopped. However,
the TCNT2 value can be accessed by the CPU, regardless of whether clkT2 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 WGM21 and WGM20 bits located in the Timer/
Counter Control Register (TCCR2A) and the WGM22 bit located in the Timer/Counter Control Register B
(TCCR2B). There are close connections between how the counter behaves (counts) and how waveforms
are generated on the Output Compare outputs OC2A and OC2B. For more details about advanced
counting sequences and waveform generation, see "Modes of Operation".
The Timer/Counter Overflow Flag (TOV2) is set according to the mode of operation selected by the
TCC2B.WGM2[2:0] bits. TOV2 can be used for generating a CPU interrupt.
OCRnx TCNTn
=(8-bit Comparator )
OCFnx (Int.Req.)
top
bottom
Waveform Generator OCnx
FOCn
WGMn[1:0] COMnx[1:0]
The OCR2x Register is 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 OCR2x 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 OCR2x Register access may seem complex, but this is not case. When the double buffering is
enabled, the CPU has access to the OCR2x Buffer Register, and if double buffering is disabled the CPU
will access the OCR2x directly.
COMnx[1]
COMnx[0] Waveform
D Q
FOCnx Generator
1
OCnx
OCnx Pin
0
D Q
DATA BUS
PORT
D Q
DDR
clk I/O
The general I/O port function is overridden by the Output Compare (OC2x) from the Waveform Generator
if either of the COM2x1:0 bits are set. However, the OC2x 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 OC2x pin
(DDR_OC2x) must be set as output before the OC2x value is visible on the pin. The port override
function is independent of the Waveform Generation mode.
The design of the Output Compare pin logic allows initialization of the OC2x state before the output is
enabled. Note that some COM2x[1:0] bit settings are reserved for certain modes of operation. See
Register Description.
An interrupt can be generated each time the counter value reaches the TOP value by using the OCF2A
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 OCR2A is lower than the current value of TCNT2, the counter will miss the
compare match. The counter will then have to count to its maximum value (0xFF) and wrap around
starting at 0x00 before the compare match can occur.
For generating a waveform output in CTC mode, the OC2A output can be set to toggle its logical level on
each compare match by setting the Compare Output mode bits to toggle mode (COM2A[1:0] = 1). The
OC2A 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 fOC2A = fclk_I/O/2 when OCR2A is set to zero
(0x00). The waveform frequency is defined by the following equation:
�clk_I/O
�OCnx =
2 ⋅ � ⋅ 1 + OCRnx
The N variable represents the prescale factor (1, 8, 32, 64, 128, 256, or 1024).
As for the Normal mode of operation, the TOV2 Flag is set in the same timer clock cycle that the counter
counts from MAX to 0x00.
TCNTn
Period 1 2 3 4 5 6 7
The Timer/Counter Overflow Flag (TOV2) is set each time the counter reaches TOP. If the interrupt is
enabled, the interrupt handler routine can be used for updating the compare value.
In fast PWM mode, the compare unit allows generation of PWM waveforms on the OC2x pin. Setting the
COM2x1:0 bits to two will produce a non-inverted PWM and an inverted PWM output can be generated
by setting the COM2x[1:0] to three. TOP is defined as 0xFF when WGM2[2:0] = 0x3, and OCR2A when
MGM2[2:0] = 0x7. The actual OC2x 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 OC2x Register at
the compare match between OCR2x and TCNT2, and clearing (or setting) the OC2x 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:
�clk_I/O
�OCnxPWM =
� ⋅ 256
The N variable represents the prescale factor (1, 8, 32, 64, 128, 256, or 1024).
The extreme values for the OCR2A Register represent special cases when generating a PWM waveform
output in the fast PWM mode. If the OCR2A is set equal to BOTTOM, the output will be a narrow spike for
each MAX+1 timer clock cycle. Setting the OCR2A equal to MAX will result in a constantly high or low
output (depending on the polarity of the output set by the COM2A[1:0] bits.)
A frequency (with 50% duty cycle) waveform output in fast PWM mode can be achieved by setting OC2x
to toggle its logical level on each compare match (COM2x[1:0] = 1). The waveform generated will have a
maximum frequency of foc2 = fclk_I/O/2 when OCR2A is set to zero. This feature is similar to the OC2A
toggle in CTC mode, except the double buffer feature of the Output Compare unit is enabled in the fast
PWM mode.
OCRnx Update
TCNTn
OCnx (COMnx[1:0] = 2)
OCnx (COMnx[1:0] = 3)
Period 1 2 3
The Timer/Counter Overflow Flag (TOV2) 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 generation of PWM waveforms on the OC2x pin.
Setting the COM2x[1:0] bits to two will produce a non-inverted PWM. An inverted PWM output can be
generated by setting the COM2x[1:0] to three. TOP is defined as 0xFF when WGM2[2:0] = 0x3, and
OCR2A when WGM2[2:0] = 7. The actual OC2x 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
OC2x Register at the compare match between OCR2x and TCNT2 when the counter increments, and
setting (or clearing) the OC2x Register at compare match between OCR2x and TCNT2 when the counter
decrements. The PWM frequency for the output when using phase correct PWM can be calculated by the
following equation:
clkI/O
clkTn
(clkI/O /1)
TOVn
The following figure shows the same timing data, but with the prescaler enabled.
clkI/O
clkTn
(clkI/O /8)
TOVn
The following figure shows the setting of OCF2A in all modes except CTC mode.
Figure 23-10. Timer/Counter Timing Diagram, Setting of OCF2A, with Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
OCFnx
The following figure shows the setting of OCF2A and the clearing of TCNT2 in CTC mode.
Figure 23-11. Timer/Counter Timing Diagram, Clear Timer on Compare Match mode, with
Prescaler (fclk_I/O/8)
clkI/O
clkTn
(clkI/O /8)
TCNTn
TOP - 1 TOP BOTTOM BOTTOM + 1
(CTC)
OCRnx TOP
OCFnx
clkT2S/8
clkT2S/32
clkT2S/64
clkT2S/128
clkT2S/256
clkT2S/1024
AS2
PSRASY 0
CS20
CS21
CS22
The clock source for TC2 is named clkT2S. It is by default connected to the main system I/O clock clkI/O.
By writing a '1' to the Asynchronous TC2 bit in the Asynchronous Status Register (ASSR.AS2), TC2 is
asynchronously clocked from the TOSC1 pin. This enables use of TC2 as a Real Time Counter (RTC).
When AS2 is set, pins TOSC1 and TOSC2 are disconnected from Port B. A crystal can then be
connected between the TOSC1 and TOSC2 pins to serve as an independent clock source for TC2. The
Oscillator is optimized for use with a 32.768kHz crystal.
For TC2, the possible prescaled selections are: clkT2S/8, clkT2S/32, clkT2S/64, clkT2S/128, clkT2S/256, and
clkT2S/1024. Additionally, clkT2S as well as 0 (stop) may be selected. The prescaler is reset by writing a '1'
to the Prescaler Reset TC2 bit in the General TC2 Control Register (GTCCR.PSRASY). This allows the
user to operate with a defined prescaler.
Bit 7 6 5 4 3 2 1 0
COM2A [1:0] COM2B [1:0] WGM2 [1:0]
Access R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0
The table below shows the COM2A[1:0] bit functionality when the WGM2[1:0] bits are set to fast PWM
mode.
Table 23-4. Compare Output Mode, Fast PWM(1)
Note:
1. A special case occurs when OCR2A equals TOP and COM2A1 is set. In this case the compare
match is ignored, but the set or clear is done at BOTTOM. Refer to Fast PWM Mode for details.
The table below shows the COM2A[1:0] bit functionality when the WGM2[2:0] bits are set to phase
correct PWM mode.
1 0 Clear OC2A on Compare Match when up-counting. Set OC2A on Compare Match
when down-counting.
1 1 Set OC2A on Compare Match when up-counting. Clear OC2A on Compare Match
when down-counting.
Note:
1. A special case occurs when OCR2A equals TOP and COM2A1 is set. In this case, the Compare
Match is ignored, but the set or clear is done at TOP. Refer to Phase Correct PWM Mode for
details.
The table below shows the COM0B[1:0] bit functionality when the WGM0[2:0] bits are set to fast PWM
mode.
Table 23-7. Compare Output Mode, Fast PWM(1)
Note:
Note:
1. A special case occurs when OCR2B equals TOP and COM2B1 is set. In this case, the Compare
Match is ignored, but the set or clear is done at TOP. Refer to Phase Correct PWM Mode for
details.
Note:
1. MAX = 0xFF
2. BOTTOM = 0x00
Bit 7 6 5 4 3 2 1 0
FOC2A FOC2B WGM2 [2] CS2[2:0]
Access R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0
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.
Name: TCNT2
Offset: 0xB2
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
TCNT2[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: OCR2A
Offset: 0xB3
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
OCR2A[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
OCR2B[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: TIMSK2
Offset: 0x70
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
OCIE2B OCIE2A TOIE2
Access R/W R/W R/W
Reset 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Bit 7 6 5 4 3 2 1 0
OCF2B OCF2A TOV2
Access R/W R/W R/W
Reset 0 0 0
Name: ASSR
Offset: 0xB6
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
EXCLK AS2 TCN2UB OCR2AUB OCR2BUB TCR2AUB TCR2BUB
Access R/W R/W R R R R R
Reset 0 0 0 0 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: GTCCR
Offset: 0x43
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x23
24.1 Features
• Full-duplex, Three-wire Synchronous Data Transfer
• Master or Slave Operation
• LSB First or MSB First Data Transfer
• Seven Programmable Bit Rates
• End of Transmission Interrupt Flag
• Write Collision Flag Protection
• Wake-up from Idle Mode
• Double Speed (CK/2) Master SPI Mode
24.2 Overview
The Serial Peripheral Interface (SPI) allows high-speed synchronous data transfer between the device
and peripheral units, or between several AVR devices.
The USART can also be used in Master SPI mode, please refer to USART in SPI Mode chapter.
To enable the SPI module, Power Reduction Serial Peripheral Interface bit in the Power Reduction
Register (PRR.PRSPI0) must be written to '0'.
DIVIDER
/2/4/8/16/32/64/128
SPI2X
SPI2X
Note: Refer to the pin-out description and the IO Port description for SPI pin placement.
The interconnection between Master and Slave CPUs with SPI is shown in the figure below. 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
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 minimum low and high periods should be longer than two CPU clock
cycles.
When the SPI is enabled, the data direction of the MOSI, MISO, SCK, and SS pins is overridden
according to the table below. For more details on automatic port overrides, refer to the IO Port
description.
Table 24-1. SPI Pin Overrides
Note: 1. See the IO Port description for how to define the SPI pin directions.
The following code examples show how to initialize the SPI as a Master and how to perform a simple
transmission. DDR_SPI in the examples must be replaced by the actual Data Direction Register
controlling the SPI pins. DD_MOSI, DD_MISO and DD_SCK must be replaced by the actual data direction
bits for these pins. E.g. if MOSI is placed on pin PB5, replace DD_MOSI with DDB5 and DDR_SPI with
DDRB.
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
C Code Example
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);
}
The following code examples show how to initialize the SPI as a Slave and how to
perform a simple reception.
Assembly Code Example
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
in r16, SPSR
sbrs r16, SPIF
rjmp SPI_SlaveReceive
; Read received data and return
in r16,SPDR
ret
C Code Example
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;
}
Related Links
The SPI data transfer formats are shown in the following figure.
Figure 24-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 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 LSB
LSB first (DORD = 1) LSB Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 MSB
SAMPLE I
MOSI/MISO
CHANGE 0
MOSI PIN
CHANGE 0
MISO PIN
SS
MSB first (DORD = 0) MSB Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 LSB
LSB first (DORD = 1) LSB Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 MSB
Name: SPCR
Offset: 0x4C [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x2C
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: SPSR
Offset: 0x4D [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x2D
Bit 7 6 5 4 3 2 1 0
SPIF WCOL SPI2X
Access R R R/W
Reset 0 0 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: SPDR
Offset: 0x4E [ID-000004d0]
Reset: 0xXX
Property: When addressing as I/O Register: address offset is 0x2E
Bit 7 6 5 4 3 2 1 0
SPID[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset x x x x x x x x
25.1 Features
• Full Duplex Operation (Independent Serial Receive and Transmit Registers)
• Asynchronous or Synchronous Operation
• Master or Slave Clocked Synchronous Operation
• High Resolution Baud Rate Generator
• Supports Serial Frames with 5, 6, 7, 8, or 9 data bits and 1 or 2 stop bits
• Odd or Even Parity Generation and Parity Check Supported by Hardware
• Data OverRun Detection
• Framing Error Detection
• Noise Filtering Includes False Start Bit Detection and Digital Low Pass Filter
• Three Separate Interrupts on TX Complete, TX Data Register Empty and RX Complete
• Multi-processor Communication Mode
• Double Speed Asynchronous Communication Mode
• Start Frame Detection
25.2 Overview
The Universal Synchronous and Asynchronous serial Receiver and Transmitter (USART) is a highly
flexible serial communication device.
The USART can also be used in Master SPI mode. The Power Reduction USART bit in the Power
Reduction Register (PRR.PRUSARTn) must be written to '0' in order to enable USARTn.
Prescaling UBRRn+1
/2 /4 /2
Down-Counter 0
1
0
OSC txclk
1
DDR_XCKn
Sync Edge
xcki Register Detector 0
XCKn UMSELn
xcko 1
Pin
DDR_XCKn UCPOLn 1
rxclk
0
Signal description:
• txclk: Transmitter clock (internal signal).
• rxclk: Receiver base clock (internal signal).
• xcki: Input from XCKn pin (internal signal). Used for synchronous slave operation.
• xcko: Clock output to XCKn pin (internal signal). Used for synchronous master operation.
• fosc: System clock frequency.
Operating Mode Equation for Calculating Baud Equation for Calculating UBRRn
Rate(1) Value
Asynchronous Normal mode �OSC �OSC
(U2Xn = 0) BAUD = ����� = −1
16 ����� + 1 16BAUD
UCPOL = 1 XCKn
RxDn / TxDn
Sample
UCPOL = 0 XCKn
RxDn / TxDn
Sample
If used, the parity bit is located between the last data bit and first stop bit of a serial frame.
The following simple USART initialization code examples show one assembly and one C
function that are equal in functionality. The examples assume asynchronous operation
using polling (no interrupts enabled) and a fixed frame format. The baud rate is given as
a function parameter. For the assembly code, the baud rate parameter is assumed to be
stored in the r17, r16 Registers.
Assembly Code Example
USART_Init:
; Set baud rate to UBRR0
out UBRR0H, r17
out UBRR0L, r16
; Enable receiver and transmitter
ldi r16, (1<<RXEN0)|(1<<TXEN0)
out UCSR0B,r16
; Set frame format: 8data, 2stop bit
ldi r16, (1<<USBS0)|(3<<UCSZ00)
out UCSR0C,r16
ret
C Code Example
The following code examples show a simple USART transmit function based on polling of
the Data Register Empty (UDRE) Flag. When using frames with less than eight bits, the
most significant bits written to the UDR0 are ignored. The USART 0 has to be initialized
before the function can be used. For the assembly code, the data to be sent is assumed
to be stored in Register R17.
Assembly Code Example
USART_Transmit:
; Wait for empty transmit buffer
in r17, UCSR0A
sbrs r17, UDRE
rjmp USART_Transmit
; Put data (r16) into buffer, sends the data
out UDR0,r16
ret
C Code Example
The following code examples show a transmit function that handles 9-bit characters. For
the assembly code, the data to be sent is assumed to be stored in registers R17:R16.
Assembly Code Example
USART_Transmit:
; Wait for empty transmit buffer
in r18, UCSR0A
sbrs r18, UDRE
rjmp USART_Transmit
; Copy 9th bit from r17 to TXB8
cbi UCSR0B,TXB8
sbrc r17,0
sbi UCSR0B,TXB8
; Put LSB data (r16) into buffer, sends the data
out UDR0,r16
ret
C Code Example
Note: These transmit functions are written to be general functions. They can be
optimized if the contents of the UCSRnB is static. For example, only the TXB8 bit of the
UCSRnB Register is used after initialization.
The following code example shows a simple USART receive function based on polling of
the Receive Complete (RXC) Flag. When using frames with less than eight bits the most
significant bits of the data read from the UDR0 will be masked to zero. The USART 0 has
to be initialized before the function can be used. For the assembly code, the received
data will be stored in R16 after the code completes.
Assembly Code Example
USART_Receive:
; Wait for data to be received
C Code Example
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 function simply waits for data to be present in the receive buffer by checking the
RXC Flag, before reading the buffer and returning the value.
The following code example shows a simple receive function for USART0 that handles
both nine bit characters and the status bits. For the assembly code, the received data will
be stored in R17:R16 after the code completes.
Assembly Code Example
USART_Receive:
; Wait for data to be received
in r16, UCSR0A
sbrs r16, RXC
rjmp USART_Receive
; Get status and 9th bit, then data from buffer
in r18, UCSR0A
in r17, UCSR0B
in r16, UDR0
; If error, return -1
andi r18,(1<<FE)|(1<<DOR)|(1<<UPE)
breq USART_ReceiveNoError
ldi r17, HIGH(-1)
ldi r16, LOW(-1)
USART_ReceiveNoError:
; Filter the 9th bit, then return
lsr r17
andi r17, 0x01
ret
C Code Example
The receive function example reads all the I/O Registers into the Register File before any
computation is done. This gives an optimal receive buffer utilization since the buffer
location read will be free to accept new data as early as possible.
The following code shows how to flush the receive buffer of USART0.
Assembly Code Example
USART_Flush:
in r16, UCSR0A
sbrs r16, RXC
ret
in r16, UDR0
rjmp USART_Flush
C Code Example
Sample
(U2X = 0) 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3
Sample
(U2X = 1) 0 1 2 3 4 5 6 7 8 1 2
When the clock recovery logic detects a high (idle) to low (start) transition on the RxDn line, the start bit
detection sequence is initiated. Let sample 1 denote the first zero-sample as shown in the figure. The
clock recovery logic then uses samples 8, 9, and 10 for Normal mode, and samples 4, 5, and 6 for
Double Speed mode (indicated with sample numbers inside boxes on the figure), to decide if a valid start
bit is received. If two or more of these three samples have logical high levels (the majority wins), the start
bit is rejected as a noise spike and the Receiver starts looking for the next high to low-transition on RxDn.
If however, a valid start bit is detected, the clock recovery logic is synchronized and the data recovery can
begin. The synchronization process is repeated for each start bit.
RxDn BIT n
Sample
(U2X = 0) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1
Sample
(U2X = 1) 1 2 3 4 5 6 7 8 1
The decision of the logic level of the received bit is taken by doing a majority voting of the logic value to
the three samples in the center of the received bit: If two or all three center samples (those marked by
their sample number inside boxes) have high levels, the received bit is registered to be a logic '1'. If two
or all three samples have low levels, the received bit is registered to be a logic '0'. This majority voting
process acts as a low pass filter for the incoming signal on the RxDn pin. The recovery process is then
repeated until a complete frame is received, including the first stop bit. The Receiver only uses the first
stop bit of a frame.
Sample
(U2X = 0) 1 2 3 4 5 6 7 8 9 10 0/1 0/1 0/1
Sample
(U2X = 1) 1 2 3 4 5 6 0/1
The same majority voting is done to the stop bit as done for the other bits in the frame. If the stop bit is
registered to have a logic '0' value, the Frame Error (UCSRnA.FE) Flag will be set.
A new high to low transition indicating the start bit of a new frame can come right after the last of the bits
used for majority voting. For Normal Speed mode, the first low level sample can be taken at point marked
(A) in the figure above. For Double Speed mode, the first low level must be delayed to (B). (C) marks a
stop bit of full length. The early start bit detection influences the operational range of the Receiver.
�+1 � �+2 �
�slow = �fast =
� − 1 + � ⋅ � + �� � + 1 � + ��
D Rslow [%] Rfast [%] Max. Total Error [%] Recommended Max. Receiver Error [%]
# (Data+Parity Bit)
5 93.20 106.67 +6.67/-6.8 ±3.0
6 94.12 105.79 +5.79/-5.88 ±2.5
D Rslow [%] Rfast [%] Max. Total Error [%] Recommended Max. Receiver Error [%]
# (Data+Parity Bit)
7 94.81 105.11 +5.11/-5.19 ±2.0
8 95.36 104.58 +4.58/-4.54 ±2.0
9 95.81 104.14 +4.14/-4.19 ±1.5
10 96.17 103.78 +3.78/-3.83 ±1.5
Table 25-3. Recommended Maximum Receiver Baud Rate Error for Double Speed Mode (U2Xn = 1)
D Rslow [%] Rfast [%] Max Total Error [%] Recommended Max Receiver Error [%]
# (Data+Parity Bit)
5 94.12 105.66 +5.66/-5.88 ±2.5
6 94.92 104.92 +4.92/-5.08 ±2.0
7 95.52 104,35 +4.35/-4.48 ±1.5
8 96.00 103.90 +3.90/-4.00 ±1.5
9 96.39 103.53 +3.53/-3.61 ±1.5
10 96.70 103.23 +3.23/-3.30 ±1.0
The recommendations of the maximum receiver baud rate error was made under the assumption that the
Receiver and Transmitter equally divides the maximum total error.
There are two possible sources for the receivers baud rate error. The Receiver’s system clock (EXTCLK)
will always have some minor instability over the supply voltage range and the temperature range. When
using a crystal to generate the system clock, this is rarely a problem, but for a resonator, the system clock
may differ more than 2% depending of the resonator's tolerance. The second source for the error is more
controllable. The baud rate generator can not always do an exact division of the system frequency to get
the baud rate wanted. In this case an UBRRn value that gives an acceptable low error can be used if
possible.
BaudRateClosest Match 2
����� % = −1 100 %
BaudRate
Table 25-8. Examples of UBRRn Settings for Commonly Used Oscillator Frequencies
The USART Transmit Data Buffer Register and USART Receive Data Buffer Registers share the same
I/O address referred to as USART Data Register or UDR0. The Transmit Data Buffer Register (TXB) will
be the destination for data written to the UDR0 Register location. Reading the UDR0 Register location will
return the contents of the Receive Data Buffer Register (RXB).
For 5-, 6-, or 7-bit characters the upper unused bits will be ignored by the Transmitter and set to zero by
the Receiver.
The transmit buffer can only be written when the UDRE0 Flag in the UCSR0A Register is set. Data
written to UDR0 when the UDRE0 Flag is not set, will be ignored by the USART Transmitter. When data
is written to the transmit buffer, and the Transmitter is enabled, the Transmitter will load the data into the
Transmit Shift Register when the Shift Register is empty. Then the data will be serially transmitted on the
TxD0 pin.
The receive buffer consists of a two level FIFO. The FIFO will change its state whenever the receive
buffer is accessed. Due to this behavior of the receive buffer, do not use Read-Modify-Write instructions
Name: UDR0
Offset: 0xC6
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
TXB / RXB[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: UCSR0A
Offset: 0xC0
Reset: 0x20
Property: -
Bit 7 6 5 4 3 2 1 0
RXC0 TXC0 UDRE0 FE0 DOR0 UPE0 U2X0 MPCM0
Access R R/W R R R R R/W R/W
Reset 0 0 1 0 0 0 0 0
Name: UCSR0B
Offset: 0xC1
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
RXCIE0 TXCIE0 UDRIE0 RXEN0 TXEN0 UCSZ02 RXB80 TXB80
Access R/W R/W R/W R/W R/W R/W R R/W
Reset 0 0 0 0 0 0 0 0
Name: UCSR0C
Offset: 0xC2
Reset: 0x06
Property: -
UMSEL0[1:0] Mode
00 Asynchronous USART
01 Synchronous USART
10 Reserved
11 Master SPI (MSPIM)(1)
Note:
1. The UDORD0, UCPHA0, and UCPOL0 can be set in the same write operation where the MSPIM is
enabled.
UPM0[1:0] ParityMode
00 Disabled
01 Reserved
10 Enabled, Even Parity
11 Enabled, Odd Parity
UDPRD0: Master SPI Mode: When set to one the LSB of the data word is transmitted first. When set to
zero the MSB of the data word is transmitted first. Refer to the USART in SPI Mode - Frame Formats for
details.
UCPOL0 Transmitted Data Changed (Output of TxD0 Received Data Sampled (Input on RxD0
Pin) Pin)
0 Rising XCK0 Edge Falling XCK0 Edge
1 Falling XCK0 Edge Rising XCK0 Edge
Master SPI Mode: The UCPOL0 bit sets the polarity of the XCK0 clock. The combination of the UCPOL0
and UCPHA0 bit settings determine the timing of the data transfer. Refer to the SPI Data Modes and
Timing for details.
Bit 7 6 5 4 3 2 1 0
RXIE RXS SFDE
Access R/W R/W R/W
Reset 0 0 0
The UBRR0L and UBRR0H register pair represents the 16-bit value, UBRR0.The low byte [7:0] (suffix L)
is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
Bit 7 6 5 4 3 2 1 0
UBRR0[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
26.1 Features
• Full Duplex, Three-wire Synchronous Data Transfer
• Master Operation
• Supports all four SPI Modes of Operation (Mode 0, 1, 2, and 3)
• LSB First or MSB First Data Transfer (Configurable Data Order)
• Queued Operation (Double Buffered)
• High Resolution Baud Rate Generator
• High Speed Operation (fXCKmax = fCK/2)
• Flexible Interrupt Generation
26.2 Overview
The Universal Synchronous and Asynchronous serial Receiver and Transmitter (USART) can be set to a
master SPI compliant mode of operation.
Setting both UMSELn[1:0] bits to one enables the USART in MSPIM logic. In this mode of operation the
SPI master control logic takes direct control over the USART resources. These resources include the
transmitter and receiver shift register and buffers, and the baud rate generator. The parity generator and
checker, the data and clock recovery logic, and the RX and TX control logic is disabled. The USART RX
and TX control logic is replaced by a common SPI transfer control logic. However, the pin control logic
and interrupt generation logic is identical in both modes of operation.
The I/O register locations are the same in both modes. However, some of the functionality of the control
registers changes when using MSPIM.
Operating Mode Equation for Calculating Baud Equation for Calculating UBRRn
Rate(1) Value
Synchronous Master �OSC �OSC
mode BAUD = ����� = −1
2 ����� + 1 2BAUD
Note: 1. The baud rate is defined to be the transfer rate in bit per second (bps)
XCK XCK
XCK XCK
clr r18
out UBRRnH,r18
out UBRRnL,r18
; Setting the XCKn port pin as output, enables master mode.
sbi XCKn_DDR, XCKn
; Set MSPI mode of operation and SPI data mode 0.
ldi r18, (1<<UMSELn1)|(1<<UMSELn0)|(0<<UCPHAn)|(0<<UCPOLn)
out UCSRnC,r18
; Enable receiver and transmitter.
ldi r18, (1<<RXENn)|(1<<TXENn)
out UCSRnB,r18
; Set baud rate.
; IMPORTANT: The Baud Rate must be set after the transmitter is enabled!
out UBRRnH, r17
out UBRRnL, r18
ret
C Code Example
{
UBRRn = 0;
/* Setting the XCKn port pin as output, enables master mode. */
XCKn_DDR |= (1<<XCKn);
/* Set MSPI mode of operation and SPI data mode 0. */
UCSRnC = (1<<UMSELn1)|(1<<UMSELn0)|(0<<UCPHAn)|(0<<UCPOLn);
/* Enable receiver and transmitter. */
UCSRnB = (1<<RXENn)|(1<<TXENn);
/* Set baud rate. */
Related Links
About Code Examples
USART_MSPIM_Transfer:
; Wait for empty transmit buffer
in r16, UCSRnA
sbrs r16, UDREn
rjmp USART_MSPIM_Transfer
; Put data (r16) into buffer, sends the data
out UDRn,r16
; Wait for data to be received
USART_MSPIM_Wait_RXCn:
in r16, UCSRnA
sbrs r16, RXCn
rjmp USART_MSPIM_Wait_RXCn
; Get and return received data from buffer
in r16, UDRn
ret
C Code Example
{
/* Wait for empty transmit buffer */
while ( !( UCSRnA & (1<<UDREn)) );
/* Put data into buffer, sends the data */
UDRn = data;
/* Wait for data to be received */
while ( !(UCSRnA & (1<<RXCn)) );
/* Get and return received data from buffer */
return UDRn;
}
Related Links
About Code Examples
27.1 Features
• Simple, yet Powerful and Flexible Communication Interface, only two Bus Lines Needed
• Both Master and Slave Operation Supported
• Device can Operate as Transmitter or Receiver
• 7-bit Address Space Allows up to 128 Different Slave Addresses
• Multi-master Arbitration Support
• Up to 400kHz Data Transfer Speed
• Slew-rate Limited Output Drivers
• Noise Suppression Circuitry Rejects Spikes on Bus Lines
• Fully Programmable Slave Address with General Call Support
• Address Recognition Causes Wake-up When AVR is in Sleep Mode
• Compatible with Philips’ I2C protocol
SDA
SCL
Term Description
Master The device that initiates and terminates a transmission. The Master also generates the
SCL clock.
Slave The device addressed by a Master.
Transmitter The device placing data on the bus.
Receiver The device reading data from the bus.
This device has one instance of TWI. For this reason, the instance index n is omitted.
The Power Reduction TWI bit in the Power Reduction Register (PRRn.PRTWI) must be written to '0' to
enable the two-wire Serial Interface.
TWI0 is in PRR.
Related Links
PM - Power Management and Sleep Modes
SDA
SCL
Data Change
SDA
SCL
SDA
SCL
1 2 7 8 9
START
SDA from
Transmitter
SDA from
Receiver
SCL from
Master
1 2 7 8 9
STOP, REPEATED
SLA+R/W Data Byte START or Next
Data Byte
Addr MSB Addr LSB R/W ACK Data MSB Data LSB ACK
SDA
SCL
1 2 7 8 9 1 2 7 8 9
SCL from
Master A
TBlow TBhigh
SCL from
Master B
SCL Bus
Line
SDA from
Master B
SDA Line
Synchronized
SCL Line
SCL SDA
Slew-rate Spike Slew-rate Spike
Control Filter Control Filter
TWI Unit
Address Register Status Register Control Register
(TWAR) (TWSR) (TWCR)
TWDR, and loads appropriate control Application loads data into TWDR, and
Action
Indicates
4.TWINT set.
Hardware
1. The first step in a TWI transmission is to transmit a START condition. This is done by writing a
specific value into TWCRn, instructing the TWI n hardware to transmit a START condition. Which
value to write is described later on. However, it is important that the TWINT bit is set in the value
written. Writing a one to TWINT clears the flag. The TWI n will not start any operation as long as
2 wait1: while (!(TWCR0 & Wait for TWINT Flag set. This indicates
in r16,TWCR0 (1<<TWINT))); that the START condition has been
sbrs r16,TWINT transmitted.
rjmp wait1
3 in r16,TWSR0 if ((TWSR0 & 0xF8) != Check value of TWI Status Register. Mask
andi r16, 0xF8 START) prescaler bits. If status different from
cpi r16, START ERROR(); START go to ERROR.
brne ERROR
ldi r16, SLA_W TWDR0 = SLA_W; Load SLA_W into TWDR Register. Clear
out TWDR0, r16 TWCR0 = (1<<TWINT) | TWINT bit in TWCR to start transmission of
ldi r16, (1<<TWINT) | (1<<TWEN); address.
(1<<TWEN)
out TWCR0, r16
4 wait2: while (!(TWCR0 & Wait for TWINT Flag set. This indicates
in r16,TWCR0 (1<<TWINT))); that the SLA+W has been transmitted, and
sbrs r16,TWINT ACK/NACK has been received.
rjmp wait2
5 in r16,TWSR0 if ((TWSR0 & 0xF8) != Check value of TWI Status Register. Mask
andi r16, 0xF8 MT_SLA_ACK) ERROR(); prescaler bits. If status different from
cpi r16, MT_SLA_ACK MT_SLA_ACK go to ERROR.
brne ERROR
ldi r16, DATA TWDR0 = DATA; Load DATA into TWDR Register. Clear
out TWDR0, r16 TWCR0 = (1<<TWINT) | TWINT bit in TWCR to start transmission of
ldi r16, (1<<TWINT) | (1<<TWEN); data.
(1<<TWEN)
out TWCR, r16
6 wait3: while (!(TWCR0 & Wait for TWINT Flag set. This indicates
in r16,TWCR0 (1<<TWINT))); that the DATA has been transmitted, and
sbrs r16,TWINT ACK/NACK has been received.
rjmp wait3
7 in r16,TWSR0 if ((TWSR0 & 0xF8) != Check value of TWI Status Register. Mask
andi r16, 0xF8 MT_DATA_ACK) ERROR(); prescaler bits. If status different from
MT_DATA_ACK go to ERROR.
S START condition
Rs REPEATED START condition
R Read bit (high level at SDA)
W Write bit (low level at SDA)
A Acknowledge bit (low level at SDA)
A Not acknowledge bit (high level at SDA)
Data 8-bit data byte
P STOP condition
SLA Slave Address
Circles are used to indicate that the TWINT Flag is set. The numbers in the circles show the status code
held in TWSRn, with the prescaler bits masked to zero. At these points, actions must be taken by the
application to continue or complete the TWI transfer. The TWI transfer is suspended until the TWINT Flag
is cleared by software.
When the TWINT Flag is set, the status code in TWSRn is used to determine the appropriate software
action. For each status code, the required software action and details of the following serial transfer are
given below in the Status Code table for each mode. Note that the prescaler bits are masked to zero in
these tables.
Device 1 Device 2
MASTER SLAVE Device 3 ........ Device n R1 R2
TRANSMITTER RECEIVER
SDA
SCL
A START condition is sent by writing a value to the TWI Control Register n (TWCRn) of the type
TWCRn=1x10x10x:
• The TWI Enable bit (TWCRn.TWEN) must be written to '1' to enable the 2-wire Serial Interface
• The TWI Start Condition bit (TWCRn.TWSTA) must be written to '1' to transmit a START condition
• The TWI Interrupt Flag (TWCRn.TWINT) must be written to '1' to clear the flag.
The TWI n will then test the 2-wire Serial Bus and generate a START condition as soon as the bus
becomes free. After a START condition has been transmitted, the TWINT Flag is set by hardware, and
the status code in TWSRn will be 0x08 (see Status Code table below). In order to enter MT mode, SLA
+W must be transmitted. This is done by writing SLA+W to the TWI Data Register (TWDRn). Thereafter,
the TWCRn.TWINT Flag should be cleared (by writing a '1' to it) to continue the transfer. This is
accomplished by writing a value to TWRC of the type TWCR=1x00x10x.
When SLA+W have been transmitted and an acknowledgment bit has been received, TWINT is set again
and a number of status codes in TWSR are possible. Possible status codes in Master mode are 0x18,
0x20, or 0x38. The appropriate action to be taken for each of these status codes is detailed in the Status
Code table below.
When SLA+W has been successfully transmitted, a data packet should be transmitted. This is done by
writing the data byte to TWDR. TWDR must only be written when TWINT is high. If not, the access will be
discarded, and the Write Collision bit (TWWC) will be set in the TWCRn Register. After updating TWDRn,
the TWINT bit should be cleared (by writing '1' to it) to continue the transfer. This is accomplished by
writing again a value to TWCRn of the type TWCRn=1x00x10x.
This scheme is repeated until the last byte has been sent and the transfer is ended, either by generating
a STOP condition or a by a repeated START condition. A repeated START condition is accomplished by
writing a regular START value TWCRn=1x10x10x. A STOP condition is generated by writing a value of
the type TWCRn=1x01x10x.
After a repeated START condition (status code 0x10), the 2-wire Serial Interface can access the same
Slave again, or a new Slave without transmitting a STOP condition. Repeated START enables the Master
to switch between Slaves, Master Transmitter mode and Master Receiver mode without losing control of
the bus.
0x08 A START condition has been Load SLA+W 0 0 1 X SLA+W will be transmitted;
transmitted ACK or NOT ACK will be
received
0x18 SLA+W has been transmitted; Load data 0 0 1 X Data byte will be transmitted
ACK has been received byte or and ACK or NOT ACK will be
received
0x20 SLA+W has been transmitted; Load data 0 0 1 X Data byte will be transmitted
NOT ACK has been received byte or and ACK or NOT ACK will be
received
0x28 Data byte has been Load data 0 0 1 X Data byte will be transmitted
transmitted; byte or and ACK or NOT ACK will be
ACK has been received received
0x30 Data byte has been Load data 0 0 1 X Data byte will be transmitted
transmitted; byte or and ACK or NOT ACK will be
NOT ACK has been received received
Successfull
transmission S SLA W A DATA A P
to a slave
receiver
Next transfer
started with a RS SLA W
repeated start
condition
0x10
Not acknowledge R
received after the A P
slave address
0x20
MR
Not acknowledge
received after a data A P
byte
0x30
0x38 0x38
To corresponding
0x68 0x78 0xB0 states in slave mode
Device 1 Device 2
MASTER SLAVE Device 3 ........ Device n R1 R2
RECEIVER TRANSMITTER
SDA
SCL
A START condition is sent by writing to the TWI Control register (TWCRn) a value of the type
TWCRn=1x10x10x:
• TWCRn.TWEN must be written to '1' to enable the 2-wire Serial Interface
• TWCRn.TWSTA must be written to '1' to transmit a START condition
• TWCRn.TWINT must be cleared by writing a '1' to it.
The TWI will then test the 2-wire Serial Bus and generate a START condition as soon as the bus
becomes free. After a START condition has been transmitted, the TWINT Flag is set by hardware, and
the status code in TWSRn will be 0x08 (see Status Code table below). In order to enter MR mode, SLA
+R must be transmitted. This is done by writing SLA+R to TWDR. Thereafter, the TWINT flag should be
cleared (by writing '1' to it) to continue the transfer. This is accomplished by writing the a value to TWCRn
of the type TWCRn=1x00x10x.
When SLA+R have been transmitted and an acknowledgment bit has been received, TWINT is set again
and a number of status codes in TWSRn are possible. Possible status codes in Master mode are 0x38,
0x40, or 0x48. The appropriate action to be taken for each of these status codes is detailed in the table
below. Received data can be read from the TWDR Register when the TWINT Flag is set high by
hardware. This scheme is repeated until the last byte has been received. After the last byte has been
received, the MR should inform the ST by sending a NACK after the last received data byte. The transfer
is ended by generating a STOP condition or a repeated START condition. A repeated START condition is
sent by writing to the TWI Control register (TWCRn) a value of the type TWCRn=1x10x10x again. A
STOP condition is generated by writing TWCRn=1x01x10x:
After a repeated START condition (status code 0x10) the 2-wire Serial Interface can access the same
Slave again, or a new Slave without transmitting a STOP condition. Repeated START enables the Master
to switch between Slaves, Master Transmitter mode and Master Receiver mode without losing control
over the bus.
Table 27-4. Status codes for Master Receiver Mode
Status Code Status of the 2-wire Serial Application Software Response Next Action Taken by TWI
(TWSRn) Bus and 2-wire Serial Hardware
To/from To TWCRn
Interface Hardware
Prescaler Bits TWD
are 0 STA STO TWINT TWEA
0x08 A START condition has been Load SLA+R 0 0 1 X SLA+R will be transmitted
transmitted
0x40 SLA+R has been transmitted; No TWDR 0 0 1 0 Data byte will be received and
ACK has been received action NOT ACK will be returned
0x50 Data byte has been received; Read data 0 0 1 0 Data byte will be received and
ACK has been returned byte NOT ACK will be returned
0x58 Data byte has been received; Read data 1 0 1 X Repeated START will be
NOT ACK has been returned byte transmitted
Successfull
reception S SLA R A DATA A DATA A P
from a slave
receiver
Not acknowledge W
received after the
A P
slave address
0x48
MT
Arbitration lost in slave Other master Other master
address or data byte
A or A continues
A continues
0x38 0x38
To corresponding
0x68 0x78 0xB0 states in slave mode
Device 1 Device 2
SLAVE MASTER Device 3 ........ Device n R1 R2
RECEIVER TRANSMITTER
SDA
SCL
To initiate the SR mode, the TWI (Slave) Address Register n (TWARn) and the TWI Control Register n
(TWCRn) must be initialized as follows:
The upper seven bits of TWARn are the address to which the 2-wire Serial Interface will respond when
addressed by a Master (TWARn.TWA[6:0]). If the LSB of TWARn is written to TWARn.TWGCI=1, the TWI
n will respond to the general call address (0x00), otherwise it will ignore the general call address.
TWCRn must hold a value of the type TWCRn=0100010x - TWCRn.TWEN must be written to '1' to
enable the TWI. TWCRn.TWEA bit must be written to '1' to enable the acknowledgment of the device’s
own slave address or the general call address. TWCRn.TWSTA and TWSTO must be written to zero.
When TWARn and TWCRn have been initialized, the TWI waits until it is addressed by its own slave
address (or the general call address, if enabled) followed by the data direction bit. If the direction bit is '0'
(write), the TWI will operate in SR mode, otherwise ST mode is entered. After its own slave address and
the write bit have been received, the TWINT Flag is set and a valid status code can be read from TWSR.
The status code is used to determine the appropriate software action, as detailed in the table below. The
SR mode may also be entered if arbitration is lost while the TWI is in the Master mode (see states 0x68
and 0x78).
If the TWCRn.TWEA bit is reset during a transfer, the TWI will return a "Not Acknowledge" ('1') to SDA
after the next received data byte. This can be used to indicate that the Slave is not able to receive any
more bytes. While TWEA is zero, the TWI does not acknowledge its own slave address. However, the 2-
wire Serial Bus is still monitored and address recognition may resume at any time by setting TWEA. This
implies that the TWEA bit may be used to temporarily isolate the TWI from the 2-wire Serial Bus.
In all sleep modes other than Idle mode, the clock system to the TWI is turned off. If the TWEA bit is set,
the interface can still acknowledge its own slave address or the general call address by using the 2-wire
Serial Bus clock as a clock source. The part will then wake up from sleep and the TWI will hold the SCL
clock low during the wake up and until the TWINT Flag is cleared (by writing '1' to it). Further data
reception will be carried out as normal, with the AVR clocks running as normal. Observe that if the AVR is
set up with a long start-up time, the SCL line may be held low for a long time, blocking other data
transmissions.
Note: The 2-wire Serial Interface Data Register (TWDRn) does not reflect the last byte present on the
bus when waking up from these Sleep modes.
0x60 Own SLA+W has been No TWDRn X 0 1 0 Data byte will be received and
received; action NOT ACK will be returned
ACK has been returned
X 0 1 1 Data byte will be received and
ACK will be returned
0x68 Arbitration lost in SLA+R/W as No TWDRn X 0 1 0 Data byte will be received and
Master; action NOT ACK will be returned
own SLA+W has been X 0 1 1 Data byte will be received and
received; ACK will be returned
ACK has been returned
0x70 General call address has been No TWDRn X 0 1 0 Data byte will be received and
received; action NOT ACK will be returned
ACK has been returned X 0 1 1 Data byte will be received and
ACK will be returned
0x78 Arbitration lost in SLA+R/W as No TWDRn X 0 1 0 Data byte will be received and
Master; action NOT ACK will be returned
General call address has been X 0 1 1 Data byte will be received and
received; ACK will be returned
ACK has been returned
0x80 Previously addressed with own Read data X 0 1 0 Data byte will be received and
SLA+W; byte NOT ACK will be returned
data has been received; X 0 1 1 Data byte will be received and
ACK has been returned ACK will be returned
0x88 Previously addressed with own Read data 0 0 1 0 Switched to the not addressed
SLA+W; byte Slave mode;
no recognition of own SLA or
data has been received;
GCA
NOT ACK has been returned
0 0 1 1 Switched to the not addressed
Slave mode;
own SLA will be recognized;
GCA will be recognized if
TWGCE = “1”
0x90 Previously addressed with Read data X 0 1 0 Data byte will be received and
general call; byte NOT ACK will be returned
data has been received; X 0 1 1 Data byte will be received and
ACK has been returned ACK will be returned
0x98 Previously addressed with Read data 0 0 1 0 Switched to the not addressed
general call; byte Slave mode;
no recognition of own SLA or
data has been received;
GCA
NOT ACK has been returned
0 0 1 1 Switched to the not addressed
Slave mode;
own SLA will be recognized;
GCA will be recognized if
TWGCE = “1”
0x88
0x68
0x98
0x78
Device 1 Device 2
SLA VE MASTER Device 3 ........ Device n R1 R2
TRANSMITTER RECEIVER
SDA
SCL
To initiate the SR mode, the TWI (Slave) Address Register (TWARn) and the TWI Control Register
(TWCRn) must be initialized as follows:
The upper seven bits of TWARn are the address to which the 2-wire Serial Interface will respond when
addressed by a Master (TWARn.TWA[6:0]). If the LSB of TWARn is written to TWARn.TWGCI=1, the TWI
will respond to the general call address (0x00), otherwise it will ignore the general call address.
TWCRn must hold a value of the type TWCRn=0100010x - TWEN must be written to one to enable the
TWI. The TWEA bit must be written to one to enable the acknowledgment of the device’s own slave
address or the general call address. TWSTA and TWSTO must be written to zero.
When TWARn and TWCRn have been initialized, the TWI waits until it is addressed by its own slave
address (or the general call address if enabled) followed by the data direction bit. If the direction bit is “1”
(read), the TWI will operate in ST mode, otherwise SR mode is entered. After its own slave address and
the write bit have been received, the TWINT Flag is set and a valid status code can be read from
TWSRb. The status code is used to determine the appropriate sofTWARne action. The appropriate action
to be taken for each status code is detailed in the table below. The ST mode may also be entered if
arbitration is lost while the TWI is in the Master mode (see state 0xB0).
If the TWCRn.TWEA bit is written to zero during a transfer, the TWI will transmit the last byte of the
transfer. State 0xC0 or state 0xC8 will be entered, depending on whether the Master Receiver transmits a
NACK or ACK after the final byte. The TWI is switched to the not addressed Slave mode, and will ignore
the Master if it continues the transfer. Thus the Master Receiver receives all '1' as serial data. State 0xC8
is entered if the Master demands additional data bytes (by transmitting ACK), even though the Slave has
transmitted the last byte (TWEA zero and expecting NACK from the Master).
While TWCRn.TWEA is zero, the TWI does not respond to its own slave address. However, the 2-wire
Serial Bus is still monitored and address recognition may resume at any time by setting TWEA. This
implies that the TWEA bit may be used to temporarily isolate the TWI from the 2-wire Serial Bus.
In all sleep modes other than Idle mode, the clock system to the TWI is turned off. If the TWEA bit is set,
the interface can still acknowledge its own slave address or the general call address by using the 2-wire
Serial Bus clock as a clock source. The part will then wake up from sleep and the TWI will hold the SCL
clock will low during the wake up and until the TWINT Flag is cleared (by writing '1' to it). Further data
transmission will be carried out as normal, with the AVR clocks running as normal. Observe that if the
AVR is set up with a long start-up time, the SCL line may be held low for a long time, blocking other data
transmissions.
Note: The 2-wire Serial Interface Data Register (TWDRn) does not reflect the last byte present on the
bus when waking up from these Sleep modes.
0xA8 Own SLA+R has been Load data X 0 1 0 Last data byte will be transmitted
received; byte and NOT ACK should be received
ACK has been returned
X 0 1 1 Data byte will be transmitted and
ACK should be received
0xB0 Arbitration lost in SLA+R/W as Load data X 0 1 0 Last data byte will be transmitted
Master; byte and NOT ACK should be received
own SLA+R has been X 0 1 1 Data byte will be transmitted and
received; ACK should be received
ACK has been returned
0xB8 Data byte in TWDRn has been Load data X 0 1 0 Last data byte will be transmitted
transmitted; byte and NOT ACK should be received
ACK has been received X 0 1 1 Data byte will be transmitted and
ACK should be received
0xC0 Data byte in TWDRn has been No TWDRn 0 0 1 0 Switched to the not addressed
transmitted; action Slave mode;
no recognition of own SLA or
NOT ACK has been received
GCA
0xC8 Last data byte in TWDRn has No TWDRn 0 0 1 0 Switched to the not addressed
been transmitted (TWEA = action Slave mode;
“0”);
0xB0
0xC8
0xF8 No relevant state information No TWDRn No TWCRn action Wait or proceed current
available; TWINT = “0” action transfer
0x00 Bus error due to an illegal No TWDRn 0 1 1 X Only the internal hardware
START or STOP condition action is affected, no STOP
condition is sent on the
bus. In all cases, the bus is
released and TWSTO is
cleared.
SDA
SCL
Several different scenarios may arise during arbitration, as described below:
• Two or more masters are performing identical communication with the same Slave. In this case,
neither the Slave nor any of the masters will know about the bus contention.
• Two or more masters are accessing the same Slave with different data or direction bit. In this case,
arbitration will occur, either in the READ/WRITE bit or in the data bits. The masters trying to output
a '1' on SDA while another Master outputs a zero will lose the arbitration. Losing masters will switch
to not addressed Slave mode or wait until the bus is free and transmit a new START condition,
depending on application software action.
• Two or more masters are accessing different slaves. In this case, arbitration will occur in the SLA
bits. Masters trying to output a '1' on SDA while another Master outputs a zero will lose the
arbitration. Masters losing arbitration in SLA will switch to Slave mode to check if they are being
addressed by the winning Master. If addressed, they will switch to SR or ST mode, depending on
the value of the READ/WRITE bit. If they are not being addressed, they will switch to not addressed
Slave mode or wait until the bus is free and transmit a new START condition, depending on
application software action.
This is summarized in the next figure. Possible status values are given in circles.
Own No 38 TWI bus will be released and not addressed slave mode will be entered
Address / General Call
A START condition will be transmitted when the bus becomes free
received
Yes
Write 68/78 Data byte will be received and NOT ACK will be returned
Direction
Data byte will be received and ACK will be returned
Read Last data byte will be transmitted and NOT ACK should be received
Data byte will be transmitted and ACK should be received
B0
Name: TWBR
Offset: 0xB8
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
TWBR [7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Name: TWSR
Offset: 0xB9
Reset: 0xF8
Property: -
To calculate bit rates, refer to Bit Rate Generator Unit. The value of TWPS1...0 is used in the equation.
The TWAR should be loaded with the 7-bit Slave address (in the seven most significant bits of TWAR) to
which the TWI will respond when programmed as a Slave Transmitter or Receiver, and not needed in the
Master modes. In multi master systems, TWAR must be set in masters which can be addressed as
Slaves by other Masters.
The LSB of TWAR is used to enable recognition of the general call address (0x00). There is an
associated address comparator that looks for the slave address (or general call address if enabled) in the
received serial address. If a match is found, an interrupt request is generated.
Name: TWAR
Offset: 0xBA
Reset: 0xFE
Property: -
Bit 7 6 5 4 3 2 1 0
TWA[6:0] TWGCE
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 1 1 1 1 1 1 1 0
In Transmit mode, TWDR contains the next byte to be transmitted. In Receive mode, the TWDR contains
the last byte received. It is writable while the TWI is not in the process of shifting a byte. This occurs when
the TWI Interrupt Flag (TWINT) is set by hardware. Note that the Data Register cannot be initialized by
the user before the first interrupt occurs. The data in TWDR remains stable as long as TWINT is set.
While data is shifted out, data on the bus is simultaneously shifted in. TWDR always contains the last
byte present on the bus, except after a wake up from a sleep mode by the TWI interrupt. In this case, the
contents of TWDR is undefined. In the case of a lost bus arbitration, no data is lost in the transition from
Master to Slave. Handling of the ACK bit is controlled automatically by the TWI logic, the CPU cannot
access the ACK bit directly.
Name: TWDR
Offset: 0xBB
Reset: 0xFF
Property: -
Bit 7 6 5 4 3 2 1 0
TWD[7:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 1 1 1 1 1 1 1 1
The TWCR is used to control the operation of the TWI. It is used to enable the TWI, to initiate a Master
access by applying a START condition to the bus, to generate a Receiver acknowledge, to generate a
stop condition, and to control halting of the bus while the data to be written to the bus are written to the
TWDR. It also indicates a write collision if data is attempted written to TWDR while the register is
inaccessible.
Name: TWCR
Offset: 0xBC
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
TWINT TWEA TWSTA TWSTO TWWC TWEN TWIE
Access R/W R/W R/W R/W R/W R/W R R/W
Reset 0 0 0 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
TWAM[6:0]
Access R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0
TWAR0
Address
Match
Address
Bit 0
TWAMR0
Address Bit Comparator 0
28.1 Overview
The Analog Comparator compares the input values on the positive pin AIN0 and negative pin AIN1.
When the voltage on the positive pin AIN0 is higher than the voltage on the negative pin AIN1, the Analog
Comparator output, ACO, is set. The comparator’s output can be set to trigger the Timer/Counter1 Input
Capture function. In addition, the comparator can trigger a separate interrupt, exclusive to the Analog
Comparator. The user can select Interrupt triggering on comparator output rise, fall or toggle. A block
diagram of the comparator and its surrounding logic is shown below.
The Power Reduction ADC bit in the Power Reduction Register (PRR.PRADC) must be written to '0' in
order to be able to use the ADC input MUX.
Figure 28-1. Analog Comparator Block Diagram
BANDGAP
REFERENCE VCC
ACBG
ACD
ACIE
AIN0
ANALOG
INTERRUPT COMPARATOR
SELECT IRQ
AIN1 ACI
ACME
ADEN
TO T/C1 CAPTURE
TRIGGER MUX
ACO
ADC MULTIPLEXER
OUTPUT(1)
Note: Refer to the Pin Configuration and the I/O Ports description for Analog Comparator pin placement
Related Links
I/O-Ports
PM - Power Management and Sleep Modes
Pin Configurations
Name: ADCSRB
Offset: 0x7B
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
ACME ADTS [2:0]
Access R/W R/W R/W R/W
Reset 0 0 0 0
The Store Program Memory Control and Status Register contains the control bits needed to control the
Boot Loader operations.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: ACSR0
Offset: 0x4F
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x2F
Bit 7 6 5 4 3 2 1 0
ACOE
Access R/W
Reset 0
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: ACSR
Offset: 0x50
Reset: N/A
Property: When addressing as I/O Register: address offset is 0x30
Name: DIDR1
Offset: 0x7F
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
AIN1D AIN0D
Access R/W R/W
Reset 0 0
29.1 Features
• 10-bit Resolution
• 0.5 LSB Integral Non-Linearity
• ±2 LSB Absolute Accuracy
• 13 - 260μs Conversion Time
• Up to 76.9kSPS (Up to 15kSPS at Maximum Resolution)
• Six Multiplexed Single Ended Input Channels
• Two Additional Multiplexed Single Ended Input Channels ( TQFP and QFN Package only)
• Temperature Sensor Input Channel
• Optional Left Adjustment for ADC Result Readout
• 0 - VCC ADC Input Voltage Range
• Selectable 1.1V ADC Reference Voltage
• Free Running or Single Conversion Mode
• Interrupt on ADC Conversion Complete
• Sleep Mode Noise Canceler
29.2 Overview
The device features a 10-bit successive approximation ADC. The ADC is connected to an 8-channel
Analog Multiplexer which allows eight single-ended voltage inputs constructed from the pins of Port A.
The single-ended voltage inputs refer to 0V (GND).
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 below.
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 how to connect this pin.
The Power Reduction ADC bit in the Power Reduction Register (PRR.PRADC) must be written to '0' in
order to be enable the ADC.
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 1.1V reference voltage may be connected to the AREF pin
by writing to the REFSn bits in the ADMUX Register. The internal voltage reference must be decoupled
by an external capacitor at the AREF pin to improve noise immunity.
ADIE
ADIF
15 0
ADC MULTIPLEXER ADC CTRL. & STATUS ADC DATA REGISTER
SELECT (ADMUX) REGISTER (ADCSRA) (ADCH/ADCL)
REFS1
ADLAR
MUX3
MUX2
MUX1
MUX0
REFS0
ADPS2
ADPS1
ADPS0
ADEN
ADSC
ADFR
ADIF
ADC[9:0]
MUX DECODER
PRESCALER
CHANNEL SELECTION
CONVERSION LOGIC
AVCC
INTERNAL 1.1V
REFERENCE SAMPLE & HOLD
COMPARATOR
AREF
10-BIT DAC -
+
TEMPERATURE
SENSOR
GND
BANDGAP
REFERENCE
ADC7
ADC5
ADC4
ADC3
ADC2
ADC1
ADC0
The analog input channel is selected by writing to the MUX bits in the ADC Multiplexer Selection register
ADMUX.MUX[3:0]. 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 writing a '1' to the ADC
Enable bit in the ADC Control and Status Register A (ADCSRA.ADEN). Voltage reference and input
channel selections will not take effect until ADEN is set. 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
ADC Left Adjust Result bit ADMUX.ADLAR.
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
START CLKADC
ADIF ADATE
SOURCE 1
. CONVERSION
. LOGIC
.
. EDGE
SOURCE n DETECTOR
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 '1' to
ADCSRA.ADSC. In this mode the ADC will perform successive conversions independently of whether the
ADC Interrupt Flag (ADIF) is cleared or not.
CK/128
CK/64
CK/32
CK/16
CK/2
CK/4
CK/8
ADPS0
ADPS1
ADPS2
Cycle Number 1 2 12 13 14 15 16 17 18 19 20 21 22 23 24 25 1 2 3
ADC Clock
ADEN
ADSC
ADIF
Cycle Number 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3
ADC Clock
ADSC
ADIF
Cycle Number 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2
ADC Clock
Trigger
Source
ADATE
ADIF
11 12 13 1 2 3 4
Cycle Number
ADC Clock
ADSC
ADIF
IIH
ADCn
1..100kΩ
CS/H= 14pF
IIL
VCC/2
PC2 (ADC2)
GND
VCC
PC1 (ADC1)
PC0 (ADC0)
ADC7
GND
10m H
AREF
ADC6
100nF
AVCC
PB5
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 29-11. Gain Error
Output Code Gain
Error
Ideal ADC
Actual ADC
• 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.
INL
Ideal ADC
Actual ADC
• 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 29-13. Differential Non-linearity (DNL)
Output Code
0x3FF
1 LSB
DNL
0x000
• Quantization Error: Due to the quantization of the input voltage into a finite number of codes, a
range of input voltages (1 LSB wide) will code to the same value. Always ±0.5 LSB.
• Absolute accuracy: The maximum deviation of an actual (unadjusted) transition compared to an
ideal transition for any code. This is the compound effect of offset, gain error, differential error, non-
linearity, and quantization error. Ideal value: ±0.5 LSB.
where VIN is the voltage on the selected input pin, and VREF the selected voltage reference (see also
descriptions of ADMUX.REFSn and ADMUX.MUX). 0x000 represents analog ground, and 0x3FF
represents the selected reference voltage minus one LSB.
Example:
ADMUX = 0xED (ADC3 - ADC2, 10× gain, 2.56V reference, left adjusted result)
Voltage on ADC3 is 300 mV, voltage on ADC2 is 500 mV.
ADCR = 512 × 10 × (300 - 500) / 2560 = -400 = 0x270
ADCL will thus read 0x00, and ADCH will read 0x9C.
Writing zero to ADLAR right adjusts the result: ADCL = 0x70, ADCH = 0x02.
The values described in the table above 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
software calibration can be done using the formula:
T = { [(ADCH << 8) | ADCL] - TOS} / k
where ADCH and ADCL are the ADC data registers, k is a fixed 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.
Gain and offset varies from device to device, so calibration has to be done for each device. Refer to
AVR122: Calibration of the AVR's Internal Temperature Reference for the detail.
Bit 7 6 5 4 3 2 1 0
REFS [1:0] ADLAR MUX [3:0]
Access R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0
Name: ADCSRA
Offset: 0x7A
Reset: 0x00
Property: -
Bit 7 6 5 4 3 2 1 0
ADEN ADSC ADATE ADIF ADIE ADPS [2:0]
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
The ADCL and ADCH register pair represents the 16-bit value, ADC Data Register. The low byte [7:0]
(suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset +
0x01. For more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
When an ADC conversion is complete, the result is found in these two registers.
When ADCL is read, the ADC Data Register is not updated until ADCH is read. Consequently, 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.
The ADLAR bit and the MUXn bits in ADMUX affect the way the result is read from the registers. If
ADLAR is set (ADLAR=1), the result is left adjusted. If ADLAR is cleared (ADLAR=0 which is the default
value), the result is right adjusted.
Bit 7 6 5 4 3 2 1 0
ADC[7:0]
Access R R R R R R R R
Reset 0 0 0 0 0 0 0 0
The ADCL and ADCH register pair represents the 16-bit value, ADC Data Register. The low byte [7:0]
(suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset +
0x01. For more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers.
When an ADC conversion is complete, the result is found in these two registers.
When ADCL is read, the ADC Data Register is not updated until ADCH is read. Consequently, 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.
The ADLAR bit and the MUXn bits in ADMUX affect the way the result is read from the registers. If
ADLAR is set (ADLAR=1), the result is left adjusted. If ADLAR is cleared (ADLAR=0 which is the default
value), the result is right adjusted.
Bit 15 14 13 12 11 10 9 8
ADC[9:2]
Access R R R R R R R R
Reset 0 0 0 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
ADC[1:0]
Access R R
Reset 0 0
Bit 7 6 5 4 3 2 1 0
ACME ADTS [2:0]
Access R/W R/W R/W R/W
Reset 0 0 0 0
When the respective bits are written to 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.
Bit 7 6 5 4 3 2 1 0
ADC7D ADC6D ADC5D ADC4D ADC3D ADC2D ADC1D ADC0D
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Bits 0, 1, 2, 3, 4, 5, 6, 7 – ADC0D, ADC1D, ADC2D, ADC3D, ADC4D, ADC5D, ADC6D, ADC7D: ADC
Digital Input Disable
30.1 Features
• Complete Program Flow Control
• Emulates All On-chip Functions, Both Digital and Analog, except RESET Pin
• Real-time Operation
• Symbolic Debugging Support (Both at C and Assembler Source Level, or for Other HLLs)
• Unlimited Number of Program Break Points (Using Software Break Points)
• Non-intrusive Operation
• Electrical Characteristics Identical to Real Device
• Automatic Configuration System
• High-speed Operation
• Programming of Non-volatile Memories
30.2 Overview
The debugWIRE On-chip debug system uses a wire with bi-directional interface to control the program
flow and execute AVR instructions in the CPU and to program the different non-volatile memories.
VCC
dW dW(RESET)
GND
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: DWDR
Offset: 0x51 [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x31
31.1 Overview
In ATmega48PB, there is no Read-While-Write support and no separate Boot Loader Section. The SPM
instruction can be executed from the entire Flash.
The device provides a Self-Programming mechanism for downloading and uploading program code by
the MCU itself. The Self-Programming can use any available data interface and associated protocol to
read code and write (program) that code into the Program Memory.
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 with
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:
Since the Flash is organized in pages (Please refer to Page Size section in Memory Programming
chapter), 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 the following figure. Note that the Page Erase and Page Write
operations are addressed independently. Therefore it is of major importance that the software addresses
the same page in both the Page Erase and Page Write operation.
The Load Program Memory (LPM) instruction uses 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.
PCMSB PAGEMSB
PROGRAM
PCPAGE PCWORD
COUNTER
01
02
PAGEEND
Note: The different variables used in this figure are listed in Page Size section in Memory Programming
chapter.
Related Links
Page Size
The algorithm for reading the Fuse Low byte (FLB) 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
Similarly, when reading the Fuse High byte (FHB), load 0x0003 in the Z-pointer. When an LPM instruction
is executed within three cycles after the SPMCSR.BLBSET and SPMCSR.SPMEN are set, the value of
the Fuse High byte (FHB) will be loaded in the destination register as shown below. Refer to Table. Fuse
High Byte for this device in Fuse Bits of Memory Programming chapter 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 (EFB), load 0x0002 in the Z-pointer. When an LPM instruction is
executed within three cycles after the SPMCSR.BLBSET and SPMCSR.SPMEN are set, the value of the
Extended Fuse byte (EFB) will be loaded in the destination register as shown below. Refer to Table.
Extended Fuse Byte for ATmega88PB/ATmega168PB in Fuse Bits of Memory Programming chapter for
detailed description and mapping of the Extended Fuse byte.
Bit 7 6 5 4 3 2 1 0
Rd EFB7 EFB6 EFB5 EFB4 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.
Related Links
Fuse Bits
Latching of Fuses
; (at least the Do_spm sub routine). Only code inside NRWW section can
;-registers used: r0, r1, temp1 (r16), temp2 (r17), looplo (r24),
;-It is assumed that either the interrupt table is moved to the Boot
.org SMALLBOOTSTART
Write_page:
; Page Erase
call Do_spm
call Do_spm
Wrloop:
ld r0, Y+
ld r1, Y+
call Do_spm
adiw ZH:ZL, 2
brne Wrloop
call Do_spm
call Do_spm
Rdloop:
lpm r0, Z+
ld r1, Y+
cpse r0, r1
jmp Error
brne Rdloop
Return:
in temp1, SPMCSR
sbrs temp1, RWWSB ; If RWWSB is set, the RWW section is not ready yet
ret
call Do_spm
rjmp Return
Do_spm:
Wait_spm:
in temp1, SPMCSR
rjmp Wait_spm
in temp2, SREG
cli
Wait_ee:
rjmp Wait_ee
spm
ret
The Store Program Memory Control and Status Register contains the control bits needed to control the
Program memory operations.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: SPMCSR
Offset: 0x57 [ID-000004d0]
Reset: 0x00
Property: When addressing I/O Registers as data space the offset address is 0x37
32.1 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: 1. A page is a section in the Flash consisting of several bytes (see Table. No. of Words in a Page
and No. of Pages in the Flash in Page Size) used during programming. The page organization does not
affect normal operation.
Related Links
Page Size
32.2 Overview
In this device, 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.
Which Section does the Z- Which Section can be read CPU Halted? Read-While-Write
pointer Address during the during Programming? Supported?
Programming?
RWW Section NRWW Section No Yes
NRWW Section None Yes No
Read-While-Write
(RWW) Section
Z-pointer
Addresses NRWW
Z-pointer Section
Addresses RWW No Read-While-Write
Section (NRWW) Section
CPU is Halted
During the Operation
Code Located in
NRWW Section
Can be Read During
the Operation
Related Links
ATmega168PB Boot Loader Parameters
ATmega88PB Boot Loader Parameters
Since the Flash is organized in pages, 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 the following figure. The Page Erase
and Page Write operations are addressed independently. Therefore it is of major importance that the Boot
Loader software addresses the same page in both the Page Erase and Page Write operation. Once a
programming operation is initiated, the address is latched and the Z-pointer can be used for other
operations.
The only SPM operation that does not use the Z-pointer is Setting the Boot Loader Lock bits. The content
of the Z-pointer is ignored and will have no effect on the operation. The LPM instruction does also use the
Z-pointer to store the address. Since this instruction addresses the Flash byte-by-byte, also the LSB (bit
Z0) of the Z-pointer is used.
PCMSB PAGEMSB
PROGRAM
PCPAGE PCWORD
COUNTER
01
02
PAGEEND
Note: The different variables used in this figure are listed in the Related Links.
Related Links
Page Size
ATmega88PB Boot Loader Parameters
The tables in Boot Loader Lock Bits show how the different settings of the Boot Loader bits affect the
Flash access.
If bits 5...0 in R0 are cleared (zero), the corresponding Lock bit will be programmed if an SPM instruction
is executed within four cycles after BLBSET and SPMEN are set in SPMCSR (SPMCSR.BLBSET and
SPMCSR.SPMEN). The Z-pointer 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 and 6 in R0 to “1” when writing the Lock bits. When
programming the Lock bits the entire Flash can be read during the operation.
Bit 7 6 5 4 3 2 1 0
Rd - - BLB12 BLB11 BLB02 BLB01 LB2 LB1
The algorithm for reading the Fuse Low byte (FLB) 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 (SPMCSR.BLBSET and SPMCSR.SPMEN). When an LPM instruction is executed within
three cycles after the SPMCSR.BLBSET and SPMCSR.SPMEN are set, the value of the Fuse Low byte
(FLB) will be loaded in the destination register as shown below.
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 (FHB), load 0x0003 in the Z-pointer. When an LPM instruction
is executed within three cycles after the SPMCSR.BLBSET and SPMCSR.SPMEN are set, the value of
the Fuse High byte (FHB) will be loaded in the destination register as shown below.
Bit 7 6 5 4 3 2 1 0
Rd FHB7 FHB6 FHB5 FHB4 FHB3 FHB2 FHB1 FHB0
When reading the Extended Fuse byte (EFB), load 0x0002 in the Z-pointer. When an LPM instruction is
executed within three cycles after the SPMCSR.BLBSET and SPMCSR.SPMEN are set, the value of the
Extended Fuse byte (EFB) will be loaded in the destination register as shown below.
Bit 7 6 5 4 3 2 1 0
Rd - - - - EFB3 EFB2 EFB1 EFB0
Fuse and Lock bits that are programmed read as '0'. Fuse and Lock bits that are unprogrammed, will read
as '1'.
Related Links
Fuse Bits
; (at least the Do_spm sub routine). Only code inside NRWW section can
;-registers used: r0, r1, temp1 (r16), temp2 (r17), looplo (r24),
;-It is assumed that either the interrupt table is moved to the Boot
.org SMALLBOOTSTART
Write_page:
; Page Erase
call Do_spm
call Do_spm
Wrloop:
ld r0, Y+
ld r1, Y+
call Do_spm
adiw ZH:ZL, 2
brne Wrloop
call Do_spm
call Do_spm
Rdloop:
lpm r0, Z+
ld r1, Y+
cpse r0, r1
jmp Error
brne Rdloop
Return:
in temp1, SPMCSR
sbrs temp1, RWWSB ; If RWWSB is set, the RWW section is not ready yet
ret
call Do_spm
rjmp Return
Do_spm:
Wait_spm:
in temp1, SPMCSR
rjmp Wait_spm
in temp2, SREG
cli
Wait_ee:
rjmp Wait_ee
spm
ret
Note: The different BOOTSZ Fuse configurations are shown in Figure 32-2.
Table 32-7. Read-While-Write Limit, ATmega88PB
For details about these two section, please refer to NRWW – No Read-While-Write Section and RWW –
Read-While-Write Section.
Table 32-8. Explanation of Different Variables used in Figure 32-3
Z0: should be zero for all SPM commands, byte select for the LPM instruction.
Please refer to Addressing the Flash During Self-Programmingor details about the use of Z-pointer during
Self- Programming.
Note: The different BOOTSZ Fuse configurations are shown in Figure 32-2.
Table 32-10. Read-While-Write Limit, ATmega168PB
For details about these two section, please refer to NRWW – No Read-While-Write Section and RWW –
Read-While-Write Section.
Table 32-11. Explanation of Different Variables used in Figure 32-3, ATmega168PB
Z0: should be zero for all SPM commands, byte select for the LPM instruction.
Please refer to Addressing the Flash During Self-Programming or details about the use of Z-pointer
during Self- Programming.
The Store Program Memory Control and Status Register contains the control bits needed to control the
Boot Loader operations.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: SPMCSR
Offset: 0x57 [ID-000004d0]
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x37
Bit 7 6 5 4 3 2 1 0
SPMIE RWWSB SIGRD RWWSRE BLBSET PGWRT PGERS SPMEN
Access R/W R/W R/W R/W R/W R/W R/W R/W
Reset 0 0 0 0 0 0 0 0
Note:
1. '1' means unprogrammed, '0' means programmed.
2. Only on ATmega88PB and ATmega168PB.
Table 33-2. Lock Bit Protection Modes(1)(2)
Note:
1. Program the Fuse bits and Boot Lock bits before programming the LB1 and LB2.
2. '1' means unprogrammed, '0' means programmed.
Table 33-4. Lock Bit Protection - BLB1 Mode(1)(2) (Only ATmega88PB and ATmega168PB.)
Note:
1. Program the Fuse bits and Boot Lock bits before programming the LB1 and LB2.
2. '1' means unprogrammed; '0' means programmed.
Note: 1. The default value of BOOTSZ[1:0] results in maximum Boot Size. See ”Pin Name Mapping”
Table 33-7. Fuse High Byte.
Note:
1. Refer to Alternate Functions of Port C in I/O-Ports chapter for description of RSTDISBL Fuse.
2. The SPIEN Fuse is not accessible in serial programming mode.
3. Refer to WDTCSR – Watchdog Timer Control Register for details.
4. Refer to Table BODLEVEL Fuse Coding in System and Reset Characteristics for BODLEVEL Fuse
decoding.
Table 33-8. Fuse Low Byte
Note:
1. The default value of SUT[1:0] results in maximum start-up time for the default clock source. See
Table. Start-up times for the internal calibrated RC Oscillator clock selection in Calibrated Internal
RC Oscillator of System Clock and Clock Options chapter for details.
2. The default setting of CKSEL[3:0] results in internal RC Oscillator @ 8MHz. See Table 'Internal
Calibrated RC Oscillator Operating Modes' in Calibrated Internal RC Oscillator of the System Clock
and Clock Options chapter for details.
3. The CKOUT Fuse allows the system clock to be output on PORTB0. Refer to Clock Output Buffer
section in the System Clock and Clock Options chapter for details.
4. Refer to System Clock Prescaler section in the System Clock and Clock Options chapter 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.
Related Links
ATmega88PB Boot Loader Parameters
ATmega168PB Boot Loader Parameters
WDTCSR
System and Reset Characteristics
Calibrated Internal RC Oscillator
Clock Output Buffer
System Clock Prescaler
Table 33-11. No. of Words in a Page and No. of Pages in the EEPROM
Related Links
WR PD3 AVCC
XA1 PD6
PAGEL PD7
+12V RESET
BS2 PC2
XTAL1
GND
Note: VCC - 0.3V < AVCC < VCC + 0.3V; however, AVCC should always be within 4.5 - 5.5V
Table 33-12. Pin Name Mapping
Step 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 the following figure, Addressing the Flash Which is
Organized in Pages, in this section. 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.
Step I. Repeat B Through H Until the Entire Flash Is Programmed or Until All Data Has Been
Programmed
01
02
PAGEEND
Note: PCPAGE and PCWORD are listed in the table of No. of Words in a Page and No. of Pages in the
Flash in Page Size section.
A B C D E B C D E G H
0x10 ADDR. LOW DATA LOW DATA HIGH XX ADDR. LOW DATA LOW DATA HIGH XX ADDR. HIGH XX
DATA
XA1
XA0
BS1
XTAL1
WR
RDY/BSY
RESET+12V
OE
PAGEL
BS2
Note: “XX” is don’t care. The letters refer to the programming description above.
A G B C E B C E L
0x11 ADDR. HIGH ADDR. LOW DATA XX ADDR. LOW DATA XX
DATA
XA1
XA0
BS1
XTAL1
WR
RDY/BSY
RESET+12V
OE
PAGEL
BS2
A C A C A C
0x40 DATA XX 0x40 DATA XX 0x40 DATA XX
DATA
XA1
XA0
BS1
BS2
XTAL1
WR
RDY/BSY
RESET +12V
OE
PAGEL
0
Extended Fuse Byte 1
DATA
BS2
Lock Bits 0
1
BS1
Fuse High Byte 1
BS2
VCC
XTAL1
RESET
GND
Note:
1. If the device is clocked by the internal Oscillator, it is no need to connect a clock source to the
XTAL1 pin.
2. VCC - 0.3V < AVCC < VCC + 0.3V, however, AVCC should always be within 1.8–5.5V .
When programming the EEPROM, an auto-erase cycle is built into the self-timed programming operation
(in the Serial mode ONLY) and there is no need to first execute the Chip Erase instruction. The Chip
Erase operation turns the content of every memory location in both the Program and EEPROM arrays
into 0xFF.
Depending on CKSEL Fuses, a valid clock must be present. The minimum low and high periods for the
serial clock (SCK) input are defined as follows:
• Low: > 2 CPU clock cycles for fck < 12MHz, , 3 CPU clock cycles for fck ≥ 12MHz
• High: > 2 CPU clock cycles for fck < 12MHz, 3 CPU clock cycles for fck ≥ 12MHz
Note: The pin mapping for SPI programming is listed. Not all parts use the SPI pins dedicated for the
internal SPI interface.
Note:
1. Not all instructions are applicable for all parts.
2. a = address.
3. Bits are programmed ‘0’, unprogrammed ‘1’.
4. To ensure future compatibility, unused Fuses and Lock bits should be unprogrammed (‘1’) .
5. Refer to the corresponding section for Fuse and Lock bits, Calibration and Signature bytes and
Page size.
6. Instructions accessing program memory use a word address. This address may be random within
the page range.
Note: See http://www.microchip.com/design-centers/8-bit/microchip-avr-mcus for Application Notes
regarding programming and programmers.
If the LSB in RDY/BSY data byte out is ‘1’, a programming operation is still pending. Wait until this bit
returns ‘0’ before the next instruction is carried out.
Within the same page, the low data byte must be loaded prior to the high data byte.
After data is loaded to the page buffer, program the EEPROM page, Please refer to the following figure.
Page Buffer
Page Offset
Page 0
Page 1
Page 2
Page Number
Page N-1
Program Memory/
EEPROM Memory
SAMPLE
Note: 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.
Note: During parallel programming, a 12V signal is connected to the Reset pin. There is therefore no
internal protection diode from the Reset pin to VCC. To achieve the same protection on the Reset pin as
on other I/O pins external protection should be added.
34.2 DC Characteristics
Table 34-2. Common DC characteristics TA = -40°C to 105°C, VCC = 1.8V to 5.5V (unless otherwise
noted) (Continued)
VIH Input High Voltage, except VCC = 1.8V - 2.4V 0.7VCC(2) VCC + 0.5 V
XTAL1 and RESET pins
VCC = 2.4V - 5.5V 0.6VCC(2) VCC + 0.5
VIL1 Input Low Voltage, VCC = 1.8V - 5.5V -0.5 0.1VCC(1) V
XTAL1 pin
VIH1 Input High Voltage, VCC = 1.8V - 2.4V 0.8VCC(2) VCC + 0.5 V
XTAL1 pin
VCC = 2.4V - 5.5V 0.7VCC(2) VCC + 0.5
VIL2 Input Low Voltage, VCC = 1.8V - 5.5V -0.5 0.1VCC(1) V
RESET pin
TA=85°C 0.6
IOL = 10mA,
TA=105°C 0.7 V
VCC = 3V
TA=85°C 2.1
IOH = 10mA,
TA=105°C 2.0 V
VCC = 3V
Note:
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 source more than the test conditions (20mA at VCC = 5V, 10mA at VCC
= 3V) under steady state conditions (non-transient), the following must be observed:
3.1. The sum of all IOH, for ports C0 - C5, D0- D4, ADC7, RESET should not exceed 100mA.
Note:
1. Values with “Minimizing Power Consumption” enabled (0xFF).
Note:
1. Values with Minimizing Power Consumption enabled (0xFF).
2. Typical values at 25°C. Maximum values are test limits in production.
3. The current consumption values include input leakage current.
4. No clock is applied to the pad during power-down mode.
Related Links
Minimizing Power Consumption
20MHz
10MHz
Safe Operating Area
4MHz
V IH1
V IL1
Symbol Parameter VCC= 1.8 - 5.5V VCC= 2.7 - 5.5V VCC= 4.5 - 5.5V Units
Min. Max. Min. Max. Min. Max.
1/tCLCL Oscillator Frequency 0 4 0 10 0 20 MHz
tCLCL Clock Period 250 - 100 - 50 - ns
tCHCX High Time 100 - 40 - 20 - ns
tCLCX Low Time 100 - 40 - 20 - ns
tCLCH Rise Time - 2.0 - 1.6 - 0.5 μs
tCHCL Fall Time - 2.0 - 1.6 - 0.5 μs
ΔtCLCL Change in period from one clock - 2 - 2 - 2 %
cycle to the next
Note:
1. Values are guidelines only.
2. The Power-on Reset will not work unless the supply voltage has been below VPOT (falling)
Table 34-8. BODLEVEL Fuse Coding(1)(2)
BODLEVEL [2:0] Fuses Min. VBOT Typ. VBOT Max VBOT Units
111 BOD Disabled
110 1.7 1.8 2.0 V
BODLEVEL [2:0] Fuses Min. VBOT Typ. VBOT Max VBOT Units
101 2.5 2.7 2.9
100 4.1 4.3 4.5
011 - 000 Reserved
Note: 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 = 110, 101 and 100.
Note: VBOT tested at 25°C and 85°C in production
Note: In SPI Programming mode the minimum SCK high/low period is:
• 2 • tCLCLCL for fCK < 12MHz
• 3 • tCLCL for fCK > 12MHz
SS
6 1
SCK
(CPOL = 0)
2 2
SCK
(CPOL = 1)
4 5 3
MISO
MSB ... LSB
(Data Input)
7 8
MOSI
MSB ... LSB
(Data Output)
SS
10 16
9
SCK
(CPOL = 0)
11 11
SCK
(CPOL = 1)
13 14 12
MOSI
MSB ... LSB
(Data Input)
15 17
MISO
MSB ... LSB X
(Data Output)
Related Links
(TEMP) SPCR – SPI Control Register
Note:
t LOW t LOW
SCL
t SU;STA t HD;STA t HD;DAT t SU;DAT
t SU;STO
SDA
t BUF
Note:
1. AVCC absolute min./max: 1.8V/5.5V
Note:
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.
Figure 34-6. Parallel Programming Timing, Including some General Timing Requirements
tXLWL
tXHXL
XTAL1
tDVXH tXLDX
Data & Contol
(DATA, XA0/1, BS1, BS2)
tBVPH tPLBX t BVWL tWLBX
PAGEL tPHPL
tWLWH
WR tPLWL
WLRL
RDY/BSY
tWLRH
Figure 34-7. Parallel Programming Timing, Loading Sequence with Timing Requirements
LOAD ADDRESS LOAD DATA LOAD DATA LOAD DATA LOAD ADDRESS
(LOW BYTE) (LOW BYTE) (HIGH BYTE) (LOW BYTE)
t XLXH tXLPH
tPLXH
XTAL1
BS1
PAGEL
DATA ADDR0 (Low Byte) DATA (Low Byte) DATA (High Byte) ADDR1 (Low Byte)
XA0
XA1
Note: The timing requirements shown in Parallel Programming Characteristics (i.e., tDVXH, tXHXL, and
tXLDX) also apply to loading operation
tXLOL
XTAL1
tBVDV
BS1
tOLDV
OE
tOHDZ
DATA ADDR0 (Low Byte) DATA (Low Byte) DATA (High Byte) ADDR1 (Low Byte)
XA0
XA1
Note: The timing requirements shown in Parallel Programming Characteristics (i.e., tDVXH, tXHXL, and
tXLDX) also apply to reading operation.
0.7
Vcc [V]
0.6 5.5
5
0.5
4.5
4
3.3
0.4
ICC [mA]
2.7
1.8
0.3
0.2
0.1
0
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
Frequency [MHz]
ACTIVE SUSupply
Figure 35-2. ATmega48PB/88PB: Active PPLY CURR ENT vs. FRE
Current QUEFrequency
vs. NCY (1-20MHz)
MEGA88 REV B
14
Vcc [V]
12
5.5
10
5
8 4.5
ICC (mA)
4
6
3.3
4
2.7
2 1.8
0
0 2 4 6 8 10 12 14 16 18 20
Frequency [MHz]
0.07
105
85
0.06 25
ICC [mA]
-40
0.05
0.04
0.03
0.02
1.5 2 2.5 3 3.5 4 4.5 5 5.5
VCC [V]
Figure 35-4. ATmega48PB/88PB: Active Supply Current 1 MHz) vs. VCC (Internal RC Oscillator, 1MHz)
Mega48/88 Power -Active Supply Current vs. Vcc
(Internal RC Oscillator,
0.9
0.8
0.7
Temp [°C]
0.6
Icc (mA)
105
0.5
85
0.4 25
-40
0.3
0.2
0.1
0
1.5 2 2.5 3 3.5 4 4.5 5 5.5
Vcc (V)
ACTIVE SUPPLY CURRENT vs. VCC
Figure 35-5. ATmega488PB/88PB: Active Supply
INTERNAL Current
RC OSCILLATOR, 8 MHz vs. V
CC (Internal RC Oscillator, 8MHz)
MEGA88PB REV B
6
Temperature [C]
5
105
85
4 25
-40
ICC [mA]
0
1.5 2 2.5 3 3.5 4 4.5 5 5.5
VCC [V]
0.08
4.5
4
ICC [mA] 0.06 3.3
2.7
0.04
1.8
0.02
0
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
Frequency [MHz]
2.4
2.1
Vcc [V]
1.8
5.5
1.5 5
Icc (mA)
4.5
1.2
4
3.3
0.9
2.7
0.6 1.8
0.3
0
0 2 4 6 8 10 12 14 16 18 20
Frequency (MHz)
IDLE SUPPLY CURRENT vs. VCC
Figure 35-8. ATmega48PB/88PB: Idle INTERNAL
Supply RC OSCILLATOR, 128 KHz
Current vs. VCC (Internal RC Oscillator, 128kHz)
MEGA88 PB REV B
0.01
0.008
0.006
0.004
1.5 2 2.5 3 3.5 4 4.5 5 5.5
VCC [V]
0.4
Temp [°C]
0.35
105
85
0.3
25
0.25
-40
ICC (mA)
0.2
0.15
0.1
0.05
0
1.5 2 2.5 3 3.5 4 4.5 5 5.5
VCC (V)
Temp [C]
0.8 Temp [°C]
Icc (mA)
105
0.6 85
25
-40
0.4
0.2
0
1.5 2 2.5 3 3.5 4 4.5 5 5.5
Vcc (V)
It is possible to calculate the typical current consumption based on the numbers from the table above for
other VCC and frequency settings than listed in the table Table 35-1.
35.1.3.1 Example
Calculate the expected current consumption in idle mode with TIMER1, ADC, and SPI enabled at VCC =
2.0V and F = 1MHz. From the table above, third column, we need to add 12.28% for the TIMER1, 19.74%
for the ADC, and 15.63% for the SPI module. Reading from Figure 35-6, we find that the idle current
consumption is ~0.036 mA at VCC = 2.0V and F = 1MHz. The total current consumption in idle mode with
TIMER1, ADC, and SPI enabled, gives:
ICCtotal ≃ 0.036 mA⋅(1 + 0.123 + 0.197 + 0.156) ≃ 0.053mA
2.5
2
Temp [°C]
-40
1.5 25
Icc (uA)
85
105
1
0.5
0
1.8 2.1 2.4 2.7 3 3.3 3.6 3.9 4.2 4.5 4.8 5.1 5.4
Vcc (V)
6 Temp [°C]
105
5
85
4
25
Icc (uA)
-40
3
0
1.8 2.1 2.4 2.7 3 3.3 3.6 3.9 4.2 4.5 4.8 5.1 5.4
Vcc (V)
5
Temp [°C]
4 -40
25
Icc (uA)
3 85
105
2
0
1.8 2.2 2.5 2.8 3.1 3.4 3.7 4 4.3 4.6 4.9 5.2 5.5
Vcc (V)
80 2 - Res
2 - Xtal
60
4 - Res
40
4 - Xtal
20 6 - Res
6 - Xtal
0
1.8 2.2 2.5 2.8 3.1 3.4 3.7 4 4.3 4.6 4.9 5.2 5.5
Vcc (V)
60
50
40
IOP ( µA)
30
10 5°C
20
85°C
10 25°C
-40°C
0
0.0 0.2 0.4 0.6 0.8 1.0 1.2 1.4 1.6 1.8 2.0
VOP (V)
100
90
80
70
60
IOP ( µA)
50
40
10 5°C
30
85°C
20
25°C
10
-40°C
0
0.0 0.5 1.0 1.5 2.0 2.5 3.0
VOP (V)
200
180
160
140
120
IOP (μA)
100
80
105°C
60
85°C
40
25°C
20
-40°C
0
0 1 2 3 4 5 6
VOP (V)
45
40
35
30
IRESE T ( uA)
25
20
10 5°C
15
85°C
10
25°C
5
-40°C
0
0.0 0.2 0.4 0.6 0.8 1.0 1.2 1.4 1.6 1.8 2.0
VRESE T (V)
Figure 35-19. ATmega48PB/88PB: Reset Pull-up Resistor Current vs. Reset Pin Voltage
(VCC = 2.7V) RESE T PULL UP RES ISTOR CURRENT vs . RESE T PIN VOLTAGE
MEG A88/48PB REV B VCC=2.7V
80
70
60
50
IRESE T ( µA)
40
30 10 5°C
20 85°C
25°C
10
-40°C
0
0.0 0.5 1.0 1.5 2.0 2.5 3.0
VRESE T (V)
RESE T PUReset
Figure 35-20. ATmega48PB/88PB: LL UP RPull-up Resistor Current vs.
GE Reset Pin Voltage (V
ES ISTOR CURRENT vs . RESE T PIN VOLTA
MEG A88/48PB REV B VCC=5.0V
CC = 5V)
160
140
120
100
IRESE T ( µA)
80
60 10 5°C
40 85°C
25°C
20
-40°C
0
0 1 2 3 4 5 6
VRESE T (V)
1.2
10 5°C
1.0
85°C
0.8 25°C
-40°C
VOL ( V)
0.6
0.4
0.2
0.0
0 5 10 15 20 25
IOL (mA)
I/O PIN OUTPUT VOLTAGE vs . SINK CURRENT
Figure 35-22. ATmega48PB/88PB: I/O
MEGPin Output
A88/48PB Voltage
Rev B NO RMAL PO W ER PINSvs. Sink Current (VCC = 5V)
VCC=5V
0.7
0.6
10 5°C
0.5
85°C
0.4 25°C
VOL ( V)
-40°C
0.3
0.2
0.1
0
0 5 10 15 20 25
IOL (mA)
3.5
3.0
VOH ( V)
2.5
10 5°C
85°C
2.0 25°C
-40°C
1.5
0 5 10 15 20 25
IOH (mA)
5.2
5.0
4.8
VOH ( V)
4.6 10 5°C
85°C
4.4
25°C
-40°C
4.2
0 5 10 15 20 25
IOH (mA)
3.5
10 5°C
3.0
85°C
2.5 25°C
-40°C
T h r es hold ( V)
2.0
1.5
1.0
0.5
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
I/O PIN INPUT THRES HOLD VOLTAGE vs . V
Figure 35-26. ATmega48PB/88PB: I/O Pin Input Threshold Voltage
M88/48PB Rev B VIL, IO PIN READ AS '0'
CC
vs. VCC (VIL, I/O Pin read as ‘0’)
2.5
10 5°C
2.0
85°C
25°C
T h r es hold ( V)
1.5
-40°C
1.0
0.5
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
1.4
10 5°C
1.2
85°C
0.8 -40°C
0.6
0.4
0.2
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
RESE T INPUT THRES HOLD VOLTAGE vs . V CC
Figure 35-28. ATmega48PB/88PB: Reset
MEG AInput Threshold
88/48PB REV B VIH READ AS '1' Voltage vs. VCC (VIH, I/O Pin read as ‘1’)
2.5
2.0 10 5°C
85°C
T h r es hold ( V)
1.5
25°C
-40°C
1.0
0.5
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
RESE T INPUT THRES HOLD VOLTAGE vs . V
Figure 35-29. ATmega48PB/88PB: Reset Input Threshold Voltage
MEG A88/48PB REV B VIL, IO PIN READ AS '0'
CC
vs. VCC (VIL, I/O Pin read as ‘0’)
2.5
2.0
10 5°C
85°C
T h r es hold ( V)
1.5
25°C
-40°C
1.0
0.5
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
0.7
0.6
0.4
0.3
10 5°C
0.2 85°C
0.1 25°C
-40°C
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
1.78
1.77
Rising
1.76
1.75
T h r es hold ( V)
1.74
1.73
Falling
1.72
1.71
1.70
-60 -40 -20 0 20 40 60 80 100 120
Temperature [°C]
BOD THRES HOLD S vs . TEMPE RATURE
Figure 35-32. ATmega48PB/88PB: BOD Thresholds
MEG A88/48 PBvs.
REV BTemperature
2.7V (BODLEVEL is 2.7V)
2.80
2.78
2.76
2.74
Rising
T h r es hold ( V)
2.72
2.70
2.68
Falling
2.66
2.64
2.62
2.60
-60 -40 -20 0 20 40 60 80 100 120
Temperature [°C]
4.40
4.38
Rising
4.36
4.34
T h r es hold ( V)
4.32
4.30
Falling
4.28
4.26
4.24
4.22
-60 -40 -20 0 20 40 60 80 100 120
Temperature [°C]
1.12
4.5V
1.12 4.0V
Bandgap Voltage (V)
3.3V
1.11 2.7V
1.8V
1.11 5.5V
1.10
1.10
-50 -30 -10 10 30 50 70 90 11 0
Temperature [°C]
1.11 0
1.105
Bandgap Voltage (V)
1.100
10 5°C
1.095
85°C
1.090 25°C
-40°C
1.085
1.080
1.075
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
Vcc (V)
122
120
Vcc [V]
118
5.5
Frequency (KHz)
5
116
4.5
4
114
3.5
3
112 2.5
2.25
110 1.8
108
-40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 110
Temperature [°C]
122
120
118
Temp [°C]
Frequency (KHz)
116
105
85
114
25
-40
112
110
CALIBRATED 8MHz RC OSCILLATOR FREQUENCY vs. OPERATING VOLTAGE
MEGA88/48 PB Rev B
108
1.5 2 2.5 3 3.5 4 4.5 5 5.5
Vcc (V)
8.5
8.4
8.3
8.2
8.1 105°C
F RC (MHz)
8.0 85°C
7.9 25°C
7.8 -40°C
7.7
7.6
7.5
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
8.4
8.3
8.2 5.5V
5.0V
8.1
F RC (MHz)
4.5V
8.0
3.3V
7.9 3.0V
7.8 1.88V
7.7
7.6
-40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 110
Temperature [°C]
Figure 35-40. ATmega48PB_88PB: Calibrated 8MHz RC Oscillator Frequency vs. OSCCAL Value Mega48/88 (59B11) Rev.K
Calibrated 8MHz RC Oscillator Frequency vs. Oscal Value
18
16
14
Temp [°C]
12
FRC (MHz)
10 105
85
8
25
6 -40
0
0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256
OSCCAL (X1)
400
350 10 5°C
85°C
300
25°C
250
-40°C
ICC ( uA)
200
150
100
50
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
160
10 5°C
140
85°C
120
25°C
100 -40°C
ICC ( uA)
80
60
40
20
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
AREF EX TERNAL REFERNCE Current vs VCC
Figure 35-43. ATmega48PB_88PB: AREF External
MEG A88/48PBReference
REV B Current vs. VCC
140
120 10 5°C
85°C
100
25°C
80
-40°C
ICC ( uA)
60
40
20
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
BROWNOUT D EDetector
Figure 35-44. ATmega48PB_88PB: Brownout TECTOR CURRECurrent
NT vs . V C C vs. V
MEG A88/48PB REV B CC
30
10 5°C
25
85°C
25°C
20
-40°C
ICC ( µA)
15
10
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
7 10 5°C
6 85°C
25°C
Icc ( mA)
5
-40°C
4
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
0.12
0.10
5.5V
5.0V
0.08 4.5V
4.0V
ICC ( mA)
0.06
3.3V
0.04 2.7V
1.8V
0.02
0.00
0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0
RESE T SUSupply
Figure 35-47. ATmega48PB_88PB: Reset PP LY CURRECurrent
N T vs . VFR EQvs.
(1 20M hFrequency
z) (1MHz - 20MHz)
ME GA 88/48PB Rev
2.5
2.0
5.5V
5.0V
1.5
4.5V
ICC ( mA)
4.0V
1.0
3.6V
2.7V
0.5
1.8V
0.0
0 2 4 6 8 10 12 14 16 18 20
1800
1600
1400
1200
800
10 5°C
600
85°C
400
25°C
200
-40°C
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
35.2.1 Active Supply Current ATmega168PB: Active Supply Current vs. Low Frequency (0.1MHz - 1MHz)
Figure 35-49. ATmega168PB: Active Supply Current vs. Low Frequency (0.1-1.0MHz)
0.8
0.7 5.5V
0.6 5.0V
0.5 4.5V
ICC (mA)
0.4 4.0V
0.3
3.3V
0.2
2.7V
0.1
1.8V
0
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0
Frequency ( MHz)
14
5.5V
12
5.0V
10
4.5V
ICC (mA)
8
4.0V
6
3.6V
4
2.7V
2
1.8V
0
0 5 10 15 20
Frequency (MHz)
0.14
0.12
0.10
105°C
ICC (mA)
0.08 85°C
0.06 25°C
- 40°C
0.04
0.02
0
1.5 1.8 2.1 2.4 2.7 3.0 3.3 3.6 3.9 4.2 4.5 4.8 5.1 5.4
VCC (V)
1.2
1.0
0.8 105°C
ICC (mA)
85°C
0.6
25°C
0.4
-40°C
0.2
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
Figure 35-53. ATmega168PB: Active Supply Current vs. VCC (Internal RC Oscillator, 8MHz)
4 105°C
85°C
ICC (mA)
3
25°C
2
-40°C
1
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
0.25
5.5V
0.20
5.0V
0.15 4.5V
ICC (mA)
4.0V
0.10
3.6V
0.05 2.7V
1.8V
0
0 0.2 0.4 0.6 0.8 1.0
Frequency (Mhz)
4.5
4.0 5.5V
3.5 5.0V
3.0
4.5V
ICC (mA)
2.5
4.0V
2.0
1.5 3.6V
1.0 2.7V
0.5
1.8V
0
0 5 10 15 20
Frequency (MHz)
ATmega168PB: Idle Supply Current vs. Vcc int RC, 128Khz)
Figure 35-56. ATmega168PB: Idle Supply Current vs. VCC (Internal RC Oscillator, 128kHz)
0.045
0.040
0.035
105°C
0.030
85°C
ICC (mA)
0.025
0.020 25°C
0.015
-40°C
0.010
0.005
0
1.5 2.5 3.5 4.5 5.5
VCC (V)
0.7
0.6
0.5
105°C
ICC (mA)
0.4
85°C
0.3
25°C
0.2
-40°C
0.1
0
1.5 2.5 3.5 4.5 5.5
VCC (V)
Figure 35-58. ATmega168PB: Idle Supply Current vs. VCC (Internal RC Oscillator, 8MHz)
2.0
1.8
1.6
1.4
105°C
ICC (mA)
1.2
85°C
1.0
0.8 25°C
0.6 -40°C
0.4
0.2
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
Table 35-4. ATmega168PB: Additional Current Consumption (percentage) in Active and Idle mode
(VCC = 2V, F = 1MHz)
It is possible to calculate the typical current consumption based on the numbers from the table above for
other VCC and frequency settings than listed in Table 35-3.
35.2.3.1 Example
Calculate the expected current consumption in idle mode with TIMER1, ADC, and SPI enabled at VCC =
2.0V and F = 1MHz. From the table above, third column, we need to add 8.91% for the TIMER1, 8.12%
for the ADC, and 7.96% for the SPI module. Reading fromFigure 35-54 , we find that the idle current
consumption is ~0.06 mA at VCC = 2.0V and F = 1MHz. The total current consumption in idle mode with
TIMER1, ADC, and SPI enabled, gives:
ICCtotal ≃ 0.06 mA⋅(1 + 0.0891 + 0.0812 + 0.0796) ≃ 0.075mA
3.5
3 Temp [°C]
105
2.5
85
Icc (uA)
25
2
-40
1.5
0.5
0
1.7 2.0 2.3 2.6 2.9 3.2 3.5 3.8 4.1 4.4 4.7 5.0 5.3 5.6
Vcc[V]
7
Temp [°C]
6 105
85
5
25
Icc (uA)
4 -40
0
1.7 2.0 2.3 2.6 2.9 3.2 3.5 3.8 4.1 4.4 4.7 5.0 5.3 5.6
Vcc [V]
4.5
105⁰C
4 25⁰C
3.5 -40⁰C
3 85⁰C
Icc (uA)
2.5
1.5
0.5
0
1.8 2.5 3 3.5 4 4.5 5 5.5
Vcc (V)
0.16
0.14
0.455 MHz - Res
0.12 1 MHz - Xtal
2 MHz - Res
0.1
2 MHz - Xtal
Icc (mA)
0.02
0
1.8 2.2 2.5 2.8 3.1 3.4 3.7 4 4.3 4.6 4.9 5.2 5.5
Vcc (V)
ATmega168PB: I/O Pin Pull up Resistor Current vs. Input Voltage (VCC = 1.8V)
35.2.7 Pin Pull-Up
Figure 35-63. ATmega168PB: I/O Pin Pull-up Resistor Current vs. Input Voltage (VCC = 1.8V)
0.07
0.06
0.05
IOP (mA)
0.04 105°C
0.03 85°C
0.02 25°C
0.01 -40°C
0.00
0.0 0.3 0.6 0.9 1.2 1.5 1.8
VOP (V)
Figure 35-64. ATmega168PB: I/O Pin Pull-up Resistor Current vs. Input Voltage (VCC = 2.7V)
0.12
0.10
0.08
105°C
IOP (mA)
0.06 85°C
0.04 25°C
0.02 -40°C
0.00
0.0 0.5 1.0 1.5 2.0 2.5 3.0
VOPCurrent
ATmega168PB: I/O Pin Pull up Resistor (V) vs. Input Voltage (VCC = 5V)
Figure 35-65. ATmega168PB: I/O Pin Pull-up Resistor Current vs. Input Voltage (VCC = 5V)
0.24
0.21
0.18
105°C
0.15
IOP (mA)
85°C
0.12
25°C
0.09
0.06 -40°C
0.03
0.00
0 1 2 3 4 5
VOP (V)
0.045
0.040
0.035
0.030
IRESET (mA)
105°C
0.025
0.020 85°C
0.015 25°C
0.010
-40°C
0.005
0.000
0.0 0.3 0.6 0.9 1.2 1.5 1.8
VRESET (V)
0.07
0.06
0.05
IRESET (mA)
0.04
105°C
0.03
85°C
0.02
25°C
0.01
-40°C
0.00
0.0 0.5 1.0 1.5 2.0 2.5 3.0
VRESET (V)
ATmega168PB: Reset Pull up Resistor Current vs. Reset Pin Voltage (VCC = 5V)
Figure 35-68. ATmega168PB: Reset Pull-up Resistor Current vs. Reset Pin Voltage (VCC = 5V)
0.14
0.12
0.10
IRESET (mA)
0.08 105°C
0.06 85°C
0.04 25°C
0.02 -40°C
0.00
0 1 2 3 4 5
VRESET (V)
1.2
105°C
1.0 85°C
0.8 25°C
VOL (V)
-40°C
0.6
0.4
0.2
0.0
0 5 10 15 20
IOL (mA)
ATmega168PB: I/O Pin Output Voltage vs. Sink Current (VCC = 5V)
Figure 35-70. ATmega168PB: I/O Pin Output Voltage vs. Sink Current (VCC = 5V)
0.7
105°C
0.6
85°C
0.5
25°C
-40°C
VOL (V)
0.4
0.3
0.2
0.1
0
0 5 10 15 20
IOL (mA)
Figure 35-71. ATmega168PB: I/O Pin Output Voltage vs. Source Current (VCC = 3V)
3.0
2.5
-40°C
2.0
25°C
VOH (V)
1.5 85°C
105°C
1.0
0.5
0.0
0 5 10 15 20
IOH (mA)
ATmega168PB I/O Pin Output Voltage vs. Source Current (VCC = 5V)
Figure 35-72. ATmega168PB I/O Pin Output Voltage vs. Source Current (VCC = 5V)
5.0
4.9
4.8
4.7
4.6
VOH (V)
4.5
4.4 -40°C
4.3 25°C
4.2 85°C
105°C
4.1
4.0
0 5 10 15 20
IOH (mA)
4.0
3.5 105°C
3.0 85°C
Threshold (V) 2.5
25°C
2.0
-40°C
1.5
1.0
0.5
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
ATmega168PB I/O Pin Output Voltage vs.Vcc(Vil I/O read as "0“)
VCC (V)
Figure 35-74. ATmega168PB I/O Pin Input Threshold Voltage vs. VCC (VIL, I/O Pin read as ‘0’)
2.5
-40°C
2.0
25°C
105°C
Threshold (V)
1.5 85°C
1.0
0.5
0.0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
1.4
-40°C
1.2
25°C
0.8 105°C
0.6
0.4
0.2
0.0
1.5 1.9 2.3 2.7 3.1 3.5 3.9 4.3 4.7 5.1 5.5
Vcc(V)
Mega168PB Input High Voltage VIH, RESET pin as I/O
Figure 35-76. ATmega168PB Reset Input Threshold Voltage vs. VCC (VIH, I/O Pin read as ‘1’)
3.0
105°C
2.5 85°C
25°C
2.0
Threshold (V)
-40°C
1.5
1.0
0.5
0.0
1.8 2.1 2.4 2.7 3.0 3.3 3.6 3.9 4.2 4.5 4.8 5.1 5.4 5.7 6.0
ATmega168PB Reset Input Threshold Voltage vs.Vcc Vil, I/O read as “0“)
VCC (V)
Figure 35-77. ATmega168PB Reset Input Threshold Voltage vs. VCC (VIL, I/O Pin read as ‘0’)
2.5
2.3
2.1
1.9 105°C
Threshold (V)
1.7 85°C
1.5 25°C
1.3
-40°C
1.1
0.9
0.7
0.5
1.8 2.2 2.6 3.0 3.4 3.8 4.2 4.6 5.0 5.4
VCC (V)
0.7
0.6
0.4 105°C
0.3
0.2 25°C
85°C
0.1 - 40°C
0.0
1.5 1.9 2.3 2.7 3.1 3.5 3.9 4.3 4.7 5.1 5.5
Vcc (V)
1.79
1.78
Rising
1.77
Threshold (mA)
1.76
1.75
1.74
Falling
1.73
1.72
-60 -40 -20 0 20 40 60 80 100 120
Temperature (°C)
2.76
2.74
Rising
2.72
Threshold (V)
2.70
2.68
2.66
Falling
2.64
2.62
- 60 -40 -20 0 20 40 60 80 100 120
MEGA168PB BOD LEVEL(°C)
Temperature AT 4.3V
4.42
4.40
Rising
4.38
4.36
Threshold
4.34
4.32
4.30
Falling
4.28
4.26
-60 -40 -20Calibrated
0 Bandgap
20 voltage
40vs. temperature
60 80 100 120
Temperature (°C)
1.125
5.5V
1.120
5.0V
4.5V
Bandg ap Voltage (V)
1.115
3.3V
1.110 3.0V
2.7V
1.105
1.8V
1.100
1.095
-50 -30 -10 10 30 50 70 90 110
Temperature (C)
1.125
1.120
105°C
1.115 85°C
1.105
1.100 -40°C
1.095
1.090
1.085
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
120
118
Vcc [V]
Frequency (KHz)
116
5.5
5
114 4.5
3.3
2.7
112
2.2
1.8
110
108
-40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 110
Temperature (C)
122
Temp [C]
120
105
118 85
Frequency (KHz)
25
116 -40
114
112
110
108
1.5 2 2.5 3 3.5 4 4.5 5 5.5
Vcc (V)
CALIBRATED 8MHz RC OSCILLATOR FREQUENCY vs. Vcc
Figure 35-86. ATmega168PB: Calibrated 8MHz RC Oscillator Frequency vs. VCC
8.5
8.4
8.3
8.2
105°C
8.1 85°C
F RC (MHz)
8.0 25°C
7.9
-40°C
7.8
7.7
7.6
7.5
1.8 2.3 2.8 3.3 3.8 4.3 4.8 5.3
VCC (V)
8.4
8.3
8.2 5.5V
8.1 5.0V
4.5V
F RC (MHz)
8.0
7.9 3.3V
7.8 3.0V
7.7
1.8V
7.6
7.5
-40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 110
Temperature (C)
20.0
105°C
18.0
16.0 85°C
14.0 25°C
FRC (MHz)
12.0
-40°C
10.0
8.0
6.0
4.0
2.0
0
0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256
OSCCAL (X1)
0.40
0.35
0.30
105°C
ICC (mA) 0.25
85°C
0.20
25°C
0.15
-40°C
0.10
0.05
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
Mega168PB AnalogVCC
Comparator
(V) Current vs. Vcc
0.16
0.14
0.12
105°C
0.10
ICC (mA)
85°C
0.08
25°C
0.06
-40°C
0.04
0.02
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
0.12
105°C
0.11
85°C
0.10
25°C
0.09
-40°C
0.08
ICC (mA) 0.07
0.06
0.05
0.04
0.03
0.02
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
Mega168PB Icc BOD vs. Vcc
0.035
0.030
0.025 105°C
ICC (mA)
0.020 85°C
0.015 25°C
0.010 -40°C
0.005
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
Programming vs Vcc
VCC (V)
10
7
105°C
6 85°C
Icc (mA)
5 25°C
4 -40°C
3
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
Vcc (V)
Figure 35-94. ATmega168PB: Reset Supply Current vs. Low Frequency (0.1MHz - 1.0MHz)
0.20
0.18 5.5V
0.16 5.0V
0.14 4.5V
0.12
ICC (mA) 4.0V
0.10
3.3V
0.08
0.06
1.8V
0.04
0.02
0.00
0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0
Frequency (MHz)
4.5
4.0
3.5
5.5V
3.0
5.0V
2.5
ICC (mA)
4.5V
2.0
4.0V
1.5
3.6V
1.0 2.7V
0.5 1.8V
0.0
0 2 4 6 8 10 12 14 16 18 20
Frequency (MHz)
3000
2500
105°C
Pulsewidth (nS)
2000
85°C
1500
25°C
1000
-40°C
500
0
1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
VCC (V)
0x23 PINB 7:0 PINB7 PINB6 PINB5 PINB4 PINB3 PINB2 PINB1 PINB0
0x24 DDRB 7:0 DDRB7 DDRB6 DDRB5 DDRB4 DDRB3 DDRB2 DDRB1 DDRB0
0x25 PORTB 7:0 PORTB7 PORTB6 PORTB5 PORTB4 PORTB3 PORTB2 PORTB1 PORTB0
0x26 PINC 7:0 PINC6 PINC5 PINC4 PINC3 PINC2 PINC1 PINC0
0x27 DDRC 7:0 DDRC6 DDRC5 DDRC4 DDRC3 DDRC2 DDRC1 DDRC0
0x28 PORTC 7:0 PORTC6 PORTC5 PORTC4 PORTC3 PORTC2 PORTC1 PORTC0
0x29 PIND 7:0 PIND7 PIND6 PIND5 PIND4 PIND3 PIND2 PIND1 PIND0
0x2A DDRD 7:0 DDRD7 DDRD6 DDRD5 DDRD4 DDRD3 DDRD2 DDRD1 DDRD0
0x2B PORTD 7:0 PORTD7 PORTD6 PORTD5 PORTD4 PORTD3 PORTD2 PORTD1 PORTD0
0x2C PINE 7:0 PINE3 PINE2 PINE1 PINE0
0x2D DDRE 7:0 DDRE3 DDRE2 DDRE1 DDRE0
0x2E PORTE 7:0 PORTE3 PORTE2 PORTE1 PORTE0
0x2F
... Reserved
0x34
0x35 TIFR0 7:0 OCF0B OCF0A TOV0
0x36 TIFR1 7:0 ICF1 OCF1B OCF1A TOV1
0x37 TIFR2 7:0 OCF2B OCF2A TOV2
0x38
... Reserved
0x3A
0x3B PCIFR 7:0 PCIF2 PCIF1 PCIF0
0x3C EIFR 7:0 INTF1 INTF0
0x3D EIMSK 7:0 INT1 INT0
0x3E GPIOR0 7:0 GPIOR0[7:0]
0x3F EECR 7:0 EEPM[1:0] EERIE EEMPE EEPE EERE
0x40 EEDR 7:0 EEDR[7:0]
0x41 7:0 EEAR[7:0]
EEARL and EEARH
0x42 15:8 EEAR[9:8]
0x43 GTCCR 7:0 TSM PSRASY PSRSYNC
0x44 TCCR0A 7:0 COM0A [1:0] COM0B [1:0] WGM0 1 WGM0 0
0x45 TCCR0B 7:0 FOC0A FOC0B WGM0 [2] CS0[2:0]
0x46 TCNT0 7:0 TCNT0[7:0]
0x47 OCR0A 7:0 OCR0A[7:0]
0x48 OCR0B 7:0 OCR0B[7:0]
0x49 Reserved
0x4A GPIOR1 7:0 GPIOR1[7:0]
0x4B GPIOR2 7:0 GPIOR2[7:0]
0x4C SPCR 7:0 SPIE SPE DORD MSTR CPOL CPHA SPR0 [1:0]
0x4D SPSR 7:0 SPIF WCOL SPI2X
0x4E SPDR 7:0 SPID[7:0]
0x4F ACSR0 7:0 ACOE
0x50 ACSR 7:0 ACD ACBG ACO ACI ACIE ACIC ACIS [1:0]
0x51 DWDR 7:0 DWDR[7:0]
0x52 Reserved
0x53 SMCR 7:0 SM[2:0] SE
0x54 MCUSR 7:0 WDRT BORF EXTRF PORF
0x55 MCUCR 7:0 BODS BODSE PUD IVSEL IVCE
0x56 Reserved
0x57 SPMCSR 7:0 SPMIE RWWSB SIGRD RWWSRE BLBSET PGWRT PGERS SPMEN
0x58
... Reserved
0x5C
0x5D 7:0 SP[7:0]
SPL and SPH
0x5E 15:8 SP[15:8]
0x5F SREG 7:0 I T H S V N Z C
0x60 WDTCSR 7:0 WDIF WDIE WDP [3] WDCE WDE WDP [2:0]
0x61 CLKPR 7:0 CLKPCE CLKPS [3:0]
0x62
... Reserved
0x63
0x64 PRR 7:0 PRTWI PRTIM2 PRTIM0 PRTIM1 PRSPI PRUSART PRADC
0x65 Reserved
0x66 OSCCAL 7:0 CAL [7:0]
0x67 Reserved
0x68 PCICR 7:0 PCIE2 PCIE1 PCIE0
0x69 EICRA 7:0 ISC1 [1:0] ISC0 [1:0]
0x6A Reserved
0x6B PCMSK0 7:0 PCINT 7 PCINT 6 PCINT 5 PCINT 4 PCINT 3 PCINT 2 PCINT 1 PCINT 0
0x6C PCMSK1 7:0 PCINT14 PCINT13 PCINT12 PCINT11 PCINT10 PCINT9 PCINT8
0x6D PCMSK2 7:0 PCINT23 PCINT22 PCINT21 PCINT20 PCINT19 PCINT18 PCINT17 PCINT16
0x6E TIMSK0 7:0 OCIE0B OCIE0A TOIE0
0x6F TIMSK1 7:0 ICIE1 OCIE1B OCIE1A TOIE1
0x70 TIMSK2 7:0 OCIE2B OCIE2A TOIE2
0x71
... Reserved
0x77
0x78 7:0 ADC[7:0]
ADCL and ADCH
0x79 15:8 ADC[9:8]
0x7A ADCSRA 7:0 ADEN ADSC ADATE ADIF ADIE ADPS [2:0]
0x7B ADCSRB 7:0 ACME ADTS [2:0]
0x7C ADMUX 7:0 REFS [1:0] ADLAR MUX [3:0]
0x7D Reserved
0x7E DIDR0 7:0 ADC7D ADC6D ADC5D ADC4D ADC3D ADC2D ADC1D ADC0D
0x7F DIDR1 7:0 AIN1D AIN0D
0x80 TCCR1A 7:0 COM1A[1:0] COM1B[1:0] WGM1[1:0]
0x81 TCCR1B 7:0 ICNC1 ICES1 WGM1[3] WGM1[2] CS1[2:0]
0x82 TCCR1C 7:0 FOC1A FOC1B
0x83 Reserved
0x84 TCNT1L and 7:0 TCNT1[7:0]
0x85 TCNT1H 15:8 TCNT1[15:8]
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
BRANCH INSTRUCTIONS
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
LPM Rd, Z+ Load Program Memory and Post-Inc Rd ← (Z), Z ← Z+1 None 3
PIN 1 IDENTIFIER
PIN 1 B
e
E1 E
D1
D
C 0°~7°
A1 A2 A
L
COMMON DIMENSIONS
(Unit of measure = mm)
2010-10-20
TITLE DRAWING NO. REV.
32A,32-lead, 7 x 7mm body size, 1.0mm body thickness,
32A C
0.8mm lead pitch, thin profile plastic quad flat package (TQFP)
D C
32 0.08 C
PIN 1 ID
2X 0.10 C
A3
2X 0.10 C
A1
BOTTOM VIEW A
L (32X)
D2
SEATING PLANE
0.10 C
e e/2
E2
COMMON DIMENSIONS
(Unit of Measure = mm)
2
Pin 1 Corner
A 0.80 - 0.90
32
K
See Option A,B
A1 0.00 - 0.05
Option A Option B PIN # 1 ID
b (32X)
A3 0.20 REF
PIN # 1 ID Notch
Chamfer (R 0.20)
(C 0.30)
12/4/13
TITLE GPC DRAWING NO. REV.
32MS1, 32-pad 5.0x5.0x0.9 mm Body, 0.50mm pitch, 3.1x3.1
Package Drawing Contact: mm Exposed pad, Saw Singulated Thermally Enhanced ZMF 32MS1 A
Plastic Very-thin Fine pitch, Quad Flat No Lead package
[email protected] (VFQFN)
39. Errata
39.1.1 Rev. A
– Wrong device ID when using debugWire
– Power consumption in power save modes
– USART start-up functionality not working
– External capacitor on AREF pin
– Increased power consumption when using voltage reference other than AVCC
1.) Wrong device ID when using debugWire
The device ID returned using debugWire is incorrect.
Problem Fix/Workaround
None.
2.) Power consumption in power save modes
Power consumption in power save modes will be higher due to improper control of internal power
management.
Problem Fix/Workaround
None.
3.) USART start-up functionality not working
While in power save modes, the USART start bit detection logic fails to wake up the device.
Problem Fix/Workaround
None.
4.) External capacitor on AREF pin
If an external capacitor is used on the analog reference pin (AREF), it should be equal to or larger than
100nF. Smaller capacitor value can make the AREF buffer unstable with large ringing which will reduce
the accuracy of the ADC.
Problem Fix/Workaround
None.
5. ) Increased power consumption when using voltage reference other than AVCC
Power consumption is higher when using internal or external voltage reference that is not equal to AVCC.
The increased current consumption will be the same for active and all sleep modes, but the largest
impact will be in low power sleep modes.
Problem Fix/Workaround
39.1.2 Rev. B
– External capacitor on AREF pin
– Power consumption in power save modes
– Increased power consumption when using voltage reference other than AVCC
1.) External capacitor on AREF pin
If an external capacitor is used on the analog reference pin (AREF), it should be equal to or larger than
100nF. Smaller capacitor value can make the AREF buffer unstable with large ringing which will reduce
the accuracy of the ADC.
Problem Fix/Workaround
None.
2.) Power consumption in power save modes
Power consumption in power save modes will be higher due to improper control of internal power
management.
Problem Fix/Workaround
None.
3. ) Increased power consumption when using voltage reference other than AVCC
Power consumption is higher when using internal or external voltage reference that is not equal to
AVCC.The increased current consumption will be the same for active and all sleep modes, but the largest
impact will be in low power sleep modes.
Problem Fix/Workaround
Select AVCC as ADC voltage reference before entering sleep mode to avoid extra power consumption
during sleep.If no internal or external reference to the ADC is used, an external pull-down resistor should
be added to the AREF pin.
39.1.3 Rev. C
No known errata.
39.1.4 Rev. D to J
Not sampled.
39.1.5 Rev. K
No known errata.
39.2.1 Rev. A
– Wrong device ID when using debugWire
– Power consumption in power save modes
39.2.2 Rev. B
– External capacitor on AREF pin
– Increased power consumption when using voltage reference other than AVCC
1.) External capacitor on AREF pin
If an external capacitor is used on the analog reference pin (AREF), it should be equal to or larger than
100nF. Smaller capacitor value can make the AREF buffer unstable with large ringing which will reduce
the accuracy of the ADC.
Problem Fix/Workaround
39.2.3 Rev. C
No known errata.
39.2.4 Rev. D to J
Not sampled.
39.2.5 Rev. K
No known errata.
39.3.1 Rev. A
– Wrong device ID when using debugWire
– Power consumption in power save modes
– USART start-up functionality not working
– External capacitor on AREF pin
– Increased power consumption when using voltage reference other than AVCC
1.) Wrong device ID when using debugWire
The device ID returned using debugWire is incorrect.
Problem Fix/Workaround
None.
2.) Power consumption in power save modes
Power consumption in power save modes will be higher due to improper control of internal power
management.
Problem Fix/Workaround
None
3.) USART start-up functionality not working
While in power save modes, the USART start bit detection logic fails to wakeup the device.
Problem Fix/Workaround
39.3.2 Rev. B
– Power consumption in power save modes
– External capacitor on AREF pin
– Increased power consumption when using voltage reference other than AVCC
1.) Power consumption in power save modes
Power consumption in power save modes will be higher due to improper control of internal power
management.
Problem Fix/Workaround
None
2.) External capacitor on AREF pin
If an external capacitor is used on the analog reference pin (AREF), it should be equal to or larger than
100nF. Smaller capacitor value can make the AREF buffer unstable with large ringing which will reduce
the accuracy of the ADC.
Problem Fix/Workaround
None.
3. ) Increased power consumption when using voltage reference other than AVCC
Power consumption is higher when using internal or external voltage reference that is not equal to AVCC.
The increased current consumption will be the same for active and all sleep modes, but the largest
impact will be in low power sleep modes.
Problem Fix/Workaround
Select AVCC as ADC voltage reference before entering sleep mode to avoid extra power consumption
during sleep. If no internal or external reference to the ADC is used, an external pull-down resistor should
be added to the AREF pin.
39.3.4 Rev. D to M
Not sampled.
39.3.5 Rev. N to O
No known errata.
6. Removed “Full Swing Crystal Oscillator” from the Table 10-1 on page 30.
7. Removed the section “Full Swing Crystal Oscillator”
8. Added ”Unique Device ID” on page 28
9. Update to correct addresses:
• “PORTE – The Port E Data Register” ,
• “DDRE – The Port E Data Direction Register” ,
• “PINE – The Port E Input Pins Address()”
11. Added ” Reading the Signature Row from Software” on page 277.
12. Updated typical values in ”ATmega48PB/88PB DC Characteristics” on page 304.
13. Updated ”ATmega48PB/88PB Typical Characteristics” on page 316.
• Added ”Power-save Supply Current” on page 323.
• Added ”Power-standby Supply Current” on page 323.
Microchip provides online support via our web site at http://www.microchip.com/. This web site is used as
a means to make files and information easily available to customers. Accessible by using your favorite
Internet browser, the web site contains the following information:
• Product Support – Data sheets and errata, application notes and sample programs, design
resources, user’s guides and hardware support documents, latest software releases and archived
software
• General Technical Support – Frequently Asked Questions (FAQ), technical support requests,
online discussion groups, Microchip consultant program member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip press releases,
listing of seminars and events, listings of Microchip sales offices, distributors and factory
representatives
Microchip’s customer notification service helps keep customers current on Microchip products.
Subscribers will receive e-mail notification whenever there are changes, updates, revisions or errata
related to a specified product family or development tool of interest.
To register, access the Microchip web site at http://www.microchip.com/. Under “Support”, click on
“Customer Change Notification” and follow the registration instructions.
Customer Support
Note the following details of the code protection feature on Microchip devices:
• Microchip products meet the specification contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is one of the most secure families of its kind on the
market today, when used in the intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of
these methods, to our knowledge, require using the Microchip products in a manner outside the
operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is
engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
Legal Notice
Information contained in this publication regarding device applications and the like is provided only for
your convenience and may be superseded by updates. It is your responsibility to ensure that your
application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR
WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY
OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS
CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE.
Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life
support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend,
indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting
from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual
property rights unless otherwise stated.
Trademarks
The Microchip name and logo, the Microchip logo, AnyRate, AVR, AVR logo, AVR Freaks, BeaconThings,
BitCloud, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KeeLoq, KeeLoq logo,
Kleer, LANCheck, LINK MD, maXStylus, maXTouch, MediaLB, megaAVR, MOST, MOST logo, MPLAB,
OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, Prochip Designer, QTouch, RightTouch, SAM-BA,
SpyNIC, SST, SST Logo, SuperFlash, tinyAVR, UNI/O, and XMEGA are registered trademarks of
Microchip Technology Incorporated in the U.S.A. and other countries.
ClockWorks, The Embedded Control Solutions Company, EtherSynch, Hyper Speed Control, HyperLight
Load, IntelliMOS, mTouch, Precision Edge, and Quiet-Wire are registered trademarks of Microchip
Technology Incorporated in the U.S.A.
Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, BodyCom,
chipKIT, chipKIT logo, CodeGuard, CryptoAuthentication, CryptoCompanion, CryptoController,
dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, EtherGREEN, In-Circuit Serial
Programming, ICSP, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, Mindi, MiWi,
motorBench, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient
Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PureSilicon, QMatrix, RightTouch logo, REAL
ICE, Ripple Blocker, SAM-ICE, Serial Quad I/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II, Total
Endurance, TSHARC, USBCheck, VariSense, ViewSpan, WiperLock, Wireless DNA, and ZENA are
trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.
Silicon Storage Technology is a registered trademark of Microchip Technology Inc. in other countries.
GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of
Microchip Technology Inc., in other countries.
All other trademarks mentioned herein are property of their respective companies.
© 2017, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.
ISO/TS 16949
Microchip received ISO/TS-16949:2009 certification for its worldwide headquarters, design and wafer
fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California
® ®
and India. The Company’s quality system processes and procedures are for its PIC MCUs and dsPIC
®
DSCs, KEELOQ code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’s quality system for the design and manufacture of development
systems is ISO 9001:2000 certified.