HCS08 datasheet(42/198 Pages) NXP

42 / 198 page

Chapter 4 Memory Map and Register Definition

MC9S08QD4 Series MCU Data Sheet, Rev. 6

Freescale Semiconductor

•

Writing a second time to a flash address before launching the previous command (There is only

one write to flash for every command.)

•

Writing a second time to FCMD before launching the previous command (There is only one write

to FCMD for every command.)

•

Writing to any flash control register other than FCMD after writing to a flash address

•

Writing any command code other than the five allowed codes (0x05, 0x20, 0x25, 0x40, or 0x41)

to FCMD

•

Writing any flash control register other than to write to FSTAT (to clear FCBEF and launch the

command) after writing the command to FCMD.

•

The MCU enters stop mode while a program or erase command is in progress (The command is

aborted.)

•

Writing the byte program, burst program, or page erase command code (0x20, 0x25, or 0x40) with

a background debug command while the MCU is secured (The background debug controller can

do blank check and mass erase commands only when the MCU is secure.)

•

Writing 0 to FCBEF to cancel a partial command

4.5.6

Flash Block Protection

The block protection feature prevents the protected region of flash from program or erase changes. Block

protection is controlled through the flash protection register (FPROT). When enabled, block protection

begins at any 512 byte boundary below the last address of flash, 0xFFFF. (see Section 4.7.4, “Flash

Protection Register (FPROT and NVPROT).”)

After exit from reset, FPROT is loaded with the contents of the NVPROT location which is in the

nonvolatile register block of the flash memory. FPROT cannot be changed directly from application

software so a runaway program cannot alter the block protection settings. Because NVPROT is within the

last 512 bytes of flash, if any amount of memory is protected, NVPROT is itself protected and cannot be

altered (intentionally or unintentionally) by the application software. FPROT can be written through

background debug commands, which allows a way to erase and reprogram a protected flash memory.

The block protection mechanism is illustrated in Figure 4-4. The FPS bits are used as the upper bits of the

last address of unprotected memory. This address is formed by concatenating FPS7:FPS1 with logic 1 bits

as shown. For example, in order to protect the last 8192 bytes of memory (addresses 0xE000 through

0xFFFF), the FPS bits must be set to 1101 111, which results in the value 0xDFFF as the last address of

unprotected memory. In addition to programming the FPS bits to the appropriate value, FPDIS (bit 0 of

NVPROT) must be programmed to logic 0 to enable block protection. Therefore the value 0xDE must be

programmed into NVPROT to protect addresses 0xE000 through 0xFFFF.

Figure 4-4. Block Protection Mechanism

FPS7

FPS6

FPS5

FPS4

FPS3

FPS2

FPS1

A15

A14

A13

A12

A11

A10

A7 A6 A5 A4 A3 A2 A1 A0

111

HCS08 bảng dữ liệu(PDF) 42 Page - NXP Semiconductors

HCS08 bảng dữ liệu(HTML) 42 Page - NXP Semiconductors

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

bảng dữ liệu tải về

Link URL