Datasheet

Table Of Contents
235
ATmega32A [DATASHEET]
Atmel-8155D-AVR-ATmega32A-Datasheet_02/2014
26. Boot Loader Support – Read-While-Write Self-Programming
26.1 Features
Read-While-Write Self-Programming
Flexible Boot Memory size
High Security (Separate Boot Lock Bits for a Flexible Protection)
Separate Fuse to Select Reset Vector
Optimized Page
(1)
Size
Code Efficient Algorithm
Efficient Read-Modify-Write Support
Note: 1. A page is a section in the flash consisting of several bytes (see Table 26-5 on page 269) used during program-
ming. The page organization does not affect normal operation.
26.2 Overview
The Boot Loader Support provides a real Read-While-Write Self-Programming mechanism for downloading and
uploading program code by the MCU itself. This feature allows flexible application software updates controlled by
the MCU using a Flash-resident Boot Loader program. The Boot Loader program can use any available data inter-
face and associated protocol to read code and write (program) that code into the Flash memory, or read the code
from the Program memory. The program code within the Boot Loader section has the capability to write into the
entire Flash, including the Boot Loader memory. The Boot Loader can thus even modify itself, and it can also erase
itself from the code if the feature is not needed anymore. The size of the Boot Loader memory is configurable with
Fuses and the Boot Loader has two separate sets of Boot Lock bits which can be set independently. This gives the
user a unique flexibility to select different levels of protection.
26.3 Application and Boot Loader Flash Sections
The Flash memory is organized in two main sections, the Application section and the Boot Loader section (see Fig-
ure 25-2). The size of the different sections is configured by the BOOTSZ Fuses as shown in Table 25-6 on page
263 and Figure 25-2. These two sections can have different level of protection since they have different sets of
Lock bits.
26.3.1 Application Section
The Application section is the section of the Flash that is used for storing the application code. The protection level
for the application section can be selected by the Application Boot Lock bits (Boot Lock bits 0), see Table 25-2 on
page 256. The Application section can never store any Boot Loader code since the SPM instruction is disabled
when executed from the Application section.
26.3.2 BLS – Boot Loader Section
While the Application section is used for storing the application code, the The Boot Loader software must be
located in the BLS since the SPM instruction can initiate a programming when executing from the BLS only. The
SPM instruction can access the entire Flash, including the BLS itself. The protection level for the Boot Loader sec-
tion can be selected by the Boot Loader Lock bits (Boot Lock bits 1), see Table 25-3 on page 256.
26.4 Read-While-Write and no Read-While-Write Flash Sections
Whether the CPU supports Read-While-Write or if the CPU is halted during a Boot Loader software update is
dependent on which address that is being programmed. In addition to the two sections that are configurable by the
BOOTSZ Fuses as described above, the Flash is also divided into two fixed sections, the Read-While-Write
(RWW) section and the No Read-While-Write (NRWW) section. The limit between the RWW- and NRWW sections
is given in Table 25-7 on page 263 and Figure 25-2 on page 255. The main difference between the two sections is: