uTasker V1.4.3 LPC2xxx Release with utFAT file system

[mark]

Hi All

I am very pleased to announce that the uTaskerV1.4.3 LPC2xxx release with utFAT is now available. Please watch the utFAT forum for technical details about the new SD-card support.

Here is an overview of the LPC2xxx V1.4 versions and the additions in the latest release.
-0 Original release on 3.8.2009
-1 8.8.2009
-2 11.10.2009
-3 New version 5.1.2010:
- uTaskerCombine V1.1 in \Tools allows Intel Hex file output beyond 64k size
- improved LPC21xx support and internal Real Time Clock
- LPC23xx.c
   02.11.2009 Use fast IO with LPC2104/5/6 since new revisions have fast ports {11}
   03.11.2009 Correct I2C character counter                              {12}
   07.11.2009 Add periodic timer and PWM                                 {13}
   08.11.2009 Modify the LPC21XX vectored interrupt entry routine to support all possible interrupt sources {14}
   14.11.2009 Enable FLASH operations when USE_PARAMETER_AREA is used    {15}
   06.12.2009 Correction to avoid unnecessary FLASH buffer write when no buffer is open {16}
- LPC23xx.h
   02.11.2009 Use fast IO with LPC2104/5/6 since new revisions have fast ports {9}
   02.11.2009 Correct _WRITE_PORT and _WRITE_PORT_MASK macros for simulator {10}
   07.11.2009 Add option timer mode and new modes, plus LPC2103 PWM registers {11}
   03.12.2009 Extended part IDs                                          {12}
- new application "SerialBoot" as reference for simple project
- random ID added to DNS to avoid problems with servers rejecting repeated IDs
- New permanent ARP entry option
- New application project "serial loader"
- Optionally add HTTP plain text header information - define HTTP_HEADER_CONTENT_INFO
- optional USE_PARAMETER_AREA support (as simple alternative to USE_PARAMETER_BLOCK)
- utFAT V1.0 SD card support added (integrated in FTP, HTTP servers plus DOS-like interface)
Note that SDCARD_SUPPORT is enabled by default and GLCD is disabled - the heap size has been increased to enable utFAT together with other services.
Configured for MCB2300 (SD card of SPI1 - not card slot! P0.14 used as chip select. 336k uFileSystem size)


The new version is downloaded when you use the original project link and can be opened with the V1.4 password.
Intermediate versions are also available in case they are needed by adding -0 (for the original release), -1 for the second release, etc.

The new utFAT module's user's guide is still in progress (probably about 65% complete) but can already be accessed here:
http://www.utasker.com/docs/uTasker/uTasker_utFAT.PDF

I am very exited about the new capabilities that the utFAT adds to the project, opening up a variety of new opportunities. It is is fully integrated into the FTP and HTTP servers and has a comfortable DOS-like menu interface via UART, USB-CDC and/or TELNET. Take a look at the user's guide to learn more about it, and see how the simulator allows SD card operation together with the uTasker simulator!! If you have an SD card slot on your development board you can also immediately start using it as source for web pages or for logging data to.

Here's to a great start in the new year - all the best for 2010.

Regards

Mark

[mark]

Hi All

Here are notes about the present version:

1) When using GCC (standalone or Rowley Crossworks) the defines for FIOXMASK in lpc23xx.h (when X is 0..4) should be change to volatile. Eg.
#define FIO0MASK                         *(_VOLATILE unsigned long*)(FAST_GPIO_BLOCK + 0x10)

This will allow the LCD to operate correctly, otherwise GCC optimises some access from the new port macros used for access.

2) The new project works well with Rowley Crossworks (including the new utFAT interface).
Unfortunately the stand-alone GCC build is not very reliable. It detects an SD card but doesn't mount it correctly. The processor tends to hang quite easily when using the serial command menu. When refreshing the start side of the web server a few times it often hangs.

It is rather surprising that the Rowley build works well but the standalone build is so unstable. Since the GCC standalone project is something which has been rather neglected in the LPC2XXX project I also don't know for sure whether this is a new problem (it is not due to the new utFAT because it is also unstable without this module linked) or whether it was always a bit like this.

I will work on identifying the source of this difference - in the meantime it may mean sticking with the previous version or else using Rowley - the IAR test was also fine so it only affects the standalone GCC (perhaps also only the GCC version that I am using, which is  4.3.2 (Sourcery G++ Lite 2008q3-66).

Regards

Mark