You need to investigate further to confirm the possible corruption and the solution may imply to low-level format the NAND chip with FSMedia_LowFmt(). In that case it might be a low-level corruption issue. The second situation is that the automatic NAND FTL configuration has not worked, and you did not specify a valid NAND FTL configuration. In that case, verify your FS_NAND_FTL_CFG structure parameters. The first situation is that you have manually specified the NAND FTL configuration using the function FS_NAND_FTL_ConfigureLowParams(). This error may arise in two situations regarding how the NAND FTL configuration is specified. It occurs because the NAND FTL configuration read from the flash block metadata does not match the user configuration. RTOS_ERR_BLK_DEV_FMT_INCOMPATIBLE: the device low-level format is incompatible with the user configuration. In the case of NAND media, you may use the debug utility function called FS_NAND_Dump() to take a NAND image snapshot for further analysis of the low-level corruption root cause before low-level formatting. The file data are still present but cannot be retrieved anymore as a new file system information must also be written. The low-level format operation builds a new metadata structure on the physical NAND or NOR flash device that will be used by the FTL. If your NAND or NOR metadata becomes corrupted for any reason, please note that a low-level format will prevent you from accessing your file data if the media was formatted with a FAT file system. Refer to section Low-Level Formatting a Media for more details. You need to low-level format the media in order to recover from these errors by using FSMedia_LowFmt(). These errors mean that the FTL was not able to use the metadata retrieved from the physical media. They are only returned by NAND and NOR media when a low-level mounting is performed. RTOS_ERR_BLK_DEV_FMT_INVALID and RTOS_ERR_BLK_DEV_CORRUPTED: these errors indicate that the low-level format is invalid and the block device metadata is corrupted, respectively. Both of these media need a certain quantity of RAM to allocate internal resources for the proper operation of the Flash Translation Layer (FTL). If the heap size is too low, this error is more likely to happen with a NAND or NOR media. In that case, the heap size is increased using LIB_MEM_CFG_HEAP_SIZE. By default the File System Core and Storage layers use the heap region as a default memory segment. RTOS_ERR_SEG_OVF: some internal resources could not be allocated on a given memory segment. When opening a block device, you may encounter these typical errors:
When calling FSBlkDev_Open(), I get an error. I want to open a file or directory on a default volume, can I still do it?
When writing a few files of a few KB in size in a RAM disk, I get the error RTOS ERR VOL FULL. I am creating a cache instance, which parameters values should I choose for the cache configuration? I want to partition my media, which options do I have? When calling FSFile Open() / FSDir Open() / FSWrkDir Open() / FSFile Write() / FSDir Truncate(), I get an error. When calling FSVol Open(), I get an error. When calling FSBlkDev Open(), I get an error.
0 kommentar(er)
