Page Comparison

...

The generic controller driver imposes a specific page layout: the sectors are stored sequentially in the main page area and OOS metadata zones are stored sequentially in the spare area, packed in the free spare zones specified by the .FreeSpareMap field of the associated FS_PART_DATA data structure. An example layout is shown below for a device with 2048 octets pages, using 512 bytes sectors.

To determine if the generic controller driver is compatible with your hardware, you can study its BSP interface, described in BSP Development Guide - Generic Controller.

...

The generic controller extension layer extends the functionality of the generic controller, mostly with regards to ECC. It allows for the reuse of the generic controller code, enabling easy customizations of the controller layer. The NAND driver ships with two generic controller extensions:

The software ECC generic controller extension (FS_NAND_CtrlrGen_SoftECC) uses µC/CRC’s ECC modules for the ECC codewords calculation and data correction. The extension is configurable through a FS_NAND_CTRLR_GEN_SOFT_ECC_CFG type structure. It should be initialized to the value FS_NAND_CtrlrGen_SoftEcc_DfltCfg before its fields are overridden to the appropriate values for your application.

typedef  struct  fs_nand_cfg {
    const ECC_CALC  *ECC_ModulePtr;                     (1)
} FS_NAND_CFG;

The Micron ECC generic controller extension (FS_NAND_CtrlrGen_MicronECC) allows the use of internal on-chip hardware ECC engines for some Micron NAND flash parts. The extension has been designed as an example for the Micron MT29F1G08ABADA, but should function properly with other similar Micron devices with internal ECC hardware modules. This module doesn’t have any configuration options, you should use DEF_NULL as the generic controller extension configuration pointer (.CtrlrExtCfg field of the FS_NAND_CTRLR_GEN_CFG structure).

...