1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
\r
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
\r
5 <meta http-equiv="Content-Style-Type" content="text/css">
\r
6 <link rel="up" title="FatFs" href="../00index_e.html">
\r
7 <link rel="stylesheet" href="../css_e.css" type="text/css" media="screen" title="ELM Default">
\r
8 <title>FatFs - f_sync</title>
\r
15 <p>The f_sync function flushes the cached information of a writing file.</p>
\r
18 FIL* <em>FileObject</em> /* Pointer to the file object */
\r
27 <dd>Pointer to the open file object to be flushed.</dd>
\r
33 <h4>Return Values</h4>
\r
36 <dd>The function succeeded.</dd>
\r
37 <dt>FR_DISK_ERR</dt>
\r
38 <dd>The function failed due to an error in the disk function.</dd>
\r
40 <dd>The function failed due to a wrong FAT structure or an internal error.</dd>
\r
41 <dt>FR_NOT_READY</dt>
\r
42 <dd>The disk drive cannot work due to no medium in the drive or any other reason.</dd>
\r
43 <dt>FR_INVALID_OBJECT</dt>
\r
44 <dd>The file object is invalid.</dd>
\r
50 <h4>Description</h4>
\r
51 <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 a sudden blackout or an unintentional disk removal. However f_sync immediataly before f_close has no advantage because f_close performs f_sync in it. This function is not available in read-only configuration.</p>
\r
57 <p><tt><a href="close.html">f_close</a></tt></p>
\r
60 <p class="foot"><a href="../00index_e.html">Return</a></p>
\r