• Full POSIX and ANSI C file system API.
  
  
• FFS specific directory quotas API.
  
  
• User triggered volume garbage collection via vclean().
  
  
• Volume statistics via vstat().
  
  

• A rugged, re-entrant, power-fail safe file system with a POSIX and ANSI C compliant API. Use of NOR flash media for the backing store is invisible to the application layer.
  
  
• Supports dynamic creation and deletion of files, directories and links with full read and write capability.
  
  
• Implements optimal wear leveling to prolong the life of the flash media.
  
  
• 'Thin' driver layer for maximum ease in porting to new platforms.
  
  

• A rugged, re-entrant, power-fail safe file system with a POSIX and ANSI C compliant API. Use of NAND flash media for the backing store is invisible to the application layer.
  
  
• Supports dynamic creation and deletion of files, directories and links with full read and write capability.
  
  
• Implements optimal wear leveling to prolong the life of the flash media.
  
  
• Detects bad NAND blocks and performs bad block recovery without user intervention.
  
  
• Can sit on top of Blunk's NAND device manager (TargetNDM) to allow for:
  • efficient use of NAND devices
  • volume partitions
  • en-masse factory pre-programming using the Skip Bad Block method
  
  
  
• 'Thin' driver layer for maximum ease in porting to new platforms.
  
  

• A reliable, re-entrant file system with a POSIX and ANSI C compliant API.
  
  
• Supports the FAT12, FAT16, and FAT32 formats.
  
  
• Long file name support (VFAT) and UTF8 file name support can be enabled as compile-time options.
  
  
• Combined with TargetFTL (NAND, NOR or NDM), TargetFAT provides power-fail recovery.
  
  
• Unique file system feature supports background reclamation of 'dirty' flash sectors when used with Blunk Microsystems' FTL products.
  
  

• Works under TargetFAT to implement a reliable, re-entrant FAT file system. Use of NAND flash media for the backing store is invisible to the application layer.
  
  
• Combined with TargetFAT, TargetFTL-NDM provides power-fail recovery.
  
  
• Sits on top of Blunk's NAND device manager (TargetNDM) to allow for:
  • efficient use of NAND devices
  • volume partitions
  • en-masse factory pre-programming using the Skip Bad Block method
  
  
  

• Works under TargetFAT to implement a reliable, re-entrant FAT file system. Use of NOR flash media for the backing store is invisible to the application layer.
  
  
• Combined with TargetFAT, TargetFTL-NOR provides power-fail recovery.
  
  
• Implements wear-leveling to prolong life of the flash media.
  
  
• 'Thin' driver layer for maximum ease in porting to new platforms.
  
  

• Detects bad NAND blocks and performs bad block recovery without user intervention.
  
  
• Supports multiple volumes (FFS, FAT or user specified) per device via partitions.
  
  
• Allows for en-masse factory pre-programming using the Skip Bad Block Method.
  
  
• 'Thin' driver layer for maximum ease in porting to new platforms.
  
  

• Serves as a read-only compressed file system for components such as an embedded web server, TargetWeb.
  
  
• Facilitates compression of application programs to be loaded into RAM for execution.
  
  
• Compresses data without losing read-only file system access to it.
  
  
• Reduces data transmission for files that are to be retrieved from a device.
  
  

• A reliable, re-entrant RAM based file system with a POSIX and ANSI C compliant API. Use of RAM for the backing store is invisible to the application layer.
  
  
• Provides fast storage of temporary files.
  
  
• Automatically calls malloc() and free() as needed when files are created, grown, or deleted. No configuration or pre-allocation of RAM memory is required.
  
  
• Garbage collection is performed to ensure minimal use of RAM for file system control information.
  
  

• Supports all commercially available CF cards
• Sits below TargetFAT and provides the read_sector()/write_sector() interface

• Supports all commercially available SD cards
• Sits below TargetFAT and provides the read_sector()/write_sector() interface
• Uses a simple SPI driver interface layer to talk to the SD card; example driver available
• Interrogates SD card for size, special features (high speed, high capacity (>2GB), etc.)