<link rel="up" title="FatFs" href="../00index_e.html">\r
<link rel="alternate" hreflang="ja" title="Japanese" href="../ja/rc.html">\r
<link rel="stylesheet" href="../css_e.css" type="text/css" media="screen" title="ELM Default">\r
-<title>FatFs - Return Codes</title>\r
+<title>FatFs - API Return Code</title>\r
</head>\r
\r
<body>\r
-<h1>Return Code of the File Functions</h1>\r
-<p>On the FatFs API, most of file functions return common result code as enum type <tt>FRESULT</tt>. When a function succeeded, it returns zero, otherwise returns non-zero value that indicates type of error.</p>\r
+<h1>Return Code of API Functions</h1>\r
+<p>Most of API functions return common result code as enum type <tt>FRESULT</tt>. When an API function succeeded, it returns zero (<tt>FR_OK</tt>), otherwise it returns non-zero value indicates type of error.</p>\r
\r
<dl class="ret">\r
+\r
<dt id="ok">FR_OK (0)</dt>\r
<dd>The function succeeded.</dd>\r
+\r
<dt id="de">FR_DISK_ERR</dt>\r
-<dd>An unrecoverable hard error occured in the lower layer, <tt>disk_read()</tt>, <tt>disk_write()</tt> or <tt>disk_ioctl()</tt> function.<br>Note that if once this error occured at any operation to an open file, the file object is aborted and all operations to the file except for close will be rejected.</dd>\r
+<dd>An unrecoverable hard error occured in the lower layer, <tt>disk_read</tt>, <tt>disk_write</tt> or <tt>disk_ioctl</tt> function.<br>Note that if once this error occured at any operation to an open file, the file object is aborted and all operations to the file except for close will be rejected.</dd>\r
+\r
<dt id="ie">FR_INT_ERR</dt>\r
<dd>Assertion failed. An insanity is detected in the internal process. One of the following possibilities is suspected.\r
<ul>\r
<li>Work area (file system object, file object or etc...) has been broken by stack overflow or any other tasks. This is the reason in most case.</li>\r
-<li>There is any error of the FAT structure on the volume.</li>\r
+<li>There is an error of the FAT structure on the volume.</li>\r
+<li>There is a bug in the FatFs module itself.</li>\r
</ul>\r
Note that if once this error occured at any operation to an open file, the file object is aborted and all operations to the file except for close will be rejected.\r
</dd>\r
+\r
<dt id="nr">FR_NOT_READY</dt>\r
-<dd>The disk drive cannot work due to incorrect medium removal or <tt>disk_initialize()</tt> function failed.</dd>\r
+<dd>The storage device cannot work due to a failure of <a href="dinit.html"><tt>disk_initialize</tt></a> function due to no medium or any other reason.</dd>\r
+\r
<dt id="nf">FR_NO_FILE</dt>\r
<dd>Could not find the file.</dd>\r
+\r
<dt id="np">FR_NO_PATH</dt>\r
<dd>Could not find the path.</dd>\r
+\r
<dt id="in">FR_INVALID_NAME</dt>\r
<dd>The given string is invalid as the <a href="filename.html">path name</a>.</dd>\r
+\r
<dt id="dn">FR_DENIED</dt>\r
<dd>The required access was denied due to one of the following reasons:\r
<ul>\r
<li>Deleting the non-empty directory or current directory.</li>\r
<li>Reading the file opened without <tt>FA_READ</tt> flag.</li>\r
<li>Any modification to the file opened without <tt>FA_WRITE</tt> flag.</li>\r
-<li>Could not create the file or directory due to the directory table is full.</li>\r
-<li>Could not create the directory due to the volume is full.</li>\r
+<li>Could not create the object due to root directory full or disk full.</li>\r
+<li>Could not allocate a contiguous area to the file.</li>\r
</ul>\r
</dd>\r
+\r
<dt id="ex">FR_EXIST</dt>\r
-<dd>Name collision. Any object that has the same name is already existing.</dd>\r
+<dd>Name collision. An object with the same name is already existing.</dd>\r
+\r
<dt id="io">FR_INVALID_OBJECT</dt>\r
-<dd>The file/directory object structure is invalid or a null pointer is given. All open objects of the logical drive are invalidated by the voulme mount process.</dd>\r
+<dd>The file/directory object is invalid or a null pointer is given. There are some reasons as follows:\r
+<ul>\r
+<li>It has been closed, it has not been opened or it has been collapsed.</li>\r
+<li>It has been invalidated by a voulme mount process. Open objects on the volume are invalidated by voulme mount process.</li>\r
+<li>Physical drive is not ready to work due to a media removal.</li>\r
+</ul>\r
+</dd>\r
+\r
<dt id="wp">FR_WRITE_PROTECTED</dt>\r
-<dd>Any write mode operation against the write-protected media.</dd>\r
+<dd>A write mode operation against the write-protected media.</dd>\r
+\r
<dt id="id">FR_INVALID_DRIVE</dt>\r
-<dd>Invalid drive number is specified in the path name. A null pointer is given as the path name. (Related option: <tt>_VOLUMES</tt>)</dd>\r
+<dd>Invalid drive number is specified in the path name. A null pointer is given as the path name. (Related option: <tt><a href="config.html#volumes">_VOLUMES</a></tt>)</dd>\r
+\r
<dt id="ne">FR_NOT_ENABLED</dt>\r
-<dd>Work area for the logical drive has not been registered by <tt>f_mount()</tt> function.</dd>\r
+<dd>Work area for the logical drive has not been registered by <tt>f_mount</tt> function.</dd>\r
+\r
<dt id="ns">FR_NO_FILESYSTEM</dt>\r
<dd>There is no valid FAT volume on the drive.</dd>\r
+\r
<dt id="ma">FR_MKFS_ABORTED</dt>\r
-<dd>The <tt>f_mkfs()</tt> function aborted before start in format due to a reason as follows:\r
+<dd>The <tt>f_mkfs</tt> function aborted before start in format due to a reason as follows:\r
<ul>\r
-<li>The disk/partition size is too small.</li>\r
-<li>Not allowable cluster size for this disk. This can occure when number of clusters gets near the boundaries of FAT sub-types.</li>\r
-<li>There is no partition related to the logical drive. (Related option: <tt>_MULTI_PARTITION</tt>)</li>\r
+<li>It is pmpossible to formart with the given parameters.</li>\r
+<li>The size of volume is too small.</li>\r
+<li>The size of given work area is too small.</li>\r
+<li>The partition bound to the logical drive coulud not be found. (Related option: <tt><a href="config.html#multi_partition">_MULTI_PARTITION</a></tt>)</li>\r
</ul>\r
</dd>\r
+\r
<dt id="tm">FR_TIMEOUT</dt>\r
-<dd>The function was canceled due to a timeout of <a href="appnote.html#reentrant">thread-safe control</a>. (Related option: <tt>_TIMEOUT</tt>)</dd>\r
+<dd>The function was canceled due to a timeout of <a href="appnote.html#reentrant">thread-safe control</a>. (Related option: <tt><a href="config.html#timeout">_TIMEOUT</a></tt>)</dd>\r
+\r
<dt id="lo">FR_LOCKED</dt>\r
-<dd>The operation to the object was rejected by <a href="appnote.html#dup">file sharing control</a>. (Related option: <tt>_FS_LOCK</tt>)</dd>\r
+<dd>The operation to the object was rejected by <a href="appnote.html#dup">file sharing control</a>. (Related option: <tt><a href="config.html#fs_lock">_FS_LOCK</a></tt>)</dd>\r
+\r
<dt id="nc">FR_NOT_ENOUGH_CORE</dt>\r
<dd>Not enough memory for the operation. There is one of the following reasons:\r
<ul>\r
-<li>Could not allocate a memory for LFN working buffer. (Related option: <tt>_USE_LFN</tt>)</li>\r
+<li>Could not allocate a memory for LFN working buffer. (Related option: <tt><a href="config.html#use_lfn">_USE_LFN</a></tt>)</li>\r
<li>Size of the given buffer is insufficient for the size required.</li>\r
</ul>\r
</dd>\r
+\r
<dt id="tf">FR_TOO_MANY_OPEN_FILES</dt>\r
-<dd>Number of open objects has been reached maximum value and no more object can be opened. (Related option: <tt>_FS_LOCK</tt>)</dd>\r
+<dd>Number of open objects has been reached maximum value and no more object can be opened. (Related option: <tt><a href="config.html#fs_lock">_FS_LOCK</a></tt>)</dd>\r
+\r
<dt id="ip">FR_INVALID_PARAMETER</dt>\r
-<dd>The given parameter is invalid or there is any inconsistent.</dd>\r
+<dd>The given parameter is invalid or there is an inconsistent for the volume.</dd>\r
</dl>\r
\r
+<p class="foot"><a href="../00index_e.html">Return</a></p>\r
</body>\r
</html>\r
projects / z180-stamp.git / blobdiff