I am working on a new prototype to be used for production eventually. I need to store some 200 configuration variables (floats ie 123.21234)and read them on startup and save them on change. My question is which would be better for this type of use FLASH or EEPROM? It appears that FLASH is read/written in large blocks while EEPROM can be read in single bytes?
Which will be easier to work with on the mbed platform to store and retreive these variables?
Thanks
Hello
I am working on a new prototype to be used for production eventually. I need to store some 200 configuration variables (floats ie 123.21234)and read them on startup and save them on change. My question is which would be better for this type of use FLASH or EEPROM? It appears that FLASH is read/written in large blocks while EEPROM can be read in single bytes?
Which will be easier to work with on the mbed platform to store and retreive these variables?
Thanks
I don't think the original supported floats directly, but this shouldn't be too difficult to plumb in.
There was also a library to do the same for the AT45 flash parts from Atmel, but those parts are hard to get hold of at the moment.
Hope that helps,
Chris
Hi Matt,
There is a nice Serial EEPROM class here :
http://mbed.org/users/Yann/libraries/24LCxx_I2C/lkvm6r
I don't think the original supported floats directly, but this shouldn't be too difficult to plumb in.
There was also a library to do the same for the AT45 flash parts from Atmel, but those parts are hard to get hold of at the moment.
Hope that helps,
Chris
Your disticntion is correct - EEPROMS can be written in single bytes, whereas flash always is written blocks. But both can be read byte by byte (but depending on how the interface really works).
For your problem, maybe you can have a look at the mFS library, which implements a small file system on top of an I2C-EEPROM.
Your disticntion is correct - EEPROMS can be written in single bytes, whereas flash always is written blocks. But both can be read byte by byte (but depending on how the interface really works).
For your problem, maybe you can have a look at the [[http://mbed.org/users/HBP/notebook/mfs/|mFS]] library, which implements a small file system on top of an I2C-EEPROM.
the Microchip EEPROM im using has a page buffer of 64KB and rated at 1,000,000 write cycles
its also fairly easy to use using the I2C commands with mbed
some EEPROMS can be read/write by page
the Microchip EEPROM im using has a page buffer of 64KB and rated at 1,000,000 write cycles
its also fairly easy to use using the I2C commands with mbed
For small amount of data like this, I think would be better EEPROM. It's easier to work with and also component cost is cheaper than Flash.
For small amount of data like this, I think would be better EEPROM. It's easier to work with and also component cost is cheaper than Flash.
Important Information for this Arm website
This site uses cookies to store information on your computer.
By continuing to use our site, you consent to our cookies.
If you are not happy with the use of these cookies, please review our
Cookie Policy
to learn how they can be disabled.
By disabling cookies, some features of the site will not work.
Access Warning
You do not have the correct permissions to perform this operation.
Hello
I am working on a new prototype to be used for production eventually. I need to store some 200 configuration variables (floats ie 123.21234)and read them on startup and save them on change. My question is which would be better for this type of use FLASH or EEPROM? It appears that FLASH is read/written in large blocks while EEPROM can be read in single bytes?
Which will be easier to work with on the mbed platform to store and retreive these variables?
Thanks