summaryrefslogtreecommitdiff
path: root/nuttx/configs/lpc4330-xplorer/README.txt
diff options
context:
space:
mode:
Diffstat (limited to 'nuttx/configs/lpc4330-xplorer/README.txt')
-rw-r--r--nuttx/configs/lpc4330-xplorer/README.txt36
1 files changed, 17 insertions, 19 deletions
diff --git a/nuttx/configs/lpc4330-xplorer/README.txt b/nuttx/configs/lpc4330-xplorer/README.txt
index 68fe3f396..cf60ca0ec 100644
--- a/nuttx/configs/lpc4330-xplorer/README.txt
+++ b/nuttx/configs/lpc4330-xplorer/README.txt
@@ -903,22 +903,20 @@ Where <subdir> is one of the following:
This configuration has some special options that can be used to
create a block device on the SPIFI FLASH. NOTE: CONFIG_LPC43_SPIFI=y
must also be defined to enable SPIFI setup support:
-
- CONFIG_SPIFI_BLKDRVR - Enable to create a block driver on the SPFI
- device.
- CONFIG_SPIFI_DEVNO - SPIFI minor device number. The SPFI device will
- be at /dev/ramN, where N is the value of CONFIG_SPIFI_DEVNO.
- Default: 0.
- CONFIG_SPIFI_RDONLY - Create a read only device on SPIFI.
- CONFIG_SPIFI_OFFSET - Offset the beginning of the block driver this
- many bytes into the device address space. Default 0.
- CONFIG_SPIFI_BLKSIZE - The size of one block. SPIFI is not block
- oriented, so most any size of the block used in the SPIFI block
- device can be used. NOTE: FAT will support only sector sizes of
- 512, 1024, 2048, or 4096. Default: 512
- CONFIG_SPIFI_NBLOCKS - The number of blocks in the file system,
- each of size CONFIG_SPIFI_BLKSIZE. The end of the file system
- will be at device offset:
- CONFIG_SPIFI_OFFSET + CONFIG_SPIFI_BLKSIZE*CONFIG_SPIFI_NBLOCKS
- The must assure that this does offset does not go beyond the end
- of the FLASH memory.
+
+ SPIFI device geometry:
+
+ CONFIG_SPIFI_OFFSET - Offset the beginning of the block driver this many
+ bytes into the device address space. This offset must be an exact
+ multiple of the erase block size (CONFIG_SPIFI_BLKSIZE). Default 0.
+ CONFIG_SPIFI_BLKSIZE - The size of one device erase block. If not defined
+ then the driver will try to determine the correct erase block size by
+ examining that data returned from spifi_initialize (which sometimes
+ seems bad).
+
+ Other SPIFI options
+
+ CONFIG_SPIFI_SECTOR512 - If defined, then the driver will report a more
+ FAT friendly 512 byte sector size and will manage the read-modify-write
+ operations on the larger erase block.
+ CONFIG_SPIFI_READONLY - Define to support only read-only operations.