File system what to choose

[pietrodicastri]

Good morning

I need a file system for a bare metal. I see there are two proposed solutions in the SDK, the FatFs and the MFS.

What are the reasons to select one or the other?.

In the perspective of interacting the lwip is one better than the other?

Thank You

[ivadorazinova]

Hi,

the biggest difference is, that MFS is dedicated to use with MQX in contrast with FatFS.

In SDK we have example here c:\Freescale\SDK_2.0_FRDM-K64F\boards\frdmk64f\driver_examples\sdcard_fatfs\

You can use lwIP Stack lwIP - A Lightweight TCP/IP stack - Summary [Savannah]

and FNET as well FNET Embedded TCP/IP Stack

I hope this helps.

Iva

[pietrodicastri]

Thank Everybody

So it is clear without MQX I can not use the MFS.

I see the example using the FatFs, it is not attached to the TCP/IP stack.

Please make clear definitely the TCP/IP stack, whoever it is, does not rely on a specific file system.

Thanks

Pietro

[mjbcswitzerland]

Hi

TCP/IP stacks don't use file systems.

Some services, such as HTTP or FTP or other application above TCP/IP, may use a file system. Generally they will open a file, list or read/write file content and so use a pretty standard API that can be used directly, or with a simple cover function, with any file system available.

In some cases you may need to preare data for listing (eg. FTP) in a certain format - either the file system used will support that format so that you need not do any thing or else you will need to add an intermediete layer to convert listings to the appropriate format, but this is not a big task to do.

When using USB sticks, SD card etc. as removable file system media you may need to add removal, mounting management to generally control this if the file system doesn't include it inherently but this will depend more on your overall system design.

Regards

Mark

[pietrodicastri]

Hi Mark

That's the point I was trying to make clear,

Thank you

I was meaning to place the correct answer, but I don t remember how to do, or something has changed since last time I did,

Suggestions for this task are accepted,,

Thank

Pietro

[mjbcswitzerland]

Hi

The comparison between the file systems gives extremently little detail to compare their actual capabilities.

Note that you can also use the utFAT from http://www.utasker.com/forum/index.php?topic=1667.0

http://www.utasker.com/docs/uTasker/uTasker_utFAT.PDF

in bare-metal projects, which has the following advantages:

- multiple instances in non-pre-emptive environment

- SD card, Memory Stick, RAM drive, internal Flash, SPI Flash, NAND Flash instances possible

- Emulated FAT mode for visualising linear data as FAT - http://www.utasker.com/docs/uTasker/uTaskerEmulatedFAT.pdf

- Multi-users of files with file protection and synchronisation

- FAT12/16/32 with LFN and Linux LFN write work-around (avoiding Microsoft patent breaches)

- Optional data buffering of file data on a per-file basis for performance optimisation

- Advanced features such a file-on-disk analysis, undelete etc.

When used in uTasker project it is fully integrated into the web and FTP servers of the TCP/IP stack so requires no further messing about between file system and stack. Valid also for RNDIS operation over USB.

Fully simulated (in Visual Studio) in approx. real-time allowing TCP/IP, file system, SDC and Kinetis operation to be fully emulated for highest performance development/debugging/code reviews etc.

Regards

Mark

[pietrodicastri]

Thank You for the support

[pietrodicastri]

Thank You

I have some answer in the document.

I am sure the MQX RTOS will not like the FtFs but it is not my problem.

I need to know what are the limitations if any, with the LWIP stack.

Have You a tip for the matter?

[pranavmadhu]

Hi,

I'm sorry that I'm not having any further knowledge about it.

Best Regards
Pranav

[pranavmadhu]

Hi,
Please refer the link below (Page 7)

http://cache.nxp.com/files/soft_dev_tools/doc/support_info/MQXKSDKGSUG.pdf