fatfs v0.04 Feb 04, 2007:

- Supported multiple drive system.
- Changed some APIs for multiple drive system.
- Added f_mkfs().
This commit is contained in:
savelij13 committed 2025-09-11 09:03:34 +03:00
1 parent f76dc3a97f
commit 3d65978d31
75 files changed
+2636 -1380

No files matched your search

+9 -9
View File
@@ -12,10 +12,10 @@
<div class="para">
<h2>f_sync</h2>
<p>The f_sync flushes the cached information of the wriiting file.</p>
<p>The f_sync function flushes the cached information of a wriiting file.</p>
<pre>
FRESULT f_sync (
FIL* <em>FileObject</em> // Pointer to the file object structure
FIL* <em>FileObject</em> /* Pointer to the file object */
);
</pre>
</div>
@@ -24,7 +24,7 @@ FRESULT f_sync (
<h4>Parameters</h4>
<dl class="par">
<dt>FileObject</dt>
<dd>Pointer to the file object to be flushed.</dd>
<dd>Pointer to the open file object to be flushed.</dd>
</dl>
</div>
@@ -35,18 +35,18 @@ FRESULT f_sync (
<dt>FR_OK (0)</dt>
<dd>The function succeeded.</dd>
<dt>FR_RW_ERROR</dt>
<dd>Any error occured in low level disk I/O.</dd>
<dt>FR_INCORRECT_DISK_CHANGE</dt>
<dd>Incorrect disk removal/change has been occured.</dd>
<dt>FR_NOT_ENABLED</dt>
<dd>FatFs module is not enabled.</dd>
<dd>Any error has occured in low level disk I/O.</dd>
<dt>FR_NOT_READY</dt>
<dd>The disk drive cannot work due to no medium in the drive or any other reason.</dd>
<dt>FR_INVALID_OBJECT</dt>
<dd>The file object is invalid.</dd>
</dl>
</div>
<div class="para">
<h4>Description</h4>
<p>The function f_sync() performs the same process as f_close() but the file is left opened and can continue file read/write operations to the file. This is suitable for applications that open files for a long time in writing mode, such as data logger. Performing f_sync() of periodic or immediataly after f_write() can minimize risk of data loss due to sudden blackout or unintentional disk removal. This function is not supported in read-only configuration.</p>
<p>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 applications that open files for a long time in writing mode, such as data logger. Performing f_sync of periodic or immediataly after f_write can minimize risk of data loss due to sudden blackout or unintentional disk removal. This function is not supported in read-only configuration.</p>
</div>