COP8AME9 Datasheet, PDF(29/83 Page) National Semiconductor (TI) – 8-Bit CMOS Flash Microcontroller with 8k Memory, Dual Op Amps, Virtual EEROM, Temperature Sensor,10-Bit A/D and Brownout Reset

English

English German Russian Spanish Italian Polish Chinese Japanese Korean French Portuguese	Language :

COP8AME9 Datasheet, PDF (29/83 Pages) National Semiconductor (TI) – 8-Bit CMOS Flash Microcontroller with 8k Memory, Dual Op Amps, Virtual EEROM, Temperature Sensor,10-Bit A/D and Brownout Reset

◁

11.0 In-System Programming (Continued)

Name

ISPADHI

ISPADLO

ISPWR

ISPRD

ISPKEY

BYTECOUNTLO

PGMTIM

Confirmation Code

KEY

TABLE 12. Register and Bit Name Definitions

Purpose

High byte of Flash Memory Address

Low byte of Flash Memory Address

The user must store the byte to be written into this register before jumping into the

write byte routine.

Data will be returned to this register after the read byte routine execution.

The ISPKEY Register is required to validate the JSRB instruction and must be loaded

within 6 instruction cycles before the JSRB.

Holds the count of the number of bytes to be read or written in block operations.

Write Timing Register. This register must be loaded, by the user, with the proper value

before execution of any USER ISP Write or Erase operation. Refer to Table 8 for the

correct value.

The user must place this code in the accumulator before execution of a Flash Memory

Mass Erase command.

Must be transferred to the ISPKEY register before execution of a JSRB instruction.

RAM

Location

0xA9

0xA8

0xAB

0xAA

0xE2

0xF1

0xE1

0x98

11.9 RESTRICTIONS ON SOFTWARE WHEN CALLING

ISP ROUTINES IN BOOT ROM

1. The hardware will disable interrupts from occurring. The

hardware will leave the GIE bit in its current state, and if

set, the hardware interrupts will occur when execution is

returned to Flash Memory. Subsequent interrupts, dur-

ing ISP operation, from the same interrupt source will be

lost. Interrupt may occur between setting the KEY

and executing the JSRB instruction. In this case, the

KEY will expire before the JSRB is executed. It is,

therefore, recommended that the software globally

disable interrupts before setting the Key.

2. The security feature in the MICROWIRE/PLUS ISP is

guaranteed by software and not hardware. When ex-

ecuting the MICROWIRE/PLUS ISP routine, the security

bit is checked prior to performing all instructions. Only

the mass erase command, write PGMTIM register, and

reading the Option register is permitted within the

MICROWIRE/PLUS ISP routine. When the user is per-

forming his own ISP, all commands are permitted. The

entry points from the userâs ISP code do not check for

security. It is the burden of the user to guarantee his own

security. See the Security bit description in Section 10.5

OPTION REGISTER for more details on security.

3. When using any of the ISP functions in Boot ROM, the

ISP routines will service the WATCHDOG within the

selected upper window. Upon return to flash memory,

the WATCHDOG is serviced, the lower window is en-

abled, and the user can service the WATCHDOG any-

time following exit from Boot ROM, but must service it

within the selected upper window to avoid a WATCH-

DOG error.

4. Block Writes can start anywhere in the page of Flash

memory, but cannot cross half page or full page bound-

aries.

5. The user must ensure that a page erase or a mass

erase is executed between two consecutive writes to

the same location in Flash memory. Two writes to

the same location without an intervening erase will

produce unpredicatable results including possible

disturbance of unassociated locations.

11.10 FLASH MEMORY DURABILITY CONSIDERATIONS

The endurance of the Flash Memory (number of possible

Erase/Write cycles) is a function of the erase time and the

lowest temperature at which the erasure occurs. If the device

is to be used at low temperature, additional erase operations

can be used to extend the erase time. The user can deter-

mine how many times to erase a page based on what

endurance is desired for the application (e.g. four page

erase cycles, each time a page erase is done, may be

required to achieve the typical 100k Erase/Write cycles in an

application which may be operating down to 0ËC). Also, the

customer can verify that the entire page is erased, with

software, and request additional erase operations if desired.

TABLE 13. Typical Flash Memory Endurance

Erase

Time

1 ms

2 ms

3 ms

4 ms

5 ms

6 ms

7 ms

8 ms

Low End of Operating Temp Range

â40ËC â20ËC 0ËC 25ËC

60k

70k

80k

90k

100k

60k

70k

80k

90k

100k

60k

100k

>25ËC

100k

www.national.com

▷