Cleanup, WIP, needs a NuttX checkout to Firmware/NuttX now

33 files changed, 0 insertions, 8154 deletions

diff --git a/nuttx/configs/Kconfig b/nuttx/configs/Kconfig
deleted file mode 100644
index ebe6d5480..000000000
--- a/nuttx/configs/Kconfig
+++ /dev/null
@@ -1,40 +0,0 @@
-#
-# For a description of the syntax of this configuration file,
-# see misc/tools/kconfig-language.txt.
-#
-
-choice
-	prompt "Select target board"
-	default ARCH_BOARD_CUSTOM
-	---help---
-		Select the board hosting the architure.  You must first select the
-		exact MCU part number, then the boards supporting that part will
-		be available for selection.  Use ARCH_BOARD_CUSTOM to create a new
-		board configuration.
-
-config ARCH_BOARD_PX4FMU
-	bool "PX4FMU board"
-	depends on ARCH_CHIP_STM32F405RG
-	---help---
-		PX4 system Flight Management Unit
-
-config ARCH_BOARD_PX4IO
-	bool "PX4IO board"
-	depends on ARCH_CHIP_STM32F100C8
-	---help---
-		PX4 system I/O expansion board
-
-endchoice
-
-config ARCH_BOARD
-	string
-	default "px4fmu"             if ARCH_BOARD_PX4FMU
-	default "px4io"              if ARCH_BOARD_PX4IO
-	default ""                   if ARCH_BOARD_CUSTOM
-
-if ARCH_BOARD_PX4FMU
-source "configs/px4fmu/Kconfig"
-endif
-if ARCH_BOARD_PX4IO
-source "configs/px4io/Kconfig"
-endif
diff --git a/nuttx/configs/README.txt b/nuttx/configs/README.txt
deleted file mode 100644
index 8d9bb381f..000000000
--- a/nuttx/configs/README.txt
+++ /dev/null
@@ -1,2098 +0,0 @@
-Board-Specific Configurations
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Table of Contents
-^^^^^^^^^^^^^^^^^
-
-  o Board-Specific Configurations
-  o Summary of Files
-  o Supported Architectures
-  o Configuring NuttX
-  o Building Symbol Tables
-
-Board-Specific Configurations
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The NuttX configuration consists of:
-
-o Processor architecture specific files.  These are the files contained
-  in the arch/<arch-name>/ directory.
-
-o Chip/SoC specific files.  Each processor processor architecture
-  is embedded in chip or System-on-a-Chip (SoC) architecture.  The
-  full chip architecture includes the processor architecture plus
-  chip-specific interrupt logic, general purpose I/O (GIO) logic, and
-  specialized, internal peripherals (such as UARTs, USB, etc.).
-
-  These chip-specific files are contained within chip-specific
-  sub-directories in the arch/<arch-name>/ directory and are selected
-  via the CONFIG_ARCH_name selection
-
-o Board specific files.  In order to be usable, the chip must be
-  contained in a board environment.  The board configuration defines
-  additional properties of the board including such things as
-  peripheral LEDs, external peripherals (such as network, USB, etc.).
-
-  These board-specific configuration files can be found in the
-  configs/<board-name>/ sub-directories and are discussed in this
-  README.  Additional configuration information maybe available in
-  board-specific configs/<board-name>/README.txt files.
-
-The configs/ subdirectory contains configuration data for each board.  These
-board-specific configurations plus the architecture-specific configurations in
-the arch/ subdirectory completely define a customized port of NuttX.
-
-Directory Structure
-^^^^^^^^^^^^^^^^^^^
-
-The configs directory contains board specific configurationlogic.  Each
-board must provide a subdirectory <board-name> under configs/ with the
-following characteristics:
-
-
-  <board-name>
-  |-- README.txt
-  |-- include/
-  |   `-- (board-specific header files)
-  |-- src/
-  |   |-- Makefile
-  |   `-- (board-specific source files)
-  |-- <config1-dir>
-  |   |-- Make.defs
-  |   |-- defconfig
-  |   |-- appconfig*
-  |   `-- setenv.sh
-  |-- <config2-dir>
-  |   |-- Make.defs
-  |   |-- defconfig
-  |   |-- appconfig*
-  |   `-- setenv.sh
-  ...
-
-  *optional
-
-Summary of Files
-^^^^^^^^^^^^^^^^
-
-README.txt -- This text file provides additional information unique to
-  each board configuration sub-directory.
-
-include/ -- This directory contains board specific header files.  This
-  directory will be linked as include/arch/board at configuration time and
-  can be included via '#include <arch/board/header.h>'.  These header file
-  can only be included by files in arch/<arch-name>include/ and
-  arch/<arch-name>/src
-
-src/ -- This directory contains board specific drivers.  This
-  directory will be linked as arch/<arch-name>/src/board at configuration
-  time and will be integrated into the build system.
-
-src/Makefile -- This makefile will be invoked to build the board specific
-  drivers.  It must support the following targets:  libext$(LIBEXT), clean,
-  and distclean.
-
-A board may have various different configurations using these common source
-files.  Each board configuration is described by three files:  Make.defs,
-defconfig, and setenv.sh.  Typically, each set of configuration files is
-retained in a separate configuration sub-directory (<config1-dir>,
-<config2-dir>, .. in the above diagram).
-
-Make.defs -- This makefile fragment provides architecture and
-  tool-specific build options.  It will be included by all other
-  makefiles in the build (once it is installed).  This make fragment
-  should define:
-
-    Tools: CC, LD, AR, NM, OBJCOPY, OBJDUMP
-    Tool options: CFLAGS, LDFLAGS
-
-  When this makefile fragment runs, it will be passed TOPDIR which
-  is the path to the root directory of the build.  This makefile
-  fragment should include:
-
-    $(TOPDIR)/.config          : Nuttx configuration
-    $(TOPDIR)/tools/Config.mk  : Common definitions
-
-  Definitions in the Make.defs file probably depend on some of the
-  settings in the .config file.  For example, the CFLAGS will most likely be
-  different if CONFIG_DEBUG=y.
-
-  The included tools/Config.mk file contains additional definitions that may
-  be overriden in the architecture-specific Make.defs file as necessary:
-
-    COMPILE, ASSEMBLE, ARCHIVE, CLEAN, and MKDEP macros
-
-defconfig -- This is a configuration file similar to the Linux
-  configuration file.  In contains variable/value pairs like:
-
-  CONFIG_VARIABLE=value
-
-  This configuration file will be used at build time:
-
-    (1) as a makefile fragment included in other makefiles, and
-    (2) to generate include/nuttx/config.h which is included by
-        most C files in the system.
-
-  The following variables are recognized by the build (you may
-  also include architecture/board-specific settings).
-
-  Architecture selection:
-
-    CONFIG_ARCH - Identifies the arch/ subdirectory
-    CONFIG_ARCH_name - For use in C code
-    CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
-    CONFIG_ARCH_CHIP_name - For use in C code
-    CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
-       hence, the board that supports the particular chip or SoC.
-    CONFIG_ARCH_BOARD_name - For use in C code
-    CONFIG_ENDIAN_BIG - define if big endian (default is little
-       endian)
-    CONFIG_ARCH_NOINTC - define if the architecture does not
-      support an interrupt controller or otherwise cannot support
-      APIs like up_enable_irq() and up_disable_irq().
-    CONFIG_ARCH_VECNOTIRQ - Usually the interrupt vector number provided
-      to interfaces like irq_attach() and irq_detach are the same as IRQ
-      numbers that are provied to IRQ management functions like
-      up_enable_irq() and up_disable_irq().  But that is not true for all
-      interrupt controller implementations.  For example, the PIC32MX
-      interrupt controller manages interrupt sources that have a many-to-one
-      relationship to interrupt vectors. In such cases, CONFIG_ARCH_VECNOTIRQ
-      must defined so that the OS logic will know not to assume it can use
-      a vector number to enable or disable interrupts.
-    CONFIG_ARCH_IRQPRIO
-      Define if the architecture suports prioritizaton of interrupts
-      and the up_prioritize_irq() API.
-    CONFIG_ADDRENV
-      The CPU supports an MMU and CPU port supports provision of address
-      environments for tasks (making the, perhaps, processes).
-
-  Some architectures require a description of the RAM configuration:
-
-    CONFIG_DRAM_SIZE - Describes the installed DRAM.
-    CONFIG_DRAM_START - The start address of DRAM (physical)
-    CONFIG_DRAM_VSTART - The start address of DRAM (virtual)
-
-  General build options:
-
-    CONFIG_RRLOAD_BINARY - make the rrload binary format used with
-      BSPs from www.ridgerun.com using the tools/mkimage.sh script.
-    CONFIG_INTELHEX_BINARY - make the Intel HEX binary format
-      used with many different loaders using the GNU objcopy program
-      Should not be selected if you are not using the GNU toolchain.
-    CONFIG_MOTOROLA_SREC - make the Motorola S-Record binary format
-      used with many different loaders using the GNU objcopy program
-      Should not be selected if you are not using the GNU toolchain.
-    CONFIG_RAW_BINARY - make a raw binary format file used with many
-      different loaders using the GNU objcopy program.  This option
-      should not be selected if you are not using the GNU toolchain.
-    CONFIG_HAVE_CXX - toolchain supports C++ and CXX, CXXFLAGS, and
-      COMPILEXX have been defined in the configurations Make.defs
-      file.
-    CONFIG_HAVE_CXXINITIALIZE - The platform-specific logic includes support
-      for initialization of static C++ instances for this architecture
-      and for the selected toolchain (via up_cxxinitialize()).
-
-  Building application code:
-
-    CONFIG_APPS_DIR - Identifies the directory that builds the
-      application to link with NuttX.  Default: ../apps This symbol must be assigned
-      to the path to the application build directory *relative* to
-      the NuttX top build direcory. If you had an application
-      directory and the NuttX directory each in separate directory
-      trees like this:
-
-      build
-       |-nuttx
-       |  |
-       |  `- Makefile
-       `-application
-       |
-       `- Makefile
-
-      Then you would set CONFIG_APPS_DIR=../application.
-
-      The application direction must contain Makefile and this make
-      file must support the following targets:
-
-      - libapps$(LIBEXT) (usually libapps.a). libapps.a is a static
-      library ( an archive) that contains all of application object
-      files.
-      - clean. Do whatever is appropriate to clean the application
-      directories for a fresh build.
-      - distclean. Clean everthing -- auto-generated files, symbolic
-      links etc. -- so that the directory contents are the same as
-      the contents in your configuration management system.
-      This is only done when you change the NuttX configuration.
-      - depend. Make or update the application build dependencies.
-
-      When this application is invoked it will receive the setting TOPDIR like:
-
-      $(MAKE) -C $(CONFIG_APPS_DIR) TOPDIR="$(TOPDIR)" <target>
-
-      TOPDIR is the full path to the NuttX directory. It can be used, for
-      example, to include makefile fragments (e.g., .config or Make.defs)
-      or to set up include file paths.
-
-  Two-pass build options.  If the 2 pass build option is selected, then these
-  options configure the make system build a extra link object. This link object
-  is assumed to be an incremental (relative) link object, but could be a static
-  library (archive) (some modification to this Makefile would be required if
-  CONFIG_PASS1_TARGET generates an archive). Pass 1 1ncremental (relative) link
-  objects should be put into the processor-specific source directory (where other
-  link objects will be created).  If the pass1 obect is an archive, it could
-  go anywhere.
-
-    CONFIG_BUILD_2PASS - Enables the two pass build options.
-
-  When the two pass build option is enabled, the following also apply:
-
-    CONFIG_PASS1_TARGET - The name of the first pass build target.  This
-      can be specific build target, a special build target (all, default, etc.)
-      or may just be left undefined.
-    CONFIG_PASS1_BUILDIR - The path, relative to the top NuttX build
-      directory to directory that contains the Makefile to build the
-      first pass object.  The Makefile must support the following targets:
-      - The special target CONFIG_PASS1_TARGET (if defined)
-      - and the usual depend, clean, and distclean targets.
-    CONFIG_PASS1_OBJECT - May be used to include an extra, pass1 object
-      into the final link.  This would probably be the object generated
-      from the CONFIG_PASS1_TARGET.  It may be available at link time
-      in the arch/<architecture>/src directory.
-
-  General OS setup
-
-    CONFIG_DEBUG - enables built-in debug options
-    CONFIG_DEBUG_VERBOSE - enables verbose debug output
-    CCONFIG_SYSLOG_ENABLE - Support an interface to enable or disable debug output.
-    CONFIG_DEBUG_SYMBOLS - build without optimization and with
-      debug symbols (needed for use with a debugger).
-    CONFIG_DEBUG_SCHED - enable OS debug output (disabled by
-      default)
-    CONFIG_DEBUG_MM - enable memory management debug output
-      (disabled by default)
-    CONFIG_DEBUG_NET - enable network debug output (disabled
-      by default)
-    CONFIG_DEBUG_USB - enable usb debug output (disabled by
-      default)
-    CONFIG_DEBUG_FS - enable filesystem debug output (disabled
-      by default)
-    CONFIG_DEBUG_LIB - enable C library debug output (disabled
-      by default)
-    CONFIG_DEBUG_BINFMT - enable binary loader debug output (disabled
-      by default)
-    CONFIG_DEBUG_GRAPHICS - enable NX graphics debug output
-      (disabled by default)
-
-    CONFIG_MM_REGIONS - If the architecture includes multiple
-      regions of memory to allocate from, this specifies the
-      number of memory regions that the memory manager must
-      handle and enables the API mm_addregion(start, end);
-    CONFIG_MM_SMALL - Each memory allocation has a small allocation
-      overhead.  The size of that overhead is normally determined by
-      the "width" of the address support by the MCU.  MCUs that support
-      16-bit addressability have smaller overhead than devices that
-      support 32-bit addressability.  However, there are many MCUs
-      that support 32-bit addressability *but* have internal SRAM
-      of size less than or equal to 64Kb.  In this case, CONFIG_MM_SMALL
-      can be defined so that those MCUs will also benefit from the
-      smaller, 16-bit-based allocation overhead.
-    CONFIG_HEAP2_BASE and CONFIG_HEAP2_SIZE
-      Some architectures use these settings to specify the size of
-      a second heap region.
-    CONFIG_GRAN
-      Enable granual allocator support.  Allocations will be aligned to the
-      granule size; allocations will be in units of the granule size.
-      Larger granules will give better performance and less overhead but
-      more losses of memory due to alignment and quantization waste.
-      NOTE: The current implementation also restricts the maximum
-      allocation size to 32 granaules.  That restriction could be
-      eliminated with some additional coding effort.
-    CONFIG_GRAN_SINGLE
-      Select if there is only one instance of the granule allocator (i.e.,
-      gran_initialize will be called only once. In this case, (1) there
-      are a few optimizations that can can be done and (2) the GRAN_HANDLE
-      is not needed.
-    CONFIG_GRAN_INTR - Normally mutual exclusive access to granule allocator
-      data is assured using a semaphore.  If this option is set then, instead,
-      mutual exclusion logic will disable interrupts.  While this options is
-      more invasive to system performance, it will also support use of the
-      granule allocator from interrupt level logic.
-    CONFIG_DEBUG_GRAM
-      Just like CONFIG_DEBUG_MM, but only generates ouput from the gran
-      allocation logic.
-
-    CONFIG_ARCH_LOWPUTC - architecture supports low-level, boot
-      time console output
-    CONFIG_MSEC_PER_TICK - The default system timer is 100Hz
-      or MSEC_PER_TICK=10.  This setting may be defined to
-      inform NuttX that the processor hardware is providing
-      system timer interrupts at some interrupt interval other
-      than 10 msec.
-    CONFIG_RR_INTERVAL - The round robin timeslice will be set
-      this number of milliseconds;  Round robin scheduling can
-      be disabled by setting this value to zero.
-    CONFIG_SCHED_INSTRUMENTATION - enables instrumentation in
-      scheduler to monitor system performance
-    CONFIG_TASK_NAME_SIZE - Specifies that maximum size of a
-      task name to save in the TCB.  Useful if scheduler
-      instrumentation is selected.  Set to zero to disable.
-    CONFIG_SCHED_HAVE_PARENT - Remember the ID of the parent task
-      when a new child task is created.  This support enables some
-      additional features (such as SIGCHLD) and modifies the behavior
-      of other interfaces.  For example, it makes waitpid() more
-      standards complete by restricting the waited-for tasks to the
-      children of the caller. Default: disabled.
-    CONFIG_SCHED_CHILD_STATUS
-      If this option is selected, then the exit status of the child task
-      will be retained after the child task exits.  This option should be
-      selected if you require knowledge of a child process' exit status.
-      Without this setting, wait(), waitpid() or waitid() may fail.  For
-      example, if you do:
-
-        1) Start child task
-        2) Wait for exit status (using wait(), waitpid(), or waitid()).
-
-      This can fail because the child task may run to completion before
-      the wait begins.  There is a non-standard work-around in this case:
-      The above sequence will work if you disable pre-emption using
-      sched_lock() prior to starting the child task, then re-enable pre-
-      emption with sched_unlock() after the wait completes.  This works
-      because the child task is not permitted to run until the wait is in
-      place.
-
-      The standard solution would be to enable CONFIG_SCHED_CHILD_STATUS.  In
-      this case the exit status of the child task is retained after the
-      child exits and the wait will successful obtain the child task's
-      exit status whether it is called before the child task exits or not.
-
-      Warning:  If you enable this feature, then your application must
-      either (1) take responsibility for reaping the child status with wait(),
-      waitpid(), or waitid(), or (2) suppress retention of child status.
-      If you do not reap the child status, then you have a memory leak and
-      your system will eventually fail.
-
-      Retention of child status can be suppressed on the parent using logic like:
-
-        struct sigaction sa;
-
-        sa.sa_handler = SIG_IGN;
-        sa.sa_flags = SA_NOCLDWAIT;
-        int ret = sigaction(SIGCHLD, &sa, NULL);
-
-    CONFIG_PREALLOC_CHILDSTATUS
-      To prevent runaway child status allocations and to improve
-      allocation performance, child task exit status structures are pre-
-      allocated when the system boots.  This setting determines the number
-      of child status structures that will be pre-allocated.  If this
-      setting is not defined or if it is defined to be zero then a value
-      of 2*MAX_TASKS is used.
-
-      Note that there cannot be more that CONFIG_MAX_TASKS tasks in total.
-      However, the number of child status structures may need to be
-      significantly larger because this number includes the maximum number
-      of tasks that are running PLUS the number of tasks that have exit'ed
-      without having their exit status reaped (via wait(), waitid(), or
-      waitpid()).
-
-      Obviously, if tasks spawn children indefinitely and never have the
-      exit status reaped, then you may have a memory leak!  If you enable
-      the SCHED_CHILD_STATUS feature, then your application must take
-      responsibility for either (1) reaping the child status with wait(),
-      waitpid(), or waitid() or it must (2) suppress retention of child
-      status.  Otherwise, your system will eventually fail.
-
-      Retention of child status can be suppressed on the parent using logic like:
-
-        struct sigaction sa;
-
-        sa.sa_handler = SIG_IGN;
-        sa.sa_flags = SA_NOCLDWAIT;
-        int ret = sigaction(SIGCHLD, &sa, NULL);
-
-    CONFIG_START_YEAR, CONFIG_START_MONTH, CONFIG_START_DAY -
-      Used to initialize the internal time logic.
-    CONFIG_GREGORIAN_TIME - Enables Gregorian time conversions.
-      You would only need this if you are concerned about accurate
-      time conversions in the past or in the distant future.
-    CONFIG_JULIAN_TIME - Enables Julian time conversions. You
-      would only need this if you are concerned about accurate
-      time conversion in the distand past.  You must also define
-      CONFIG_GREGORIAN_TIME in order to use Julian time.
-    CONFIG_DEV_CONSOLE - Set if architecture-specific logic
-      provides /dev/console.  Enables stdout, stderr, stdin.
-      This implies the "normal" serial driver provides the
-      console unless another console device is specified
-      (See CONFIG_DEV_LOWCONSOLE).
-    CONFIG_MUTEX_TYPES - Set to enable support for recursive and
-      errorcheck mutexes.  Enables pthread_mutexattr_settype().
-    CONFIG_PRIORITY_INHERITANCE - Set to enable support for
-      priority inheritance on mutexes and semaphores.
-      Priority inheritance is a strategy for addressing priority
-      inversion.
-    CONFIG_SEM_PREALLOCHOLDERS: This setting is only used if priority
-      inheritance is enabled.  It defines the maximum number of
-      different threads (minus one) that can take counts on a
-      semaphore with priority inheritance support.  This may be
-      set to zero if priority inheritance is disabled OR if you
-      are only using semaphores as mutexes (only one holder) OR
-      if no more than two threads participate using a counting
-      semaphore.  If defined, then this should be a relatively
-      large number because this is the total number of counts on
-      the total number of semaphores (like 64 or 100).
-    CONFIG_SEM_NNESTPRIO.  If priority inheritance is enabled,
-      then this setting is the maximum number of higher priority
-      threads (minus 1) than can be waiting for another thread
-      to release a count on a semaphore.  This value may be set
-      to zero if no more than one thread is expected to wait for
-      a semaphore.  If defined, then this should be a relatively
-      small number because this the number of maximumum of waiters
-      on one semaphore (like 4 or 8).
-    CONFIG_FDCLONE_DISABLE. Disable cloning of all file descriptors
-      by task_create() when a new task is started.  If set, all
-        files/drivers will appear to be closed in the new task.
-    CONFIG_FDCLONE_STDIO. Disable cloning of all but the first
-      three file descriptors (stdin, stdout, stderr) by task_create()
-      when a new task is started. If set, all files/drivers will
-      appear to be closed in the new task except for stdin, stdout,
-      and stderr.
-    CONFIG_SDCLONE_DISABLE. Disable cloning of all socket
-      desciptors by task_create() when a new task is started. If
-      set, all sockets will appear to be closed in the new task.
-    CONFIG_SCHED_WORKQUEUE.  Create a dedicated "worker" thread to
-      handle delayed processing from interrupt handlers.  This feature
-      is required for some drivers but, if there are not complaints,
-      can be safely disabled.  The worker thread also performs
-      garbage collection -- completing any delayed memory deallocations
-      from interrupt handlers.  If the worker thread is disabled,
-      then that clean will be performed by the IDLE thread instead
-      (which runs at the lowest of priority and may not be appropriate
-      if memory reclamation is of high priority).  If CONFIG_SCHED_WORKQUEUE
-      is enabled, then the following options can also be used:
-    CONFIG_SCHED_WORKPRIORITY - The execution priority of the worker
-      thread.  Default: 192
-    CONFIG_SCHED_WORKPERIOD - How often the worker thread checks for
-      work in units of microseconds.  Default: 50*1000 (50 MS).
-    CONFIG_SCHED_WORKSTACKSIZE - The stack size allocated for the worker
-      thread.  Default: CONFIG_IDLETHREAD_STACKSIZE.
-    CONFIG_SIG_SIGWORK - The signal number that will be used to wake-up
-      the worker thread.  Default: 17
-    CONFIG_SCHED_LPWORK. If CONFIG_SCHED_WORKQUEUE is defined, then a single
-      work queue is created by default.  If CONFIG_SCHED_LPWORK is also defined
-      then an additional, lower-priority work queue will also be created.  This
-      lower priority work queue is better suited for more extended processing
-      (such as file system clean-up operations)
-    CONFIG_SCHED_LPWORKPRIORITY - The execution priority of the lower priority
-      worker thread.  Default: 50
-    CONFIG_SCHED_LPWORKPERIOD - How often the lower priority worker thread
-      checks for work in units of microseconds.  Default: 50*1000 (50 MS).
-    CONFIG_SCHED_LPWORKSTACKSIZE - The stack size allocated for the lower
-      priority worker thread.  Default: CONFIG_IDLETHREAD_STACKSIZE.
-    CONFIG_SCHED_WAITPID - Enables the waitpid() interface in a default,
-      non-standard mode (non-standard in the sense that the waited for
-      PID need not be child of the caller).  If SCHED_HAVE_PARENT is
-      also defined, then this setting will modify the behavior or
-      waitpid() (making more spec compliant) and will enable the
-      waitid() and wait() interfaces as well.
-    CONFIG_SCHED_ATEXIT -  Enables the atexit() API
-    CONFIG_SCHED_ATEXIT_MAX -  By default if CONFIG_SCHED_ATEXIT is
-      selected, only a single atexit() function is supported. That number
-      can be increased by defined this setting to the number that you require.
-    CONFIG_SCHED_ONEXIT -  Enables the on_exit() API
-    CONFIG_SCHED_ONEXIT_MAX -  By default if CONFIG_SCHED_ONEXIT is selected,
-      only a single on_exit() function is supported. That number can be
-      increased by defined this setting to the number that you require.
-    CONFIG_USER_ENTRYPOINT - The name of the entry point for user
-      applications.  For the example applications this is of the form 'app_main'
-      where 'app' is the application name. If not defined, CONFIG_USER_ENTRYPOINT
-      defaults to user_start.
-
-  Signal Numbers:
-
-    CONFIG_SIG_SIGUSR1 - Value of standard user signal 1 (SIGUSR1).
-      Default: 1
-    CONFIG_SIG_SIGUSR2 - Value of standard user signal 2 (SIGUSR2).
-      Default: 2
-    CONFIG_SIG_SIGALARM - Default the standard signal used with POSIX
-      timers (SIGALRM).  Default: 3
-    CONFIG_SIG_SIGCHLD - The SIGCHLD signal is sent to the parent of a child
-      process when it exits, is interrupted (stopped), or resumes after being
-      interrupted. Default: 4
-
-    CONFIG_SIG_SIGCONDTIMEDOUT - This non-standard signal number is used in
-      the implementation of pthread_cond_timedwait(). Default 16.
-    CONFIG_SIG_SIGWORK - SIGWORK is a non-standard signal used to wake up
-      the internal NuttX worker thread. Default: 17.
-
-  Binary Loaders:
-    CONFIG_BINFMT_DISABLE - By default, support for loadable binary formats
-      is built.
-    This logic may be suppressed be defining this setting.
-    CONFIG_BINFMT_CONSTRUCTORS - Build in support for C++ constructors in
-      loaded modules.
-    CONFIG_SYMTAB_ORDEREDBYNAME - Symbol tables are order by name (rather
-      than value).
-    CONFIG_NXFLAT. Enable support for the NXFLAT binary format. This format
-      will support execution of NuttX binaries located in a ROMFS filesystem
-      (see apps/examples/nxflat).
-    CONFIG_ELF - Enable support for the ELF binary format. This format will
-      support execution of ELF binaries copied from a file system and
-      relocated into RAM (see apps/examples/elf).
-
-    If CONFIG_ELF is selected, then these additional options are available:
-
-    CONFIG_ELF_ALIGN_LOG2 - Align all sections to this Log2 value:  0->1,
-      1->2, 2->4, etc.
-    CONFIG_ELF_STACKSIZE - This is the default stack size that will will
-      be used when starting ELF binaries.
-    CONFIG_ELF_BUFFERSIZE - This is an I/O buffer that is used to access
-      the ELF file.  Variable length items will need to be read (such as
-      symbol names).  This is really just this initial size of the buffer;
-      it will be reallocated as necessary to hold large symbol names).
-      Default: 128
-    CONFIG_ELF_BUFFERINCR - This is an I/O buffer that is used to access
-      the ELF file.  Variable length items will need to be read (such as
-      symbol names). This value specifies the size increment to use each
-      time the buffer is reallocated. Default: 32
-    CONFIG_ELF_DUMPBUFFER - Dump various ELF buffers for debug purposes.
-      This option requires CONFIG_DEBUG and CONFIG_DEBUG_VERBOSE.
-
-  System Logging:
-    CONFIG_SYSLOG enables general system logging support.
-    CONFIG_SYSLOG_DEVPATH - The full path to the system logging device.  Default
-      "/dev/ramlog" (RAMLOG) or "dev/ttyS1" (character device)
-
-    At present, there are two system loggins devices available. If CONFIG_SYSLOG
-    is selected, then these options are also available.
-
-    CONFIG_SYSLOG_CHAR - Enable the generic character device for the SYSLOG.
-      A disadvantage of using the generic character device for the SYSLOG is that
-      it cannot handle debug output generated from interrupt level handlers.
-      NOTE:  No more than one SYSLOG device should be configured.
-
-    CONFIG_RAMLOG - Enables the RAM logging feature. The RAM log is a circular
-      buffer in RAM. NOTE:  No more than one SYSLOG device should be configured.
-    CONFIG_RAMLOG_CONSOLE - Use the RAM logging device as a system console.
-      If this feature is enabled (along with CONFIG_DEV_CONSOLE), then all
-      console output will be re-directed to a circular buffer in RAM.  This
-      is useful, for example, if the only console is a Telnet console.  Then
-      in that case, console output from non-Telnet threads will go to the
-      circular buffer and can be viewed using the NSH 'dmesg' command.
-    CONFIG_RAMLOG_SYSLOG - Use the RAM logging device for the syslogging
-      interface.  If this feature is enabled (along with CONFIG_SYSLOG),
-      then all debug output (only) will be re-directed to the circular
-      buffer in RAM.  This RAM log can be view from NSH using the 'dmesg'
-      command.  NOTE:  Unlike the limited, generic character driver SYSLOG
-      device, the RAMLOG *can* be used to generate debug output from interrupt
-      level handlers.
-    CONFIG_RAMLOG_NPOLLWAITERS - The number of threads than can be waiting
-     for this driver on poll().  Default: 4
-
-    If CONFIG_RAMLOG_CONSOLE or CONFIG_RAMLOG_SYSLOG is selected, then the
-    following may also be provided:
-
-    CONFIG_RAMLOG_CONSOLE_BUFSIZE - Size of the console RAM log.  Default: 1024
-
-  Kernel build options:
-    CONFIG_NUTTX_KERNEL - Builds NuttX as a separately compiled kernel.
-    CONFIG_SYS_RESERVED - Reserved system call values for use
-      by architecture-specific logic.
-
-  OS setup related to on-demand paging:
-
-    CONFIG_PAGING - If set =y in your configation file, this setting will
-      enable the on-demand paging feature as described in
-      http://www.nuttx.org/NuttXDemandPaging.html.
-
-  If CONFIG_PAGING is selected, then you will probabaly need CONFIG_BUILD_2PASS to
-  correctly position the code and the following configuration options also apply:
-
-    CONFIG_PAGING_PAGESIZE - The size of one managed page.  This must
-      be a value supported by the processor's memory management unit.
-    CONFIG_PAGING_NLOCKED - This is the number of locked pages in the
-      memory map.  The locked address region will then be from
-      CONFIG_DRAM_VSTART through (CONFIG_DRAM_VSTART +
-      CONFIG_PAGING_PAGESIZE*CONFIG_PAGING_NLOCKED)
-    CONFIG_PAGING_LOCKED_PBASE and CONFIG_PAGING_LOCKED_VBASE - These
-      may be defined to determine the base address of the locked page
-      regions.  If neither are defined, the logic will be set the bases
-      to CONFIG_DRAM_START and CONFIG_DRAM_VSTART (i.e., it assumes
-      that the base address of the locked region is at the beginning
-      of RAM).
-      NOTE:  In some architectures, it may be necessary to take some
-      memory from the beginning of this region for vectors or for a
-      page table. In such cases, CONFIG_PAGING_LOCKED_P/VBASE should
-      take that into consideration to prevent overlapping the locked
-      memory region and the system data at the beginning of SRAM.
-    CONFIG_PAGING_NPPAGED - This is the number of physical pages
-      available to support the paged text region.  This paged region
-      begins at (CONFIG_PAGING_LOCKED_PBASE + CONFIG_PAGING_PAGESIZE*CONFIG_PAGING_NPPAGED)
-      and continues until (CONFIG_PAGING_LOCKED_PBASE + CONFIG_PAGING_PAGESIZE*(CONFIG_PAGING_NLOCKED +
-      CONFIG_PAGING_NPPAGED)
-    CONFIG_PAGING_NVPAGED - This actual size of the paged text region
-      (in pages).  This is also the number of virtual pages required to
-      support the entire paged region. The on-demand paging feature is
-      intended to support only the case where the virtual paged text
-      area is much larger the available physical pages.  Otherwise, why
-      would you enable on-demand paging?
-    CONFIG_PAGING_NDATA - This is the number of data pages in the memory
-      map.  The data region will extend to the end of RAM unless overridden
-      by a setting in the configuration file.
-      NOTE:  In some architectures, it may be necessary to take some memory
-      from the end of RAM for page tables or other system usage.  The
-      configuration settings and linker directives must be cognizant of that:
-      CONFIG_PAGING_NDATA should be defined to prevent the data region from
-      extending all the way to the end of memory.
-    CONFIG_PAGING_DEFPRIO - The default, minimum priority of the page fill
-      worker thread.  The priority of the page fill work thread will be boosted
-      boosted dynmically so that it matches the priority of the task on behalf
-      of which it peforms the fill.  This defines the minimum priority that
-      will be used. Default: 50.
-    CONFIG_PAGING_STACKSIZE - Defines the size of the allocated stack
-      for the page fill worker thread. Default: 1024.
-    CONFIG_PAGING_BLOCKINGFILL - The architecture specific up_fillpage()
-      function may be blocking or non-blocking.  If defined, this setting
-      indicates that the up_fillpage() implementation will block until the
-      transfer is completed. Default:  Undefined (non-blocking).
-    CONFIG_PAGING_WORKPERIOD - The page fill worker thread will wake periodically
-      even if there is no mapping to do.  This selection controls that wake-up
-      period (in microseconds).  This wake-up a failsafe that will handle any
-      cases where a single is lost (that would really be a bug and shouldn't
-      happen!) and also supports timeouts for case of non-blocking, asynchronous
-      fills (see CONFIG_PAGING_TIMEOUT_TICKS).
-    CONFIG_PAGING_TIMEOUT_TICKS - If defined, the implementation will monitor
-      the (asynchronous) page fill logic.  If the fill takes longer than this
-      number if microseconds, then a fatal error will be declared.
-      Default: No timeouts monitored.
-
-    Some architecture-specific settings.  Defaults are architecture specific.
-    If you don't know what you are doing, it is best to leave these undefined
-    and try the system defaults:
-
-    CONFIG_PAGING_VECPPAGE - This the physical address of the page in
-      memory to be mapped to the vector address.
-    CONFIG_PAGING_VECL2PADDR - This is the physical address of the L2
-      page table entry to use for the vector mapping.
-    CONFIG_PAGING_VECL2VADDR - This is the virtual address of the L2
-      page table entry to use for the vector mapping.
-    CONFIG_PAGING_BINPATH - If CONFIG_PAGING_BINPATH is defined, then it
-      is the full path to a file on a mounted file system that contains
-      a binary image of the NuttX executable.  Pages will be filled by
-      reading from offsets into this file that correspond to virtual
-      fault addresses.
-    CONFIG_PAGING_MOUNTPT - If CONFIG_PAGING_BINPATH is defined, additional
-      options may be provided to control the initialization of underlying
-      devices. CONFIG_PAGING_MOUNTPT identifies the mountpoint to be used
-      if a device is mounted.
-    CONFIG_PAGING_MINOR - Some mount operations require a "minor" number
-      to identify the specific device instance. Default: 0
-    CONFIG_PAGING_SDSLOT - If CONFIG_PAGING_BINPATH is defined, additional
-      options may be provided to control the initialization of underlying
-      devices. CONFIG_PAGING_SDSLOT identifies the slot number of the SD
-      device to initialize. This must be undefined if SD is not being used.
-      This should be defined to be zero for the typical device that has
-      only a single slot (See CONFIG_MMCSD_NSLOTS). If defined,
-      CONFIG_PAGING_SDSLOT will instruct certain board-specific logic to
-      initialize the media in this SD slot.
-    CONFIG_PAGING_M25PX - Use the m25px.c FLASH driver.  If this is selected,
-      then the MTD interface to the M25Px device will be used to support
-      paging.
-    CONFIG_PAGING_AT45DB - Use the at45db.c FLASH driver.  If this is selected,
-      then the MTD interface to the Atmel AT45DB device will be used to support
-      paging.
-    CONFIG_PAGING_BINOFFSET - If CONFIG_PAGING_M25PX or is CONFIG_PAGING_AT45DB
-      defined then CONFIG_PAGING_BINOFFSET will be used to specify the offset
-      in bytes into the FLASH device where the NuttX binary image is located.
-      Default: 0
-    CONFIG_PAGING_SPIPORT - If CONFIG_PAGING_M25PX CONFIG_PAGING_AT45DB is
-       defined and the device has multiple SPI busses (ports), then this
-      configuration should be set to indicate which SPI port the device is
-      connected. Default: 0
-
-  The following can be used to disable categories of APIs supported
-  by the OS.  If the compiler supports weak functions, then it
-  should not be necessary to disable functions unless you want to
-  restrict usage of those APIs.
-
-  There are certain dependency relationships in these features.
-
-    o mq_notify logic depends on signals to awaken tasks
-      waiting for queues to become full or empty.
-    o pthread_condtimedwait() depends on signals to wake
-      up waiting tasks.
-
-    CONFIG_DISABLE_CLOCK, CONFIG_DISABLE_POSIX_TIMERS, CONFIG_DISABLE_PTHREAD.
-    CONFIG_DISABLE_SIGNALS, CONFIG_DISABLE_MQUEUE, CONFIG_DISABLE_MOUNTPOUNT,
-    CONFIG_DISABLE_ENVIRON, CONFIG_DISABLE_POLL
-
-  Misc libc settings
-
-    CONFIG_NOPRINTF_FIELDWIDTH - sprintf-related logic is a little smaller
-      if we do not support fieldwidthes
-    CONFIG_LIBC_FLOATINGPOINT - By default, floating point support in printf,
-      sscanf, etc. is disabled.
-    CONFIG_LIBC_STRERROR - strerror() is useful because it decodes 'errno'
-      values into a human readable strings.  But it can also require
-      a lot of memory.  If this option is selected, strerror() will still
-      exist in the build but it will not decode error values.  This option
-      should be used by other logic to decide if it should use strerror() or
-      not.  For example, the NSH application will not use strerror() if this
-      option is not selected; perror() will not use strerror() is this option
-      is not selected (see also CONFIG_NSH_STRERROR).
-    CONFIG_LIBC_STRERROR_SHORT - If this option is selected, then strerror()
-      will use a shortened string when it decodes the error.  Specifically,
-      strerror() is simply use the string that is the common name for the
-      error.  For example, the 'errno' value of 2 will produce the string
-      "No such file or directory" if CONFIG_LIBC_STRERROR_SHORT is not
-      defined but the string "ENOENT" if CONFIG_LIBC_STRERROR_SHORT is
-      defined.
-    CONFIG_LIBC_PERROR_STDOUT - POSIX requires that perror() provide its output
-      on stderr.  This option may be defined, however, to provide perror() output
-      that is serialized with other stdout messages.
-
-  Allow for architecture optimized implementations
-
-    The architecture can provide optimized versions of the
-    following to improve system performance
-
-      CONFIG_ARCH_MEMCPY, CONFIG_ARCH_MEMCMP, CONFIG_ARCH_MEMMOVE
-      CONFIG_ARCH_MEMSET, CONFIG_ARCH_STRCMP, CONFIG_ARCH_STRCPY
-      CONFIG_ARCH_STRNCPY, CONFIG_ARCH_STRLEN, CONFIG_ARCH_STRNLEN
-      CONFIG_ARCH_BZERO
-
-  If CONFIG_ARCH_MEMCPY is not selected, then you make also select Daniel
-  Vik's optimized implementation of memcpy():
-
-    CONFIG_MEMCPY_VIK - Select this option to use the optimized memcpy()
-      function by Daniel Vik.  Select this option for improved performance
-      at the expense of increased size. See licensing information in the
-      top-level COPYING file.  Default: n
-
-  And if CONFIG_MEMCPY_VIK is selected, the following tuning options are available:
-
-    CONFIG_MEMCPY_PRE_INC_PTRS - Use pre-increment of pointers. Default is
-      post increment of pointers.
-
-    CONFIG_MEMCPY_INDEXED_COPY - Copying data using array indexing. Using
-      this option, disables the CONFIG_MEMCPY_PRE_INC_PTRS option.
-
-    CONFIG_MEMCPY_64BIT - Compiles memcpy for architectures that suppport
-      64-bit operations efficiently.
-
-  If CONFIG_ARCH_MEMSET is not selected, then the following option is
-  also available:
-
-    CONFIG_MEMSET_OPTSPEED - Select this option to use a version of memcpy()
-      optimized for speed. Default: memcpy() is optimized for size.
-
-  And if CONFIG_MEMSET_OPTSPEED is selected, the following tuning option is
-  available:
-
-    CONFIG_MEMSET_64BIT - Compiles memset() for architectures that suppport
-      64-bit operations efficiently.
-
-  The architecture may provide custom versions of certain standard header
-  files:
-
-    CONFIG_ARCH_STDBOOL_H - The stdbool.h header file can be found at
-      nuttx/include/stdbool.h. However, that header includes logic to redirect
-      the inclusion of an architecture specific header file like:
-
-        #ifdef CONFIG_ARCH_STDBOOL_H
-        #  include <arch/stdbool.h>
-        #else
-        ...
-        #endif
-
-      Recall that that include path, include/arch, is a symbolic link and
-      will refer to a version of stdbool.h at nuttx/arch/<architecture>/include/stdbool.h.
-
-    CONFIG_ARCH_STDINT_H - Similar logic exists for the stdint.h header
-      file can also be found at nuttx/include/stdint.h.
-
-        #ifdef CONFIG_ARCH_STDBOOL_H
-        #  include <arch/stdinit.h>
-        #else
-        ...
-        #endif
-
-    CONFIG_ARCH_MATH_H - There is also a re-directing version of math.h in
-      the source tree. However, it resides out-of-the-way at include/nuttx/math.h
-      because it conflicts too often with the system math.h. If CONFIG_ARCH_MATH_H=y
-      is  defined, however, the top-level makefile will copy the redirecting
-      math.h header file from include/nuttx/math.h to include/math.h. math.h
-      will then include the architecture-specific version of math.h that you
-      must provide at nuttx/arch/>architecture</include/math.h.
-
-        #ifdef CONFIG_ARCH_MATH_H
-        #  include <arch/math.h>
-        #endif
-
-      So for the architectures that define CONFIG_ARCH_MATH_H=y, include/math.h
-      will be the redirecting math.h header file; for the architectures that
-      don't select CONFIG_ARCH_MATH_H, the redirecting math.h header file will
-      stay out-of-the-way in include/nuttx/.
-
-    CONFIG_ARCH_FLOAT_H
-      If you enable the generic, built-in math library, then that math library
-      will expect your toolchain to provide the standard float.h header file.
-      The float.h header file defines the properties of your floating point
-      implementation.  It would always be best to use your toolchain's float.h
-      header file but if none is avaiable, a default float.h header file will
-      provided if this option is selected.  However, there is no assurance that
-      the settings in this float.h are actually correct for your platform!
-
-    CONFIG_ARCH_STDARG_H - There is also a redirecting version of stdarg.h in
-      the source tree as well. It also resides out-of-the-way at include/nuttx/stdarg.h.
-      This is because you should normally use your toolchain's stdarg.h file. But
-      sometimes, your toolchain's stdarg.h file may have other header file
-      dependencies and so may not be usable in the NuttX build environment. In
-      those cases, you may have to create a architecture-specific stdarg.h header
-      file at nuttx/arch/>architecture</include/stdarg.h
-
-      If CONFIG_ARCH_STDARG_H=y is defined, the top-level makefile will copy the
-      re-directing stdarg.h header file from include/nuttx/stdarg.h to
-      include/stdarg.h. So for the architectures that cannot use their toolchain's
-      stdarg.h file, they can use this alternative by defining CONFIG_ARCH_STDARG_H=y
-      and providing. If CONFIG_ARCH_STDARG_H, is not defined, then the stdarg.h
-      header file will stay out-of-the-way in include/nuttx/.
-
-    CONFIG_ARCH_ROMGETC - In Harvard architectures, data accesses and
-      instruction accesses occur on different busses, perhaps
-      concurrently.  All data accesses are performed on the data bus
-      unless special machine instructions are used to read data
-      from the instruction address space.  Also, in the typical
-      MCU, the available SRAM data memory is much smaller that the
-      non-volatile FLASH instruction memory.  So if the application
-      requires many constant strings, the only practical solution may
-      be to store those constant strings in FLASH memory where they
-      can only be accessed using architecture-specific machine
-      instructions.
-
-      If CONFIG_ARCH_ROMGETC is defined, then the architecture logic
-      must export the function up_romgetc().  up_romgetc() will simply
-      read one byte of data from the instruction space.
-
-      If CONFIG_ARCH_ROMGETC, certain C stdio functions are effected:
-      (1) All format strings in printf, fprintf, sprintf, etc. are
-      assumed to lie in FLASH (string arguments for %s are still assumed
-      to reside in SRAM). And (2), the string argument to puts and fputs
-      is assumed to reside in FLASH.  Clearly, these assumptions may have
-      to modified for the particular needs of your environment.  There
-      is no "one-size-fits-all" solution for this problem.
-
-  Sizes of configurable things (0 disables)
-
-    CONFIG_MAX_TASKS - The maximum number of simultaneously
-      active tasks.  This value must be a power of two.
-    CONFIG_NPTHREAD_KEYS - The number of items of thread-
-      specific data that can be retained
-    CONFIG_NFILE_DESCRIPTORS - The maximum number of file
-      descriptors (one for each open)
-    CONFIG_NFILE_STREAMS - The maximum number of streams that
-      can be fopen'ed
-    CONFIG_NAME_MAX - Maximum number of bytes in a filename (not including
-      terminating null).  Default: 32
-    CONFIG_PATH_MAX - Maximum number of bytes in a pathname, including the
-      terminating null character.  Default: MIN(256,(4*CONFIG_NAME_MAX+1))
-    CONFIG_STDIO_BUFFER_SIZE - Size of the buffer to allocate
-      on fopen. (Only if CONFIG_NFILE_STREAMS > 0)
-    CONFIG_STDIO_LINEBUFFER - If standard C buffered I/O is enabled
-      (CONFIG_STDIO_BUFFER_SIZE > 0), then this option may be added
-      to force automatic, line-oriented flushing the output buffer
-      for putc(), fputc(), putchar(), puts(), fputs(), printf(),
-      fprintf(), and vfprintf().  When a newline is encountered in
-      the output string, the output buffer will be flushed.  This
-      (slightly) increases the NuttX footprint but supports the kind
-      of behavior that people expect for printf().
-    CONFIG_NUNGET_CHARS - Number of characters that can be
-      buffered by ungetc() (Only if CONFIG_NFILE_STREAMS > 0)
-    CONFIG_PREALLOC_MQ_MSGS - The number of pre-allocated message
-      structures.  The system manages a pool of preallocated
-      message structures to minimize dynamic allocations
-    CONFIG_PREALLOC_IGMPGROUPS - Pre-allocated IGMP groups are used
-      only if needed from interrupt level group created (by the IGMP server).
-      Default: 4.
-    CONFIG_MQ_MAXMSGSIZE - Message structures are allocated with
-      a fixed payload size given by this settin (does not include
-      other message structure overhead.
-    CONFIG_PREALLOC_WDOGS - The number of pre-allocated watchdog
-      structures.  The system manages a pool of preallocated
-      watchdog structures to minimize dynamic allocations
-    CONFIG_DEV_PIPE_SIZE - Size, in bytes, of the buffer to allocated
-      for pipe and FIFO support
-
-  Filesystem configuration
-
-    CONFIG_FS_FAT - Enable FAT filesystem support
-    CONFIG_FAT_LCNAMES - Enable use of the NT-style upper/lower case 8.3
-      file name support.
-    CONFIG_FAT_LFN - Enable FAT long file names.  NOTE:  Microsoft claims
-      patents on FAT long file name technology.  Please read the
-      disclaimer in the top-level COPYING file and only enable this
-      feature if you understand these issues.
-    CONFIG_FAT_MAXFNAME - If CONFIG_FAT_LFN is defined, then the
-      default, maximum long file name is 255 bytes.  This can eat up
-      a lot of memory (especially stack space).  If you are willing
-      to live with some non-standard, short long file names, then
-      define this value.  A good choice would be the same value as
-      selected for CONFIG_NAME_MAX which will limit the visibility
-      of longer file names anyway.
-    CONFIG_FS_FATTIME: Support FAT date and time. NOTE:  There is not
-      much sense in supporting FAT date and time unless you have a
-      hardware RTC or other way to get the time and date.
-    CONFIG_FS_NXFFS: Enable NuttX FLASH file system (NXFF) support.
-    CONFIG_NXFFS_ERASEDSTATE: The erased state of FLASH.
-      This must have one of the values of 0xff or 0x00.
-      Default: 0xff.
-    CONFIG_NXFFS_PACKTHRESHOLD: When packing flash file data,
-      don't both with file chunks smaller than this number of data bytes.
-      Default: 32.
-    CONFIG_NXFFS_MAXNAMLEN: The maximum size of an NXFFS file name.
-      Default: 255.
-    CONFIG_NXFFS_PACKTHRESHOLD: When packing flash file data,
-      don't both with file chunks smaller than this number of data bytes.
-      Default: 32.
-    CONFIG_NXFFS_TAILTHRESHOLD: clean-up can either mean
-      packing files together toward the end of the file or, if file are
-      deleted at the end of the file, clean up can simply mean erasing
-      the end of FLASH memory so that it can be re-used again.  However,
-      doing this can also harm the life of the FLASH part because it can
-      mean that the tail end of the FLASH is re-used too often. This
-      threshold determines if/when it is worth erased the tail end of FLASH
-      and making it available for re-use (and possible over-wear).
-      Default: 8192.
-    CONFIG_FS_ROMFS - Enable ROMFS filesystem support
-    CONFIG_NFS - Enable Network File System (NFS) client file system support.
-      Provided support is version 3 using UDP.  In addition to common
-      prerequisites for mount-able file systems in general, this option
-      requires UDP networking support; this would include CONFIG_NETand
-      CONFIG_NET_UDP at a minimum.
-    CONFIG_FS_RAMMAP - For file systems that do not support XIP, this
-      option will enable a limited form of memory mapping that is
-      implemented by copying whole files into memory.
-
-  RTC
-
-    CONFIG_RTC - Enables general support for a hardware RTC.  Specific
-      architectures may require other specific settings.
-    CONFIG_RTC_DATETIME - There are two general types of RTC:  (1) A simple
-      battery backed counter that keeps the time when power is down, and (2)
-       A full date / time RTC the provides the date and time information, often
-      in BCD format.  If CONFIG_RTC_DATETIME is selected, it specifies this
-      second kind of RTC. In this case, the RTC is used to "seed" the normal
-      NuttX timer and the NuttX system timer provides for higher resoution
-      time.
-    CONFIG_RTC_HIRES - If CONFIG_RTC_DATETIME not selected, then the simple,
-      battery backed counter is used.  There are two different implementations
-      of such simple counters based on the time resolution of the counter:
-      The typical RTC keeps time to resolution of 1 second, usually
-      supporting a 32-bit time_t value.  In this case, the RTC is used to
-      "seed" the normal NuttX timer and the NuttX timer provides for higher
-      resoution time. If CONFIG_RTC_HIRES is enabled in the NuttX configuration,
-      then the RTC provides higher resolution time and completely replaces the
-      system timer for purpose of date and time.
-    CONFIG_RTC_FREQUENCY - If CONFIG_RTC_HIRES is defined, then the frequency
-      of the high resolution RTC must be provided.  If CONFIG_RTC_HIRES is
-      not defined, CONFIG_RTC_FREQUENCY is assumed to be one.
-    CONFIG_RTC_ALARM - Enable if the RTC hardware supports setting of an
-      alarm.  A callback function will be executed when the alarm goes off
-
-  CAN driver
-
-    CONFIG_CAN - Enables CAN support (one or both of CONFIG_STM32_CAN1 or
-      CONFIG_STM32_CAN2 must also be defined)
-    CONFIG_CAN_EXTID - Enables support for the 29-bit extended ID.  Default
-      Standard 11-bit IDs.
-    CONFIG_CAN_FIFOSIZE - The size of the circular buffer of CAN messages.
-      Default: 8
-    CONFIG_CAN_NPENDINGRTR - The size of the list of pending RTR requests.
-      Default: 4
-    CONFIG_CAN_LOOPBACK - A CAN driver may or may not support a loopback
-      mode for testing. If the driver does support loopback mode, the setting
-      will enable it. (If the driver does not, this setting will have no effect).
-
-  SPI driver
-
-    CONFIG_SPI_OWNBUS - Set if there is only one active device
-      on the SPI bus.  No locking or SPI configuration will be performed.
-      It is not necessary for clients to lock, re-configure, etc..
-    CONFIG_SPI_EXCHANGE - Driver supports a single exchange method
-      (vs a recvblock() and sndblock ()methods)
-
-  SPI-based MMC/SD driver
-
-    CONFIG_MMCSD_NSLOTS - Number of MMC/SD slots supported by the
-      driver. Default is one.
-    CONFIG_MMCSD_READONLY -  Provide read-only access.  Default is
-      Read/Write
-    CONFIG_MMCSD_SPICLOCK - Maximum SPI clock to drive MMC/SD card.
-      Default is 20MHz.
-
-  SDIO/SDHC driver:
-
-    CONFIG_SDIO_DMA - SDIO driver supports DMA
-    CONFIG_SDIO_MUXBUS - Set this SDIO interface if the SDIO interface
-      or hardware resources are shared with other drivers.
-    CONFIG_SDIO_WIDTH_D1_ONLY - Select 1-bit transfer mode.  Default:
-      4-bit transfer mode.
-    CONFIG_MMCSD_MULTIBLOCK_DISABLE - Use only the single block transfer method.
-      This setting is used to work around buggy SDIO drivers that cannot handle
-      multiple block transfers.
-
-  SDIO-based MMC/SD driver
-
-    CONFIG_FS_READAHEAD - Enable read-ahead buffering
-    CONFIG_FS_WRITEBUFFER - Enable write buffering
-    CONFIG_MMCSD_MMCSUPPORT - Enable support for MMC cards
-    CONFIG_MMCSD_HAVECARDDETECT - SDIO driver card detection is
-      100% accurate
-
-  RiT P14201 OLED driver
-
-    CONFIG_LCD_P14201 - Enable P14201 support
-    CONFIG_P14201_SPIMODE - Controls the SPI mode
-    CONFIG_P14201_FREQUENCY - Define to use a different bus frequency
-    CONFIG_P14201_NINTERFACES - Specifies the number of physical P14201
-      devices that will be supported.
-    CONFIG_P14201_FRAMEBUFFER - If defined, accesses will be performed
-      using an in-memory copy of the OLEDs GDDRAM.  This cost of this
-      buffer is 128 * 96 / 2 = 6Kb.  If this is defined, then the driver
-      will be fully functional. If not, then it will have the following
-      limitations:
-      - Reading graphics memory cannot be supported, and
-      - All pixel writes must be aligned to byte boundaries.
-      The latter limitation effectively reduces the 128x96 disply to 64x96.
-
-  Nokia 6100 Configuration Settings:
-
-    CONFIG_NOKIA6100_SPIMODE - Controls the SPI mode
-    CONFIG_NOKIA6100_FREQUENCY - Define to use a different bus frequency
-    CONFIG_NOKIA6100_NINTERFACES - Specifies the number of physical Nokia
-      6100 devices that will be supported.
-    CONFIG_NOKIA6100_BPP - Device supports 8, 12, and 16 bits per pixel.
-    CONFIG_NOKIA6100_S1D15G10 - Selects the Epson S1D15G10 display controller
-    CONFIG_NOKIA6100_PCF8833 - Selects the Phillips PCF8833 display controller
-    CONFIG_NOKIA6100_BLINIT - Initial backlight setting
-
-    The following may need to be tuned for your hardware:
-    CONFIG_NOKIA6100_INVERT - Display inversion, 0 or 1, Default: 1
-    CONFIG_NOKIA6100_MY - Display row direction, 0 or 1, Default: 0
-    CONFIG_NOKIA6100_MX - Display column direction, 0 or 1, Default: 1
-    CONFIG_NOKIA6100_V - Display address direction, 0 or 1, Default: 0
-    CONFIG_NOKIA6100_ML - Display scan direction, 0 or 1, Default: 0
-    CONFIG_NOKIA6100_RGBORD - Display RGB order, 0 or 1, Default: 0
-
-    Required LCD driver settings:
-    CONFIG_LCD_NOKIA6100 - Enable Nokia 6100 support
-    CONFIG_LCD_MAXCONTRAST - must be 63 with the Epson controller and 127 with
-      the Phillips controller.
-    CONFIG_LCD_MAXPOWER - Maximum value of backlight setting.  The backlight
-      control is managed outside of the 6100 driver so this value has no
-      meaning to the driver.  Board-specific logic may place restrictions on
-      this value.
-
-  Input Devices
-
-    CONFIG_INPUT
-      Enables general support for input devices
-
-    CONFIG_INPUT_TSC2007
-      If CONFIG_INPUT is selected, then this setting will enable building
-      of the TI TSC2007 touchscreen driver.
-    CONFIG_TSC2007_MULTIPLE
-      Normally only a single TI TSC2007 touchscreen is used.  But if
-      there are multiple TSC2007 touchscreens, this setting will enable
-      multiple touchscreens with the same driver.
-
-    CONFIG_INPUT_STMPE811
-      Enables support for the STMPE811 driver (Needs CONFIG_INPUT)
-    CONFIG_STMPE811_SPI
-      Enables support for the SPI interface (not currenly supported)
-    CONFIG_STMPE811_I2C
-      Enables support for the I2C interface
-    CONFIG_STMPE811_MULTIPLE
-      Can be defined to support multiple STMPE811 devices on board.
-    CONFIG_STMPE811_ACTIVELOW
-      Interrupt is generated by an active low signal (or falling edge).
-    CONFIG_STMPE811_EDGE
-      Interrupt is generated on an edge (vs. on the active level)
-    CONFIG_STMPE811_NPOLLWAITERS
-      Maximum number of threads that can be waiting on poll() (ignored if
-      CONFIG_DISABLE_POLL is set).
-    CONFIG_STMPE811_TSC_DISABLE
-      Disable driver touchscreen functionality.
-    CONFIG_STMPE811_ADC_DISABLE
-      Disable driver ADC functionality.
-    CONFIG_STMPE811_GPIO_DISABLE
-      Disable driver GPIO functionlaity.
-    CONFIG_STMPE811_GPIOINT_DISABLE
-      Disable driver GPIO interrupt functionality (ignored if GPIO
-      functionality is disabled).
-    CONFIG_STMPE811_SWAPXY
-      Reverse the meaning of X and Y to handle different LCD orientations.
-    CONFIG_STMPE811_TEMP_DISABLE
-      Disable driver temperature sensor functionality.
-    CONFIG_STMPE811_REGDEBUG
-      Enabled very low register-level debug output.  Requires CONFIG_DEBUG.
-    CONFIG_STMPE811_THRESHX and CONFIG_STMPE811_THRESHY
-      STMPE811 touchscreen data comes in a a very high rate.  New touch positions
-      will only be reported when the X or Y data changes by these thresholds.
-      This trades reduces data rate for some loss in dragging accuracy.  The
-      STMPE811 is configure for 12-bit values so the raw ranges are 0-4095. So
-      for example, if your display is 320x240, then THRESHX=13 and THRESHY=17
-      would correspond to one pixel.  Default: 12
-
-  Analog Devices
-
-    CONFIG_DAC
-      Enables general support for Digital-to-Analog conversion devices.
-    CONFIG_ADC
-      Enables general support for Analog-to-Digital conversion devices.
-    CONFIG_ADC_ADS125X
-      Adds support for the TI ADS 125x ADC.
-
-  ENC28J60 Ethernet Driver Configuration Settings:
-
-    CONFIG_ENC28J60 - Enabled ENC28J60 support
-    CONFIG_ENC28J60_SPIMODE - Controls the SPI mode
-    CONFIG_ENC28J60_FREQUENCY - Define to use a different bus frequency
-    CONFIG_ENC28J60_NINTERFACES - Specifies the number of physical ENC28J60
-      devices that will be supported.
-    CONFIG_ENC28J60_STATS - Collect network statistics
-    CONFIG_ENC28J60_HALFDUPPLEX - Default is full duplex
-
-  Networking support via uIP
-
-    CONFIG_NET - Enable or disable all network features
-    CONFIG_NET_NOINTS --  CONFIG_NET_NOINT indicates that uIP not called from
-      the interrupt level.  If CONFIG_NET_NOINTS is defined, critical sections
-      will be managed with semaphores; Otherwise, it assumed that uIP will be
-      called from interrupt level handling and critical sections will be
-      managed by enabling and disabling interrupts.
-    CONFIG_NET_MULTIBUFFER - Traditionally, uIP has used a single buffer
-      for all incoming and outgoing traffic.  If this configuration is
-      selected, then the driver can manage multiple I/O buffers and can,
-      for example, be filling one input buffer while sending another
-      output buffer.  Or, as another example, the driver may support
-      queuing of concurrent input/ouput and output transfers for better
-      performance.
-    CONFIG_NET_IPv6 - Build in support for IPv6
-    CONFIG_NSOCKET_DESCRIPTORS - Maximum number of socket descriptors
-    per task/thread.
-    CONFIG_NET_NACTIVESOCKETS - Maximum number of concurrent socket
-      operations (recv, send, etc.).  Default: CONFIG_NET_TCP_CONNS+CONFIG_NET_UDP_CONNS
-    CONFIG_NET_SOCKOPTS - Enable or disable support for socket options
-
-    CONFIG_NET_BUFSIZE - uIP buffer size
-    CONFIG_NET_TCPURGDATA - Determines if support for TCP urgent data
-      notification should be compiled in. Urgent data (out-of-band data)
-      is a rarely used TCP feature that is very seldom would be required.
-    CONFIG_NET_TCP - TCP support on or off
-    CONFIG_NET_TCP_CONNS - Maximum number of TCP connections (all tasks)
-    CONFIG_NET_MAX_LISTENPORTS - Maximum number of listening TCP ports (all tasks)
-    CONFIG_NET_TCP_READAHEAD_BUFSIZE - Size of TCP read-ahead buffers
-    CONFIG_NET_NTCP_READAHEAD_BUFFERS - Number of TCP read-ahead buffers
-      (may be zero to disable TCP/IP read-ahead buffering)
-    CONFIG_NET_TCP_RECVDELAY - Delay (in deciseconds) after a TCP/IP packet
-      is received.  This delay may allow catching of additional packets
-      when TCP/IP read-ahead is disabled.  Default: 0
-    CONFIG_NET_TCPBACKLOG - Incoming connections pend in a backlog until
-      accept() is called. The size of the backlog is selected when listen()
-      is called.
-    CONFIG_NET_UDP - UDP support on or off
-    CONFIG_NET_UDP_CHECKSUMS - UDP checksums on or off
-    CONFIG_NET_UDP_CONNS - The maximum amount of concurrent UDP
-      connections
-    CONFIG_NET_ICMP - Enable minimal ICMP support. Includes built-in support
-      for sending replies to received ECHO (ping) requests.
-    CONFIG_NET_ICMP_PING - Provide interfaces to support application level
-      support for sending ECHO (ping) requests and associating ECHO
-      replies.
-    CONFIG_NET_IGMP - Enable IGMPv2 client support.
-    CONFIG_PREALLOC_IGMPGROUPS - Pre-allocated IGMP groups are used
-      only if needed from interrupt level group created (by the IGMP server).
-      Default: 4.
-    CONFIG_NET_PINGADDRCONF - Use "ping" packet for setting IP address
-    CONFIG_NET_STATISTICS - uIP statistics on or off
-    CONFIG_NET_RECEIVE_WINDOW - The size of the advertised receiver's
-      window
-    CONFIG_NET_ARPTAB_SIZE - The size of the ARP table
-    CONFIG_NET_ARP_IPIN - Harvest IP/MAC address mappings from the ARP table
-      from incoming IP packets.
-    CONFIG_NET_BROADCAST - Incoming UDP broadcast support
-    CONFIG_NET_MULTICAST - Outgoing multi-cast address support
-
-  SLIP Driver.  SLIP supports point-to-point IP communications over a serial
-    port.  The default data link layer for uIP is Ethernet. If CONFIG_NET_SLIP
-    is defined in the NuttX configuration file, then SLIP will be supported.
-    The basic differences between the SLIP and Ethernet configurations is that
-    when SLIP is selected:
-
-    * The link level header (that comes before the IP header) is omitted.
-    * All MAC address processing is suppressed.
-    * ARP is disabled.
-
-    If CONFIG_NET_SLIP is not selected, then Ethernet will be used (there is
-    no need to define anything special in the configuration file to use
-    Ethernet -- it is the default).
-
-    CONFIG_NET_SLIP -- Enables building of the SLIP driver. SLIP requires
-      at least one IP protocols selected and the following additional
-      network settings: CONFIG_NET_NOINTS and CONFIG_NET_MULTIBUFFER.
-      CONFIG_NET_BUFSIZE *must* be set to 296.  Other optional configuration
-      settings that affect the SLIP driver: CONFIG_NET_STATISTICS.
-      Default: Ethernet
-
-    If SLIP is selected, then the following SLIP options are available:
-
-    CONFIG_CLIP_NINTERFACES -- Selects the number of physical SLIP
-      interfaces to support.  Default: 1
-    CONFIG_SLIP_STACKSIZE -- Select the stack size of the SLIP RX and
-      TX tasks.  Default: 2048
-    CONFIG_SLIP_DEFPRIO - The priority of the SLIP RX and TX tasks.
-      Default: 128
-
-  UIP Network Utilities
-
-    CONFIG_NET_DHCP_LIGHT - Reduces size of DHCP
-    CONFIG_NET_RESOLV_ENTRIES - Number of resolver entries
-    CONFIG_NET_RESOLV_MAXRESPONSE - This setting determines the maximum
-      size of response message that can be received by the DNS resolver.
-      The default is 96 but may need to be larger on enterprise networks
-      (perhaps 176).
-
-  THTTPD
-
-    CONFIG_THTTPD_PORT - THTTPD Server port number
-    CONFIG_THTTPD_IPADDR - Server IP address (no host name)
-    CONFIG_THTTPD_SERVER_ADDRESS - SERVER_ADDRESS: response
-    CONFIG_THTTPD_SERVER_SOFTWARE - SERVER_SOFTWARE: response
-    CONFIG_THTTPD_PATH - Server working directory
-    CONFIG_THTTPD_CGI_PATH - Path to CGI executables
-    CONFIG_THTTPD_CGI_PATTERN - Only CGI programs matching this
-      pattern will be executed.  In fact, if this value is not defined
-      then no CGI logic will be built.
-    CONFIG_THTTPD_CGI_PRIORITY - Provides the priority of CGI child tasks
-    CONFIG_THTTPD_CGI_STACKSIZE - Provides the initial stack size of
-      CGI child task (will be overridden by the stack size in the NXFLAT
-      header)
-    CONFIG_THTTPD_CGI_BYTECOUNT - Byte output limit for CGI tasks.
-    CONFIG_THTTPD_CGI_TIMELIMIT - How many seconds to allow CGI programs
-      to run before killing them.
-    CONFIG_THTTPD_CHARSET- The default character set name to use with
-      text MIME types.
-    CONFIG_THTTPD_IOBUFFERSIZE -
-    CONFIG_THTTPD_INDEX_NAMES - A list of index filenames to check. The
-      files are searched for in this order.
-    CONFIG_AUTH_FILE - The file to use for authentication. If this is
-      defined then thttpd checks for this file in the local directory
-      before every fetch. If the file exists then authentication is done,
-      otherwise the fetch proceeds as usual. If you leave this undefined
-      then thttpd will not implement authentication at all and will not
-      check for auth files, which saves a bit of CPU time. A typical
-      value is ".htpasswd"
-    CONFIG_THTTPD_LISTEN_BACKLOG - The listen() backlog queue length.
-    CONFIG_THTTPD_LINGER_MSEC - How many milliseconds to leave a connection
-      open while doing a lingering close.
-    CONFIG_THTTPD_OCCASIONAL_MSEC - How often to run the occasional
-      cleanup job.
-    CONFIG_THTTPD_IDLE_READ_LIMIT_SEC - How many seconds to allow for
-     reading the initial request on a new connection.
-    CONFIG_THTTPD_IDLE_SEND_LIMIT_SEC - How many seconds before an
-      idle connection gets closed.
-    CONFIG_THTTPD_TILDE_MAP1 and CONFIG_THTTPD_TILDE_MAP2 - Tilde mapping.
-      Many URLs use ~username to indicate a user's home directory. thttpd
-       provides two options for mapping this construct to an  actual filename.
-      1) Map ~username to <prefix>/username. This is the recommended choice.
-        Each user gets a subdirectory in the main web tree, and the tilde
-        construct points there. The prefix could be something like "users",
-        or it could be empty.
-      2) Map ~username to <user's homedir>/<postfix>. The postfix would be
-        the name of a subdirectory off of the user's actual home dir,
-        something like "public_html".
-      You can also leave both options undefined, and thttpd will not do
-      anything special about tildes. Enabling both options is an error.
-      Typical values, if they're defined, are "users" for
-      CONFIG_THTTPD_TILDE_MAP1 and "public_html"forCONFIG_THTTPD_TILDE_MAP2.
-    CONFIG_THTTPD_GENERATE_INDICES
-    CONFIG_THTTPD_URLPATTERN - If defined, then it will be used to match
-      and verify referrers.
-
-  FTP Server
-
-    CONFIG_FTPD_VENDORID - The vendor name to use in FTP communications.
-      Default: "NuttX"
-    CONFIG_FTPD_SERVERID - The server name to use in FTP communications.
-      Default: "NuttX FTP Server"
-    CONFIG_FTPD_CMDBUFFERSIZE - The maximum size of one command.  Default:
-      128 bytes.
-    CONFIG_FTPD_DATABUFFERSIZE - The size of the I/O buffer for data
-      transfers.  Default: 512 bytes.
-    CONFIG_FTPD_WORKERSTACKSIZE - The stacksize to allocate for each
-      FTP daemon worker thread.  Default:  2048 bytes.
-
-    Other required configuration settings:  Of course TCP networking support
-    is required.  But here are a couple that are less obvious:
-
-      CONFIG_DISABLE_PTHREAD - pthread support is required
-      CONFIG_DISABLE_POLL - poll() support is required
-
-  USB device controller driver
-
-    CONFIG_USBDEV - Enables USB device support
-    CONFIG_USBDEV_COMPOSITE
-      Enables USB composite device support
-    CONFIG_USBDEV_ISOCHRONOUS - Build in extra support for isochronous
-      endpoints
-    CONFIG_USBDEV_DUALSPEED -Hardware handles high and full speed
-      operation (USB 2.0)
-    CONFIG_USBDEV_SELFPOWERED - Will cause USB features to indicate
-      that the device is self-powered
-    CONFIG_USBDEV_MAXPOWER - Maximum power consumption in mA
-    CONFIG_USBDEV_TRACE - Enables USB tracing for debug
-    CONFIG_USBDEV_TRACE_NRECORDS - Number of trace entries to remember
-
-  USB host controller driver
-
-    CONFIG_USBHOST
-      Enables USB host support
-    CONFIG_USBHOST_NPREALLOC
-      Number of pre-allocated class instances
-    CONFIG_USBHOST_BULK_DISABLE
-      On some architectures, selecting this setting will reduce driver size
-      by disabling bulk endpoint support
-    CONFIG_USBHOST_INT_DISABLE
-      On some architectures, selecting this setting will reduce driver size
-      by disabling interrupt endpoint support
-    CONFIG_USBHOST_ISOC_DISABLE
-      On some architectures, selecting this setting will reduce driver size
-      by disabling isochronous endpoint support
-
-  USB host HID class driver. Requires CONFIG_USBHOST=y,
-    CONFIG_USBHOST_INT_DISABLE=n, CONFIG_NFILE_DESCRIPTORS > 0,
-    CONFIG_SCHED_WORKQUEUE=y, and CONFIG_DISABLE_SIGNALS=n.
-
-    CONFIG_HIDKBD_POLLUSEC
-      Device poll rate in microseconds. Default: 100 milliseconds.
-    CONFIG_HIDKBD_DEFPRIO
-      Priority of the polling thread.  Default: 50.
-    CONFIG_HIDKBD_STACKSIZE
-      Stack size for polling thread.  Default: 1024
-    CONFIG_HIDKBD_BUFSIZE
-      Scancode buffer size.  Default: 64.
-    CONFIG_HIDKBD_NPOLLWAITERS
-      If the poll() method is enabled, this defines the maximum number
-      of threads that can be waiting for keyboard events.  Default: 2.
-    CONFIG_HIDKBD_RAWSCANCODES
-      If set to y no conversion will be made on the raw keyboard scan
-      codes.  Default: ASCII conversion.
-    CONFIG_HIDKBD_ALLSCANCODES'
-      If set to y all 231 possible scancodes will be converted to
-      something.  Default:  104 key US keyboard.
-    CONFIG_HIDKBD_NODEBOUNCE
-      If set to y normal debouncing is disabled.  Default:
-      Debounce enabled (No repeat keys).
-
-  USB host mass storage class driver. Requires CONFIG_USBHOST=y,
-    CONFIG_USBHOST_BULK_DISABLE=n, CONFIG_NFILE_DESCRIPTORS > 0,
-    and CONFIG_SCHED_WORKQUEUE=y
-
-  USB serial device class driver (Prolific PL2303 Emulation)
-
-    CONFIG_PL2303
-      Enable compilation of the USB serial driver
-    CONFIG_PL2303_EPINTIN
-      The logical 7-bit address of a hardware endpoint that supports
-      interrupt IN operation
-    CONFIG_PL2303_EPBULKOUT
-      The logical 7-bit address of a hardware endpoint that supports
-      bulk OUT operation
-    CONFIG_PL2303_EPBULKIN
-      The logical 7-bit address of a hardware endpoint that supports
-      bulk IN operation
-    CONFIG_PL2303_NWRREQS and CONFIG_PL2303_NRDREQS
-      The number of write/read requests that can be in flight
-    CONFIG_PL2303_VENDORID and CONFIG_PL2303_VENDORSTR
-      The vendor ID code/string
-    CONFIG_PL2303_PRODUCTID and CONFIG_PL2303_PRODUCTSTR
-      The product ID code/string
-    CONFIG_PL2303_RXBUFSIZE and CONFIG_PL2303_TXBUFSIZE
-      Size of the serial receive/transmit buffers
-
-  USB serial device class driver (Standard CDC ACM class)
-
-    CONFIG_CDCACM
-      Enable compilation of the USB serial driver
-    CONFIG_CDCACM_COMPOSITE
-      Configure the CDC serial driver as part of a composite driver
-      (only if CONFIG_USBDEV_COMPOSITE is also defined)
-    CONFIG_CDCACM_IFNOBASE
-       If the CDC driver is part of a composite device, then this may need to
-      be defined to offset the CDC/ACM interface numbers so that they are
-      unique and contiguous.  When used with the Mass Storage driver, the
-      correct value for this offset is zero.
-    CONFIG_CDCACM_STRBASE
-      If the CDC driver is part of a composite device, then this may need to
-      be defined to offset the CDC/ACM string numbers so that they are
-      unique and contiguous.  When used with the Mass Storage driver, the
-      correct value for this offset is four (this value actuallly only needs
-      to be defined if names are provided for the Notification interface,
-      CONFIG_CDCACM_NOTIFSTR, or the data interface, CONFIG_CDCACM_DATAIFSTR).
-    CONFIG_CDCACM_EP0MAXPACKET
-      Endpoint 0 max packet size. Default 64.
-    CONFIG_CDCACM_EPINTIN
-      The logical 7-bit address of a hardware endpoint that supports
-      interrupt IN operation.  Default 2.
-    CONFIG_CDCACM_EPINTIN_FSSIZE
-      Max package size for the interrupt IN endpoint if full speed mode.
-      Default 64.
-    CONFIG_CDCACM_EPINTIN_HSSIZE
-      Max package size for the interrupt IN endpoint if high speed mode.
-      Default 64.
-    CONFIG_CDCACM_EPBULKOUT
-      The logical 7-bit address of a hardware endpoint that supports
-      bulk OUT operation
-    CONFIG_CDCACM_EPBULKOUT_FSSIZE
-      Max package size for the bulk OUT endpoint if full speed mode.
-      Default 64.
-    CONFIG_CDCACM_EPBULKOUT_HSSIZE
-      Max package size for the bulk OUT endpoint if high speed mode.
-      Default 512.
-    CONFIG_CDCACM_EPBULKIN
-      The logical 7-bit address of a hardware endpoint that supports
-      bulk IN operation
-    CONFIG_CDCACM_EPBULKIN_FSSIZE
-      Max package size for the bulk IN endpoint if full speed mode.
-      Default 64.
-    CONFIG_CDCACM_EPBULKIN_HSSIZE
-      Max package size for the bulk IN endpoint if high speed mode.
-      Default 512.
-    CONFIG_CDCACM_NWRREQS and CONFIG_CDCACM_NRDREQS
-      The number of write/read requests that can be in flight.
-      CONFIG_CDCACM_NWRREQS includes write requests used for both the
-      interrupt and bulk IN endpoints.  Default 4.
-    CONFIG_CDCACM_VENDORID and CONFIG_CDCACM_VENDORSTR
-      The vendor ID code/string.  Default 0x0525 and "NuttX"
-      0x0525 is the Netchip vendor and should not be used in any
-      products.  This default VID was selected for compatibility with
-      the Linux CDC ACM default VID.
-    CONFIG_CDCACM_PRODUCTID and CONFIG_CDCACM_PRODUCTSTR
-      The product ID code/string. Default 0xa4a7 and "CDC/ACM Serial"
-      0xa4a7 was selected for compatibility with the Linux CDC ACM
-      default PID.
-    CONFIG_CDCACM_RXBUFSIZE and CONFIG_CDCACM_TXBUFSIZE
-      Size of the serial receive/transmit buffers. Default 256.
-
-  USB Storage Device Configuration
-
-    CONFIG_USBMSC
-      Enable compilation of the USB storage driver
-    CONFIG_USBMSC_COMPOSITE
-      Configure the mass storage driver as part of a composite driver
-      (only if CONFIG_USBDEV_COMPOSITE is also defined)
-    CONFIG_USBMSC_IFNOBASE
-      If the CDC driver is part of a composite device, then this may need to
-      be defined to offset the mass storage interface number so that it is
-      unique and contiguous.  When used with the CDC/ACM driver, the
-      correct value for this offset is two (because of the two CDC/ACM
-      interfaces that will precede it).
-    CONFIG_USBMSC_STRBASE
-      If the CDC driver is part of a composite device, then this may need to
-      be defined to offset the mass storage string numbers so that they are
-      unique and contiguous.  When used with the CDC/ACM driver, the
-      correct value for this offset is four (or perhaps 5 or 6, depending
-      on if CONFIG_CDCACM_NOTIFSTR or CONFIG_CDCACM_DATAIFSTR are defined).
-    CONFIG_USBMSC_EP0MAXPACKET
-      Max packet size for endpoint 0
-    CONFIG_USBMSCEPBULKOUT and CONFIG_USBMSC_EPBULKIN
-      The logical 7-bit address of a hardware endpoints that support
-      bulk OUT and IN operations
-    CONFIG_USBMSC_NWRREQS and CONFIG_USBMSC_NRDREQS
-      The number of write/read requests that can be in flight
-    CONFIG_USBMSC_BULKINREQLEN and CONFIG_USBMSC_BULKOUTREQLEN
-      The size of the buffer in each write/read request.  This
-      value needs to be at least as large as the endpoint
-      maxpacket and ideally as large as a block device sector.
-    CONFIG_USBMSC_VENDORID and CONFIG_USBMSC_VENDORSTR
-      The vendor ID code/string
-    CONFIG_USBMSC_PRODUCTID and CONFIG_USBMSC_PRODUCTSTR
-      The product ID code/string
-    CONFIG_USBMSC_REMOVABLE
-      Select if the media is removable
-
-  USB Composite Device Configuration
-
-    CONFIG_USBDEV_COMPOSITE
-      Enables USB composite device support
-    CONFIG_CDCACM_COMPOSITE
-      Configure the CDC serial driver as part of a composite driver
-      (only if CONFIG_USBDEV_COMPOSITE is also defined)
-    CONFIG_USBMSC_COMPOSITE
-      Configure the mass storage driver as part of a composite driver
-      (only if CONFIG_USBDEV_COMPOSITE is also defined)
-    CONFIG_COMPOSITE_IAD
-      If one of the members of the composite has multiple interfaces
-      (such as CDC/ACM), then an Interface Association Descriptor (IAD)
-      will be necessary.  Default:  IAD will be used automatically if
-      needed.  It should not be necessary to set this.
-    CONFIG_COMPOSITE_EP0MAXPACKET
-      Max packet size for endpoint 0
-    CONFIG_COMPOSITE_VENDORID and CONFIG_COMPOSITE_VENDORSTR
-      The vendor ID code/string
-    CONFIG_COMPOSITE_PRODUCTID and CONFIG_COMPOSITE_PRODUCTSTR
-      The product ID code/string
-    CONFIG_COMPOSITE_SERIALSTR
-      Device serial number string
-    CONFIG_COMPOSITE_CONFIGSTR
-      Configuration string
-    CONFIG_COMPOSITE_VERSIONNO
-      Interface version number.
-
-  Graphics related configuration settings
-
-    CONFIG_NX
-      Enables overall support for graphics library and NX
-    CONFIG_NX_MULTIUSER
-      Configures NX in multi-user mode
-    CONFIG_NX_NPLANES
-      Some YUV color formats requires support for multiple planes,
-      one for each color component.  Unless you have such special
-      hardware, this value should be undefined or set to 1.
-    CONFIG_NX_DISABLE_1BPP, CONFIG_NX_DISABLE_2BPP,
-    CONFIG_NX_DISABLE_4BPP, CONFIG_NX_DISABLE_8BPP,
-    CONFIG_NX_DISABLE_16BPP, CONFIG_NX_DISABLE_24BPP, and
-    CONFIG_NX_DISABLE_32BPP
-      NX supports a variety of pixel depths.  You can save some
-      memory by disabling support for unused color depths.
-    CONFIG_NX_PACKEDMSFIRST
-      If a pixel depth of less than 8-bits is used, then NX needs
-      to know if the pixels pack from the MS to LS or from LS to MS
-    CONFIG_NX_LCDDRIVER
-      By default, NX builds to use a framebuffer driver (see
-      include/nuttx/fb.h). If this option is defined, NX will
-      build to use an LCD driver (see include/nuttx/lcd/lcd.h).
-    CONFIG_LCD_MAXPOWER - The full-on power setting for an LCD
-      device.
-    CONFIG_LCD_MAXCONTRAST - The maximum contrast value for an
-      LCD device.
-    CONFIG_LCD_LANDSCAPE, CONFIG_LCD_PORTRAIT, CONFIG_LCD_RLANDSCAPE,
-      and CONFIG_LCD_RPORTRAIT - Some LCD drivers may support
-      these options to present the display in landscape, portrait,
-      reverse landscape, or reverse portrait orientations.  Check
-      the README.txt file in each board configuration directory to
-      see if any of these are supported by the board LCD logic.
-    CONFIG_NX_MOUSE
-      Build in support for mouse input.
-    CONFIG_NX_KBD
-      Build in support of keypad/keyboard input.
-    CONFIG_NXTK_BORDERWIDTH
-      Specifies with with of the border (in pixels) used with
-      framed windows.   The default is 4.
-    CONFIG_NXTK_BORDERCOLOR1 and CONFIG_NXTK_BORDERCOLOR2
-      Specify the colors of the border used with framed windows.
-      CONFIG_NXTK_BORDERCOLOR2 is the shadow side color and so
-      is normally darker.  The default is medium and dark grey,
-      respectively
-    CONFIG_NXTK_AUTORAISE
-      If set, a window will be raised to the top if the mouse position
-      is over a visible portion of the window.  Default: A mouse
-      button must be clicked over a visible portion of the window.
-    CONFIG_NXFONTS_CHARBITS
-      The number of bits in the character set.  Current options are
-      only 7 and 8.  The default is 7.
-
-    CONFIG_NXFONT_SANS23X27
-      This option enables support for a tiny, 23x27 san serif font
-      (font ID FONTID_SANS23X27 == 1).
-    CONFIG_NXFONT_SANS22X29
-      This option enables support for a small, 22x29 san serif font
-      (font ID FONTID_SANS22X29 == 2).
-    CONFIG_NXFONT_SANS28X37
-      This option enables support for a medium, 28x37 san serif font
-      (font ID FONTID_SANS28X37 == 3).
-    CONFIG_NXFONT_SANS39X48
-      This option enables support for a large, 39x48 san serif font
-      (font ID FONTID_SANS39X48 == 4).
-    CONFIG_NXFONT_SANS22X29B
-      This option enables support for a small, 22x29 san serif bold font
-      (font ID FONTID_SANS22X29B == 5).
-    CONFIG_NXFONT_SANS28X37B
-      This option enables support for a medium, 28x37 san serif bold font
-      (font ID FONTID_SANS28X37B == 6).
-    CONFIG_NXFONT_SANS40X49B
-      This option enables support for a large, 40x49 san serif bold font
-      (font ID FONTID_SANS40X49B == 7).
-    CONFIG_NXFONT_SERIF22X29
-      This option enables support for a small, 22x29 font (with serifs)
-      (font ID FONTID_SERIF22X29 == 8).
-    CONFIG_NXFONT_SERIF29X37
-      This option enables support for a medium, 29x37 font (with serifs)
-      (font ID FONTID_SERIF29X37 == 9).
-    CONFIG_NXFONT_SERIF38X48
-      This option enables support for a large, 38x48 font (with serifs)
-      (font ID FONTID_SERIF38X48 == 10).
-    CONFIG_NXFONT_SERIF22X28B
-      This option enables support for a small, 27x38 bold font (with serifs)
-      (font ID FONTID_SERIF22X28B == 11).
-    CONFIG_NXFONT_SERIF27X38B
-      This option enables support for a medium, 27x38 bold font (with serifs)
-      (font ID FONTID_SERIF27X38B == 12).
-    CONFIG_NXFONT_SERIF38X49B
-      This option enables support for a large, 38x49 bold font (with serifs)
-      (font ID FONTID_SERIF38X49B == 13).
-
-  NX Multi-user only options:
-
-    CONFIG_NX_BLOCKING
-      Open the client message queues in blocking mode.  In this case,
-      nx_eventhandler() will never return.
-    CONFIG_NX_MXSERVERMSGS and CONFIG_NX_MXCLIENTMSGS
-      Specifies the maximum number of messages that can fit in
-      the message queues.  No additional resources are allocated, but
-      this can be set to prevent flooding of the client or server with
-      too many messages (CONFIG_PREALLOC_MQ_MSGS controls how many
-      messages are pre-allocated).
-
-  Stack and heap information
-
-    CONFIG_BOOT_RUNFROMFLASH - Some configurations support XIP
-      operation from FLASH but must copy initialized .data sections to RAM.
-    CONFIG_BOOT_COPYTORAM -  Some configurations boot in FLASH
-      but copy themselves entirely into RAM for better performance.
-    CONFIG_ARCH_RAMFUNCS - Other configurations may copy just some functions
-      into RAM, either for better performance or for errata workarounds.
-    CONFIG_STACK_ALIGNMENT - Set if the your application has specific
-      stack alignment requirements (may not be supported
-      in all architectures).
-    CONFIG_IDLETHREAD_STACKSIZE - The size of the initial stack.
-      This is the thread that (1) performs the inital boot of the system up
-      to the point where user_start() is spawned, and (2) there after is the
-      IDLE thread that executes only when there is no other thread ready to
-      run.
-    CONFIG_USERMAIN_STACKSIZE - The size of the stack to allocate
-      for the main user thread that begins at the user_start() entry point.
-    CONFIG_PTHREAD_STACK_MIN - Minimum pthread stack size
-    CONFIG_PTHREAD_STACK_DEFAULT - Default pthread stack size
-    CONFIG_HEAP_BASE - The beginning of the heap
-    CONFIG_HEAP_SIZE - The size of the heap
-
-appconfig -- This is another configuration file that is specific to the
-  application.  This file is copied into the application build directory
-  when NuttX is configured.  See ../apps/README.txt for further details.
-
-setenv.sh -- This is a script that you can include that will be installed at
-  the toplevel of the directory structure and can be sourced to set any
-  necessary environment variables.  You will most likely have to customize the
-  default setenv.sh script in order for it to work correctly in your
-  environment.
-
-Supported Boards
-^^^^^^^^^^^^^^^^
-
-configs/amber
-  This is placeholder for the SoC Robotics Amber Web Server that is based
-  on the Atmel AVR ATMega128 MCU.  There is not much there yet and what is
-  there is untested due to tool-related issues.
-
-configs/avr32dev1
-  This is a port of NuttX to the Atmel AVR32DEV1 board.  That board is
-  based on the Atmel AT32UC3B0256 MCU and uses a specially patched
-  version of the GNU toolchain:  The patches provide support for the
-  AVR32 family.  That patched GNU toolchain is available only from the
-  Atmel website.  STATUS: This port is functional but very basic.  There
-  are configurations for NSH and the OS test.
-
-configs/c5471evm
-  This is a port to the Spectrum Digital C5471 evaluation board.  The
-  TMS320C5471 is a dual core processor from TI with an ARM7TDMI general
-  purpose processor and a c54 DSP.  It is also known as TMS320DA180 or just DA180.
-  NuttX runs on the ARM core and is built with a GNU arm-nuttx-elf toolchain*.
-  This port is complete and verified.
-
-configs/cloudctrl
-  Darcy's CloudController board.  This is a small network relay development
-  board. Based on the Shenzhou IV development board design.  It is based on
-  the STM32F107VC MCU.
-
-configs/compal_e88 and compal_e99
-  These directories contain the board support for compal e88 and e99 phones.
-  These ports are based on patches contributed by Denis Carikli for both the
-  compal e99 and e88.  The patches were made by Alan Carvalho de Assis and
-  Denis Carikli using the Stefan Richter's Osmocom-bb patches.
-
-configs/demo9s12ne64
-  Freescale DMO9S12NE64 board based on the MC9S12NE64 hcs12 cpu.  This
-  port uses the m9s12x GCC toolchain.  STATUS:  (Still) under development; it
-  is code complete but has not yet been verified.
-
-configs/ea3131
-  Embedded Artists EA3131 Development board.  This board is based on the
-  an NXP LPC3131 MCU. This OS is built with the arm-nuttx-elf toolchain*.
-  STATUS:  This port is complete and mature.
-
-configs/ea3152
-  Embedded Artists EA3152 Development board.  This board is based on the
-  an NXP LPC3152 MCU. This OS is built with the arm-nuttx-elf toolchain*.
-  STATUS:  This port is has not be exercised well, but since it is
-  a simple derivative of the ea3131, it should be fully functional.
-
-configs/eagle100
-  Micromint Eagle-100 Development board.  This board is based on the
-  an ARM Cortex-M3 MCU, the Luminary LM3S6918. This OS is built with the
-  arm-nuttx-elf toolchain*.  STATUS:  This port is complete and mature.
-
-configs/ekk-lm3s9b96
-  TI/Stellaris EKK-LM3S9B96 board.  This board is based on the
-  an EKK-LM3S9B96 which is a Cortex-M3.
-
-configs/ez80f0910200kitg
-  ez80Acclaim! Microcontroller.  This port use the Zilog ez80f0910200kitg
-  development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
-  tools.  The development environment is Cygwin under WinXP.
-
-configs/ez80f0910200zco
-  ez80Acclaim! Microcontroller.  This port use the Zilog ez80f0910200zco
-  development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
-  tools.  The development environment is Cygwin under WinXP.
-
-configs/fire-stm32v2
-  A configuration for the M3 Wildfire STM32 board.  This board is based on the
-  STM32F103VET6 chip.  See http://firestm32.taobao.com .  Version 2 and 3 of
-  the boards are supported but only version 2 has been tested.
-
-configs/hymini-stm32v
-  A configuration for the HY-Mini STM32v board.  This board is based on the
-  STM32F103VCT chip.
-
-configs/kwikstik-k40.
-  Kinetis K40 Cortex-M4 MCU.  This port uses the FreeScale KwikStik-K40
-  development board.
-
-configs/lincoln60
-   NuttX port to the Micromint Lincoln 60 board.
-
-configs/lm3s6432-s2e
-  Stellaris RDK-S2E Reference Design Kit and the MDL-S2E Ethernet to
-  Serial module.
-
-configs/lm3s6965-ek
-  Stellaris LM3S6965 Evaluation Kit.  This board is based on the
-  an ARM Cortex-M3 MCU, the Luminary/TI LM3S6965. This OS is built with the
-  arm-nuttx-elf toolchain*.  STATUS:  This port is complete and mature.
-
-configs/lm3s8962-ek
-  Stellaris LMS38962 Evaluation Kit.
-
-configs/lpcxpresso-lpc1768
-  Embedded Artists base board with NXP LPCExpresso LPC1768.  This board
-  is based on the NXP LPC1768.  The Code Red toolchain is used by default.
-  STATUS:  Under development.
-
-configs/lpc4330-xplorer
-  NuttX port to the LPC4330-Xplorer board from NGX Technologies featuring
-  the NXP LPC4330FET100 MCU
-
-configs/m68322evb
-  This is a work in progress for the venerable m68322evb board from
-  Motorola. This OS is also built with the arm-nuttx-elf toolchain*.  STATUS:
-  This port was never completed.
-
-configs/mbed
-  The configurations in this directory support the mbed board (http://mbed.org)
-  that features the NXP LPC1768 microcontroller. This OS is also built
-  with the arm-nuttx-elf toolchain*.  STATUS:  Contributed.
-
-configs/mcu123-lpc214x
-  This port is for the NXP LPC2148 as provided on the mcu123.com
-  lpc214x development board. This OS is also built with the arm-nuttx-elf
-  toolchain*.  The port supports serial, timer0, spi, and usb.
-
-configs/micropendous3
-  This is a port to the Opendous Micropendous 3 board. This board may
-  be populated with either an AVR AT90USB646, 647, 1286, or 1287 MCU.
-  Support is configured for the AT90USB647.
-
-configs/mirtoo
-  This is the port to the DTX1-4000L "Mirtoo" module.  This module uses MicroChip
-  PIC32MX250F128D.  See http://www.dimitech.com/ for further information.
-
-configs/mx1ads
-  This is a port to the Motorola MX1ADS development board.  That board
-  is based on the Freescale i.MX1 processor.  The i.MX1 is an ARM920T.
-  STATUS:  This port is nearly code complete but was never fully
-  integrated due to tool-related issues.
-
-configs/ne64badge
-  Future Electronics Group NE64 /PoE Badge board based on the
-  MC9S12NE64 hcs12 cpu.  This port uses the m9s12x GCC toolchain.
-  STATUS:  Under development.  The port is code-complete but has
-  not yet been fully tested.
-
-configs/ntosd-dm320
-  This port uses the Neuros OSD v1.0 Dev Board with a GNU arm-nuttx-elf
-  toolchain*: see
-
-    http://wiki.neurostechnology.com/index.php/OSD_1.0_Developer_Home
-
-  There are some differences between the Dev Board and the currently
-  available commercial v1.0 Boards.  See
-
-    http://wiki.neurostechnology.com/index.php/OSD_Developer_Board_v1
-
-  NuttX operates on the ARM9EJS of this dual core processor.
-  STATUS: This port is code complete, verified, and included in the
-  NuttX 0.2.1 release.
-
-configs/nucleus2g
-  This port uses the Nucleus 2G board (with Babel CAN board).  This board
-  features an NXP LPC1768 processor.  See the 2G website (http://www.2g-eng.com/)
-  for more information about the Nucleus 2G.
-
-configs/olimex-lpc1766stk
-  This port uses the Olimex LPC1766-STK board and a GNU GCC toolchain* under
-  Linux or Cygwin.  STATUS: Complete and mature.
-
-configs/olimex-lpc2378
-  This port uses the Olimex-lpc2378 board and a GNU arm-nuttx-elf toolchain* under
-  Linux or Cygwin.  STATUS: ostest and NSH configurations available.
-  This port for the NXP LPC2378 was contributed by Rommel Marcelo.
-
-configs/olimex-stm32-p107
-  This port uses the Olimex STM32-P107 board (STM32F107VC) and a GNU arm-nuttx-elf
-  toolchain* under Linux or Cygwin. See the https://www.olimex.com/dev/stm32-p107.html
-  for further information.  Contributed by Max Holtzberg.  STATUS: Configurations
-  for the basic OS test and NSH are available and verified.
-
-configs/olimex-strp711
-  This port uses the Olimex STR-P711 board and a GNU arm-nuttx-elf toolchain* under
-  Linux or Cygwin. See the http://www.olimex.com/dev/str-p711.html" for
-  further information.  STATUS: Configurations for the basic OS test and NSH
-  are complete and verified.
-
-configs/pcblogic-pic32mx
-  This is the port of NuttX to the PIC32MX board from PCB Logic Design Co.
-  This board features the MicroChip 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.
-  STATUS:  Code complete but testing has been stalled due to tool related problems
-  (PICkit 2 does not work with the PIC32).
-
-configs/p112
-  The P112 is notable because it was the first of the hobbyist single board
-  computers to reach the production stage. The P112 hobbyist computers
-  were relatively widespread and inspired other hobbyist centered home brew
-  computing projects such as N8VEM home brew computing project. The P112
-  project still maintains many devoted enthusiasts and has an online
-  repository of software and other information.
-
-  The P112 computer originated as a commercial product of "D-X Designs Pty
-  Ltd" of Australia. They describe the computer as "The P112 is a stand-alone
-  8-bit CPU board. Typically running CP/M (tm) or a similar operating system,
-  it provides a Z80182 (Z-80 upgrade) CPU with up to 1MB of memory, serial,
-  parallel and diskette IO, and realtime clock, in a 3.5-inch drive form factor.
-  Powered solely from 5V, it draws 150mA (nominal: not including disk drives)
-  with a 16MHz CPU clock. Clock speeds up to 24.576MHz are possible."
-
-  The P112 board was last available new in 1996 by Dave Brooks. In late 2004
-  on the Usenet Newsgroup comp.os.cpm, talk about making another run of P112
-  boards was discussed. David Griffith decided to produce additional P112 kits
-  with Dave Brooks blessing and the assistance of others. In addition Terry
-  Gulczynski makes additional P112 derivative hobbyist home brew computers.
-  Hal Bower was very active in the mid 1990's on the P112 project and ported
-  the "Banked/Portable BIOS".
-
-  Dave Brooks was successfully funded through Kickstarter for and another
-  run of P112 boards in November of 2012.
-
-configs/pic32-starterkit
-  This directory contains the port of NuttX to the Microchip PIC32 Ethernet
-  Starter Kit (DM320004) with the Multimedia Expansion Board (MEB, DM320005).
-  See www.microchip.com for further information.
-
-configs/pic32mx7mmb
-  This directory will (eventually) contain the port of NuttX to the
-  Mikroelektronika PIC32MX7 Multimedia Board (MMB).  See
-  http://www.mikroe.com/ for further information.
-
-configs/pjrc-8051
-  8051 Microcontroller.  This port uses the PJRC 87C52 development system
-  and the SDCC toolchain.   This port is not quite ready for prime time.
-
-configs/qemu-i486
-  Port of NuttX to QEMU in i486 mode.  This port will also run on real i486
-  hardwared (Google the Bifferboard).
-
-configs/rgmp
-  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.
-
-  See http://rgmp.sourceforge.net/wiki/index.php/Main_Page for further information
-  about RGMP.
-
-configs/sam3u-ek
-  The port of NuttX to the Atmel SAM3U-EK development board.
-
-configs/sim
-  A user-mode port of NuttX to the x86 Linux platform is available.
-  The purpose of this port is primarily to support OS feature development.
-  This port does not support interrupts or a real timer (and hence no
-  round robin scheduler)  Otherwise, it is complete.
-
-configs/shenzhou
-  This is the port of NuttX to the Shenzhou development board from
-  www.armjishu.com. This board features the STMicro STM32F107VCT MCU.
-
-configs/skp16c26
-  Renesas M16C processor on the Renesas SKP16C26 StarterKit.  This port
-  uses the GNU m32c toolchain.  STATUS:  The port is complete but untested
-  due to issues with compiler internal errors.
-
-configs/stm3210e-eval
-  STMicro STM3210E-EVAL development board based on the STMicro STM32F103ZET6
-  microcontroller (ARM Cortex-M3).  This port uses the GNU Cortex-M3
-  toolchain.
-
-configs/stm3220g-eval
-  STMicro STM3220G-EVAL development board based on the STMicro STM32F407IG
-  microcontroller (ARM Cortex-M3).
-
-configs/stm3240g-eval
-  STMicro STM3240G-EVAL development board based on the STMicro STM32F103ZET6
-  microcontroller (ARM Cortex-M4 with FPU).  This port uses a GNU Cortex-M4
-  toolchain (such as CodeSourcery).
-
-configs/stm32f100rc_generic
-  STMicro STM32F100RC generic board based on STM32F100RC high-density value line
-  chip. This "generic" configuration is not very usable out-of-box, but can be
-  used as a starting point to creating new configs with similar STM32
-  high-density value line chips.
-  
-configs/stm32f4discovery
-  STMicro STM32F4-Discovery board based on the STMIcro STM32F407VGT6 MCU.
-
-configs/sure-pic32mx
-  The "Advanced USB Storage Demo Board," Model DB-DP11215, from Sure
-  Electronics (http://www.sureelectronics.net/).  This board features
-  the MicroChip PIC32MX440F512H.  See also
-  http://www.sureelectronics.net/goods.php?id=1168 for further
-  information about the Sure DB-DP11215 board.
-
-configs/teensy
-  This is the port of NuttX to the PJRC Teensy++ 2.0 board.  This board is
-  developed by http://pjrc.com/teensy/.  The Teensy++ 2.0 is based
-  on an Atmel AT90USB1286 MCU.
-
-configs/twr-k60n512
-  Kinetis K60 Cortex-M4 MCU.  This port uses the FreeScale TWR-K60N512
-  development board.
-
-configs/ubw32
-
-  This is the port to the Sparkfun UBW32 board.  This port uses the original v2.4
-  board which is based on the MicroChip PIC32MX460F512L.  See
-  http://www.sparkfun.com/products/8971.  This older version has been replaced
-  with this board http://www.sparkfun.com/products/9713. See also
-  http://www.schmalzhaus.com/UBW32/.
-
-configs/us7032evb1
-  This is a port of the Hitachi SH-1 on the Hitachi SH-1/US7032EVB1 board.
-  STATUS:  Work has just began on this port.
-
-configs/vsn
-  ISOTEL NetClamps VSN V1.2 ready2go sensor network platform based on the
-  STMicro STM32F103RET6.  Contributed by Uros Platise.  See
-  http://isotel.eu/NetClamps/
-
-configs/xtrs
-  TRS80 Model 3.  This port uses a vintage computer based on the Z80.
-  An emulator for this computer is available to run TRS80 programs on a
-  linux platform (http://www.tim-mann.org/xtrs.html).
-
-configs/z16f2800100zcog
-  z16f Microcontroller.  This port use the Zilog z16f2800100zcog
-  development kit and the Zilog ZDS-II Windows command line tools.  The
-  development environment is Cygwin under WinXP.
-
-configs/z80sim
-  z80 Microcontroller.  This port uses a Z80 instruction set simulator.
-  That simulator can be found in the NuttX SVN at
-  http://svn.code.sf.net/p/nuttx/code/trunk/misc/sims/z80sim.
-  This port also uses the SDCC toolchain (http://sdcc.sourceforge.net/")
-  (verified with version 2.6.0).
-
-configs/z8encore000zco
-  z8Encore! Microcontroller.  This port use the Zilog z8encore000zco
-  development kit, Z8F6403 part, and the Zilog ZDS-II Windows command line
-  tools.  The development environment is Cygwin under WinXP.
-
-configs/z8f64200100kit
-  z8Encore! Microcontroller.  This port use the Zilog z8f64200100kit
-  development kit, Z8F6423 part, and the Zilog ZDS-II Windows command line
-  tools.  The development environment is Cygwin under WinXP.
-
-configs/zp214xpa
-  This port is for the NXP LPC2148 as provided on the The0.net
-  ZPA213X/4XPA development board. Includes support for the
-  UG-2864AMBAG01 OLED also from The0.net
-
-Configuring NuttX
-^^^^^^^^^^^^^^^^^
-
-Configuring NuttX requires only copying
-
-  configs/<board-name>/<config-dir>/Make.def to ${TOPDIR}/Make.defs
-  configs/<board-name>/<config-dir>/setenv.sh to ${TOPDIR}/setenv.sh
-  configs/<board-name>/<config-dir>/defconfig to ${TOPDIR}/.config
-
-And if configs/<board-name>/<config-dir>/appconfig exists in the board
-configuration directory:
-
-  Copy configs/<board-name>/<config-dir>/appconfig to <app-dir>/.config
-  echo "APPS_LOC=\"<app-dir>\"" >> "${TOPDIR}/.config"
-
-tools/configure.sh
-  There is a script that automates these steps.  The following steps will
-  accomplish the same configuration:
-
-    cd tools
-   ./configure.sh <board-name>/<config-dir>
-
-  There is an alternative Windows batch file that can be used in the
-  windows native enironment like:
-
-    cd ${TOPDIR}\tools
-    configure.bat <board-name>\<config-dir>
-
-  See tools/README.txt for more information about these scripts.
-
-  And if configs/<board-name>/<config-dir>/appconfig exists and your
-  application directory is not in the standard loction (../apps), then
-  you should also specify the location of the application directory on the
-  command line like:
-
-    cd tools
-    ./configure.sh -a <app-dir> <board-name>/<config-dir>
-
-Building Symbol Tables
-^^^^^^^^^^^^^^^^^^^^^^
-
-Symbol tables are needed at several of the binfmt interfaces in order to bind
-a module to the base code.  These symbol tables can be tricky to create and
-will probably have to be tailored for any specific application, balancing
-the number of symbols and the size of the symbol table against the symbols
-required by the applications.
-
-The top-level System.map file is one good source of symbol information
-(which, or course, was just generated from the top-level nuttx file
-using the GNU 'nm' tool).
-
-There are also common-separated value (CSV) values in the source try that
-provide information about symbols.  In particular:
-
-  nuttx/syscall/syscall.csv - Describes the NuttX RTOS interface, and
-  nuttx/lib/lib.csv         - Describes the NuttX C library interface.
-
-There is a tool at nuttx/tools/mksymtab that will use these CSV files as
-input to generate a generic symbol table.  See nuttx/tools/README.txt for
-more information about using the mksymtab tool.
diff --git a/nuttx/configs/px4fmu/Kconfig b/nuttx/configs/px4fmu/Kconfig
deleted file mode 100644
index b5e6d5515..000000000
--- a/nuttx/configs/px4fmu/Kconfig
+++ /dev/null
@@ -1,26 +0,0 @@
-#
-# For a description of the syntax of this configuration file,
-# see misc/tools/kconfig-language.txt.
-#
-
-if ARCH_BOARD_PX4FMU
-config ARCH_LEDS
-	bool "NuttX LED support"
-	default n
-	---help---
-		"Support control of board LEDs by NuttX to indicate system state"
-
-config ARCH_BUTTONS
-	bool "Button support"
-	default n
-	---help---
-		"Support interfaces to use buttons provided by the board."
-
-config ARCH_IRQBUTTONS
-	bool "Button interrupt support"
-	default n
-	depends on ARCH_BUTTONS
-	---help---
-		"Support EXTI interrupts on button presses and releases."
-
-endif
diff --git a/nuttx/configs/px4fmu/README.txt b/nuttx/configs/px4fmu/README.txt
deleted file mode 100755
index c92169206..000000000
--- a/nuttx/configs/px4fmu/README.txt
+++ /dev/null
@@ -1,601 +0,0 @@
-README
-======
-
-This README discusses issues unique to NuttX configurations for the
-PX4FMU development board.
-
-Or, it will once those are established.  For now, this is a copy of the file
-as presented for the STMicro STM32F407 evaluation board.  Read with caution.
-
-Contents
-========
-
-  - Development Environment
-  - GNU Toolchain Options
-  - IDEs
-  - NuttX buildroot Toolchain
-  - STM3240G-EVAL-specific Configuration Options
-  - LEDs
-  - Ethernet
-  - PWM
-  - CAN
-  - Configurations
-
-Development Environment
-=======================
-
-  Either Linux or Cygwin on Windows can be used for the development environment.
-  The source has been built only using the GNU toolchain (see below).  Other
-  toolchains will likely cause problems. Testing was performed using the Cygwin
-  environment because the Raisonance R-Link emulatator and some RIDE7 development tools
-  were used and those tools works only under Windows.
-
-GNU Toolchain Options
-=====================
-
-  The NuttX make system has been modified to support the following different
-  toolchain options.
-
-  1. The CodeSourcery GNU toolchain,
-  2. The devkitARM GNU toolchain,
-  3. Raisonance GNU toolchain, or
-  4. The NuttX buildroot Toolchain (see below).
-
-  All testing has been conducted using the CodeSourcery toolchain for Windows.  To use
-  the devkitARM, Raisonance GNU, or NuttX buildroot toolchain, you simply need to
-  add one of the following configuration options to your .config (or defconfig)
-  file:
-
-    CONFIG_STM32_CODESOURCERYW=y  : CodeSourcery under Windows
-    CONFIG_STM32_CODESOURCERYL=y  : CodeSourcery under Linux
-    CONFIG_STM32_DEVKITARM=y      : devkitARM under Windows
-    CONFIG_STM32_RAISONANCE=y     : Raisonance RIDE7 under Windows
-    CONFIG_STM32_BUILDROOT=y      : NuttX buildroot under Linux or Cygwin (default)
-
-  If you change the default toolchain, then you may also have to modify the PATH in
-  the setenv.h file if your make cannot find the tools.
-
-  NOTE: the CodeSourcery (for Windows), devkitARM, and Raisonance toolchains are
-  Windows native toolchains.  The CodeSourcey (for Linux) and NuttX buildroot
-  toolchains are Cygwin and/or Linux native toolchains. There are several limitations
-  to using a Windows based toolchain in a Cygwin environment.  The three biggest are:
-
-  1. The Windows toolchain cannot follow Cygwin paths.  Path conversions are
-     performed automatically in the Cygwin makefiles using the 'cygpath' utility
-     but you might easily find some new path problems.  If so, check out 'cygpath -w'
-
-  2. Windows toolchains cannot follow Cygwin symbolic links.  Many symbolic links
-     are used in Nuttx (e.g., include/arch).  The make system works around these
-     problems for the Windows tools by copying directories instead of linking them.
-     But this can also cause some confusion for you:  For example, you may edit
-     a file in a "linked" directory and find that your changes had no effect.
-     That is because you are building the copy of the file in the "fake" symbolic
-     directory.  If you use a Windows toolchain, you should get in the habit of
-     making like this:
-
-       make clean_context all
-
-     An alias in your .bashrc file might make that less painful.
-
-  3. Dependencies are not made when using Windows versions of the GCC.  This is
-     because the dependencies are generated using Windows pathes which do not
-     work with the Cygwin make.
-
-     Support has been added for making dependencies with the windows-native toolchains.
-     That support can be enabled by modifying your Make.defs file as follows:
-
-    -  MKDEP                = $(TOPDIR)/tools/mknulldeps.sh
-    +  MKDEP                = $(TOPDIR)/tools/mkdeps.sh --winpaths "$(TOPDIR)"
-
-     If you have problems with the dependency build (for example, if you are not
-     building on C:), then you may need to modify tools/mkdeps.sh
-
-  NOTE 1: The CodeSourcery toolchain (2009q1) does not work with default optimization
-  level of -Os (See Make.defs).  It will work with -O0, -O1, or -O2, but not with
-  -Os.
-
-  NOTE 2: The devkitARM toolchain includes a version of MSYS make.  Make sure that
-  the paths to Cygwin's /bin and /usr/bin directories appear BEFORE the devkitARM
-  path or will get the wrong version of make.
-
-IDEs
-====
-
-  NuttX is built using command-line make.  It can be used with an IDE, but some
-  effort will be required to create the project.
-  
-  Makefile Build
-  --------------
-  Under Eclipse, it is pretty easy to set up an "empty makefile project" and
-  simply use the NuttX makefile to build the system.  That is almost for free
-  under Linux.  Under Windows, you will need to set up the "Cygwin GCC" empty
-  makefile project in order to work with Windows (Google for "Eclipse Cygwin" -
-  there is a lot of help on the internet).
-
-  Native Build
-  ------------
-  Here are a few tips before you start that effort:
-
-  1) Select the toolchain that you will be using in your .config file
-  2) Start the NuttX build at least one time from the Cygwin command line
-     before trying to create your project.  This is necessary to create
-     certain auto-generated files and directories that will be needed.
-  3) Set up include pathes:  You will need include/, arch/arm/src/stm32,
-     arch/arm/src/common, arch/arm/src/armv7-m, and sched/.
-  4) All assembly files need to have the definition option -D __ASSEMBLY__
-     on the command line.
-
-  Startup files will probably cause you some headaches.  The NuttX startup file
-  is arch/arm/src/stm32/stm32_vectors.S.  With RIDE, I have to build NuttX
-  one time from the Cygwin command line in order to obtain the pre-built
-  startup object needed by RIDE.
-
-NuttX buildroot Toolchain
-=========================
-
-  A GNU GCC-based toolchain is assumed.  The files */setenv.sh should
-  be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
-  different from the default in your PATH variable).
-
-  If you have no Cortex-M3 toolchain, one can be downloaded from the NuttX
-  SourceForge download site (https://sourceforge.net/project/showfiles.php?group_id=189573).
-  This GNU toolchain builds and executes in the Linux or Cygwin environment.
-
-  1. You must have already configured Nuttx in <some-dir>/nuttx.
-
-     cd tools
-     ./configure.sh stm3240g-eval/<sub-dir>
-
-  2. Download the latest buildroot package into <some-dir>
-
-  3. unpack the buildroot tarball.  The resulting directory may
-     have versioning information on it like buildroot-x.y.z.  If so,
-     rename <some-dir>/buildroot-x.y.z to <some-dir>/buildroot.
-
-  4. cd <some-dir>/buildroot
-
-  5. cp configs/cortexm3-defconfig-4.3.3 .config
-
-  6. make oldconfig
-
-  7. make
-
-  8. Edit setenv.h, if necessary, so that the PATH variable includes
-     the path to the newly built binaries.
-
-  See the file configs/README.txt in the buildroot source tree.  That has more
-  detailed PLUS some special instructions that you will need to follow if you are
-  building a Cortex-M3 toolchain for Cygwin under Windows.
-
-Ethernet
-========
-
-The Ethernet driver is configured to use the MII interface:
-
-  Board Jumper Settings:
-
-    Jumper  Description
-    JP8     To enable MII, JP8 should not be fitted.
-    JP6     2-3: Enable MII interface mode
-    JP5     2-3: Provide 25 MHz clock for MII or 50 MHz clock for RMII by MCO at PA8
-    SB1     Not used with MII
-
-LEDs
-====
-
-The STM3240G-EVAL board has four LEDs labeled LD1, LD2, LD3 and LD4 on the
-board.. These LEDs are not used by the board port unless CONFIG_ARCH_LEDS is
-defined.  In that case, the usage by the board port is defined in
-include/board.h and src/up_leds.c. The LEDs are used to encode OS-related\
-events as follows:
-
-	SYMBOL				Meaning					LED1*	LED2	LED3	LED4
-	-------------------	-----------------------	-------	-------	-------	------
-	LED_STARTED			NuttX has been started	ON		OFF		OFF		OFF
-	LED_HEAPALLOCATE	Heap has been allocated	OFF		ON		OFF		OFF
-	LED_IRQSENABLED		Interrupts enabled		ON		ON		OFF		OFF
-	LED_STACKCREATED	Idle stack created		OFF		OFF		ON		OFF
-	LED_INIRQ			In an interrupt**		ON		N/C		N/C		OFF
-	LED_SIGNAL			In a signal handler***  N/C		ON		N/C		OFF
-	LED_ASSERTION		An assertion failed		ON		ON		N/C		OFF
-	LED_PANIC			The system has crashed	N/C		N/C		N/C		ON
-    LED_IDLE            STM32 is is sleep mode  (Optional, not used)
-
-  * If LED1, LED2, LED3 are statically on, then NuttX probably failed to boot
-    and these LEDs will give you some indication of where the failure was
- ** The normal state is LED3 ON and LED1 faintly glowing.  This faint glow
-    is because of timer interupts that result in the LED being illuminated
-    on a small proportion of the time.
-*** LED2 may also flicker normally if signals are processed.
-
-PWM
-===
-
-The STM3240G-Eval has no real on-board PWM devices, but the board can be
-configured to output a pulse train using TIM4 CH2.  This pin is used by
-FSMC is but is also connected to the Motor Control Connector (CN5) just
-for this purpose:
-
-  PD13 FSMC_A18 / MC_TIM4_CH2 pin 33 (EnB)
-
-FSMC must be disabled in this case!  PD13 is available at:
-
-  Daughterboard Extension Connector, CN3, pin 32 - available
-  TFT LCD Connector, CN19, pin 17 -- not available without removing the LCD.
-  Motor Control Connector CN15, pin 33 -- not available unless you bridge SB14.
-
-CAN
-===
-
-Connector 10 (CN10) is DB-9 male connector that can be used with CAN1 or CAN2.
-
-  JP10 connects CAN1_RX or CAN2_RX to the CAN transceiver
-  JP3 connects CAN1_TX or CAN2_TX to the CAN transceiver
-
-CAN signals are then available on CN10 pins:
-
-  CN10 Pin 7 = CANH
-  CN10 Pin 2 = CANL
-
-Mapping to STM32 GPIO pins:
-
-  PD0   = FSMC_D2 & CAN1_RX   
-  PD1   = FSMC_D3 & CAN1_TX   
-  PB13  = ULPI_D6 & CAN2_TX
-  PB5   = ULPI_D7 & CAN2_RX
-
-Configuration Options:
-
-  CONFIG_CAN - Enables CAN support (one or both of CONFIG_STM32_CAN1 or
-    CONFIG_STM32_CAN2 must also be defined)
-  CONFIG_CAN_FIFOSIZE - The size of the circular buffer of CAN messages.
-    Default: 8
-  CONFIG_CAN_NPENDINGRTR - The size of the list of pending RTR requests.
-    Default: 4
-
-  CONFIG_STM32_CAN1 - Enable support for CAN1
-  CONFIG_CAN1_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN1 is defined.
-  CONFIG_STM32_CAN2 - Enable support for CAN1
-  CONFIG_CAN2_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN2 is defined.
-  CONFIG_CAN_REGDEBUG - If CONFIG_DEBUG is set, this will generate an
-    dump of all CAN registers.
-
-STM3240G-EVAL-specific Configuration Options
-============================================
-
-	CONFIG_ARCH - Identifies the arch/ subdirectory.  This should
-	   be set to:
-
-	   CONFIG_ARCH=arm
-
-	CONFIG_ARCH_family - For use in C code:
-
-	   CONFIG_ARCH_ARM=y
-
-	CONFIG_ARCH_architecture - For use in C code:
-
-	   CONFIG_ARCH_CORTEXM4=y
-
-	CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
-
-	   CONFIG_ARCH_CHIP=stm32
-
-	CONFIG_ARCH_CHIP_name - For use in C code to identify the exact
-	   chip:
-
-	   CONFIG_ARCH_CHIP_STM32F407IG=y
-
-    CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG - Enables special STM32 clock
-       configuration features.
-
-       CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
- 
-	CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
-	   hence, the board that supports the particular chip or SoC.
-
-	   CONFIG_ARCH_BOARD=stm3240g_eval (for the STM3240G-EVAL development board)
-
-	CONFIG_ARCH_BOARD_name - For use in C code
-
-	   CONFIG_ARCH_BOARD_STM3240G_EVAL=y
-
-	CONFIG_ARCH_LOOPSPERMSEC - Must be calibrated for correct operation
-	   of delay loops
-
-	CONFIG_ENDIAN_BIG - define if big endian (default is little
-	   endian)
-
-	CONFIG_DRAM_SIZE - Describes the installed DRAM (SRAM in this case):
-
-	   CONFIG_DRAM_SIZE=0x00010000 (64Kb)
-
-	CONFIG_DRAM_START - The start address of installed DRAM
-
-	   CONFIG_DRAM_START=0x20000000
-
-	CONFIG_DRAM_END - Last address+1 of installed RAM
-
-	   CONFIG_DRAM_END=(CONFIG_DRAM_START+CONFIG_DRAM_SIZE)
-
-	CONFIG_ARCH_IRQPRIO - The STM3240xxx supports interrupt prioritization
-
-	   CONFIG_ARCH_IRQPRIO=y
-
-	CONFIG_ARCH_FPU - The STM3240xxx supports a floating point unit (FPU)
-
-	   CONFIG_ARCH_FPU=y
-
-	CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to boards that
-	   have LEDs
-
-	CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt
-	   stack. If defined, this symbol is the size of the interrupt
-	    stack in bytes.  If not defined, the user task stacks will be
-	  used during interrupt handling.
-
-	CONFIG_ARCH_STACKDUMP - Do stack dumps after assertions
-
-	CONFIG_ARCH_LEDS -  Use LEDs to show state. Unique to board architecture.
-
-	CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that
-	   cause a 100 second delay during boot-up.  This 100 second delay
-	   serves no purpose other than it allows you to calibratre
-	   CONFIG_ARCH_LOOPSPERMSEC.  You simply use a stop watch to measure
-	   the 100 second delay then adjust CONFIG_ARCH_LOOPSPERMSEC until
-	   the delay actually is 100 seconds.
-
-  Individual subsystems can be enabled:
-
-	AHB1
-	----
-	CONFIG_STM32_CRC
-	CONFIG_STM32_BKPSRAM
-	CONFIG_STM32_CCMDATARAM
-	CONFIG_STM32_DMA1
-	CONFIG_STM32_DMA2
-	CONFIG_STM32_ETHMAC
-	CONFIG_STM32_OTGHS
-
-	AHB2
-	----
-	CONFIG_STM32_DCMI
-	CONFIG_STM32_CRYP
-	CONFIG_STM32_HASH
-	CONFIG_STM32_RNG
-	CONFIG_STM32_OTGFS
-
-	AHB3
-	----
-	CONFIG_STM32_FSMC
-
-	APB1
-	----
-	CONFIG_STM32_TIM2
-	CONFIG_STM32_TIM3
-	CONFIG_STM32_TIM4
-	CONFIG_STM32_TIM5
-	CONFIG_STM32_TIM6
-	CONFIG_STM32_TIM7
-	CONFIG_STM32_TIM12
-	CONFIG_STM32_TIM13
-	CONFIG_STM32_TIM14
-	CONFIG_STM32_WWDG
-	CONFIG_STM32_SPI2
-	CONFIG_STM32_SPI3
-	CONFIG_STM32_USART2
-	CONFIG_STM32_USART3
-	CONFIG_STM32_UART4
-	CONFIG_STM32_UART5
-	CONFIG_STM32_I2C1
-	CONFIG_STM32_I2C2
-	CONFIG_STM32_I2C3
-	CONFIG_STM32_CAN1
-	CONFIG_STM32_CAN2
-	CONFIG_STM32_DAC1
-	CONFIG_STM32_DAC2
-	CONFIG_STM32_PWR -- Required for RTC
-
-	APB2
-	----
-	CONFIG_STM32_TIM1
-	CONFIG_STM32_TIM8
-	CONFIG_STM32_USART1
-	CONFIG_STM32_USART6
-	CONFIG_STM32_ADC1
-	CONFIG_STM32_ADC2
-	CONFIG_STM32_ADC3
-	CONFIG_STM32_SDIO
-	CONFIG_STM32_SPI1
-	CONFIG_STM32_SYSCFG
-	CONFIG_STM32_TIM9
-	CONFIG_STM32_TIM10
-	CONFIG_STM32_TIM11
-
-  Timer and I2C devices may need to the following to force power to be applied
-  unconditionally at power up.  (Otherwise, the device is powered when it is
-  initialized).
-
-    CONFIG_STM32_FORCEPOWER
-
-  Timer devices may be used for different purposes.  One special purpose is
-  to generate modulated outputs for such things as motor control.  If CONFIG_STM32_TIMn
-  is defined (as above) then the following may also be defined to indicate that
-  the timer is intended to be used for pulsed output modulation, ADC conversion,
-  or DAC conversion.
-
-	CONFIG_STM32_TIM1_PWM
-	CONFIG_STM32_TIM2_PWM
-	CONFIG_STM32_TIM3_PWM
-	CONFIG_STM32_TIM4_PWM
-	CONFIG_STM32_TIM5_PWM
-	CONFIG_STM32_TIM8_PWM
-	CONFIG_STM32_TIM9_PWM
-	CONFIG_STM32_TIM10_PWM
-	CONFIG_STM32_TIM11_PWM
-	CONFIG_STM32_TIM12_PWM
-	CONFIG_STM32_TIM13_PWM
-	CONFIG_STM32_TIM14_PWM
-
-	CONFIG_STM32_TIM1_ADC
-	CONFIG_STM32_TIM2_ADC
-	CONFIG_STM32_TIM3_ADC
-	CONFIG_STM32_TIM4_ADC
-	CONFIG_STM32_TIM5_ADC
-	CONFIG_STM32_TIM6_ADC
-	CONFIG_STM32_TIM7_ADC
-	CONFIG_STM32_TIM8_ADC
-
-	CONFIG_STM32_TIM1_DAC
-	CONFIG_STM32_TIM2_DAC
-	CONFIG_STM32_TIM3_DAC
-	CONFIG_STM32_TIM4_DAC
-	CONFIG_STM32_TIM5_DAC
-	CONFIG_STM32_TIM6_DAC
-	CONFIG_STM32_TIM7_DAC
-	CONFIG_STM32_TIM8_DAC
-
-  For each timer that is enabled for PWM usage, we need the following additional
-  configuration settings:
-
-	CONFIG_STM32_TIMx_CHANNEL - Specifies the timer output channel {1,..,4}
- 
-  NOTE: The STM32 timers are each capable of generating different signals on
-  each of the four channels with different duty cycles.  That capability is
-  not supported by this driver:  Only one output channel per timer.
-
-  JTAG Enable settings (by default JTAG-DP and SW-DP are disabled):
-
-	CONFIG_STM32_JTAG_FULL_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-	CONFIG_STM32_JTAG_NOJNTRST_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-	  but without JNTRST.
-	CONFIG_STM32_JTAG_SW_ENABLE - Set JTAG-DP disabled and SW-DP enabled
-
-  STM3240xxx specific device driver settings
-
-	CONFIG_U[S]ARTn_SERIAL_CONSOLE - selects the USARTn (n=1,2,3) or UART
-           m (m=4,5) for the console and ttys0 (default is the USART1).
-	CONFIG_U[S]ARTn_RXBUFSIZE - Characters are buffered as received.
-	   This specific the size of the receive buffer
-	CONFIG_U[S]ARTn_TXBUFSIZE - Characters are buffered before
-	   being sent.  This specific the size of the transmit buffer
-	CONFIG_U[S]ARTn_BAUD - The configure BAUD of the UART.  Must be
-	CONFIG_U[S]ARTn_BITS - The number of bits.  Must be either 7 or 8.
-	CONFIG_U[S]ARTn_PARTIY - 0=no parity, 1=odd parity, 2=even parity
-	CONFIG_U[S]ARTn_2STOP - Two stop bits
-
-	CONFIG_STM32_SPI_INTERRUPTS - Select to enable interrupt driven SPI
-	  support. Non-interrupt-driven, poll-waiting is recommended if the
-	  interrupt rate would be to high in the interrupt driven case.
-	CONFIG_STM32_SPI_DMA - Use DMA to improve SPI transfer performance.
-	  Cannot be used with CONFIG_STM32_SPI_INTERRUPT.
-
-	CONFIG_SDIO_DMA - Support DMA data transfers.  Requires CONFIG_STM32_SDIO
-	  and CONFIG_STM32_DMA2.
-	CONFIG_SDIO_PRI - Select SDIO interrupt prority.  Default: 128
-	CONFIG_SDIO_DMAPRIO - Select SDIO DMA interrupt priority. 
-	  Default:  Medium
-	CONFIG_SDIO_WIDTH_D1_ONLY - Select 1-bit transfer mode.  Default:
-	  4-bit transfer mode.
-
-	CONFIG_STM32_PHYADDR - The 5-bit address of the PHY on the board
-	CONFIG_STM32_MII - Support Ethernet MII interface
-	CONFIG_STM32_MII_MCO1 - Use MCO1 to clock the MII interface
-	CONFIG_STM32_MII_MCO2 - Use MCO2 to clock the MII interface
-	CONFIG_STM32_RMII - Support Ethernet RMII interface
-	CONFIG_STM32_AUTONEG - Use PHY autonegotion to determine speed and mode
-	CONFIG_STM32_ETHFD - If CONFIG_STM32_AUTONEG is not defined, then this
-	  may be defined to select full duplex mode. Default: half-duplex
-	CONFIG_STM32_ETH100MBPS - If CONFIG_STM32_AUTONEG is not defined, then this
-	  may be defined to select 100 MBps speed.  Default: 10 Mbps
-	CONFIG_STM32_PHYSR - This must be provided if CONFIG_STM32_AUTONEG is
-	  defined.  The PHY status register address may diff from PHY to PHY.  This
-	  configuration sets the address of the PHY status register.
-	CONFIG_STM32_PHYSR_SPEED - This must be provided if CONFIG_STM32_AUTONEG is
-	  defined.  This provides bit mask indicating 10 or 100MBps speed.
-	CONFIG_STM32_PHYSR_100MBPS - This must be provided if CONFIG_STM32_AUTONEG is
-	  defined.  This provides the value of the speed bit(s) indicating 100MBps speed.
-	CONFIG_STM32_PHYSR_MODE - This must be provided if CONFIG_STM32_AUTONEG is
-	  defined.  This provide bit mask indicating full or half duplex modes.
-	CONFIG_STM32_PHYSR_FULLDUPLEX - This must be provided if CONFIG_STM32_AUTONEG is
-	  defined.  This provides the value of the mode bits indicating full duplex mode.
-	CONFIG_STM32_ETH_PTP - Precision Time Protocol (PTP).  Not supported
-	  but some hooks are indicated with this condition.
-
-  STM3240G-EVAL CAN Configuration
-
-	CONFIG_CAN - Enables CAN support (one or both of CONFIG_STM32_CAN1 or
-	  CONFIG_STM32_CAN2 must also be defined)
-	CONFIG_CAN_FIFOSIZE - The size of the circular buffer of CAN messages.
-	  Default: 8
-	CONFIG_CAN_NPENDINGRTR - The size of the list of pending RTR requests.
-	  Default: 4
-	CONFIG_CAN_LOOPBACK - A CAN driver may or may not support a loopback
-	  mode for testing. The STM32 CAN driver does support loopback mode.
-	CONFIG_CAN1_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN1 is defined.
-	CONFIG_CAN2_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN2 is defined.
-	CONFIG_CAN_REGDEBUG - If CONFIG_DEBUG is set, this will generate an
-	  dump of all CAN registers.
-
-  STM3240G-EVAL LCD Hardware Configuration
-
-Configurations
-==============
-
-Each STM3240G-EVAL configuration is maintained in a sudirectory and
-can be selected as follow:
-
-	cd tools
-	./configure.sh stm3240g-eval/<subdir>
-	cd -
-	. ./setenv.sh
-
-Where <subdir> is one of the following:
-
-  dhcpd:
-  -----
-
-    This builds the DCHP server using the apps/examples/dhcpd application
-    (for execution from FLASH.) See apps/examples/README.txt for information
-    about the dhcpd example.  The server address is 10.0.0.1 and it serves
-    IP addresses in the range 10.0.0.2 through 10.0.0.17 (all of which, of
-    course, are configurable).
-
-    CONFIG_STM32_CODESOURCERYW=y  : CodeSourcery under Windows
-
-  nettest:
-  -------
-
-    This configuration directory may be used to verify networking performance
-    using the STM32's Ethernet controller. It uses apps/examples/nettest to excercise the
-    TCP/IP network.
-
-    CONFIG_EXAMPLE_NETTEST_SERVER=n                       : Target is configured as the client
-    CONFIG_EXAMPLE_NETTEST_PERFORMANCE=y                  : Only network performance is verified.
-    CONFIG_EXAMPLE_NETTEST_IPADDR=(10<<24|0<<16|0<<8|2)   : Target side is IP: 10.0.0.2
-    CONFIG_EXAMPLE_NETTEST_DRIPADDR=(10<<24|0<<16|0<<8|1) : Host side is IP: 10.0.0.1
-    CONFIG_EXAMPLE_NETTEST_CLIENTIP=(10<<24|0<<16|0<<8|1) : Server address used by which ever is client.
-
-  ostest:
-  ------
-    This configuration directory, performs a simple OS test using
-    examples/ostest.  By default, this project assumes that you are
-    using the DFU bootloader.
-
-    CONFIG_STM32_CODESOURCERYW=y  : CodeSourcery under Windows
-
-  nsh:
-  ---
-    Configures the NuttShell (nsh) located at apps/examples/nsh.  The
-    Configuration enables both the serial and telnet NSH interfaces.
-
-    CONFIG_STM32_CODESOURCERYW=y              : CodeSourcery under Windows
-    CONFIG_NSH_DHCPC=n                        : DHCP is disabled
-    CONFIG_NSH_IPADDR=(10<<24|0<<16|0<<8|2)   : Target IP address 10.0.0.2
-    CONFIG_NSH_DRIPADDR=(10<<24|0<<16|0<<8|1) : Host IP address 10.0.0.1
-
-    NOTE:  This example assumes that a network is connected.  During its
-    initialization, it will try to negotiate the link speed.  If you have
-    no network connected when you reset the board, there will be a long
-    delay (maybe 30 seconds?) before anything happens.  That is the timeout
-    before the networking finally gives up and decides that no network is
-    available.
diff --git a/nuttx/configs/px4fmu/common/Make.defs b/nuttx/configs/px4fmu/common/Make.defs
deleted file mode 100644
index 756286ccb..000000000
--- a/nuttx/configs/px4fmu/common/Make.defs
+++ /dev/null
@@ -1,184 +0,0 @@
-############################################################################
-# configs/px4fmu/common/Make.defs
-#
-#   Copyright (C) 2011 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-
-#
-# Generic Make.defs for the PX4FMU
-# Do not specify/use this file directly - it is included by config-specific
-# Make.defs in the per-config directories.
-#
-
-include ${TOPDIR}/tools/Config.mk
-
-#
-# We only support building with the ARM bare-metal toolchain from
-# https://launchpad.net/gcc-arm-embedded on Windows, Linux or Mac OS.
-#
-CONFIG_ARMV7M_TOOLCHAIN	:= GNU_EABI
-
-include ${TOPDIR}/arch/arm/src/armv7-m/Toolchain.defs
-
-CC			 = $(CROSSDEV)gcc
-CXX			 = $(CROSSDEV)g++
-CPP			 = $(CROSSDEV)gcc -E
-LD			 = $(CROSSDEV)ld
-AR			 = $(CROSSDEV)ar rcs
-NM			 = $(CROSSDEV)nm
-OBJCOPY			 = $(CROSSDEV)objcopy
-OBJDUMP			 = $(CROSSDEV)objdump
-
-MAXOPTIMIZATION		 = -O3
-ARCHCPUFLAGS		 = -mcpu=cortex-m4 \
-			   -mthumb \
-			   -march=armv7e-m \
-			   -mfpu=fpv4-sp-d16 \
-			   -mfloat-abi=hard
-
-
-# enable precise stack overflow tracking
-INSTRUMENTATIONDEFINES	 = -finstrument-functions \
-			   -ffixed-r10
-
-# pull in *just* libm from the toolchain ... this is grody
-LIBM			 = "${shell $(CC) $(ARCHCPUFLAGS) -print-file-name=libm.a}"
-EXTRA_LIBS		+= $(LIBM)
-
-# use our linker script
-LDSCRIPT		 = ld.script
-
-ifeq ($(WINTOOL),y)
-  # Windows-native toolchains
-  DIRLINK		 = $(TOPDIR)/tools/copydir.sh
-  DIRUNLINK		 = $(TOPDIR)/tools/unlink.sh
-  MKDEP			 = $(TOPDIR)/tools/mknulldeps.sh
-  ARCHINCLUDES		 = -I. -isystem "${shell cygpath -w $(TOPDIR)/include}"
-  ARCHXXINCLUDES	 = -I. -isystem "${shell cygpath -w $(TOPDIR)/include}" -isystem "${shell cygpath -w $(TOPDIR)/include/cxx}"
-  ARCHSCRIPT		 = -T "${shell cygpath -w $(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/common/$(LDSCRIPT)}"
-else
-  ifeq ($(PX4_WINTOOL),y)
-    # Windows-native toolchains (MSYS)
-    DIRLINK		 = $(TOPDIR)/tools/copydir.sh
-    DIRUNLINK		 = $(TOPDIR)/tools/unlink.sh
-    MKDEP		 = $(TOPDIR)/tools/mknulldeps.sh
-    ARCHINCLUDES	 = -I. -isystem $(TOPDIR)/include
-    ARCHXXINCLUDES	 = -I. -isystem $(TOPDIR)/include -isystem $(TOPDIR)/include/cxx
-    ARCHSCRIPT		 = -T$(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/common/$(LDSCRIPT)
-  else
-    # Linux/Cygwin-native toolchain 
-    MKDEP		 = $(TOPDIR)/tools/mkdeps.sh
-    ARCHINCLUDES	 = -I. -isystem $(TOPDIR)/include
-    ARCHXXINCLUDES	 = -I. -isystem $(TOPDIR)/include -isystem $(TOPDIR)/include/cxx
-    ARCHSCRIPT		 = -T$(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/common/$(LDSCRIPT)
-  endif
-endif
-
-# tool versions
-ARCHCCVERSION		 = ${shell $(CC) -v 2>&1 | sed -n '/^gcc version/p' | sed -e 's/^gcc version \([0-9\.]\)/\1/g' -e 's/[-\ ].*//g' -e '1q'}
-ARCHCCMAJOR		 = ${shell echo $(ARCHCCVERSION) | cut -d'.' -f1}
-
-# optimisation flags
-ARCHOPTIMIZATION	 = $(MAXOPTIMIZATION) \
-			   -fno-strict-aliasing \
-			   -fno-strength-reduce \
-			   -fomit-frame-pointer \
-   			   -funsafe-math-optimizations \
-   			   -fno-builtin-printf \
-   			   -ffunction-sections \
-   			   -fdata-sections
-
-ifeq ("${CONFIG_DEBUG_SYMBOLS}","y")
-ARCHOPTIMIZATION	+= -g
-endif
-
-ARCHCFLAGS		 = -std=gnu99
-ARCHCXXFLAGS		 = -fno-exceptions -fno-rtti -std=gnu++0x
-ARCHWARNINGS		 = -Wall \
-			   -Wextra \
-			   -Wdouble-promotion \
-			   -Wshadow \
-			   -Wfloat-equal \
-			   -Wframe-larger-than=1024 \
-			   -Wpointer-arith \
-			   -Wlogical-op \
-			   -Wmissing-declarations \
-			   -Wpacked \
-			   -Wno-unused-parameter
-#   -Wcast-qual  - generates spurious noreturn attribute warnings, try again later
-#   -Wconversion - would be nice, but too many "risky-but-safe" conversions in the code
-#   -Wcast-align - would help catch bad casts in some cases, but generates too many false positives
-
-ARCHCWARNINGS		 = $(ARCHWARNINGS) \
-			   -Wbad-function-cast \
-			   -Wstrict-prototypes \
-			   -Wold-style-declaration \
-			   -Wmissing-parameter-type \
-			   -Wmissing-prototypes \
-			   -Wnested-externs \
-			   -Wunsuffixed-float-constants
-ARCHWARNINGSXX		 = $(ARCHWARNINGS) \
-			   -Wno-psabi
-ARCHDEFINES		 =
-ARCHPICFLAGS		 = -fpic -msingle-pic-base -mpic-register=r10
-
-# this seems to be the only way to add linker flags
-EXTRA_LIBS		+= --warn-common \
-			   --gc-sections
-
-CFLAGS			 = $(ARCHCFLAGS) $(ARCHCWARNINGS) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHINCLUDES) $(INSTRUMENTATIONDEFINES) $(ARCHDEFINES) $(EXTRADEFINES) -pipe -fno-common
-CPICFLAGS		 = $(ARCHPICFLAGS) $(CFLAGS)
-CXXFLAGS		 = $(ARCHCXXFLAGS) $(ARCHWARNINGSXX) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHXXINCLUDES) $(INSTRUMENTATIONDEFINES) $(ARCHDEFINES) $(EXTRADEFINES) -pipe
-CXXPICFLAGS		 = $(ARCHPICFLAGS) $(CXXFLAGS)
-CPPFLAGS		 = $(ARCHINCLUDES) $(INSTRUMENTATIONDEFINES) $(ARCHDEFINES) $(EXTRADEFINES)
-AFLAGS			 = $(CFLAGS) -D__ASSEMBLY__
-
-NXFLATLDFLAGS1		 = -r -d -warn-common
-NXFLATLDFLAGS2		 = $(NXFLATLDFLAGS1) -T$(TOPDIR)/binfmt/libnxflat/gnu-nxflat.ld -no-check-sections
-LDNXFLATFLAGS		 = -e main -s 2048
-
-OBJEXT			 = .o
-LIBEXT			 = .a
-EXEEXT			 =
-
-
-# produce partially-linked $1 from files in $2
-define PRELINK
-	@echo "PRELINK: $1"
-	$(Q) $(LD) -Ur -o $1 $2 && $(OBJCOPY) --localize-hidden $1
-endef
-
-HOSTCC			 = gcc
-HOSTINCLUDES		 = -I.
-HOSTCFLAGS		 = -Wall -Wstrict-prototypes -Wshadow -g -pipe
-HOSTLDFLAGS		 =
-
diff --git a/nuttx/configs/px4fmu/common/ld.script b/nuttx/configs/px4fmu/common/ld.script
deleted file mode 100644
index de8179e8d..000000000
--- a/nuttx/configs/px4fmu/common/ld.script
+++ /dev/null
@@ -1,149 +0,0 @@
-/****************************************************************************
- * configs/px4fmu/common/ld.script
- *
- *   Copyright (C) 2011 Gregory Nutt. All rights reserved.
- *   Author: Gregory Nutt <gnutt@nuttx.org>
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- * 3. Neither the name NuttX nor the names of its contributors may be
- *    used to endorse or promote products derived from this software
- *    without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
- * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
- * POSSIBILITY OF SUCH DAMAGE.
- *
- ****************************************************************************/
-
-/* The STM32F405 has 1024Kb of FLASH beginning at address 0x0800:0000 and
- * 192Kb of SRAM. SRAM is split up into three blocks:
- *
- * 1) 112Kb of SRAM beginning at address 0x2000:0000
- * 2)  16Kb of SRAM beginning at address 0x2001:c000
- * 3)  64Kb of TCM SRAM beginning at address 0x1000:0000
- *
- * When booting from FLASH, FLASH memory is aliased to address 0x0000:0000
- * where the code expects to begin execution by jumping to the entry point in
- * the 0x0800:0000 address range.
- *
- * The first 0x4000 of flash is reserved for the bootloader.
- */
-
-MEMORY
-{
-    flash (rx)   : ORIGIN = 0x08004000, LENGTH = 1008K
-    sram (rwx)   : ORIGIN = 0x20000000, LENGTH = 128K
-    ccsram (rwx) : ORIGIN = 0x10000000, LENGTH = 64K
-}
-
-OUTPUT_ARCH(arm)
-
-ENTRY(__start)		/* treat __start as the anchor for dead code stripping */
-EXTERN(_vectors)	/* force the vectors to be included in the output */
-
-/* 
- * Ensure that abort() is present in the final object.  The exception handling
- * code pulled in by libgcc.a requires it (and that code cannot be easily avoided).
- */
-EXTERN(abort)
-
-SECTIONS
-{
-	.text : {
-		_stext = ABSOLUTE(.);
-		*(.vectors)
-		*(.text .text.*)        
-		*(.fixup)
-		*(.gnu.warning)
-		*(.rodata .rodata.*)        
-		*(.gnu.linkonce.t.*)
-		*(.got)
-		*(.gcc_except_table)
-		*(.gnu.linkonce.r.*)
-		_etext = ABSOLUTE(.);
-
-		/* 
-		 * This is a hack to make the newlib libm __errno() call
-		 * use the NuttX get_errno_ptr() function.
-		 */
-		__errno = get_errno_ptr;
-	} > flash
-
-	/*
-	 * Init functions (static constructors and the like)
-	 */
-        .init_section : {
-                _sinit = ABSOLUTE(.);
-                KEEP(*(.init_array .init_array.*))
-                _einit = ABSOLUTE(.);
-        } > flash
-
-	/*
-	 * Construction data for parameters.
-	 */
-	__param ALIGN(4): {
-		__param_start = ABSOLUTE(.);
-		KEEP(*(__param*))
-		__param_end = ABSOLUTE(.);
-	} > flash
-
-	.ARM.extab : {
-		*(.ARM.extab*)
-	} > flash
-
-	__exidx_start = ABSOLUTE(.);
-	.ARM.exidx : {
-		*(.ARM.exidx*)
-	} > flash
-	__exidx_end = ABSOLUTE(.);
-
-	_eronly = ABSOLUTE(.);
-
-	.data : {
-		_sdata = ABSOLUTE(.);
-		*(.data .data.*)
-		*(.gnu.linkonce.d.*)
-		CONSTRUCTORS
-		_edata = ABSOLUTE(.);
-	} > sram AT > flash
-
-	.bss : {
-		_sbss = ABSOLUTE(.);
-		*(.bss .bss.*)
-		*(.gnu.linkonce.b.*)
-		*(COMMON)
-		_ebss = ABSOLUTE(.);
-	} > sram
-
-	/* Stabs debugging sections. */
-	.stab 0 : { *(.stab) }
-	.stabstr 0 : { *(.stabstr) }
-	.stab.excl 0 : { *(.stab.excl) }
-	.stab.exclstr 0 : { *(.stab.exclstr) }
-	.stab.index 0 : { *(.stab.index) }
-	.stab.indexstr 0 : { *(.stab.indexstr) }
-	.comment 0 : { *(.comment) }
-	.debug_abbrev 0 : { *(.debug_abbrev) }
-	.debug_info 0 : { *(.debug_info) }
-	.debug_line 0 : { *(.debug_line) }
-	.debug_pubnames 0 : { *(.debug_pubnames) }
-	.debug_aranges 0 : { *(.debug_aranges) }
-}
diff --git a/nuttx/configs/px4fmu/include/board.h b/nuttx/configs/px4fmu/include/board.h
deleted file mode 100755
index 294b6c398..000000000
--- a/nuttx/configs/px4fmu/include/board.h
+++ /dev/null
@@ -1,373 +0,0 @@
-/************************************************************************************
- * configs/px4fmu/include/board.h
- * include/arch/board/board.h
- *
- *   Copyright (C) 2009 Gregory Nutt. All rights reserved.
- *   Author: Gregory Nutt <gnutt@nuttx.org>
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- * 3. Neither the name NuttX nor the names of its contributors may be
- *    used to endorse or promote products derived from this software
- *    without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
- * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
- * POSSIBILITY OF SUCH DAMAGE.
- *
- ************************************************************************************/
-
-#ifndef __ARCH_BOARD_BOARD_H
-#define __ARCH_BOARD_BOARD_H
-
-/************************************************************************************
- * Included Files
- ************************************************************************************/
-
-#include <nuttx/config.h>
-#ifndef __ASSEMBLY__
-# include <stdint.h>
-#endif
-
-/************************************************************************************
- * Definitions
- ************************************************************************************/
-
-/* Clocking *************************************************************************/
-/* The PX4FMU uses a 24MHz crystal connected to the HSE.
- *
- * This is the "standard" configuration as set up by arch/arm/src/stm32f40xx_rcc.c:
- *   System Clock source           : PLL (HSE)
- *   SYSCLK(Hz)                    : 168000000    Determined by PLL configuration
- *   HCLK(Hz)                      : 168000000    (STM32_RCC_CFGR_HPRE)
- *   AHB Prescaler                 : 1            (STM32_RCC_CFGR_HPRE)
- *   APB1 Prescaler                : 4            (STM32_RCC_CFGR_PPRE1)
- *   APB2 Prescaler                : 2            (STM32_RCC_CFGR_PPRE2)
- *   HSE Frequency(Hz)             : 24000000     (STM32_BOARD_XTAL)
- *   PLLM                          : 24           (STM32_PLLCFG_PLLM)
- *   PLLN                          : 336          (STM32_PLLCFG_PLLN)
- *   PLLP                          : 2            (STM32_PLLCFG_PLLP)
- *   PLLQ                          : 7            (STM32_PLLCFG_PPQ)
- *   Main regulator output voltage : Scale1 mode  Needed for high speed SYSCLK
- *   Flash Latency(WS)             : 5
- *   Prefetch Buffer               : OFF
- *   Instruction cache             : ON
- *   Data cache                    : ON
- *   Require 48MHz for USB OTG FS, : Enabled
- *   SDIO and RNG clock
- */
-
-/* HSI - 16 MHz RC factory-trimmed
- * LSI - 32 KHz RC
- * HSE - On-board crystal frequency is 24MHz
- * LSE - not installed
- */
-
-#define STM32_BOARD_XTAL        24000000ul
-
-#define STM32_HSI_FREQUENCY     16000000ul
-#define STM32_LSI_FREQUENCY     32000
-#define STM32_HSE_FREQUENCY     STM32_BOARD_XTAL
-//#define STM32_LSE_FREQUENCY     32768
-
-/* Main PLL Configuration.
- *
- * PLL source is HSE
- * PLL_VCO = (STM32_HSE_FREQUENCY / PLLM) * PLLN
- *         = (25,000,000 / 25) * 336
- *         = 336,000,000
- * SYSCLK  = PLL_VCO / PLLP
- *         = 336,000,000 / 2 = 168,000,000
- * USB OTG FS, SDIO and RNG Clock
- *         =  PLL_VCO / PLLQ
- *         = 48,000,000
- */
-
-#define STM32_PLLCFG_PLLM       RCC_PLLCFG_PLLM(24)
-#define STM32_PLLCFG_PLLN       RCC_PLLCFG_PLLN(336)
-#define STM32_PLLCFG_PLLP       RCC_PLLCFG_PLLP_2
-#define STM32_PLLCFG_PLLQ       RCC_PLLCFG_PLLQ(7)
-
-#define STM32_SYSCLK_FREQUENCY  168000000ul
-
-/* AHB clock (HCLK) is SYSCLK (168MHz) */
-
-#define STM32_RCC_CFGR_HPRE     RCC_CFGR_HPRE_SYSCLK  /* HCLK  = SYSCLK / 1 */
-#define STM32_HCLK_FREQUENCY    STM32_SYSCLK_FREQUENCY
-#define STM32_BOARD_HCLK        STM32_HCLK_FREQUENCY  /* same as above, to satisfy compiler */
-
-/* APB1 clock (PCLK1) is HCLK/4 (42MHz) */
-
-#define STM32_RCC_CFGR_PPRE1    RCC_CFGR_PPRE1_HCLKd4     /* PCLK1 = HCLK / 4 */
-#define STM32_PCLK1_FREQUENCY   (STM32_HCLK_FREQUENCY/4)
-
-/* Timers driven from APB1 will be twice PCLK1 */
-
-#define STM32_APB1_TIM2_CLKIN   (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM3_CLKIN   (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM4_CLKIN   (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM5_CLKIN   (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM6_CLKIN   (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM7_CLKIN   (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM12_CLKIN  (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM13_CLKIN  (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM14_CLKIN  (2*STM32_PCLK1_FREQUENCY)
-
-/* APB2 clock (PCLK2) is HCLK/2 (84MHz) */
-
-#define STM32_RCC_CFGR_PPRE2    RCC_CFGR_PPRE2_HCLKd2     /* PCLK2 = HCLK / 2 */
-#define STM32_PCLK2_FREQUENCY   (STM32_HCLK_FREQUENCY/2)
-
-/* Timers driven from APB2 will be twice PCLK2 */
-
-#define STM32_APB2_TIM1_CLKIN   (2*STM32_PCLK2_FREQUENCY)
-#define STM32_APB2_TIM8_CLKIN   (2*STM32_PCLK2_FREQUENCY)
-#define STM32_APB2_TIM9_CLKIN   (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB2_TIM10_CLKIN  (2*STM32_PCLK1_FREQUENCY)
-#define STM32_APB2_TIM11_CLKIN  (2*STM32_PCLK1_FREQUENCY)
-
-/* Timer Frequencies, if APBx is set to 1, frequency is same to APBx
- * otherwise frequency is 2xAPBx. 
- * Note: TIM1,8 are on APB2, others on APB1
- */
-
-#define STM32_TIM18_FREQUENCY   (2*STM32_PCLK2_FREQUENCY)
-#define STM32_TIM27_FREQUENCY   (2*STM32_PCLK1_FREQUENCY)
-
-/* SDIO dividers.  Note that slower clocking is required when DMA is disabled 
- * in order to avoid RX overrun/TX underrun errors due to delayed responses
- * to service FIFOs in interrupt driven mode.  These values have not been
- * tuned!!!
- *
- * HCLK=72MHz, SDIOCLK=72MHz, SDIO_CK=HCLK/(178+2)=400 KHz
- */
-  
-#define SDIO_INIT_CLKDIV        (178 << SDIO_CLKCR_CLKDIV_SHIFT)
-
-/* DMA ON:  HCLK=72 MHz, SDIOCLK=72MHz, SDIO_CK=HCLK/(2+2)=18 MHz
- * DMA OFF: HCLK=72 MHz, SDIOCLK=72MHz, SDIO_CK=HCLK/(3+2)=14.4 MHz
- */
-
-#ifdef CONFIG_SDIO_DMA
-#  define SDIO_MMCXFR_CLKDIV    (2 << SDIO_CLKCR_CLKDIV_SHIFT) 
-#else
-#  define SDIO_MMCXFR_CLKDIV    (3 << SDIO_CLKCR_CLKDIV_SHIFT) 
-#endif
-
-/* DMA ON:  HCLK=72 MHz, SDIOCLK=72MHz, SDIO_CK=HCLK/(1+2)=24 MHz
- * DMA OFF: HCLK=72 MHz, SDIOCLK=72MHz, SDIO_CK=HCLK/(3+2)=14.4 MHz
- */
-
-#ifdef CONFIG_SDIO_DMA
-#  define SDIO_SDXFR_CLKDIV     (1 << SDIO_CLKCR_CLKDIV_SHIFT)
-#else
-#  define SDIO_SDXFR_CLKDIV     (3 << SDIO_CLKCR_CLKDIV_SHIFT)
-#endif
-
-/* High-resolution timer
- */
-#ifdef CONFIG_HRT_TIMER
-# define HRT_TIMER		1	/* use timer1 for the HRT */
-# define HRT_TIMER_CHANNEL	1	/* use capture/compare channel */
-#endif
-
-/* LED definitions ******************************************************************/
-/* PX4 has two LEDs that we will encode as: */
-
-#define LED_STARTED       0  /* LED? */
-#define LED_HEAPALLOCATE  1  /* LED? */
-#define LED_IRQSENABLED   2  /* LED? + LED? */
-#define LED_STACKCREATED  3  /* LED? */
-#define LED_INIRQ         4  /* LED? + LED? */
-#define LED_SIGNAL        5  /* LED? + LED? */
-#define LED_ASSERTION     6  /* LED? + LED? + LED? */
-#define LED_PANIC         7  /* N/C  + N/C  + N/C + LED? */
-
-/* Alternate function pin selections ************************************************/
-
-/*
- * UARTs.
- *
- * Note that UART5 has no optional pinout.
- */
-#define GPIO_USART1_RX	GPIO_USART1_RX_2
-#define GPIO_USART1_TX	GPIO_USART1_TX_2
-
-#define GPIO_USART2_RX	GPIO_USART2_RX_1
-#define GPIO_USART2_TX	GPIO_USART2_TX_1
-#define GPIO_USART2_RTS	GPIO_USART2_RTS_1
-#define GPIO_USART2_CTS	GPIO_USART2_CTS_1
-
-#define GPIO_USART6_RX	GPIO_USART6_RX_1
-#define GPIO_USART6_TX	GPIO_USART6_TX_1
-
-/* UART DMA configuration for USART1/6 */
-#define DMAMAP_USART1_RX DMAMAP_USART1_RX_2
-#define DMAMAP_USART6_RX DMAMAP_USART6_RX_2
-
-/*
- * PWM
- *
- * Four PWM outputs can be configured on pins otherwise shared with
- * USART2; two can take the flow control pins if they are not being used.
- *
- * Pins:
- *
- * CTS - PA0 - TIM2CH1
- * RTS - PA1 - TIM2CH2
- * TX  - PA2 - TIM2CH3
- * RX  - PA3 - TIM2CH4
- *
- */
-#define GPIO_TIM2_CH1OUT	GPIO_TIM2_CH1OUT_1
-#define GPIO_TIM2_CH2OUT	GPIO_TIM2_CH2OUT_1
-#define GPIO_TIM2_CH3OUT	GPIO_TIM2_CH3OUT_1
-#define GPIO_TIM2_CH4OUT	GPIO_TIM2_CH4OUT_1
-
-/*
- * PPM
- *
- * PPM input is handled by the HRT timer.
- */
-#if defined(CONFIG_HRT_TIMER) && defined (CONFIG_HRT_PPM)
-# define HRT_PPM_CHANNEL	3	/* use capture/compare channel 3 */
-# define GPIO_PPM_IN	(GPIO_ALT|GPIO_AF1|GPIO_SPEED_50MHz|GPIO_PULLUP|GPIO_PORTA|GPIO_PIN10)
-#endif
-
-/* 
- * CAN
- *
- * CAN2 is routed to the expansion connector.
- */
-
-#define GPIO_CAN2_RX	GPIO_CAN2_RX_2
-#define GPIO_CAN2_TX	GPIO_CAN2_TX_2
-
-/*
- * I2C
- *
- * The optional _GPIO configurations allow the I2C driver to manually
- * reset the bus to clear stuck slaves.  They match the pin configuration,
- * but are normally-high GPIOs.
- */
-#define GPIO_I2C1_SCL		GPIO_I2C1_SCL_2
-#define GPIO_I2C1_SDA		GPIO_I2C1_SDA_2
-#define GPIO_I2C1_SCL_GPIO	(GPIO_OUTPUT|GPIO_OPENDRAIN|GPIO_SPEED_50MHz|GPIO_OUTPUT_SET|GPIO_PORTB|GPIO_PIN8)
-#define GPIO_I2C1_SDA_GPIO	(GPIO_OUTPUT|GPIO_OPENDRAIN|GPIO_SPEED_50MHz|GPIO_OUTPUT_SET|GPIO_PORTB|GPIO_PIN9)
-
-#define GPIO_I2C2_SCL		GPIO_I2C2_SCL_1
-#define GPIO_I2C2_SDA		GPIO_I2C2_SDA_1
-#define GPIO_I2C2_SCL_GPIO	(GPIO_OUTPUT|GPIO_OPENDRAIN|GPIO_SPEED_50MHz|GPIO_OUTPUT_SET|GPIO_PORTB|GPIO_PIN10)
-#define GPIO_I2C2_SDA_GPIO	(GPIO_OUTPUT|GPIO_OPENDRAIN|GPIO_SPEED_50MHz|GPIO_OUTPUT_SET|GPIO_PORTB|GPIO_PIN11)
-
-#define GPIO_I2C3_SCL		GPIO_I2C3_SCL_1
-#define GPIO_I2C3_SDA		GPIO_I2C3_SDA_1
-#define GPIO_I2C3_SCL_GPIO	(GPIO_OUTPUT|GPIO_OPENDRAIN|GPIO_SPEED_50MHz|GPIO_OUTPUT_SET|GPIO_PORTA|GPIO_PIN8)
-#define GPIO_I2C3_SDA_GPIO	(GPIO_OUTPUT|GPIO_OPENDRAIN|GPIO_SPEED_50MHz|GPIO_OUTPUT_SET|GPIO_PORTC|GPIO_PIN9)
-
-/*
- * I2C busses
- */
-#define PX4_I2C_BUS_ESC		1
-#define PX4_I2C_BUS_ONBOARD	2
-#define PX4_I2C_BUS_EXPANSION	3
-
-/*
- * Devices on the onboard bus.
- *
- * Note that these are unshifted addresses.
- */
-#define PX4_I2C_OBDEV_HMC5883	0x1e
-#define PX4_I2C_OBDEV_MS5611	0x76
-#define PX4_I2C_OBDEV_EEPROM	NOTDEFINED
-
-#define PX4_I2C_OBDEV_PX4IO_BL	0x18
-#define PX4_I2C_OBDEV_PX4IO	0x1a
-
-/*
- * SPI
- */
-#define GPIO_SPI1_MISO	GPIO_SPI1_MISO_1
-#define GPIO_SPI1_MOSI	GPIO_SPI1_MOSI_1
-#define GPIO_SPI1_SCK	GPIO_SPI1_SCK_1
-
-#define GPIO_SPI2_MISO	GPIO_SPI2_MISO_2
-#define GPIO_SPI2_MOSI	GPIO_SPI2_MOSI_2
-#define GPIO_SPI2_SCK	GPIO_SPI2_SCK_2
-
-#define GPIO_SPI3_MISO	GPIO_SPI3_MISO_2
-#define GPIO_SPI3_MOSI	GPIO_SPI3_MOSI_1
-#define GPIO_SPI3_SCK	GPIO_SPI3_SCK_2
-#define GPIO_SPI3_NSS	GPIO_SPI3_NSS_2
-
-/*
- * Use these in place of the spi_dev_e enumeration to
- * select a specific SPI device on SPI1
- */
-#define PX4_SPIDEV_GYRO		1
-#define PX4_SPIDEV_ACCEL	2
-#define PX4_SPIDEV_MPU		3
-
-#define PX4_SPIDEV_ACCEL_MAG 2 // external for anti vibration test
-
-/*
- * Tone alarm output
- */
-#define TONE_ALARM_TIMER	3	/* timer 3 */
-#define TONE_ALARM_CHANNEL	3	/* channel 3 */
-#define GPIO_TONE_ALARM_IDLE	(GPIO_OUTPUT|GPIO_PUSHPULL|GPIO_SPEED_2MHz|GPIO_OUTPUT_CLEAR|GPIO_PORTC|GPIO_PIN8)
-#define GPIO_TONE_ALARM		(GPIO_ALT|GPIO_AF2|GPIO_SPEED_2MHz|GPIO_FLOAT|GPIO_PUSHPULL|GPIO_PORTC|GPIO_PIN8)
-
-/************************************************************************************
- * Public Data
- ************************************************************************************/
-
-#ifndef __ASSEMBLY__
-
-#undef EXTERN
-#if defined(__cplusplus)
-#define EXTERN extern "C"
-extern "C" {
-#else
-#define EXTERN extern
-#endif
-
-/************************************************************************************
- * Public Function Prototypes
- ************************************************************************************/
-/************************************************************************************
- * Name: stm32_boardinitialize
- *
- * Description:
- *   All STM32 architectures must provide the following entry point.  This entry point
- *   is called early in the intitialization -- after all memory has been configured
- *   and mapped but before any devices have been initialized.
- *
- ************************************************************************************/
-
-EXTERN void stm32_boardinitialize(void);
-
-#undef EXTERN
-#if defined(__cplusplus)
-}
-#endif
-
-#endif /* __ASSEMBLY__ */
-#endif  /* __ARCH_BOARD_BOARD_H */
diff --git a/nuttx/configs/px4fmu/include/nsh_romfsimg.h b/nuttx/configs/px4fmu/include/nsh_romfsimg.h
deleted file mode 100644
index 15e4e7a8d..000000000
--- a/nuttx/configs/px4fmu/include/nsh_romfsimg.h
+++ /dev/null
@@ -1,42 +0,0 @@
-/****************************************************************************
- *
- *   Copyright (C) 2013 PX4 Development Team. All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- * 3. Neither the name PX4 nor the names of its contributors may be
- *    used to endorse or promote products derived from this software
- *    without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
- * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
- * POSSIBILITY OF SUCH DAMAGE.
- *
- ****************************************************************************/
-
-/**
- * nsh_romfsetc.h
- *
- * This file is a stub for 'make export' purposes; the actual ROMFS
- * must be supplied by the library client.
- */
-
-extern unsigned char romfs_img[];
-extern unsigned int romfs_img_len;
diff --git a/nuttx/configs/px4fmu/nsh/Make.defs b/nuttx/configs/px4fmu/nsh/Make.defs
deleted file mode 100644
index 3e6f88bd3..000000000
--- a/nuttx/configs/px4fmu/nsh/Make.defs
+++ /dev/null
@@ -1,3 +0,0 @@
-include ${TOPDIR}/.config
-
-include $(TOPDIR)/configs/px4fmu/common/Make.defs
diff --git a/nuttx/configs/px4fmu/nsh/appconfig b/nuttx/configs/px4fmu/nsh/appconfig
deleted file mode 100644
index 0e18aa8ef..000000000
--- a/nuttx/configs/px4fmu/nsh/appconfig
+++ /dev/null
@@ -1,52 +0,0 @@
-############################################################################
-# configs/px4fmu/nsh/appconfig
-#
-#   Copyright (C) 2011 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-
-# Path to example in apps/examples containing the user_start entry point
-
-CONFIGURED_APPS	+= examples/nsh
-
-# The NSH application library
-CONFIGURED_APPS += nshlib
-CONFIGURED_APPS += system/readline
-
-ifeq ($(CONFIG_CAN),y)
-#CONFIGURED_APPS += examples/can
-endif
-
-#ifeq ($(CONFIG_USBDEV),y)
-#ifeq ($(CONFIG_CDCACM),y)
-CONFIGURED_APPS += examples/cdcacm
-#endif
-#endif
diff --git a/nuttx/configs/px4fmu/nsh/defconfig b/nuttx/configs/px4fmu/nsh/defconfig
deleted file mode 100755
index 02e224302..000000000
--- a/nuttx/configs/px4fmu/nsh/defconfig
+++ /dev/null
@@ -1,1064 +0,0 @@
-############################################################################
-# configs/px4fmu/nsh/defconfig
-#
-#   Copyright (C) 2012 PX4 Development Team. All rights reserved.
-#   Copyright (C) 2011-2012 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-#
-# architecture selection
-#
-# CONFIG_ARCH - identifies the arch subdirectory and, hence, the
-#   processor architecture.
-# CONFIG_ARCH_family - for use in C code.  This identifies the
-#   particular chip family that the architecture is implemented
-#   in.
-# CONFIG_ARCH_architecture - for use in C code.  This identifies the
-#   specific architecture within the chip family.
-# CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
-# CONFIG_ARCH_CHIP_name - For use in C code
-# CONFIG_ARCH_BOARD - identifies the configs subdirectory and, hence,
-#   the board that supports the particular chip or SoC.
-# CONFIG_ARCH_BOARD_name - for use in C code
-# CONFIG_ENDIAN_BIG - define if big endian (default is little endian)
-# CONFIG_BOARD_LOOPSPERMSEC - for delay loops
-# CONFIG_DRAM_SIZE - Describes the installed DRAM.
-# CONFIG_DRAM_START - The start address of DRAM (physical)
-# CONFIG_ARCH_IRQPRIO - The STM3240xxx supports interrupt prioritization
-# CONFIG_ARCH_FPU - The STM3240xxx supports a floating point unit (FPU).
-# CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt
-#   stack. If defined, this symbol is the size of the interrupt
-#   stack in bytes.  If not defined, the user task stacks will be
-#   used during interrupt handling.
-# CONFIG_ARCH_STACKDUMP - Do stack dumps after assertions
-# CONFIG_ARCH_BOOTLOADER - Set if you are using a bootloader.
-# CONFIG_ARCH_LEDS -  Use LEDs to show state. Unique to board architecture.
-# CONFIG_ARCH_BUTTONS -  Enable support for buttons. Unique to board architecture.
-# CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that
-#   cause a 100 second delay during boot-up.  This 100 second delay
-#   serves no purpose other than it allows you to calibrate
-#   CONFIG_BOARD_LOOPSPERMSEC.  You simply use a stop watch to measure
-#   the 100 second delay then adjust CONFIG_BOARD_LOOPSPERMSEC until
-#   the delay actually is 100 seconds.
-# CONFIG_ARCH_DMA - Support DMA initialization
-#
-CONFIG_ARCH="arm"
-CONFIG_ARCH_ARM=y
-CONFIG_ARCH_CORTEXM4=y
-CONFIG_ARCH_CHIP="stm32"
-CONFIG_ARCH_CHIP_STM32F405RG=y
-CONFIG_ARCH_BOARD="px4fmu"
-CONFIG_ARCH_BOARD_PX4FMU=y
-CONFIG_BOARD_LOOPSPERMSEC=16717
-CONFIG_DRAM_SIZE=0x00030000
-CONFIG_DRAM_START=0x20000000
-CONFIG_ARCH_IRQPRIO=y
-CONFIG_ARCH_FPU=y
-CONFIG_ARCH_INTERRUPTSTACK=n
-CONFIG_ARCH_STACKDUMP=y
-CONFIG_ARCH_BOOTLOADER=n
-CONFIG_ARCH_LEDS=n
-CONFIG_ARCH_BUTTONS=n
-CONFIG_ARCH_CALIBRATION=n
-CONFIG_ARCH_DMA=y
-CONFIG_ARCH_MATH_H=y
-
-CONFIG_ARMV7M_CMNVECTOR=y
-
-#
-# JTAG Enable settings (by default JTAG-DP and SW-DP are enabled):
-#
-#   CONFIG_STM32_DFU - Use the DFU bootloader, not JTAG (ignored)
-#
-# JTAG Enable options:
-#
-#   CONFIG_STM32_JTAG_FULL_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-#   CONFIG_STM32_JTAG_NOJNTRST_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-#     but without JNTRST.
-#   CONFIG_STM32_JTAG_SW_ENABLE - Set JTAG-DP disabled and SW-DP enabled
-#
-CONFIG_STM32_DFU=n
-CONFIG_STM32_JTAG_FULL_ENABLE=y
-CONFIG_STM32_JTAG_NOJNTRST_ENABLE=n
-CONFIG_STM32_JTAG_SW_ENABLE=n
-
-#
-# On-chip CCM SRAM configuration
-#
-# CONFIG_STM32_CCMEXCLUDE - Exclude CCM SRAM from the HEAP.  You would need
-#   to do this if DMA is enabled to prevent non-DMA-able CCM memory from
-#   being a part of the stack.
-#
-
-#
-# On-board FSMC SRAM configuration
-#
-# CONFIG_STM32_FSMC - Required.  See below
-# CONFIG_MM_REGIONS - Required.  Must be 2 or 3 (see above)
-#
-# CONFIG_STM32_FSMC_SRAM=y - Indicates that SRAM is available via the
-#   FSMC (as opposed to an LCD or FLASH).
-# CONFIG_HEAP2_BASE - The base address of the SRAM in the FSMC address space
-# CONFIG_HEAP2_END - The end (+1) of the SRAM in the FSMC address space
-#
-#CONFIG_STM32_FSMC_SRAM=n
-#CONFIG_HEAP2_BASE=0x64000000
-#CONFIG_HEAP2_END=(0x64000000+(2*1024*1024))
-
-#
-#  Individual subsystems can be enabled:
-#
-# This set is exhaustive for PX4FMU and should be safe to cut and
-# paste into any other config.
-#
-# AHB1:
-CONFIG_STM32_CRC=n
-CONFIG_STM32_BKPSRAM=y
-CONFIG_STM32_CCMDATARAM=y
-CONFIG_STM32_DMA1=y
-CONFIG_STM32_DMA2=y
-CONFIG_STM32_ETHMAC=n
-CONFIG_STM32_OTGHS=n
-# AHB2:
-CONFIG_STM32_DCMI=n
-CONFIG_STM32_CRYP=n
-CONFIG_STM32_HASH=n
-CONFIG_STM32_RNG=n
-CONFIG_STM32_OTGFS=y
-# AHB3:
-CONFIG_STM32_FSMC=n
-# APB1:
-# TIM2 is owned by PWM output
-CONFIG_STM32_TIM2=n
-# TIM3 is owned by TONE_ALARM
-CONFIG_STM32_TIM3=n
-CONFIG_STM32_TIM4=y
-CONFIG_STM32_TIM5=y
-CONFIG_STM32_TIM6=y
-CONFIG_STM32_TIM7=y
-CONFIG_STM32_TIM12=y
-CONFIG_STM32_TIM13=y
-CONFIG_STM32_TIM14=y
-CONFIG_STM32_WWDG=y
-CONFIG_STM32_IWDG=n
-CONFIG_STM32_SPI2=n
-CONFIG_STM32_SPI3=y
-CONFIG_STM32_USART2=y
-CONFIG_STM32_USART3=n
-CONFIG_STM32_UART4=n
-CONFIG_STM32_UART5=y
-CONFIG_STM32_I2C1=y
-CONFIG_STM32_I2C2=y
-CONFIG_STM32_I2C3=y
-CONFIG_STM32_CAN1=n
-CONFIG_STM32_CAN2=n
-CONFIG_STM32_DAC=n
-CONFIG_STM32_PWR=y
-# APB2:
-# TIM1 is owned by the HRT
-CONFIG_STM32_TIM1=n
-# TIM8 is owned by PWM output
-CONFIG_STM32_TIM8=n
-CONFIG_STM32_USART1=y
-CONFIG_STM32_USART6=y
-# We use our own driver, but leave this on.
-CONFIG_STM32_ADC1=y
-CONFIG_STM32_ADC2=n
-CONFIG_STM32_ADC3=n
-CONFIG_STM32_SDIO=n
-CONFIG_STM32_SPI1=y
-CONFIG_STM32_SYSCFG=y
-CONFIG_STM32_TIM9=y
-CONFIG_STM32_TIM10=y
-CONFIG_STM32_TIM11=y
-
-#
-# Enable single wire support.  If this is not defined, then this mode cannot
-# be enabled.
-#
-CONFIG_STM32_USART_SINGLEWIRE=y
-
-#
-# We want the flash prefetch on for max performance.
-#
-STM32_FLASH_PREFETCH=y
-
-#
-# Enable the MTD driver for the onboard I2C EEPROM
-#
-# Note that we are using a private copy of the AT24XX driver that
-# does not require CONFIG_MTD_XT24XX to be set.
-#
-#CONFIG_MTD_AT24XX=y
-CONFIG_AT24XX_ADDR=0x50
-CONFIG_AT24XX_SIZE=128
-CONFIG_AT24XX_MTD_BLOCKSIZE=256
-
-#
-# STM32F40xxx specific serial device driver settings
-#
-# CONFIG_SERIAL_TERMIOS - Serial driver supports termios.h interfaces (tcsetattr,
-#   tcflush, etc.).  If this is not defined, then the terminal settings (baud,
-#   parity, etc.) are not configurable at runtime; serial streams cannot be
-#   flushed, etc.
-# CONFIG_SERIAL_CONSOLE_REINIT - re-initializes the console serial port
-#   immediately after creating the /dev/console device.  This is required
-#   if the console serial port has RX DMA enabled.
-#
-# CONFIG_USARTn_SERIAL_CONSOLE - selects the USARTn for the
-#   console and ttys0 (default is the USART1).
-# CONFIG_USARTn_RXBUFSIZE - Characters are buffered as received.
-#   This specific the size of the receive buffer
-# CONFIG_USARTn_TXBUFSIZE - Characters are buffered before
-#   being sent.  This specific the size of the transmit buffer
-# CONFIG_USARTn_BAUD - The configure BAUD of the UART.  Must be
-# CONFIG_USARTn_BITS - The number of bits.  Must be either 7 or 8.
-# CONFIG_USARTn_PARTIY - 0=no parity, 1=odd parity, 2=even parity
-# CONFIG_USARTn_2STOP - Two stop bits
-#
-CONFIG_SERIAL_TERMIOS=y
-CONFIG_SERIAL_CONSOLE_REINIT=y
-CONFIG_STANDARD_SERIAL=y
-
-CONFIG_USART1_SERIAL_CONSOLE=y
-CONFIG_USART2_SERIAL_CONSOLE=n
-CONFIG_USART3_SERIAL_CONSOLE=n
-CONFIG_UART4_SERIAL_CONSOLE=n
-CONFIG_UART5_SERIAL_CONSOLE=n
-CONFIG_USART6_SERIAL_CONSOLE=n
-
-#Mavlink messages can be bigger than 128
-CONFIG_USART1_TXBUFSIZE=512
-CONFIG_USART2_TXBUFSIZE=256
-CONFIG_USART3_TXBUFSIZE=256
-CONFIG_UART4_TXBUFSIZE=256
-CONFIG_UART5_TXBUFSIZE=256
-CONFIG_USART6_TXBUFSIZE=128
-
-CONFIG_USART1_RXBUFSIZE=512
-CONFIG_USART2_RXBUFSIZE=256
-CONFIG_USART3_RXBUFSIZE=256
-CONFIG_UART4_RXBUFSIZE=256
-CONFIG_UART5_RXBUFSIZE=256
-CONFIG_USART6_RXBUFSIZE=256
-
-CONFIG_USART1_BAUD=57600
-CONFIG_USART2_BAUD=115200
-CONFIG_USART3_BAUD=115200
-CONFIG_UART4_BAUD=115200
-CONFIG_UART5_BAUD=115200
-CONFIG_USART6_BAUD=9600
-
-CONFIG_USART1_BITS=8
-CONFIG_USART2_BITS=8
-CONFIG_USART3_BITS=8
-CONFIG_UART4_BITS=8
-CONFIG_UART5_BITS=8
-CONFIG_USART6_BITS=8
-
-CONFIG_USART1_PARITY=0
-CONFIG_USART2_PARITY=0
-CONFIG_USART3_PARITY=0
-CONFIG_UART4_PARITY=0
-CONFIG_UART5_PARITY=0
-CONFIG_USART6_PARITY=0
-
-CONFIG_USART1_2STOP=0
-CONFIG_USART2_2STOP=0
-CONFIG_USART3_2STOP=0
-CONFIG_UART4_2STOP=0
-CONFIG_UART5_2STOP=0
-CONFIG_USART6_2STOP=0
-
-CONFIG_USART1_RXDMA=y
-SERIAL_HAVE_CONSOLE_DMA=y
-CONFIG_USART2_RXDMA=y
-CONFIG_USART3_RXDMA=n
-CONFIG_UART4_RXDMA=n
-CONFIG_UART5_RXDMA=y
-CONFIG_USART6_RXDMA=y
-
-#
-# PX4FMU specific driver settings
-#
-# CONFIG_HRT_TIMER
-#   Enables the high-resolution timer.  The board definition must
-#   set HRT_TIMER and HRT_TIMER_CHANNEL to the timer and capture/
-#   compare channels to be used.
-# CONFIG_HRT_PPM
-#   Enables R/C PPM input using the HRT.  The board definition must
-#   set HRT_PPM_CHANNEL to the timer capture/compare channel to be
-#   used, and define GPIO_PPM_IN to configure the appropriate timer
-#   GPIO.
-#
-CONFIG_HRT_TIMER=y
-CONFIG_HRT_PPM=y
-
-#
-# STM32F40xxx specific SPI device driver settings
-#
-CONFIG_SPI_EXCHANGE=y
-# DMA needs more work, not implemented on STM32F4x yet
-#CONFIG_STM32_SPI_DMA=y
-
-#
-# STM32F40xxx specific CAN device driver settings
-#
-# CONFIG_CAN - Enables CAN support (one or both of CONFIG_STM32_CAN1 or
-#   CONFIG_STM32_CAN2 must also be defined)
-# CONFIG_CAN_EXTID - Enables support for the 29-bit extended ID.  Default
-#   Standard 11-bit IDs.
-# CONFIG_CAN_FIFOSIZE - The size of the circular buffer of CAN messages.
-#   Default: 8
-# CONFIG_CAN_NPENDINGRTR - The size of the list of pending RTR requests.
-#   Default: 4
-# CONFIG_CAN_LOOPBACK - A CAN driver may or may not support a loopback
-#   mode for testing. The STM32 CAN driver does support loopback mode.
-# CONFIG_CAN1_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN1 is defined.
-# CONFIG_CAN2_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN2 is defined.
-# CONFIG_CAN_TSEG1 - The number of CAN time quanta in segment 1. Default: 6
-# CONFIG_CAN_TSEG2 - the number of CAN time quanta in segment 2. Default: 7
-#
-CONFIG_CAN=n
-CONFIG_CAN_EXTID=n
-#CONFIG_CAN_FIFOSIZE
-#CONFIG_CAN_NPENDINGRTR
-CONFIG_CAN_LOOPBACK=n
-CONFIG_CAN1_BAUD=700000
-CONFIG_CAN2_BAUD=700000
-
-
-# XXX remove after integration testing
-# Allow 180 us per byte, a wide margin for the 400 KHz clock we're using
-# e.g. 9.6 ms for an EEPROM page write, 0.9 ms for a MAG update
-CONFIG_STM32_I2CTIMEOUS_PER_BYTE=200
-# Constant overhead for generating I2C start / stop conditions
-CONFIG_STM32_I2CTIMEOUS_START_STOP=700
-# XXX this is bad and we want it gone
-CONFIG_I2C_WRITEREAD=y
-
-#
-# I2C configuration
-#
-CONFIG_I2C=y
-CONFIG_I2C_POLLED=n
-CONFIG_I2C_TRANSFER=y
-CONFIG_I2C_TRACE=n
-CONFIG_I2C_RESET=y
-# XXX fixed per-transaction timeout
-CONFIG_STM32_I2CTIMEOMS=10
-
-
-# XXX re-enable after integration testing
-
-#
-# I2C configuration
-#
-#CONFIG_I2C=y
-#CONFIG_I2C_POLLED=y
-#CONFIG_I2C_TRANSFER=y
-#CONFIG_I2C_TRACE=n
-#CONFIG_I2C_RESET=y
-
-# Dynamic timeout
-#CONFIG_STM32_I2C_DYNTIMEO=y
-#CONFIG_STM32_I2C_DYNTIMEO_STARTSTOP=500
-#CONFIG_STM32_I2C_DYNTIMEO_USECPERBYTE=200
-
-# Fixed per-transaction timeout
-#CONFIG_STM32_I2CTIMEOSEC=0
-#CONFIG_STM32_I2CTIMEOMS=10
-
-
-
-
-
-
-#
-# General build options
-#
-# CONFIG_RRLOAD_BINARY - make the rrload binary format used with
-#   BSPs from www.ridgerun.com using the tools/mkimage.sh script
-# CONFIG_INTELHEX_BINARY - make the Intel HEX binary format
-#   used with many different loaders using the GNU objcopy program
-#   Should not be selected if you are not using the GNU toolchain.
-# CONFIG_MOTOROLA_SREC - make the Motorola S-Record binary format
-#   used with many different loaders using the GNU objcopy program
-#   Should not be selected if you are not using the GNU toolchain.
-# CONFIG_RAW_BINARY - make a raw binary format file used with many
-#   different loaders using the GNU objcopy program.  This option
-#   should not be selected if you are not using the GNU toolchain.
-# CONFIG_HAVE_LIBM - toolchain supports libm.a
-#
-CONFIG_RRLOAD_BINARY=n
-CONFIG_INTELHEX_BINARY=n
-CONFIG_MOTOROLA_SREC=n
-CONFIG_RAW_BINARY=y
-CONFIG_HAVE_LIBM=y
-
-#
-# General OS setup
-#
-# CONFIG_APPS_DIR - Identifies the relative path to the directory
-#   that builds the application to link with NuttX.  Default: ../apps
-# CONFIG_DEBUG - enables built-in debug options
-# CONFIG_DEBUG_VERBOSE - enables verbose debug output
-# CONFIG_DEBUG_SYMBOLS - build without optimization and with
-#   debug symbols (needed for use with a debugger).
-# CONFIG_HAVE_CXX - Enable support for C++
-# CONFIG_HAVE_CXXINITIALIZE - The platform-specific logic includes support
-#   for initialization of static C++ instances for this architecture
-#   and for the selected toolchain (via up_cxxinitialize()).
-# CONFIG_MM_REGIONS - If the architecture includes multiple
-#   regions of memory to allocate from, this specifies the
-#   number of memory regions that the memory manager must
-#   handle and enables the API mm_addregion(start, end);
-# CONFIG_ARCH_LOWPUTC - architecture supports low-level, boot
-#   time console output
-# CONFIG_MSEC_PER_TICK - The default system timer is 100Hz
-#   or MSEC_PER_TICK=10.  This setting may be defined to
-#   inform NuttX that the processor hardware is providing
-#   system timer interrupts at some interrupt interval other
-#   than 10 msec.
-# CONFIG_RR_INTERVAL - The round robin timeslice will be set
-#   this number of milliseconds;  Round robin scheduling can
-#   be disabled by setting this value to zero.
-# CONFIG_SCHED_INSTRUMENTATION - enables instrumentation in 
-#   scheduler to monitor system performance
-# CONFIG_TASK_NAME_SIZE - Spcifies that maximum size of a
-#   task name to save in the TCB.  Useful if scheduler
-#   instrumentation is selected.  Set to zero to disable.
-# CONFIG_START_YEAR, CONFIG_START_MONTH, CONFIG_START_DAY -
-#   Used to initialize the internal time logic.
-# CONFIG_GREGORIAN_TIME - Enables Gregorian time conversions.
-#   You would only need this if you are concerned about accurate
-#   time conversions in the past or in the distant future.
-# CONFIG_JULIAN_TIME - Enables Julian time conversions. You
-#   would only need this if you are concerned about accurate
-#   time conversion in the distand past.  You must also define
-#   CONFIG_GREGORIAN_TIME in order to use Julian time.
-# CONFIG_DEV_CONSOLE - Set if architecture-specific logic
-#   provides /dev/console.  Enables stdout, stderr, stdin.
-# CONFIG_DEV_LOWCONSOLE - Use the simple, low-level serial console
-#   driver (minimul support)
-# CONFIG_MUTEX_TYPES: Set to enable support for recursive and
-#   errorcheck mutexes. Enables pthread_mutexattr_settype().
-# CONFIG_PRIORITY_INHERITANCE : Set to enable support for priority
-#   inheritance on mutexes and semaphores. 
-# CONFIG_SEM_PREALLOCHOLDERS: This setting is only used if priority
-#   inheritance is enabled.  It defines the maximum number of
-#   different threads (minus one) that can take counts on a
-#   semaphore with priority inheritance support.  This may be 
-#   set to zero if priority inheritance is disabled OR if you
-#   are only using semaphores as mutexes (only one holder) OR
-#   if no more than two threads participate using a counting
-#   semaphore.
-# CONFIG_SEM_NNESTPRIO.  If priority inheritance is enabled,
-#   then this setting is the maximum number of higher priority
-#   threads (minus 1) than can be waiting for another thread
-#   to release a count on a semaphore.  This value may be set
-#   to zero if no more than one thread is expected to wait for
-#   a semaphore.
-# CONFIG_FDCLONE_DISABLE. Disable cloning of all file descriptors
-#   by task_create() when a new task is started.  If set, all
-#   files/drivers will appear to be closed in the new task.
-# CONFIG_FDCLONE_STDIO. Disable cloning of all but the first
-#   three file descriptors (stdin, stdout, stderr) by task_create()
-#   when a new task is started. If set, all files/drivers will
-#   appear to be closed in the new task except for stdin, stdout,
-#   and stderr.
-# CONFIG_SDCLONE_DISABLE. Disable cloning of all socket
-#   desciptors by task_create() when a new task is started. If
-#   set, all sockets will appear to be closed in the new task.
-# CONFIG_SCHED_WORKQUEUE.  Create a dedicated "worker" thread to
-#   handle delayed processing from interrupt handlers.  This feature
-#   is required for some drivers but, if there are not complaints,
-#   can be safely disabled.  The worker thread also performs
-#   garbage collection -- completing any delayed memory deallocations
-#   from interrupt handlers.  If the worker thread is disabled,
-#   then that clean will be performed by the IDLE thread instead
-#   (which runs at the lowest of priority and may not be appropriate
-#   if memory reclamation is of high priority).  If CONFIG_SCHED_WORKQUEUE
-#   is enabled, then the following options can also be used:
-# CONFIG_SCHED_WORKPRIORITY - The execution priority of the worker
-#   thread.  Default: 192
-# CONFIG_SCHED_WORKPERIOD - How often the worker thread checks for
-#   work in units of microseconds.  Default: 50*1000 (50 MS).
-# CONFIG_SCHED_WORKSTACKSIZE - The stack size allocated for the worker
-#   thread.  Default: CONFIG_IDLETHREAD_STACKSIZE.
-# CONFIG_SIG_SIGWORK - The signal number that will be used to wake-up
-#   the worker thread.  Default: 4
-#
-# CONFIG_SCHED_LPWORK. If CONFIG_SCHED_WORKQUEUE is defined, then a single
-#   work queue is created by default.  If CONFIG_SCHED_LPWORK is also defined
-#   then an additional, lower-priority work queue will also be created.  This
-#   lower priority work queue is better suited for more extended processing
-#   (such as file system clean-up operations)
-# CONFIG_SCHED_LPWORKPRIORITY - The execution priority of the lower priority
-#   worker thread.  Default: 50
-# CONFIG_SCHED_LPWORKPERIOD - How often the lower priority worker thread
-#  checks for work in units of microseconds.  Default: 50*1000 (50 MS).
-# CONFIG_SCHED_LPWORKSTACKSIZE - The stack size allocated for the lower
-#   priority worker thread.  Default: CONFIG_IDLETHREAD_STACKSIZE.
-# CONFIG_SCHED_WAITPID - Enable the waitpid() API
-# CONFIG_SCHED_ATEXIT - Enabled the atexit() API
-#
-CONFIG_USER_ENTRYPOINT="nsh_main"
-#CONFIG_APPS_DIR=
-CONFIG_DEBUG=y
-CONFIG_DEBUG_VERBOSE=y
-CONFIG_DEBUG_SYMBOLS=y
-CONFIG_DEBUG_FS=n
-CONFIG_DEBUG_GRAPHICS=n
-CONFIG_DEBUG_LCD=n
-CONFIG_DEBUG_USB=n
-CONFIG_DEBUG_NET=n
-CONFIG_DEBUG_RTC=n
-CONFIG_DEBUG_ANALOG=n
-CONFIG_DEBUG_PWM=n
-CONFIG_DEBUG_CAN=n
-CONFIG_DEBUG_I2C=n
-CONFIG_DEBUG_INPUT=n
-
-CONFIG_HAVE_CXX=y
-CONFIG_HAVE_CXXINITIALIZE=y
-CONFIG_MM_REGIONS=2
-CONFIG_ARCH_LOWPUTC=y
-CONFIG_MSEC_PER_TICK=1
-CONFIG_RR_INTERVAL=0
-CONFIG_SCHED_INSTRUMENTATION=y
-CONFIG_TASK_NAME_SIZE=24
-CONFIG_START_YEAR=1970
-CONFIG_START_MONTH=1
-CONFIG_START_DAY=1
-CONFIG_GREGORIAN_TIME=n
-CONFIG_JULIAN_TIME=n
-CONFIG_DEV_CONSOLE=y
-CONFIG_DEV_LOWCONSOLE=n
-CONFIG_MUTEX_TYPES=n
-CONFIG_PRIORITY_INHERITANCE=y
-CONFIG_SEM_PREALLOCHOLDERS=0
-CONFIG_SEM_NNESTPRIO=8
-CONFIG_FDCLONE_DISABLE=n
-CONFIG_FDCLONE_STDIO=y
-CONFIG_SDCLONE_DISABLE=y
-CONFIG_SCHED_WORKQUEUE=y
-CONFIG_SCHED_WORKPRIORITY=192
-CONFIG_SCHED_WORKPERIOD=5000
-CONFIG_SCHED_WORKSTACKSIZE=2048
-CONFIG_SCHED_LPWORK=y
-CONFIG_SCHED_LPWORKPRIORITY=50
-CONFIG_SCHED_LPWORKPERIOD=50000
-CONFIG_SCHED_LPWORKSTACKSIZE=2048
-CONFIG_SIG_SIGWORK=4
-CONFIG_SCHED_WAITPID=y
-CONFIG_SCHED_ATEXIT=n
-
-#
-# System Logging
-#
-# CONFIG_SYSLOG - Enables the System Logging feature.
-# CONFIG_RAMLOG - Enables the RAM logging feature
-# CONFIG_RAMLOG_CONSOLE - Use the RAM logging device as a system console.
-#   If this feature is enabled (along with CONFIG_DEV_CONSOLE), then all
-#   console output will be re-directed to a circular buffer in RAM.  This
-#   is useful, for example, if the only console is a Telnet console.  Then
-#   in that case, console output from non-Telnet threads will go to the
-#   circular buffer and can be viewed using the NSH 'dmesg' command.
-# CONFIG_RAMLOG_SYSLOG - Use the RAM logging device for the syslogging
-#   interface.  If this feature is enabled (along with CONFIG_SYSLOG),
-#   then all debug output (only) will be re-directed to the circular
-#   buffer in RAM.  This RAM log can be view from NSH using the 'dmesg'
-#   command.
-# CONFIG_RAMLOG_NPOLLWAITERS - The number of threads than can be waiting
-#   for this driver on poll().  Default: 4
-#
-# If CONFIG_RAMLOG_CONSOLE or CONFIG_RAMLOG_SYSLOG is selected, then the
-# following may also be provided:
-#
-# CONFIG_RAMLOG_CONSOLE_BUFSIZE - Size of the console RAM log.  Default: 1024
-#
-
-CONFIG_SYSLOG=n
-CONFIG_RAMLOG=n
-CONFIG_RAMLOG_CONSOLE=n
-CONFIG_RAMLOG_SYSLOG=n
-#CONFIG_RAMLOG_NPOLLWAITERS
-#CONFIG_RAMLOG_CONSOLE_BUFSIZE
-
-#
-# The following can be used to disable categories of
-# APIs supported by the OS.  If the compiler supports
-# weak functions, then it should not be necessary to
-# disable functions unless you want to restrict usage
-# of those APIs.
-#
-# There are certain dependency relationships in these
-# features.
-#
-# o mq_notify logic depends on signals to awaken tasks
-#   waiting for queues to become full or empty.
-# o pthread_condtimedwait() depends on signals to wake
-#   up waiting tasks.
-#
-CONFIG_DISABLE_CLOCK=n
-CONFIG_DISABLE_POSIX_TIMERS=n
-CONFIG_DISABLE_PTHREAD=n
-CONFIG_DISABLE_SIGNALS=n
-CONFIG_DISABLE_MQUEUE=n
-CONFIG_DISABLE_MOUNTPOINT=n
-CONFIG_DISABLE_ENVIRON=n
-CONFIG_DISABLE_POLL=n
-
-#
-# Misc libc settings
-#
-# CONFIG_NOPRINTF_FIELDWIDTH - sprintf-related logic is a
-#   little smaller if we do not support fieldwidthes
-# CONFIG_LIBC_FLOATINGPOINT - Enables printf("%f")
-# CONFIG_LIBC_FIXEDPRECISION - Sets 7 digits after dot for printing:
-#   5.1234567
-# CONFIG_HAVE_LONG_LONG - Enabled printf("%llu)
-# CONFIG_LIBC_STRERR - allow printing of error text
-# CONFIG_LIBC_STRERR_SHORT - allow printing of short error text
-#
-CONFIG_NOPRINTF_FIELDWIDTH=n
-CONFIG_LIBC_FLOATINGPOINT=y
-CONFIG_HAVE_LONG_LONG=y
-CONFIG_LIBC_STRERROR=n
-CONFIG_LIBC_STRERROR_SHORT=n
-
-#
-# Allow for architecture optimized implementations
-#
-# The architecture can provide optimized versions of the
-# following to improve system performance
-#
-CONFIG_ARCH_MEMCPY=y
-CONFIG_ARCH_MEMCMP=n
-CONFIG_ARCH_MEMMOVE=n
-CONFIG_ARCH_MEMSET=n
-CONFIG_ARCH_STRCMP=n
-CONFIG_ARCH_STRCPY=n
-CONFIG_ARCH_STRNCPY=n
-CONFIG_ARCH_STRLEN=n
-CONFIG_ARCH_STRNLEN=n
-CONFIG_ARCH_BZERO=n
-
-#
-# Sizes of configurable things (0 disables)
-#
-# CONFIG_MAX_TASKS - The maximum number of simultaneously
-#   active tasks.  This value must be a power of two.
-# CONFIG_MAX_TASK_ARGS - This controls the maximum number of
-#   of parameters that a task may receive (i.e., maxmum value
-#   of 'argc')
-# CONFIG_NPTHREAD_KEYS - The number of items of thread-
-#   specific data that can be retained
-# CONFIG_NFILE_DESCRIPTORS - The maximum number of file
-#   descriptors (one for each open)
-# CONFIG_NFILE_STREAMS - The maximum number of streams that
-#   can be fopen'ed
-# CONFIG_NAME_MAX - The maximum size of a file name.
-# CONFIG_STDIO_BUFFER_SIZE - Size of the buffer to allocate
-#   on fopen. (Only if CONFIG_NFILE_STREAMS > 0)
-# CONFIG_STDIO_LINEBUFFER - If standard C buffered I/O is enabled
-#   (CONFIG_STDIO_BUFFER_SIZE > 0), then this option may be added
-#   to force automatic, line-oriented flushing the output buffer
-#   for putc(), fputc(), putchar(), puts(), fputs(), printf(),
-#   fprintf(), and vfprintf().  When a newline is encountered in
-#   the output string, the output buffer will be flushed.  This
-#   (slightly) increases the NuttX footprint but supports the kind
-#   of behavior that people expect for printf().
-# CONFIG_NUNGET_CHARS - Number of characters that can be
-#   buffered by ungetc() (Only if CONFIG_NFILE_STREAMS > 0)
-# CONFIG_PREALLOC_MQ_MSGS - The number of pre-allocated message
-#   structures.  The system manages a pool of preallocated
-#   message structures to minimize dynamic allocations
-# CONFIG_MQ_MAXMSGSIZE - Message structures are allocated with
-#   a fixed payload size given by this settin (does not include
-#   other message structure overhead.
-# CONFIG_MAX_WDOGPARMS - Maximum number of parameters that
-#   can be passed to a watchdog handler
-# CONFIG_PREALLOC_WDOGS - The number of pre-allocated watchdog
-#   structures.  The system manages a pool of preallocated
-#   watchdog structures to minimize dynamic allocations
-# CONFIG_PREALLOC_TIMERS - The number of pre-allocated POSIX
-#   timer structures.  The system manages a pool of preallocated
-#   timer structures to minimize dynamic allocations.  Set to
-#   zero for all dynamic allocations.
-#
-CONFIG_MAX_TASKS=32
-CONFIG_MAX_TASK_ARGS=8
-CONFIG_NPTHREAD_KEYS=4
-CONFIG_NFILE_DESCRIPTORS=32
-CONFIG_NFILE_STREAMS=25
-CONFIG_NAME_MAX=32
-CONFIG_STDIO_BUFFER_SIZE=256
-CONFIG_STDIO_LINEBUFFER=y
-CONFIG_NUNGET_CHARS=2
-CONFIG_PREALLOC_MQ_MSGS=4
-CONFIG_MQ_MAXMSGSIZE=32
-CONFIG_MAX_WDOGPARMS=2
-CONFIG_PREALLOC_WDOGS=50
-CONFIG_PREALLOC_TIMERS=50
-
-#
-# Filesystem configuration
-#
-# CONFIG_FS_FAT - Enable FAT filesystem support
-# CONFIG_FAT_SECTORSIZE - Max supported sector size
-# CONFIG_FAT_LCNAMES - Enable use of the NT-style upper/lower case 8.3
-#   file name support.
-# CONFIG_FAT_LFN - Enable FAT long file names.  NOTE:  Microsoft claims
-#   patents on FAT long file name technology.  Please read the
-#   disclaimer in the top-level COPYING file and only enable this
-#   feature if you understand these issues.
-# CONFIG_FAT_MAXFNAME - If CONFIG_FAT_LFN is defined, then the
-#   default, maximum long file name is 255 bytes.  This can eat up
-#   a lot of memory (especially stack space).  If you are willing
-#   to live with some non-standard, short long file names, then
-#   define this value.  A good choice would be the same value as
-#   selected for CONFIG_NAME_MAX which will limit the visibility
-#   of longer file names anyway.
-# CONFIG_FS_NXFFS: Enable NuttX FLASH file system (NXFF) support.
-# CONFIG_NXFFS_ERASEDSTATE: The erased state of FLASH. 
-#   This must have one of the values of 0xff or 0x00.
-#   Default: 0xff.
-# CONFIG_NXFFS_PACKTHRESHOLD: When packing flash file data,
-#   don't both with file chunks smaller than this number of data bytes.
-# CONFIG_NXFFS_MAXNAMLEN: The maximum size of an NXFFS file name.
-#   Default: 255.
-# CONFIG_NXFFS_PACKTHRESHOLD: When packing flash file data,
-#   don't both with file chunks smaller than this number of data bytes.
-#   Default: 32.
-# CONFIG_NXFFS_TAILTHRESHOLD: clean-up can either mean
-#   packing files together toward the end of the file or, if file are
-#   deleted at the end of the file, clean up can simply mean erasing
-#   the end of FLASH memory so that it can be re-used again.  However,
-#   doing this can also harm the life of the FLASH part because it can
-#   mean that the tail end of the FLASH is re-used too often. This
-#   threshold determines if/when it is worth erased the tail end of FLASH
-#   and making it available for re-use (and possible over-wear).
-#   Default: 8192.
-# CONFIG_FS_ROMFS - Enable ROMFS filesystem support
-# CONFIG_FS_RAMMAP - For file systems that do not support XIP, this
-#   option will enable a limited form of memory mapping that is
-#   implemented by copying whole files into memory.
-#
-CONFIG_FS_FAT=y
-CONFIG_FAT_LCNAMES=y
-CONFIG_FAT_LFN=y
-CONFIG_FAT_MAXFNAME=32
-CONFIG_FS_NXFFS=y
-CONFIG_NXFFS_MAXNAMLEN=32
-CONFIG_NXFFS_TAILTHRESHOLD=2048
-CONFIG_NXFFS_PREALLOCATED=y
-CONFIG_FS_ROMFS=y
-CONFIG_FS_BINFS=y
-
-#
-# SPI-based MMC/SD driver
-#
-# CONFIG_MMCSD_NSLOTS
-#   Number of MMC/SD slots supported by the driver
-# CONFIG_MMCSD_READONLY
-#   Provide read-only access (default is read/write)
-# CONFIG_MMCSD_SPICLOCK - Maximum SPI clock to drive MMC/SD card.
-#   Default is 20MHz, current setting 24 MHz
-#
-CONFIG_MMCSD=y
-CONFIG_MMCSD_SPI=y
-CONFIG_MMCSD_NSLOTS=1
-CONFIG_MMCSD_READONLY=n
-CONFIG_MMCSD_SPICLOCK=24000000
-
-#
-# Block driver buffering
-#
-# CONFIG_FS_READAHEAD
-#   Enable read-ahead buffering
-# CONFIG_FS_WRITEBUFFER
-#   Enable write buffering
-#
-CONFIG_FS_READAHEAD=n
-CONFIG_FS_WRITEBUFFER=n
-
-#
-# RTC Configuration
-#
-# CONFIG_RTC - Enables general support for a hardware RTC.  Specific
-#   architectures may require other specific settings.
-# CONFIG_RTC_DATETIME - There are two general types of RTC:  (1) A simple
-#   battery backed counter that keeps the time when power is down, and (2)
-#    A full date / time RTC the provides the date and time information, often
-#   in BCD format.  If CONFIG_RTC_DATETIME is selected, it specifies this
-#   second kind of RTC. In this case, the RTC is used to "seed" the normal
-#   NuttX timer and the NuttX system timer provides for higher resoution
-#   time.
-# CONFIG_RTC_HIRES - If CONFIG_RTC_DATETIME not selected, then the simple,
-#   battery backed counter is used.  There are two different implementations
-#   of such simple counters based on the time resolution of the counter:
-#   The typical RTC keeps time to resolution of 1 second, usually
-#   supporting a 32-bit time_t value.  In this case, the RTC is used to
-#   "seed" the normal NuttX timer and the NuttX timer provides for higher
-#   resoution time. If CONFIG_RTC_HIRES is enabled in the NuttX configuration,
-#   then the RTC provides higher resolution time and completely replaces the
-#   system timer for purpose of date and time.
-# CONFIG_RTC_FREQUENCY - If CONFIG_RTC_HIRES is defined, then the frequency
-#  of the high resolution RTC must be provided.  If CONFIG_RTC_HIRES is
-#   not defined, CONFIG_RTC_FREQUENCY is assumed to be one.
-# CONFIG_RTC_ALARM - Enable if the RTC hardware supports setting of an
-#  alarm.  A callback function will be executed when the alarm goes off
-#
-CONFIG_RTC=n
-CONFIG_RTC_DATETIME=y
-CONFIG_RTC_HIRES=n
-CONFIG_RTC_FREQUENCY=n
-CONFIG_RTC_ALARM=n
-
-#
-# USB Device Configuration
-#
-# CONFIG_USBDEV
-#   Enables USB device support
-# CONFIG_USBDEV_ISOCHRONOUS
-#   Build in extra support for isochronous endpoints
-# CONFIG_USBDEV_DUALSPEED
-#   Hardware handles high and full speed operation (USB 2.0)
-# CONFIG_USBDEV_SELFPOWERED
-#   Will cause USB features to indicate that the device is
-#   self-powered
-# CONFIG_USBDEV_MAXPOWER
-#   Maximum power consumption in mA
-# CONFIG_USBDEV_TRACE
-#   Enables USB tracing for debug
-# CONFIG_USBDEV_TRACE_NRECORDS
-#   Number of trace entries to remember
-#
-CONFIG_USBDEV=y
-CONFIG_USBDEV_ISOCHRONOUS=n
-CONFIG_USBDEV_DUALSPEED=n
-CONFIG_USBDEV_SELFPOWERED=y
-CONFIG_USBDEV_REMOTEWAKEUP=n
-CONFIG_USBDEV_MAXPOWER=500
-CONFIG_USBDEV_TRACE=n
-CONFIG_USBDEV_TRACE_NRECORDS=512
-
-#
-# USB serial device class driver (Standard CDC ACM class)
-#
-# CONFIG_CDCACM
-#   Enable compilation of the USB serial driver
-# CONFIG_CDCACM_CONSOLE
-#   Configures the CDC/ACM serial port as the console device.
-# CONFIG_CDCACM_EP0MAXPACKET
-#   Endpoint 0 max packet size. Default 64
-# CONFIG_CDCACM_EPINTIN
-#   The logical 7-bit address of a hardware endpoint that supports
-#   interrupt IN operation.  Default 2.
-# CONFIG_CDCACM_EPINTIN_FSSIZE
-#   Max package size for the interrupt IN endpoint if full speed mode.
-#   Default 64.
-# CONFIG_CDCACM_EPINTIN_HSSIZE
-#   Max package size for the interrupt IN endpoint if high speed mode.
-#   Default 64
-# CONFIG_CDCACM_EPBULKOUT
-#   The logical 7-bit address of a hardware endpoint that supports
-#   bulk OUT operation.  Default 4.
-# CONFIG_CDCACM_EPBULKOUT_FSSIZE
-#   Max package size for the bulk OUT endpoint if full speed mode.
-#   Default 64.
-# CONFIG_CDCACM_EPBULKOUT_HSSIZE
-#   Max package size for the bulk OUT  endpoint if high speed mode.
-#   Default 512.
-# CONFIG_CDCACM_EPBULKIN
-#   The logical 7-bit address of a hardware endpoint that supports
-#   bulk IN operation.  Default 3.
-# CONFIG_CDCACM_EPBULKIN_FSSIZE
-#   Max package size for the bulk IN endpoint if full speed mode.
-#   Default 64.
-# CONFIG_CDCACM_EPBULKIN_HSSIZE
-#   Max package size for the bulk IN  endpoint if high speed mode.
-#   Default 512.
-# CONFIG_CDCACM_NWRREQS and CONFIG_CDCACM_NRDREQS
-#   The number of write/read requests that can be in flight.
-#   Default 256.
-# CONFIG_CDCACM_VENDORID and CONFIG_CDCACM_VENDORSTR
-#   The vendor ID code/string.  Default 0x0525 and "NuttX"
-#   0x0525 is the Netchip vendor and should not be used in any
-#   products.  This default VID was selected for compatibility with
-#   the Linux CDC ACM default VID.
-# CONFIG_CDCACM_PRODUCTID and CONFIG_CDCACM_PRODUCTSTR
-#   The product ID code/string. Default 0xa4a7 and "CDC/ACM Serial"
-#   0xa4a7 was selected for compatibility with the Linux CDC ACM
-#   default PID.
-# CONFIG_CDCACM_RXBUFSIZE and CONFIG_CDCACM_TXBUFSIZE
-#   Size of the serial receive/transmit buffers. Default 256.
-#
-CONFIG_CDCACM=y
-CONFIG_CDCACM_CONSOLE=n
-#CONFIG_CDCACM_EP0MAXPACKET
-CONFIG_CDCACM_EPINTIN=1
-#CONFIG_CDCACM_EPINTIN_FSSIZE
-#CONFIG_CDCACM_EPINTIN_HSSIZE
-CONFIG_CDCACM_EPBULKOUT=3
-#CONFIG_CDCACM_EPBULKOUT_FSSIZE
-#CONFIG_CDCACM_EPBULKOUT_HSSIZE
-CONFIG_CDCACM_EPBULKIN=2
-#CONFIG_CDCACM_EPBULKIN_FSSIZE
-#CONFIG_CDCACM_EPBULKIN_HSSIZE
-#CONFIG_CDCACM_NWRREQS
-#CONFIG_CDCACM_NRDREQS
-CONFIG_CDCACM_VENDORID=0x26AC
-CONFIG_CDCACM_VENDORSTR="3D Robotics"
-CONFIG_CDCACM_PRODUCTID=0x0010
-CONFIG_CDCACM_PRODUCTSTR="PX4 FMU v1.6"
-#CONFIG_CDCACM_RXBUFSIZE
-#CONFIG_CDCACM_TXBUFSIZE
-
-
-#
-# Settings for apps/nshlib
-#
-# CONFIG_NSH_BUILTIN_APPS - Support external registered,
-#   "named" applications that can be executed from the NSH
-#   command line (see apps/README.txt for more information).
-# CONFIG_NSH_FILEIOSIZE - Size of a static I/O buffer
-# CONFIG_NSH_STRERROR - Use strerror(errno)
-# CONFIG_NSH_LINELEN - Maximum length of one command line
-# CONFIG_NSH_MAX_ARGUMENTS - Maximum number of arguments for command line
-# CONFIG_NSH_NESTDEPTH - Max number of nested if-then[-else]-fi
-# CONFIG_NSH_DISABLESCRIPT - Disable scripting support
-# CONFIG_NSH_DISABLEBG - Disable background commands
-# CONFIG_NSH_ROMFSETC - Use startup script in /etc
-# CONFIG_NSH_CONSOLE - Use serial console front end
-# CONFIG_NSH_TELNET - Use telnetd console front end
-# CONFIG_NSH_ARCHINIT - Platform provides architecture
-#   specific initialization (nsh_archinitialize()).
-#
-# If CONFIG_NSH_TELNET is selected:
-# CONFIG_NSH_IOBUFFER_SIZE -- Telnetd I/O buffer size
-# CONFIG_NSH_DHCPC - Obtain address using DHCP
-# CONFIG_NSH_IPADDR - Provides static IP address
-# CONFIG_NSH_DRIPADDR - Provides static router IP address
-# CONFIG_NSH_NETMASK - Provides static network mask
-# CONFIG_NSH_NOMAC - Use a bogus MAC address
-#
-# If CONFIG_NSH_ROMFSETC is selected:
-# CONFIG_NSH_ROMFSMOUNTPT - ROMFS mountpoint
-# CONFIG_NSH_INITSCRIPT - Relative path to init script
-# CONFIG_NSH_ROMFSDEVNO - ROMFS RAM device minor
-# CONFIG_NSH_ROMFSSECTSIZE - ROMF sector size
-# CONFIG_NSH_FATDEVNO - FAT FS RAM device minor
-# CONFIG_NSH_FATSECTSIZE - FAT FS sector size
-# CONFIG_NSH_FATNSECTORS - FAT FS number of sectors
-# CONFIG_NSH_FATMOUNTPT - FAT FS mountpoint
-#
-CONFIG_BUILTIN=y
-CONFIG_NSH_BUILTIN_APPS=y
-CONFIG_NSH_FILEIOSIZE=512
-CONFIG_NSH_STRERROR=y
-CONFIG_NSH_LINELEN=128
-CONFIG_NSH_MAX_ARGUMENTS=12
-CONFIG_NSH_NESTDEPTH=8
-CONFIG_NSH_DISABLESCRIPT=n
-CONFIG_NSH_DISABLEBG=n
-CONFIG_NSH_ROMFSETC=y
-CONFIG_NSH_ARCHROMFS=y
-CONFIG_NSH_CONSOLE=y
-CONFIG_NSH_USBCONSOLE=n
-CONFIG_NSH_USBCONDEV="/dev/ttyACM0"
-CONFIG_NSH_TELNET=n
-CONFIG_NSH_ARCHINIT=y
-CONFIG_NSH_IOBUFFER_SIZE=512
-CONFIG_NSH_DHCPC=n
-CONFIG_NSH_NOMAC=y
-CONFIG_NSH_IPADDR=0x0a000002
-CONFIG_NSH_DRIPADDR=0x0a000001
-CONFIG_NSH_NETMASK=0xffffff00
-CONFIG_NSH_ROMFSMOUNTPT="/etc"
-CONFIG_NSH_INITSCRIPT="init.d/rcS"
-CONFIG_NSH_ROMFSDEVNO=0
-CONFIG_NSH_ROMFSSECTSIZE=128 # Default 64, increased to allow for more than 64 folders on the sdcard
-CONFIG_NSH_FATDEVNO=1
-CONFIG_NSH_FATSECTSIZE=512
-CONFIG_NSH_FATNSECTORS=1024
-CONFIG_NSH_FATMOUNTPT=/tmp
-
-#
-# Architecture-specific NSH options
-#
-CONFIG_NSH_MMCSDSPIPORTNO=3
-CONFIG_NSH_MMCSDSLOTNO=0
-CONFIG_NSH_MMCSDMINOR=0
-
-
-#
-# Stack and heap information
-#
-# CONFIG_BOOT_RUNFROMFLASH - Some configurations support XIP
-#   operation from FLASH but must copy initialized .data sections to RAM.
-#   (should also be =n for the STM3240G-EVAL which always runs from flash)
-# CONFIG_BOOT_COPYTORAM -  Some configurations boot in FLASH
-#   but copy themselves entirely into RAM for better performance.
-# CONFIG_CUSTOM_STACK - The up_ implementation will handle
-#   all stack operations outside of the nuttx model.
-# CONFIG_STACK_POINTER - The initial stack pointer (arm7tdmi only)
-# CONFIG_IDLETHREAD_STACKSIZE - The size of the initial stack.
-#  This is the thread that (1) performs the inital boot of the system up
-#  to the point where user_start() is spawned, and (2) there after is the
-#  IDLE thread that executes only when there is no other thread ready to
-#  run.
-# CONFIG_USERMAIN_STACKSIZE - The size of the stack to allocate
-#  for the main user thread that begins at the user_start() entry point.
-# CONFIG_PTHREAD_STACK_MIN - Minimum pthread stack size
-# CONFIG_PTHREAD_STACK_DEFAULT - Default pthread stack size
-# CONFIG_HEAP_BASE - The beginning of the heap
-# CONFIG_HEAP_SIZE - The size of the heap
-#
-CONFIG_BOOT_RUNFROMFLASH=n
-CONFIG_BOOT_COPYTORAM=n
-CONFIG_CUSTOM_STACK=n
-CONFIG_STACK_POINTER=
-# Idle thread needs 4096 bytes
-# default 1 KB is not enough
-# 4096 bytes 
-CONFIG_IDLETHREAD_STACKSIZE=6000
-# USERMAIN stack size probably needs to be around 4096 bytes
-CONFIG_USERMAIN_STACKSIZE=4096
-CONFIG_PTHREAD_STACK_MIN=512
-CONFIG_PTHREAD_STACK_DEFAULT=2048
-CONFIG_HEAP_BASE=
-CONFIG_HEAP_SIZE=
-
-# enable bindir 
-CONFIG_APPS_BINDIR=y
diff --git a/nuttx/configs/px4fmu/nsh/setenv.sh b/nuttx/configs/px4fmu/nsh/setenv.sh
deleted file mode 100755
index 265520997..000000000
--- a/nuttx/configs/px4fmu/nsh/setenv.sh
+++ /dev/null
@@ -1,67 +0,0 @@
-#!/bin/bash
-# configs/stm3240g-eval/nsh/setenv.sh
-#
-#   Copyright (C) 2011 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-
-if [ "$_" = "$0" ] ; then
-  echo "You must source this script, not run it!" 1>&2
-  exit 1
-fi
-
-WD=`pwd`
-if [ ! -x "setenv.sh" ]; then
-  echo "This script must be executed from the top-level NuttX build directory"
-  exit 1
-fi
-
-if [ -z "${PATH_ORIG}" ]; then
-  export PATH_ORIG="${PATH}"
-fi
-
-# This the Cygwin path to the location where I installed the RIDE
-# toolchain under windows.  You will also have to edit this if you install
-# the RIDE toolchain in any other location
-#export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/Raisonance/Ride/arm-gcc/bin"
-
-# This the Cygwin path to the location where I installed the CodeSourcery
-# toolchain under windows.  You will also have to edit this if you install
-# the CodeSourcery toolchain in any other location
-export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/CodeSourcery/Sourcery G++ Lite/bin"
-
-# This the Cygwin path to the location where I build the buildroot
-# toolchain.
-#export TOOLCHAIN_BIN="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
-
-# Add the path to the toolchain to the PATH varialble
-export PATH="${TOOLCHAIN_BIN}:/sbin:/usr/sbin:${PATH_ORIG}"
-
-echo "PATH : ${PATH}"
diff --git a/nuttx/configs/px4fmu/src/Makefile b/nuttx/configs/px4fmu/src/Makefile
deleted file mode 100644
index d4276f7fc..000000000
--- a/nuttx/configs/px4fmu/src/Makefile
+++ /dev/null
@@ -1,84 +0,0 @@
-############################################################################
-# configs/px4fmu/src/Makefile
-#
-#   Copyright (C) 2011 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-
--include $(TOPDIR)/Make.defs
-
-CFLAGS		+= -I$(TOPDIR)/sched
-
-ASRCS		= 
-AOBJS		= $(ASRCS:.S=$(OBJEXT))
-
-CSRCS		= empty.c
-COBJS		= $(CSRCS:.c=$(OBJEXT))
-
-SRCS		= $(ASRCS) $(CSRCS)
-OBJS		= $(AOBJS) $(COBJS)
-
-ARCH_SRCDIR	= $(TOPDIR)/arch/$(CONFIG_ARCH)/src
-ifeq ($(WINTOOL),y)
-  CFLAGS	+= -I "${shell cygpath -w $(ARCH_SRCDIR)/chip}" \
-  		   -I "${shell cygpath -w $(ARCH_SRCDIR)/common}" \
-  		   -I "${shell cygpath -w $(ARCH_SRCDIR)/armv7-m}"
-else
-  CFLAGS	+= -I$(ARCH_SRCDIR)/chip -I$(ARCH_SRCDIR)/common -I$(ARCH_SRCDIR)/armv7-m
-endif
-
-all: libboard$(LIBEXT)
-
-$(AOBJS): %$(OBJEXT): %.S
-	$(call ASSEMBLE, $<, $@)
-
-$(COBJS) $(LINKOBJS): %$(OBJEXT): %.c
-	$(call COMPILE, $<, $@)
-
-libboard$(LIBEXT): $(OBJS)
-	$(call ARCHIVE, $@, $(OBJS))
-
-.depend: Makefile $(SRCS)
-	$(Q) $(MKDEP) $(CC) -- $(CFLAGS) -- $(SRCS) >Make.dep
-	$(Q) touch $@
-
-depend: .depend
-
-clean:
-	$(call DELFILE, libboard$(LIBEXT))
-	$(call CLEAN)
-
-distclean: clean
-	$(call DELFILE, Make.dep)
-	$(call DELFILE, .depend)
-
--include Make.dep
-
diff --git a/nuttx/configs/px4fmu/src/empty.c b/nuttx/configs/px4fmu/src/empty.c
deleted file mode 100644
index ace900866..000000000
--- a/nuttx/configs/px4fmu/src/empty.c
+++ /dev/null
@@ -1,4 +0,0 @@
-/*
- * There are no source files here, but libboard.a can't be empty, so 
- * we have this empty source file to keep it company.
- */
diff --git a/nuttx/configs/px4io/README.txt b/nuttx/configs/px4io/README.txt
deleted file mode 100755
index 9b1615f42..000000000
--- a/nuttx/configs/px4io/README.txt
+++ /dev/null
@@ -1,806 +0,0 @@
-README
-======
-
-This README discusses issues unique to NuttX configurations for the
-STMicro STM3210E-EVAL development board.
-
-Contents
-========
-
-  - Development Environment
-  - GNU Toolchain Options
-  - IDEs
-  - NuttX buildroot Toolchain
-  - DFU and JTAG
-  - OpenOCD
-  - LEDs
-  - Temperature Sensor
-  - RTC
-  - STM3210E-EVAL-specific Configuration Options
-  - Configurations
-
-Development Environment
-=======================
-
-  Either Linux or Cygwin on Windows can be used for the development environment.
-  The source has been built only using the GNU toolchain (see below).  Other
-  toolchains will likely cause problems. Testing was performed using the Cygwin
-  environment because the Raisonance R-Link emulatator and some RIDE7 development tools
-  were used and those tools works only under Windows.
-
-GNU Toolchain Options
-=====================
-
-  The NuttX make system has been modified to support the following different
-  toolchain options.
-
-  1. The CodeSourcery GNU toolchain,
-  2. The devkitARM GNU toolchain,
-  3. Raisonance GNU toolchain, or
-  4. The NuttX buildroot Toolchain (see below).
-
-  All testing has been conducted using the NuttX buildroot toolchain.  However,
-  the make system is setup to default to use the devkitARM toolchain.  To use
-  the CodeSourcery, devkitARM or Raisonance GNU toolchain, you simply need to
-  add one of the following configuration options to your .config (or defconfig)
-  file:
-
-    CONFIG_STM32_CODESOURCERYW=y  : CodeSourcery under Windows
-    CONFIG_STM32_CODESOURCERYL=y  : CodeSourcery under Linux
-    CONFIG_STM32_DEVKITARM=y      : devkitARM under Windows
-    CONFIG_STM32_RAISONANCE=y     : Raisonance RIDE7 under Windows
-    CONFIG_STM32_BUILDROOT=y      : NuttX buildroot under Linux or Cygwin (default)
-
-  If you are not using CONFIG_STM32_BUILDROOT, then you may also have to modify
-  the PATH in the setenv.h file if your make cannot find the tools.
-
-  NOTE: the CodeSourcery (for Windows), devkitARM, and Raisonance toolchains are
-  Windows native toolchains.  The CodeSourcey (for Linux) and NuttX buildroot
-  toolchains are Cygwin and/or Linux native toolchains. There are several limitations
-  to using a Windows based toolchain in a Cygwin environment.  The three biggest are:
-
-  1. The Windows toolchain cannot follow Cygwin paths.  Path conversions are
-     performed automatically in the Cygwin makefiles using the 'cygpath' utility
-     but you might easily find some new path problems.  If so, check out 'cygpath -w'
-
-  2. Windows toolchains cannot follow Cygwin symbolic links.  Many symbolic links
-     are used in Nuttx (e.g., include/arch).  The make system works around these
-     problems for the Windows tools by copying directories instead of linking them.
-     But this can also cause some confusion for you:  For example, you may edit
-     a file in a "linked" directory and find that your changes had no effect.
-     That is because you are building the copy of the file in the "fake" symbolic
-     directory.  If you use a Windows toolchain, you should get in the habit of
-     making like this:
-
-       make clean_context all
-
-     An alias in your .bashrc file might make that less painful.
-
-  3. Dependencies are not made when using Windows versions of the GCC.  This is
-     because the dependencies are generated using Windows pathes which do not
-     work with the Cygwin make.
-
-     Support has been added for making dependencies with the windows-native toolchains.
-     That support can be enabled by modifying your Make.defs file as follows:
-
-    -  MKDEP                = $(TOPDIR)/tools/mknulldeps.sh
-    +  MKDEP                = $(TOPDIR)/tools/mkdeps.sh --winpaths "$(TOPDIR)"
-
-     If you have problems with the dependency build (for example, if you are not
-     building on C:), then you may need to modify tools/mkdeps.sh
-
-  NOTE 1: The CodeSourcery toolchain (2009q1) does not work with default optimization
-  level of -Os (See Make.defs).  It will work with -O0, -O1, or -O2, but not with
-  -Os.
-
-  NOTE 2: The devkitARM toolchain includes a version of MSYS make.  Make sure that
-  the paths to Cygwin's /bin and /usr/bin directories appear BEFORE the devkitARM
-  path or will get the wrong version of make.
-
-IDEs
-====
-
-  NuttX is built using command-line make.  It can be used with an IDE, but some
-  effort will be required to create the project (There is a simple RIDE project
-  in the RIDE subdirectory).
-  
-  Makefile Build
-  --------------
-  Under Eclipse, it is pretty easy to set up an "empty makefile project" and
-  simply use the NuttX makefile to build the system.  That is almost for free
-  under Linux.  Under Windows, you will need to set up the "Cygwin GCC" empty
-  makefile project in order to work with Windows (Google for "Eclipse Cygwin" -
-  there is a lot of help on the internet).
-
-  Native Build
-  ------------
-  Here are a few tips before you start that effort:
-
-  1) Select the toolchain that you will be using in your .config file
-  2) Start the NuttX build at least one time from the Cygwin command line
-     before trying to create your project.  This is necessary to create
-     certain auto-generated files and directories that will be needed.
-  3) Set up include pathes:  You will need include/, arch/arm/src/stm32,
-     arch/arm/src/common, arch/arm/src/armv7-m, and sched/.
-  4) All assembly files need to have the definition option -D __ASSEMBLY__
-     on the command line.
-
-  Startup files will probably cause you some headaches.  The NuttX startup file
-  is arch/arm/src/stm32/stm32_vectors.S.  With RIDE, I have to build NuttX
-  one time from the Cygwin command line in order to obtain the pre-built
-  startup object needed by RIDE.
-
-NuttX buildroot Toolchain
-=========================
-
-  A GNU GCC-based toolchain is assumed.  The files */setenv.sh should
-  be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
-  different from the default in your PATH variable).
-
-  If you have no Cortex-M3 toolchain, one can be downloaded from the NuttX
-  SourceForge download site (https://sourceforge.net/project/showfiles.php?group_id=189573).
-  This GNU toolchain builds and executes in the Linux or Cygwin environment.
-
-  1. You must have already configured Nuttx in <some-dir>/nuttx.
-
-     cd tools
-     ./configure.sh stm3210e-eval/<sub-dir>
-
-  2. Download the latest buildroot package into <some-dir>
-
-  3. unpack the buildroot tarball.  The resulting directory may
-     have versioning information on it like buildroot-x.y.z.  If so,
-     rename <some-dir>/buildroot-x.y.z to <some-dir>/buildroot.
-
-  4. cd <some-dir>/buildroot
-
-  5. cp configs/cortexm3-defconfig-4.3.3 .config
-
-  6. make oldconfig
-
-  7. make
-
-  8. Edit setenv.h, if necessary, so that the PATH variable includes
-     the path to the newly built binaries.
-
-  See the file configs/README.txt in the buildroot source tree.  That has more
-  detailed PLUS some special instructions that you will need to follow if you are
-  building a Cortex-M3 toolchain for Cygwin under Windows.
-
-DFU and JTAG
-============
-
-  Enbling Support for the DFU Bootloader
-  --------------------------------------
-  The linker files in these projects can be configured to indicate that you
-  will be loading code using STMicro built-in USB Device Firmware Upgrade (DFU)
-  loader or via some JTAG emulator.  You can specify the DFU bootloader by
-  adding the following line:
-
-    CONFIG_STM32_DFU=y
-
-  to your .config file. Most of the configurations in this directory are set
-  up to use the DFU loader.
-
-  If CONFIG_STM32_DFU is defined, the code will not be positioned at the beginning
-  of FLASH (0x08000000) but will be offset to 0x08003000.  This offset is needed
-  to make space for the DFU loader and 0x08003000 is where the DFU loader expects
-  to find new applications at boot time.  If you need to change that origin for some
-  other bootloader, you will need to edit the file(s) ld.script.dfu for each
-  configuration.
-
-  The DFU SE PC-based software is available from the STMicro website,
-  http://www.st.com.  General usage instructions:
-  
-  1. Convert the NuttX Intel Hex file (nuttx.ihx) into a special DFU
-     file (nuttx.dfu)... see below for details.
-  2. Connect the STM3210E-EVAL board to your computer using a USB
-     cable.
-  3. Start the DFU loader on the STM3210E-EVAL board.  You do this by
-     resetting the board while holding the "Key" button.  Windows should
-     recognize that the DFU loader has been installed.
-  3. Run the DFU SE program to load nuttx.dfu into FLASH.
-
-  What if the DFU loader is not in FLASH?  The loader code is available
-  inside of the Demo dirctory of the USBLib ZIP file that can be downloaded
-  from the STMicro Website.  You can build it using RIDE (or other toolchains);
-  you will need a JTAG emulator to burn it into FLASH the first time.
-
-  In order to use STMicro's built-in DFU loader, you will have to get
-  the NuttX binary into a special format with a .dfu extension.  The
-  DFU SE PC_based software installation includes a file "DFU File Manager"
-  conversion program that a file in Intel Hex format to the special DFU
-  format.  When you successfully build NuttX, you will find a file called
-  nutt.ihx in the top-level directory.  That is the file that you should
-  provide to the DFU File Manager.  You will need to rename it to nuttx.hex
-  in order to find it with the DFU File Manager. You will end up with
-  a file called nuttx.dfu that you can use with the STMicro DFU SE program.
-
-  Enabling JTAG
-  -------------
-  If you are not using the DFU, then you will probably also need to enable
-  JTAG support.  By default, all JTAG support is disabled but there NuttX
-  configuration options to enable JTAG in various different ways.
-
-  These configurations effect the setting of the SWJ_CFG[2:0] bits in the AFIO
-  MAPR register.  These bits are used to configure the SWJ and trace alternate function I/Os. The SWJ (SerialWire JTAG) supports JTAG or SWD access to the
-  Cortex debug port.  The default state in this port is for all JTAG support
-  to be disable.
-
-  CONFIG_STM32_JTAG_FULL_ENABLE - sets SWJ_CFG[2:0] to 000 which enables full
-    SWJ (JTAG-DP + SW-DP)
-
-  CONFIG_STM32_JTAG_NOJNTRST_ENABLE - sets SWJ_CFG[2:0] to 001 which enable
-    full SWJ (JTAG-DP + SW-DP) but without JNTRST.
-
-  CONFIG_STM32_JTAG_SW_ENABLE - sets SWJ_CFG[2:0] to 010 which would set JTAG-DP
-    disabled and SW-DP enabled
-
-  The default setting (none of the above defined) is SWJ_CFG[2:0] set to 100
-  which disable JTAG-DP and SW-DP.
-
-OpenOCD
-=======
-
-I have also used OpenOCD with the STM3210E-EVAL.  In this case, I used
-the Olimex USB ARM OCD.  See the script in configs/stm3210e-eval/tools/oocd.sh
-for more information.  Using the script:
-
-1) Start the OpenOCD GDB server
-
-   cd <nuttx-build-directory>
-   configs/stm3210e-eval/tools/oocd.sh $PWD
-
-2) Load Nuttx
-
-   cd <nuttx-built-directory>
-   arm-none-eabi-gdb nuttx
-   gdb> target remote localhost:3333
-   gdb> mon reset
-   gdb> mon halt
-   gdb> load nuttx
-
-3) Running NuttX
-
-   gdb> mon reset
-   gdb> c
-
-LEDs
-====
-
-The STM3210E-EVAL board has four LEDs labeled LD1, LD2, LD3 and LD4 on the
-board.. These LEDs are not used by the board port unless CONFIG_ARCH_LEDS is
-defined.  In that case, the usage by the board port is defined in
-include/board.h and src/up_leds.c. The LEDs are used to encode OS-related
-events as follows:
-
-    SYMBOL           Meaning                 LED1* LED2  LED3  LED4
-    ---------------- ----------------------- ----- ----- ----- -----
-    LED_STARTED      NuttX has been started  ON    OFF   OFF   OFF
-    LED_HEAPALLOCATE Heap has been allocated OFF   ON    OFF   OFF
-    LED_IRQSENABLED  Interrupts enabled      ON    ON    OFF   OFF
-    LED_STACKCREATED Idle stack created      OFF   OFF   ON    OFF
-    LED_INIRQ        In an interrupt**       ON    N/C   N/C   OFF
-    LED_SIGNAL       In a signal handler***  N/C   ON    N/C   OFF
-    LED_ASSERTION    An assertion failed     ON    ON    N/C   OFF
-    LED_PANIC        The system has crashed  N/C   N/C   N/C   ON
-    LED_IDLE         STM32 is is sleep mode  (Optional, not used)
-
-  * If LED1, LED2, LED3 are statically on, then NuttX probably failed to boot
-    and these LEDs will give you some indication of where the failure was
- ** The normal state is LED3 ON and LED1 faintly glowing.  This faint glow
-    is because of timer interupts that result in the LED being illuminated
-    on a small proportion of the time.
-*** LED2 may also flicker normally if signals are processed.
-
-Temperature Sensor
-==================
-
-Support for the on-board LM-75 temperature sensor is available.  This supported
-has been verified, but has not been included in any of the available the
-configurations.  To set up the temperature sensor, add the following to the
-NuttX configuration file
-
-  CONFIG_I2C=y
-  CONFIG_I2C_LM75=y
-
-Then you can implement logic like the following to use the temperature sensor:
-
-  #include <nuttx/sensors/lm75.h>
-  #include <arch/board/board.h>
-
-  ret =  stm32_lm75initialize("/dev/temp");       /* Register the temperature sensor */
-  fd = open("/dev/temp", O_RDONLY);               /* Open the temperature sensor device */
-  ret = ioctl(fd, SNIOC_FAHRENHEIT, 0);           /* Select Fahrenheit */
-  bytesread = read(fd, buffer, 8*sizeof(b16_t));  /* Read temperature samples */
-
-More complex temperature sensor operations are also available.  See the IOCTAL
-commands enumerated in include/nuttx/sensors/lm75.h.  Also read the descriptions
-of the stm32_lm75initialize() and stm32_lm75attach() interfaces in the
-arch/board/board.h file (sames as configs/stm3210e-eval/include/board.h).
-
-RTC
-===
-
-  The STM32 RTC may configured using the following settings.
-
-    CONFIG_RTC - Enables general support for a hardware RTC. Specific
-      architectures may require other specific settings.
-    CONFIG_RTC_HIRES - The typical RTC keeps time to resolution of 1
-      second, usually supporting a 32-bit time_t value.  In this case,
-      the RTC is used to &quot;seed&quot; the normal NuttX timer and the
-      NuttX timer provides for higher resoution time. If CONFIG_RTC_HIRES
-      is enabled in the NuttX configuration, then the RTC provides higher
-      resolution time and completely replaces the system timer for purpose of
-      date and time.
-      CONFIG_RTC_FREQUENCY - If CONFIG_RTC_HIRES is defined, then the
-      frequency of the high resolution RTC must be provided.  If CONFIG_RTC_HIRES
-      is not defined, CONFIG_RTC_FREQUENCY is assumed to be one.
-    CONFIG_RTC_ALARM - Enable if the RTC hardware supports setting of an alarm. 
-      A callback function will be executed when the alarm goes off
-
-  In hi-res mode, the STM32 RTC operates only at 16384Hz.  Overflow interrupts
-  are handled when the 32-bit RTC counter overflows every 3 days and 43 minutes.
-  A BKP register is incremented on each overflow interrupt creating, effectively,
-  a 48-bit RTC counter.
-
-  In the lo-res mode, the RTC operates at 1Hz.  Overflow interrupts are not handled
-  (because the next overflow is not expected until the year 2106.
-
-   WARNING:  Overflow interrupts are lost whenever the STM32 is powered down.  The
-   overflow interrupt may be lost even if the STM32 is powered down only momentarily.
-   Therefore hi-res solution is only useful in systems where the power is always on.
-
-STM3210E-EVAL-specific Configuration Options
-============================================
-
-    CONFIG_ARCH - Identifies the arch/ subdirectory.  This should
-       be set to:
-
-       CONFIG_ARCH=arm
-
-    CONFIG_ARCH_family - For use in C code:
-
-       CONFIG_ARCH_ARM=y
-
-    CONFIG_ARCH_architecture - For use in C code:
-
-       CONFIG_ARCH_CORTEXM3=y
-
-    CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
-
-       CONFIG_ARCH_CHIP=stm32
-
-    CONFIG_ARCH_CHIP_name - For use in C code to identify the exact
-       chip:
-
-       CONFIG_ARCH_CHIP_STM32F103ZET6
-
-    CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG - Enables special STM32 clock
-       configuration features.
-
-       CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
- 
-    CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
-       hence, the board that supports the particular chip or SoC.
-
-       CONFIG_ARCH_BOARD=stm3210e_eval (for the STM3210E-EVAL development board)
-
-    CONFIG_ARCH_BOARD_name - For use in C code
-
-       CONFIG_ARCH_BOARD_STM3210E_EVAL=y
-
-    CONFIG_ARCH_LOOPSPERMSEC - Must be calibrated for correct operation
-       of delay loops
-
-    CONFIG_ENDIAN_BIG - define if big endian (default is little
-       endian)
-
-    CONFIG_DRAM_SIZE - Describes the installed DRAM (SRAM in this case):
-
-       CONFIG_DRAM_SIZE=0x00010000 (64Kb)
-
-    CONFIG_DRAM_START - The start address of installed DRAM
-
-       CONFIG_DRAM_START=0x20000000
-
-    CONFIG_DRAM_END - Last address+1 of installed RAM
-
-       CONFIG_DRAM_END=(CONFIG_DRAM_START+CONFIG_DRAM_SIZE)
-
-    CONFIG_ARCH_IRQPRIO - The STM32F103Z supports interrupt prioritization
-
-       CONFIG_ARCH_IRQPRIO=y
-
-    CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to boards that
-       have LEDs
-
-    CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt
-       stack. If defined, this symbol is the size of the interrupt
-        stack in bytes.  If not defined, the user task stacks will be
-      used during interrupt handling.
-
-    CONFIG_ARCH_STACKDUMP - Do stack dumps after assertions
-
-    CONFIG_ARCH_LEDS -  Use LEDs to show state. Unique to board architecture.
-
-    CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that
-       cause a 100 second delay during boot-up.  This 100 second delay
-       serves no purpose other than it allows you to calibratre
-       CONFIG_ARCH_LOOPSPERMSEC.  You simply use a stop watch to measure
-       the 100 second delay then adjust CONFIG_ARCH_LOOPSPERMSEC until
-       the delay actually is 100 seconds.
-
-  Individual subsystems can be enabled:
-    AHB
-    ---
-    CONFIG_STM32_DMA1
-    CONFIG_STM32_DMA2
-    CONFIG_STM32_CRC
-    CONFIG_STM32_FSMC
-    CONFIG_STM32_SDIO
-
-    APB1
-    ----
-    CONFIG_STM32_TIM2
-    CONFIG_STM32_TIM3
-    CONFIG_STM32_TIM4
-    CONFIG_STM32_TIM5
-    CONFIG_STM32_TIM6
-    CONFIG_STM32_TIM7
-    CONFIG_STM32_WWDG
-    CONFIG_STM32_SPI2
-    CONFIG_STM32_SPI4
-    CONFIG_STM32_USART2
-    CONFIG_STM32_USART3
-    CONFIG_STM32_UART4
-    CONFIG_STM32_UART5
-    CONFIG_STM32_I2C1
-    CONFIG_STM32_I2C2
-    CONFIG_STM32_USB
-    CONFIG_STM32_CAN
-    CONFIG_STM32_BKP
-    CONFIG_STM32_PWR
-    CONFIG_STM32_DAC1
-    CONFIG_STM32_DAC2
-    CONFIG_STM32_USB
-
-    APB2
-    ----
-    CONFIG_STM32_ADC1
-    CONFIG_STM32_ADC2
-    CONFIG_STM32_TIM1
-    CONFIG_STM32_SPI1
-    CONFIG_STM32_TIM8
-    CONFIG_STM32_USART1
-    CONFIG_STM32_ADC3
-
-  Timer and I2C devices may need to the following to force power to be applied
-  unconditionally at power up.  (Otherwise, the device is powered when it is
-  initialized).
-
-    CONFIG_STM32_FORCEPOWER
-
-  Timer devices may be used for different purposes.  One special purpose is
-  to generate modulated outputs for such things as motor control.  If CONFIG_STM32_TIMn
-  is defined (as above) then the following may also be defined to indicate that
-  the timer is intended to be used for pulsed output modulation, ADC conversion,
-  or DAC conversion.  Note that ADC/DAC require two definition:  Not only do you have
-  to assign the timer (n) for used by the ADC or DAC, but then you also have to
-  configure which ADC or DAC (m) it is assigned to.
-
-    CONFIG_STM32_TIMn_PWM   Reserve timer n for use by PWM, n=1,..,8
-    CONFIG_STM32_TIMn_ADC   Reserve timer n for use by ADC, n=1,..,8
-    CONFIG_STM32_TIMn_ADCm  Reserve timer n to trigger ADCm, n=1,..,8, m=1,..,3
-    CONFIG_STM32_TIMn_DAC   Reserve timer n for use by DAC, n=1,..,8
-    CONFIG_STM32_TIMn_DACm  Reserve timer n to trigger DACm, n=1,..,8, m=1,..,2
-
-  For each timer that is enabled for PWM usage, we need the following additional
-  configuration settings:
-
-    CONFIG_STM32_TIMx_CHANNEL - Specifies the timer output channel {1,..,4}
- 
-  NOTE: The STM32 timers are each capable of generating different signals on
-  each of the four channels with different duty cycles.  That capability is
-  not supported by this driver:  Only one output channel per timer.
-
-  Alternate pin mappings (should not be used with the STM3210E-EVAL board):
-
-    CONFIG_STM32_TIM1_FULL_REMAP
-    CONFIG_STM32_TIM1_PARTIAL_REMAP
-    CONFIG_STM32_TIM2_FULL_REMAP
-    CONFIG_STM32_TIM2_PARTIAL_REMAP_1
-    CONFIG_STM32_TIM2_PARTIAL_REMAP_2
-    CONFIG_STM32_TIM3_FULL_REMAP
-    CONFIG_STM32_TIM3_PARTIAL_REMAP
-    CONFIG_STM32_TIM4_REMAP
-    CONFIG_STM32_USART1_REMAP
-    CONFIG_STM32_USART2_REMAP
-    CONFIG_STM32_USART3_FULL_REMAP
-    CONFIG_STM32_USART3_PARTIAL_REMAP
-    CONFIG_STM32_SPI1_REMAP
-    CONFIG_STM32_SPI3_REMAP
-    CONFIG_STM32_I2C1_REMAP
-    CONFIG_STM32_CAN1_FULL_REMAP
-    CONFIG_STM32_CAN1_PARTIAL_REMAP
-    CONFIG_STM32_CAN2_REMAP
-
-  JTAG Enable settings (by default JTAG-DP and SW-DP are disabled):
-    CONFIG_STM32_JTAG_FULL_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-    CONFIG_STM32_JTAG_NOJNTRST_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-      but without JNTRST.
-    CONFIG_STM32_JTAG_SW_ENABLE - Set JTAG-DP disabled and SW-DP enabled
-
-  STM32F103Z specific device driver settings
-
-    CONFIG_U[S]ARTn_SERIAL_CONSOLE - selects the USARTn (n=1,2,3) or UART
-           m (m=4,5) for the console and ttys0 (default is the USART1).
-    CONFIG_U[S]ARTn_RXBUFSIZE - Characters are buffered as received.
-       This specific the size of the receive buffer
-    CONFIG_U[S]ARTn_TXBUFSIZE - Characters are buffered before
-       being sent.  This specific the size of the transmit buffer
-    CONFIG_U[S]ARTn_BAUD - The configure BAUD of the UART.  Must be
-    CONFIG_U[S]ARTn_BITS - The number of bits.  Must be either 7 or 8.
-    CONFIG_U[S]ARTn_PARTIY - 0=no parity, 1=odd parity, 2=even parity
-    CONFIG_U[S]ARTn_2STOP - Two stop bits
-
-    CONFIG_STM32_SPI_INTERRUPTS - Select to enable interrupt driven SPI
-      support. Non-interrupt-driven, poll-waiting is recommended if the
-      interrupt rate would be to high in the interrupt driven case.
-    CONFIG_STM32_SPI_DMA - Use DMA to improve SPI transfer performance.
-      Cannot be used with CONFIG_STM32_SPI_INTERRUPT.
-
-    CONFIG_SDIO_DMA - Support DMA data transfers.  Requires CONFIG_STM32_SDIO
-      and CONFIG_STM32_DMA2.
-    CONFIG_SDIO_PRI - Select SDIO interrupt prority.  Default: 128
-    CONFIG_SDIO_DMAPRIO - Select SDIO DMA interrupt priority. 
-      Default:  Medium
-    CONFIG_SDIO_WIDTH_D1_ONLY - Select 1-bit transfer mode.  Default:
-      4-bit transfer mode.
-
-  STM3210E-EVAL CAN Configuration
-
-    CONFIG_CAN - Enables CAN support (one or both of CONFIG_STM32_CAN1 or
-      CONFIG_STM32_CAN2 must also be defined)
-    CONFIG_CAN_EXTID - Enables support for the 29-bit extended ID.  Default
-      Standard 11-bit IDs.
-    CONFIG_CAN_FIFOSIZE - The size of the circular buffer of CAN messages.
-      Default: 8
-    CONFIG_CAN_NPENDINGRTR - The size of the list of pending RTR requests.
-      Default: 4
-    CONFIG_CAN_LOOPBACK - A CAN driver may or may not support a loopback
-      mode for testing. The STM32 CAN driver does support loopback mode.
-    CONFIG_CAN1_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN1 is defined.
-    CONFIG_CAN2_BAUD - CAN1 BAUD rate.  Required if CONFIG_STM32_CAN2 is defined.
-    CONFIG_CAN_TSEG1 - The number of CAN time quanta in segment 1. Default: 6
-    CONFIG_CAN_TSEG2 - the number of CAN time quanta in segment 2. Default: 7
-    CONFIG_CAN_REGDEBUG - If CONFIG_DEBUG is set, this will generate an
-      dump of all CAN registers.
-
-  STM3210E-EVAL LCD Hardware Configuration
-
-    CONFIG_LCD_LANDSCAPE - Define for 320x240 display "landscape"
-      support. Default is this 320x240 "landscape" orientation
-      (this setting is informative only... not used).
-    CONFIG_LCD_PORTRAIT - Define for 240x320 display "portrait"
-      orientation support.  In this orientation, the STM3210E-EVAL's
-      LCD ribbon cable is at the bottom of the display. Default is
-      320x240 "landscape" orientation.
-    CONFIG_LCD_RPORTRAIT - Define for 240x320 display "reverse
-      portrait" orientation support.  In this orientation, the
-      STM3210E-EVAL's LCD ribbon cable is at the top of the display.
-      Default is 320x240 "landscape" orientation.
-    CONFIG_LCD_BACKLIGHT - Define to support a backlight.
-    CONFIG_LCD_PWM - If CONFIG_STM32_TIM1 is also defined, then an
-      adjustable backlight will be provided using timer 1 to generate
-      various pulse widthes.  The granularity of the settings is
-      determined by CONFIG_LCD_MAXPOWER.  If CONFIG_LCD_PWM (or
-      CONFIG_STM32_TIM1) is not defined, then a simple on/off backlight
-      is provided.
-    CONFIG_LCD_RDSHIFT - When reading 16-bit gram data, there appears
-      to be a shift in the returned data.  This value fixes the offset.
-      Default 5.
-
-    The LCD driver dynamically selects the LCD based on the reported LCD
-    ID value.  However, code size can be reduced by suppressing support for
-    individual LCDs using:
-
-    CONFIG_STM32_AM240320_DISABLE
-    CONFIG_STM32_SPFD5408B_DISABLE
-    CONFIG_STM32_R61580_DISABLE
-
-Configurations
-==============
-
-Each STM3210E-EVAL configuration is maintained in a sudirectory and
-can be selected as follow:
-
-    cd tools
-    ./configure.sh stm3210e-eval/<subdir>
-    cd -
-    . ./setenv.sh
-
-Where <subdir> is one of the following:
-
-  buttons:
-  --------
-
-    Uses apps/examples/buttons to exercise STM3210E-EVAL buttons and
-    button interrupts.
- 
-    CONFIG_STM32_CODESOURCERYW=y  : CodeSourcery under Windows
-
-  composite
-  ---------
-
-    This configuration exercises a composite USB interface consisting
-    of a CDC/ACM device and a USB mass storage device.  This configuration
-    uses apps/examples/composite.
-
-  nsh and nsh2:
-  ------------
-    Configure the NuttShell (nsh) located at examples/nsh.
-
-    Differences between the two NSH configurations:
-
-    =========== ======================= ================================
-                nsh                     nsh2
-    =========== ======================= ================================
-    Toolchain:  NuttX buildroot for     Codesourcery for Windows (1)
-                Linux or Cygwin (1,2)
-    ----------- ----------------------- --------------------------------
-    Loader:     DfuSe                   DfuSe
-    ----------- ----------------------- --------------------------------
-    Serial      Debug output: USART1    Debug output: USART1
-    Console:    NSH output:   USART1    NSH output:   USART1 (3)
-    ----------- ----------------------- --------------------------------
-    microSD     Yes                     Yes
-    Support
-    ----------- ----------------------- --------------------------------
-    FAT FS      CONFIG_FAT_LCNAME=y     CONFIG_FAT_LCNAME=y
-    Config      CONFIG_FAT_LFN=n        CONFIG_FAT_LFN=y (4)
-    ----------- ----------------------- --------------------------------
-    Support for No                      Yes
-    Built-in
-    Apps
-    ----------- ----------------------- --------------------------------
-    Built-in    None                    apps/examples/nx
-    Apps                                apps/examples/nxhello
-                                        apps/examples/usbstorage (5)
-    =========== ======================= ================================
-
-    (1) You will probably need to modify nsh/setenv.sh or nsh2/setenv.sh
-        to set up the correct PATH variable for whichever toolchain you
-        may use.
-    (2) Since DfuSe is assumed, this configuration may only work under
-        Cygwin without modification.
-    (3) When any other device other than /dev/console is used for a user
-        interface, (1) linefeeds (\n) will not be expanded to carriage return
-        / linefeeds \r\n). You will need to configure your terminal program
-        to account for this. And (2) input is not automatically echoed so
-        you will have to turn local echo on.
-    (4) Microsoft holds several patents related to the design of
-        long file names in the FAT file system.  Please refer to the
-        details in the top-level COPYING file.  Please do not use FAT
-        long file name unless you are familiar with these patent issues.
-    (5) When built as an NSH add-on command (CONFIG_EXAMPLES_USBMSC_BUILTIN=y),
-        Caution should be used to assure that the SD drive is not in use when
-        the USB storage device is configured.  Specifically, the SD driver
-        should be unmounted like:
-
-        nsh> mount -t vfat /dev/mmcsd0 /mnt/sdcard # Card is mounted in NSH
-        ...
-        nsh> umount /mnd/sdcard                    # Unmount before connecting USB!!!
-        nsh> msconn                                # Connect the USB storage device
-        ...
-        nsh> msdis                                 # Disconnect USB storate device
-        nsh> mount -t vfat /dev/mmcsd0 /mnt/sdcard # Restore the mount
-
-        Failure to do this could result in corruption of the SD card format.
-
-  nx:
-  ---
-    An example using the NuttX graphics system (NX).  This example
-    focuses on general window controls, movement, mouse and keyboard
-    input.
-
-    CONFIG_STM32_CODESOURCERYW=y  : CodeSourcery under Windows
-    CONFIG_LCD_RPORTRAIT=y        : 240x320 reverse portrait
-
-  nxlines:
-  ------
-    Another example using the NuttX graphics system (NX).   This
-    example focuses on placing lines on the background in various
-    orientations.
-
-    CONFIG_STM32_CODESOURCERYW=y  : CodeSourcery under Windows
-    CONFIG_LCD_RPORTRAIT=y        : 240x320 reverse portrait
-
-  nxtext:
-  ------
-    Another example using the NuttX graphics system (NX).   This
-    example focuses on placing text on the background while pop-up
-    windows occur.  Text should continue to update normally with
-    or without the popup windows present.
-
-    CONFIG_STM32_BUILDROOT=y      : NuttX buildroot under Linux or Cygwin
-    CONFIG_LCD_RPORTRAIT=y        : 240x320 reverse portrait
-
-    NOTE:  When I tried building this example with the CodeSourcery
-    tools, I got a hardfault inside of its libgcc.  I haven't
-    retested since then, but beware if you choose to change the
-    toolchain.
-
-  ostest:
-  ------
-    This configuration directory, performs a simple OS test using
-    examples/ostest.  By default, this project assumes that you are
-    using the DFU bootloader.
-
-    CONFIG_STM32_BUILDROOT=y      : NuttX buildroot under Linux or Cygwin
-
-  RIDE
-  ----
-    This configuration builds a trivial bring-up binary.  It is
-    useful only because it words with the RIDE7 IDE and R-Link debugger.
-
-    CONFIG_STM32_RAISONANCE=y     : Raisonance RIDE7 under Windows
-
-  usbserial:
-  ---------
-    This configuration directory exercises the USB serial class
-    driver at examples/usbserial.  See examples/README.txt for
-    more information.
-
-    CONFIG_STM32_BUILDROOT=y      : NuttX buildroot under Linux or Cygwin
-
-    USB debug output can be enabled as by changing the following
-    settings in the configuration file:
-
-    -CONFIG_DEBUG=n
-    -CONFIG_DEBUG_VERBOSE=n
-    -CONFIG_DEBUG_USB=n
-    +CONFIG_DEBUG=y
-    +CONFIG_DEBUG_VERBOSE=y
-    +CONFIG_DEBUG_USB=y
-
-    -CONFIG_EXAMPLES_USBSERIAL_TRACEINIT=n
-    -CONFIG_EXAMPLES_USBSERIAL_TRACECLASS=n
-    -CONFIG_EXAMPLES_USBSERIAL_TRACETRANSFERS=n
-    -CONFIG_EXAMPLES_USBSERIAL_TRACECONTROLLER=n
-    -CONFIG_EXAMPLES_USBSERIAL_TRACEINTERRUPTS=n
-    +CONFIG_EXAMPLES_USBSERIAL_TRACEINIT=y
-    +CONFIG_EXAMPLES_USBSERIAL_TRACECLASS=y
-    +CONFIG_EXAMPLES_USBSERIAL_TRACETRANSFERS=y
-    +CONFIG_EXAMPLES_USBSERIAL_TRACECONTROLLER=y
-    +CONFIG_EXAMPLES_USBSERIAL_TRACEINTERRUPTS=y
-
-    By default, the usbserial example uses the Prolific PL2303
-    serial/USB converter emulation.  The example can be modified
-    to use the CDC/ACM serial class by making the following changes
-    to the configuration file:
-
-    -CONFIG_PL2303=y
-    +CONFIG_PL2303=n
-
-    -CONFIG_CDCACM=n
-    +CONFIG_CDCACM=y
-
-    The example can also be converted to use the alternative
-    USB serial example at apps/examples/usbterm by changing the 
-    following:
-
-    -CONFIGURED_APPS += examples/usbserial
-    +CONFIGURED_APPS += examples/usbterm
-
-    In either the original appconfig file (before configuring)
-    or in the final apps/.config file (after configuring).
-
-  usbstorage:
-  ----------
-    This configuration directory exercises the USB mass storage
-    class driver at examples/usbstorage.  See examples/README.txt for
-    more information.
-
-    CONFIG_STM32_BUILDROOT=y      : NuttX buildroot under Linux or Cygwin
-
diff --git a/nuttx/configs/px4io/common/Make.defs b/nuttx/configs/px4io/common/Make.defs
deleted file mode 100644
index 7f782b5b2..000000000
--- a/nuttx/configs/px4io/common/Make.defs
+++ /dev/null
@@ -1,175 +0,0 @@
-############################################################################
-# configs/px4fmu/common/Make.defs
-#
-#   Copyright (C) 2011 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-
-#
-# Generic Make.defs for the PX4FMU
-# Do not specify/use this file directly - it is included by config-specific
-# Make.defs in the per-config directories.
-#
-
-include ${TOPDIR}/tools/Config.mk
-
-#
-# We only support building with the ARM bare-metal toolchain from
-# https://launchpad.net/gcc-arm-embedded on Windows, Linux or Mac OS.
-#
-CONFIG_ARMV7M_TOOLCHAIN	:= GNU_EABI
-
-include ${TOPDIR}/arch/arm/src/armv7-m/Toolchain.defs
-
-CC			 = $(CROSSDEV)gcc
-CXX			 = $(CROSSDEV)g++
-CPP			 = $(CROSSDEV)gcc -E
-LD			 = $(CROSSDEV)ld
-AR			 = $(CROSSDEV)ar rcs
-NM			 = $(CROSSDEV)nm
-OBJCOPY			 = $(CROSSDEV)objcopy
-OBJDUMP			 = $(CROSSDEV)objdump
-
-MAXOPTIMIZATION		 = -O3
-ARCHCPUFLAGS		 = -mcpu=cortex-m3 \
-			   -mthumb \
-			   -march=armv7-m
-
-# enable precise stack overflow tracking
-#INSTRUMENTATIONDEFINES	 = -finstrument-functions \
-#			   -ffixed-r10
-
-# use our linker script
-LDSCRIPT		 = ld.script
-
-ifeq ($(WINTOOL),y)
-  # Windows-native toolchains
-  DIRLINK		 = $(TOPDIR)/tools/copydir.sh
-  DIRUNLINK		 = $(TOPDIR)/tools/unlink.sh
-  MKDEP			 = $(TOPDIR)/tools/mknulldeps.sh
-  ARCHINCLUDES		 = -I. -isystem "${shell cygpath -w $(TOPDIR)/include}"
-  ARCHXXINCLUDES	 = -I. -isystem "${shell cygpath -w $(TOPDIR)/include}" -isystem "${shell cygpath -w $(TOPDIR)/include/cxx}"
-  ARCHSCRIPT		 = -T "${shell cygpath -w $(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/common/$(LDSCRIPT)}"
-else
-  ifeq ($(PX4_WINTOOL),y)
-    # Windows-native toolchains (MSYS)
-    DIRLINK		 = $(TOPDIR)/tools/copydir.sh
-    DIRUNLINK		 = $(TOPDIR)/tools/unlink.sh
-    MKDEP		 = $(TOPDIR)/tools/mknulldeps.sh
-    ARCHINCLUDES	 = -I. -isystem $(TOPDIR)/include
-    ARCHXXINCLUDES	 = -I. -isystem $(TOPDIR)/include -isystem $(TOPDIR)/include/cxx
-    ARCHSCRIPT		 = -T$(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/common/$(LDSCRIPT)
-  else
-    # Linux/Cygwin-native toolchain 
-    MKDEP		 = $(TOPDIR)/tools/mkdeps.sh
-    ARCHINCLUDES	 = -I. -isystem $(TOPDIR)/include
-    ARCHXXINCLUDES	 = -I. -isystem $(TOPDIR)/include -isystem $(TOPDIR)/include/cxx
-    ARCHSCRIPT		 = -T$(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/common/$(LDSCRIPT)
-  endif
-endif
-
-# tool versions
-ARCHCCVERSION		 = ${shell $(CC) -v 2>&1 | sed -n '/^gcc version/p' | sed -e 's/^gcc version \([0-9\.]\)/\1/g' -e 's/[-\ ].*//g' -e '1q'}
-ARCHCCMAJOR		 = ${shell echo $(ARCHCCVERSION) | cut -d'.' -f1}
-
-# optimisation flags
-ARCHOPTIMIZATION	 = $(MAXOPTIMIZATION) \
-			   -fno-strict-aliasing \
-			   -fno-strength-reduce \
-			   -fomit-frame-pointer \
-   			   -funsafe-math-optimizations \
-   			   -fno-builtin-printf \
-   			   -ffunction-sections \
-   			   -fdata-sections
-
-ifeq ("${CONFIG_DEBUG_SYMBOLS}","y")
-ARCHOPTIMIZATION	+= -g
-endif
-
-ARCHCFLAGS		 = -std=gnu99
-ARCHCXXFLAGS		 = -fno-exceptions -fno-rtti -std=gnu++0x
-ARCHWARNINGS		 = -Wall \
-			   -Wextra \
-			   -Wdouble-promotion \
-			   -Wshadow \
-			   -Wfloat-equal \
-			   -Wframe-larger-than=1024 \
-			   -Wpointer-arith \
-			   -Wlogical-op \
-			   -Wmissing-declarations \
-			   -Wpacked \
-			   -Wno-unused-parameter
-#   -Wcast-qual  - generates spurious noreturn attribute warnings, try again later
-#   -Wconversion - would be nice, but too many "risky-but-safe" conversions in the code
-#   -Wcast-align - would help catch bad casts in some cases, but generates too many false positives
-
-ARCHCWARNINGS		 = $(ARCHWARNINGS) \
-			   -Wbad-function-cast \
-			   -Wstrict-prototypes \
-			   -Wold-style-declaration \
-			   -Wmissing-parameter-type \
-			   -Wmissing-prototypes \
-			   -Wnested-externs \
-			   -Wunsuffixed-float-constants
-ARCHWARNINGSXX		 = $(ARCHWARNINGS)
-ARCHDEFINES		 = 
-ARCHPICFLAGS		 = -fpic -msingle-pic-base -mpic-register=r10
-
-# this seems to be the only way to add linker flags
-EXTRA_LIBS		+= --warn-common \
-			   --gc-sections
-
-CFLAGS			 = $(ARCHCFLAGS) $(ARCHCWARNINGS) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHINCLUDES) $(INSTRUMENTATIONDEFINES) $(ARCHDEFINES) $(EXTRADEFINES) -pipe -fno-common
-CPICFLAGS		 = $(ARCHPICFLAGS) $(CFLAGS)
-CXXFLAGS		 = $(ARCHCXXFLAGS) $(ARCHWARNINGSXX) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHXXINCLUDES) $(INSTRUMENTATIONDEFINES) $(ARCHDEFINES) $(EXTRADEFINES) -pipe
-CXXPICFLAGS		 = $(ARCHPICFLAGS) $(CXXFLAGS)
-CPPFLAGS		 = $(ARCHINCLUDES) $(INSTRUMENTATIONDEFINES) $(ARCHDEFINES) $(EXTRADEFINES)
-AFLAGS			 = $(CFLAGS) -D__ASSEMBLY__
-
-NXFLATLDFLAGS1		 = -r -d -warn-common
-NXFLATLDFLAGS2		 = $(NXFLATLDFLAGS1) -T$(TOPDIR)/binfmt/libnxflat/gnu-nxflat.ld -no-check-sections
-LDNXFLATFLAGS		 = -e main -s 2048
-
-OBJEXT			 = .o
-LIBEXT			 = .a
-EXEEXT			 =
-
-# produce partially-linked $1 from files in $2
-define PRELINK
-	@echo "PRELINK: $1"
-	$(Q) $(LD) -Ur -o $1 $2 && $(OBJCOPY) --localize-hidden $1
-endef
-
-HOSTCC			 = gcc
-HOSTINCLUDES		 = -I.
-HOSTCFLAGS		 = -Wall -Wstrict-prototypes -Wshadow -g -pipe
-HOSTLDFLAGS		 =
-
diff --git a/nuttx/configs/px4io/common/ld.script b/nuttx/configs/px4io/common/ld.script
deleted file mode 100755
index 69c2f9cb2..000000000
--- a/nuttx/configs/px4io/common/ld.script
+++ /dev/null
@@ -1,129 +0,0 @@
-/****************************************************************************
- * configs/stm3210e-eval/nsh/ld.script
- *
- *   Copyright (C) 2009, 2011 Gregory Nutt. All rights reserved.
- *   Author: Gregory Nutt <spudmonkey@racsa.co.cr>
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- * 3. Neither the name NuttX nor the names of its contributors may be
- *    used to endorse or promote products derived from this software
- *    without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
- * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
- * POSSIBILITY OF SUCH DAMAGE.
- *
- ****************************************************************************/
-
-/* The STM32F100C8 has 64Kb of FLASH beginning at address 0x0800:0000 and
- * 8Kb of SRAM beginning at address 0x2000:0000.  When booting from FLASH,
- * FLASH memory is aliased to address 0x0000:0000 where the code expects to
- * begin execution by jumping to the entry point in the 0x0800:0000 address
- * range.
- */
-
-MEMORY
-{
-    flash (rx) : ORIGIN = 0x08001000, LENGTH = 60K
-    sram (rwx) : ORIGIN = 0x20000000, LENGTH = 8K
-}
-
-OUTPUT_ARCH(arm)
-ENTRY(__start)		/* treat __start as the anchor for dead code stripping */
-EXTERN(_vectors)	/* force the vectors to be included in the output */
-
-/* 
- * Ensure that abort() is present in the final object.  The exception handling
- * code pulled in by libgcc.a requires it (and that code cannot be easily avoided).
- */
-EXTERN(abort)
-
-SECTIONS
-{
-	.text : {
-		_stext = ABSOLUTE(.);
-		*(.vectors)
-		*(.text .text.*)        
-		*(.fixup)
-		*(.gnu.warning)
-		*(.rodata .rodata.*)        
-		*(.gnu.linkonce.t.*)
-		*(.glue_7)
-		*(.glue_7t)
-		*(.got)
-		*(.gcc_except_table)
-		*(.gnu.linkonce.r.*)
-		_etext = ABSOLUTE(.);
-	} > flash
-
-	/*
-	 * Init functions (static constructors and the like)
-	 */
-        .init_section : {
-                _sinit = ABSOLUTE(.);
-                KEEP(*(.init_array .init_array.*))
-                _einit = ABSOLUTE(.);
-        } > flash
-
-	.ARM.extab : {
-		*(.ARM.extab*)
-	} > flash
-
-	__exidx_start = ABSOLUTE(.);
-	.ARM.exidx : {
-		*(.ARM.exidx*)
-	} > flash
-	__exidx_end = ABSOLUTE(.);
-
-	_eronly = ABSOLUTE(.);
-
-	/* The STM32F100CB has 8Kb of SRAM beginning at the following address */
-
-	.data : {
-		_sdata = ABSOLUTE(.);
-		*(.data .data.*)
-		*(.gnu.linkonce.d.*)
-		CONSTRUCTORS
-		_edata = ABSOLUTE(.);
-	} > sram AT > flash
-
-	.bss : {
-		_sbss = ABSOLUTE(.);
-		*(.bss .bss.*)
-		*(.gnu.linkonce.b.*)
-		*(COMMON)
-		_ebss = ABSOLUTE(.);
-	} > sram
-
-	/* Stabs debugging sections. */
-	.stab 0 : { *(.stab) }
-	.stabstr 0 : { *(.stabstr) }
-	.stab.excl 0 : { *(.stab.excl) }
-	.stab.exclstr 0 : { *(.stab.exclstr) }
-	.stab.index 0 : { *(.stab.index) }
-	.stab.indexstr 0 : { *(.stab.indexstr) }
-	.comment 0 : { *(.comment) }
-	.debug_abbrev 0 : { *(.debug_abbrev) }
-	.debug_info 0 : { *(.debug_info) }
-	.debug_line 0 : { *(.debug_line) }
-	.debug_pubnames 0 : { *(.debug_pubnames) }
-	.debug_aranges 0 : { *(.debug_aranges) }
-}
diff --git a/nuttx/configs/px4io/common/setenv.sh b/nuttx/configs/px4io/common/setenv.sh
deleted file mode 100755
index ff9a4bf8a..000000000
--- a/nuttx/configs/px4io/common/setenv.sh
+++ /dev/null
@@ -1,47 +0,0 @@
-#!/bin/bash
-# configs/stm3210e-eval/dfu/setenv.sh
-#
-#   Copyright (C) 2009 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-
-if [ "$(basename $0)" = "setenv.sh" ] ; then
-  echo "You must source this script, not run it!" 1>&2
-  exit 1
-fi
-
-if [ -z "${PATH_ORIG}" ]; then export PATH_ORIG="${PATH}"; fi
-
-WD=`pwd`
-export RIDE_BIN="/cygdrive/c/Program Files/Raisonance/Ride/arm-gcc/bin"
-export BUILDROOT_BIN="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
-export PATH="${BUILDROOT_BIN}:${RIDE_BIN}:/sbin:/usr/sbin:${PATH_ORIG}"
-
-echo "PATH : ${PATH}"
diff --git a/nuttx/configs/px4io/include/README.txt b/nuttx/configs/px4io/include/README.txt
deleted file mode 100755
index 2264a80aa..000000000
--- a/nuttx/configs/px4io/include/README.txt
+++ /dev/null
@@ -1 +0,0 @@
-This directory contains header files unique to the PX4IO board.
diff --git a/nuttx/configs/px4io/include/board.h b/nuttx/configs/px4io/include/board.h
deleted file mode 100755
index fcbc93620..000000000
--- a/nuttx/configs/px4io/include/board.h
+++ /dev/null
@@ -1,172 +0,0 @@
-/************************************************************************************
- * configs/px4io/include/board.h
- * include/arch/board/board.h
- *
- *   Copyright (C) 2009 Gregory Nutt. All rights reserved.
- *   Author: Gregory Nutt <gnutt@nuttx.org>
- *   Copyright (C) 2012 PX4 Development Team. All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- * 3. Neither the name NuttX nor the names of its contributors may be
- *    used to endorse or promote products derived from this software
- *    without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
- * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
- * POSSIBILITY OF SUCH DAMAGE.
- *
- ************************************************************************************/
-
-#ifndef __ARCH_BOARD_BOARD_H
-#define __ARCH_BOARD_BOARD_H
-
-/************************************************************************************
- * Included Files
- ************************************************************************************/
-
-#include <nuttx/config.h>
-#ifndef __ASSEMBLY__
-# include <stdint.h>
-# include <stdbool.h>
-#endif
-#include <stm32_rcc.h>
-#include <stm32_sdio.h>
-#include <stm32_internal.h>
-
-/************************************************************************************
- * Definitions
- ************************************************************************************/
-
-/* Clocking *************************************************************************/
-
-/* On-board crystal frequency is 24MHz (HSE) */
-
-#define STM32_BOARD_XTAL        24000000ul
-
-/* Use the HSE output as the system clock */
-
-#define STM32_SYSCLK_SW         RCC_CFGR_SW_HSE
-#define STM32_SYSCLK_SWS        RCC_CFGR_SWS_HSE
-#define STM32_SYSCLK_FREQUENCY  STM32_BOARD_XTAL
-
-/* AHB clock (HCLK) is SYSCLK (24MHz) */
-
-#define STM32_RCC_CFGR_HPRE     RCC_CFGR_HPRE_SYSCLK
-#define STM32_HCLK_FREQUENCY    STM32_SYSCLK_FREQUENCY
-#define STM32_BOARD_HCLK        STM32_HCLK_FREQUENCY    /* same as above, to satisfy compiler */
-
-/* APB2 clock (PCLK2) is HCLK (24MHz) */
-
-#define STM32_RCC_CFGR_PPRE2    RCC_CFGR_PPRE2_HCLK
-#define STM32_PCLK2_FREQUENCY   STM32_HCLK_FREQUENCY
-#define STM32_APB2_CLKIN        (STM32_PCLK2_FREQUENCY)   /* Timers 2-4 */
-
-/* APB2 timer 1 will receive PCLK2. */
-
-#define STM32_APB2_TIM1_CLKIN   (STM32_PCLK2_FREQUENCY)
-#define STM32_APB2_TIM8_CLKIN   (STM32_PCLK2_FREQUENCY)
-
-/* APB1 clock (PCLK1) is HCLK (24MHz) */
-
-#define STM32_RCC_CFGR_PPRE1    RCC_CFGR_PPRE1_HCLK
-#define STM32_PCLK1_FREQUENCY   (STM32_HCLK_FREQUENCY)
-
-/* All timers run off PCLK */
-
-#define STM32_APB1_TIM1_CLKIN   (STM32_PCLK2_FREQUENCY)
-#define STM32_APB1_TIM2_CLKIN   (STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM3_CLKIN   (STM32_PCLK1_FREQUENCY)
-#define STM32_APB1_TIM4_CLKIN   (STM32_PCLK1_FREQUENCY)
-
-/*
- * Some of the USART pins are not available; override the GPIO
- * definitions with an invalid pin configuration.
- */
-#undef GPIO_USART2_CTS
-#define GPIO_USART2_CTS	0xffffffff
-#undef GPIO_USART2_RTS
-#define GPIO_USART2_RTS	0xffffffff
-#undef GPIO_USART2_CK
-#define GPIO_USART2_CK 	0xffffffff
-#undef GPIO_USART3_TX
-#define GPIO_USART3_TX 	0xffffffff
-#undef GPIO_USART3_CK
-#define GPIO_USART3_CK 	0xffffffff
-#undef GPIO_USART3_CTS
-#define GPIO_USART3_CTS	0xffffffff
-#undef GPIO_USART3_RTS
-#define GPIO_USART3_RTS	0xffffffff
-
-/* 
- * High-resolution timer
- */
-#ifdef CONFIG_HRT_TIMER
-# define HRT_TIMER		1	/* use timer1 for the HRT */
-# define HRT_TIMER_CHANNEL	2	/* use capture/compare channel 2 */
-#endif
-
-/*
- * PPM
- *
- * PPM input is handled by the HRT timer.
- *
- * Pin is PA8, timer 1, channel 1
- */
-#if defined(CONFIG_HRT_TIMER) && defined (CONFIG_HRT_PPM)
-# define HRT_PPM_CHANNEL	1	/* use capture/compare channel 1 */
-# define GPIO_PPM_IN		GPIO_TIM1_CH1IN
-#endif
-
-/************************************************************************************
- * Public Data
- ************************************************************************************/
-
-#ifndef __ASSEMBLY__
-
-#undef EXTERN
-#if defined(__cplusplus)
-#define EXTERN extern "C"
-extern "C" {
-#else
-#define EXTERN extern
-#endif
-
-/************************************************************************************
- * Public Function Prototypes
- ************************************************************************************/
-/************************************************************************************
- * Name: stm32_boardinitialize
- *
- * Description:
- *   All STM32 architectures must provide the following entry point.  This entry point
- *   is called early in the intitialization -- after all memory has been configured
- *   and mapped but before any devices have been initialized.
- *
- ************************************************************************************/
-
-EXTERN void stm32_boardinitialize(void);
-    
-#if defined(__cplusplus)
-}
-#endif
-
-#endif /* __ASSEMBLY__ */
-#endif  /* __ARCH_BOARD_BOARD_H */
diff --git a/nuttx/configs/px4io/include/drv_i2c_device.h b/nuttx/configs/px4io/include/drv_i2c_device.h
deleted file mode 100644
index 02582bc09..000000000
--- a/nuttx/configs/px4io/include/drv_i2c_device.h
+++ /dev/null
@@ -1,42 +0,0 @@
-/****************************************************************************
- *
- *   Copyright (C) 2012 PX4 Development Team. All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- * 3. Neither the name PX4 nor the names of its contributors may be
- *    used to endorse or promote products derived from this software
- *    without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
- * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
- * POSSIBILITY OF SUCH DAMAGE.
- *
- ****************************************************************************/
-
- /**
-  * @file A simple, polled I2C slave-mode driver.
-  *
-  * The master writes to and reads from a byte buffer, which the caller 
-  * can update inbetween calls to the FSM.
-  */
-
-extern void	i2c_fsm_init(uint8_t *buffer, size_t buffer_size);
-extern bool	i2c_fsm(void);
diff --git a/nuttx/configs/px4io/io/Make.defs b/nuttx/configs/px4io/io/Make.defs
deleted file mode 100644
index 369772d03..000000000
--- a/nuttx/configs/px4io/io/Make.defs
+++ /dev/null
@@ -1,3 +0,0 @@
-include ${TOPDIR}/.config
-
-include $(TOPDIR)/configs/px4io/common/Make.defs
diff --git a/nuttx/configs/px4io/io/appconfig b/nuttx/configs/px4io/io/appconfig
deleted file mode 100644
index 48a41bcdb..000000000
--- a/nuttx/configs/px4io/io/appconfig
+++ /dev/null
@@ -1,32 +0,0 @@
-############################################################################
-#
-#   Copyright (C) 2012 PX4 Development Team. All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name PX4 nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
diff --git a/nuttx/configs/px4io/io/defconfig b/nuttx/configs/px4io/io/defconfig
deleted file mode 100755
index bb937cf4e..000000000
--- a/nuttx/configs/px4io/io/defconfig
+++ /dev/null
@@ -1,548 +0,0 @@
-############################################################################
-# configs/px4io/nsh/defconfig
-#
-#   Copyright (C) 2012 PX4 Development Team. All rights reserved.
-#   Copyright (C) 2011-2012 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-#
-# architecture selection
-#
-# CONFIG_ARCH - identifies the arch subdirectory and, hence, the
-#   processor architecture.
-# CONFIG_ARCH_family - for use in C code.  This identifies the
-#   particular chip family that the architecture is implemented
-#   in.
-# CONFIG_ARCH_architecture - for use in C code.  This identifies the
-#   specific architecture within the chip family.
-# CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
-# CONFIG_ARCH_CHIP_name - For use in C code
-# CONFIG_ARCH_BOARD - identifies the configs subdirectory and, hence,
-#   the board that supports the particular chip or SoC.
-# CONFIG_ARCH_BOARD_name - for use in C code
-# CONFIG_ENDIAN_BIG - define if big endian (default is little endian)
-# CONFIG_BOARD_LOOPSPERMSEC - for delay loops
-# CONFIG_DRAM_SIZE - Describes the installed DRAM.
-# CONFIG_DRAM_START - The start address of DRAM (physical)
-# CONFIG_ARCH_IRQPRIO - The ST32F100CB supports interrupt prioritization
-# CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt
-#   stack. If defined, this symbol is the size of the interrupt
-#   stack in bytes.  If not defined, the user task stacks will be
-#   used during interrupt handling.
-# CONFIG_ARCH_STACKDUMP - Do stack dumps after assertions
-# CONFIG_ARCH_BOOTLOADER - Set if you are using a bootloader.
-# CONFIG_ARCH_LEDS -  Use LEDs to show state. Unique to board architecture.
-# CONFIG_ARCH_BUTTONS -  Enable support for buttons. Unique to board architecture.
-# CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that
-#   cause a 100 second delay during boot-up.  This 100 second delay
-#   serves no purpose other than it allows you to calibrate
-#   CONFIG_BOARD_LOOPSPERMSEC.  You simply use a stop watch to measure
-#   the 100 second delay then adjust CONFIG_BOARD_LOOPSPERMSEC until
-#   the delay actually is 100 seconds.
-# CONFIG_ARCH_DMA - Support DMA initialization
-#
-CONFIG_ARCH="arm"
-CONFIG_ARCH_ARM=y
-CONFIG_ARCH_CORTEXM3=y
-CONFIG_ARCH_CHIP="stm32"
-CONFIG_ARCH_CHIP_STM32F100C8=y
-CONFIG_ARCH_BOARD="px4io"
-CONFIG_ARCH_BOARD_PX4IO=y
-CONFIG_BOARD_LOOPSPERMSEC=2000
-CONFIG_DRAM_SIZE=0x00002000
-CONFIG_DRAM_START=0x20000000
-CONFIG_ARCH_IRQPRIO=y
-CONFIG_ARCH_INTERRUPTSTACK=n
-CONFIG_ARCH_STACKDUMP=y
-CONFIG_ARCH_BOOTLOADER=n
-CONFIG_ARCH_LEDS=n
-CONFIG_ARCH_BUTTONS=n
-CONFIG_ARCH_CALIBRATION=n
-CONFIG_ARCH_DMA=y
-CONFIG_ARCH_MATH_H=y
-
-CONFIG_ARMV7M_CMNVECTOR=y
-
-#
-# JTAG Enable settings (by default JTAG-DP and SW-DP are disabled):
-#
-#   CONFIG_STM32_DFU - Use the DFU bootloader, not JTAG
-#
-# JTAG Enable options:
-#
-#   CONFIG_STM32_JTAG_FULL_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-#   CONFIG_STM32_JTAG_NOJNTRST_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-#     but without JNTRST.
-#   CONFIG_STM32_JTAG_SW_ENABLE - Set JTAG-DP disabled and SW-DP enabled
-#
-CONFIG_STM32_DFU=n
-CONFIG_STM32_JTAG_FULL_ENABLE=y
-CONFIG_STM32_JTAG_NOJNTRST_ENABLE=n
-CONFIG_STM32_JTAG_SW_ENABLE=n
-
-#
-# Individual subsystems can be enabled:
-#
-# AHB: 
-CONFIG_STM32_DMA1=y
-CONFIG_STM32_DMA2=n
-CONFIG_STM32_CRC=n
-# APB1:
-# Timers 2,3 and 4 are owned by the PWM driver
-CONFIG_STM32_TIM2=n
-CONFIG_STM32_TIM3=n
-CONFIG_STM32_TIM4=n
-CONFIG_STM32_TIM5=n
-CONFIG_STM32_TIM6=n
-CONFIG_STM32_TIM7=n
-CONFIG_STM32_WWDG=n
-CONFIG_STM32_SPI2=n
-CONFIG_STM32_USART2=y
-CONFIG_STM32_USART3=y
-CONFIG_STM32_I2C1=y
-CONFIG_STM32_I2C2=n
-CONFIG_STM32_BKP=n
-CONFIG_STM32_PWR=n
-CONFIG_STM32_DAC=n
-# APB2:
-# We use our own ADC driver, but leave this on for clocking purposes.
-CONFIG_STM32_ADC1=y
-CONFIG_STM32_ADC2=n
-# TIM1 is owned by the HRT
-CONFIG_STM32_TIM1=n
-CONFIG_STM32_SPI1=n
-CONFIG_STM32_TIM8=n
-CONFIG_STM32_USART1=y
-CONFIG_STM32_ADC3=n
-
-
-#
-# STM32F100 specific serial device driver settings
-#
-# CONFIG_USARTn_SERIAL_CONSOLE - selects the USARTn for the
-#   console and ttys0 (default is the USART1).
-# CONFIG_USARTn_RXBUFSIZE - Characters are buffered as received.
-#   This specific the size of the receive buffer
-# CONFIG_USARTn_TXBUFSIZE - Characters are buffered before
-#   being sent.  This specific the size of the transmit buffer
-# CONFIG_USARTn_BAUD - The configure BAUD of the UART.  Must be
-# CONFIG_USARTn_BITS - The number of bits.  Must be either 7 or 8.
-# CONFIG_USARTn_PARTIY - 0=no parity, 1=odd parity, 2=even parity
-# CONFIG_USARTn_2STOP - Two stop bits
-#
-CONFIG_SERIAL_TERMIOS=y
-CONFIG_STANDARD_SERIAL=y
-
-CONFIG_USART1_SERIAL_CONSOLE=y
-CONFIG_USART2_SERIAL_CONSOLE=n
-CONFIG_USART3_SERIAL_CONSOLE=n
-
-CONFIG_USART1_TXBUFSIZE=64
-CONFIG_USART2_TXBUFSIZE=64
-CONFIG_USART3_TXBUFSIZE=64
-
-CONFIG_USART1_RXBUFSIZE=64
-CONFIG_USART2_RXBUFSIZE=64
-CONFIG_USART3_RXBUFSIZE=64
-
-CONFIG_USART1_BAUD=115200
-CONFIG_USART2_BAUD=115200
-CONFIG_USART3_BAUD=115200
-
-CONFIG_USART1_BITS=8
-CONFIG_USART2_BITS=8
-CONFIG_USART3_BITS=8
-
-CONFIG_USART1_PARITY=0
-CONFIG_USART2_PARITY=0
-CONFIG_USART3_PARITY=0
-
-CONFIG_USART1_2STOP=0
-CONFIG_USART2_2STOP=0
-CONFIG_USART3_2STOP=0
-
-CONFIG_USART1_RXDMA=y
-SERIAL_HAVE_CONSOLE_DMA=y
-# Conflicts with I2C1 DMA
-CONFIG_USART2_RXDMA=n
-CONFIG_USART3_RXDMA=y
-
-#
-# PX4IO specific driver settings
-#
-# CONFIG_HRT_TIMER
-#   Enables the high-resolution timer.  The board definition must
-#   set HRT_TIMER and HRT_TIMER_CHANNEL to the timer and capture/
-#   compare channels to be used.
-# CONFIG_HRT_PPM
-#   Enables R/C PPM input using the HRT.  The board definition must
-#   set HRT_PPM_CHANNEL to the timer capture/compare channel to be
-#   used, and define GPIO_PPM_IN to configure the appropriate timer
-#   GPIO.
-# CONFIG_PWM_SERVO
-#   Enables the PWM servo driver.  The driver configuration must be
-#   supplied by the board support at initialisation time.
-#   Note that USART2 must be disabled on the PX4 board for this to
-#   be available.
-#
-#
-CONFIG_HRT_TIMER=y
-CONFIG_HRT_PPM=y
-
-#
-# General build options
-#
-# CONFIG_RRLOAD_BINARY - make the rrload binary format used with
-#   BSPs from www.ridgerun.com using the tools/mkimage.sh script
-# CONFIG_INTELHEX_BINARY - make the Intel HEX binary format
-#   used with many different loaders using the GNU objcopy program
-#   Should not be selected if you are not using the GNU toolchain.
-# CONFIG_MOTOROLA_SREC - make the Motorola S-Record binary format
-#   used with many different loaders using the GNU objcopy program
-#   Should not be selected if you are not using the GNU toolchain.
-# CONFIG_RAW_BINARY - make a raw binary format file used with many
-#   different loaders using the GNU objcopy program.  This option
-#   should not be selected if you are not using the GNU toolchain.
-# CONFIG_HAVE_LIBM - toolchain supports libm.a
-#
-CONFIG_RRLOAD_BINARY=n
-CONFIG_INTELHEX_BINARY=n
-CONFIG_MOTOROLA_SREC=n
-CONFIG_RAW_BINARY=y
-CONFIG_HAVE_LIBM=n
-
-#
-# General OS setup
-#
-# CONFIG_APPS_DIR - Identifies the relative path to the directory
-#   that builds the application to link with NuttX.  Default: ../apps
-# CONFIG_DEBUG - enables built-in debug options
-# CONFIG_DEBUG_VERBOSE - enables verbose debug output
-# CONFIG_DEBUG_SYMBOLS - build without optimization and with
-#   debug symbols (needed for use with a debugger).
-# CONFIG_HAVE_CXX - Enable support for C++
-# CONFIG_HAVE_CXXINITIALIZE - The platform-specific logic includes support
-#   for initialization of static C++ instances for this architecture
-#   and for the selected toolchain (via up_cxxinitialize()).
-# CONFIG_MM_REGIONS - If the architecture includes multiple
-#   regions of memory to allocate from, this specifies the
-#   number of memory regions that the memory manager must
-#   handle and enables the API mm_addregion(start, end);
-# CONFIG_ARCH_LOWPUTC - architecture supports low-level, boot
-#   time console output
-# CONFIG_MSEC_PER_TICK - The default system timer is 100Hz
-#   or MSEC_PER_TICK=10.  This setting may be defined to
-#   inform NuttX that the processor hardware is providing
-#   system timer interrupts at some interrupt interval other
-#   than 10 msec.
-# CONFIG_RR_INTERVAL - The round robin timeslice will be set
-#   this number of milliseconds;  Round robin scheduling can
-#   be disabled by setting this value to zero.
-# CONFIG_SCHED_INSTRUMENTATION - enables instrumentation in 
-#   scheduler to monitor system performance
-# CONFIG_TASK_NAME_SIZE - Spcifies that maximum size of a
-#   task name to save in the TCB.  Useful if scheduler
-#   instrumentation is selected.  Set to zero to disable.
-# CONFIG_START_YEAR, CONFIG_START_MONTH, CONFIG_START_DAY -
-#   Used to initialize the internal time logic.
-# CONFIG_GREGORIAN_TIME - Enables Gregorian time conversions.
-#   You would only need this if you are concerned about accurate
-#   time conversions in the past or in the distant future.
-# CONFIG_JULIAN_TIME - Enables Julian time conversions. You
-#   would only need this if you are concerned about accurate
-#   time conversion in the distand past.  You must also define
-#   CONFIG_GREGORIAN_TIME in order to use Julian time.
-# CONFIG_DEV_CONSOLE - Set if architecture-specific logic
-#   provides /dev/console.  Enables stdout, stderr, stdin.
-# CONFIG_DEV_LOWCONSOLE - Use the simple, low-level serial console
-#   driver (minimul support)
-# CONFIG_MUTEX_TYPES: Set to enable support for recursive and
-#   errorcheck mutexes. Enables pthread_mutexattr_settype().
-# CONFIG_PRIORITY_INHERITANCE : Set to enable support for priority
-#   inheritance on mutexes and semaphores. 
-# CONFIG_SEM_PREALLOCHOLDERS: This setting is only used if priority
-#   inheritance is enabled.  It defines the maximum number of
-#   different threads (minus one) that can take counts on a
-#   semaphore with priority inheritance support.  This may be 
-#   set to zero if priority inheritance is disabled OR if you
-#   are only using semaphores as mutexes (only one holder) OR
-#   if no more than two threads participate using a counting
-#   semaphore.
-# CONFIG_SEM_NNESTPRIO.  If priority inheritance is enabled,
-#   then this setting is the maximum number of higher priority
-#   threads (minus 1) than can be waiting for another thread
-#   to release a count on a semaphore.  This value may be set
-#   to zero if no more than one thread is expected to wait for
-#   a semaphore.
-# CONFIG_FDCLONE_DISABLE. Disable cloning of all file descriptors
-#   by task_create() when a new task is started.  If set, all
-#   files/drivers will appear to be closed in the new task.
-# CONFIG_FDCLONE_STDIO. Disable cloning of all but the first
-#   three file descriptors (stdin, stdout, stderr) by task_create()
-#   when a new task is started. If set, all files/drivers will
-#   appear to be closed in the new task except for stdin, stdout,
-#   and stderr.
-# CONFIG_SDCLONE_DISABLE. Disable cloning of all socket
-#   desciptors by task_create() when a new task is started. If
-#   set, all sockets will appear to be closed in the new task.
-# CONFIG_SCHED_WORKQUEUE.  Create a dedicated "worker" thread to
-#  handle delayed processing from interrupt handlers.  This feature
-#  is required for some drivers but, if there are not complaints,
-#  can be safely disabled.  The worker thread also performs
-#  garbage collection -- completing any delayed memory deallocations
-#  from interrupt handlers.  If the worker thread is disabled,
-#  then that clean will be performed by the IDLE thread instead
-#  (which runs at the lowest of priority and may not be appropriate
-#  if memory reclamation is of high priority).  If CONFIG_SCHED_WORKQUEUE
-#  is enabled, then the following options can also be used:
-# CONFIG_SCHED_WORKPRIORITY - The execution priority of the worker
-#  thread.  Default: 50
-# CONFIG_SCHED_WORKPERIOD - How often the worker thread checks for
-#  work in units of microseconds.  Default: 50*1000 (50 MS).
-# CONFIG_SCHED_WORKSTACKSIZE - The stack size allocated for the worker
-#  thread.  Default: CONFIG_IDLETHREAD_STACKSIZE.
-# CONFIG_SIG_SIGWORK - The signal number that will be used to wake-up
-#  the worker thread.  Default: 4
-# CONFIG_SCHED_WAITPID - Enable the waitpid() API
-# CONFIG_SCHED_ATEXIT - Enabled the atexit() API
-#
-CONFIG_USER_ENTRYPOINT="user_start"
-#CONFIG_APPS_DIR=
-CONFIG_DEBUG=n
-CONFIG_DEBUG_VERBOSE=n
-CONFIG_DEBUG_SYMBOLS=y
-CONFIG_DEBUG_FS=n
-CONFIG_DEBUG_GRAPHICS=n
-CONFIG_DEBUG_LCD=n
-CONFIG_DEBUG_USB=n
-CONFIG_DEBUG_NET=n
-CONFIG_DEBUG_RTC=n
-CONFIG_DEBUG_ANALOG=n
-CONFIG_DEBUG_PWM=n
-CONFIG_DEBUG_CAN=n
-CONFIG_DEBUG_I2C=n
-CONFIG_DEBUG_INPUT=n
-
-CONFIG_MSEC_PER_TICK=1
-CONFIG_HAVE_CXX=y
-CONFIG_HAVE_CXXINITIALIZE=y
-CONFIG_MM_REGIONS=1
-CONFIG_MM_SMALL=y
-CONFIG_ARCH_LOWPUTC=y
-CONFIG_RR_INTERVAL=0
-CONFIG_SCHED_INSTRUMENTATION=n
-CONFIG_TASK_NAME_SIZE=8
-CONFIG_START_YEAR=1970
-CONFIG_START_MONTH=1
-CONFIG_START_DAY=1
-CONFIG_GREGORIAN_TIME=n
-CONFIG_JULIAN_TIME=n
-# this eats ~1KiB of RAM ... work out why
-CONFIG_DEV_CONSOLE=y
-CONFIG_DEV_LOWCONSOLE=n
-CONFIG_MUTEX_TYPES=n
-CONFIG_PRIORITY_INHERITANCE=n
-CONFIG_SEM_PREALLOCHOLDERS=0
-CONFIG_SEM_NNESTPRIO=0
-CONFIG_FDCLONE_DISABLE=y
-CONFIG_FDCLONE_STDIO=y
-CONFIG_SDCLONE_DISABLE=y
-CONFIG_SCHED_WORKQUEUE=n
-CONFIG_SCHED_WORKPRIORITY=50
-CONFIG_SCHED_WORKPERIOD=50000
-CONFIG_SCHED_WORKSTACKSIZE=1024
-CONFIG_SIG_SIGWORK=4
-CONFIG_SCHED_WAITPID=n
-CONFIG_SCHED_ATEXIT=n
-
-#
-# The following can be used to disable categories of
-# APIs supported by the OS.  If the compiler supports
-# weak functions, then it should not be necessary to
-# disable functions unless you want to restrict usage
-# of those APIs.
-#
-# There are certain dependency relationships in these
-# features.
-#
-# o mq_notify logic depends on signals to awaken tasks
-#   waiting for queues to become full or empty.
-# o pthread_condtimedwait() depends on signals to wake
-#   up waiting tasks.
-#
-CONFIG_DISABLE_CLOCK=n
-CONFIG_DISABLE_POSIX_TIMERS=y
-CONFIG_DISABLE_PTHREAD=y
-CONFIG_DISABLE_SIGNALS=y
-CONFIG_DISABLE_MQUEUE=y
-CONFIG_DISABLE_MOUNTPOINT=y
-CONFIG_DISABLE_ENVIRON=y
-CONFIG_DISABLE_POLL=y
-
-#
-# Misc libc settings
-#
-# CONFIG_NOPRINTF_FIELDWIDTH - sprintf-related logic is a
-#   little smaller if we do not support fieldwidthes
-#
-CONFIG_NOPRINTF_FIELDWIDTH=n
-
-#
-# Allow for architecture optimized implementations
-#
-# The architecture can provide optimized versions of the
-# following to improve system performance
-#
-CONFIG_ARCH_MEMCPY=n
-CONFIG_ARCH_MEMCMP=n
-CONFIG_ARCH_MEMMOVE=n
-CONFIG_ARCH_MEMSET=n
-CONFIG_ARCH_STRCMP=n
-CONFIG_ARCH_STRCPY=n
-CONFIG_ARCH_STRNCPY=n
-CONFIG_ARCH_STRLEN=n
-CONFIG_ARCH_STRNLEN=n
-CONFIG_ARCH_BZERO=n
-
-#
-# Sizes of configurable things (0 disables)
-#
-# CONFIG_MAX_TASKS - The maximum number of simultaneously
-#   active tasks.  This value must be a power of two.
-# CONFIG_MAX_TASK_ARGS - This controls the maximum number of
-#   of parameters that a task may receive (i.e., maxmum value
-#   of 'argc')
-# CONFIG_NPTHREAD_KEYS - The number of items of thread-
-#   specific data that can be retained
-# CONFIG_NFILE_DESCRIPTORS - The maximum number of file
-#   descriptors (one for each open)
-# CONFIG_NFILE_STREAMS - The maximum number of streams that
-#   can be fopen'ed
-# CONFIG_NAME_MAX - The maximum size of a file name.
-# CONFIG_STDIO_BUFFER_SIZE - Size of the buffer to allocate
-#   on fopen. (Only if CONFIG_NFILE_STREAMS > 0)
-# CONFIG_STDIO_LINEBUFFER - If standard C buffered I/O is enabled
-#   (CONFIG_STDIO_BUFFER_SIZE > 0), then this option may be added
-#   to force automatic, line-oriented flushing the output buffer
-#   for putc(), fputc(), putchar(), puts(), fputs(), printf(),
-#   fprintf(), and vfprintf().  When a newline is encountered in
-#   the output string, the output buffer will be flushed.  This
-#   (slightly) increases the NuttX footprint but supports the kind
-#   of behavior that people expect for printf().
-# CONFIG_NUNGET_CHARS - Number of characters that can be
-#   buffered by ungetc() (Only if CONFIG_NFILE_STREAMS > 0)
-# CONFIG_PREALLOC_MQ_MSGS - The number of pre-allocated message
-#   structures.  The system manages a pool of preallocated
-#   message structures to minimize dynamic allocations
-# CONFIG_MQ_MAXMSGSIZE - Message structures are allocated with
-#   a fixed payload size given by this settin (does not include
-#   other message structure overhead.
-# CONFIG_MAX_WDOGPARMS - Maximum number of parameters that
-#   can be passed to a watchdog handler
-# CONFIG_PREALLOC_WDOGS - The number of pre-allocated watchdog
-#   structures.  The system manages a pool of preallocated
-#   watchdog structures to minimize dynamic allocations
-# CONFIG_PREALLOC_TIMERS - The number of pre-allocated POSIX
-#   timer structures.  The system manages a pool of preallocated
-#   timer structures to minimize dynamic allocations.  Set to
-#   zero for all dynamic allocations.
-#
-CONFIG_MAX_TASKS=4
-CONFIG_MAX_TASK_ARGS=4
-CONFIG_NPTHREAD_KEYS=2
-CONFIG_NFILE_DESCRIPTORS=8
-CONFIG_NFILE_STREAMS=0
-CONFIG_NAME_MAX=12
-CONFIG_STDIO_BUFFER_SIZE=32
-CONFIG_STDIO_LINEBUFFER=n
-CONFIG_NUNGET_CHARS=2
-CONFIG_PREALLOC_MQ_MSGS=4
-CONFIG_MQ_MAXMSGSIZE=32
-CONFIG_MAX_WDOGPARMS=2
-CONFIG_PREALLOC_WDOGS=4
-CONFIG_PREALLOC_TIMERS=0
-
-
-#
-# Settings for apps/nshlib
-#
-# CONFIG_NSH_BUILTIN_APPS - Support external registered,
-#   "named" applications that can be executed from the NSH
-#   command line (see apps/README.txt for more information).
-# CONFIG_NSH_FILEIOSIZE - Size of a static I/O buffer
-# CONFIG_NSH_STRERROR - Use strerror(errno)
-# CONFIG_NSH_LINELEN - Maximum length of one command line
-# CONFIG_NSH_NESTDEPTH - Max number of nested if-then[-else]-fi
-# CONFIG_NSH_DISABLESCRIPT - Disable scripting support
-# CONFIG_NSH_DISABLEBG - Disable background commands
-# CONFIG_NSH_ROMFSETC - Use startup script in /etc
-# CONFIG_NSH_CONSOLE - Use serial console front end
-# CONFIG_NSH_TELNET - Use telnetd console front end
-# CONFIG_NSH_ARCHINIT - Platform provides architecture
-#   specific initialization (nsh_archinitialize()).
-#
-
-# Disable NSH completely
-CONFIG_NSH_CONSOLE=n
-
-#
-# Stack and heap information
-#
-# CONFIG_BOOT_RUNFROMFLASH - Some configurations support XIP
-#   operation from FLASH but must copy initialized .data sections to RAM.
-#   (should also be =n for the STM3210E-EVAL which always runs from flash)
-# CONFIG_BOOT_COPYTORAM -  Some configurations boot in FLASH
-#   but copy themselves entirely into RAM for better performance.
-# CONFIG_CUSTOM_STACK - The up_ implementation will handle
-#   all stack operations outside of the nuttx model.
-# CONFIG_STACK_POINTER - The initial stack pointer (arm7tdmi only)
-# CONFIG_IDLETHREAD_STACKSIZE - The size of the initial stack.
-#  This is the thread that (1) performs the inital boot of the system up
-#  to the point where user_start() is spawned, and (2) there after is the
-#  IDLE thread that executes only when there is no other thread ready to
-#  run.
-# CONFIG_USERMAIN_STACKSIZE - The size of the stack to allocate
-#  for the main user thread that begins at the user_start() entry point.
-# CONFIG_PTHREAD_STACK_MIN - Minimum pthread stack size
-# CONFIG_PTHREAD_STACK_DEFAULT - Default pthread stack size
-# CONFIG_HEAP_BASE - The beginning of the heap
-# CONFIG_HEAP_SIZE - The size of the heap
-#
-CONFIG_BOOT_RUNFROMFLASH=n
-CONFIG_BOOT_COPYTORAM=n
-CONFIG_CUSTOM_STACK=n
-CONFIG_STACK_POINTER=
-CONFIG_IDLETHREAD_STACKSIZE=1024
-CONFIG_USERMAIN_STACKSIZE=1200
-CONFIG_PTHREAD_STACK_MIN=512
-CONFIG_PTHREAD_STACK_DEFAULT=1024
-CONFIG_HEAP_BASE=
-CONFIG_HEAP_SIZE=
diff --git a/nuttx/configs/px4io/io/setenv.sh b/nuttx/configs/px4io/io/setenv.sh
deleted file mode 100755
index ff9a4bf8a..000000000
--- a/nuttx/configs/px4io/io/setenv.sh
+++ /dev/null
@@ -1,47 +0,0 @@
-#!/bin/bash
-# configs/stm3210e-eval/dfu/setenv.sh
-#
-#   Copyright (C) 2009 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-
-if [ "$(basename $0)" = "setenv.sh" ] ; then
-  echo "You must source this script, not run it!" 1>&2
-  exit 1
-fi
-
-if [ -z "${PATH_ORIG}" ]; then export PATH_ORIG="${PATH}"; fi
-
-WD=`pwd`
-export RIDE_BIN="/cygdrive/c/Program Files/Raisonance/Ride/arm-gcc/bin"
-export BUILDROOT_BIN="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
-export PATH="${BUILDROOT_BIN}:${RIDE_BIN}:/sbin:/usr/sbin:${PATH_ORIG}"
-
-echo "PATH : ${PATH}"
diff --git a/nuttx/configs/px4io/nsh/Make.defs b/nuttx/configs/px4io/nsh/Make.defs
deleted file mode 100644
index 87508e22e..000000000
--- a/nuttx/configs/px4io/nsh/Make.defs
+++ /dev/null
@@ -1,3 +0,0 @@
-include ${TOPDIR}/.config
-
-include $(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/common/Make.defs
diff --git a/nuttx/configs/px4io/nsh/appconfig b/nuttx/configs/px4io/nsh/appconfig
deleted file mode 100644
index d5809a939..000000000
--- a/nuttx/configs/px4io/nsh/appconfig
+++ /dev/null
@@ -1,43 +0,0 @@
-############################################################################
-# configs/stm3210e-eval/nsh/appconfig
-#
-#   Copyright (C) 2011-2012 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-
-# Path to example in apps/examples containing the user_start entry point
-
-CONFIGURED_APPS += examples/nsh
-
-CONFIGURED_APPS += system/readline
-CONFIGURED_APPS += nshlib
-CONFIGURED_APPS += reboot
-
diff --git a/nuttx/configs/px4io/nsh/defconfig b/nuttx/configs/px4io/nsh/defconfig
deleted file mode 100755
index 6f4e20869..000000000
--- a/nuttx/configs/px4io/nsh/defconfig
+++ /dev/null
@@ -1,565 +0,0 @@
-############################################################################
-# configs/px4io/nsh/defconfig
-#
-#   Copyright (C) 2009-2012 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-#
-# architecture selection
-#
-# CONFIG_ARCH - identifies the arch subdirectory and, hence, the
-#   processor architecture.
-# CONFIG_ARCH_family - for use in C code.  This identifies the
-#   particular chip family that the architecture is implemented
-#   in.
-# CONFIG_ARCH_architecture - for use in C code.  This identifies the
-#   specific architecture within the chip familyl.
-# CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
-# CONFIG_ARCH_CHIP_name - For use in C code
-# CONFIG_ARCH_BOARD - identifies the configs subdirectory and, hence,
-#   the board that supports the particular chip or SoC.
-# CONFIG_ARCH_BOARD_name - for use in C code
-# CONFIG_ENDIAN_BIG - define if big endian (default is little endian)
-# CONFIG_BOARD_LOOPSPERMSEC - for delay loops
-# CONFIG_DRAM_SIZE - Describes the installed DRAM.
-# CONFIG_DRAM_START - The start address of DRAM (physical)
-# CONFIG_DRAM_END - Last address+1 of installed RAM
-# CONFIG_ARCH_IRQPRIO - The ST32F100CB supports interrupt prioritization
-# CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt
-#   stack. If defined, this symbol is the size of the interrupt
-#   stack in bytes.  If not defined, the user task stacks will be
-#   used during interrupt handling.
-# CONFIG_ARCH_STACKDUMP - Do stack dumps after assertions
-# CONFIG_ARCH_BOOTLOADER - Set if you are using a bootloader.
-# CONFIG_ARCH_LEDS -  Use LEDs to show state. Unique to board architecture.
-# CONFIG_ARCH_BUTTONS -  Enable support for buttons. Unique to board architecture.
-# CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that
-#   cause a 100 second delay during boot-up.  This 100 second delay
-#   serves no purpose other than it allows you to calibrate
-#   CONFIG_BOARD_LOOPSPERMSEC.  You simply use a stop watch to measure
-#   the 100 second delay then adjust CONFIG_BOARD_LOOPSPERMSEC until
-#   the delay actually is 100 seconds.
-# CONFIG_ARCH_DMA - Support DMA initialization
-#
-CONFIG_ARCH=arm
-CONFIG_ARCH_ARM=y
-CONFIG_ARCH_CORTEXM3=y
-CONFIG_ARCH_CHIP=stm32
-CONFIG_ARCH_CHIP_STM32F100C8=y
-CONFIG_ARCH_BOARD=px4io
-CONFIG_ARCH_BOARD_PX4IO=y
-CONFIG_BOARD_LOOPSPERMSEC=24000
-CONFIG_DRAM_SIZE=0x00002000
-CONFIG_DRAM_START=0x20000000
-CONFIG_DRAM_END=(CONFIG_DRAM_START+CONFIG_DRAM_SIZE)
-CONFIG_ARCH_IRQPRIO=y
-CONFIG_ARCH_INTERRUPTSTACK=n
-CONFIG_ARCH_STACKDUMP=y
-CONFIG_ARCH_BOOTLOADER=n
-CONFIG_ARCH_LEDS=y
-CONFIG_ARCH_BUTTONS=y
-CONFIG_ARCH_CALIBRATION=n
-CONFIG_ARCH_DMA=n
-CONFIG_ARMV7M_CMNVECTOR=y
-
-#
-# JTAG Enable settings (by default JTAG-DP and SW-DP are disabled):
-#
-#   CONFIG_STM32_DFU - Use the DFU bootloader, not JTAG
-#
-# JTAG Enable options:
-#
-#   CONFIG_STM32_JTAG_FULL_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-#   CONFIG_STM32_JTAG_NOJNTRST_ENABLE - Enables full SWJ (JTAG-DP + SW-DP)
-#     but without JNTRST.
-#   CONFIG_STM32_JTAG_SW_ENABLE - Set JTAG-DP disabled and SW-DP enabled
-#
-CONFIG_STM32_DFU=n
-CONFIG_STM32_JTAG_FULL_ENABLE=y
-CONFIG_STM32_JTAG_NOJNTRST_ENABLE=n
-CONFIG_STM32_JTAG_SW_ENABLE=n
-
-#
-# Individual subsystems can be enabled:
-# AHB: 
-CONFIG_STM32_DMA1=n
-CONFIG_STM32_DMA2=n
-CONFIG_STM32_CRC=n
-# APB1:
-# Timers 2,3 and 4 are owned by the PWM driver
-CONFIG_STM32_TIM2=n
-CONFIG_STM32_TIM3=n
-CONFIG_STM32_TIM4=n
-CONFIG_STM32_TIM5=n
-CONFIG_STM32_TIM6=n
-CONFIG_STM32_TIM7=n
-CONFIG_STM32_WWDG=n
-CONFIG_STM32_SPI2=n
-CONFIG_STM32_USART2=y
-CONFIG_STM32_USART3=y
-CONFIG_STM32_I2C1=y
-CONFIG_STM32_I2C2=n
-CONFIG_STM32_BKP=n
-CONFIG_STM32_PWR=n
-CONFIG_STM32_DAC=n
-# APB2:
-CONFIG_STM32_ADC1=y
-CONFIG_STM32_ADC2=n
-# TIM1 is owned by the HRT
-CONFIG_STM32_TIM1=n
-CONFIG_STM32_SPI1=n
-CONFIG_STM32_TIM8=n
-CONFIG_STM32_USART1=y
-CONFIG_STM32_ADC3=n
-
-#
-# Timer and I2C devices may need to the following to force power to be applied:
-#
-#CONFIG_STM32_FORCEPOWER=y
-
-#
-# STM32F100 specific serial device driver settings
-#
-# CONFIG_USARTn_SERIAL_CONSOLE - selects the USARTn for the
-#   console and ttys0 (default is the USART1).
-# CONFIG_USARTn_RXBUFSIZE - Characters are buffered as received.
-#   This specific the size of the receive buffer
-# CONFIG_USARTn_TXBUFSIZE - Characters are buffered before
-#   being sent.  This specific the size of the transmit buffer
-# CONFIG_USARTn_BAUD - The configure BAUD of the UART.  Must be
-# CONFIG_USARTn_BITS - The number of bits.  Must be either 7 or 8.
-# CONFIG_USARTn_PARTIY - 0=no parity, 1=odd parity, 2=even parity
-# CONFIG_USARTn_2STOP - Two stop bits
-#
-CONFIG_USART1_SERIAL_CONSOLE=y
-CONFIG_USART2_SERIAL_CONSOLE=n
-CONFIG_USART3_SERIAL_CONSOLE=n
-
-CONFIG_USART1_TXBUFSIZE=64
-CONFIG_USART2_TXBUFSIZE=64
-CONFIG_USART3_TXBUFSIZE=64
-
-CONFIG_USART1_RXBUFSIZE=64
-CONFIG_USART2_RXBUFSIZE=64
-CONFIG_USART3_RXBUFSIZE=64
-
-CONFIG_USART1_BAUD=57600
-CONFIG_USART2_BAUD=115200
-CONFIG_USART3_BAUD=115200
-
-CONFIG_USART1_BITS=8
-CONFIG_USART2_BITS=8
-CONFIG_USART3_BITS=8
-
-CONFIG_USART1_PARITY=0
-CONFIG_USART2_PARITY=0
-CONFIG_USART3_PARITY=0
-
-CONFIG_USART1_2STOP=0
-CONFIG_USART2_2STOP=0
-CONFIG_USART3_2STOP=0
-
-#
-# PX4IO specific driver settings
-#
-# CONFIG_HRT_TIMER
-#   Enables the high-resolution timer.  The board definition must
-#   set HRT_TIMER and HRT_TIMER_CHANNEL to the timer and capture/
-#   compare channels to be used.
-# CONFIG_HRT_PPM
-#   Enables R/C PPM input using the HRT.  The board definition must
-#   set HRT_PPM_CHANNEL to the timer capture/compare channel to be
-#   used, and define GPIO_PPM_IN to configure the appropriate timer
-#   GPIO.
-# CONFIG_PWM_SERVO
-#   Enables the PWM servo driver.  The driver configuration must be
-#   supplied by the board support at initialisation time.
-#   Note that USART2 must be disabled on the PX4 board for this to
-#   be available.
-#
-#
-CONFIG_HRT_TIMER=y
-CONFIG_HRT_PPM=y
-CONFIG_PWM_SERVO=y
-
-#
-# General build options
-#
-# CONFIG_RRLOAD_BINARY - make the rrload binary format used with
-#   BSPs from www.ridgerun.com using the tools/mkimage.sh script
-# CONFIG_INTELHEX_BINARY - make the Intel HEX binary format
-#   used with many different loaders using the GNU objcopy program
-#   Should not be selected if you are not using the GNU toolchain.
-# CONFIG_MOTOROLA_SREC - make the Motorola S-Record binary format
-#   used with many different loaders using the GNU objcopy program
-#   Should not be selected if you are not using the GNU toolchain.
-# CONFIG_RAW_BINARY - make a raw binary format file used with many
-#   different loaders using the GNU objcopy program.  This option
-#   should not be selected if you are not using the GNU toolchain.
-# CONFIG_HAVE_LIBM - toolchain supports libm.a
-#
-CONFIG_RRLOAD_BINARY=n
-CONFIG_INTELHEX_BINARY=n
-CONFIG_MOTOROLA_SREC=n
-CONFIG_RAW_BINARY=y
-CONFIG_HAVE_LIBM=n
-
-#
-# General OS setup
-#
-# CONFIG_APPS_DIR - Identifies the relative path to the directory
-#   that builds the application to link with NuttX.  Default: ../apps
-# CONFIG_DEBUG - enables built-in debug options
-# CONFIG_DEBUG_VERBOSE - enables verbose debug output
-# CONFIG_DEBUG_SYMBOLS - build without optimization and with
-#   debug symbols (needed for use with a debugger).
-# CONFIG_HAVE_CXX - Enable support for C++
-# CONFIG_HAVE_CXXINITIALIZE - The platform-specific logic includes support
-#   for initialization of static C++ instances for this architecture
-#   and for the selected toolchain (via up_cxxinitialize()).
-# CONFIG_MM_REGIONS - If the architecture includes multiple
-#   regions of memory to allocate from, this specifies the
-#   number of memory regions that the memory manager must
-#   handle and enables the API mm_addregion(start, end);
-# CONFIG_ARCH_LOWPUTC - architecture supports low-level, boot
-#   time console output
-# CONFIG_MSEC_PER_TICK - The default system timer is 100Hz
-#   or MSEC_PER_TICK=10.  This setting may be defined to
-#   inform NuttX that the processor hardware is providing
-#   system timer interrupts at some interrupt interval other
-#   than 10 msec.
-# CONFIG_RR_INTERVAL - The round robin timeslice will be set
-#   this number of milliseconds;  Round robin scheduling can
-#   be disabled by setting this value to zero.
-# CONFIG_SCHED_INSTRUMENTATION - enables instrumentation in 
-#   scheduler to monitor system performance
-# CONFIG_TASK_NAME_SIZE - Spcifies that maximum size of a
-#   task name to save in the TCB.  Useful if scheduler
-#   instrumentation is selected.  Set to zero to disable.
-# CONFIG_START_YEAR, CONFIG_START_MONTH, CONFIG_START_DAY -
-#   Used to initialize the internal time logic.
-# CONFIG_GREGORIAN_TIME - Enables Gregorian time conversions.
-#   You would only need this if you are concerned about accurate
-#   time conversions in the past or in the distant future.
-# CONFIG_JULIAN_TIME - Enables Julian time conversions. You
-#   would only need this if you are concerned about accurate
-#   time conversion in the distand past.  You must also define
-#   CONFIG_GREGORIAN_TIME in order to use Julian time.
-# CONFIG_DEV_CONSOLE - Set if architecture-specific logic
-#   provides /dev/console.  Enables stdout, stderr, stdin.
-# CONFIG_DEV_LOWCONSOLE - Use the simple, low-level serial console
-#   driver (minimul support)
-# CONFIG_MUTEX_TYPES: Set to enable support for recursive and
-#   errorcheck mutexes. Enables pthread_mutexattr_settype().
-# CONFIG_PRIORITY_INHERITANCE : Set to enable support for priority
-#   inheritance on mutexes and semaphores. 
-# CONFIG_SEM_PREALLOCHOLDERS: This setting is only used if priority
-#   inheritance is enabled.  It defines the maximum number of
-#   different threads (minus one) that can take counts on a
-#   semaphore with priority inheritance support.  This may be 
-#   set to zero if priority inheritance is disabled OR if you
-#   are only using semaphores as mutexes (only one holder) OR
-#   if no more than two threads participate using a counting
-#   semaphore.
-# CONFIG_SEM_NNESTPRIO.  If priority inheritance is enabled,
-#   then this setting is the maximum number of higher priority
-#   threads (minus 1) than can be waiting for another thread
-#   to release a count on a semaphore.  This value may be set
-#   to zero if no more than one thread is expected to wait for
-#   a semaphore.
-# CONFIG_FDCLONE_DISABLE. Disable cloning of all file descriptors
-#   by task_create() when a new task is started.  If set, all
-#   files/drivers will appear to be closed in the new task.
-# CONFIG_FDCLONE_STDIO. Disable cloning of all but the first
-#   three file descriptors (stdin, stdout, stderr) by task_create()
-#   when a new task is started. If set, all files/drivers will
-#   appear to be closed in the new task except for stdin, stdout,
-#   and stderr.
-# CONFIG_SDCLONE_DISABLE. Disable cloning of all socket
-#   desciptors by task_create() when a new task is started. If
-#   set, all sockets will appear to be closed in the new task.
-# CONFIG_NXFLAT. Enable support for the NXFLAT binary format.
-#  This format will support execution of NuttX binaries located
-#  in a ROMFS filesystem (see examples/nxflat).
-# CONFIG_SCHED_WORKQUEUE.  Create a dedicated "worker" thread to
-#  handle delayed processing from interrupt handlers.  This feature
-#  is required for some drivers but, if there are not complaints,
-#  can be safely disabled.  The worker thread also performs
-#  garbage collection -- completing any delayed memory deallocations
-#  from interrupt handlers.  If the worker thread is disabled,
-#  then that clean will be performed by the IDLE thread instead
-#  (which runs at the lowest of priority and may not be appropriate
-#  if memory reclamation is of high priority).  If CONFIG_SCHED_WORKQUEUE
-#  is enabled, then the following options can also be used:
-# CONFIG_SCHED_WORKPRIORITY - The execution priority of the worker
-#  thread.  Default: 50
-# CONFIG_SCHED_WORKPERIOD - How often the worker thread checks for
-#  work in units of microseconds.  Default: 50*1000 (50 MS).
-# CONFIG_SCHED_WORKSTACKSIZE - The stack size allocated for the worker
-#  thread.  Default: CONFIG_IDLETHREAD_STACKSIZE.
-# CONFIG_SIG_SIGWORK - The signal number that will be used to wake-up
-#  the worker thread.  Default: 4
-#
-#CONFIG_APPS_DIR=
-CONFIG_DEBUG=n
-CONFIG_DEBUG_VERBOSE=n
-CONFIG_DEBUG_SYMBOLS=y
-CONFIG_HAVE_CXX=n
-CONFIG_HAVE_CXXINITIALIZE=n
-CONFIG_MM_REGIONS=1
-CONFIG_MM_SMALL=y
-CONFIG_ARCH_LOWPUTC=y
-CONFIG_RR_INTERVAL=200
-CONFIG_SCHED_INSTRUMENTATION=n
-CONFIG_TASK_NAME_SIZE=0
-CONFIG_START_YEAR=2009
-CONFIG_START_MONTH=9
-CONFIG_START_DAY=21
-CONFIG_GREGORIAN_TIME=n
-CONFIG_JULIAN_TIME=n
-CONFIG_DEV_CONSOLE=y
-CONFIG_DEV_LOWCONSOLE=n
-CONFIG_MUTEX_TYPES=n
-CONFIG_PRIORITY_INHERITANCE=n
-CONFIG_SEM_PREALLOCHOLDERS=0
-CONFIG_SEM_NNESTPRIO=0
-CONFIG_FDCLONE_DISABLE=n
-CONFIG_FDCLONE_STDIO=y
-CONFIG_SDCLONE_DISABLE=y
-CONFIG_NXFLAT=n
-CONFIG_SCHED_WORKQUEUE=n
-CONFIG_SCHED_WORKPRIORITY=50
-CONFIG_SCHED_WORKPERIOD=(50*1000)
-CONFIG_SCHED_WORKSTACKSIZE=512
-CONFIG_SIG_SIGWORK=4
-
-#
-# The following can be used to disable categories of
-# APIs supported by the OS.  If the compiler supports
-# weak functions, then it should not be necessary to
-# disable functions unless you want to restrict usage
-# of those APIs.
-#
-# There are certain dependency relationships in these
-# features.
-#
-# o mq_notify logic depends on signals to awaken tasks
-#   waiting for queues to become full or empty.
-# o pthread_condtimedwait() depends on signals to wake
-#   up waiting tasks.
-#
-CONFIG_DISABLE_CLOCK=n
-CONFIG_DISABLE_POSIX_TIMERS=y
-CONFIG_DISABLE_PTHREAD=n
-CONFIG_DISABLE_SIGNALS=n
-CONFIG_DISABLE_MQUEUE=y
-CONFIG_DISABLE_MOUNTPOINT=y
-CONFIG_DISABLE_ENVIRON=y
-CONFIG_DISABLE_POLL=y
-
-#
-# Misc libc settings
-#
-# CONFIG_NOPRINTF_FIELDWIDTH - sprintf-related logic is a
-#   little smaller if we do not support fieldwidthes
-#
-CONFIG_NOPRINTF_FIELDWIDTH=n
-
-#
-# Allow for architecture optimized implementations
-#
-# The architecture can provide optimized versions of the
-# following to improve system performance
-#
-CONFIG_ARCH_MEMCPY=n
-CONFIG_ARCH_MEMCMP=n
-CONFIG_ARCH_MEMMOVE=n
-CONFIG_ARCH_MEMSET=n
-CONFIG_ARCH_STRCMP=n
-CONFIG_ARCH_STRCPY=n
-CONFIG_ARCH_STRNCPY=n
-CONFIG_ARCH_STRLEN=n
-CONFIG_ARCH_STRNLEN=n
-CONFIG_ARCH_BZERO=n
-
-#
-# Sizes of configurable things (0 disables)
-#
-# CONFIG_MAX_TASKS - The maximum number of simultaneously
-#   active tasks.  This value must be a power of two.
-# CONFIG_MAX_TASK_ARGS - This controls the maximum number of
-#   of parameters that a task may receive (i.e., maxmum value
-#   of 'argc')
-# CONFIG_NPTHREAD_KEYS - The number of items of thread-
-#   specific data that can be retained
-# CONFIG_NFILE_DESCRIPTORS - The maximum number of file
-#   descriptors (one for each open)
-# CONFIG_NFILE_STREAMS - The maximum number of streams that
-#   can be fopen'ed
-# CONFIG_NAME_MAX - The maximum size of a file name.
-# CONFIG_STDIO_BUFFER_SIZE - Size of the buffer to allocate
-#   on fopen. (Only if CONFIG_NFILE_STREAMS > 0)
-# CONFIG_NUNGET_CHARS - Number of characters that can be
-#   buffered by ungetc() (Only if CONFIG_NFILE_STREAMS > 0)
-# CONFIG_PREALLOC_MQ_MSGS - The number of pre-allocated message
-#   structures.  The system manages a pool of preallocated
-#   message structures to minimize dynamic allocations
-# CONFIG_MQ_MAXMSGSIZE - Message structures are allocated with
-#   a fixed payload size given by this settin (does not include
-#   other message structure overhead.
-# CONFIG_MAX_WDOGPARMS - Maximum number of parameters that
-#   can be passed to a watchdog handler
-# CONFIG_PREALLOC_WDOGS - The number of pre-allocated watchdog
-#   structures.  The system manages a pool of preallocated
-#   watchdog structures to minimize dynamic allocations
-# CONFIG_PREALLOC_TIMERS - The number of pre-allocated POSIX
-#   timer structures.  The system manages a pool of preallocated
-#   timer structures to minimize dynamic allocations.  Set to
-#   zero for all dynamic allocations.
-#
-CONFIG_MAX_TASKS=4
-CONFIG_MAX_TASK_ARGS=4
-CONFIG_NPTHREAD_KEYS=2
-CONFIG_NFILE_DESCRIPTORS=6
-CONFIG_NFILE_STREAMS=4
-CONFIG_NAME_MAX=32
-CONFIG_STDIO_BUFFER_SIZE=64
-CONFIG_NUNGET_CHARS=2
-CONFIG_PREALLOC_MQ_MSGS=1
-CONFIG_MQ_MAXMSGSIZE=32
-CONFIG_MAX_WDOGPARMS=2
-CONFIG_PREALLOC_WDOGS=3
-CONFIG_PREALLOC_TIMERS=1
-
-
-#
-# Settings for apps/nshlib
-#
-# CONFIG_NSH_BUILTIN_APPS - Support external registered,
-#   "named" applications that can be executed from the NSH
-#   command line (see apps/README.txt for more information).
-# CONFIG_NSH_FILEIOSIZE - Size of a static I/O buffer
-# CONFIG_NSH_STRERROR - Use strerror(errno)
-# CONFIG_NSH_LINELEN - Maximum length of one command line
-# CONFIG_NSH_NESTDEPTH - Max number of nested if-then[-else]-fi
-# CONFIG_NSH_DISABLESCRIPT - Disable scripting support
-# CONFIG_NSH_DISABLEBG - Disable background commands
-# CONFIG_NSH_ROMFSETC - Use startup script in /etc
-# CONFIG_NSH_CONSOLE - Use serial console front end
-# CONFIG_NSH_TELNET - Use telnetd console front end
-# CONFIG_NSH_ARCHINIT - Platform provides architecture
-#   specific initialization (nsh_archinitialize()).
-#
-# If CONFIG_NSH_TELNET is selected:
-# CONFIG_NSH_IOBUFFER_SIZE -- Telnetd I/O buffer size
-# CONFIG_NSH_DHCPC - Obtain address using DHCP
-# CONFIG_NSH_IPADDR - Provides static IP address
-# CONFIG_NSH_DRIPADDR - Provides static router IP address
-# CONFIG_NSH_NETMASK - Provides static network mask
-# CONFIG_NSH_NOMAC - Use a bogus MAC address
-#
-# If CONFIG_NSH_ROMFSETC is selected:
-# CONFIG_NSH_ROMFSMOUNTPT - ROMFS mountpoint
-# CONFIG_NSH_INITSCRIPT - Relative path to init script
-# CONFIG_NSH_ROMFSDEVNO - ROMFS RAM device minor
-# CONFIG_NSH_ROMFSSECTSIZE - ROMF sector size
-# CONFIG_NSH_FATDEVNO - FAT FS RAM device minor
-# CONFIG_NSH_FATSECTSIZE - FAT FS sector size
-# CONFIG_NSH_FATNSECTORS - FAT FS number of sectors
-# CONFIG_NSH_FATMOUNTPT - FAT FS mountpoint
-#
-CONFIG_NSH_BUILTIN_APPS=y
-CONFIG_NSH_FILEIOSIZE=64
-CONFIG_NSH_STRERROR=n
-CONFIG_NSH_LINELEN=64
-CONFIG_NSH_NESTDEPTH=1
-CONFIG_NSH_DISABLESCRIPT=y
-CONFIG_NSH_DISABLEBG=n
-CONFIG_NSH_ROMFSETC=n
-CONFIG_NSH_CONSOLE=y
-CONFIG_NSH_TELNET=n
-CONFIG_NSH_ARCHINIT=y
-CONFIG_NSH_IOBUFFER_SIZE=256
-#CONFIG_NSH_STACKSIZE=1024
-CONFIG_NSH_DHCPC=n
-CONFIG_NSH_NOMAC=n
-CONFIG_NSH_IPADDR=(10<<24|0<<16|0<<8|2)
-CONFIG_NSH_DRIPADDR=(10<<24|0<<16|0<<8|1)
-CONFIG_NSH_NETMASK=(255<<24|255<<16|255<<8|0)
-CONFIG_NSH_ROMFSMOUNTPT="/etc"
-CONFIG_NSH_INITSCRIPT="init.d/rcS"
-CONFIG_NSH_ROMFSDEVNO=0
-CONFIG_NSH_ROMFSSECTSIZE=64
-CONFIG_NSH_FATDEVNO=1
-CONFIG_NSH_FATSECTSIZE=512
-CONFIG_NSH_FATNSECTORS=1024
-CONFIG_NSH_FATMOUNTPT=/tmp
-
-#
-# Architecture-specific NSH options
-#
-CONFIG_NSH_MMCSDSPIPORTNO=0
-CONFIG_NSH_MMCSDSLOTNO=0
-CONFIG_NSH_MMCSDMINOR=0
-
-#
-# Stack and heap information
-#
-# CONFIG_BOOT_RUNFROMFLASH - Some configurations support XIP
-#   operation from FLASH but must copy initialized .data sections to RAM.
-#   (should also be =n for the STM3210E-EVAL which always runs from flash)
-# CONFIG_BOOT_COPYTORAM -  Some configurations boot in FLASH
-#   but copy themselves entirely into RAM for better performance.
-# CONFIG_CUSTOM_STACK - The up_ implementation will handle
-#   all stack operations outside of the nuttx model.
-# CONFIG_STACK_POINTER - The initial stack pointer (arm7tdmi only)
-# CONFIG_IDLETHREAD_STACKSIZE - The size of the initial stack.
-#  This is the thread that (1) performs the inital boot of the system up
-#  to the point where user_start() is spawned, and (2) there after is the
-#  IDLE thread that executes only when there is no other thread ready to
-#  run.
-# CONFIG_USERMAIN_STACKSIZE - The size of the stack to allocate
-#  for the main user thread that begins at the user_start() entry point.
-# CONFIG_PTHREAD_STACK_MIN - Minimum pthread stack size
-# CONFIG_PTHREAD_STACK_DEFAULT - Default pthread stack size
-# CONFIG_HEAP_BASE - The beginning of the heap
-# CONFIG_HEAP_SIZE - The size of the heap
-#
-CONFIG_BOOT_RUNFROMFLASH=n
-CONFIG_BOOT_COPYTORAM=n
-CONFIG_CUSTOM_STACK=n
-CONFIG_STACK_POINTER=
-CONFIG_IDLETHREAD_STACKSIZE=800
-CONFIG_USERMAIN_STACKSIZE=1024
-CONFIG_PTHREAD_STACK_MIN=256
-CONFIG_PTHREAD_STACK_DEFAULT=512
-CONFIG_HEAP_BASE=
-CONFIG_HEAP_SIZE=
diff --git a/nuttx/configs/px4io/nsh/setenv.sh b/nuttx/configs/px4io/nsh/setenv.sh
deleted file mode 100755
index d83685192..000000000
--- a/nuttx/configs/px4io/nsh/setenv.sh
+++ /dev/null
@@ -1,47 +0,0 @@
-#!/bin/bash
-# configs/stm3210e-eval/dfu/setenv.sh
-#
-#   Copyright (C) 2009 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <spudmonkey@racsa.co.cr>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-
-if [ "$(basename $0)" = "setenv.sh" ] ; then
-  echo "You must source this script, not run it!" 1>&2
-  exit 1
-fi
-
-if [ -z "${PATH_ORIG}" ]; then export PATH_ORIG="${PATH}"; fi
-
-WD=`pwd`
-export RIDE_BIN="/cygdrive/c/Program Files/Raisonance/Ride/arm-gcc/bin"
-export BUILDROOT_BIN="${WD}/../buildroot/build_arm_nofpu/staging_dir/bin"
-export PATH="${BUILDROOT_BIN}:${RIDE_BIN}:/sbin:/usr/sbin:${PATH_ORIG}"
-
-echo "PATH : ${PATH}"
diff --git a/nuttx/configs/px4io/src/Makefile b/nuttx/configs/px4io/src/Makefile
deleted file mode 100644
index bb9539d16..000000000
--- a/nuttx/configs/px4io/src/Makefile
+++ /dev/null
@@ -1,84 +0,0 @@
-############################################################################
-# configs/stm3210e-eval/src/Makefile
-#
-#   Copyright (C) 2009-2010 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <spudmonkey@racsa.co.cr>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-
--include $(TOPDIR)/Make.defs
-
-CFLAGS		+= -I$(TOPDIR)/sched
-
-ASRCS		= 
-AOBJS		= $(ASRCS:.S=$(OBJEXT))
-
-CSRCS		= empty.c
-
-COBJS		= $(CSRCS:.c=$(OBJEXT))
-
-SRCS		= $(ASRCS) $(CSRCS)
-OBJS		= $(AOBJS) $(COBJS)
-
-ARCH_SRCDIR	= $(TOPDIR)/arch/$(CONFIG_ARCH)/src
-ifeq ($(WINTOOL),y)
-  CFLAGS	+= -I "${shell cygpath -w $(ARCH_SRCDIR)/chip}" \
-  		   -I "${shell cygpath -w $(ARCH_SRCDIR)/common}" \
-  		   -I "${shell cygpath -w $(ARCH_SRCDIR)/armv7-m}"
-else
-  CFLAGS	+= -I$(ARCH_SRCDIR)/chip -I$(ARCH_SRCDIR)/common -I$(ARCH_SRCDIR)/armv7-m
-endif
-
-all: libboard$(LIBEXT)
-
-$(AOBJS): %$(OBJEXT): %.S
-	$(call ASSEMBLE, $<, $@)
-
-$(COBJS) $(LINKOBJS): %$(OBJEXT): %.c
-	$(call COMPILE, $<, $@)
-
-libboard$(LIBEXT): $(OBJS)
-	$(call ARCHIVE, $@, $(OBJS))
-
-.depend: Makefile $(SRCS)
-	@$(MKDEP) $(CC) -- $(CFLAGS) -- $(SRCS) >Make.dep
-	@touch $@
-
-depend: .depend
-
-clean:
-	$(call DELFILE, libboard$(LIBEXT))
-	$(call CLEAN)
-
-distclean: clean
-	$(call DELFILE, Make.dep)
-	$(call DELFILE, .depend)
-
--include Make.dep
diff --git a/nuttx/configs/px4io/src/README.txt b/nuttx/configs/px4io/src/README.txt
deleted file mode 100644
index d4eda82fd..000000000
--- a/nuttx/configs/px4io/src/README.txt
+++ /dev/null
@@ -1 +0,0 @@
-This directory contains drivers unique to the STMicro STM3210E-EVAL development board.
diff --git a/nuttx/configs/px4io/src/drv_i2c_device.c b/nuttx/configs/px4io/src/drv_i2c_device.c
deleted file mode 100644
index 1f5931ae5..000000000
--- a/nuttx/configs/px4io/src/drv_i2c_device.c
+++ /dev/null
@@ -1,618 +0,0 @@
-/****************************************************************************
- *
- *   Copyright (C) 2012 PX4 Development Team. All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * 1. Redistributions of source code must retain the above copyright
- *    notice, this list of conditions and the following disclaimer.
- * 2. Redistributions in binary form must reproduce the above copyright
- *    notice, this list of conditions and the following disclaimer in
- *    the documentation and/or other materials provided with the
- *    distribution.
- * 3. Neither the name PX4 nor the names of its contributors may be
- *    used to endorse or promote products derived from this software
- *    without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
- * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
- * POSSIBILITY OF SUCH DAMAGE.
- *
- ****************************************************************************/
-
- /**
-  * @file A simple, polled I2C slave-mode driver.
-  *
-  * The master writes to and reads from a byte buffer, which the caller 
-  * can update inbetween calls to the FSM.
-  */
-
-#include <stdbool.h>
-
-#include "stm32_i2c.h"
-
-#include <string.h>
-
-/*
- * I2C register definitions.
- */
-#define I2C_BASE	STM32_I2C1_BASE
-
-#define REG(_reg)	(*(volatile uint32_t *)(I2C_BASE + _reg))
-
-#define rCR1		REG(STM32_I2C_CR1_OFFSET)
-#define rCR2		REG(STM32_I2C_CR2_OFFSET)
-#define rOAR1		REG(STM32_I2C_OAR1_OFFSET)
-#define rOAR2		REG(STM32_I2C_OAR2_OFFSET)
-#define rDR		REG(STM32_I2C_DR_OFFSET)
-#define rSR1		REG(STM32_I2C_SR1_OFFSET)
-#define rSR2		REG(STM32_I2C_SR2_OFFSET)
-#define rCCR		REG(STM32_I2C_CCR_OFFSET)
-#define rTRISE		REG(STM32_I2C_TRISE_OFFSET)
-
-/*
- * "event" values (cr2 << 16 | cr1) as described in the ST DriverLib
- */
-#define  I2C_EVENT_SLAVE_RECEIVER_ADDRESS_MATCHED          ((uint32_t)0x00020002) /* BUSY and ADDR flags */
-#define  I2C_EVENT_SLAVE_TRANSMITTER_ADDRESS_MATCHED       ((uint32_t)0x00060082) /* TRA, BUSY, TXE and ADDR flags */
-#define  I2C_EVENT_SLAVE_BYTE_RECEIVED                     ((uint32_t)0x00020040) /* BUSY and RXNE flags */
-#define  I2C_EVENT_SLAVE_STOP_DETECTED                     ((uint32_t)0x00000010) /* STOPF flag */
-#define  I2C_EVENT_SLAVE_BYTE_TRANSMITTED                  ((uint32_t)0x00060084) /* TRA, BUSY, TXE and BTF flags */
-#define  I2C_EVENT_SLAVE_BYTE_TRANSMITTING                 ((uint32_t)0x00060080) /* TRA, BUSY and TXE flags */
-#define  I2C_EVENT_SLAVE_ACK_FAILURE                       ((uint32_t)0x00000400) /* AF flag */
-
-/**
- * States implemented by the I2C FSM.
- */
-enum fsm_state {
-	BAD_PHASE,	 // must be zero, default exit on a bad state transition
-
-	WAIT_FOR_MASTER,
-
-	/* write from master */
-	WAIT_FOR_COMMAND,
-	RECEIVE_COMMAND,
-	RECEIVE_DATA,
-	HANDLE_COMMAND,
-
-	/* read from master */
-	WAIT_TO_SEND,
-	SEND_STATUS,
-	SEND_DATA,
-
-	NUM_STATES
-};
-
-/**
- * Events recognised by the I2C FSM.
- */
-enum fsm_event {
-	/* automatic transition */
-	AUTO,
-
-	/* write from master */
-	ADDRESSED_WRITE,
-	BYTE_RECEIVED,
-	STOP_RECEIVED,
-
-	/* read from master */
-	ADDRESSED_READ,
-	BYTE_SENDABLE,
-	ACK_FAILED,
-
-	NUM_EVENTS
-};
-
-/**
- * Context for the I2C FSM
- */
-static struct fsm_context {
-	enum fsm_state		state;
-
-	/* XXX want to eliminate these */
-	uint8_t			command;
-	uint8_t			status;
-
-	uint8_t			*data_ptr;
-	uint32_t		data_count;
-
-	size_t			buffer_size;
-	uint8_t			*buffer;
-} context;
-
-/**
- * Structure defining one FSM state and its outgoing transitions.
- */
-struct fsm_transition {
-		void (*handler)(void);
-		enum fsm_state next_state[NUM_EVENTS];
-};
-
-static bool	i2c_command_received;
-
-static void	fsm_event(enum fsm_event event);
-
-static void	go_bad(void);
-static void	go_wait_master(void);
-
-static void	go_wait_command(void);
-static void	go_receive_command(void);
-static void	go_receive_data(void);
-static void	go_handle_command(void);
-
-static void	go_wait_send(void);
-static void	go_send_status(void);
-static void	go_send_buffer(void);
-
-/**
- * The FSM state graph.
- */
-static const struct fsm_transition fsm[NUM_STATES] = {
-		[BAD_PHASE] = {
-				.handler = go_bad,
-				.next_state = {
-						[AUTO] = WAIT_FOR_MASTER,
-				},
-		},
-
-		[WAIT_FOR_MASTER] = {
-				.handler = go_wait_master,
-				.next_state = {
-						[ADDRESSED_WRITE] = WAIT_FOR_COMMAND,
-						[ADDRESSED_READ] = WAIT_TO_SEND,
-				},
-		},
-
-		/* write from master*/
-		[WAIT_FOR_COMMAND] = {
-				.handler = go_wait_command,
-				.next_state = {
-						[BYTE_RECEIVED] = RECEIVE_COMMAND,
-						[STOP_RECEIVED] = WAIT_FOR_MASTER,
-				},
-		},
-		[RECEIVE_COMMAND] = {
-				.handler = go_receive_command,
-				.next_state = {
-						[BYTE_RECEIVED] = RECEIVE_DATA,
-						[STOP_RECEIVED] = HANDLE_COMMAND,
-				},
-		},
-		[RECEIVE_DATA] = {
-				.handler = go_receive_data,
-				.next_state = {
-						[BYTE_RECEIVED] = RECEIVE_DATA,
-						[STOP_RECEIVED] = HANDLE_COMMAND,
-				},
-		},
-		[HANDLE_COMMAND] = {
-				.handler = go_handle_command,
-				.next_state = {
-						[AUTO] = WAIT_FOR_MASTER,
-				},
-		},
-
-		/* buffer send */
-		[WAIT_TO_SEND] = {
-			.handler = go_wait_send,
-			.next_state = {
-					[BYTE_SENDABLE] = SEND_STATUS,
-			},
-		},
-		[SEND_STATUS] = {
-				.handler = go_send_status,
-				.next_state = {
-						[BYTE_SENDABLE] = SEND_DATA,
-						[ACK_FAILED] = WAIT_FOR_MASTER,
-				},
-		},
-		[SEND_DATA] = {
-				.handler = go_send_buffer,
-				.next_state = {
-						[BYTE_SENDABLE] = SEND_DATA,
-						[ACK_FAILED] = WAIT_FOR_MASTER,
-				},
-		},
-};
-
-
-/* debug support */
-#if 1
-struct fsm_logentry {
-	char		kind;
-	uint32_t	code;
-};
-
-#define LOG_ENTRIES	32
-static struct fsm_logentry fsm_log[LOG_ENTRIES];
-int	fsm_logptr;
-#define LOG_NEXT(_x)	(((_x) + 1) % LOG_ENTRIES)
-#define LOGx(_kind, _code)		\
-		do {					\
-			fsm_log[fsm_logptr].kind = _kind; \
-			fsm_log[fsm_logptr].code = _code; \
-			fsm_logptr = LOG_NEXT(fsm_logptr); \
-			fsm_log[fsm_logptr].kind = 0; \
-		} while(0)
-
-#define LOG(_kind, _code) \
-		do {\
-			if (fsm_logptr < LOG_ENTRIES) { \
-				fsm_log[fsm_logptr].kind = _kind; \
-				fsm_log[fsm_logptr].code = _code; \
-				fsm_logptr++;\
-			}\
-		}while(0)
-
-#else
-#define LOG(_kind, _code)
-#endif
-
-
-static void i2c_setclock(uint32_t frequency);
-
-/**
- * Initialise I2C
- *
- */
-void
-i2c_fsm_init(uint8_t *buffer, size_t buffer_size)
-{
-	/* save the buffer */
-	context.buffer = buffer;
-	context.buffer_size = buffer_size;
-
-	// initialise the FSM
-	context.status = 0;
-	context.command = 0;
-	context.state = BAD_PHASE;
-	fsm_event(AUTO);
-
-#if 0
-	// enable the i2c block clock and reset it
-	modifyreg32(STM32_RCC_APB1ENR, 0, RCC_APB1ENR_I2C1EN);
-	modifyreg32(STM32_RCC_APB1RSTR, 0, RCC_APB1RSTR_I2C1RST);
-	modifyreg32(STM32_RCC_APB1RSTR, RCC_APB1RSTR_I2C1RST, 0);
-
-	// configure the i2c GPIOs
-	stm32_configgpio(GPIO_I2C1_SCL);
-	stm32_configgpio(GPIO_I2C1_SDA);
-
-	// set the peripheral clock to match the APB clock
-	rCR2 = STM32_PCLK1_FREQUENCY / 1000000;
-
-	// configure for 100kHz operation
-	i2c_setclock(100000);
-
-	// enable i2c
-	rCR1 = I2C_CR1_PE;
-#endif
-}
-
-/**
- * Run the I2C FSM for some period.
- *
- * @return True if the buffer has been updated by a command.
- */
-bool
-i2c_fsm(void)
-{
-	uint32_t	event;
-	int		idle_iterations = 0;
-
-	for (;;) {
-		// handle bus error states by discarding the current operation
-		if (rSR1 & I2C_SR1_BERR) {
-			context.state = WAIT_FOR_MASTER;
-			rSR1 = ~I2C_SR1_BERR;
-		}
-
-		// we do not anticipate over/underrun errors as clock-stretching is enabled
-
-		// fetch the most recent event
-		event = ((rSR2 << 16) | rSR1) & 0x00ffffff;
-
-		// generate FSM events based on I2C events
-		switch (event) {
-		case I2C_EVENT_SLAVE_RECEIVER_ADDRESS_MATCHED:
-			LOG('w', 0);
-			fsm_event(ADDRESSED_WRITE);
-			break;
-
-		case I2C_EVENT_SLAVE_TRANSMITTER_ADDRESS_MATCHED:
-			LOG('r', 0);
-			fsm_event(ADDRESSED_READ);
-			break;
-
-		case I2C_EVENT_SLAVE_BYTE_RECEIVED:
-			LOG('R', 0);
-			fsm_event(BYTE_RECEIVED);
-			break;
-
-		case I2C_EVENT_SLAVE_STOP_DETECTED:
-			LOG('s', 0);
-			fsm_event(STOP_RECEIVED);
-			break;
-
-		case I2C_EVENT_SLAVE_BYTE_TRANSMITTING:
-		//case I2C_EVENT_SLAVE_BYTE_TRANSMITTED:
-			LOG('T', 0);
-			fsm_event(BYTE_SENDABLE);
-			break;
-
-		case I2C_EVENT_SLAVE_ACK_FAILURE:
-			LOG('a', 0);
-			fsm_event(ACK_FAILED);
-			break;
-
-		default:
-			idle_iterations++;
-//			if ((event) && (event != 0x00020000))
-//				LOG('e', event);
-			break;
-		}
-
-		/* if we have just received something, drop out and let the caller handle it */
-		if (i2c_command_received) {
-			i2c_command_received = false;
-			return true;
-		}
-
-		/* if we have done nothing recently, drop out and let the caller have a slice */
-		if (idle_iterations > 1000)
-			return false;
-	}
-}
-
-/**
- * Update the FSM with an event
- *
- * @param event	New event.
- */
-static void
-fsm_event(enum fsm_event event)
-{
-	// move to the next state
-	context.state = fsm[context.state].next_state[event];
-
-	LOG('f', context.state);
-
-	// call the state entry handler
-	if (fsm[context.state].handler) {
-		fsm[context.state].handler();
-	}
-}
-
-static void
-go_bad()
-{
-	LOG('B', 0);
-	fsm_event(AUTO);
-}
-
-/**
- * Wait for the master to address us.
- *
- */
-static void
-go_wait_master()
-{
-	// We currently don't have a command byte.
-	//
-	context.command = '\0';
-
-	// The data pointer starts pointing to the start of the data buffer.
-	//
-	context.data_ptr = context.buffer;
-
-	// The data count is either:
-	// - the size of the data buffer
-	// - some value less than or equal the size of the data buffer during a write or a read
-	//
-	context.data_count = context.buffer_size;
-
-	// (re)enable the peripheral, clear the stop event flag in
-	// case we just finished receiving data
-	rCR1 |= I2C_CR1_PE;
-
-	// clear the ACK failed flag in case we just finished sending data
-	rSR1 = ~I2C_SR1_AF;
-}
-
-/**
- * Prepare to receive a command byte.
- *
- */
-static void
-go_wait_command()
-{
-	// NOP
-}
-
-/**
- * Command byte has been received, save it and prepare to handle the data.
- *
- */
-static void
-go_receive_command()
-{
-
-	// fetch the command byte
-	context.command = (uint8_t)rDR;
-	LOG('c', context.command);
-
-}
-
-/**
- * Receive a data byte.
- *
- */
-static void
-go_receive_data()
-{
-	uint8_t	d;
-
-	// fetch the byte
-	d = (uint8_t)rDR;
-	LOG('d', d);
-
-	// if we have somewhere to put it, do so
-	if (context.data_count) {
-		*context.data_ptr++ = d;
-		context.data_count--;
-	}
-}
-
-/**
- * Handle a command once the host is done sending it to us.
- *
- */
-static void
-go_handle_command()
-{
-	// presume we are happy with the command
-	context.status = 0;
-
-	// make a note that the buffer contains a fresh command
-	i2c_command_received = true;
-
-	// kick along to the next state
-	fsm_event(AUTO);
-}
-
-/**
- * Wait to be able to send the status byte.
- *
- */
-static void
-go_wait_send()
-{
-	// NOP
-}
-
-/**
- * Send the status byte.
- *
- */
-static void
-go_send_status()
-{
-	rDR = context.status;
-	LOG('?', context.status);
-}
-
-/**
- * Send a data or pad byte.
- *
- */
-static void
-go_send_buffer()
-{
-	if (context.data_count) {
-		LOG('D', *context.data_ptr);
-		rDR = *(context.data_ptr++);
-		context.data_count--;
-	} else {
-		LOG('-', 0);
-		rDR = 0xff;
-	}
-}
-
-/* cribbed directly from the NuttX master driver */
-static void 
-i2c_setclock(uint32_t frequency)
-{
-	uint16_t cr1;
-	uint16_t ccr;
-	uint16_t trise;
-	uint16_t freqmhz;
-	uint16_t speed;
-
-	/* Disable the selected I2C peripheral to configure TRISE */
-
-	cr1 = rCR1;
-	rCR1 &= ~I2C_CR1_PE;
-
-	/* Update timing and control registers */
-
-	freqmhz = (uint16_t)(STM32_PCLK1_FREQUENCY / 1000000);
-	ccr = 0;
-
-	/* Configure speed in standard mode */
-
-	if (frequency <= 100000) {
-		/* Standard mode speed calculation */
-
-		speed = (uint16_t)(STM32_PCLK1_FREQUENCY / (frequency << 1));
-
-		/* The CCR fault must be >= 4 */
-
-		if (speed < 4) {
-			/* Set the minimum allowed value */
-
-			speed = 4;  
-		}
-		ccr |= speed;
-
-		/* Set Maximum Rise Time for standard mode */
-
-		trise = freqmhz + 1; 
-				
-	/* Configure speed in fast mode */
-	} else { /* (frequency <= 400000) */
-		/* Fast mode speed calculation with Tlow/Thigh = 16/9 */
-
-#ifdef CONFIG_I2C_DUTY16_9
-	      speed = (uint16_t)(STM32_PCLK1_FREQUENCY / (frequency * 25));
-
-		/* Set DUTY and fast speed bits */
-
-		ccr |= (I2C_CCR_DUTY|I2C_CCR_FS);
-#else
-		/* Fast mode speed calculation with Tlow/Thigh = 2 */
-
-		speed = (uint16_t)(STM32_PCLK1_FREQUENCY / (frequency * 3));
-
-		/* Set fast speed bit */
-
-		ccr |= I2C_CCR_FS;
-#endif
-
-		/* Verify that the CCR speed value is nonzero */
-
-		if (speed < 1) {
-	        	/* Set the minimum allowed value */
-
-	        	speed = 1;  
-	        }
-		ccr |= speed;
-
-		/* Set Maximum Rise Time for fast mode */
-
-		trise = (uint16_t)(((freqmhz * 300) / 1000) + 1);  
-	}
-
-	/* Write the new values of the CCR and TRISE registers */
-
-	rCCR = ccr;
-	rTRISE = trise;
-
-	/* Bit 14 of OAR1 must be configured and kept at 1 */
-
-	rOAR1 = I2C_OAR1_ONE);
-
-	/* Re-enable the peripheral (or not) */
-
-	rCR1 = cr1;
-}
diff --git a/nuttx/configs/px4io/src/empty.c b/nuttx/configs/px4io/src/empty.c
deleted file mode 100644
index ace900866..000000000
--- a/nuttx/configs/px4io/src/empty.c
+++ /dev/null
@@ -1,4 +0,0 @@
-/*
- * There are no source files here, but libboard.a can't be empty, so 
- * we have this empty source file to keep it company.
- */