PIC16F62X
At the completion of the write cycle, the WR bit is
cleared in hardware and the EE Write Complete
Interrupt Flag bit (EEIF) is set. The user can either
enable this interrupt or poll this bit. The EEIF bit in the
PIR1 registers must be cleared by software.
13.3
READING THE EEPROM DATA
MEMORY
To read a data memory location, the user must write
the address to the EEADR register and then set con-
trol bit RD (EECON1<0>). The data is available, in the
very next cycle, in the EEDATA register; therefore it
can be read in the next instruction. EEDATA will hold
this value until another read or until it is written to by
the user (during a write operation).
13.5
WRITE VERIFY
Depending on the application, good programming
practice may dictate that the value written to the Data
EEPROM should be verified (Example 13-3) to the
desired value to be written. This should be used in
applications where an EEPROM bit will be stressed
near the specification limit.
EXAMPLE 13-1: DATA EEPROM READ
BCF
STATUS, RP0 ; Bank 0
MOVLW CONFIG_ADDR
;
MOVWF
BSF
BSF
BCF
MOVF
EEADR
; Address to read
STATUS, RP0 ; Bank 1
EECON1, RD ; EE Read
STATUS, RP0 ; Bank 0
EEDATA, W ; W = EEDATA
EXAMPLE 13-3: WRITE VERIFY
BCF
:
STATUS, RP0 ; Bank 0
; Any code can go here
:
;
13.4
WRITING TO THE EEPROM DATA
MEMORY
MOVF EEDATA, W
BSF
BSF
; Must be in Bank 0
STATUS, RP0 ; Bank 1 READ
EECON1, RD ; YES, Read the
; value written
To write an EEPROM data location, the user must first
write the address to the EEADR register and the data
to the EEDATA register. Then the user must follow a
specific sequence to initiate the write for each byte.
BCF
STATUS, RP0 ; Bank 0
;
; Is the value written (in W reg) and
; read (in EEDATA) the same?
;
EXAMPLE 13-2: DATA EEPROM WRITE
SUBWF EEDATA, W
;
BSF
BSF
BCF
MOVLW
MOVWF
MOVLW
MOVWF
BSF
STATUS, RP0
EECON1, WREN
INTCON, GIE
55h
EECON2
AAh
; Bank 1
BTFSS STATUS, Z
GOTO WRITE_ERR
:
:
; Is difference 0?
; NO, Write error
; YES, Good write
; Continue program
; Enable write
; Disable INTs.
;
; Write 55h
;
; Write AAh
; Set WR bit
; begin write
; Enable INTs.
EECON2
EECON1,WR
13.6
PROTECTION AGAINST SPURIOUS
WRITE
BSF
INTCON, GIE
There are conditions when the device may not want to
write to the data EEPROM memory. To protect against
spurious EEPROM writes, various mechanisms have
been built in. On power-up, WREN is cleared. Also,
the Power-up Timer (72 ms duration) prevents
EEPROM write.
The write will not initiate if the above sequence is not
exactly followed (write 55h to EECON2, write AAh to
EECON2, then set WR bit) for each byte. We strongly
recommend that interrupts be disabled during this
code segment. A cycle count is executed during the
required sequence. Any number what is not equal to
the required cycles to execute the required sequence
will cause the data not to be written into the EEPROM.
The write initiate sequence and the WREN bit together
help prevent an accidental write during brown-out,
power glitch, or software malfunction.
Additionally, the WREN bit in EECON1 must be set to
enable write. This mechanism prevents accidental
writes to data EEPROM due to errant (unexpected)
code execution (i.e., lost programs). The user should
keep the WREN bit clear at all times, except when
updating EEPROM. The WREN bit is not cleared
by hardware
13.7
DATA EEPROM OPERATION DURING
CODE PROTECT
When the device is code protected, the CPU is able to
read and write unscrambled data to the Data
EEPROM.
After a write sequence has been initiated, clearing the
WREN bit will not affect this write cycle. The WR bit
will be inhibited from being set unless the WREN bit is
set.
1999 Microchip Technology Inc.
Preliminary
DS40300B-page 93