223/* This option switches tiny buffer configuration. (0:Normal or 1:Tiny)
224/ At the tiny configuration, size of file object (FIL) is shrinked FF_MAX_SS bytes.
225/ Instead of private sector buffer eliminated from the file object, common sector
226/ buffer in the filesystem object (FATFS) is used for the file data transfer. */
227
228
229#define FF_FS_EXFAT 0
230/* This option switches support for exFAT filesystem. (0:Disable or 1:Enable)
231/ When enable exFAT, also LFN needs to be enabled.
232/ Note that enabling exFAT discards ANSI C (C89) compatibility. */
233
234
235#define FF_FS_HEAPBUF 1
236/* This option enables the use of the heap for allocating buffers. Otherwise
237/ _MAX_SS sized buffers are allocated statically in relevant structures (in
238/ FATFS if _FS_TINY, otherwise in FATFS and FIL)
239/ This option allows the filesystem to dynamically allocate the buffers based
240/ on underlying sector size. */
241
242
243#define FF_FS_NORTC 0
244#define FF_NORTC_MON 1
245#define FF_NORTC_MDAY 1
246#define FF_NORTC_YEAR 2017
247/* The option FF_FS_NORTC switches timestamp functiton. If the system does not have
248/ any RTC function or valid timestamp is not needed, set FF_FS_NORTC = 1 to disable
249/ the timestamp function. All objects modified by FatFs will have a fixed timestamp
250/ defined by FF_NORTC_MON, FF_NORTC_MDAY and FF_NORTC_YEAR in local time.
251/ To enable timestamp function (FF_FS_NORTC = 0), get_fattime() function need to be
252/ added to the project to read current time form real-time clock. FF_NORTC_MON,
253/ FF_NORTC_MDAY and FF_NORTC_YEAR have no effect.
254/ These options have no effect at read-only configuration (FF_FS_READONLY = 1). */
255
256
257#define FF_FS_LOCK 0
258/* The option FF_FS_LOCK switches file lock function to control duplicated file open
259/ and illegal operation to open objects. This option must be 0 when FF_FS_READONLY
260/ is 1.
261/
262/ 0: Disable file lock function. To avoid volume corruption, application program
263/ should avoid illegal open, remove and rename to the open objects.
264/ >0: Enable file lock function. The value defines how many files/sub-directories
265/ can be opened simultaneously under file lock control. Note that the file
266/ lock control is independent of re-entrancy. */
267
268
269#define FF_FS_REENTRANT 0
270#define FF_FS_TIMEOUT 1000
271#define FF_SYNC_t HANDLE
272/* The option FF_FS_REENTRANT switches the re-entrancy (thread safe) of the FatFs
273/ module itself. Note that regardless of this option, file access to different
274/ volume is always re-entrant and volume control functions, f_mount(), f_mkfs()
275/ and f_fdisk() function, are always not re-entrant. Only file/directory access
276/ to the same volume is under control of this function.
277/
278/ 0: Disable re-entrancy. FF_FS_TIMEOUT and FF_SYNC_t have no effect.
279/ 1: Enable re-entrancy. Also user provided synchronization handlers,
280/ ff_req_grant(), ff_rel_grant(), ff_del_syncobj() and ff_cre_syncobj()
281/ function, must be added to the project. Samples are available in
282/ option/syscall.c.
283/
284/ The FF_FS_TIMEOUT defines timeout period in unit of time tick.
285/ The FF_SYNC_t defines O/S dependent sync object type. e.g. HANDLE, ID, OS_EVENT*,
286/ SemaphoreHandle_t and etc. A header file for O/S definitions needs to be
287/ included somewhere in the scope of ff.h. */
288
289/* #include <windows.h> // O/S definitions */
290
291#define FLUSH_ON_NEW_CLUSTER 0 /* Sync the file on every new cluster */
292#define FLUSH_ON_NEW_SECTOR 1 /* Sync the file on every new sector */
293/* Only one of these two defines needs to be set to 1. If both are set to 0
294 the file is only sync when closed.
295 Clusters are group of sectors (eg: 8 sectors). Flushing on new cluster means
296 it would be less often than flushing on new sector. Sectors are generally
297 512 Bytes long. */
298
299
300/*--- End of configuration options ---*/
Important Information for this Arm website
This site uses cookies to store information on your computer.
By continuing to use our site, you consent to our cookies.
If you are not happy with the use of these cookies, please review our
Cookie Policy
to learn how they can be disabled.
By disabling cookies, some features of the site will not work.