Download Application Note - Renesas Electronics

Transcript
Overview
Chapter 1
1.2 General approach
For the 78k0 devices the same physical flash memory is used for storing
application code as well for the EEL data. The flash memory does not support so
called “dual operation”, consequently each flash access being performed by the
self-programming firmware inhibits the execution of application code at the same
time. From CPU point of view the application code disappears practically during
the flash access. This fact influences seriously the real-time behavior of the whole
system when the EEL driver is active. NEC’s implementation of the EEPROM
emulation tries to defuse the real-time situation and to retrieve the maximum of
flexibility and transparency for applications operation. Following claims and
requirements formed the guideline for the chosen implementation way:
•
•
•
•
•
•
•
•
•
simple straight forward architecture based on request-response
model
write and read access of any data portions between 1 and 255 bytes
EEL variable identification based on unique 1 byte identifier
inconsistencies caused by asynchronous power-off RESET are
always detectable and repairable
reparation initiated by the application to avoid a non-deterministic
write/read access time
read- and write-access time is independent of the internal driver
status
no blocking time longer than a period pre-determined by the user
user configurable interrupt scenario for EEL operation
no additional interrupt latency caused by the EEL driver
Basically the data stored in an EEPROM could be categorized as following:
1.
2.
3.
static data like product number, serial number, static parameter….
rare updatable data like immobilizer key, engine characteristic…
agile, dynamic data like ODO-meter, window lifter position….
For handling of data type (1.) we recommend to use pure self-programming
functions however it is also possible to integrate it into the EEPROM emulation.
Data of type (2.) and (3.) are predestined to be managed by the EEPROM
emulation driver. The partitioning of the data should be done with respect to
constrains resulting from the limited flash block-size. This causes limited number
of independent EEL variables and is limiting total size (sum of particular sizes) of
all EEL variables.
Application Note U18991EE2V0AN00
9