Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.

THIN by HCC-Embedded



Other Middleware

Product Description

THIN is a highly optimized, reduced footprint version of our highly successful FAT system. This DOS compatible file system is designed for configurations with limited resources. It is especially effective for use in low-power devices and environments with small amounts of RAM and ROM.

THIN is scalable. By selecting only the functionality required for the application, the system becomes highly optimized for both speed and size.

FEATURES

* FAT12, FAT16 and FAT32
* Long filenames
* Highly scalable
* Small footprint
* Low memory resource usage
* Media error handling
* Fully PC-compatible
* ANSI-compliant C source

SCALABILITY

THIN is a DOS-compatible flash file system that is designed to be extremely scalable. It allows the developer with limited resources to build precisely the system that is needed, and no more. The system is full-featured; new options can be enabled as requirements change.

It is not possible to give definitive figures for footprints because processors and development tools have major differences.

Estimated Code Footprint

Depending on the options selected at build time, the code footprint of the file system can be less than 4k for a minimum DOS-compatible system for accessing files on a disk, up to around 20K for a complete file system with all options enabled including disk formatting.

Data Footprint

THIN works completely independently of any host system. Memory is statically allocated; there is no need to provide a heap. The typical total data footprint is <1K plus 0.5K for each open file.

Stack Requirement

Typically the stack requirement for any call to the file system is less than 0.5K.

Options

The system contains a large number of build options. These are detailed in the developer’s guide. Some of the options are:

* F_FAT12
* F_FAT16
* F_FAT32
* F_FORMAT
* F_LONGFILES
* F_WRITE
* F_NAMECHECKING
* F_WILDCARDS
* F_DIRECTORIES
* ... and many, many more

Each and every API call can be included or excluded from the build. This automatically removes unnecessary sub-routines.

PORTING

THIN is designed to be very portable. It is tested on several commercial RTOSes and also in a stand-alone system with no RTOS. We are not aware of any RTOS with which it cannot be used.

All the code is supplied in ANSI-compliant C. It has been built on four different development environments and run through a syntax checker to ensure the highest level of compatibility.

Sample application code is supplied for easy exercise of the system, as well as sample drivers for different media types with clear reference to their hardware dependencies.

THIN

Market Segment(s)

  • Embedded
  • Mobile

Target Platform(s)

  • ITRON
  • Nucleus
  • OSE
  • Other OS
  • QNX
  • ThreadX
  • VRTX
  • VxWorks

ARM Processor(s)

  • ARM7EJ-S
  • ARM7TDMI
  • ARM7TDMI-S
  • ARM720T
  • ARM920T
  • ARM922T
  • ARM926EJ-S
  • ARM940T
  • ARM946E-S
  • ARM966E-S
  • ARM968E-S
  • VFP9-S
  • ARM1020E
  • ARM1022E
  • ARM1026EJ-S
  • VFP10
  • ARM1136J-S
  • ARM1136JF-S
  • ARM1156T2(F)-S
  • ARM1176JZ(F)-S
  • ARM11 MPCore
  • Cortex-A53
  • Cortex-A57
  • Cortex-A8
  • Cortex-A9
  • Cortex-M0
  • Cortex-M1
  • Cortex-M3
  • Cortex-R4
  • SC100
  • SC200
  • SC300
  • ARMv5
  • ARMv8
  • StrongARM
  • XScale
  • Other
 
ARM Connected