ATmega32C1 Automotive Atmel Corporation, ATmega32C1 Automotive Datasheet - Page 280

• Manufacturer Part Number: ATmega32C1 Automotive
• Manufacturer: Atmel Corporation

Specifications of ATmega32C1 Automotive

• Flash (kbytes): 32 Kbytes
• Pin Count: 32
• Max. Operating Frequency: 16 MHz
• Cpu: 8-bit AVR
• # Of Touch Channels: 12
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 27
• Ext Interrupts: 27
• Usb Speed: No
• Usb Interface: No
• Spi: 1
• Uart: 1
• Can: 1
• Lin: 1
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 11
• Adc Resolution (bits): 10
• Adc Speed (ksps): 125
• Analog Comparators: 4
• Resistive Touch Screen: No
• Dac Channels: 1
• Dac Resolution (bits): 10
• Temp. Sensor: Yes
• Crypto Engine: No
• Sram (kbytes): 2
• Eeprom (bytes): 1024
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: No
• Picopower: No
• Temp. Range (deg C): -40 to 150
• I/o Supply Class: 2.7 to 5.5
• Operating Voltage (vcc): 2.7 to 5.5
• Fpu: No
• Mpu / Mmu: no / no
• Timers: 2
• Output Compare Channels: 4
• Input Capture Channels: 1
• Pwm Channels: 4
• 32khz Rtc: No
• Calibrated Rc Oscillator: Yes

24.3
24.3.1
24.3.2
280
Read-While-Write and No Read-While-Write Flash Sections
Atmel ATmega16/32/64/M1/C1
RWW – Read-While-Write Section
NRWW – No Read-While-Write Section
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
the two sections is:
Note that the user software can never read any code that is located inside the RWW section
during a Boot Loader software operation. The syntax “Read-While-Write section” refers to
which section that is being programmed (erased or written), not which section that actually is
being read during a Boot Loader software update.
If a Boot Loader software update is programming a page inside the RWW section, it is possi-
ble to read code from the Flash, but only code that is located in the NRWW section. During an
on-going programming, the software must ensure that the RWW section never is being read. If
the user software is trying to read code that is located inside the RWW section (i.e., by a
call/jmp/lpm or an interrupt) during programming, the software might end up in an unknown
state. To avoid this, the interrupts should either be disabled or moved to the Boot Loader sec-
tion. The Boot Loader section is always located in the NRWW section. The RWW Section
Busy bit (RWWSB) in the Store Program Memory Control and Status Register (SPMCSR) will
be read as logical one as long as the RWW section is blocked for reading. After a program-
ming is completed, the RWWSB must be cleared by software before reading code located in
the RWW section.
page 284.
The code located in the NRWW section can be read when the Boot Loader software is updat-
ing a page in the RWW section. When the Boot Loader code updates the NRWW section, the
CPU is halted during the entire Page Erase or Page Write operation.
Table 24-1.
• When erasing or writing a page located inside the RWW section, the NRWW section can
• When erasing or writing a page located inside the NRWW section, the CPU is halted during
Which Section does the Z-pointer
be read during the operation.
the entire operation.
Table 24-8 on page 292
Address During the
for details on how to clear RWWSB.
Programming?
NRWW Section
RWW Section
Read-While-Write Features
See “Store Program Memory Control and Status Register – SPMCSR” on
and
Figure 24-2 on page
Which Section Can
be Read During
Programming?
NRWW Section
None
282. The main difference between
Is the CPU
Halted?
Yes
No
Read-While-Write
Supported?
7647G–AVR–09/11
Yes
No