...
The port being contemplated may already exist; failing that, some similar CPU/device may have already be supported.
FC-1(1) µC/Clk act as a centralized clock management module. If you use an external real-time clock, you will have to write functions to let µC/FS know the date and time.
FC-1(2) The CPU port (within µC/CPU) adapts the file system suite to the CPU and compiler characteristics. The fixed-width types (e.g., CPU_INT16U) used in the file system suite are defined here.
FC-1(3) The RTOS port adapts the file system suite to the OS kernel (if any) included in the application. The files FS_OS.C/H contain functions primarily aimed at making accesses to devices and critical information in memory thread-safe.
FC-1(4) µC/FS interfaces with memory devices through drivers following a generic driver model. It is possible to create a driver for a different type of device from this model/template.
FC-1(5) The SD/MMC driver can be ported to any SD/MMC host controller for cardmode access.
FC-1(6) The SD/MMC driver can be ported to any SPI peripheral for SPI mode access.
FC-1(7) The NAND driver can be ported for many physical organizations (page size, bus width, SLC/MLC, etc.).
FC-1(8) The NAND driver can be ported to any bus interface. A NAND device can also be located directly on GPIO and accessed by direct toggling of port pins.
FC-1(9) The NOR driver can be ported to many physical organization (command set, bus type, etc.).
FC-1(10) The NOR driver can be ported to any bus interface.
FC-1(11) The NOR driver can be ported to any SPI peripheral (for SPI flash).