Prep for 5.8 release

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2810 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo
2010-07-18 15:30:23 +00:00
parent 4b7e64be02
commit a46a349ae9
4 changed files with 144 additions and 74 deletions
+32
View File
@@ -1298,3 +1298,35 @@ ARM Cortex-M3 architecture:
Further efforts include: (1) development of a DMA support library, (2) SPI-based MMC/SD
support, and (3) verification of the USB driver. Watch for announcement of the completed
LPC1768 port expected in NuttX-5.8.
nuttx-5.8
^^^^^^^^^
This is the 55th release of NuttX. This includes several important bugfixes:
* Corrects some interrupt vectoring for the TI/Stellarix LM3S port
* Correct initialization logic for NXP LPC17xxx NuttX ports: Power was
not being provided to the GPIO module!
* Corrected (but did not verify) implementation of the optional interrupt
stack feature (all Cortex M3 architectures).
* Correct a HardFault in the LPC17xx SSP driver.
Additional minor fixes are also included as detailed in the ChangeLog.
Several new features have been fully developed and included in this release, but
full verification of most of these new features has been blocked for a variety
of issues:
* Added microSD support for the NuttShell (NSH) configuration in the
Nucleus2G LPC1768 port. For reasons that have not yet been determined,
I have not successfully accessed the microSD card as of this writing.
* Two USB configurations were also added for the Nucleus2G board: One to
support the USB serial device and one for the USB mass storage device.
Some testing of the USB driver was performed, but full verification is
stalled for an OTG style USB cable.
* LEDs now work correctly on the Nucleus2G LPC1768 board.
* The NuttX/uIP networking subsystem now supports IGMPv2 client. IGMP
(Internet Group Multicast Protocol) network "appliances" to join into
multicast groups. Outbound traffic to enter and leave multicast groups
has been verified, but full verification will require a switch capable of
multicast. Issues associated with the receipt of multicast packets are likely.