Mirtoo README.txt and SST25 comments update

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4874 42af7a65-404d-4744-a932-0658087f49c3

2 files changed, 23 insertions, 11 deletions

diff --git a/nuttx/configs/mirtoo/README.txt b/nuttx/configs/mirtoo/README.txt
index a2f8296a2..5e7dec6a3 100644
--- a/nuttx/configs/mirtoo/README.txt
+++ b/nuttx/configs/mirtoo/README.txt
@@ -821,13 +821,14 @@ Where <subdir> is one of the following:
 
   nxffs:
     This is a configuration very similar to the nsh configuration.  This
-    configure also provides the NuttShell (NSH).  This configuration use
+    configure also provides the NuttShell (NSH).  And this configuration use
     UART1 which is available on FUNC 4 and 5 on connector X3 (as described
-    for the nsh configuration).  This configuration differs in the fillowing
-    ways:
+    for the nsh configuration).  This configuration differs from the nsh
+    configuration in the following ways:
 
     1) SPI2 is enabled and support is included for the NXFFS file system
-       on the 32Mbi SST25 device on the Mirtoo board.
+       on the 32Mbit SST25 device on the Mirtoo board.  NXFFS is the NuttX
+       wear-leveling file system.
 
        CONFIG_PIC32MX_SPI2=y
        CONFIG_MTD_SST25=y
@@ -866,12 +867,15 @@ Where <subdir> is one of the following:
        CONFIG_NSH_DISABLE_TEST=y
        CONFIG_NSH_DISABLE_WGET=y
 
+     When the system boots, you should have the NXFFS file system mounted
+     at /mnt/sst25.
+
      NOTES:  (1) It takes many seconds to boot the sytem using the NXFFS
      file system because the entire FLASH must be verified on power up
-     (a probably several minutes the first time that NXFFS comes up and
-     had to format the file system). (2) FAT does not have these delays
-     and this configuration can be modified to use the (larger) FAT file
-     system as described below:
+     (and many *minutes* the first time that NXFFS comes up and has to
+     format the file system). (2) FAT does not have these delays and this
+     configuration can be modified to use the (larger) FAT file system as
+     described below:
 
   fat:
      There is no FAT configuration, but the nxffx configuration can be used
@@ -881,3 +885,11 @@ Where <subdir> is one of the following:
        CONFIG_FS_NXFFS=n
        CONFIG_FS_FAT=y
        CONFIG_NSH_DISABLE_MKFATFS=n
+
+     In this configuration, the FAT file system will not be automatically
+     monounted.  When NuttX boots to the NSH prompt, you will find the
+     SST5 block driver at /dev/mtdblock0.  This can be formatted with a
+     FAT file system and mounted with these commands:
+
+       nsh> mkfatfs /dev/mtdblock0
+       nsh> mount -t vfat /dev/mtdblock0 /mnt/sst25
diff --git a/nuttx/drivers/mtd/sst25.c b/nuttx/drivers/mtd/sst25.c
index 81b5dc1bf..83fbdc347 100644
--- a/nuttx/drivers/mtd/sst25.c
+++ b/nuttx/drivers/mtd/sst25.c
@@ -60,9 +60,9 @@
  * Pre-processor Definitions
  ************************************************************************************/
 /* Configuration ********************************************************************/
-/* Per the data sheet, the SST25 parts can be driven with either SPI mode 0 (CPOL=0 and
- * CPHA=0) or mode 3 (CPOL=1 and CPHA=1). But I have heard that other devices can
- * operated in mode 0 or 1.  So you may need to specify CONFIG_SST25_SPIMODE to
+/* Per the data sheet, the SST25 parts can be driven with either SPI mode 0 (CPOL=0
+ * and CPHA=0) or mode 3 (CPOL=1 and CPHA=1). But I have heard that other devices
+ * can operate in mode 0 or 1.  So you may need to specify CONFIG_SST25_SPIMODE to
  * select the best mode for your device.  If CONFIG_SST25_SPIMODE is not defined,
  * mode 0 will be used.
  */