From ea9632faaa263a373e0ddfbdb0cc20187789ab61 Mon Sep 17 00:00:00 2001 From: patacongo Date: Wed, 8 Sep 2010 01:53:23 +0000 Subject: [PATCH] Prep for 5.10 release git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2928 42af7a65-404d-4744-a932-0658087f49c3 --- Documentation/NuttX.html | 120 +++++++++++++++++++++++++-------------- 1 file changed, 77 insertions(+), 43 deletions(-) diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html index 4ea3c1f50fc..9a6087152d9 100644 --- a/Documentation/NuttX.html +++ b/Documentation/NuttX.html @@ -8,7 +8,7 @@

NuttX RTOS

-

Last Updated: September 5, 2010

+

Last Updated: September 7, 2010

@@ -772,58 +772,72 @@ -

nuttx-5.9 Release Notes: +

nuttx-5.10 Release Notes:

- This 56th release of NuttX was made on August 25, 2010 and is available for download from the + This 57th release of NuttX, Version 5.10, was made on September 7, 2010 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 CVS. These unreleased changes are listed here. -

- This release is difficult to categorize; - NuttX-5.9 was really released because there were too many changes accumulating in CVS -- - a few important, some large, unverified implementations, and a couple of important bugfixes. -

- This includes several important bugfixes: + This release includes a combination of some new features as well as several bugfixes. + New features include:

@@ -1153,6 +1167,20 @@
+ +
+ +

+ 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. +

+ + + +
+
+
@@ -1244,15 +1272,15 @@ STATUS: Some initial files for the LPC17xx family were released in NuttX 5.6, but the first functional release for the NXP LPC1768/Nucleus2G occured with NuttX 5.7 with some - additional enhancements through NuttX-5.9. + additional enhancements through NuttX-5.9. That initial, 5.6, basic release included timer interrupts and a serial console and was verified using the NuttX OS test (examples/ostest). - Configurations available include include a verified NuttShell (NSH) configuration + Configurations available include include a verified NuttShell (NSH) configuration (see the NSH User Guide). The NSH configuration support the Nucleus2G's microSD slot and additional configurations are available to exercise the the USB serial and USB mass storage devices. - However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified. - (Although it has been reported to me that the SPI microSD is functional on other platforms). + However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified. + (Although it has been reported to me that the SPI microSD is functional on other platforms).

Development Environments: @@ -1933,14 +1961,14 @@ nuttx-5.10 2010-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> For people who have their own configurations and/or Makefiles, you will need to make a couple of changes: - - Replace all occurrences of CONFIG_EXAMPLE=foobar with + - Replace all occurrences of CONFIG_EXAMPLE=foobar with CONFIG_APP_DIR=examples/foobar in all of the configuration files. - Replace any occurrences of examples/$(CONFIG_EXAMPLE) with $(CONFIG_APP_DIR) - Replace any occurrences of lib$(CONFIG_EXAMPLE)$(LIBEXT) with libapp$(LIBEXT) in your Makefiles. - - Check any other occurrences of CONFIG_EXAMPLE.pascal-2.1 2010-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> + - Check any other occurrences of CONFIG_EXAMPLE. * arch/arm/src/lpc313x/lpc313x_spi.c - Fix compilation error when when CONFIG_DEBUG is enabled. @@ -1952,6 +1980,12 @@ nuttx-5.10 2010-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> should not be conditioned on CONFIG_ARCH_LEDs being defined! * arch/arm/src/lpc313x/ - APB0 and APB1 cannot lie in different sections; they are too close together. + * arch/arm/src/lpc313x/lpc13x_boot.c - Resetting all of the clocking + had a side effect of wiping out the first 6 words of memory where the + interrupt vectors are located (and also not resetting the fractional + dividers). This is not usually noticeable because the IRQ vectors + are after this point, but really causes problems if you want to handle + data and prefectch aborts which are within this zeroed region. pascal-2.1 2010-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>