Hi Roger,
I agree with others that MFS is not right approach and using NAND flash controller with FFS way over kill.
What is the architecture of your current embedded flash based file system? How do you implement it?
If the number of configuration files is small and not changing often (i.e. on-chip Flash has limited erase/program cycles) say less than 10K cycles, just using your flash based file system should work.
A more formal filesystem for this might be using TFS with MQX (or specifically the OSA_Abstraction layer):
C:\Freescale\KSDK_1.2.0\rtos\mqx\mqx\source\nio\drivers\nio_tfs\src
It does require OSA function calls such as OSA _MemAlloc, OSA_MemFree, OSA_SemaDestroy, etc...
A MQX httpsrv example of having web pages in on-chip flash using a TFS (Trivial File System) is at:
C:\Freescale\KSDK_1.2.0\middleware\tcpip\rtcs\examples\httpsrv
Look at the _readme.txt in the folder.
Files can be place into the ./filesystem/web folder and when the mktfs.bat is run a new nio_tfs_data.c is generated. Compile it into your application and you are good to go.
Regards,
David