projects / z180-stamp.git / blame
| Commit | Line | Data |
|---|---|---|
| 53668523 L |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">\r |
| 2 | <html lang="en">\r | |
| 3 | <head>\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="alternate" hreflang="ja" title="Japanese" href="../ja/dread.html">\r | |
| 8 | <link rel="stylesheet" href="../css_e.css" type="text/css" media="screen" title="ELM Default">\r | |
| 9 | <title>FatFs - disk_read</title>\r | |
| 10 | </head>\r | |
| 11 | \r | |
| 12 | <body>\r | |
| 13 | \r | |
| 14 | <div class="para func">\r | |
| 15 | <h2>disk_read</h2>\r | |
| 16 | <p>The disk_read function reads sector(s) from the storage device.</p>\r | |
| 17 | <pre>\r | |
| 18 | DRESULT disk_read (\r | |
| 19 | BYTE <span class="arg">pdrv</span>, <span class="c">/* [IN] Physical drive number */</span>\r | |
| 20 | BYTE* <span class="arg">buff</span>, <span class="c">/* [OUT] Pointer to the read data buffer */</span>\r | |
| 21 | DWORD <span class="arg">sector</span>, <span class="c">/* [IN] Start sector number */</span>\r | |
| 22 | UINT <span class="arg">count</span> <span class="c">/* [IN] Number of sectros to read */</span>\r | |
| 23 | );\r | |
| 24 | </pre>\r | |
| 25 | </div>\r | |
| 26 | \r | |
| 27 | <div class="para arg">\r | |
| 28 | <h4>Parameters</h4>\r | |
| 29 | <dl class="par">\r | |
| 30 | <dt>pdrv</dt>\r | |
| 31 | <dd>Physical drive number to identify the target device.</dd>\r | |
| 32 | <dt>buff</dt>\r | |
| 70702af1 | 33 | <dd>Pointer to the first item of the <em>byte array</em> to store read data.</dd>\r |
| 53668523 | 34 | <dt>sector</dt>\r |
| 7b78a5a2 | 35 | <dd>Start sector number in 32-bit LBA.</dd>\r |
| 53668523 | 36 | <dt>count</dt>\r |
| 70702af1 | 37 | <dd>Number of sectors to read.</dd>\r |
| 53668523 L |
38 | </dl>\r |
| 39 | </div>\r | |
| 40 | \r | |
| 41 | \r | |
| 42 | <div class="para ret">\r | |
| 43 | <h4>Return Value</h4>\r | |
| 44 | <dl class="ret">\r | |
| 45 | <dt>RES_OK (0)</dt>\r | |
| 46 | <dd>The function succeeded.</dd>\r | |
| 47 | <dt>RES_ERROR</dt>\r | |
| 48 | <dd>Any hard error occured during the read operation and could not recover it.</dd>\r | |
| 49 | <dt>RES_PARERR</dt>\r | |
| 50 | <dd>Invalid parameter.</dd>\r | |
| 51 | <dt>RES_NOTRDY</dt>\r | |
| 52 | <dd>The device has not been initialized.</dd>\r | |
| 53 | </dl>\r | |
| 54 | </div>\r | |
| 55 | \r | |
| 56 | \r | |
| 57 | <div class="para desc">\r | |
| 58 | <h4>Description</h4>\r | |
| 70702af1 L |
59 | <p>The data read/write operation to the storage devices is done in unit of <em>sector</em>. FatFs supports the sector size in range of from 512 to 4096 bytes. When FatFs is configured to fixed sector size (<tt>_MIN_SS == MAX_SS</tt>, this will be the most case), the read/write function must work at that sector size. When FatFs is configured to variable sector size (<tt>_MIN_SS != MAX_SS</tt>), sector size is inquired with <tt>disk_ioctl</tt> function following <tt>disk_initialize</tt> function.</p>\r |
| 60 | <p>The memory address specified by <tt class="arg">buff</tt> is not that always aligned to word boundary because the argument is defined as <tt>BYTE*</tt>. The unaligned read/write request can occure at <a href="appnote.html#fs1">direct transfer</a>. If the bus architecture, especially DMA controller, does not allow unaligned memory access, it should be solved in this function. There are some workarounds described below to avoid this issue.</p>\r | |
| 53668523 | 61 | <ul>\r |
| 7b78a5a2 | 62 | <li>Convert word transfer to byte transfer in this function if needed. - Recommended.</li>\r |
| 70702af1 L |
63 | <li>On the <tt>f_read</tt> calls, avoid long read request that includes a whole of sector. - Any direct transfer never occures.</li>\r |
| 64 | <li>On the <tt>f_read</tt> calls, make sure that <tt>(((UINT)data & 3) == (f_tell(fp) & 3))</tt> is true. - Word alignment of <tt>buff</tt> is guaranteed.</li>\r | |
| 53668523 L |
65 | </ul>\r |
| 66 | <p>Generally, a multiple sector transfer request must not be split into single sector transactions to the storage device, or you will not get good read throughput.</p>\r | |
| 67 | </div>\r | |
| 68 | \r | |
| 69 | \r | |
| 70 | <p class="foot"><a href="../00index_e.html">Return</a></p>\r | |
| 71 | </body>\r | |
| 72 | </html>\r |