All geek questions in one place

Is it worth it to implement a small file system for EEPROM

I bought an EEPROM I2C. I want to store sensor and voltage data. I assume that the value can be more than one byte, and there can be a lot of data. Is it worth it to implement a file system with a small file allocation table? It would be easier for me to look into the EEPROM, for example.

+4
source share
3 answers

I see two reasons for FAT on EEPROM

  • If there is a need for the flexibility of having different files. Such as for data logging or configurations. It allows several of these configuration / log files to be independent and easy to add in the future. This can be a very successful building block for future projects.
  • For easy access to other devices or libraries. Usually this is only an option if the memory device is directly accessible by another interface. Where, as in this case, is the EEPROM. If your device was directly USB-compatible, such as ATmega32u4 (leo), you can use LUFA tools to make USB appear as MASS storage. Creating FAT is the perfect solution. Or perhaps if the device has an Ethernet screen.

, , KISS (Keep It Simple Solution) . .

, SdCards Sd ( IDE), SdFat ( GitHub), FAT32. - .

+3

, mpflaga .

, , :

  • /, , , , ?
  • ?
  • / , , / /etc?

, :

  • , , , / , .

  • , , , , , .

  • . , TLV, , ; , , . , , , , !

, :

  • , , .
  • , , .
+3

Having a small standard file system such as FAT16 is worth implementing because you can map this file system via USB or a network to other devices / computers.

Standardization in your design is a big advantage in terms of compliance.

You can find ready-made sources / libraries or, if it is FAT16, and because it is really simple and well described / documented, try to realize yourself.

+1
source

Source: https://habr.com/ru/post/1548396/

More articles:


All Articles