是否值得实现一个EEPROM的小文件系统 [英] Is it worth to implement small filesystem for an EEPROM
问题描述
- 如果要求具有不同文件的灵活性。如
用于数据记录或配置。它允许多个这样的配置/日志文件在将来独立并且容易地被添加。这对未来的项目来说可能是非常成功的基石。 - 便于其他设备或库的访问。如果内存设备可以被其他接口直接访问，通常只有一个选项。在这种情况下，它是一个EEPROM。如果您的设备是直接支持USB的，例如ATmega32u4（leo），则可以使用LUFA工具将USB显示为MASS存储。使FAT成为理想的解决方案。或者可能的话，如果该设备有一个以太网盾。
所有说法，如果这种情况下只是一个数据记录器，然后KISS它简单的解决方案）可能是一个好方法。因此，人们可以关注收集数据本身的原始主题。
值得注意的是，SdCards可以轻松添加廉价的Sd库（IDE股票）或SdFat库（GitHub更多的功能）添加几乎无限容量的FAT32日志记录。唯一的折衷是它们消耗了一大片代码空间。
I have bought an I2C EEPROM. I want to store sensor and voltage data. I'm assuming that value can be bigger than one byte, and there can be a lot of data. Is it worth is such case to implement a filesystem with small file allocation table? It would make me easier to peek trought EEPROM for example.
I see two causes for a FAT on EEPROM
- If there is a requirement for the flexibility of having different files. Such as for data logging or configurations. It allows multiple such configuration/log files, to be independent and easily added in the future. This can be a very successful building block for future projects.
- For ease of access by other devices or libraries. Typically only an option if the memory device is directly accessible by other interface. Where as in this case it is an EEPROM. If your device was directly USB capable, such as a ATmega32u4 (leo) then you can use LUFA tools to have the USB show up as MASS storage. Making FAT an ideal solution. Or possibly if the device has an Ethernet Shield.
with all being said and if this case simply a datalogger, then the KISS (Keep It Simple Solution) may be a good way to go. So that one can keep focus on the original subject for collecting the data itself.
It is worth noting that SdCards can be easily added for cheap either of the well established Sd library (IDE stock) or SdFat Library (GitHub more features) adding an almost infinite capacity of logging of FAT32. The only trade off is they consume a fair chunk of code space.
这篇关于是否值得实现一个EEPROM的小文件系统的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
