From 1b4e32ef207acfc1687f488192fe5ecbc64efeb3 Mon Sep 17 00:00:00 2001
From: Gregory Nutt <gnutt@nuttx.org>
Date: Mon, 9 Mar 2015 19:58:59 -0600
Subject: [PATCH] Update README

---
 Documentation/NuttX.html       |  2 +-
 configs/sam4e-ek/README.txt    |  2 +-
 configs/samv71-xult/README.txt | 77 ++++++++++++++++++++++++++++++++++
 3 files changed, 79 insertions(+), 2 deletions(-)

diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html
index 196405c831..8c10a00697 100644
--- a/Documentation/NuttX.html
+++ b/Documentation/NuttX.html
@@ -3870,7 +3870,7 @@ Mem:         29232       5920      23312      23312
   <p>
     <b>Development Environments:</b>
     The same basic development environment is recommended for the Cortex-M7 as for the Cortex-M4.
-    It would be wise to use the last GNU toolchains for this part because as of this writing (2015-02-09), support for the Cortex-M7 is a very new GCC feature.
+    It would be wise to use the latest GNU toolchains for this part because as of this writing (2015-02-09), support for the Cortex-M7 is a very new GCC feature.
   </p>
   </td>
 </tr>
diff --git a/configs/sam4e-ek/README.txt b/configs/sam4e-ek/README.txt
index 48efd2dd58..d86d2f2385 100644
--- a/configs/sam4e-ek/README.txt
+++ b/configs/sam4e-ek/README.txt
@@ -1240,7 +1240,7 @@ Configurations
     . ./setenv.sh
 
   Before sourcing the setenv.sh file above, you should examine it and perform
-  edits as necessary so that BUILDROOT_BIN is the correct path to the directory
+  edits as necessary so that TOOLCHAIN_BIN is the correct path to the directory
   than holds your toolchain binaries.
 
   And then build NuttX by simply typing the following.  At the conclusion of
diff --git a/configs/samv71-xult/README.txt b/configs/samv71-xult/README.txt
index 2fe1ba5bca..c73822d50c 100644
--- a/configs/samv71-xult/README.txt
+++ b/configs/samv71-xult/README.txt
@@ -172,3 +172,80 @@ NOTES:
 
 Configurations
 ==============
+
+  Information Common to All Configurations
+  ----------------------------------------
+  Each SAMV71-XULT configuration is maintained in a sub-directory and
+  can be selected as follow:
+
+    cd tools
+    ./configure.sh samv71-xult/<subdir>
+    cd -
+    . ./setenv.sh
+
+  Before sourcing the setenv.sh file above, you should examine it and perform
+  edits as necessary so that TOOLCHAIN_BIN is the correct path to the directory
+  than holds your toolchain binaries.
+
+  And then build NuttX by simply typing the following.  At the conclusion of
+  the make, the nuttx binary will reside in an ELF file called, simply, nuttx.
+
+    make oldconfig
+    make
+
+  The <subdir> that is provided above as an argument to the tools/configure.sh
+  must be is one of the following.
+
+  NOTES:
+
+  1. These configurations use the mconf-based configuration tool.  To
+    change any of these configurations using that tool, you should:
+
+    a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
+       and misc/tools/
+
+    b. Execute 'make menuconfig' in nuttx/ in order to start the
+       reconfiguration process.
+
+  2. Unless stated otherwise, all configurations generate console
+     output on USART3 (i.e., for the Arduino serial shield).
+
+  3. All of these configurations are set up to build under Windows using the
+     devkitARM toolchain (unless stated otherwise in the description of
+     the configuration).  That build selection can easily be reconfigured
+     using 'make menuconfig'.  Here are the relevant current settings:
+
+     Build Setup:
+       CONFIG_HOST_WINDOWS=y               : Window environment
+       CONFIG_WINDOWS_CYGWIN=y             : Cywin under Windows
+
+     System Type -> Toolchain:
+       CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM toolchain
+
+    You an get the free devkitARM toolchain from http://devkitpro.org/ or
+    http://sourceforge.net/projects/devkitpro/
+
+  Configuration sub-directories
+  -----------------------------
+
+  nsh:
+
+    Configures the NuttShell (nsh) located at examples/nsh.
+    NOTES:
+
+    1. Default stack sizes are large and should really be tuned to reduce
+       the RAM footprint:
+
+         CONFIG_ARCH_INTERRUPTSTACK=2048
+         CONFIG_IDLETHREAD_STACKSIZE=1024
+         CONFIG_USERMAIN_STACKSIZE=2048
+         CONFIG_PTHREAD_STACK_DEFAULT=2048
+         ... and others ...
+
+    2. NSH built-in applications are supported.
+
+       Binary Formats:
+         CONFIG_BUILTIN=y                    : Enable support for built-in programs
+
+       Application Configuration:
+         CONFIG_NSH_BUILTIN_APPS=y           : Enable starting apps from NSH command line