If i decide to use the PIC then the "Microchip MDD File System" is my choice...
If i get deep into it and use a ARM7 uC then i will use the FatFs code since its more portable. I might be able to port the MDD FileSystem from Microchip to the ARM7 uC but will be more work i think lol
Cannot help you there, nor give advice, I use MMC cards to "log" stuff that is "much more data then eeprom can hold" or when "usb interface to computer" is not feasible (device is unmovable, computer is not near .. etc)...
As I log *mine* data to the card, I will need *mine* application to read that data and present it (for example the temperature and pressure for last 6 months measured every 15minutes - the recent project, final version is with 2 eeproms but first version was with mmc card).... As *mine* application is reading the data, data does not need to be "on fat disk in text file"
I write data directly to MMC card, raw, with checksum (even double it sometimes for safety), then I write app to read that data directly from the card on windoze side...
The benefit is:
- full control over the data
- no overhead to implement fs functions (code on uC is smaller)
- speed of execution (code on uC is faster)
- speed of development (code on uC is written very fast)
The downside is:
- you have to implement low level IO read from card so you are somehow limited by the languages accessible (you cannot raw read the card from perl/php/java on windows for example)
- you have to have client application installed on the computer to retrieve data, you cannot use "any" computer to backup the content of the card