- •Features
- •Pin Configurations
- •Overview
- •Block Diagram
- •Disclaimer
- •Pin Descriptions
- •Port A (PA7..PA0)
- •Port B (PB7..PB0)
- •Port C (PC7..PC0)
- •Port D (PD7..PD0)
- •Port E(PE2..PE0)
- •RESET
- •XTAL1
- •XTAL2
- •AVR CPU Core
- •Introduction
- •Architectural Overview
- •Status Register
- •Stack Pointer
- •Interrupt Response Time
- •In-System Reprogrammable Flash Program memory
- •SRAM Data Memory
- •Data Memory Access Times
- •EEPROM Data Memory
- •EEPROM Read/Write Access
- •I/O Memory
- •Overview
- •Address Latch Requirements
- •Pull-up and Bus Keeper
- •Timing
- •Using all Locations of External Memory Smaller than 64 KB
- •Using all 64KB Locations of External Memory
- •Clock Systems and their Distribution
- •Clock Sources
- •Default Clock Source
- •Crystal Oscillator
- •External RC Oscillator
- •External Clock
- •Idle Mode
- •Power-down Mode
- •Standby Mode
- •Analog Comparator
- •Brown-out Detector
- •Internal Voltage Reference
- •Watchdog Timer
- •Port Pins
- •Resetting the AVR
- •Reset Sources
- •Power-on Reset
- •External Reset
- •Brown-out Detection
- •Watchdog Reset
- •Watchdog Timer
- •Timed Sequences for Changing the Configuration of the Watchdog Timer
- •Safety Level 0
- •Safety Level 1
- •Safety Level 2
- •Interrupts
- •Moving Interrupts between Application and Boot Space
- •I/O Ports
- •Introduction
- •Configuring the Pin
- •Reading the Pin Value
- •Unconnected pins
- •Alternate Port Functions
- •Alternate Functions of Port A
- •Alternate Functions Of Port B
- •Alternate Functions of Port C
- •Alternate Functions of Port D
- •Alternate Functions of Port E
- •Register Description for I/O Ports
- •External Interrupts
- •8-bit Timer/Counter0 with PWM
- •Overview
- •Registers
- •Definitions
- •Counter Unit
- •Output Compare Unit
- •Force Output Compare
- •Modes of Operation
- •Normal Mode
- •Fast PWM Mode
- •Phase Correct PWM Mode
- •Internal Clock Source
- •Prescaler Reset
- •External Clock Source
- •16-bit Timer/Counter1
- •Overview
- •Registers
- •Definitions
- •Compatibility
- •Counter Unit
- •Input Capture Unit
- •Input Capture Trigger Source
- •Noise Canceler
- •Using the Input Capture Unit
- •Output Compare Units
- •Force Output Compare
- •Modes of Operation
- •Normal Mode
- •Fast PWM Mode
- •Phase Correct PWM Mode
- •Slave Mode
- •Master Mode
- •Data Modes
- •USART
- •Single USART
- •Clock Generation
- •External Clock
- •Synchronous Clock Operation
- •Frame Formats
- •Parity Bit Calculation
- •USART Initialization
- •Sending Frames with 5 to 8 Data Bits
- •Sending Frames with 9 Data Bits
- •Parity Generator
- •Disabling the Transmitter
- •Receiving Frames with 5 to 8 Data Bits
- •Receiving Frames with 9 Data Bits
- •Receiver Error Flags
- •Parity Checker
- •Disabling the Receiver
- •Flushing the Receive Buffer
- •Asynchronous Data Recovery
- •Using MPCM
- •Write Access
- •Read Access
- •Analog Comparator
- •Features
- •Application Section
- •Boot Loader Lock bits
- •Performing a Page Write
- •Using the SPM Interrupt
- •Setting the Boot Loader Lock bits by SPM
- •Reading the Fuse and Lock bits from Software
- •Preventing Flash Corruption
- •Simple Assembly Code Example for a Boot Loader
- •Program and Data Memory Lock bits
- •Fuse bits
- •Latching of Fuses
- •Signature Bytes
- •Calibration Byte
- •Calibration Byte
- •Signal Names
- •Parallel Programming
- •Enter Programming Mode
- •Chip Erase
- •Programming the Flash
- •Programming the EEPROM
- •Reading the Flash
- •Reading the EEPROM
- •Programming the Lock bits
- •Reading the Signature Bytes
- •Reading the Calibration Byte
- •Serial Downloading
- •Data Polling Flash
- •Data Polling EEPROM
- •Electrical Characteristics
- •Absolute Maximum Ratings*
- •External Clock Drive Waveforms
- •External Clock Drive
- •External Data Memory Timing
- •Active Supply Current
- •Idle Supply Current
- •Standby Supply Current
- •Pin Pull-up
- •Pin Driver Strength
- •Internal Oscillator Speed
- •Register Summary
- •Instruction Set Summary
- •Ordering Information
- •Packaging Information
- •Errata
- •ATmega8515(L) Rev. B
- •Changes from Rev. 2512F-12/03 to Rev. 2512G-03/05
- •Changes from Rev. 2512F-12/03 to Rev. 2512E-09/03
- •Changes from Rev. 2512D-02/03 to Rev. 2512E-09/03
- •Changes from Rev. 2512C-10/02 to Rev. 2512D-02/03
- •Changes from Rev. 2512B-09/02 to Rev. 2512C-10/02
- •Changes from Rev. 2512A-04/02 to Rev. 2512B-09/02
- •Table of Contents
|
|
|
ATmega8515(L) |
|
|
|
|
|
Performing Page Erase by |
|
|
|
To execute Page Erase, set up the address in the Z-pointer, write “X0000011” to |
||
|
|||
|
SPM |
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 PCPAGE in the Z-register. |
|
|
|
Other bits in the Z-pointer must be written zero during this operation. |
|
|
|
• Page Erase to the RWW section: The NRWW section can be read during the Page |
|
|
|
Erase. |
|
|
|
• Page Erase to the NRWW section: The CPU is halted during the operation. |
|
|
Filling the Temporary Buffer |
To write an instruction word, set up the address in the Z pointer and data in R1:R0, write |
|
|
(page loading) |
“00000001” to SPMCR and execute SPM within four clock cycles after writing SPMCR. |
|
|
|
The content of PCWORD in the Z-register is used to address the data in the temporary |
|
|
|
buffer. The temporary buffer will auto-erase after a Page Write operation or by writing |
|
|
|
the RWWSRE bit in SPMCR. It is also erased after a System Reset. Note that it is not |
|
|
|
possible to write more than one time to each address without erasing the temporary |
|
|
|
buffer. |
|
|
|
Note: If the EEPROM is written in the middle of an SPM Page Load operation, all data loaded |
|
|
|
will be lost. |
|
|
Performing a Page Write |
To execute Page Write, set up the address in the Z-pointer, write “X0000101” to |
|
|
|
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 PCPAGE. Other bits in the Z- |
|
|
|
pointer must be written zero during this operation. |
|
|
|
• Page Write to the RWW section: The NRWW section can be read during the Page |
|
|
|
Write. |
|
|
|
• Page Write to the NRWW section: The CPU is halted during the operation. |
|
|
Using the SPM Interrupt |
If the SPM interrupt is enabled, the SPM interrupt will generate a constant interrupt |
|
|
|
when the SPMEN bit in SPMCR is cleared. This means that the interrupt can be used |
|
|
|
instead of polling the SPMCR Register in software. When using the SPM interrupt, the |
|
|
|
Interrupt Vectors should be moved to the BLS section to avoid that an interrupt is |
|
|
|
accessing the RWW section when it is blocked for reading. How to move the interrupts |
|
|
|
is described in “Interrupts” on page 53. |
|
|
Consideration While Updating |
Special care must be taken if the user allows the Boot Loader section to be updated by |
|
|
BLS |
leaving Boot Lock bit11 unprogrammed. An accidental write to the Boot Loader itself can |
|
|
|
corrupt the entire Boot Loader, and further software updates might be impossible. If it is |
|
|
|
not necessary to change the Boot Loader software itself, it is recommended to program |
|
|
|
the Boot Lock bit11 to protect the Boot Loader software from any internal software |
|
|
|
changes. |
|
|
Prevent Reading the RWW |
During Self-Programming (either Page Erase or Page Write), the RWW section is |
|
|
Section During Self- |
always blocked for reading. The user software itself must prevent that this section is |
|
|
Programming |
addressed during the Self-Programming operation. The RWWSB in the SPMCR will be |
|
|
|
set as long as the RWW section is busy. During Self-Programming the Interrupt Vector |
|
|
|
table should be moved to the BLS as described in “Interrupts” on page 53, or the inter- |
|
|
|
rupts must be disabled. Before addressing the RWW section after the programming is |
|
|
|
completed, the user software must clear the RWWSB by writing the RWWSRE. See |
|
|
|
“Simple Assembly Code Example for a Boot Loader” on page 173 for an example. |
171
2512G–AVR–03/05
Setting the Boot Loader Lock bits by SPM
To set the Boot Loader Lock bits, write the desired data to R0, write “X0001001” to 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
See Table 74 and Table 75 for how the different settings of the Boot Loader bits affect |
|||||||||
|
the Flash access. |
|
|
|
|
|
|
|
|
|
|
If bits 5..2 in R0 are cleared (zero), the corresponding Boot Lock bit will be programmed |
|||||||||
|
if an SPM instruction is executed within four cycles after BLBSET and SPMEN are set in |
|||||||||
|
SPMCR. The Z-pointer is don’t care during this operation, but for future compatibility it is |
|||||||||
|
recommended to load the Z-pointer with $0001 (same as used for reading the Lock |
|||||||||
|
bits). For future compatibility It is also recommended to set bits 7, 6, 1, and 0 in R0 to “1” |
|||||||||
|
when writing the Lock bits. When programming the Lock bits the entire Flash can be |
|||||||||
|
read during the operation. |
|
|
|
|
|
|
|
||
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. |
|
|
|
|
|
|
|
|
|
Reading the Fuse and Lock bits from Software
It is possible to read both the Fuse and Lock bits from software. To read the Lock bits, load the Z-pointer with $0001 and set the BLBSET and SPMEN bits in SPMCR. When an LPM instruction is executed within three CPU cycles after the BLBSET and SPMEN bits are set in SPMCR, the value of the Lock bits will be loaded in the destination register. The BLBSET and SPMEN bits will auto-clear upon completion of reading the Lock bits or if no LPM instruction is executed within three CPU cycles or no SPM instruction is executed within four CPU cycles. When BLBSET and SPMEN are cleared, LPM will work as described in the Instruction set Manual.
Bit |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|
Rd |
– |
– |
BLB12 |
BLB11 |
BLB02 |
BLB01 |
LB2 |
LB1 |
|
|
|
|
|
|
|
|
|
|
|
The algorithm for reading the Fuse Low 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 three cycles after the BLBSET and SPMEN bits are set in the SPMCR, the value of the Fuse Low bits (FLB) will be loaded in the destination register as shown below. Refer to Table 84 on page 179 for a detailed description and mapping of the Fuse Low bits.
Bit |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Rd |
FLB7 |
FLB6 |
FLB5 |
FLB4 |
FLB3 |
FLB2 |
FLB1 |
FLB0 |
|
|
|
|
|
|
|
|
|
Similarly, when reading the Fuse High bits, load $0003 in the Z-pointer. When an LPM instruction is executed within three cycles after the BLBSET and SPMEN bits are set in the SPMCR, the value of the Fuse High bits (FHB) will be loaded in the destination register as shown below. Refer to Table 83 on page 178 for detailed description and mapping of the Fuse High bits.
Bit |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Rd |
FHB7 |
FHB6 |
FHB5 |
FHB4 |
FHB3 |
FHB2 |
FHB1 |
FHB0 |
|
|
|
|
|
|
|
|
|
Fuse and Lock bits that are programmed, will be read as zero. Fuse and Lock bits that are unprogrammed, will be read as one.
172 ATmega8515(L)
2512G–AVR–03/05
|
|
|
ATmega8515(L) |
|
|
|
|
|
Preventing Flash Corruption |
|
|
|
During periods of low VCC, the Flash program can be corrupted because the supply volt- |
||
|
|||
|
|
age is too low for the CPU and the Flash to operate properly. These issues are the same |
|
|
|
as for board level systems using the Flash, and the same design solutions should be |
|
|
|
applied. |
|
|
|
A Flash program corruption can be caused by two situations when the voltage is too low. |
|
|
|
First, a regular write sequence to the Flash requires a minimum voltage to operate cor- |
|
|
|
rectly. Secondly, the CPU itself can execute instructions incorrectly, if the supply voltage |
|
|
|
for executing instructions is too low. |
|
|
|
Flash corruption can easily be avoided by following these design recommendations (one |
|
|
|
is sufficient): |
|
|
|
1. If there is no need for a Boot Loader update in the system, program the Boot |
|
|
|
Loader Lock bits to prevent any Boot Loader software updates. |
|
|
|
2. Keep the AVR RESET active (low) during periods of insufficient power supply |
|
|
|
voltage. This can be done by enabling the internal Brown-out Detector (BOD) if |
|
|
|
the operating voltage matches the detection level. If not, an external low VCC |
|
|
|
Reset Protection circuit can be used. If a Reset occurs while a write operation is |
|
|
|
in progress, the write operation will be completed provided that the power supply |
|
|
|
voltage is sufficient. |
|
|
|
3. Keep the AVR core in Power-down Sleep mode during periods of low VCC. This |
|
|
|
will prevent the CPU from attempting to decode and execute instructions, effec- |
|
|
|
tively protecting the SPMCR Register and thus the Flash from unintentional |
|
|
|
writes. |
|
|
Programming Time for Flash |
The calibrated RC Oscillator is used to time Flash accesses. Table 77 shows the typical |
|
|
when using SPM |
programming time for Flash accesses from the CPU. |
|
|
|
Table 77. SPM Programming Time |
Simple Assembly Code Example for a Boot Loader
Symbol |
Min Programming Time |
Max Programming Time |
|
|
|
|
|
Flash Write (Page Erase, Page |
3.7 ms |
4.5 ms |
|
Write, and write Lock bits by SPM) |
|||
|
|
||
|
|
|
;-the routine writes one page of data from RAM to Flash
;the first data location in RAM is pointed to by the Y pointer
;the first data location in Flash is pointed to by the Z pointer ;-error handling is not included
;-the routine must be placed inside the boot space
;(at least the Do_spm sub routine). Only code inside NRWW section
can
;be read during Self-Programming (page erase and page write).
;-registers used: r0, r1, temp1 (r16), temp2 (r17), looplo (r24),
;loophi (r25), spmcrval (r20)
;storing and restoring of registers is not included in the routine
;register usage can be optimized at the expense of code size
;-It is assumed that either the interrupt table is moved to the Boot
; loader section or that the interrupts are disabled.
.equ |
PAGESIZEB = PAGESIZE*2 |
;PAGESIZEB is page size in BYTES, not |
words |
|
|
.org |
SMALLBOOTSTART |
|
Write_page: |
|
; page erase
ldi spmcrval, (1<<PGERS) | (1<<SPMEN) rcallDo_spm
173
2512G–AVR–03/05
|
|
|
|
|
|
|
|
|
|
|
|
|
|
; re-enable the RWW section |
|
|||||
ldi |
spmcrval, (1<<RWWSRE) | (1<<SPMEN) |
|||||
rcallDo_spm |
|
|||||
; transfer data from RAM to Flash page buffer |
||||||
ldi |
looplo, low(PAGESIZEB) |
;init loop variable |
||||
ldi |
loophi, high(PAGESIZEB) |
;not required for PAGESIZEB<=256 |
||||
Wrloop: |
|
|||||
ld |
r0, Y+ |
|
||||
ld |
r1, Y+ |
|
||||
ldi |
spmcrval, (1<<SPMEN) |
|
||||
rcallDo_spm |
|
|||||
adiw |
ZH:ZL, 2 |
|
||||
sbiw |
loophi:looplo, 2 |
;use subi for PAGESIZEB<=256 |
||||
brne |
Wrloop |
|
||||
; execute page write |
|
|||||
subi |
ZL, low(PAGESIZEB) |
;restore pointer |
||||
sbci |
ZH, high(PAGESIZEB) |
;not required for PAGESIZEB<=256 |
||||
ldi |
spmcrval, (1<<PGWRT) | (1<<SPMEN) |
|||||
rcallDo_spm |
|
|||||
; re-enable the RWW section |
|
|||||
ldi |
spmcrval, (1<<RWWSRE) | (1<<SPMEN) |
|||||
rcallDo_spm |
|
|||||
; read back and check, optional |
||||||
ldi |
looplo, low(PAGESIZEB) |
;init loop variable |
||||
ldi |
loophi, high(PAGESIZEB) |
;not required for PAGESIZEB<=256 |
||||
subi |
YL, low(PAGESIZEB) |
;restore pointer |
||||
sbci |
YH, high(PAGESIZEB) |
|
||||
Rdloop: |
|
|||||
lpm |
r0, Z+ |
|
||||
ld |
r1, Y+ |
|
||||
cpse |
r0, r1 |
|
||||
rjmp |
Error |
|
||||
sbiw |
loophi:looplo, 1 |
;use subi for PAGESIZEB<=256 |
||||
brne |
Rdloop |
|
;return to RWW section
;verify that RWW section is safe to read Return:
in temp1, SPMCR
sbrs temp1, RWWSB |
; If RWWSB is set, the RWW section is |
not |
|
|
; ready yet |
ret
; re-enable the RWW section
ldi spmcrval, (1<<RWWSRE) | (1<<SPMEN) rcallDo_spm
rjmp Return
Do_spm:
; check for previous SPM complete Wait_spm:
in temp1, SPMCR sbrc temp1, SPMEN rjmp Wait_spm
174 ATmega8515(L)
2512G–AVR–03/05
ATmega8515(L)
;input: spmcrval determines SPM action
;disable interrupts if enabled, store status in temp2, SREG
cli
;check that no EEPROM write access is present Wait_ee:
sbic EECR, EEWE rjmp Wait_ee
;SPM timed sequence
out SPMCR, spmcrval spm
; restore SREG (to enable interrupts if originally enabled) out SREG, temp2
ret
ATmega8515 Boot Loader |
In Table 78 through Table 80, the parameters used in the description of the Self-Pro- |
||||||||||||
Parameters |
gramming are given. |
|
|
|
|
|
|
|
|
|
|||
|
Table 78. Boot Size Configuration(1) |
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
Boot |
|
|
|
|
|
|
|
|
|
|
|
|
|
Reset |
|
|
|
|
|
|
|
|
|
|
|
|
|
Address |
|
|
|
|
|
|
|
|
Boot |
|
|
|
(start |
|
|
|
|
|
|
|
|
Application |
Loader |
|
End |
Boot |
||
|
BOOTS |
BOOTS |
|
Boot |
|
Flash |
Flash |
|
Application |
Loader |
|||
|
Z1 |
|
Z0 |
|
Size |
Pages |
Section |
Section |
|
Section |
Section) |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
|
1 |
|
128 |
4 |
0x000 - |
0xF80 - |
|
0xF7F |
0xF80 |
||
|
|
|
words |
0xF7F |
0xFFF |
|
|||||||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
|
0 |
|
256 |
8 |
0x000 - |
0xF00 - |
|
0xEFF |
0xF00 |
||
|
|
|
words |
0xEFF |
0xFFF |
|
|||||||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0 |
|
1 |
|
512 |
16 |
0x000 - |
0xE00 - |
|
0xDFF |
0xE00 |
||
|
|
|
words |
0xDFF |
0xFFF |
|
|||||||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0 |
|
0 |
|
1024 |
32 |
0x000 - |
0xC00 - |
|
0xBFF |
0xC00 |
||
|
|
|
words |
0xBFF |
0xFFF |
|
|||||||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||
|
Note: |
1. |
The different BOOTSZ Fuse configurations are shown in Figure 73 |
|
|||||||||
|
Table 79. Read-While-Write Limit(1) |
|
|
|
|
|
|
|
|||||
|
Section |
|
|
|
|
|
|
Pages |
|
Address |
|
||
|
|
|
|
|
|
|
|
||||||
|
Read-While-Write section (RWW) |
|
|
96 |
|
|
0x000 - 0xBFF |
||||||
|
|
|
|
|
|
|
|
||||||
|
No Read-While-Write section (NRWW) |
|
|
32 |
|
|
0xC00 - 0xFFF |
||||||
|
|
|
|
|
|
||||||||
|
Note: |
1. |
For details about these two section, see “NRWW – No Read-While-Write Section” on |
||||||||||
|
|
|
page 165 and “RWW – Read-While-Write Section” on page 165. |
|
175
2512G–AVR–03/05
Table 80. Explanation of Different Variables used in Figure 74 and the Mapping to the
Z-pointer(1)
|
|
|
Corresponding |
|
Variable |
|
|
Z-value |
Description |
|
|
|
|
|
PCMSB |
|
11 |
|
Most significant bit in the Program Counter. |
|
|
|
|
(The Program Counter is 12 bits PC[11:0]) |
|
|
|
|
|
PAGEMSB |
|
4 |
|
Most significant bit which is used to address |
|
|
|
|
the words within one page (32 words in a page |
|
|
|
|
requires five bits PC [4:0]). |
|
|
|
|
|
ZPCMSB |
|
|
Z12 |
Bit in Z-register that is mapped to PCMSB. |
|
|
|
|
Because Z0 is not used, the ZPCMSB equals |
|
|
|
|
PCMSB + 1. |
|
|
|
|
|
ZPAGEMSB |
|
Z5 |
Bit in Z-register that is mapped to PAGEMSB. |
|
|
|
|
|
Because Z0 is not used, the ZPAGEMSB |
|
|
|
|
equals PAGEMSB + 1. |
|
|
|
|
|
PCPAGE |
|
PC[11:5] |
Z12:Z6 |
Program Counter page address: Page select, |
|
|
|
|
for Page Erase and Page Write |
|
|
|
|
|
PCWORD |
|
PC[4:0] |
Z5:Z1 |
Program Counter word address: Word select, |
|
|
|
|
for filling temporary buffer (must be zero during |
|
|
|
|
Page Write operation) |
|
|
|
|
|
Note: 1. |
Z15:Z13: always ignored. |
|
||
|
Z0: should be zero for all SPM commands, byte select for the LPM instruction. |
|||
|
See “Addressing the Flash During Self-Programming” on page 169 for details about |
|||
|
the use of Z-pointer during Self-Programming. |
176 ATmega8515(L)
2512G–AVR–03/05