At Mega 163
At Mega 163
At Mega 163
Rev. 1142E–AVR–02/03
1
Pin Configurations
(SDA)
(SCL)
(SDA)
(SCL)
2 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Description The ATmega163 is a low-power CMOS 8-bit microcontroller based on the AVR architec-
ture. By executing powerful instructions in a single clock cycle, the ATmega163
achieves throughputs approaching 1 MIPS per MHz allowing the system designer to
optimize power consumption versus processing speed.
VCC
GND
DATA REGISTER DATA DIR. DATA REGISTER DATA DIR.
PORTA REG. PORTA PORTC REG. PORTC
AVCC
INTERNAL
REFERENCE INTERNAL
OSCILLATOR
OSCILLATOR
XTAL2
PROGRAM STACK WATCHDOG TIMING AND
RESET
COUNTER POINTER TIMER CONTROL
X
INSTRUCTION INTERRUPT
Y
DECODER UNIT
Z
CONTROL
LINES ALU EEPROM
INTERNAL
STATUS CALIBRATED
REGISTER OSCILLATOR
PROGRAMMING
SPI UART
LOGIC
COMPARATOR
ANALOG
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
3
1142E–AVR–02/03
cycle. The resulting architecture is more code efficient while achieving throughputs up to
ten times faster than conventional CISC microcontrollers.
The ATmega163 provides the following features: 16K bytes of In-System Self-Program-
mable Flash, 512 bytes EEPROM, 1024 bytes SRAM, 32 general purpose I/O lines, 32
general purpose working registers, three flexible Timer/Counters with compare modes,
internal and external interrupts, a byte oriented Two-wire Serial Interface, an 8-channel,
10-bit ADC, a programmable Watchdog Timer with internal Oscillator, a programmable
serial UART, an SPI serial port, and four software selectable power saving modes. The
Idle mode stops the CPU while allowing the SRAM, Timer/Counters, SPI port, and inter-
rupt 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 Oscillator 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 asynchro-
nous timer and ADC, to minimize switching noise during ADC conversions.
The On-chip ISP Flash can be programmed through an SPI serial interface or a conven-
tional programmer. By installing a Self-Programming Boot Loader, the microcontroller
can be updated within the application without any external components. The Boot Pro-
gram can use any interface to download the application program in the Application Flash
memory. By combining an 8-bit CPU with In-System Self-Programmable Flash on a
monolithic chip, the Atmel ATmega163 is a powerful microcontroller that provides a
highly flexible and cost effective solution to many embedded control applications.
The ATmega163 AVR is supported with a full suite of program and system development
tools including: C compilers, macro assemblers, program debugger/simulators, In-Cir-
cuit Emulators, and evaluation kits.
Pin Descriptions
Port A (PA7..PA0) Port A serves as the analog inputs to the A/D Converter.
Port A also serves as an 8-bit bi-directional I/O port, if the A/D Converter is not used.
Port pins can provide internal pull-up resistors (selected for each bit). The Port A output
buffers can sink 20mA and can drive LED displays directly. When pins PA0 to PA7 are
used as inputs and are externally pulled low, they will source current if the internal pull-
up resistors are activated. The Port A pins are tristated when a reset condition becomes
active, even if the clock is not running.
Port B (PB7..PB0) Port B is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each
bit). The Port B output buffers can sink 20 mA. As inputs, Port B pins that are externally
pulled low will source current if the pull-up resistors are activated. Port B also serves the
functions of various special features of the ATmega83/163 as listed on page 117. The
Port B pins are tristated when a reset condition becomes active, even if the clock is not
running.
Port C (PC7..PC0) Port C is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each
bit). The Port C output buffers can sink 20 mA. As inputs, Port C pins that are externally
pulled low will source current if the pull-up resistors are activated. The Port C pins are
tristated when a reset condition becomes active, even if the clock is not running.
4 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Port C also serves the functions of various special features of the ATmega163 as listed
on page 124.
Port D (PD7..PD0) Port D is an 8-bit bidirectional I/O port with internal pull-up resistors (selected for each
bit). The Port D output buffers can sink 20 mA. As inputs, Port D pins that are externally
pulled low will source current if the pull-up resistors are activated. Port D also serves the
functions of various special features of the ATmega163 as listed on page 128. The Port
D pins are tristated when a reset condition becomes active, even if the clock is not
running.
RESET Reset input. A low level on this pin for more than 500 ns will generate a Reset, even if
the clock is not running. Shorter pulses are not guaranteed to generate a Reset.
XTAL1 Input to the inverting Oscillator amplifier and input to the internal clock operating circuit.
AVCC This is the supply voltage pin for Port A and the A/D Converter. It should be externally
connected to VCC, even if the ADC is not used. If the ADC is used, it should be con-
nected to VCC through a low-pass filter. See page 105 for details on operation of the
ADC.
AREF AREF is the analog reference input pin for the A/D Converter. For ADC operations, a
voltage in the range 2.5V to AVCC can be applied to this pin.
AGND Analog ground. If the board has a separate analog ground plane, this pin should be con-
nected to this ground plane. Otherwise, connect to GND.
Clock Options The device has the following clock source options, selectable by Flash Fuse bits as
shown:
Internal RC Oscillator The internal RC Oscillator option is an On-chip Oscillator running at a fixed frequency of
nominally 1 MHz. If selected, the device can operate with no external components. The
device is shipped with this option selected. See “EEPROM Read/Write Access” on page
62 for information on calibrating this Oscillator.
5
1142E–AVR–02/03
Crystal Oscillator XTAL1 and XTAL2 are input and output, respectively, of an inverting amplifier which can
be configured for use as an On-chip Oscillator, as shown in Figure 2. Either a quartz
crystal or a ceramic resonator may be used.
External Clock To drive the device from an external clock source, XTAL1 should be driven as shown in
Figure 3.
External RC Oscillator For timing insensitive applications, the external RC configuration shown in Figure 4 can
be used. For details on how to choose R and C, see Table 64 on page 162.
R NC XTAL2
XTAL1
C
GND
Timer Oscillator For the Timer Oscillator pins, TOSC1 and TOSC2, the crystal is connected directly
between the pins. No external capacitors are needed. The Oscillator is optimized for use
with a 32,768 Hz watch crystal. Applying an external clock source to the TOSC1 pin is
not recommended.
6 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Architectural The fast-access Register File concept contains 32 x 8-bit general purpose working reg-
isters with a single clock cycle access time. This means that during one single clock
Overview
cycle, one Arithmetic Logic Unit (ALU) operation is executed. 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-bits indirect address register pointers for
Data Space addressing – enabling efficient address calculations. One of the three
address pointers is also used as the address pointer for look-up tables in Flash Program
memory. These added function registers are the 16-bits X-, Y-, and Z-register.
The ALU supports arithmetic and logic operations between registers or between a con-
stant and a register. Single register operations are also executed in the ALU. Figure 5
shows the ATmega163 AVR Enhanced RISC microcontroller architecture.
In addition to the register operation, the conventional Memory Addressing modes can be
used on the Register File as well. This is enabled by the fact that the Register File is
assigned the 32 lowest Data Space addresses ($00 - $1F), allowing them to be
accessed as though they were ordinary memory locations.
The I/O Memory space contains 64 addresses for CPU peripheral functions as Control
Registers, Timer/Counters, A/D-converters, and other I/O functions. The I/O Memory
can be accessed directly, or as the Data Space locations following those of the Register
File, $20 - $5F.
7
1142E–AVR–02/03
Figure 5. The ATmega163 AVR RISC Architecture
32 x 8 Serial
Instruction General UART
Register Purpose
Registrers
Two-wire Serial
Interface
Instruction
Decoder
Indirect Addressing
8-bit
Direct Addressing
Timer/Counter
ALU
Control Lines 16-bit
Timer/Counter
with PWM
8-bit
Timer/Counter
1024 x 8 with PWM
Data
SRAM Watchdog
Timer
512 x 8
EEPROM A/D Converter
32 Analog
I/O Lines Comparator
The AVR uses a Harvard architecture concept – with separate memories and buses for
program and data. The Program memory is executed with a two stage pipeline. 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 Re-programmable Flash memory.
With the jump and call instructions, the whole 8K word address space is directly
accessed. Most AVR instructions have a single 16-bit word format. Every program
memory address contains a 16- or 32-bit instruction.
Program Flash memory space is divided in two sections, the Boot Program section (256
to 2,048 bytes, see page 134) and the Application Program section. Both sections have
dedicated Lock bits for write and read/write protection. The SPM instruction that writes
into the Application Flash memory section is allowed only in the Boot Program section.
During interrupts and subroutine calls, the return address Program Counter (PC) is
stored on the Stack. The Stack is effectively allocated in the general data SRAM, and
consequently the Stack size is only limited by the total SRAM size and the usage of the
SRAM. All user programs must initialize the SP in the reset routine (before subroutines
or interrupts are executed). The 11-bit Stack Pointer SP is read/write accessible in the
I/O space.
8 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
The 1,024 bytes data SRAM can be easily accessed through the five different address-
ing modes supported in the AVR architecture.
The memory spaces in the AVR architecture are all linear and regular memory maps.
A flexible interrupt module has its Control Registers in the I/O space with an additional
Global Interrupt Enable bit in the Status Register. All interrupts have a separate Interrupt
Vector in the Interrupt Vector table at the beginning of the Program memory. The inter-
rupts have priority in accordance with their Interrupt Vector position. The lower the
Interrupt Vector address, the higher the priority.
$0000
9
1142E–AVR–02/03
The General Purpose Figure 7 shows the structure of the 32 general purpose working registers in the CPU.
Register File
Figure 7. AVR CPU General Purpose Working Registers
7 0 Addr.
R0 $00
R1 $01
R2 $02
…
R13 $0D
General R14 $0E
Purpose R15 $0F
Working R16 $10
Registers R17 $11
…
R26 $1A X-register Low Byte
R27 $1B X-register High Byte
R28 $1C Y-register Low Byte
R29 $1D Y-register High Byte
R30 $1E Z-register Low Byte
R31 $1F Z-register High Byte
All the register operating instructions in the instruction set have direct and single cycle
access to all registers. The only exception is the five constant arithmetic and logic
instructions SBCI, SUBI, CPI, ANDI, and ORI between a constant and a register, and
the LDI instruction for load immediate constant data. These instructions apply to the
second half of the registers in the Register File – R16..R31. The general SBC, SUB, CP,
AND, and OR and all other operations between two registers or on a single register
apply to the entire Register File.
As shown in Figure 7, each register is also assigned a data memory address, mapping
them directly into the first 32 locations of the user Data Space. Although not being phys-
ically implemented as SRAM locations, this memory organization provides great
flexibility in access of the registers, as the X-, Y-, and Z-registers can be set to index any
register in the file.
The X-register, Y-register, and The registers R26..R31 have some added functions to their general purpose usage.
Z-register These registers are address pointers for indirect addressing of the Data Space. The
three indirect address registers X, Y, and Z are defined as:
15 XH XL 0
X - register 7 0 7 0
R27 ($1B) R26 ($1A)
15 YH YL 0
Y - register 7 0 7 0
R29 ($1D) R28 ($1C)
15 ZH ZL 0
Z - register 7 0 7 0
R31 ($1F) R30 ($1E)
10 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
In the different addressing modes these address registers have functions as fixed dis-
placement, automatic increment and decrement (see the descriptions for the different
instructions).
The ALU – Arithmetic The high-performance AVR ALU operates in direct connection with all the 32 general
Logic Unit purpose working registers. Within a single clock cycle, ALU operations between regis-
ters in the Register File are executed. The ALU operations are divided into three main
categories – arithmetic, logical, and bit-functions. ATmega163 also provides a powerful
multiplier supporting both signed/unsigned multiplication and fractional format. See the
Instruction Set section for a detailed description.
The In-System Self- The ATmega163 contains 16K bytes On-chip In-System Self-Programmable Flash
Programmable Flash memory for program storage. Since all instructions are 16- or 32-bit words, the Flash is
Program Memory organized as 8K x 16. The Flash Program memory space is divided in two sections,
Boot Program section and Application Program section.
The Flash memory has an endurance of at least 1,000 write/erase cycles. The
ATmega163 Program Counter (PC) is 13 bits wide, thus addressing the 8,192 Program
Memory locations. The operation of Boot Program section and associated Boot Lock
bits for software protection are described in detail on page 134. See also page 154 for a
detailed description on Flash data serial downloading.
Constant tables can be allocated within the entire Program Memory address space (see
the LPM – Load Program Memory instruction description).
See also page 12 for the different Program Memory Addressing modes.
The SRAM Data Memory Figure 9 shows how the ATmega163 SRAM Memory is organized.
R29 $001D
R30 $001E
R31 $001F
I/O Registers
$00 $0020
$01 $0021
$02 $0022
... ...
$3D $005D
$3E $005E
$3F $005F
Internal SRAM
$0060
$0061
...
$045E
$045F
11
1142E–AVR–02/03
The lower 1,120 Data Memory locations address the Register File, the I/O Memory, and
the internal data SRAM. The first 96 locations address the Register File + I/O Memory,
and the next 1,024 locations address the internal data SRAM.
The five different addressing modes for the data memory cover: Direct, Indirect with Dis-
placement, Indirect, Indirect with Pre-decrement, and Indirect with Post-increment. In
the Register File, registers R26 to R31 feature the indirect Addressing Pointer
Registers.
The direct addressing reaches the entire data space.
The Indirect with Displacement mode features a 63 address locations reach from the
base address given by the Y- or Z-register.
When using register indirect addressing modes with automatic pre-decrement and post-
increment, the address registers X, Y, and Z are decremented and incremented.
The 32 general purpose working registers, 64 I/O Registers, and the 1,024 bytes of
internal data SRAM in the ATmega163 are all accessible through all these addressing
modes.
The Program and Data The ATmega163 AVR Enhanced RISC microcontroller supports powerful and efficient
Addressing Modes addressing modes for access to the Program Memory (Flash) and Data Memory
(SRAM, Register File, and I/O Memory). This section describes the different addressing
modes supported by the AVR architecture. In the figures, OP means the operation code
part of the instruction word. To simplify, not all figures show the exact location of the
addressing bits.
12 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Register Direct, Two Registers Figure 11. Direct Register Addressing, Two Registers
Rd And Rr
Operands are contained in register r (Rr) and d (Rd). The result is stored in register d
(Rd).
$045F
13
1142E–AVR–02/03
Data Indirect with Figure 14. Data Indirect with Displacement
Displacement
Data Space
$0000
15 0
Y OR Z - REGISTER
15 10 6 5 0
OP n a
$045F
Operand address is the result of the Y- or Z-register contents added to the address con-
tained in 6 bits of the instruction word.
$045F
Data Indirect with Pre- Figure 16. Data Indirect Addressing with Pre-decrement
decrement Data Space
$0000
15 0
X, Y OR Z - REGISTER
-1
$045F
The X-, Y-, or the Z-register is decremented before the operation. Operand address is
the decremented contents of the X-, Y-, or the Z-register.
14 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Data Indirect with Post- Figure 17. Data Indirect Addressing with Post-increment
increment Data Space
$0000
15 0
X, Y OR Z - REGISTER
$045F
The X-, Y-, or the Z-register is incremented after the operation. Operand address is the
content of the X-, Y-, or the Z-register prior to incrementing.
$1FFF
Constant byte address is specified by the Z-register contents. The 15 MSBs select word
address (0 - 8K). For LPM, the LSB selects Low Byte if cleared (LSB = 0) or High Byte if
set (LSB = 1). For SPM, the LSB should be cleared.
$1FFF
15
1142E–AVR–02/03
Relative Program Addressing, Figure 20. Relative Program Memory Addressing
RJMP and RCALL
$1FFF
The EEPROM Data The ATmega163 contains 512 bytes of data EEPROM memory. It is organized as a sep-
Memory arate data space, in which single bytes can be read and written. The EEPROM has an
endurance of at least 100,000 write/erase cycles. The access between the EEPROM
and the CPU is described on page 62 specifying the EEPROM Address Registers, the
EEPROM Data Register, and the EEPROM Control Register.
For the SPI data downloading, see page 154 for a detailed description.
Memory Access Times This section describes the general access timing concepts for instruction execution and
and Instruction internal memory access.
Execution Timing The AVR CPU is driven by the System Clock Ø, directly generated from the main Oscil-
lator for the chip. No internal clock division is used.
Figure 21 shows the parallel instruction fetches and instruction executions enabled by
the Harvard architecture and the fast-access Register File concept. This is the basic
pipelining concept to obtain up to 1 MIPS per MHz with the corresponding unique results
for functions per cost, functions per clocks, and functions per power-unit.
System Clock Ø
Figure 22 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.
16 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
System Clock Ø
The internal data SRAM access is performed in two System Clock cycles as described
in Figure 23.
System Clock Ø
Data
Write
WR
Data
Read
RD
I/O Memory The I/O space definition of the ATmega163 is shown in the following table:
17
1142E–AVR–02/03
Table 2. ATmega163 I/O Space (Continued) (1)
I/O Address
(SRAM Address) Name Function
$32 ($52) TCNT0 Timer/Counter0 (8-bit)
$31 ($51) OSCCAL Oscillator Calibration Register
$30 ($50) SFIOR Special Function I/O Register
$2F ($4F) TCCR1A Timer/Counter1 Control Register A
$2E ($4E) TCCR1B Timer/Counter1 Control Register B
$2D ($4D) TCNT1H Timer/Counter1 High-byte
$2C ($4C) TCNT1L Timer/Counter1 Low-byte
$2B ($4B) OCR1AH Timer/Counter1 Output Compare Register A High-byte
$2A ($4A) OCR1AL Timer/Counter1 Output Compare Register A Low-byte
$29 ($49) OCR1BH Timer/Counter1 Output Compare Register B High-byte
$28 ($48) OCR1BL Timer/Counter1 Output Compare Register B Low-byte
$27 ($47) ICR1H T/C 1 Input Capture Register High-byte
$26 ($46) ICR1L T/C 1 Input Capture Register Low-byte
$25 ($45) TCCR2 Timer/Counter2 Control Register
$24 ($44) TCNT2 Timer/Counter2 (8-bit)
$23 ($43) OCR2 Timer/Counter2 Output Compare Register
$22 ($42) ASSR Asynchronous Mode Status Register
$21 ($41) WDTCR Watchdog Timer Control Register
$20 ($40) UBRRHI UART Baud Rate Register High-byte
$1F ($3F) EEARH EEPROM Address Register High-byte
$1E ($3E) EEARL EEPROM Address Register Low-byte
$1D ($3D) EEDR EEPROM Data Register
$1C ($3C) EECR EEPROM Control Register
$1B ($3B) PORTA Data Register, Port A
$1A ($3A) DDRA Data Direction Register, Port A
$19 ($39) PINA Input Pins, Port A
$18 ($38) PORTB Data Register, Port B
$17 ($37) DDRB Data Direction Register, Port B
$16 ($36) PINB Input Pins, Port B
$15 ($35) PORTC Data Register, Port C
$14 ($34) DDRC Data Direction Register, Port C
$13 ($33) PINC Input Pins, Port C
$12 ($32) PORTD Data Register, Port D
$11 ($31) DDRD Data Direction Register, Port D
$10 ($30) PIND Input Pins, Port D
18 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
19
1142E–AVR–02/03
The Status Register – SREG The AVR Status Register – SREG – at I/O space location $3F ($5F) is defined as:
Bit 7 6 5 4 3 2 1 0
$3F ($5F) I T H S V N Z C SREG
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
20 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
The Stack Pointer – SP The ATmega163 Stack Pointer is implemented as two 8-bit registers in the I/O space
locations $3E ($5E) and $3D ($5D). As the ATmega163 data memory has $460 loca-
tions, 11 bits are used.
Bit 15 14 13 12 11 10 9 8
$3E ($5E) – – – – – SP10 SP9 SP8 SPH
$3D ($5D) SP7 SP6 SP5 SP4 SP3 SP2 SP1 SP0 SPL
7 6 5 4 3 2 1 0
Read/Write R R R R R R/W R/W R/W
R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
The Stack Pointer points to the data SRAM Stack area where the Subroutine and Inter-
rupt Stacks are located. This Stack space in the data SRAM must be defined by the
program before any subroutine calls are executed or interrupts are enabled. The Stack
Pointer must be set to point above $60. The Stack Pointer is decremented by one when
data is pushed onto the Stack with the PUSH instruction, and it is decremented by two
when the return address is pushed onto the Stack with subroutine call and interrupt. The
Stack Pointer is incremented by one when data is popped from the Stack with the POP
instruction, and it is incremented by two when data is popped from the Stack with return
from subroutine RET or return from interrupt RETI.
Reset and Interrupt The ATmega163 provides 17 different interrupt sources. These interrupts and the sepa-
Handling rate Reset Vector, each have a separate Program Vector in the Program Memory
space. All interrupts are assigned individual enable bits which must be set (one)
together with the I-bit in the Status Register in order to enable the interrupt.
The lowest addresses in the Program Memory space are automatically defined as the
Reset and Interrupt Vectors. The complete list of vectors is shown in Table 3. The list
also determines the priority levels of the different interrupts. The lower the address the
higher is the priority level. RESET has the highest priority, and next is INT0 – the Exter-
nal Interrupt Request 0, etc.
21
1142E–AVR–02/03
Table 3. Reset and Interrupt Vectors (Continued)
Program
Vector No. Address Source Interrupt Definition
13 $018 UART, UDRE UART Data Register Empty
14 $01A UART, TXC UART, Tx Complete
15 $01C ADC ADC Conversion Complete
16 $01E EE_RDY EEPROM Ready
17 $020 ANA_COMP Analog Comparator
18 $022 TWI Two-wire Serial Interface
Note: 1. When the BOOTRST Fuse is programmed, the device will jump to the Boot Loader
address at reset, see “Boot Loader Support” on page 134.
The most typical and general program setup for the Reset and Interrupt Vector
Addresses in ATmega163 is:
22 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
When the BOOTRST Fuse is programmed and the Boot section size set to 512 bytes,
the most typical and general program setup for the Reset and Interrupt Vector
Addresses in ATmega163 is:
23
1142E–AVR–02/03
Figure 24. Reset Logic
DATA BUS
MCU Status
Register (MCUSR)
PORF
BORF
EXTRF
WDRF
Power-on
VCC Reset Circuit
Brown-out
BODEN
BODLEVEL Reset Circuit
Internal Reset
100-500kW
SPIKE
RESET FILTER
Reset Circuit
Counter Reset
Watchdog
Timer
On-chip
RC Oscillator
CKSEL[3:0]
24 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Notes: 1. On power-up, the start-up time is increased with typ. 0.6 ms.
2. “1” means unprogrammed, “0” means programmed.
3. For possible clock selections, see “Clock Options” on page 5.
4. When BODEN is programmed, add 100 µs.
5. When BODEN is programmed, add 25 µs.
6. Default value.
Table 5 shows the Start-up Times from Reset. When the CPU wakes up from Power-
down or Power-save, only the clock counting part of the start-up time is used. The
Watchdog Oscillator is used for timing the real time part of the start-up time. The number
of WDT Oscillator cycles used for each time-out is shown in Table 6.
The frequency of the Watchdog Oscillator is voltage dependent as shown in the Electri-
cal Characteristics section. The device is shipped with CKSEL = “0010” (Int. RC
Oscillator, slowly rising power).
25
1142E–AVR–02/03
Table 6. Number of Watchdog Oscillator Cycles(1)
BODLEVEL VCC Condition Time-out Number of Cycles
Unprogrammed 2.7V 30 µs 8
Unprogrammed 2.7V 130 µs 32
Unprogrammed 2.7V 4.2 ms 1K
Unprogrammed 2.7V 67 ms 16K
Programmed 4.0V 10 µs 8
Programmed 4.0V 35 µs 32
Programmed 4.0V 5.8 ms 4K
Programmed 4.0V 92 ms 64K
Note: 1. The Bodlevel Fuse can be used to select start-up times even if the Brown-out Detec-
tion is disabled (BODEN Fuse unprogrammed).
Power-on Reset A Power-on Reset (POR) pulse is generated by an On-chip detection circuit. The detec-
tion level is defined in Table 4. The POR is activated whenever V CC is below the
detection level. The POR circuit can be used to trigger the Start-up Reset, as well as to
detect a failure in supply voltage.
A Power-on Reset (POR) circuit ensures that the device is reset from Power-on. Reach-
ing the Power-on Reset threshold voltage invokes a delay counter, which determines
the delay, for which the device is kept in RESET after VCC rise. The Time-out Period of
the delay counter can be defined by the user through the CKSEL Fuses. The different
selections for the delay period are presented in Table 5. The RESET signal is activated
again, without any delay, when the VCC decreases below detection level.
VRST
RESET
tTOUT
TIME-OUT
INTERNAL
RESET
26 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
VRST
RESET
tTOUT
TIME-OUT
INTERNAL
RESET
External Reset An External Reset is generated by a low level on the RESET pin. Reset pulses longer
than 500 ns will generate a Reset, even if the clock is not running. Shorter pulses are
not guaranteed to generate a Reset. When the applied signal reaches the Reset
Threshold Voltage – VRST on its positive edge, the delay timer starts the MCU after the
Time-out Period tTOUT has expired.
Brown-out Detection ATmega163 has an On-chip Brown-out Detection (BOD) circuit for monitoring the VCC
level during the operation. The BOD circuit can be enabled/disabled by the fuse
BODEN. When the BOD is enabled (BODEN programmed), and VCC decreases to a
value below the trigger level, the Brown-out Reset is immediately activated. When VCC
increases above the trigger level, the Brown-out Reset is deactivated after a delay. The
delay is defined by the user in the same way as the delay of POR signal, in Table 5. The
trigger level for the BOD can be selected by the fuse BODLEVEL to be 2.7V
(BODLEVEL unprogrammed), or 4.0V (BODLEVEL programmed). The trigger level has
a hysteresis of 50 mV to ensure spike free Brown-out Detection.
The BOD circuit will only detect a drop in VCC if the voltage stays below the trigger level
for longer than 9 µs for trigger level 4.0V, 21 µs for trigger level 2.7V (typical values).
27
1142E–AVR–02/03
Figure 28. Brown-out Reset During Operation
VCC VBOT+
VBOT-
RESET
TIME-OUT tTOUT
INTERNAL
RESET
Watchdog Reset When the Watchdog times out, it will generate a short reset pulse of 1 XTAL cycle dura-
tion. On the falling edge of this pulse, the delay timer starts counting the Time-out Period
tTOUT. Refer to page 60 for details on operation of the Watchdog Timer.
1 CK Cycle
MCU Status Register – The MCU Status Register provides information on which reset source caused an MCU
MCUSR Reset.
Bit 7 6 5 4 3 2 1 0
$34 ($54) – – – – WDRF BORF EXTRF PORF MCUSR
Read/Write R R R R R/W R/W R/W R/W
Initial Value 0 0 0 0 See Bit Description
28 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Internal Voltage Reference ATmega163 features an internal bandgap reference with a nominal voltage of 1.22V.
This reference is used for Brown-out Detection, and it can be used as an input to the
Analog Comparator and ADC. The 2.56V reference to the ADC is also generated from
the internal bandgap reference.
Voltage Reference Enable To save power, the reference is not always turned on. The reference is on during the fol-
Signals and Start-up Time lowing situations:
1. When the BOD is enabled (by programming the BODEN Fuse)
2. When the bandgap reference is connected to the Analog Comparator (by setting
the ACBG bit in ACSR).
3. When the ADC is enabled.
Thus, when the BOD is not enabled, after setting the ACBG bit, the user must always
allow the reference to start up before the output from the Analog Comparator is used.
The bandgap reference uses typically 10 µA, and to reduce power consumption in
Power-down mode, the user can avoid the three conditions above to ensure that the ref-
erence is turned off before entering Power-down mode.
Interrupt Handling The ATmega163 has two 8-bit Interrupt Mask Control Registers: GIMSK – General
Interrupt Mask Register and TIMSK – Timer/Counter Interrupt Mask Register.
When an interrupt occurs, the Global Interrupt Enable I-bit is cleared (zero) and all inter-
rupts are disabled. The user software must set (one) the I-bit to enable nested
interrupts. The I-bit is set (one) when a Return from Interrupt instruction – RETI – is
executed.
When the Program Counter is vectored to the actual Interrupt Vector in order to execute
the interrupt handling routine, hardware clears the corresponding flag that generated the
interrupt. Some of the interrupt flags can also be cleared by writing a logic one to the flag
bit position(s) to be cleared.
If an interrupt condition occurs when the corresponding interrupt enable bit is cleared
(zero), the Interrupt Flag will be set and remembered until the interrupt is enabled, or the
flag is cleared by software.
29
1142E–AVR–02/03
If one or more interrupt conditions occur when the Global Interrupt Enable bit is cleared
(zero), the corresponding interrupt flag(s) will be set and remembered until the Global
Interrupt Enable bit is set (one), and will be executed by order of priority.
Note that external level interrupt does not have a flag, and will only be remembered for
as long as the interrupt condition is present.
Note that the Status Register is not automatically stored when entering an interrupt rou-
tine and restored when returning from an interrupt routine. This must be handled by
software.
Interrupt Response Time The interrupt execution response for all the enabled AVR interrupts is four clock cycles
minimum. After four clock cycles the Program Vector address for the actual interrupt
handling routine is executed. During this four clock cycle period, the Program Counter
(13 bits) is pushed onto the Stack. The vector is normally a jump to the interrupt routine,
and this jump takes three clock cycles. If an interrupt occurs during execution of a multi-
cycle instruction, this instruction is completed before the interrupt is served. If an inter-
rupt occurs when the MCU is in sleep mode, the interrupt execution response time is
increased by four clock cycles.
A return from an interrupt handling routine takes four clock cycles. During these four
clock cycles, the Program Counter (two bytes) is popped back from the Stack, the Stack
Pointer is incremented by two, and the I Flag in SREG is set. When AVR exits from an
interrupt, it will always return to the main program and execute one more instruction
before any pending interrupt is served.
30 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
31
1142E–AVR–02/03
(at vector $00A) is executed if a capture triggering event occurs on PD6 (ICP), i.e., when
the ICF1 bit is set in the Timer/Counter Interrupt Flag Register – TIFR.
32 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Timer/Counter2 Overflow Interrupt is executed. In up/down PWM mode, this bit is set
when Timer/Counter2 changes counting direction at $00.
External Interrupts The external interrupts are triggered by the INT0 and INT1 pins. Observe that, if
enabled, the interrupts will trigger even if the INT0/INT1 pins are configured as outputs.
This feature provides a way of generating a software interrupt. The external interrupts
can be triggered by a falling or rising edge or a low level. This is set up as indicated in
the specification for the MCU Control Register – MCUCR. When the external interrupt is
enabled and is configured as level triggered, the interrupt will trigger as long as the pin is
held low.
33
1142E–AVR–02/03
MCU Control Register – The MCU Control Register contains control bits for general MCU functions.
MCUCR
Bit 7 6 5 4 3 2 1 0
$35 ($55) – SE SM1 SM0 ISC11 ISC10 ISC01 ISC00 MCUCR
Read/Write R R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
34 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Sleep Modes To enter any of the four sleep modes, the SE bit in MCUCR must be set (one) and a
SLEEP instruction must be executed. The SM1 and SM0 bits in the MCUCR Register
select which sleep mode (Idle, ADC Noise Reduction, Power-down, or Power-save) will
be activated by the SLEEP instruction. See Table 7 for a summary. If an enabled inter-
rupt occurs while the MCU is in a sleep mode, the MCU wakes up. The MCU is then
halted for four cycles, executes the interrupt routine, and resumes execution from the
instruction following SLEEP. The contents of the Register File, SRAM, and I/O memory
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.
Idle Mode When the SM1/SM0 bits are set to 00, the SLEEP instruction makes the MCU enter Idle
mode, stopping the CPU but allowing SPI, UART, Analog Comparator, ADC, Two-wire
Serial Interface, Timer/Counters, Watchdog, and the interrupt system to continue oper-
ating (if enabled). This enables the MCU to wake up from external triggered interrupts
as well as internal ones like the Timer Overflow and UART Receive Complete interrupts.
If wake-up from the Analog Comparator interrupt is not required, the Analog Comparator
can be powered down by setting the ACD bit in the Analog Comparator Control and Sta-
tus Register – ACSR. This will reduce power consumption in Idle Mode. If the ADC is
enabled, a conversion starts automatically when this mode is entered.
ADC Noise Reduction Mode When the SM1/SM0 bits are set to 01, the SLEEP instruction makes the MCU enter
ADC Noise Reduction mode, stopping the CPU but allowing the ADC, the external inter-
rupts, the Two-wire Serial Interface address watch, Timer/Counter2 and the Watchdog
to continue operating (if enabled). This improves the noise environment for the ADC,
enabling higher resolution measurements. If the ADC is enabled, a conversion starts
automatically when this mode is entered. Apart from the ADC Conversion Complete
interrupt, only an External Reset, a Watchdog Reset (if enabled), a Brown-out Reset, a
Two-wire Serial Interface address match interrupt, or an external level interrupt can
wake up the MCU from ADC Noise Reduction Mode. A Timer/Counter2 Output Com-
pare or overflow event will wake up the MCU, but will not generate an interrupt unless
Timer/Counter2 is clocked asynchronously.
In future devices this is subject to change. It is recommended for future code compatibil-
ity to disable Timer/Counter2 interrupts during ADC Noise Reduction mode if the
Timer/Counter2 is clocked synchronously.
35
1142E–AVR–02/03
Power-down Mode When the SM1/SM0 bits are 10, the SLEEP instruction makes the MCU enter Power-
down mode. In this mode, the external Oscillator is stopped, while the external inter-
rupts, the Two-wire Serial Interface address match, and the Watchdog continue
operating (if enabled). Only an External Reset, a Watchdog Reset, a Brown-out Reset, a
Two-wire Serial Interface address match interrupt, or an external level interrupt can
wake up the MCU.
Note that if a level triggered interrupt is used for wake-up from Power-down mode, the
changed level must be held for some time to wake up the MCU. This makes the MCU
less sensitive to noise. The changed level is sampled twice by the Watchdog Oscillator
clock, and if the input has the required level during this time, the MCU will wake up. The
period of the Watchdog Oscillator is 1 µs (nominal) at 5.0V and 25°C. The frequency of
the Watchdog Oscillator is voltage dependent as shown in the Electrical Characteristics
section.
When waking up from Power-down mode, there is a delay from the wake-up condition
occurs until the wake-up becomes effective. This allows the clock to restart and become
stable after having been stopped. The wake-up period is defined by the same CKSEL
Fuses that define the Reset Time-out period, as seen in Table 5 on page 25.
Power-save Mode When the SM1/SM0 bits are 11, the SLEEP instruction forces the MCU into the Power-
save mode. This mode is identical to Power-down, with one exception:
If Timer/Counter2 is clocked asynchronously, i.e., the AS2 bit in ASSR is set,
Timer/Counter2 will run during sleep. The device can wake up from either Timer Over-
f lo w o r O u tp u t C o m p a r e e v e n t fr o m Ti me r /C o u n te r2 i f t h e c o r r e s p o n d i n g
Timer/Counter2 interrupt enable bits are set in TIMSK, and the global interrupt enable
bit in SREG is set.
If the asynchronous timer is NOT clocked asynchronously, Power-down mode is recom-
mended instead of Power-save mode because the contents of the registers in the
asynchronous timer should be considered undefined after wake-up in Power-save mode
if AS2 is 0.
36 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Calibrated Internal RC The calibrated internal Oscillator provides a fixed 1 MHz (nominal) clock at 5V and
Oscillator 25°C. This clock may be used as the system clock. See the section “Clock Options” on
page 5 for information on how to select this clock as the system clock. This Oscillator
can be calibrated by writing the calibration byte to the OSCCAL Register. When this
Oscillator is used as the chip clock, the Watchdog Oscillator will still be used for the
Watchdog Timer and for the Reset Time-out. At 5V and 25oC, the pre-programmed cali-
bration byte gives a frequency within ± 1% of the nominal frequency. For details on how
to use the pre-programmed calibration value, see “Calibration Byte” on page 144.
37
1142E–AVR–02/03
• Bit 2 – PUD: Pull-up Disable
When this bit is set (one), all pull-ups on all ports are disabled. If the bit is cleared (zero),
the pull-ups can be individually enabled as described in the chapter “I/O Ports” on page
115.
38 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Timer/Counters The ATmega163 provides three general purpose Timer/Counters – two 8-bit T/Cs and
one 16-bit T/C. Timer/Counter2 can optionally be asynchronously clocked from an exter-
nal Oscillator. This Oscillator is optimized for use with a 32.768 kHz watch crystal,
enabling use of Timer/Counter2 as a Real Time Clock (RTC). Timer/Counter0 and
Timer/Counter1 have individual prescaling selection from the same 10-bit prescaler.
Timer/Counter2 has its own prescaler. Both these prescalers can be reset by setting the
corresponding control bits in the Special Functions I/O Register (SFIOR). These
Timer/Counters can either be used as a timer with an internal clock time-base or as a
counter with an external pin connection which triggers the counting.
PSR10
TCK1 TCK0
For Timer/Counter0 and Timer/Counter1, the four different prescaled selections are:
CK/8, CK/64, CK/256, and CK/1024, where CK is the Oscillator clock. For the two
Timer/Counter0 and Timer/Counter1, CK, external source, and stop can also be
selected as clock sources. Setting the PSR10 bit in SFIOR resets the prescaler. This
allows the user to operate with a predictable prescaler. Note that Timer/Counter1 and
Timer/Counter0 share the same prescaler and a Prescaler Reset will affect both
Timer/Counters.
39
1142E–AVR–02/03
Figure 31. Prescaler for Timer/Counter2
CK PCK2
10-BIT T/C PRESCALER
Clear
TOSC1
PCK2/8
PCK2/32
PCK2/64
PCK2/128
PCK2/256
PCK2/1024
AS2
PSR2 0
CS20
CS21
CS22
The clock source for Timer/Counter2 is named PCK2. PCK2 is by default connected to
the main system clock CK. By setting the AS2 bit in ASSR, Timer/Counter2 is asynchro-
nously clocked from the PC6(TOSC1) pin. This enables use of Timer/Counter2 as a
Real Time Clock (RTC). When AS2 is set, pins PC6(TOSC1) and PC7(TOSC2) are dis-
connected from Port C. A crystal can then be connected between the PC6(TOSC1) and
PC7(TOSC2) pins to serve as an independent clock source for Timer/Counter2. The
Oscillator is optimized for use with a 32.768 kHz crystal. Applying an external clock
source to TOSC1 is not recommended. Setting the PSR2 bit in SFIOR resets the pres-
caler. This allows the user to operate with a predictable prescaler.
40 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
OCIE1B
OCIE1A
8-BIT DATA BUS
TICIE1
OCIE2
TOIE2
TOIE1
TOIE0
TIMER INT. MASK TIMER INT. FLAG T/C0 CONTROL
REGISTER (TIMSK) REGISTER (TIFR) REGISTER (TCCR0)
CS02
CS01
CS00
TOV2
TOV0
OCF2
ICF1
OCF1B
OCF1A
TOV1
7 0
TIMER/COUNTER0 T/C CLK SOURCE CONTROL CK
(TCNT0) LOGIC
Timer/Counter0 Control
Register – TCCR0 Bit 7 6 5 4 3 2 1 0
$33 ($53) – – – – – CS02 CS01 CS00 TCCR0
Read/Write R R R R R R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
The Stop condition provides a Timer Enable/Disable function. The prescaled CK modes
are scaled directly from the CK Oscillator clock. If the external pin modes are used for
Timer/Counter0, transitions on PB0/(T0) will clock the counter even if the pin is config-
ured as an output. This feature can give the user SW control of the counting.
41
1142E–AVR–02/03
Timer/Counter 0 – TCNT0
Bit 7 6 5 4 3 2 1 0
$34 ($54) MSB LSB TCNT0
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
The Timer/Counter0 is implemented as an up-counter with read and write access. If the
Timer/Counter0 is written and a clock source is present, the Timer/Counter0 continues
counting in the clock cycle following the write operation.
OCF1B
OCF1A
TICIE1
OCIE2
TOIE2
TOIE1
TOIE0
OCF2
TOV2
TOV0
TOV1
ICF1
TIMER INT. MASK TIMER INT. FLAG T/C1 CONTROL T/C1 CONTROL
REGISTER (TIMSK) REGISTER (TIFR) REGISTER A (TCCR1A) REGISTER B (TCCR1B)
PWM11
CS12
CS10
COM1A1
COM1B1
ICNC1
CTC1
PWM10
CS11
COM1A0
COM1B0
ICES1
FOC1A
FOC1B
OCF1B
OCF1A
TOV1
ICF1
15 8 7 0
15 8 7 0 T/C CLEAR
T/C CLOCK SOURCE
TIMER/COUNTER1 (TCNT1)
UP/DOWN
15 8 7 0 15 8 7 0
15 8 7 0 15 8 7 0
The 16-bit Timer/Counter1 can select clock source from CK, prescaled CK, or an exter-
nal pin. In addition it can be stopped as described in section “Timer/Counter1 Control
Register B – TCCR1B” on page 45. The different Status Flags (Overflow, Compare
Match, and Capture Event) are found in the Timer/Counter Interrupt Flag Register –
TIFR. Control signals are found in the Timer/Counter1 Control Registers – TCCR1A and
TCCR1B. The interrupt enable/disable settings for Timer/Counter1 are found in the
Timer/Counter Interrupt Mask Register – TIMSK.
When Timer/Counter1 is externally clocked, the external signal is synchronized with the
Oscillator frequency of the CPU. To assure proper sampling of the external clock, the
minimum time between two external clock transitions must be at least one internal CPU
42 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
clock period. The external clock signal is sampled on the rising edge of the internal CPU
clock.
The 16-bit Timer/Counter1 features both a high resolution and a high accuracy usage
with the lower prescaling opportunities. Similarly, the high prescaling opportunities
makes the Timer/Counter1 useful for lower speed functions or exact timing functions
with infrequent actions.
The Timer/Counter1 supports two Output Compare functions using the Output Compare
Register 1 A and B (OCR1A and OCR1B) as the data sources to be compared to the
Timer/Counter1 contents. The Output Compare functions includes optional clearing of
the counter on Compare A Match, and actions on the Output Compare pins on both
compare matches.
Timer/Counter1 can also be used as an 8-, 9-, or 10-bit Pulse Width Modulator (PWM).
In this mode the counter and the OCR1A/OCR1B Registers serve as a dual glitch-free
stand-alone PWM with centered pulses. Alternatively, the Timer/Counter1 can be con-
figured to operate at twice the speed in PWM mode, but without centered pulses. Refer
to page 48 for a detailed description of this function.
The Input Capture function of Timer/Counter1 provides a capture of the Timer/Counter1
contents to the Input Capture Register – ICR1, triggered by an external event on the
Input Capture Pin – ICP. The actual capture event settings are defined by the
Timer/Counter1 Control Register – TCCR1B. In addition, the Analog Comparator can be
set to trigger the Input Capture. Refer to the section, “The Analog Comparator” on page
102, for details on this. The ICP pin logic is shown in Figure 34.
If the noise canceler function is enabled, the actual trigger condition for the capture
event is monitored over four samples, and all four must be equal to activate the Capture
Flag.
43
1142E–AVR–02/03
Timer/Counter1 Control
Register A – TCCR1A Bit 7 6 5 4 3 2 1 0
$2F ($4F) COM1A1 COM1A0 COM1B1 COM1B0 FOC1A FOC1B PWM11 PWM10 TCCR1A
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
Note: 1. X = A or B.
In PWM mode, these bits have a different function. Refer to Table 14 for a detailed
description.
44 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
in the Timer. The automatic action programmed in COM1B1 and COM1B0 happens as if
a Compare Match had occurred, but no interrupt is generated. The corresponding I/O
pin must be set as an output pin for the FOC1B bit to have effect on the pin. The FOC1B
bit will always be read as zero. The setting of the FOC1B bit has no effect in PWM
mode.
Timer/Counter1 Control
Bit 7 6 5 4 3 2 1 0
Register B – TCCR1B
$2E ($4E) ICNC1 ICES1 – – CTC1 CS12 CS11 CS10 TCCR1B
Read/Write R/W R/W R R R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
45
1142E–AVR–02/03
When the prescaler is set to divide by eight, the Timer will count like this:
... | C-1, C-1, C-1, C-1, C-1, C-1, C-1, C-1 | C, C, C, C, C, C, C, C | 0, 0, 0, 0, 0, 0, 0, 0
|1,1,1,1,1,1,1,1|...
In PWM mode, this bit has a different function. If the CTC1 bit is cleared in PWM mode,
the Timer/Counter1 acts as an up/down counter. If the CTC1 bit is set (one), the
Timer/Counter wraps when it reaches the TOP value. Refer to page 48 for a detailed
description.
The Stop condition provides a Timer Enable/Disable function. The prescaled modes are
scaled directly from the CK Oscillator clock. If the external pin modes are used for
Timer/Counter1, transitions on PB1/(T1) will clock the counter even if the pin is config-
ured as an output. This feature can give the user SW control of the counting.
Timer/Counter1 – TCNT1H
and TCNT1L Bit 15 14 13 12 11 10 9 8
$2D ($4D) MSB TCNT1H
$2C ($4C) LSB TCNT1L
7 6 5 4 3 2 1 0
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
This 16-bit register contains the prescaled value of the 16-bit Timer/Counter1. To
ensure that both the high and low bytes are read and written simultaneously when the
CPU accesses these registers, the access is performed using an 8-bit temporary regis-
ter (TEMP). This temporary register is also used when accessing OCR1A, OCR1B, and
ICR1. If the main program and also interrupt routines perform access to registers using
TEMP, interrupts must be disabled during access from the main program and interrupt
routines.
46 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
TCNT1 Timer/Counter1 Write When the CPU writes to the high byte TCNT1H, the written data is placed in the TEMP
Register. Next, when the CPU writes the low byte TCNT1L, this byte of data is combined
with the byte data in the TEMP Register, and all 16 bits are written to the TCNT1
Timer/Counter1 Register simultaneously. Consequently, the high byte TCNT1H must be
accessed first for a full 16-bit register write operation.
TCNT1 Timer/Counter1 Read When the CPU reads the low byte TCNT1L, the data of the Low Byte TCNT1L is sent to
the CPU and the data of the High Byte TCNT1H is placed in the TEMP Register. When
the CPU reads the data in the High Byte TCNT1H, the CPU receives the data in the
TEMP Register. Consequently, the Low Byte TCNT1L must be accessed first for a full
16-bit register read operation.
The Timer/Counter1 is realized as an up or up/down (in PWM mode) counter with read
and write access. If Timer/Counter1 is written to and a clock source is selected, the
Timer/Counter1 continues counting in the timer clock cycle after it is preset with the writ-
ten value.
Timer/Counter1 Output
Compare Register – OCR1AH Bit 15 14 13 12 11 10 9 8
and OCR1AL $2B ($4B) MSB OCR1AH
$2A ($4A) LSB OCR1AL
7 6 5 4 3 2 1 0
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
Timer/Counter1 Output
Bit 15 14 13 12 11 10 9 8
Compare Register – OCR1BH
$29 ($49) MSB OCR1BH
and OCR1BL
$28 ($48) LSB OCR1BL
7 6 5 4 3 2 1 0
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
47
1142E–AVR–02/03
The TEMP Register is also used when accessing TCNT1 and ICR1. If the main program
and also interrupt routines perform access to registers using TEMP, interrupts must be
disabled during access from the main program and interrupt routines.
Timer/Counter1 in PWM Mode When the PWM mode is selected, Timer/Counter1 and the Output Compare Register1A
– OCR1A and the Output Compare Register1B – OCR1B, form a dual 8,- 9-, or 10-bit,
free-running, glitch-free, and phase correct PWM with outputs on the PD5 (OC1A) and
PD4(OC1B) pins. In this mode, the Timer/Counter1 acts as an up/down counter, count-
ing up from $0000 to TOP (see Table 16), where it turns and counts down again to zero
before the cycle is repeated. When the counter value matches the contents of the 8, 9,
or 10 least significant bits (depending on resolution) of OCR1A or OCR1B, the
PD5(OC1A)/PD4(OC1B) pins are set or cleared according to the settings of the
COM1A1/COM1A0 or COM1B1/COM1B0 bits in the Timer/Counter1 Control Register
TCCR1A. Refer to Table 12 on page 44 for details.
Alternatively, the Timer/Counter1 can be configured to a PWM that operates at twice the
speed as in the mode described above. Then the Timer/Counter1 and the Output Com-
pare Register1A – OCR1A and the Output Compare Register1B – OCR1B, form a dual
8-, 9-, or 10-bit, free-running and glitch-free PWM with outputs on the PD5(OC1A) and
PD4(OC1B) pins.
48 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
As shown in Table 15, the PWM operates at either 8, 9, or 10 bits resolution. Note the
unused bits in OCR1A, OCR1B, and TCNT1 will automatically be written to zero by
hardware. For example, bit 9 to 15 will be set to zero in OCR1A, OCR1B, and TCNT1 if
the 9-bit PWM resolution is selected. This makes it possible for the user to perform read-
modify-write operations in any of the three resolution modes and the unused bits will be
treated as don’t care.
Note: 1. X = A or B
Note that in the PWM mode, the 8, 9, or 10 least significant OCR1A/OCR1B bits
(depending on resolution), when written, are transferred to a temporary location. They
are latched when Timer/Counter1 reaches the value TOP. This prevents the occurrence
of odd-length PWM pulses (glitches) in the event of an unsynchronized OCR1A/OCR1B
write. See Figure 35 and Figure 36 for an example in each mode.
49
1142E–AVR–02/03
Figure 35. Effects of Unsynchronized OCR1 Latching.
Note: x = A or B
Note: X = A or B
During the time between the write and the latch operation, a read from OCR1A or
OCR1B will read the contents of the temporary location. This means that the most
recently written value always will read out of OCR1A/B.
When the OCR1X contains $0000 or TOP, and the up/down PWM mode is selected, the
output OC1A/OC1B is updated to low or high on the next Compare Match according to
the settings of COM1A1/COM1A0 or COM1B1/COM1B0. This is shown in Table 18. In
overflow PWM mode, the output OC1A/OC1B is held low or high only when the Output
Compare Register contains TOP.
Note: 1. X = A or B
50 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
In overflow PWM mode, the table above is only valid for OCR1X = TOP.
In PWM mode, the Timer Overflow Flag1, TOV1, is set when the counter advances from
$00 00. In overflow PWM mode, the Timer Overflow Flag is set as in Normal
Timer/Counter mode. Timer Overflow Interrupt1 operates exactly as in Normal
Timer/Counter mode, i.e., it is executed when TOV1 is set provided that Timer Overflow
Interrupt1 and global interrupts are enabled. This also applies to the Timer Output
Compare1 Flags and interrupts.
TOIE1
TOIE0
OCF2
TOV2
TIMER INT. MASK TIMER INT. FLAG T/C2 CONTROL
REGISTER (TIMSK) REGISTER (TIFR) REGISTER (TCCR2)
CS22
CS21
CS20
COM21
COM20
CTC2
FOC2
PWM2
TOV2
TOV0
OCF2
ICF1
OCF1A
OCF1B
TOV1
7 0 T/C CLEAR
TIMER/COUNTER2 T/C CLK SOURCE CK
(TCNT2) CONTROL PSR2
UP/DOWN
LOGIC
TOSC1
7 0
8-BIT COMPARATOR
7 0
OUTPUT COMPARE ASYNCH. STATUS
REGISTER2 (OCR2) REGISTER (ASSR)
AS2
ICR2UB
OCR2UB
TC2UB
CK
SYNCH UNIT
PCK2
The 8-bit Timer/Counter2 can select clock source from CK, prescaled CK, or external
crystal input TOSC1. It can also be stopped as described in the section “Timer/Counter2
Control Register – TCCR2” on page 52.
The Status Flags (Overflow and Compare Match) are found in the Timer/Counter Inter-
rupt Flag Register – TIFR. Control signals are found in the Timer/Counter Control
Register TCCR2. The interrupt enable/disable settings are found in “The Timer/Counter
Interrupt Mask Register – TIMSK” on page 31.
When Timer/Counter2 is externally clocked, the external signal is synchronized with the
Oscillator frequency of the CPU. To assure proper sampling of the external clock, the
minimum time between two external clock transitions must be at least one internal CPU
51
1142E–AVR–02/03
clock period. The external clock signal is sampled on the rising edge of the internal CPU
clock.
This module features a high resolution and a high accuracy usage with the lower pres-
caling opportunities. Similarly, the high prescaling opportunities make this unit useful for
lower speed functions or exact timing functions with infrequent actions.
Timer/Counter2 can also be used as an 8-bit Pulse Width Modulator. In this mode,
Timer/Counter2 and the Output Compare Register serve as a glitch-free, stand-alone
PWM with centered pulses. Refer to page 57 for a detailed description on this function.
Timer/Counter2 Control
Register – TCCR2 Bit 7 6 5 4 3 2 1 0
$25 ($45) FOC2 PWM2 COM21 COM20 CTC2 CS22 CS21 CS20 TCCR2
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
Note: 1. In PWM mode, these bits have a different function. Refer to Table 21 on page 55 for
a detailed description.
52 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
The Stop condition provides a Timer Enable/Disable function. The prescaled modes are
scaled directly from the PCK2 clock.
Timer/Counter2 – TCNT2
Bit 7 6 5 4 3 2 1 0
$24 ($44) MSB LSB TCNT2
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
53
1142E–AVR–02/03
Timer/Counter2 Output
Bit 7 6 5 4 3 2 1 0
Compare Register – OCR2
$23 ($43) MSB LSB OCR2
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
Timer/Counter2 in PWM Mode When PWM mode is selected, the Timer/Counter2 either wraps (overflows) when it
reaches $FF or it acts as an up/down counter.
If the up/down mode is selected, the Timer/Counter2 and the Output Compare Register
– OCR2 form an 8-bit, free-running, glitch-free, and phase correct PWM with outputs on
the PD7(OC2) pin.
If the overflow mode is selected, the Timer/Counter2 and the Output Compare Register
– OCR2 form an 8-bit, free-running, and glitch-free PWM, operating with twice the speed
of the up/down counting mode.
PWM Modes (Up/Down and The two different PWM modes are selected by the CTC2 bit in the Timer/Counter Con-
Overflow) trol Register – TCCR2.
If CTC2 is cleared and PWM mode is selected, the Timer/Counter acts as an up/down
counter, counting up from $00 to $FF, where it turns and counts down again to zero
before the cycle is repeated. When the counter value matches the contents of the Out-
put Compare Register, the PD7(OC2) pin is set or cleared according to the settings of
the COM21/COM20 bits in the Timer/Counter Control Register TCCR2.
If CTC2 is set and PWM mode is selected, the Timer/Counters will wrap and start count-
ing from $00 after reaching $FF. The PD7(OC2) pin will be set or cleared according to
the settings of COM21/COM20 on a Timer/Counter overflow or when the counter value
matches the contents of the Output Compare Register. Refer to Table 21 for details.
54 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Note that in PWM mode, the value to be written to the Output Compare Register is first
tr an sfe rr ed to a temp o ra ry lo ca tio n , an d the n latc he d in to O CR 2 w h en th e
Timer/Counter reaches $FF. This prevents the occurrence of odd-length PWM pulses
(glitches) in the event of an unsynchronized OCR2 write. See Figure 38 for examples.
55
1142E–AVR–02/03
Figure 39. Effects of Unsynchronized OCR Latching in Overflow Mode.
Compare Value changes
Counter Value
Compare Value
During the time between the write and the latch operation, a read from OCR2 will read
the contents of the temporary location. This means that the most recently written value
always will read out of OCR2.
When the Output Compare Register contains $00 or $FF, and the up/down PWM mode
is selected, the output PD7(OC2) is updated to low or high on the next compare match
according to the settings of COM21/COM20. This is shown in Table 22. In overflow
PWM mode, the output PD7(OC2) is held low or high only when the Output Compare
Register contains $FF.
In up/down PWM mode, the Timer Overflow Flag – TOV2, is set when the counter
changes direction at $00. In overflow PWM mode, the Timer Overflow Flag is set as in
normal Timer/Counter mode. The Timer Overflow Interrupt operates exactly as in nor-
mal Timer/Counter mode, i.e., it is executed when TOV2 is set provided that Timer
Overflow Interrupt and Global Interrupts are enabled. This also applies to the Timer Out-
put Compare Flag and Interrupt.
The frequency of the PWM will be Timer Clock Frequency divided by 510.
56 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Asynchronous Status
Register – ASSR Bit 7 6 5 4 3 2 1 0
$22 ($22) – – – – AS2 TCN2UB OCR2UB TCR2UB ASSR
Read/Write R R R R R/W R R R
Initial Value 0 0 0 0 0 0 0 0
57
1142E–AVR–02/03
Asynchronous Operation of When Timer/Counter2 operates asynchronously, some considerations must be taken.
Timer/Counter2 • Warning: When switching between asynchronous and synchronous clocking of
Timer/Counter2, the Timer Registers TCNT2, OCR2, and TCCR2 might be
corrupted. A safe procedure for switching clock source is:
1. Disable the Timer/Counter2 interrupts by clearing OCIE2 and TOIE2.
2. Select clock source by setting AS2 as appropriate.
3. Write new values to TCNT2, OCR2, and TCCR2.
4. To switch to asynchronous operation: Wait for TCN2UB, OCR2UB, and
TCR2UB.
5. Clear the Timer/Counter2 Interrupt Flags.
6. Enable interrupts, if needed.
• The Oscillator is optimized for use with a 32.768 kHz watch crystal. Applying an
external clock to the TOSC1 pin may result in incorrect Timer/Counter2 operation.
The CPU main clock frequency must be more than four times the Oscillator
frequency.
• When writing to one of the registers TCNT2, OCR2, or TCCR2, the value is
transferred to a temporary register, and latched after two positive edges on TOSC1.
The user should not write a new value before the contents of the temporary register
have been transferred to its destination. Each of the three mentioned registers have
their individual temporary register, which means that e.g. writing to TCNT2 does not
disturb an OCR2 write in progress. To detect that a transfer to the destination
register has taken place, the Asynchronous Status Register – ASSR has been
implemented.
• When entering Power-save mode after having written to TCNT2, OCR2, or TCCR2,
the user must wait until the written register has been updated if Timer/Counter2 is
used to wake up the device. Otherwise, the MCU will enter sleep mode before the
changes are effective. This is particularly important if the Output Compare2 interrupt
is used to wake up the device, since the output compare function is disabled during
writing to OCR2 or TCNT2. If the write cycle is not finished, and the MCU enters
sleep mode before the OCR2UB bit returns to zero, the device will never receive a
compare match interrupt, and the MCU will not wake up.
• If Timer/Counter2 is used to wake the device up from Power-save mode,
precautions must be taken if the user wants to re-enter Power-save mode: The
interrupt logic needs one TOSC1 cycle to be Reset. If the time between wake-up
and re-entering Power-save mode is less than one TOSC1 cycle, the interrupt will
not occur, and the device will fail to wake up. If the user is in doubt whether the time
before re-entering Power-save is sufficient, the following algorithm can be used to
ensure that one TOSC1 cycle has elapsed:
1. Write a value to TCCR2, TCNT2, or OCR2.
2. Wait until the corresponding Update Busy Flag in ASSR returns to zero.
3. Enter Power-save mode.
• When the asynchronous operation is selected, the 32.768 kHz Oscillator for
Timer/Counter2 is always running, except in Power-down mode. After a Power-up
Reset or Wake-up from Power-down, the user should be aware of the fact that this
Oscillator might take as long as one second to stabilize. The user is advised to wait
for at least one second before using Timer/Counter2 after Power-up or wake-up
from Power-down. The contents of all Timer/Counter2 Registers must be considered
lost after a wake-up from Power-down due to unstable clock signal upon startup.
• Description of wake-up from Power-save mode when the Timer is clocked
asynchronously: When the interrupt condition is met, the wake-up process is started
58 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
on the following cycle of the timer clock, that is, the timer is always advanced by at
least one before the processor can read the counter value. After wake-up, the MCU
is halted for four clock cycles, it executes the interrupt routine, and resumes
execution from the instruction following SLEEP.
• During asynchronous operation, the synchronization of the interrupt flags for the
asynchronous timer takes three processor cycles plus one timer cycle. The timer is
therefore advanced by at least one before the processor can read the timer value
causing the setting of the Interrupt Flag. The output compare pin is changed on the
timer clock and is not synchronized to the processor clock.
• After waking up from Power-save mode with the asynchronous timer enabled, there
will be a short interval in which TCNT2 will read as the same value as before Power-
save mode was entered. After an edge on the asynchronous clock, TCNT2 will read
correctly (The compare and overflow functions of the Timer are not affected by this
behavior.). Safe procedure to ensure that the correct value is read:
1. Write any value to either of the registers OCR2 or TCCR2.
2. Wait for the corresponding Update Busy Flag to be cleared.
3. Read TCNT2.
Note that OCR2 and TCCR2 are never modified by hardware, and will always read
correctly.
59
1142E–AVR–02/03
Watchdog Timer The Watchdog Timer is clocked from a separate On-chip Oscillator which runs at
1 MHz. This is the typical value at VCC = 5V. See characterization data for typical values
at other VCC levels. By controlling the Watchdog Timer prescaler, the Watchdog Reset
interval can be adjusted as shown in Table 23 on page 61. The WDR – Watchdog Reset
– instruction resets the Watchdog Timer. Eight different clock cycle periods can be
selected to determine the reset period. If the reset period expires without another
Watchdog Reset, the ATmega163 resets and executes from the Reset Vector. For tim-
ing details on the Watchdog Reset, refer to page 28.
To prevent unintentional disabling of the Watchdog, a special turn-off sequence must be
followed when the Watchdog is disabled. Refer to the description of the Watchdog Timer
Control Register for details.
OSCILLATOR
1 MHz at VCC = 5V
60 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
1. In the same operation, write a logical one to WDTOE and WDE. A logical one
must be written to WDE even though it is set to one before the disable operation
starts.
2. Within the next four clock cycles, write a logical 0 to WDE. This disables the
Watchdog.
61
1142E–AVR–02/03
EEPROM Read/Write The EEPROM Access Registers are accessible in the I/O space.
Access The write access time is in the range of 1.9 - 3.8 ms, depending on the VCC voltages.
See Table 24 for details. A self-timing function, however, lets the user software detect
when the next byte can be written. If the user code contains code that writes the
EEPROM, some precautions must be taken. In heavily filtered power supplies, VCC is
likely to rise or fall slowly on Power-up/down. This causes the device for some period of
time to run at a voltage lower than specified as minimum for the clock frequency used.
CPU operation under these conditions is likely to cause the Program Counter to perform
unintentional jumps and potentially execute the EEPROM write code. To secure
EEPROM integrity, the user is advised to use an External under-voltage Reset circuit or
the internal BOD in this case.
In order to prevent unintentional EEPROM writes, a specific write procedure must be fol-
lowed. Refer to the description of the EEPROM Control Register for details on this.
When the EEPROM is read, the CPU is halted for four clock cycles before the next
instruction is executed. When the EEPROM is written, the CPU is halted for two clock
cycles before the next instruction is executed.
62 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
63
1142E–AVR–02/03
The user should poll the EEWE bit before starting the read operation. If a write operation
is in progress, it is not possible to set the EERE bit, nor to change the EEAR Register.
The calibrated Oscillator is used to time the EEPROM accesses. Table 24 lists the typi-
cal programming time for EEPROM access from the CPU
Preventing EEPROM During periods of low VCC, the EEPROM data can be corrupted because the supply volt-
Corruption age is too low for the CPU and the EEPROM to operate properly. These issues are the
same as for board level systems using the EEPROM, and the same design solutions
should be applied.
An EEPROM data corruption can be caused by two situations when the voltage is too
low. First, a regular write sequence to the EEPROM requires a minimum voltage to
operate correctly. Secondly, the CPU itself can execute instructions incorrectly, if the
supply voltage for executing instructions is too low.
EEPROM data corruption can easily be avoided by following these design recommen-
dations (one is sufficient):
1. Keep the AVR RESET active (low) during periods of insufficient power supply
voltage. This can be done by enabling the internal Brown-out Detector (BOD) if
the operating voltage matches the detection level. If not, an external low VCC
Reset Protection circuit can be used. If a Reset occurs while a write operation is
in progress, the write operation will be completed provided that the power supply
is voltage is sufficient.
2. Keep the AVR core in Power-down Sleep Mode during periods of low VCC. This
will prevent the CPU from attempting to decode and execute instructions, effec-
tively protecting the EEPROM Registers from unintentional writes.
3. Store constants in Flash memory if the ability to change memory contents from
software is not required. Flash memory can not be updated by the CPU unless
the boot loader software supports writing to the Flash and the Boot Lock bits are
configured so that writing to the Flash memory from CPU is allowed. See “Boot
Loader Support” on page 134 for details.
64 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Serial Peripheral The Serial Peripheral Interface (SPI) allows high-speed synchronous data transfer
between the ATmega163 and peripheral devices or between several AVR devices. The
Interface – SPI
ATmega163 SPI includes the following 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
DIVIDER
/2/4/8/16/32/64/128
SPI2X
SPI2X
The interconnection between Master and Slave CPUs with SPI is shown in Figure 42.
The PB7(SCK) pin is the clock output in the Master mode and the clock input in the
Slave mode. Writing to the SPI Data Register of the Master CPU starts the SPI clock
generator, and the data written shifts out of the PB5(MOSI) pin and into the PB5(MOSI)
pin of the Slave CPU. 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 Slave Select input, PB4(SS), is set low to
select an individual Slave SPI device. The two Shift Registers in the Master and the
Slave can be considered as one distributed 16-bit circular Shift Register. This is shown
in Figure 42. When data is shifted from the Master to the Slave, data is also shifted in
65
1142E–AVR–02/03
the opposite direction, simultaneously. During one shift cycle, data in the Master and the
Slave is interchanged.
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.
When the SPI is enabled, the data direction of the MOSI, MISO, SCK, and SS pins is
overridden according to Table 25.
Note: 1. See “Alternate Functions Of PORTB” on page 118 for a detailed description of how to
define the direction of the user defined SPI pins.
SS Pin Functionality When the SPI is configured as a Master (MSTR in SPCR is set), the user can determine
the direction of the SS pin. If SS is configured as an output, the pin is a general output
pin which does not affect the SPI system. If SS is configured as an input, it must be held
high to ensure Master SPI operation. If the SS pin is driven low by peripheral circuitry
when the SPI is configured as a Master with the SS pin defined as an input, the SPI sys-
tem interprets this as another Master selecting the SPI as a Slave and starting to send
data to it. To avoid bus contention, the SPI system takes the following actions:
1. The MSTR bit in SPCR is cleared and the SPI system becomes a Slave. As a
result of the SPI becoming a Slave, the MOSI and SCK pins become inputs.
2. The SPIF Flag in SPSR is set, and if the SPI interrupt is enabled, and the I-bit in
SREG is set, the interrupt routine will be executed.
Thus, when interrupt-driven SPI transmission is used in Master mode, and there exists a
possibility that SS is driven low, the interrupt should always check that the MSTR bit is
still set. If the MSTR bit has been cleared by a slave select, it must be set by the user to
re-enable SPI Master mode.
66 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
When the SPI is configured as a Slave, the SS pin is always input. When SS is held low,
the SPI is activated, and MISO becomes an output if configured so by the user. All other
pins are inputs. When SS is driven high, all pins are inputs, and the SPI is passive,
which means that it will not receive incoming data. Note that the SPI logic will be Reset
once the SS pin is driven high. If the SS pin is driven high during a transmission, the SPI
will stop sending and receiving immediately and both data received and data sent must
be considered as lost.
Data Modes There are four combinations of SCK phase and polarity with respect to serial data,
which are determined by control bits CPHA and CPOL. The SPI data transfer formats
are shown in Figure 43 and Figure 44.
67
1142E–AVR–02/03
• Bit 5 – DORD: Data Order
When the DORD bit is set (one), the LSB of the data word is transmitted first.
When the DORD bit is cleared (zero), the MSB of the data word is transmitted first.
68 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
The SPI Data Register is a read/write register used for data transfer between the Regis-
ter File and the SPI Shift Register. Writing to the register initiates data transmission.
Reading the register causes the Shift Register Receive buffer to be read.
69
1142E–AVR–02/03
UART The ATmega163 features a full duplex (separate Receive and Transmit Registers) Uni-
versal Asynchronous Receiver and Transmitter (UART). The main features are:
• Baud Rate Generator Generates any Baud Rate
• High Baud Rates at Low XTAL Frequencies
• 8 or 9 Bits Data
• Noise Filtering
• OverRun Detection
• Framing Error Detection
• False Start Bit Detection
• Three Separate Interrupts on TX Complete, TX Data Register Empty, and RX Complete
• Multi-processor Communication Mode
• Double Speed UART Mode
Data Transmission A block schematic of the UART transmitter is shown in Figure 45.
Data transmission is initiated by writing the data to be transmitted to the UART I/O Data
Register, UDR. Data is transferred from UDR to the Transmit Shift Register when:
• A new character has been written to UDR after the stop bit from the previous
character has been shifted out. The Shift Register is loaded immediately.
• A new character has been written to UDR before the stop bit from the previous
character has been shifted out. The Shift Register is loaded when the stop bit of the
character currently being transmitted has been shifted out.
70 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
When data is transferred from UDR to the Shift Register, the UDRE (UART Data Regis-
ter Empty) bit in the UART Status Register, USR, is set. When this bit is set (one), the
UART is ready to receive the next character. At the same time as the data is transferred
from UDR to the 10(11)-bit Shift Register, bit 0 of the Shift Register is cleared (start bit)
and bit 9 or 10 is set (stop bit). If 9-bit data word is selected (the CHR9 bit in the UART
Control Register, UCR is set), the TXB8 bit in UCR is transferred to bit 9 in the Transmit
Shift Register.
On the Baud Rate clock following the transfer operation to the Shift Register, the start bit
is shifted out on the TXD pin. Then follows the data, LSB first. When the stop bit has
been shifted out, the Shift Register is loaded if any new data has been written to the
UDR during the transmission. During loading, UDRE is set. If there is no new data in the
UDR Register to send when the stop bit is shifted out, the UDRE Flag will remain set
until UDR is written again. When no new data has been written, and the stop bit has
been present on TXD for one bit length, the Transmit Complete Flag, TXC, in USR is
set.
The TXEN bit in UCR enables the UART transmitter when set (one). When this bit is
cleared (zero), the PD1 pin can be used for general I/O. When TXEN is set, the UART
Transmitter will be connected to PD1, which is forced to be an output pin regardless of
the setting of the DDD1 bit in DDRD.
71
1142E–AVR–02/03
Data Reception Figure 46 shows a block diagram of the UART Receiver
The Receiver front-end logic samples the signal on the RXD pin at a frequency 16 times
the baud rate. While the line is idle, one single sample of logical zero will be interpreted
as the falling edge of a start bit, and the start bit detection sequence is initiated. Let sam-
ple 1 denote the first zero-sample. Following the 1 to 0-transition, the receiver samples
the RXD pin at samples 8, 9, and 10. If two or more of these three samples are found to
be logical ones, the start bit is rejected as a noise spike and the receiver starts looking
for the next 1 to 0-transition.
If however, a valid start bit is detected, sampling of the data bits following the start bit is
performed. These bits are also sampled at samples 8, 9, and 10. The logical value found
in at least two of the three samples is taken as the bit value. All bits are shifted into the
Transmitter Shift Register as they are sampled. Sampling of an incoming character is
shown in Figure 47. Note that the description above is not valid when the UART trans-
mission speed is doubled. See “Double Speed Transmission” on page 78 for a detailed
description.
72 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Note: 1. This figure is not valid when the UART speed is doubled. See “Double Speed Trans-
mission” on page 78 for a detailed description.
When the stop bit enters the Receiver, the majority of the three samples must be one to
accept the stop bit. If two or more samples are logical zeros, the Framing Error (FE)
Flag in the UART Status Register (USR) is set. Before reading the UDR Register, the
user should always check the FE bit to detect Framing Errors.
Whether or not a valid stop bit is detected at the end of a character reception cycle, the
data is transferred to UDR and the RXC Flag in USR is set. UDR is in fact two physically
separate registers, one for transmitted data and one for received data. When UDR is
read, the Receive Data Register is accessed, and when UDR is written, the Transmit
Data Register is accessed. If 9-bit data word is selected (the CHR9 bit in the UART Con-
trol Register, UCR is set), the RXB8 bit in UCR is loaded with bit nine in the Transmit
Shift Register when data is transferred to UDR.
If, after having received a character, the UDR Register has not been read since the last
receive, the OverRun (OR) Flag in UCR is set. This means that the last data byte shifted
into to the Shift Register could not be transferred to UDR and has been lost. The OR bit
is buffered, and is updated when the valid data byte in UDR is read. Thus, the user
should always check the OR bit when reading the UDR Register in order to detect any
overruns if the baud rate is high or CPU load is high.
When the RXEN bit in the UCR Register is cleared (zero), the receiver is disabled. This
means that the PD0 pin can be used as a general I/O pin. When RXEN is set, the UART
Receiver will be connected to PD0, which is forced to be an input pin regardless of the
setting of the DDD0 bit in DDRD. When PD0 is forced to input by the UART, the
PORTD0 bit can still be used to control the pull-up resistor on the pin.
When the CHR9 bit in the UCR Register is set, transmitted and received characters are
9-bit long plus start and stop bits. The ninth data bit to be transmitted is the TXB8 bit in
UCR Register. This bit must be set to the wanted value before a transmission is initated
by writing to the UDR Register. The 9th data bit received is the RXB8 bit in the UCR
Register.
It is important that the Status Register (USR) always is read before the Data Register
(UDR). The Data Register should be read only once for each received byte. Otherwise,
the Status Register (USR) might get updated with incorrect values.
Multi-processor The Multi-Processor Communication mode enables several Slave MCUs to receive data
Communication Mode from a Master MCU. This is done by first decoding an address byte to find out which
MCU has been addressed. If a particular Slave MCU has been addressed, it will receive
the following data bytes as normal, while the other Slave MCUs will ignore the data
bytes until another address byte is received.
For an MCU to act as a Master MCU, it should enter 9-bit transmission mode (CHR9 in
UCSRB set). The ninth bit must be one to indicate that an address byte is being trans-
mitted, and zero to indicate that a data byte is being transmitted.
For the Slave MCUs, the mechanism appears slightly differently for 8-bit and 9-bit
reception mode. In 8-bit reception mode (CHR9 in UCSRB cleared), the stop bit is one
for an address byte and zero for a data byte. In 9-bit reception mode (CHR9 in UCSRB
73
1142E–AVR–02/03
set), the 9th bit is one for an address byte and zero for a data byte, whereas the stop bit
is always high.
The following procedure should be used to exchange data in Multi-Processor Communi-
cation mode:
1. All Slave MCUs are in Multi-Processor Communication mode (MPCM in UCSRA
is set).
2. The Master MCU sends an address byte, and all slaves receive and read this
byte. In the Slave MCUs, the RXC Flag in UCSRA will be set as normal.
3. Each Slave MCU reads the UDR Register and determines if it has been
selected. If so, it clears the MPCM bit in UCSRA, otherwise it waits for the next
address byte.
4. For each received data byte, the receiving MCU will set the Receive Complete
Flag (RXC in UCSRA). In 8-bit mode, the receiving MCU will also generate a
Framing Error (FE in UCSRA set), since the stop bit is zero. The other slave
MCUs, which still have the MPCM bit set, will ignore the data byte. In this case,
the UDR Register and the RXC or FE Flags will not be affected.
5. After the last byte has been transferred, the process repeats from step 2.
UART Control
The UDR Register is actually two physically separate registers sharing the same I/O
address. When writing to the register, the UART Transmit Data Register is written.
When reading from UDR, the UART Receive Data Register is read.
74 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
When the TXCIE bit in UCR is set, setting of TXC causes the UART Transmit Complete
interrupt to be executed. TXC is cleared by hardware when executing the corresponding
interrupt handling vector. Alternatively, the TXC bit is cleared (zero) by writing a logical
one to the bit.
75
1142E–AVR–02/03
UART Control and Status
Bit 7 6 5 4 3 2 1 0
Register B – UCSRB
$0A ($2A) RXCIE TXCIE UDRIE RXEN TXEN CHR9 RXB8 TXB8 UCSRB
Read/Write R/W R/W R/W R/W R/W R/W R W
Initial Value 0 0 0 0 0 0 1 0
Baud Rate Generator The Baud Rate generator is a frequency divider which generates baud-rates according
to the following equation:
f CK
BAUD = ---------------------------------
16(UBR + 1 )
• BAUD = Baud Rate
• fCK= Crystal Clock frequency
• UBR = Contents of the UBRRHI and UBRR Registers, (0 - 4095)
76 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
• Note that this equation is not valid when the UART transmission speed is doubled.
See “Double Speed Transmission” on page 78 for a detailed description.
For standard crystal frequencies, the most commonly used baud rates can be generated
by using the UBR settings in Table 27. UBR values which yield an actual baud rate dif-
fering less than 2% from the target baud rate, are bold in the table. However, using baud
rates that have more than 1% error is not recommended. High error ratings give less
noise resistance.
Baud R ate 3,28 MHz % Error 3,69 MHz % Erro r 4 MHz % Error 4,608 MHz % Error
2400 UBR= 84 0,4 U BR = 95 0 ,0 U BR = 103 0,2 U BR = 119 0,0
4800 UBR= 42 0,8 U BR = 47 0 ,0 U BR = 51 0,2 U BR = 59 0,0
9600 UBR= 20 1,6 U BR = 23 0 ,0 U BR = 25 0,2 U BR = 29 0,0
14400 UBR= 13 1,6 U BR = 15 0 ,0 U BR = 16 2,1 U BR = 19 0,0
19200 UBR= 10 3,1 U BR = 11 0 ,0 U BR = 12 0,2 U BR = 14 0,0
28800 UBR= 6 1,6 U BR = 7 0 ,0 U BR = 8 3,7 U BR = 9 0,0
38400 UBR= 4 6,3 U BR = 5 0 ,0 U BR = 6 7,5 U BR = 7 6,7
57600 UBR= 3 12,5 U BR = 3 0 ,0 U BR = 3 7,8 U BR = 4 0,0
76800 UBR= 2 12,5 U BR = 2 0 ,0 U BR = 2 7,8 U BR = 3 6,7
11520 0 UBR= 1 12,5 U BR = 1 0 ,0 U BR = 1 7,8 U BR = 2 2 0,0
77
1142E–AVR–02/03
UART Baud Rate Registers –
Bit 15 14 13 12 11 10 9 8
UBRR and UBRRHI
$20 ($40) – – – – MSB LSB UBRRHI
$09 ($29) MSB LSB UBRR
7 6 5 4 3 2 1 0
Read/Write R R R R R/W R/W R/W R/W
R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
This is a 12-bit register which contains the UART Baud Rate according to the equation
on the previous page. The UBRRHI contains the four most significant bits, and the
UBRR contains the eight least significant bits of the UART Baud Rate.
Double Speed The ATmega163 provides a separate UART mode which allows the user to double the
Transmission communication speed. By setting the U2X bit in the UART Control and Status Register
UCSRA, the UART speed will be doubled. Note, however, that the receiver will in this
case only use half the number of samples (only 8 instead of 16) for data sampling and
clock recovery, and therefore requires more accurate baud rate setting and system
clock.
The data reception will differ slightly from Normal mode. Since the speed is doubled, the
Receiver front-end logic samples the signals on RXD pin at a frequency eight times the
baud rate. While the line is idle, one single sample of logical zero will be interpreted as
the falling edge of a start bit, and the start bit detection sequence is initiated. Let sample
1 denote the first zero-sample. Following the 1 to 0-transition, the Receiver samples the
RXD pin at samples 4, 5, and 6. If two or more of these three samples are found to be
logical ones, the start bit is rejected as a noise spike and the receiver starts looking for
the next 1 to 0-transition.
If however, a valid start bit is detected, sampling of the data bits following the start bit is
performed. These bits are also sampled at samples 4, 5, and 6. The logical value found
in at least two of the three samples is taken as the bit value. All bits are shifted into the
Transmitter Shift Register as they are sampled. Sampling of an incoming character is
shown in Figure 48.
Figure 48. Sampling Received Data When the Transmission Speed is Doubled
RXD
START BIT D0 D1 D2 D3 D4 D5 D6 D7 STOP BIT
RECEIVER
SAMPLING
The Baud Rate Generator in Note that the baud-rate equation is different from the equation on page 78 when the
Double UART Speed Mode UART speed is doubled:
f CK
BAUD = ------------------------------
8(UBR + 1 )
78 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
number of samples are reduced, and the system clock might have some variance (this
applies especially when using resonators), it is recommended that the baud rate error is
less than 0.5%.
Table 28. UBR Settings at Various Crystal Frequencies in Double Speed Mode
1.0000 MHz % Error 1.8432 MHz % Error 2.0000 MHz % Error
UBR = 51 0.2 UBR = 95 0.0 UBR = 103 0.2
UBR = 25 0.2 UBR = 47 0.0 UBR = 51 0.2
UBR = 12 0.2 UBR = 23 0.0 UBR = 25 0.2
UBR = 8 3.7 UBR = 15 0.0 UBR = 16 2.1
UBR = 6 7.5 UBR = 11 0.0 UBR = 12 0.2
UBR = 3 7.8 UBR = 7 0.0 UBR = 8 3.7
UBR = 2 7.8 UBR = 5 0.0 UBR = 6 7.5
UBR = 1 7.8 UBR = 3 0.0 UBR = 3 7.8
UBR = 1 22.9 UBR = 2 0.0 UBR = 2 7.8
UBR = 0 84.3 UBR = 1 0.0 UBR = 1 7.8
- - UBR = 0 0.0 - -
79
1142E–AVR–02/03
Two-wire Serial The Two-wire Serial Interface supports bi-directional serial communication. It is
designed primarily for simple but efficient integrated circuit (IC) control. The system is
Interface (Byte
comprised of two lines, SCL (Serial Clock) and SDA (Serial Data) that carry information
Oriented) between the ICs connected to them. Various communication configurations can be
designed using this bus. Figure 49 shows a typical Two-wire Serial Bus configuration.
Any device connected to the bus can be master or slave. Note that all AVR devices con-
nected to the bus must be powered to allow any bus operation.
V
CC
SCL
SDA
SCL 1 2 7 8 9 1 2 8 9
START ACK ACK
CONDITION
The block diagram of the Two-wire Serial Interface is shown in Figure 51.
80 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
ADDRESS REGISTER
AND
COMPARATOR
TWAR
STATE MACHINE
STATUS
AND
REGISTER
STATUS DECODER
TWSR
The CPU interfaces with the Two-wire Serial Interface via the following five I/O Regis-
ters: the Two-wire Serial Interface Bit Rate Register (TWBR), the Two-wire Serial
Interface Control Register (TWCR), the Two-wire Serial Interface Status Register
(TWSR), the Two-wire Serial Interface Data Register (TWDR), and the Two-wire Serial
Interface Address Register (TWAR, used in Slave mode).
81
1142E–AVR–02/03
The Two-wire Serial Interface
Bit 7 6 5 4 3 2 1 0
Bit Rate Register – TWBR
$00 ($20) TWBR7 TWBR6 TWBR5 TWBR4 TWBR3 TWBR2 TWBR1 TWBR0 TWBR
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
f CK
Bit Rate = -----------------------------------------------------------
16 + 2(TWBR) + t A f CK
TWBR should be set to a value higher than seven to ensure correct Two-wire Serial Bus
functionality. The bus alignment adjustion is automatically inserted by the Two-wire
Serial Interface, and ensures the validity of setup and hold times on the bus for any
TWBR value higher than seven. This adjustment may vary from 200 ns to 600 ns
depending on bus loads and drive capabilities of the devices connected to the bus.
82 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
83
1142E–AVR–02/03
• Bit 0 – TWIE: Two-wire Serial Interface Interrupt Enable
When this bit is enabled, and the I-bit in SREG is set, the Two-wire Serial Interface inter-
rupt will be activated for as long as the TWINT Flag is high.
The TWCR is used to control the operation of the Two-wire Serial Interface. It is used to
enable the Two-wire Serial Interface, 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.
84 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
• Bit 0 – TWGCE: Two-wire Serial Interface General Call Recognition Enable Bit
This bit enables, if set, the recognition of the General Call given over the Two-wire Serial
Bus.
The TWAR should be loaded with the 7-bit slave address (in the seven most significant
bits of TWAR) to which the Two-wire Serial Interface will respond when programmed as
a Slave Transmitter or Receiver, and not needed in the Master modes. The LSB of
TWAR is used to enable recognition of the general call address ($00). There is an asso-
ciated address comparator that looks for the slave address (or generall call address if
enabled) in the received serial address. If a match is found, an interrupt request is
generated.
Two-wire Serial Interface The Two-wire Serial Interface can operate in four different modes:
Modes • Master Transmitter
• Master Receiver
• Slave Receiver
• Slave Transmitter
Data transfer in each mode of operation is shown in Figure 52 to Figure 55. These fig-
ures contain the following abbreviations:
S: 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
In Figure 52 to Figure 55, circles are used to indicate that the Two-wire Serial Interface
Interrupt Flag is set. The numbers in the circles show the status code held in TWSR. At
these points, actions must be taken by the application to continue or complete the Two-
wire Serial Bus transfer. The Two-wire Serial Bus transfer is suspended until the Two-
wire Serial Interface Interrupt Flag is cleared by software.
The Two-wire Serial Interface Interrupt Flag is not automatically cleared by hardware
when executing the interrupt routine. Software has to clear the flag to continue the Two-
wire transfer. Also note that the Two-wire Serial Interface starts execution as soon as
this bit is cleared, so that all access to TWAR, TWDR, and TWSR must have been com-
pleted before clearing this flag.
85
1142E–AVR–02/03
When the Two-wire Serial Interface Interrupt Flag is set, the status code in TWSR 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 in Table 32 to Table
36.
Master Transmitter Mode In the Master Transmitter mode, a number of data bytes are transmitted to a Slave
Receiver (see Figure 52). Before Master Transmitter mode can be entered, the TWCR
must be initialized as follows:
Table 29. TWCR: Master Transmitter Mode Initialization
TWCR TWINT TWEA TWSTA TWSTO TWWC TWEN – TWIE
Value 0 X 0 0 0 1 0 X
TWEN must be set to enable the Two-wire Serial Interface, TWSTA and TWSTO must
be cleared.
The Master Transmitter mode may now be entered by setting the TWSTA bit. The Two-
wire Serial Interface logic will then test the Two-wire Serial Bus and generate a START
condition as soon as the bus becomes free. When a START condition is transmitted, the
Two-wire Serial Interface Interrupt Flag (TWINT) is set by hardware, and the status code
in TWSR will be $08. TWDR must then be loaded with the slave address and the data
direction bit (SLA+W). Clearing the TWINT bit in software will continue the transfer. The
TWINT Flag is cleared by writing a logic one to the flag.
When the slave address and the direction bit have been transmitted and an acknowl-
edgement 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 $18, $20, or $38. The
appropriate action to be taken for each of these status codes is detailed in Table 32. The
data must be loaded when TWINT is high only. If not, the access will be discarded, and
the Write Collision bit – TWWC will be set in the TWCR Register. This scheme is
repeated until the last byte is sent and the transfer is ended by generating a STOP con-
dition or a repeated START condition. A STOP condition is generated by setting
TWSTO, a repeated START condition is generated by setting TWSTA and TWSTO.
After a repeated START condition (state $10) the Two-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 loosing control over the bus.
Assembly code illustrating operation of the Master Transmitter mode is given at the end
of the TWI section.
Master Receiver Mode In the Master Receiver mode, a number of data bytes are received from a Slave Trans-
mitter (see Figure 53). The transfer is initialized as in the Master Transmitter mode.
When the START condition has been transmitted, the TWINT Flag is set by hardware.
The software must then load TWDR with the 7-bit slave address and the Data Direction
bit (SLA+R). The transfer will then continue when the TWINT Flag is cleared by
software.
When the slave address and the direction bit have been transmitted and an acknowl-
edgement 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 $40, $48, or $38. The
appropriate action to be taken for each of these status codes is detailed in Table 52.
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 and a STOP
condition is transmitted by writing a logic one to the TWSTO bit in the TWCR Register.
86 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
After a repeated START condition (state $10), the Two-wire Serial Interface may switch
to the Master Transmitter mode by loading TWDR with SLA+W or access a new Slave
as Master Receiver or Transmitter.
Assembly code illustrating operation of the Master Receiver mode is given at the end of
the TWI section.
Slave Receiver Mode In the Slave Receiver mode, a number of data bytes are received from a Master Trans-
mitter (see Figure 54). To initiate the Slave Receiver mode, TWAR and TWCR must be
initialized as follows:
Table 30. TWAR: Slave Receiver Mode Initialization
TWAR TWA6 TWA5 TWA4 TWA3 TWA2 TWA1 TWA0 TWGCE
Value Device’s Own Slave Address
The upper seven bits are the address to which the Two-wire Serial Interface will respond
when addressed by a Master. If the LSB is set, the Two-wire Serial Interface will
respond to the general call address ($00), otherwise it will ignore the general call
address.
Table 31. WCR: Slave Receiver Mode Initialization
TWCR TWINT TWEA TWSTA TWSTO TWWC TWEN – TWIE
Value 0 1 0 0 0 1 0 X
TWEN must be set to enable the Two-wire Serial Interface. The TWEA bit must be set to
enable the acknowledgement of the device’s own slave address or the general call
address. TWSTA and TWSTO must be cleared.
When TWAR and TWCR have been initialized, the Two-wire Serial Interface waits until
it is addressed by its own slave address (or the general call address if enabled) followed
by the Data Direction bit which must be “0” (write) for the Two-wire Serial Interface to
operate in the Slave Receiver mode. After its own slave address and the write bit have
been received, the Two-wire Serial Interface Interrupt Flag is set and a valid status code
can be read from TWSR. The status code is used to determine the appropriate software
action. The appropriate action to be taken for each status code is detailed in Table 34.
The Slave Receiver mode may also be entered if arbitration is lost while the Two-wire
Serial Interface is in the Master mode (see states $68 and $78).
If the TWEA bit is reset during a transfer, the Two-wire Serial Interface will return a “Not
Acknowledge” (“1”) to SDA after the next received data byte. While TWEA is Reset, the
Two-wire Serial Interface does not respond to its own slave address. However, the Two-
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
Two-wire Serial Interface from the Two-wire Serial Bus.
In ADC Noise Reduction mode, Power-down mode, and Power-save mode, the clock
system to the Two-wire Serial Interface is turned off. If the Slave Receive mode is
enabled, the interface can still acknowledge a general call and its own slave address by
using the Two-wire Serial Bus clock as a clock source. The part will then wake-up from
sleep and the Two-wire Serial Interface will hold the SCL clock wil low during the wake-
up and until the TWINT Flag is cleared.
Note that the Two-wire Serial Interface Data Register – TWDR – does not reflect the last
byte present on the bus when waking up from these sleep modes.
Assembly code illustrating operation of the Slave Receiver mode is given at the end of
the TWI section.
87
1142E–AVR–02/03
Slave Transmitter Mode In the Slave Transmitter mode, a number of data bytes are transmitted to a Master
Receiver (see Figure 55). The transfer is initialized as in the Slave Receiver mode.
When TWAR and TWCR have been initialized, the Two-wire Serial Interface waits until
it is addressed by its own slave address (or the general call address if enabled) followed
by the Data Direction bit which must be “1” (read) for the Two-wire Serial Interface to
operate in the Slave Transmitter mode. After its own slave address and the read bit
have been received, the Two-wire Serial Interface Interrupt Flag is set and a valid status
code can be read from TWSR. The status code is used to determine the appropriate
software action. The appropriate action to be taken for each status code is detailed in
Table 35. The slave transmitter mode may also be entered if arbitration is lost while the
Two-wire Serial Interface is in the Master mode (see state $B0).
If the TWEA bit is reset during a transfer, the Two-wire Serial Interface will transmit the
last byte of the transfer and enter state $C0 or state $C8. the Two-wire Serial Interface
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. While TWEA is
reset, the Two-wire Serial Interface does not respond to its own slave address. How-
ever, the Two-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 Two-wire Serial Interface from the Two-wire Serial Bus.
Assembly code illustrating operation of the Slave Receiver mode is given at the end of
the TWI section.
Miscellaneous States There are two status codes that do not correspond to a defined Two-wire Serial Inter-
face state, see Table 36.
Status $F8 indicates that no relevant information is available because the Two-wire
Serial Interface Interrupt Flag (TWINT) is not set yet. This occurs between other states,
and when the Two-wire Serial Interface is not involved in a serial transfer.
Status $00 indicates that a bus error has occured during a Two-wire Serial Bus transfer.
A bus error occurs when a START or STOP condition occurs at an illegal position in the
format frame. Examples of such illegal positions are during the serial transfer of an
address byte, a data byte or an acknowledge bit. When a bus error occurs, TWINT is
set. To recover from a bus error, the TWSTO Flag must set and TWINT must be cleared
by writing a logic one to it. This causes the Two-wire Serial Interface to enter the not
addressed Slave mode and to clear the TWSTO Flag (no other bits in TWCR are
affected). The SDA and SCL lines are released and no STOP condition is transmitted.
88 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
89
1142E–AVR–02/03
Figure 52. Formats and States in the Master Transmitter Mode
MT
Successfull
Transmission S SLA W A DATA A P
to a Slave
Receiver
Next Transfer
Started with a S SLA W
Repeated Start
Condition
$10
Not Acknowledge R
Received After the A P
Slave Address
$20
MR
Not Acknowledge
Received After a Data A P
Byte
$30
$38 $38
To Corresponding
$68 $78 $B0 States in Slave Mode
Assembly Code Example – ;The Slave being addressed has address 0x64. The code examples also assumes
Master Transmitter Mode some sort of error handling routine named ERROR.
;Part specific include file and TWI include file must be included.
wait1: in r16,TWCR ; Wait for TWINT Flag set. This indicates that
sbrs r16,TWINT ; the START condition has been transmitted
rjmp wait1
90 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
brne ERROR
wait2:in r16, TWCR ; Wait for TWINT Flag set. This indicates that
sbrs r16, TWINT ; SLA+W has been transmitted, and ACK/NACK has
rjmp wait2 ; been received
ldi r16, 0x33 ; Load data (here, data = 0x33) into TWDR Register
out TWDR, r16
ldi r16, (1<<TWINT) | (1<<TWEN)
out TWCR, r16 ; Clear TWINT bit in TWCR to start transmission of data
wait3:in r16, TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT; data has been transmitted, and ACK/NACK has
rjmp wait3 ; been received
ldi r16, 0x44 ; Load data (here, data = 0x44) into TWDR Register
out TWDR, r16
ldi r16, (1<<TWINT) | (1<<TWEN)
out TWCR, r16 ; Clear TWINT bit in TWCR to start transmission of data
wait4:in r16, TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT; data has been transmitted, and ACK/NACK has
rjmp wait4 ; been received
91
1142E–AVR–02/03
Table 33. Status Codes for Master Receiver Mode
Application Software Response
Status of the Two-wire Serial
To TWCR
Status Code Bus and Two-wire Serial Inter- Next Action Taken by Two-wire Serial Interface Hard-
To/from TWDR
(TWSR) face hardware STA STO TWINT TWEA ware
$08 A START condition has been Load SLA+R X 0 1 X SLA+R will be transmitted
transmitted ACK or NOT ACK will be received
$10 A repeated START condition Load SLA+R or X 0 1 X SLA+R will be transmitted
has been transmitted ACK or NOT ACK will be received
Load SLA+W X 0 1 X SLA+W will be transmitted
Logic will switch to Master Transmitter mode.
$38 Arbitration lost in SLA+R or No TWDR action or 0 0 1 X Two-wire Serial Bus will be released and not addressed
NOT ACK bit Slave mode will be entered
No TWDR actio 1 0 1 X A START condition will be transmitted when the bus
becomes free
$40 SLA+R has been transmitted; No TWDR action or 0 0 1 0 Data byte will be received and NOT ACK will be
ACK has been received returned
No TWDR action 0 0 1 1 Data byte will be received and ACK will be returned
$48 SLA+R has been transmitted; No TWDR action or 1 0 1 X Repeated START will be transmitted
NOT ACK has been received No TWDR action or 0 1 1 X STOP condition will be transmitted and TWSTO Flag
will be Reset
No TWDR action 1 1 1 X STOP condition followed by a START condition will be
transmitted and TWSTO Flag will be Reset
$50 Data byte has been received; Read data byte or 0 0 1 0 Data byte will be received and NOT ACK will be
ACK has been returned returned
Read data byte 0 0 1 1 Data byte will be received and ACK will be returned
$58 Data byte has been received; Read data byte or 1 0 1 X Repeated START will be transmitted
NOT ACK has been returned Read data byte or 0 1 1 X STOP condition will be transmitted and TWSTO Flag
will be Reset
Read data byte 1 1 1 X STOP condition followed by a START condition will be
transmitted and TWSTO Flag will be Reset
Successfull
Reception S SLA R A DATA A DATA A P
From a Slave
Receiver
Next Transfer
Started with a S SLA R
Repeated Start
Condition
$10
Not Acknowledge W
Received After the A P
Slave Address
$48
MT
Arbitration Lost in Slave Other Master Other Master
Address or Data Byte A or A Continues A Continues
$38 $38
To corresponding
$68 $78 $B0 states in slave mode
92 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Assembly Code Example – ;Part specific include file and TWI include file must be included.
Master Receiver Mode ; <Initialize registers TWAR and TWBR>
wait5:in r16,TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT ; the START condition has been transmitted
rjmp wait5
wait6:in r16,TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT ; SLA+R has been transmitted, and ACK/NACK has
rjmp wait6 ; been received
93
1142E–AVR–02/03
sbrs r16, TWINT ; data has been received and ACK returned
rjmp wait8
94 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
95
1142E–AVR–02/03
Figure 54. Formats and States in the Slave Receiver Mode
Reception of the Own
Slave Address and One or S SLA W A DATA A DATA A P or S
More Data Bytes. All are
Acknowledged
$88
$68
$98
$78
Assembly Code Example – ;Part specific include file and TWI include file must be included.
Slave Receiver Mode ; <Initialize registers TWAR and TWBR>
wait10:in r16,TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT ; START followed by SLA+W has been received
rjmp wait10
96 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
97
1142E–AVR–02/03
Table 35. Status Codes for Slave Transmitter Mode
Application Software Response
Status of the Two-wire Serial Bus
To TWCR
Status Code and Two-wire Serial Interface Next Action Taken by Two-wire Serial Interface Hard-
To/from TWDR
(TWSR) hardware STA STO TWINT TWEA ware
$A8 Own SLA+R has been received; Load data byte or X 0 1 0 Last data byte will be transmitted and NOT ACK should
ACK has been returned be received
Load data byte X 0 1 1 Data byte will be transmitted and ACK should be re-
ceived
$B0 Arbitration lost in SLA+R/W as Load data byte or X 0 1 0 Last data byte will be transmitted and NOT ACK should
master; own SLA+R has been be received
received; ACK has been returned Load data byte X 0 1 1 Data byte will be transmitted and ACK should be re-
ceived
$B8 Data byte in TWDR has been Load data byte or X 0 1 0 Last data byte will be transmitted and NOT ACK should
transmitted; ACK has been be received
received Load data byte X 0 1 1 Data byte will be transmitted and ACK should be re-
ceived
$C0 Data byte in TWDR has been No TWDR action or 0 0 1 0 Switched to the not addressed Slave mode;
transmitted; NOT ACK has been no recognition of own SLA or GCA
received No TWDR action or 0 0 1 1 Switched to the not addressed Slave mode;
own SLA will be recognized;
GCA will be recognized if TWGCE = “1”
No TWDR action or 1 0 1 0 Switched to the not addressed Slave mode;
no recognition of own SLA or GCA;
a START condition will be transmitted when the bus
becomes free
No TWDR action 1 0 1 1 Switched to the not addressed Slave mode;
own SLA will be recognized;
GCA will be recognized if TWGCE = “1”;
a START condition will be transmitted when the bus
becomes free
$C8 Last data byte in TWDR has been No TWDR action or 0 0 1 0 Switched to the not addressed Slave mode;
transmitted (TWEA = “0”); ACK no recognition of own SLA or GCA
has been received No TWDR action or 0 0 1 1 Switched to the not addressed Slave mode;
own SLA will be recognized;
GCA will be recognized if TWGCE = “1”
No TWDR action or 1 0 1 0 Switched to the not addressed slave mode;
no recognition of own SLA or GCA;
a START condition will be transmitted when the bus
becomes free
No TWDR action 1 0 1 1 Switched to the not addressed Slave mode;
own SLA will be recognized;
GCA will be recognized if TWGCE = “1”;
a START condition will be transmitted when the bus
becomes free
$B0
$C8
98 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Assembly Code Example – ; Part specific include file and TWI include file must be included.
Slave Transmitter Mode ; <Initialize registers, including TWAR, TWBR and TWCR>
wait14:in r16,TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT ; SLA+R has been received, and ACK/NACK has
rjmp wait14 ; been returned
ldi r16, 0x33 ; Load data (here, data = 0x33) into TWDR Register
out TWDR, r16
ldi r16, (1<<TWINT) | (1<<TWEA) | (1<<TWEN)
out TWCR, r16 ; Clear TWINT bit in TWCR to start transmission of
; data. Setting TWEA indicates that ACK should be
; received when transfer finished
; <Send more data bytes if needed>
wait15: in r16,TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT ; data has been transmitted, and ACK/NACK has
rjmp wait15 ; been received
ldi r16, 0x44 ; Load data (here, data = 0x44) into TWDR Register
out TWDR, r16
ldi r16, (1<<TWINT) | (1<<TWEA) | (1<<TWEN)
out TWCR, r16 ; Clear TWINT bit in TWCR to start transmission of
; data. Setting TWEA indicates that ACK should be
; received when transfer finished
wait16:in r16,TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT ; data has been transmitted, and ACK/NACK has
rjmp wait16 ; been received
ldi r16, 0x55 ; Load data (here, data = 0x55) into TWDR Register
out TWDR, r16
ldi r16, (1<<TWINT) | (1<<TWEN)
out TWCR, r16 ; Clear TWINT bit in TWCR to start transmission of
; data. Not setting TWEA indicates that NACK should
99
1142E–AVR–02/03
; be received after data byte Master signalling end
; of transmission)
wait17:in r16,TWCR ; Wait for TWINT flag set. This indicates that
sbrs r16, TWINT ; data has been transmitted, and ACK/NACK has
rjmp wait17 ; been received
100 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
.equ ST_DATA_NACK =$C0 ;Data byte has been tramsmitted and NACK
;received
.equ ST_LAST_DATA =$C8 ;Last byte in I2DR has been transmitted (TWEA =
;’0’), ACK has been received
101
1142E–AVR–02/03
The Analog The Analog Comparator compares the input values on the positive pin PB2 (AIN0) and
negative pin PB3 (AIN1). When the voltage on the positive pin PB2 (AIN0) is higher than
Comparator
the voltage on the negative pin PB3 (AIN1), the Analog Comparator Output, ACO, is set
(one). 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 in
Figure 56.
BANDGAP
REFERENCE
ACBG
ACME
ADEN
ADC MULTIPLEXER
OUTPUT 1)
102 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
When changing the ACIS1/ACIS0 bits, The Analog Comparator Interrupt must be dis-
abled by clearing its Interrupt Enable bit in the ACSR Register. Otherwise an interrupt
can occur when the bits are changed.
103
1142E–AVR–02/03
Analog Comparator It is possible to select any of the PA7..0 (ADC7..0) pins to replace the negative input to
Multiplexed Input the Analog Comparator. The ADC multiplexer is used to select this input, and conse-
quently, the ADC must be switched off to utilize this feature. If the Analog Comparator
Multiplexer Enable bit (ACME in SFIOR) is set (one) and the ADC is switched off (ADEN
in ADCSR is zero), MUX2..0 in ADMUX select the input pin to replace the negative input
to the Analog Comparator, as shown in Table 38. If ACME is cleared (zero) or ADEN is
set (one), PB3 (AIN1) is applied to the negative input to the Analog Comparator.
104 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Analog to Digital
Converter
105
1142E–AVR–02/03
Figure 57. Analog to Digital Converter Block Schematic
ADC CONVERSION
COMPLETE IRQ
ADIE
ADIF
15 0
ADC MULTIPLEXER ADC CTRL. & STATUS ADC DATA REGISTER
SELECT (ADMUX) REGISTER (ADCSR) (ADCH/ADCL)
REFS1
REFS0
ADLAR
MUX4
MUX3
MUX2
MUX1
MUX0
ADPS2
ADPS1
ADPS0
ADEN
ADSC
ADFR
ADIF
ADC[9:0]
PRESCALER
MUX DECODER
CHANNEL SELECTION
CONVERSION LOGIC
AVCC
INTERNAL 2.56 V
REFERENCE SAMPLE & HOLD
COMPARATOR
AREF
10-BIT DAC -
+
AGND
1.22 V BANDGAP
REFERENCE
ADC7
ADC6
ADC MULTIPLEXER
ADC5 INPUT OUTPUT
MUX
ADC4
ADC3
ADC2
ADC1
ADC0
Operation The ADC converts an analog input voltage to a 10-bit digital value through successive
approximation. The minimum value represents AGND and the maximum value repre-
sents the voltage on the AREF pin minus 1 LSB. Optionally, AVCC or an internal 2.56V
reference voltage may be connected to the AREF pin by writing to the REFSn bits in the
ADMUX Register. The internal voltage reference may thus be decoupled by an external
capacitor at the AREF pin to improve noise immunity.
The analog input channel is selected by writing to the MUX bits in ADMUX. Any of the
eight ADC input pins ADC7..0, as well as AGND and a fixed bandgap voltage reference
of nominally 1.22V (VBG), can be selected as single ended inputs to the ADC.
The ADC can operate in two modes – Single Conversion and Free Running mode. In
Single Conversion mode, each conversion will have to be initiated by the user. In Free
Running mode, the ADC is constantly sampling and updating the ADC Data Register.
The ADFR bit in ADCSR selects between the two available modes.
The ADC is enabled by setting the ADC Enable bit, ADEN in ADCSR. Voltage reference
and input channel selections will not go into effect until ADEN is set. The ADC does not
106 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
consume power when ADEN is cleared, so it is recommended to switch off the ADC
before entering power saving sleep modes.
A conversion is started by writing a logical one to the ADC Start Conversion bit, ADSC.
This bit stays high as long as the conversion is in progress and will be set to zero by
hardware when the conversion is completed. If a different data channel is selected while
a conversion is in progress, the ADC will finish the current conversion before performing
the channel change.
The ADC generates a 10-bit result, which are presented in the ADC Data Registers,
ADCH and ADCL. By default, the result is presented right adjusted, but can optionally
be presented left adjusted by setting the ADLAR bit in ADMUX.
If the result is left adjusted and no more than 8-bit precision is required, it is sufficient to
read ADCH. Otherwise, ADCL must be read first, then ADCH, to ensure that the content
of the Data Registers belongs to the same conversion. Once ADCL is read, ADC access
to Data Registers is blocked. This means that if ADCL has been read, and a conversion
completes before ADCH is read, neither register is updated and the result from the con-
version is lost. When ADCH is read, ADC access to the ADCH and ADCL Registers is
re-enabled.
The ADC has its own interrupt which can be triggered when a conversion completes.
When ADC access to the Data Registers is prohibited between reading of ADCH and
ADCL, the interrupt will trigger even if the result is lost.
CK/128
CK/64
CK/32
CK/16
CK/2
CK/4
CK/8
ADPS0
ADPS1
ADPS2
107
1142E–AVR–02/03
When initiating a conversion by setting the ADSC bit in ADCSR, the conversion starts at
the following rising edge of the ADC clock cycle.
A normal conversion takes 13 ADC clock cycles. In certain situations, the ADC needs
more clock cycles to initalization and minimize offset errors. Extended conversions take
25 ADC clock cycles and occur as the first conversion after the ADC is switched on
(ADEN in ADCSR is set). Additionally, when changing voltage reference, the user may
improve accuracy by disregarding the first conversion result after the reference or MUX
setting was changed.
The actual sample-and-hold takes place 1.5 ADC clock cycles after the start of a normal
conversion and 13.5 ADC clock cycles after the start of an extended conversion. When
a conversion is complete, the result is written to the ADC Data Registers, and ADIF is
set. In Single Conversion mode, ADSC is cleared simultaneously. The software may
then set ADSC again, and a new conversion will be initated on the first rising ADC clock
edge. In Free Running mode, a new conversion will be started immediately after the
conversion completes, while ADSC remains high. Using Free Running mode and an
ADC clock frequency of 200 kHz gives the lowest conversion time with a maximum res-
olution, 65 µs, equivalent to 15 kSPS. For a summary of conversion times, see Table
39.
Figure 59. ADC Timing Diagram, Extended Conversion (Single Conversion Mode)
Next
Extended Conversion Conversion
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
108 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
11 12 13 1 2 3 4
Cycle Number
ADC Clock
ADSC
ADIF
ADC Noise Canceler The ADC features a Noise Canceler that enables conversion during ADC Noise Reduc-
Function tion mode (see “Sleep Modes” on page 35) to reduce noise induced from the CPU core
and other I/O peripherals. If other I/O peripherals must be active during conversion, this
mode works equivalently for Idle mode. To make use of this feature, the following proce-
dure should be used:
1. Make sure that the ADC is enabled and is not busy converting. Single Conver-
sion Mode must be selected and the ADC conversion complete interrupt must be
enabled.
ADEN = 1
ADSC = 0
ADFR = 0
ADIE = 1
2. Enter ADC Noise Reduction mode (or Idle mode). The ADC will start a conver-
sion once the CPU has been halted.
3. If no other interrupts occur before the ADC conversion completes, the ADC inter-
rupt will wake up the CPU and execute the ADC Conversion Complete interrupt
routine.
109
1142E–AVR–02/03
The ADC Multiplexer Selection
Bit 7 6 5 4 3 2 1 0
Register – ADMUX
$07 ($27) REFS1 REFS0 ADLAR MUX4 MUX3 MUX2 MUX1 MUX0 ADMUX
Read/Write R/W R/W R/W R/W R/W R/W R/W R/W
Initial Value 0 0 0 0 0 0 0 0
110 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
111
1142E–AVR–02/03
• Bits 2..0 – ADPS2..0: ADC Prescaler Select Bits
These bits determine the division factor between the XTAL frequency and the input
clock to the ADC.
ADLAR = 0
Bit 15 14 13 12 11 10 9 8
$05 ($25) SIGN – – – – – ADC9 ADC8 ADCH
$04 ($24) ADC7 ADC6 ADC5 ADC4 ADC3 ADC2 ADC1 ADC0 ADCL
7 6 5 4 3 2 1 0
Read/Write R R R R R R R R
R R R R R R R R
Initial Value 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
ADLAR = 1
Bit 15 14 13 12 11 10 9 8
$05 ($25) ADC9 ADC8 ADC7 ADC6 ADC5 ADC4 ADC3 ADC2 ADCH
$04 ($24) ADC1 ADC0 – – – – – – ADCL
7 6 5 4 3 2 1 0
Read/Write R R R R R R R R
R R R R R R R R
Initial Value 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
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. Conse-
quently, 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 in ADMUX affects the way the result is read from the registers. If ADLAR
is set, the result is left adjusted. If ADLAR is cleared (default), the result is right adjusted.
112 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Scanning Multiple Since change of analog channel always is delayed until a conversion is finished, the
Channels Free Running mode can be used to scan multiple channels without interrupting the con-
verter. Typically, the ADC Conversion Complete interrupt will be used to perform the
channel shift. However, the user should take the following fact into consideration:
The interrupt triggers once the result is ready to be read. In Free Running mode, the
next conversion will start immediately when the interrupt triggers. If ADMUX is changed
after the interrupt triggers, the next conversion has already started, and the old setting is
used.
ADC Noise Canceling Digital circuitry inside and outside the ATmega163 generates EMI which might affect the
Techniques accuracy of analog measurements. If conversion accuracy is critical, the noise level can
be reduced by applying the following techniques:
1. The analog part of the ATmega163 and all analog components in the application
should have a separate analog ground plane on the PCB. This ground plane is
connected to the digital ground plane via a single point on the PCB.
2. Keep analog signal paths as short as possible. Make sure analog tracks run over
the analog ground plane, and keep them well away from high-speed switching
digital tracks.
3. The AVCC pin on the ATmega163 should be connected to the digital VCC supply
voltage via an LC network as shown in Figure 62.
4. Use the ADC noise canceler function to reduce induced noise from the CPU.
5. If some Port A pins are used as digital outputs, it is essential that these do not
switch while a conversion is in progress.
PA1 (ADC1)
PA2 (ADC2)
VCC
GND
39 38 37 36 35 34
33 PA4 (ADC4)
32 PA5 (ADC5)
31 PA6 (ADC6)
30 PA7 (ADC7)
10µΗ
29 AREF
ATmega163
AGND
28
100nF
AVCC
27
26 PC7 (TOSC2)
113
1142E–AVR–02/03
ADC Characteristics
Table 43. ADC Characteristics
Symbol Parameter Condition Min Typ Max Units
Resolution Single-ended Conversion 10 Bits
VREF = 4V
Absolute accuracy 1 2 LSB
ADC clock = 200 kHz
VREF = 4V
Absolute accuracy 4 LSB
ADC clock = 1 MHz
VREF = 4V
Absolute accuracy 16 LSB
ADC clock = 2 MHz
Integral Non-linearity VREF > 2V 0.5 LSB
Differential Non-linearity VREF > 2V 0.5 LSB
Zero Error (Offset) VREF > 2V 1 LSB
Conversion Time Free Running Conversion 65 260 µs
Clock Frequency 50 200 kHz
(1) (2)
AVCC Analog Supply Voltage VCC - 0.3 VCC + 0.3 V
VREF Reference Voltage 2V AVCC V
VINT Internal Voltage Reference 2.35 2.56 2.77 V
VBG Bandgap Voltage Reference 1.12 1.22 1.32 V
RREF Reference Input Resistance 6 10 13 kΩ
114 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
I/O Ports 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 uninten-
tionally changing the direction of any other pin with the SBI and CBI instructions. The
same applies for changing drive value (if configured as output) or enabling/disabling of
pull-up resistors (if configured as input).
The Port A Input Pins Address – PINA – is not a register, and this address enables
access to the physical value on each Port A pin. When reading PORTA the PORTA
Data Latch is read, and when reading PINA, the logical values present on the pins are
read.
PORT A as General Digital I/O All 8 bits in PORT A are equal when used as digital I/O pins.
PAn, General I/O pin: The DDAn bit in the DDRA Register selects the direction of this
pin, if DDAn is set (one), PAn is configured as an output pin. If DDAn is cleared (zero),
PAn is configured as an input pin. If PORTAn is set (one) when the pin configured as an
input pin, the MOS pull up resistor is activated. To switch the pull up resistor off, the
PORTAn has to be cleared (zero), the pin has to be configured as an output pin, or the
115
1142E–AVR–02/03
PUD bit has to be set. The Port A pins are tri-stated when a reset condition becomes
active, even if the clock is not running.
PORT A Schematics Note that all port pins are synchronized. The synchronization latches are not shown in
the figure.
RD
MOS
PULL- PUD
UP
RESET
Q D
DDAn
C
WD
DATA BUS
RESET
PDn Q D
PORTAn
C
RL
WP
PWRDN RP
ADCn
TO ADC MUX
WP: WRITE PORTA
WD: WRITE DDRA
RL: READ PORTA LATCH
RP: READ PORTA PIN
RD: READ DDRA
n: 0-7
PUD: PULL-UP DISABLE
116 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
When the pins are used for the alternate function, the DDRB and PORTB Registers
have to be set according to the alternate function description.
The Port B Input Pins Address – PINB – is not a register, and this address enables
access to the physical value on each Port B pin. When reading PORTB, the PORTB
Data Latch is read, and when reading PINB, the logical values present on the pins are
read.
117
1142E–AVR–02/03
Port B As General Digital I/O All eight bits in Port B are equal when used as digital I/O pins. PBn, General I/O pin: The
DDBn bit in the DDRB Register selects the direction of this pin, if DDBn is set (one), PBn
is configured as an output pin. If DDBn is cleared (zero), PBn is configured as an input
pin. If PORTBn is set (one) when the pin configured as an input pin, the MOS pull up
resistor is activated. To switch the pull up resistor off, the PORTBn has to be cleared
(zero), the pin has to be configured as an output pin, or the PUD bit has to be set. The
Port B pins are tri-stated when a reset condition becomes active, even if the clock is not
running.
• SS – PORTB, Bit 4
SS: Slave Port Select input. When the SPI is enabled as a Slave, this pin is configured
as an input regardless of the setting of DDB4. As a slave, the SPI is activated when this
pin is driven low. When the SPI is enabled as a Master, the data direction of this pin is
controlled by DDB4. When the pin is forced to be an input, the pull-up can still be con-
trolled by the PORTB4 bit. See the description of the SPI port for further details.
118 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
• T1 – PORTB, Bit 1
T1, Timer/Counter1 Counter Source. See the Timer description for further details.
• T0 – PORTB, Bit 0
T0: Timer/Counter0 Counter Source. See the Timer description for further details.
Port B Schematics Note that all port pins are synchronized. The synchronization latches are not shown in
the figures.
PUD
119
1142E–AVR–02/03
Figure 65. PORTB Schematic Diagram (Pins PB2 and PB3)
RD
MOS
PULL- PUD
UP
RESET
Q D
DDBn
C
WD
DATA BUS
RESET
PBn Q D
PORTBn
C
RL
WP
PWRDN RP
AINm
TO COMPARATOR
WP: WRITE PORTB
WD: WRITE DDRB
RL: READ PORTB LATCH
RP: READ PORTB PIN
RD: READ DDRB
n: 2, 3
m: 0, 1
PUD: PULL-UP DISABLE
MOS
PULL- PUD
UP
RESET
Q D
DDB4
C
WD
RESET
DATA BUS
PB4 Q D
PORTB4
C
RL
WP
RP
MSTR
WP: WRITE PORTB
WD: WRITE DDRB SPE
RL: READ PORTB LATCH
RP: READ PORTB PIN
RD: READ DDRB
MSTR: SPI MASTER ENABLE
SPE: SPI ENABLE SPI SS
PUD: PULL-UP DISABLE
120 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
MOS PUD
PULL-
UP
RESET
R
Q D
DDB5
C
WD
DATA BUS
RESET
R
PB5 Q D
PORTB5
C
RL
WP
RP
SPI SLAVE
IN
MOS
PUD
PULL-
UP
RESET
R
Q D
DDB6
C
WD
DATA BUS
RESET
R
PB6 Q D
PORTB6
C
RL
WP
RP
121
1142E–AVR–02/03
Figure 69. PORTB Schematic Diagram (Pin PB7)
RD
MOS
PUD
PULL-
UP
RESET
R
Q D
DDB7
C
WD
DATA BUS
RESET
R
PB7 Q D
PORTB7
C
RL
WP
RP
SPI CLOCK
IN
122 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
The Port C Input Pins Address – PINC – is not a register, and this address enables
access to the physical value on each Port C pin. When reading PORTC, the PORTC
Data Latch is read, and when reading PINC, the logical values present on the pins are
read.
Port C as General Digital I/O All eight bits in PORT C are equal when used as digital I/O pins.
PCn, General I/O pin: The DDCn bit in the DDRC Register selects the direction of this
pin, if DDCn is set (one), PCn is configured as an output pin. If DDCn is cleared (zero),
PCn is configured as an input pin. If PORTCn is set (one) when the pin configured as an
input pin, the MOS pull up resistor is activated. To switch the pull up resistor off,
PORTCn has to be cleared (zero), the pin has to be configured as an output pin, or the
PUD bit has to be set. The Port C pins are tri-stated when a reset condition becomes
active, even if the clock is not running.
123
1142E–AVR–02/03
Table 48. DDCn Effects on PORT C Pins(1)
DDCn PORTCn PUD I/O Pull Up Comment
0 0 x Input No Tri-state (Hi-Z)
0 1 1 Input No Tri-state (Hi-Z)
0 1 0 Input Yes PCn will source current if ext. pulled low.
1 0 x Output No Push-pull Zero Output
1 1 x Output No Push-pull One Output
124 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Port C Schematics Note that all port pins are synchronized. The synchronization latches are not shown in
the figure.
0
DDCn
PUD
1
PCn n
1
SCL/SDA out
SCL/SDA in
TWEN
125
1142E–AVR–02/03
Figure 71. PORTC Schematic Diagram (Pins PC2 - PC5)
RD
MOS
PULL- PUD
UP
RESET
R
Q D
DDCn
C
WD
DATA BUS
RESET
R
PCn Q D
PORTCn
C
RL
WP
RP
MOS PUD
PULL-
UP
RESET
R
Q D
DDC6
C
WD
DATA BUS
RESET
R
PC6 Q D
PORTC6
C
RL
WP
RP
AS2
T/C2 OSC
AMP INPUT
WP: WRITE PORTC
WD: WRITE DDRC
RL: READ PORTC LATCH
RP: READ PORTC PIN
RD: READ DDRC
AS2: ASYNCH SELECT T/C2
PUD: PULL-UP DISABLE
126 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
PUD
127
1142E–AVR–02/03
Port D Port D is an 8 bit bi-directional I/O port with internal pull-up resistors.
Three I/O memory address locations are allocated for Port D, one each for the Data
Register – PORTD, $12($32), Data Direction Register – DDRD, $11($31) and the Port D
Input Pins – PIND, $10($30). The Port D Input Pins address is read only, while the Data
Register and the Data Direction Register are read/write.
The Port D output buffers can sink 20 mA. As inputs, Port D pins that are externally
pulled low will source current if the pull-up resistors are activated. Some Port D pins
have alternate functions as shown in Table 49.
The Port D Input Pins Address – PIND – is not a register, and this address enables
access to the physical value on each Port D pin. When reading PORTD, the PORTD
Data Latch is read, and when reading PIND, the logical values present on the pins are
read.
128 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Port D as General Digital I/O PDn, General I/O pin: The DDDn bit in the DDRD Register selects the direction of this
pin. If DDDn is set (one), PDn is configured as an output pin. If DDDn is cleared (zero),
PDn is configured as an input pin. If PDn is set (one) when configured as an input pin
the MOS pull up resistor is activated. To switch the pull up resistor off the PDn has to be
cleared (zero), the pin has to be configured as an output pin, or the PUD bit has to be
set. The Port D pins are tri-stated when a reset condition becomes active, even if the
clock is not running.
129
1142E–AVR–02/03
• INT0 – PORTD, Bit 2
INT0, External Interrupt Source 0: The PD2 pin can serve as an External Interrupt
Source to the MCU. See the interrupt description for further details, and how to enable
the source.
Port D Schematics Note that all port pins are synchronized. The synchronization latches are not shown in
the figures.
MOS PUD
PULL-
UP
RESET
Q D
DDD0
C
WD
DATA BUS
RESET
PD0 Q D
PORTD0
C
RL
WP
RP
130 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
RD
MOS PUD
PULL-
UP
RESET
R
Q D
DDD1
C
WD
DATA BUS
RESET
R
PD1 Q D
PORTD1
C
RL
WP
RP
PUD
131
1142E–AVR–02/03
Figure 77. PORTD Schematic Diagram (Pins PD4 and PD5)
PUD
RD
MOS
PULL- PUD
UP
RESET
R
Q D
DDD6
C
WD
DATA BUS
RESET
R
PD6 Q D
PORTD6
C
RL
WP
RP
132 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
PUD
133
1142E–AVR–02/03
Memory
Programming
Boot Loader Support The ATmega163 provides a mechanism for Programming and Re-programming code by
the MCU itself. This feature allows flexible application software updates, controlled by
the MCU using a Flash-resident Boot Loader program. This makes it possible to pro-
gram the AVR in a target system without access to its SPI pins. The Boot Loader
program can use any available data interface and associated protocol, such as UART
serial bus interface, to input or output program code, and write (program) that code into
the Flash memory, or read the code from the Flash memory.
The ATmega163 Flash memory is organized in two main sections:
• The Application Flash section
• The Boot Loader Flash section
The Application Flash section and the Boot Loader Flash section have seperate Boot
Lock bits. Thus the user can select different levels of protection for the two sections. The
Store Program Memory (SPM) instruction can only be executed from the Boot Loader
Flash section.
The Program Flash memory in ATmega163 is divided into 128 pages of 64 words each.
The Boot Loader Flash section is located at the high address space of the Flash, and
can be configured through the BOOTSZ Fuses as shown in Table 51.
134 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
$1EFF
$1F7F $1F00
$1F80 Boot Flash Section
Boot Flash Section 4 (256 x 16)
2 (128 x 16) $1FFF $1FFF
$1BFF
$1DFF $1C00
$1E00
Boot Flash Section
Boot Flash Section 16
8 (1024 x 16)
(512 x 16)
$1FFF $1FFF
135
1142E–AVR–02/03
Entering the Boot Loader The SPM instruction can access the entire Flash, but can only be executed from the
Program Boot Loader Flash section. If no Boot Loader capability is needed, the entire Flash is
available for application code. Entering the Boot Loader takes place by a jump or call
from the application program. This may be initiated by some trigger such as a command
received via UART or SPI interface, for example. Alternatively, the Boot Reset Fuse can
be programmed so that the Reset Vector is pointing to the Boot Flash start address after
a reset. In this case, the Boot Loader is started after a reset. After the application code is
loaded, the program can start executing the application code. Note that the fuses cannot
be changed by the MCU itself. This means that once the Boot Reset Fuse is pro-
grammed, the Reset Vector will always point to the Boot Loader Reset and the fuse can
only be changed through the serial or parallel programming interface.
Capabilities of the Boot The program code within the Boot Loader section has the capability to read from and
Loader write into the entire Flash, including the Boot Loader memory. This allows the user to
update both the Application code and the Boot Loader code that handles the software
update. The Boot Loader can thus even modify itself, and it can also erase itself from
the code if the feature is not needed anymore.
Self-Programming the Programming of the Flash is executed one page at a time. The Flash page must be
Flash erased first for correct programming. The general Write Lock (Lock bit 2) does not con-
trol the programming of the Flash memory by SPM instruction. Similarly, the general
Read/Write Lock (Lock bit 1) does not control reading nor writing by LPM/SPM, if it is
attempted.
The Program memory can only be updated page by page, not word by word. One page
is 128 bytes (64 words). The Program memory will be modified by first performing Page
Erase, then filling the temporary page buffer one word at a time using SPM, and
then executing Page Write. If only part of the page needs to be changed, the other
parts must be stored (for example in internal SRAM) before the erase, and then be re-
written. The temporary page buffer can be accessed in a random sequence. It is essen-
tial that the page address used in both the Page Erase and Page Write operation is
addressing the same page. See “Assembly code example for a Boot Loader” on page
141 for an assembly code example.
Se e Table 60 on p age 156 for typical p rogr amming times w hen usin g Self-
Programming.
Performing Page Erase by To execute Page Erase, set up the address in the Z-pointer, write “00011” to the five
SPM LSB in SPMCR and execute SPM within four clock cycles after writing SPMCR. The
data in R1 and R0 is ignored. The page address must be written to Z13:Z7. Other bits in
the Z-pointer will be ignored during this operation. It is recommended that the interrupts
are disabled during the page erase operation.
Fill the Temporary Buffer To write an instruction word, set up the address in the Z-pointer and data in R1:R0, write
(Page Load) “00001” to the five LSB in SPMCR and execute SPM within four clock cycles after writ-
ing SPMCR. The content of Z6:Z1 is used to address the data in the temporary buffer.
Z13:Z7 must point to the page that is supposed to be written.
136 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Perform a Page Write To execute Page Write, set up the address in the Z-pointer, write “00101” to the five LSB
in SPMCR and execute SPM within four clock cycles after writing SPMCR. The data in
R1 and R0 is ignored. The page address must be written to Z13:Z7. During this opera-
tion, Z6:Z0 must be zero to ensure that the page is written correctly. It is recommended
that the interrupts are disabled during the page write operation.
Consideration while Updating Special care must be taken if the user allows the Boot Loader section to be updated by
the Boot Loader Section leaving Boot Lock bit 11 unprogrammed. An accidental write to the Boot Loader itself
can corrupt the entire Boot Loader, and further software updates might be impossible. If
it is not necessary to change the Boot Loader software itself, it is recommended to pro-
gram the Boot Lock Bit 11 to protect the Boot Loader software from any internal
software changes.
Wait for SPM Instruction to Though the CPU is halted during Page Write, Page Erase or Lock bit write, for future
Complete compatibility, the user software must poll for SPM complete by reading the SPMCR
Register and loop until the SPMEN bit is cleared after a programming operation. See
“Assembly code example for a Boot Loader” on page 141 for a code example.
Instruction Word Read after To ensure proper instruction pipelining after programming action (Page Erase, Page
Page Erase, Page Write, and Write, or Lock bit write), the SPM instruction must be followed with the sequence (.dw
Lock Bit Write $FFFF - NOP) as shown below:
spm
.dw $FFFF
nop
If not, the instruction following SPM might fail. It is not necessary to add this sequence
when the SPM instruction only loads the temporary buffer.
Avoid Reading the Application During Self-Programming (either Page Erase or Page Write), the user software should
Section During Self- not read the application section. The user software itself must prevent addressing this
Programming section during the Self-Programming operations. This implies that interrupts must be
disabled. Before addressing the application section after the programming is completed,
for future compatibility, the user software must write “10001” to the five LSB in SPMCR
and execute SPM within four clock cycles. Then the user software should verify that the
ASB bit is cleared. See “Assembly code example for a Boot Loader” on page 141 for an
example. Though the ASB and ASRE bits have no special function in this device, it is
important for future code compatibility that they are treated as described above.
Boot Loader Lock Bits ATmega163 has two separate sets of Boot Lock bits which can be set independently.
This gives the user a unique flexibility to select different levels of protection.
The user can select:
• To protect the entire Flash from a software update by the MCU
• To only protect the Boot Loader Flash section from a software update by the MCU
• To only protect application Flash section from a software update by the MCU
• Allowing software update in the entire Flash
See Table and Table for further details. The Boot Lock bits can be set in software and
in Serial or Parallel Programming mode, but they can only be cleared by a chip erase
command.
137
1142E–AVR–02/03
Table 53. Boot Lock Bit0 Protection Modes (Application Section) (1)
BLB0 mode BLB02 BLB01 Protection
No restrictions for SPM, LPM accessing the Application
1 1 1
section
2 1 0 SPM is not allowed to write to the Application section
SPM is not allowed to write to the Application section, and
3 0 0 LPM executing from the Boot Loader section is not
allowed to read from the Application section
LPM executing from the Boot Loader section is not
4 0 1
allowed to read from the Application section
Table 54. Boot Lock Bit1 Protection Modes (Boot Loader Section)(1)
BLB1 mode BLB12 BLB11 Protection
No restrictions for SPM, LPM accessing the Boot Loader
1 1 1
section
2 1 0 SPM is not allowed to write to the Boot Loader section
SPM is not allowed to write to the Boot Loader section,
and LPM executing from the Application section is not
3 0 0 allowed to read from the Boot Loader section. If code is
executed from Boot section, the interrupts are disabled
when BLB12 is programmed.
LPM executing from the Application section is not allowed
to read from the Boot Loader section. If code is executed
4 0 1
from Boot section, the interrupts are disabled when BLB12
is programmed.
Setting the Boot Loader Lock To set the Boot Loader Lock bits, write the desired data to R0, write “00001001” to
Bits by SPM SPMCR and execute SPM within four clock cycles after writing SPMCR. The only
accessible Lock bits are the Boot Lock bits that may prevent the Application and Boot
Loader section from any software update by the MCU.
Bit 7 6 5 4 3 2 1 0
R0 1 1 BLB12 BLB11 BLB02 BLB01 1 1
If bits 5..2 in R0 are cleared (zero), the corresponding Boot Lock bit will be programmed
if an SPM instruction is executed within four cycles after BLBSET and SPMEN are set in
SPMCR.
Reading the Fuse and Lock It is possible to read both the Fuse and Lock bits from software. To read the Lock bits,
Bits from Software load the Z-pointer with $0001 and set the BLBSET and SPMEN bits in SPMCR. When
an LPM instruction is executed within five CPU cycles after the BLBSET and SPMEN
bits are set in SPMCR, the value of the Lock bits will be loaded in the destination regis-
ter. The BLBSET and SPMEN bits will auto-clear upon completion of reading the Lock
bits or if no SPM, or LPM, instruction is executed within four, respectively five, CPU
cycles. When BLBSET and SPMEN are cleared, LPM will work as described in “Con-
stant Addressing Using The LPM and SPM Instructions” on page 15 and in the
Instruction set Manual.
138 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Bit 7 6 5 4 3 2 1 0
Rd – – BLB12 BLB11 BLB02 BLB01 LB2 LB1
The algorithm for reading the Fuse Low bits is similar to the one described above for
reading the Lock bits. To read the Fuse Low bits, load the Z-pointer with $0000 and set
the BLBSET and SPMEN bits in SPMCR. When an LPM instruction is executed within
five cycles after the BLBSET and SPMEN bits are set in the SPMCR, the value of the
Fuse Low bits will be loaded in the destination register as shown below.
Bit 7 6 5 4 3 2 1 0
Rd BODLEVEL BODEN SPIEN – CKSEL3 CKSEL2 CKSEL1 CKSEL0
Similarly, when reading the Fuse High bits, load $0003 in the Z-pointer. When an LPM
instruction is executed within five cycles after the BLBSET and SPMEN bits are set in
the SPMCR, the value of the Fuse High bits will be loaded in the destination register as
shown below.
Bit 7 6 5 4 3 2 1 0
Rd – – – – – BOOTSZ1 BOOTSZ0 BOOTRST
Fuse and Lock bits that are programmed, will be read as zero. Fuse and Lock bits that
are unprogrammed, will be read as one.
In all cases, the read value of unused bit positions are undefined.
EEPROM Write Prevents Note that an EEPROM write operation will block all software programming to Flash.
Writing to SPMCR Reading the Fuses and Lock bits from software will also be prevented during the
EEPROM write operation. It is recommended that the user checks the status bit (EEWE)
in the EECR Register and verifies that the bit is cleared before writing to the SPMCR
Register. If EEPROM writing is performed inside an interrupt routine, the user software
should disable that interrupt before checking the EEWE status bit.
Addressing the Flash During The Z-pointer is used to address the SPM commands.
Self-Programming
Bit 15 14 13 12 11 10 9 8
ZH (R31) Z15 Z14 Z13 Z12 Z11 Z10 Z9 Z8
ZL (R30) Z7 Z6 Z5 Z4 Z3 Z2 Z1 Z0
7 6 5 4 3 2 1 0
139
1142E–AVR–02/03
Store Program Memory The Store Program Memory Control Register contains the control bits needed to control
Control Register – SPMCR the programming of the Flash from internal code execution.
Bit 7 6 5 4 3 2 1 0
$37 ($57) – ASB – ASRE BLBSET PGWRT PGERS SPMEN SPMCR
Read/Write R R R R/W R/W R/W R/W R/W
Initial Value x 0 0 0 0 0 0 0
140 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Preventing Flash During periods of low VCC, the Flash can be corrupted because the supply voltage is too
Corruption low for the CPU and the Flash to operate properly. These issues are the same as for
board level systems using the Flash, and the same design solutions should be applied.
A Flash corruption can be caused by two situations when the voltage is too low. First, a
regular write sequence to the Flash requires a minimum voltage to operate correctly.
Secondly, the CPU itself can execute instructions incorrectly, if the supply voltage for
executing instructions is too low.
Flash corruption can easily be avoided by following these design recommendations (one
is sufficient):
1. Keep the AVR RESET active (low) during periods of insufficient power supply
voltage. This can be done be enabling the internal Brown-out Detector (BOD) if
the operating voltage matches the detection level. If not, an external low VCC
Reset Protection circuit can be used. If a Reset occurs while a write operation is
in progress, the write operation will be completed provided that the power supply
voltage is sufficient. The total Reset Time must be longer thatn the Flash write
time. This can be achieved by holding the External Reset, or by selecting a long
Reset Time-out.
2. Keep the AVR core in Power-down sleep mode during periods of low VCC. This
will prevent the CPU from attempting to decode and execute instructions, effec-
tively protecting the Flash from unintentional writes.
Assembly code example for a ;- the routine writes one page of data from RAM to Flash
Boot Loader ; the first data location in RAM is pointed to by the Y pointer (lowest
address)
; the first data location in Flash is pointed to by the Z-pointer (lowest
address)
;- error handling is not included
;- the routine must be placed inside the boot space
; Only code inside boot loader
; section should be read during Self-Programming.
;- registers used: r0, r1, temp1, temp2, looplo, loophi, spmcrval
; storing and restoring of registers is not included in the routine
; register usage can be optimized at the expense of code size
;- It is assumed that the interrupts are disabled
.equ PAGESIZEB = PAGESIZE*2 ;PAGESIZEB is page size in BYTES,
not words
.org SMALLBOOTSTART
Write_page:
; page erase
ldi spmcrval, (1<<PGERS) + (1<<SPMEN)
call Do_spm
141
1142E–AVR–02/03
; re-enable the Application Section
ldi spmcrval, (1<<ASRE) + (1<<SPMEN)
call Do_spm
Do_spm:
; input: spmcrval determines SPM action
; check that no EEPROM write access is running
Wait_ee:
sbic EECR, EEWE
rjmp Wait_ee
; SPM timed sequence
out SPMCR, spmcrval
spm
.dw $FFFF ; ensure proper pipelining
nop ; of next instruction
; check for SPM complete
Wait_spm:
in temp1, SPMCR
142 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Program and Data The ATmega163 provides six Lock bits which can be left unprogrammed (“1”) or can be
Memory Lock Bits programmed (“0”) to obtain the additional features listed in Table 55. The Lock bits can
only be erased to “1” with the Chip Erase command.
Note: 1. Program the Fuse bits before programming the Lock bits.
143
1142E–AVR–02/03
Fuse Bits The ATmega163 has ten Fuse bits, divided in two groups. The Fuse High bits are
BOOTSZ1..0 and BOOTRST, and the Fuse Low bits are BODLEVEL, BODEN, SPIEN,
and CKSEL3..0.
• BOOTSZ1..0 select the size and start address of the Boot Flash section according
to Table 51 on page 134. Default value is “11” (both unprogrammed).
• When BOOTRST is programmed (“0”), the Reset Vector is set to the start address of
the Boot Flash section, as selected by the BOOTSZ fuses according to Table 51 on
page 134. If the BOOTRST is unprogrammed (“1”), the Reset Vector is set to
address $0000. Default value is unprogrammed (“1”).
• The BODLEVEL Fuse selects the Brown-out Detection Level and changes the Start-
up times, according to Table 4 on page 24 and Table 5 on page 25, respectively.
Default value is unprogrammed (“1”).
• When the BODEN Fuse is programmed (“0”), the Brown-out Detector is enabled.
See “Reset and Interrupt Handling” on page 21. Default value is unprogrammed
(“1”).
• When the SPIEN Fuse is programmed (“0”), Serial Program and Data Downloading
are enabled. Default value is programmed (“0”). The SPIEN Fuse is not accessible
in serial programming mode.
• CKSEL3..0 select the clock source and the start-up delay after reset, according to
Table 1 on page 5 and Table 5 on page 25. Default value is “0010” (Internal RC
Oscillator).
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.
Signature Bytes All Atmel microcontrollers have a three-byte signature code which identifies the device.
This code can be read in both serial and parallel mode. The three bytes reside in a sep-
arate address space.
The ATmega163 the signature bytes are:
1. $000: $1E (indicates manufactured by Atmel).
2. $001: $94 (indicates 16KB Flash memory).
3. $002: $02 (indicates ATmega163 device when $001 is $94).
Calibration Byte The ATmega163 has a one byte calibration value for the internal RC Oscillator. This
byte resides in the high byte of address $000 in the signature address space. During
Memory Programming, the external programmer must read this location and program it
into a selected location in the normal Flash Program memory. At start-up, the user soft-
ware must read this Flash location and write the value to the OSCCAL Register.
144 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Parallel Programming This section describes how to Parallel Program and verify Flash Program memory,
EEPROM Data memory + Program And Data Memory Lock bits and Fuse bits in the
ATmega163. Pulses are assumed to be at least 500ns unless otherwise noted.
Signal Names In this section, some pins of the ATmega163 are referenced by signal names describing
their functionality during parallel programming, see Figure 81 and Table 56. Pins not
described in the following table are referenced by pin names.
The XA1/XA0 pins determine the action executed when the XTAL1 pin is given a posi-
tive pulse. The bit coding are shown in Table 57.
When pulsing WR or OE, the command loaded determines the action executed. The
Command is a byte where the different bits are assigned functions as shown in Table
58.
The BS2 pin should be low unless otherwise noted.
XA1 PD6
PAGEL PD7
+12 V RESET
BS2 PA0
XTAL1
GND AGND
145
1142E–AVR–02/03
Table 56. Pin Name Mapping (Continued)
Signal Name in
Programming Mode Pin Name I/O Function
PAGEL PD7 I Program Memory Page Load
Byte Select 2 (“0” selects low byte, “1” selects 2’nd
BS2 PA0 I
high byte)
DATA PB7 - 0 I/O Bidirectional Databus (Output when OE is low)
Enter Programming Mode The following algorithm puts the device in Parallel Programming mode:
1. Apply 4.5 - 5.5V between VCC and GND.
2. Set RESET and BS pins to “0” and wait at least 100 ns.
3. Apply 11.5 - 12.5V to RESET. Any activity on BS1 within 100 ns after +12V has
been applied to RESET, will cause the device to fail entering Programming
mode.
Chip Erase The Chip Erase command will erase the Flash and EEPROM memories and the Lock
bits. The Lock bits are not reset until the Program memory has been completely erased.
The Fuse bits are not changed. A Chip Erase must be performed before the Flash is re-
programmed.
Load Command “Chip Erase”
1. Set XA1, XA0 to “10”. This enables command loading.
2. Set BS1 to “0”.
146 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
3. Set DATA to “1000 0000”. This is the command for Chip Erase.
4. Give WR a negative pulse. This starts the Chip Erase. RDY/BSY goes low.
5. Wait until RDY/BSY goes high before loading a new command.
Programming the Flash The Flash is organized as 128 pages of 128 bytes each. When programming the Flash,
the program data is latched into a page buffer. This allows one page of program data to
be programmed simultaneously. The following procedure describes how to program the
entire Flash memory:
A. Load Command “Write Flash”
1. Set XA1, XA0 to “10”. This enables command loading.
2. Set BS1 to “0”.
3. Set DATA to “0001 0000”. This is the command for Write Flash.
4. Give XTAL1 a positive pulse. This loads the command.
B. Load Address Low Byte
1. Set XA1, XA0 to “00”. This enables address loading.
2. Set BS1 to “0”. This selects low address.
3. Set DATA = Address Low Byte ($00 - $FF).
4. Give XTAL1 a positive pulse. This loads the address Low Byte.
C. Load Data Low Byte
1. Set XA1, XA0 to “01”. This enables data loading.
2. Set DATA = Data Low Byte ($00 - $FF).
3. Give XTAL1 a positive pulse. This loads the data byte.
D. Latch Data Low Byte
1. Set BS1 to “0”. This selects Low Data Byte.
2. Give PAGEL a positive pulse. This latches the data Low Byte.
(See Figure 82 for signal waveforms)
E. Load Data High Byte
1. Set BS1 to “1”. This selects High Data Byte.
2. Set XA1, XA0 to “01”. This enables data loading.
3. Set DATA = Data High Byte ($00 - $FF).
4. Give XTAL1 a positive pulse. This loads the data byte.
F. Latch Data High Byte
1. Set BS1 to “1”. This selects High Data Byte.
2. Give PAGEL a positive pulse. This latches the data High Byte.
G. Repeat B through F 64 times to fill the page buffer.
To address a page in the Flash, seven bits are needed (128 pages). The five most sig-
nificant bits are read from address high byte as described in section “H” below. The two
least significant page address bits however, are the two most significant bits (bit7 and
bit6) of the latest loaded address low byte as described in section “B”.
147
1142E–AVR–02/03
H. Load Address High byte
1. 1. Set XA1, XA0 to “00”. This enables address loading.
2. Set BS1 to “1”. This selects high address.
3. Set DATA = Address High Byte ($00 - $1F).
4. Give XTAL1 a positive pulse. This loads the address High Byte.
I. Program Page
1. Give WR a negative pulse. This starts programming of the entire page of
data. RDY/BSYgoes low.
2. Wait until RDY/BSY goes high.
(See Figure 83 for signal waveforms)
J. End Page Programming
1. Set XA1, XA0 to “10”. This enables command loading.
2. Set DATA to “0000 0000”. This is the command for No Operation.
3. Give XTAL1 a positive pulse. This loads the command, and the internal write
signals are reset.
K. Repeat A through J 128 times or until all data has been programmed.
XA1
XA2
BS1
XTAL1
WR
DY/BSY
RESET +12V
OE
BS2
PAGEL
148 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
XA1
XA0
BS1
XTAL1
WR
RDY/BSY
RESET +12V
OE
PAGEL
BS2
Programming the EEPROM The programming algorithm for the EEPROM Data Memory is as follows (refer to “Pro-
gramming the Flash” on page 147 for details on Command, Address and Data loading):
1. A: Load Command “0001 0001”.
2. H: Load Address High Byte ($00 - $01)
3. B: Load Address Low Byte ($00 - $FF)
4. E: Load Data Low Byte ($00 - $FF)
L: Write Data Low Byte
1. Set BS to “0”. This selects low data.
2. Give WR a negative pulse. This starts programming of the data byte.
RDY/BSY goes low.
3. Wait until to RDY/BSY goes high before programming the next byte.
(See Figure 84 for signal waveforms)
The loaded command and address are retained in the device during programming. For
efficient programming, the following should be considered.
• The command needs only be loaded once when writing or reading multiple memory
locations.
• Address high byte needs only be loaded before programming a new 256 word page
in the EEPROM.
• Skip writing the data value $FF, that is the contents of the entire EEPROM after a
Chip Erase.
These considerations also applies to Flash, EEPROM and Signature bytes reading.
149
1142E–AVR–02/03
Figure 84. Programming the EEPROM Waveforms
DATA $11 ADDR. HIGH ADDR. LOW DATA LOW
XA1
XA2
BS1
XTAL1
WR
RDY/BSY
RESET +12V
OE
BS2
PAGEL
Reading the Flash The algorithm for reading the Flash memory is as follows (refer to “Programming the
Flash” on page 147 for details on Command and Address loading):
1. A: Load Command “0000 0010”.
2. H: Load Address High Byte ($00 - $1F).
3. B: Load Address Low Byte ($00 - $FF).
4. Set OE to “0”, and BS1 to “0”. The Flash word low byte can now be read at DATA.
5. Set BS to “1”. The Flash word high byte can now be read at DATA.
6. Set OE to “1”.
Reading the EEPROM The algorithm for reading the EEPROM memory is as follows (refer to “Programming the
Flash” on page 147 for details on Command and Address loading):
1. A: Load Command “0000 0011”.
2. H: Load Address High Byte ($00 - $01).
3. B: Load Address ($00 - $FF).
4. Set OE to “0”, and BS1 to “0”. The EEPROM Data byte can now be read at
DATA.
5. Set OE to “1”.
Programming the Fuse Low The algorithm for programming the Fuse Low bits is as follows (refer to “Programming
Bits the Flash” on page 147 for details on Command and Data loading):
1. A: Load Command “0100 0000”.
2. C: Load Data Low Byte. Bit n = “0” programs and bit n = “1” erases the Fuse bit.
Bit 7 = BODLEVEL Fuse bit
Bit 6 = BODEN Fuse bit
Bit 5 = SPIEN Fuse bit
Bit 3..0 = CKSEL3..0 Fuse bits
Bit 4 = “1”. This bit is reserved and should be left unprogrammed (“1”).
3. Give WR a negative pulse and wait for RDY/BSY to go high.
150 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Programming the Fuse High The algorithm for programming the Fuse high bits is as follows (refer to “Programming
Bits the Flash” on page 147 for details on Command and Data loading):
1. A: Load Command “0100 0000”.
2. C: Load Data Low Byte. Bit n = “0” programs and bit n = “1” erases the Fuse bit.
Bit 2..1 = BOOTSZ1..0 Fuse bits
Bit 0 = BOOTRST Fuse bit
Bit 7..3 = “1”. These bits are reserved and should be left unprogrammed (“1”).
3. Set BS1 to “1”. This selects high data byte.
4. Give WR a negative pulse and wait for RDY/BSY to go high.
5. Set BS1 to “0”. This selects low data byte.
Programming the Lock Bits The algorithm for programming the Lock bits is as follows (refer to “Programming the
Flash” on page 147 for details on Command and Data loading):
1. A: Load Command “0010 0000”.
2. D: Load Data Low Byte. Bit n = “0” programs the Lock bit.
Bit 5 = Boot Lock bit12
Bit 4 = Boot Lock bit11
Bit 3 = Boot Lock bit02
Bit 2 = Boot Lock bit01
Bit 1 = Lock bit2
Bit 0 = Lock bit1
Bit 7..6 = “1”. These bits are reserved and should be left unprogrammed (“1”).
3. L: Write Data Low Byte.
The Lock bits can only be cleared by executing Chip Erase.
Reading the Fuse and Lock The algorithm for reading the Fuse and Lock bits is as follows (refer to “Programming
Bits the Flash” on page 147 for details on Command loading):
1. A: Load Command “0000 0100”.
2. Set OE to “0”, BS2 to “0” and BS1 to “0”. The status of the Fuse Low bits can
now be read at DATA (“0” means programmed).
Bit 7 = BODLEVEL Fuse bit
Bit 6 = BODEN Fuse bit
Bit 5 = SPIEN Fuse bit
Bit 3..0 = CKSEL3..0 Fuse bits
3. Set OE to “0”, BS2 to “1” and BS1 to “1”. The status of the Fuse High bits can
now be read at DATA (“0” means programmed).
Bit 2..1 = BOOTSZ1..0 Fuse bits
Bit 0 = BOOTRST Fuse bit
4. Set OE to “0”, BS2 to “0” and BS1 to “1”. The status of the Lock bits can now be
read at DATA (“0” means programmed).
Bit 5 = Boot Lock bit12
Bit 4 = Boot Lock bit11
Bit 3 = Boot Lock bit02
Bit 2 = Boot Lock bit01
Bit 1 = Lock bit2
Bit 0 = Lock bit1
5. Set OE to “1”.
151
1142E–AVR–02/03
Reading the Signature Bytes The algorithm for reading the Signature bytes is as follows (refer to Programming the
Flash for details on Command and Address loading):
1. A: Load Command “0000 1000”.
2. C: Load Address Low Byte ($00 - $02).
3. Set OE to “0”, and BS to “0”. The selected Signature byte can now be read at
DATA.
4. Set OE to “1”.
Reading the Calibration Byte The algorithm for reading the Calibration byte is as follows (refer to Programming the
Flash for details on Command and Address loading):
1. A: Load Command “0000 1000”.
2. C: Load Address Low Byte, $00.
Set OE to “0”, and BS1 to “1”. The Calibaration byte can now be read at DATA.
3. Set OE to “1”.
152 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Write
WR tPLWL
WLRL
RDY/BSY
tWLRH
OE
tXLOL tOHDZ
Read
tOLDV
DATA
Notes: 1. tWLRH is valid for the Write EEPROM, Write Fuse Bits and Write Lock Bits
commands.
2. tWLRH_CE is valid for the Chip Erase command.
3. tWLRH_FLASH is valid for the Write Flash command.
153
1142E–AVR–02/03
Serial Downloading Both the Flash and EEPROM memory arrays can be programmed using the serial SPI
bus while RESET is pulled to GND. The serial interface consists of pins SCK, MOSI
(input) and MISO (output). After RESET is set low, the Programming Enable instruction
needs to be executed first before program/erase operations can be executed.
VCC
(2)
2.7 - 5.5V
XTAL1
RESET
GND AGND
Notes: 1. If the device is clocked by the internal Oscillator, connecting a clock source to XTAL1
is not required.
2. VCC - 0.3 V < AVCC < VCC + 0.3 V, however, AVCC should always be within 2.7 -
5.5 V.
When programming the EEPROM, an auto-erase cycle is built into the self-timed pro-
gramming 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 $FF.
The Program and EEPROM memory arrays have separate address spaces:
$0000 to $1FFF for Program memory and $0000 to $01FF for EEPROM memory.
The device can be clocked by any clock option during Serial Programming. The mini-
mum low and high periods for the serial clock (SCK) input are defined as follows:
Low: > 2 MCU clock cycles
High: > 2 MCU clock cycles
154 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Serial Programming When writing serial data to the ATmega163, data is clocked on the rising edge of SCK.
Algorithm When reading data from the ATmega163, data is clocked on the falling edge of SCK.
See Figure 87, Figure 88 and Table 62 for timing details.
To program and verify the ATmega163 in the serial programming mode, the following
sequence is recommended (See four byte instruction formats in Table 61):
1. Power-up sequence:
Apply power between VCC and GND while RESET and SCK are set to “0”. In accor-
dance with the setting of CKSEL Fuses, apply a crystal/resonator, external clock, or
RC network, or let the device run on the internal RC Oscillator. In some systems,
the programmer can not guarantee that SCK is held low during power-up. In this
case, wait for 100 ms after SCK has been set to “0”. RESET must be then given a
positive pulse of at least two XTAL1 cycles duration and then set to “0”.
2. Wait for at least 20 ms and enable serial programming by sending the Program-
ming Enable serial instruction to pin MOSI/PB5.
3. The Serial Programming instructions will not work if the communication is out of
synchronization. When in sync. the second byte ($53), will echo back when issu-
ing the third byte of the Programming Enable instruction. Whether the echo is
correct or not, all four bytes of the instruction must be transmitted. If the $53 did
not echo back, give SCK a positive pulse and issue a new Programming Enable
command. If the $53 is not seen within 32 attempts, there is no functional device
connected.
4. If a Chip Erase is performed (must be done to erase the Flash), wait 2•tWD_FLASH
after the instruction, give RESET a positive pulse, and start over from Step 2.
See Table 60 for the tWD_FLASH figure.
5. The Flash is programmed one page at a time. The memory page is loaded one
byte at a time by supplying the 6 LSB of the address and data together with the
Load Program Memory Page instruction. The Program Memory Page is stored
by loading the Write Program Memory Page instruction with the 7 MSB of the
address. If polling is not used, the user must wait at least tWD_FLASH before issu-
ing the next page. (Please refer to Table 60). Accessing the serial programming
interface before the Flash write operation completes can result in incorrect
programming.
6. The EEPROM array is programmed one byte at a time by supplying the address
and data together with the appropriate Write instruction. An EEPROM memory
location is first automatically erased before new data is written. If polling is not
used, the user must wait at least tWD_EEPROM before issuing the next byte. (Please
refer to Table 60). In a chip erased device, no $FFs in the data file(s) need to be
programmed.
7. Any memory location can be verified by using the Read instruction which returns
the content at the selected address at serial output MISO/PB6.
8. At the end of the programming session, RESET can be set high to commence
normal operation.
9. Power-off sequence (if needed):
Set XTAL1 to “0” (if external clock is used).
Set RESET to “1”.
Turn VCC power-off.
155
1142E–AVR–02/03
Data Polling Flash When a page is being programmed into the Flash, reading an address location within
the page being programmed will give the value $FF. At the time the device is ready for a
new page, the programmed value will read correctly. This is used to determine when the
next page can be written. Note that the entire page is written simultaneously and any
address within the page can be used for polling. Data polling of the Flash will not work
for the value $FF, so when programming this value, the user will have to wait for at least
tWD_FLASH before programming the next page. As a chip-erased device contains $FF in
all locations, programming of addresses that are meant to contain $FF, can be skipped.
See Table 60 for tWD_FLASH value.
Data Polling EEPROM When a new byte has been written and is being programmed into EEPROM, reading the
address location being programmed will give the value $FF. At the time the device is
ready for a new byte, the programmed value will read correctly. This is used to deter-
mine when the next byte can be written. This will not work for the value $FF, but the user
should have the following in mind: As a chip-erased device contains $FF in all locations,
programming of addresses that are meant to contain $FF, can be skipped. This does
not apply if the EEPROM is re-programmed without chip-erasing the device. In this
case, data polling cannot be used for the value $FF, and the user will have to wait at
least tWD_EEPROM before programming the next byte. See Table 60 for tWD_EEPROM value.
Programming Times for Non- The internal RC Oscillator is used to control programming time when programming or
volatile Memory erasing Flash, EEPORM, Fuses, and Lock bits. During Parallel or Serial Programming,
the device is in reset, and this Oscillator runs at its initial, uncalibrated frequency, which
may vary from 0.5 MHz to 1.0 MHz. In software it is possible to calibrate this Oscillator to
1.0 MHz (see “Calibrated Internal RC Oscillator” on page 37). Consequently, program-
ming times will be shorter and more accurate when Programming or erasing non-volatile
memory from software, using SPM or the EEPROM interface. See Table 60 for a sum-
mary of programming times.
Notes: 1. Includes variation over voltage and temperature after RC Oscillator has been cali-
brated to 1.0 MHz
2. Parallel EEPROM Programming takes 1K cycles
3. Per page
156 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
SAMPLE
157
1142E–AVR–02/03
.
158 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
SCK
tSHSL
MISO
tSLIV
Table 62. Serial Programming Characteristics, TA = -40°C to 85°C, VCC = 2.7V - 5.5V
(Unless otherwise noted)
Symbol Parameter Min Typ Max Units
1/tCLCL Oscillator Frequency (VCC = 2.7 - 5.5 V) 0 4 MHz
tCLCL Oscillator Period (VCC = 2.7 - 5.5 V) 250 ns
1/tCLCL Oscillator Frequency (VCC = 4.0 - 5.5 V) 0 8 MHz
tCLCL Oscillator Period (VCC = 4.0 - 5.5 V) 125 ns
tSHSL SCK Pulse Width High 2 tCLCL ns
tSLSH SCK Pulse Width Low 2 tCLCL ns
tOVSH MOSI Setup to SCK High tCLCL ns
tSHOX MOSI Hold after SCK High 2 tCLCL ns
tSLIV SCK Low to MISO Valid 10 16 32 ns
159
1142E–AVR–02/03
Electrical Characteristics
DC Characteristics
TA = -40°C to 85°C, VCC = 2.7V to 5.5V (unless otherwise noted)
Symbol Parameter Condition Min Typ Max Units
VIL Input Low-voltage (Except XTAL1) -0.5 0.3 VCC(1) V
(XTAL1), CKSEL3 fuse
-0.5 0.3 VCC(1) V
programmed
VIL1 Input Low-voltage
(XTAL1), CKSEL3 fuse
-0.5 0.2 VCC(1) V
unprogrammed
VIH Input High-voltage (Except XTAL1, RESET) 0.6 VCC(2) VCC + 0.5 V
(XTAL1), CKSEL3 fuse
0.6 VCC(2) VCC + 0.5 V
programmed
VIH1 Input High-voltage
(XTAL1), CKSEL3 fuse
0.8 VCC(2) VCC + 0.5 V
unprogrammed
VIH2 Input High-voltage (RESET) 0.9 VCC(2) VCC + 0.5 V
(3)
Output Low-voltage IOL = 20 mA, V CC = 5V 0.6 V
VOL
(Ports A,B,C,D) IOL = 10 mA, V CC = 3V 0.5 V
Output High-voltage(4) IOH = -3 mA, VCC = 5V 4.2 V
VOH
(Ports A,B,C,D) IOH = -1.5 mA, VCC = 3V 2.3 V
Input Leakage Vcc = 5.5V, pin low
IIL 8.0 µA
Current I/O pin (absolute value)
Input Leakage Vcc = 5.5V, pin high
IIH 980 nA
Current I/O pin (absolute value)
RRST Reset Pull-up Resistor 100 500 kΩ
RI/O I/O Pin Pull-up Resistor 35 120 kΩ
160 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
DC Characteristics (Continued)
161
1142E–AVR–02/03
External Clock Drive
Table 63. External Clock Drive
VCC = 2.7V to 5.5V VCC = 4.0V to 5.5V
Symbol Parameter Min Max Min Max Units
1/tCLCL Oscillator Frequency 0 4 0 8 MHz
tCLCL Clock Period 250 125 ns
tCHCX High Time 100 50 ns
tCLCX Low Time 100 50 ns
tCLCH Rise Time 1.6 0.5 µs
tCHCL Fall Time 1.6 0.5 µs
162 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
163
1142E–AVR–02/03
Figure 90. Two-wire Serial Bus Timing
tof tHIGH
tLOW tLOW
SCL
tSU;STA tHD;STA tHD;DAT tSU;DAT tSU;STO
SDA
tBUF
164 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Typical The following charts show typical behavior. These figures are not tested during manu-
facturing. All current consumption measurements are performed with all I/O pins
Characteristics
configured as inputs and with internal pull-ups enabled. All pins on Port F are pulled high
externally. A sine wave generator with rail-to-rail output is used as clock source.
The power consumption in Power-down mode is independent of clock selection.
The current consumption is a function of several factors such as: operating voltage,
operating frequency, loading of I/O pins, switching rate of I/O pins, code executed and
ambient temperature. The dominating factors are operating voltage and frequency.
The current drawn from capacitive loaded pins may be estimated (for one pin) as CL •
VCC • f, where CL = load capacitance, VCC = operating voltage and f = average switching
frequency of I/O pin.
The parts are characterized at frequencies higher than test limits. Parts are not guaran-
teed to function properly at frequencies higher than the ordering code indicates.
The difference between current consumption in Power-down mode with Watchdog
Timer enabled and Power-down mode with Watchdog Timer disabled represents the dif-
ferential current drawn by the Watchdog Timer.
Figure 91. Analog Comparator Offset Voltage vs, Common Mode Voltage (VCC = 5V)
18
16
TA = 25˚C
14
Offset Voltage (mV)
12
TA = 85˚C
10
0
0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5
165
1142E–AVR–02/03
Figure 92. Analog Comparator Offset Voltage vs. Common Mode Voltage (VCC = 2.7V)
10
TA = 25˚C
0
0 0.5 1 1.5 2 2.5 3
Figure 93. Analog Comparator Input Leakage Current (VCC = 6V; TA = 25°C)
60
50
40
(nA) ACLK
30
I
20
10
-10
0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5 5.5 6 6.5 7
VIN (V)
166 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
1600
TA = 25˚C
1400
TA = 85˚C
1200
1000
F RC (KHz) 800
600
400
200
0
2 2.5 3 3.5 4 4.5 5 5.5 6
Vcc (V)
Sink and source capabilities of I/O ports are measured on one pin at a time.
Figure 95. Pull-up Resistor Current vs. Input Voltage (VCC = 5V)
120
TA = 25˚C
100
TA = 85˚C
80
OP (µA)
60
I
40
20
167
1142E–AVR–02/03
Figure 96. Pull-up Resistor Current vs. Input Voltage (VCC = 2.7V)
30
TA = 25˚C
25
TA = 85˚C
20
OP (µA)
I 15
10
0
0 0.5 1 1.5 2 2.5 3
VOP (V)
Figure 97. I/O Pin Sink Current vs. Output Voltage (VCC = 5V)
70
TA = 25˚C
60
TA = 85˚C
50
40
OL (mA)
30
I
20
10
0
0 0.5 1 1.5 2 2.5 3
VOL (V)
168 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Figure 98. I/O Pin Source Current vs. Output Voltage (VCC = 5V)
20 TA = 25˚C
18
16
TA = 85˚C
14
12
OH (mA) 10
8
I
0
0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5
VOH (V)
Figure 99. I/O Pin Sink Current vs. Output Voltage (VCC = 2.7V)
25
TA = 25˚C
20
TA = 85˚C
15
OL (mA)
10
I
0
0 0.5 1 1.5 2
VOL (V)
169
1142E–AVR–02/03
Figure 100. I/O Pin Source Current vs. Output Voltage (VCC = 2.7V)
6 TA = 25˚C
5
TA = 85˚C
OH (mA)
I 3
0
0 0.5 1 1.5 2 2.5 3
VOH (V)
Figure 101. I/O Pin Input Threshold vs. VCC (TA = 25°C)
2.5
2
Threshold Voltage (V)
1.5
0.5
0
2.7 4.0 5.0
Vcc
170 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Figure 102. I/O Pin Input Hysteresis vs. VCC (TA = 25°C)
0.18
0.16
0.14
0.1
0.08
0.06
0.04
0.02
0
2.7 4.0 5.0
Vcc
171
1142E–AVR–02/03
Register Summary
Address Name Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Page
$3F ($5F) SREG I T H S V N Z C 20
$3E ($5E) SPH – – – – – SP10 SP9 SP8 21
$3D ($5D) SPL SP7 SP6 SP5 SP4 SP3 SP2 SP1 SP0 21
$3C ($5C) Reserved
$3B ($5B) GIMSK INT1 INT0 – – – – – – 30
$3A ($5A) GIFR INTF1 INTF0 – – – – – – 31
$39 ($59) TIMSK OCIE2 TOIE2 TICIE1 OCIE1A OCIE1B TOIE1 – TOIE0 32
$38 ($58) TIFR OCF2 TOV2 ICF1 OCF1A OCF1B TOV1 – TOV0 32
$37 ($57) SPMCR – ASB – ASRE BLBSET PGWRT PGERS SPMEN 140
$36 ($56) TWCR TWINT TWEA TWSTA TWSTO TWWC TWEN – TWIE 82
$35 ($55) MCUCR – SE SM1 SM0 ISC11 ISC10 ISC01 ISC00 34
$34 ($54) MCUSR – – – – WDRF BORF EXTRF PORF 28
$33 ($53) TCCR0 – – – – – CS02 CS01 CS00 41
$32 ($52) TCNT0 Timer/Counter0 (8 Bits) 42
$31 ($51) OSCCAL Oscillator Calibration Register 37
$30 ($50) SFIOR – – – – ACME PUD PSR2 PSR10 40
$2F ($4F) TCCR1A COM1A1 COM1A0 COM1B1 COM1B0 FOC1A FOC1B PWM11 PWM10 44
$2E ($4E) TCCR1B ICNC1 ICES1 – – CTC1 CS12 CS11 CS10 45
$2D ($4D) TCNT1H Timer/Counter1 – Counter Register High Byte 46
$2C ($4C) TCNT1L Timer/Counter1 – Counter Register Low Byte 46
$2B ($4B) OCR1AH Timer/Counter1 – Output Compare Register A High Byte 47
$2A ($4A) OCR1AL Timer/Counter1 – Output Compare Register A Low Byte 47
$29 ($49) OCR1BH Timer/Counter1 – Output Compare Register B High Byte 47
$28 ($48) OCR1BL Timer/Counter1 – Output Compare Register B Low Byte 47
$27 ($47) ICR1H Timer/Counter1 – Input Capture Register High Byte 48
$26 ($46) ICR1L Timer/Counter1 – Input Capture Register Low Byte 48
$25 ($45) TCCR2 FOC2 PWM2 COM21 COM20 CTC2 CS22 CS21 CS20 52
$24 ($44) TCNT2 Timer/Counter2 (8 Bits) 53
$23 ($43) OCR2 Timer/Counter2 Output Compare Register 54
$22 ($42) ASSR – – – – AS2 TCN2UB OCR2UB TCR2UB 57
$21 ($41) WDTCR – – – WDTOE WDE WDP2 WDP1 WDP0 60
$20 ($40) UBRRHI – – – – UBRR[11:8] 78
$1F ($3F) EEARH – – – – – – – EEAR8 62
$1E ($3E) EEARL EEAR7 EEAR6 EEAR5 EEAR4 EEAR3 EEAR2 EEAR1 EEAR0 62
$1D ($3D) EEDR EEPROM Data Register 62
$1C ($3C) EECR – – – – EERIE EEMWE EEWE EERE 63
$1B ($3B) PORTA PORTA7 PORTA6 PORTA5 PORTA4 PORTA3 PORTA2 PORTA1 PORTA0 115
$1A ($3A) DDRA DDA7 DDA6 DDA5 DDA4 DDA3 DDA2 DDA1 DDA0 115
$19 ($39) PINA PINA7 PINA6 PINA5 PINA4 PINA3 PINA2 PINA1 PINA0 115
$18 ($38) PORTB PORTB7 PORTB6 PORTB5 PORTB4 PORTB3 PORTB2 PORTB1 PORTB0 117
$17 ($37) DDRB DDB7 DDB6 DDB5 DDB4 DDB3 DDB2 DDB1 DDB0 117
$16 ($36) PINB PINB7 PINB6 PINB5 PINB4 PINB3 PINB2 PINB1 PINB0 117
$15 ($35) PORTC PORTC7 PORTC6 PORTC5 PORTC4 PORTC3 PORTC2 PORTC1 PORTC0 123
$14 ($34) DDRC DDC7 DDC6 DDC5 DDC4 DDC3 DDC2 DDC1 DDC0 123
$13 ($33) PINC PINC7 PINC6 PINC5 PINC4 PINC3 PINC2 PINC1 PINC0 123
$12 ($32) PORTD PORTD7 PORTD6 PORTD5 PORTD4 PORTD3 PORTD2 PORTD1 PORTD0 128
$11 ($31) DDRD DDD7 DDD6 DDD5 DDD4 DDD3 DDD2 DDD1 DDD0 128
$10 ($30) PIND PIND7 PIND6 PIND5 PIND4 PIND3 PIND2 PIND1 PIND0 128
$0F ($2F) SPDR SPI Data Register 69
$0E ($2E) SPSR SPIF WCOL – – – – – SPI2X 68
$0D ($2D) SPCR SPIE SPE DORD MSTR CPOL CPHA SPR1 SPR0 67
$0C ($2C) UDR UART I/O Data Register 74
$0B ($2B) UCSRA RXC TXC UDRE FE OR – U2X MPCM 74
$0A ($2A) UCSRB RXCIE TXCIE UDRIE RXEN TXEN CHR9 RXB8 TXB8 76
$09 ($29) UBRR UART Baud Rate Register 78
$08 ($28) ACSR ACD ACBG ACO ACI ACIE ACIC ACIS1 ACIS0 102
$07 ($27) ADMUX REFS1 REFS0 ADLAR MUX4 MUX3 MUX2 MUX1 MUX0 110
$06 ($26) ADCSR ADEN ADSC ADFR ADIF ADIE ADPS2 ADPS1 ADPS0 111
$05 ($25) ADCH ADC Data Register High Byte 112
$04 ($24) ADCL ADC Data Register Low Byte 112
$03 ($23) TWDR Two-wire Serial Interface Data Register 84
$02 ($22) TWAR TWA6 TWA5 TWA4 TWA3 TWA2 TWA1 TWA0 TWGCE 85
$01 ($21) TWSR TWS7 TWS6 TWS5 TWS4 TWS3 – – – 84
172 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
173
1142E–AVR–02/03
Instruction Set Summary
Mnemonics Operands Description Operation Flags #Clocks
ARITHMETIC AND LOGIC INSTRUCTIONS
ADD Rd, Rr Add two Registers Rd ← Rd + Rr Z,C,N,V,H 1
ADC Rd, Rr Add with Carry two Registers Rd ← Rd + Rr + C Z,C,N,V,H 1
ADIW Rdl,K Add Immediate to Word Rdh:Rdl ← Rdh:Rdl + K Z,C,N,V,S 2
SUB Rd, Rr Subtract two Registers Rd ← Rd - Rr Z,C,N,V,H 1
SUBI Rd, K Subtract Constant from Register Rd ← Rd - K Z,C,N,V,H 1
SBC Rd, Rr Subtract with Carry two Registers Rd ← Rd - Rr - C Z,C,N,V,H 1
SBCI Rd, K Subtract with Carry Constant from Reg. Rd ← Rd - K - C Z,C,N,V,H 1
SBIW Rdl,K Subtract Immediate from Word Rdh:Rdl ← Rdh:Rdl - K Z,C,N,V,S 2
AND Rd, Rr Logical AND Registers Rd ← Rd • Rr Z,N,V 1
ANDI Rd, K Logical AND Register and Constant Rd ← Rd • K Z,N,V 1
OR Rd, Rr Logical OR Registers Rd ← Rd v Rr Z,N,V 1
ORI Rd, K Logical OR Register and Constant Rd ← Rd v K Z,N,V 1
EOR Rd, Rr Exclusive OR Registers Rd ← Rd ⊕ Rr Z,N,V 1
COM Rd One’s Complement Rd ← $FF − Rd Z,C,N,V 1
NEG Rd Two’s Complement Rd ← $00 − Rd Z,C,N,V,H 1
SBR Rd,K Set Bit(s) in Register Rd ← Rd v K Z,N,V 1
CBR Rd,K Clear Bit(s) in Register Rd ← Rd • ($FF - K) Z,N,V 1
INC Rd Increment Rd ← Rd + 1 Z,N,V 1
DEC Rd Decrement Rd ← Rd − 1 Z,N,V 1
TST Rd Test for Zero or Minus Rd ← Rd • Rd Z,N,V 1
CLR Rd Clear Register Rd ← Rd ⊕ Rd Z,N,V 1
SER Rd Set Register Rd ← $FF None 1
MUL Rd, Rr Multiply Unsigned R1:R0 ← Rd x Rr Z,C 2
MULS Rd, Rr Multiply Signed R1:R0 ← Rd x Rr Z,C 2
MULSU Rd, Rr Multiply Signed with Unsigned R1:R0 ← Rd x Rr Z,C 2
FMUL Rd, Rr Fractional Multiply Unsigned R1:R0 ← (Rd x Rr) << 1 Z,C 2
FMULS Rd, Rr Fractional Multiply Signed R1:R0 ← (Rd x Rr) << 1 Z,C 2
FMULSU Rd, Rr Fractional Multiply Signed with Unsigned R1:R0 ← (Rd x Rr) << 1 Z,C 2
BRANCH INSTRUCTIONS
RJMP k Relative Jump PC ← PC + k + 1 None 2
IJMP Indirect Jump to (Z) PC ← Z None 2
JMP k Direct Jump PC ← k None 3
RCALL k Relative Subroutine Call PC ← PC + k + 1 None 3
ICALL Indirect Call to (Z) PC ← Z None 3
CALL k Direct Subroutine Call PC ← k None 4
RET Subroutine Return PC ← STACK None 4
RETI Interrupt Return PC ← STACK I 4
CPSE Rd,Rr Compare, Skip if Equal if (Rd = Rr) PC ← PC + 2 or 3 None 1/2/3
CP Rd,Rr Compare Rd − Rr Z, N,V,C,H 1
CPC Rd,Rr Compare with Carry Rd − Rr − C Z, N,V,C,H 1
CPI Rd,K Compare Register with Immediate Rd − K Z, N,V,C,H 1
SBRC Rr, b Skip if Bit in Register Cleared if (Rr(b)=0) PC ← PC + 2 or 3 None 1/2/3
SBRS Rr, b Skip if Bit in Register is Set if (Rr(b)=1) PC ← PC + 2 or 3 None 1/2/3
SBIC P, b Skip if Bit in I/O Register Cleared if (P(b)=0) PC ← PC + 2 or 3 None 1/2/3
SBIS P, b Skip if Bit in I/O Register is Set if (P(b)=1) PC ← PC + 2 or 3 None 1/2/3
BRBS s, k Branch if Status Flag Set if (SREG(s) = 1) then PC←PC+k + 1 None 1/2
BRBC s, k Branch if Status Flag Cleared if (SREG(s) = 0) then PC←PC+k + 1 None 1/2
BREQ k Branch if Equal if (Z = 1) then PC ← PC + k + 1 None 1/2
BRNE k Branch if Not Equal if (Z = 0) then PC ← PC + k + 1 None 1/2
BRCS k Branch if Carry Set if (C = 1) then PC ← PC + k + 1 None 1/2
BRCC k Branch if Carry Cleared if (C = 0) then PC ← PC + k + 1 None 1/2
BRSH k Branch if Same or Higher if (C = 0) then PC ← PC + k + 1 None 1/2
BRLO k Branch if Lower if (C = 1) then PC ← PC + k + 1 None 1/2
BRMI k Branch if Minus if (N = 1) then PC ← PC + k + 1 None 1/2
BRPL k Branch if Plus if (N = 0) then PC ← PC + k + 1 None 1/2
BRGE k Branch if Greater or Equal, Signed if (N ⊕ V= 0) then PC ← PC + k + 1 None 1/2
BRLT k Branch if Less Than Zero, Signed if (N ⊕ V= 1) then PC ← PC + k + 1 None 1/2
BRHS k Branch if Half Carry Flag Set if (H = 1) then PC ← PC + k + 1 None 1/2
BRHC k Branch if Half Carry Flag Cleared if (H = 0) then PC ← PC + k + 1 None 1/2
BRTS k Branch if T Flag Set if (T = 1) then PC ← PC + k + 1 None 1/2
BRTC k Branch if T Flag Cleared if (T = 0) then PC ← PC + k + 1 None 1/2
BRVS k Branch if Overflow Flag is Set if (V = 1) then PC ← PC + k + 1 None 1/2
BRVC k Branch if Overflow Flag is Cleared if (V = 0) then PC ← PC + k + 1 None 1/2
174 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
175
1142E–AVR–02/03
Instruction Set Summary (Continued)
CLH Clear Half Carry Flag in SREG H←0 H 1
NOP No Operation None 1
SLEEP Sleep (see specific descr. for Sleep function) None 1
WDR Watchdog Reset (see specific descr. for WDR/timer) None 1
176 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Ordering Information
Speed (MHz) Power Supply Ordering Code Package Operation Range
4 2.7 - 5.5V ATmega163L-4AC 44A Commercial
ATmega163L-4PC 40P6 (0°C to 70°C)
ATmega163L-4AI 44A Industrial
ATmega163L-4PI 40P6 (-40°C to 85°C)
8 4.0 - 5.5V ATmega163-8AC 44A Commercial
ATmega163-8PC 40P6 (0°C to 70°C)
ATmega163-8AI 44A Industrial
ATmega163-8PI 40P6 (-40°C to 85°C)
Package Type
44A 44-lead, Thin (1.0 mm) Plastic Gull Wing Quad Flat Package (TQFP)
40P6 40-lead, 0.600" Wide, Plastic Dual Inline Package (PDIP)
177
1142E–AVR–02/03
Packaging Information
44A
PIN 1
B
PIN 1 IDENTIFIER
e E1 E
D1
D
C 0˚~7˚
A1 A2 A
L
COMMON DIMENSIONS
(Unit of Measure = mm)
10/5/2001
TITLE DRAWING NO. REV.
2325 Orchard Parkway
44A, 44-lead, 10 x 10 mm Body Size, 1.0 mm Body Thickness,
R San Jose, CA 95131 44A B
0.8 mm Lead Pitch, Thin Profile Plastic Quad Flat Package (TQFP)
178 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
40P6
D
PIN
1
E1
SEATING PLANE
A1
L
B
B1
e
COMMON DIMENSIONS
0º ~ 15º REF (Unit of Measure = mm)
C
SYMBOL MIN NOM MAX NOTE
eB A – – 4.826
A1 0.381 – –
D 52.070 – 52.578 Note 2
E 15.240 – 15.875
E1 13.462 – 13.970 Note 2
B 0.356 – 0.559
Notes: 1. This package conforms to JEDEC reference MS-011, Variation AC. B1 1.041 – 1.651
2. Dimensions D and E1 do not include mold Flash or Protrusion. L 3.048 – 3.556
Mold Flash or Protrusion shall not exceed 0.25 mm (0.010").
C 0.203 – 0.381
eB 15.494 – 17.526
e 2.540 TYP
09/28/01
TITLE DRAWING NO. REV.
2325 Orchard Parkway
40P6, 40-lead (0.600"/15.24 mm Wide) Plastic Dual 40P6 B
R San Jose, CA 95131 Inline Package (PDIP)
179
1142E–AVR–02/03
Erratas
180 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Problem Fix/Workaround
Ensure at least one instruction (e.g., nop) is executed between two writes to TWCR.
181
1142E–AVR–02/03
Change Log This section containes a log on the changes made to the data sheet for ATmega163. All
refereces to pages in Change Log, are referred to this document.
Changes from Rev. 1. Added “Not Recommend for New Designs. Use ATmega16.”.
1142C-09/01 to Rev.
1142D-09/02
Changes from Rev. 1. Updated Table 52, “Boot Reset Fuse,” on page 136.
1142D-09/09 to Rev.
1142E-02/03 2. Corrected pin numbers in Figure 62 on page 113.
4. Changed max bit rate for the TWI from 400 kHz to 217 kHz.
5. Removed redundant and harmful loop in a code example for Slave Receiver
mode for the TWI on page 96.
6. Added AGND and AVCC in Figure 81 on page 145 and Figure 86 on page 154.
182 ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
Pin Configurations................................................................................ 2
Description ............................................................................................ 3
Block Diagram....................................................................................... 3
Pin Descriptions.................................................................................................... 4
Clock Options ....................................................................................................... 5
Timer Oscillator..................................................................................................... 6
Architectural Overview......................................................................... 7
The General Purpose Register File .................................................................... 10
The ALU – Arithmetic Logic Unit......................................................................... 11
The In-System Self-Programmable Flash Program Memory.............................. 11
The SRAM Data Memory.................................................................................... 11
The Program and Data Addressing Modes ........................................................ 12
The EEPROM Data Memory .............................................................................. 16
Memory Access Times and Instruction Execution Timing .................................. 16
I/O Memory ......................................................................................................... 17
Reset and Interrupt Handling .............................................................................. 21
Sleep Modes....................................................................................................... 35
Calibrated Internal RC Oscillator ........................................................................ 37
Timer/Counters ................................................................................... 39
Timer/Counter Prescalers ................................................................................... 39
8-bit Timer/Counter0........................................................................................... 40
16-bit Timer/Counter1......................................................................................... 42
8-bit Timer/Counter 2 .......................................................................................... 51
Watchdog Timer.................................................................................. 60
UART.................................................................................................... 70
Data Transmission.............................................................................................. 70
Data Reception ................................................................................................... 72
UART Control ..................................................................................................... 74
Double Speed Transmission............................................................................... 78
i
1142E–AVR–02/03
Two-wire Serial Interface (Byte Oriented) ........................................ 80
Two-wire Serial Interface Modes ........................................................................ 85
Master Transmitter Mode.................................................................................... 86
Master Receiver Mode........................................................................................ 86
Slave Receiver Mode.......................................................................................... 87
Slave Transmitter Mode...................................................................................... 88
Miscellaneous States .......................................................................................... 88
ii ATmega163(L)
1142E–AVR–02/03
ATmega163(L)
iii
1142E–AVR–02/03
iv ATmega163(L)
1142E–AVR–02/03
Atmel Headquarters Atmel Operations
Corporate Headquarters Memory RF/Automotive
2325 Orchard Parkway 2325 Orchard Parkway Theresienstrasse 2
San Jose, CA 95131 San Jose, CA 95131 Postfach 3535
TEL 1(408) 441-0311 TEL 1(408) 441-0311 74025 Heilbronn, Germany
FAX 1(408) 487-2600 FAX 1(408) 436-4314 TEL (49) 71-31-67-0
FAX (49) 71-31-67-2340
Europe Microcontrollers
Atmel Sarl 2325 Orchard Parkway 1150 East Cheyenne Mtn. Blvd.
Route des Arsenaux 41 San Jose, CA 95131 Colorado Springs, CO 80906
Case Postale 80 TEL 1(408) 441-0311 TEL 1(719) 576-3300
CH-1705 Fribourg FAX 1(408) 436-4314 FAX 1(719) 540-1759
Switzerland
TEL (41) 26-426-5555 La Chantrerie Biometrics/Imaging/Hi-Rel MPU/
FAX (41) 26-426-5500 BP 70602 High Speed Converters/RF Datacom
44306 Nantes Cedex 3, France Avenue de Rochepleine
Asia TEL (33) 2-40-18-18-18 BP 123
Room 1219 FAX (33) 2-40-18-19-60 38521 Saint-Egreve Cedex, France
Chinachem Golden Plaza TEL (33) 4-76-58-30-00
77 Mody Road Tsimhatsui ASIC/ASSP/Smart Cards FAX (33) 4-76-58-34-80
East Kowloon Zone Industrielle
Hong Kong 13106 Rousset Cedex, France
TEL (852) 2721-9778 TEL (33) 4-42-53-60-00
FAX (852) 2722-1369 FAX (33) 4-42-53-60-01
e-mail
literature@atmel.com
Web Site
http://www.atmel.com
Other terms and product names may be the trademarks of others. Printed on recycled paper.
1142E–AVR–02/03 0M