Tevero Logo  
Go to home page Go to product page Go to services page Go to contact info page Tevero Hjem - Norsk
 

FAQ (Frequently Asked Questions)

Download RDC doc.

Download shrdconf.h and rdcconf.h file to see what needs to be configured.

Go here for pricing info and conditions.

 
RDC The RAM Disk Controller (RDC) provides an easy-to-add component in order to also use TFFS on RAM media. This is especially suitable for embedded systems with flash disks (slow) and temporary and/or permanent RAM disks (fast).

RDC is suitable for embedding with any target and any OS, as long as the C/C++ language is supported. It has been designed in a robust manner in order to cope with restarts and abnormal terminations.

RDC is primarily intended for use with TFFS.


Datasheet:

RDC provides the following functionality:

  • Volatile mode for temporary partitions (not recoverable)

  • Non-volatile mode for recoverable partitions (for instance battery backed-up RAM).

  • Usable in a preemptive context (i.e. reentrant). Protection is provided by user defined protection functions per partition as needed. (May not be needed if using similar higher layer protection in for instance a file system.)

  • Applicable for any random access memory (RAM) media with optional provision of access drivers for special handling.

  • Handling an unlimited number of RAM disk partitions.

  • Supports removable RAM media.

  • The minimum write unit (block) is user defined per partition (minimum 32 bytes).

  • Each partition may theoretically support up to 228 - 1 blocks

  
  • Supports the recovery of any aborted write operation (power failure etc.) in non-volatile mode

  • Optional support for 'errno' updating

  • Some diagnostics functions supported

  • Written in ANSI/ISO C.

  • Host debugging and development support.

The following is required when using RDC and is not included in RDC:

  • Optionally provide read and/or write function for accessing RAM media with special requirements.

  • If used in a preemptive context, protection functions for the selected environment must be implemented if no higher level protection exists.

  • Provide the following C library glue functions: free, malloc, memcmp, memcpy, memset, strcmp, strcpy, strlen, and printf (printf only if debugging or diagnostics enabled). The functions are defined in shrdconf.h/rdcconf.h and they must all be reentrant if used in a preemptive environment


© 2000-2010

real competence - real commitment - real-time

mail@tevero.no