NuttX RTOSLast Updated: March 11, 2011 |
Table of Contents |
|
Overview |
Goals. Nuttx is a real timed embedded operating system (RTOS). Its goals are:
Small Footprint | |
Usable in all but the tightest micro-controller environments, The focus is on the tiny-to-small, deeply embedded environment. | |
Rich Feature OS Set | |
The goal is to provide implementations of most standard POSIX OS interfaces to support a rich, multi-threaded development environment for deeply embedded processors. NON-GOALS: (1) It is not a goal to provide the rich level of OS features like those provided with Linux. Small footprint is more important than features. Standard compliance is more important than small footprint. (2) There is no MMU-based support for processes. At present, NuttX assumes a flat address space. | |
Highly Scalable | |
Fully scalable from tiny (8-bit) to moderate embedded (32-bit). Scalability with rich feature set is accomplished with: Many tiny source files, link from static libraries, highly configurable, use of weak symbols when available. | |
Standards Compliance | |
NuttX strives to achieve a high degree of standards compliance.
The primary governing standards are POSIX and ANSI standards.
Additional standard APIs from Unix and other common RTOS's are
adopted for functionality not available under these standards
or for functionality that is not appropriate for the deeply-embedded
RTOS (such as Because of this standards conformance, software developed under other standard OSs (such as Linux) should port easily to NuttX. | |
Real-Time | |
Fully pre-emptible, fixed priority and round-robin scheduling. | |
Totally Open | |
Non-restrictive BSD license. | |
GNU Toolchains | |
Compatible GNU toolchains based on buildroot available for download to provide a complete development environment for many architectures. |
Feature Set. Key features of NuttX include:
Standards Compliant Core Task Management | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
File system | |
| |
| |
| |
/dev/null , /dev/zero drivers. | |
| |
| |
| |
| |
| |
C Library | |
| |
Networking | |
| |
| |
| |
| |
| |
FLASH Support | |
| |
| |
| |
USB Host Support | |
| |
| |
| |
USB Device Support | |
| |
| |
| |
| |
Graphics Support | |
| |
| |
|
NuttX Add-Ons. The following packages are available to extend the basic NuttX feature set:
NuttShell (NSH) | |
| |
Pascal Compiler with NuttX runtime P-Code interpreter add-on | |
|
Look at all those files and features... How can it be a tiny OS?. The NuttX feature list (above) is fairly long and if you look at the NuttX source tree, you will see that there are hundreds of source files comprising NuttX. How can NuttX be a tiny OS with all of that?
Lots of Features -- More can be smaller! | |
The philosophy behind that NuttX is that lots of features are great... BUT also that if you don't use those features, then you should not have to pay a penalty for the unused features. And, with NuttX, you don't! If you don't use a feature, it will not be included in the final executable binary. You only have to pay the penalty of increased footprint for the features that you actually use. Using a variety of technologies, NuttX can scale from the very tiny to the moderate-size system. I have executed NuttX with some simple applications in as little as 32Kb total memory (code and data). On the other hand, typical, richly featured NuttX builds require more like 64Kb (and if all of the features are used, this can push 100Kb). |
|
Many, many files -- More really is smaller! | |
One may be intimidated by the size NuttX source tree. There are hundreds of source files! How can that be a tiny OS? Actually, the large number of files is one of the tricks to keep NuttX small and as scalable as possible. Most files contain only a single function. Sometimes just one tiny function with only a few lines of code. Why?
|
|
Other Tricks | |
As mentioned above, the use of many, tiny source files and linking from static libraries keeps the size of NuttX down. Other tricks used in NuttX include:
|
NuttX Discussion Group |
Most Nuttx-related discussion occurs on the Yahoo! NuttX group. You are cordially invited to join. I make a special effort to answer any questions and provide any help that I can.
Downloads |
nuttx-5.18 Release Notes:
The 65th release of NuttX, Version 5.18, was made on February 27, 2011 and is available for download from the SourceForge website. The change log associated with the release is available here. Unreleased changes after this release are available in SVN. These unreleased changes are listed here.
This is first release from the new NuttX SVN repository. This release is made primarily to keep the release tarball in synchronization with SVN. Many smaller changes have been made as identified in the ChangeLog. Headlines would include:
Supported Platforms |
Linux User Mode | |
A user-mode port of NuttX to the x86 Linux/Cygwin platform is available. The purpose of this port is primarily to support OS feature development. STATUS: Does not support interrupts but is otherwise fully functional. |
|
ARM7TDMI. | |
TI TMS320C5471 (also called C5471 or TMS320DA180 or DA180). NuttX operates on the ARM7 of this dual core processor. This port uses the Spectrum Digital evaluation board with a GNU arm-elf toolchain* under Linux or Cygwin. STATUS: This port is complete, verified, and included in the initial NuttX release. |
|
NXP LPC214x. Support is provided for the NXP LPC214x family of processors. In particular, support is provided for the mcu123.com lpc214x evaluation board (LPC2148). This port also used the GNU arm-elf toolchain* under Linux or Cygwin. STATUS: This port boots and passes the OS test (examples/ostest). The port is complete and verified. As of NuttX 0.3.17, the port includes: timer interrupts, serial console, USB driver, and SPI-based MMC/SD card support. A verified NuttShell (NSH) configuration is also available. Development Environments: 1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain (CodeSourcery or devkitARM). A DIY toolchain for Linux or Cygwin is provided by the NuttX buildroot package. |
|
NXP LPC2378. Support is provided for the NXP LPC2378 MCU. In particular, support is provided for the Olimex-LPC2378 development board. This port was contributed by Rommel Marcelo is was first released in NuttX-5.3. This port also used the GNU arm-elf toolchain* under Linux or Cygwin. STATUS: This port boots and passes the OS test (examples/ostest) and includes a working implementation of the NuttShell (NSH). The port is complete and verified. As of NuttX 5.3, the port includes only basic timer interrupts and serial console support. Development Environments: (Same as for the NXP LPC214x). |
|
STMicro STR71x. Support is provided for the STMicro STR71x family of processors. In particular, support is provided for the Olimex STR-P711 evaluation board. This port also used the GNU arm-elf toolchain* under Linux or Cygwin. STATUS: Integration is complete on the basic port (boot logic, system time, serial console). Two configurations have been verified: (1) The board boots and passes the OS test with console output visible on UART0, and the NuttShell (NSH) is fully functional with interrupt driven serial console. An SPI driver is available but only partially tested. Additional features are needed: USB driver, MMC integration, to name two (the slot on the board appears to accept on MMC card dimensions; I have only SD cards). An SPI-based ENC29J60 Ethernet driver for add-on hardware is under development and should be available in the NuttX 5.5 release. Development Environments: 1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain (CodeSourcery or devkitARM). A DIY toolchain for Linux or Cygwin is provided by the NuttX buildroot package. |
|
ARM920T. | |
Freescale MC9328MX1 or i.MX1. This port uses the Freescale MX1ADS development board with a GNU arm-elf toolchain* under either Linux or Cygwin. STATUS: This port has stalled due to development tool issues. Coding is complete on the basic port (timer, serial console, SPI). |
|
ARM926EJS. | |
TI TMS320DM320 (also called DM320). NuttX operates on the ARM9 of this dual core processor. This port uses the Neuros OSD with a GNU arm-elf toolchain* under Linux or Cygwin. The port was performed using the OSD v1.0, development board. STATUS: The basic port (timer interrupts, serial ports, network, framebuffer, etc.) is complete. All implemented features have been verified with the exception of the USB device-side driver; that implementation is complete but untested. |
|
NXP LPC3131.
The port for the NXP LPC3131 on the Embedded Artists EA3131
development board was first released in NuttX-5.1 with a GNU arm-elf or arm-eabi toolchain* under Linux or Cygwin
(but was not functional until NuttX-5.2).
STATUS: The basic EA3131 port is complete and verified in NuttX-5.2 This basic port includes basic boot-up, serial console, and timer interrupts. This port was extended in NuttX 5.3 with a USB high speed driver contributed by David Hewson. David also contributed I2C and SPI drivers plus several important LPC313x USB bug fixes that appear in the NuttX 5.6 release. This port has been verified using the NuttX OS test, USB serial and mass storage tests and includes a working implementation of the NuttShell (NSH). Support for on-demand paging has been developed for the EA3131. That support would all execute of a program in SPI FLASH by paging code sections out of SPI flash as needed. However, as of this writing, I have not had the opportunity to verify this new feature. |
|
ARM Cortex-M3. | |
Luminary/TI LM3S6918. This port uses the Micromint Eagle-100 development board with a GNU arm-elf toolchain* under either Linux or Cygwin. STATUS: The initial, release of this port was included in NuttX version 0.4.6. The current port includes timer, serial console, Ethernet, SSI, and microSD support. There are working configurations the NuttX OS test, to run the NuttShell (NSH), the NuttX networking test, and the uIP web server. Development Environments: 1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain (CodeSourcery or devkitARM). A DIY toolchain for Linux or Cygwin is provided by the NuttX buildroot package. |
|
Luminary/TI LM3S6965. This port uses the Stellaris LM3S6965 Ethernet Evalution Kit with a GNU arm-elf toolchain* under either Linux or Cygwin. STATUS: This port was released in NuttX 5.5. Features are the same as with the Eagle-100 LM3S6918 described above. The examples/ostest configuration has been successfully verified and an NSH configuration with telnet support is available. MMC/SD and Networking support was not been thoroughly verified: Current development efforts are focused on porting the NuttX window system (NX) to work with the Evaluation Kits OLED display. NOTE: As it is configured now, you MUST have a network connected. Otherwise, the NSH prompt will not come up because the Ethernet driver is waiting for the network to come up. Development Environments: See the Eagle-100 LM3S6918 above. |
|
Luminary/TI LM3S8962. This port uses the Stellaris EKC-LM3S8962 Ethernet+CAN Evalution Kit with a GNU arm-elf toolchain* under either Linux or Cygwin. Contributed by Larry Arnold. STATUS: This port was released in NuttX 5.10. Features are the same as with the Eagle-100 LM3S6918 described above. |
|
Luminary/TI LM3S9B96. Header file support was contributed by Tiago Maluta for this part. However, no complete board support configuration is available as of this writing. |
|
STMicro STM32F103x. Support for three MCUs and two board configurations are available. MCU support includes: STM32F103ZET6, STM32F103RET6, and STM32F107VC. Board support includes:
These ports uses a GNU arm-elf toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
STATUS: Development Environments: 1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain (RIDE7, CodeSourcery or devkitARM). A DIY toolchain for Linux or Cygwin is provided by the NuttX buildroot package. |
|
Atmel AT91SAM3U. This port uses the Atmel SAM3U-EK development board that features the AT91SAM3U4E MCU. This port uses a GNU arm-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools). STATUS: The basic SAM3U-EK port was released in NuttX version 5.1. The basic port includes boot-up logic, interrupt driven serial console, and system timer interrupts. That release passes the NuttX OS test and is proven to have a valid OS implementation. A configuration to support the NuttShell is also included. NuttX version 5.4 adds support for the HX8347 LCD on the SAM3U-EK board. This LCD support includes an example using the NX graphics system. Subsequent NuttX releases will extend this port and add support for SDIO-based SD cards and USB device (and possible LCD support). These extensions may or may not happen by the Nuttx 5.5 release as my plate is kind of full now. Development Environments: 1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain (CodeSourcery or devkitARM). A DIY toolchain for Linux or Cygwin is provided by the NuttX buildroot package. |
|
NXP LPC1766 and LPC1768. Configurations are available for three boards:
The Nucleus 2G and the mbed boards feature the NXP LPC1768 MCU; the Olimex LPC1766-STK board features an LPC1766. All use a GNU arm-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
STATUS: The following summarizes the features that has been developed and verified on individual LPC17xx-based boards. These features should, however, be common and available for all LPC17xx-based boards. Nucleus2G LPC1768.
That initial, 5.6, basic release included timer interrupts and a serial console and was
verified using the NuttX OS test ( mbed LPC1768.
This port includes a NuttX OS test configuration (see Olimex LPC1766-STK. Verified configurations are now available for the NuttX OS test, for the NuttShell with networking and microSD support(NSH, see the NSH User Guide), for the NuttX network test, for the THTTPD webserver, for USB serial deive and USB storage devices examples, and for the USB host HID keyboard driver. Support for the USB host mass storage device can optionally be configured for the NSH example. A driver for the Nokia 6100 LCD and an NX graphics configuration for the Olimex LPC1766-STK have been added. However, neither the LCD driver nor the NX configuration have been verified as of the the NuttX-5.17 release. Development Environments: 1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain (CodeSourcery or devkitARM). A DIY toolchain for Linux or Cygwin is provided by the NuttX buildroot package. |
|
Intel 8052 Microcontroller | |
PJRC 87C52 Development Board. This port uses the PJRC 87C52 development system and the SDCC toolchain under Linux or Cygwin. STATUS: This port is complete but not stable with timer interrupts enabled. There seems to be some issue when the stack pointer enters into the indirect IRAM address space during interrupt handling. This architecture has not been built in some time will likely have some compilation problems because of SDCC compiler differences. |
|
Intel 80486 (i486) Microprocessor | |
QEMU i486. This port uses the QEMU i486 and the native Linux, Cywgin, MinGW the GCC toolchain under Linux or Cygwin. STATUS: This port is code complete but not yet tested. Stayed tuned. |
|
Frescale M68HSC12 | |
MC9S12NE64. Support for the MC9S12NE64 MCU and two boards are included:
Both use a GNU arm-elf toolchain* under Linux or Cygwin. The NuttX buildroot provides a properly patched GCC 3.4.4 toolchain that is highly optimized for the m9s12x family. STATUS: Coding is complete for the MC9S12NE64 and for the NE64 Badge board. However, testing has not yet begun due to issues with BDMs, Code Warrior, and the paging in the build process. Progress is slow, but I hope to see a fully verified MC9S12NE64 port in the near future. |
|
Atmel AVR32 | |
AV32DEV1. This port uses the www.mcuzone.com AVRDEV1 board based on the Atmel AT32UC3B0256 MCU. This port requires a special GNU avr32 toolchain available from atmel.com website. This is a windows native toolchain and so can be used only under Cygwin on Windows.
STATUS: This port is has completed all basic development, but there is more that needs to be done. All code is complete for the basic NuttX port including header files for all AT32UC3* peripherals. The untested AVR32 code was present in the 5.12 release of NuttX. Since then, the basic RTOS port has solidified: |
|
Renesas/Hitachi SuperH | |
SH-1 SH7032. This port uses the Hitachi SH-1 Low-Cost Evaluation Board (SH1_LCEVB1), US7032EVB, with a GNU arm-elf toolchain* under Linux or Cygwin. STATUS: This port is available as of release 0.3.18 of NuttX. The port is basically complete and many examples run correctly. However, there are remaining instabilities that make the port un-usable. The nature of these is not understood; the behavior is that certain SH-1 instructions stop working as advertised. This could be a silicon problem, some pipeline issue that is not handled properly by the gcc 3.4.5 toolchain (which has very limit SH-1 support to begin with), or perhaps with the CMON debugger. At any rate, I have exhausted all of the energy that I am willing to put into this cool old processor for the time being. |
|
Renesas M16C/26 | |
Renesas M16C/26 Microncontroller. This port uses the Renesas SKP16C26 Starter kit and the GNU M32C toolchain. The development environment is either Linux or Cygwin under WinXP.
STATUS:
Initial source files released in nuttx-0.4.2.
At this point, the port has not been integrated; the target cannot be built
because the GNU m32c-elf-ld: BFD (GNU Binutils) 2.19 assertion fail /home/Owner/projects/nuttx/buildroot/toolchain_build_m32c/binutils-2.19/bfd/elf32-m32c.c:482
Where the reference line is: /* If the symbol is out of range for a 16-bit address, we must have allocated a plt entry. */ BFD_ASSERT (*plt_offset != (bfd_vma) -1); No workaround is known at this time. This is a show stopper for M16C for the time being. |
|
Zilog Z16F | |
Zilog z16f Microncontroller. This port use the Zilog z16f2800100zcog development kit and the Zilog ZDS-II Windows command line tools. The development environment is Cygwin under WinXP. STATUS: The initial release of support for the z16f was made available in NuttX version 0.3.7. |
|
Zilog eZ80 Acclaim! | |
Zilog eZ80Acclaim! Microncontroller. There are two eZ80Acclaim! ports:
Both boards are based on the eZ80F091 part and both use the Zilog ZDS-II Windows command line tools. The development environment is Cygwin under WinXP. STATUS: Integration and testing of NuttX on the ZiLOG ez80f0910200zcog-d is complete. The first integrated version was released in NuttX version 0.4.2 (with important early bugfixes in 0.4.3 and 0.4.4). As of this writing, that port provides basic board support with a serial console, SPI, and eZ80F91 EMAC driver. |
|
Zilog Z8Encore! | |
Zilog Z8Encore! Microncontroller. This port uses the either:
and the Zilog ZDS-II Windows command line tools. The development environment is Cygwin under WinXP. STATUS: This release has been verified only on the ZiLOG ZDS-II Z8Encore! chip simulation as of nuttx-0.3.9. |
|
Zilog Z80 | |
Z80 Instruction Set Simulator. This port uses the SDCC toolchain under Linux or Cygwin (verified using version 2.6.0). This port has been verified using only a Z80 instruction simulator. That simulator can be found in the NuttX SVN here. STATUS: This port is complete and stable to the extent that it can be tested using an instruction set simulator. |
|
XTRS: TRS-80 Model I/III/4/4P Emulator for Unix. A very similar Z80 port is available for XTRS, the TRS-80 Model I/III/4/4P Emulator for Unix. That port also uses the SDCC toolchain under Linux or Cygwin (verified using version 2.6.0). STATUS: Basically the same as for the Z80 instruction set simulator. This port was contributed by Jacques Pelletier. |
|
Other ports | |
There are partial ports for the TI TMS320DM270 and for MIPS. |
* A highly modified buildroot is available that may be used to build a NuttX-compatible ELF toolchain under Linux or Cygwin. Configurations are available in that buildroot to support ARM, m68k, m68hc11, m68hc12, and SuperH ports.
Development Environments |
Linux + GNU make + GCC/binutils
|
|
The is the most natural development environment for NuttX. Any version of the GCC/binutils toolchain may be used. There is a highly modified buildroot available for download from the NuttX SourceForge page. This download may be used to build a NuttX-compatible ELF toolchain under Linux or Cygwin. That toolchain will support ARM, m68k, m68hc11, m68hc12, and SuperH ports. The buildroot SVN may be accessed in the NuttX SVN. |
|
Linux + GNU make + SDCC
|
|
Also very usable is the Linux environment using the SDCC compiler. The SDCC compiler provides support for the 8051/2, z80, hc08, and other microcontrollers. The SDCC-based logic is less well exercised and you will likely find some compilation issues if you use parts of NuttX with SDCC that have not been well-tested. |
|
Cygwin + GNU make + GCC/binutils
|
|
This combination works well too. It works just as well as the native Linux environment except that compilation and build times are a little longer. The custom NuttX buildroot referenced above may be build in the Cygwin environment as well. |
|
Cygwin + GNU make + SDCC
|
|
I have never tried this combination, but it would probably work just fine. |
|
Cygwin + GNU make + Windows Native Toolchain
|
|
This is a tougher environment. In this case, the Windows native toolchain is unaware of the Cygwin sandbox and, instead, operates in the native Windows environment. The primary difficulties with this are:
Fortunately, this conversion is done simply using the The NuttX make system works around this limitation by copying the platform specific directories in place. These copied directories make work a little more complex, but otherwise work well.
NOTE: In this environment, it should be possible to use the NTFS
NOTE: dependencies are suppress by setting the make variable Supported Windows Native Toolchains. At present, only the Zilog Z16F, z8Encore, and eZ80Acclaim ports use a non-GCC native Windows toolchain(the Zilog ZDS-II toolchain). Support for Windows native GCC toolchains (CodeSourcery and devkitARM) is currently implemented for the NXP LPC214x, STMicro STR71x, and Luminary LMS6918 ARM ports. (but could easily be extended to any other GCC-based platform with a small effort). |
|
Other Environments?
Windows Native make + Windows Native Toolchain?
|
|
Environment Dependencies. The primary environmental dependency of NuttX are (1) GNU make, (2) bash scripting, and (3) Linux utilities (such as cat, sed, etc.). If you have other platforms that support GNU make or make utilities that are compatible with GNU make, then it is very likely that NuttX would work in that environment as well (with some porting effort). If GNU make is not supported, then some significant modification of the Make system would be required. GNUWin32. For example, with suitable make system changes, it should be possible to use native GNU tools (such as those from GNUWin32) to build NuttX. However, that environment has not been used as of this writing.
NOTE: One of the members on the NuttX forum
reported that they successful built NuttX using such a GNUWin32-based, Windows native environment.
They reported that the only necessary change was to the use the NTFS mklink command to create links
(see |
Memory Footprint |
C5471 (ARM7) The build for this ARM7 target that includes most of the OS features and a broad range of OS tests. The size of this executable as given by the Linux size command is (3/9/07):
text data bss dec hex filename 53272 428 3568 57268 dfb4 nuttx
DM320 (ARM9) This build for the ARM9 target includes a significant subset of OS features, a filesystem, Ethernet driver, full TCP/IP, UDP and (minimal) ICMP stacks (via uIP) and a small network test application: (11/8/07, configuration netconfig, examples/nettest)
text data bss dec hex filename 49472 296 3972 53740 d1ec nuttx
Another build for the ARM9 target includes a minimal OS feature set, Ethernet driver, full TCP/IP and (minimal) ICMP stacks, and a small webserver: (11/20/07, configuration uipconfig, examples/uip)
text data bss dec hex filename 52040 72 4148 56260 dbc4 nuttx
87C52 A reduced functionality OS test for the 8052 target requires only about 18-19Kb:
Stack starts at: 0x21 (sp set to 0x20) with 223 bytes available. Other memory: Name Start End Size Max ---------------- -------- -------- -------- -------- PAGED EXT. RAM 0 256 EXTERNAL RAM 0x0100 0x02fd 510 7936 ROM/EPROM/FLASH 0x2100 0x6e55 19798 24384
Licensing |
NuttX is available under the highly permissive BSD license. Other than some fine print that you agree to respect the copyright you should feel absolutely free to use NuttX in any environment and without any concern for jeopardizing any proprietary software that you may link with it.
Release History |
The current NuttX Change Log is available in SVN here. ChangeLog snapshots associated with the current release are available below.
Change Logs for All NuttX Releases |
|
ChangeLog for the Current Releases |
|
Unreleased Changes |
ChangeLog for the Current Release |
nuttx-5.18 2011-02-27 Gregory Nutt <spudmonkey@racsa.co.cr> * Incorporate several uIP patches from http://gitweb.aeruder.net/?p=uip.git;a=summary. - Lost SYNACK causes connection reset - Fix missing UDP stats for sent/received packets - Added support for Cygwin as development/test platform. * configs/demo9s12ne64 - Integrate new buildroot-1.9 m8s12x toolchain. * 'uname -o' is used throughout the build logic in bash scripts and also in Make.defs files in order to distinguish between Cygwin and Linux. However, the -o option is not standard and is not supported under, for example, OS-X or Solaris. This was solved by changing all 'uname -o' references to the more complex: 'uname -o 2>/dev/null || echo "Other"' * drivers/usbhost/usbhost_enumerate.c -- Add logic to get the VID and PID. This is necessary in order to support vendor-specific USB devices. * examplex/wlan, configs/olimex-lpc1766stk/wlan, drivers/usbhost/usbhost_rtl8187.c, Add infrastructure to support RTL18187 wireless USB. * configs/nucleus2g -- backed out USB host changes... wrong board. * Renamed arc/hc/include/mc9s12ne64 and src/mc9s12ne64 -- m9s12. That name is shorter and more general. * The NuttX repository has been converted to SVN and can now be found here http://nuttx.svn.sourceforge.net/viewvc/nuttx/ * configs/mbed/hidkbd -- Added USB host support for the mbed LPC1768 board; add a USB host HID keyboard configuraion. * drivers/usbhost/hid_parser.c -- Leverages the LUFA HID parser written by Dean Camera. * examples/nsh -- Correct an usage of getopt(): If you stop calling getopt() before all parameters are parsed, you can leave getopt() in a strange state. * include/nuttx/fb.h -- Restore missing RGB type that was accidentally removed when Nokia 6100 support was added. * Rename arch/pjrc-8051 to arch/8051 * configs/ne64badge -- Add a configuration for the Future Electronics Group NE64 Badge development board (Freescale MC9S12NE64) * Changes contributed by Uros Platise: - Add support for the STM32F103RET6 - configs/vsn - Support for the ISOTEL NetClamps VSN V1.2 ready2go sensor network platform * arch/hc, configs/ne64badge -- Development is complete for the Freescale mc9s12ne64 on the Future Electronics Group NE64 /PoE Badge board. Howeve, this port remains untested until I figure out this BDM / Code Warrior and paged build thing * Added a new 'kill' command to NSH that will support sending signals to running NuttX tasks. pascal-2.0 2009-12-21 Gregory Nutt <spudmonkey@racsa.co.cr> * Updated to use standard C99 types in stdint.h and stdbool.h. This change was necessary for compatibility with NuttX-5.0 (any beyond). buildroot-1.9 2011-02-10 <spudmonkey@racsa.co.cr> * configs/arm926t-defconfig-4.3.3: update arm926t-defconfig-4.2.4 * configs/arm926t-defconfig-nxflat: NXFLAT-only configuration for arm926 * toolchain/gdb/gdb.mk - Remove ncurses dependency from gdb_target target. * toolchain/gdb/gdb.mk - Added --disable-werror to GDB configuration line. GDB 6.8 won't build because the tarbal was released with -Werror enabled and the build stops on the first warning. * Add support for Freescale m9s12x using binutils 2.18 and gcc 3.3.6 and patches available from http://www.msextra.com/tools courtesy of James Cortina. Add configs/m9x12x-defconfig-3.3.6.
Unreleased Changes |
nuttx-5.19 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> * arch/arm/stm32/stm32_idle.c -- During idle times, the STM32 now uses the WFI instruction to sleep in a reduced power mode until the next interrupt occurs (Contributed by Uros Platise). * NSH: 'mem' command renamed to 'free'. Output is now more similar to the Linux 'free' command. * NSH: Correct a redirection bug in NSH. The following would not work; it resulted in a hang after the 'cat /dev/fifo': nsh> mkfile /dev/fifo nsh> cd /tmp # /tmp is a mounted RAM disk nsh> cat /dev/fifo > test.txt & nsh> echo "This is a test" > /dev/fifo The error was caused because (1) there was a path that resulted in stdout being closed (the "hang") and also (2) the 'cat' command was always outputting to stdout, not to the redirected file descriptor. Now: nsh> cat test.txt This is a test * drivers/pipes/pipe_common.c -- Driver open method eas not returning an EINTR error when it received a signal. Instead, it just re-started the wait. This makes it impossible to kill a background pipe operation from NSH. * include/stdint.h -- Correct some errors in conditional compilation (submitted by Johannes Hampel). * arch/arm/lpc17xx/lp17_idle.c -- Uses the same logic as the STM32: uses the WFI instruction to sleep in a reduced power mode until the next interrupt occurs. * configs/olimex-lpc1766stk -- Added an LED encoded to indicate if the LPC1766 is in sleeping. * examples/mm -- This is a simplified version of the "built-in" memory manager test of mm/mm_test.c. It is simplified because it does not have access to the internals of the memory manager as does mm/mm_test.c, but it has the advantage that it runs in the actual NuttX tasking environment (the mm/mm_test.c only runs in a PC simulation environment). * drivers/mmcsd_sdio.c/h -- Several corrections submitted by Uros Platise. * arch/x86 - Provide support for x86 architectures. Support for the i486 architecture under QEMU is provided under arch/x86/include/i486, arch/x86/include/qemu, arch/x86/src/i486, and arch/x86/src/qemu. * configs/qemu-i486 - "Board" support configurations for verifying the QEME i486 port. * arch/arm/src/stm32/stm32_spi.c -- Correct base address of SPI3 (reported by Uros Platise). * drivers/mmcsd/mmcsd_sdio.c -- Correct a loop termination condition (also reported by Uros Platise). * drivers/mtd/ramtron.c - Driver for SPI-based RAMTRON NVRAM devices FM25V10 (and others). Contributed by Uros Platise. * examples/nsh and tools/mkromfsimg.sh -- Add support for platform-specific ROMFS-based NSH start-up scripts. * drivers/uart_16550.c and include/nuttx/uart_16550.h - Support for a generic 16550 UART. * configure/qemu-i486/nsh - QEMU NSH example. * ../apps - The apps directory add-on was created by Uros Platise. It supports a set of end-user applications than can be executed on top of NSH. Think of it this way: In a buckled-up embedded application, your end-user programs will probably have their own dedicated start-up logic. But, during development, you might want to have you applications available and executable from the NSH command line. This apps/ addon (and NSH hooks) was contributed by Uros to accomplish just that. pascal-2.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> buildroot-1.10 2011-xx-xx* Add patch submitted by Dimiter Georgiev to work around problems in building GDB 6.8 with versions of Cygwin > 1.7. * configs/i486-defconfig-4.3.3 - Builds an i486 cross development toolchain using gcc 4.3.3. Why wouldyou want such a thing? On Linux, of course, such a thing is not needed because you can use the installed GCC to build i486 ELF binaries. But that will not work under Cygwin! The Cygwin toolchain (and probably MinGW), build DOS MZ format executables (i.e., .exe files). That is probably not usable for most NuttX targets. Instead, you should use this i486-elf-gcc to generate true ELF binaries under Cygwin.
Bugs, Issues, Things-To-Do |
The current list of NuttX Things-To-Do in SVN here. A snapshot of the To-Do list associated with the current release are available here.
Other Documentation |
User Guide | |
Porting Guide | |
NuttShell (NSH) | |
NXFLAT Binary Format | |
NX Graphics Subsystem | |
Demand Paging | |
NuttX README Files | |
Change Log | |
To-Do List | |
USB Device Driver Tracing |
Trademarks |
NOTE: NuttX is not licensed to use the POSIX trademark. NuttX uses the POSIX standard as a development guideline only.