This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HERCULES-F021FLASHAPI: Using FEE library on top of F021

Expert 1920 points
Part Number: HERCULES-F021FLASHAPI
Other Parts Discussed in Thread: HALCOGEN

The FEE library or driver, from HalCogen, is based on the F021 or uses it.

I don't fully understand why one needs this FEE driver. What does it provide on top of the F021 library which is really needed to read, write the emulated EEPROM?

The virtual sectors and blocks of data, those look entirely software constructs. So can I do without it, if I just do flash word writes?

Also this is a dumb question, but is direct read access those flash locations through just mem mapped addresses  (i.e, through direct load to register from 0xF0200000 etc..)?  not possible because it sits on "Flash Wrapper"  / Bus 2 interface or goes through VBUSM switch,  unlike main flash which is direct to Cortex?

What is "Flash Wrapper"  ?

  • Hello,

    Many applications require storing small quantities of system related data (e.g., calibration values, device configuration) in a non-volatile memory, so that it can be used, modified or reused even after power cycling the system. EEPROMs are primarily used for this purpose. EEPROMs have the ability to erase and write individual bytes of memory many times over and the programmed locations retain the data over a long period even when the system is powered down.

    The objective of TI FEE Driver is to provide a set of software functions intended to use a Sector of on-chip Flash memory (bank 7) as the emulated EEPROM. 

    You can write data to bank 7 using F021 APIs directly. If you know the address of the data, you can read it directly from the address.

  • Is the Flash type and technology same in bank 7 as in bank0 (main flash) ?  Is "Emulated EEPROM" only due to software layer, or that flash is more supportive of some way.?

    Where can I read on how many writes it supports life time, and it's data retension?

  • Hi V01d,

    The EEPROM uses the same technology as the main flash. 

    Where can I read on how many writes it supports life time, and it's data retension?

    You can find them in datasheet.

  • Ok, if they have same technology,  what is then the difference between these tags - Fapi_FLEP  Fapi_FLEE Fapi_FLES Fapi_FLHV ?  

    On some devices as you know, 0714, it returns FLEE for EEPROM flash, on some - 1227 - it returns FLEP.    Are these only to discriminate between flash programing widths?    Could you map each to each for me, I could only see 3 possibilities (with ECC),  288, 144, 72.

  • Frankly, I don't know other differences among FLEE, FLEP, and FLV.