Rev. 1.0, 09/02, page 460 of 568
An example in which flash memory block area EB0 is overlapped is shown in figure 19.8.
1. The RAM area to be overlapped is fixed at a 1-kbyte area in the range H
′
FFE000 to
H
′
FFE3FF.
2. The flash memory area to overlap is selected by RAMER from a 1-kbyte area of the EB0 to
EB3 blocks.
3. The overlapped RAM area can be accessed from both the flash memory addresses and RAM
addresses.
4. 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 P1 or E1 bit in FLMCR1 to 1
does not make a transition to program mode or erase mode.
5. A RAM area cannot be erased by execution of software in accordance with the erase
algorithm.
6. Block area EB0 contains the vector table. When performing RAM emulation, the vector table
is needed in the overlap RAM.
H'000000
Flash memory
(EB0)
Flash memory
(EB0)
(EB1)
(EB2)
(EB3)
H'0003FF
H'000400
H'0007FF
H'000800
H'000BFF
H'000C00
H'000FFF
H'FFE000
H'FFE3FF
On-chip RAM
(1 kbyte)
On-chip RAM
(Shadow of
H'FFE000 to
H'FFE3FF)
Flash memory
(EB2)
On-chip RAM
(1 kbyte)
(EB3)
Normal memory map
Memory map
with overlapped RAM
Figure 19.8 Example of RAM Overlap Operation
Summary of Contents for H8S/2627
Page 22: ...Rev 1 0 09 02 page xx of xxxvi Index 565 ...
Page 30: ...Rev 1 0 09 02 page xxviii of xxxiv ...
Page 36: ...Rev 1 0 09 02 page xxxiv of xxxiv Table 23 9 Flash Memory Characteristics 561 ...
Page 82: ...Rev 1 0 09 02 page 46 of 568 ...
Page 88: ...Rev 1 0 09 02 page 52 of 568 ...
Page 98: ...Rev 1 0 09 02 page 62 of 568 ...
Page 156: ...Rev 1 0 09 02 page 120 of 568 ...
Page 390: ...Rev 1 0 09 02 page 354 of 568 ...
Page 480: ...Rev 1 0 09 02 page 444 of 568 ...
Page 512: ...Rev 1 0 09 02 page 476 of 568 ...
Page 528: ...Rev 1 0 09 02 page 492 of 568 ...
Page 580: ...Rev 1 0 09 02 page 544 of 568 ...