AT89LP51 datasheet(16/113 Pages) ATMEL

16 / 113 page

3709C–MICRO–5/11

AT89LP51/52 - Preliminary

not accessible while DMEN = 0. FDATA can be accessed only by 16-bit (MOVX @DPTR)

addresses. MOVX @Ri instructions to the FDATA address range will access external memory.

Addresses above the FDATA range are mapped to XDATA.

3.3.2.1

Write Protocol

The FDATA address space accesses an internal nonvolatile data memory. This address space

can be read just like EDATA by issuing a MOVX A,@DPTR; however, writes to FDATA require a

more complex protocol and take several milliseconds to complete.

For internal execution the AT89LP51/52 uses an idle-while-write architecture where the CPU is

placed in an idle state while the write occurs. When the write completes, the CPU will continue

executing with the instruction after the MOVX @DPTR,A instruction that started the write. All

peripherals will continue to function during the write cycle; however, interrupts will not be ser-

viced until the write completes.

For external execution the AT89LP51/52 uses an execute-while-write architecture where the

CPU continues to operate while the write occurs. The software should poll the state of the BUSY

flag to determine when the write completes. Interrupts must be disabled during the write

sequence as the CPU will not be able to vector to the internal interrupt table and care should be

taken that the application does not jump to an internal address until the write completes.

To enable write access to the nonvolatile data memory, the MWEN bit (MEMCON.4) must be set

to one. When MWEN = 1 and DMEN = 1, MOVX @DPTR,A may be used to write to FDATA.

FDATA uses flash memory with a page-based programming model. Flash data memory differs

from traditional EEPROM data memory in the method of writing data. EEPROM generally can

update a single byte with any value. Flash memory splits programming into write and erase

operations. A Flash write can only program zeroes, i.e change ones into zeroes (). Any

ones in the write data are ignored. A Flash erase sets an entire page of data to ones so that all

bytes become FFH. Therefore after an erase, each byte in the page can only be written once

with any possible value. Bytes can be overwritten without an erase as long as only ones are

changed into zeroes. However, if even a single bit needs updating from zero to one (

);

then the contents of the page must first be saved, the entire page must be erased and the zero

bits in all bytes (old and new data combined) must be written. Avoiding unnecessary page

erases greatly improves the endurance of the memory..

The AT89LP51/52 includes 2 data pages of 128 bytes each. One or more bytes in a page may

be written at one time. The AT89LP51/52 includes a temporary page buffer of 64 bytes, or half of

a page. Because the page buffer is 64 bytes long, the maximum number of bytes written at one

time is 64. Therefore, two write cycles are required to fill the entire 128-byte page, one for the

low half page (00H–3FH) and one for the high half page (40H–7FH) as shown in Figure 3-7.

Figure 3-7.

Page Programming Structure

→

Low Half Page

Data Memory

High Half Page

Page Buffer

AT89LP51 Datasheet(PDF) 16 Page - ATMEL Corporation

AT89LP51 Datasheet(HTML) 16 Page - ATMEL Corporation

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

Datasheet Download

Link URL