path: root/nuttx/Documentation/NuttX.html



<html>
<head>
<title>NuttX</title>
</head>
<body background="backgd.gif">
<hr><hr>
<table width ="100%">
  <tr align="center" bgcolor="#e4e4e4">
    <td>
      <h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
      <p>Last Updated: February 18, 2013</p>
    </td>
  </tr>
</table>
<hr><hr>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
    <td>
  <h1>Table of Contents</h1>
    </td>
  </tr>
</table>

<center><table width ="80%">
<tr>
<td>
<table>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#overview">Overview</a>.<br>
    What is NuttX?  Look at all those files and features... How can it be a tiny OS?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#group">NuttX Discussion Group</a>.<br>
    Do you want to talk about NuttX features?  Do you need some help?  Problems?  Bugs?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#downloads">Downloads</a>.<br>
    Where can I get NuttX?  What is the current development status?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#platforms">Supported Platforms</a>.<br>
    What target platforms has NuttX been ported to?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#environments">Development Environments</a>.<br>
    What kinds of host cross-development platforms can be used with NuttX?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#footprint">Memory Footprint</a>.<br>
    Just how big is it?  Do I have enough memory to use NuttX?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#licensing">Licensing</a>.<br>
    Are there any licensing restrictions for the use of NuttX? (Almost none)
    Will there be problems if I link my proprietary code with NuttX? (No)
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#history">Release History</a><br>
    What has changed in the last release of NuttX?
    What unreleased changes are pending in SVN?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#TODO">Bugs, Issues, <i>Things-To-Do</i></a>.<br>
    Software is never finished nor ever tested well enough.
    (Do you want to help develop NuttX?  If so, send me an email).
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#documentation">Other Documentation</a>.<br>
    What other NuttX documentation is available?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#trademarks">Trademarks</a>.<br>
    Some of the words used in this document belong to other people.
  </td>
</tr>
</table>
</td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="overview"><h1>Overview</h1></a>
  </td>
  </tr>
</table>

<p>
  <b>Goals</b>.
  NuttX is a real timed embedded operating system (RTOS).
  Its goals are:
<p>
<center><table width="90%">
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Small Footprint</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Usable in all but the tightest micro-controller environments,
      The focus is on the tiny-to-small, deeply embedded environment.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Rich Feature OS Set</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      The goal is to provide implementations of most standard POSIX OS interfaces
      to support a rich, multi-threaded development environment for deeply embedded
      processors.
    </p>
      NON-GOALS: (1) It is not a goal to provide the level of OS features like those provided by Linux.
      In order to work with smaller MCUs, small footprint must be more important than an extensive feature set.
      But standard compliance is more important than small footprint.
      Surely a smaller RTOS could be produced by ignoring standards.
      Think of NuttX is a tiny Linux work-alike with a much reduced feature set.
      (2) There is no MMU-based support for processes.
      At present, NuttX assumes a flat address space.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Highly Scalable</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Fully scalable from tiny (8-bit) to moderate embedded (32-bit).
      Scalability with rich feature set is accomplished with:
      Many tiny source files, link from static libraries, highly configurable, use of
      weak symbols when available.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Standards Compliance</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      NuttX strives to achieve a high degree of standards compliance.
      The primary governing standards are POSIX and ANSI standards.
      Additional standard APIs from Unix and other common RTOS's are
      adopted for functionality not available under these standards
      or for functionality that is not appropriate for the deeply-embedded
      RTOS (such as <code>fork()</code>).
    </p>
    <p>
      Because of this standards conformance, software developed under other
      standard OSs (such as Linux) should port easily to NuttX.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Real-Time</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Fully pre-emptible, fixed priority and round-robin scheduling.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Totally Open</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Non-restrictive BSD license.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>GNU Toolchains</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Compatible GNU toolchains based on <a href="http://buildroot.uclibc.org/">buildroot</a>
      available for
      <a href="https://sourceforge.net/projects/nuttx/files/">download</a>
      to provide a complete development environment for many architectures.
    </p>
</tr>
</table></center>

<p>
  <b>Feature Set</b>.
  Key features of NuttX include:
<p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Standards Compliant Core Task Management</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Fully pre-emptible.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Naturally scalable.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Highly configurable.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Easily extensible to new processor architectures, SoC architecture, or board architectures.
        A <a href="NuttxPortingGuide.html">Porting Guide</a> is available.
      </li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>FIFO and round-robin scheduling.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Realtime, deterministic, with support for priority inheritance</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>POSIX/ANSI-like task controls, named message queues, counting semaphores, clocks/timers, signals, pthreads, environment variables, filesystem.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>VxWorks-like task management and watchdog timers.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>BSD socket interface.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Extensions to manage pre-emption.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Optional tasks with address environments (<i>Processes</i>).</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Inheritable &quot;controlling terminals&quot; and I/O re-direction.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>On-demand paging.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <li>System logging.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>May be built either as an open, flat embedded RTOS or as a separately built, secure micro-kernel with a system call interface.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Well documented in the NuttX <a href="NuttxUserGuide.html">User Guide</a>.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>File system</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Tiny, in-memory, root pseudo-file-system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Virtual file system supports drivers and mountpoints.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Mount-able volumes.  Bind mountpoint, filesystem, and block device driver.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Generic system logging (SYSLOG) support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        FAT12/16/32 filesystem support with optional FAT long file name support<small><sup>1</sup></small>.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NFS Client. Client side support for a Network File System (NFS, version 3, UDP).
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NXFFS. The tiny NuttX wear-leveling FLASH file system.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>ROMFS filesystem support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>BINFS pseudo-filesystem support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        A <a href="NuttXBinfmt.html">binary loader</a> with support for the following formats:
        <ul>
          <li>Separately linked ELF modules.</li>
          <li>
            Separately linked <a href="NuttXNxFlat.html">NXFLAT</a> modules.
            NXFLAT is a binary format that can be XIP from a file system.
          </li>
          <li>
            &quot;Built-In&quot; applications.</li>
          </li>
        </ul>
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>PATH variable support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><small>
      <sup>1</sup>
      FAT long file name support may be subject to certain Microsoft patent restrictions if enabled.
      See the top-level <code>COPYING</code> file for details.
    </small></p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Device Drivers</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Supports character and block drivers as well as specialized driver interfaces.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Network, USB (host), USB (device), serial, CAN, ADC, DAC, PWM, Quadrature Encoder, and watchdog timer driver architectures.
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        RAMDISK, pipes, FIFO, <code>/dev/null</code>, <code>/dev/zero</code>, <code>/dev/random</code>, and loop drivers.
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Generic driver for SPI-based or SDIO-based MMC/SD/SDH cards.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><a href="NuttxPortingGuide.html#pwrmgmt">Power management</a> sub-system.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>ModBus support provided by built-in <a href="http://freemodbus.berlios.de/">FreeModBus</a> version 1.5.0.</li>
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>C/C++ Libraries</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Standard C Library Fully integrated into the OS.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Includes floating point support via a Standard Math Library.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Add-on <a href="http://cxx.uclibc.org/">uClibc++</a> module provides Standard C++ Library (LGPL).</li>
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Networking</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>TCP/IP, UDP, ICMP, IGMPv2 (client) stacks.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>SLIP</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>A port cJSON</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Small footprint (based on uIP).</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>BSD compatible socket layer.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Networking utilities (DHCP server and client, SMTP client, TELNET client, FTP server and client, TFTP client, HTTP server and client).  Inheritable TELNET sessions (as &quot;controlling terminal&quot;)</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NFS Client. Client side support for a Network File System (NFS, version 3, UDP).
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        A NuttX port of Jeff Poskanzer's <a href="http://acme.com/software/thttpd">THTTPD</a> HTTP server
        integrated with the NuttX <a href="NuttXBinfmt.html">binary loader</a> to provide true, embedded CGI.
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        UDP Network Discover (Contributed by Richard Cochran).
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        XML RPC Server (Contributed by Richard Cochran).
      </li>
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>FLASH Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>MTD</i>-inspired interface for <i>M</i>emory <i>T</i>echnology <i>D</i>evices.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>FTL</i>.  Simple <i>F</i>lash <i>T</i>ranslation <i>L</i>ayer support file systems on FLASH.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>NXFFS. the NuttX wear-leveling FLASH file system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Support for SPI-based FLASH and FRAM devices.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>USB Host Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB host architecture for USB host controller drivers and device-dependent USB class drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB host controller drivers available for the NXP LPC17xx.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Device-dependent USB class drivers available for USB mass storage and HID keyboard.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>USB Device Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>Gadget</i>-like architecture for USB device controller drivers and device-dependent USB class drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB device controller drivers available for the PIC32, NXP LPC17xx, LPC214x, LPC313x, LPC43xx, STMicro STM32 and TI DM320.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Device-dependent USB class drivers available for USB serial (CDC/ACM and a PL2303 emulation), for USB mass storage, and for a composite CDC/ACM and mass storage device.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Built-in <a href="UsbTrace.html">USB trace</a> functionality for USB debug.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Graphics Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Framebuffer drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>LCD drivers for both parallel and SPI LCDs and OLEDs.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         NX: A graphics library, tiny windowing system and tiny font support that works with either framebuffer or LCD drivers.
         Documented in the <a href="NXGraphicsSubsystem.html">NX Graphics Subsystem</a>
         manual.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Font management sub-system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         <a href="NxWidgets.html">NxWidgets</a>: NXWidgets is library of graphic objects, or &quot;widgets,&quot (labels, buttons, text boxes, images, sliders, progress bars, etc.). NXWidgets is written in C++ and integrates seamlessly with the NuttX NX graphics and font management subsystems.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         <a href="NxWidgets.html">NxWM</a>: NxWM is the tiny NuttX window manager based on NX and NxWidgets.
      </li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Input Devices</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Touchscreen, USB keyboard, GPIO-based buttons and keypads. </li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Analog Devices</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Support for Analog-to-Digital conversion (ADC), Digital-to-Analog conversion (DAC), multiplexers, and amplifiers.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Motor Control</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Pulse width modulation (PWM) / Pulse count modulation.</li>
    </p>
</tr>
</table></center>

<p>
  <b>NuttX Add-Ons</b>.
  The following packages are available to extend the basic NuttX feature set:
</p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>NuttShell (NSH)</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>A small, scalable, bash-like shell for NuttX with rich feature set and small footprint.
        See the <a href="NuttShell.html">NuttShell User Guide</a>.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Pascal Compiler with NuttX runtime P-Code interpreter add-on</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>The Pascal add-on is available for download from the
        <a href="http://sourceforge.net/projects/nuttx/files/">SourceForge</a>
        website.</li>
    </p>
  </td>
</tr>
</table></center>

<p>
  <b>Look at all those files and features... How can it be a tiny OS?</b>.
  The NuttX feature list (above) is fairly long and if you look at the NuttX
  source tree, you will see that there are hundreds of source files comprising
  NuttX.  How can NuttX be a tiny OS with all of that?
</p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Lots of Features -- More can be smaller!</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      The philosophy behind that NuttX is that lots of features are great... <i>BUT</i>
      also that if you don't use those features, then you should not have to pay a penalty
      for the unused features.
      And, with NuttX, you don't!  If you don't use a feature, it will not
      be included in the final executable binary.
      You only have to pay the penalty of increased footprint for the features
      that you actually use.
    </p>
    <p>
      Using a variety of technologies, NuttX can scale from the very tiny to
      the moderate-size system.  I have executed NuttX with some simple applications
      in as little as 32K <i>total</i> memory (code and data).
      On the other hand, typical, richly featured NuttX builds require more like 64K
      (and if all of the features are used, this can push 100K).
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Many, many files -- More really is smaller!</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      One may be intimidated by the size NuttX source tree.  There are hundreds of source files!
      How can that be a tiny OS?
      Actually, the large number of files is one of the tricks to keep NuttX small and
      as scalable as possible.
      Most files contain only a single function. 
      Sometimes just one tiny function with only a few lines of code.
      Why?
    </p>
    <ul>
      <li>
        <b>Static Libraries</b>.
        Because in the NuttX build processed, objects are compiled and saved into
        <i>static libraries</i> (<i>archives</i>).
        Then, when the file executable is linked, only the object files that are needed
        are extracted from the archive and added to the final executable.
        By having many, many tiny source files, you can assure that no code that you do
        not execute is ever included in the link.
        And by having many, tiny source files you have better granularity --
        if you don't use that tiny function of even just a few lines of code, it will
        not be included in the binary.
      </li>
    </ul>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Other Tricks</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      As mentioned above, the use of many, tiny source files and linking from static
      libraries keeps the size of NuttX down.
      Other tricks used in NuttX include:
    </p>
    <ul>
      <li>
         <b>Configuration Files</b>.
         Before you build NuttX, you must provide a configuration file that specifies
         what features you plan to use and which features you do not.
         This configuration file contains a long list of settings that control
         what is built into NuttX and what is not.
         There are hundreds of such settings
         (see the <a href="NuttxPortingGuide.html#apndxconfigs">NuttX Porting Guide</a>
         for a partial list that excludes platform specific settings).
         These many, many configuration options allow NuttX to be highly tuned to
         meet size requirements.
         The downside to all of these configuration options is that it greatly
         complicates the maintenance of NuttX -- but that is my problem, not yours.
      </li>
      <li>
         <b>Weak Symbols</b>
         The GNU toolchain supports <i>weak</i> symbols and these also help to keep
         the size of NuttX down.
         Weak symbols prevent object files from being drawn into the link even if they
         are accessed from source code.
         Careful use of weak symbols is another trick for keep unused code out of the
         final binary.
      </li>
    </ul>
  </td>
</tr>

</table></center>


<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="group"><h1>NuttX Discussion Group</h1></a>
  </td>
  </tr>
</table>

<p>
  Most NuttX-related discussion occurs on the <a href="http://tech.groups.yahoo.com/group/nuttx/" target="_top"><i>Yahoo!</i> NuttX group</a>.
  You are cordially invited to <a href="http://groups.yahoo.com/group/nuttx/join" target="_top">join</a>.
  I make a special effort to answer any questions and provide any help that I can.
</p>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="downloads"><h1>Downloads</h1></a>
  </td>
  </tr>
</table>

<h2>nuttx-6.25 Release Notes</h2>
<p>
  The 92<sup>nd</sup> release of NuttX, Version 6.25, was made on February 1, 2013, and is available for download from the
  <a href="http://sourceforge.net/projects/nuttx/files/">SourceForge</a> website.
  Note that the release consists of two tarballs:  <code>nuttx-6.25.tar.gz</code> and <code>apps-6.25.tar.gz</code>.
  Both may be needed (see the top-level <code>nuttx/README.txt</code> file for build information)
  The change log associated with the release is available <a href="#currentrelease">here</a>.
  Unreleased changes after this release are available in SVN.
  These unreleased changes are also listed <a href="#pendingchanges">here</a>.
</p>
<p>
  This release corresponds with SVN release number: r5595,
  Note that all SVN information has been stripped from the tarballs.
  If you need the SVN configuration, you should check out directly from SVN.
  Revision r5595 should equivalent to release 6.25 of NuttX:
</p>
<ul><pre>
svn checkout -r5595 svn://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
</pre></ul>
<p>Or (HTTP):</p>
<ul><pre>
svn checkout -r5595 http://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
</pre></ul>

<p>
  <b>Additional new features and extended functionality</b>
</p>
<ul>
  <li>
    <p>
      <b>OS Initialization</b>
    </p>
    <ul>
      <li>
        Removed support for <code>CONFIG_BUILTIN_APP_START</code>. 
        This is not really a useful feature and creates a violation of the OS layered architecture.
    </ul>
  </li>
  <li>
    <p>
      <b>Task Creation</b>
    </p>
    <ul>
      <li>
        Implement a simple <code>vfork()</code>).
        In NuttX-6.25, this interface is available only for ARM7/9, ARMv7-M (Cortext-M3/4), and MIPS32 (PIC32MX) platforms.
      </li>
      <li>
        <code>exec()</code> now sets the priority of the new task to the same priority as the parent task (instead of the arbirtrary value of 50).
      </li>
      <li>
        New, partially complient implementations of <code>execv()</code> and <code>execl()</code>.
        These are only partially compliant because they do not overlay any existing &quot;process space&quot; but rather create the new task and <code>exit()</code>.
      </li>
      <li>
        Add a complete implementation of <code>posix_spawn()</code>.
        This standard interface is a better match for an MMU-less architecture than are <code>vfork()</code>) plus <code>execv()</code> or <code>execl()</code>.
      </li>
      <li>
        Add a task start hook that will be called before the task main executes.
        This can be used, for example, to schedule C++ static constructors to run automatically in the context of the new task.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Task Parentage</b>
    </p>
    <ul>
      <li>
        Repartitioned tasking data structures.
        All shared resources are now collected together in a &quot;task group&quot;. 
        A &quot;task group&quot; includes the resource for the original task that are shared with all of the <code>pthreads</code> created by the task.
      </li>
      <li>
        Added support for remember the parent &quot;task group&quot; when a new task is started.
      </li>
      <li>
        Added optional support to record the membership of each thread in the &quot;task group&quot;.
      </li>
      <li>
        Implement support for retaining child task status in the &quot;task group&quot; after the child task exists.
        This is behavior required by POSIX.
        But in NuttX is only enabled with <code>CONFIG_SCHED_HAVE_PARENT</code> and <code>CONFIG_SCHED_CHILD_STATUS</code>.
      </li>
      <li>
        Add internal logic to &quot;reparent&quot; a task.
        This is useful, for example, where the child task is created through a trampoline task that redirects I/O.
        Reparenting allows the caller of <code>posix_spawn()</code> to be reparented for the eventual child thread.
      </li>
      <li>
        Added support for <code>SIGCHLD</code>.
        Sent to all members of the parent &quot;task group&quot; when the finall member of the child task group exits.
      </li>
      <li>
        If <code>SIGCHLD</code> and retention of child task exist status are enabled, then a more spec-compliant version of <code>waitpid()</code> is enabled.
      </li>
      <li>
        New interfaces <code>waitid()</code> and <code>wait()</code> are also enabled when <code>SIGCHLD</code> is enabled.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>File System</b>
    </p>
    <ul>
      <li>
        <code>dup()</code> and <code>dup2()</code> can new be used with opened files in a mounted file system.
        This supports re-direction of output in NSH to files.
      </li>
      <li>
        The <code>binfs</code> file system was moved from <code>apps/builtin</code> to <code>fs/binfs</code>.
        The <code>binfs</code> file system was extended to support execution of &quot;builtin applications&quot; using <code>exec()</code>, <code>execv()</code>, <code>execl()</code>, or <code>posix_spawn()</code>.
      </li>
      <li>
        Added logic based on <code>SIGCHLD</code> to automatically unload and clean-up after running a task that was loaded into memory.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Binary Formats</b>
    </p>
    <ul>
      <li>
        Much of the logic for &quot;builtin applications&quot; was moved from <code>apps/builtin</code> to <code>nuttx/binfmt/libbuiltin</code>.
        Includes some extensions contributed by Mike Smith.
      </li>
      <li>
        A binary loader was added for builtin applications to support execution of &quot;builtin applications&quot; using <code>exec()</code>, <code>execv()</code>, <code>execl()</code>, or <code>posix_spawn()</code>.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Drivers</b>
    </p>
    <ul>
      <li>
        Added logic to marshal and serialized &quot;out-of-band&quot; keyboard commands (such as cursor controls and key release events) intermixed with normal ASCII keypress data.
        The encoding is partially integrated in the HID keyboard driver and the decoding is fully integrated into the <code>apps/examples</code> <code>hidkbd/</code> and <code>keypadtest/</code> (the latter contributed by Denis Carlikli).
      </li>
      <li>
        Driver for the UG-2864HSWEG01 OLED contributed by Darcy Gong.
      </li>
      <li>
        Add support for removable serial devices (like USB serial).
        This support is enabled by <code>CONFIG_SERIAL_REMOVABLE</code>.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>ARMv7-M</b>
    </p>
    <ul>
      <li>
        Added an option to use the <code>BASEPRI</code> register to disable interrupts (instead of the <code>PRIMASK</code> register).
        This eliminates some innocuous hardfaults that interfere with some debug tools.
        You need to switch to the <code>BASEPRI</code> method only if you have such tool interference.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Drivers</b>
    </p>
    <ul>
      <li>
        Bring STM32 F1 DMA capabilities up to par with the STM32 F2/F4 (contributed by Mike Smith).
      </li>
      <li>
        Add support for USART single wire mode (Contributed by the PX4 team).
      </li>
      <li>
        Updates to support for SPI DMA on the STM32 F1/F2/F4.
        From Petteri Aimonen.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Boards</b>
    </p>
    <ul>
      <li>
        New configuration to support the UG-2864HSWEG01 OLED on the STM32F4Discovery board.
      </li>
      <li>
        Added a <code>posix_spawn()</code> test configuration for the STM32F4Discovery.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LM3S/LM4F</b>
    </p>
    <ul>
      <li>
        Files and directories repartitioned to support both LM3S and LM4F using the STM32 organization as a model.
      </li>
      <li>
        Partial definitions for the LM4F contributed by Jose Pablo Carballo (this is still a work in progress).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LM3S Boards</b>
    </p>
    <ul>
      <li>
        Added scripts and documentation to use OpenOCD with the LM3S (from Jose Pablo Carballo).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LPC176x/LPC178x</b>
    </p>
    <ul>
      <li>
        Files and directories repartitioned to support both LPC175x/LPC176x and the LPC177x/LPC178x families using the STM32 organization as a model.
        The LPC1788 port is a work in progress by Rommel Marcelo.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LPC176x/LPC178x Boards</b>
    </p>
    <ul>
      <li>
        Added a configuration to support the Wave Share Open1788 board.
        This is still a work in progress by Rommel Marcelo.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LPC2148 Boards</b>
    </p>
    <ul>
      <li>
        Add basic support for the The0.net ZP213x/4xPA board (with the LPC2148 and the UG_2864AMBAG01 OLED).
      </li>
      <li>
        Add an nxlines configuration for the ZP213x/4xPA (with the LPC2148 and the UG_2864AMBAG01).
       </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Simulator</b>
    </p>
    <ul>
      <li>
        Add an nxlines configuration for the simulator.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Networking</b>
    </p>
    <ul>
      <li>
        Add logic to work around delayed ACKs by splitting packets (contributed by Yan T.).
      </li>
      <li>
        Split <code>net_poll()</code> to create the internal interface <code>psock_poll()</code>.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LCDs</b>
    </p>
    <ul>
      <li>
        Added support for LCD1602 alphanumeric LCD (HD4468OU controller).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Graphics</b>
    </p>
    <ul>
      <li>
        Added 5x8 monospace font.
        This tiny font is useful for graph labels and for small bitmapped display.
        Contributed by Petteri Aimonen.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Build System</b>
    </p>
    <ul>
      <li>
        Add an options to better manage toolchain prefixes.
      </li>
      <li>
        Redesigned how the context targer works in the <code>apps/</code> directory.
        The old design caused lots of problems when changing configurations because there is no easy way to get the system to rebuild the context.
        This change should solve most the problems and eliminate questions like &quot;Why don't I see my builtin application in NSH?&quot;
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Kconfig Files</b>
    </p>
    <ul>
      <li>
        <p>
          There are several new configurations that use the kconfig-frontends tools and several older configurations that have been converted to use these tools.
          There is still a long way to go before the conversion is complete:
        </p>
        <ul>
          <li>
            <code>configs/sim/nxwm</code>
          </li>
          <li>
            <code>configs/sim/nsh</code>
          </li>
          <li>
            <code>configs/stm3220g-eval/nxwm</code>
          </li>
          <li>
            <code>configs/stm32f4discovery/posix_spawn</code>
          </li>
          <li>
            <code>configs/olimex-lpc1766stk/nsh</code>
          </li>
          <li>
            <code>configs/olimex-lpc1766stk/hidkbd</code>
          </li>
          <li>
            <code>configs/olimex-lpc1766stk/nettest</code>
          </li>
          <li>
            <code>configs/open1788/ostest</code>
          </li>
          <li>
            <code>configs/stm32f4discovery/nsh</code>
          </li>
          <li>
            <code>configs/stm32f4discovery/usbnsh</code>
          </li>
          <li>
            <code>configs/lm326965-ek</code> (all configurations)
          </li>
          <li>
            <code>configs/mcu123-214x/nsh</code>
          </li>
          <li>
            <code>configs/ubw32/ostest</code>
          </li>
        </ul>
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Tools</b>
    </p>
    <ul>
      <li>
        <code>tools/kconfig.bat</code>:  Kludge to run kconfig-frontends from a DOS shell.
      </li>
      <li>
        <code>tools/configure.c</code>:  <code>configure.c</code> can be used to build a work-alike program as a replacement for <code>configure.sh</code>.
        This work-alike program would be used in environments that do not support Bash scripting (such as the Windows native environment).
      </li>
      <li>
        <code>tools/configure.bat</code>: <code>configure.bat</code> is a small Windows batch file that can be used as a replacement for <code>configure.sh</code> in a Windows native environment.
        <code>configure.bat</code> is actually just a thin layer that executes <code>configure.exe</code> if it is available.
        If <code>configure.exe</code> is not available, then configure.bat will attempt to build it first (assumes the MinGW-GCC is available).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Applications</b>
    </p>
    <ul>
      <li>
        New and modified examples:
        <p>
          <ul>
            <li>
              <code>apps/examples/wlan</code>: Remove non-functional example.
            </li>
            <li>
              <code>apps/examples/ostest</code>: Added a test of <code>vfork()</code>).
              Extend signal handler test to catch death-of-child signals (<code>SIGCHLD</code>).
              Add a test for <code>waitpid()</code>, <code>waitid()</code>, and <code>wait()</code>.
            </li>
            <li>
              <code>apps/exampes/posix_spawn</code>: Added a test of <code>posix_spawn()</code>.
            </li>
          </ul>
        <p>
      </li>
      <li>
        NSH:
        <p>
          <ul>
            <li>
              NSH now supports re-direction of I/O to files (but still not from).
            </li>
            <li>
              The block driver source argument to the mount command is now optional for file systems that do not require a block driver.
            </li>
          </ul>
        </p>
      </li>
      <li>
        NSH can now execute a program from a file system using <code>posix_spawn()</code>.
      </li>
      <li>
        Added support for a login script.
        The <code>init.d/rcS</code> script will be executed once when NSH starts;
        the <code>.nshrc</code> script will be executed for each session:
        Once for a serial console, once for each USB connection, and once for each Telnet session.
      </li>
      <li>
        Supports a new daemon that can be used to monitor USB trace outpout.
      </li>
      <li>
        Removed non-functional <code>wlan</code> example.
      </li>
    </ul>
  </li>
</ul>
<p>
  <b>Bugfixes</b> (see the change log for details).
  Some of these are very important:
</p>
<ul>
  <li>
    <p>
      <b>Tasking</b>
    </p>
    <ul>
      <li>
        Fixed a *critical* task exit bug.
        Here is the failure scenario:
        (1) <code>sched_lock()</code> is called increments the lockcount on the current TCB (i.e., the one at the head of the ready to run list),
        (2) <code>sched_mergepending()</code> is called which may change the task at the head of the ready-to-run list, then
        (3) <code>sched_unlock()</code> is called which decrements the lockcount on the wrong TCB.
        The failure case that I saw was that pre-emption got disabled in the IDLE thread, locking up the whole system.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Signals</b>
    </p>
    <ul>
      <li>
        <code>sigtimedwait()</code> would return a bad signal number if the signal was already pending when the function was called.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Drivers</b>
    </p>
    <ul>
      <li>
        Some SD cards will appear busy until switched to SPI mode for first time.
        Having a pull-up resistor on MISO may avoid this problem, but this fix from Petteri Aimonen makes it work also without pull-up.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Drivers</b>
    </p>
    <ul>
      <li>
        STM32 FLASH driver counting error (from Freddie Chopin).
      </li>
      <li>
        STM32 F4 maximum SPI frequency was wrong (corrected by Petteri Aimonen).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Boards</b>
    </p>
    <ul>
      <li>
        Due to cloning of untested code, the logic to control on-board LEDs did not work on any STM32 boards.
      </li>
      <li>
        Serial devices number <code>/dev/ttyS0-5</code> is there is a serial console, but <code>/dev/ttyS1-6</code> if there is no serial console.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Binary Formats</b>
    </p>
    <ul>
      <li>
        C++ static constructors execute now using a start taskhook so that they execute in the context of the child task (instead of in the context of the parent task).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>File Systems</b>
    </p>
    <ul>
      <li>
        Several FAT-related bugs fixed by Petteri Aimonen.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Networking</b>
    </p>
    <ul>
      <li>
        Fix poll/select issure reported by Qiang: <code>poll_interrupt()</code> must call <code>net_lostconnection()</code> when a loss of connection is reported.
        Otherwise, the system will not remember that the connection has been lost and will hang waiting on a unconnected socket later.
      </li>
      <li>
        Similar issues corrected for <code>recvfrom()</code> and <code>send()</code>.
      </li>
      <li>
        Telnetd would hang in a loop if <code>recv()</code> ever returned a value &lt;= 0.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Libraries</b>
    </p>
    <ul>
      <li>
        <code>fread()</code> could hang on certain error conditions.
      </li>
      <li>
        Can't handle <code>SYSLOG</code> output to a character device from the IDLE task (because the IDLE task can't block). 
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Build System</b>
    </p>
    <ul>
      <li>
      Serial was driver was not being built if there is no console device.
      Obviously, the serial driver may be needed even in this case.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Additional Bugfixes</b>
    </p>
    <ul>
      <li>
        <code>sig_timedwait()</code> and <code>clock_time2ticks.c</code>:  Timing &quot;rounding&quot; logic
      </li>
      <li>
        ARM9 Compilation issue with low vectors.
      </li>
      <li>
        <code>readline()</code> return value
      </li>
      <li>
        As well as other, less critical bugs as detailed in the ChangeLog: HID keyboard, LPC17xx bit definitions, strndup(), PL2303, SYSLOG error handling, AT25, <code>apps/examples</code>.
      </li>
    </ul>
  </li>
</ul>
<p>
  See the <a href="#currentrelease">ChangeLog</a> for additional, detailed changes.
</p>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="platforms"><h1>Supported Platforms</h1></a>
  </td>
  </tr>
</table>

<p>
  The short story (Number of ports follow in parentheses).
  The state of the various ports vary from board-to-board.
  Follow the links for the details:
</p>
<center><table width="90%">
<ul>
  <tr>
  <td bgcolor="#e4e4e4" valign="top">
  <li><a href="#linuxusermode">Linux user mode simulation</a> (1)</li>
  <li>ARM
    <ul>
      <li><a href="#arm7tdmi">ARM7TDMI</b></a> (5)</li>
      <li><a href="#arm920t">ARM920T</a> (1) </li>
      <li><a href="#arm926ejs">ARM926EJS</a> (3) </li>
      <li><a href="#armcortexm0">ARM Cortex-M0</a> (1)</li>
      <li><a href="#armcortexm3">ARM Cortex-M3</a> (16)</li>
      <li><a href="#armcortexm4">ARM Cortex-M4</a> (6)</li>
    </ul>
  <li>Atmel AVR
    <ul>
      <li><a href="#atmelavr">Atmel 8-bit AVR</a> (3) </li>
      <li><a href="#atmelavr32">Atmel AVR32</a> (1) </li>
    </ul>
  </li>
  </td>
  <td bgcolor="#e4e4e4" valign="top">
  <li>Freescale <a href="#m68hcs12">M68HCS12</a> (2) </li>
  <li>Intel
    <ul>
      <li><a href="#8052">Intel 8052 Microcontroller</a> (1)</li>
      <li><a href="#80x86">Intel 80x86</a> (2)</li>
    </ul>
  </li>
  <li>MicroChip <a href="#pic32mips">PIC32MX</a> (MIPS) (4)</li>
  <li>Renesas/Hitachi:
    <ul>
        <li><a href="#superh">Renesas/Hitachi SuperH</a> (1/2)</li>
        <li><a href="#m16c">Renesas M16C/26</a> (1/2)</li>
    </ul>
  </li>
  </td>
  <td bgcolor="#e4e4e4" valign="top">
  <li>ZiLOG
    <ul>
        <li><a href="#zilogz16f">ZiLOG Z16F</a> (1)</li>
        <li><a href="#zilogez80acclaim">ZiLOG eZ80 Acclaim!</a> (1)</li>
        <li><a href="#zilogz8encore">ZiLOG Z8Encore!</a> (2)</li>
        <li><a href="#zilogz180">ZiLOG Z180</a> (1)</li>
        <li><a href="#zilogz80">ZiLOG Z80</a> (2)</li>
    </ul>
  </li>
</ul>
  </tr>
</table></center>

<p>The details, caveats and fine print follow:</p>

<center><table width="90%">
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="linuxusermode"><b>Linux User Mode</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      A user-mode port of NuttX to the x86 Linux/Cygwin platform is available.
      The purpose of this port is primarily to support OS feature development.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Does not support interrupts but is otherwise fully functional.
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm7tdmi"><b>ARM7TDMI</b></a>.
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI TMS320C5471</b> (also called <b>C5471</b> or <b>TMS320DA180</b> or <b>DA180</b>).
      NuttX operates on the ARM7 of this dual core processor.
      This port uses the <a href="http://www.spectrumdigital.com/">Spectrum Digital</a>
      evaluation board with a GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port is complete, verified, and included in the initial NuttX release.
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Calypso</b>.
      This port supports the TI &quot;Calypso&quot; MCU used in various cell phones (and, in particular,
      by the <a href="http://bb.osmocom.org/trac/">Osmocom-bb project</a>).
      Like the c5471, NuttX operates on the  ARM7 of this dual core processor.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC214x</b>.
      Support is provided for the NXP LPC214x family of processors.  In particular,
      support is provided for (1) the mcu123.com lpc214x evaluation board (LPC2148)
      and (1) the The0.net ZPA213X/4XPA development board (with the The0.net UG-2864AMBAG01 OLED)
      This port also used the GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port boots and passes the OS test (apps/examples/ostest).
        The port is complete and verified.  As of NuttX 0.3.17, the port includes:
        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.
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
        with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
        package.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC2378</b>.
      Support is provided for the NXP LPC2378 MCU.  In particular,
      support is provided for the Olimex-LPC2378 development board.
      This port was contributed by Rommel Marcelo is was first released in NuttX-5.3.
      This port also used the GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port boots and passes the OS test (apps/examples/ostest) and includes a
        working implementation of the NuttShell (<a href="NuttShell.html">NSH</a>).
        The port is complete and verified.
        As of NuttX 5.3, the port includes only basic timer interrupts and serial console support.
      </p>
      <p>
        <b>Development Environments:</b> (Same as for the NXP LPC214x).
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STR71x</b>.
      Support is provided for the STMicro STR71x family of processors.  In particular,
      support is provided for the Olimex STR-P711 evaluation board.
      This port also used the GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Integration is complete on the basic port (boot logic, system time, serial console).
        Two configurations have been verified: (1) The board boots and passes the OS test
        with console output visible on UART0, and the NuttShell (<a href="NuttShell.html">NSH</a>)
        is fully functional with interrupt driven serial console.  An SPI driver is available
        but only partially tested.  Additional features are needed: USB driver, MMC integration,
        to name two (the slot on the board appears to accept on MMC card dimensions; I have only
        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).
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
        with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
        package.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm920t"><b>ARM920T</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Freescale MC9328MX1</b> or <b>i.MX1</b>.
      This port uses the Freescale MX1ADS development board with a GNU arm-nuttx-elf toolchain*
      under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port has stalled due to development tool issues.
          Coding is complete on the basic port (timer, serial console, SPI).
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm926ejs"><b>ARM926EJS</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI TMS320DM320</b> (also called <b>DM320</b>).
      NuttX operates on the ARM9 of this dual core processor.
      This port uses the
      <a href="http://wiki.neurostechnology.com/index.php/Developer_Welcome">Neuros OSD</a>
      with a GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
      The port was performed using the OSD v1.0, development board.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <b>NXP <a href="http://ics.nxp.com/products/lpc3000/lpc313x.lpc314x.lpc315x/">LPC3131</a></b>.
    The port for the NXP LPC3131 on the <a href="http://www.embeddedartists.com/products/kits/lpc3131_kit.php">Embedded Artists EA3131</a> 
    development board was first released in NuttX-5.1 with a GNU arm-nuttx-elf or arm-eabi toolchain* under Linux or Cygwin
    (but was not functional until NuttX-5.2).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          The basic EA3131 port is complete and verified in NuttX-5.2 
          This basic port includes basic boot-up, serial console, and timer interrupts.
          This port was extended in NuttX 5.3 with a USB high speed driver contributed by David Hewson.
          David also contributed I2C and SPI drivers plus several important LPC313x USB bug fixes
          that appear in the NuttX 5.6 release.
          This port has been verified using the NuttX OS test, USB serial and mass storage
          tests and includes a working implementation of the NuttShell (<a href="NuttShell.html">NSH</a>).
      </p>
      <p>
          Support for <a href="NuttXDemandPaging.html">on-demand paging</a> has been developed for the EA3131.
      That support would all execute of a program in SPI FLASH by paging code sections out of SPI flash as needed.
      However, as of this writing, I have not had the opportunity to verify this new feature.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <b>NXP <a href="http://ics.nxp.com/products/lpc3000/lpc313x.lpc314x.lpc315x/">LPC315x</a></b>.
    Support for the NXP LPC315x family has been incorporated into the code base as of NuttX-6.4.
    Support has added for the Embedded Artists EA3152 board in NuttX-6.11.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          Basic support is in place for both the LPC3152 MCU and the EA3152 board.
          Verification of the port was deferred due to tool issues
          However, because of the high degree of compatibility between the LPC313x and LPC315x family, it
          is very likely that the support is in place (or at least very close).
          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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm0"><b>ARM Cortex-M0</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NuvoTon NUC120</b>.
      This is a port of NuttX to the Nuvoton NuTiny-SDK-NUC120 that features the NUC120LE3AN MCU.
    </p>
    <ul>
      <p>
        <b>STATUS</b>.
        As of this writing, this is very much a work in progress.
        For a full-featured RTOS such as NuttX, providing support in a usable and meaningful way within the tiny memories of the NUC120 will be a challenge (128KB FLASH and 16KB of SRAM).
        Initial support for the NUC120 is expected in NuttX-6.26.
      </p>
    </ul>
    <p>
      <b>Development Environments:</b>
      1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
      with Windows native toolchain, or 4) Native Windows.
      A DIY toolchain for Linux or Cygwin is provided by the NuttX
      <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
    </p>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm3"><b>ARM Cortex-M3</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Stellaris LM3S6432</b>.
      This is a port of NuttX to the Stellaris RDK-S2E Reference Design Kit and the MDL-S2E Ethernet to Serial module
      (contributed by Mike Smith).
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S6918</b>.
      This port uses the <a href=" http://www.micromint.com/">Micromint</a> Eagle-100 development
      board with a GNU arm-nuttx-elf toolchain* under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          The initial, release of this port was included in NuttX  version 0.4.6.
          The current port includes timer, serial console, Ethernet, SSI, and microSD support.
          There are working configurations the NuttX OS test, to run the <a href="NuttShell.html">NuttShell
          (NSH)</a>, the NuttX networking test, and the uIP web server.
      </p>
     </ul>
    <p>
      <b>Development Environments:</b>
      1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
      with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux
      or Cygwin is provided by the NuttX
      <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
      package.
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S6965</b>.
      This port uses the Stellaris LM3S6965 Ethernet Evalution Kit with a GNU arm-nuttx-elf toolchain*
      under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was released in NuttX 5.5.  
          Features are the same as with the Eagle-100 LM3S6918 described above.
          The apps/examples/ostest configuration has been successfully verified and an
          NSH configuration with Telnet support is available.
          MMC/SD and Networking support was not been thoroughly verified:
          Current development efforts are focused on porting the NuttX window system (NX)
          to work with the Evaluation Kits OLED display.
      </p>
      <p><small>
         <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.
      </small></p>
     </ul>
    <p>
      <b>Development Environments:</b> See the Eagle-100 LM3S6918 above.
    </p>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S8962</b>.
      This port uses the Stellaris EKC-LM3S8962 Ethernet+CAN Evalution Kit with a GNU arm-nuttx-elf toolchain*
      under either Linux or Cygwin.
      Contributed by Larry Arnold.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was released in NuttX 5.10. 
          Features are the same as with the Eagle-100 LM3S6918 described above.
      </p>
     </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S9B96</b>.
      Header file support was contributed by Tiago Maluta for this part.
      Jose Pablo Rojas V. is currently using those header file changes to port NuttX to the TI/Stellaris EKK-LM3S9B96.
      With any luck, that port should be working and available in the NuttX-6.20 release.
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Stellaris LM3S6432S2E</b>.
      This port uses Serial-to-Ethernet Reference Design Kit (<a href="http://www.ti.com/tool/rdk-s2e">RDK-S2E</a>)
      and has similar support as for the other Stellaris family members.
      Configurations are available for the OS test and for the NuttShell (NSH)
      (see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
      The NSH configuration including networking support with a Telnet NSH console.
      This port was contributed by Mike Smith.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was will be released in NuttX 6.14. 
      </p>
     </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F100x (STM32 F1 &quot;Value Line&quot;Family)</b>.
      Chip support for these STM32 &quot;Value Line&quot; family was contributed by Mike Smith and users have reported that they have successful brought up NuttX on there proprietary boards using this logic.
      This logic was extended to support the <i>high density</i> STM32F100RC chips by Freddie Chopin
      However, there is <i>no</i> specific board support for this chip families in the NuttX source tree.
      There is, however, <i>generic</i> support for STM32F100RC boards.
    </p>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F103x (STM32 F1 Family)</b>.
      Support for four MCUs and four board configurations are available.
      MCU support includes all of the high density and connectivity line families.
      Board supported is available specifically for: STM32F103ZET6, STM32F103RET6, STM32F103VCT, and STM32F103VET6.
      Boards supported include:
    </p>
    <ol>
      <li>
        A port for the <a href=" http://www.st.com/">STMicro</a> STM3210E-EVAL development board that
        features the STM32F103ZET6 MCU.
      </li>
      <li>
        The ISOTEL NetClamps VSN V1.2 ready2go sensor network platform based on the
        STMicro STM32F103RET6.  Contributed by Uros Platise.
      </li>
      <li>
        A port for the HY-Mini STM32v board.  This board is based on the
        STM32F103VCT chip.  Contributed by Laurent Latil.
      </li>
      <li>
         The M3 Wildfire development board (STM32F103VET6), version 2.
         See <a href="http://firestm32.taobao.com">http://firestm32.taobao.com</a> (the current board is version 3).
      </li>
    </ol>
    <p>
      These ports uses a GNU arm-nuttx-elf toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
      </p>
      <ul>
        <li><b>Basic Support/Drivers</b>.
          The basic STM32 port was released in NuttX version 0.4.12. The basic port includes boot-up
          logic, interrupt driven serial console, and system timer interrupts.
          The 0.4.13 release added support for SPI, serial FLASH, and USB device.;
          The 4.14 release added support for buttons and SDIO-based MMC/SD and verifed DMA support.
          Verified configurations are available for NuttX OS test, the NuttShell (NSH) example,
          the USB serial device class, and the USB mass storage device class example.
        </li>
        <li><b>NetClamps VSN</b>.
          Support for the NetClamps VSN was included in version 5.18 of NuttX.
          Uros Platise added support for timers, RTC, I2C, FLASH, extended power management
          and other features.
        </li>
        <li><b>Additional Drivers</b>.
          Additional drivers and configurations were added in NuttX 6.13 and later releases for the STM32 F1 and F4.
          F1 compatible drivers include an Ethernet driver, ADC driver, DAC driver, PWM driver, IWDG, WWDG, and CAN drivers.
        </li>
        <li><b>M3 Wildfire</b>.
          Support for the Wildfire board was included in version 6.22 of NuttX.
          The board port is basically functional.
          Not all features have been verified.
          Support for FAT file system on an an SD card had been verified.
          The ENC28J60 network is functional (but required lifting the chip select pin on the W25x16 part).
          Customizations for the v3 version of the Wildfire board are selectable (but untested).
        </li>
      </ul>
     </ul>
     <p>
       <b>Development Environments:</b>
       1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
       with Windows native toolchain (RIDE7, CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain or Linux
       or Cygwin is provided by the NuttX
       <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
       package.
     </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F107x (STM32 F1 &quot;Connectivity Line&quot; family)</b>.
      Chip support for the STM32 F1 &quot;Connectivity Line&quot; family has been present in NuttX for some time and users have reported that they have successful brought up NuttX on there proprietary boards using this logic.
    </p>
    <p>
      <b>Olimex STM32-P107</b>
      Support for the <a href="https://www.olimex.com/dev/stm32-p107.html">Olimex STM32-P107</a> was contributed by Max Holtzberg and first appeared in NuttX-6.21.  That port features the STMicro STM32F107VC MCU.
      <ul>
        <b>STATUS:</b>
        Configurations for the basic OS test and NSH are available and verified.
        Networking is functional.
      </ul>
    </p>
    <p>
      <b>Shenzhou IV</b>
      Work is underway as of this writing to port NuttX to the Shenzhou IV development board (See <a href="http://www.armjishu.com">www.armjishu.com</a>) featuring the STMicro STM32F107VCT MCU.
      If all goes according to plan, this port should be verified and available in NuttX-6.22.
      <ul>
        <b>STATUS:</b>
        In progress.
        The following have been verified:
        (1) Basic Cortex-M3 port, 
        (2) Ethernet,
        (3) On-board LEDs
      </ul>
    </p>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F207IG (STM32 F2 family)</b>.
      Support for the STMicro STM3220G-EVAL development board was contributed by Gary Teravskis and first released in NuttX-6.16.
    </p>
    <ul>
      <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.
      </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Atmel AT91SAM3U</b>.
      This port uses the <a href="http://www.atmel.com/">Atmel</a> SAM3U-EK
      development board that features the AT91SAM3U4E MCU.
      This port uses a GNU arm-nuttx-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The basic SAM3U-EK port was released in NuttX version 5.1. The basic port includes boot-up
        logic, interrupt driven serial console, and system timer interrupts.
        That release passes the NuttX OS test and is proven to have a valid OS implementation.
        A configuration to support the NuttShell is also included.
        NuttX version 5.4 adds support for the HX8347 LCD on the SAM3U-EK board.
        This LCD support includes an example using the
        <a href=" http://www.nuttx.org/Documentation/NXGraphicsSubsystem.html">NX graphics system</a>.
        NuttX version 6.10 adds SPI support.
      </p>
      <p>
        Subsequent NuttX releases will extend this port and add support for SDIO-based SD cards and
        USB device (and possible LCD support).
        These extensions may or may not happen soon as my plate is kind of full now.
      </p>
     </ul>
     <p>
       <b>Development Environments:</b>
       1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
       with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for inux
       or Cygwin is provided by the NuttX
       <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
       package.
     </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC1766, LPC1768, and LPC1769</b>.
      Drivers are available for CAN, DAC, Ethernet, GPIO, GPIO interrupts, I2C, UARTs, SPI, SSP, USB host, and USB device.
      Verified LPC17xx onfigurations are available for three boards.
      <ul>
        <li>
          The Nucleus 2G board from <a href="http://www.2g-eng.com/">2G Engineering</a> (LPC1768),
        </li>
        <li>
          The mbed board from <a href="http://mbed.org">mbed.org</a> (LPC1768, Contributed by Dave Marples), and
        </li>
        <li>
          The LPC1766-STK board from <a href="http://www.olimex.com/">Olimex</a> (LPC1766).
        </li>
        <li>
          The Embedded Artists base board with NXP LPCXpresso LPC1768.
        </li>
        <li>
          The <a href="http://micromint.com/">Micromint</a> Lincoln60 board with an NXP LPC1769.
        </li>
      </ul>
    </p>
    <p>
      The Nucleus 2G board, the mbed board, and the LPCXpresso all feature the NXP LPC1768 MCU;
      the Olimex LPC1766-STK board features an LPC1766.
      All use a GNU arm-nuttx-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The following summarizes the features that has been developed and verified on individual LPC17xx-based boards.
        These features should, however, be common and available for all LPC17xx-based boards.
      </p>
      <ol>
        <li>
        <p><b>Nucleus2G LPC1768</b></p>
        <ul>
          <li>
            Some initial files for the LPC17xx family were released in NuttX 5.6, but
          </li>
          <li>
            The first functional release for the NXP LPC1768/Nucleus2G occured with NuttX 5.7 with
            Some additional enhancements through NuttX-5.9.
          </li>
        </ul>
      </p>
      <p>
        That initial, 5.6, basic release included <i>timer</i> interrupts and a <i>serial console</i> and was
        verified using the NuttX OS test (<code>apps/examples/ostest</code>).
        Configurations available include include a verified NuttShell (NSH) configuration
        (see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
        The NSH configuration supports the Nucleus2G's microSD slot and additional configurations
        are available to exercise the the USB serial and USB mass storage devices.
        However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified.
        (Although they have since been verfiied on other platforms; this needs to be revisited on the Nucleus2G).
      </p>
      </li>
      <li>
        <p><b>mbed LPC1768</b></p>
        <ul>
          <li>
            Support for the mbed board was contributed by Dave Marples and released in NuttX-5.11.
          </li>
        </ul>
      </p>
      <p>
        This port includes a NuttX OS test configuration (see <code>apps/examples/ostest</code>).
      </p>
      </li>
      <li>
        <p><b>Olimex LPC1766-STK</b></p>
        <ul>
          <li>
            Support for that Olimex-LPC1766-STK board was added to NuttX 5.13.
          </li>
          <li>
            The NuttX-5.14 release extended that support with an <i>Ethernet driver</i>.
          </li>
          <li>
            The NuttX-5.15 release further extended the support with a functional <i>USB device driver</i> and <i>SPI-based micro-SD</i>.
          </li>
          <li>
            The NuttX-5.16 release added a functional <i>USB host controller driver</i> and <i>USB host mass storage class driver</i>.
          </li>
          <li>
            The NuttX-5.17 released added support for low-speed USB devicers, interrupt endpoints, and a <i>USB host HID keyboard class driver</i>.
          </li>
        </ul>
      </p>
      <p>
        Verified configurations are now available for the NuttX OS test,
        for the NuttShell with networking and microSD support(NSH, see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>),
        for the NuttX network test, for the <a href="http://acme.com/software/thttpd">THTTPD</a> webserver,
        for USB serial deive and USB storage devices examples, and for the USB host HID keyboard driver.
        Support for the USB host mass storage device can optionally be configured for the NSH example.
        A driver for the <i>Nokia 6100 LCD</i> and an NX graphics configuration for the Olimex LPC1766-STK have been added.
        However, neither the LCD driver nor the NX configuration have been verified as of the the NuttX-5.17 release.
      </p>
      </li>
      <li>
        <p><b>Embedded Artists base board with NXP LPCXpresso LPC1768</b></p>
        <p>
           An fully verified board configuration is included in NuttX-6.2.
           The Code Red toolchain is supported under either Linux or Windows.
           Verifed configurations include DHCPD, the NuttShell (NSH), NuttX graphis (NX), the NuttX OS test, THTTPD, and USB mass storage device.
        </p>
      </li>
      <li>
        <p><b>Micromint Lincoln60 board with an NXP LPC1769</b></p>
        <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 for more information about the <a href="http://micromint.com/Products/lincoln60.html">Lincoln60</a> board.
           More to come.
        </p>
      </li>
      </ol>
     </ul>
     <p>
       <b>Development Environments:</b>
       1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
       with Windows native toolchain (CodeSourcery devkitARM or Code Red), or 4) Native Windows.  A DIY toolchain for Linux
       or Cygwin is provided by the NuttX
       <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
     </p>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm4"><b>ARM Cortex-M4</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>FreeScale Kinetis K40</b>.
      This port uses the Freescale Kinetis KwikStik K40.
      Refer to the <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KWIKSTIK-K40">Freescale web site</a> for further information about this board.
      The Kwikstik is used with the FreeScale Tower System (mostly just to provide a simple UART connection)
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The unverified KwikStik K40 first appeared in NuttX-6.8
        As of this writing, the basic port is complete but I accidentally locked my board during the initial bringup.
        Further development is stalled unless I learn how to unlock the device (or until I get another K40).
        Additional work remaining includes, among other things: (1) complete the basic bring-up,
        (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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>FreeScale Kinetis K60</b>.
      This port uses the Freescale Kinetis TWR-K60N512 tower system.
      Refer to the <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=TWR-K60N512-KIT">Freescale web site</a> for further information about this board.
      The TWR-K60N51 includes with the FreeScale Tower System which provides (among other things) a DBP UART connection.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        As of this writing, the basic port is complete and passes the NuttX OS test.
        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 is completely untested.
        Additional work remaining includes: (1) integrate the Ethernet and SDHC drivers, and (2) develop support for USB host and device.
        NOTE: Most of these remaining tasks (excluding the Ethernet driver) are the same as the pending K40 tasks described above.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM3240G-EVAL (STM32 F4 family)</b>.
      This port uses the STMicro STM3240G-EVAL board featuring the STM32F407IGH6 MCU.
      Refer to the <a href="http://www.st.com/internet/evalboard/product/252216.jsp">STMicro web site</a> for further information about this board.
    </p>
    <p>
      <b>STATUS:</b>
      <ul>
        <li><b>NuttX-6.12</b>
          The basic port is complete and first appeared in NuttX-6.12.
          The initial port passes the NuttX OS test and includes a validated configuration for the NuttShell (NSH, see the
          <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>) as well as several other configurations.
        </li>
        <li><b>NuttX-6.13-6.16</b>
          Additional drivers and configurations were added in NuttX 6.13-6.16.
          Drivers include an Ethernet driver, ADC driver, DAC driver, PWM driver, CAN driver, F4 RTC driver, Quadrature Encoder, DMA, SDIO with DMA
          (these should all be compatible with the STM32 F2 family and many should also be compatible with the STM32 F1 family as well).
        </li>
        <li><b>NuttX-6.16</b>
          The NuttX 6.16 release also includes and logic for saving/restoring F4 FPU registers in context switches.
          Networking intensions include support for Telnet NSH sessions and new configurations for DHPCD and the networking test (nettest).
        </li>
        <li><b>NuttX-6.17</b>
          The USB OTG device controller driver, and LCD driver and a function I2C driver were added in NuttX 6.17.
        </li>
        <li><b>NuttX-6.18</b>
          STM32 IWDG and WWDG watchdog timer drivers were added in NuttX 6.18 (should be compatible with F1 and F2).
          An LCD driver and a touchscreen driver for the STM3240G-EVAL based on the STMPE811 I/O expander were also added in NuttX 6.18.
        </li>
        <li><b>NuttX-6.21</b>
          A USB OTG host controller driver was added in NuttX 6.21.
        </li>
      </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F4-Discovery (STM32 F4 family)</b>.
      This port uses the STMicro STM32F4-Discovery board featuring the STM32F407VGT6 MCU.
      Refer to the <a href="http://www.st.com/internet/evalboard/product/252419.jsp">STMicro web site</a> for further information about this board.
    </p>
    <ul>
      <p>
        <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 plaform as well.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F3-Discovery (STM32 F3 family)</b>.
      This port uses the STMicro STM32F3-Discovery board featuring the STM32F303VCT6 MCU (STM32 F3 family).
      Refer to the <a href="http://www.st.com/internet/evalboard/product/254044.jsp">STMicro web site</a> for further information about this board.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        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 plaform as well.
        New drivers will be required for ADC and I2C which are very different on this platform.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXG Technologies LPC4330-Xplorer</b>.
      This NuttX port is for the LPC4330-Xplorer board from NGX Technologies featuring the NXP LPC4330FET100 MCU.
      See the <a href="http://shop.ngxtechnologies.com/product_info.php?cPath=21_37&products_id=104">NXG website</a> for further information about this board.
    </p>
    <p>
      <b>STATUS:</b>
    </p>
    <ul>
      <li>
        <p><b>NuttX-6.20</b>
          The basic port is complete.
          The OS test configuration and the basic NSH configurations are 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:
          <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 poriting 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>
        </p>
      </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>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
  <p>
    <b>Development Environments:</b>
    1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU Cortex-M3 or 4 toolchain, 3) Cygwin/MSYS with Windows native GNU Cortex-M3 or M4 toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux or Cygwin is provided by the NuttX
    <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
    I use FreeScale's <i>CodeWarrior</i> IDE only to work with the JTAG debugger built into the Kinetis boards.
    I use the <i>Code Red</i> IDE with the some of the NXP parts and the <i>Atollic</i> toolchain with some of the STMicroelectronics parts.
  </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="atmelavr"><b>Atmel AVR</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>SoC Robotics ATMega128</b>.
      This port of NuttX to the Amber Web Server from <a href="http://www.soc-robotics.com/index.htm">SoC Robotics</a>
      is partially completed.
      The Amber Web Server is based on an Atmel ATMega128.
    </p>
    <ul>
      <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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Micropendous 3 AT90USB64x</b> and <b>AT90USB6128x</b>.
      This port of NuttX to the Opendous Micropendous 3 board. The Micropendous3 is
      may be populated with an AT90USB646, 647, 1286, or 1287.  I have only the AT90USB647
      version for testing.  This version have very limited memory resources: 64K of
      FLASH and 4K of SRAM.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PJRC Teensy++ 2.0 AT90USB1286</b>.
      This is a port of NuttX to the PJRC Teensy++ 2.0 board.
      This board was developed by <a href="http://pjrc.com/teensy/">PJRC</a>.
      The Teensy++ 2.0 is based on an Atmel AT90USB1286 MCU.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         The basic port was released in NuttX-6.5.  This basic port consists of
         a &quot;Hello, World!!&quot; example that demonstrates initialization of the OS,
         creation of a simple task, and serial console output as well as a somewhat
         simplified NuttShell (NSH) configuration (see the
         <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
      </p>
      <p>
         An SPI driver and a USB device driver exist for the AT90USB as well
         as a USB mass storage configureation.  However, this configuration is not
         fully debugged as of the NuttX-6.5 release.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><b>AVR-Specific Issues</b>.
      The basic AVR port is solid and biggest issue for using AVR is its tiny SRAM memory and its Harvard architecture.
      Because of the Harvard architecture, constant data that resides to flash is inaccessible using &quot;normal&quot; memory reads and writes (only SRAM data can be accessed &quot;normally&quot;).
      Special AVR instructions are available for accessing data in FLASH, but these have not been integrated into the normal, general purpose OS.
    </p>
    <p>
      Most NuttX test applications are console-oriented with lots of strings used for printf and debug output.
      These strings are all stored in SRAM now due to these data accessing issues and even the smallest console-oriented applications can quickly fill a 4-8K memory.
      So, in order for the AVR port to be useful, one of two things would need to be done:
    </p>
    <ol>
      <li>
        Don't use console applications that required lots of strings.
        The basic AVR port is solid and your typical deeply embedded application should work fine.
        Or,
      </li>
      <li>
        Create a special version of printf that knows how to access strings that reside in FLASH (or EEPROM).
      </li>
    </ol>
</tr>
<tr>
  <td><br></td>
  <td>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS with Windows native toolchain, or 4) Native Windows. 
        All testing, however, has been performed using the NuttX DIY toolchain for Linux  or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
        As a result, that toolchain is recommended.
      </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><br></td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="atmelavr32"><b>Atmel AVR32</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>AV32DEV1</b>.
      This port uses the www.mcuzone.com AVRDEV1 board based on the Atmel AT32UC3B0256 MCU.
      This port requires a special GNU avr32 toolchain available from atmel.com website.
      This is a windows native toolchain and so can be used only under Cygwin on Windows.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         This port is has completed all basic development, but there is more that needs to be done.
         All code is complete for the basic NuttX port including header files for all AT32UC3* peripherals.
         The untested AVR32 code was present in the 5.12 release of NuttX.
         Since then, the basic RTOS port has solidified:
      </p>
      <ul>
        <li>
          The port successfully passes the NuttX OS test (apps/examples/ostest).
        </li>
        <li>
          A NuttShell (NSH) configuration is in place (see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
          Testing of that configuration has been postponed (because it got bumped by the Olimex LPC1766-STK port).
          Current Status: I think I have a hardware problem with my serial port setup.
          There is a good chance that the NSH port is complete and functional, but I am not yet able to demonstrate that.
          At present, I get nothing coming in the serial RXD line (probably because the pins are configured wrong or I have the MAX232 connected wrong).
        </li>
      </ul>
      <p>
        The basic, port (including the verified apps/examples/ostest configuration) 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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="m68hcs12"><b>Freescale M68HCS12</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>MC9S12NE64</b>.
      Support for the MC9S12NE64 MCU and two boards are included:
    </p>
    <ul>
      <li>
        The Freescale DEMO9S12NE64 Evaluation Board, and
      </li>
      <li>
        The Future Electronics Group NE64 /PoE Badge board.
      </li>
    </ul>
    <p>
      Both use a GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
      The NuttX <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> provides a properly patched GCC 3.4.4 toolchain that is highly optimized for the m9s12x family.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         Coding is complete for the MC9S12NE64 and for the NE64 Badge board.
         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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="8052"><b>Intel 8052 Microcontroller</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PJRC 87C52 Development Board</b>.
      This port uses the <a href="http://www.pjrc.com/">PJRC</a> 87C52 development system
      and the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is complete but not stable with timer interrupts enabled.
        There seems to be some issue when the stack pointer enters into the indirect IRAM
        address space during interrupt handling.
        This architecture has not been built in some time will likely have some compilation
        problems because of SDCC compiler differences.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="80x86"><b>Intel 80x86</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>QEMU/Bifferboard i486</b>.
      This port uses the <a href="http://wiki.qemu.org/Main_Page">QEMU</a> i486 and the native
      Linux, Cywgin, MinGW the GCC toolchain under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         The basic port was code-complete in NuttX-5.19 and verifed in NuttX-6.0.
         The port was verified using the OS and NuttShell (NSH) examples under QEMU.
         The port is reported to be functional on the <a href="http://bifferos.bizhat.com">Bifferboard</a> as well.
         This is a great, stable starting point for anyone interest in fleshing out the x86 port!
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>RGMP</b>.
      RGMP stands for RTOS and GPOS on Multi-Processor.
      RGMP is a project for  running GPOS and RTOS simultaneously on multi-processor platforms
      You can port your favorite RTOS to RGMP together with an unmodified Linux to form a hybrid operating system.
      This makes your application able to use both RTOS and GPOS features.
    </p>
    <p>
      See the <a href="http://rgmp.sourceforge.net/wiki/index.php/Main_Page">RGMP Wiki</a> for further information about RGMP.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         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!
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="pic32mips"><b>MicroChip PIC32 (MIPS)</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><b>PIC32MX250F128D</b>.
      A port is in progress from the DTX1-4000L &quot;Mirtoo&quot; module from <a href="http://www.dimitech.com/" >Dimitech</a>.
      This module uses MicroChip PIC32MX250F128D and the Dimitech DTX1-4000L EV-kit1 V2.
      See the <a href="http://www.dimitech.com/">Dimitech</a> website for further information.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The basic port is code complete.
        Two configurations are available:
        (1) An OS test configuration and a (2) configuration that support the NuttShell (NSH).
        The OS test configuration is fully functional and proves that we have a basically healthy NuttX port to the Mirtoo.
        The NSH configuration includes support for a serial console and for the SST25 serial FLASH and the PGA117 amplifier/multiplexer on board the module.
        The NSH configuration is set up to use the NuttX wear-leveling FLASH file system (NXFFS).
        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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
   <p><b>PIC32MX460F512L</b>.  There one two board ports using this chip:</p>
   <ul>
    <li><b>PIC32MX Board from PCB Logic Design Co</b>.
      This port is for the PIC32MX board from PCB Logic Design Co. and used the PIC32MX460F512L.
      The board is a very simple -- little more than a carrier for the PIC32 MCU plus voltage regulation, debug interface, and an OTG connector.
    </li>
    <p>
      <b>STATUS:</b>
      The basic port is code complete and fully verified in NuttX 6.13.
      Available configurations include the OS test and the NuttShell (NSH - see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
    </p>
    <li><b>UBW32 Board from Sparkfun</b>
      This is the port to the Sparkfun UBW32 board.
      This port uses the <a href="http://www.sparkfun.com/products/8971">original v2.5</a> board which is based on the MicroChip PIC32MX460F512L.
      This older version has been replaced with this <a href="http://www.sparkfun.com/products/9713">newer board</a>.
      See also the <a href="http://www.schmalzhaus.com/UBW32/">UBW32</a> web site.
    </li>
    <p>
      <b>STATUS:</b>
      The basic port is code complete and fully verified in NuttX 6.18.
      Available configurations include the OS test and 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.
    </p>
  </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PIC32MX440F512H</b>.
        This port uses the &quot;Advanced USB Storage Demo Board,&quot; Model DB-DP11215, from <a href="http://www.sureelectronics.net">Sure Electronics</a>.
        This board features the MicroChip PIC32MX440F512H.
        See the <a href="http://www.sureelectronics.net/goods.php?id=1168">Sure website</a> for further information about the DB-DP11215 board.
        (I believe that that the DB-DP11215 may be obsoleted now but replaced with the very similar, DB-DP11212.
        The DB-DP11212 board differs, I believe, only in its serial port configuration.)
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       This NuttX port is code complete and has considerable test testing.
       The port for this board was completed in NuttX 6.11, but still required a few bug fixes before it will be ready for prime time.
       The fully verified port first appeared in NuttX 6.13.
       Available configurations include the OS test and the NuttShell (NSH - see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
       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.
       </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PIC32MX795F512L</b>.
        There one two board ports using this chip:
    </p>
    <ul>
      <li><b>Microchip PIC32 Ethernet Starter Kit</b>.
         This port uses the Microchip PIC32 Ethernet Starter Kit (DM320004) with the Expansion I/O board.
         See the <a href="http://ww.microchip.com">Microchip website</a> for further information.
      </li>
      <p>
       <b>STATUS:</b>
         This port was started and then shelved for some time until I received the Expansion I/O board.
         The basic Starter Kit (even with the Multimedia Expansion Board, MEB, DM320005)) has no serial port and most NuttX test configurations depend heavily on console output.
      </p>
      <p>
         Verified configurations for the OS test and 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.
         Stay tuned for updates.
      </p>
     <li><b>Mikroelektronika PIC32MX7 Mulitmedia Board (MMB)</b>.
        A port has been completed for the  Mikroelektronika PIC32MX7 Multimedia Board (MMB).
        See http://www.mikroe.com/ for further information about this board.
      </li>
      <p>
       <b>STATUS:</b>
         Two verified configurations are available:
         (1) The basic OS test configuration that verfies the correctness port of NuttX, and (2) an extensive <a href="NuttShell.html">NuttShell (NSH)</a> configuration.
         The NSH configuration includes:
         (1) Full network support,
         (2) Verified SPI driver,
         (3) SPI-based SD Card support,
         (4) USB device support (including configuration options for the USB mass storage device and the CDC/ACM serial class), and
         (5) Support for the MIO873QT2 LCD on the PIC32MX7 MMB.
       </p>
       </p>
         The PIC32MX7 MMB's touchscreen is connected directly to the MCU via ADC pins.
         A touchscreen driver has been developed using the PIC32's ADC capabilities and can be enabled in the NSH configuration.
         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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Development Environment:</b>
      These ports uses either:
    </p>
    <ol>
      <li>
        The <i>LITE</i> version of the PIC32MX toolchain available
        for download from the <a href="http://www.microchip.com">MicroChip</a> website, or
      </li>
      <li>
        The Pinguino MIPS ELF toolchain avaiable from the Pinquino <a href="http://code.google.com/p/pinguino32/downloads/list">website</a>.
      </li>
    </ol>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><br></td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="superh"><b>Renesas/Hitachi SuperH</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>SH-1 SH7032</b>.
      This port uses the Hitachi SH-1 Low-Cost Evaluation Board (SH1_LCEVB1), US7032EVB,
      with a GNU ELF toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is available as of release 0.3.18 of NuttX.  The port is basically complete
        and many examples run correctly.  However, there are remaining instabilities that
        make the port un-usable.  The nature of these is not understood; the behavior is
        that certain SH-1 instructions stop working as advertised.  This could be a silicon
        problem, some pipeline issue that is not handled properly by the gcc 3.4.5 toolchain
        (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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="m16c"><b>Renesas M16C/26</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Renesas M16C/26 Microncontroller</b>.
      This port uses the Renesas SKP16C26 Starter kit and the GNU M32C toolchain. 
      The development environment is either Linux or Cygwin under WinXP.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Initial source files released in nuttx-0.4.2.
        At this point, the port has not been integrated;    the target cannot be built
        because the GNU <code>m16c-nuttx-elf-ld</code> link fails with  the following message:
      </p>
      <ul>
      <code>m32c-nuttx-elf-ld: BFD (GNU Binutils) 2.19 assertion fail /home/Owner/projects/nuttx/buildroot/toolchain_build_m32c/binutils-2.19/bfd/elf32-m32c.c:482</code>
      </ul>
      <p>Where the reference line is:</p>
      <ul><pre>
/* If the symbol is out of range for a 16-bit address,
   we must have allocated a plt entry.  */
BFD_ASSERT (*plt_offset != (bfd_vma) -1);
</pre></ul>
      <p>
        No workaround is known at this time.  This is a show stopper for M16C for
        the time being.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz16f"><b>Zilog Z16F</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog z16f Microncontroller</b>.
      This port use the Zilog z16f2800100zcog development kit and the Zilog
      ZDS-II Windows command line tools.
      The development environment is either Windows native or Cygwin under Windows.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The initial release of support for the z16f was made available in NuttX version 0.3.7.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogez80acclaim"><b>Zilog eZ80 Acclaim!</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog eZ80Acclaim! Microncontroller</b>.
      There are two eZ80Acclaim! ports:
    </p>
    <ul>
      <li>One uses the ZiLOG ez80f0910200kitg development kit, and
      <li>The other uses the ZiLOG ez80f0910200zcog-d development kit.
    </ul>
    <p>
      Both boards are based on the eZ80F091 part and both use the Zilog ZDS-II
      Windows command line tools.
      The development environment is either Windows native or Cygwin under Windows.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Integration and testing of NuttX on the  ZiLOG ez80f0910200zcog-d is complete.
        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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz8encore"><b>Zilog Z8Encore!</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog Z8Encore! Microncontroller</b>.
      This port uses the either:
    </p>
    <ul>
      <li>Zilog z8encore000zco development kit, Z8F6403 part, or</li>
      <li>Zilog z8f64200100kit development kit, Z8F6423 part</li>
    </ul>
    <p>
      and the Zilog ZDS-II Windows command line tools.
      The development environment is either Windows native or Cygwin under Windows.
    </p>
    <ul>
       <p>
         <b>STATUS:</b>
         This release has been verified only on the ZiLOG ZDS-II Z8Encore! chip simulation
         as of nuttx-0.3.9.
       </p>
     <ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz180"><b>Zilog Z180</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>P112</b>.
      The P112 is a hobbyist single board computer based on a 16MHz Z80182 with up to 1MB of memory, serial,
parallel and diskette IO, and realtime clock, in a 3.5-inch drive form factor..
      The P112 computer originated as a commercial product of &quot;D-X Designs Pty Ltd&quot[ of Australia.
    </p>
    </p>
      Dave Brooks was successfully funded through Kickstarter for and another run of P112 boards in November of 2012.
      In addition Terry Gulczynski makes additional P112 derivative hobbyist home brew computers.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       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 first quarter of 2013.
       So it will be some time before this port is verified on hardware.
      </p>
    <ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz80"><b>Zilog Z80</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Z80 Instruction Set Simulator</b>.
      This port uses the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain
      under Linux or Cygwin (verified using version 2.6.0).
      This port has been verified using only a Z80 instruction simulator.
      That simulator can be found in the NuttX SVN
      <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/sims/z80sim/">here</a>.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is complete and stable to the extent that it can be tested
        using an instruction set simulator.
      </p>
    <ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>XTRS: TRS-80 Model I/III/4/4P Emulator for Unix</b>.
      A very similar Z80 port is available for <a href="http://www.tim-mann.org/xtrs.html">XTRS</a>,
      the TRS-80 Model I/III/4/4P Emulator for Unix.
      That port also uses the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain
      under Linux or Cygwin (verified using version 2.6.0).
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       Basically the same as for the Z80 instruction set simulator.
       This port was contributed by Jacques Pelletier.
      </p>
    <ul>
  </td>
</tr>
</table></center>

<blockquote>* A highly modified <a href="http://buildroot.uclibc.org/">buildroot</a>
is available that may be used to build a NuttX-compatible ELF toolchain under
Linux or Cygwin.  Configurations are available in that buildroot to support ARM, Cortex-M3,
avr, m68k, m68hc11, m68hc12, m9s12, blackfin, m32c, h8, and SuperH ports.</blockquote>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="environments"><h1>Development Environments</h1></a>
  </td>
  </tr>
</table>

<center><table width="90%">
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Linux + GNU <code>make</code> + GCC/binutils for Linux</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      The is the most natural development environment for NuttX.
      Any version of the GCC/binutils toolchain may be used.
      There is a  highly modified <a href="http://buildroot.uclibc.org/">buildroot</a>
      available for download from the
      <a href="http://sourceforge.net/projects/nuttx/files/">NuttX SourceForge</a>
      page.
      This download may be used to build a NuttX-compatible ELF toolchain under Linux or Cygwin.
      That toolchain will support ARM, m68k, m68hc11, m68hc12, and SuperH ports.
      The buildroot SVN may be accessed in the 
      <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/buildroot/">NuttX SVN</a>.
    </p>
   </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Linux + GNU <code>make</code> + SDCC for Linux</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Also very usable is the Linux environment using the 
      <a href="http://sdcc.sourceforge.net/">SDCC</a> compiler.
      The SDCC compiler provides support for the 8051/2, z80, hc08, and other microcontrollers.
      The SDCC-based logic is less well exercised and you will likely find some compilation
      issues if you use parts of NuttX with SDCC that have not been well-tested.
    </p>
   </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows with Cygwin + GNU <code>make</code> + GCC/binutils (custom built under Cygwin)</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      This combination works well too.
      It works just as well as the native Linux environment except that compilation and build times are a little longer.
      The custom NuttX <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> referenced above may be build in the Cygwin environment as well.
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows with Cygwin + GNU <code>make</code> + SDCC (custom built under Cygwin)</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
       I have never tried this combination, but it would probably work just fine.
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows with Cygwin + GNU <code>make</code> + Windows Native Toolchain</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      This is a tougher environment.
      In this case, the Windows native toolchain is unaware of the
      Cygwin <i>sandbox</i> and, instead, operates in the native Windows environment.
      The primary difficulties with this are:
    </p>
    <ul>
      <li>
        <b>Paths</b>.
        Full paths for the native toolchain must follow Windows standards.
        For example, the path <code>/home/my\ name/nuttx/include</code> my have to be
        converted to something like <code>'C:\cygwin\home\my name\nuttx\include'</code>
        to be usable by the toolchain.
      </li>
      <p>
        Fortunately, this conversion is done simply using the <code>cygpath</code> utility.
      </p>
      <li>
        <b>Symbolic Links</b>
        NuttX depends on symbolic links to install platform-specific directories in the build system.
        On Linux, true symbolic links are used.
        On Cygwin, emulated symbolic links are used.
        Unfortunately, for native Windows applications that operate outside of the
        Cygwin <i>sandbox</i>, these symbolic links cannot be used.
      </li>
      <p>
        The NuttX make system works around this limitation by copying the platform
        specific directories in place.
        These copied directories make work a little more complex, but otherwise work well.
      </p>
      <p><small>
        NOTE: In this environment, it should be possible to use the NTFS <code>mklink</code> command to create links.
        This should only require a minor modification to the build scripts (see <code>tools/copydir.sh</code> script).
      </small></p>
      <li>
        <b>Dependencies</b>
        NuttX uses the GCC compiler's <code>-M</code> option to generate make dependencies.  These
        dependencies are retained in files called <code>Make.deps</code> throughout the system.
        For compilers other than GCC, there is no support for making dependencies in this way.
        For Windows native GCC compilers, the generated dependencies are windows paths and not
        directly usable in the Cygwin make.  By default, dependencies are surpressed for these
        compilers as well.
      </li>
      <p><small>
        NOTE: dependencies are suppress by setting the make variable <code>MKDEPS</code> to point
        to the do-nothing dependency script, <code>tools/mknulldeps.sh</code>.
      </small></p>
    </ul>
    <p>
      <b>Supported Windows Native Toolchains</b>.
      At present, the following Windows native toolchains are in use:
      <ol>
        <li>GCC built for Windows (such as CodeSourcery, Atollic, devkitARM, etc.),</li>
        <li>SDCC built for Windows,</li>
        <li> the ZiLOG XDS-II toolchain for Z16F, z8Encore, and eZ80Acclaim parts.</li>
      </ol>
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows Native (<code>CMD.exe</code>) + GNUWin32 (including GNU <code>make</code>) + MinGW Host GCC compiler + Windows Native Toolchain</b>
  </td>
</tr>
  <td><br></td>
  <td>
    <p>
      Build support has been added to support building natively in a Windows console rather than in a POSIX-like environment.
    </p>
    <p>
      This build:
    </p>
    <ol>
      <li>Uses all Windows style paths</li>
      <li>Uses primarily Windows batch commands from cmd.exe, with</li>
      <li>A few extensions from GNUWin32</li>
    </ol>
    <p>
      This capability first appeared in NuttX-6.24 and should still be considered a work in progress because: (1) it has not been verfied on all targets and tools, and (2) still lacks some of the creature-comforts of the more mature environments.
      The windows native build logic initiatiated if <code>CONFIG_WINDOWS_NATIVE=y</code> is defined in the NuttX configuration file:
    </p>
    <p>
      At present, this build environment also requires:
    </p>
    <ul>
      <li>
        <b>Windows Console</b>.
        The build must be performed in a Windows console window.
        This may be using the standard <code>CMD.exe</code> terminal that comes with Windows.
        I prefer the ConEmu terminal which can be downloaded from:
        http://code.google.com/p/conemu-maximus5/
      </li>
      <li>
        <b>GNUWin32</b>.
        The build still relies on some Unix-like commands.
        I usethe GNUWin32 tools that can be downloaded from http://gnuwin32.sourceforge.net/.
        See the top-level <code>nuttx/README.txt</code> file for some download, build, and installation notes.
      </li>
      <li>
        <b>MinGW-GCC</b>.
        MinGW-GCC is used to compiler the C tools in the <code>nuttx/tools</code> directory that are neede by the build.
        MinGW-GCC can be downloaded from http://www.mingw.org/.
        If you are using GNUWin32, then it is recommendedthe you not install the optional MSYS components as there may be conflicts.
      </li>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Wine + GNU <code>make</code> + Windows Native Toolchain</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      I've never tried this one, but I off the following reported by an ez80 user using the ZiLOG ZDS-II Windows-native toolchain:
    </p>
    <blockquote>
      <p>
         &quot;I've installed ZDS-II 5.1.1 (IDE for ez80-based boards) on wine (windows emulator for UNIX) and to my surprise, not many changes were needed to make SVN snapshot of NuttX buildable...
         I've tried nsh profile and build process completed successfully.
         One remark is necessary: NuttX makefiles for ez80 are referencing <code>cygpath</code> utility.
         Wine provides similar thing called <code>winepath</code> which is compatible and offers compatible syntax.
         To use that, <code>winepath</code> (which itself is a shell script) has to be copied as <code>cygpath</code> somewhere in <code>$PATH</code>, and edited as in following patch:
       </p>
       <ul><pre>
# diff -u `which winepath` `which cygpath`
--- /usr/bin/winepath 2011-05-02 16:00:40.000000000 +0200
+++ /usr/bin/cygpath 2011-06-22 20:57:27.199351255 +0200
@@ -20,7 +20,7 @@
#

# determine the app Winelib library name
-appname=`basename "$0" .exe`.exe
+appname=winepath.exe

# first try explicit WINELOADER
if [ -x "$WINELOADER" ]; then exec "$WINELOADER" "$appname" "$@"; fi
</pre></ul>
      <p>
        &quot;Better solution would be replacing all <code>cygpath</code> references in  <code>Makefiles </code> with  <code>$(CONVPATH)</code> (or  <code>${CONVPATH}</code> in shell scripts) and setting <code>CONVPATH</code> to  <code>cygpath</code> or  <code>winepath</code> regarding to currently used environment.
      </p>
    </blockquote>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Other Environments?</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Environment Dependencies</b>.
      The primary environmental dependency of NuttX are (1) GNU make,
      (2) bash scripting, and (3) Linux utilities (such as cat, sed, etc.).
      If you have other platforms that support GNU make or make
      utilities that are compatible with GNU make, then it is very
      likely that NuttX would work in that environment as well (with some
      porting effort). If GNU make is not supported, then some significant
      modification of the Make system would be required.
    </p>
    <p>
      <b>MSYS</b>.
      I have not used MSYS but what I gather from talking with NuttX users is that MSYS can be used as an alternative to Cygwin in any of the above Cygwin environments.
      This is not surprising since MSYS is based on an older version of Cygwin (cygwin-1.3).
      MSYS has been modified, however, to interoperate in the Windows environment better than Cygwin and that may be of value to some users.
    </p>
    <p>
      MSYS, however, cannot be used with the native Windows NuttX build because it will invoke the MSYS bash shell instead of the <code>CMD.exe</code> shell.
      Use GNUWin32 in the native Windows build envionment.
    </p>
  </td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="footprint"><h1>Memory Footprint</h1></a>
  </td>
  </tr>
</table>

<ul>
<p><b>C5471 (ARM7)</b>
  The build for this ARM7 target that includes most of the OS features and
  a broad range of OS tests.  The size of this executable as given by the
  Linux <tt>size</tt> command is (3/9/07):
</p>
<pre>
   text    data     bss     dec     hex filename
  53272     428    3568   57268    dfb4 nuttx
</pre>
<p><b>DM320 (ARM9)</b>
  This build for the ARM9 target includes a significant subset of OS
  features, a filesystem, Ethernet driver, full TCP/IP, UDP and (minimal)
  ICMP stacks (via uIP) and a small network test application: (11/8/07,
  configuration netconfig, apps/examples/nettest)
</p>
<pre>
   text    data     bss     dec     hex filename
  49472     296    3972   53740    d1ec nuttx
</pre>
<p>
  Another build for the ARM9 target includes a minimal OS feature
  set, Ethernet driver, full TCP/IP and (minimal) ICMP stacks, and
  a small webserver: (11/20/07, configuration uipconfig, apps/examples/uip)
</p>
<pre>
   text    data     bss     dec     hex filename
  52040      72    4148   56260    dbc4 nuttx
</pre>
<p><b>87C52</b>
  A reduced functionality OS test for the 8052 target requires only
  about 18-19K:
</p>
<pre>
Stack starts at: 0x21 (sp set to 0x20) with 223 bytes available.

Other memory:
   Name             Start    End      Size     Max
   ---------------- -------- -------- -------- --------
   PAGED EXT. RAM                         0      256
   EXTERNAL RAM     0x0100   0x02fd     510     7936
   ROM/EPROM/FLASH  0x2100   0x6e55   19798    24384
</pre>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="licensing"><h1>Licensing</h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
  NuttX is available under the highly permissive
  <a href="http://en.wikipedia.org/wiki/BSD_license">BSD license</a>.
  Other than some fine print that you agree to respect the copyright
  you should feel absolutely free to use NuttX in any environment and
  without any concern for jeopardizing any proprietary software that
  you may link with it.
</p>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="history"><h1>Release History</h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
   ChangeLog snapshots associated with the previous, current, and future release are available below.
</p>
</ul>

<center><table width ="80%">
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="ChangeLog.txt">Change logs for previous NuttX releases</a><br>
   </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="#currentrelease">ChangeLog for the current NuttX releases</a><br>
   </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="#pendingchanges">Unreleased changes</a>
   </td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="currentrelease">ChangeLog for the Current Release</a>
  </td>
  </tr>
</table>

<ul><pre>
nuttx-6.25 2013-02-01 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * graphics/: Adds 5x8 monospace font. This tiny font is useful for graph
      labels and for small bitmapped display.  Contributed by Petteri
      Aimonen.
    * configs/stm3220g-eval/nxwm:  Converted to use the kconfig-frontends
      configuration tool.
    * configs/sim/nxwm:  Converted to use the kconfig-frontends configuration
      tool.
    * include/pthread.h:  In sys/prctl.h because it is needed by
      pthread_[set|get]name_np()
    * tools/kconfig.bat:  Kludge to run kconfig-frontends from a DOS shell.
    * sched/sig_timedwait.c:  Should always move the time up to the next
      largest number of system ticks.  The logic was rounding.  Noted by
      Petteri Aimonen.
    * arch/arm/src/up_head.S:  Fix backward conditional compilation.  NOTE
      there is a issue of ARM9 systems with low vectors and large memories
      that will have to be addressed in the future.
    * libc/misc/lib_kbdencode.c and lib_kbddecode.c:  Add logic to marshal
      and serialized &quot;out-of-band&quot; keyboard commands intermixed with normal
      ASCII data (not yet hooked into anything).
    * drivers/usbhost/usbhost_hidkbd.c:  If CONFIG_HIDKBD_ENCODED is
      defined, this driver will now use libc/misc/lib_kbdencode.c to
      encode special function keys.
    * configs/olimex-lpc1766stk/hidkbd:  This configuration has been
      converted to use the kconfig-frontends configuration tool.
    * drivers/lcd/ug-2864hsweg01.c and include/nuttx/lcd/ug-2864hsweg01.h:
      Driver for UG-2864HSWEG01 OLED contributed by Darcy Gong.
    * configs/stm32f4discovery/src/up_ug2864hsweg01.c: Support for the
      UG-2864HSWEG01 OLED for the STM32F4Discovery board.
    * drivers/usbhost/usbhost_hidkbd.c:  Correct a logic error in how
      tasks waiting for read data are awakened.
    * libc/misc/lib_kbdencode.c and lib_kbddecode.c:  Now handles keypress
      events too.  However, the USB HID keyboard driver has not yet been
      updated to detect key release events.  That is kind of tricky in
      the USB HID keyboard report data.
    * configs/mcu123-214x/nsh:  Converted to use the kconfig-frontends
      configuration tool.
    * configs/zp214xpa:  Add basic support for the The0.net ZP213x/4xPA
      board (with the LPC2148 and the UG_2864AMBAG01).
    * configs/sim/nxlines:  Add an nxlines configuration for the
      simulator.
    * configs/zp214xpa/nxlines:  Add an nxlines configuration for the
      ZP213x/4xPA (with the LPC2148 and the UG_2864AMBAG01).  Working
      as of 2012-12-30.
    * configs/olimex-lpc1766stk/wlan:  Remove non-functional
      configuration.
    * configs/stm32f4discovery/src and nuttx/drivers/lcd/ug-2864hsweg01.c:
      Updates and correctinos for the UG-2864HSWEG01 from Darcy Gong.
    * configs/lm326965-ek:  All configurations converted to use the
      kconfig-frontends configuration tool.
    * configs/Kconfig: NSH_MMCSDSPIPORTNO should depend on MMCSD_SPI,
      not just SPI (from Jose Pablo Carballo).
    * arch/arm/src/arm/Kconfig and armv7m/Kconfig:  Add an option for
      buildroot toolchains:  They may be EABI or OABI.
    * include/nuttx/progmem and arch/arm/src/stm32/stm32_flash.c:
      Fix a counting bug plus change interface to use either relative
      or absolute FLASH addressing (from Freddie Chopin).
    * libc/misc/Make.defs:  Fix error in conditional for KBD CODEC.
    * libc/Kconfig and configs/*/defconfig (several):  The default
      setting should be CONFIG_LIB_KBDCODEC=n
    * tools/configure.c:  configure.c can be used to build a work-alike
      program as a replacement for configure.sh.  This work-alike
      program would be used in environments that do not support Bash
      scripting (such as the Windows native environment).
    * tools/configure.bat: configure.bat is a small Windows batch
      file that can be used as a replacement for configure.sh in a
      Windows native environment.  configure.bat is actually just a
      thin layer that executes configure.exe if it is available. If
      configure.exe is not available, then configure.bat will attempt
      to build it first.
    * arch/arm/src/lpc17xx/lpc17_syscon.h:  Correct some typos in bit
      definitions (from Rommel Marcelo).
    * libc/string/lib_strndup.c: strndup() should use strnlen(), not
      strlen(), to determine the size of the string.
    * sched/os_bringup.c:  Remove support for CONFIG_BUILTIN_APP_START.
      This is not really a useful feature and creates a violation of the
      OS layered architecture.
    * include/unistd.h, arch/arch/src/*:  Implement a simple vfork().
      On initial checkin, this API is available only for ARM platforms.
    * binfmt/binfmt_exec.c: exec() now sets the priority of the new task
      to the same priority as the current task (instead of the arbirtrary
      value of 50).
    * libc/unisted/lib_execv.c and lib_execl.c:  New, somewhat flawed,
      implementations of execv() and execl().
    * tools/cfgdefine.c:  Strips quotes from CONFIG_EXECFUNCS_SYMTAB
      value.
    * arch/arm/include/lm3s/chip.h:  Move chip definitions into
      public include area for compatibility with other architectures.
    * arch/arm/src/lm3s/chip:  Move register definition header files
      into a new chip/ sub-directory.
    * arch/arm/src/lm3s/lm3s_internal.h:  Broke up into several
      smaller header files.
    * arch/arm/src/lm:  Rename the arch/arm/src/lm3s directory to
      arch/arm/src/lm so that is can support other members of the
      Stellaris family.
    * libc/spawn:  Add file action interfaces needed by posix_spawn().
    * sched/clock_time2ticks.c:  Another case where time was being
      rounded down instead of up (from Mike Smith).
    * libc/spawn:  Implementation of posix_spawn() is complete but
      untested and undocumented.
    * drivers/usbdev/pl2303.c:  Fix typols in the PL2303 driver
      (from Max Holtzberg).
    * configs/stm32f4discovery/posix_spawn:  Added a configuration
      that can be used for testing posix_spawn().
    * arch/arm/src/stm32: Bring F1 support for general DMA and serial
      DMA in paricular up to parity with F2/F4 (from Mike Smith).
    * libc/stdio/lib_libfread.c:  Correct some error handling when
      lib_fread() was passed a bad stream.  Needed to move the
      releasing of a semaphore inside of some conditional logic
      (cosmetic).
    * include/nuttx/sched.h, sched/task_setup.c, and sched/task_exithook.c:
      Add support for remembering the parent task and sending
      SIGCHLD to the parent when the task exists.
    * sched/task_exithook.c:  Fixed a *critical* bug.  Here is
      the scenario: (1) sched_lock() is called increments the lockcount
      on the current TCB (i.e., the one at the head of the ready to run
      list), (2) sched_mergepending is called which may change the task
      at the head of the ready-to-run list, then (3) sched_unlock() is called
      which decrements the lockcount on the wrong TCB.  The failure case
      that I saw was that pre-emption got disabled in the IDLE thread,
      locking up the whole system.
    * sched/sched_waitpid.c:  Use SIGCHLD instead of a semaphore.  This
      is a much more spec-compliant implementation.  However, there are
      some issues with overruning signals because NuttX does not support
      queueing of signals (POSIX does not require it).  I think it may
      need to.
    * sched/sched_waitid.c and sched_wait.c:  Add support for waitid()
      and wait().  See issues with waitpid() above.
    * include/nuttx/fs/fs.h and fs/fs_files.c:  Add a dup() method to
      the struct mountpt_operations.  When dup'ing a file that resides
      on a mounted volume, let the file system's dup() method do the
      work.
    * fs/romfs/fs_romfs.c: Implemented the dup() method for the ROMFS
      file system.
    * fs/fat/fs_fat32.c, fs/nxffs/nxffs_initialize, and
      fs/nfs/nfs_vfsops.c:  Add hooks for dup() method (not yet
      implemented).
    * fs/romfs:  Remove the rf_open flag.  It looks good, but actually
      does nothing.
    * fs/fat:  Remove the ff_open flag.  Same story as for the ROMFS
      rf_open flag.
    * fs/fat/fs_fat32.c, fs/nxffs/nxffs_initialize, and
      fs/nfs/nfs_vfsops.c:  Completed implementation of the dup() methods.
      There is still no good test available.
    * sched/sig_timedwait.c:  sigtimedwait() would return a bad signal
      number if the signal was already pending when the function was
      called.
    * configs/ubw32/scripts:  All common linker scripts moved to this
      scripts sub-directory
    * configs/ubw32/ostest:  Configuration configured to use the
      kconfig-frontends tools.
    * arch/mips/src/mips32/up_vfork.c, up_vfork.h, and vfork.S:
      Implement vfork() for MIPS32 (no floating point support)
    * configs/ubw32/ostest: Enable the vfork() test.
    * fs/binfs:  Move apps/builtin/binfs.c to fs/binfs/fs_binfs.c
      CONFIG_APPS_BINDIR rename CONFIG_FS_BINFS
    * include/nuttx/binfmt/builtin.h:  Some of the content of
      apps/include/apps.h moved to include/nuttx/binfmt/builtin.h
    * binfmt/libbuiltin/libbuiltin_utils.c:  Move builtin
      utility functions from apps/builtin/exec_builtins.c to
      binfmt/libbuiltin/libbuiltin_utils.c
    * binfmt/builtin.c and binfmt/libbuiltin:  Add a binary &quot;loader&quot;
      that can be used to execute builtin programs from the BINFS
      file system.
    * configs/sim/nsh: Convert to use kconfig-frontends configuration
      tool.
    * binfmt/binfmt_schedunload.c:  Add logic based on SIGCHLD to
      automatically unload and clean-up after running a task that
      was loaded into memory.
    * binfmt/libbuiltin: Extensions from Mike Smith
    * sched/task_reparent.c:  Add internal interface to change the
      parent task.
    * sched/task_posixspawn():  Move libc/spawn/lib_ps.c to
      sched/task_posixspawn() now it requires internal, reparenting
      interfaces
    * include/nuttx/spawn():  Move libc/spawn.h to include/nuttx/spawn.h
    * arch/arm/include/lpc17xx/chip.h, irq178x.h:  Integrate Marcelo
      Rommel's LPC1788 definitions into the base LPC17xx.
    * configs/olimex-lpc1766stk/nsh:  Convert configuration to use
      the kconfig-frontends tools.
    * sched/task_reparent.c:  Simplify reparenting interface.
    * arch/arm/src/[many]: More LPC1788 definitions from Rommel
      Marcelo incorporated.
    * configs/open1788:  Board configuration for the Wave Share
      Open1788 board.  Still fragmentary (contributed by Rommel
      Marcelo, adapted to use kconfig-frontends.
    * net/send():  Add logic to work around delayed ACKs by splitting
      packets (contributed by Yan T.).
    * net/recvfrom():  Fix a bug.  When the host closes a connection
      (gracefully).  recv[from]() returned success and the closure
      was never detected.  Hmmm.. I don't know why the network monitor
      did not catch this event.  This is an important bug fix.
    * net/recvfrom():  Fix a introduced with the last bugfix.  If
      the peer does an orderly closure of the socket, report 0 not
      -ENOTCONN
    * configs/lm3s6965-ek/README.txt and tools/:  Add an OpenOCD
      configuration for the LM3S (from Jose Pablo Carballo).
    * nuttx/lcd/hd4478ou.h and configs/pcblogic-pic32mx/src/up_lcd1602:
      Start of support of LCD1602 alphanumeric LCD.  I need a few
      more parts before I can finish integrating this one.
    * arch/arm/src/*/chip.h and arch/arm/include/*/chip.h:  Move all
      priority ranges from the src to the include chip.h header file.
    * arch/arm/include/armv7-m/irq.h:  Add inline functions to enable
      and disable interrupts via the BASEPRI register.
    * arch/arm/Kconfig:  Add new option CONFIG_ARM7VM_USEBASEI
    * arch/arm/src/*/*_irq.c:  Set the priority of the SVCALL exception
      to the highest possible value.
    * arch/armv7-m/up_hardfault.c:  Fail if a hardfault occurs
      while CONFIG_ARM7VM_USEBASEPRI=y.
    * arch/arm/src/stm32/stm32_serial.c:  Add support for USART
      single wire mode (Contributed by the PX4 team).
    * sched/: Implement support for retaining child task status after
      the child task exists.  This is behavior required by POSIX.
      But in NuttX is only enabled with CONFIG_SCHED_HAVE_PARENT and
      CONFIG_SCHED_CHILD_STATUS
    * Add support for keyboard encode to the keypad test (from
      Denis Carikli).
    * configs/olimex-lpc1766stk/nettest:  Configuration converted to
      use the kconfig-frontends tools.
    * net/net_poll.c:  Split net_poll() to create psock_poll() too.
    * net/net_poll.c:  Fix poll/select issure reported by Qiang:
      poll_interrupt() must call net_lostconnection() when a
      loss of connection is reported.  Otherwise, the system will
      not know that the connection has been lost.
    * sched/group_create.c, group_join.c, and group_leave.c:  Add
      support for task groups.
    * sched/group_signal.c and task_exithook.c:  Send signal to all
      members for the parent task group.
    * include/nuttx/sched.h and sched/env_*.c:  Move environment
      variables into task group structure.
    * sched/: Lots of file changed.  Don't keep the parent task's
      task ID in the child task's TCB.  Instead, keep the parent
      task group IN the child task's task group.
    * fs/, sched/, include/nuttx/sched.h, and include/nutts/fs/fs.h:
      Move file data from the TCB to the task group structure.
    * libc/stdio/, sched/, include/nuttx/lib.h, and include/nutts/fs/fs.h:
      Move stream data from the TCB to the task group structure.
    * net/, sched/, and include/nuttx/net/net.h:  Move socket data
      from the TCB to the task group structure.
    * sched/task_starthook.c, sched/task_start.c, and include/nuttx/sched.h:
      Add a task start hook that will be called before the task main
      is started. This can be used to schedule C++ constructors to run
      automatically in the context of the new task.
    * binfmt/binfmt_execmodule: Execute constructors as a start hook.
    * sched/os_start.c: Fix ordering of group initialization.
    * configs/stm32f4discovery/usbnsh:  Add an NSH STM32F4Discovery
      configuration that uses USB CDC/ACM for the NSH console.
    * configs/stm32f4discovery/nsh: Converted to use the kconfig-frontends
      tools.
    * configs/*/src/up_userleds.c: Fix a error that was cloned into
      all STM32 user LED code.  The wrong definitions were being used
      to set LEDs on or off.
    * arch/*/common/up_internal.h and arch/*/common/up_initialize.c:
      Serial was driver was not being built if there is no console
      device.  Obviously, the serial driver may be needed even in
      this case.
    * arch/arm/src/stm32/stm32_serial.c: If there is a serial console,
      it would be ttyS0 and the others would be ttyS1-5.  If there
      is not serial console, was labeling them ttyS1-6; now labels them
      ttyS0-5.
    * fs/fs_syslog.c: Can't handle SYSLOG output to character device from
      the IDLE task (because it can't block). syslog_putc now returns EOF
      on failure and sets errno.  Fixed some errors in error handling.
    * libc/stdio/lib_syslogstream.c:  Checking of return value from
      syslog_putc was bogus.  Switching to EOF for all errors solves
      this.
    * arch/arm/src/lm/chip/lm4f_memorymap.h: More LM4F changes from
      Jose Pablo Carballo.
    * drivers/serial/serial.c, include/nuttx/serial/serial.h,
      drivers/usbdev/cdcacm.c, and drivers/pl2303.c: Add support for
      removable serial devices (like USB serial).  This support is enabled
      by CONFIG_SERIAL_REMOVABLE.
    * arch/*/src/*/Toolchain.defs: Change assignment so that we can
      override CROSSDEV with a make command line argument.
    * include/assert.h:  Mark assertion functions as non-returning.
    * arch/*/src/*/up_assert.h:  Mark _up_assert() as non-returning.
    * drivers/mtd/at25.c: When the AT25 device was not available the
      initialization did not fail like it should. From Petteri Aimonen.
    * fs/fat/fs_configfat.c:  Fix some errors in FAT formatting logic
      for large devices and for FAT32. From Petteri Aimonen.
    * fs/fat/fs_fat32util.c:  Fix an initialization error found by
      Petteri Aimonen.  freecount and next freecount initialization were
      reversed.
    * drivers/mmcsd/mmcsd_spi.c: Some SD cards will appear busy until
      switched to SPI mode for first time.  Having a pull-up resistor on
      MISO may avoid this problem, but this patch makes it work also
      without pull-up.  From Petteri Aimonen.
    * fs/fat/fs_fat32.c: Fix a compilation error when FAT_DMAMEMORY=y. 
      From Petteri Aimonen.
    * arch/arm/src/stm32/chip/stm32_spi.h: STM32F4 max SPI clock freq is
      37.5 MHz.  Patch from Petteri Aimonen.
    * arch/arm/src/stm32/stm32_spi.c: Fixes for SPI DMA work on the
      STM32F4. Includes untested additions for the F1 implementation as
      well.  From Petteri Aimonen.

apps-6.25 2013-02-01 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * Makefiles: Removed dependency of distclean on clean in most top-level
      files.  It makes sense for 'leaf' Makefiles to have this dependency,
      but it does not make sense for upper-level Makefiles.
    * apps/namedapp/: Renamed to builtins in preparation for another change.
    * .context:  Removed the .context kludge.  This caused lots of problems
      when changing configurations because there is no easy way to get the
      system to rebuild the context.  Now, the context will be rebuilt
      whenever there is a change in either .config or the Makefile.
    * apps/builtin/registry:  Updated new built-in registration logic to handle
      cases where (1) old apps/.config is used, and (2) applications ared
      removed, not just added.
    * apps/examples/nettest/Makefile:  Fix an error that crept in during
      some of the recent, massive build system changes.
    * apps/builtin/Makefile:  Need to have auto-generated header files
      in place early in the dependency generation phase to avoid warnings.
      It is not important if they are only stubbed out header files at
      this build phase.
    * apps/examples/hidbkd: Now supports decoding of encoded special keys
      if CONFIG_EXAMPLES_HIDKBD_ENCODED is defined.
    * apps/examples/hidbkd:  Add support for decoding key release events
      as well.  However, the USB HID keyboard drier has not yet been
      updated to detect key release events.  That is kind of tricky in
      the USB HID keyboard report data.
    * apps/examples/wlan: Remove non-functional example.
    * apps/examples/ostest/vfork.c:  Added a test of vfork().
    * apps/exampes/posix_spawn: Added a test of posix_spawn().
    * apps/examples/ostest:  Extend signal handler test to catch
      death-of-child signals (SIGCHLD).
    * apps/examples/ostest/waitpid.c:  Add a test for waitpid(), waitid(),
      and wait().
    * builtin/binfs.c:  Add hooks for dup() method (not implemented).
    * builtin/exec_builtin.c, nshlib/nsh_parse.c, and nshlib/nsh_builtin.c:
      NSH now supports re-direction of I/O to files (but still not from).
    * builtin/binfs.c:  Greatly simplified (it is going to need to be
      very lightweight).  Now supports open, close, and a new ioctl to recover
      the builtin filename.  The latter will be needed to support a binfs
      binfmt.
    * builtin/binfs.c:  Move apps/builtin/binfs.c to fs/binfs/fs_binfs.c
      CONFIG_APPS_BINDIR rename CONFIG_FS_BINFS
    * apps/include/builtin.h:  Some of the content of
      apps/include/apps.h moved to include/nuttx/binfmt/builtin.h.
      apps/include/apps.h renamed builtin.h
    * apps/builtin/exec_builtins.c:  Move builtin
      utility functions from apps/builtin/exec_builtins.c to
      binfmt/libbuiltin/libbuiltin_utils.c
    * apps/nshlib/nsh_mountcmds.c:  The block driver/source
      argument is now optional.  Many files systems do not need
      a source and it is really stupid to have to enter a bogus
      source parameter.
    * apps/nshlib/nsh_fileapp.c:  Add the ability to execute a file
      from a file system using posix_spawn().
    * apps/builtin/: Extensions from Mike Smith.
    * apps/examples/ftpd/Makefile: Name ftpd_start is not the name of
      the entrypoint.  Should be ftpd_main (from Yan T.)
    * apps/netutils/telnetd/telnetd_driver: Was stuck in a loop if
      recv[from]() ever returned a value &lt;= 0.
    * apps/examples/nettest and poll:  Complete Kconfig files.
    * apps/examples/ostest/waitpid.c:  Need to use WEXITSTATUS()
      to decode the correct exit status.
    * apps/system/usbmonitor:  A daemon that can be used to monitor USB
      trace outpout.
    * apps/nshlib/nsh_usbdev.c, nsh_consolemain.c, nsh_session.c, nsh_script.c:
      Add support for a login script.  The init.d/rcS script will be executed
      once when NSH starts; the .nshrc script will be executed for each session:
      Once for serial, once for each USB connection, once for each Telnet
      session.
    * apps/system/readline: Correct readline() return value.  Was not
      any returning special values when end-of-file or read errors
      occur (it would return an empty string which is not very useful).

NxWidgets-1.5 2013-02-01 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * NxWidgets::CGraphicsPort::move():  Fix typo bug in bounding rectangle
      calculation (from Petteri Aimonen).
    * NxWM::CScrollingPanel::scrollChildren(): Avoid unnecessary redraws in
      CScrollingPanel (contributed by Petteri Aimonen).
    * NxWM::CCycleButton:  Remove the separator from CCycleButton. It draws in
      wrong place, and doesnt look very good in the correct place either.
      (from Petteri Aimonen).
    * NxWidgets::CGraphicsPort: Many times we only want a constant background.
      In that case the old code fills the background, reads it back, renders
      the text and then writes it back. When used with LCD's (instead of
      framebuffers) this causes unnecessary delay and screen flicker.
      This commit adds a variant of drawText that takes background color,
      so that the background and text can both be rendered at one go.
      The old functions still function as before (Petteri Aimonen).
    * NxWidgets::CLabel: The label was drawn as a single rectangular region,
      then a text was added to the on top of this.  The result is that the
      text would flicker when the CLabel was updated. With this change, the
      two step update is replaced with a five step update:  The background
      is updated as four rectangulear regions (leaving the previous text in
      place), then the new text is updated.  This eliminates the flicker
      (Petteri Aimonen).
    * Kconfig: Many NxWidgets/NxWM settings do not have meaningful, generic
      default values.  Colors, for example, depend on pixel depth.  Some
      geometry settings depending on other geometry settings.  Font IDs are
      not know-able by the configuration system.  etc.  In these cases, it
      is best if the settings are just not undefined so that the system can
      calculate a reasonable default.  however, if no default is provided
      in the .config file, mconf will complain and generate errors.  So work
      around this, I added several &quot;enabling&quot; settings to override the
      default setting.  This is awkward and I preferred the configuration as
      it was before, but this avoids the mconf errors and warnings.
    * UnitTests:  Changed occurrences of lib_rawprintf() and lib_lowprintf()
      to match recent changes to NuttX (will be in NuttX-6.25)
    * CGraphicsPort::_drawText:  Renamed from CGraphicsPort::drawText in order
      to eliminate some naming collisions when overloaded in some configurations
      (i.e., when both bool and nx_pixel_t are uint8_t).  From Petteri Aimonen.
    * CNxWidgets::drawContents: Change base drawContents from a do-nothing
      function to a function that fills the widget with the background color.
      This is useful when using CNxWidgets as a &quot;panel&quot; , i.e. a container
      for other widgets. Subclasses will override drawContents and decide
      themselves how to draw the background.
    * CNxWidgets::CTabPanel:  A new widget contributed by Petteri Aimonen.
      This widget provides a tab panel, which has a button bar at the top
      and panels below it. Pressing a button will select the corresponding
      panel.

uClibc++-1.0 2011-11-05 &lt;gnutt@nuttx.org&gt;

    * The initial release of the uClibc++ implementation of the standard
      C++ library for NuttX.  This package was contributed ay Qiang Yu and
      David for the RGMP team.

buildroot-1.11 2011-11-05 &lt;gnutt@nuttx.org&gt;

    * configs/avr-defconfig-4.3.3 - Added --enable-long-long as a GCC
      option.
    * configs/avr-defconfig-4.5.2 - New configuration.
    * Config.in and almost all configurations in configs/ - Changed the
      default nuttx path to $(TOPDIR)/../../nuttx
    * Misc files.  Patch provided by Gerd v. Egidy that solves the following
      problems
      - binutils 2.21 is not available on the gnu servers anymore, they replaced
        it with 2.21.1
      - there is some assembler error when compiling gcc for arm, gcc bugzilla
        43999
      - you can't build nuttx for cortex m3/m4 because of a missing instruction
        in the assembler, binutils bugzilla 12296
    * Add support for binutils 2.22 and GCC 4.6.3.
    * Change name of all tools from xxx-elf to xxx-nuttx-elf
    * Added an ARM EABI GCC 4.6.3 configuration (tool name is arm-nuttx-eabi-).
    * ldnxflat: Add support for the R_ARM_REL32 relocation.  This relocation
      type was not generated by GCC/LD prior to gcc-4.6.3
    * R_ARM_REL32 logic is conditionally disabled because it has not been
      tested.
    * ldnxflat: Correct a memory allocation error that could cause written
      past the end of allocated memory.  Partial restoration of R_ARM_REL32
      logic.  There are lots of issues that I still do not understand here.

pascal-3.0 2011-05-15 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * nuttx/:  The Pascal add-on module now installs and builds under the
      apps/interpreters directory.  This means that the pascal-2.1 module is
      incompatible with will all releases of NuttX prior to nuttx-6.0 where the 
      apps/ module was introduced.
</pre></ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="pendingchanges">Unreleased Changes</a>
  </td>
  </tr>
</table>

<ul>
  <li><b>nuttx-6.18</b>.
    The ChangeLog for the not-yet-released version 6.18 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/nuttx/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>apps-6.18</b>.
    The ChangeLog for the not-yet-released version 6.18 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/apps/ChangeLog.txt?view=log">SourceForge SVN</a>.
  </li>
  <li><b>NxWidgets-1.1</b>.
    The ChangeLog for the not-yet-released version 1.1 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/NxWidgets/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>pascal-1.1</b>.
    The ChangeLog for the not-yet-released version 1.1 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/pascal/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>buildroot-1.11</b>.
    The ChangeLog for the not-yet-released version 1.11 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/buildroot/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="TODO"><h1>Bugs, Issues, <i>Things-To-Do</i></h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
   The current list of NuttX <i>Things-To-Do</i> in SVN <a href="http://svn.code.sf.net/p/nuttx/code/trunk/nuttx/TODO?view=log">here</a>.
   A snapshot of the <i>To-Do</i> list associated with the current release are available <a href="TODO.txt">here</a>.
</p>
</ul>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="documentation"><h1>Other Documentation</h1></a>
  </td>
  </tr>
</table>

<ul><table>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXGettingStarted.html">Getting Started</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttxUserGuide.html">User Guide</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttxPortingGuide.html">Porting Guide</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttShell.html">NuttShell (NSH)</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXBinfmt.html">NuttX Binary Loader</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXNxFlat.html">NXFLAT Binary Format</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NXGraphicsSubsystem.html">NX Graphics Subsystem</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NxWidgets.html">NxWidgets</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXDemandPaging.html">Demand Paging</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="README.html">NuttX README Files</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="ChangeLog.txt">Change Log</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="TODO.txt">To-Do List</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="UsbTrace.html">USB Device Driver Tracing</a></td>
</tr>
</center></ul>

<small>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="trademarks"><h1>Trademarks</h1></a>
  </td>
  </tr>
</table>
<ul>
  <li>ARM, ARM7 ARM7TDMI, ARM9, ARM920T, ARM926EJS Cortex-M3 are trademarks of Advanced RISC Machines, Limited.</li>
  <li>Cygwin is a trademark of Red Hat, Incorporated.</li>
  <li>Linux is a registered trademark of Linus Torvalds.</li>
  <li>Eagle-100 is a trademark of <a href=" http://www.micromint.com/">Micromint USA, LLC</a>.
  <li>LPC2148 is a trademark of NXP Semiconductors.</li>
  <li>TI is a tradename of Texas Instruments Incorporated.</li>
  <li>UNIX is a registered trademark of The Open Group.</li>
  <li>VxWorks is a registered trademark of Wind River Systems, Incorporated.</li>
  <li>ZDS, ZNEO, Z16F, Z80, and Zilog are a registered trademark of Zilog, Inc.</li>
</ul>
<p>
  NOTE: NuttX is <i>not</i> licensed to use the POSIX trademark.  NuttX uses the POSIX
  standard as a development guideline only.
</p>
</small>

</body>
</html>
<html>
<head>
<title>NuttX</title>
</head>
<body background="backgd.gif">
<hr><hr>
<table width ="100%">
  <tr align="center" bgcolor="#e4e4e4">
    <td>
      <h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
      <p>Last Updated: February 18, 2013</p>
    </td>
  </tr>
</table>
<hr><hr>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
    <td>
  <h1>Table of Contents</h1>
    </td>
  </tr>
</table>

<center><table width ="80%">
<tr>
<td>
<table>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#overview">Overview</a>.<br>
    What is NuttX?  Look at all those files and features... How can it be a tiny OS?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#group">NuttX Discussion Group</a>.<br>
    Do you want to talk about NuttX features?  Do you need some help?  Problems?  Bugs?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#downloads">Downloads</a>.<br>
    Where can I get NuttX?  What is the current development status?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#platforms">Supported Platforms</a>.<br>
    What target platforms has NuttX been ported to?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#environments">Development Environments</a>.<br>
    What kinds of host cross-development platforms can be used with NuttX?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#footprint">Memory Footprint</a>.<br>
    Just how big is it?  Do I have enough memory to use NuttX?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#licensing">Licensing</a>.<br>
    Are there any licensing restrictions for the use of NuttX? (Almost none)
    Will there be problems if I link my proprietary code with NuttX? (No)
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#history">Release History</a><br>
    What has changed in the last release of NuttX?
    What unreleased changes are pending in SVN?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#TODO">Bugs, Issues, <i>Things-To-Do</i></a>.<br>
    Software is never finished nor ever tested well enough.
    (Do you want to help develop NuttX?  If so, send me an email).
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#documentation">Other Documentation</a>.<br>
    What other NuttX documentation is available?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#trademarks">Trademarks</a>.<br>
    Some of the words used in this document belong to other people.
  </td>
</tr>
</table>
</td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="overview"><h1>Overview</h1></a>
  </td>
  </tr>
</table>

<p>
  <b>Goals</b>.
  NuttX is a real timed embedded operating system (RTOS).
  Its goals are:
<p>
<center><table width="90%">
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Small Footprint</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Usable in all but the tightest micro-controller environments,
      The focus is on the tiny-to-small, deeply embedded environment.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Rich Feature OS Set</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      The goal is to provide implementations of most standard POSIX OS interfaces
      to support a rich, multi-threaded development environment for deeply embedded
      processors.
    </p>
      NON-GOALS: (1) It is not a goal to provide the level of OS features like those provided by Linux.
      In order to work with smaller MCUs, small footprint must be more important than an extensive feature set.
      But standard compliance is more important than small footprint.
      Surely a smaller RTOS could be produced by ignoring standards.
      Think of NuttX is a tiny Linux work-alike with a much reduced feature set.
      (2) There is no MMU-based support for processes.
      At present, NuttX assumes a flat address space.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Highly Scalable</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Fully scalable from tiny (8-bit) to moderate embedded (32-bit).
      Scalability with rich feature set is accomplished with:
      Many tiny source files, link from static libraries, highly configurable, use of
      weak symbols when available.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Standards Compliance</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      NuttX strives to achieve a high degree of standards compliance.
      The primary governing standards are POSIX and ANSI standards.
      Additional standard APIs from Unix and other common RTOS's are
      adopted for functionality not available under these standards
      or for functionality that is not appropriate for the deeply-embedded
      RTOS (such as <code>fork()</code>).
    </p>
    <p>
      Because of this standards conformance, software developed under other
      standard OSs (such as Linux) should port easily to NuttX.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Real-Time</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Fully pre-emptible, fixed priority and round-robin scheduling.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Totally Open</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Non-restrictive BSD license.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>GNU Toolchains</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Compatible GNU toolchains based on <a href="http://buildroot.uclibc.org/">buildroot</a>
      available for
      <a href="https://sourceforge.net/projects/nuttx/files/">download</a>
      to provide a complete development environment for many architectures.
    </p>
</tr>
</table></center>

<p>
  <b>Feature Set</b>.
  Key features of NuttX include:
<p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Standards Compliant Core Task Management</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Fully pre-emptible.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Naturally scalable.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Highly configurable.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Easily extensible to new processor architectures, SoC architecture, or board architectures.
        A <a href="NuttxPortingGuide.html">Porting Guide</a> is available.
      </li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>FIFO and round-robin scheduling.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Realtime, deterministic, with support for priority inheritance</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>POSIX/ANSI-like task controls, named message queues, counting semaphores, clocks/timers, signals, pthreads, environment variables, filesystem.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>VxWorks-like task management and watchdog timers.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>BSD socket interface.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Extensions to manage pre-emption.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Optional tasks with address environments (<i>Processes</i>).</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Inheritable &quot;controlling terminals&quot; and I/O re-direction.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>On-demand paging.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <li>System logging.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>May be built either as an open, flat embedded RTOS or as a separately built, secure micro-kernel with a system call interface.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Well documented in the NuttX <a href="NuttxUserGuide.html">User Guide</a>.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>File system</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Tiny, in-memory, root pseudo-file-system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Virtual file system supports drivers and mountpoints.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Mount-able volumes.  Bind mountpoint, filesystem, and block device driver.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Generic system logging (SYSLOG) support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        FAT12/16/32 filesystem support with optional FAT long file name support<small><sup>1</sup></small>.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NFS Client. Client side support for a Network File System (NFS, version 3, UDP).
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NXFFS. The tiny NuttX wear-leveling FLASH file system.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>ROMFS filesystem support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>BINFS pseudo-filesystem support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        A <a href="NuttXBinfmt.html">binary loader</a> with support for the following formats:
        <ul>
          <li>Separately linked ELF modules.</li>
          <li>
            Separately linked <a href="NuttXNxFlat.html">NXFLAT</a> modules.
            NXFLAT is a binary format that can be XIP from a file system.
          </li>
          <li>
            &quot;Built-In&quot; applications.</li>
          </li>
        </ul>
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>PATH variable support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><small>
      <sup>1</sup>
      FAT long file name support may be subject to certain Microsoft patent restrictions if enabled.
      See the top-level <code>COPYING</code> file for details.
    </small></p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Device Drivers</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Supports character and block drivers as well as specialized driver interfaces.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Network, USB (host), USB (device), serial, CAN, ADC, DAC, PWM, Quadrature Encoder, and watchdog timer driver architectures.
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        RAMDISK, pipes, FIFO, <code>/dev/null</code>, <code>/dev/zero</code>, <code>/dev/random</code>, and loop drivers.
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Generic driver for SPI-based or SDIO-based MMC/SD/SDH cards.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><a href="NuttxPortingGuide.html#pwrmgmt">Power management</a> sub-system.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>ModBus support provided by built-in <a href="http://freemodbus.berlios.de/">FreeModBus</a> version 1.5.0.</li>
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>C/C++ Libraries</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Standard C Library Fully integrated into the OS.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Includes floating point support via a Standard Math Library.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Add-on <a href="http://cxx.uclibc.org/">uClibc++</a> module provides Standard C++ Library (LGPL).</li>
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Networking</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>TCP/IP, UDP, ICMP, IGMPv2 (client) stacks.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>SLIP</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>A port cJSON</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Small footprint (based on uIP).</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>BSD compatible socket layer.</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Networking utilities (DHCP server and client, SMTP client, TELNET client, FTP server and client, TFTP client, HTTP server and client).  Inheritable TELNET sessions (as &quot;controlling terminal&quot;)</li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NFS Client. Client side support for a Network File System (NFS, version 3, UDP).
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        A NuttX port of Jeff Poskanzer's <a href="http://acme.com/software/thttpd">THTTPD</a> HTTP server
        integrated with the NuttX <a href="NuttXBinfmt.html">binary loader</a> to provide true, embedded CGI.
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        UDP Network Discover (Contributed by Richard Cochran).
      </li>
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        XML RPC Server (Contributed by Richard Cochran).
      </li>
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>FLASH Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>MTD</i>-inspired interface for <i>M</i>emory <i>T</i>echnology <i>D</i>evices.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>FTL</i>.  Simple <i>F</i>lash <i>T</i>ranslation <i>L</i>ayer support file systems on FLASH.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>NXFFS. the NuttX wear-leveling FLASH file system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Support for SPI-based FLASH and FRAM devices.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>USB Host Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB host architecture for USB host controller drivers and device-dependent USB class drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB host controller drivers available for the NXP LPC17xx.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Device-dependent USB class drivers available for USB mass storage and HID keyboard.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>USB Device Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>Gadget</i>-like architecture for USB device controller drivers and device-dependent USB class drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB device controller drivers available for the PIC32, NXP LPC17xx, LPC214x, LPC313x, LPC43xx, STMicro STM32 and TI DM320.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Device-dependent USB class drivers available for USB serial (CDC/ACM and a PL2303 emulation), for USB mass storage, and for a composite CDC/ACM and mass storage device.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Built-in <a href="UsbTrace.html">USB trace</a> functionality for USB debug.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Graphics Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Framebuffer drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>LCD drivers for both parallel and SPI LCDs and OLEDs.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         NX: A graphics library, tiny windowing system and tiny font support that works with either framebuffer or LCD drivers.
         Documented in the <a href="NXGraphicsSubsystem.html">NX Graphics Subsystem</a>
         manual.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Font management sub-system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         <a href="NxWidgets.html">NxWidgets</a>: NXWidgets is library of graphic objects, or &quot;widgets,&quot (labels, buttons, text boxes, images, sliders, progress bars, etc.). NXWidgets is written in C++ and integrates seamlessly with the NuttX NX graphics and font management subsystems.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         <a href="NxWidgets.html">NxWM</a>: NxWM is the tiny NuttX window manager based on NX and NxWidgets.
      </li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Input Devices</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Touchscreen, USB keyboard, GPIO-based buttons and keypads. </li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Analog Devices</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Support for Analog-to-Digital conversion (ADC), Digital-to-Analog conversion (DAC), multiplexers, and amplifiers.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Motor Control</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Pulse width modulation (PWM) / Pulse count modulation.</li>
    </p>
</tr>
</table></center>

<p>
  <b>NuttX Add-Ons</b>.
  The following packages are available to extend the basic NuttX feature set:
</p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>NuttShell (NSH)</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>A small, scalable, bash-like shell for NuttX with rich feature set and small footprint.
        See the <a href="NuttShell.html">NuttShell User Guide</a>.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Pascal Compiler with NuttX runtime P-Code interpreter add-on</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>The Pascal add-on is available for download from the
        <a href="http://sourceforge.net/projects/nuttx/files/">SourceForge</a>
        website.</li>
    </p>
  </td>
</tr>
</table></center>

<p>
  <b>Look at all those files and features... How can it be a tiny OS?</b>.
  The NuttX feature list (above) is fairly long and if you look at the NuttX
  source tree, you will see that there are hundreds of source files comprising
  NuttX.  How can NuttX be a tiny OS with all of that?
</p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Lots of Features -- More can be smaller!</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      The philosophy behind that NuttX is that lots of features are great... <i>BUT</i>
      also that if you don't use those features, then you should not have to pay a penalty
      for the unused features.
      And, with NuttX, you don't!  If you don't use a feature, it will not
      be included in the final executable binary.
      You only have to pay the penalty of increased footprint for the features
      that you actually use.
    </p>
    <p>
      Using a variety of technologies, NuttX can scale from the very tiny to
      the moderate-size system.  I have executed NuttX with some simple applications
      in as little as 32K <i>total</i> memory (code and data).
      On the other hand, typical, richly featured NuttX builds require more like 64K
      (and if all of the features are used, this can push 100K).
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Many, many files -- More really is smaller!</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      One may be intimidated by the size NuttX source tree.  There are hundreds of source files!
      How can that be a tiny OS?
      Actually, the large number of files is one of the tricks to keep NuttX small and
      as scalable as possible.
      Most files contain only a single function. 
      Sometimes just one tiny function with only a few lines of code.
      Why?
    </p>
    <ul>
      <li>
        <b>Static Libraries</b>.
        Because in the NuttX build processed, objects are compiled and saved into
        <i>static libraries</i> (<i>archives</i>).
        Then, when the file executable is linked, only the object files that are needed
        are extracted from the archive and added to the final executable.
        By having many, many tiny source files, you can assure that no code that you do
        not execute is ever included in the link.
        And by having many, tiny source files you have better granularity --
        if you don't use that tiny function of even just a few lines of code, it will
        not be included in the binary.
      </li>
    </ul>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Other Tricks</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      As mentioned above, the use of many, tiny source files and linking from static
      libraries keeps the size of NuttX down.
      Other tricks used in NuttX include:
    </p>
    <ul>
      <li>
         <b>Configuration Files</b>.
         Before you build NuttX, you must provide a configuration file that specifies
         what features you plan to use and which features you do not.
         This configuration file contains a long list of settings that control
         what is built into NuttX and what is not.
         There are hundreds of such settings
         (see the <a href="NuttxPortingGuide.html#apndxconfigs">NuttX Porting Guide</a>
         for a partial list that excludes platform specific settings).
         These many, many configuration options allow NuttX to be highly tuned to
         meet size requirements.
         The downside to all of these configuration options is that it greatly
         complicates the maintenance of NuttX -- but that is my problem, not yours.
      </li>
      <li>
         <b>Weak Symbols</b>
         The GNU toolchain supports <i>weak</i> symbols and these also help to keep
         the size of NuttX down.
         Weak symbols prevent object files from being drawn into the link even if they
         are accessed from source code.
         Careful use of weak symbols is another trick for keep unused code out of the
         final binary.
      </li>
    </ul>
  </td>
</tr>

</table></center>


<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="group"><h1>NuttX Discussion Group</h1></a>
  </td>
  </tr>
</table>

<p>
  Most NuttX-related discussion occurs on the <a href="http://tech.groups.yahoo.com/group/nuttx/" target="_top"><i>Yahoo!</i> NuttX group</a>.
  You are cordially invited to <a href="http://groups.yahoo.com/group/nuttx/join" target="_top">join</a>.
  I make a special effort to answer any questions and provide any help that I can.
</p>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="downloads"><h1>Downloads</h1></a>
  </td>
  </tr>
</table>

<h2>nuttx-6.25 Release Notes</h2>
<p>
  The 92<sup>nd</sup> release of NuttX, Version 6.25, was made on February 1, 2013, and is available for download from the
  <a href="http://sourceforge.net/projects/nuttx/files/">SourceForge</a> website.
  Note that the release consists of two tarballs:  <code>nuttx-6.25.tar.gz</code> and <code>apps-6.25.tar.gz</code>.
  Both may be needed (see the top-level <code>nuttx/README.txt</code> file for build information)
  The change log associated with the release is available <a href="#currentrelease">here</a>.
  Unreleased changes after this release are available in SVN.
  These unreleased changes are also listed <a href="#pendingchanges">here</a>.
</p>
<p>
  This release corresponds with SVN release number: r5595,
  Note that all SVN information has been stripped from the tarballs.
  If you need the SVN configuration, you should check out directly from SVN.
  Revision r5595 should equivalent to release 6.25 of NuttX:
</p>
<ul><pre>
svn checkout -r5595 svn://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
</pre></ul>
<p>Or (HTTP):</p>
<ul><pre>
svn checkout -r5595 http://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
</pre></ul>

<p>
  <b>Additional new features and extended functionality</b>
</p>
<ul>
  <li>
    <p>
      <b>OS Initialization</b>
    </p>
    <ul>
      <li>
        Removed support for <code>CONFIG_BUILTIN_APP_START</code>. 
        This is not really a useful feature and creates a violation of the OS layered architecture.
    </ul>
  </li>
  <li>
    <p>
      <b>Task Creation</b>
    </p>
    <ul>
      <li>
        Implement a simple <code>vfork()</code>).
        In NuttX-6.25, this interface is available only for ARM7/9, ARMv7-M (Cortext-M3/4), and MIPS32 (PIC32MX) platforms.
      </li>
      <li>
        <code>exec()</code> now sets the priority of the new task to the same priority as the parent task (instead of the arbirtrary value of 50).
      </li>
      <li>
        New, partially complient implementations of <code>execv()</code> and <code>execl()</code>.
        These are only partially compliant because they do not overlay any existing &quot;process space&quot; but rather create the new task and <code>exit()</code>.
      </li>
      <li>
        Add a complete implementation of <code>posix_spawn()</code>.
        This standard interface is a better match for an MMU-less architecture than are <code>vfork()</code>) plus <code>execv()</code> or <code>execl()</code>.
      </li>
      <li>
        Add a task start hook that will be called before the task main executes.
        This can be used, for example, to schedule C++ static constructors to run automatically in the context of the new task.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Task Parentage</b>
    </p>
    <ul>
      <li>
        Repartitioned tasking data structures.
        All shared resources are now collected together in a &quot;task group&quot;. 
        A &quot;task group&quot; includes the resource for the original task that are shared with all of the <code>pthreads</code> created by the task.
      </li>
      <li>
        Added support for remember the parent &quot;task group&quot; when a new task is started.
      </li>
      <li>
        Added optional support to record the membership of each thread in the &quot;task group&quot;.
      </li>
      <li>
        Implement support for retaining child task status in the &quot;task group&quot; after the child task exists.
        This is behavior required by POSIX.
        But in NuttX is only enabled with <code>CONFIG_SCHED_HAVE_PARENT</code> and <code>CONFIG_SCHED_CHILD_STATUS</code>.
      </li>
      <li>
        Add internal logic to &quot;reparent&quot; a task.
        This is useful, for example, where the child task is created through a trampoline task that redirects I/O.
        Reparenting allows the caller of <code>posix_spawn()</code> to be reparented for the eventual child thread.
      </li>
      <li>
        Added support for <code>SIGCHLD</code>.
        Sent to all members of the parent &quot;task group&quot; when the finall member of the child task group exits.
      </li>
      <li>
        If <code>SIGCHLD</code> and retention of child task exist status are enabled, then a more spec-compliant version of <code>waitpid()</code> is enabled.
      </li>
      <li>
        New interfaces <code>waitid()</code> and <code>wait()</code> are also enabled when <code>SIGCHLD</code> is enabled.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>File System</b>
    </p>
    <ul>
      <li>
        <code>dup()</code> and <code>dup2()</code> can new be used with opened files in a mounted file system.
        This supports re-direction of output in NSH to files.
      </li>
      <li>
        The <code>binfs</code> file system was moved from <code>apps/builtin</code> to <code>fs/binfs</code>.
        The <code>binfs</code> file system was extended to support execution of &quot;builtin applications&quot; using <code>exec()</code>, <code>execv()</code>, <code>execl()</code>, or <code>posix_spawn()</code>.
      </li>
      <li>
        Added logic based on <code>SIGCHLD</code> to automatically unload and clean-up after running a task that was loaded into memory.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Binary Formats</b>
    </p>
    <ul>
      <li>
        Much of the logic for &quot;builtin applications&quot; was moved from <code>apps/builtin</code> to <code>nuttx/binfmt/libbuiltin</code>.
        Includes some extensions contributed by Mike Smith.
      </li>
      <li>
        A binary loader was added for builtin applications to support execution of &quot;builtin applications&quot; using <code>exec()</code>, <code>execv()</code>, <code>execl()</code>, or <code>posix_spawn()</code>.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Drivers</b>
    </p>
    <ul>
      <li>
        Added logic to marshal and serialized &quot;out-of-band&quot; keyboard commands (such as cursor controls and key release events) intermixed with normal ASCII keypress data.
        The encoding is partially integrated in the HID keyboard driver and the decoding is fully integrated into the <code>apps/examples</code> <code>hidkbd/</code> and <code>keypadtest/</code> (the latter contributed by Denis Carlikli).
      </li>
      <li>
        Driver for the UG-2864HSWEG01 OLED contributed by Darcy Gong.
      </li>
      <li>
        Add support for removable serial devices (like USB serial).
        This support is enabled by <code>CONFIG_SERIAL_REMOVABLE</code>.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>ARMv7-M</b>
    </p>
    <ul>
      <li>
        Added an option to use the <code>BASEPRI</code> register to disable interrupts (instead of the <code>PRIMASK</code> register).
        This eliminates some innocuous hardfaults that interfere with some debug tools.
        You need to switch to the <code>BASEPRI</code> method only if you have such tool interference.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Drivers</b>
    </p>
    <ul>
      <li>
        Bring STM32 F1 DMA capabilities up to par with the STM32 F2/F4 (contributed by Mike Smith).
      </li>
      <li>
        Add support for USART single wire mode (Contributed by the PX4 team).
      </li>
      <li>
        Updates to support for SPI DMA on the STM32 F1/F2/F4.
        From Petteri Aimonen.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Boards</b>
    </p>
    <ul>
      <li>
        New configuration to support the UG-2864HSWEG01 OLED on the STM32F4Discovery board.
      </li>
      <li>
        Added a <code>posix_spawn()</code> test configuration for the STM32F4Discovery.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LM3S/LM4F</b>
    </p>
    <ul>
      <li>
        Files and directories repartitioned to support both LM3S and LM4F using the STM32 organization as a model.
      </li>
      <li>
        Partial definitions for the LM4F contributed by Jose Pablo Carballo (this is still a work in progress).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LM3S Boards</b>
    </p>
    <ul>
      <li>
        Added scripts and documentation to use OpenOCD with the LM3S (from Jose Pablo Carballo).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LPC176x/LPC178x</b>
    </p>
    <ul>
      <li>
        Files and directories repartitioned to support both LPC175x/LPC176x and the LPC177x/LPC178x families using the STM32 organization as a model.
        The LPC1788 port is a work in progress by Rommel Marcelo.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LPC176x/LPC178x Boards</b>
    </p>
    <ul>
      <li>
        Added a configuration to support the Wave Share Open1788 board.
        This is still a work in progress by Rommel Marcelo.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LPC2148 Boards</b>
    </p>
    <ul>
      <li>
        Add basic support for the The0.net ZP213x/4xPA board (with the LPC2148 and the UG_2864AMBAG01 OLED).
      </li>
      <li>
        Add an nxlines configuration for the ZP213x/4xPA (with the LPC2148 and the UG_2864AMBAG01).
       </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Simulator</b>
    </p>
    <ul>
      <li>
        Add an nxlines configuration for the simulator.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Networking</b>
    </p>
    <ul>
      <li>
        Add logic to work around delayed ACKs by splitting packets (contributed by Yan T.).
      </li>
      <li>
        Split <code>net_poll()</code> to create the internal interface <code>psock_poll()</code>.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>LCDs</b>
    </p>
    <ul>
      <li>
        Added support for LCD1602 alphanumeric LCD (HD4468OU controller).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Graphics</b>
    </p>
    <ul>
      <li>
        Added 5x8 monospace font.
        This tiny font is useful for graph labels and for small bitmapped display.
        Contributed by Petteri Aimonen.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Build System</b>
    </p>
    <ul>
      <li>
        Add an options to better manage toolchain prefixes.
      </li>
      <li>
        Redesigned how the context targer works in the <code>apps/</code> directory.
        The old design caused lots of problems when changing configurations because there is no easy way to get the system to rebuild the context.
        This change should solve most the problems and eliminate questions like &quot;Why don't I see my builtin application in NSH?&quot;
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Kconfig Files</b>
    </p>
    <ul>
      <li>
        <p>
          There are several new configurations that use the kconfig-frontends tools and several older configurations that have been converted to use these tools.
          There is still a long way to go before the conversion is complete:
        </p>
        <ul>
          <li>
            <code>configs/sim/nxwm</code>
          </li>
          <li>
            <code>configs/sim/nsh</code>
          </li>
          <li>
            <code>configs/stm3220g-eval/nxwm</code>
          </li>
          <li>
            <code>configs/stm32f4discovery/posix_spawn</code>
          </li>
          <li>
            <code>configs/olimex-lpc1766stk/nsh</code>
          </li>
          <li>
            <code>configs/olimex-lpc1766stk/hidkbd</code>
          </li>
          <li>
            <code>configs/olimex-lpc1766stk/nettest</code>
          </li>
          <li>
            <code>configs/open1788/ostest</code>
          </li>
          <li>
            <code>configs/stm32f4discovery/nsh</code>
          </li>
          <li>
            <code>configs/stm32f4discovery/usbnsh</code>
          </li>
          <li>
            <code>configs/lm326965-ek</code> (all configurations)
          </li>
          <li>
            <code>configs/mcu123-214x/nsh</code>
          </li>
          <li>
            <code>configs/ubw32/ostest</code>
          </li>
        </ul>
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Tools</b>
    </p>
    <ul>
      <li>
        <code>tools/kconfig.bat</code>:  Kludge to run kconfig-frontends from a DOS shell.
      </li>
      <li>
        <code>tools/configure.c</code>:  <code>configure.c</code> can be used to build a work-alike program as a replacement for <code>configure.sh</code>.
        This work-alike program would be used in environments that do not support Bash scripting (such as the Windows native environment).
      </li>
      <li>
        <code>tools/configure.bat</code>: <code>configure.bat</code> is a small Windows batch file that can be used as a replacement for <code>configure.sh</code> in a Windows native environment.
        <code>configure.bat</code> is actually just a thin layer that executes <code>configure.exe</code> if it is available.
        If <code>configure.exe</code> is not available, then configure.bat will attempt to build it first (assumes the MinGW-GCC is available).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Applications</b>
    </p>
    <ul>
      <li>
        New and modified examples:
        <p>
          <ul>
            <li>
              <code>apps/examples/wlan</code>: Remove non-functional example.
            </li>
            <li>
              <code>apps/examples/ostest</code>: Added a test of <code>vfork()</code>).
              Extend signal handler test to catch death-of-child signals (<code>SIGCHLD</code>).
              Add a test for <code>waitpid()</code>, <code>waitid()</code>, and <code>wait()</code>.
            </li>
            <li>
              <code>apps/exampes/posix_spawn</code>: Added a test of <code>posix_spawn()</code>.
            </li>
          </ul>
        <p>
      </li>
      <li>
        NSH:
        <p>
          <ul>
            <li>
              NSH now supports re-direction of I/O to files (but still not from).
            </li>
            <li>
              The block driver source argument to the mount command is now optional for file systems that do not require a block driver.
            </li>
          </ul>
        </p>
      </li>
      <li>
        NSH can now execute a program from a file system using <code>posix_spawn()</code>.
      </li>
      <li>
        Added support for a login script.
        The <code>init.d/rcS</code> script will be executed once when NSH starts;
        the <code>.nshrc</code> script will be executed for each session:
        Once for a serial console, once for each USB connection, and once for each Telnet session.
      </li>
      <li>
        Supports a new daemon that can be used to monitor USB trace outpout.
      </li>
      <li>
        Removed non-functional <code>wlan</code> example.
      </li>
    </ul>
  </li>
</ul>
<p>
  <b>Bugfixes</b> (see the change log for details).
  Some of these are very important:
</p>
<ul>
  <li>
    <p>
      <b>Tasking</b>
    </p>
    <ul>
      <li>
        Fixed a *critical* task exit bug.
        Here is the failure scenario:
        (1) <code>sched_lock()</code> is called increments the lockcount on the current TCB (i.e., the one at the head of the ready to run list),
        (2) <code>sched_mergepending()</code> is called which may change the task at the head of the ready-to-run list, then
        (3) <code>sched_unlock()</code> is called which decrements the lockcount on the wrong TCB.
        The failure case that I saw was that pre-emption got disabled in the IDLE thread, locking up the whole system.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Signals</b>
    </p>
    <ul>
      <li>
        <code>sigtimedwait()</code> would return a bad signal number if the signal was already pending when the function was called.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Drivers</b>
    </p>
    <ul>
      <li>
        Some SD cards will appear busy until switched to SPI mode for first time.
        Having a pull-up resistor on MISO may avoid this problem, but this fix from Petteri Aimonen makes it work also without pull-up.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Drivers</b>
    </p>
    <ul>
      <li>
        STM32 FLASH driver counting error (from Freddie Chopin).
      </li>
      <li>
        STM32 F4 maximum SPI frequency was wrong (corrected by Petteri Aimonen).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>STM32 Boards</b>
    </p>
    <ul>
      <li>
        Due to cloning of untested code, the logic to control on-board LEDs did not work on any STM32 boards.
      </li>
      <li>
        Serial devices number <code>/dev/ttyS0-5</code> is there is a serial console, but <code>/dev/ttyS1-6</code> if there is no serial console.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Binary Formats</b>
    </p>
    <ul>
      <li>
        C++ static constructors execute now using a start taskhook so that they execute in the context of the child task (instead of in the context of the parent task).
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>File Systems</b>
    </p>
    <ul>
      <li>
        Several FAT-related bugs fixed by Petteri Aimonen.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Networking</b>
    </p>
    <ul>
      <li>
        Fix poll/select issure reported by Qiang: <code>poll_interrupt()</code> must call <code>net_lostconnection()</code> when a loss of connection is reported.
        Otherwise, the system will not remember that the connection has been lost and will hang waiting on a unconnected socket later.
      </li>
      <li>
        Similar issues corrected for <code>recvfrom()</code> and <code>send()</code>.
      </li>
      <li>
        Telnetd would hang in a loop if <code>recv()</code> ever returned a value &lt;= 0.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Libraries</b>
    </p>
    <ul>
      <li>
        <code>fread()</code> could hang on certain error conditions.
      </li>
      <li>
        Can't handle <code>SYSLOG</code> output to a character device from the IDLE task (because the IDLE task can't block). 
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Build System</b>
    </p>
    <ul>
      <li>
      Serial was driver was not being built if there is no console device.
      Obviously, the serial driver may be needed even in this case.
      </li>
    </ul>
  </li>
  <li>
    <p>
      <b>Additional Bugfixes</b>
    </p>
    <ul>
      <li>
        <code>sig_timedwait()</code> and <code>clock_time2ticks.c</code>:  Timing &quot;rounding&quot; logic
      </li>
      <li>
        ARM9 Compilation issue with low vectors.
      </li>
      <li>
        <code>readline()</code> return value
      </li>
      <li>
        As well as other, less critical bugs as detailed in the ChangeLog: HID keyboard, LPC17xx bit definitions, strndup(), PL2303, SYSLOG error handling, AT25, <code>apps/examples</code>.
      </li>
    </ul>
  </li>
</ul>
<p>
  See the <a href="#currentrelease">ChangeLog</a> for additional, detailed changes.
</p>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="platforms"><h1>Supported Platforms</h1></a>
  </td>
  </tr>
</table>

<p>
  The short story (Number of ports follow in parentheses).
  The state of the various ports vary from board-to-board.
  Follow the links for the details:
</p>
<center><table width="90%">
<ul>
  <tr>
  <td bgcolor="#e4e4e4" valign="top">
  <li><a href="#linuxusermode">Linux user mode simulation</a> (1)</li>
  <li>ARM
    <ul>
      <li><a href="#arm7tdmi">ARM7TDMI</b></a> (5)</li>
      <li><a href="#arm920t">ARM920T</a> (1) </li>
      <li><a href="#arm926ejs">ARM926EJS</a> (3) </li>
      <li><a href="#armcortexm0">ARM Cortex-M0</a> (1)</li>
      <li><a href="#armcortexm3">ARM Cortex-M3</a> (16)</li>
      <li><a href="#armcortexm4">ARM Cortex-M4</a> (6)</li>
    </ul>
  <li>Atmel AVR
    <ul>
      <li><a href="#atmelavr">Atmel 8-bit AVR</a> (3) </li>
      <li><a href="#atmelavr32">Atmel AVR32</a> (1) </li>
    </ul>
  </li>
  </td>
  <td bgcolor="#e4e4e4" valign="top">
  <li>Freescale <a href="#m68hcs12">M68HCS12</a> (2) </li>
  <li>Intel
    <ul>
      <li><a href="#8052">Intel 8052 Microcontroller</a> (1)</li>
      <li><a href="#80x86">Intel 80x86</a> (2)</li>
    </ul>
  </li>
  <li>MicroChip <a href="#pic32mips">PIC32MX</a> (MIPS) (4)</li>
  <li>Renesas/Hitachi:
    <ul>
        <li><a href="#superh">Renesas/Hitachi SuperH</a> (1/2)</li>
        <li><a href="#m16c">Renesas M16C/26</a> (1/2)</li>
    </ul>
  </li>
  </td>
  <td bgcolor="#e4e4e4" valign="top">
  <li>ZiLOG
    <ul>
        <li><a href="#zilogz16f">ZiLOG Z16F</a> (1)</li>
        <li><a href="#zilogez80acclaim">ZiLOG eZ80 Acclaim!</a> (1)</li>
        <li><a href="#zilogz8encore">ZiLOG Z8Encore!</a> (2)</li>
        <li><a href="#zilogz180">ZiLOG Z180</a> (1)</li>
        <li><a href="#zilogz80">ZiLOG Z80</a> (2)</li>
    </ul>
  </li>
</ul>
  </tr>
</table></center>

<p>The details, caveats and fine print follow:</p>

<center><table width="90%">
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="linuxusermode"><b>Linux User Mode</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      A user-mode port of NuttX to the x86 Linux/Cygwin platform is available.
      The purpose of this port is primarily to support OS feature development.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Does not support interrupts but is otherwise fully functional.
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm7tdmi"><b>ARM7TDMI</b></a>.
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI TMS320C5471</b> (also called <b>C5471</b> or <b>TMS320DA180</b> or <b>DA180</b>).
      NuttX operates on the ARM7 of this dual core processor.
      This port uses the <a href="http://www.spectrumdigital.com/">Spectrum Digital</a>
      evaluation board with a GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port is complete, verified, and included in the initial NuttX release.
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Calypso</b>.
      This port supports the TI &quot;Calypso&quot; MCU used in various cell phones (and, in particular,
      by the <a href="http://bb.osmocom.org/trac/">Osmocom-bb project</a>).
      Like the c5471, NuttX operates on the  ARM7 of this dual core processor.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC214x</b>.
      Support is provided for the NXP LPC214x family of processors.  In particular,
      support is provided for (1) the mcu123.com lpc214x evaluation board (LPC2148)
      and (1) the The0.net ZPA213X/4XPA development board (with the The0.net UG-2864AMBAG01 OLED)
      This port also used the GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port boots and passes the OS test (apps/examples/ostest).
        The port is complete and verified.  As of NuttX 0.3.17, the port includes:
        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.
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
        with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
        package.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC2378</b>.
      Support is provided for the NXP LPC2378 MCU.  In particular,
      support is provided for the Olimex-LPC2378 development board.
      This port was contributed by Rommel Marcelo is was first released in NuttX-5.3.
      This port also used the GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port boots and passes the OS test (apps/examples/ostest) and includes a
        working implementation of the NuttShell (<a href="NuttShell.html">NSH</a>).
        The port is complete and verified.
        As of NuttX 5.3, the port includes only basic timer interrupts and serial console support.
      </p>
      <p>
        <b>Development Environments:</b> (Same as for the NXP LPC214x).
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STR71x</b>.
      Support is provided for the STMicro STR71x family of processors.  In particular,
      support is provided for the Olimex STR-P711 evaluation board.
      This port also used the GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Integration is complete on the basic port (boot logic, system time, serial console).
        Two configurations have been verified: (1) The board boots and passes the OS test
        with console output visible on UART0, and the NuttShell (<a href="NuttShell.html">NSH</a>)
        is fully functional with interrupt driven serial console.  An SPI driver is available
        but only partially tested.  Additional features are needed: USB driver, MMC integration,
        to name two (the slot on the board appears to accept on MMC card dimensions; I have only
        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).
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
        with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
        package.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm920t"><b>ARM920T</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Freescale MC9328MX1</b> or <b>i.MX1</b>.
      This port uses the Freescale MX1ADS development board with a GNU arm-nuttx-elf toolchain*
      under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port has stalled due to development tool issues.
          Coding is complete on the basic port (timer, serial console, SPI).
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm926ejs"><b>ARM926EJS</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI TMS320DM320</b> (also called <b>DM320</b>).
      NuttX operates on the ARM9 of this dual core processor.
      This port uses the
      <a href="http://wiki.neurostechnology.com/index.php/Developer_Welcome">Neuros OSD</a>
      with a GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
      The port was performed using the OSD v1.0, development board.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <b>NXP <a href="http://ics.nxp.com/products/lpc3000/lpc313x.lpc314x.lpc315x/">LPC3131</a></b>.
    The port for the NXP LPC3131 on the <a href="http://www.embeddedartists.com/products/kits/lpc3131_kit.php">Embedded Artists EA3131</a> 
    development board was first released in NuttX-5.1 with a GNU arm-nuttx-elf or arm-eabi toolchain* under Linux or Cygwin
    (but was not functional until NuttX-5.2).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          The basic EA3131 port is complete and verified in NuttX-5.2 
          This basic port includes basic boot-up, serial console, and timer interrupts.
          This port was extended in NuttX 5.3 with a USB high speed driver contributed by David Hewson.
          David also contributed I2C and SPI drivers plus several important LPC313x USB bug fixes
          that appear in the NuttX 5.6 release.
          This port has been verified using the NuttX OS test, USB serial and mass storage
          tests and includes a working implementation of the NuttShell (<a href="NuttShell.html">NSH</a>).
      </p>
      <p>
          Support for <a href="NuttXDemandPaging.html">on-demand paging</a> has been developed for the EA3131.
      That support would all execute of a program in SPI FLASH by paging code sections out of SPI flash as needed.
      However, as of this writing, I have not had the opportunity to verify this new feature.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <b>NXP <a href="http://ics.nxp.com/products/lpc3000/lpc313x.lpc314x.lpc315x/">LPC315x</a></b>.
    Support for the NXP LPC315x family has been incorporated into the code base as of NuttX-6.4.
    Support has added for the Embedded Artists EA3152 board in NuttX-6.11.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          Basic support is in place for both the LPC3152 MCU and the EA3152 board.
          Verification of the port was deferred due to tool issues
          However, because of the high degree of compatibility between the LPC313x and LPC315x family, it
          is very likely that the support is in place (or at least very close).
          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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm0"><b>ARM Cortex-M0</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NuvoTon NUC120</b>.
      This is a port of NuttX to the Nuvoton NuTiny-SDK-NUC120 that features the NUC120LE3AN MCU.
    </p>
    <ul>
      <p>
        <b>STATUS</b>.
        As of this writing, this is very much a work in progress.
        For a full-featured RTOS such as NuttX, providing support in a usable and meaningful way within the tiny memories of the NUC120 will be a challenge (128KB FLASH and 16KB of SRAM).
        Initial support for the NUC120 is expected in NuttX-6.26.
      </p>
    </ul>
    <p>
      <b>Development Environments:</b>
      1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
      with Windows native toolchain, or 4) Native Windows.
      A DIY toolchain for Linux or Cygwin is provided by the NuttX
      <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
    </p>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm3"><b>ARM Cortex-M3</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Stellaris LM3S6432</b>.
      This is a port of NuttX to the Stellaris RDK-S2E Reference Design Kit and the MDL-S2E Ethernet to Serial module
      (contributed by Mike Smith).
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S6918</b>.
      This port uses the <a href=" http://www.micromint.com/">Micromint</a> Eagle-100 development
      board with a GNU arm-nuttx-elf toolchain* under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          The initial, release of this port was included in NuttX  version 0.4.6.
          The current port includes timer, serial console, Ethernet, SSI, and microSD support.
          There are working configurations the NuttX OS test, to run the <a href="NuttShell.html">NuttShell
          (NSH)</a>, the NuttX networking test, and the uIP web server.
      </p>
     </ul>
    <p>
      <b>Development Environments:</b>
      1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
      with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux
      or Cygwin is provided by the NuttX
      <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
      package.
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S6965</b>.
      This port uses the Stellaris LM3S6965 Ethernet Evalution Kit with a GNU arm-nuttx-elf toolchain*
      under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was released in NuttX 5.5.  
          Features are the same as with the Eagle-100 LM3S6918 described above.
          The apps/examples/ostest configuration has been successfully verified and an
          NSH configuration with Telnet support is available.
          MMC/SD and Networking support was not been thoroughly verified:
          Current development efforts are focused on porting the NuttX window system (NX)
          to work with the Evaluation Kits OLED display.
      </p>
      <p><small>
         <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.
      </small></p>
     </ul>
    <p>
      <b>Development Environments:</b> See the Eagle-100 LM3S6918 above.
    </p>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S8962</b>.
      This port uses the Stellaris EKC-LM3S8962 Ethernet+CAN Evalution Kit with a GNU arm-nuttx-elf toolchain*
      under either Linux or Cygwin.
      Contributed by Larry Arnold.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was released in NuttX 5.10. 
          Features are the same as with the Eagle-100 LM3S6918 described above.
      </p>
     </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S9B96</b>.
      Header file support was contributed by Tiago Maluta for this part.
      Jose Pablo Rojas V. is currently using those header file changes to port NuttX to the TI/Stellaris EKK-LM3S9B96.
      With any luck, that port should be working and available in the NuttX-6.20 release.
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Stellaris LM3S6432S2E</b>.
      This port uses Serial-to-Ethernet Reference Design Kit (<a href="http://www.ti.com/tool/rdk-s2e">RDK-S2E</a>)
      and has similar support as for the other Stellaris family members.
      Configurations are available for the OS test and for the NuttShell (NSH)
      (see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
      The NSH configuration including networking support with a Telnet NSH console.
      This port was contributed by Mike Smith.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was will be released in NuttX 6.14. 
      </p>
     </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F100x (STM32 F1 &quot;Value Line&quot;Family)</b>.
      Chip support for these STM32 &quot;Value Line&quot; family was contributed by Mike Smith and users have reported that they have successful brought up NuttX on there proprietary boards using this logic.
      This logic was extended to support the <i>high density</i> STM32F100RC chips by Freddie Chopin
      However, there is <i>no</i> specific board support for this chip families in the NuttX source tree.
      There is, however, <i>generic</i> support for STM32F100RC boards.
    </p>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F103x (STM32 F1 Family)</b>.
      Support for four MCUs and four board configurations are available.
      MCU support includes all of the high density and connectivity line families.
      Board supported is available specifically for: STM32F103ZET6, STM32F103RET6, STM32F103VCT, and STM32F103VET6.
      Boards supported include:
    </p>
    <ol>
      <li>
        A port for the <a href=" http://www.st.com/">STMicro</a> STM3210E-EVAL development board that
        features the STM32F103ZET6 MCU.
      </li>
      <li>
        The ISOTEL NetClamps VSN V1.2 ready2go sensor network platform based on the
        STMicro STM32F103RET6.  Contributed by Uros Platise.
      </li>
      <li>
        A port for the HY-Mini STM32v board.  This board is based on the
        STM32F103VCT chip.  Contributed by Laurent Latil.
      </li>
      <li>
         The M3 Wildfire development board (STM32F103VET6), version 2.
         See <a href="http://firestm32.taobao.com">http://firestm32.taobao.com</a> (the current board is version 3).
      </li>
    </ol>
    <p>
      These ports uses a GNU arm-nuttx-elf toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
      </p>
      <ul>
        <li><b>Basic Support/Drivers</b>.
          The basic STM32 port was released in NuttX version 0.4.12. The basic port includes boot-up
          logic, interrupt driven serial console, and system timer interrupts.
          The 0.4.13 release added support for SPI, serial FLASH, and USB device.;
          The 4.14 release added support for buttons and SDIO-based MMC/SD and verifed DMA support.
          Verified configurations are available for NuttX OS test, the NuttShell (NSH) example,
          the USB serial device class, and the USB mass storage device class example.
        </li>
        <li><b>NetClamps VSN</b>.
          Support for the NetClamps VSN was included in version 5.18 of NuttX.
          Uros Platise added support for timers, RTC, I2C, FLASH, extended power management
          and other features.
        </li>
        <li><b>Additional Drivers</b>.
          Additional drivers and configurations were added in NuttX 6.13 and later releases for the STM32 F1 and F4.
          F1 compatible drivers include an Ethernet driver, ADC driver, DAC driver, PWM driver, IWDG, WWDG, and CAN drivers.
        </li>
        <li><b>M3 Wildfire</b>.
          Support for the Wildfire board was included in version 6.22 of NuttX.
          The board port is basically functional.
          Not all features have been verified.
          Support for FAT file system on an an SD card had been verified.
          The ENC28J60 network is functional (but required lifting the chip select pin on the W25x16 part).
          Customizations for the v3 version of the Wildfire board are selectable (but untested).
        </li>
      </ul>
     </ul>
     <p>
       <b>Development Environments:</b>
       1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
       with Windows native toolchain (RIDE7, CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain or Linux
       or Cygwin is provided by the NuttX
       <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
       package.
     </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F107x (STM32 F1 &quot;Connectivity Line&quot; family)</b>.
      Chip support for the STM32 F1 &quot;Connectivity Line&quot; family has been present in NuttX for some time and users have reported that they have successful brought up NuttX on there proprietary boards using this logic.
    </p>
    <p>
      <b>Olimex STM32-P107</b>
      Support for the <a href="https://www.olimex.com/dev/stm32-p107.html">Olimex STM32-P107</a> was contributed by Max Holtzberg and first appeared in NuttX-6.21.  That port features the STMicro STM32F107VC MCU.
      <ul>
        <b>STATUS:</b>
        Configurations for the basic OS test and NSH are available and verified.
        Networking is functional.
      </ul>
    </p>
    <p>
      <b>Shenzhou IV</b>
      Work is underway as of this writing to port NuttX to the Shenzhou IV development board (See <a href="http://www.armjishu.com">www.armjishu.com</a>) featuring the STMicro STM32F107VCT MCU.
      If all goes according to plan, this port should be verified and available in NuttX-6.22.
      <ul>
        <b>STATUS:</b>
        In progress.
        The following have been verified:
        (1) Basic Cortex-M3 port, 
        (2) Ethernet,
        (3) On-board LEDs
      </ul>
    </p>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F207IG (STM32 F2 family)</b>.
      Support for the STMicro STM3220G-EVAL development board was contributed by Gary Teravskis and first released in NuttX-6.16.
    </p>
    <ul>
      <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.
      </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Atmel AT91SAM3U</b>.
      This port uses the <a href="http://www.atmel.com/">Atmel</a> SAM3U-EK
      development board that features the AT91SAM3U4E MCU.
      This port uses a GNU arm-nuttx-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The basic SAM3U-EK port was released in NuttX version 5.1. The basic port includes boot-up
        logic, interrupt driven serial console, and system timer interrupts.
        That release passes the NuttX OS test and is proven to have a valid OS implementation.
        A configuration to support the NuttShell is also included.
        NuttX version 5.4 adds support for the HX8347 LCD on the SAM3U-EK board.
        This LCD support includes an example using the
        <a href=" http://www.nuttx.org/Documentation/NXGraphicsSubsystem.html">NX graphics system</a>.
        NuttX version 6.10 adds SPI support.
      </p>
      <p>
        Subsequent NuttX releases will extend this port and add support for SDIO-based SD cards and
        USB device (and possible LCD support).
        These extensions may or may not happen soon as my plate is kind of full now.
      </p>
     </ul>
     <p>
       <b>Development Environments:</b>
       1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
       with Windows native toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for inux
       or Cygwin is provided by the NuttX
       <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
       package.
     </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC1766, LPC1768, and LPC1769</b>.
      Drivers are available for CAN, DAC, Ethernet, GPIO, GPIO interrupts, I2C, UARTs, SPI, SSP, USB host, and USB device.
      Verified LPC17xx onfigurations are available for three boards.
      <ul>
        <li>
          The Nucleus 2G board from <a href="http://www.2g-eng.com/">2G Engineering</a> (LPC1768),
        </li>
        <li>
          The mbed board from <a href="http://mbed.org">mbed.org</a> (LPC1768, Contributed by Dave Marples), and
        </li>
        <li>
          The LPC1766-STK board from <a href="http://www.olimex.com/">Olimex</a> (LPC1766).
        </li>
        <li>
          The Embedded Artists base board with NXP LPCXpresso LPC1768.
        </li>
        <li>
          The <a href="http://micromint.com/">Micromint</a> Lincoln60 board with an NXP LPC1769.
        </li>
      </ul>
    </p>
    <p>
      The Nucleus 2G board, the mbed board, and the LPCXpresso all feature the NXP LPC1768 MCU;
      the Olimex LPC1766-STK board features an LPC1766.
      All use a GNU arm-nuttx-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The following summarizes the features that has been developed and verified on individual LPC17xx-based boards.
        These features should, however, be common and available for all LPC17xx-based boards.
      </p>
      <ol>
        <li>
        <p><b>Nucleus2G LPC1768</b></p>
        <ul>
          <li>
            Some initial files for the LPC17xx family were released in NuttX 5.6, but
          </li>
          <li>
            The first functional release for the NXP LPC1768/Nucleus2G occured with NuttX 5.7 with
            Some additional enhancements through NuttX-5.9.
          </li>
        </ul>
      </p>
      <p>
        That initial, 5.6, basic release included <i>timer</i> interrupts and a <i>serial console</i> and was
        verified using the NuttX OS test (<code>apps/examples/ostest</code>).
        Configurations available include include a verified NuttShell (NSH) configuration
        (see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
        The NSH configuration supports the Nucleus2G's microSD slot and additional configurations
        are available to exercise the the USB serial and USB mass storage devices.
        However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified.
        (Although they have since been verfiied on other platforms; this needs to be revisited on the Nucleus2G).
      </p>
      </li>
      <li>
        <p><b>mbed LPC1768</b></p>
        <ul>
          <li>
            Support for the mbed board was contributed by Dave Marples and released in NuttX-5.11.
          </li>
        </ul>
      </p>
      <p>
        This port includes a NuttX OS test configuration (see <code>apps/examples/ostest</code>).
      </p>
      </li>
      <li>
        <p><b>Olimex LPC1766-STK</b></p>
        <ul>
          <li>
            Support for that Olimex-LPC1766-STK board was added to NuttX 5.13.
          </li>
          <li>
            The NuttX-5.14 release extended that support with an <i>Ethernet driver</i>.
          </li>
          <li>
            The NuttX-5.15 release further extended the support with a functional <i>USB device driver</i> and <i>SPI-based micro-SD</i>.
          </li>
          <li>
            The NuttX-5.16 release added a functional <i>USB host controller driver</i> and <i>USB host mass storage class driver</i>.
          </li>
          <li>
            The NuttX-5.17 released added support for low-speed USB devicers, interrupt endpoints, and a <i>USB host HID keyboard class driver</i>.
          </li>
        </ul>
      </p>
      <p>
        Verified configurations are now available for the NuttX OS test,
        for the NuttShell with networking and microSD support(NSH, see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>),
        for the NuttX network test, for the <a href="http://acme.com/software/thttpd">THTTPD</a> webserver,
        for USB serial deive and USB storage devices examples, and for the USB host HID keyboard driver.
        Support for the USB host mass storage device can optionally be configured for the NSH example.
        A driver for the <i>Nokia 6100 LCD</i> and an NX graphics configuration for the Olimex LPC1766-STK have been added.
        However, neither the LCD driver nor the NX configuration have been verified as of the the NuttX-5.17 release.
      </p>
      </li>
      <li>
        <p><b>Embedded Artists base board with NXP LPCXpresso LPC1768</b></p>
        <p>
           An fully verified board configuration is included in NuttX-6.2.
           The Code Red toolchain is supported under either Linux or Windows.
           Verifed configurations include DHCPD, the NuttShell (NSH), NuttX graphis (NX), the NuttX OS test, THTTPD, and USB mass storage device.
        </p>
      </li>
      <li>
        <p><b>Micromint Lincoln60 board with an NXP LPC1769</b></p>
        <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 for more information about the <a href="http://micromint.com/Products/lincoln60.html">Lincoln60</a> board.
           More to come.
        </p>
      </li>
      </ol>
     </ul>
     <p>
       <b>Development Environments:</b>
       1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS
       with Windows native toolchain (CodeSourcery devkitARM or Code Red), or 4) Native Windows.  A DIY toolchain for Linux
       or Cygwin is provided by the NuttX
       <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
     </p>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm4"><b>ARM Cortex-M4</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>FreeScale Kinetis K40</b>.
      This port uses the Freescale Kinetis KwikStik K40.
      Refer to the <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KWIKSTIK-K40">Freescale web site</a> for further information about this board.
      The Kwikstik is used with the FreeScale Tower System (mostly just to provide a simple UART connection)
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The unverified KwikStik K40 first appeared in NuttX-6.8
        As of this writing, the basic port is complete but I accidentally locked my board during the initial bringup.
        Further development is stalled unless I learn how to unlock the device (or until I get another K40).
        Additional work remaining includes, among other things: (1) complete the basic bring-up,
        (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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>FreeScale Kinetis K60</b>.
      This port uses the Freescale Kinetis TWR-K60N512 tower system.
      Refer to the <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=TWR-K60N512-KIT">Freescale web site</a> for further information about this board.
      The TWR-K60N51 includes with the FreeScale Tower System which provides (among other things) a DBP UART connection.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        As of this writing, the basic port is complete and passes the NuttX OS test.
        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 is completely untested.
        Additional work remaining includes: (1) integrate the Ethernet and SDHC drivers, and (2) develop support for USB host and device.
        NOTE: Most of these remaining tasks (excluding the Ethernet driver) are the same as the pending K40 tasks described above.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM3240G-EVAL (STM32 F4 family)</b>.
      This port uses the STMicro STM3240G-EVAL board featuring the STM32F407IGH6 MCU.
      Refer to the <a href="http://www.st.com/internet/evalboard/product/252216.jsp">STMicro web site</a> for further information about this board.
    </p>
    <p>
      <b>STATUS:</b>
      <ul>
        <li><b>NuttX-6.12</b>
          The basic port is complete and first appeared in NuttX-6.12.
          The initial port passes the NuttX OS test and includes a validated configuration for the NuttShell (NSH, see the
          <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>) as well as several other configurations.
        </li>
        <li><b>NuttX-6.13-6.16</b>
          Additional drivers and configurations were added in NuttX 6.13-6.16.
          Drivers include an Ethernet driver, ADC driver, DAC driver, PWM driver, CAN driver, F4 RTC driver, Quadrature Encoder, DMA, SDIO with DMA
          (these should all be compatible with the STM32 F2 family and many should also be compatible with the STM32 F1 family as well).
        </li>
        <li><b>NuttX-6.16</b>
          The NuttX 6.16 release also includes and logic for saving/restoring F4 FPU registers in context switches.
          Networking intensions include support for Telnet NSH sessions and new configurations for DHPCD and the networking test (nettest).
        </li>
        <li><b>NuttX-6.17</b>
          The USB OTG device controller driver, and LCD driver and a function I2C driver were added in NuttX 6.17.
        </li>
        <li><b>NuttX-6.18</b>
          STM32 IWDG and WWDG watchdog timer drivers were added in NuttX 6.18 (should be compatible with F1 and F2).
          An LCD driver and a touchscreen driver for the STM3240G-EVAL based on the STMPE811 I/O expander were also added in NuttX 6.18.
        </li>
        <li><b>NuttX-6.21</b>
          A USB OTG host controller driver was added in NuttX 6.21.
        </li>
      </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F4-Discovery (STM32 F4 family)</b>.
      This port uses the STMicro STM32F4-Discovery board featuring the STM32F407VGT6 MCU.
      Refer to the <a href="http://www.st.com/internet/evalboard/product/252419.jsp">STMicro web site</a> for further information about this board.
    </p>
    <ul>
      <p>
        <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 plaform as well.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F3-Discovery (STM32 F3 family)</b>.
      This port uses the STMicro STM32F3-Discovery board featuring the STM32F303VCT6 MCU (STM32 F3 family).
      Refer to the <a href="http://www.st.com/internet/evalboard/product/254044.jsp">STMicro web site</a> for further information about this board.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        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 plaform as well.
        New drivers will be required for ADC and I2C which are very different on this platform.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXG Technologies LPC4330-Xplorer</b>.
      This NuttX port is for the LPC4330-Xplorer board from NGX Technologies featuring the NXP LPC4330FET100 MCU.
      See the <a href="http://shop.ngxtechnologies.com/product_info.php?cPath=21_37&products_id=104">NXG website</a> for further information about this board.
    </p>
    <p>
      <b>STATUS:</b>
    </p>
    <ul>
      <li>
        <p><b>NuttX-6.20</b>
          The basic port is complete.
          The OS test configuration and the basic NSH configurations are 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:
          <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 poriting 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>
        </p>
      </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>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
  <p>
    <b>Development Environments:</b>
    1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU Cortex-M3 or 4 toolchain, 3) Cygwin/MSYS with Windows native GNU Cortex-M3 or M4 toolchain (CodeSourcery or devkitARM), or 4) Native Windows.  A DIY toolchain for Linux or Cygwin is provided by the NuttX
    <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
    I use FreeScale's <i>CodeWarrior</i> IDE only to work with the JTAG debugger built into the Kinetis boards.
    I use the <i>Code Red</i> IDE with the some of the NXP parts and the <i>Atollic</i> toolchain with some of the STMicroelectronics parts.
  </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="atmelavr"><b>Atmel AVR</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>SoC Robotics ATMega128</b>.
      This port of NuttX to the Amber Web Server from <a href="http://www.soc-robotics.com/index.htm">SoC Robotics</a>
      is partially completed.
      The Amber Web Server is based on an Atmel ATMega128.
    </p>
    <ul>
      <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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Micropendous 3 AT90USB64x</b> and <b>AT90USB6128x</b>.
      This port of NuttX to the Opendous Micropendous 3 board. The Micropendous3 is
      may be populated with an AT90USB646, 647, 1286, or 1287.  I have only the AT90USB647
      version for testing.  This version have very limited memory resources: 64K of
      FLASH and 4K of SRAM.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PJRC Teensy++ 2.0 AT90USB1286</b>.
      This is a port of NuttX to the PJRC Teensy++ 2.0 board.
      This board was developed by <a href="http://pjrc.com/teensy/">PJRC</a>.
      The Teensy++ 2.0 is based on an Atmel AT90USB1286 MCU.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         The basic port was released in NuttX-6.5.  This basic port consists of
         a &quot;Hello, World!!&quot; example that demonstrates initialization of the OS,
         creation of a simple task, and serial console output as well as a somewhat
         simplified NuttShell (NSH) configuration (see the
         <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
      </p>
      <p>
         An SPI driver and a USB device driver exist for the AT90USB as well
         as a USB mass storage configureation.  However, this configuration is not
         fully debugged as of the NuttX-6.5 release.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><b>AVR-Specific Issues</b>.
      The basic AVR port is solid and biggest issue for using AVR is its tiny SRAM memory and its Harvard architecture.
      Because of the Harvard architecture, constant data that resides to flash is inaccessible using &quot;normal&quot; memory reads and writes (only SRAM data can be accessed &quot;normally&quot;).
      Special AVR instructions are available for accessing data in FLASH, but these have not been integrated into the normal, general purpose OS.
    </p>
    <p>
      Most NuttX test applications are console-oriented with lots of strings used for printf and debug output.
      These strings are all stored in SRAM now due to these data accessing issues and even the smallest console-oriented applications can quickly fill a 4-8K memory.
      So, in order for the AVR port to be useful, one of two things would need to be done:
    </p>
    <ol>
      <li>
        Don't use console applications that required lots of strings.
        The basic AVR port is solid and your typical deeply embedded application should work fine.
        Or,
      </li>
      <li>
        Create a special version of printf that knows how to access strings that reside in FLASH (or EEPROM).
      </li>
    </ol>
</tr>
<tr>
  <td><br></td>
  <td>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS with Windows native toolchain, or 4) Native Windows. 
        All testing, however, has been performed using the NuttX DIY toolchain for Linux  or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
        As a result, that toolchain is recommended.
      </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><br></td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="atmelavr32"><b>Atmel AVR32</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>AV32DEV1</b>.
      This port uses the www.mcuzone.com AVRDEV1 board based on the Atmel AT32UC3B0256 MCU.
      This port requires a special GNU avr32 toolchain available from atmel.com website.
      This is a windows native toolchain and so can be used only under Cygwin on Windows.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         This port is has completed all basic development, but there is more that needs to be done.
         All code is complete for the basic NuttX port including header files for all AT32UC3* peripherals.
         The untested AVR32 code was present in the 5.12 release of NuttX.
         Since then, the basic RTOS port has solidified:
      </p>
      <ul>
        <li>
          The port successfully passes the NuttX OS test (apps/examples/ostest).
        </li>
        <li>
          A NuttShell (NSH) configuration is in place (see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
          Testing of that configuration has been postponed (because it got bumped by the Olimex LPC1766-STK port).
          Current Status: I think I have a hardware problem with my serial port setup.
          There is a good chance that the NSH port is complete and functional, but I am not yet able to demonstrate that.
          At present, I get nothing coming in the serial RXD line (probably because the pins are configured wrong or I have the MAX232 connected wrong).
        </li>
      </ul>
      <p>
        The basic, port (including the verified apps/examples/ostest configuration) 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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="m68hcs12"><b>Freescale M68HCS12</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>MC9S12NE64</b>.
      Support for the MC9S12NE64 MCU and two boards are included:
    </p>
    <ul>
      <li>
        The Freescale DEMO9S12NE64 Evaluation Board, and
      </li>
      <li>
        The Future Electronics Group NE64 /PoE Badge board.
      </li>
    </ul>
    <p>
      Both use a GNU arm-nuttx-elf toolchain* under Linux or Cygwin.
      The NuttX <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> provides a properly patched GCC 3.4.4 toolchain that is highly optimized for the m9s12x family.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         Coding is complete for the MC9S12NE64 and for the NE64 Badge board.
         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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="8052"><b>Intel 8052 Microcontroller</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PJRC 87C52 Development Board</b>.
      This port uses the <a href="http://www.pjrc.com/">PJRC</a> 87C52 development system
      and the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is complete but not stable with timer interrupts enabled.
        There seems to be some issue when the stack pointer enters into the indirect IRAM
        address space during interrupt handling.
        This architecture has not been built in some time will likely have some compilation
        problems because of SDCC compiler differences.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="80x86"><b>Intel 80x86</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>QEMU/Bifferboard i486</b>.
      This port uses the <a href="http://wiki.qemu.org/Main_Page">QEMU</a> i486 and the native
      Linux, Cywgin, MinGW the GCC toolchain under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         The basic port was code-complete in NuttX-5.19 and verifed in NuttX-6.0.
         The port was verified using the OS and NuttShell (NSH) examples under QEMU.
         The port is reported to be functional on the <a href="http://bifferos.bizhat.com">Bifferboard</a> as well.
         This is a great, stable starting point for anyone interest in fleshing out the x86 port!
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>RGMP</b>.
      RGMP stands for RTOS and GPOS on Multi-Processor.
      RGMP is a project for  running GPOS and RTOS simultaneously on multi-processor platforms
      You can port your favorite RTOS to RGMP together with an unmodified Linux to form a hybrid operating system.
      This makes your application able to use both RTOS and GPOS features.
    </p>
    <p>
      See the <a href="http://rgmp.sourceforge.net/wiki/index.php/Main_Page">RGMP Wiki</a> for further information about RGMP.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         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!
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="pic32mips"><b>MicroChip PIC32 (MIPS)</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><b>PIC32MX250F128D</b>.
      A port is in progress from the DTX1-4000L &quot;Mirtoo&quot; module from <a href="http://www.dimitech.com/" >Dimitech</a>.
      This module uses MicroChip PIC32MX250F128D and the Dimitech DTX1-4000L EV-kit1 V2.
      See the <a href="http://www.dimitech.com/">Dimitech</a> website for further information.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The basic port is code complete.
        Two configurations are available:
        (1) An OS test configuration and a (2) configuration that support the NuttShell (NSH).
        The OS test configuration is fully functional and proves that we have a basically healthy NuttX port to the Mirtoo.
        The NSH configuration includes support for a serial console and for the SST25 serial FLASH and the PGA117 amplifier/multiplexer on board the module.
        The NSH configuration is set up to use the NuttX wear-leveling FLASH file system (NXFFS).
        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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
   <p><b>PIC32MX460F512L</b>.  There one two board ports using this chip:</p>
   <ul>
    <li><b>PIC32MX Board from PCB Logic Design Co</b>.
      This port is for the PIC32MX board from PCB Logic Design Co. and used the PIC32MX460F512L.
      The board is a very simple -- little more than a carrier for the PIC32 MCU plus voltage regulation, debug interface, and an OTG connector.
    </li>
    <p>
      <b>STATUS:</b>
      The basic port is code complete and fully verified in NuttX 6.13.
      Available configurations include the OS test and the NuttShell (NSH - see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
    </p>
    <li><b>UBW32 Board from Sparkfun</b>
      This is the port to the Sparkfun UBW32 board.
      This port uses the <a href="http://www.sparkfun.com/products/8971">original v2.5</a> board which is based on the MicroChip PIC32MX460F512L.
      This older version has been replaced with this <a href="http://www.sparkfun.com/products/9713">newer board</a>.
      See also the <a href="http://www.schmalzhaus.com/UBW32/">UBW32</a> web site.
    </li>
    <p>
      <b>STATUS:</b>
      The basic port is code complete and fully verified in NuttX 6.18.
      Available configurations include the OS test and 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.
    </p>
  </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PIC32MX440F512H</b>.
        This port uses the &quot;Advanced USB Storage Demo Board,&quot; Model DB-DP11215, from <a href="http://www.sureelectronics.net">Sure Electronics</a>.
        This board features the MicroChip PIC32MX440F512H.
        See the <a href="http://www.sureelectronics.net/goods.php?id=1168">Sure website</a> for further information about the DB-DP11215 board.
        (I believe that that the DB-DP11215 may be obsoleted now but replaced with the very similar, DB-DP11212.
        The DB-DP11212 board differs, I believe, only in its serial port configuration.)
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       This NuttX port is code complete and has considerable test testing.
       The port for this board was completed in NuttX 6.11, but still required a few bug fixes before it will be ready for prime time.
       The fully verified port first appeared in NuttX 6.13.
       Available configurations include the OS test and the NuttShell (NSH - see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
       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.
       </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PIC32MX795F512L</b>.
        There one two board ports using this chip:
    </p>
    <ul>
      <li><b>Microchip PIC32 Ethernet Starter Kit</b>.
         This port uses the Microchip PIC32 Ethernet Starter Kit (DM320004) with the Expansion I/O board.
         See the <a href="http://ww.microchip.com">Microchip website</a> for further information.
      </li>
      <p>
       <b>STATUS:</b>
         This port was started and then shelved for some time until I received the Expansion I/O board.
         The basic Starter Kit (even with the Multimedia Expansion Board, MEB, DM320005)) has no serial port and most NuttX test configurations depend heavily on console output.
      </p>
      <p>
         Verified configurations for the OS test and 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.
         Stay tuned for updates.
      </p>
     <li><b>Mikroelektronika PIC32MX7 Mulitmedia Board (MMB)</b>.
        A port has been completed for the  Mikroelektronika PIC32MX7 Multimedia Board (MMB).
        See http://www.mikroe.com/ for further information about this board.
      </li>
      <p>
       <b>STATUS:</b>
         Two verified configurations are available:
         (1) The basic OS test configuration that verfies the correctness port of NuttX, and (2) an extensive <a href="NuttShell.html">NuttShell (NSH)</a> configuration.
         The NSH configuration includes:
         (1) Full network support,
         (2) Verified SPI driver,
         (3) SPI-based SD Card support,
         (4) USB device support (including configuration options for the USB mass storage device and the CDC/ACM serial class), and
         (5) Support for the MIO873QT2 LCD on the PIC32MX7 MMB.
       </p>
       </p>
         The PIC32MX7 MMB's touchscreen is connected directly to the MCU via ADC pins.
         A touchscreen driver has been developed using the PIC32's ADC capabilities and can be enabled in the NSH configuration.
         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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Development Environment:</b>
      These ports uses either:
    </p>
    <ol>
      <li>
        The <i>LITE</i> version of the PIC32MX toolchain available
        for download from the <a href="http://www.microchip.com">MicroChip</a> website, or
      </li>
      <li>
        The Pinguino MIPS ELF toolchain avaiable from the Pinquino <a href="http://code.google.com/p/pinguino32/downloads/list">website</a>.
      </li>
    </ol>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><br></td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="superh"><b>Renesas/Hitachi SuperH</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>SH-1 SH7032</b>.
      This port uses the Hitachi SH-1 Low-Cost Evaluation Board (SH1_LCEVB1), US7032EVB,
      with a GNU ELF toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is available as of release 0.3.18 of NuttX.  The port is basically complete
        and many examples run correctly.  However, there are remaining instabilities that
        make the port un-usable.  The nature of these is not understood; the behavior is
        that certain SH-1 instructions stop working as advertised.  This could be a silicon
        problem, some pipeline issue that is not handled properly by the gcc 3.4.5 toolchain
        (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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="m16c"><b>Renesas M16C/26</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Renesas M16C/26 Microncontroller</b>.
      This port uses the Renesas SKP16C26 Starter kit and the GNU M32C toolchain. 
      The development environment is either Linux or Cygwin under WinXP.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Initial source files released in nuttx-0.4.2.
        At this point, the port has not been integrated;    the target cannot be built
        because the GNU <code>m16c-nuttx-elf-ld</code> link fails with  the following message:
      </p>
      <ul>
      <code>m32c-nuttx-elf-ld: BFD (GNU Binutils) 2.19 assertion fail /home/Owner/projects/nuttx/buildroot/toolchain_build_m32c/binutils-2.19/bfd/elf32-m32c.c:482</code>
      </ul>
      <p>Where the reference line is:</p>
      <ul><pre>
/* If the symbol is out of range for a 16-bit address,
   we must have allocated a plt entry.  */
BFD_ASSERT (*plt_offset != (bfd_vma) -1);
</pre></ul>
      <p>
        No workaround is known at this time.  This is a show stopper for M16C for
        the time being.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz16f"><b>Zilog Z16F</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog z16f Microncontroller</b>.
      This port use the Zilog z16f2800100zcog development kit and the Zilog
      ZDS-II Windows command line tools.
      The development environment is either Windows native or Cygwin under Windows.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The initial release of support for the z16f was made available in NuttX version 0.3.7.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogez80acclaim"><b>Zilog eZ80 Acclaim!</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog eZ80Acclaim! Microncontroller</b>.
      There are two eZ80Acclaim! ports:
    </p>
    <ul>
      <li>One uses the ZiLOG ez80f0910200kitg development kit, and
      <li>The other uses the ZiLOG ez80f0910200zcog-d development kit.
    </ul>
    <p>
      Both boards are based on the eZ80F091 part and both use the Zilog ZDS-II
      Windows command line tools.
      The development environment is either Windows native or Cygwin under Windows.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Integration and testing of NuttX on the  ZiLOG ez80f0910200zcog-d is complete.
        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.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz8encore"><b>Zilog Z8Encore!</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog Z8Encore! Microncontroller</b>.
      This port uses the either:
    </p>
    <ul>
      <li>Zilog z8encore000zco development kit, Z8F6403 part, or</li>
      <li>Zilog z8f64200100kit development kit, Z8F6423 part</li>
    </ul>
    <p>
      and the Zilog ZDS-II Windows command line tools.
      The development environment is either Windows native or Cygwin under Windows.
    </p>
    <ul>
       <p>
         <b>STATUS:</b>
         This release has been verified only on the ZiLOG ZDS-II Z8Encore! chip simulation
         as of nuttx-0.3.9.
       </p>
     <ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz180"><b>Zilog Z180</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>P112</b>.
      The P112 is a hobbyist single board computer based on a 16MHz Z80182 with up to 1MB of memory, serial,
parallel and diskette IO, and realtime clock, in a 3.5-inch drive form factor..
      The P112 computer originated as a commercial product of &quot;D-X Designs Pty Ltd&quot[ of Australia.
    </p>
    </p>
      Dave Brooks was successfully funded through Kickstarter for and another run of P112 boards in November of 2012.
      In addition Terry Gulczynski makes additional P112 derivative hobbyist home brew computers.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       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 first quarter of 2013.
       So it will be some time before this port is verified on hardware.
      </p>
    <ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz80"><b>Zilog Z80</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Z80 Instruction Set Simulator</b>.
      This port uses the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain
      under Linux or Cygwin (verified using version 2.6.0).
      This port has been verified using only a Z80 instruction simulator.
      That simulator can be found in the NuttX SVN
      <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/sims/z80sim/">here</a>.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is complete and stable to the extent that it can be tested
        using an instruction set simulator.
      </p>
    <ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>XTRS: TRS-80 Model I/III/4/4P Emulator for Unix</b>.
      A very similar Z80 port is available for <a href="http://www.tim-mann.org/xtrs.html">XTRS</a>,
      the TRS-80 Model I/III/4/4P Emulator for Unix.
      That port also uses the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain
      under Linux or Cygwin (verified using version 2.6.0).
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       Basically the same as for the Z80 instruction set simulator.
       This port was contributed by Jacques Pelletier.
      </p>
    <ul>
  </td>
</tr>
</table></center>

<blockquote>* A highly modified <a href="http://buildroot.uclibc.org/">buildroot</a>
is available that may be used to build a NuttX-compatible ELF toolchain under
Linux or Cygwin.  Configurations are available in that buildroot to support ARM, Cortex-M3,
avr, m68k, m68hc11, m68hc12, m9s12, blackfin, m32c, h8, and SuperH ports.</blockquote>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="environments"><h1>Development Environments</h1></a>
  </td>
  </tr>
</table>

<center><table width="90%">
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Linux + GNU <code>make</code> + GCC/binutils for Linux</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      The is the most natural development environment for NuttX.
      Any version of the GCC/binutils toolchain may be used.
      There is a  highly modified <a href="http://buildroot.uclibc.org/">buildroot</a>
      available for download from the
      <a href="http://sourceforge.net/projects/nuttx/files/">NuttX SourceForge</a>
      page.
      This download may be used to build a NuttX-compatible ELF toolchain under Linux or Cygwin.
      That toolchain will support ARM, m68k, m68hc11, m68hc12, and SuperH ports.
      The buildroot SVN may be accessed in the 
      <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/buildroot/">NuttX SVN</a>.
    </p>
   </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Linux + GNU <code>make</code> + SDCC for Linux</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Also very usable is the Linux environment using the 
      <a href="http://sdcc.sourceforge.net/">SDCC</a> compiler.
      The SDCC compiler provides support for the 8051/2, z80, hc08, and other microcontrollers.
      The SDCC-based logic is less well exercised and you will likely find some compilation
      issues if you use parts of NuttX with SDCC that have not been well-tested.
    </p>
   </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows with Cygwin + GNU <code>make</code> + GCC/binutils (custom built under Cygwin)</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      This combination works well too.
      It works just as well as the native Linux environment except that compilation and build times are a little longer.
      The custom NuttX <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> referenced above may be build in the Cygwin environment as well.
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows with Cygwin + GNU <code>make</code> + SDCC (custom built under Cygwin)</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
       I have never tried this combination, but it would probably work just fine.
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows with Cygwin + GNU <code>make</code> + Windows Native Toolchain</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      This is a tougher environment.
      In this case, the Windows native toolchain is unaware of the
      Cygwin <i>sandbox</i> and, instead, operates in the native Windows environment.
      The primary difficulties with this are:
    </p>
    <ul>
      <li>
        <b>Paths</b>.
        Full paths for the native toolchain must follow Windows standards.
        For example, the path <code>/home/my\ name/nuttx/include</code> my have to be
        converted to something like <code>'C:\cygwin\home\my name\nuttx\include'</code>
        to be usable by the toolchain.
      </li>
      <p>
        Fortunately, this conversion is done simply using the <code>cygpath</code> utility.
      </p>
      <li>
        <b>Symbolic Links</b>
        NuttX depends on symbolic links to install platform-specific directories in the build system.
        On Linux, true symbolic links are used.
        On Cygwin, emulated symbolic links are used.
        Unfortunately, for native Windows applications that operate outside of the
        Cygwin <i>sandbox</i>, these symbolic links cannot be used.
      </li>
      <p>
        The NuttX make system works around this limitation by copying the platform
        specific directories in place.
        These copied directories make work a little more complex, but otherwise work well.
      </p>
      <p><small>
        NOTE: In this environment, it should be possible to use the NTFS <code>mklink</code> command to create links.
        This should only require a minor modification to the build scripts (see <code>tools/copydir.sh</code> script).
      </small></p>
      <li>
        <b>Dependencies</b>
        NuttX uses the GCC compiler's <code>-M</code> option to generate make dependencies.  These
        dependencies are retained in files called <code>Make.deps</code> throughout the system.
        For compilers other than GCC, there is no support for making dependencies in this way.
        For Windows native GCC compilers, the generated dependencies are windows paths and not
        directly usable in the Cygwin make.  By default, dependencies are surpressed for these
        compilers as well.
      </li>
      <p><small>
        NOTE: dependencies are suppress by setting the make variable <code>MKDEPS</code> to point
        to the do-nothing dependency script, <code>tools/mknulldeps.sh</code>.
      </small></p>
    </ul>
    <p>
      <b>Supported Windows Native Toolchains</b>.
      At present, the following Windows native toolchains are in use:
      <ol>
        <li>GCC built for Windows (such as CodeSourcery, Atollic, devkitARM, etc.),</li>
        <li>SDCC built for Windows,</li>
        <li> the ZiLOG XDS-II toolchain for Z16F, z8Encore, and eZ80Acclaim parts.</li>
      </ol>
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Windows Native (<code>CMD.exe</code>) + GNUWin32 (including GNU <code>make</code>) + MinGW Host GCC compiler + Windows Native Toolchain</b>
  </td>
</tr>
  <td><br></td>
  <td>
    <p>
      Build support has been added to support building natively in a Windows console rather than in a POSIX-like environment.
    </p>
    <p>
      This build:
    </p>
    <ol>
      <li>Uses all Windows style paths</li>
      <li>Uses primarily Windows batch commands from cmd.exe, with</li>
      <li>A few extensions from GNUWin32</li>
    </ol>
    <p>
      This capability first appeared in NuttX-6.24 and should still be considered a work in progress because: (1) it has not been verfied on all targets and tools, and (2) still lacks some of the creature-comforts of the more mature environments.
      The windows native build logic initiatiated if <code>CONFIG_WINDOWS_NATIVE=y</code> is defined in the NuttX configuration file:
    </p>
    <p>
      At present, this build environment also requires:
    </p>
    <ul>
      <li>
        <b>Windows Console</b>.
        The build must be performed in a Windows console window.
        This may be using the standard <code>CMD.exe</code> terminal that comes with Windows.
        I prefer the ConEmu terminal which can be downloaded from:
        http://code.google.com/p/conemu-maximus5/
      </li>
      <li>
        <b>GNUWin32</b>.
        The build still relies on some Unix-like commands.
        I usethe GNUWin32 tools that can be downloaded from http://gnuwin32.sourceforge.net/.
        See the top-level <code>nuttx/README.txt</code> file for some download, build, and installation notes.
      </li>
      <li>
        <b>MinGW-GCC</b>.
        MinGW-GCC is used to compiler the C tools in the <code>nuttx/tools</code> directory that are neede by the build.
        MinGW-GCC can be downloaded from http://www.mingw.org/.
        If you are using GNUWin32, then it is recommendedthe you not install the optional MSYS components as there may be conflicts.
      </li>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Wine + GNU <code>make</code> + Windows Native Toolchain</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      I've never tried this one, but I off the following reported by an ez80 user using the ZiLOG ZDS-II Windows-native toolchain:
    </p>
    <blockquote>
      <p>
         &quot;I've installed ZDS-II 5.1.1 (IDE for ez80-based boards) on wine (windows emulator for UNIX) and to my surprise, not many changes were needed to make SVN snapshot of NuttX buildable...
         I've tried nsh profile and build process completed successfully.
         One remark is necessary: NuttX makefiles for ez80 are referencing <code>cygpath</code> utility.
         Wine provides similar thing called <code>winepath</code> which is compatible and offers compatible syntax.
         To use that, <code>winepath</code> (which itself is a shell script) has to be copied as <code>cygpath</code> somewhere in <code>$PATH</code>, and edited as in following patch:
       </p>
       <ul><pre>
# diff -u `which winepath` `which cygpath`
--- /usr/bin/winepath 2011-05-02 16:00:40.000000000 +0200
+++ /usr/bin/cygpath 2011-06-22 20:57:27.199351255 +0200
@@ -20,7 +20,7 @@
#

# determine the app Winelib library name
-appname=`basename "$0" .exe`.exe
+appname=winepath.exe

# first try explicit WINELOADER
if [ -x "$WINELOADER" ]; then exec "$WINELOADER" "$appname" "$@"; fi
</pre></ul>
      <p>
        &quot;Better solution would be replacing all <code>cygpath</code> references in  <code>Makefiles </code> with  <code>$(CONVPATH)</code> (or  <code>${CONVPATH}</code> in shell scripts) and setting <code>CONVPATH</code> to  <code>cygpath</code> or  <code>winepath</code> regarding to currently used environment.
      </p>
    </blockquote>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Other Environments?</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Environment Dependencies</b>.
      The primary environmental dependency of NuttX are (1) GNU make,
      (2) bash scripting, and (3) Linux utilities (such as cat, sed, etc.).
      If you have other platforms that support GNU make or make
      utilities that are compatible with GNU make, then it is very
      likely that NuttX would work in that environment as well (with some
      porting effort). If GNU make is not supported, then some significant
      modification of the Make system would be required.
    </p>
    <p>
      <b>MSYS</b>.
      I have not used MSYS but what I gather from talking with NuttX users is that MSYS can be used as an alternative to Cygwin in any of the above Cygwin environments.
      This is not surprising since MSYS is based on an older version of Cygwin (cygwin-1.3).
      MSYS has been modified, however, to interoperate in the Windows environment better than Cygwin and that may be of value to some users.
    </p>
    <p>
      MSYS, however, cannot be used with the native Windows NuttX build because it will invoke the MSYS bash shell instead of the <code>CMD.exe</code> shell.
      Use GNUWin32 in the native Windows build envionment.
    </p>
  </td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="footprint"><h1>Memory Footprint</h1></a>
  </td>
  </tr>
</table>

<ul>
<p><b>C5471 (ARM7)</b>
  The build for this ARM7 target that includes most of the OS features and
  a broad range of OS tests.  The size of this executable as given by the
  Linux <tt>size</tt> command is (3/9/07):
</p>
<pre>
   text    data     bss     dec     hex filename
  53272     428    3568   57268    dfb4 nuttx
</pre>
<p><b>DM320 (ARM9)</b>
  This build for the ARM9 target includes a significant subset of OS
  features, a filesystem, Ethernet driver, full TCP/IP, UDP and (minimal)
  ICMP stacks (via uIP) and a small network test application: (11/8/07,
  configuration netconfig, apps/examples/nettest)
</p>
<pre>
   text    data     bss     dec     hex filename
  49472     296    3972   53740    d1ec nuttx
</pre>
<p>
  Another build for the ARM9 target includes a minimal OS feature
  set, Ethernet driver, full TCP/IP and (minimal) ICMP stacks, and
  a small webserver: (11/20/07, configuration uipconfig, apps/examples/uip)
</p>
<pre>
   text    data     bss     dec     hex filename
  52040      72    4148   56260    dbc4 nuttx
</pre>
<p><b>87C52</b>
  A reduced functionality OS test for the 8052 target requires only
  about 18-19K:
</p>
<pre>
Stack starts at: 0x21 (sp set to 0x20) with 223 bytes available.

Other memory:
   Name             Start    End      Size     Max
   ---------------- -------- -------- -------- --------
   PAGED EXT. RAM                         0      256
   EXTERNAL RAM     0x0100   0x02fd     510     7936
   ROM/EPROM/FLASH  0x2100   0x6e55   19798    24384
</pre>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="licensing"><h1>Licensing</h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
  NuttX is available under the highly permissive
  <a href="http://en.wikipedia.org/wiki/BSD_license">BSD license</a>.
  Other than some fine print that you agree to respect the copyright
  you should feel absolutely free to use NuttX in any environment and
  without any concern for jeopardizing any proprietary software that
  you may link with it.
</p>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="history"><h1>Release History</h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
   ChangeLog snapshots associated with the previous, current, and future release are available below.
</p>
</ul>

<center><table width ="80%">
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="ChangeLog.txt">Change logs for previous NuttX releases</a><br>
   </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="#currentrelease">ChangeLog for the current NuttX releases</a><br>
   </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="#pendingchanges">Unreleased changes</a>
   </td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="currentrelease">ChangeLog for the Current Release</a>
  </td>
  </tr>
</table>

<ul><pre>
nuttx-6.25 2013-02-01 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * graphics/: Adds 5x8 monospace font. This tiny font is useful for graph
      labels and for small bitmapped display.  Contributed by Petteri
      Aimonen.
    * configs/stm3220g-eval/nxwm:  Converted to use the kconfig-frontends
      configuration tool.
    * configs/sim/nxwm:  Converted to use the kconfig-frontends configuration
      tool.
    * include/pthread.h:  In sys/prctl.h because it is needed by
      pthread_[set|get]name_np()
    * tools/kconfig.bat:  Kludge to run kconfig-frontends from a DOS shell.
    * sched/sig_timedwait.c:  Should always move the time up to the next
      largest number of system ticks.  The logic was rounding.  Noted by
      Petteri Aimonen.
    * arch/arm/src/up_head.S:  Fix backward conditional compilation.  NOTE
      there is a issue of ARM9 systems with low vectors and large memories
      that will have to be addressed in the future.
    * libc/misc/lib_kbdencode.c and lib_kbddecode.c:  Add logic to marshal
      and serialized &quot;out-of-band&quot; keyboard commands intermixed with normal
      ASCII data (not yet hooked into anything).
    * drivers/usbhost/usbhost_hidkbd.c:  If CONFIG_HIDKBD_ENCODED is
      defined, this driver will now use libc/misc/lib_kbdencode.c to
      encode special function keys.
    * configs/olimex-lpc1766stk/hidkbd:  This configuration has been
      converted to use the kconfig-frontends configuration tool.
    * drivers/lcd/ug-2864hsweg01.c and include/nuttx/lcd/ug-2864hsweg01.h:
      Driver for UG-2864HSWEG01 OLED contributed by Darcy Gong.
    * configs/stm32f4discovery/src/up_ug2864hsweg01.c: Support for the
      UG-2864HSWEG01 OLED for the STM32F4Discovery board.
    * drivers/usbhost/usbhost_hidkbd.c:  Correct a logic error in how
      tasks waiting for read data are awakened.
    * libc/misc/lib_kbdencode.c and lib_kbddecode.c:  Now handles keypress
      events too.  However, the USB HID keyboard driver has not yet been
      updated to detect key release events.  That is kind of tricky in
      the USB HID keyboard report data.
    * configs/mcu123-214x/nsh:  Converted to use the kconfig-frontends
      configuration tool.
    * configs/zp214xpa:  Add basic support for the The0.net ZP213x/4xPA
      board (with the LPC2148 and the UG_2864AMBAG01).
    * configs/sim/nxlines:  Add an nxlines configuration for the
      simulator.
    * configs/zp214xpa/nxlines:  Add an nxlines configuration for the
      ZP213x/4xPA (with the LPC2148 and the UG_2864AMBAG01).  Working
      as of 2012-12-30.
    * configs/olimex-lpc1766stk/wlan:  Remove non-functional
      configuration.
    * configs/stm32f4discovery/src and nuttx/drivers/lcd/ug-2864hsweg01.c:
      Updates and correctinos for the UG-2864HSWEG01 from Darcy Gong.
    * configs/lm326965-ek:  All configurations converted to use the
      kconfig-frontends configuration tool.
    * configs/Kconfig: NSH_MMCSDSPIPORTNO should depend on MMCSD_SPI,
      not just SPI (from Jose Pablo Carballo).
    * arch/arm/src/arm/Kconfig and armv7m/Kconfig:  Add an option for
      buildroot toolchains:  They may be EABI or OABI.
    * include/nuttx/progmem and arch/arm/src/stm32/stm32_flash.c:
      Fix a counting bug plus change interface to use either relative
      or absolute FLASH addressing (from Freddie Chopin).
    * libc/misc/Make.defs:  Fix error in conditional for KBD CODEC.
    * libc/Kconfig and configs/*/defconfig (several):  The default
      setting should be CONFIG_LIB_KBDCODEC=n
    * tools/configure.c:  configure.c can be used to build a work-alike
      program as a replacement for configure.sh.  This work-alike
      program would be used in environments that do not support Bash
      scripting (such as the Windows native environment).
    * tools/configure.bat: configure.bat is a small Windows batch
      file that can be used as a replacement for configure.sh in a
      Windows native environment.  configure.bat is actually just a
      thin layer that executes configure.exe if it is available. If
      configure.exe is not available, then configure.bat will attempt
      to build it first.
    * arch/arm/src/lpc17xx/lpc17_syscon.h:  Correct some typos in bit
      definitions (from Rommel Marcelo).
    * libc/string/lib_strndup.c: strndup() should use strnlen(), not
      strlen(), to determine the size of the string.
    * sched/os_bringup.c:  Remove support for CONFIG_BUILTIN_APP_START.
      This is not really a useful feature and creates a violation of the
      OS layered architecture.
    * include/unistd.h, arch/arch/src/*:  Implement a simple vfork().
      On initial checkin, this API is available only for ARM platforms.
    * binfmt/binfmt_exec.c: exec() now sets the priority of the new task
      to the same priority as the current task (instead of the arbirtrary
      value of 50).
    * libc/unisted/lib_execv.c and lib_execl.c:  New, somewhat flawed,
      implementations of execv() and execl().
    * tools/cfgdefine.c:  Strips quotes from CONFIG_EXECFUNCS_SYMTAB
      value.
    * arch/arm/include/lm3s/chip.h:  Move chip definitions into
      public include area for compatibility with other architectures.
    * arch/arm/src/lm3s/chip:  Move register definition header files
      into a new chip/ sub-directory.
    * arch/arm/src/lm3s/lm3s_internal.h:  Broke up into several
      smaller header files.
    * arch/arm/src/lm:  Rename the arch/arm/src/lm3s directory to
      arch/arm/src/lm so that is can support other members of the
      Stellaris family.
    * libc/spawn:  Add file action interfaces needed by posix_spawn().
    * sched/clock_time2ticks.c:  Another case where time was being
      rounded down instead of up (from Mike Smith).
    * libc/spawn:  Implementation of posix_spawn() is complete but
      untested and undocumented.
    * drivers/usbdev/pl2303.c:  Fix typols in the PL2303 driver
      (from Max Holtzberg).
    * configs/stm32f4discovery/posix_spawn:  Added a configuration
      that can be used for testing posix_spawn().
    * arch/arm/src/stm32: Bring F1 support for general DMA and serial
      DMA in paricular up to parity with F2/F4 (from Mike Smith).
    * libc/stdio/lib_libfread.c:  Correct some error handling when
      lib_fread() was passed a bad stream.  Needed to move the
      releasing of a semaphore inside of some conditional logic
      (cosmetic).
    * include/nuttx/sched.h, sched/task_setup.c, and sched/task_exithook.c:
      Add support for remembering the parent task and sending
      SIGCHLD to the parent when the task exists.
    * sched/task_exithook.c:  Fixed a *critical* bug.  Here is
      the scenario: (1) sched_lock() is called increments the lockcount
      on the current TCB (i.e., the one at the head of the ready to run
      list), (2) sched_mergepending is called which may change the task
      at the head of the ready-to-run list, then (3) sched_unlock() is called
      which decrements the lockcount on the wrong TCB.  The failure case
      that I saw was that pre-emption got disabled in the IDLE thread,
      locking up the whole system.
    * sched/sched_waitpid.c:  Use SIGCHLD instead of a semaphore.  This
      is a much more spec-compliant implementation.  However, there are
      some issues with overruning signals because NuttX does not support
      queueing of signals (POSIX does not require it).  I think it may
      need to.
    * sched/sched_waitid.c and sched_wait.c:  Add support for waitid()
      and wait().  See issues with waitpid() above.
    * include/nuttx/fs/fs.h and fs/fs_files.c:  Add a dup() method to
      the struct mountpt_operations.  When dup'ing a file that resides
      on a mounted volume, let the file system's dup() method do the
      work.
    * fs/romfs/fs_romfs.c: Implemented the dup() method for the ROMFS
      file system.
    * fs/fat/fs_fat32.c, fs/nxffs/nxffs_initialize, and
      fs/nfs/nfs_vfsops.c:  Add hooks for dup() method (not yet
      implemented).
    * fs/romfs:  Remove the rf_open flag.  It looks good, but actually
      does nothing.
    * fs/fat:  Remove the ff_open flag.  Same story as for the ROMFS
      rf_open flag.
    * fs/fat/fs_fat32.c, fs/nxffs/nxffs_initialize, and
      fs/nfs/nfs_vfsops.c:  Completed implementation of the dup() methods.
      There is still no good test available.
    * sched/sig_timedwait.c:  sigtimedwait() would return a bad signal
      number if the signal was already pending when the function was
      called.
    * configs/ubw32/scripts:  All common linker scripts moved to this
      scripts sub-directory
    * configs/ubw32/ostest:  Configuration configured to use the
      kconfig-frontends tools.
    * arch/mips/src/mips32/up_vfork.c, up_vfork.h, and vfork.S:
      Implement vfork() for MIPS32 (no floating point support)
    * configs/ubw32/ostest: Enable the vfork() test.
    * fs/binfs:  Move apps/builtin/binfs.c to fs/binfs/fs_binfs.c
      CONFIG_APPS_BINDIR rename CONFIG_FS_BINFS
    * include/nuttx/binfmt/builtin.h:  Some of the content of
      apps/include/apps.h moved to include/nuttx/binfmt/builtin.h
    * binfmt/libbuiltin/libbuiltin_utils.c:  Move builtin
      utility functions from apps/builtin/exec_builtins.c to
      binfmt/libbuiltin/libbuiltin_utils.c
    * binfmt/builtin.c and binfmt/libbuiltin:  Add a binary &quot;loader&quot;
      that can be used to execute builtin programs from the BINFS
      file system.
    * configs/sim/nsh: Convert to use kconfig-frontends configuration
      tool.
    * binfmt/binfmt_schedunload.c:  Add logic based on SIGCHLD to
      automatically unload and clean-up after running a task that
      was loaded into memory.
    * binfmt/libbuiltin: Extensions from Mike Smith
    * sched/task_reparent.c:  Add internal interface to change the
      parent task.
    * sched/task_posixspawn():  Move libc/spawn/lib_ps.c to
      sched/task_posixspawn() now it requires internal, reparenting
      interfaces
    * include/nuttx/spawn():  Move libc/spawn.h to include/nuttx/spawn.h
    * arch/arm/include/lpc17xx/chip.h, irq178x.h:  Integrate Marcelo
      Rommel's LPC1788 definitions into the base LPC17xx.
    * configs/olimex-lpc1766stk/nsh:  Convert configuration to use
      the kconfig-frontends tools.
    * sched/task_reparent.c:  Simplify reparenting interface.
    * arch/arm/src/[many]: More LPC1788 definitions from Rommel
      Marcelo incorporated.
    * configs/open1788:  Board configuration for the Wave Share
      Open1788 board.  Still fragmentary (contributed by Rommel
      Marcelo, adapted to use kconfig-frontends.
    * net/send():  Add logic to work around delayed ACKs by splitting
      packets (contributed by Yan T.).
    * net/recvfrom():  Fix a bug.  When the host closes a connection
      (gracefully).  recv[from]() returned success and the closure
      was never detected.  Hmmm.. I don't know why the network monitor
      did not catch this event.  This is an important bug fix.
    * net/recvfrom():  Fix a introduced with the last bugfix.  If
      the peer does an orderly closure of the socket, report 0 not
      -ENOTCONN
    * configs/lm3s6965-ek/README.txt and tools/:  Add an OpenOCD
      configuration for the LM3S (from Jose Pablo Carballo).
    * nuttx/lcd/hd4478ou.h and configs/pcblogic-pic32mx/src/up_lcd1602:
      Start of support of LCD1602 alphanumeric LCD.  I need a few
      more parts before I can finish integrating this one.
    * arch/arm/src/*/chip.h and arch/arm/include/*/chip.h:  Move all
      priority ranges from the src to the include chip.h header file.
    * arch/arm/include/armv7-m/irq.h:  Add inline functions to enable
      and disable interrupts via the BASEPRI register.
    * arch/arm/Kconfig:  Add new option CONFIG_ARM7VM_USEBASEI
    * arch/arm/src/*/*_irq.c:  Set the priority of the SVCALL exception
      to the highest possible value.
    * arch/armv7-m/up_hardfault.c:  Fail if a hardfault occurs
      while CONFIG_ARM7VM_USEBASEPRI=y.
    * arch/arm/src/stm32/stm32_serial.c:  Add support for USART
      single wire mode (Contributed by the PX4 team).
    * sched/: Implement support for retaining child task status after
      the child task exists.  This is behavior required by POSIX.
      But in NuttX is only enabled with CONFIG_SCHED_HAVE_PARENT and
      CONFIG_SCHED_CHILD_STATUS
    * Add support for keyboard encode to the keypad test (from
      Denis Carikli).
    * configs/olimex-lpc1766stk/nettest:  Configuration converted to
      use the kconfig-frontends tools.
    * net/net_poll.c:  Split net_poll() to create psock_poll() too.
    * net/net_poll.c:  Fix poll/select issure reported by Qiang:
      poll_interrupt() must call net_lostconnection() when a
      loss of connection is reported.  Otherwise, the system will
      not know that the connection has been lost.
    * sched/group_create.c, group_join.c, and group_leave.c:  Add
      support for task groups.
    * sched/group_signal.c and task_exithook.c:  Send signal to all
      members for the parent task group.
    * include/nuttx/sched.h and sched/env_*.c:  Move environment
      variables into task group structure.
    * sched/: Lots of file changed.  Don't keep the parent task's
      task ID in the child task's TCB.  Instead, keep the parent
      task group IN the child task's task group.
    * fs/, sched/, include/nuttx/sched.h, and include/nutts/fs/fs.h:
      Move file data from the TCB to the task group structure.
    * libc/stdio/, sched/, include/nuttx/lib.h, and include/nutts/fs/fs.h:
      Move stream data from the TCB to the task group structure.
    * net/, sched/, and include/nuttx/net/net.h:  Move socket data
      from the TCB to the task group structure.
    * sched/task_starthook.c, sched/task_start.c, and include/nuttx/sched.h:
      Add a task start hook that will be called before the task main
      is started. This can be used to schedule C++ constructors to run
      automatically in the context of the new task.
    * binfmt/binfmt_execmodule: Execute constructors as a start hook.
    * sched/os_start.c: Fix ordering of group initialization.
    * configs/stm32f4discovery/usbnsh:  Add an NSH STM32F4Discovery
      configuration that uses USB CDC/ACM for the NSH console.
    * configs/stm32f4discovery/nsh: Converted to use the kconfig-frontends
      tools.
    * configs/*/src/up_userleds.c: Fix a error that was cloned into
      all STM32 user LED code.  The wrong definitions were being used
      to set LEDs on or off.
    * arch/*/common/up_internal.h and arch/*/common/up_initialize.c:
      Serial was driver was not being built if there is no console
      device.  Obviously, the serial driver may be needed even in
      this case.
    * arch/arm/src/stm32/stm32_serial.c: If there is a serial console,
      it would be ttyS0 and the others would be ttyS1-5.  If there
      is not serial console, was labeling them ttyS1-6; now labels them
      ttyS0-5.
    * fs/fs_syslog.c: Can't handle SYSLOG output to character device from
      the IDLE task (because it can't block). syslog_putc now returns EOF
      on failure and sets errno.  Fixed some errors in error handling.
    * libc/stdio/lib_syslogstream.c:  Checking of return value from
      syslog_putc was bogus.  Switching to EOF for all errors solves
      this.
    * arch/arm/src/lm/chip/lm4f_memorymap.h: More LM4F changes from
      Jose Pablo Carballo.
    * drivers/serial/serial.c, include/nuttx/serial/serial.h,
      drivers/usbdev/cdcacm.c, and drivers/pl2303.c: Add support for
      removable serial devices (like USB serial).  This support is enabled
      by CONFIG_SERIAL_REMOVABLE.
    * arch/*/src/*/Toolchain.defs: Change assignment so that we can
      override CROSSDEV with a make command line argument.
    * include/assert.h:  Mark assertion functions as non-returning.
    * arch/*/src/*/up_assert.h:  Mark _up_assert() as non-returning.
    * drivers/mtd/at25.c: When the AT25 device was not available the
      initialization did not fail like it should. From Petteri Aimonen.
    * fs/fat/fs_configfat.c:  Fix some errors in FAT formatting logic
      for large devices and for FAT32. From Petteri Aimonen.
    * fs/fat/fs_fat32util.c:  Fix an initialization error found by
      Petteri Aimonen.  freecount and next freecount initialization were
      reversed.
    * drivers/mmcsd/mmcsd_spi.c: Some SD cards will appear busy until
      switched to SPI mode for first time.  Having a pull-up resistor on
      MISO may avoid this problem, but this patch makes it work also
      without pull-up.  From Petteri Aimonen.
    * fs/fat/fs_fat32.c: Fix a compilation error when FAT_DMAMEMORY=y. 
      From Petteri Aimonen.
    * arch/arm/src/stm32/chip/stm32_spi.h: STM32F4 max SPI clock freq is
      37.5 MHz.  Patch from Petteri Aimonen.
    * arch/arm/src/stm32/stm32_spi.c: Fixes for SPI DMA work on the
      STM32F4. Includes untested additions for the F1 implementation as
      well.  From Petteri Aimonen.

apps-6.25 2013-02-01 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * Makefiles: Removed dependency of distclean on clean in most top-level
      files.  It makes sense for 'leaf' Makefiles to have this dependency,
      but it does not make sense for upper-level Makefiles.
    * apps/namedapp/: Renamed to builtins in preparation for another change.
    * .context:  Removed the .context kludge.  This caused lots of problems
      when changing configurations because there is no easy way to get the
      system to rebuild the context.  Now, the context will be rebuilt
      whenever there is a change in either .config or the Makefile.
    * apps/builtin/registry:  Updated new built-in registration logic to handle
      cases where (1) old apps/.config is used, and (2) applications ared
      removed, not just added.
    * apps/examples/nettest/Makefile:  Fix an error that crept in during
      some of the recent, massive build system changes.
    * apps/builtin/Makefile:  Need to have auto-generated header files
      in place early in the dependency generation phase to avoid warnings.
      It is not important if they are only stubbed out header files at
      this build phase.
    * apps/examples/hidbkd: Now supports decoding of encoded special keys
      if CONFIG_EXAMPLES_HIDKBD_ENCODED is defined.
    * apps/examples/hidbkd:  Add support for decoding key release events
      as well.  However, the USB HID keyboard drier has not yet been
      updated to detect key release events.  That is kind of tricky in
      the USB HID keyboard report data.
    * apps/examples/wlan: Remove non-functional example.
    * apps/examples/ostest/vfork.c:  Added a test of vfork().
    * apps/exampes/posix_spawn: Added a test of posix_spawn().
    * apps/examples/ostest:  Extend signal handler test to catch
      death-of-child signals (SIGCHLD).
    * apps/examples/ostest/waitpid.c:  Add a test for waitpid(), waitid(),
      and wait().
    * builtin/binfs.c:  Add hooks for dup() method (not implemented).
    * builtin/exec_builtin.c, nshlib/nsh_parse.c, and nshlib/nsh_builtin.c:
      NSH now supports re-direction of I/O to files (but still not from).
    * builtin/binfs.c:  Greatly simplified (it is going to need to be
      very lightweight).  Now supports open, close, and a new ioctl to recover
      the builtin filename.  The latter will be needed to support a binfs
      binfmt.
    * builtin/binfs.c:  Move apps/builtin/binfs.c to fs/binfs/fs_binfs.c
      CONFIG_APPS_BINDIR rename CONFIG_FS_BINFS
    * apps/include/builtin.h:  Some of the content of
      apps/include/apps.h moved to include/nuttx/binfmt/builtin.h.
      apps/include/apps.h renamed builtin.h
    * apps/builtin/exec_builtins.c:  Move builtin
      utility functions from apps/builtin/exec_builtins.c to
      binfmt/libbuiltin/libbuiltin_utils.c
    * apps/nshlib/nsh_mountcmds.c:  The block driver/source
      argument is now optional.  Many files systems do not need
      a source and it is really stupid to have to enter a bogus
      source parameter.
    * apps/nshlib/nsh_fileapp.c:  Add the ability to execute a file
      from a file system using posix_spawn().
    * apps/builtin/: Extensions from Mike Smith.
    * apps/examples/ftpd/Makefile: Name ftpd_start is not the name of
      the entrypoint.  Should be ftpd_main (from Yan T.)
    * apps/netutils/telnetd/telnetd_driver: Was stuck in a loop if
      recv[from]() ever returned a value &lt;= 0.
    * apps/examples/nettest and poll:  Complete Kconfig files.
    * apps/examples/ostest/waitpid.c:  Need to use WEXITSTATUS()
      to decode the correct exit status.
    * apps/system/usbmonitor:  A daemon that can be used to monitor USB
      trace outpout.
    * apps/nshlib/nsh_usbdev.c, nsh_consolemain.c, nsh_session.c, nsh_script.c:
      Add support for a login script.  The init.d/rcS script will be executed
      once when NSH starts; the .nshrc script will be executed for each session:
      Once for serial, once for each USB connection, once for each Telnet
      session.
    * apps/system/readline: Correct readline() return value.  Was not
      any returning special values when end-of-file or read errors
      occur (it would return an empty string which is not very useful).

NxWidgets-1.5 2013-02-01 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * NxWidgets::CGraphicsPort::move():  Fix typo bug in bounding rectangle
      calculation (from Petteri Aimonen).
    * NxWM::CScrollingPanel::scrollChildren(): Avoid unnecessary redraws in
      CScrollingPanel (contributed by Petteri Aimonen).
    * NxWM::CCycleButton:  Remove the separator from CCycleButton. It draws in
      wrong place, and doesnt look very good in the correct place either.
      (from Petteri Aimonen).
    * NxWidgets::CGraphicsPort: Many times we only want a constant background.
      In that case the old code fills the background, reads it back, renders
      the text and then writes it back. When used with LCD's (instead of
      framebuffers) this causes unnecessary delay and screen flicker.
      This commit adds a variant of drawText that takes background color,
      so that the background and text can both be rendered at one go.
      The old functions still function as before (Petteri Aimonen).
    * NxWidgets::CLabel: The label was drawn as a single rectangular region,
      then a text was added to the on top of this.  The result is that the
      text would flicker when the CLabel was updated. With this change, the
      two step update is replaced with a five step update:  The background
      is updated as four rectangulear regions (leaving the previous text in
      place), then the new text is updated.  This eliminates the flicker
      (Petteri Aimonen).
    * Kconfig: Many NxWidgets/NxWM settings do not have meaningful, generic
      default values.  Colors, for example, depend on pixel depth.  Some
      geometry settings depending on other geometry settings.  Font IDs are
      not know-able by the configuration system.  etc.  In these cases, it
      is best if the settings are just not undefined so that the system can
      calculate a reasonable default.  however, if no default is provided
      in the .config file, mconf will complain and generate errors.  So work
      around this, I added several &quot;enabling&quot; settings to override the
      default setting.  This is awkward and I preferred the configuration as
      it was before, but this avoids the mconf errors and warnings.
    * UnitTests:  Changed occurrences of lib_rawprintf() and lib_lowprintf()
      to match recent changes to NuttX (will be in NuttX-6.25)
    * CGraphicsPort::_drawText:  Renamed from CGraphicsPort::drawText in order
      to eliminate some naming collisions when overloaded in some configurations
      (i.e., when both bool and nx_pixel_t are uint8_t).  From Petteri Aimonen.
    * CNxWidgets::drawContents: Change base drawContents from a do-nothing
      function to a function that fills the widget with the background color.
      This is useful when using CNxWidgets as a &quot;panel&quot; , i.e. a container
      for other widgets. Subclasses will override drawContents and decide
      themselves how to draw the background.
    * CNxWidgets::CTabPanel:  A new widget contributed by Petteri Aimonen.
      This widget provides a tab panel, which has a button bar at the top
      and panels below it. Pressing a button will select the corresponding
      panel.

uClibc++-1.0 2011-11-05 &lt;gnutt@nuttx.org&gt;

    * The initial release of the uClibc++ implementation of the standard
      C++ library for NuttX.  This package was contributed ay Qiang Yu and
      David for the RGMP team.

buildroot-1.11 2011-11-05 &lt;gnutt@nuttx.org&gt;

    * configs/avr-defconfig-4.3.3 - Added --enable-long-long as a GCC
      option.
    * configs/avr-defconfig-4.5.2 - New configuration.
    * Config.in and almost all configurations in configs/ - Changed the
      default nuttx path to $(TOPDIR)/../../nuttx
    * Misc files.  Patch provided by Gerd v. Egidy that solves the following
      problems
      - binutils 2.21 is not available on the gnu servers anymore, they replaced
        it with 2.21.1
      - there is some assembler error when compiling gcc for arm, gcc bugzilla
        43999
      - you can't build nuttx for cortex m3/m4 because of a missing instruction
        in the assembler, binutils bugzilla 12296
    * Add support for binutils 2.22 and GCC 4.6.3.
    * Change name of all tools from xxx-elf to xxx-nuttx-elf
    * Added an ARM EABI GCC 4.6.3 configuration (tool name is arm-nuttx-eabi-).
    * ldnxflat: Add support for the R_ARM_REL32 relocation.  This relocation
      type was not generated by GCC/LD prior to gcc-4.6.3
    * R_ARM_REL32 logic is conditionally disabled because it has not been
      tested.
    * ldnxflat: Correct a memory allocation error that could cause written
      past the end of allocated memory.  Partial restoration of R_ARM_REL32
      logic.  There are lots of issues that I still do not understand here.

pascal-3.0 2011-05-15 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * nuttx/:  The Pascal add-on module now installs and builds under the
      apps/interpreters directory.  This means that the pascal-2.1 module is
      incompatible with will all releases of NuttX prior to nuttx-6.0 where the 
      apps/ module was introduced.
</pre></ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="pendingchanges">Unreleased Changes</a>
  </td>
  </tr>
</table>

<ul>
  <li><b>nuttx-6.18</b>.
    The ChangeLog for the not-yet-released version 6.18 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/nuttx/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>apps-6.18</b>.
    The ChangeLog for the not-yet-released version 6.18 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/apps/ChangeLog.txt?view=log">SourceForge SVN</a>.
  </li>
  <li><b>NxWidgets-1.1</b>.
    The ChangeLog for the not-yet-released version 1.1 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/NxWidgets/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>pascal-1.1</b>.
    The ChangeLog for the not-yet-released version 1.1 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/pascal/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>buildroot-1.11</b>.
    The ChangeLog for the not-yet-released version 1.11 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://svn.code.sf.net/p/nuttx/code/trunk/misc/buildroot/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="TODO"><h1>Bugs, Issues, <i>Things-To-Do</i></h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
   The current list of NuttX <i>Things-To-Do</i> in SVN <a href="http://svn.code.sf.net/p/nuttx/code/trunk/nuttx/TODO?view=log">here</a>.
   A snapshot of the <i>To-Do</i> list associated with the current release are available <a href="TODO.txt">here</a>.
</p>
</ul>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="documentation"><h1>Other Documentation</h1></a>
  </td>
  </tr>
</table>

<ul><table>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXGettingStarted.html">Getting Started</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttxUserGuide.html">User Guide</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttxPortingGuide.html">Porting Guide</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttShell.html">NuttShell (NSH)</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXBinfmt.html">NuttX Binary Loader</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXNxFlat.html">NXFLAT Binary Format</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NXGraphicsSubsystem.html">NX Graphics Subsystem</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NxWidgets.html">NxWidgets</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXDemandPaging.html">Demand Paging</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="README.html">NuttX README Files</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="ChangeLog.txt">Change Log</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="TODO.txt">To-Do List</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="UsbTrace.html">USB Device Driver Tracing</a></td>
</tr>
</center></ul>

<small>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="trademarks"><h1>Trademarks</h1></a>
  </td>
  </tr>
</table>
<ul>
  <li>ARM, ARM7 ARM7TDMI, ARM9, ARM920T, ARM926EJS Cortex-M3 are trademarks of Advanced RISC Machines, Limited.</li>
  <li>Cygwin is a trademark of Red Hat, Incorporated.</li>
  <li>Linux is a registered trademark of Linus Torvalds.</li>
  <li>Eagle-100 is a trademark of <a href=" http://www.micromint.com/">Micromint USA, LLC</a>.
  <li>LPC2148 is a trademark of NXP Semiconductors.</li>
  <li>TI is a tradename of Texas Instruments Incorporated.</li>
  <li>UNIX is a registered trademark of The Open Group.</li>
  <li>VxWorks is a registered trademark of Wind River Systems, Incorporated.</li>
  <li>ZDS, ZNEO, Z16F, Z80, and Zilog are a registered trademark of Zilog, Inc.</li>
</ul>
<p>
  NOTE: NuttX is <i>not</i> licensed to use the POSIX trademark.  NuttX uses the POSIX
  standard as a development guideline only.
</p>
</small>

</body>
</html>