Could you advice any file system to include in our project for IoT application?
I hope that somebody on this forum had faced the similar problems.
We are looking for solution allows to make three function: write, read, erase. The system should works fast and be
insensitive to power failures.
Firstly, we tried to use Coffee file system https://github.com/contiki-os/contiki/w ... em-example
But it works too slow.
Also we tried out to use the UBI FS / JAFFS systems from Linux. But actually we haven't enough RAM for this systems.
Therefore we are looking for something else.
The our prototype has NOR flash (64 Mb). Controller stm32f3*.
File system for NOR flash
Moderators: RoccoMarco, lbednarz, tfAteba
- Giovanni
- Site Admin
- Posts: 14893
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 997 times
Re: File system for NOR flash
Hi,
OK, no other answers. I don't have a ready solution, are you sure there isn't something else that could be adapted? by searching on Google I get several results.
Giovanni
OK, no other answers. I don't have a ready solution, are you sure there isn't something else that could be adapted? by searching on Google I get several results.
Giovanni
Re: File system for NOR flash
Why not FatFS? I have it working smoothly at stm32f072 with 16kB of RAM, for a 8 MB so8-size flash.
Re: File system for NOR flash
kreyl wrote:Why not FatFS? I have it working smoothly at stm32f072 with 16kB of RAM, for a 8 MB so8-size flash.
Won't there be no wear levelling, so it will kill the sectors that are beat most at the start of the FS? That's why there are specialist FS for flash......
- Giovanni
- Site Admin
- Posts: 14893
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 997 times
Re: File system for NOR flash
I think that FatFS could be used on top of an EEPROM emulator that does wear leveling.
Disk blocks don't need to be at fixed addresses in flash but written sequentially replacing old copies, reaching the end of the flash bank would trigger a garbage collection involving a flash erase.
I had plans for a flash FS but I dropped it, a generic EE emulator would be more useful.
Giovanni
Disk blocks don't need to be at fixed addresses in flash but written sequentially replacing old copies, reaching the end of the flash bank would trigger a garbage collection involving a flash erase.
I had plans for a flash FS but I dropped it, a generic EE emulator would be more useful.
Giovanni