Page Comparison

...

• fs_dev_nand.c (\Micrium\Software\uC-FS\Dev\NAND.)
• fs_dev_nand.h (\Micrium\Software\uC-FS\Dev\NAND.)
• fs_dev_nand_ctrlr_gen.c (\Micrium\Software\uC-FS\Dev\NAND\Ctrlr)
• fs_dev_nand_ctrlr_gen.h (\Micrium\Software\uC-FS\Dev\NAND\Ctrlr)
• fs_dev_nand_part_static.c (\Micrium\Software\uC-FS\Dev\NAND\Part)
• fs_dev_nand_part_static.h (\Micrium\Software\uC-FS\Dev\NAND\Part)
• ecc_hamming.c (\Micrium\Software\uC-CRC\Source)
• ecc_hamming.h (\Micrium\Software\uC-CRC\Source)
• ecc.h (\Micrium\Software\uC-CRC\Source)
• Your BSP layer implementation (derived from fs_dev_nand_ctrlr_gen_bsp.c in \Micrium\Software\uC-FS\Dev\NAND\BSP\Template).

The example in the listing below shows  shows how to open a single NAND volume. The file system initialization function (FS_Init()) must have previously been called.

If the NAND initialization succeeds, the file system traces (if a sufficiently high trace level is configured) will produce an output similar to the listing below . See section Trace Configuration about configuring the trace level.

...