| Electronic Components Datasheet Search |
|
XC2000 Datasheet(PDF) 109 Page - Infineon Technologies AG |
|
|
|||||||||||||||||||||||||||||
XC2000 Datasheet(HTML) 109 Page - Infineon Technologies AG |
|
109 / 647 page ![]() XC2000 Derivatives System Units (Vol. 1 of 2) Memory Organization Preliminary User’s Manual 3-47 V1.0, 2007-06 MemoryX2K, V1.1 3.9.8 EEPROM Emulation The flash memory of the XC2000 is used for three purposes: 1. Storage of program code. Updates happen usually very seldom. The main criteria to be fulfilled is a retention of the life-time of the product. 2. Storage of constant data: this data is stored together with program code. So this data is very seldom updated. Endurance is of no issue here but retention identical to the code memory is required. 3. Data updated during run-time: this might be data with a very high frequency of updates like a mileage counter or access keys for key-less entry. Other data might be changed only in case of failures and other data might only be transferred from RAM to non-volatile memory before the system is powered down. Especially for the third type of data the non-volatile memory needs EEPROM like characteristics: • Fine program/erase granularity which is in EEPROMs typically 1 byte. • Higher endurance than the intrinsic endurance of flash cells. • Short program and erase duration per byte. Especially for storing data in an emergency (e.g. power failure) short latencies might be required. A basic requirement for changing data during run-time is that code execution can still resume, especially interrupt requests must still be serviced. This requirement is fulfilled in the XC2000 because all three flash modules work independently. If one is busy with program or erase then code can still be executed from the other two. The other requirements are more difficult to fulfill because the XC2000 does not have an EEPROM available but only the flash memory with the already frequently mentioned limitations: big program/erase granularity, moderately long program/erase duration, limited cell endurance with reduced retention at high number of program/erase cycles, pages not isolated but affected by drain disturbs. In order to alleviate these effects on run-time storage of data software is used to emulate EEPROM. There is quite a number of algorithms for efficiently using flash memory as EEPROM. The following section describes one (the most simple) of these algorithms. It should be noted that the XC2000 does not offer the customer any hardware means for EEPROM emulation. All of the following must be realized by software. 3.9.8.1 The Traditional EEPROM Emulation This algorithm was already used in the Pegasus devices. The key point is to solve the limited endurance by storing data in N different physical places. In XC2000 the algorithm would use N sequential pages or groups of pages. If data is currently stored in the page “x” then the next program happens to the page “(x+1) mod N”. The software typically stores the current address in a table in RAM to avoid searching for the page at every access. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |