Datasheet

Section 19 Flash Memory (F-ZTAT Version)
Rev. 3.00 Mar 17, 2006 page 794 of 926
REJ09B0283-0300
3. After the program data has been confirmed, the RAMS bit is cleared, thus releasing RAM
overlap.
4. The data written in the overlapping RAM is written into the flash memory space (EB0).
Start of emulation program
Set RAMER
Write tuning data to overlap
RAM
Execute application program
Tuning OK?
Clear RAMER
Write to flash memory
emulation block
End of emulation program
No
Ye s
Figure 19.8 Flowchart for Flash Memory Emulation in RAM
Example in which flash memory block is overlapped is shown in figure 19.9.
1. The RAM area to be overlapped is fixed at a 4-kbyte area in the range of H'FFA000 to
H'FFAFFF.
2. The flash memory area to overlap is selected by RAMER from a 4-kbyte area among one of
the EB0 to EB7 blocks.
3. The overlapped RAM area can be accessed from both the flash memory addresses and RAM
addresses.
Notes: 1. When the RAMS bit in RAMER is set to 1, program/erase protection is enabled for all
flash memory blocks (emulation protection). In this state, setting the P or E bit in
FLMCR1 to 1 does not cause a transition to program mode or erase mode.
2. A RAM area cannot be erased by execution of software in accordance with the erase
algorithm.