X-Git-Url: http://cloudbase.mooo.com/gitweb/z180-stamp.git/blobdiff_plain/5366852335044c1e68a5c32548d3051cc943552f..289f6a146c0b2087607d8d8659531ea90142779a:/fatfs/doc/en/dread.html diff --git a/fatfs/doc/en/dread.html b/fatfs/doc/en/dread.html deleted file mode 100644 index f81cf90..0000000 --- a/fatfs/doc/en/dread.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - - - -FatFs - disk_read - - - - -
-

disk_read

-

The disk_read function reads sector(s) from the storage device.

-
-DRESULT disk_read (
-  BYTE pdrv,     /* [IN] Physical drive number */
-  BYTE* buff,    /* [OUT] Pointer to the read data buffer */
-  DWORD sector,  /* [IN] Start sector number */
-  UINT count     /* [IN] Number of sectros to read */
-);
-
-
- -
-

Parameters

-
-
pdrv
-
Physical drive number to identify the target device.
-
buff
-
Pointer to the byte array to store the read data.
-
sector
-
Start sector number in logical block address (LBA).
-
count
-
Number of sectors to read. FatFs specifis it in range of from 1 to 128.
-
-
- - -
-

Return Value

-
-
RES_OK (0)
-
The function succeeded.
-
RES_ERROR
-
Any hard error occured during the read operation and could not recover it.
-
RES_PARERR
-
Invalid parameter.
-
RES_NOTRDY
-
The device has not been initialized.
-
-
- - -
-

Description

-

The memory address specified by buff is not that always aligned to word boundary because the type of argument is defined as BYTE*. The misaligned read/write request can occure at direct transfer. If the bus architecture, especially DMA controller, does not allow misaligned memory access, it should be solved in this function. There are some workarounds described below to avoid this issue.

- -

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.

-
- - -

Return

- -