FATFS: FAT File System TZEN=1 and secure context TZEN=1 and secure context TZEN=0 Not in use. RTOS in use (on L5) RTOS not in use. In use on L5 Not in use. In use on L5 Not in use. In use on L5 Not in use. When enabled, generate code based on sd_diskio_dma_rtos_template.* files. Please ensure that the DMA controller to be used is properly configured. Note: DMA choice forced to enabled to ensure sync and notification mechanism under FreeRTOS control. When enabled, generate code based on sd_diskio_dma_template.* files (recommended choice). Please ensure that the DMA controller to be used is properly configured. When disabled, generate code based on sd_diskio_template.* files Generate code based on usbh_diskio_dma_template.* files. Generate code based on usbh_diskio_template.* files. - The default option is User to generate user_diskio.* files. - On the other hand, the SD choice provides the generation of sd_diskio.* files (to be completed by user). TO DO - The default option is Generic to generate sram_diskio.* files using generic bsp files (generated by CubeMx). - On the other hand, the Custom choice provides the generation of sram_diskio.* files using BSP files from the board (to be added to the project by the user). The BSP code has to be added to the project according to the board (ST or custom) in use. TO DO Nothing generated by CubeMx: the BSP code has to be added to the project according to the board (ST or custom) in use. If not equals to None, will include the right header file in the generated sd_diskio.h. If not equals to None, will include the right header file in the generated sd_diskio.h. If not equals to None, will include the right header file in the generated sd_diskio.h. If not equals to None, will include the right header file in the generated sd_diskio.h. If not equals to None, will include the right header file in the generated sd_diskio.h. If not equals to None, will include the right header file in the generated sd_diskio.h. No board available, as no custom configuration on-going/possible on that series Setting FS_READONLY to 1 defines read only configuration. This removes writing functions: f_write, f_sync, f_unlink, f_mkdir, f_chmod, f_rename, f_truncate and useless f_getfree. Dependency: FS_READONLY = 1 (Enabled) possible as FS_LOCK = 0. Setting FS_READONLY to 1 defines read only configuration. This removes writing functions: f_write, f_sync, f_unlink, f_mkdir, f_chmod, f_rename, f_truncate and useless f_getfree. Dependency: FS_READONLY = 1 (Enabled) not possible: it requires FS_LOCK = 0. The FS_MINIMIZE option defines minimization level to remove some functions. 0: All basic functions are enabled. 1: f_stat(), f_getfree(), f_unlink(), f_mkdir(), f_truncate() and f_rename() functions are removed. 2: f_opendir(), f_readdir() and f_closedir() are removed in addition to 1. 3: f_lseek() function is removed in addition to 2. The FS_MINIMIZE option defines minimization level to remove some functions. 0: All basic functions are enabled. 1: f_stat(), f_getfree(), f_unlink(), f_mkdir(), f_chmod(), f_utime(), f_truncate() and f_rename() functions are removed. 2: f_opendir(), f_readdir() and f_closedir() are removed in addition to 1. 3: f_lseek() function is removed in addition to 2. To enable string functions (f_gets, f_putc, f_puts, ...), set USE_STRFUNC to 1 or 2. When set to 2, makes a LF -> CRLF conversion. This option switches filtered directory read feature and related functions, f_findfirst() and f_findnext(). (0:Disable or 1:Enable). To enable f_mkfs function, set USE_MKFS to 1 (Enabled) and set FS_READONLY to 0 (Disabled) To enable f_forward function, set USE_FORWARD to 1 (Enabled) and set FS_TINY to 1 (Enabled). To enable volume label functions, set USE_LABEL to 1 (Enabled). To enable fast seek feature, set USE_FASTSEEK to 1 (Enabled). Removed in R0.12c */ This option is available only for usbh diskio interface (see the usbh_diskio.c file) and allows to disable the management of the unaligned buffer. When STM32 USB OTG HS or FS IP is used with internal DMA enabled, this define is set to 0 (Disabled) to align data into 32bits through an internal scratch buffer before being processed by the DMA. Otherwise (DMA not used), this define is set to 1 (Enabled) to avoid Data alignment and improve the performance. Please note that if _USE_BUFF_WO_ALIGNMENT is set to 1 and an unaligned 32bits buffer is forwarded to the FatFs Write/Read functions, an error will be returned. (0: default value or 1: unaligned buffer return an error). */ This option is available only for usbh diskio interface (see the usbh_diskio.c file) and allows to disable the management of the unaligned buffer. When STM32 USB OTG HS or FS IP is used with internal DMA enabled, this define is set to 0 (Disabled) to align data into 32bits through an internal scratch buffer before being processed by the DMA. Otherwise (DMA not used), this define is set to 1 (Enabled) to avoid Data alignment and improve the performance. Please note that if _USE_BUFF_WO_ALIGNMENT is set to 1 and an unaligned 32bits buffer is forwarded to the FatFs Write/Read functions, an error will be returned. (0: default value or 1: unaligned buffer return an error). */ This option is not available for the current mcu. */ The CODE_PAGE specifies the OEM code page to be used on the target system. Incorrect setting of the code page can cause a file open failure. The CODE_PAGE specifies the OEM code page to be used on the target system. Incorrect setting of the code page can cause a file open failure. Dependency: CODE_PAGE = 1 (ASCII only) possible as USE_LFN = 0 (Disabled). The CODE_PAGE specifies the OEM code page to be used on the target system. Incorrect setting of the code page can cause a file open failure. Dependency: CODE_PAGE = 1 (ASCII only) possible as USE_LFN = 0 (Disabled). The CODE_PAGE specifies the OEM code page to be used on the target system. Incorrect setting of the code page can cause a file open failure. Dependency: CODE_PAGE = 1 (ASCII only) possible as USE_LFN = 0 (Disabled). The CODE_PAGE specifies the OEM code page to be used on the target system. Incorrect setting of the code page can cause a file open failure. Dependency: CODE_PAGE = 1 (ASCII only) not possible: it requires USE_LFN = 0 (Disabled). The USE_LFN option switches the LFN feature. - 0: Disable LFN feature. MAX_LFN has no effect. - 1: Enable LFN with static working buffer on the BSS. Always NOT reentrant. - 2: Enable LFN with dynamic working buffer on the STACK. - 3: Enable LFN with dynamic working buffer on the HEAP. To enable LFN feature, Unicode handling functions ff_convert() and ff_wtoupper() function must be added to the project. The LFN working buffer occupies (MAX_LFN + 1) * 2 bytes. When use stack for the working buffer, take care on stack overflow. When use heap memory for the working buffer, memory management functions, ff_memalloc() and ff_memfree(), must be added to the project. Dependency: USE_LFN = 0 (Disabled) not possible : it requires LFN_UNICODE != 1 (Unicode). The USE_LFN option switches the LFN feature. - 0: Disable LFN feature. MAX_LFN has no effect. - 1: Enable LFN with static working buffer on the BSS. Always NOT reentrant. - 2: Enable LFN with dynamic working buffer on the STACK. - 3: Enable LFN with dynamic working buffer on the HEAP. To enable LFN feature, Unicode handling functions ff_convert() and ff_wtoupper() function must be added to the project. The LFN working buffer occupies (MAX_LFN + 1) * 2 bytes. When use stack for the working buffer, take care on stack overflow. When use heap memory for the working buffer, memory management functions, ff_memalloc() and ff_memfree(), must be added to the project. Dependencies: 1) USE_LFN = 0 (Disabled) not possible : it requires LFN_UNICODE != 1 (Unicode) 2) USE_LFN = 1 (Enabled with static working buffer on the BSS) not possible : it requires FS_REENTRANT = 0 (Disabled). The USE_LFN option switches the LFN feature. - 0: Disable LFN feature. MAX_LFN has no effect. - 1: Enable LFN with static working buffer on the BSS. Always NOT reentrant. - 2: Enable LFN with dynamic working buffer on the STACK. - 3: Enable LFN with dynamic working buffer on the HEAP. To enable LFN feature, Unicode handling functions ff_convert() and ff_wtoupper() function must be added to the project. The LFN working buffer occupies (MAX_LFN + 1) * 2 bytes. When use stack for the working buffer, take care on stack overflow. When use heap memory for the working buffer, memory management functions, ff_memalloc() and ff_memfree(), must be added to the project. Dependency: USE_LFN = 1 not possible: it requires FS_REENTRANT = 0 (Disabled). The USE_LFN option switches the LFN feature. - 0: Disable LFN feature. MAX_LFN has no effect. - 1: Enable LFN with static working buffer on the BSS. Always NOT reentrant. - 2: Enable LFN with dynamic working buffer on the STACK. - 3: Enable LFN with dynamic working buffer on the HEAP. To enable LFN feature, Unicode handling functions ff_convert() and ff_wtoupper() function must be added to the project. The LFN working buffer occupies (MAX_LFN + 1) * 2 bytes. When use stack for the working buffer, take care on stack overflow. When use heap memory for the working buffer, memory management functions, ff_memalloc() and ff_memfree(), must be added to the project. Dependency: All choices available as FS_REENTRANT = 0 (Disabled) and LFN_UNICODE = 0 (ANSI/OEM). Maximum LFN length to handle. To switch the character encoding on the FatFs API to Unicode, enable LFN feature (USE_LFN set to Enabled) and set LFN_UNICODE to 1 (Unicode). To switch the character encoding on the FatFs API to Unicode, enable LFN feature (USE_LFN set to Enabled) and set LFN_UNICODE to 1 (Unicode). Dependency: Must be set to 0 (ANSI/OEM) as USE_LFN is set to 0 (Disabled) When Unicode API is enabled, character encoding on the all FatFs API is switched to Unicode. STRF_ENCODE option selects the character encoding on the file to be read/written via string functions, f_gets(), f_putc(), f_puts and f_printf(). - 0: Read/Write a character in ANSI/OEM. - 1: Read/Write a character in UTF-16LE. - 2: Read/Write a character in UTF-16BE, - 3: Read/Write a character in UTF-8 Dependency: This option has no effect when LFN_UNICODE is 0 (ANSI/OEM). The FS_RPATH option configures relative path feature. - 0: Disable relative path feature and remove related functions. - 1: Enable relative path. f_chdrive() and f_chdir() function are available. - 2: f_getcwd() function is available in addition to 1. Note that output of the f_readdir() function is affected by this option. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Number of volumes (logical drives) to be used. Maximum sector size to be handled. Four possible values: 512, 1024, 2048, 4096. Always set 512 for memory card and hard disk but a larger value may be required for on-board flash memory, floppy disk and optical disk. When MAX_SS is larger than 512, it configures FatFs to variable sector size and GET_SECTOR_SIZE command must be implemented to the disk_ioctl() function. Minimum sector size to be handled. Note: must be less than or equal to _MAX_SS. Minimum sector size to be handled. Note: must be less than or equal to _MAX_SS. Minimum sector size to be handled. Note: must be less than or equal to _MAX_SS. Minimum sector size to be handled. Note: must be less than or equal to _MAX_SS. When set to 0 (Disabled), each volume is bound to the same physical drive number and it can mount only first primaly partition. When it is set to 1 (Enabled), each volume is tied to the partitions listed in VolToPart[]. This option switches ATA-TRIM feature. (0:Disable or 1:Enable) To enable Trim feature, also CTRL_TRIM command should be implemented to the disk_ioctl() function. If you need to know correct free space on the FAT32 volume, set bit 0 of this option and f_getfree() function at first time after volume mount will force a full FAT scan. Bit 1 controls the last allocated cluster number as bit 0. - bit0=0: Use free cluster count in the FSINFO if available. - bit0=1: Do not trust free cluster count in the FSINFO. - bit1=0: Use last allocated cluster number in the FSINFO if available. - bit1=1: Do not trust last allocated cluster number in the FSINFO. When FS_TINY is set to 1, FatFs uses the sector buffer in the file system object instead of the sector buffer in the individual file object for file data transfer. This reduces memory consumption 512 bytes each file object. The _FS_NORTC option switches timestamp feature. - If the system does not have an RTC function or valid timestamp is not needed, set _FS_NORTC to 1 (Fixed timestamp) to disable the timestamp feature. All objects modified by FatFs will have a fixed timestamp defined by _NORTC_MON, _NORTC_MDAY and _NORTC_YEAR. - When timestamp feature is enabled (Dynamic timestamp), get_fattime() function need to be added to the project to read current time form RTC and generate a timestamp. _NORTC_MON, _NORTC_MDAY and _NORTC_YEAR have no effect. As FS_NORTC is enabled, it is the year part of the timestamps used by Fatfs. Useless as FS_NORTC is disabled (otherwise, it is the year part of the timestamps used by Fatfs). As FS_NORTC is enabled, it is the month part of the timestamps used by Fatfs. Useless as FS_NORTC is disabled (otherwise, it is the month part of the timestamps used by Fatfs). As FS_NORTC is enabled, it is the day part of the timestamps used by Fatfs. As FS_NORTC is enabled, it is the day part of the timestamps used by Fatfs. As FS_NORTC is enabled, it is the day part of the timestamps used by Fatfs. Useless as FS_NORTC is disabled (otherwise, it is the day part of the timestamps used by Fatfs). The WORD_ACCESS option is an only platform dependent option. It defines which access method is used to the word data on the FAT volume. - 0: Byte-by-byte access. Always compatible with all platforms. - 1: Word access. Do not choose this unless under both the following conditions. - Byte order on the memory is little-endian. - Address miss-aligned word access is always allowed for all instructions. If it is the case, WORD_ACCESS can also be set to 1 to improve performance and reduce code size. Hidden as removed in R0.12. The FS_REENTRANT option switches the re-entrancy (thread safe) of the FatFs module. - 1: Enable re-entrancy. Also user provided synchronization handlers, ff_req_grant(), ff_rel_grant(), ff_del_syncobj() and ff_cre_syncobj() function must be added to the project. The FS_REENTRANT option switches the re-entrancy (thread safe) of the FatFs module. - 0: Disable re-entrancy. SYNC_t and FS_TIMEOUT have no effect. Timeout period in unit of time ticks New param for better support of CMSIS-RTOS v2 New param for better support of CMSIS-RTOS v2 O/S dependent type of sync object. e.g. HANDLE, OS_EVENT*, ID and etc.. O/S dependent type of sync object. e.g. HANDLE, OS_EVENT*, ID and etc.. Not needed when there is no Os in use. To enable file lock control feature, set FS_LOCK to 1 or greater. The value defines how many files can be opened simultaneously. Flag to enable the f_expand function (0:Disabled or 1:Enabled). The f_expand function prepares or allocates a contiguous data area to the file. Note: can be enabled as _FS_READONLY equals to 0 (Disabled) Flag to enable the f_expand function (0:Disabled or 1:Enabled). The f_expand function prepares or allocates a contiguous data area to the file. Note: forced to disabled as _FS_READONLY equals to 1 (Enabled) Hidden parameter when version less than 12. Flag to enable the f_chmod function (0:Disabled or 1:Enabled). The f_chmod function changes the attribute of a file or sub-directory. Note: can be enabled as _FS_READONLY equals to 0 (Disabled) Flag to enable the f_chmod function (0:Disabled or 1:Enabled). The f_chmod function changes the attribute of a file or sub-directory. Note: forced to disabled as _FS_READONLY equals to 1 (Enabled) Hidden parameter when version less than 12. This option switches support of exFAT file system. (0:Disabled or 1:Enabled). When enable exFAT, also LFN needs to be enabled. (_USE_LFN >= 1). Note that enabling exFAT discards C89 compatibility. This option switches support of exFAT file system. (0:Disabled or 1:Enabled). When enable exFAT, also LFN needs to be enabled. (_USE_LFN >= 1). Note that enabling exFAT discards C89 compatibility. Hidden parameter when version != 12. FATFS_SDIO_Init FATFS_FSMC_NAND16_Init FATFS_FMC_SDRAM_Init FATFS_SRAM_Init FATFS_USB_Init FATFS_USER_DEFINED_Init S_FATFS_SDRAM$context S_FATFS_SRAM$context S_FATFS_SRAM_FOR_M33 S_FATFS_SDIO$context S_FATFS_SDIO_FOR_M33 S_FATFS_USB$context S_FATFS_Generic$context S_FATFS_Generic_FOR_M33 S_FATFS_ENABLED