diff --git a/ChangeLog b/ChangeLog
index 037f89ee77..64ab65b92c 100755
--- a/ChangeLog
+++ b/ChangeLog
@@ -11878,7 +11878,7 @@
 	* arch/arm/src/samv7: Fix missing unlock of device in MCAN
 	  mcan_txempty().  From Frank Benkert (2016-06-01).
 
-7.17 2016-xx-xx Gregory Nutt <gnutt@nuttx.org>
+7.17 2016-07-25 Gregory Nutt <gnutt@nuttx.org>
 
 	* drivers/mtd/flash_eraseall.c:  Removed.  This is no longer used
 	  in the OS and is simply a wrapper around the MDIOC_BULKERASE
@@ -11917,27 +11917,16 @@
 	* arch/arm/src/stm32:  Add support for the STM32F105R.  From Konstantin
 	  Berezenko  (2016-06-06).
 	* include/signal.h:  Change type of SIG_ERR, SIG_IGN, ... to
-	  _sa_handler_t.  They type void does not work with the IAR toolchain.
+	  _sa_handler_t.  The type void does not work with the IAR toolchain.
 	  From Aleksandr Vyhovanec (2016-06-07).
-	* arch/arm/src/stm32f7 and include/stm32f7:  Added STM32FF76xxx and
-	  STM32FF7xx families. From David Sidrane (2016-06-08).
-	* Refactoring configs/nucleo-144 sub-directories to support additional
-	  nucleo-144 board.  Add support for the Nucleo-F767ZI board. From David
-	  Sidrane (2016-06-08).
-	* arch/arm/src/kinetis: Add a USB device controller driver for kinetis.
-	  Derived from pic32mx usb driver, which uses the same usb controller.
-	  From kfazz (2016-06-06).
-	* configs/teensy-3.x:  Add USB device support and usbnsh configuration.
-	  From kfazz (2016-06-06.
-	* arch/arm/src/stm32:  Add STM32F105R support.  From Konstantin Berezenko
-	  (2016-06-06).
-	* include/signal.h:  Change type of SIG_IGN and related defines to
-	  _sa_handler_t.  From Aleksandr Vyhovanec (2016-06-07).
 	* configs/nucleo-144: Refactored configs/nucleo-144 sub-directories to
 	  support additional nucleo-144 board.  Add support for the Nucleo-F767ZI
 	  board.  From David Sidrane (2016-06-07).
-	* arch/arm/src/stm32f7: Add support for STM32FF76xxx and STM32FF7xx
-	  families.  From David Sidrane (2016-06-08).
+	* arch/arm/src/stm32f7 and include/stm32f7:  Added STM32F76xxx and
+	  STM32F77xx families. From David Sidrane (2016-06-08).
+	* Refactoring configs/nucleo-144 sub-directories to support additional
+	  nucleo-144 board.  Add support for the Nucleo-F767ZI board. From David
+	  Sidrane (2016-06-08).
 	* include/assert.h: Check if NDEBUG is defined.  From Paul Alexander
 	  Patience (2016-06-08).
 	* arch/arm/src/stm32: Fix STM32 DMA code and configuration for STM32F37X
@@ -11958,25 +11947,10 @@
 	  and the full packet length, need to subtract the size of the link
 	  layer header before making the comparison or we will get false
 	  positives (i.e., the packet is really too small) (2016-06-09)
-	* drivers/mtd: Added driver of IS25xP SPI flash devices.  Based on
-	  sst25xx driver. From Marten Svanfeldt (2016-06-09).
-	* arch/arm/src/kinetis:  Teensy clock fixes.  The High Gain bit in
-	  MCG_C1 was preventing teensy from booting except after a programming
-	  session. The second change doesn't appear to change any functionality,
-	  but complies with restrictions in the k20  family reference manual on
-	  FEI -> FBE clock transiions.  From kfazz (2016-06-09).
-	* arch/arm/src/stm32: Fix timer input clock definitions.  From David
-	  Sidrane (2016-06-09).
 	* configs/: All configurations that have both CONFIG_NSH_LIBRARY=y and
 	  CONFIG_NET=y must now also have CONFIG_NSH_NETINIT=y (2016-06-09).
 	* arch/arm/src/kinetis: Kinetis pwm support, based on kl_pwm driver.
 	  From kfazz (2016-06-09).
-	* net/: In both IPv6 and IPv4 incoming logic:  (1) Should check if the
-	  packet size is large enough before trying to access the packet length
-	  in the IP header.  (2) In the comparison between the IP length and the
-	  full packet length, need to subtract the size of the link layer header
-	  before making the comparison or we will get false positives (i.e., the
-	  packet is really too small) (2016-06-09).
 	* arch/srm/src/stm32: Fix compilation errors in debug mode of
 	  stm32_pwm.c.  From Konstantin Berezenko (2016-06-09).
 	* arch/arm/src/kinetis: Support up to 8 channels per timer.  From kfazz
@@ -11991,7 +11965,7 @@
 	  chips. From Konstantin Berezenko (2016-06-10).
 	* drivers/include/input: Button upper half driver:  Add definitions
 	  needed for compilation with the poll() interface is not disabled
-	  (2016-06-11).  
+	  (2016-06-11).
 	* Kconfig/, include/debug.h, and many other files:  (1) Debug features
 	  are now enabled separately from debug output. CONFIG_DEBUG is gone.
 	  It is replaced with CONFIG_DEBUG_FEATURES. (2) The macros dbg() and
@@ -12033,7 +12007,7 @@
 	    control the delay between the assertion of the ChipSelect and the
 	    first bit, between the last bit and the de-assertion of the
 	    ChipSelect and between two ChipSelects. This is needed to tune the
-	    transfer according the specification of the connected devices.  
+	    transfer according the specification of the connected devices.
 	  - Add three "hw-features" for the SAMV7, which controls the behavior
 	    of the ChipSelect:
 	    - force CS inactive after transfer: this forces a (short)
@@ -12136,7 +12110,7 @@
 	  refresh (via tools/refresh.sh).  I assume that it is a hand-edited
 	  configuration and, hence, must be removed from the repository
 	  (2016-06-23).
-	* arch/arm/arc/sam34: DAC bugfix: DACC_WPMR_WPKEY_MASK -> DACC_WPMR_WPKEY. 
+	* arch/arm/arc/sam34: DAC bugfix: DACC_WPMR_WPKEY_MASK -> DACC_WPMR_WPKEY.
 	  Timer bugfix:  Fix ops check in TCIOC_STOP.  From Wolfgang Reissnegge
 	  (2016-06-23).
 	* configs/nucleo-144: Added SDMMC support to Nucleo-144. From David
@@ -12212,7 +12186,7 @@
 	  style symbolic links.
 	  The fix here is to also execute the clean_context AFTER executing
 	  menuconfig.  A lot more happens now:  It used to be that doing 'make
-	  menuconfig' only did the menuconfig operation.  No it does context,
+	  menuconfig' only did the menuconfig operation.  Now it does context,
 	  pre_config, menuconfig, clean_context.  Not nearly as snappy as it used
 	  to be (2016-06-28).
 	* arch/arm/src/efm32, lcp43, stm32, stm32l4: disable interrupts with
@@ -12377,11 +12351,11 @@
 	  Pettit (2016-07-14).
 	* arch/arm/src/lpc32xx: Extend LPC43xx EMC code to support SDRAM on a
 	  dynamic memory interface.  From Vytautas Lukenskas (2016-07-19).
-	* arch/srim/src:  Add the simulated QSPI (N25Q) flash to the simulation
+	* arch/sim/src:  Add the simulated QSPI (N25Q) flash to the simulation
 	  and modify sim up_spiflash.c to enable it to run with different MTD
 	  drivers based on config options (currently m25p, sst26 and w25).
 	  From Ken Pettit (2016-07-19).
-	* drivers/pipe:  Add support to allocated different sizes for pipe and
+	* drivers/pipe:  Add support to allocating different sizes for pipe and
 	  fifo buffers.  Adds mkfifo2() and pipe2() which are just like mkfifo()
 	  and pipe(), but allow control of the size of the underlying, in-memory
 	  circular buffer .  Move pipe() and mkpipe() to nuttx/libc, they are no
@@ -12418,3 +12392,5 @@
 	  banks.  This fixes a race condition where the HW fills a FIFO bank
 	  while the SW is busy, resulting in out of sequence USB packets
 	  (2016-07-23).
+
+7.18 2016-xx-xx Gregory Nutt <gnutt@nuttx.org>
diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html
index 83c42c61cf..700876be65 100644
--- a/Documentation/NuttX.html
+++ b/Documentation/NuttX.html
@@ -8,7 +8,7 @@
   <tr align="center" bgcolor="#e4e4e4">
     <td>
       <h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
-      <p>Last Updated: June 1, 2016</p>
+      <p>Last Updated: July 25, 2016</p>
     </td>
   </tr>
 </table>
@@ -389,9 +389,10 @@
   <td><br></td>
   <td>
     <p>
-      <li>Inheritable &quot;controlling terminals&quot; and I/O re-direction.</li>
+      <li>Inheritable &quot;controlling terminals&quot; and I/O re-direction. Pseudo-terminals</li>
     </p>
 </tr>
+
 <tr>
   <td><br></td>
   <td>
@@ -1003,7 +1004,7 @@
   <td><br></td>
   <td>
     <p>
-      <li>USB device controller drivers available for the PIC32, Atmel AVR, SAM3, SAM4, and SAMA5Dx, NXP LPC17xx, LPC214x, LPC313x, and LPC43xx, Silicon Laboraties EFM32, STMicro STM32 F1, F2, F3, and F4, and TI DM320.</li>
+      <li>USB device controller drivers available for the PIC32, Atmel AVR, SAM3, SAM4, SAMv7, and SAMA5Dx, NXP/Freescale LPC17xx, LPC214x, LPC313x, LPC43xx, and Kinetis, Silicon Laboraties EFM32, STMicro STM32 F1, F2, F3, F4, and F7, and TI DM320.</li>
     </p>
 </tr>
 <tr>
@@ -1340,11 +1341,11 @@
 <h2>Released Versions</h2>
 <p>
   In addition to the ever-changing GIT repository, there are frozen released versions of NuttX available.
-  The current release is NuttX 7.16.
-  NuttX 7.16 is the 116<sup>th</sup> release of NuttX.
+  The current release is NuttX 7.17.
+  NuttX 7.17 is the 117<sup>th</sup> release of NuttX.
   It was released on June 1, 2016, and is available for download from the
   <a href="https://bitbucket.org/nuttx/nuttx/downloads/">Bitbucket.org</a> website.
-  Note that the release consists of two tarballs:  <code>nuttx-7.16.tar.gz</code> and <code>apps-7.16.tar.gz</code>.
+  Note that the release consists of two tarballs:  <code>nuttx-7.17.tar.gz</code> and <code>apps-7.17.tar.gz</code>.
   Both may be needed (see the top-level <code>nuttx/README.txt</code> file for build information).
 </p>
 
@@ -1353,7 +1354,7 @@
 <ul>
   <li><b>nuttx</b>.
     <ul><p>
-      Release notes for NuttX 7.16 are available <a href="https://bitbucket.org/nuttx/nuttx/downloads/">here</a>.
+      Release notes for NuttX 7.17 are available <a href="https://bitbucket.org/nuttx/nuttx/downloads/">here</a>.
       Release notes for all released versions on NuttX are available in the <a href="https://bitbucket.org/nuttx/nuttx/src/master/ReleaseNotes" target="_blank">Bitbucket GIT</a>.
       The ChangeLog for all releases of NuttX is available in the ChangeLog file that can viewed in the <a href="https://bitbucket.org/nuttx/nuttx/src/master/ChangeLog" target="_blank">Bitbucket GIT</a>.
       The ChangeLog for the current release is at the bottom of that file.
@@ -1361,7 +1362,7 @@
   </li></ul>
   <li><b>apps</b>.
     <ul><p>
-      Release notes for NuttX 7.16 are available <a href="https://bitbucket.org/nuttx/apps/downloads/">here</a>.
+      Release notes for NuttX 7.17 are available <a href="https://bitbucket.org/nuttx/apps/downloads/">here</a>.
       Release notes for all released versions on NuttX are available in the <a href="https://bitbucket.org/nuttx/nuttx/src/master/ReleaseNotes" target="_blank">Bitbucket GIT</a>
       The ChangeLog for the all releases of <code>apps/</code> is available in the ChangeLog file that can viewed in the <a href="https://bitbucket.org/nuttx/apps/src/master/ChangeLog.txt" target="_blank">Bitbucket GIT</a>.
       The ChangeLog for the current release is at the bottom of that file.
@@ -1419,8 +1420,8 @@
       <li><a href="#armcortexr4">ARM Cortex-R4</a> (1)</li>
       <li><a href="#armcortexm0">ARM Cortex-M0/M0+</a> (7)</li>
       <li><a href="#armcortexm3">ARM Cortex-M3</a> (35)</li>
-      <li><a href="#armcortexm4">ARM Cortex-M4</a> (29)</li>
-      <li><a href="#armcortexm7">ARM Cortex-M7</a> (4)</li>
+      <li><a href="#armcortexm4">ARM Cortex-M4</a> (31)</li>
+      <li><a href="#armcortexm7">ARM Cortex-M7</a> (7)</li>
     </ul>
   <li>Atmel AVR
     <ul>
@@ -1513,6 +1514,7 @@
       <li><a href="#kinetisk20">FreeScale Kinetis K20</a> <small>(ARM Cortex-M4)</small></li>
       <li><a href="#kinetisk40">FreeScale Kinetis K40</a> <small>(ARM Cortex-M4)</small></li>
       <li><a href="#kinetisk60">FreeScale Kinetis K60</a> <small>(ARM Cortex-M4)</small></li>
+      <li><a href="#kinetisk64">FreeScale Kinetis K64</a> <small>(ARM Cortex-M4)</small></li>
     </ul>
   </li>
   <li>Host PC based simulations
@@ -1578,6 +1580,7 @@
       <li><a href="#stm32f102x">STMicro STM32F102x</a> <small>(STM32 F1 Family, ARM Cortex-M3)</small></li>
       <li><a href="#stm32f103cx">STMicro STM32F103C4/C8</a> <small>(STM32 F1 &quot;Low- and Medium-Density Line&quot; Family, ARM Cortex-M3)</small></li>
       <li><a href="#stm32f103x">STMicro STM32F103x</a> <small>(STM32 F1 Family, ARM Cortex-M3)</small></li>
+      <li><a href="#stm32f105x">STMicro STM32F105x</a> <small>(ARM Cortex-M3)</small></li>
       <li><a href="#stm32f107x">STMicro STM32F107x</a> <small>(STM32 F1 &quot;Connectivity Line&quot; family, ARM Cortex-M3)</small></li>
       <li><a href="#stm32f205x">STMicro STM32F205x</a> <small>(STM32 F2 family, ARM Cortex-M3)</small></li>
       <li><a href="#stm32f207x">STMicro STM32F207x</a> <small>(STM32 F2 family, ARM Cortex-M3)</small></li>
@@ -1598,6 +1601,7 @@
       <li><a href="#stm32l476">STMicro STM32 L476</a> <small>(STM32 F4 family, ARM Cortex-M4)</small></li>
       <li><a href="#stm32f74x">STMicro STM32 F745/F746</a> <small>(STM32 F7 family, ARM Cortex-M7)</small></li>
       <li><a href="#stm32f75x">STMicro STM32 F756</a> <small>(STM32 F7 family, ARM Cortex-M7)</small></li>
+      <li><a href="#stm32f76xx77xx">STMicro STM32 F76xx/F77xx</a> <small>(STM32 F7 family, ARM Cortex-M7)</small></li>
     </ul>
   <li>Texas Instruments (some formerly Luminary)
     <ul>
@@ -1659,7 +1663,7 @@
       <p>
         <b>STATUS:</b>
         Does not support interrupts but is otherwise fully functional.
-        Refer to the NuttX <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sim/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sim/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
    </td>
@@ -1684,7 +1688,7 @@
       <p>
         <b>STATUS:</b>
         This port is complete, verified, and included in the initial NuttX release.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/c5471evm/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/c5471evm/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
    </td>
@@ -1709,7 +1713,7 @@
         This port was contributed by  Denis Carilki and includes the work of Denis Carikli, Alan Carvalho de Assis, and Stefan Richter.
         Calypso support first appeared in NuttX-6.17 with LCD drivers.
         Support for the Calypso keyboard was added in NuttX-6.24 by Denis Carilki.
-        Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/compal_e88/README.txt" target="_blank">Compal E88</a>, <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/compal_e99/README.txt" target="_blank">Compal E99</a> and <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/pirelli_dpl10/README.txt" target="_blank">Pirelli DP-L10</a> phones for further information.
+        Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/compal_e88/README.txt" target="_blank">Compal E88</a>, <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/compal_e99/README.txt" target="_blank">Compal E99</a> and <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pirelli_dpl10/README.txt" target="_blank">Pirelli DP-L10</a> phones for further information.
       </p>
     </ul>
   </td>
@@ -1736,7 +1740,7 @@
         timer interrupts, serial console, USB driver, and SPI-based MMC/SD card
         support.  A verified NuttShell (<a href="NuttShell.html">NSH</a>)
         configuration is also available.
-        Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/mcu123-lpc214x/README.txt" target="_blank">mcu123.com</a> and for the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/zp214xpa/README.txt" target="_blank">ZPA213X/4XPA</a> boards for further information.
+        Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mcu123-lpc214x/README.txt" target="_blank">mcu123.com</a> and for the <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/zp214xpa/README.txt" target="_blank">ZPA213X/4XPA</a> boards for further information.
       </p>
       <p>
         <b>Development Environments:</b>
@@ -1771,7 +1775,7 @@
         The port is complete and verified.
         As of NuttX 5.3, the port included only basic timer interrupts and serial console support.
         In NuttX 7.1, Lizhuoyi contributed additional I2C and SPI drivers.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/olimex-lpc2378/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-lpc2378/README.txt" target="_blank">README</a> file for further information.
       </p>
       <p>
         <b>Development Environments:</b> (Same as for the NXP LPC214x).
@@ -1804,7 +1808,7 @@
         SD cards).
         An SPI-based ENC28J60 Ethernet driver for add-on hardware is available and
         but has not been fully verified on the Olimex board (due to issues powering the ENC28J60 add-on board).
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/olimex-strp711/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-strp711/README.txt" target="_blank">README</a> file for further information.
       </p>
       <p>
         <b>Development Environments:</b>
@@ -1836,7 +1840,7 @@
         <b>STATUS:</b>
           This port has stalled due to development tool issues.
           Coding is complete on the basic port (timer, serial console, SPI).
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/mx1ads/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mx1ads/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
    </td>
@@ -1865,7 +1869,7 @@
           The basic port (timer interrupts, serial ports, network, framebuffer, etc.) is complete.
           All implemented features have been verified with the exception of the USB device-side
           driver; that implementation is complete but untested.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ntosd-dm320/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ntosd-dm320/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -1901,7 +1905,7 @@
             However, as of this writing, I have not had the opportunity to verify this new feature.
           </p>
           <p>
-            Refer to the Embedded Artists EA3131 board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ea3131/README.txt" target="_blank">README</a> file for further information.
+            Refer to the Embedded Artists EA3131 board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ea3131/README.txt" target="_blank">README</a> file for further information.
           </p>
         </ul>
       </li>
@@ -1917,7 +1921,7 @@
             NOTE: That driver should work on the EA3131 as well.  However, the EA3131 uses a PCA9532 PWM part to controller the port power so the it would not quite be a simple drop-in.
           </p>
           <p>
-            Refer to the Olimex LPC-H3131 board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/olimex-lpc-h3131/README.txt" target="_blank">README</a> file for further information.
+            Refer to the Olimex LPC-H3131 board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-lpc-h3131/README.txt" target="_blank">README</a> file for further information.
           </p>
         </ul>
       </li>
@@ -1945,7 +1949,7 @@
           At this point, verification of the EA3152 port has been overcome by events and
           may never happen.
           However, the port is available for anyone who may want to use it.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ea3152/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ea3152/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -2137,7 +2141,7 @@
           NuttX-7.4 added support for the on-board WM8904 CODEC chip and for <i>Tickless</i> operation.
         </p>
         <p>
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sama5d3x-ek/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sama5d3x-ek/README.txt" target="_blank">README</a> file for further information.
         </p>
       </ul>
       <li>
@@ -2158,7 +2162,7 @@
           The SAMA5D3 Xplained board does not have NOR FLASH and, as a consequence NuttX must boot into SDRAM with the help of U-Boot.
         </p>
         <p>
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sama5d3-xplained/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sama5d3-xplained/README.txt" target="_blank">README</a> file for further information.
         </p>
       </li>
     </ul>
@@ -2189,7 +2193,7 @@
         The TM7000 LCDC with the maXTouch multi-touch controller are also fully support in a special NxWM configuration for that larger display.
         Support for a graphics media player is included (although there were issues with the WM8904 audio CODEC on my board).
         An SRAM bootloader was also included.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sama5d4-ek/README.txt" target="_blank">README</a> file for current status.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sama5d4-ek/README.txt" target="_blank">README</a> file for current status.
       <p></li>
     </ul>
   </td>
@@ -2232,7 +2236,7 @@
           This port was developed on the v1 board, but the others may be compatible:
         </p>
         <p>
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/pcduino-a10/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pcduino-a10/README.txt" target="_blank">README</a> file for further information.
         </p>
         <p>
           <b>STATUS</b>.
@@ -2264,7 +2268,7 @@
         <p>
           <b>Sabre-6Quad</b>.
           This is a port to the NXP/Freescale Sabre-6Quad board.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sabre-6quad/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sabre-6quad/README.txt" target="_blank">README</a> file for further information.
         </p>
         <p>
           <b>STATUS:</b>
@@ -2274,7 +2278,7 @@
         </p>
         <p>
           Basic support of NuttX running in SMP mode on the i.MX6Q was also accomplished in NuttX-7.16.
-          However, there are still known issues with SMP support on this platform as described in the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sabre-6quad/README.txt" target="_blank">README</a> file for the board.
+          However, there are still known issues with SMP support on this platform as described in the <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sabre-6quad/README.txt" target="_blank">README</a> file for the board.
         </p>
       </li>
     </ul>
@@ -2298,13 +2302,13 @@
       <p>
         <b>STATUS</b>.
         This is currently in progress but the effort is stalled due to tool-related issues.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/launchxl-tms57004/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/launchxl-tms57004/README.txt" target="_blank">README</a> file for further information.
       </p>
       <p>
         <b>Toolchain:</b>
         The TMS570 is a big-endian ARM platform and requires a big-endian ARM toolchain.
         All testing has been performed using a big-endian NuttX buildroot toolchain.
-        Instructions for building this toolchain are included in the board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/launchxl-tms57004/README.txt" target="_blank">README</a> file.
+        Instructions for building this toolchain are included in the board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/launchxl-tms57004/README.txt" target="_blank">README</a> file.
       </p>
     </ul>
   </td>
@@ -2329,7 +2333,7 @@
         This initial support is very minimal:
         There is a NuttShell (<a href="NuttShell.html">NSH</a>) configuration that might be the basis for an application development.
         As of this writing, more device drivers are needed to make this a more complete port.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/nutiny-nuc120/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nutiny-nuc120/README.txt" target="_blank">README</a> file for further information.
       </p>
       <p>
         <b>Memory Usage</b>.
@@ -2393,7 +2397,7 @@ nsh>
           As of NuttX-6.28 more device driver development would be needed to make this a complete port, particularly to support USB OTG.
           A TSI and a SPI driver were added in NuttX-6.29.
           Alan contributed a PWM driver in NuttX-6.32.
-          Refer to the Freedom KL25Z board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/freedom-kl25z/README.txt" target="_blank">README</a> file for further information.
+          Refer to the Freedom KL25Z board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-kl25z/README.txt" target="_blank">README</a> file for further information.
         </p>
       </ul>
       <p>
@@ -2407,7 +2411,7 @@ nsh>
           <b>STATUS</b>.
           This is the work of Michael Hope.
           Verified, initial support for the Teensy-LC first appeared in NuttX-7.10.
-          Refer to the Teensy-LC board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/teensy-lc/README.txt" target="_blank">README</a> file for further information.
+          Refer to the Teensy-LC board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/teensy-lc/README.txt" target="_blank">README</a> file for further information.
         </p>
       </ul>
     </ul>
@@ -2431,7 +2435,7 @@ nsh>
         This work was contributed in NuttX 7.8 by Derek B. Noonburg.
         The board support is very similar to the Freedom-KL25Z.
         It was decided to support this a a separate board, however, due to some small board-level differences.
-        Refer to the Freedom KL26Z board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/freedom-kl26z/README.txt" target="_blank">README</a> file for further information.
+        Refer to the Freedom KL26Z board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-kl26z/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -2454,7 +2458,7 @@ nsh>
         The initial SAMD20 Xplained Pro release (NuttX 7.1) included a functional NuttShell (NSH) configuration.
         An SPI driver was also included to support the OLED1 and I/O1 modules.
         That SPI driver, however, was not completed verified due to higher priority tasks that came up (I hope to get back to this later).
-        Refer to the SAMD20 Explained Pro board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/samd20-xplained/README.txt" target="_blank">README</a> file for further information.
+        Refer to the SAMD20 Explained Pro board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/samd20-xplained/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -2478,7 +2482,7 @@ nsh>
         Initial support for the SAML21 Xplained Pro was release in the NuttX 7.10.
         This initial support included a basic configuration for the NuttShell (NSH)
         (see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
-        Refer to the SAML21 Explained Pro board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/saml21-xplained/README.txt" target="_blank">README</a> file for further information.
+        Refer to the SAML21 Explained Pro board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/saml21-xplained/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -2500,7 +2504,7 @@ nsh>
       <p>
         <b>STATUS:</b>
         The first released version was provided in NuttX 7.10.
-        Refer to the board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lpcxpresso-lpc1115/README.txt" target="_blank">README.txt</a> file for further information.
+        Refer to the board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpcxpresso-lpc1115/README.txt" target="_blank">README.txt</a> file for further information.
       </p>
     </ul>
   </td>
@@ -2541,7 +2545,7 @@ nsh>
       <p>
         <b>STATUS:</b>
           This port was was released in NuttX 6.14.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lm3s6432-s2e/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lm3s6432-s2e/README.txt" target="_blank">README</a> file for further information.
       </p>
      </ul>
   </td>
@@ -2565,7 +2569,7 @@ nsh>
           The current port includes timer, serial console, Ethernet, SSI, and microSD support.
           There are working configurations to run the <a href="NuttShell.html">NuttShell
           (NSH)</a>, the NuttX networking test, and the uIP web server.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/eagle100/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/eagle100/README.txt" target="_blank">README</a> file for further information.
       </p>
      </ul>
     <p>
@@ -2605,7 +2609,7 @@ nsh>
         <b>NOTE</b>: As it is configured now, you MUST have a network connected.
         Otherwise, the NSH prompt will not come up because the Ethernet
         driver is waiting for the network to come up.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lm3s6965-ek/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lm3s6965-ek/README.txt" target="_blank">README</a> file for further information.
       </small></p>
      </ul>
     <p>
@@ -2631,7 +2635,7 @@ nsh>
         <b>STATUS:</b>
           This port was released in NuttX 5.10.
           Features are the same as with the Eagle-100 LM3S6918 described above.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lm3s8962-ek/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lm3s8962-ek/README.txt" target="_blank">README</a> file for further information.
       </p>
      </ul>
    </td>
@@ -2648,7 +2652,7 @@ nsh>
       Header file support was contributed by Tiago Maluta for this part.
       Jose Pablo Rojas V. is used those header file changes to port NuttX to the TI/Stellaris EKK-LM3S9B96.
       That port was available in the NuttX-6.20 release.
-      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ekk-lm3s9b96/README.txt" target="_blank">README</a> file for further information.
+      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ekk-lm3s9b96/README.txt" target="_blank">README</a> file for further information.
     </p>
   </td>
 </tr>
@@ -2691,7 +2695,7 @@ nsh>
           DMA and USART-based SPI supported are included, but not fully tested.
         </p>
         <p>
-           Refer to the EFM32 Gecko Starter Kit <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/efm32-g8xx-stk/README.txt" target="_blank"><i>README.txt</i></a> file for further information.
+           Refer to the EFM32 Gecko Starter Kit <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/efm32-g8xx-stk/README.txt" target="_blank"><i>README.txt</i></a> file for further information.
         </p>
       </li>
       <li>
@@ -2715,7 +2719,7 @@ nsh>
           The board suppport is complete but untested because of tool-related issues.  An OpenOCD compatible, SWD debugger would be required to make further progress in testing.
         </p>
         <p>
-           Refer to the Olimex EFM32G880F120-STK <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/olimex-efm32g880f129-stk/README.txt" target="_blank"><i>README.txt</i></a> for further information.
+           Refer to the Olimex EFM32G880F120-STK <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-efm32g880f129-stk/README.txt" target="_blank"><i>README.txt</i></a> for further information.
         </p>
       </li>
     </ol>
@@ -2810,7 +2814,7 @@ nsh>
         This initial support includes a configuration using the NuttShell (<a href="NuttShell.html">NSH</a>) that might be the basis for an application development.
         A driver for the on-board segment LCD is included as well as an option to drive the segment LCD from an NSH &quot;built-in&quot; command.
         As of this writing, a few more things are needed to make this a more complete port:  1) Verfication of more device drivers (timers, quadrature encoders, PWM, etc.), and 2) logic that actually uses the low-power consumption modes of the EnergyLite part.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32ldiscovery/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32ldiscovery/README.txt" target="_blank">README</a> file for further information.
       </p>
       <p>
         <b>Memory Usage</b>.
@@ -2877,7 +2881,7 @@ nsh>
             <b>STM32VL-Discovery</b>.
             In NuttX-6.33, support for the STMicro STM32VL-Discovery board was contributed by Alan Carvalho de Assis.
             The STM32VL-Discovery board features an STM32F100RB MCU.
-            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32vldiscovery/README.txt" target="_blank">README</a> file for further information.
+            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32vldiscovery/README.txt" target="_blank">README</a> file for further information.
           </p>
        </li>
     </ul>
@@ -2933,7 +2937,7 @@ nsh>
     <ul>
         The basic STM32F103C8 port was released in NuttX version 6.28.
         This work was contributed by Laurent Latil.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32_tiny/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32_tiny/README.txt" target="_blank">README</a> file for further information.
       </p>
      </ul>
   </td>
@@ -2958,21 +2962,21 @@ nsh>
            <b>STM3210E-EVAL</b>.
            A port for the <a href=" http://www.st.com/">STMicro</a> STM3210E-EVAL development board that
            features the STM32F103ZET6 MCU.
-           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm3210e-eval/README.txt" target="_blank">README</a> file for further information.
+           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm3210e-eval/README.txt" target="_blank">README</a> file for further information.
          </p>
       </li>
       <li>
          <p>
            <b>HY-Mini STM32v board</b>.
            This board is based on the STM32F103VCT chip.  Port contributed by Laurent Latil.
-           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/hymini-stm32v/README.txt" target="_blank">README</a> file.
+           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/hymini-stm32v/README.txt" target="_blank">README</a> file.
          </p>
       </li>
       <li>
          <p>
             <b>The M3 Wildfire development board (STM32F103VET6), version 2</b>.
             See <a href="http://firestm32.taobao.com">http://firestm32.taobao.com</a> (the current board is version 3).
-            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/fire-stm32v2/README.txt" target="_blank">README</a> file for further information.
+            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/fire-stm32v2/README.txt" target="_blank">README</a> file for further information.
          </p>
       </li>
       <li>
@@ -2980,7 +2984,7 @@ nsh>
             <b>LeafLab's Maple and Maple Mini boards</b>.
             These boards are based on the STM32F103RBT6 chip for the standard version and on the STM32F103CBT6 for the mini version.
             See the <a href="http://leaflabs.com/docs/hardware/maple.html">LeafLabs</a> web site for hardware information;
-            see the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/maple/README.txt" target="_blank">README</a> file for further information about the NuttX port.
+            see the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/maple/README.txt" target="_blank">README</a> file for further information about the NuttX port.
          </p>
       </li>
       <li>
@@ -2989,7 +2993,7 @@ nsh>
             The Spark boards are based on the STM32F103CBT6 chip and feature wireless networking using the TI CC3000 WLAN module.
             See the <a href="http://www.spark.io">Spark</a> web site for hardware information;
             The <i>emulated Spark</i> is a base board for the Maple Mini board (see above) developed by David Sidrane that supports Spark development while we all way breathlessly for or Spark boards.
-            see the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/spark/README.txt" target="_blank">README</a> file for further information about the NuttX port.
+            see the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/spark/README.txt" target="_blank">README</a> file for further information about the NuttX port.
          <p>
          </p>
             Initially Spark support was introduced in NuttX 6.31 and completed in NuttX 6.32.
@@ -3078,6 +3082,20 @@ nsh>
   <td><br></td>
   <td><hr></td>
 </tr>
+<tr>
+  <td><br></td>
+  <td>
+    <p>
+      <a name="stm32f105x"><b>STMicro STM32F105x</b>.</a>
+      Architecture support (only) for the STM32 F105R was contribed in NuttX-7.17 by Konstantin Berezenko.
+      There is currently no support for boards using any STM32F105x parts in the source tree.
+    </p>
+  </td>
+</tr>
+<tr>
+  <td><br></td>
+  <td><hr></td>
+</tr>
 <tr>
   <td><br></td>
   <td>
@@ -3110,7 +3128,7 @@ nsh>
         (1) Basic Cortex-M3 port,
         (2) Ethernet,
         (3) On-board LEDs.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/shenzhou/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/shenzhou/README.txt" target="_blank">README</a> file for further information.
       </p>
     </li>
     <li>
@@ -3137,7 +3155,7 @@ nsh>
         <b>STATUS:</b>
         Networking and touchscreen support are well test.
         But, at present, neither USB nor LCD functionality have been verified.
-        Refer to the SViewtool STM32F103/F107 <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/viewtool-stm32f107/README.txt" target="_blank">README</a> file for further information.
+        Refer to the SViewtool STM32F103/F107 <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/viewtool-stm32f107/README.txt" target="_blank">README</a> file for further information.
       </p>
     </li>
   </td>
@@ -3181,7 +3199,7 @@ nsh>
         <b>STATUS:</b>
         The peripherals of the STM32 F2 family are compatible with the STM32 F4 family.
         See discussion of the STM3240G-EVAL board below for further information.
-        Refer also to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm3220g-eval/README.txt" target="_blank">README</a> file for further information.
+        Refer also to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm3220g-eval/README.txt" target="_blank">README</a> file for further information.
       </p>
       <p>
         Support for both the IAR and uVision GCC IDEs added for the STM3220G-EVAL board in NuttX 7.16.
@@ -3219,7 +3237,7 @@ nsh>
       <p>
         Subsequent NuttX releases will extend this port and add support for the SDIO-based SD cards and
         USB device.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sam3u-ek/README.txt" target="_blank">README</a> file for further information about this port.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam3u-ek/README.txt" target="_blank">README</a> file for further information about this port.
       </p>
      </ul>
      <p>
@@ -3249,7 +3267,7 @@ nsh>
         <b>STATUS:</b>
         As of this writing, the basic port is code complete and a fully verified configuration exists for the NuttShell <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>).
         The first fully functional Arduino Due port was released in NuttX-6.29.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/arduino-due/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/arduino-due/README.txt" target="_blank">README</a> file for further information.
       </p>
      </ul>
      <p>
@@ -3341,7 +3359,7 @@ nsh>
         <ul>
           <li>
             Support for the mbed board was contributed by Dave Marples and released in NuttX-5.11.
-            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/mbed/README.txt" target="_blank">README</a> file for further information.
+            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mbed/README.txt" target="_blank">README</a> file for further information.
           </li>
         </ul>
       </p>
@@ -3365,7 +3383,7 @@ nsh>
             The NuttX-5.17 released added support for low-speed USB devices, interrupt endpoints, and a <i>USB host HID keyboard class driver</i>.
           </li>
           <li>
-            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/olimex-lpc1766stk/README.txt" target="_blank">README</a> file for further information.
+            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-lpc1766stk/README.txt" target="_blank">README</a> file for further information.
           </li>
         </ul>
       </p>
@@ -3384,7 +3402,7 @@ nsh>
            An fully verified board configuration is included in NuttX-6.2.
            The Code Red toolchain is supported under either Linux or Windows.
            Verified configurations include DHCPD, the NuttShell (NSH), NuttX graphis (NX), THTTPD, and USB mass storage device.
-           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lpcxpresso-lpc1768/README.txt" target="_blank">README</a> file for further information.
+           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpcxpresso-lpc1768/README.txt" target="_blank">README</a> file for further information.
         </p>
       </li>
       <li>
@@ -3395,7 +3413,7 @@ nsh>
           The initial release was included NuttX-6.26.
           The Nuttx Buildroot toolchain is used by default.
           Verifed configurations include the &quot;Hello, World!&quot; example application and a THTTPD demonstration.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/zkit-arm-1769/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/zkit-arm-1769/README.txt" target="_blank">README</a> file for further information.
         </p>
       </li>
       <li>
@@ -3403,7 +3421,7 @@ nsh>
         <p>
            This board configuration was contributed and made available in NuttX-6.20.
            As contributed board support, I am unsure of what all has been verfied and what has not.
-           See the Microment website <a href="http://micromint.com/Products/lincoln60.html">Lincoln60</a> board and the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lincoln60/README.txt" target="_blank">README</a> file for further information about the Lincoln board.
+           See the Microment website <a href="http://micromint.com/Products/lincoln60.html">Lincoln60</a> board and the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lincoln60/README.txt" target="_blank">README</a> file for further information about the Lincoln board.
         </p>
       </li>
       <li>
@@ -3411,7 +3429,7 @@ nsh>
         <p>
            This board configuration was contributed by Vladimir Komendantskiy and made available in NuttX-7.15.
            This is a variant of the LPCXpresso LPC1768 board support with special provisions for the U-Blox Model Evaluation board.
-           See the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/u-blox-c027/README.txt" target="_blank">README</a> file for further information about this port.
+           See the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/u-blox-c027/README.txt" target="_blank">README</a> file for further information about this port.
         </p>
       </li>
       </ol>
@@ -3446,7 +3464,7 @@ nsh>
       The NSH configuration includes verified support for a DMA-based SD card interface.
       The frame-buffer LCD driver is functional and uses the SDRAM for frame-buffer memory.
       A touchscreen interface has been developed but there appears to be a hardware issue with the WaveShare implementation of the XPT2046 touchscreen controller.
-      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/open1788/README.txt" target="_blank">README</a> file for further information.
+      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/open1788/README.txt" target="_blank">README</a> file for further information.
     </ul>
   </td>
 </tr>
@@ -3469,7 +3487,7 @@ nsh>
     <ul>
       <p>
         <b>STATUS:</b>
-        Refer to the Teensy-3.1 board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/teensy-3.x/README.txt" target="_blank">README</a> file for further information.
+        Refer to the Teensy-3.1 board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/teensy-3.x/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -3497,7 +3515,7 @@ nsh>
         (2) bring up the NuttShell NSH, (3) develop support for the SDHC-based SD card,
         (4) develop support for USB host and device, and (2) develop an LCD driver.
         NOTE: Some of these remaining tasks are shared with the K60 work described below.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/kwikstik-k40/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/kwikstik-k40/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -3522,12 +3540,7 @@ nsh>
         An additional, validated configuration exists for the NuttShell (NSH, see the
         <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
         This basic TWR-K60N512 first appeared in NuttX-6.8.
-        Ethernet and SD card (SDHC) drivers also exist:
-        The SDHC driver is partially integrated in to the NSH configuration but has some outstanding issues.
-        the Ethernet driver became stable in NuttX-7.14 thanks to the efforts of Andrew Webster.
-        Additional work remaining includes: (1) integrate th SDHC drivers, and (2) develop support for USB host and device.
-        NOTE: Most of these remaining tasks are the same as the pending K40 tasks described above.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/twr-k60n512/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/twr-k60n512/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
     <p>
@@ -3536,6 +3549,43 @@ nsh>
     </p>
   </td>
 </tr>
+<tr>
+  <td><br></td>
+  <td>
+    <p>
+      <a name="kinetisk64"><b>FreeScale Kinetis K64</b>.</a>
+      Support for the Kinetis K64 family and specifically for the NXP/Freescale Freedom K64F board was added in NuttX 7.17.
+      Initial release includes two NSH configurations with support for on-board LEDs, buttons, and Ethernet with the on-board KSZ8081 PHY.
+      SDHC supported has been integrated, but not verified.
+      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-k64f/README.txt" target="_blank">README</a> file for further information.
+    </p>
+  </td>
+</tr>
+<tr>
+  <td><br></td>
+  <td>
+    <p>
+      <b>Driver Status</b>.
+    </p>
+    <ul>
+      <li>
+        <b>NuttX-6.8</b>.
+        Ethernet and SD card (SDHC) drivers also exist:
+        The SDHC driver is partially integrated in to the NSH configuration but has some outstanding issues.
+        Additional work remaining includes: (1) integrate th SDHC drivers, and (2) develop support for USB host and device.
+        NOTE: Most of these remaining tasks are the same as the pending K40 tasks described above.
+      </li>
+      <li>
+        <b>NuttX-7.14</b>.
+        The Ethernet driver became stable in NuttX-7.14 thanks to the efforts of Andrew Webster.
+      <li>
+        <b>NuttX-7.17</b>.
+        Ethernet support was extended and verified on the Freedom K64F.
+        A Kinetis USB device controller driver and PWM support was contributed by kfazz.
+      </li>
+    </ul>
+  </td>
+</tr>
 <tr>
   <td><br></td>
   <td><hr></td>
@@ -3577,7 +3627,7 @@ nsh>
         The basic port for the STM32F3-Discover was first released in NuttX-6.26.
         Many of the drivers previously released for the STM32 F1, Value Line, and F2 and F4 may be usable on this platform as well.
         New drivers will be required for ADC and I2C which are very different on this platform.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32f3discovery/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f3discovery/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
 
@@ -3632,7 +3682,7 @@ nsh>
         <li><b>NuttX-7.2</b>
           The basic port for STMicro Nucleo F401RE board was contributed by Frank Bennett.
         <li>
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/nucleo-f401re/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f401re/README.txt" target="_blank">README</a> file for further information.
         </li>
       </ul>
     </p>
@@ -3685,7 +3735,7 @@ nsh>
           Support for the Olimex STM32 H405 board was added in NuttX-7.3.
         </li>
         <li>
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm3240g-eval/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm3240g-eval/README.txt" target="_blank">README</a> file for further information.
         </li>
       </ul>
     </p>
@@ -3716,7 +3766,7 @@ nsh>
         <b>STATUS:</b>
         The basic port for the STM32F4-Discovery was contributed by Mike Smith and was first released in NuttX-6.14.
         All drivers listed for the STM3240G-EVAL are usable on this platform as well.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32f4discovery/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f4discovery/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
     <p>
@@ -3733,7 +3783,7 @@ nsh>
       <li>Battery connect and batter charger circuit.</li>
     </ul>
     <p>
-      See the <a href="http://www.mikroe.com/mikromedia/stm32-m4/">Mikroelektronika</a> website for more information about this board and the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/mikroe-stm32f4/README.txt" target="_blank">README</a> file for further information about the NuttX port.
+      See the <a href="http://www.mikroe.com/mikromedia/stm32-m4/">Mikroelektronika</a> website for more information about this board and the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mikroe-stm32f4/README.txt" target="_blank">README</a> file for further information about the NuttX port.
     </p>
     <ul>
       <p>
@@ -3745,12 +3795,17 @@ nsh>
     <p>
       <b>Olimex STM32 H405</b>.
       Support for the Olimex STM32 H405 development board was contributed by Martin Lederhilger and appeared in NuttX-7.3.
-      See the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/olimex-stm32-h405/README.txt" target="_blank">README</a> file for further information about the NuttX port.
+      See the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-h405/README.txt" target="_blank">README</a> file for further information about the NuttX port.
     </p>
     <p>
       <b>Olimex STM32 H407</b>.
       Support for the Olimex STM32 H407 development board was contributed by Neil Hancock and appeared in NuttX-7.14.
-      See the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/olimex-stm32-h407/README.txt" target="_blank">README</a> file for further information about the NuttX port.
+      See the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-h407/README.txt" target="_blank">README</a> file for further information about the NuttX port.
+    </p>
+    <p>
+      <b>Olimex STM32 E407</b>.
+      Support for the Olimex STM32 E407 development board was contributed by Mateusz Szafoni and appeared in NuttX-7.17.
+      See the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-e407/README.txt" target="_blank">README</a> file for further information about the NuttX port.
     </p>
   </td>
 </tr>
@@ -3808,7 +3863,7 @@ nsh>
       </li>
     </ul>
     <p>
-      Refer to the STM32F429I-Discovery board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32f429i-disco/README.txt" target="_blank">README</a> file for further information.
+      Refer to the STM32F429I-Discovery board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f429i-disco/README.txt" target="_blank">README</a> file for further information.
     </p>
   </td>
 </tr>
@@ -3857,13 +3912,13 @@ nsh>
       <li>
         <p>
           <b>Nucleo-L476RG</b>.
-          Board support for the STMicro NucleoL476RG board from ST Micro was contributed by Sebastien Lorquet in NuttX-7.15.  See the <a href="http://www.st.com/nucleo-l476rg" target="_blank">STMicro website</a> and the board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/nucleo-l476rg/README.txt" target="_blank">README</a> file for further information.
+          Board support for the STMicro NucleoL476RG board from ST Micro was contributed by Sebastien Lorquet in NuttX-7.15.  See the <a href="http://www.st.com/nucleo-l476rg" target="_blank">STMicro website</a> and the board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-l476rg/README.txt" target="_blank">README</a> file for further information.
         </p>
       </li>
       <li>
         <p>
           <b>STM32L476VG Discovery</b>.
-          Board support for the STMicro STM32L476VG Discovery board from ST Micro was contributed by Dave in NuttX-7.15.  See the <a href="http://www.st.com/stm32l476g-disco" target="_blank">STMicro website</a> and the board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32l476vg-disco/README.txt" target="_blank">README</a> file for further information.
+          Board support for the STMicro STM32L476VG Discovery board from ST Micro was contributed by Dave in NuttX-7.15.  See the <a href="http://www.st.com/stm32l476g-disco" target="_blank">STMicro website</a> and the board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32l476vg-disco/README.txt" target="_blank">README</a> file for further information.
         </p>
       </li>
     </ul>
@@ -3912,42 +3967,15 @@ nsh>
       <ul>
         <li>
           <p><b>STATUS:</b>
-            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lpc4330-xplorer/README.txt" target="_blank">README</a> file for more detailed information about this port.
+            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpc4330-xplorer/README.txt" target="_blank">README</a> file for more detailed information about this port.
           </p>
         </li>
         <li>
           <p><b>NuttX-6.20</b>
-            The basic port is complete.
+            The basic LPC4330-Xplorer port is complete.
             The basic NuttShell (NSH) configuration is present and fully verified.
             This includes verified support for:  SYSTICK system time, pin and GPIO configuration, and a serial console.
           </p>
-          <p>
-            Several drivers have been copied from the related LPC17xx port but require integration into the LPC43xx:  ADC, DAC, GPDMA, I2C, SPI, and SSP.
-            The registers for these blocks are the same in both the LPC43xx and the LPC17xx and they should integrate into the LPC43xx very easily by simply adapting the clocking and pin configuration logic.
-          </p>
-          <p>
-            Other LPC17xx drivers were not brought into the LPC43xx port because these peripherals have been completely redesigned:  CAN, Ethernet, USB device, and USB host.
-          </p>
-          <p>
-            So then there is no support for the following LPC43xx peripherals: SD/MMC, EMC, USB0,USB1, Ethernet, LCD, SCT, Timers 0-3, MCPWM, QEI, Alarm timer, WWDT, RTC, Event monitor, and CAN.
-          </p>
-          <p>
-            Some of these can be leveraged from other MCUs that appear to support the same peripheral IP:
-          </p>
-          <ul>
-            <li>
-              The LPC43xx USB0 peripheral appears to be the same as the USB OTG peripheral for the LPC31xx.
-              The LPC31xx USB0 device-side driver has been copied from the LPC31xx port but also integration into the LPC43xx (clocking and pin configuration).
-              It should be possible to complete porting of this LPC31xx driver with a small porting effort.
-            </li>
-            <li>
-              The Ethernet block looks to be based on the same IP as the STM32 Ethernet and, as a result, it should be possible to leverage the NuttX STM32 Ethernet driver with a little more effort.
-            </li>
-          </ul>
-        </li>
-        <li>
-          <p><b>NuttX-6.21</b>
-          Added support for a SPIFI block driver and for RS-485 option to the serial driver.
         </li>
       </ul>
       <p>
@@ -3959,7 +3987,7 @@ nsh>
       <ul>
       <li>
         <p><b>STATUS:</b>
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lpc4357-evb/README.txt" target="_blank">README</a> file for more detailed information about this port.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpc4357-evb/README.txt" target="_blank">README</a> file for more detailed information about this port.
         </p>
       </li>
       <li>
@@ -3979,7 +4007,7 @@ nsh>
       <ul>
         <li>
           <p><b>STATUS:</b>
-            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lpc4370-link2/README.txt" target="_blank">README</a> file for more detailed information about this port.
+            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpc4370-link2/README.txt" target="_blank">README</a> file for more detailed information about this port.
           </p>
         </li>
         <li>
@@ -3996,7 +4024,7 @@ nsh>
       <ul>
         <li>
           <p><b>STATUS:</b>
-            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/lpc4337-ws/README.txt" target="_blank">README</a> file for more detailed information about this port.
+            Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpc4337-ws/README.txt" target="_blank">README</a> file for more detailed information about this port.
           </p>
         </li>
         <li>
@@ -4010,10 +4038,52 @@ nsh>
             Alexander also contributed an LPC43xx AES driver available in NuttX-7.16.
           </p>
         </li>
-
       </ul>
   </td>
 </tr>
+<tr>
+  <td><br></td>
+  <td>
+    <p>
+      <b>Driver Status</b>.
+    </p>
+    <ul>
+      <li>
+        <p><b>NuttX-6.20</b>
+          Several drivers have been copied from the related LPC17xx port but require integration into the LPC43xx:  ADC, DAC, GPDMA, I2C, SPI, and SSP.
+          The registers for these blocks are the same in both the LPC43xx and the LPC17xx and they should integrate into the LPC43xx very easily by simply adapting the clocking and pin configuration logic.
+        </p>
+        <p>
+          Other LPC17xx drivers were not brought into the LPC43xx port because these peripherals have been completely redesigned:  CAN, Ethernet, USB device, and USB host.
+        </p>
+        <p>
+          So then there is no support for the following LPC43xx peripherals: SD/MMC, EMC, USB0,USB1, Ethernet, LCD, SCT, Timers 0-3, MCPWM, QEI, Alarm timer, WWDT, RTC, Event monitor, and CAN.
+        </p>
+        <p>
+          Some of these can be leveraged from other MCUs that appear to support the same peripheral IP:
+        </p>
+        <ul>
+          <li>
+            The LPC43xx USB0 peripheral appears to be the same as the USB OTG peripheral for the LPC31xx.
+            The LPC31xx USB0 device-side driver has been copied from the LPC31xx port but also integration into the LPC43xx (clocking and pin configuration).
+            It should be possible to complete porting of this LPC31xx driver with a small porting effort.
+          </li>
+          <li>
+            The Ethernet block looks to be based on the same IP as the STM32 Ethernet and, as a result, it should be possible to leverage the NuttX STM32 Ethernet driver with a little more effort.
+          </li>
+        </ul>
+      </li>
+      <li>
+        <p><b>NuttX-6.21</b>
+        Added support for a SPIFI block driver and for RS-485 option to the serial driver.
+      </li>
+      <li>
+        <p><b>NuttX-7.17</b>
+        EMC support was extended to include support SDRAM by Vytautas Lukenska.
+      </li>
+    </ul>
+  </td>
+</tr>
 <tr>
   <td><br></td>
   <td><hr></td>
@@ -4063,7 +4133,7 @@ nsh>
            </li>
         </ul>
       </p>
-        Refer to the EK-TM4C123GXL board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/tm4c123g-launchpad/README.txt" target="_blank">README</a> file for more detailed information about this port.
+        Refer to the EK-TM4C123GXL board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/tm4c123g-launchpad/README.txt" target="_blank">README</a> file for more detailed information about this port.
       </p>
     </ul>
   </td>
@@ -4089,7 +4159,7 @@ nsh>
            </li>
         </ul>
       </p>
-        Refer to the EK-TM4C1294XL board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/tm4c1294-launchpad/README.txt" target="_blank">README</a> file for more detailed information about this port.
+        Refer to the EK-TM4C1294XL board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/tm4c1294-launchpad/README.txt" target="_blank">README</a> file for more detailed information about this port.
       </p>
     </ul>
   </td>
@@ -4119,11 +4189,11 @@ nsh>
           <li>
             This board supports included two configurations for the NuttShell (<a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>).
             Both are networked enabled:  One configured to support IPv4 and one configured to supported IPv6.
-            Instructions are included in the board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/dk-tm4c129x/README.txt" target="_blank">README</a> file for configuring both IPv4 and IPv6 simultaneously..
+            Instructions are included in the board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/dk-tm4c129x/README.txt" target="_blank">README</a> file for configuring both IPv4 and IPv6 simultaneously..
           </li>
         </ul>
       </p>
-        Refer to the DK-TM4C129X board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/dk-tm4c129x/README.txt" target="_blank">README</a> file for more detailed information about this port.
+        Refer to the DK-TM4C129X board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/dk-tm4c129x/README.txt" target="_blank">README</a> file for more detailed information about this port.
       </p>
     </ul>
   </td>
@@ -4146,7 +4216,7 @@ nsh>
         The basic port was released in NuttX-7.5.
         This basic board supported includes an verified configuration for the NuttShell <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>).
         Key wireless networking capability is still missing.
-        Refer to the CC3200 LaunchPad board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/cc3200-launchpad/README.txt" target="_blank">README</a> file for more detailed information about this port.
+        Refer to the CC3200 LaunchPad board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/cc3200-launchpad/README.txt" target="_blank">README</a> file for more detailed information about this port.
       </p>
     </ul>
   </td>
@@ -4182,7 +4252,7 @@ nsh>
         </li>
       </ul>
       </p>
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sam4l-xplained/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4l-xplained/README.txt" target="_blank">README</a> file for further information.
       </p>
       <p>
         <b>Memory Usage</b>.
@@ -4258,7 +4328,7 @@ Mem:         29232       5920      23312      23312
       A DMA-base SPI driver is supported and has been verified with the AT25 Serial FLASH.
       Touchscreen and LCD support was added in NuttX-7.3, but has not been fully integrated as of this writing.
       The SAM4E-EK should be compatible with most of the other SAM3/4 drivers (like HSMCI, DMAC, etc.) but those have not be verified on the SAM4E-EK as of this writing.
-      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sam4e-ek/README.txt" target="_blank">README</a> file for further information.
+      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4e-ek/README.txt" target="_blank">README</a> file for further information.
     </ul>
   </td>
 </tr>
@@ -4287,7 +4357,7 @@ Mem:         29232       5920      23312      23312
           Support for the on-board 1MB SRAM was added in NuttX-6.29.
           An RTT driver was Bob Doiron in NuttX-7.3.
           Bob also added an high resolution RTC emulation using the RTT for the sub-second counter.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sam4s-xplained/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4s-xplained/README.txt" target="_blank">README</a> file for further information.
         </p>
       </ul>
      </li>
@@ -4302,7 +4372,7 @@ Mem:         29232       5920      23312      23312
           As of this writing, the basic port is code complete and a fully verified configuration exists for the NuttShell <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>).
           The first fully functional SAM4S Xplained Pro port was released in NuttX-7.2.
           This supported also added HSMCI, RTC, and watchdog and verified support for USB device.
-          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sam4s-xplained-pro/README.txt" target="_blank">README</a> file for further information.
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4s-xplained-pro/README.txt" target="_blank">README</a> file for further information.
         </p>
       </ul>
      </li>
@@ -4335,7 +4405,7 @@ Mem:         29232       5920      23312      23312
       A new Ethernet MAC driver has been developed and is functional in the NSH configuration.
       A DMA-base SPI driver is supported and has been verified with the AT25 Serial FLASH.
       The SAM4E-EK should be compatible with most of the other SAM3/4 drivers (like HSMCI, DMAC, etc.) but those have not be verified on the SAM4E-EK as of this writing.
-      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sam4e-ek/README.txt" target="_blank">README</a> file for further information.
+      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4e-ek/README.txt" target="_blank">README</a> file for further information.
     </ul>
   </td>
 </tr>
@@ -4421,7 +4491,7 @@ Mem:         29232       5920      23312      23312
         <li>RSWDT driver.</li>
       </ul>
       </p>
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/samv71-xult/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/samv71-xult/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -4438,7 +4508,7 @@ Mem:         29232       5920      23312      23312
       This port uses Atmel SAM E70 Xplained Evaluation Kit (ATSAME70-XPLD).
       This board is essentially a lower cost version of the SAMV71-XULT board featuring the ATSAME70Q21 Cortex-M7 microcontroller.
       See the <a href="#at91samv71">Atmel SAMV71</a> for supported features.
-      Also refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/same70-xplained/README.txt" target="_blank">README</a> file for further information.
+      Also refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/same70-xplained/README.txt" target="_blank">README</a> file for further information.
     </p>
   </td>
 <tr>
@@ -4461,24 +4531,39 @@ Mem:         29232       5920      23312      23312
       <p>
          A basic port for the Nucleo-144 board with the STM32F746ZG MCU was contribued in NuttX-7.16 by Kconstantin Berezenko.
       </p>
+      <p>
+        <b>STATUS:</b>
+      </p>
+      <ul>
+        <p>
+          The basic STM32F746G-DISCO port is complete and there are two, verified configurations available.
+          Both configurations use the NuttShell (NSH) and a serial console; one includes Ethernet support.
+          The first release of the STM32F746G_DISCO port was available in NuttX-7.11.
+        </p>
+        </p>
+          Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f746g-disco/README.txt" target="_blank">README</a> file for further information.
+        </p>
+      </ul>
     </ul>
     <p>
-      <b>STATUS:</b>
+      <a name="stm32f7drivers"><b>STM32 F7 Driver Status:</b></a>
     </p>
     <ul>
-      <p>
-        The basic STM32F746G-DISCO port is complete and there are two, verified configurations available.
-        Both configurations use the NuttShell (NSH) and a serial console; one includes Ethernet support.
-        DMA supports is available.
-        The STM32 F7 peripherals are very similar to some members of the STM32 F4 and additional drivers can easily be ported the F7 as discussed in this Wiki page: <a href="http://www.nuttx.org/doku.php?id=wiki:howtos:port-drivers_stm32f7">Porting Drivers to the STM32 F7</a>
-        The first release of the STM32F746G_DISCO port was available in NuttX-7.11.
-      </p>
-      </p>
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/stm32f746g-disco/README.txt" target="_blank">README</a> file for further information.
-      </p>
+      <li>
+        <p><b>NuttX-7.11</b>.
+          Serial driver and Ethernet driver support, along with DMA support, were available availabe in this initial release.
+          The STM32 F7 peripherals are very similar to some members of the STM32 F4 and additional drivers can easily be ported the F7 as discussed in this Wiki page: <a href="http://www.nuttx.org/doku.php?id=wiki:howtos:port-drivers_stm32f7">Porting Drivers to the STM32 F7</a>
+        </p>
+      </li>
+      <li>
+        <p><b>NuttX-7.17</b>.
+        Davide Sidrane contributed PWR, RTC, BBSRAM, and DBGMCU support.
+        Lok Tep contribed SPI, I2c, ADC, SDMMC, and USB device driver support.
+      </li>
     </ul>
   </td>
 </tr>
+
 <tr>
   <td><br></td>
   <td><hr></td>
@@ -4490,9 +4575,38 @@ Mem:         29232       5920      23312      23312
       <a name="stm32f75x"><b>STMicro STM32 F756</b>.</a>
       Architecture-only support is available for the STM32 F756 family (meaning that the parts are supported, but there is not example board supported in the system).
       This support was made available in NuttX-7.11.
+      See <a href="#stm32f7drivers">above</a> for STM32 F7 driver availability.
     </p>
   </td>
 </tr>
+
+<tr>
+  <td><br></td>
+  <td><hr></td>
+</tr>
+<tr>
+  <td><br></td>
+  <td>
+    <p>
+      <a name="stm32f76xx77xx"><b>STMicro STM32 F76xx/F77xx</b>.</a>
+      Architecture support for the STM32 F76xx and F77xx families was contributed by David Sidrane in NuttX 7.17.  Support is available for one board from this family:
+    </p>
+    <ul>
+      <li>
+        <p>
+          <b>Nucleo-F767ZI</b>.
+          This is a member of the Nucleo-144 board family.
+          Support for this board was also contributed by David Sidrane in NuttX-7.17.
+          See the board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-144/README.txt">README.txt</a> file for further information.
+        </p>
+      </li>
+    </ul>
+    <p>
+      See <a href="#stm32f7drivers">above</a> for STM32 F7 driver availability.
+    </p>
+  </td>
+</tr>
+
 <tr>
   <td><br></td>
   <td><hr></td>
@@ -4530,14 +4644,14 @@ Mem:         29232       5920      23312      23312
         <p>
          <b>STATUS:</b>
            Work on this port has stalled due to toolchain issues.  Complete, but untested code for this port appears in the NuttX 6.5 release.
-           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/amber/README.txt" target="_blank">README</a> file for further information.
+           Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/amber/README.txt" target="_blank">README</a> file for further information.
         </p>
       </ul>
       <p>
         <a name="avratmega1284p"><b>LowPowerLab MoteinoMEGA</b>.</a>
         This port of NuttX to the MoteinoMEGA from <a href="http://www.lowpowerlab.com">LowPowerLab</a>.
         The MoteinoMEGA is based on an Atmel ATMega1284P.
-        See the LowPowerlab <a href="https://lowpowerlab.com/shop/index.php?_route_=Moteino/moteinomega">website</a> and the board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/moteio-mega/README.txt" target="_blank">README</a> file for further information.
+        See the LowPowerlab <a href="https://lowpowerlab.com/shop/index.php?_route_=Moteino/moteinomega">website</a> and the board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/moteio-mega/README.txt" target="_blank">README</a> file for further information.
       </p>
       <ul>
         <p>
@@ -4554,7 +4668,7 @@ Mem:         29232       5920      23312      23312
          <b>STATUS:</b>
          The basic port was released in NuttX-7.14 including a simple &quot;Hello, World!&quot; and OS test configurations.
          Extensive effort was made to the use the special capabilities of the Atmel Studio AVR compiler to retain strings in FLASH memory and so keep the SRAM memory usage to a minimum.
-         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/arduino-mega2560/README.txt" target="_blank">README</a> file for further information.
+         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/arduino-mega2560/README.txt" target="_blank">README</a> file for further information.
         </p>
       </ul>
     </ul>
@@ -4584,7 +4698,7 @@ Mem:         29232       5920      23312      23312
          The basic port was released in NuttX-6.5.  This basic port consists only of
          a &quot;Hello, World!!&quot; example that demonstrates initialization of the OS,
          creation of a simple task, and serial console output.
-         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/micropendous3/README.txt" target="_blank">README</a> file for further information.
+         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/micropendous3/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
     <p>
@@ -4606,7 +4720,7 @@ Mem:         29232       5920      23312      23312
          An SPI driver and a USB device driver exist for the AT90USB as well
          as a USB mass storage configuration.  However, this configuration is not
          fully debugged as of the NuttX-6.5 release.
-         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/teensy-2.0/README.txt" target="_blank">README</a> file for further information.
+         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/teensy-2.0/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
 </tr>
@@ -4699,7 +4813,7 @@ Mem:         29232       5920      23312      23312
         The basic, port was be released in NuttX-5.13.
         A complete port will include drivers for additional AVR32 UC3 devices -- like SPI and USB --- and will be available in a later release,
         time permitting.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/avr32dev1/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/avr32dev1/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -4736,7 +4850,7 @@ Mem:         29232       5920      23312      23312
          However, testing has not yet begun due to issues with BDMs, Code Warrior, and
          the paging in the build process.
          Progress is slow, but I hope to see a fully verified MC9S12NE64 port in the near future.
-         Refer to the NuttX board README files for <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/demo9s12ne64/README.txt" target="_blank">DEMO9S12NE64</a> and for the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ne64badge/README.txt" target="_blank">NE64 /PoE Badge</a> for further information.
+         Refer to the NuttX board README files for <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/demo9s12ne64/README.txt" target="_blank">DEMO9S12NE64</a> and for the <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ne64badge/README.txt" target="_blank">NE64 /PoE Badge</a> for further information.
       </p>
     </ul>
   </td>
@@ -4763,7 +4877,7 @@ Mem:         29232       5920      23312      23312
          The port is reported to be functional on the <a href="http://bifferos.bizhat.com">Bifferboard</a> as well.
          In NuttX 7.1, Lizhuoyi contributed additional keyboard and VGA drivers.
          This is a great, stable starting point for anyone interest in fleshing out the x86 port!
-         Refer to the NuttX <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/qemu-i486/README.txt" target="_blank">README</a> file for further information.
+         Refer to the NuttX <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/qemu-i486/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -4791,7 +4905,7 @@ Mem:         29232       5920      23312      23312
          This initial port of NuttX to RGMP was provided in NuttX-6.3.
          This initial RGP port provides only minimal driver support and does not use the native NuttX interrupt system.
          This is a great, stable starting point for anyone interest in working with NuttX under RGMP!
-         Refer to the NuttX <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/rgmp/README.txt" target="_blank">README</a> file for further information.
+         Refer to the NuttX <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/rgmp/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -4822,7 +4936,7 @@ Mem:         29232       5920      23312      23312
         The PGA117, however, is not yet fully integrated to support ADC sampling.
         See the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a> for further information about NSH.
         The first verified port to the Mirtoo module was available with the NuttX 6.20 release.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/mirtoo/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mirtoo/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -4856,7 +4970,7 @@ Mem:         29232       5920      23312      23312
        An untested USB device-side driver is available in the source tree.
        A more complete port would include support of the USB OTG port and of the LCD display on this board.
        Those drivers are not yet available as of this writing.
-       Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sure-pic32mx/README.txt" target="_blank">README</a> file for further information.
+       Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sure-pic32mx/README.txt" target="_blank">README</a> file for further information.
        </p>
     </ul>
    <p>
@@ -4872,7 +4986,7 @@ Mem:         29232       5920      23312      23312
       <b>STATUS:</b>
       The basic port is code complete and fully verified in NuttX 6.13.
       Available configurations include the NuttShell (NSH - see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
-      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/pcblogic-pic32mx/README.txt" target="_blank">README</a> file for further information.
+      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pcblogic-pic32mx/README.txt" target="_blank">README</a> file for further information.
     </p>
     <li><b>UBW32 Board from Sparkfun</b>
       This is the port to the Sparkfun UBW32 board.
@@ -4885,7 +4999,7 @@ Mem:         29232       5920      23312      23312
       The basic port is code complete and fully verified in NuttX 6.18.
       Available configurations include the NuttShell (NSH - see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
       USB has not yet been fully tested but on first pass appears to be functional.
-      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ubw32/README.txt" target="_blank">README</a> file for further information.
+      Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ubw32/README.txt" target="_blank">README</a> file for further information.
     </p>
     </ul>
     </ul>
@@ -4916,7 +5030,7 @@ Mem:         29232       5920      23312      23312
          A verified configuration is available for the NuttShel (NSH) appeared in NuttX-6.16.
          Board support includes a verified USB (device-side) driver.
          Also included are a a verified Ethernet driver, a partially verified USB device controller driver, and an unverifed SPI driver.
-         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/pic32mx-starterkit/README.txt" target="_blank">README</a> file for further information.
+         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pic32mx-starterkit/README.txt" target="_blank">README</a> file for further information.
       </p>
      <li><b>Mikroelektronika PIC32MX7 Mulitmedia Board (MMB)</b>.
         A port has been completed for the  Mikroelektronika PIC32MX7 Multimedia Board (MMB).
@@ -4939,7 +5053,7 @@ Mem:         29232       5920      23312      23312
          However, additional verification and tuning of this driver is required.
          Further display/touchscreen verification would require C++ support (for NxWidgets and NxWM).
          Since I there is no PIC32 C++ is the free version of the MPLAB C32 toolchain, further graphics development is stalled.
-         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/pic32mx7mmb/README.txt" target="_blank">README</a> file for further information.
+         Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pic32mx7mmb/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -5010,7 +5124,7 @@ Mem:         29232       5920      23312      23312
         <li>Ethernet (code complete, but not yet functional),</li>
       </ul>
       </p>
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/pic32mz-starterkit/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pic32mz-starterkit/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -5056,7 +5170,7 @@ Mem:         29232       5920      23312      23312
         (which has very limit SH-1 support to begin with), or perhaps with the CMON debugger.
         At any rate, I have exhausted all of the energy that I am willing to put into this cool
         old processor for the time being.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/us7032evb1/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/us7032evb1/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -5093,7 +5207,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
 </pre></ul>
       <p>
         No workaround is known at this time.  This is a show stopper for M16C.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/skp16c26/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/skp16c26/README.txt" target="_blank">README</a> file for further information.
       </p>
     </ul>
   </td>
@@ -5120,7 +5234,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
         The initial release of support for the z16f was made available in NuttX version 0.3.7.
         A working NuttShell (NSH) configuration as added in NuttX-6.33 (although a patch is required to work around an issue with a ZDS-II 5.0.1 tool problem).
         An ESPI driver was added in NuttX-7.2.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/z16f2800100zcog/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z16f2800100zcog/README.txt" target="_blank">README</a> file for further information.
       </p>
     </li>
   </ul>
@@ -5155,7 +5269,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
         The first integrated version was released in NuttX version 0.4.2 (with important early bugfixes
         in 0.4.3 and 0.4.4).
         As of this writing, that port provides basic board support with a serial console, SPI, and eZ80F91 EMAC driver.
-        Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ez80f910200kitg/README.txt" target="_blank">ez80f0910200kitg</a> and <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/ez80f910200zco/README.txt" target="_blank">ez80f910200zco</a>file for further information.
+        Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200kitg/README.txt" target="_blank">ez80f0910200kitg</a> and <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/README.txt" target="_blank">ez80f910200zco</a>file for further information.
       </p>
     </ul>
   </td>
@@ -5186,7 +5300,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
          <b>STATUS:</b>
          This release has been verified only on the ZiLOG ZDS-II Z8Encore! chip simulation
          as of nuttx-0.3.9.
-         Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/z8encore000zco/README.txt" target="_blank">z8encore000zco</a> and for the<a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/z8f64200100kit/README.txt" target="_blank">z8f64200100kit</a> for further information.
+         Refer to the NuttX board README files for the <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z8encore000zco/README.txt" target="_blank">z8encore000zco</a> and for the<a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z8f64200100kit/README.txt" target="_blank">z8f64200100kit</a> for further information.
        </p>
      <ul>
   </td>
@@ -5215,7 +5329,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
        Most of the NuttX is in port for both the Z80182 and for the P112 board.
        Boards from Kickstarter project will not be available, however, until the third quarter of 2013.
        So it will be some time before this port is verified on hardware.
-       Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/p112/README.txt" target="_blank">README</a> file for further information.
+       Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/p112/README.txt" target="_blank">README</a> file for further information.
       </p>
     <ul>
   </td>
@@ -5240,7 +5354,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
        <b>STATUS:</b>
         This port is complete and stable to the extent that it can be tested
         using an instruction set simulator.
-        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/z80sim/README.txt" target="_blank">README</a> file for further information.
+        Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z80sim/README.txt" target="_blank">README</a> file for further information.
       </p>
     <ul>
   </td>
@@ -5264,7 +5378,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
        <b>STATUS:</b>
        Basically the same as for the Z80 instruction set simulator.
        This port was contributed by Jacques Pelletier.
-       Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/xtrs/README.txt" target="_blank">README</a> file for further information.
+       Refer to the NuttX board <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/xtrs/README.txt" target="_blank">README</a> file for further information.
       </p>
     <ul>
   </td>
diff --git a/ReleaseNotes b/ReleaseNotes
index 5afe3d5724..27710f0c6b 100644
--- a/ReleaseNotes
+++ b/ReleaseNotes
@@ -8905,25 +8905,25 @@ Additional new features and extended functionality:
         This is based on the similar SAMD20 Xplained Pro board.
 
     * Freescale/NXP KL:
-  
+
       - KL25Z64: Added support for the KL25Z64.  The KL25Z64 is a lower
         memory variant of the KL25Z128 and is used on the Teensy LC.  From
         Michael as SourceForge patch 50.
 
     * Freescale/NXP KL Boards:
-  
+
       - Teensy-LC: Add board support for the Teensy LC board.  Support is
         based off the Freedom KL25Z board.  LED, PWM, and UART0 have been
         tested. The SPI pins are mapped correctly but have not yet been
         tested.  From Michael Hope as SourceForge patch 51.
 
     * NXP LPC111x:
-    
+
       - LPC111x:  Support for the LPC11xx family (the LPC1115 MCU in
         particular).  Contributed by Alan Carvalho de Assis.
 
     * NXP LPC111x Boards:
-    
+
       - LPCXpresso LPC1115:  Support for the LPCXpression LPC1115
         board.  Contributed by Alan Carvalho de Assis.
 
@@ -9158,7 +9158,7 @@ detailed bugfix information):
       - LPC17 USB OHCI:  Correct some initialization of data structures.
         When hub support is enabled, it would overwrite the end of an array
         and clobber some OS data structures.
-      - LPC17xx Ethernet:  Review, update, and modify the Ethernet driver so 
+      - LPC17xx Ethernet:  Review, update, and modify the Ethernet driver so
         that it works better with CONFIG_NET_NOINTS=y.  Also, update all
         LPC17xx networking configurations so that they have
         CONFIG_NET_NOTINTS=y selected.
@@ -9585,7 +9585,7 @@ detailed bugfix information):
     * ARMv7-A:
 
       - Cortex-A5 vfork():  Fix a Cortex-A compilation error when system
-        calls are enabled in modes other than CONFIG_BUILD_KERNEL. 
+        calls are enabled in modes other than CONFIG_BUILD_KERNEL.
 
     * Atmel SAMA5 Drivers:
 
@@ -10099,7 +10099,7 @@ Additional new features and extended functionality:
       - ps command:  The 'ps' command now uses /proc/<pid>/ to obtain task
         status information.  A consequence of this is that you cannot use
         the 'ps' command if the procfs is not enabled and mounted at /proc.
- 
+
     * Applications: apps/system:
 
       - apps/system/hexed:  Port the hexed command line hexadeciamal editor
@@ -10144,7 +10144,7 @@ detailed bugfix information):
 
     * Graphics/Graphic Drivers:
 
-      - ILI9432:  Fixed errors in orientation. Portrait, RPortrait, and 
+      - ILI9432:  Fixed errors in orientation. Portrait, RPortrait, and
         Landscript should work correly now.  They were displayed mirrored.
         From  Marco Krahl.
 
@@ -10321,7 +10321,7 @@ Additional new features and extended functionality:
         pointer indicates that the referenced object may reside either in
         flash or in RAM. The compiler automatically makes 32-bit pointer
         with flag indicating whether referenced object is in flash or RAM
-        and generates code to access either in run-time. Thus, any function 
+        and generates code to access either in run-time. Thus, any function
         hat accepts __memx object can transparently work with RAM and flash
         objects.
         For platforms with a Harvard architecture and a very small RAM like
@@ -10350,7 +10350,7 @@ Additional new features and extended functionality:
         dependencies generated by a Windows compiler so that they can be
         used with the Cygwin make.
       - tools/mkwindeps.sh: A script that coordinates use of cnvwindeps.exe.
-        Dependencies now work on the Cygwin platform when using a Windows 
+        Dependencies now work on the Cygwin platform when using a Windows
         ative toolchain.
 
     * Applications: NSH
@@ -10516,7 +10516,7 @@ Additional new features and extended functionality:
         implemented via ioctl calls.  However, it does not yet implement
         the standard ADC interface.  From Alexander Entinger.
       - U-Blox Modem:  Add an upper half driver for the U-Blox Modem.  From
-        Vladimir Komendantskiy. 
+        Vladimir Komendantskiy.
       - I2C: Add an I2C, "upper half", character drivers to support raw I2C
         data transfers for test applications.
       - RGB LED: Add a driver to manage a RGB LED via PWM.  From Alan
@@ -10857,7 +10857,7 @@ Additional new features and extended functionality:
         Neil Hancock.
       - STM32 L4 QSPI: Add a QSPI driver with DMA support and (optional
         memory mapped mode support. From Dave ziggurat29).
-      - STM32, STM32 L4, and STM32 F7 Serial:  Add support for compliant 
+      - STM32, STM32 L4, and STM32 F7 Serial:  Add support for compliant
         SD-style breaks. From David Sidrane.
       - STM32 L4 CAN: Add CAN support for STM32L4.  From Sebastien Lorquet.
       - STM32 1-Wire:  Add support for a custom 1-wire driver.  The serial
@@ -11079,3 +11079,699 @@ detailed bugfix information):
       - Several Makefiles: Add .PHONY definitions to prevent 'clean up to date'
         message weirdness when 'make clean' is done with no .config or
         Make.defs file.
+
+NuttX-7.17 Release Notes
+------------------------
+
+The 117th release of NuttX, Version 7.17, was made on July 25, 2016,
+and is available for download from the Bitbucket.org website.  Note
+that release consists of two tarballs:  nuttx-7.17.tar.gz and
+apps-7.17.tar.gz.  These are available from:
+
+    https://bitbucket.org/nuttx/nuttx/downloads
+    https://bitbucket.org/nuttx/apps/downloads
+
+Both may be needed (see the top-level nuttx/README.txt file for build
+information).
+
+Additional new features and extended functionality:
+
+    * File System and Block and MTD Drivers:
+
+      - drivers/mtd: Add a driver of IS25xP SPI flash devices.  Based on
+        sst25xx driver.  From Marten Svanfeldt.
+
+    * Networking and Network Drivers:
+
+      - Break out internal interface psock_ioctl().
+
+    * Common Device Drivers:
+
+      - PTYs: Added support for pseduo-terminals: Device drivers that can be
+        used for communications between tasks (usually with re-directed I/O).
+        Based on existing pipe logic.
+      - Button upper half driver:  Added support for poll().
+      - CAN:  Add support for poll. From Paul Alexander Patience.
+      - GPIO:  Add support for a simple GPIO driver.  It supports only pre-
+        configured input, output, and interrupting pins with basic input and
+        output operations.  Interrupt events can lead to notification via a
+        signal.
+      - I/O Expander: Shadow-Mode: The output- and configuration registers of
+        the IO-Expander are held in the microcontrollers memory and only
+        written to the IO-Expander.  This reduces bus traffic and is more
+        error-proof than the normal read-modify-write operation. Retry Mode:
+        If enabled and an error occurs while writing to the IO-Expander the
+        current transmission is automatically repeated once. From Michael
+        Spahlinger.
+      - Pipes/FIFOs:  Add support to allocating different sizes for pipe and
+        fifo buffers.  Adds mkfifo2() and pipe2() which are just like mkfifo()
+        and pipe(), but allow control of the size of the underlying, in-memory
+        circular buffer.  Move pipe() and mkpipe() to the C library, they are
+        no longer core OS interfaces.  Capability currenty used only by PTY
+        logic to support, configurable, smaller buffers for PTYs.
+
+    * SYSLOG/Debug Output:
+
+      - SYSLOG: Consolidated all SYSLOG logic in drivers/syslog.  Added an
+        abstraction layer that supports:  (1) redirection of SYSLOG outpout.
+        This is usually so that you can boot with one SYSLOG output but
+        transition to another SYSLOG output when the OS has initialialized,
+        (2) adds common serialization of interrupt output as a configuration
+        option.  Without this configuration setting, interrupt level output
+        will be asynchronous.  And (3) vsyslog is now a system call and is
+        usable with other-than-FLAT builds.
+      - SYSLOG: syslog() will now automatically redirect output to
+        lowsyslog() if called from an interrupt handler.
+      - Extended SYSLOG logic so that we can send SYSLOG output to a file.
+      - SYSLOG character device channel will now expand LF to CR-LF.
+        Controllable with a configuration option.
+      - Add a SYSLOG character device that can be used to re-direct output
+        to the SYSLOG channel (Not be be confused the the SYSLGO output to a
+        character device).
+      - Debug features are now enabled separately from debug output.
+        (1) CONFIG_DEBUG is gone. It is replaced with CONFIG_DEBUG_FEATURES.
+        (2) The macros dbg() and vdbg() have renamed as _err() and _info(),
+        respectively. This also applies to all of the variants as well,
+        XXdbg() and XXvdbg().  (3) Add a new debug level, _warn() (and
+        all variants XXwarn(), XXvwarn(), etc.). (4) Debug assertions can
+        now be enabled separately from debug output. (5) You can now enable
+        subsystem/device driver debug output at different output levels. For
+        example, CONFIG_DEBUG_FS no longer enables file system debug output
+        It enables general file system debug logic and enables selection of
+        CONFIG_DEBUG_FS_ERROR, CONFIG_DEBUG_FS_WARN, and CONFIG_DEBUG_FS_INFO.
+      - Since the SYSLOG layer now automatically handles low-level vs.
+        high-level output, the low-level (ll) variants of the debug macros
+        were eliminated.
+      - Reviewed all uses of *err().  These macro family should indicate
+        only error conditions.  Convert *err() to either *info() or add
+        ERROR:, depending on if an error is reported.
+      - _alert(): New debug macro: _alert().  This is high priority,
+         unconditional output and is used to simplify and standardize crash
+         error reporting.
+      - Many CONFIG_DEBUG_* options did not have matching macros defined in
+        include/debug.h.  Rather, there were various definitions scattered
+        throughout the sourse tree.  These were collected together and
+        centralized with single macro definitions in include/debug.h
+
+    * Simulation Platform:
+
+      - Added the simulated QSPI (N25Q) flash to the simulation and extened
+        flash simulation capabilities to run with MTD drivers based on config
+        options (currently m25p, sst26 and w25). From Ken Pettit.
+
+    * Atmel SAMV7 Drivers:
+
+      - SPI: SPI-Freq. 40MHz; VARSELECT; hw-features This change adds the
+        following improvements:
+
+          o Increase the allowed SPI-Frequency from 20 to 40 MHz.
+          o Correct and rename the "VARSELECT" option   This option was
+            included in the code as "CONFIG_SPI_VARSELECT" but nowhere
+            defined in a Kconfig file. The change renames it to
+            "CONFIG_SAMV7_SPI_VARSELECT" and corrects the implementation
+            according the datasheet of Atmel. In short, this option
+            switches the processor from "fixed peripheral selection"
+            (single device) to "variable peripheral selection" (multiple
+            devices on the bus).
+          o Add a new Function to the interface to control the timing and
+            delays of the chip according the ChipSelect lines. This function
+            can control the delay between the assertion of the ChipSelect and
+            the first bit, between the last bit and the de-assertion of the
+            ChipSelect and between two ChipSelects. This is needed to tune
+            the transfer according the specification of the connected devices.
+          o Add three "hw-features" for the SAMV7, which controls the behavior
+            of the ChipSelect:
+              - force CS inactive after transfer: this forces a (short) de-
+                assertion of the CS after a transfer, even if more data is
+                available in time
+              - force CS active after transfer: this forces the CS to stay
+                active after a transfer, even if the chip runs out of data.
+                Btw.: this is a prerequisit to make the LASTXFER bit working
+                at all.
+              - escape LASTXFER: this suppresses the LASTXFER bit at the end
+                of the next transfer. The "escape"-Flag is reset automatically.
+
+        From Frank Benkert
+      - TWISHS:  Driver improvements from Michael Spahlinger.
+      - GPIO-Driver fixed for Open-Drain Pins:
+
+          o sam_gpioread: Now the actual line level from the pin is read
+            back.   This is extremely important for Open-Drain Pins, which
+            can be used bidirectionally
+          o Re-Implemented twi_reset-function and enhanced it so it can be
+            called from inside the driver (see next point)
+          o Glitch-Filter: Added a configuration option to enable the twi-
+            built-in glitch filter
+          o Added a "Single Master Mode": In EMC Testing the TWI-Bus got
+            stuck because the TWI-Master detected a Multi-Master access (but
+            there is no second master). With the option "Single Master" we
+            detect these events and automatically trigger a twi_reset. We
+            also do an automatic recovery if a slave got stuck (SDA stays
+            low).
+
+        With the above changes I�C-Bus reliability in harsh environments (eg.
+        EMC) is greatly improved. The small change in the GPIO-Driver was
+        necessary because otherwise you cannot read back the correct line
+        status of Open-Drain Outputs and this is needed by the twi_reset
+        function.  From Michael Spahlinger
+
+    * NXP Freescale LPC43xx Drivers:
+
+      - EMC: Extend LPC43xx EMC code to support SDRAM on a dynamic memory
+        interface.  From Vytautas Lukenskas.
+
+    * NXP Freescale Kinetis:
+
+      - Kinetis K64:  Add basic support for the K64 family.  I leveraged the
+        changes from https://github.com/jmacintyre/nuttx-k64f and merged
+        into the existing kinetis code  with a lot of changes and additions
+        (like pin multiplexing definitions).
+
+    * NXP Freescale Kinetis Drivers:
+
+      - Add a KinetisUSB device controller driver.  Derived from the pic32mx
+        usb driver, which uses the same usb controller.  From kfazz.
+      - Kinetis pwm support, based on the KL pwm driver.  From kfazz.
+      - Kinetis Ethernet:  Add support for the KSZ8081 PHY.
+      - Kinetis Ethernet:  Modified Ethernet driver to try all PHY addresses
+        and then only fail if the driver cannot find a usable PHY address.
+        This means that you no longer have to specific the PHY address in
+        advance.
+      - Kinetis Ethernet:  Add support for CONFIG_NET_NOINTS.  The driver no
+        longer runs the networking at interrupt level but can defer interrupt
+        work to the high-priority work queue.
+
+    * NXP Freescale Kinetis Boards:
+
+      - Teensy-3.x:  Add USB support and a usbnsh configuration.
+        From kfazz (2016-06).
+      - Freedom-K64F: Add support for the NXP Freedom-K64F board at 120MHz.
+        This is primarily the work of Jordan Macintyre.  I leveraged this
+        code from https://github.com/jmacintyre/nuttx-k64f which was, itself,
+        a leverage from the old K60 TWR configuration.  This includes
+        significant corrections (LEDs, buttons, README, etc) and extensions
+        and updates to match more recent BSPs.
+      - Freedom-K64F:  Added a configuration that supports networking.
+
+    * STMicro STM32:
+
+      - STM32 F1-4: Added support for the STM32F105R.  From Konstantin
+        Berezenko.
+      - STM32 F4: Added support for the STM32FF76xxx and STM32FF7xx
+        families. From David Sidrane.
+      - STM32 F1-4:  Add support for Tickless mode (two timer
+        implementation).  From Max Neklyudov.
+      - STM32 L4: Add support for tickless OS, and incidentally timers,
+        PWM, oneshot, free-running....  From ziggurat29.
+
+    * STMicro STM32 Drivers:
+
+      - STM32 F1-4: Add the up_getc() function to STM32 in order to support
+        the minnsh configuration.  From Alan Carvalho de Assis.
+      - STM32 F7: Add SPI driver.  From David Sidrane.
+      - STM32 F7: Add SPI, I2C, and ADC drivers.  From Lok Tep.
+      - STM32 L4: Add ioctls to set/get CAN bit timing in stm32l4.  Add
+        ioctl hooks to allow future management of can id filters. From
+        Sebastien Lorquet.
+      - STM32 L4: Add some CAN mode IOCTL calls.  These will be useful for
+        device autotest when the application boots.  They are redundant
+        with the CONFIG_CAN_LOOPBACK option, which can now just be
+        interpreted as a default setting.  From Sebastien Lorquet.
+      - STM32 F1-4: Port STM32L4 CAN IOCTLs to STM32.  From Sebastien Lorquet.
+      - STM32 L4: Implementation of loopback IOCTLs.  From Sebastien
+        Lorquet.
+      - STM32 F7: Added SDMMC1 support for stm32F7 74-75.  From Lok Tep.
+      - STM32 F7: Add USB support.  From Lok Tep.
+      - STM32 F7: Added PWR, RTC, and BBSRAM support for stm32f7. From David
+        Sidrane.
+      - STM32 F7: Added STMF7xxx RTC.  From David Sidrane.
+      - STM32 F7: Added STM32F7 DBGMCU.  From David Sidrane.
+      - STM32 L4: Port support for both RX FIFOs from STM32 CAN.  From Paul
+        Alexander Patience.
+
+    * STMicro STM32 Boards:
+
+      - Added a minnsh configuration for the STM32F103-Minimum board.  From
+        Alan Carvalho de Assis .
+      - Added support for the Nucleo-F767ZI board. From David Sidrane.
+      - Nucleo-144/Nucleo-F767ZI:  Add test for STM32 F7 SPI.  From David
+        Sidrane.
+      - Nucleo-144: Added SDMMC support to Nucleo-144. From David Sidrane.
+      - Olimex STM32-E4077:  Add support for Olimex STM32 E407 board.  From
+        Mateusz Szafoni.
+      - Nucleo-144: Added USB OTG device to Nucleo-144.  From David Sidrane.
+      - Nucleo-144: Added bbsram test to Nucleo-144.  From David Sidrane.
+      - STM32F4 Disovery: add CAN support for STM32F4 Discovery.  From
+        Matthias Renner.
+      - STM32F4 Disovery:  added a canard configuration files.  From
+        Matthias Renner.
+      - STM32F4 Discovery: Add FPU support for ostest for the STM32F4
+        Disovery platform. From David Alessio.
+      - STM32L476 Discovery: Update stm32l476 disco to include init code for
+        smartfs and nxffs for cases where those fs are included in build.
+        From ziggurat29.
+
+    * C Library/Header Files:
+
+      - include/assert.h: Check if NDEBUG is defined.  From Paul Alexander
+        Patience.
+      - assert.h: Define static assert for C++ usage.  From Paul Alexander
+        Patience.
+      - Add crc64 support. From  Paul Alexander Patience.
+      - hex2bin:  Move the portable library portion of apps/system/hex2bin
+        the C library with the OS internals.  It is used in certain internal
+        boot-loader builds.
+      - Add raise().
+      - libm: This change should significantly improve the performance of
+        single precision floating point math library functions. The vast
+        majority of changes have to do with preventing the compiler from
+        needlessly promoting floats to doubles, performing the calculation
+        with doubles, only to demote the result to float. These changes only
+        affect the math lib functions that return float. From David Alessio.
+      - printf(): If there are no streams, let printf() fall back to use
+        syslog() for output.
+      - Move pipe() and mkpipe() to nuttx/libc, they are no
+        longer core OS interfaces.  Capability currenty used only by PTY logi
+        to support, configurable, smaller buffers for PTYs.
+      - Move driver-related files from include/nuttx to include/nuttx/drivers.
+        Move driver related prototypes out of include/nuttx/fs/fs.h and into
+        new include/drivers/drivers.h.
+      - include /nuttx/lib: Move library-related files from include/nuttx to
+        include/nuttx/lib.
+
+    * Build/Configuration System:
+
+      - Custom Board Configuration: Add logic to support custom board
+        directories that include a Kconfig file.  During the context phase
+        of the build, any Kconfig file in the custom board directory is
+        copied into configs/dummy, replacing the existing Kconfig file with
+        the target Kconfig file.
+      - Remove the includes/apps link to apps/include.  It is no longer
+        used.  From Sebastien Lorquet.
+
+    * Tools:
+
+      - tools/tesbuild.sh will now build NxWM configurations.
+
+    * Appplication Build/Configuration System:
+
+      - Change to the way that apps/ Kconfig files are generated in
+        order to better support reuse of the apps/ directory in NuttX
+        products.  Changes include: Make the full tree use wildcards
+        make.defs, Add empty preconfig rules to 'leaf' makefiles, Use
+        directory.mk for recursive dir makefiles, Individual app kconfig
+        fixes, Recursive Kconfig autogeneration, Add kconfig files for
+        pcode and tiff, and fix a gitignore rule,  From S�bastien Lorquet.
+      - apps/include directory structure reorganized.  There are no longer
+        any header files in the apps/include/. directory.  Rather, sub-
+        directories were added to match the partitioning of apps/ sub-
+        directories and the header files were moved into the appropriate
+        sub-directory.  This change is intended to help with some changes
+        being considered by S�bastien Lorquet.
+      - Call all includes from <apps/bla/bla.h> to "bla/bla.h". From Sebastien
+        Lorquet.
+      - Add apps/include to include path in top-level Make.defs file.
+
+    * Applications: apps/nshlib:
+
+      - Make NSH net-initialization be a configuration option. From Marten
+        Svanfeld.
+      - Add NTP client initialization in NSH network startup logic.  From
+        David S. Alessio .
+      - 'ps' command now prints out the stack usage if stack coloration is
+        enabled.  From Frank Benkert.
+      - Allow stack usage to be disabled on constrained systems. From David
+        Sidrane.
+
+    * Applications: apps/netutils:
+
+      - NTP Client:  Add retries.  From David S. Alessio.
+      - NTP Client:  The NTP client will now optionally use pool.ntp.org as
+        the NTP server; and reset the retry count upon success -- more robust.
+        From David Alessio.
+      - ESP8266: Add logic to set the BAUD rate.  From Pierre-noel Bouteville.
+      - ESP8266: In Kconfig, select ARCH_HAVE_NET when NETUTILS_ESP8266 is
+        selected.  This allows, among other things, support for network debug
+        output.  From Pierre-noel Bouteville.
+
+    * Applications: apps/fsutils:
+
+      - flash_eraseall: IOCTL wrapper for MDCIO_BULKERASE command.   Was in
+        nuttx/drivers/mtd.  Moved to apps/fsutils because the call directly into
+        the OS was incorrect.
+
+    * Applications: apps/canutils:
+
+      - canlib: Basic CAN utility library. From Sebastien Lorquet.
+
+    * Platforms: apps/system:
+
+      - flash_eraseall: Now uses the IOCTL wrapper at apps/fsutils/flash_eraseall.
+
+    * Platforms: apps/platform:
+
+      - Add platform files for Olimex STM32 E407.  From Mateusz Szafoni.
+
+    * Applications: apps/examples:
+
+      - apps/examples/canard:  Add canard example application.  From
+        Matthias Renner.
+      - apps/examples/pty_test: PTY test program.  From Alan Carvalho de
+        Assis.
+
+Works-In-Progress:
+
+    * IEEE802.14.5/6LowPAN.  Hooks and framework for this effort were
+      introduced in NuttX-7.15.  Work has continued on this effort on
+      forks from the main repositories, albeit with many interruptions.
+      The completion of this wireless feature will postponed until at
+      least NuttX-7.18.
+
+    * i.MX6 SMP.  Partially functional, but there is more that still
+      needs to be done.
+
+Bugfixes.  Only the most critical bugfixes are listed here (see the
+ChangeLog for the complete list of bugfixes and for additional, more
+detailed bugfix information):
+
+    * Core OS:
+
+      - semaphores: Need to set errno to EINVAL on errors in sem_post()
+        and sem_wait(). From Paul Alexander Patience.
+
+    * File System/Block Drivers/MTD Drivers:
+
+      - Several MTD FLASH drivers nullify the freed 'priv' structure and
+        failed to return NULL as stated in the comments. Result, will
+        operate on a NULL pointer later.  Noted by David Sidrane.
+      - VFS ioctl().  Per comments from David Sidrane, file_ioctl() should
+        not return succeed if the ioctl method is not supported.  It
+        probably should return ENOTTY in that case.
+      - SST26 Driver: Before accessing the sst26 flash, the "Global Unlock"
+        command must me executed, which I do in the sst26 driver.  BUT re-
+        reading the datasheet, the WREN instruction is required to enable
+        the execution of this command. This was not done. I have no idea how
+        the driver currently works except by chance. The writes should never
+        happen at all, the flash is half-enabled!  From Sebastien Lorquet.
+      - N25Qxx Driver: Alter the notion of 'blocksize' to be equivalent to
+        'flash write page size' in order to align with assumptions in the
+        smartfs driver (at least, maybe other things do as well).  Correct a
+        bug that was previously masked by having blocksize=eraseblocksize
+        which would cause buffer overflows and delicious hardfaults.
+        Trivial spelling changes in comments, etc.  From ziggurat29.
+      - SmartFS: Fix a 32-byte memory leak.  From Ken Pettit.
+      - SMART MTD layer: Fixes freesector logic error when sectorsPerBlk=256,
+        adds DEBUGASSERT for invalid geometry and additional memory debug
+        logic.  Also fixes the dangling pointer on error bug.  From Ken
+        Pettit.
+
+    * Common Drivers:
+
+      - USB CDC/ACM Device Class: cdcacm_unbind leaks write request objects.
+        This arises due to freeing the bulk IN endpoint before the loop
+        that frees the requests via cdcasm_freereq.  That function checks
+        the parameters and skips the freeing if either is NULL.  Freeing
+        the bulk IN enpoint will cause the first param to be NULL, thereby
+        bypassing the free operation.  To fix, I moved the release of the
+        bulk IN endpoint until after to loop (much as was the case for the
+        OUT and read requests, which did not exhibit the problem).  From
+        ziggurat29.
+      - Pipes and FIFOs: Add missing configuration for pipe ring buffer
+        size.  From Frank Benkert.
+      - UART 16550: Handle when CONFIG_SERIAL_UART_ARCH_IOCTL is not
+        enabled. From Heath Petersen.
+      - Common Serial Upper Half:  Fix a race condition noted by Stefan
+        Kolb.  Between the test if the TX buffer is full and entering a
+        critical section, bytes may be removed from the TX buffer making
+        the wait unnecessary.  The unnecessary wait is an inefficiency,
+        but not really a problem.  But with USB CDC/ACM it can be a problem
+        because the entire TX buffer may be emptied when we lose the race.
+        If that happens that uart_putxmitchar() can hang waiting for data
+        to be removed from an empty TX buffer.
+      - USB MSC Device Class: Add locks when removing request from queue.
+        From Wolfgang Reissnegger.
+      - USB MSC Device Class: Fix reversed logic on waiting for SCSI thread
+        start.  The scsi thread was waiting for the wrong condition.
+        However, this was masked by the fact that the code creating the
+        scsi thread was also holding usbmsc_scsi_lock(priv) while
+        initializing data, hence this lock synchronized the scsi thread
+        start with init completion.  From Wolfgang Reissnegger.
+
+    * Graphics and Graphic Drivers:
+
+      - Correct conditional compilation in ST7565 LCD driver.  From Pierre-
+        noel Bouteville
+
+    * Networking:
+
+      - In both IPv6 and IPv4 incoming logic:  (1) Should check if the
+        packet size is large enough before trying to access the packet
+        length in the IP header.  (2) In the comparison between the IP
+        length and the full packet length, need to subtract the size of
+        he link layer header before making the comparison or we will get
+        false positives (i.e., the packet is really too small)
+      - TCP Networking: While working with version 7.10 I discovered a
+        problem in TCP stack that could be observed on high network load.
+        Generally speaking, the problem is that RST flag is set in
+        unnecessary case, in which between loss of some TCP packet and its
+        proper retransmission, another packets had been successfully sent.
+        The scenario is as follows:  NuttX did not receive ACK for some sent
+        packet, so it has been probably lost somewhere. But before its
+        retransmission starts, NuttX is correctly issuing next TCP packets,
+        with sequence numbers increasing properly. When the retransmission
+        of previously lost packet finally succeeds, tcp_input receives the
+        accumulated ACK value, which acknowledges also the packets sent in
+        the meantime (i.e. between unsuccessful sending of lost packet and
+        its proper retransmission). However, variable unackseq is still set
+        to conn->isn + conn->sent, which is truth only if no further
+        packets transmission occurred in the meantime.  Because of incorrect
+        (in such specific case) unackseq value, few lines further condition
+        if (ackseq <= unackseq)is not met, and, as a result, we are going to
+        reset label.  From Jakub Lagwa.
+
+    * ARMv7-M:
+
+      - ARM stack check: Fix double fault on IDLE task with stack size = 0.
+        From David Sidrane.
+
+    * Atmel SAMV7 Drivers:
+
+      - CAN: CAN Message Filtering fixed: (1) stdfilters didn't work because
+        the filter was never enabled (wrong number of bits to shift), and
+        (2) Filters were never used because the configuration register
+        cannot be written without using the initialization mode. Both bugs
+        are fixed by this change. Filtering has been tested with both
+        standard and extended identifiers and is now working properly. From
+        Michael Spahlinger.
+
+    * Atmel SAMA5:
+
+
+    * Atmel SAM3/4 Drivers:
+
+      - Fix some errors in AFEC header file.  From OrbitalFox.
+      - DAC: DACC_WPMR_WPKEY_MASK -> DACC_WPMR_WPKEY.  From Wolfgang
+        Reissnegge.
+      - Timer:  Fix ops check in TCIOC_STOP.  From Wolfgang Reissnegge.
+      - I2C: Fix reversed logic in twi_startmessage().  From Wolfgang
+        Reissnegger.
+      - SAM3/4 UDP: Fix handling of endpoint RX FIFO banks.  This fixes
+        a race condition where the HW fills a FIFO bank while the SW is
+        busy, resulting in out of sequence USB packets.
+
+    * Atmel SAMV7 Drivers:
+
+      - USBHS Device:  This change solves a problem which causes data loss
+        while sending data via USB. This problem is caused by an incorrect
+        handling of the endpoint state in the USB driver sam_usbdevhs.  This
+        leads under some circumstances to situations in which an DMA
+        transfer is setup while a previous DMA transfer is currently active.
+        Amongst other things I introduced the new endpoint state
+        USBHS_EPSTATE_SENDING_DMA for the fix.  To reproduce the problem, I
+        used a program which send as many data as possible via a CDC/ACM
+        device and verified the received data on the PC.  From Stefan Kolb.
+
+    * NXP Freescale Kinetis Drivers:
+
+      - Timers: Support up to 8 channels per timer.  From kfazz.
+
+    * NXP Freescale Kinetis Boards:
+
+      - Teensy 3.x clock fixes:  The High Gain bit in MCG_C1 was preventing
+        teensy from booting except after a programming session. The second
+        change doesn't appear to change any functionality, but complies with
+        restrictions in the k20 family reference manual on FEI -> FBE clock
+        transiions.  From kfazz.
+
+    * NXP Freescale LPC17xx Drivers:
+
+      - LPC17 Ethernet:  Needs to correctly ignore PHYID2 revision number
+        when comparing PHY IDs.
+
+    * NXP Freescale LPC43xx Drivers:
+
+      - Fix errors in GPIO interrupt logic.  From v01d (phreakuencies)
+      - Ethernet:  Correct auto-negotiation mode in the LPC43xx Ethernet.
+        From Alexander Vasiljev
+      - Writing zero to NVIC_IRQ_ENABLE has no effect.  Disable interrupts
+        with  NVIC_IRQ_CLEAR. From Paul Alexander Patience.
+      - SPIFI: If CONFIG_SPIFI_SECTOR512 undefined, lpc43_bwrite doesn't do
+        actual write (probably copy/paste errors). Still not sure about
+        current state of lpc43_spifi implementation, but for me NXFFS works
+        with this change.  From Vytautas Lukenskas.
+
+    * Qemu-i486:
+
+      - Fix qemu-i486/ostest/Make.defs test for M32.  From Heath Petersen.
+
+    * SiLabs EFM32 Drivers:
+
+      - Fix EFM32 FLASH conditional compilation.  From Pierre-noel
+        Bouteville
+      - Writing zero to NVIC_IRQ_ENABLE has no effect.  Disable interrupts
+        with  NVIC_IRQ_CLEAR. From Paul Alexander Patience.
+
+    * STMicro STM32:
+
+      - STM32 F1-F4:  In PWM driver, just update duty if frequency is not
+        changed and PSM started.  This removeis glitch or blinking when
+        only duty is frequently changed.  From Pierre-noel Bouteville.
+
+    * STMicro STM32 Drivers:
+
+      - STM32 F7: Fixed STM32F7 DMA stm32_dmacapable.  DMA working on SDMMC.
+        From David Sidrane.
+      - STM32 F1-F4 Timer Driver: Change calculation of per- timer pre-scaler
+        value.  Add support for all timers
+      - STM32 F1-F4: Correct conditional compilation in STM32 timer capture
+        logic.  From Pierre-noel Bouteville
+      - STM32 F1-F4: Fix STM32 DMA code and configuration for STM32F37X chips.
+        From Marten Svanfeldt.
+      - STM32 F1-F4: Fix compilation errors in debug mode of stm32_pwm.c.
+        From Konstantin Berezenko.
+      - STM32 F1-F4: Correct the CAN2 RX IRQ number for stm32f10xx chips.
+        From Konstantin Berezenko.
+      - STM32 F1-F4: Move backup domain reset to to earlier in the
+        initialization sequence (stm32_rcc.c() in order to avoid disabling
+        LSE during RTC initialiation.  From Alan Carvalho de Assis.
+      - STM32 F1-F4: When configuring a GPIO via stm32_configgpio() the
+        function will first set the mode to output and then set the initial
+        state of the gpio later on.  If you have an application with an
+        externaly pulled-up pin, this would lead to a glitch on the line
+        that may be dangerous in some applications (e.G. Reset Line for
+        other chips, etc).  This changes sets the output state before
+        configuring the pin as an output.  From Pascal Speck .
+      - STM32 F7: Apply Pascal Speck's GPIO STM32 change to STM32 L4.
+      - STM32 L4: Apply Pascal Speck's GPIO STM32 change to STM32 L4.
+        From Sebastien Lorquet.
+      - STM32 F7:  BUGFIX: PLLs IS2 and SAI P Calculation. From David
+        Sidrane.
+      - STM32 L4:  STM32 CAN fixes need to be backported to STM32L4 as well.
+      - STM32 F1-F4 and L4: Writing zero to NVIC_IRQ_ENABLE has no effect.
+        Disable interrupts with  NVIC_IRQ_CLEAR. From Paul Alexander
+        Patience.
+      - STM32 F7: STMF7xxx RTC: (1) Remove proxy #defines, (2) Ensure the
+        LSE(ON) etal are set and remembered in a) A cold start (RTC_MAGIC
+        invalid) of the RTC, and b) A warm start (RTC_MAGIC valid) of the
+        RTC but a clock change.  The change was needed because in bench
+        testing a merge of the latest's STM32  53ec3ca (and friends) it
+        became apparent that the sequence of operation is wrong in the
+        reset of the Backup Domain in the RCC code.  PWR is required before
+        the Backup Domain can be futzed with. !!!This Code should be tested
+        on STM32 and if needed rippled to the STM32 families.  From David
+        Sidrane.
+      - STM32 F1-F4: STM32 BBSRAM fixed (and formatted) flags.  From David
+        Sidrane.
+      - STM32 F7: STM32F7 BBSRAM fixed (and formatted) flags. From David
+        Sidrane.
+      - STM32 L4: Fix incorrect clock setup for LPTIM1.  From ziggurat29.
+      - STM32 F4/L4 RTC ALARM: were enabling interrupts too early in the
+        power-up sequence,  BEFORE the interrupt system was being
+        initialized.
+
+    * STMicro STM32 Boards:
+
+      - STM32 board.h: Fix STM32 timer input clock definitions.  From David
+        Sidrane.
+
+    * TI Tiva Drivers:
+
+      - Bug Fix in tiva_serial.c - UART5, UART6 and UART7 were not being
+        configured as TTYS0 for printing over serial console. From Shirshak
+        Sengupta.
+
+    * C Library/Header Files:
+
+      - include/signal.h:  Change type of SIG_ERR, SIG_IGN, ... to
+        _sa_handler_t.  The type void does not work with the IAR toolchain.
+        From Aleksandr Vyhovanec.
+      - crc16: fix error. From  Paul Alexander Patience.
+      - strtoul() and strtoull():  Fix errno settings required by function
+        definition.  Resolved Bitbucket Issue #1. From Sebastien Lorquet.
+
+    * Build/Configuration System:
+
+      - Build system: This change fixes a build problem that only occurs
+        when reconfiguring from Linux to Windows or vice-versa.  It is a
+        problem that was present but not usually experienced until two
+        things happened: (1) The pre_config target was added to run before
+        the menconfig operation and (2) the context target was added before
+        the pre_config target in order to set up the correct symbolic links
+        (in the apps/platform directory) needed by the pre_config target.
+        But then now if you start with a Linux system and run 'make
+        menuconfig' to switch to Linux, the context target will execute
+        first and set up POSIX style symbolic links before doing the
+        menuconfig.  Then after the menuconfig, the make will fail on
+        Windows if you are using a Windows native toolchain because that
+        native toolchain cannot follow the Cygwin- style symbolic links.
+        The fix here is to also execute the clean_context AFTER executing
+        menuconfig.  A lot more happens now:  It used to be that doing
+        'make menuconfig' only did the menuconfig operation.  Now it does
+        context, pre_config, menuconfig, clean_context.  Not nearly as
+        snappy as it used to be.
+      - Need to build the drivers/ directory even it file descriptors are
+        not supported.  There are things in the drivers/ directory that are
+        still needed (like SYSLOG logic).
+      - Remove all inclusion of header files from the apps/include
+        directory from NuttX core logic.  There should be no dependency on
+        logic within NuttX on logic within apps/.  This caused a lot of
+        reshuffling of logic:  binfmt pcode support, usbmonitor is now a
+        kernel thread, TZ/Olson database moved to libc/zoneinfo.
+
+    * Application Build/Configuration System:
+
+      - Make sure that APPNAME is defined in all Makefiles that generate
+        applications.  From Sebastien Lorquet.
+
+    * apps/builtins:
+
+      - apps/builtins: exec_builtin was not using the provided open flags.
+        As a result >> redirection was not working; it was treated the same
+        as >.
+
+    * apps/nshlib:
+
+      - apps/nshilib: PS Command: When Priority Inheritance is enabled, the
+        format of /proc/<PID>/status changes to show both the current
+        priority and the thread�s base priority.  This messes up the format
+        of cmd_ps. From David Alessio.
+
+    * apps/netutils:
+
+      - apps/netutils, uIP webserver:  Fix a data declaration in a header
+        file.
+
+    * apps/canutils:
+
+      - apps/canutils/libuavcan: Fix for recent change to STM32 timer
+        frequency definiitions.
+
+    * apps/examples:
+
+      - apps/examples/alarm: ioctl call was clobbering file descriptor.
+      - apps/examples/can: Some variables were not declared in all required
+        cases. From Sebastien Lorquet.
+      - apps/examples/media: media example was intended to take either a
+        command line argument, or a compiled-in default value from config.
+        However, the default was ignored, leading to confusing error
+        messages. From ziggurat29.