The Embedded Experts

Release notes for emFile version V5.28.0

Version 5.28.0 [26 February 2024]

New Features

  1. Added support for fail-safe erase operation to Universal NAND driver.
  2. Added support for GigaDevice GD25Q16C serial NOR flash device.
  3. Added "freesectors" command to Storage Image Creator utility.
  4. Added FS_WINDRIVE_AllowImageFile() API function.
  5. Added FS_GetVolumeLayout() API function.
  6. Added FS_GetClusterInfo() API function.
  7. Added FS_GetATInfo() API function.
  8. Added FS_GetFirstCluster() API function.

Improvements

  1. Storage Image Creator: Extended the "format" command by a parameter that can be used to specify the cluster size.
  2. File Disk driver: Improved the initialization of sector usage information.

Program corrections

  1. File system: The file system failed to correctly delete a file with a size greater than 232 bytes minus number of bytes in a cluster. Fixed. Introduced in the initial version.
  2. File system: The file system failed to correctly change the size of a file with a size greater than 232 bytes minus number of bytes in a cluster. Fixed. Introduced in the initial version.
  3. File system: The file system was not able to determine that a file or directory was located on the default volume if the name of that file or directory did not contain a volume name. This behavior occurs only when a file or directory name is passed as parameter to an API function that instead expects a volume name. Fixed. Introduced in version 5.0.0
  4. EFS: FS_Format() failed to correctly format a storage device with a total number of clusters that is either a power of 2 value or one less than a power of 2 value. This behavior does not affect applications that call FS_Format() with the second parameter set to NULL. Fixed. Introduced in the initial version.
  5. FAT: FS_Move() failed to preserve the modification time of the source file. Fixed. Introduced in the initial version.
  6. Serial NOR physical layer: Winbond W25Q512JV NOR flash device was not identified correctly. Fixed. Introduced in version 5.24.0
  7. 2048x8 NAND physical layer: The physical layer failed to return the correct number of bit errors that occurred in a NAND page. This behavior affects Toshiba and Samsung NAND flash devices with internal HW ECC. Fixed. Introduced in version 4.04a
  8. ONFI NAND physical layer: The physical layer failed to return the correct number of bit errors that occurred in a NAND page. This behavior affects Macronix and SkyHigh NAND flash devices with internal HW ECC. Fixed. Introduced in version 5.8.0

Version 5.26.0 [4 December 2023]

New Features

  1. Added Storage Image Creator.
  2. Added support for trim operation to File Disk driver.
  3. Added FS_GetFileSizeEx() API function.
  4. Added FS_STORAGE_SyncEx() API function.
  5. Added FS_STORAGE_FindVolumeByIndex() API function.
  6. Added FS_STORAGE_FreeSectorsEx() API function.
  7. Added FS_STORAGE_Mount() API function.
  8. Added FS_STORAGE_MountEx() API function.
  9. Added FS_STORAGE_GetCleanCntEx() API function.
  10. Added FS_STORAGE_CleanOneEx() API function.
  11. Added FS_STORAGE_CleanEx() API function.
  12. Added FS_STORAGE_GetSectorUsageEx() API function.
  13. Added FS_STORAGE_RefreshSectorsEx() API function.
  14. Added FS_STORAGE_SyncSectorsEx() API function.
  15. Added FS_STORAGE_SetAutoMountType() API function.
  16. Added FS_STORAGE_GetAutoMountType() API function.
  17. Added FS_STORAGE_GetMountType() API function.
  18. Added FS_STORAGE_SetAutoMountTypeEx() API function.
  19. Added FS_STORAGE_GetAutoMountTypeEx() API function.
  20. Added FS_STORAGE_GetMountTypeEx() API function.
  21. Added FS_STORAGE_FindVolumeByDevice() API function.

Improvements

  1. File system: Improved the performance of the file copy operation.
  2. Serial NOR physical layer: Improved the handling of read mode bits.

Program corrections

  1. File system: FS_FClose() returned a wrong error code when it failed to read the directory entry of the file. Fixed. Introduced in version 5.1.0
  2. File system: FS_SetFileSize() returned a wrong error code when it failed to read the directory entry of the file. Fixed. Introduced in version 5.1.0
  3. File system: FS_SetEndOfFile() returned a wrong error code when it failed to read the directory entry of the file. Fixed. Introduced in version 5.1.0
  4. File system: FS_CopyFile() failed to report an error when the application unmounted the volume on which the destination file was located while the copy operation was in progress. This behavior affects configurations that set FS_OS_LOCKING to 2. Fixed. Introduced in the initial version.
  5. File system: FS_CopyFileEx() failed to report an error when the application unmounted the volume on which the destination file was located while the copy operation was in progress. This behavior affects configurations that set FS_OS_LOCKING to 2. Fixed. Introduced in the initial version.
  6. EFS: FS_Format() failed to format a storage device when the specified cluster size was greater than 128 sectors. Fixed. Introduced in the initial version.
  7. File system: FS_FGets() failed to report an error when the file handle was invalidated by a different task during the operation. This behavior affects configurations that set FS_OS_LOCKING to 2. Fixed. Introduced in version 5.20.0
  8. File system: FS_Truncate() tried to access an invalid memory location when the volume on which the specified file was located was not mounted. Introduced in the initial version.
  9. File system: FS_SetEndOfFile() tried to access an invalid memory location when the volume on which the specified file was located was not mounted. This behavior affects configurations that set FS_OS_LOCKING to 1 or 2. Introduced in the initial version.
  10. BigFAT: FS_BIGFAT_SetSize() failed to modify the file size if the new size was not a multiple of the maximum fragment file size. Fixed. Introduced in version 5.0.0
  11. BigFAT: FS_BIGFAT_GetSize() returned an incorrect value when the function was called immediately after a write operation that modified the data of that file. Fixed. Introduced in version 5.0.0
  12. BigFAT: FS_BIGFAT_Write() incorrectly reported that the operation failed if FS_BIGFAT_SetSize() was called immediately before the write operation. Fixed. Introduced in version 5.0.0
  13. FAT: FS_Format() failed to correctly format a storage device with a capacity of 128 GB or greater when the specified number of sectors per cluster was set to 1 and the logical sector size was 512 bytes large. Fixed. Introduced in the initial version.
  14. EFS: FS_Format() failed to correctly format a storage device with a capacity of 128 GB or greater when the specified number of sectors per cluster was set to 1 and the logical sector size was 512 bytes large. Fixed. Introduced in the initial version.

Version 5.24.0 [28 August 2023]

New Features

  1. Added File Disk driver.
  2. Added support for Infineon FM25V02A serial FRAM device.
  3. Added support for Fujitsu MB85RS128TY serial FRAM device.
  4. Added support for Fujitsu MB85RS256TY serial FRAM device.
  5. Added support for Adesto AT25PE16 DataFlash device.
  6. Added support for Adesto AT25XE321D serial NOR flash device.
  7. Added support for Macronix MX25UM51245G serial NOR flash device.
  8. Added support for Macronix MX66L1G45G serial NOR flash device.
  9. Added support for ISSI IS25LP064D serial NOR flash device.
  10. Added support for Winbond W25Q80DV serial NOR flash device.
  11. Added support for Micron MT29F4G01ABAFD serial NAND flash device.
  12. Added support for GigaDevice GD25Q64EYIGR serial NOR flash device.
  13. Added support for Eon EN25QX64A serial NOR flash device.
  14. Added "exportfolder" command to NAND Image Creator utility.
  15. Added "exportimage" command to NOR Image Creator utility.
  16. Added support for removing entire directory trees to NAND Image Creator utility.
  17. Added support for FS_CMD_GET_CLEAN_CNT command to LOGVOL driver.
  18. Added FS_LOGVOL_SUPPORT_TRIM configuration define.
  19. Added FS_LOGVOL_SUPPORT_CLEAN configuration define.
  20. Added FS_MMC_CM_ReadCSD() API function.
  21. Added FS_MMC_CM_ReadSectors() API function.
  22. Added FS_MMC_CM_WriteSectors() API function.

Improvements

  1. SPI MMC/SD driver: Improved the error recovery of the SD card initialization.
  2. SPIFI NOR physical layer: Improved the performance of the operation that checks if a physical sector is blank.
  3. Block Map NOR driver: Optimized the operation that checks if a physical sector does not contain valid data.
  4. Block Map NOR driver: Improved the performance by caching the value of the minimum erase count.
  5. File system: Improved the Busy LED functionality so that the LED is also driven when the driver is initialized and when a free sector operation is performed.
  6. LOGVOL driver: A storage device is now unmounted only when the last LOGVOL partition located on it is unmounted by the application.
  7. Encryption: Optimized the performance of the operation that reads multiple sectors from a file.

Program corrections

  1. Serial NOR physical layer: The physical layer failed to correctly remove the write protection of Micron serial NOR flash devices. Fixed. Introduced in the initial version.
  2. File system: FS_WipeFile() failed to correctly lock the file system with FS_OS_LOCKING set to 2. Fixed. Introduced in version 3.30f
  3. File system: FS_Truncate() failed to correctly lock the file system with FS_OS_LOCKING set to 2. Fixed. Introduced in version 4.04g
  4. SPI MMC/SD driver: FS_MMC_GetCardId() failed to initialize the storage device. Fixed. Introduced in the initial version.
  5. SPI MMC/SD driver: FS_MMC_GetCardInfo() returned the wrong card type. Fixed. Introduced in version 5.14.0
  6. Serial NOR physical layer: The physical layer failed to correctly identify the Winbond W25Q80EW serial NOR flash device. Fixed. Introduced in the initial version.
  7. LOGVOL driver: The logical driver wrote wrong data when the file system layer was performing a repeated write operation and the driver instance was configured to use use multiple storage devices. Fixed. Introduced in the initial version.
  8. LOGVOL driver: The logical driver failed to return the correct logical sector usage. Fixed. Introduced in version 4.04f
  9. SLC1 NAND driver: The driver failed to return the correct usage of a logical sector with an index greater than 32767 on a 16-bit target. Fixed. Introduced in version 5.10.0
  10. Universal NAND driver: The driver failed to return the correct usage of a logical sector with an index greater than 32767 on a 16-bit target. Fixed. Introduced in version 4.06b
  11. Block Map NOR driver: The driver failed to return the correct usage of a logical sector with an index greater than 32767 on a 16-bit target. Fixed. Introduced in version 5.6.0
  12. SLC1 NAND driver: The driver falsely reported an error on an operation that freed a logical sector with an index greater than 32767 on a 16-bit target. Fixed. Introduced in version 5.10.0
  13. Universal NAND driver: The driver falsely reported an error on an operation that freed a logical sector with an index greater than 32767 on a 16-bit target. Fixed. Introduced in version 4.06b
  14. Block Map NOR driver: The driver falsely reported an error on an operation that freed a logical sector with an index greater than 32767 on a 16-bit target. Fixed. Introduced in version 5.6.0

Version 5.22.0 [21 February 2023]

New Features

  1. Added FS_BIGFAT_GetTime() API function.
  2. Added FS_BIGFAT_SetTime() API function.
  3. Added FS_MMC_CM_ReadGeneral() API function.
  4. Added FS_MMC_CM_WriteGeneral() API function.
  5. Added FS_STORAGE_FillSectors() API function.
  6. Added FS_STORAGE_FillSectorsEx() API function.
  7. Added support for FRAM storage devices.
  8. Added support for Winbond W25N512GVEIG serial NAND flash device.
  9. Added support for ST M95P32 serial NOR flash device.
  10. Added a new version of Block Map NOR driver that works in read-only mode.
  11. Added a new version of SPIFI NOR physical layer that works in read-only mode.

Improvements

  1. CFI NOR physical layer: Added configurable byte ordering for the access to CFI parameters.
  2. Serial NOR physical layer: Improved the write protection handling of the Winbond serial NOR flash devices.
  3. Encryption: Improved the error handling of the API functions.
  4. File system: Improved the performance of the FS_GetFileInfo() API function.
  5. Serial NOR physical layer: Improved the device identification operation.

Program corrections

  1. FAT: The file system failed to correctly mount a storage device with a capacity smaller than or equal to 128 KB that was formatted with a logical sector size of 2 KB. Fixed. Introduced in the initial version.
  2. File system: Wrong CHS (Cylinder, Head, Sector) address was calculated if the number of cylinders exceeded the maximum value that is permitted to be stored in the partition entry. Fixed. Introduced in the initial version.
  3. NOR Image Creator: The createimage command did not accept a space character as parameter delimiter. Fixed. Introduced in the initial version.

Version 5.20.0 [15 November 2022]

New Features

  1. Added FS_FGets() API function.
  2. Added support for GPT partitions.
  3. Added support for GigaDevice GD5F2GQ5UE serial NAND flash device.
  4. Added support for Cypress S25FL128L serial NOR flash device.
  5. Added support for the disconnection of the SD card internal pull-up of the D3 signal.
  6. Added macOS executables for all the utilities.

Improvements

  1. Block Map NOR driver: Improved the error handling of the physical sector allocation.
  2. File system: Extended FS_GetVolumeInfoEx(), FS_GetVolumeFreeSpaceFirst() and FS_GetVolumeFreeSpaceNext() with the ability to use a work buffer provided by the application.
  3. Serial NOR physical layer: Improved the error handling of ISSI, GigaDevice and Adesto serial NOR flash devices.
  4. SPIFI NOR physical layer: Improved the error handling.

Program corrections

  1. EFS: FS_Rename() did not report an error if the file to be renamed was opened. Fixed. Introduced in the initial version.
  2. Block Map NOR driver: The driver did not correctly recover from an interrupted logical sector write operation. As a result, a read error was wrongly reported when the application tried to access that logical sector. The behavior affects only file system configurations that enable either the CRC or ECC verification and the optimization for the fast write operation (FS_NOR_OPTIMIZE_DATA_WRITE set to 1). Fixed. Introduced in version 5.16.0
  3. WinDrive driver: The driver was not able to read less than 512 bytes from the image file. Fixed. Introduced in initial version.
  4. ONFI NAND physical layer: SkyHigh NAND flash devices with internal HW ECC were not identified correctly. Fixed. Introduced in version 5.12.0
  5. NOR Image Creator: Invalid write operations were performed when an image was created using the commands "setlinesize 8" and "setrewritesupport 0". Fixed. Introduced in version 4.06b.
  6. Block Map NOR driver: The driver failed to correctly access the data stored on the NOR flash device when: (1) the support for variable line size was enabled (FS_NOR_SUPPORT_VARIABLE_LINE_SIZE set to 1), (2) the flash line size was set to 16 bytes (FS_NOR_LINE_SIZE set to 16), (3) a flash line size of eight bytes was set at runtime via FS_NOR_BM_SetDeviceLineSize(). Fixed. Introduced in version 5.6.0
  7. Universal NAND driver: Under special circumstances the bit error handling procedure performed during the low-level mount operation caused a data loss by incorrectly discarding valid data. This behavior affects only file system configurations that set FS_NAND_MAX_BIT_ERROR_CNT to a value different than 0. Fixed. Introduced in version 4.04a
  8. FAT: FS_GetVolumeName() was truncating the last character of a volume label when the volume label was 11 characters long. Fixed. Introduced in version 5.0.0
  9. Universal NAND driver: Under special circumstances a logical sector was not marked as not being in use. This behavior did not affect the integrity of the data stored on the NAND flash device. Fixed. Introduced in the initial version.
  10. NOR Image Creator: The image file was not closed at the end of the script processing. Fixed. Introduced in the initial version.
  11. File system: FS_FSeek() accidentally cleared the error flag of the file handle. Fixed. Introduced in the initial version.

Version 5.18.1 [30 August 2022]

Program corrections

  1. SPIFI NOR physical layer: A false error was reported for NOR flash devices that required the sending of mode bits during a read memory array command. Fixed. Introduced in version 5.18.0

Version 5.18.0 [26 August 2022]

New Features

  1. Added FS_NOR_SPIFI_AllowDTRMode() API function.
  2. Added FS_NOR_SPIFI_AllowOctalMode() API function.
  3. Added FS_MMC_CM_AllowCacheActivation() API function.
  4. Added support for Macronix MX25LM51245G serial NOR flash device.
  5. Added support for Alliance Memory AS5F38G04SND serial NAND flash device.
  6. Added support for Winbond W25Q512JV serial NOR flash device.
  7. Added support for DTR mode for Winbond W25Q64JV, W25Q128JV, W25Q256JW, and W25Q512JV serial NOR flash devices.
  8. Added support for Kioxia TC58BVG1S3HTA00 parallel NAND flash device.
  9. Added support for XTX XT27G02BTSIG parallel NAND flash device.

Improvements

  1. SPIFI NOR physical layer: Added support for data transfers in DTR mode.
  2. SPIFI NOR physical layer: Added support for data transfers via eight data lines.
  3. SPIFI NOR physical layer: Improved the configuration of Micron serial NOR flash devices that transfer the data via four data lines.
  4. FreeRTOS OS layer: Added support for the static allocation of synchronization objects.
  5. FreeRTOS OS layer: Added support for an OS tick different than 1 millisecond.
  6. Universal NAND driver: Improved the error recovery at low-level mount.

Program corrections

  1. SPIFI NOR physical layer: An incorrect address was used in a dual flash mode configuration with two 16 MB serial NOR flash devices. Fixed. Introduced in version 5.0.0
  2. Block Map NOR driver: An incorrect flash line size was used when writing the data of a logical sector with the support for variable flash line size enabled. Fixed. Introduced in version 4.06b.
  3. Card Mode MMC/SD driver: The check for supported SD card functions did not work correctly. Fixed. Introduced in version 5.4.0
  4. Block Map NOR driver: FS_NOR_BM_WriteOff() possibly caused an invalid memory access with support for variable flash line size enabled. Fixed. Introduced in version 5.0.0
  5. File system: FS_Format() and FS_FAT_FormatSD() did not correctly unmount the file system if the storage device was present. Fixed. Introduced in the initial version.
  6. FAT LFN: Duplicated short file names were possibly generated if the number of characters in the base name of a long file name was smaller than six. Fixed. Introduced in the initial version.
  7. SPIFI NOR physical layer: The write protection removal for the Microchip 16 and 32 Mbit serial NOR flashes devices did not work correctly. Fixed. Introduced in version 4.04a
  8. File system: FS_DeleteDir() removed opened files. Fixed. Introduced in version 4.04d
  9. SPIFI NOR physical layer: A Cypress/Spansion S25FL064L serial NOR flash device was not identified correctly. Fixed. Introduced in version 4.04a
  10. EFS: FS_CheckDisk() possibly corrupted the file system structure if directory names were present on the storage device that started with a period character. Fixed. Introduced in the initial version.
  11. File system: FS_GetNumFilesOpen() and FS_GetNumFilesOpenEx() failed to correctly lock the file system with FS_OS_LOCKING set to 2. Fixed. Introduced in version 5.0.0
  12. Storage layer: FS_STORAGE_GetCounters() and FS_STORAGE_ResetCounters() failed to lock the file system. Fixed. Introduced in the initial version.
  13. Storage layer: FS_STORAGE_FreeSectors() accessed the wrong logical sectors if the storage device was partitioned via MBR. Fixed. Introduced in version 3.32a
  14. Block Map NOR driver: The operation that invalidates a logical sector was not fail-safe with the support for ECC enabled. Fixed. Introduced in version 5.6.0
  15. File system: FS_SetEndOfFile() and FS_SetFileSize() possibly corrupted the file system if the requested file size was larger than the available free storage space. Fixed. Introduced in the initial version.

Version 5.16.2 [5 August 2022]

Improvements

  1. BigFile: Changed the name to BigFAT.

Version 5.16.1 [14 June 2022]

Program corrections

  1. Universal NAND driver: The bit error handling procedure performed during the low-level mount operation potentially caused a data loss when using a NAND flash device that was excessively worn out. This behavior applies only to file system configurations that set FS_NAND_MAX_BIT_ERROR_CNT to a value different than 0. Fixed. Introduced in version 4.04a

Version 5.16.0 [10 May 2022]

New Features

  1. Added FS_NAND_UNI_SetMaxPageSize() API function.
  2. Added FS_NAND_UNI_SetMaxSpareAreaSize() API function.
  3. Added FS_FPuts() API function.
  4. Added FS_FPrintf() API function.
  5. Added FS_NOR_ErasePhySector() API function.
  6. Added FS_NOR_WriteOff() API function.
  7. Added new Storage layer API functions.
  8. Added FS_OPTIMIZATION_LEVEL configuration define.
  9. Added support for ISSI IS25LP128F serial NOR flash device.
  10. Added support for Alliance Memory AS5F32G04SND and AS5F34G04SND serial NAND flash devices.
  11. Added statistical counter for the number of pre-erase operations performed by the Block Map NOR driver.

Improvements

  1. Block Map NOR driver: Added optimization for the sector data write operation.
  2. Universal NAND driver: FS_NAND_UNI_GetBlockInfo() and FS_NAND_UNI_GetBlockInfoEx() now return the erase count of empty NAND blocks.

Program corrections

  1. RAID5 driver: Some of the memory allocated for the driver instance was not freed during deinitialization. Fixed. Introduced in version 4.06a
  2. LOGVOL driver: A configuration that exceeded the capacity of the storage device was not reported as error. Fixed. Introduced in the initial version.
  3. File system: FS_DeleteDir() possibly corrupted the file system structure on a EFS formatted volume when the specified maximum recursion level was smaller than the maximum directory depth. Fixed. Introduced in version 4.04d

Version 5.14.0 [9 March 2022]

New Features

  1. Added FS_BIGFILE_CheckDisk() API function.
  2. Added FS_MMC_GetCardInfo() API function.
  3. Added FS_NAND_2048X8_SetDeviceList() API function.
  4. Added support for ISSI IS25LP512M serial NOR flash device.
  5. Added support for ISSI IS34ML04G081, IS34ML01G084, IS34ML04G084 and IS34ML02G084 parallel NAND flash devices.
  6. Added support for Micron MT29F8G01ADBFD serial NAND flash device.
  7. Added support for Samsung K9F1G08U0F serial NAND flash device.
  8. Added support for Winbond W25N02K and W25N04K serial NAND flash devices.
  9. Added support for Winbond W29N02GZSIBF and W29N08GVSIAA parallel NAND flash devices.
  10. Added support for Winbond W25Q16JV serial NOR flash device.
  11. Added read and write functions to NOR SPI HW layer that are able to report error conditions.
  12. Added high speed mode support for Kioxia serial NAND flash devices.
  13. Added new configuration option (FS_NOR_SUPPORT_FORMAT) that can be used to disable the low-level format operation of the Block Map NOR driver.
  14. Added OS layer for MbedOS.
  15. Added OS layer for ThreadX.

Improvements

  1. Journaling: Improved the handling of consecutive logical sector operations.
  2. FAT: The disk checking operation verifies now that all the directory entries following the last used entry are marked as not used.
  3. File system: FS_SetFileAttributes() and FS_ModifyAttributes() now ignore any attempt to modify undefined flags.
  4. File system: Improved the handling of memory allocation errors.
  5. FAT: The number of free clusters stored in the FSInfo sector is updated now on a synchronize or unmount operation with the value calculated by any API function that scans the allocation table.

Program corrections

  1. Universal NAND driver: The statistical counters ReadSpareCnt and ReadByteCnt were not correctly updated if FS_NAND_OPTIMIZE_SPARE_AREA_READ was set to 1. Fixed. Introduced in version 4.04f
  2. RAID5 driver: Burst read and write operations were not handled correctly. Fixed. Introduced in version 4.06a
  3. Journaling: The MaxWriteSectorCnt statistical counter was not correctly updated. Fixed. Introduced in version 5.2.0
  4. Journaling: The first sector in a sector range was possibly not marked as free on the storage. Fixed. Introduced in version 5.4.0
  5. Journaling: Increasing the journal file size without a file system reinitialization possibly caused a data loss. Fixed. Introduced in the initial version.

Version 5.12.0 [6 December 2021]

New Features

  1. Added support for UHC encoded Korean file names.
  2. Added support for Big5 and GBK encoded Chinese file names.
  3. Added support for SkyHigh S34ML16G2 parallel NAND flash device.
  4. Added FS_FAT_GetLFNConverter() API function.
  5. Added FS_FAT_GetConfig() API function.
  6. Added FS_EFS_GetConfig() API function.
  7. Added FS_GetAutoMountType() API function.
  8. Added FS_NOR_SPIFI_ExecCmd() API function.

Improvements

  1. NOR physical layer: Added support for status polling in the hardware for all supported serial NOR flash devices.
  2. ONFI NAND physical layer: Improved the initialization of the SkyHigh S34ML08G3 parallel NAND flash device.

Program corrections

  1. FAT: Some of the small letters from the Latin-1 Supplement Unicode block such as LATIN SMALL LETTER O WITH STROKE were not converted correctly to capital letters. Fixed. Introduced in the initial version.
  2. Journaling: FS_JOURNAL_Create() and FS_JOURNAL_CreateEx() did not check for the minimum number of logical sectors in the journal file required for the correct operation. Fixed. Introduced in the initial version.
  3. EFS: The EFS file system failed to identify two UTF-8 encoded file names as identical when: (1) the file name contained letters, (2) the only difference between the file names was the case of the letters, (3) the support for case insensitive file names was enabled and (4) the number of bytes in the UTF-8 encoding of the small and capital was different. Fixed. Introduced in the initial version.
  4. SPIFI NOR physical layer: Writing a number of odd bytes in dual flash mode did not work correctly. Fixed. Introduced in version 5.0.0
  5. File system: An attempt to move a directory to one of its subdirectories was not correctly detected. Fixed. Introduced in version 5.4.0
  6. Sector Map NOR driver: FS_NOR_ReadOff() failed to initialize the NOR flash device before the read operation. Fixed. Introduced in the initial version.
  7. File system: Moving a file opened in write mode to a different location on the same volume possibly corrupted the file system structure. Fixed. Introduced in the initial version.
  8. File system: FS_DeleteDir() possibly corrupted the file system structure on a FAT formatted volume with the support for long file names enabled. Fixed. Introduced in version 4.04f
  9. Journaling: A logical sector was not marked as not being used when a transaction overflow occurred during a file delete operation. Fixed. Introduced in version 3.34b
  10. Storage: The callback function registered via FS_STORAGE_SetOnDeviceActivityCallback() was not called when the file system performed a read burst operation. Fixed. Introduced in version 3.12a
  11. File system: FS_FreeSectors() failed to mount the file system before performing the operation. Fixed. Introduced in version 3.34a
  12. File system: FS_FreeSectors() failed to create a journal transaction before performing the operation. Fixed. Introduced in version 3.34a
  13. Journaling: FS_JOURNAL_IsEnabled() failed to mount the file system before performing the operation. Fixed. Introduced in version 5.0.0

Version 5.10.0 [27 August 2021]

New Features

  1. Added support for Micron MT29F8G01ADAFD and MT29F4G01ABBFD serial NAND flash devices.
  2. Added support for Winbond W25M02GVZEIT serial NAND flash device.
  3. Added support for GigaDevice GD5F1GQ4UFYIG serial NAND flash device.
  4. Added support for Micron MT29F2G08ABAGA and MT29F4G08ABADA parallel NAND flash devices.
  5. Added "setnumworkblocks" command to NOR Image Creator.
  6. Added FS_NAND_QSPI_SetDeviceList() API function.

Improvements

  1. File system: Debug messages reporting that a storage device is not formatted are output now as warning.
  2. Universal NAND driver: Added support for calculating the number of clean operations via FS_STORAGE_GetCleanCnt().
  3. SLC1 NAND driver: Added support for calculating the number of clean operations via FS_STORAGE_GetCleanCnt().

Program corrections

  1. File system: The unmount operation possibly closed a handle to a file that was not located on the volume that was unmounted. This behavior applies to configurations that set FS_OS_LOCKING to 2. Fixed. Introduced in version 3.34a
  2. SLC1 NAND driver: DataFlash devices with the erase unit set to one block (FS_NAND_BLOCK_TYPE set to 0) were not handled correctly. Fixed. Introduced in the initial version.
  3. Card Mode MMC/SD driver: The forced unmount operation wrongly tried to access the storage device. Fixed. Introduced in version 5.0.0
  4. DataFlash NAND physical layer: Adesto AT45DB641E DataFlash was not handled correctly with FS_NAND_BLOCK_TYPE set to 0 or 1. Fixed. Introduced in version 3.34a
  5. FAT: The file system was not properly synchronized with the support for Journaling and for updating of dirty flag enabled (FS_SUPPORT_JOURNAL and FS_FAT_UPDATE_DIRTY_FLAG both set to 1). Fixed. Introduced in the version 4.04a

Version 5.8.1 [15 June 2021]

Program corrections

  1. Universal NAND driver: The data of a logical sector which had all bytes set to 0xFF was potentially not copied internally during a block conversion leading to a data loss. This behavior applies to parallel NAND flash devices with internal HW ECC that are able correct more than 1 bit error and that do not have support for internal page copy operation. Fixed. Introduced in version 5.0.0

Version 5.8.0 [7 June 2021]

New Features

  1. Added FS_CACHE_GetType() API function.
  2. Added FS_NAND_UNI_GetBlockInfo() API function.
  3. Added FS_NAND_ONFI_SetDeviceList() API function.
  4. Added support for EON EN25QH128A serial NOR flash device.
  5. Added support for Macronix MX30LF1G28AD, MX60LF8G28AD, MX30LF4GE8AB, MX30LF4G28AD, MX30LF2G28AD, and MX30LF2GE8AB parallel NAND flash devices.
  6. Added support for Macronix MX35LF1G24AD, MX35LF2G24AD, MX35LF2GE4AD, MX35LF4G24AD, and MX35LF4GE4AD serial NAND flash devices.
  7. Added support for Kioxia TC58CYG1S3HRAIJ, TC58CYG0S3HRAIJ, TH58CYG3S0HRAIJ, TC58CYG2S0HRAIJ, TC58CVG1S3HRAIJ, TC58CVG2S0HRAIJ, TH58CVG3S0HRAIJ, and TC58CVG0S3HRAIJ serial NAND flash devices.
  8. Added support for SkyHigh S34ML04G200TFI000, S34ML04G300TFI000, S34ML04G300TFI100, S34ML08G201TFI000, and S34ML08G301TFI000 parallel NAND flash devices.
  9. Added support for GigaDevice GD9FU4G8F2A and GD9FU1G8F2A parallel NAND flash devices.
  10. Added support for GigaDevice GD25LQ128D and GD25LQ16C serial NOR flash devices.
  11. Added support for Adesto AT25XE041D and AT25XE081D serial NOR flash devices.
  12. Added support for sector-aligned file buffer read operations.
  13. Added support for application-defined serial NOR device list.
  14. Added new configuration option (FS_NAND_ENABLE_STATS_SECTOR_STATUS) that can be used to disable the collection of information about the number of valid logical sectors by the Universal NAND driver.
  15. Added new configuration option (FS_BUFFER_SIZE_FILE_WIPE) that can be used to specify the size of the work buffer used by FS_WipeFile().
  16. Added new configuration option (FS_BUFFER_SIZE_TRUNCATE) that can be used to specify the size of the work buffer used by FS_Truncate().

Improvements

  1. Universal NAND driver: Increased the performance of the mount operation when using the 1-bit ECC software algorithm for bit error correction.
  2. Universal NAND driver: Improved the detection of the factory defective blocks of SkyHigh/Cypress/Spansion parallel NAND flash devices.

Program corrections

  1. FAT: The file system was not properly unmounted with the support for Journaling and for updating of dirty flag enabled (FS_SUPPORT_JOURNAL and FS_FAT_UPDATE_DIRTY_FLAG both set to 1). Fixed. Introduced in the version 4.04a
  2. File system: FS_GetFileId() was not correctly locking the file system with FS_OS_LOCKING set to 2 when the application was requesting the id of a directory. Fixed. Introduced in version 3.32b
  3. CompactFlash/IDE driver: The driver was not deinitialized correctly. Fixed. Introduced in the initial version.
  4. GCC reported warnings about the usage of strncpy(). Fixed. Introduced in the initial version.

Version 5.6.1 [23 March 2021]

Program corrections

  1. Block Map NOR driver: An invalid write operation was performed during an internal logical sector copy operation when the available free memory was smaller than the logical sector size and not aligned to a flash line. This defect affects only configurations that set FS_NOR_CAN_REWRITE to 0. Fixed. Introduced in version 4.04d
  2. Block Map NOR driver: Incorrect data was written during an internal logical sector copy operation with the support for bit error correction and header write optimization enabled. Fixed. Introduced in version 5.6.0

Version 5.6.0 [16 February 2021]

New Features

  1. Added ECC support to Block Map NOR driver.
  2. Added support for runtime configurable OS layer.
  3. Added FS_NOR_BM_Mount() API function.
  4. Added FS_MMC_CM_SetDriverStrength() API function.
  5. Added support for Adesto AT25SL321 serial NOR flash device.
  6. Added support for Macronix MX66L2G45G serial NOR flash device.

Improvements

  1. Added ability to configure the size of the work buffers allocated by the Block Map NOR driver on the stack.
  2. Added ability to configure where the buffer for the formatting of debug messages is allocated (statically or on the stack).

Program corrections

  1. Block Map NOR driver: A false error was reported when writing data to a NOR flash device with support for incremental write operations and with the CRC verification feature enabled. Fixed. Introduced in version 5.0.0

Version 5.4.1 [19 November 2020]

Program corrections

  1. Block Map NOR driver: Uninitialized variable caused a compiler warning. Fixed. Introduced in version 5.4.0
  2. FAT: Unused variable caused a compiler warning. Fixed. Introduced in version 5.4.0

Version 5.4.0 [16 November 2020]

New Features

  1. Added support for ultra high speed access modes of SD cards and MMC devices.
  2. Added support for the two-plane operation of NAND flash devices.
  3. Added FS_NOR_SFDP_Configure() API function.
  4. Added FS_GetVolumeAlias() API function.
  5. Added support for Adesto AT25SF128A serial NOR flash device.

Improvements

  1. Block Map NOR driver: Added support for preserving the erase count of a physical sector erased during a clean operation for NOR flash devices that do not support incremental write operations.
  2. File system: Added the ability to set a constant volume alias.
  3. Journaling: Improved the write performance by removing redundant sector write operations.
  4. File system: Improved the write performance in FAST write mode by removing redundant sector read operations.

Program corrections

  1. File system: Wrong error code was return when the file system was not able to update the allocation table. Fixed. Introduced in version 4.06b
  2. File system: Moving a file to the same volume with FS_MULTI_HANDLE_SAFE set to 1 possibly created a path longer than the file system was able to handle. Fixed. Introduced in the initial version.
  3. File system: Moving a directory to one of its subdirectories corrupted the file system. Fixed. Introduced in the initial version.
  4. FAT: Partitions with a cluster size of 128 KiB were not handled correctly. Fixed. Introduced in the initial version.
  5. Journaling: The failure of a single subtransaction caused an error on all of the other subtransactions that were executed as part of the same main transaction. Fixed. Introduced in version 5.2.0
  6. NOR SPI physical layer: The file system failed to initialize a Microchip SST26VF064B NOR flash device. Fixed. Introduced in version 5.0.0
  7. NOR SPI physical layer: The busy status of ISSI IS25LP01G NOR flash was not handled correctly. Fixed. Introduced in the version 4.06b
  8. Block Map NOR driver: FS_NOR_BM_ReadOff() and FS_NOR_BM_WriteOff() accessed the wrong offset when using a NOR flash device with different physical sector sizes. Fixed. Introduced in version 4.04g
  9. WinDrive driver: The presence of a removable device was not detected correctly. Fixed. Introduced in version 5.0.0
  10. WinDrive driver: The checking for administrative rights was not working correctly. Fixed. Introduced in the initial version.
  11. WinDrive driver: The capacity of some storage devices was not calculated correctly. Fixed. Introduced in the initial version.
  12. WinDrive driver: Unaligned data buffers caused data access errors. Fixed. Introduced in the initial version.
  13. SPI MMC/SD driver: A false error was reported when trying to delete a file. Fixed. Introduced in version 5.1.0
  14. NAND SPI physical layer: Management data was written to the range of the spare area reserved for the ECC for a Micron MT29F2G01ABAGDSF NAND flash device. Fixed. Introduced in the version 4.04e
  15. File system: FS_SetFileBufferFlagsEx() returned an error even when the operation succeeded. Introduced in the version 4.04f
  16. File system: FS_Sync() failed to update the file buffer data of opened files to storage device. Fixed. Introduced in the version 4.04a
  17. File system: Wrong data was read from a file configured to use a file buffer in read mode when the data present in the file buffer was overwritten. Fixed. Introduced in the version 4.04a
  18. File system: Wrong file position was returned on 16-bit targets when the file position was larger than 65535. Fixed. Introduced in the version 5.0.0
  19. FAT LFN: The file system possibly accessed invalid memory when the application tried to access a file with a name containing extended ASCII characters with FS_SUPPORT_EXT_ASCII set to 0. Fixed. Introduced in version 5.0.0

Version 5.2.0 [26 June 2020]

New Features

  1. Added PC utility for merging and splitting of files managed by the BigFile component.
  2. Added FS_NOR_BM_SetInvalidSectorError() API function.

Improvements

  1. EFS: Reduced the RAM usage.
  2. Sector Map NOR driver: Optimized the write performance of the management data.

Program corrections

  1. File system: The file system was locked recursively with FS_DEBUG_LEVEL set to a value greater than or equal to FS_DEBUG_LEVEL_LOG_ERRORS. Fixed. Introduced in version 5.0.0
  2. NAND DataFlash physical layer: Invalid data was read from a 64 Mbit DataFlash device with FS_NAND_SUPPORT_READ_CACHE set to 0. Fixed. Introduced in the initial version.
  3. File system: An empty string was not recognized as root directory. Fixed. Introduced in version 4.06b
  4. FAT LFN: The file system was not able to open short file names that contained two or more dot characters. Fixed. Introduced in version 4.04a
  5. Block Map NOR driver: The write error recovery did not work correctly when a copy of the affected logical sector was present in the block. Fixed. Introduced in version 4.04e

Version 5.1.0 [5 May 2020]

New Features

  1. Added FS_GetMountType() API function.
  2. Added FS_GetMemInfo() API function.
  3. Added FS_NOR_SPIFI_SetSectorSize() API function.
  4. Added support for Macronix MX25V1635F.

Improvements

  1. File buffer: Added option for the alignment of the file position to sector boundary to help improve the write performance.
  2. EFS: Added support for free cluster cache to help improve the write performance.
  3. File system: Added a cache for the internal sector buffers.
  4. Journaling: Improved the error handling.

Version 5.0.1 [16 March 2020]

Program corrections

  1. File system: FS_Move() did not unlock the file system with FS_OS_LOCKING set to 1. Fixed. Introduced in the version 5.0.0
  2. NAND physical layer: The physical layer for NXP iMX6U5 tried to access invalid memory. Fixed. Introduced in version 5.0.0

Version 5.0.0 [9 March 2020]

New Features

  1. The source files are now MISRA C:2012 compliant.
  2. Added support for Shift JIS encoded Japanese file names.
  3. Added BigFile extension that enables an application to handle files larger than 4 GiB.
  4. Added support for dual flash mode to SFDP NOR physical layer.
  5. Added support for Cypress S25FL256L serial NOR flash device.
  6. Added support for Toshiba TC58CYG2S0HRAIG NAND flash device.
  7. Added "clean" and "createjournal" commands to NOR Image Creator.

Improvements

  1. File system: The strategy for the allocation of clusters was improved.
  2. EFS: The file name case sensitivity can now be configured at runtime.
  3. Shipment: The file structure was cleaned up.

Program corrections

  1. File system: The file buffer was not invalidated when the application wrote at once a number of bytes larger than the buffer size. A following read operation returned old data. Fixed. Introduced in the version 4.04g.
  2. FAT LFN: Leading space and trailing period characters were not removed from file names as required by the FAT specification. Fixed. Introduced in the initial version.
  3. File system: FS_FindFirstFile() and FS_FindNextFile() wrote past the end of the file name buffer when the short name of the file had an extension and the size of the file name buffer was equal to or smaller than the size of the file name. Fixed. Introduced in the initial version.
  4. Universal NAND driver: The driver unintentionally tried to write to a page that was not empty. This behavior affects only configurations that calculate the ECC in the NAND physical layer and by which the ECC value of a blank data block does not have all the bits set to 1. Fixed. Introduced in the initial version.
  5. Journaling: FS_JOURNAL_Invalidate() unintentionally disabled the journal operation. Fixed. Introduced in the version 4.04b.
  6. File system: The file system tried to free the memory block allocated for a file buffer twice. Fixed. Introduced in the version 4.04f.
  7. FAT: The file delete optimization did not work properly causing a data loss. Fixed. Introduced in the initial version.
  8. FAT: A file system corruption occurred with the file write mode set to FAST when the size of the file was decreased. Fixed. Introduced in the initial version.
  9. EFS: The disk checking operation incorrectly reported an error when a file name contained exactly the maximum number of characters allowed. Fixed. Introduced in the initial version.
  10. File system: The handle to an opened file was unintentionally closed when the an unmount operation was concurrently performed on a different volume than the volume on which the file was stored. The behavior affects only configurations that set FS_OS_LOCKING to 2. Introduced in the initial version.
  11. SPI NAND physical layer: Identification of Micron MT29F1G01ABAFDSF serial NAND flash failed in case of an uncorrectable bit error in the page 0 of block 0. Fixed. Introduced in the initial version.
  12. SPI NAND physical layer: An uncorrectable bit error was not propagated to the caller by the page copy operation. Fixed. Introduced in the initial version.
  13. FAT: The backup copy of the allocation table was not updated correctly with the delete optimization enabled. Fixed. Introduced in the initial version.
  14. File system: The file system tried to access invalid memory after a forced unmount. Fixed. Introduced in the initial version.
  15. Universal NAND driver: The bit error checking feature was not disabled when calling FS_NAND_UNI_SetMaxBitErrorCnt() with the BitErrorCnt parameter set to 0. Fixed. Introduced in the version 4.04a.
  16. LOGVOL driver: A driver instance was not initialized correctly after the application performed a deinitialization of the file system. Fixed. Introduced in the initial version.

Version 4.06b [7 Mai 2019]

New Features

  1. Added new versions of Universal NAND and SD / MMC driver that allow only a read access to the storage device.
  2. Added power save mode support for SD card storage devices.
  3. Added FS_InitCheck(), FS_CheckAT() and FS_CheckDir() API functions that can be used to check the integrity of the file system structure in a non-blocking way.
  4. Added support for ISSI IS25LP01G serial NOR flash device.

Improvements

  1. Increased the write performance of the Universal NAND driver.
  2. The memory copy function used internally by the file system is now configurable via the FS_MEMCPY() define.

Program corrections

  1. M25 NOR physical layer: NOR flash devices with a block size larger than 64KB were not handled correctly when the size of the physical sector was manually configured. Fixed. The behavior has been present since initial version.
  2. Block map NOR driver: The data storage functions did not return an error on attempt to access an invalid sector index. Fixed. The behavior has been present since initial version.
  3. SD / MMC driver: An incorrect number of sectors was passed to the storage device when reading large amounts of data. Fixed. The behavior has been present since version 4.04g.
  4. File system: FS_GetFileAttributes() failed to indicate that a directory did not exist when the name of directory ended with a directory delimiter. Fixed. The behavior has been present since version 4.04c.
  5. Block map NOR driver: A wrong data block was discarded when an unexpected reset interrupted a in-place work block conversion for NOR flash devices that cannot rewrite. Fixed. The behavior has been present since version 4.06a.
  6. FAT: On an almost full storage device the file system tried to access the data of an out-of-bounds logical sector when the write mode was set to medium or fast. Fixed. The behavior has been present since initial version.
  7. SFDP NOR physical layer: The configuration a specific physical sector size for ISSI IS25LP128 did not work as expected. Fixed. The behavior has been present since initial version 4.04g.
  8. Block map NOR driver: The driver attempted to modify for the second time the same flash line on NOR flash devices that cannot rewrite when writing with the CRC feature enabled. Fixed. The behavior has been present since version 4.04g.
  9. SPI NAND physical layer: Management data was stored to locations that were not protected by ECC on Micron MT29F1G01ABAFD serial NAND flash device. The compatibility to the older emFile versions can be ensured by setting the FS_NAND_SUPPORT_COMPATIBILITY_MODE to 1 or 2. Fixed. The behavior has been present since version 4.04e.
  10. FAT: Under special circumstances changing the volume label caused an invalid memory access. Fixed. The behavior has been present since initial version.
  11. EFS: Under special circumstances attempting to create a directory on a full volume corrupted the file system structure. Fixed. The behavior has been present since initial version.

Version 4.06a [11 December 2018]

New Features

  1. Added RAID5 logical driver that can be used to increase data reliability.
  2. Added support non-blocking free space checking operation via the API functions FS_GetVolumeFreeSpaceFirst() and FS_GetVolumeFreeSpaceNext().
  3. Added support to block map NOR driver for permanently switching the NOR flash device to read-only mode in case of a fatal error.
  4. Added quad and dual support for serial NAND flash devices.
  5. Added support for Micron MT29F1G08ABAFA NAND flash device to ONFI physical layer.
  6. Added support for Macronix MX25L128 NOR flash device.
  7. Added support for ISSI IS37SML01G1 and IS38SML01G1 NAND flash devices to SPI NAND physical layer.
  8. Added quad and dual support for Winbond serial NOR flash devices.

Improvements

  1. SPI NAND physical layer: Added timeout for the operation that waits for the NAND device to finish the execution of a command.
  2. Journal: Unused bytes are filled with 0xFF in order to help improve the lifetime of some NAND flash devices by reducing the number of bits set to 0.
  3. Block map NOR driver: Added support for conversion of work blocks in-place for NOR flash devices without rewrite support.
  4. NOR physical layer: Added function for blank checking of an erased physical sector and for the initialization of NOR flash device.

Program corrections

  1. ONFI NAND physical layer: The page copy operation was enabled / disabled only for the first instance of the physical layer. Fixed. The behavior has been present since version 4.04g.
  2. Card Mode MMC/SD driver: Read or write errors were not reported to the storage layer. Fixed. The behavior has been present since version 4.04g.
  3. SPI NOR physical layer: The address mode was not set correctly for Macronix devices with a capacity larger than 128 Mbit. Fixed. The behavior has been present since version 4.04f.
  4. Block map NOR driver: Redundant write retry operations were performed when a logical sector was copied negatively affecting the write performance. Fixed. The behavior has been present since version 4.04g.
  5. Block map NOR driver: Invalidating a physical sector during the low-level format operation caused a second write to a flash line on a NOR flash without rewrite support. Fixed. The behavior has been present since initial version.
  6. FAT file system: SD cards and eMMC devices with a capacity of exactly 2GB were not formatted correctly via FS_FormatSD() API function. Fixed. The behavior has been present since version 4.04f.
  7. Universal NAND driver: FS_NAND_UNI_IsBlockBad() returned an incorrect value. Fixed. The behavior has been present since version 4.04b.
  8. Card Mode MMC/SD driver: The driver did not perform the correct number of initialization retries for eMMC devices. Fixed. The behavior has been present since initial version.
  9. Universal NAND driver: The driver failed to recover the data via RAID when the affected page was located in a work block. Fixed. The behavior has been present since version 4.02a.

Version 4.04g [6 July 2018]

New Features

  1. Added POSIX support to FS_Truncate() API function.
  2. Added CRC verification for management and user data to block map NOR driver.
  3. Added support for eMMC power save mode to SD / MMC driver.
  4. Added support for eMMC data cache to SD / MMC driver.
  5. Added support for ISSI IS25LP128, Macronix MX25L3233, GigaDevice GD25Q32C and GigaDevice GD25Q64C serial NOR flash devices.

Improvements

  1. File system: Replaced the old version of the file buffer with the new faster implementation.
  2. Journal: Added optimization when deleting and writing a file in the same journal transaction.
  3. Journal: Added support for calling an application-registered callback function on journal overflow.
  4. File system: Added support to configure the vsnprintf() function used by the file system to format the debug messages.
  5. SFDP NOR physical layer: Added support for the sharing of the SPI bus via lock and unlock functions.
  6. Block map NOR driver: Improved the error handling.
  7. Sector map NOR driver: Improved the blank checking of physical sector.
  8. Universal NAND driver: Added support to configure under which conditions a NAND block is marked as defective.

Program corrections

  1. EFS: The file system failed to create a directory entry of the maximum size after the application created and then deleted two or more adjacent directory entries with a combined size larger than the maximum directory entry size. Fixed. The behavior has been present since version 4.04b.
  2. File system: SD cards and eMMC devices with a capacity larger than 2GB were not formatted correctly by the FS_FormatSD() API function. Fixed. The behavior has been present since version 4.04f.
  3. File system: The format operation via FS_FormatSD() API function did not work for storage devices with very small capacity such as RAMDISK. Fixed. The behavior has been present since initial version.
  4. LFN: The FS_FindFirstFile() and FS_FileNextFile() API functions returned the short instead of the long file name when the size of the destination buffer was one byte larger than the length of the long file name and the long file name was terminated by NUL. Fixed. The behavior has been present since initial version.
  5. DISKPART driver: Under special circumstances a false positive error was reported when the Universal NAND driver tried to recover data via the RAID1 module. Fixed. The behavior has been present since version 4.04e.
  6. SPIFI NOR physical layer: The number of bytes used as storage was not calculated correctly. Fixed. The behavior has been present since version 4.02b.
  7. SFDP NOR physical layer: The number of bytes used as storage was not calculated correctly. Fixed. The behavior has been present since version 3.34b.
  8. SPIFI NOR physical layer: Under special circumstances the NOR flash device was not released from the power down mode. Fixed. The behavior has been present since version 4.02b.
  9. File buffer: The file buffer was not updated correctly when the file was truncated. Fixed. The behavior has been present since version 4.04a.
  10. 2048x8 NAND physical layer: Under special circumstances wrong ECC correction status was returned. Fixed. The behavior has been present since 4.04a.

Version 4.04f [19 Feb 2018]

New Features

  1. Added support for deleting entire FAT directory trees via FS_DeleteDir().
  2. Added FS_SetFileBufferFlagsEx() function that can be used to configure the file buffer flags for files opened on a specific volume.
  3. Added support for the allocation of EFS directory entry buffers from the memory pool of file system.
  4. Added FS_NOR_BM_WriteOff() and FS_NOR_BM_ErasePhySector() functions to allow an application to write to and to erase physical sectors directly.
  5. Added support for hardware polling to SPIFI NOR physical layer.

Improvements

  1. 2048x8 NAND physical layer: Added support for hardware copy page operation.
  2. Universal NAND driver: Optimized the operations that read data from the spare area.
  3. Card Mode MMC/SD driver: Added support for efficiently writing the same sector data multiple times.
  4. File system: Replaced all calls to strcpy() by calls to strncpy() to comply to coding standards.
  5. FAT LFN: Optimized the performance of file delete operation.
  6. SPIFI NOR physical layer: Added support for dual and quad write operations.
  7. NOR SFDP and SPIFI physical layers: Added support GigaDevice GD25Q256 and GD25Q127C NOR flash devices.

Program corrections

  1. File system: The fast file buffer caused a memory leak when a global file buffer has been configured. Fixed. The behavior has been present since version 4.04a.
  2. Universal NAND driver: Wrong ECC block size was passed to physical layer. Fixed. The behavior has been present since version 4.04d.
  3. Sector write buffer: Multiple write operations were not handled correctly. Fixed. The behavior has been present since initial version.
  4. Universal NAND driver: Under special circumstances the data in the spare are buffer was overwritten when the data was recovered via RAID1 add-on. Fixed. The behavior has been present since version 4.02a.
  5. EFS: Under special circumstances FS_DeleteDir() falsely reported that the maximum recursion level has been reached. Fixed. The behavior has been present since version 4.04d.
  6. NOR sector map driver: False positive error message was reported when a logical sector has been invalidated by an emFile version older than 4.04d. Fixed. The behavior has been present since version 4.04e.
  7. Universal NAND driver: Under special circumstances an incorrect data CRC was stored after an error recovery via the RAID1 add-on. Fixed. The behavior has been present since version 4.04e.
  8. Universal NAND driver: Incorrect number of work blocks was reported when the number of configured work blocks was different than the number of work blocks used at low-level format. Fixed. The behavior has been present since initial version.
  9. FAT LFN: Invalid characters were allowed in a file name. Fixed. The behavior has been present since initial version.

Version 4.04e [20 Oct 2017]

New Features

  1. Added FS_MMC_CM_SetSectorRange() API function that can be used to configure which sectors of the SD card have to be used as storage.
  2. Added new configuration option that lets the application specify if the file system has to report the end-of-file condition as error or not.

Improvements

  1. Universal NAND driver: Added optional CRC verification of data.
  2. NAND physical layer: Added support for manual configuration of the NAND flash device parameters.
  3. NOR SFDP and SPIFI physical layer: Added support for the following Macronix serial NOR flash devices: MX25R64, MX25L256, and MX25L512.
  4. NOR M25 physical layer: Added support for the Micron N25Q512A serial NOR flash device.
  5. SPI NAND physical layer: Added support for the following serial NAND flash devices: Micron MT29F1G01ABAF, Micron MT29F2G01ABAGD, and Macronix MX35LF1GE4AB.

Program corrections

  1. NAND SPI physical layer: Using a software ECC instead of the internal HW ECC of the serial NAND flash caused uncorrectable bit errors. Fixed. The behavior has been present since initial version.
  2. NOR sector map driver: Data written using a version of the file system older than 4.04d was not recognized as valid. Fixed. The behavior has been present since version 4.04d.
  3. NOR block map driver: Under special circumstances a work block was not converted correctly to a data block possibly leading to a data loss. Fixed. The behavior has been present since version 4.04d.
  4. Universal NAND driver: FS_NAND_UNI_ReadPageRaw() read and incorrect number of bytes from data area. Fixed. The behavior has been present since version 4.04d.
  5. Universal NAND driver: FS_NAND_UNI_WritePageRaw() wrote and incorrect number of bytes to data area. Fixed. The behavior has been present since version 4.04d.
  6. Universal NAND driver: FS_NAND_UNI_WritePage() wrote incorrect data to spare area. Fixed. The behavior has been present since version 4.04b.
  7. Universal NAND driver: An incorrect number of NAND blocks was calculated when the first block in the partition was marked as defective. Fixed. The behavior has been present since version 3.34a.
  8. Storage layer: The API functions FS_STORAGE_SyncSectors() and FS_STORAGE_FreeSectors() did not lock the file system when FS_OS_LOCKING was set to 2. Fixed. The behavior has been present since version 4.00a.
  9. Storage layer: FS_STORAGE_RefreshSectors() and FS_STORAGE_GetSectorUsage() locked the file system recursively. Fixed. The behavior has been present since version 4.00a.
  10. File system: Data was written at a wrong position after the same file was opened in read mode with a file write mode configured to fast or medium and with support for multiple file handles enabled. Fixed. The behavior has been present since initial version.
  11. DISKPART driver: The request for corrected sector data was not handled correctly. Fixed. The behavior has been present since initial version.
  12. File system: FS_CheckDisk() failed to correct errors when the auto-mount mode was set to read-only. Fixed. The behavior has been present since version 4.04b.
  13. 2048x8 NAND physical layer: Data stored to the cache of NAND flash device was used after being invalidated by a NAND reset operation. Fixed. The behavior has been present since version 4.04a.

Version 4.04d [16 Jun 2017]

New Features

  1. Added FS_DeleteDir() API function that can be used to delete entire directory trees.
  2. Added FS_NAND_UNI_SetBlockReserve() API function that can be used to configure the number of blocks reserved by the Universal NAND driver as replacement for the blocks that become defective.

Improvements

  1. NOR block map driver: Improved the performance of write, "free sector" and low-level format operations.
  2. Universal NAND driver: Improved the performance of low-level mount operation.
  3. NOR sector map: Improved the procedure of detecting if the storage has been low-level formatted with the fail-safe erase option enabled.
  4. NOR CFI physical layer: Improved error handling and added support for Cypress HyperFlash.
  5. ST M25 NOR physical layer: Added support for configuring new NOR flash devices.
  6. SPI NOR physical layer: Added support for ISSI IS25LP064A device.
  7. MMC card mode driver: Added workaround for ATP 512 MB microSD cards that report an error when the last sector on the storage is read via a multiple block read command.

Program corrections

  1. File system: FS_GetFileAttributes() and FS_ModifyFileAttributes() did not return an error when the volume was not mounted properly. Fixed. The behavior has been present since initial version.
  2. EFS: The index of a directory entry overflowed when a large number of files were created in a directory causing an endless loop when scanning the files via FS_FindFirstFile()/FS_FindNextFile(). Fixed. The behavior has been present since initial version.
  3. NOR sector map: Physical sectors marked as invalid were not used for data storage. Fixed. The behavior has been present since version 3.34b.
  4. SPI NOR physical layer: The timeout for the program and erase operations was not calculated correctly. Fixed. The behavior has been present since version 4.04c.
  5. File system: Wrong number of bytes was returned when reading more bytes than available with file buffer. Fixed. The behavior has been present since version 4.04a.
  6. File system: EOF error was not reported when the application tried to read beyond the end of file. Fixed. The behavior has been present since initial version.

Version 4.04c [16 Mar 2017]

New Features

  1. Added support for SPI bus locking to SPI NAND physical layer.
  2. Added support for partial sector read operation to Universal NAND driver.
  3. Added FS_GetFileInfo() API function that returns information about a file or directory.
  4. Added FS_NOR_SPI_ReadDeviceId() function that can be used to read the device id of a serial NOR flash device.
  5. Added FS_MMC_CM_AllowBufferedWrite() function that can be used to enable / disable the buffering of data written to storage device.

Improvements

  1. Universal NAND driver: If possible, the "free sector" operation marks entire NAND blocks as invalid to increase performance.
  2. Universal NAND driver: Added statistical counters for the number of bit errors corrected.
  3. Universal NAND driver: Added support for software multi-bit error correction.
  4. EFS file system: Improved the performance of the operations that check for free space on the storage.

Program corrections

  1. NOR block map driver: Wrong range of sectors was detected for NOR flash devices with bottom boot sectors. Fixed. The behavior has been present since initial version.
  2. File system: An error was returned when the application queried the attributes of the root directory. Fixed. The behavior has been present since initial version.
  3. File system: FS_GetFileAttributes() did not return when the application queried the attributes of the root directory of a FAT volume with support for long file names enabled. Fixed. The behavior has been present since initial version.
  4. NOR drivers: Under rare circumstances a write operation interrupted by an unexpected reset caused a data loss when using a serial NOR flash as storage device. Fixed. The behavior has been present since initial version.
  5. File system: Wrong number of bytes was returned when reading more bytes than available in the file with the file buffer enabled. Fixed. The behavior has been present since version 4.04a.
  6. File system: FS_FTell() returned the wrong value in case of an error. Fixed. The behavior has been present since version 3.34a.
  7. SPI NOR physical layer: Serial NOR flash devices with a physical sector size larger than 64 KByte were not handled correctly on 8- and 16-bit targets. Fixed. The behavior has been present since version 3.34a.

Version 4.04b [17 Nov 2016]

New Features

  1. Added support for fast write operation to SLC1 NAND driver.
  2. Added new function to Journaling which can be used to cancel pending transactions.
  3. Added new test functions to NAND drivers.
  4. Added support for partitions to NAND Image Creator.

Improvements

  1. NAND drivers: In case of a fatal error the NAND flash is no longer mark as read-only by default. The application has to request this via the fatal error callback.
  2. NOR SPI physical layer: Added support for Winbond SPI NOR flash devices.
  3. NOR SPI physical layer: Added support for Spansion SPI NOR flash devices with a capacity larger than 128 Mbit.
  4. NOR drivers: Added support for runtime configuration of the erase and write verification feature.
  5. NOR drivers: Added support for runtime configuration of the "skip blank sector" feature.
  6. NOR sector map driver: Improved the error handling.
  7. NAND ONFI physical layer: Added support for multiple planes, page copy operation and ECC result query.
  8. File system: Improved the performance of the "free sector" operation.
  9. EFS file system: Improved the error handling and reduced the stack usage.
  10. SLC1 NAND driver: Improved the performance of the "free sector" operation.

Program corrections

  1. SPI NOR physical layer: Wrong physical sector size was detected for some Spansion SPI NOR flash devices. Fixed. The behavior has been present since version 4.04a.
  2. SPI NOR physical layer: Wrong number of dummy cycles was used for the read operation on some Spansion SPI NOR flash devices. Fixed. The behavior has been present since version 4.04a.
  3. SPI NOR physical layer: Switching to 4-byte addresses did not work for some Micron SPI NOR flash devices. Fixed. The behavior has been present since version 4.04a.
  4. NOR drivers: The timeout for the write and erase operations was not calculated correctly. Fixed. The behavior has been present since version 4.04a.
  5. NOR block map driver: Under rare circumstances a data loss occurred after a power fail when a logical sector containing valid data was marked as invalid. Fixed. The behavior has been present since initial version.
  6. NOR sector map driver: An incompletely erased physical sector was not marked as invalid. Fixed. The behavior has been present since version 3.34b.
  7. File system: The file pointer was not positioned correctly when calling FS_FSeek() with the file buffer enabled. Fixed. The behavior has been present since version 4.04a.
  8. NAND SPI physical layer: Data was not stored correctly on NAND flash devices which support only one plane. Fixed. The behavior has been present since initial version.
  9. File system: The deinitialization operation failed when an external memory manager was used. Fixed. The behavior has been present since version 4.04a.
  10. File system: The performance of file copy operation using FS_CopyFileEx() decreased when the specified work buffer was not a multiple of logical sector size. Fixed. The behavior has been present since version 3.26b.
  11. Universal NAND driver: Under special circumstances a work block was not loaded correctly at low-level mount causing an error. Fixed. The behavior has been present since version 4.00a.

Version 4.04a [21 Jun 2016]

New Features

  1. Added support for recognizing if a volume was properly unmounted before reset.
  2. Added support for profiling via SEGGER SystemView.
  3. Added FS_X_OS_Delay() to the OS layer.
  4. Added faster file buffer implementation.

Improvements

  1. NOR SPI physical layer: The type of serial NOR devices supported is now configurable via FS_NOR_SetDeviceList() and FS_NOR_SPIFI_SetDeviceList() respectively.
  2. Universal NAND driver: The driver relocates NAND flash blocks based on the number of bit errors corrected in order to prevent data loss.
  3. File system: All standard C library functions used by the file system can be overwritten at compile time.
  4. 2048x8 NAND physical layer: Added support for Toshiba TC58NVG0S3HTA00 devices.
  5. ONFI NAND physical layer: Added support for Toshiba TC58CVG1S3HxAIx devices.
  6. NOR drivers: The drivers invalidate the erase signature only if it is valid. This prevents write errors on physical sectors which were not properly erased.
  7. FAT file system: Improved the performance of directory creation operation. A multiple write operation is used instead of writing one sector at a time.
  8. SPI NAND physical layer: Added support for Winbond W25N01GVxxIG/IT devices.

Program corrections

  1. EFS file system: An error was reported when moving empty directories. Fixed. The behavior has been present since initial version.
  2. EFS file system: The directory entry was not updated when closing the file if an EOF error was encountered by a previous read operation. Fixed. The behavior has been present since initial version.
  3. FAT file system: The check disk operation reported a false invalid directory entry error on the next directory entry following an invalid long file name. Fixed. The behavior has been present since initial version.
  4. FAT LFN: Wrong long file name entries were created when the file name contained 2 or more dot characters. Fixed. The behavior has been present since initial version.
  5. File system: External memory allocation/deallocation functions were not deinitialized properly. Fixed. The behavior has been present since initial version.
  6. File system: FS_CreateDir() did not use Journal to protect the operation against power failure. Fixed. The behavior has been present since initial version.
  7. SLC1 NAND driver: The driver reported the wrong number of available logical sectors after the second initialization. Fixed. The behavior has been present since version 3.24e.
  8. Block map NOR driver: Under special circumstances the block map NOR driver invalidated a data block at low-level mount which could have caused a data loss. Fixed. The behavior has been present since version 3.26a.
  9. File system: FS_CheckDisk() did not return an error when it failed to fix file system errors. Fixed. Present since initial version.
  10. EFS file system: A read operation failed to release the used sector buffer in case of an error. Fixed. Present since initial version.
  11. EFS file system: No error was reported when the file delete operation failed. Fixed. Present since initial version.
  12. File system: FS_ModifyFileAttributes() failed to report an error when the volume was mounted as read only. Fixed. Present since version 3.32c.
  13. File system: FS_RmDir() failed to report an error when the volume was mounted as read only. Fixed. Present since initial version.
  14. Card Mode MMC/SD driver: FS_MMC_CM_GetCardId() caused a buffer overflow. Fixed. Present since version 3.30g.

Version 4.02b [10 Feb 2016]

New Features

  1. Added support for memory-mapped SPI NOR flash devices.
  2. Added support for trim and reliable write operations for MMC storage devices.

Improvements

  1. FAT: Directory entries belonging to the same long file name are marked as deleted using the minimum number of sector write operations possible.

Version 4.02a [3 Dec 2015]

New Features

  1. Added RAID1 logical driver which can be used to increase the data reliability. This is achieved by mirroring the sector data on a different volume.
  2. Added FS_MMC_CM_ReadExtCSD() and FS_MMC_CM_WriteExtCSD() functions. They can be used access the EXT_CSD internal register of MMC/eMMC devices.

Improvements

  1. Card Mode MMC/SD driver: Added more debug and log messages and improved the error handling.
  2. SLC1 NAND driver: Improved data reliability by adding the possibility to relocate blocks in which 1 bit error occurred. DataFlash physical layer: Added workaround for devices which sometimes return invalid data when reading via RAM buffer. By default the data is now read directly from the memory array.
  3. SPI MMC/SD driver: Added workaround for ATP 512 MB microSD cards which report an error when the last sector on the storage is read via a multiple block read command.

Program corrections

  1. SLC1 NAND driver: Under special conditions a block containing valid data was marked as being free at low-level mount possibly causing a data loss. Fixed. The behavior has been present since version 3.24e.
  2. LOGVOL driver: The deinitialization operation did not free the memory of all device drivers causing a memory leak. Fixed. The behavior has been present since initial version.
  3. Storage layer: FS_STORAGE_FreeSectors() locked the file system recursively. Fixed. The behavior has been present since version 3.32a.
  4. Storage layer: FS_STORAGE_SyncSectors() locked the file system recursively. Fixed. The behavior has been present since version 3.34b.
  5. FAT file system: The number of free clusters was not correctly set for FAT32 partitions at high-level format. Fixed. The behavior has been present since initial version.
  6. SPI MMC/SD driver: The capacity of SD cards larger than 2 GB was not calculated correctly. Fixed. The behavior has been present since initial version.

Version 4.00b [26 Aug 2015]

New Features

  1. Added FS_MMC_CM_GetCardInfo() function. The function can be used to get information about the storage card.
  2. Added FS_STORAGE_GetSectorUsage() function that returns information about whether a sector contains valid data or not.

Improvements

  1. NAND 4096x8 physical layer: Added support for Hynix H27UAG8T2A series NAND flash devices.
  2. Universal NAND driver: The active wear leveling process checks now also the erase count of work blocks when searching for the NAND block with the lowest erase count.

Program corrections

  1. SPI MMC/SD driver: The driver caused and invalid memory access after the re-initialization of the file system. Fixed. The behavior has been present since version 4.00a.
  2. NAND physical layer: The FS_NAND_PHY_ReadONFIPara() and FS_NAND_PHY_ReadDeviceId() functions were using the hardware layer routines from the version V3.34b of emFile. Fixed. The behavior has been present since version V4.00a.
  3. File system: The FS_GetVolumeInfo(), FS_GetVolumeInfoEx() and FS_CheckDisk() functions were not properly locking the file system against concurrent access when FS_OS_LOCKING was set to 2. Fixed. The behavior has been present since version V3.32c.
  4. File system: The FS_Remove() function was not properly locking the file system system against concurrent access when FS_OS_LOCKING was set to 2. Fixed. The behavior has been present since initial version.

Version 4.00a [19 Jun 2015]

New Features

  1. Replaced hard-coded function names of the hardware layer API with function tables. An update of the emFile configuration is required. For more information refer to section "Porting emFile 3.x to 4.x" of the emFile manual.
  2. Added support for grouping physical block to Universal NAND driver. It saves RAM space when using a NAND flash with a large number of physical blocks. Block grouping can be configured via FS_NAND_UNI_SetNumBlocksPerGroup() function.
  3. Added support for fast write operations to Universal NAND driver. The application can reserve buffer space and the write without performing a copy/erase operation. The buffer space can be reserved via the functions FS_NAND_UNI_Clean() and FS_NAND_UNI_SetCleanThreshold().
  4. Added the possibility to configure whether read-only files/directories stored on a FAT partition can be moved or renamed. This feature is can be configured via the FS_FAT_ConfigROFileMovePermission() function.

Improvements

  1. File system: The directory entry is updated now on file close only when necessary.
  2. Journal: The journal will cancel automatically a transaction in case of an error.
  3. SPI MMC/SD driver: Added support for the locking of the SPI bus.
  4. Card Mode MMC/SD driver: The sequence for switching into 4-bit mode of an SD/MMC card has been improved. In case of a failure the driver falls back to 1-bit mode.
  5. NAND drivers: The write performance of the NAND drivers has been improved. A write operation that triggers the allocation of a new work block is performed during the block copy operation.
  6. NAND DataFlash physical layer: Three different block sizes can be configured for a DataFlash via FS_NAND_BLOCK_TYPE define as: 1 x DataFlash block, 8 x DataFlash block and 1 x DataFlash sector.
  7. NOR drivers: A blank physical sector will not be erased at low-level format the define FS_NOR_SKIP_BLANK_SECTORS set to 1.
  8. NAND DataFlash physical layer: A virtual page can be configured for the DataFlash physical layer. This allows Universal NAND driver to support DataFlash devices. The virtual page can be set via the FS_NAND_DF_SetMinPageSize() function.

Program corrections

  1. FAT file system: FS_FAT_CheckDisk() reported an error when checking a volume immediately after a high-level format. Fixed. The behavior has been present since version 3.34b.
  2. FAT file system: An integer overflow occurred when FS_FAT_CheckDisk() tried to compute the number of clusters allocated to a file with the size of 0xFFFFFFFF bytes. Fixed. The behavior has been present since initial version.
  3. EFS file system: Under special circumstances FS_EFS_CheckDisk() failed to repair damaged EFS partition and did not return. Fixed. The behavior has been present since initial version.
  4. File system: On some cases FS_FOpenEx() returned the wrong error code. Fixed. The behavior has been present since version 3.34a.
  5. FAT file system: An invalid root directory was created by the format operation when support for free sector was enabled (FS_SUPPORT_FREE_SECTOR == 1). Fixed. The behavior has been present since version 3.24g.
  6. FAT file system: FS_FormatSD() was not locked against concurrent access when FS_OS_LOCKING was set to 2. Fixed. The behavior has been present since initial version
  7. FAT LFN: Duplicated short names were generated when two or more long file/directory names were created on the same subdirectory containing a dot as the first character in the name. Fixed. The behavior has been present since initial version.
  8. File system: The contents of the file was corrupted when the application tried to write beyond 4 GB file size limit. Fixed. The behavior has been present since initial version.
  9. Journal: The support for free sectors was always enabled when creating the journal even when the application required for it to be disabled. Fixed. The behavior has been present since version 3.34b.
  10. File system: Calling FS_GetVolumeStatus() when the storage medium was not preset caused a following mount operation to fail. Fixed. The behavior has been present since initial version.
  11. File system: FS_Sync() locked the file system recursively when FS_OS_LOCKING was set to 2. Fixed. The behavior has been present since initial version.
  12. Card Mode MMC/SD driver: The bus test procedure for MultiMedia cards did not work properly. Fixed. The behavior has been present since version 3.28a.

Version 3.34b [7 Jan 2015]

New Features

  1. Added new logical driver which helps increase the data reliability by maintaining a copy of each sector data.
  2. New logical driver available which implements a write buffer for sector data.
  3. New physical layer available which supports JEDEC JESD216B compliant SPI NOR flash devices and data transfers via 1, 2 or 4 data lines.
  4. Added FS_JOURNAL_CreateEx() API function. The function can used to create a journal which informs the storage driver about unused sectors.
  5. Added support for SPI NOR flash devices with a capacity greater than 128Mbit.
  6. Added FS_MMC_CM_Erase() API function. It can be used to erase MMC cards.

Improvements

  1. File system: Improved the performance of the disk checking operation.
  2. SPI NAND physical layer: Improved the read and write performance.
  3. Storage layer: Improved the sector refresh operation. Only the sectors which contain valid data will be refreshed.

Program corrections

  1. File system: Some API functions did not return the correct error code when the volume was not mounted and the auto-mount feature was disabled. Fixed. The behavior has been present since version V3.34a

Version 3.34a [4 Jun 2014]

New Features

  1. Added FS_FOpenEx() API function. It opens a file and returns an error code if the operation fails.
  2. Added new logical driver which supports the access to a storage medium using a sector size different than that of the storage driver.
  3. Added FS_SetFileSize() API function. It can be used increase the size of the file without moving the file pointer.
  4. Added FS_FreeSectors() API function. It can be used to inform the storage layer about unused sectors.
  5. Added support for 64Mbit DataFlash devices with a page size of 256 bytes.

Improvements

  1. Universal NAND driver: Improved the write verification functionality.
  2. Universal NAND driver: Reduced the low-level mount time for the NAND flashes which support HW ECC.
  3. FAT LFN: A single short directory entry is created if the file name complies with the 8.3 format.
  4. File system API: Added meaningful return codes to several API functions.
  5. SPI MMC/SD driver: Some SD cards did not respond correctly to a CMD12 (STOP_TRANSMISSION) command. Added retries to work around this.
  6. NAND 4096x8 physical layer: Added support for Samsung NAND flash devices with 128 pages per block.

Program corrections

  1. SPI MMC/SD driver: SD cards with a capacity greater than 2GB were not identified correctly on 16-bit systems. Fixed. The behavior has been present since initial version.
  2. NAND ONFI physical layer: The read functions did not return any data in case of an ECC error. In a NAND dump the pages appeared as containing all zeros. Fixed. The behavior has been present since version V3.24g.
  3. NAND DataFlash physical layer: Devices with a page size of 256 bytes were not handled correctly. Fixed. The behavior has been present since version V3.24g.
  4. CRYPT driver: When reading several sectors at once invalid data was returned in the first byte of the first sector read. Fixed. The behavior has been present since version V3.30b.
  5. File system: FS_ModifyFileAttributes() did not use the journal when writing data to storage. Fixed. The behavior has been present since version V3.32c.
  6. File system: The time stamp of volume label was not correctly set. Fixed. The behavior has been present since initial version.
  7. Storage layer: Internal API functions called from the MSD component of emUSB were not locked against concurrent access when the locking level of the file system was set to coarse. Fixed. The behavior has been present since initial version.

Version 3.32c [30 Jan 2014]

New Features

  1. Added FS_GetVolumeInfoEx() API function. It can be used to get information about how the storage medium is formatted.
  2. Added FS_STORAGE_GetCleanCnt() function. An application can call it to get the number of clean operations which must be performed before all the invalid data is erased.
  3. Added FS_ModifyFileAttributes() API function which can be used to set and clear file attributes with a single function call.
  4. Added support for NOR flash devices connected via SPIFI.

Improvements

  1. NOR block map driver: Added support for getting the number of clean operation required before all the invalid data on the storage medium is erased.
  2. SPI MMC/SD driver: Improved the identification mechanism of SD cards which responded incorrectly to SEND_IF_COND initialization command.
  3. Disk checking: Replaced numeric literal return values with symbolic constants to improve readability.
  4. Universal NAND driver: Added initialization with 0's of unused sectors in a data block in order to reduce the chance of bit errors.

Program corrections

  1. Card Mode MMC/SD driver: Functions of the HW layer were called before the HW layer initialization. Fixed. The behavior has been present since version V3.20a.
  2. NAND ONFI physical layer: The physical layer failed to allocate an internal memory buffer when only the storage layer was used and no file system was configured. Fixed. The behavior has been present since version V3.24e.
  3. NOR sector map driver: The clean operation tried to erase a physical sector which was already blank. Fixed. The behavior has been present since version V3.26i.
  4. File system: The unmount operation tried to call functions of the file system layer even when no file system was configured causing linking errors. Fixed. The behavior has been present since initial version.
  5. File system: The volume searching function returned a valid volume pointer even when the volume was not correctly initialized. Fixed. The behavior has been present since initial version.
  6. File buffer: The file buffer flags were not initialized to default values when opening a file. Fixed. The behavior has been present since version V3.22a.
  7. FAT with LFN: Under special circumstances an invalid memory access occurred when checking the validity of a file name with support for UTF-8 enabled. Fixed. The behavior has been present since initial version.

Version 3.32b [24 Jul 2013]

Improvements

  1. NOR block map driver: Improved the handling of clean operations triggered via FS_STORAGE_Clean()/FS_STORAGE_CleanOne() API calls. Physical sectors containing invalid data are erased in order to increase the write performance.
  2. File system: Added 2 new return codes to FS_CheckDisk(). Code 3 is returned when the maximum recursion level has been reached. A negative value is returned in case of a file system error.

Program corrections

  1. Encryption: Files larger than a cluster size which were stored on non-consecutive clusters were incorrectly encrypted. Fixed. The behavior has been present since version V3.30b.
  2. Atmel SD/MMC driver: The capacity of 2GB SD cards was not computed correctly. Fixed. The behavior has been present initial version.

Version 3.32a [22 May 2013]

New Features

  1. New physical layer available for NAND flash devices with SPI interface.
  2. New logical driver available which reads sectors in advance and caches them. This logical driver can be used together with an SD/MMC driver to improve the performance of searching for free clusters in the allocation table.
  3. Added file buffer support to EFS. The file buffer improves the read and write performance when accessing small amounts of data.
  4. Added FS_STORAGE_FreeSectors() API function which can be used by a file system to help the NAND or NOR driver to manage the data more efficiently.

Improvements

  1. File system: Added a check at mount time to test if the number of sectors available on the storage medium has shrunk.

Program corrections

  1. File buffer: The contents of file was corrupted when seeking to end of file with the file buffer enabled. Fixed. The behavior has been present since version V3.22a.
  2. File buffer: The contents of file buffer was discarded when opening the same file for the second time with FS_MULTI_HANDLE_SAFE enabled. Fixed. The behavior has been present since version V3.22a.
  3. NAND physical layer: Wrong data was read by the FS_NAND_PHY_512x8 physical layer from NAND512-A devices which support sequential row read. Fixed. The behavior has been present since initial version.

Version 3.30l [22 Mar 2013]

Program corrections

  1. Encryption: File contents was corrupted when writing with enabled file buffering. Fixed. The behavior has been present since version V3.30b.
  2. Encryption: File contents was corrupted when truncating a file. Fixed. The behavior has been present since version V3.30b.
  3. File system: Unused variables caused compiler warnings. Fixed.

Version 3.30k [5 Mar 2013]

Program corrections

  1. Encryption: File contents was corrupted when writing close to the end of file. Fixed. The behavior has been present since version V3.30b.
  2. FAT: A 0xFFFFFFFF value in a FAT32 entry was interpreted as read error. Fixed. The behavior has been present since version V3.10e.

Version 3.30j [18 Feb 2013]

Program corrections

  1. Journaling: The mount operation used the wrong journal unit number when more than one volume was configured. Fixed. The behavior has been present since version V3.30i.

Version 3.30i [11 Feb 2013]

New Features

  1. Added FS_JOURNAL_Enable() and FS_JOURNAL_Disable() API functions. An application can use these functions to explicitly activate or deactivate the journal.

Improvements

  1. File system: Normalized the format of the error and warning debug messages. A new line is not emitted at the end of these messages anymore.
  2. Journaling: Optimized the write performance of journal when the application explicitly controls a transaction by calling the FS_JOURNAL_Begin()/FS_JOURNAL_End() functions.
  3. SLC1 NAND driver: Added support for verification of a sector write.

Program corrections

  1. EFS: A format operation accidentally deleted the information about the partitioning of storage medium. Fixed. The behavior has been present since version V3.10e.
  2. Journaling: The command sent by the file system to NAND or NOR driver to mark a sector as not used was not handled properly. The sectors could have been erased before the end of transaction which could have caused the corruption of file data. Fixed. The behavior has been present since version V3.30g.

Version 3.30h [14 Dec 2012]

New Features

  1. Added FS_NAND_2048x8_EnableReadCache() and FS_NAND_2048x8_DisableReadCache() API functions which can be used to enable/disable the page read optimization of the FS_NAND_PHY_2048x8 physical layer.

Version 3.30g [19 Nov 2012]

New Features

  1. Added FS_MMC_CM_GetCardId() API function. It can be used to read the serial number and other identification information from an SD card.

Program corrections

  1. File system: FS_Truncate() reduced the size of a file with more bytes than requested leaving the file system in an inconsistent state. Fixed. The behavior has been present since version 3.28a.

Version 3.30f [8 Nov 2012]

New Features

  1. Added FS_WipeFile() API function which can be used to overwrite the contents of a file. Typically used before removing a file which contains sensitive data.

Program corrections

  1. NOR CFI physical layer: Data was written to a wrong address on NOR devices with write buffer and which have been configured with an address gap. Fixed. The behavior has been present since version 3.30d.

Version 3.30e [30 Oct 2012]

Improvements

  1. SPI NOR physical layer: Added support for the identification of 256MBit NOR flash devices.

Program corrections

  1. Journaling: FS_CheckDisk() reported an error after the creation of journal file. Fixed. The behavior has been present since version 3.30c.
  2. NOR block map driver: The physical layer was not de-initialized properly. Fixed. The behavior has been present since version 3.26a.

Version 3.30d [19 Oct 2012]

New Features

  1. Added FS_NOR_CFI_SetAddrGap() API function which can be used to configure a gap in the address space of a CFI NOR flash.

Program corrections

  1. File system: The number of free clusters reported on FAT32 volumes was 1 less than the actual number. Fixed. The behavior has been present since version 3.30a.
  2. File system: FS_Mount() reported an incorrect value when the mount operation failed. Fixed. The behavior has been present since initial version.
  3. File system: The file buffer stopped working properly after several file open/close cycles. Fixed. The behavior has been present since version 3.30a.
  4. Journaling: The module was not de-initialized properly. Fixed. The behavior has been present since version V3.10e.

Version 3.30c [5 Oct 2012]

New Features

  1. Encryption and Journaling add-ons are included now in the trial version.
  2. Added FS_SetFileWriteModeEx() API function which can be used to configure the write mode for each volume separately.
  3. Added FS_CreateMBR() and FS_GetPartitionInfo() API functions for the management of Master Boot Record.

Program corrections

  1. File system: The modification time stamp of a file was updated even when the file data was not modified. Fixed.

Version 3.30b [6 Sep 2012]

New Features

  1. New add-on available for encryption/decryption of individual files. DES and AES encryption algorithms are supported.

Improvements

  1. SPI NOR physical layer: Improved the medium initialization sequence to support the use of HW layers which work in interrupt mode.
  2. Universal NAND driver: Added support for NAND flashes with a spare area larger than 1/32 of the main area of the page.

Program corrections

  1. Universal NAND driver: Low-level mount failed when correctable bit errors were detected in the first empty page of a work block. Fixed.
  2. FAT: The size of the allocation table was not calculated correctly at high-level format leading to errors when the file system tried to access the last 2 clusters. Fixed.

Version 3.30a [3 Aug 2012]

New Features

  1. New logical driver available which provides AES encryption for file system data. 128-bit and 256-bit key lengths are supported.

Program corrections

  1. Universal NAND driver: Wrong duplicated data block was discarded at low-level mount causing a data loss. Fixed.
  2. File system: An newly allocated file buffer was not correctly initialized. Fixed.

Version 3.28d [16 Jul 2012]

New Features

  1. Increased the number of files which can be opened at once in the trial version from 1 to 2.

Improvements

  1. Universal NAND driver: Changed the low-level format procedure to allow the erasing of the blocks marked as defect by the driver.
  2. SLC1 NAND driver: Improved the handling of bad blocks. The first byte in the spare area of the second page in a block is checked now for a bad block marker.
  3. SPI NOR physical layer: Improved the initialization sequence to remove the write protection of storage blocks only if present.

Program corrections

  1. Universal NAND driver: The status of a block (good/bad) was read with ECC enabled which caused ECC errors. Fixed.

Version 3.28c [4 Jul 2012]

Improvements

  1. SLC1 NAND driver: Changed the low-level format procedure to allow the erasing of the blocks marked as defect by the driver.

Program corrections

  1. File system cache: When reading multiple sectors invalid data was stored to cache. Fixed.
  2. NOR sector map driver: Instance pointer was not invalidated at de-initialization causing a data corruption. Fixed.

Version 3.28b [20 Jun 2012]

Program corrections

  1. File system: Uninitialized variables caused compiler warnings. Fixed.

Version 3.28a [17 Jun 2012]

New Features

  1. New logical driver available which allows emFile to mount any partition defined in a Master Boot Record.
  2. New cache module with configurable associativity level available. It offers better performance for the same cache capacity.
  3. Added to new API function FS_CACHE_SetAssocLevel(). It can be used to configure the associativity level of a multi-way set cache.
  4. Added to new API function FS_CACHE_GetNumSectors(). It returns the number of sectors which can be stored to cache.
  5. Added FS_SIZEOF_CACHE_... defines to help an application to allocate a cache buffer large enough to store a specified number of sectors.
  6. Added new API function FS_STORAGE_RefreshSectors(). The function rewrites one or more sectors with original data. Typically called to extend data life.
  7. Added new API function FS_FFlush(). An application can use it to update the buffered data of an opened file to storage medium .

Improvements

  1. NOR block map driver: Added compile-time configurable number of reserved bytes to reduce the NOR flash resource usage.
  2. FAT: Improved the validity check of the FSInfoSector. During a write operation, Windows sets a specific flag in a reserved byte of the boot sector. If this flag is found set, the information of the FSInfoSector is considered invalid.
  3. File system: Made FS_MAINTAIN_FAT_COPY option run-time configurable. The FS_FAT_ConfigMaintainFATCopy() function must be called to enable/disable this feature.
  4. File system: Made FS_FAT_USE_FSINFO_SECTOR option run-time configurable. The FS_FAT_ConfigUseFSInfoSector() function must be called to enable/disable this feature.
  5. File system: Added a warning message for the case when an application tries to call FS_Init() more than one time without calling FS_DeInit() in between.
  6. NAND physical layer: Improved the read performance of the NAND_PHY_2048x8 physical layer. When possible, data is read from the NAND flash internal buffer. No data is fetched from the memory array in this case.
  7. Card Mode MMC/SD driver: Added support for eMMC devices operating at 2.8V.
  8. LOGVOL driver: Improved the support for removable storage mediums. The correct media status is reported and the storage capacity is updated when a new storage storage medium is inserted.

Program corrections

  1. File system: When truncating a file to 0 the first cluster field of the directory entry was not set to 0 leaving the file system into an inconsistent state. Fixed.
  2. File system: When passed an unknown volume name the format functions always performed the operation on the first volume. Fixed.
  3. File system: Missing default value for FS_OS_LOCKING define caused compiler warnings. Fixed.
  4. Journaling: The de-initialization of journaling module caused an invalid memory access. Fixed.
  5. NOR physical layer: The NOR_PHY_ST_M25 physical layer did not wait for the write to status sector (write protection removal) to finish causing the following operations to fail. Fixed.
  6. LOGVOL driver: The logical driver tried to access the storage medium before the initialization of device drivers. Fixed.

Version 3.26k [19 Apr 2012]

Program corrections

  1. Universal NAND driver: Low-level format failed when ECC errors were detected by the HW ECC. Fixed.

Version 3.26j [12 Apr 2012]

Improvements

  1. NOR block map driver: Added compile-time configurable number of reserved bytes to reduce the NOR flash resource usage.

Program corrections

  1. File system: FS_SetMaxSectorSize() did not accept a sector size smaller than 512 bytes. Fixed.

Version 3.26i [22 Mar 2012]

New Features

  1. Added two new API functions FS_STORAGE_Clean() and FS_STORAGE_CleanOne(). The functions can be called to perform garbage collection on a NOR or NAND flash.

Improvements

  1. NOR block map driver: Added compile-time configurable rewrite mode to support internal flashes which are not able to rewrite same data when 0s are maintained.
  2. NOR block map driver: Added compile-time configurable flash line size to support internal flashes which require aligned writes.
  3. NOR sector map driver: Added support for garbage collection. An application can call the FS_STORAGE_Clean() and FS_STORAGE_CleanAll() API functions to create writable logical sectors.
  4. NOR SPI physical layer: Added the ability to remove the write protection of flash blocks.

Program corrections

  1. File system: FS_Sync() returned 0 on an invalid/missing volume. Fixed.
  2. SPI MMC/SD driver: SD cards with a capacity larger than 4GB were formatted incorrectly on 16-bit systems due to an integer overflow. Fixed.

Version 3.26h [22 Feb 2012]

New Features

  1. Made the number of LOGVOL instances compile-time configurable.
  2. Made the usage of large blocks for an Atmel DataFlash compile-time configurable.

Improvements

  1. LFN: Added the ability to interpret the case of short name entries created by Windows. The base or the extension part of a file name is converted to lower case when the corresponding flags in the reserved field of directory entry are set.
  2. SPI MMC/SD driver: Implemented a workaround for the SD cards which report invalid values for the access time parameters. In such a case, the driver uses fixed timeout values for read and write accesses.
  3. Card Mode MMC/SD driver: Improved the error handling. A data read/write operation is started only if the SD card responds without error to data transfer command.

Version 3.26g [10 Feb 2012]

Program corrections

  1. Journaling: On a storage medium formatted with MBR the start sector of partition was not considered when calculating the position of the Journal.dat file. Filling up the free space on the disk could have caused the corruption of the file system. Fixed.

Version 3.26f [30 Jan 2012]

Program corrections

  1. File system: memcmp() was called instead of generic FS_MEMCMP() macro. This lead to errors when compiling with FS_NO_CLIB set to 1. Fixed.

Version 3.26e [9 Jan 2012]

Program corrections

  1. SLC1 NAND driver: A bit error in the ECC protecting the sector data was copied to destination sector without being corrected. In special circumstances this could lead to several blocks being marked as bad by the driver. Fixed.
  2. SLC1 NAND driver: Driver API functions did not return an error when an invalid sector was accessed. Fixed.

Version 3.26d [5 Dec 2011]

New Features

  1. Added new API function FS_NAND_PHY_GetONFIPara(). It reads the ONFI parameters from an ONFI compatible NAND flash.

Improvements

  1. Card Mode MMC/SD driver: Increased the number of initialization retries to allow the communication with some types of micro SD cards.
  2. NOR sector map driver: Added more statistics counters.

Program corrections

  1. Block map NOR driver: During the processing of a trim command a sector containing data was marked (by accident) as invalid. Fixed.
  2. FAT: Trying to format a medium which was not large enough caused a memory fault. Fixed.

Version 3.26c [11 Nov 2011]

Program corrections

  1. EFS: An empty source file caused FS_CopyFile()/FS_CopyFileEx() to allocate all the free space on the medium. Fixed.

Version 3.26b [7 Nov 2011]

New Features

  1. Added new API function FS_CopyFileEx() which allows an application to provide its own temporary buffer.

Improvements

  1. EFS: Improved the write speed when using journaling. Data appended to a file is written directly to medium.
  2. FAT: Improved the error handling when searching the allocation table.

Program corrections

  1. Storage driver: Status of driver was queried before the driver initialization. Fixed.
  2. NAND/NOR drivers: Internal counters were not correctly reset. Fixed.
  3. NAND driver: FS_NAND_ReadDeviceId() did not initialize the NAND flash. Fixed.

Version 3.26a [5 Oct 2011]

New Features

  1. New NAND driver available which supports SLC and MLC NAND flashes.
  2. New NOR driver available which requires very few RAM.

Improvements

  1. NAND driver: Improved the speed of active wear leveling. The driver checks now only the allocated blocks.
  2. ONFI physical layer: Added functions to enable/disable the NAND flash internal ECC engine.
  3. File system: Improved the computation speed of the CRC16 routine.
  4. SPI MMC/SD driver: Improved the read/write speed.

Program corrections

  1. IDE driver: Write Feature command did not work properly. Fixed.

Version 3.24g [29 Jul 2011]

Improvements

  1. NAND driver: In case of a fatal error the application has now the possibility to decide whether the medium should be marked as read-only or not.

Program corrections

  1. NAND driver: Minimum erase count was not updated when converting a work block into a data block. Fixed.
  2. NAND driver: Missing pointer casts caused errors when compiling with a C++ compiler. Fixed.
  3. NAND driver: Missing ONFI support caused linking errors when using the object code version of emFile. Fixed.

Version 3.24f [22 Jul 2011]

Improvements

  1. NAND driver: Removed the checking for the number of work blocks. The driver will always use the number of work blocks read from device.

Program corrections

  1. NAND driver: Low-level format caused an array overflow when the number of work blocks configured was greater than the number of work blocks read from device. Fixed.

Version 3.24e [5 Jul 2011]

New Features

  1. Added new API function FS_NAND_SetNumWorkBlocks(). It configures at runtime the number of work blocks the NAND driver uses.
  2. Added new API functions FS_Lock(), FS_Unlock(), FS_LockVolume(), FS_UnlockVolume(). These functions allow a task to get exclusive access to file system or a specified volume.
  3. Added ONFI physical layer for the NAND driver.

Improvements

  1. NAND driver: Added support for file system TRIM operation.
  2. NOR driver: Improving the write speed. The sectors are marked as erasable only when required.

Program corrections

  1. FAT: FAT_Format() failed when the number of sectors was less than 256. Fixed.
  2. FAT: Invalid error code returned when reading a FAT entry. Fixed.
  3. File system: Incorrect number of bytes written returned by FS_Write() on journal overflow. Fixed.
  4. DataFlash NAND physical layer: Wrong read command was used for a 64Mbit DataFlash connected over SPI. Fixed.
  5. DataFlash physical layer: Decision where to store the spare are on a 64Mbit device was wrong. Fixed.
  6. File system: FS_BITFIELD_CalcSize() caused an integer overflow on 16-bit targets. Fixed.
  7. Serial NOR physical layer: Initialization caused an integer overflow on 16-bit targets. Fixed.

Version 3.24d [21 Mar 2011]

Improvements

  1. NAND driver: Improved the write speed by optimizing the copy of a block. The ECC of the copied sector is computed only once.

Program corrections

  1. Atmel SD/MMC driver: Driver blocked when the second unit was unmounted. Fixed.
  2. NAND driver: Mount procedure failed to delete a duplicated data block. Fixed.

Version 3.24c [28 Feb 2011]

Program corrections

  1. File system: Compile error generated when FS_SUPPORT_DEINIT == 1 and FS_USE_FILE_BUFFER == 0. Fixed.
  2. Journaling: Race condition occurred when FS_OS_LOCKING == 2. Fixed.
  3. FAT: Buffer was not deallocated when FS_Format() failed. Fixed.

Version 3.24b [10 Feb 2011]

New Features

  1. Added new API function FS_NAND_SetOnFatalErrorCB(). It registers callback function which is invoked when the NAND driver encounters a fatal error.

Improvements

  1. NAND driver: Optimized the write speed and added read retries to improve the recovery from bit errors.
  2. Journaling: Improved the write speed.
  3. Atmel MMC driver: Added support for the second MCI controller.

Program corrections

  1. NAND driver: False error message at deinitialization about an invalid unit number. Fixed.
  2. NOR driver: False error message at deinitialization about an invalid unit number. Fixed.
  3. File system: File buffers were not properly freed at deinitialization. Fixed.
  4. Atmel SD/MMC driver: Data was corrupted when reading a large number of sectors at once. Fixed.

Version 3.24a [8 Dec 2010]

New Features

  1. Added support for eMMC, MMCplus, MMCmobile cards (v4.x standard).
  2. Added new API function FS_NAND_SetMaxEraseCntDiff() which allows the user to control the wear leveling.
  3. Added new API function FS_AddOnExitHandler() which gives the user the opportunity to perform additional tasks at deinitialization.
  4. Added new API function FS_NOR_SetSectorSize() which allows configuration of sector size of NOR driver.

Improvements

  1. NAND driver: Improved the wear leveling and the handling of device errors.
  2. MMC Atmel driver: Improved the data transfer and the handling of events.

Program corrections

  1. NAND driver: At deinitialization the resources were not properly freed. Fixed.
  2. embOS integration: Resources were not properly freed at deinitialization. Fixed.
  3. FAT with LFN: File names were not properly checked for invalid characters. Fixed.
  4. Journaling: Deinitialization of caused a memory fault. Fixed.

Version 3.22c [18 Oct 2010]

Improvements

  1. NAND_PHY_2048x8.c: Improved the readability.

Program corrections

  1. FS_SetEndOfFile(): Allocated one cluster more on EFS when the size of the file was a multiple of cluster size. Fixed.
  2. File buffering: When writing to a file using buffering, emFile accidentally caused a buffer overflow. Fixed.
  3. FS_AssigCache(): This function caused a deadlock on an OS which didn't support multiple locking from the same task. Fixed.
  4. FS_GetFileAttributes(): This function returned 0 instead of 0xff when the volume was not found. Fixed.

Version 3.22a [12 Jul 2010]

New Features

  1. Added new API function FS_ConfigFileBufferDefault() which allows the user to use file buffers to increase read/write performance when reading/writing files in small chunks.
  2. Added new API function FS_ConfigFileBufferFlags() which allows configurations of the file buffer flags on a per-file basis.
  3. Added new API function FS_SetFileWriteMode() which allows to choose between different file write modes.

Improvements

  1. FS_Remove(): File could be deleted even if they were opened / in use.

Program corrections

  1. SPI MMC/SD driver: some SD cards do not work properly in high speed mode.

Version 3.20i [21 Jun 2010]

Program corrections

  1. FAT_SetEndOfFile.c: When truncating a file, emFile accidentally truncated one cluster too much. Fixed
  2. Atmel SPI MMC/SD driver: After a complete read operation, the driver did not send a STOP command to the SD card. Fixed
  3. DataFlash physical layer: 64 MBit / 128 MBit devices were not identified / auto-configured correctly.

Version 3.20h [20 Apr 2010]

Improvements

  1. Data Flash: Added support for 128MBit data flash. A warning is shown, when data flash is in "power of 2 mode".
  2. Ramdisk: Added FS_HUGE macro to the RAMDISK pointer in order to have a hint for 16-bit compilers.
  3. WinDrive: Added support for Windows Vista and Windows 7.

Program corrections

  1. NAND driver: When converting a work block into a data block the internal index of the sectors was not written which causes data misinterpretation after a power failure. Fixed
  2. SPI MMC/SD driver: Data CRC was not calculated correctly. Fixed
  3. NOR flash driver: On 16-bit processors the calculation of internal data caused data overflows. Fixed
  4. General API: Internal data were set before checking for NULL-pointer. Fixed

Version 3.20g [21 Jan 2010]

Improvements

  1. Long file name support: Reduced the amount of time taken to generate short file names.

Version 3.20f [23 Nov 2009]

Program corrections

  1. NAND driver: Under some circumstances, especially if most of the NAND flash was full, a work block was marked as free accidentally. Fixed

Version 3.20e [6 Nov 2009]

Program corrections

  1. FS_USE_FILE_BUFFER: When setting this macro to 1, compile errors could occur. Fixed.

Version 3.20d [28 Oct 2009]

Program corrections

  1. FS_STORAGE_ReadSectors/FS_STORAGE_WriteSectors: When the volume was mounted, used and unmounted and the volume is then accessed by the STORAGE functions, a partition offset when reading/writing in burst-mode was not reset which could be lead in wrong sector data. Fixed.

Version 3.20c [12 Oct 2009]

Program corrections

  1. FS_Unmount: When unmounting a volume the IDE/CF and Card Mode MMC/SD driver did not handle this correctly. Fixed.

Version 3.20b [14 Sep 2009]

Program corrections

  1. FS_Rename/FS_Move: When renaming or moving a file or directory and an invalid file name was specified the file name was not checked for valid file name characters. Fixed.
  2. FS_FOpen: When opening a file on a write-protected medium a valid file handle was returned instead of return a NULL handle. Fixed.
  3. FS_Unmount: When unmounting a volume the driver was not signaled to unmount the volume. Fixed.

Version 3.20a [17 Aug 2009]

New Features

  1. New Configuration function FS_NOR_SPI_Configure() to setup a SPI NOR flash manually.
  2. Added new function FS_Sync() to synchronize/flushes all memory/cached data to medium.
  3. MMC/SD driver (both card mode and SPI) support high speed mode of SD cards.

Improvements

  1. NOR flashes: Reduced the RAM usage of the NOR driver.

Program corrections

  1. NAND driver: Under some circumstance the wrong block was assigned to read. Fixed.

Version 3.14a [15 Dec 2008]

New Features

  1. Added new physical layer for NAND flashes (very large page NAND flashes).

Improvements

  1. NAND flashes: Reduced the RAM usage of the NAND driver.
  2. NOR CFI flashes. Added support for write buffer functionality for better write performance.
  3. NOR CFI flashes. Added support for automatically unlock sectors.
  4. NOR CFI flashes. Added new macro to use call a delay/sleep function during sector operation.

Program corrections

  1. NAND driver: During a low-level-mount invalid work blocks were added to the work block list which lead to use wrong work blocks. Fixed.
  2. NAND driver: Blocks that were not used by the NAND driver have not been added to the free block list, which lead the NAND driver to overwrite the block 0 of the NAND flash and cause the NAND driver to corrupt the low-level-information. Fixed.

Version 3.12j [6 Nov 2008]

Program corrections

  1. FS_CopyFile: When the destination file during a file copy could not be created the file object of the destination file was not freed. Fixed.
  2. Journaling: When FS_SUPPORT_JOURNAL and FS_SUPPORT_DEINIT is enabled the function FS__JOURNAL_DeInit was not found during linking. Fixed.
  3. EFS: FS_FOpen could create a file although the file name already exists. Fixed.

Version 3.12i [6 Aug 2008]

Program corrections

  1. FAT LFN: With LFN enabled a wrong file handle or wrong directory could returned/opened. Fixed.

Version 3.12h [4 Aug 2008]

Program corrections

  1. FAT LFN file handles: A false file handle could be returned with LFN support. Fixed.

Version 3.12g [22 Jun 2008]

Program corrections

  1. Low-level mount robustness: A volume corrupted on power failure or by sector copying. Fixed.
  2. FS_X_OS_Lock() called before FS_X_OS_Init(): With OS locking level 2 (FS_OS_LOCKING 2) FS_X_OS_Lock() was called before FS_OS_Init(). Fixed.

Version 3.12f [10 Jun 2008]

Improvements

  1. FS_Unmount(). FS_Unmount sets the state of a volume to uninitialized even if the volume is not mounted.

Program corrections

  1. Caches: When insufficient memory was assigned to the cache, the function could fail. Fixed.
  2. CacheRWQuota: When the FS_CACHE_SetMode and FS_CACHE_SetQuota was called after selecting the FS_CACHE_RWQUOTA cache all cached sector were wrongly invalided. Fixed.
  3. Alignment: When calling FS_GetFileAttributes with unaligned 32bit variable could cause on some CPU system a memory fault. Fixed.
  4. FAT: The character "&" was identified as an invalid char when using it for a short name entry leading to fail the file/directory operation. Fixed
  5. LFN/UTF8: When copying a Unicode string the alignment of the buffer was not checked which could cause on some CPU system a memory fault. Fixed.
  6. LFN: When generating a short name entry for a long file name, an internal variable was incremented twice which lead to abort the short name generation in half of the time.
  7. OS locking When FS_OS_LOCKING is set 2, FS_X_OS_Lock() and FS_X_OS_Unlock() was called before FS_X_OS_Init() was called. Fixed. FS_DeInit: When using more than one volume, FS_DeInit will fail before of referencing a invalid pointer. Fixed.

Version 3.12e [30 Jun 2008]

Program corrections

  1. Caches: When reading data in burst mode (multiple sectors read) and any FS' cache is enabled, the system crashed. Fixed.
  2. Memory allocation: When memory for an additional file handle/object or an additional volume object is allocated, the pointer was not checked if valid. Fixed.

Version 3.12d [19 Jun 2008]

New Features

  1. Added new function: FS_CACHE_Invalidate.
  2. Added new functions for checking and performing low-level-format in FS_X_AddDevices: FS_NOR_IsLLFormatted(), FS_NOR_FormatLow(), FS_NAND_IsLLFormatted and FS_NAND_FormatLow.
  3. Added new function for setting the NOR flash driver sector size: FS_NOR_SetSectorSize().

Improvements

  1. Cache modules check for alignment.
  2. Improved debug logging and error handling.

Program corrections

  1. FS_Move, FAT: Moving a file could fail, the wrong file name was passed. Fixed.

Version 3.12c [10 Jun 2008]

Program corrections

  1. MMC Card mode driver: When checking the card type, MMC and MMC plus card may not recognized correctly. Fixed.

Version 3.12b [3 Jun 2008]

Program corrections

  1. FAT LFN & UTF8 : When a unaligned pointer to a UTF8 string was given, the conversion to an Unicode string might fail. Fixed.

Version 3.12a [24 Apr 2008]

New Features

  1. New add-on available: Independent FS-Journaling.
  2. New run-time configurable functions available: FS_WriteUpdateDir - Configures whether the directory entry shall be updated after user data has been written. FS_MMC_CM_Allow4bitMode - Configures the Card Mode MMC/SD driver to allow 4-bit mode data transfer.
  3. Added FS_SetOnDeviceActivityHook which allows to log which sectors are read/written by file system.

Improvements

  1. EFS: Improved read/write performance.
  2. File handles/volume objects are rather allocated than predefined by compile time switch.
  3. Allow to use an external memory manager if required.

Program corrections

  1. FS_SetVolumeLabel: Setting a volume label always failed. Fixed.

Version 3.10j [22 Apr 2008]

Improvements

  1. Removed any compiler warning that may be reported by a 16-bit compiler.

Version 3.10i [14 Apr 2008]

Improvements

  1. Improved support for newer SD cards that conforms with SD card specification V2.00.
  2. Improved support for newer MMCplus cards.

Version 3.10h [7 Jan 2008]

New Features

  1. FAT disk checking operation supports orphaned long file name entries.

Version 3.10g [14 Dec 2007]

Program corrections

  1. FS_Rename(FAT): When renaming a file or directory with a long file name, the long file name entry was not removed. Fixed.
  2. LFN (FAT): When looking for a file/directory, the operation could fail, due of not handling orphaned long directory entries correctly. Fixed.
  3. FS_Rename(FAT): Renaming a file or directory could fail when using absolute file paths. Fixed.

Version 3.10f [4 Dec 2007]

Program corrections

  1. FS_Rename/FS_Move (FAT): When moving/renaming a file or directory other directory entries could be affected. Fixed.
  2. Unmount/Remount: When unmounting and remounting a volume using FS_Mount() could fail. Fixed.

Version 3.10e [2 Nov 2007]

Program corrections

  1. NAND driver: An wrong identifier was used to mark a bad block which could result in using the bad block later when searching for a new block. Fixed.

Version 3.10d [25 Oct 2007]

Program corrections

  1. FAT CheckDisk: FS_CheckDisk() removed short directory entries if directory entry name was shorter than 8+3 characters. Fixed.
  2. FS_GetTotalSpace, FS_GetFreeSpace(): In opposite to the manual FS_GetTotalSpace(), FS_GetFreeSpace() expected an additional parameter DevIndex, which was not used. Fixed.

Version 3.10c [16 Oct 2007]

Program corrections

  1. RamDisk, WinDrive: Driver were not included. Fixed.
  2. Compile time switches Enabling the switches FS_VERIFY_WRITE or FS_SUPPORT_CHECK_MEMORY could cause that the compilation failed. Fixed.

Version 3.10b [5 Oct 2007]

Program corrections

  1. MMC_SPI: Some comments did not end correctly. Fixed.

Version 3.10a [24 Sep 2007]

New Features

  1. SD HC cards are supported.
  2. The max sector size is run-time configurable.
  3. Atmel DATAFLASH is supported by NAND driver.
  4. New function added: FS_UnmountForced().

Improvements

  1. Improved SD card mode handling.

Program corrections

  1. FAT: FS_Rename(), FS_Move could move a file/directory although the file/directory has read-only attributes. Fixed.
  2. When setting a volume label after formatting the volume and creating a file/directory with the same file, file/directory operation could fail. Fixed.
  3. MMC: MMC card initialization in SPI mode could fail, if there is no pull-up on MISO line. The MMC driver did not wait accordingly to the spec. Fixed.

Version 3.08b [6 Jul 2007]

Improvements

  1. Additional functions which allow using the storage layer stand alone (without file system) added.
  2. FS_Init() and FS_InitStorage() can now be called multiple times, simplifying the use of the storage layer without file system. Typically applications are usage of the storage layer with a USB mass storage device.

Version 3.08a [4 Jul 2007]

New Features

  1. New function to initialize the storage layer (aka LBL) only added.
  2. New configuration function for IDE/CF driver added.

Improvements

  1. NAND flash driver: Multiple work blocks supported, improving write speed.

Version 3.06b [6 Jun 2007]

Program corrections

  1. NAND: The NAND driver could report an ECC error although no data has ever been written to this sector. Fixed.

Version 3.06a [5 Jun 2007]

Program corrections

  1. FAT: When LFN support is enabled, files/directories with short file names could not be opened. Fixed.

Version 3.04c [18 May 2007]

Program corrections

  1. FS_X_GetTimeDate(): In the configuration samples date and time were stored in wrong order, this could cause wrong time and date values in directory entries. Fixed.
  2. When FS_MULTI_HANDLE_SAFE is set to 1 and a file object is no longer used, the FS__FreeFileObj did not remove the string that is used to identify the file object. Fixed.

Version 3.04b [10 May 2007]

Program corrections

  1. FAT: The wrong date and time were written when creating a file. Fixed.

Version 3.04a [10 May 2007]

New features

  1. Major conceptional changes from version 2.xx. Improved flexibility and ease of use. Configuration simplified. For details, refer to the manual.
  2. Hardware and configuration samples to sample directory added.
  3. User provided functions for time and date FS_X_GetTime(), FS_X_GetDate() have been replaced by single function FS_X_GetTimeDate().

Improvements

  1. IDE, Card Mode MMC/SD driver improvements.
  2. NAND flash driver: Use a large (2048 bytes) page with sector sizes of 512 bytes.
  3. NOR flash driver: Fail safety improved.

Program corrections

  1. The physical NAND driver for 8bit small NAND flashes, generic 8bit NAND flashes and 16bit large page NAND flash have not been adapted to the new driver structure. Fixed.
  2. NAND: The driver could allocate memory for its instance information twice. Fixed.
  3. NAND: Data for the first sector in a block could be corrupted under some circumstances (other sectors of the same block already written, but the first block not) when powered down. Fixed.
  4. EFS: When no more cluster were available for data store the EFS writing routine did not return and could cause data corruption on the medium. Fixed.