diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html index 56ecb399286..52bd5b17773 100644 --- a/Documentation/NuttX.html +++ b/Documentation/NuttX.html @@ -8,7 +8,7 @@

NuttX RTOS

-

Last Updated: June 20, 2011

+

Last Updated: June 21, 2011

@@ -829,59 +829,97 @@ -

nuttx-6.4 Release Notes: +

nuttx-6.5 Release Notes:

- The 71st release of NuttX, Version 6.4, was made on June 6, 2011 and is available for download from the + The 72nd release of NuttX, Version 6.5, was made on June 21, 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 also listed here.

- The 6.4 release includes several new features: + The 6.5 release is all about support for the Atmel 8-bit AVR family. + I have been interested in the AVR family for some time but because of the + severe SRAM constraints and because of the availability of many tiny schedulers + for the AVR, it has not been "on the radar screen." + However, I have recently become interested because of interest expressed by + members of the Nuttx forum and because of the availability of newer, larger + capacity AVR parts (that I don't have yet). +

+

+ This release includes support for the following AVR boards. + As with any initial support for new architectures, there are some incomplete areas and a few caveats that need to be stated. + Here they are, ordered from the least to the most complete:

-

- This release also includes some completed but untested functionality: -

- -

- Additional miscellaneous enhancements and bug fixes to task_delete(), recvfrom(), and other changes as noted in the ChangeLog. +

AVR-Specific Issues. + The basic AVR port is solid and biggest issue for using AVR is its tiny SRAM memory and its Harvard architecture. + Because of the Harvard architecture, constant data that resides to flash is inaccessible using "normal" memory reads and writes (only SRAM data can be accessed "normally"). + Special AVR instructions are available for accessing data in FLASH, but these have not been integrated into the normal, general purpose OS.

+

+ Most NuttX test applications are console-oriented with lots of strings used for printf and debug output. + These strings are all stored in SRAM now due to these data accessing issues and even the smallest console-oriented applications can quickly fill a 4-8Kb memory. + So, in order for the AVR port to be useful, one of two things would need to be done: +

+
    +
  1. + Don't use console applications that required lots of strings. + The basic AVR port is solid and your typical deeply embedded application should work fine. + Or, +
  2. +
  3. + Create a special version of printf that knows how to access strings that reside in FLASH (or EEPROM). +
  4. +
@@ -1548,8 +1586,8 @@ @@ -1565,26 +1603,42 @@

PJRC Teensy++ 2.0 AT9USB1286. This is a port of NuttX to the PJRC Teensy++ 2.0 board. - This board is developed by PJRC. + This board was developed by PJRC. The Teensy++ 2.0 is based on an Atmel AT90USB1286 MCU.

+ + + + + + + + @@ -2290,62 +2344,30 @@ Other memory:



+

+ Development Environments: + 1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain. + All testing, however, has been performed using the Nuttx DIY toolchain for Linux or Cygwin is provided by the NuttX + buildroot package. + As a result, that toolchain is recommended. +

+