ST eeprom simulation weird memory footprint.

[dotm]

I simply refuse to understand this, maybe someone can enlight me:
When I read AN4056 (http://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/DM00049071.pdf) it says:

Memory footprint for EEPROM emulation mechanism
Minimum⁽¹⁾ required code size (bytes)
Flash: 2260
SRAM: 2074
(1) Based on one 32-bit variable (16-bit for address and 16-bit for data). The SRAM memory used increases
depending on the number of variables used.

Well then look at the code attached. It's the driver. Where the   are the 2k RAM used?
I even thought that maybe the Flash functions have compiler directives to be loaded to the ram, but: no.
This is driving me NUTS!  

[sn00p]

A quick read of the data sheet indicates that it has a mode where you store "variables" in flash, I and sync them between ram and flash with a flush call.  It looks like its all caching.

[bobcat1]

Hi

Flash memory can only written in block's (depend on processor word size)
There for you need at lest twice the size of the lowest block size to emulate eeprom on flash

All the best

Bobi

[dotm]

Flash memory can only written in block's (depend on processor word size)
There for you need at lest twice the size of the lowest block size to emulate eeprom on flash

Do you mean Pages? If yes, this driver uses two pages to continouusly transfer from one to another.
My question was: where at the code (for the driver) is the SRAM used with such a huge amount

[Ichan]

My question was: where at the code (for the driver) is the SRAM used with such a huge amount

I am just guessing, it can be on the flash access routine - i think the eeprom driver calling it.

Have you compile the code? Is the compiler confirm that 2K RAM requirement?

Yeah no internal eeprom can be a pain, i choose to use external eeprom / fram - remember that writing the flash will stall the MCU, no interrupt can be catch on that time.

-ichan

[dotm]

I am just guessing, it can be on the flash access routine - i think the eeprom driver calling it.

Have you compile the code? Is the compiler confirm that 2K RAM requirement?

See attached file. have not found the RAM usage in this driver neither. I want to avoid any further ram usage that's why I hesitated using the eeprom driver yet.
As far as I can see this code will not use any more RAM than the stack.