fatfs v0.05 Aug 25, 2007:
- Changed arguments of f_read, f_write. - Changed arguments of f_mkfs. (FatFs) - Fixed f_mkfs on FAT32 creates incorrect FSInfo. (FatFs) - Fixed f_mkdir on FAT32 creates incorrect directory. (FatFs)
This commit is contained in:
1 parent
c0c10d0bea
commit
36c173e705
34 files changed
+461
-225
No files matched your search
@@ -12,10 +12,10 @@
|
||||
|
||||
<div class="para">
|
||||
<h2>File and Path name on the FatFs module</h2>
|
||||
<p>The format of file and path name on the FatFs module is similer to MS-DOS. However it does not have a concept of current directory, all objects on the drive are specified in full path from the roor directory.</p>
|
||||
<p>The format of file and path name on the FatFs module is similer to MS-DOS. However it does not have a concept of current directory, all objects on the drive are specified in full path name from the root directory.</p>
|
||||
<pre>
|
||||
|
||||
"[<em>logical drive#</em>:][/]<em>directory</em>/<em>file</em>"
|
||||
"[<em>drive#</em>:][/]<em>directory</em>/<em>file</em>"
|
||||
|
||||
"file1.txt" a file on drive 0
|
||||
"/file1.txt" (same as above)
|
||||
@@ -28,13 +28,13 @@
|
||||
|
||||
</pre>
|
||||
<p>The FatFs module supports only 8.3 format file name and long file name is currentry not supported. For directory separator, a '/' is used, not a '\'. Heading '/' is ignored and can be omitted.</p>
|
||||
<p>The logical drive number is specified in a numeral with a colon. When drive number is omitted, it means the default drive (0). As for the Tiny-FatFs, it has only one logical drive and always works as drive 0. Any drive number cannot be contained in the path name.</p>
|
||||
<p>The logical drive number is specified in a numeral with a colon. When the drive number is omitted, it means the default drive (0). As for the Tiny-FatFs, it has only one logical drive and always works as drive 0. Any drive number cannot be contained in the path name.</p>
|
||||
</div>
|
||||
|
||||
<p><br></p>
|
||||
<div class="para">
|
||||
<h2>Correspondence between logical/physical drive</h2>
|
||||
<p>In default, the FatFs module has work areas that called file system object for each logical drive. The logical drive is bound simply to the physical drive that has same drive number, and first partition is mounted. When <tt>_MULTI_PARTITION</tt> is specified in configuration option, each individual logical drive can be bound to any physical drive/partition. In this case, a drive number resolution table must be defined as follows:</p>
|
||||
<p>In default, the FatFs module has work areas that called `file system object' for each logical drive. The logical drive is bound simply to the physical drive that has same drive number, and first partition is mounted. When <tt>_MULTI_PARTITION</tt> is specified in configuration option, each individual logical drive can be bound to any physical drive/partition. In this case, a drive number resolution table must be defined as follows:</p>
|
||||
<pre>
|
||||
Example: Logical drive 0-2 are assigned to three pri-partitions on the physical drive 0 (fixed disk)
|
||||
Logical drive 3 is assigned to physical drive 0 (removable disk)
|
||||
@@ -49,8 +49,8 @@ const PARTITION Drives[] = {
|
||||
<p>There are some consideration when use <tt>_MULTI_PARTITION</tt> configuration.</p>
|
||||
<ul>
|
||||
<li>Only pri-partition (0-3) can be mounted.</li>
|
||||
<li>When the drive have no partition table (super floppy format), partition number is ignored.</li>
|
||||
<li>The drive that has two or more logical drive must be fixed drive.</li>
|
||||
<li>When the physical drive have no partition table (super floppy format), the partition number is ignored.</li>
|
||||
<li>The physical drive that has two or more logical drives must be fixed drive.</li>
|
||||
</li>
|
||||
</div>
|
||||
|
||||
|
||||
Reference in new issue
Block a user