SAMA5 NAND: Basic NAND access now work (software ECC and no DMA)

1 files changed, 964 insertions, 1050 deletions

diff --git a/nuttx/configs/sama5d3x-ek/README.txt b/nuttx/configs/sama5d3x-ek/README.txt
index 060bbe601..115d4934b 100644
--- a/nuttx/configs/sama5d3x-ek/README.txt
+++ b/nuttx/configs/sama5d3x-ek/README.txt
@@ -73,15 +73,22 @@ Contents
   - Creating and Using NORBOOT
   - Buttons and LEDs
   - Serial Consoles
-  - Serial FLASH
+  - Networking
+  - AT25 Serial FLASH
   - HSMCI Card Slots
   - USB Ports
+  - USB High-Speed Device
+  - USB High-Speed Host
   - SDRAM Support
   - NAND Support
   - AT24 Serial EEPROM
+  - I2C Tool
   - CAN Usage
   - SAMA5 ADC Support
   - SAMA5 PWM Support
+  - RTC
+  - Watchdog Timer
+  - TRNG and /dev/random
   - OV2640 Camera Interface
   - I2S Audio Support
   - SAMA5D3x-EK Configuration Options
@@ -429,8 +436,13 @@ Creating and Using NORBOOT
       sequence has been most convenient for me since it allows me to
       step into the program in NOR.
 
+   7. An option is to use the SAM-BA tool to write the NORBOOT image into
+      Serial FLASH.  Then, the system will boot from Serial FLASH by
+      copying the NORBOOT image in SRAM which will run and then start the
+      image in NOR FLASH automatically.
+
     STATUS:
-      2013-7-30:  I have been unable to execute this configuration from NOR
+      2013-7-30:  I have been unable to execute these configurations from NOR
         FLASH by closing the BMS jumper (J9).  As far as I can tell, this
         jumper does nothing on my board???  So I have been using the norboot
         configuration exclusively to start the program-under-test in NOR FLASH.
@@ -534,8 +546,190 @@ Serial Consoles
     - Jumper JP16 not fitted: CDC is enabled
     - Jumper JP16 fitted : CDC is disabled"
 
-Serial FLASH
-============
+Networking
+==========
+
+  Networking support via the can be added to NSH by selecting the following
+  configuration options.  The SAMA5D3x supports two different Ethernet MAC
+  peripherals:  (1) The 10/100Base-T EMAC peripheral and (2) the
+  10/100/1000Base-T GMAC peripheral.  Only the SAMA5D31 and SAMAD35 support
+  the EMAC peripheral; Only the SAMA5D33, SAMA5D34, and SAMA5D35 support
+  the GMAC perpheral!  NOTE that the SAMA5D35 supports both!
+
+  Selecting the EMAC peripheral
+  -----------------------------
+
+  System Type
+    CONFIG_ARCH_CHIP_ATSAMA5D31=y       : SAMA5D31 or SAMAD35 support EMAC
+    CONFIG_ARCH_CHIP_ATSAMA5D35=y       : (others do not)
+
+  System Type -> SAMA5 Peripheral Support
+    CONFIG_SAMA5_EMAC=y                 : Enable the EMAC peripheral
+
+  System Type -> EMAC device driver options
+    CONFIG_SAMA5_EMAC_NRXBUFFERS=16     : Set aside some RS and TX buffers
+    CONFIG_SAMA5_EMAC_NTXBUFFERS=4
+    CONFIG_SAMA5_EMAC_PHYADDR=1         : KSZ8051 PHY is at address 1
+    CONFIG_SAMA5_EMAC_AUTONEG=y         : Use autonegotiation
+    CONFIG_SAMA5_EMAC_RMII=y            : Either MII or RMII interface should work
+    CONFIG_SAMA5_EMAC_PHYSR=30          : Address of PHY status register on KSZ8051
+    CONFIG_SAMA5_EMAC_PHYSR_ALTCONFIG=y : Needed for KSZ8051
+    CONFIG_SAMA5_EMAC_PHYSR_ALTMODE=0x7 : "    " " " "     "
+    CONFIG_SAMA5_EMAC_PHYSR_10HD=0x1    : "    " " " "     "
+    CONFIG_SAMA5_EMAC_PHYSR_100HD=0x2   : "    " " " "     "
+    CONFIG_SAMA5_EMAC_PHYSR_10FD=0x5    : "    " " " "     "
+    CONFIG_SAMA5_EMAC_PHYSR_100FD=0x6   : "    " " " "     "
+
+  PHY selection.  Later in the configuration steps, you will need to select
+  the KSZ8051 PHY for EMAC (See below)
+
+  Selecting the GMAC peripheral
+  -----------------------------
+
+  System Type
+    CONFIG_ARCH_CHIP_ATSAMA5D33=y       : SAMA5D31, SAMA5D33 and SAMAD35
+    CONFIG_ARCH_CHIP_ATSAMA5D34=y       : support GMAC (others do not)
+    CONFIG_ARCH_CHIP_ATSAMA5D35=y       :
+
+  System Type -> SAMA5 Peripheral Support
+    CONFIG_SAMA5_GMAC=y                 : Enable the GMAC peripheral
+
+  System Type -> GMAC device driver options
+    CONFIG_SAMA5_GMAC_NRXBUFFERS=16     : Set aside some RS and TX buffers
+    CONFIG_SAMA5_GMAC_NTXBUFFERS=4
+    CONFIG_SAMA5_GMAC_PHYADDR=1         : KSZ8051 PHY is at address 1
+    CONFIG_SAMA5_GMAC_AUTONEG=y         : Use autonegotiation
+
+  If both EMAC and GMAC are selected, you will also need:
+
+    CONFIG_SAMA5_GMAC_ISETH0=y          : GMAC is "eth0"; EMAC is "eth1"
+
+  PHY selection.  Later in the configuration steps, you will need to select
+  the  KSZ9021/31 PHY for GMAC (See below)
+
+  Common configuration settings
+  -----------------------------
+
+  Networking Support
+    CONFIG_NET=y                        : Enable Neworking
+    CONFIG_NET_SOCKOPTS=y               : Enable socket operations
+    CONFIG_NET_BUFSIZE=562              : Maximum packet size (MTD) 1518 is more standard
+    CONFIG_NET_RECEIVE_WINDOW=562       : Should be the same as CONFIG_NET_BUFSIZE
+    CONFIG_NET_TCP=y                    : Enable TCP/IP networking
+    CONFIG_NET_TCPBACKLOG=y             : Support TCP/IP backlog
+    CONFIG_NET_TCP_READAHEAD_BUFSIZE=562  Read-ahead buffer size
+    CONFIG_NET_UDP=y                    : Enable UDP networking
+    CONFIG_NET_ICMP=y                   : Enable ICMP networking
+    CONFIG_NET_ICMP_PING=y              : Needed for NSH ping command
+                                        : Defaults should be okay for other options
+  Device drivers -> Network Device/PHY Support
+    CONFIG_NETDEVICES=y                 : Enabled PHY selection
+    CONFIG_ETH0_PHY_KSZ8051=y           : Select the KSZ8051 PHY (for EMAC), OR
+    CONFIG_ETH0_PHY_KSZ90x1=y           : Select teh KSZ9021/31 PHY (for GMAC)
+
+  Application Configuration -> Network Utilities
+    CONFIG_NETUTILS_RESOLV=y            : Enable host address resolution
+    CONFIG_NETUTILS_TELNETD=y           : Enable the Telnet daemon
+    CONFIG_NETUTILS_TFTPC=y             : Enable TFTP data file transfers for get and put commands
+    CONFIG_NETUTILS_UIPLIB=y            : Network library support is needed
+    CONFIG_NETUTILS_WEBCLIENT=y         : Needed for wget support
+                                        : Defaults should be okay for other options
+  Application Configuration -> NSH Library
+    CONFIG_NSH_TELNET=y                 : Enable NSH session via Telnet
+    CONFIG_NSH_IPADDR=0x0a000002        : Select an IP address
+    CONFIG_NSH_DRIPADDR=0x0a000001      : IP address of gateway/host PC
+    CONFIG_NSH_NETMASK=0xffffff00       : Netmask
+    CONFIG_NSH_NOMAC=y                  : Need to make up a bogus MAC address
+                                        : Defaults should be okay for other options
+
+  Using the network with NSH
+  --------------------------
+
+  So what can you do with this networking support?  First you see that
+  NSH has several new network related commands:
+
+    ifconfig, ifdown, ifup:  Commands to help manage your network
+    get and put:             TFTP file transfers
+    wget:                    HTML file transfers
+    ping:                    Check for access to peers on the network
+    Telnet console:          You can access the NSH remotely via telnet.
+
+  You can also enable other add on features like full FTP or a Web
+  Server or XML RPC and others.  There are also other features that
+  you can enable like DHCP client (or server) or network name
+  resolution.
+
+  By default, the IP address of the SAMA5D3x-EK will be 10.0.0.2 and
+  it will assume that your host is the gateway and has the IP address
+  10.0.0.1.
+
+    nsh> ifconfig
+    eth0    HWaddr 00:e0:de:ad:be:ef at UP
+            IPaddr:10.0.0.2 DRaddr:10.0.0.1 Mask:255.255.255.0
+
+  You can use ping to test for connectivity to the host (Careful,
+  Window firewalls usually block ping-related ICMP traffic).  On the
+  target side, you can:
+
+    nsh> ping 10.0.0.1
+    PING 10.0.0.1 56 bytes of data
+    56 bytes from 10.0.0.1: icmp_seq=1 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=2 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=3 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=4 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=5 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=6 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=7 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=8 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=9 time=0 ms
+    56 bytes from 10.0.0.1: icmp_seq=10 time=0 ms
+    10 packets transmitted, 10 received, 0% packet loss, time 10100 ms
+
+  NOTE: In this configuration is is normal to have packet loss > 0%
+  the first time you ping due to the default handling of the ARP
+  table.
+
+  On the host side, you should also be able to ping the SAMA5D3-EK:
+
+    $ ping 10.0.0.2
+
+  You can also log into the NSH from the host PC like this:
+
+    $ telnet 10.0.0.2
+    Trying 10.0.0.2...
+    Connected to 10.0.0.2.
+    Escape character is '^]'.
+    sh_telnetmain: Session [3] Started
+
+    NuttShell (NSH) NuttX-6.31
+    nsh> help
+    help usage:  help [-v] [<cmd>]
+
+      [           echo        ifconfig    mkdir       mw          sleep
+      ?           exec        ifdown      mkfatfs     ping        test
+      cat         exit        ifup        mkfifo      ps          umount
+      cp          free        kill        mkrd        put         usleep
+      cmp         get         losetup     mh          rm          wget
+      dd          help        ls          mount       rmdir       xd
+      df          hexdump     mb          mv          sh
+
+    Builtin Apps:
+    nsh>
+
+  NOTE:  If you enable this feature, you experience a delay on booting.
+  That is because the start-up logic waits for the network connection
+  to be established before starting NuttX.  In a real application, you
+  would probably want to do the network bringup on a separate thread
+  so that access to the NSH prompt is not delayed.
+
+  This delay will be especially long if the board is not connected to
+  a network.
+
+AT25 Serial FLASH
+=================
+
+  Connections
+  -----------
 
   Both the Ronetix and Embest versions of the SAMAD3x CPU modules include an
   Atmel AT25DF321A, 32-megabit, 2.7-volt SPI serial flash.  The SPI
@@ -553,9 +747,69 @@ Serial FLASH
   PD13; on the Ronetix schematic, JP11 seems only to bypass a resistor (may
   not be populated?).  I think closing JP1 is correct in either case.
 
+  Configuration
+  -------------
+
+  The Embest or Ronetix CPU module includes an Atmel AT25DF321A, 32-megabit,
+  2.7-volt SPI serial flash.  Support for that serial FLASH can be enabled
+  in these configurations.  These are the relevant  configuration settings:
+
+    System Type -> SAMA5 Peripheral Support
+      CONFIG_SAMA5_SPI0=y                   : Enable SPI0
+      CONFIG_SAMA5_DMAC0=y                  : Enable DMA controller 0
+
+    System Type -> SPI device driver options
+      CONFIG_SAMA5_SPI_DMA=y                : Use DMA for SPI transfers
+      CONFIG_SAMA5_SPI_DMATHRESHOLD=4       : Don't DMA for small transfers
+
+    Device Drivers -> SPI Driver Support
+      CONFIG_SPI=y                          : Enable SPI support
+      CONFIG_SPI_EXCHANGE=y                 : Support the exchange method
+
+    Device Drivers -> Memory Technology Device (MTD) Support
+      CONFIG_MTD=y                          : Enable MTD support
+      CONFIG_MTD_AT25=y                     : Enable the AT25 driver
+      CONFIG_AT25_SPIMODE=0                 : Use SPI mode 0
+      CONFIG_AT25_SPIFREQUENCY=10000000     : Use SPI frequency 10MHz
+
+  The AT25 is capable of higher SPI rates than this.  I have not experimented
+  a lot, but at 20MHz, the behavior is not the same with all CM modules.  This
+  lower rate gives more predictable performance.
+
+    Application Configuration -> NSH Library
+      CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
+
+    Board Selection
+      CONFIG_SAMA5_AT25_AUTOMOUNT=y         : Mounts AT25 for NSH
+      CONFIG_SAMA5_AT25_FTL=y               : Create block driver for FAT
+
+  NOTE that you must close JP1 on the Embest/Ronetix board in order to
+  enable the AT25 FLASH chip select.
+
+  You can then format the AT25 FLASH for a FAT file system and mount the
+  file system at /mnt/at25 using these NSH commands:
+
+    nsh> mkfatfs /dev/mtdblock0
+    nsh> mount -t vfat /dev/mtdblock0 /mnt/at25
+
+  Then you an use the FLASH as a normal FAT file system:
+
+    nsh> echo "This is a test" >/mnt/at25/atest.txt
+    nsh> ls -l /mnt/at25
+    /mnt/at25:
+     -rw-rw-rw-      16 atest.txt
+    nsh> cat /mnt/at25/atest.txt
+    This is a test
+
+  NOTE:  It appears that if Linux runs out of NAND, it will destroy the
+  contents of the AT25.
+
 HSMCI Card Slots
 ================
 
+  Physical Slots
+  --------------
+
   The SAMA5D3x-EK provides a two SD memory card slots:  (1) a full size SD
   card slot (J7 labeled MCI0), and (2) a microSD memory card slot (J6
   labeled MCI1).
@@ -589,6 +843,84 @@ HSMCI Card Slots
     PB24  MCI1_CK
     PB19  MCI1_CDA
 
+  Configuration Settings
+  ----------------------
+
+  Enabling HSMCI support. The SAMA5D3x-EK provides a two SD memory card
+  slots:  (1) a full size SD card slot (J7 labeled MCI0), and (2) a
+  microSD memory card slot (J6 labeled MCI1).  The full size SD card slot
+  connects via HSMCI0; the microSD connects vi HSMCI1.  Supportfor both SD
+  slots can be enabled with the following settings:
+
+    System Type->ATSAMA5 Peripheral Support
+      CONFIG_SAMA5_HSMCI0=y                 : Enable HSMCI0 support
+      CONFIG_SAMA5_HSMCI1=y                 : Enable HSMCI1 support
+      CONFIG_SAMA5_DMAC0=y                  : DMAC0 is needed by HSMCI0
+      CONFIG_SAMA5_DMAC1=y                  : DMAC1 is needed by HSMCI1
+
+    System Type
+      CONFIG_SAMA5_PIO_IRQ=y                : PIO interrupts needed
+      CONFIG_SAMA5_PIOD_IRQ=y               : Card detect pins are on PIOD
+
+    Device Drivers -> MMC/SD Driver Support
+      CONFIG_MMCSD=y                        : Enable MMC/SD support
+      CONFIG_MMSCD_NSLOTS=1                 : One slot per driver instance
+      CONFIG_MMCSD_HAVECARDDETECT=y         : Supports card-detect PIOs
+      CONFIG_MMCSD_MMCSUPPORT=n             : Interferes with some SD cards
+      CONFIG_MMCSD_SPI=n                    : No SPI-based MMC/SD support
+      CONFIG_MMCSD_SDIO=y                   : SDIO-based MMC/SD support
+      CONFIG_SDIO_DMA=y                     : Use SDIO DMA
+      CONFIG_SDIO_BLOCKSETUP=y              : Needs to know block sizes
+
+    Library Routines
+      CONFIG_SCHED_WORKQUEUE=y              : Driver needs work queue support
+
+    Application Configuration -> NSH Library
+      CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
+
+    Using the SD card
+    -----------------
+
+    1) After booting, the HSCMI devices will appear as /dev/mmcsd0
+       and /dev/mmcsd1.
+
+    2) If you try mounting an SD card with nothing in the slot, the
+       mount will fail:
+
+         nsh> mount -t vfat /dev/mmcsd1 /mnt/sd1
+         nsh: mount: mount failed: 19
+
+       NSH can be configured to provide errors as strings instead of
+       numbers.  But in this case, only the error number is reported.  The
+       error numbers can be found in nuttx/include/errno.h:
+
+         #define ENODEV              19
+         #define ENODEV_STR          "No such device"
+
+       So the mount command is saying that there is no device or, more
+       correctly, that there is no card in the SD card slot.
+
+    3) Inserted the SD card.  Then the mount should succeed.
+
+        nsh> mount -t vfat /dev/mmcsd1 /mnt/sd1
+        nsh> ls /mnt/sd1
+        /mnt/sd1:
+         atest.txt
+        nsh> cat /mnt/sd1/atest.txt
+        This is a test
+
+    4) Before removing the card, you must umount the file system.  This is
+       equivalent to "ejecting" or "safely removing" the card on Windows:  It
+       flushes any cached data to the card and makes the SD card unavailable
+       to the applications.
+
+         nsh> umount -t /mnt/sd1
+
+       It is now safe to remove the card.  NuttX provides into callbacks
+       that can be used by an application to automatically unmount the
+       volume when it is removed.  But those callbacks are not used in
+       these configurations.
+
 USB Ports
 =========
 
@@ -642,8 +974,312 @@ USB Ports
     ---- ----------- -------------------------------------------------------
     PD28 OVCUR_USB   Combined overrcurrent indication from port A and B
 
+USB High-Speed Device
+=====================
+
+  Basic USB High-Speed Device Configuration
+  -----------------------------------------
+
+  Support the USB high-speed device (UDPHS) driver can be enabled with these
+  NuttX configuration settings.
+
+    Device Drivers -> USB Device Driver Support
+      CONFIG_USBDEV=y                       : Enable USB device support
+      CONFIG_USBDEV_DUALSPEED=y             : Device support High and Full Speed
+      CONFIG_USBDEV_DMA=y                   : Device uses DMA
+
+    System Type -> ATSAMA5 Peripheral Support
+      CONFIG_SAMA5_UDPHS=y                  : Enable UDPHS High Speed USB device
+
+    Application Configuration -> NSH Library
+      CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
+
+  Mass Storage Class
+  ------------------
+
+  The Mass Storage Class (MSC) class driver is selected for use with
+  UDPHS:
+
+    Device Drivers -> USB Device Driver Support
+      CONFIG_USBMSC=y                       : Enable the USB MSC class driver
+      CONFIG_USBMSC_EPBULKOUT=1             : Use EP1 for the BULK OUT endpoint
+      CONFIG_USBMSC_EPBULKIN=2              : Use EP2 for the BULK IN endpoint
+
+  The following setting enables an add-on that can can be used to control
+  the USB MSC device.  It will add two new NSH commands:
+
+    a. msconn will connect the USB serial device and export the AT25
+       to the host, and
+    b. msdis which will disconnect the USB serial device.
+
+    Application Configuration -> System Add-Ons:
+      CONFIG_SYSTEM_USBMSC=y                : Enable the USBMSC add-on
+      CONFIG_SYSTEM_USBMSC_NLUNS=1          : One LUN
+      CONFIG_SYSTEM_USBMSC_DEVMINOR1=0      : Minor device zero
+      CONFIG_SYSTEM_USBMSC_DEVPATH1="/dev/mtdblock0"
+                                            : Use a single, LUN:  The AT25
+                                            : block driver.
+
+    NOTES:
+
+    a. To prevent file system corruption, make sure that the AT25 is un-
+       mounted *before* exporting the mass storage device to the host:
+
+         nsh> umount /mnt/at25
+         nsh> mscon
+
+       The AT25 can be re-mounted after the mass storage class is disconnected:
+
+        nsh> msdis
+        nsh> mount -t vfat /dev/mtdblock0 /mnt/at25
+
+    b. If you change the value CONFIG_SYSTEM_USBMSC_DEVPATH1, then you
+       can export other file systems:
+
+        "/dev/mmcsd1" will export the HSMCI1 microSD
+        "/dev/mmcsd0" will export the HSMCI0 full-size SD slot
+        "/dev/ram0" could even be used to export a RAM disk.  But you would
+          first have to use mkrd to create the RAM disk and mkfatfs to put
+          a FAT file system on it.
+
+  CDC/ACM Serial Device Class
+  ---------------------------
+
+  This will select the CDC/ACM serial device.  Defaults for the other
+  options should be okay.
+
+    Device Drivers -> USB Device Driver Support
+      CONFIG_CDCACM=y                       : Enable the CDC/ACM device
+      CONFIG_CDCACM_BULKIN_REQLEN=768       : Default too small for high-speed
+
+  The following setting enables an example that can can be used to control
+  the CDC/ACM device.  It will add two new NSH commands:
+
+    a. sercon will connect the USB serial device (creating /dev/ttyACM0), and
+    b. serdis which will disconnect the USB serial device (destroying
+        /dev/ttyACM0).
+
+    Application Configuration -> Examples:
+      CONFIG_SYSTEM_CDCACM=y              : Enable an CDC/ACM example
+
+  Debugging USB Device
+  --------------------
+
+  There is normal console debug output available that can be enabled with
+  CONFIG_DEBUG + CONFIG_DEBUG_USB.  However, USB device operation is very
+  time critical and enabling this debug ouput WILL interfere with the
+  operation of the UDPHS.  USB device tracing is a less invasive way to get
+  debug information:  If tracing is enabled, the USB device will save
+  encoded trace output in in-memory buffer; if the USB monitor is also
+  enabled, that trace buffer will be periodically emptied and dumped to the
+  system logging device (the serial console in this configuration):
+
+    Device Drivers -> "USB Device Driver Support:
+      CONFIG_USBDEV_TRACE=y                   : Enable USB trace feature
+      CONFIG_USBDEV_TRACE_NRECORDS=256        : Buffer 256 records in memory
+      CONFIG_USBDEV_TRACE_STRINGS=y           : (optional)
+
+    Application Configuration -> NSH LIbrary:
+      CONFIG_NSH_USBDEV_TRACE=n               : No builtin tracing from NSH
+      CONFIG_NSH_ARCHINIT=y                   : Automatically start the USB monitor
+
+    Application Configuration -> System NSH Add-Ons:
+      CONFIG_SYSTEM_USBMONITOR=y              : Enable the USB monitor daemon
+      CONFIG_SYSTEM_USBMONITOR_STACKSIZE=2048 : USB monitor daemon stack size
+      CONFIG_SYSTEM_USBMONITOR_PRIORITY=50    : USB monitor daemon priority
+      CONFIG_SYSTEM_USBMONITOR_INTERVAL=1     : Dump trace data every second
+      CONFIG_SYSTEM_USBMONITOR_TRACEINIT=y    : Enable TRACE output
+      CONFIG_SYSTEM_USBMONITOR_TRACECLASS=y
+      CONFIG_SYSTEM_USBMONITOR_TRACETRANSFERS=y
+      CONFIG_SYSTEM_USBMONITOR_TRACECONTROLLER=y
+      CONFIG_SYSTEM_USBMONITOR_TRACEINTERRUPTS=y
+
+  NOTE: If USB debug output is also enabled, both outpus will appear on the
+  serial console.  However, the debug output will be asynchronous with the
+  trace output and, hence, difficult to interpret.
+
+USB High-Speed Host
+===================
+
+  OHCI Only
+  ---------
+
+  Support the USB low/full-speed OHCI host driver can be enabled by changing
+  the NuttX configuration file as follows:
+
+    System Type -> ATSAMA5 Peripheral Support
+      CONFIG_SAMA5_UHPHS=y                 : USB Host High Speed
+
+    System Type -> USB High Speed Host driver options
+      CONFIG_SAMA5_OHCI=y                  : Low/full-speed OHCI support
+                                           : Defaults for values probably OK
+    Device Drivers
+      CONFIG_USBHOST=y                     : Enable USB host support
+
+    Device Drivers -> USB Host Driver Support
+      CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not used
+      CONFIG_USBHOST_MSC=y                 : Enable the mass storage class driver
+      CONFIG_USBHOST_HIDKBD=y              : Enable the HID keyboard class driver
+
+    Library Routines
+      CONFIG_SCHED_WORKQUEUE=y             : Worker thread support is required
+
+    Application Configuration -> NSH Library
+      CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
+
+  NOTE:  When OHCI is selected, the SAMA5 will operate at 384MHz instead of
+  396MHz.  This is so that the PLL generates a frequency which is a multiple
+  of the 48MHz needed for OHCI.  The delay loop calibration values that are
+  used will be off slightly because of this.
+
+  EHCI
+  ----
+
+  Support the USB high-speed EHCI host driver can be enabled by changing the
+  NuttX configuration file as follows.  If EHCI is enabled by itself, then
+  only high-speed devices can be supported.  If OHCI is also enabled, then
+  all low-, full-, and high speed devices will work.
+
+    System Type -> ATSAMA5 Peripheral Support
+      CONFIG_SAMA5_UHPHS=y                 : USB Host High Speed
+
+    System Type -> USB High Speed Host driver options
+      CONFIG_SAMA5_EHCI=y                  : High-speed EHCI support
+      CONFIG_SAMA5_OHCI=y                  : Low/full-speed OHCI support
+                                               : Defaults for values probably OK for both
+    Device Drivers
+      CONFIG_USBHOST=y                     : Enable USB host support
+      CONFIG_USBHOST_INT_DISABLE=y         : Interrupt endpoints not needed
+      CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not needed
+
+    Device Drivers -> USB Host Driver Support
+      CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not used
+      CONFIG_USBHOST_MSC=y                 : Enable the mass storage class driver
+      CONFIG_USBHOST_HIDKBD=y              : Enable the HID keyboard class driver
+
+    Library Routines
+      CONFIG_SCHED_WORKQUEUE=y             : Worker thread support is required
+
+    Application Configuration -> NSH Library
+      CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
+
+  Mass Storage Device Usage
+  -------------------------
+
+  Example Usage:
+
+    NuttShell (NSH) NuttX-6.29
+    nsh> ls /dev
+     /dev:
+     console
+     mtdblock0
+     null
+     ttyS0
+
+  Here a USB FLASH stick is inserted.  Nothing visible happens in the
+  shell.  But a new device will appear:
+
+    nsh> ls /dev
+    /dev:
+     console
+     mtdblock0
+     null
+     sda
+     ttyS0
+    nsh> mount -t vfat /dev/sda /mnt/sda
+    nsh> ls -l /mnt/sda
+    /mnt/sda:
+     -rw-rw-rw-    8788 viminfo
+     drw-rw-rw-       0 .Trash-1000/
+     -rw-rw-rw-    3378 zmodem.patch
+     -rw-rw-rw-    1503 sz-1.log
+     -rw-rw-rw-     613 .bashrc
+
+  HID Keyboard Usage
+  ------------------
+
+  If a (supported) USB keyboard is connected, a /dev/kbda device will appear:
+
+    nsh> ls /dev
+    /dev:
+     console
+     kbda
+     mtdblock0
+     null
+     ttyS0
+
+  /dev/kbda is a read-only serial device.  Reading from /dev/kbda will get
+  keyboard input as ASCII data (other encodings are possible):
+
+    nsh> cat /dev/kbda
+
+  Debugging USB Host
+  ------------------
+
+  There is normal console debug output available that can be enabled with
+  CONFIG_DEBUG + CONFIG_DEBUG_USB.  However, USB host operation is very time
+  critical and enabling this debug output might interfere with the operation
+  of the UDPHS.  USB host tracing is a less invasive way to get debug
+  information:  If tracing is enabled, the USB host will save encoded trace
+  output in in-memory buffer; if the USB monitor is also enabled, that trace
+  buffer will be periodically emptied and dumped to the system logging device
+  (the serial console in this configuration):
+
+    Device Drivers -> "USB Host Driver Support:
+      CONFIG_USBHOST_TRACE=y                   : Enable USB host trace feature
+      CONFIG_USBHOST_TRACE_NRECORDS=256        : Buffer 256 records in memory
+      CONFIG_USBHOST_TRACE_VERBOSE=y           : Buffer everything
+
+    Application Configuration -> NSH LIbrary:
+      CONFIG_NSH_USBDEV_TRACE=n               : No builtin tracing from NSH
+      CONFIG_NSH_ARCHINIT=y                   : Automatically start the USB monitor
+
+    Application Configuration -> System NSH Add-Ons:
+      CONFIG_SYSTEM_USBMONITOR=y              : Enable the USB monitor daemon
+      CONFIG_SYSTEM_USBMONITOR_STACKSIZE=2048 : USB monitor daemon stack size
+      CONFIG_SYSTEM_USBMONITOR_PRIORITY=50    : USB monitor daemon priority
+      CONFIG_SYSTEM_USBMONITOR_INTERVAL=1     : Dump trace data every second
+
+  NOTE: If USB debug output is also enabled, both outpus will appear on the
+  serial console.  However, the debug output will be asynchronous with the
+  trace output and, hence, difficult to interpret.
+
+NOR FLASH Support
+=================
+
+  Most of these configurations execute out of CS0 NOR flash and can only be
+  loaded via SAM-BA.  These are the relevant configuration options the
+  define the NOR FLASH configuration:
+
+    CONFIG_SAMA5_BOOT_CS0FLASH=y            : Boot from FLASH on CS0
+    CONFIG_BOOT_RUNFROMFLASH=y              : Run in place on FLASH (vs copying to RAM)
+
+    CONFIG_SAMA5_EBICS0=y                   : Enable CS0 external memory
+    CONFIG_SAMA5_EBICS0_SIZE=134217728      : Memory size is 128KB
+    CONFIG_SAMA5_EBICS0_NOR=y               : Memory type is NOR FLASH
+
+    CONFIG_FLASH_START=0x10000000           : Physical FLASH start address
+    CONFIG_FLASH_VSTART=0x10000000          : Virtual FLASH start address
+    CONFIG_FLASH_SIZE=134217728             : FLASH size (again)
+
+    CONFIG_RAM_START=0x00300400             : Data stored after page table
+    CONFIG_RAM_VSTART=0x00300400
+    CONFIG_RAM_SIZE=114688                  : Available size of 128KB - 16KB for page table
+
+  NOTE:  In order to boot in this configuration, you need to close the BMS
+  jumper.
+
+  STATUS:  I have been unable to execute these configurations from NOR FLASH
+  by closing the BMS jumper (J9).  As far as I can tell, this jumper does
+  nothing on my board???  So I have been using the norboot configuration
+  exclusively to start the program-under-test in NOR FLASH (see below).
+
 SDRAM Support
 =============
+
+  Configuration
+  -------------
+
   In these configurations, .data and .bss are retained in ISRAM.  SDRAM can
   be initialized and included in the heap.  Relevant configuration settings:
 
@@ -664,9 +1300,53 @@ SDRAM Support
     Memory Management
       CONFIG_MM_REGIONS=2                   : Two heap memory regions:  ISRAM and SDRAM
 
+  RAM Test
+  --------
+
+  Another thing you could do is to enable the RAM test built-in application.
+  You can enable the NuttX RAM test that may be used to verify the external
+  SDRAM.  To do this, keep the SDRAM out of the heap so that it can be tested
+  without crashing programs using the memory:
+
+    System Type->Heap Configuration
+      CONFIG_SAMA5_DDRCS_HEAP=n             : Don't add the SDRAM to the heap
+
+    Memory Management
+      CONFIG_MM_REGIONS=1                   : One memory regions:  ISRAM
+
+  Then enable the RAM test built-in application:
+
+    Application Configuration->System NSH Add-Ons->Ram Test
+      CONFIG_SYSTEM_RAMTEST=y
+
+  In this configuration, the SDRAM is not added to heap and so is not
+  accessable to the applications.  So the RAM test can be freely executed
+  against the SRAM memory beginning at address 0x2000:0000 (DDR CS):
+
+    nsh> ramtest -h
+    Usage: <noname> [-w|h|b] <hex-address> <decimal-size>
+
+    Where:
+      <hex-address> starting address of the test.
+      <decimal-size> number of memory locations (in bytes).
+      -w Sets the width of a memory location to 32-bits.
+      -h Sets the width of a memory location to 16-bits (default).
+      -b Sets the width of a memory location to 8-bits.
+
+    To test the entire external 256MB SRAM:
+
+    nsh> ramtest -w 20000000 268435456
+    RAMTest: Marching ones: 20000000 268435456
+    RAMTest: Marching zeroes: 20000000 268435456
+    RAMTest: Pattern test: 20000000 268435456 55555555 aaaaaaaa
+    RAMTest: Pattern test: 20000000 268435456 66666666 99999999
+    RAMTest: Pattern test: 20000000 268435456 33333333 cccccccc
+    RAMTest: Address-in-address test: 20000000 268435456
+
 NAND Support
 ============
-  NAND Support can be added to the the NSH configuration by modifying the
+
+  NAND Support can be added to the NSH configuration by modifying the
   NuttX configuration file as follows:
 
     System Type -> SAMA5 Peripheal support
@@ -708,9 +1388,18 @@ NAND Support
       bad blocks and only NXFFS performs wear-leveling.
 
       NOTE:  NXFFS is very slow.  The first time that you start the system,
-      be prepared for a long wait.  I have lots of debug on so I don't know
-      what the optimized wait will be.  But with debug ON, the wait is in
-      units of hours.
+      be prepared for a long wait; NXFFS will need to scan the entire NAND,
+      erase it, reformat, and rescan the NAND.  I have lots of debug on so I
+      don't know what the optimized wait would be.  But with debug ON,
+      software ECC, and no DMA the wait is in many tens of minutes, perhaps
+      hours.
+
+      On subsequent boots, after the NXFFS file system has been created,
+      the boot time can still be substantial.  This is because NXFFS needs
+      to scan the entire NAND device and build the in-memory dataset need
+      to access NAND.  It is recommended you create a separated thread at
+      boot time to bring up NXFFS so that you don't delay the boot-to-prompt
+      time excessively.
 
       NOTE:  There is another NXFFS related issue:  When the FLASH is
       fully used, NXFFS will restructure the entire FLASH, the delay to
@@ -719,12 +1408,26 @@ NAND Support
       does the job a little-at-a-time so that there is no massive clean-up
       when the FLASH becomes full.
 
+      WARNING:  This will wipe out everything that you may have on the NAND
+      FLASH!  I have found that using the JTAG with no valid image on NAND
+      or Serial FLASH is a problem:  In that case, the code always ends up
+      in the SAM-BA bootloader.
+
+      The work around for this case is to put the NORBOOT image into Serial
+      FLASH.  Then, the system will boot from Serial FLASH by copying the
+      NORBOOT image in SRAM which will run and then start the image in NOR
+      FLASH.  See the discussion of the NORBOOT configuration in the
+      "Creating and Using NORBOOT" section above.
+
     Application Configuration -> NSH Library
      CONFIG_NSH_ARCHINIT=y              : Use architecture-specific initialization
 
 AT24 Serial EEPROM
 ==================
 
+  AT24 Connections
+  ----------------
+
   A AT24C512 Serial EEPPROM was used for tested I2C.  There are other I2C/TWI
   devices on-board, but the serial EEPROM is the simplest test.
 
@@ -740,6 +1443,132 @@ AT24 Serial EEPROM
   By default, PA30 and PA31 are SWJ-DP pins, it can be used as a pin for TWI
   peripheral in the end application.
 
+  Configuration Settings
+  ----------------------
+
+  The following configuration settings were used:
+
+    System Type -> SAMA5 Peripheral Support
+      CONFIG_SAMA5_TWI0=y                   : Enable TWI0
+
+    System Type -> TWI device driver options
+      SAMA5_TWI0_FREQUENCY=100000           : Select a TWI frequency
+
+    Device Drivers -> I2C Driver Support
+      CONFIG_I2C=y                          : Enable I2C support
+      CONFIG_I2C_TRANSFER=y                 : Driver supports the transfer() method
+      CONFIG_I2C_WRITEREAD=y                : Driver supports the writeread() method
+
+    Device Drivers -> Memory Technology Device (MTD) Support
+      CONFIG_MTD=y                          : Enable MTD support
+      CONFIG_MTD_AT24XX=y                   : Enable the AT24 driver
+      CONFIG_AT24XX_SIZE=512                : Specifies the AT 24C512 part
+      CONFIG_AT24XX_ADDR=0x53               : AT24 I2C address
+
+    Application Configuration -> NSH Library
+      CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
+
+    File systems
+      CONFIG_NXFFS=y                        : Enables the NXFFS file system
+      CONFIG_NXFFS_PREALLOCATED=y           : Required
+                                            : Other defaults are probably OK
+
+    Board Selection
+      CONFIG_SAMA5_AT24_AUTOMOUNT=y         : Mounts AT24 for NSH
+      CONFIG_SAMA5_AT24_NXFFS=y             : Mount the AT24 using NXFFS
+
+  You can then format the AT24 EEPROM for a FAT file system and mount the
+  file system at /mnt/at24 using these NSH commands:
+
+    nsh> mkfatfs /dev/mtdblock0
+    nsh> mount -t vfat /dev/mtdblock0 /mnt/at24
+
+  Then you an use the FLASH as a normal FAT file system:
+
+    nsh> echo "This is a test" >/mnt/at24/atest.txt
+    nsh> ls -l /mnt/at24
+    /mnt/at24:
+     -rw-rw-rw-      16 atest.txt
+    nsh> cat /mnt/at24/atest.txt
+    This is a test
+
+I2C Tool
+========
+
+  I2C Tool. NuttX supports an I2C tool at apps/system/i2c that can be used
+  to peek and poke I2C devices.  That tool cal be enabled by setting the
+  following:
+
+    System Type -> SAMA5 Peripheral Support
+      CONFIG_SAMA5_TWI0=y                   : Enable TWI0
+      CONFIG_SAMA5_TWI1=y                   : Enable TWI1
+      CONFIG_SAMA5_TWI2=y                   : Enable TWI2
+
+    System Type -> TWI device driver options
+      SAMA5_TWI0_FREQUENCY=100000           : Select a TWI0 frequency
+      SAMA5_TWI1_FREQUENCY=100000           : Select a TWI1 frequency
+      SAMA5_TWI2_FREQUENCY=100000           : Select a TWI2 frequency
+
+    Device Drivers -> I2C Driver Support
+      CONFIG_I2C=y                          : Enable I2C support
+      CONFIG_I2C_TRANSFER=y                 : Driver supports the transfer() method
+      CONFIG_I2C_WRITEREAD=y                : Driver supports the writeread() method
+
+    Application Configuration -> NSH Library
+      CONFIG_SYSTEM_I2CTOOL=y               : Enable the I2C tool
+      CONFIG_I2CTOOL_MINBUS=0               : TWI0 has the minimum bus number 0
+      CONFIG_I2CTOOL_MAXBUS=2               : TWI2 has the maximum bus number 2
+      CONFIG_I2CTOOL_DEFFREQ=100000         : Pick a consistent frequency
+
+    The I2C tool has extensive help that can be accessed as follows:
+
+    nsh> i2c help
+    Usage: i2c <cmd> [arguments]
+    Where <cmd> is one of:
+
+      Show help     : ?
+      List busses   : bus
+      List devices  : dev [OPTIONS] <first> <last>
+      Read register : get [OPTIONS] [<repititions>]
+      Show help     : help
+      Write register: set [OPTIONS] <value> [<repititions>]
+      Verify access : verf [OPTIONS] [<value>] [<repititions>]
+
+    Where common "sticky" OPTIONS include:
+      [-a addr] is the I2C device address (hex).  Default: 03 Current: 03
+      [-b bus] is the I2C bus number (decimal).  Default: 0 Current: 0
+      [-r regaddr] is the I2C device register address (hex).  Default: 00 Current: 00
+      [-w width] is the data width (8 or 16 decimal).  Default: 8 Current: 8
+      [-s|n], send/don't send start between command and data.  Default: -n Current: -n
+      [-i|j], Auto increment|don't increment regaddr on repititions.  Default: NO Current: NO
+      [-f freq] I2C frequency.  Default: 100000 Current: 100000
+
+    NOTES:
+    o Arguments are "sticky".  For example, once the I2C address is
+      specified, that address will be re-used until it is changed.
+
+    WARNING:
+    o The I2C dev command may have bad side effects on your I2C devices.
+      Use only at your own risk.
+
+    As an example, the I2C dev comman can be used to list all devices
+    responding on TWI0 (the default) like this:
+
+      nsh> i2c dev 0x03 0x77
+          0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
+      00:          -- -- -- -- -- -- -- -- -- -- -- -- --
+      10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- --
+      20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
+      30: -- -- -- -- -- -- -- -- -- 39 -- -- -- 3d -- --
+      40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
+      50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
+      60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
+      70: -- -- -- -- -- -- -- --
+      nsh>
+
+     Address 0x1a is the WM8904.  Address 0x39 is the SIL9022A. I am not sure
+     what is at address 0x3d and 0x60
+
 CAN Usage
 =========
   I planned to verify CAN using the IXXAT USB-to-CAN Compact.  This section
@@ -1024,6 +1853,79 @@ SAMA5 PWM Support
       [-t duration] is the duration of the pulse train in seconds.  Default: 5 Current: 5
       [-h] shows this message and exits
 
+RTC
+===
+
+  The Real Time Clock/Calendar RTC) may be enabled with these settings:
+
+    System Type:
+      CONFIG_SAMA5_RTC=y                   : Enable the RTC driver
+
+    Drivers (these values will be selected automatically):
+      CONFIG_RTC=y                         : Use the RTC for system time
+      CONFIG_RTC_DATETIME=y                : RTC supports data/time
+
+  The RTC supports an alarm that may be enable with the following settings.
+  However, there is nothing in the system that currently makes use of this
+  alarm.
+
+    Drivers:
+      CONFIG_RTC_ALARM=y                   : Enable the RTC alarm
+
+    Library Routines
+      CONFIG_SCHED_WORKQUEUE=y              : Alarm needs work queue support
+
+Watchdog Timer
+==============
+
+  NSH can be configured to exercise the watchdog timer test
+  (apps/examples/watchdog).  This can be selected with the following
+  settings in the NuttX configuration file:
+
+    System Type:
+      CONFIG_SAMA5_WDT=y                  : Enable the WDT peripheral
+                                          : Defaults in "RTC Configuration" should be OK
+
+    Drivers (this will automatically be selected):
+      CONFIG_WATCHDOG=y                   : Enables watchdog timer driver support
+
+    Application Configuration -> Eamples
+      CONFIG_EXAMPLES_WATCHDOG=y          : Enable apps/examples/watchdog
+
+  The WDT timer is driven off the slow, 32768Hz clock divided by 128. As a
+  result, the watchdog a maximum timeout value of 16 seconds.  The SAMA5 WDT
+  may also only be programmed one time; the processor must be reset before
+  the WDT can be reprogrammed.
+
+  The SAMA5 always boots with the watchdog timer enabled at its maximum
+  timeout (16 seconds).  In the normal case where no watchdog timer driver
+  has been configured, the watchdog timer is disabled as part of the start
+  up logic.  But, since we are permitted only one opportunity to program
+  the WDT, we cannot disable the watchdog time if CONFIG_SAMA5_WDT=y.  So,
+  be forewarned:  You have only 16 seconds to run your watchdog timer test!
+
+  NOTE:  If you are using the norboot program to run from FLASH as I did,
+  beware that the default version also disables the watchdog.  You will
+  need a special version of norboot with CONFIG_SAMA5_WDT=y.
+
+TRNG and /dev/random
+====================
+
+  NSH can be configured to enable the SAMA5 TRNG peripheral so that it
+  provides /dev/random.  The following configuration will enable the TRNG,
+  /dev/random, and the simple test of /dev/random at apps/examples/ranadom:
+
+    System Type:
+      CONFIG_SAMA5_TRNG=y                 : Enable the TRNG peripheral
+
+    Drivers (automatically selected):
+      CONFIG_DEV_RANDOM=y                 : Enable /dev/random
+
+    Applications -> Examples
+      CONFIG_EXAMPLES_RANDOM=y            : Enable apps/examples/random
+      CONFIG_EXAMPLES_MAXSAMPLES=64       : Default settings are probably OK
+      CONFIG_EXAMPLES_NSAMPLES=8
+
 OV2640 Camera Interface
 =======================
 
@@ -1404,7 +2306,7 @@ Configurations
      See also the "NOTE about Windows native toolchains" in the section call
      "GNU Toolchain Options" above.
 
-  Configuration sub-directories
+  Configuration Sub-directories
   -----------------------------
   Summary:  Some of the descriptions below are long and wordy. Here is the
   concise summary of the available SAMA5D3x-EK configurations:
@@ -1474,344 +2376,47 @@ Configurations
        CONFIG_ARMV7A_TOOLCHAIN_CODESOURCERYW=y : CodeSourcery for Windows
 
     3. This configuration executes out of CS0 NOR flash and can only
-       be loaded via SAM-BA.  These are the relevant configuration options
-       the define the NOR FLASH configuration:
-
-       CONFIG_SAMA5_BOOT_CS0FLASH=y            : Boot from FLASH on CS0
-       CONFIG_BOOT_RUNFROMFLASH=y              : Run in place on FLASH (vs copying to RAM)
-
-       CONFIG_SAMA5_EBICS0=y                   : Enable CS0 external memory
-       CONFIG_SAMA5_EBICS0_SIZE=134217728      : Memory size is 128KB
-       CONFIG_SAMA5_EBICS0_NOR=y               : Memory type is NOR FLASH
-
-       CONFIG_FLASH_START=0x10000000           : Physical FLASH start address
-       CONFIG_FLASH_VSTART=0x10000000          : Virtual FLASH start address
-       CONFIG_FLASH_SIZE=134217728             : FLASH size (again)
-
-       CONFIG_RAM_START=0x00300400             : Data stored after page table
-       CONFIG_RAM_VSTART=0x00300400
-       CONFIG_RAM_SIZE=114688                  : Available size of 128KB - 16KB for page table
-
-       NOTE:  In order to boot in this configuration, you need to close the
-       BMS jumper.
+       be loaded via SAM-BA.  The are the relevant configuration options
+       are provided above in the section entitled "NOR FLASH Support".
 
     The following features are pre-enabled in the demo configuration, but not
     in the nsh configuration:
 
     4. SDRAM is supported.  .data and .bss is still retained in ISRAM, but
        SDRAM is intialized and the SDRAM memory is included in the heap.
-       Relevant configuration settings:
-
-       System Type->ATSAMA5 Peripheral Support
-         CONFIG_SAMA5_MPDDRC=y                 : Enable the DDR controller
-
-       System Type->External Memory Configuration
-         CONFIG_SAMA5_DDRCS=y                  : Tell the system that DRAM is at the DDR CS
-         CONFIG_SAMA5_DDRCS_SIZE=268435456     : 2Gb DRAM -> 256GB
-         CONFIG_SAMA5_DDRCS_LPDDR2=y           : Its DDR2
-         CONFIG_SAMA5_MT47H128M16RT=y          : This is the type of DDR2
+       Relevant configuration settings are provided in the paragraph entitled
+       "SDRAM Support" above.
 
-       System Type->Heap Configuration
-         CONFIG_SAMA5_DDRCS_HEAP=y             : Add the SDRAM to the heap
-         CONFIG_SAMA5_DDRCS_HEAP_OFFSET=0
-         CONFIG_SAMA5_DDRCS_HEAP_SIZE=268435456
-
-       Memory Management
-         CONFIG_MM_REGIONS=2                   : Two heap memory regions:  ISRAM and SDRAM
-
-    5. The Real Time Clock/Calendar RTC) is enabled.  These are the relevant
-       settings:
-
-        System Type:
-          CONFIG_SAMA5_RTC=y                   : Enable the RTC driver
-
-        Drivers (these values will be selected automatically):
-          CONFIG_RTC=y                         : Use the RTC for system time
-          CONFIG_RTC_DATETIME=y                : RTC supports data/time
+    5. The Real Time Clock/Calendar RTC) is enabled.  See the sectino entitled
+       "RTC" above.
 
     6. The Embest or Ronetix CPU module includes an Atmel AT25DF321A,
        32-megabit, 2.7-volt SPI serial flash.  Support for that serial
-       FLASH can is enabled in this configuration.  These are the relevant
-       configuration settings:
-
-       System Type -> SAMA5 Peripheral Support
-         CONFIG_SAMA5_SPI0=y                   : Enable SPI0
-         CONFIG_SAMA5_DMAC0=y                  : Enable DMA controller 0
-
-       System Type -> SPI device driver options
-         CONFIG_SAMA5_SPI_DMA=y                : Use DMA for SPI transfers
-         CONFIG_SAMA5_SPI_DMATHRESHOLD=4       : Don't DMA for small transfers
-
-       Device Drivers -> SPI Driver Support
-         CONFIG_SPI=y                          : Enable SPI support
-         CONFIG_SPI_EXCHANGE=y                 : Support the exchange method
-
-       Device Drivers -> Memory Technology Device (MTD) Support
-         CONFIG_MTD=y                          : Enable MTD support
-         CONFIG_MTD_AT25=y                     : Enable the AT25 driver
-         CONFIG_AT25_SPIMODE=0                 : Use SPI mode 0
-         CONFIG_AT25_SPIFREQUENCY=10000000     : Use SPI frequency 10MHz
-
-       The AT25 is capable of higher SPI rates than this.  I have not
-       experimented a lot, but at 20MHz, the behavior is not the same with
-       all CM modules.  This lower rate gives more predictable performance.
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       Board Selection
-         CONFIG_SAMA5_AT25_AUTOMOUNT=y         : Mounts AT25 for NSH
-         CONFIG_SAMA5_AT25_FTL=y               : Create block driver for FAT
-
-       NOTE that you must close JP1 on the Embest/Ronetix board in
-       order to enable the AT25 FLASH chip select.
-
-       You can then format the AT25 FLASH for a FAT file system and mount
-       the file system at /mnt/at25 using these NSH commands:
-
-         nsh> mkfatfs /dev/mtdblock0
-         nsh> mount -t vfat /dev/mtdblock0 /mnt/at25
-
-       Then you an use the FLASH as a normal FAT file system:
-
-         nsh> echo "This is a test" >/mnt/at25/atest.txt
-         nsh> ls -l /mnt/at25
-         /mnt/at25:
-          -rw-rw-rw-      16 atest.txt
-         nsh> cat /mnt/at25/atest.txt
-         This is a test
-
-       NOTE:  It appears that if Linux runs out of NAND, it will destroy the
-       contents of the AT25.
+       FLASH can is enabled in this configuration.  See the paragraph
+       entitle "AT25 Serial FLASH" for detailed configuration settings.
 
     7. Support for HSMCI car slots. The SAMA5D3x-EK provides a two SD memory
        card slots:  (1) a full size SD card slot (J7 labeled MCI0), and (2)
        a microSD memory card slot (J6 labeled MCI1).  The full size SD card
        slot connects via HSMCI0; the microSD connects vi HSMCI1.  Relevant
-       configuration settings include:
-
-       System Type->ATSAMA5 Peripheral Support
-         CONFIG_SAMA5_HSMCI0=y                 : Enable HSMCI0 support
-         CONFIG_SAMA5_HSMCI1=y                 : Enable HSMCI1 support
-         CONFIG_SAMA5_DMAC0=y                  : DMAC0 is needed by HSMCI0
-         CONFIG_SAMA5_DMAC1=y                  : DMAC1 is needed by HSMCI1
-
-       System Type
-         CONFIG_SAMA5_PIO_IRQ=y                : PIO interrupts needed
-         CONFIG_SAMA5_PIOD_IRQ=y               : Card detect pins are on PIOD
-
-       Device Drivers -> MMC/SD Driver Support
-         CONFIG_MMCSD=y                        : Enable MMC/SD support
-         CONFIG_MMSCD_NSLOTS=1                 : One slot per driver instance
-         CONFIG_MMCSD_HAVECARDDETECT=y         : Supports card-detect PIOs
-         CONFIG_MMCSD_MMCSUPPORT=n             : Interferes with some SD cards
-         CONFIG_MMCSD_SPI=n                    : No SPI-based MMC/SD support
-         CONFIG_MMCSD_SDIO=y                   : SDIO-based MMC/SD support
-         CONFIG_SDIO_DMA=y                     : Use SDIO DMA
-         CONFIG_SDIO_BLOCKSETUP=y              : Needs to know block sizes
-
-       Library Routines
-         CONFIG_SCHED_WORKQUEUE=y              : Driver needs work queue support
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       Using the SD card:
-
-       1) After booting, the HSCMI devices will appear as /dev/mmcsd0
-          and /dev/mmcsd1.
-
-       2) If you try mounting an SD card with nothing in the slot, the
-          mount will fail:
-
-            nsh> mount -t vfat /dev/mmcsd1 /mnt/sd1
-            nsh: mount: mount failed: 19
-
-          NSH can be configured to provide errors as strings instead of
-          numbers.  But in this case, only the error number is reported.
-          The  error numbers can be found in nuttx/include/errno.h:
-
-            #define ENODEV              19
-            #define ENODEV_STR          "No such device"
-
-          So the mount command is saying that there is no device or, more
-          correctly, that there is no card in the SD card slot.
-
-       3) Inserted the SD card.  Then the mount should succeed.
-
-           nsh> mount -t vfat /dev/mmcsd1 /mnt/sd1
-           nsh> ls /mnt/sd1
-           /mnt/sd1:
-            atest.txt
-           nsh> cat /mnt/sd1/atest.txt
-           This is a test
-
-       4) Before removing the card, you must umount the file system.  This
-          is equivalent to "ejecting" or "safely removing" the card on
-          Windows:  It flushes any cached data to the card and makes the SD
-          card unavailable to the applications.
-
-            nsh> umount -t /mnt/sd1
-
-          It is now safe to remove the card.  NuttX provides into callbacks
-          that can be used by an application to automatically unmount the
-          volume when it is removed.  But those callbacks are not used in
-          this configuration.
-
-    8. Support the USB high-speed device (UDPHS) driver is enabled.
-       These are the relevant NuttX configuration settings:
-
-       Device Drivers -> USB Device Driver Support
-         CONFIG_USBDEV=y                       : Enable USB device support
-         CONFIG_USBDEV_DUALSPEED=y             : Device support High and Full Speed
-         CONFIG_USBDEV_DMA=y                   : Device uses DMA
-
-       System Type -> ATSAMA5 Peripheral Support
-         CONFIG_SAMA5_UDPHS=y                  : Enable UDPHS High Speed USB device
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       The Mass Storage Class (MSC) class driver is selected for use with
-       UDPHS:
-
-       Device Drivers -> USB Device Driver Support
-         CONFIG_USBMSC=y                       : Enable the USB MSC class driver
-         CONFIG_USBMSC_EPBULKOUT=1             : Use EP1 for the BULK OUT endpoint
-         CONFIG_USBMSC_EPBULKIN=2              : Use EP2 for the BULK IN endpoint
-
-       The following setting enables an add-on that can can be used to
-       control the CDC/ACM device.  It will add two new NSH commands:
-
-         a. msconn will connect the USB serial device and export the AT25
-            to the host, and
-         b. msdis which will disconnect the USB serial device.
-
-       Application Configuration -> System Add-Ons:
-         CONFIG_SYSTEM_USBMSC=y                : Enable the USBMSC add-on
-         CONFIG_SYSTEM_USBMSC_NLUNS=1          : One LUN
-         CONFIG_SYSTEM_USBMSC_DEVMINOR1=0      : Minor device zero
-         CONFIG_SYSTEM_USBMSC_DEVPATH1="/dev/mtdblock0"
-                                               : Use a single, LUN:  The AT25
-                                               : block driver.
-
-       NOTES:
+       configuration settings can be found in the section entitle "HSMCI
+       Card Slots" above.
 
-       a. To prevent file system corruption, make sure that the AT25 is un-
-          mounted *before* exporting the mass storage device to the host:
-
-            nsh> umount /mnt/at25
-            nsh> mscon
-
-          The AT25 can be re-mounted after the mass storage class is disconnected:
-
-           nsh> msdis
-           nsh> mount -t vfat /dev/mtdblock0 /mnt/at25
-
-       b. If you change the value CONFIG_SYSTEM_USBMSC_DEVPATH1, then you
-          can export other file systems:
-
-           "/dev/mmcsd1" will export the HSMCI1 microSD
-           "/dev/mmcsd0" will export the HSMCI0 full-size SD slot
-           "/dev/ram0" could even be used to export a RAM disk.  But you would
-             first have to use mkrd to create the RAM disk and mkfatfs to put
-             a FAT file system on it.
+    8. Support the USB high-speed device (UDPHS) driver is enabled.  See the
+       section above entitled "USB High-Speed Device" for relevant NuttX
+       configuration settings.
 
     9. The USB high-speed EHCI and the low-/full- OHCI host drivers are supported
-       in this configuration.
-
-       Here are the relevant configuration options that enable EHCI support:
-
-       System Type -> ATSAMA5 Peripheral Support
-         CONFIG_SAMA5_UHPHS=y                 : USB Host High Speed
-
-       System Type -> USB High Speed Host driver options
-         CONFIG_SAMA5_EHCI=y                  : High-speed EHCI support
-         CONFIG_SAMA5_OHCI=y                  : Low/full-speed OHCI support
-                                              : Defaults for values probably OK for both
-       Device Drivers
-         CONFIG_USBHOST=y                     : Enable USB host support
-         CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not needed
-
-       Device Drivers -> USB Host Driver Support
-         CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not used
-         CONFIG_USBHOST_MSC=y                 : Enable the mass storage class driver
-         CONFIG_USBHOST_HIDKBD=y              : Enable the HID keybaord class driver
-                                              : Defaults for values probably OK for both
-
-       Library Routines
-         CONFIG_SCHED_WORKQUEUE=y             : Worker thread support is required
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       Example Usage:
-
-       NuttShell (NSH) NuttX-6.29
-       nsh> ls /dev
-        /dev:
-        console
-        mtdblock0
-        null
-        ttyS0
-
-       Here a USB FLASH stick is inserted.  Nothing visible happens in the
-       the shell.  But a new device will appear:
-
-       nsh> ls /dev
-       /dev:
-        console
-        mtdblock0
-        null
-        sda
-        ttyS0
-       nsh> mount -t vfat /dev/sda /mnt/sda
-       nsh> ls -l /mnt/sda
-       /mnt/sda:
-        -rw-rw-rw-    8788 viminfo
-        drw-rw-rw-       0 .Trash-1000/
-        -rw-rw-rw-    3378 zmodem.patch
-        -rw-rw-rw-    1503 sz-1.log
-        -rw-rw-rw-     613 .bashrc
-
-       Or, if a (supported) USB keyboard is connected, a /dev/kbda device
-       will appear:
-
-       nsh> ls /dev
-       /dev:
-        console
-        kbda
-        mtdblock0
-        null
-        ttyS0
-
-       /dev/kbda is a read-only serial device.  Reading from /dev/kbda will
-       get keyboard input as ASCII data (other encodings are possible):
-
-       nsh> cat /dev/kbda
+       in this configuration.  See the section above entitle "USB High-Speed Host"
+       for relevant configuration information.
 
     10. Support SAMA5D3 TRNG peripheral is enabled so that it provides
-        /dev/random.  The following configuration settings are relevant:
-
-        System Type:
-          CONFIG_SAMA5_TRNG=y                 : Enable the TRNG peripheral
-
-        Drivers (automatically selected):
-          CONFIG_DEV_RANDOM=y                 : Enable /dev/random
+        /dev/random.  See the section entitled "TRNG and /dev/random"
+        above for detailed configuration information.
 
     The following features are *not* enabled in the demo configuration but
     might be of some use to you:
 
-    10. The RTC supports an alarm that may be enable with the following settings.
-        However, there is nothing in the system that currently makes use of this
-        alarm.
-
-        Drivers:
-          CONFIG_RTC_ALARM=y                   : Enable the RTC alarm
-
-        Library Routines
-         CONFIG_SCHED_WORKQUEUE=y              : Alarm needs work queue support
-
     11. Debugging USB.  There is normal console debug output available that
         can be enabled with CONFIG_DEBUG + CONFIG_DEBUG_USB.  However, USB
         operation is very time critical and enabling this debug output WILL
@@ -1953,26 +2558,8 @@ Configurations
        CONFIG_ARMV7A_TOOLCHAIN_CODESOURCERYW=y : CodeSourcery for Windows
 
     3. This configuration executes out of CS0 NOR flash and can only
-       be loaded via SAM-BA.  These are the relevant configuration options
-       the define the NOR FLASH configuration:
-
-       CONFIG_SAMA5_BOOT_CS0FLASH=y            : Boot from FLASH on CS0
-       CONFIG_BOOT_RUNFROMFLASH=y              : Run in place on FLASH (vs copying to RAM)
-
-       CONFIG_SAMA5_EBICS0=y                   : Enable CS0 external memory
-       CONFIG_SAMA5_EBICS0_SIZE=134217728      : Memory size is 128KB
-       CONFIG_SAMA5_EBICS0_NOR=y               : Memory type is NOR FLASH
-
-       CONFIG_FLASH_START=0x10000000           : Physical FLASH start address
-       CONFIG_FLASH_VSTART=0x10000000          : Virtual FLASH start address
-       CONFIG_FLASH_SIZE=134217728             : FLASH size (again)
-
-       CONFIG_RAM_START=0x00300400             : Data stored after page table
-       CONFIG_RAM_VSTART=0x00300400
-       CONFIG_RAM_SIZE=114688                  : Available size of 128KB - 16KB for page table
-
-       NOTE:  In order to boot in this configuration, you need to close the
-       BMS jumper.
+       be loaded via SAM-BA.  The are the relevant configuration options
+       are provided above in the section entitled "NOR FLASH Support".
 
     4. This configuration has support for NSH built-in applications enabled.
        However, no built-in applications are selected in the base configuration.
@@ -1981,663 +2568,44 @@ Configurations
        by default, there are no block drivers intialized.  The FAT file system can
        still be used to create RAM disks.
 
-    6. SDRAM support can be enabled by adding the following to your NuttX
-       configuration file:
-
-       System Type->ATSAMA5 Peripheral Support
-         CONFIG_SAMA5_MPDDRC=y                 : Enable the DDR controller
-
-       System Type->External Memory Configuration
-         CONFIG_SAMA5_DDRCS=y                  : Tell the system that DRAM is at the DDR CS
-         CONFIG_SAMA5_DDRCS_SIZE=268435456     : 2Gb DRAM -> 256GB
-         CONFIG_SAMA5_DDRCS_LPDDR2=y           : Its DDR2
-         CONFIG_SAMA5_MT47H128M16RT=y          : This is the type of DDR2
-
-       Now that you have SDRAM enabled, what are you going to do with it?  One
-       thing you can is add it to the heap
-
-       System Type->Heap Configuration
-         CONFIG_SAMA5_DDRCS_HEAP=y             : Add the SDRAM to the heap
-         CONFIG_SAMA5_DDRCS_HEAP_OFFSET=0
-         CONFIG_SAMA5_DDRCS_HEAP_SIZE=268435456
-
-       Memory Management
-         CONFIG_MM_REGIONS=2                   : Two memory regions:  ISRAM and SDRAM
-
-       Another thing you could do is to enable the RAM test built-in
-       application:
-
-    7. You can enable the NuttX RAM test that may be used to verify the
-       external SDAM.  To do this, keep the SDRAM out of the heap so that
-       it can be tested without crashing programs using the memory:
+    6. SDRAM support can be enabled by modifying your NuttX configuration as
+       described above in the paragraph entitle "SDRAM Support"
 
-       System Type->Heap Configuration
-         CONFIG_SAMA5_DDRCS_HEAP=n             : Don't add the SDRAM to the heap
-
-       Memory Management
-         CONFIG_MM_REGIONS=1                   : One memory regions:  ISRAM
-
-       Then enable the RAM test built-in application:
-
-       Application Configuration->System NSH Add-Ons->Ram Test
-         CONFIG_SYSTEM_RAMTEST=y
-
-       In this configuration, the SDRAM is not added to heap and so is not
-       excessible to the applications.  So the RAM test can be freely
-       executed against the SRAM memory beginning at address 0x2000:0000
-       (DDR CS):
-
-       nsh> ramtest -h
-       Usage: <noname> [-w|h|b] <hex-address> <decimal-size>
-
-       Where:
-         <hex-address> starting address of the test.
-         <decimal-size> number of memory locations (in bytes).
-         -w Sets the width of a memory location to 32-bits.
-         -h Sets the width of a memory location to 16-bits (default).
-         -b Sets the width of a memory location to 8-bits.
-
-       To test the entire external 256MB SRAM:
-
-       nsh> ramtest -w 20000000 268435456
-       RAMTest: Marching ones: 20000000 268435456
-       RAMTest: Marching zeroes: 20000000 268435456
-       RAMTest: Pattern test: 20000000 268435456 55555555 aaaaaaaa
-       RAMTest: Pattern test: 20000000 268435456 66666666 99999999
-       RAMTest: Pattern test: 20000000 268435456 33333333 cccccccc
-       RAMTest: Address-in-address test: 20000000 268435456
-
-    8. The Embest or Ronetix CPU module includes an Atmel AT25DF321A,
+    7. The Embest or Ronetix CPU module includes an Atmel AT25DF321A,
        32-megabit, 2.7-volt SPI serial flash.  Support for that serial
        FLASH can be enabled by modifying the NuttX configuration as
-       follows:
-
-       System Type -> SAMA5 Peripheral Support
-         CONFIG_SAMA5_SPI0=y                   : Enable SPI0
-
-       Device Drivers -> SPI Driver Support
-         CONFIG_SPI=y                          : Enable SPI support
-         CONFIG_SPI_EXCHANGE=y                 : Support the exchange method
-
-       Device Drivers -> Memory Technology Device (MTD) Support
-         CONFIG_MTD=y                          : Enable MTD support
-         CONFIG_MTD_AT25=y                     : Enable the AT25 driver
-         CONFIG_AT25_SPIMODE=0                 : Use SPI mode 0
-         CONFIG_AT25_SPIFREQUENCY=10000000     : Use SPI frequency 10MHz
+       described above in the paragraph entitled "AT25 Serial FLASH".
 
-       The AT25 is capable of higher SPI rates than this.  I have not
-       experimented a lot, but at 20MHz, the behavior is not the same with
-       all CM modules.  This lower rate gives more predictable performance.
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       Board Selection
-         CONFIG_SAMA5_AT25_AUTOMOUNT=y         : Mounts AT25 for NSH
-         CONFIG_SAMA5_AT25_FTL=y               : Create block driver for FAT
-
-       The SPI driver can be built to do polled or DMA SPI data transfers.
-       The following additional changes will enable SPI DMA:
-
-       System Type -> SAMA5 Peripheral Support
-         CONFIG_SAMA5_DMAC0=y                   : Enable DMA controller 0
-
-       System Type -> SPI device driver options
-         CONFIG_SAMA5_SPI_DMA=y                 : Use DMA for SPI transfers
-         CONFIG_SAMA5_SPI_DMATHRESHOLD=4        : Don't DMA for small transfers
-
-       NOTE that you must close JP1 on the Embest/Ronetix board in
-       order to enable the AT25 FLASH chip select.
-
-       You can then format the AT25 FLASH for a FAT file system and mount
-       the file system at /mnt/at25 using these NSH commands:
-
-         nsh> mkfatfs /dev/mtdblock0
-         nsh> mount -t vfat /dev/mtdblock0 /mnt/at25
-
-       Then you an use the FLASH as a normal FAT file system:
-
-         nsh> echo "This is a test" >/mnt/at25/atest.txt
-         nsh> ls -l /mnt/at25
-         /mnt/at25:
-          -rw-rw-rw-      16 atest.txt
-         nsh> cat /mnt/at25/atest.txt
-         This is a test
-
-    9. Enabling HSMCI support. The SAMA5D3x-EK provides a two SD memory card
+    8. Enabling HSMCI support. The SAMA5D3x-EK provides a two SD memory card
        slots:  (1) a full size SD card slot (J7 labeled MCI0), and (2) a
        microSD memory card slot (J6 labeled MCI1).  The full size SD card
        slot connects via HSMCI0; the microSD connects vi HSMCI1.  Support
-       for both SD slots can be enabled with the following settings:
-
-       System Type->ATSAMA5 Peripheral Support
-         CONFIG_SAMA5_HSMCI0=y                 : Enable HSMCI0 support
-         CONFIG_SAMA5_HSMCI1=y                 : Enable HSMCI1 support
-         CONFIG_SAMA5_DMAC0=y                  : DMAC0 is needed by HSMCI0
-         CONFIG_SAMA5_DMAC1=y                  : DMAC1 is needed by HSMCI1
-
-       System Type
-         CONFIG_SAMA5_PIO_IRQ=y                : PIO interrupts needed
-         CONFIG_SAMA5_PIOD_IRQ=y               : Card detect pins are on PIOD
-
-       Device Drivers -> MMC/SD Driver Support
-         CONFIG_MMCSD=y                        : Enable MMC/SD support
-         CONFIG_MMSCD_NSLOTS=1                 : One slot per driver instance
-         CONFIG_MMCSD_HAVECARDDETECT=y         : Supports card-detect PIOs
-         CONFIG_MMCSD_MMCSUPPORT=n             : Interferes with some SD cards
-         CONFIG_MMCSD_SPI=n                    : No SPI-based MMC/SD support
-         CONFIG_MMCSD_SDIO=y                   : SDIO-based MMC/SD support
-         CONFIG_SDIO_DMA=y                     : Use SDIO DMA
-         CONFIG_SDIO_BLOCKSETUP=y              : Needs to know block sizes
-
-       Library Routines
-         CONFIG_SCHED_WORKQUEUE=y              : Driver needs work queue support
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       Using the SD card:
-
-       1) After booting, the HSCMI devices will appear as /dev/mmcsd0
-          and /dev/mmcsd1.
-
-       2) If you try mounting an SD card with nothing in the slot, the
-          mount will fail:
-
-            nsh> mount -t vfat /dev/mmcsd1 /mnt/sd1
-            nsh: mount: mount failed: 19
-
-          NSH can be configured to provide errors as strings instead of
-          numbers.  But in this case, only the error number is reported.
-          The  error numbers can be found in nuttx/include/errno.h:
-
-            #define ENODEV              19
-            #define ENODEV_STR          "No such device"
-
-          So the mount command is saying that there is no device or, more
-          correctly, that there is no card in the SD card slot.
-
-       3) Inserted the SD card.  Then the mount should succeed.
-
-           nsh> mount -t vfat /dev/mmcsd1 /mnt/sd1
-           nsh> ls /mnt/sd1
-           /mnt/sd1:
-            atest.txt
-           nsh> cat /mnt/sd1/atest.txt
-           This is a test
-
-       3) Before removing the card, you must umount the file system.  This
-          is equivalent to "ejecting" or "safely removing" the card on
-          Windows:  It flushes any cached data to the card and makes the SD
-          card unavailable to the applications.
+       for both SD slots can be enabled with the settings provided in the
+       paragraph entitled "HSMCI Card Slots" above.
 
-            nsh> umount -t /mnt/sd1
+    9. Support the USB low-, high- and full-speed OHCI host driver can be enabled
+       by changing the NuttX configuration file as described in the section
+       entitled "USB High-Speed Host" above.
 
-          It is now safe to remove the card.  NuttX provides into callbacks
-          that can be used by an application to automatically unmount the
-          volume when it is removed.  But those callbacks are not used in
-          this configuration.
+    10. Support the USB high-speed USB device driver (UDPHS) can be enabled
+        by changing the NuttX configuration file as described above in the
+        section entitled "USB High-Speed Device."
 
-    10. Support the USB low/full-speed OHCI host driver can be enabled by changing
-        the NuttX configuration file as follows:
+    11. AT24 Serial EEPROM. A AT24C512 Serial EEPPROM was used for tested
+        I2C.  There is, however, no AT24 EEPROM on board the SAMA5D3x-EK:
+        The  serial EEPROM was mounted on an external adaptor board and
+        connected to the SAMA5D3x-EK thusly.  See the section above entitle
+        "AT24 Serial EEPROM" for further information.
 
-        System Type -> ATSAMA5 Peripheral Support
-          CONFIG_SAMA5_UHPHS=y                 : USB Host High Speed
+    12. I2C Tool. NuttX supports an I2C tool at apps/system/i2c that can be
+        used to peek and poke I2C devices.  See the discussion above under
+        "I2C Tool" for detailed configuration settings.
 
-        System Type -> USB High Speed Host driver options
-          CONFIG_SAMA5_OHCI=y                  : Low/full-speed OHCI support
-                                               : Defaults for values probably OK
-        Device Drivers
-          CONFIG_USBHOST=y                     : Enable USB host support
+    13. Networking support via the can be added to NSH by modifying the
+        configuration.  See the "Networking" section above for detailed
+        configuration settings.
 
-        Device Drivers -> USB Host Driver Support
-          CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not used
-          CONFIG_USBHOST_MSC=y                 : Enable the mass storage class driver
-
-        Library Routines
-          CONFIG_SCHED_WORKQUEUE=y             : Worker thread support is required
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       NOTE:  When OHCI is selected, the SAMA5 will operate at 384MHz instead
-       of 396MHz.  This is so that the PLL generates a frequency which is a
-       multiple of the 48MHz needed for OHCI.  The delay loop calibration
-       values that are used will be off slightly because of this.
-
-    11. Support the USB high-speed EHCI host driver can be enabled by changing
-        the NuttX configuration file as follows.  If EHCI is enabled by itself,
-        then only high-speed devices can be supported.  If OHCI is also enabled,
-        then all low-, full-, and high speed devices will work.
-
-        System Type -> ATSAMA5 Peripheral Support
-          CONFIG_SAMA5_UHPHS=y                 : USB Host High Speed
-
-        System Type -> USB High Speed Host driver options
-          CONFIG_SAMA5_EHCI=y                  : High-speed EHCI support
-          CONFIG_SAMA5_OHCI=y                  : Low/full-speed OHCI support
-                                               : Defaults for values probably OK for both
-        Device Drivers
-          CONFIG_USBHOST=y                     : Enable USB host support
-          CONFIG_USBHOST_INT_DISABLE=y         : Interrupt endpoints not needed
-          CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not needed
-
-        Device Drivers -> USB Host Driver Support
-          CONFIG_USBHOST_ISOC_DISABLE=y        : Isochronous endpoints not used
-          CONFIG_USBHOST_MSC=y                 : Enable the mass storage class driver
-
-        Library Routines
-          CONFIG_SCHED_WORKQUEUE=y             : Worker thread support is required
-
-        Application Configuration -> NSH Library
-          CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-        Debugging USB Host.  There is normal console debug output available
-        that can be enabled with CONFIG_DEBUG + CONFIG_DEBUG_USB.  However,
-        USB host operation is very time critical and enabling this debug
-        output might interfere with the operation of the UDPHS.  USB host
-        tracing is a less invasive way to get debug information:  If tracing
-        is enabled, the USB host will save encoded trace output in in-memory
-        buffer; if the USB monitor is also enabled, that trace buffer will be
-        periodically emptied and dumped to the system logging device (the
-        serial console in this configuration):
-
-        Device Drivers -> "USB Host Driver Support:
-          CONFIG_USBHOST_TRACE=y                   : Enable USB host trace feature
-          CONFIG_USBHOST_TRACE_NRECORDS=256        : Buffer 256 records in memory
-          CONFIG_USBHOST_TRACE_VERBOSE=y           : Buffer everything
-
-        Application Configuration -> NSH LIbrary:
-          CONFIG_NSH_USBDEV_TRACE=n               : No builtin tracing from NSH
-          CONFIG_NSH_ARCHINIT=y                   : Automatically start the USB monitor
-
-        Application Configuration -> System NSH Add-Ons:
-          CONFIG_SYSTEM_USBMONITOR=y              : Enable the USB monitor daemon
-          CONFIG_SYSTEM_USBMONITOR_STACKSIZE=2048 : USB monitor daemon stack size
-          CONFIG_SYSTEM_USBMONITOR_PRIORITY=50    : USB monitor daemon priority
-          CONFIG_SYSTEM_USBMONITOR_INTERVAL=1     : Dump trace data every second
-
-       NOTE: If USB debug output is also enabled, both outpus will appear
-       on the serial console.  However, the debug output will be
-       asynchronous with the trace output and, hence, difficult to
-       interpret.
-
-    12. Support the USB high-speed USB device driver (UDPHS) can be enabled
-        by changing the NuttX configuration file as follows:
-
-        Device Drivers -> USB Device Driver Support
-          CONFIG_USBDEV=y                       : Enable USB device support
-          CONFIG_USBDEV_DMA=y                   : Device uses DMA
-          CONFIG_USBDEV_DUALSPEED=y             : Device support High and Full Speed
-
-        System Type -> ATSAMA5 Peripheral Support
-          CONFIG_SAMA5_UDPHS=y                  : Enable UDPHS High Speed USB device
-
-        Application Configuration -> NSH Library
-          CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-        You also need to select a device-side class driver for the USB device,
-        This will select the CDC/ACM serial device.  Defaults for the other
-        options should be okay.
-
-        Device Drivers -> USB Device Driver Support
-          CONFIG_CDCACM=y                       : Enable the CDC/ACM device
-          CONFIG_CDCACM_BULKIN_REQLEN=768       : Default too small for high-speed
-
-        The following setting enables an example that can can be used to
-        control the CDC/ACM device.  It will add two new NSH commands:
-        (1) sercon will connect the USB serial device (creating /dev/ttyACM0),
-        and (2) serdis which will disconnect the USB serial device (destroying
-        /dev/ttyACM0).
-
-        Application Configuration -> Examples:
-          CONFIG_SYSTEM_CDCACM=y              : Enable an CDC/ACM example
-
-        Debugging USB Device.  There is normal console debug output available
-        that can be enabled with CONFIG_DEBUG + CONFIG_DEBUG_USB.  However,
-        USB device operation is very time critical and enabling this debug
-        output WILL interfere with the operation of the UDPHS.  USB device
-        tracing is a less invasive way to get debug information:  If tracing
-        is enabled, the USB device will save encoded trace output in in-memory
-        buffer; if the USB monitor is also enabled, that trace buffer will be
-        periodically emptied and dumped to the system logging device (the
-        serial console in this configuration):
-
-        Device Drivers -> "USB Device Driver Support:
-          CONFIG_USBDEV_TRACE=y                   : Enable USB trace feature
-          CONFIG_USBDEV_TRACE_NRECORDS=256        : Buffer 256 records in memory
-          CONFIG_USBDEV_TRACE_STRINGS=y           : (optional)
-
-        Application Configuration -> NSH LIbrary:
-          CONFIG_NSH_USBDEV_TRACE=n               : No builtin tracing from NSH
-          CONFIG_NSH_ARCHINIT=y                   : Automatically start the USB monitor
-
-        Application Configuration -> System NSH Add-Ons:
-          CONFIG_SYSTEM_USBMONITOR=y              : Enable the USB monitor daemon
-          CONFIG_SYSTEM_USBMONITOR_STACKSIZE=2048 : USB monitor daemon stack size
-          CONFIG_SYSTEM_USBMONITOR_PRIORITY=50    : USB monitor daemon priority
-          CONFIG_SYSTEM_USBMONITOR_INTERVAL=1     : Dump trace data every second
-          CONFIG_SYSTEM_USBMONITOR_TRACEINIT=y    : Enable TRACE output
-          CONFIG_SYSTEM_USBMONITOR_TRACECLASS=y
-          CONFIG_SYSTEM_USBMONITOR_TRACETRANSFERS=y
-          CONFIG_SYSTEM_USBMONITOR_TRACECONTROLLER=y
-          CONFIG_SYSTEM_USBMONITOR_TRACEINTERRUPTS=y
-
-       NOTE: If USB debug output is also enabled, both outpus will appear
-       on the serial console.  However, the debug output will be
-       asynchronous with the trace output and, hence, difficult to
-       interpret.
-
-    13. AT24 Serial EEPROM. A AT24C512 Serial EEPPROM was used for tested
-        I2C.  There are other I2C/TWI devices on-board, but the serial
-        EEPROM is the simplest test.
-
-        There is, however, no AT24 EEPROM on board the SAMA5D3x-EK:  The
-        serial EEPROM was mounted on an external adaptor board and
-        connected to the SAMA5D3x-EK thusly:
-
-        - VCC -- VCC
-        - GND -- GND
-        - TWCK0(PA31) -- SCL
-        - TWD0(PA30)  -- SDA
-
-        By default, PA30 and PA31 are SWJ-DP pins, it can be used as a pin
-        for TWI peripheral in the end application.
-
-        The following configuration settings were used:
-
-       System Type -> SAMA5 Peripheral Support
-         CONFIG_SAMA5_TWI0=y                   : Enable TWI0
-
-       System Type -> TWI device driver options
-         SAMA5_TWI0_FREQUENCY=100000           : Select a TWI frequency
-
-       Device Drivers -> I2C Driver Support
-         CONFIG_I2C=y                          : Enable I2C support
-         CONFIG_I2C_TRANSFER=y                 : Driver supports the transfer() method
-         CONFIG_I2C_WRITEREAD=y                : Driver supports the writeread() method
-
-       Device Drivers -> Memory Technology Device (MTD) Support
-         CONFIG_MTD=y                          : Enable MTD support
-         CONFIG_MTD_AT24XX=y                   : Enable the AT24 driver
-         CONFIG_AT24XX_SIZE=512                : Specifies the AT 24C512 part
-         CONFIG_AT24XX_ADDR=0x53               : AT24 I2C address
-
-       Application Configuration -> NSH Library
-         CONFIG_NSH_ARCHINIT=y                 : NSH board-initialization
-
-       File systems
-         CONFIG_NXFFS=y                        : Enables the NXFFS file system
-         CONFIG_NXFFS_PREALLOCATED=y           : Required
-                                               : Other defaults are probably OK
-
-       Board Selection
-         CONFIG_SAMA5_AT24_AUTOMOUNT=y         : Mounts AT24 for NSH
-         CONFIG_SAMA5_AT24_NXFFS=y             : Mount the AT24 using NXFFS
-
-       You can then format the AT25 FLASH for a FAT file system and mount
-       the file system at /mnt/at24 using these NSH commands:
-
-         nsh> mkfatfs /dev/mtdblock0
-         nsh> mount -t vfat /dev/mtdblock0 /mnt/at24
-
-       Then you an use the FLASH as a normal FAT file system:
-
-         nsh> echo "This is a test" >/mnt/at24/atest.txt
-         nsh> ls -l /mnt/at24
-         /mnt/at24:
-          -rw-rw-rw-      16 atest.txt
-         nsh> cat /mnt/at24/atest.txt
-         This is a test
-
-    14. I2C Tool. NuttX supports an I2C tool at apps/system/i2c that can be
-        used to peek and poke I2C devices.  That tool cal be enabled by
-        setting the following:
-
-       System Type -> SAMA5 Peripheral Support
-         CONFIG_SAMA5_TWI0=y                   : Enable TWI0
-         CONFIG_SAMA5_TWI1=y                   : Enable TWI1
-         CONFIG_SAMA5_TWI2=y                   : Enable TWI2
-
-       System Type -> TWI device driver options
-         SAMA5_TWI0_FREQUENCY=100000           : Select a TWI0 frequency
-         SAMA5_TWI1_FREQUENCY=100000           : Select a TWI1 frequency
-         SAMA5_TWI2_FREQUENCY=100000           : Select a TWI2 frequency
-
-       Device Drivers -> I2C Driver Support
-         CONFIG_I2C=y                          : Enable I2C support
-         CONFIG_I2C_TRANSFER=y                 : Driver supports the transfer() method
-         CONFIG_I2C_WRITEREAD=y                : Driver supports the writeread() method
-
-       Application Configuration -> NSH Library
-         CONFIG_SYSTEM_I2CTOOL=y               : Enable the I2C tool
-         CONFIG_I2CTOOL_MINBUS=0               : TWI0 has the minimum bus number 0
-         CONFIG_I2CTOOL_MAXBUS=2               : TWI2 has the maximum bus number 2
-         CONFIG_I2CTOOL_DEFFREQ=100000         : Pick a consistent frequency
-
-       The I2C tool has extensive help that can be accessed as follows:
-
-       nsh> i2c help
-       Usage: i2c <cmd> [arguments]
-       Where <cmd> is one of:
-
-         Show help     : ?
-         List busses   : bus
-         List devices  : dev [OPTIONS] <first> <last>
-         Read register : get [OPTIONS] [<repititions>]
-         Show help     : help
-         Write register: set [OPTIONS] <value> [<repititions>]
-         Verify access : verf [OPTIONS] [<value>] [<repititions>]
-
-       Where common "sticky" OPTIONS include:
-         [-a addr] is the I2C device address (hex).  Default: 03 Current: 03
-         [-b bus] is the I2C bus number (decimal).  Default: 0 Current: 0
-         [-r regaddr] is the I2C device register address (hex).  Default: 00 Current: 00
-         [-w width] is the data width (8 or 16 decimal).  Default: 8 Current: 8
-         [-s|n], send/don't send start between command and data.  Default: -n Current: -n
-         [-i|j], Auto increment|don't increment regaddr on repititions.  Default: NO Current: NO
-         [-f freq] I2C frequency.  Default: 100000 Current: 100000
-
-       NOTES:
-       o Arguments are "sticky".  For example, once the I2C address is
-         specified, that address will be re-used until it is changed.
-
-       WARNING:
-       o The I2C dev command may have bad side effects on your I2C devices.
-         Use only at your own risk.
-
-       As an example, the I2C dev comman can be used to list all devices
-       responding on TWI0 (the default) like this:
-
-         nsh> i2c dev 0x03 0x77
-              0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
-         00:          -- -- -- -- -- -- -- -- -- -- -- -- --
-         10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- --
-         20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-         30: -- -- -- -- -- -- -- -- -- 39 -- -- -- 3d -- --
-         40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-         50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-         60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-         70: -- -- -- -- -- -- -- --
-         nsh>
-
-        Address 0x1a is the WM8904.  Address 0x39 is the SIL9022A. I am
-        not sure what is at address 0x3d and 0x60
-
-    15. Networking support via the can be added to NSH be selecting the
-        following configuration options.  The SAMA5D3x supports two different
-        Ethernet MAC peripherals:  (1) The 10/100Base-T EMAC peripheral and
-        and (2) the 10/100/1000Base-T GMAC peripheral.  Only the SAMA5D31
-        and SAMAD35 support the EMAC peripheral; Only the SAMA5D33, SAMA5D34,
-        and SAMA5D35 support the GMAC perpheral!  NOTE that the SAMA5D35
-        supports both!
-
-        a) Selecting the EMAC peripheral:
-
-          System Type
-            CONFIG_ARCH_CHIP_ATSAMA5D31=y       : SAMA5D31 or SAMAD35 support EMAC
-            CONFIG_ARCH_CHIP_ATSAMA5D35=y       : (others do not)
-
-          System Type -> SAMA5 Peripheral Support
-            CONFIG_SAMA5_EMAC=y                 : Enable the EMAC peripheral
-
-          System Type -> EMAC device driver options
-            CONFIG_SAMA5_EMAC_NRXBUFFERS=16     : Set aside some RS and TX buffers
-            CONFIG_SAMA5_EMAC_NTXBUFFERS=4
-            CONFIG_SAMA5_EMAC_PHYADDR=1         : KSZ8051 PHY is at address 1
-            CONFIG_SAMA5_EMAC_AUTONEG=y         : Use autonegotiation
-            CONFIG_SAMA5_EMAC_RMII=y            : Either MII or RMII interface should work
-            CONFIG_SAMA5_EMAC_PHYSR=30          : Address of PHY status register on KSZ8051
-            CONFIG_SAMA5_EMAC_PHYSR_ALTCONFIG=y : Needed for KSZ8051
-            CONFIG_SAMA5_EMAC_PHYSR_ALTMODE=0x7 : "    " " " "     "
-            CONFIG_SAMA5_EMAC_PHYSR_10HD=0x1    : "    " " " "     "
-            CONFIG_SAMA5_EMAC_PHYSR_100HD=0x2   : "    " " " "     "
-            CONFIG_SAMA5_EMAC_PHYSR_10FD=0x5    : "    " " " "     "
-            CONFIG_SAMA5_EMAC_PHYSR_100FD=0x6   : "    " " " "     "
-
-          PHY selection.  Later in the configuration steps, you will need to
-          select the KSZ8051 PHY for EMAC (See below)
-
-        b) Selecting the GMAC peripheral:
-
-          System Type
-            CONFIG_ARCH_CHIP_ATSAMA5D33=y       : SAMA5D31, SAMA5D33 and SAMAD35
-            CONFIG_ARCH_CHIP_ATSAMA5D34=y       : support GMAC (others do not)
-            CONFIG_ARCH_CHIP_ATSAMA5D35=y       :
-
-          System Type -> SAMA5 Peripheral Support
-            CONFIG_SAMA5_GMAC=y                 : Enable the GMAC peripheral
-
-          System Type -> GMAC device driver options
-            CONFIG_SAMA5_GMAC_NRXBUFFERS=16     : Set aside some RS and TX buffers
-            CONFIG_SAMA5_GMAC_NTXBUFFERS=4
-            CONFIG_SAMA5_GMAC_PHYADDR=1         : KSZ8051 PHY is at address 1
-            CONFIG_SAMA5_GMAC_AUTONEG=y         : Use autonegotiation
-
-          If both EMAC and GMAC are selected, you will also need:
-
-            CONFIG_SAMA5_GMAC_ISETH0=y          : GMAC is "eth0"; EMAC is "eth1"
-
-          PHY selection.  Later in the configuration steps, you will need to
-          select the  KSZ9021/31 PHY for GMAC (See below)
-
-        c) Common configuration settings
-
-          Networking Support
-            CONFIG_NET=y                        : Enable Neworking
-            CONFIG_NET_SOCKOPTS=y               : Enable socket operations
-            CONFIG_NET_BUFSIZE=562              : Maximum packet size (MTD) 1518 is more standard
-            CONFIG_NET_RECEIVE_WINDOW=562       : Should be the same as CONFIG_NET_BUFSIZE
-            CONFIG_NET_TCP=y                    : Enable TCP/IP networking
-            CONFIG_NET_TCPBACKLOG=y             : Support TCP/IP backlog
-            CONFIG_NET_TCP_READAHEAD_BUFSIZE=562  Read-ahead buffer size
-            CONFIG_NET_UDP=y                    : Enable UDP networking
-            CONFIG_NET_ICMP=y                   : Enable ICMP networking
-            CONFIG_NET_ICMP_PING=y              : Needed for NSH ping command
-                                                : Defaults should be okay for other options
-          Device drivers -> Network Device/PHY Support
-            CONFIG_NETDEVICES=y                 : Enabled PHY selection
-            CONFIG_ETH0_PHY_KSZ8051=y           : Select the KSZ8051 PHY (for EMAC), OR
-            CONFIG_ETH0_PHY_KSZ90x1=y           : Select teh KSZ9021/31 PHY (for GMAC)
-
-          Application Configuration -> Network Utilities
-            CONFIG_NETUTILS_RESOLV=y            : Enable host address resolution
-            CONFIG_NETUTILS_TELNETD=y           : Enable the Telnet daemon
-            CONFIG_NETUTILS_TFTPC=y             : Enable TFTP data file transfers for get and put commands
-            CONFIG_NETUTILS_UIPLIB=y            : Network library support is needed
-            CONFIG_NETUTILS_WEBCLIENT=y         : Needed for wget support
-                                                : Defaults should be okay for other options
-          Application Configuration -> NSH Library
-            CONFIG_NSH_TELNET=y                 : Enable NSH session via Telnet
-            CONFIG_NSH_IPADDR=0x0a000002        : Select an IP address
-            CONFIG_NSH_DRIPADDR=0x0a000001      : IP address of gateway/host PC
-            CONFIG_NSH_NETMASK=0xffffff00       : Netmask
-            CONFIG_NSH_NOMAC=y                  : Need to make up a bogus MAC address
-                                                : Defaults should be okay for other options
-
-        d) Using the network with NSH
-
-          So what can you do with this networking support?  First you see that
-          NSH has several new network related commands:
-
-            ifconfig, ifdown, ifup:  Commands to help manage your network
-            get and put:             TFTP file transfers
-            wget:                    HTML file transfers
-            ping:                    Check for access to peers on the network
-            Telnet console:          You can access the NSH remotely via telnet.
-
-          You can also enable other add on features like full FTP or a Web
-          Server or XML RPC and others.  There are also other features that
-          you can enable like DHCP client (or server) or network name
-          resolution.
-
-          By default, the IP address of the SAMA5D3x-EK will be 10.0.0.2 and
-          it will assume that your host is the gateway and has the IP address
-          10.0.0.1.
-
-            nsh> ifconfig
-            eth0    HWaddr 00:e0:de:ad:be:ef at UP
-                    IPaddr:10.0.0.2 DRaddr:10.0.0.1 Mask:255.255.255.0
-
-          You can use ping to test for connectivity to the host (Careful,
-          Window firewalls usually block ping-related ICMP traffic).  On the
-          target side, you can:
-
-            nsh> ping 10.0.0.1
-            PING 10.0.0.1 56 bytes of data
-            56 bytes from 10.0.0.1: icmp_seq=1 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=2 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=3 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=4 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=5 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=6 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=7 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=8 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=9 time=0 ms
-            56 bytes from 10.0.0.1: icmp_seq=10 time=0 ms
-            10 packets transmitted, 10 received, 0% packet loss, time 10100 ms
-
-          NOTE: In this configuration is is normal to have packet loss > 0%
-          the first time you ping due to the default handling of the ARP
-          table.
-
-          On the host side, you should also be able to ping the SAMA5D3-EK:
-
-            $ ping 10.0.0.2
-
-          You can also log into the NSH from the host PC like this:
-
-            $ telnet 10.0.0.2
-            Trying 10.0.0.2...
-            Connected to 10.0.0.2.
-            Escape character is '^]'.
-            sh_telnetmain: Session [3] Started
-
-            NuttShell (NSH) NuttX-6.31
-            nsh> help
-            help usage:  help [-v] [<cmd>]
-
-              [           echo        ifconfig    mkdir       mw          sleep
-              ?           exec        ifdown      mkfatfs     ping        test
-              cat         exit        ifup        mkfifo      ps          umount
-              cp          free        kill        mkrd        put         usleep
-              cmp         get         losetup     mh          rm          wget
-              dd          help        ls          mount       rmdir       xd
-              df          hexdump     mb          mv          sh
-
-            Builtin Apps:
-            nsh>
-
-          NOTE:  If you enable this feature, you experience a delay on booting.
-          That is because the start-up logic waits for the network connection
-          to be established before starting NuttX.  In a real application, you
-          would probably want to do the network bringup on a separate thread
-          so that access to the NSH prompt is not delayed.
-
-          This delay will be especially long if the board is not connected to
-          a network.
-
-    16. You can enable the touchscreen by modifying the configuration
+    14. You can enable the touchscreen by modifying the configuration
         in the following ways:
 
         System Type:
@@ -2667,72 +2635,18 @@ Configurations
 
         Defaults should be okay for all related settings.
 
-    17. The Real Time Clock/Calendar RTC) may be enabled with these settings:
-
-        System Type:
-          CONFIG_SAMA5_RTC=y                   : Enable the RTC driver
-
-        Drivers (these values will be selected automatically):
-          CONFIG_RTC=y                         : Use the RTC for system time
-          CONFIG_RTC_DATETIME=y                : RTC supports data/time
-
-        The RTC supports an alarm that may be enable with the following settings.
-        However, there is nothing in the system that currently makes use of this
-        alarm.
-
-        Drivers:
-          CONFIG_RTC_ALARM=y                   : Enable the RTC alarm
-
-        Library Routines
-         CONFIG_SCHED_WORKQUEUE=y              : Alarm needs work queue support
-
-    18. This example can be configured to exercise the watchdog timer test
-        (apps/examples/watchdog).  This can be selected with the following
-        settings in the NuttX configuration file:
-
-        System Type:
-          CONFIG_SAMA5_WDT=y                  : Enable the WDT peripheral
-                                              : Defaults in "RTC Configuration" should be OK
-
-        Drivers (this will automatically be selected):
-          CONFIG_WATCHDOG=y                   : Enables watchdog timer driver support
-
-        Application Configuration -> Eamples
-          CONFIG_EXAMPLES_WATCHDOG=y          : Enable apps/examples/watchdog
-
-        The WDT timer is driven off the slow, 32768Hz clock divided by 128.
-        As a result, the watchdog a maximum timeout value of 16 seconds.  The
-        SAMA5 WDT may also only be programmed one time; the processor must be
-        reset before the WDT can be reprogrammed.
-
-        The SAMA5 always boots with the watchdog timer enabled at its maximum
-        timeout (16 seconds).  In the normal case where no watchdog timer driver
-        has been configured, the watchdog timer is disabled as part of the start
-        up logic.  But, since we are permitted only one opportunity to program
-        the WDT, we cannot disable the watchdog time if CONFIG_SAMA5_WDT=y.  So,
-        be forewarned:  You have only 16 seconds to run your watchdog timer test!
-
-        NOTE:  If you are using the norboot program to run from FLASH as I did,
-        beware that the default version also disables the watchdog.  You will
-        need a special version of norboot with CONFIG_SAMA5_WDT=y.
-
-    19. This example can be configured to enable the SAMA5 TRNG peripheral so
-        that it provides /dev/random.  The following configuration will enable
-        the TRNG, /dev/random, and the simple test of /dev/random at
-        apps/examples/ranadom:
-
-        System Type:
-          CONFIG_SAMA5_TRNG=y                 : Enable the TRNG peripheral
+    15. The Real Time Clock/Calendar RTC) may be enabled by reconfiguring NuttX.
+        See the section entitled "RTC" above for detailed configuration settings.
 
-        Drivers (automatically selected):
-          CONFIG_DEV_RANDOM=y                 : Enable /dev/random
+    16. This example can be configured to exercise the watchdog timer test
+        (apps/examples/watchdog).  See the detailed configuration settings in
+        the section entitled "Watchdog Timer" above.
 
-        Applications -> Examples
-          CONFIG_EXAMPLES_RANDOM=y            : Enable apps/examples/random
-          CONFIG_EXAMPLES_MAXSAMPLES=64       : Default settings are probably OK
-          CONFIG_EXAMPLES_NSAMPLES=8
+    17. This example can be configured to enable the SAMA5 TRNG peripheral so
+        that it provides /dev/random.  See the section entitled "TRNG and
+        /dev/random" above for detailed configuration information.
 
-    20. See also the sections above for additional configuration options:
+    18. See also the sections above for additional configuration options:
         "AT24 Serial EEPROM", "CAN Usage", "SAMA5 ADC Support", "SAMA5 PWM
         Support", "OV2640 Camera Interface", "I2S Audio Support"