...
The port being contemplated may already exist; failing that, some similar CPU/device may have already be supported.
| Panel | ||
|---|---|---|
| ||
|
| Panel | ||
|---|---|---|
| ||
(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. (2) The CPU port (within µC/CPU) adapts the file system suite to the CPU and compiler characteristics. The fixed-width types (e.g., (3) The RTOS port adapts the file system suite to the OS kernel (if any) included in the application. The files (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. (5) The SD/MMC driver can be ported to any SD/MMC host controller for cardmode access. (6) The SD/MMC driver can be ported to any SPI peripheral for SPI mode access. (7) The NAND driver can be ported for many physical organizations (page size, bus width, SLC/MLC, etc.). (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. (9) The NOR driver can be ported to many physical organization (command set, bus type, etc.). (10) The NOR driver can be ported to any bus interface. (11) The NOR driver can be ported to any SPI peripheral (for SPI flash). |