Rtfs tiny is a very low footprint implementation of the FAT file system with journaling support.
C Makefile
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
License
Makefile
README.MD
codesizes.txt
main
main.c
manual.txt
rtfslconst.c
rtfsldata.c
rtfsldelete.c
rtfslfailsafe.c
rtfslfileseek.c
rtfslfilestat.c
rtfslfiliocore.c
rtfslfiliord.c
rtfslfiliowr.c
rtfslfssystem.c
rtfslgfirst.c
rtfslite.h
rtfslitecore.c
rtfsliteshell.c
rtfslitetests.h
rtfslmkdir.c
rtfslopenpath.c
rtfslrename.c
rtfslrmdir.c
rtfslsystem.c
rtfstlitefileload.c
rtfstlitetestfileio.c
rtfstlitetests.c
rtfstlitetestutils.c

README.MD

Tinyfatfs Low footprint Embedded FAT file system

EBS - RTFS (Real Time File Manager)

  • Copyright, Peter Van Oudenaren

  • EBS Inc. 1987-2015

  • All rights reserved.

  • This code may not be redistributed in source or linkable object form

  • without the consent of its author.

  • contact sales@ebsembeddedsoftware.com

Rtfs tiny is a very low footprint implementation of the FAT file system.

This software was written as an experiment to create the smallest footprint FAT file system with the most attainable functionality.

The code achieves small code size by relying on experience providing commercial FAT file system products over many years.

The current code does not support vfat but that can be added pretty easilly in we estimate 1 to 2 K of code space.

The code is still not totally refined so beware, send us an email if you'd find a bug or you would like to conrtibute a patch.

The ram and rom requirements for rtfsl built under various configurations is provided below.

These are for the ARM Processor using the IAR compiler, similar builds need to be made for AVR.

read only code bytesread only data bytes read/write data bytesbuild description
7422 52 1340 Full build with journaling optimized for size
7098 86 792 Full build minus journaling un-optimized
5480 52 792 Full build minus journaling optimized
5192 20 780 Full build minus journaling, minus subdirectory support optimized for size
3588 20 780 Read only file io, directory traversal and file stat functions.
2896 12 532 Functionality to load a file from the root directory into memory, optimized for size.

Full build includes the follow functionality for fat12, fat16 and fat32.
  • create a sub-directory in the root or in a subdirectory.
  • delete a sub-directory
  • create a file in the root or in a subdirectory.
  • write to a file.
  • read from a file.
  • seek within a file.
  • close a file.
  • delete a file
  • When Failsafe support is enabled, the follow functionality is included.

    • . journaling flush.
    • . journaling journal of FAT table changes and directory entry changes.
    • . journaling restore.

    To build the test applcation for a Linux target: type:. make

    To run the symple command shell based example:

    type: sudo ./main devicename

    for example, to access a USB stick at /dev/sdb1: sudo ./main /dev/sdb1

    If that is successful you should see the following help screen:

    LOAD FILENAME
    LMOUNT - re-mount rtfs lite drive
    LEXIT - Exit Lite mode refreshes device mount for rtfs
    LFLUSH - Flush rtfs lite buffers
    DIR
    RENAME oldname newname
    DELETE filename
    CHDIR path
    MKDIR dirname 0|1 (1 = fragment)
    RMDIR dirname
    FILLPAT filename nlongs 0|1 (1=fragment)
    APPENDPAT filename nlongs 0|1 (1=fragment)
    READPAT filename
    RANDREAD filename
    RANDWRITE filename
    FILLDISK filenamebase
    FSSTART Start Journaling
    FSSTOP Stop Journaling
    FSSYNC Sync volume, keep journaling
    FSFLUSH Flush journal keep journaling
    FSRESTORE Retore the volume from the journal

    The currently supported features include:
    . File io (create,reopen, read,write,seek,delete).
    . Subdirectory support (mkdir, rmdir and set working directory).
    . Failsafe journaling and restore support.
    . All features have been tested both with using Failsafe and not using Failsafe.
    . All tests have been performed with FAT12 so far, typically the most difficult case.

    Ongoing development efforts include the following:
    . Tests still need to be performed on FAT16 and FAT32.
    . Testing is on-going with development of more rigorous tests planned for tomorrow.