From 20236a8a990cae729bca1f7a4e0d619e92a5e37d Mon Sep 17 00:00:00 2001 From: Damien George Date: Sat, 20 Dec 2014 21:15:16 +0000 Subject: stmhal: Upgrade to latest fatfs driver. --- stmhal/fatfs/doc/en/sync.html | 66 ------------------------------------------- 1 file changed, 66 deletions(-) delete mode 100644 stmhal/fatfs/doc/en/sync.html (limited to 'stmhal/fatfs/doc/en/sync.html') diff --git a/stmhal/fatfs/doc/en/sync.html b/stmhal/fatfs/doc/en/sync.html deleted file mode 100644 index 4c819b818..000000000 --- a/stmhal/fatfs/doc/en/sync.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - - - -FatFs - f_sync - - - - -
-

f_sync

-

The f_sync function flushes the cached information of a writing file.

-
-FRESULT f_sync (
-  FIL* fp     /* [IN] File object */
-);
-
-
- -
-

Parameter

-
-
fp
-
Pointer to the open file object to be flushed.
-
-
- - -
-

Return Values

-

-FR_OK, -FR_DISK_ERR, -FR_INT_ERR, -FR_NOT_READY, -FR_INVALID_OBJECT, -FR_TIMEOUT -

-
- - -
-

Description

-

The f_sync() function performs the same process as f_close() function but the file is left opened and can continue read/write/seek operations to the file. This is suitable for the applications that open files for a long time in write mode, such as data logger. Performing f_sync() function of periodic or immediataly after f_write() function can minimize the risk of data loss due to a sudden blackout or an unintentional media removal. For more information, refer to application note.

-

However the f_sync() function immediataly before f_close() function has no advantage because it performs f_sync() function in it. In other words, the differnce between those functions is that the file object is invalidated or not.

-
- - -
-

QuickInfo

-

Available when _FS_READONLY == 0.

-
- - -
-

See Also

-

f_close

-
- -

Return

- - -- cgit v1.2.3