diff --git a/Documentation/README.html b/Documentation/README.html
index b014caecad54a84fd5d63646f7f031ae86b7b1af..225692172428d774c357203c350a16d18df11e7a 100755
--- a/Documentation/README.html
+++ b/Documentation/README.html
@@ -9,7 +9,7 @@
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec"><i>NuttX README Files</i></font></big></h1>
- <p>Last Updated: October 14, 2009</p>
+ <p>Last Updated: December 31, 2009</p>
</td>
</tr>
</table>
@@ -49,6 +49,8 @@
| | `- <a href="configs/c5471evm/README.txt"><b><i>README.txt</i></b></a>
| |- demo9s12ne64/
| | `- <a href="configs/demo9s12ne64/README.txt"><b><i>README.txt</i></b></a>
+ | |- ea3131/
+ | | `- <a href="configs/ea3131/README.txt"><b><i>README.txt</i></b></a>
| |- eagle100/
| | |- <a href="configs/eagle100/include/README.txt">include/README.txt</a>
| | |- <a href="configs/eagle100/src/README.txt">src/README.txt</a>
diff --git a/README.txt b/README.txt
index 35e97ad68bafaaa154bf203f396ae6188f7f2e3e..63a61906b03ec1457dd6a0d156df15ed0cd2d17e 100755
--- a/README.txt
+++ b/README.txt
@@ -140,6 +140,8 @@ Below is a guide to the available README files in the NuttX source tree:
| | `- README.txt
| |- demo0s12ne64/
| | `- README.txt
+ | |- ea3131/
+ | | `- README.txt
| |- eagle100/
| | |- include/README.txt
| | |- src/README.txt
diff --git a/configs/ea3131/README.txt b/configs/ea3131/README.txt
new file mode 100755
index 0000000000000000000000000000000000000000..e52aafbb8a3d788b37b930760b189eff0bc95a2d
--- /dev/null
+++ b/configs/ea3131/README.txt
@@ -0,0 +1,295 @@
+README
+^^^^^^
+
+ This README file discusses the port of NuttX to the Embedded Artists
+ EA3131 board.
+
+Contents
+^^^^^^^^
+
+ o Development Environment
+ o GNU Toolchain Options
+ o IDEs
+ o NuttX buildroot Toolchain
+ o Boot Sequence
+ o ARM/EA3131-specific Configuration Options
+ o Configurations
+
+Development Environment
+^^^^^^^^^^^^^^^^^^^^^^^
+
+ Either Linux or Cygwin on Windows can be used for the development environment.
+ The source has been built only using the GNU toolchain (see below). Other
+ toolchains will likely cause problems.
+
+GNU Toolchain Options
+^^^^^^^^^^^^^^^^^^^^^
+
+ The NuttX make system has been modified to support the following different
+ toolchain options.
+
+ 1. The CodeSourcery GNU toolchain,
+ 2. The devkitARM GNU toolchain,
+ 3. Raisonance GNU toolchain, or
+ 4. The NuttX buildroot Toolchain (see below).
+
+ All testing has been conducted using the NuttX buildroot toolchain. However,
+ the make system is setup to default to use the devkitARM toolchain. To use
+ the CodeSourcery, devkitARM or Raisonance GNU toolchain, you simply need to
+ add one of the following configuration options to your .config (or defconfig)
+ file:
+
+ CONFIG_LPC313X_CODESOURCERYW=y : CodeSourcery under Windows
+ CONFIG_LPC313X_CODESOURCERYL=y : CodeSourcery under Linux
+ CONFIG_LPC313X_DEVKITARM=y : devkitARM under Windows
+ CONFIG_LPC313X_RAISONANCE=y : Raisonance RIDE7 under Windows
+ CONFIG_LPC313X_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
+
+ If you are not using CONFIG_LPC313X_BUILDROOT, then you may also have to modify
+ the PATH in the setenv.h file if your make cannot find the tools.
+
+ NOTE: the CodeSourcery (for Windows), devkitARM, and Raisonance toolchains are
+ Windows native toolchains. The CodeSourcey (for Linux) and NuttX buildroot
+ toolchains are Cygwin and/or Linux native toolchains. There are several limitations
+ to using a Windows based toolchain in a Cygwin environment. The three biggest are:
+
+ 1. The Windows toolchain cannot follow Cygwin paths. Path conversions are
+ performed automatically in the Cygwin makefiles using the 'cygpath' utility
+ but you might easily find some new path problems. If so, check out 'cygpath -w'
+
+ 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links
+ are used in Nuttx (e.g., include/arch). The make system works around these
+ problems for the Windows tools by copying directories instead of linking them.
+ But this can also cause some confusion for you: For example, you may edit
+ a file in a "linked" directory and find that your changes had not effect.
+ That is because you are building the copy of the file in the "fake" symbolic
+ directory. If you use a Windows toolchain, you should get in the habit of
+ making like this:
+
+ make clean_context all
+
+ An alias in your .bashrc file might make that less painful.
+
+ 3. Dependencies are not made when using Windows versions of the GCC. This is
+ because the dependencies are generated using Windows pathes which do not
+ work with the Cygwin make.
+
+ Support has been added for making dependencies with the windows-native toolchains.
+ That support can be enabled by modifying your Make.defs file as follows:
+
+ - MKDEP = $(TOPDIR)/tools/mknulldeps.sh
+ + MKDEP = $(TOPDIR)/tools/mkdeps.sh --winpaths "$(TOPDIR)"
+
+ If you have problems with the dependency build (for example, if you are not
+ building on C:), then you may need to modify tools/mkdeps.sh
+
+ NOTE 1: The CodeSourcery toolchain (2009q1) does not work with default optimization
+ level of -Os (See Make.defs). It will work with -O0, -O1, or -O2, but not with
+ -Os.
+
+ NOTE 2: The devkitARM toolchain includes a version of MSYS make. Make sure that
+ the paths to Cygwin's /bin and /usr/bin directories appear BEFORE the devkitARM
+ path or will get the wrong version of make.
+
+IDEs
+^^^^
+
+ NuttX is built using command-line make. It can be used with an IDE, but some
+ effort will be required to create the project (There is a simple RIDE project
+ in the RIDE subdirectory). Here are a few tip before you start that effort:
+
+ 1) Select the toolchain that you will be using in your .config file
+ 2) Start the NuttX build at least one time from the Cygwin command line
+ before trying to create your project. This is necessary to create
+ certain auto-generated files and directories that will be needed.
+ 3) Set up include pathes: You will need include/, arch/arm/src/lpc313x,
+ arch/arm/src/common, arch/arm/src/cortexm3, and sched/.
+ 4) All assembly files need to have the definition option -D __ASSEMBLY__
+ on the command line.
+
+ Startup files will probably cause you some headaches. The NuttX startup file
+ is arch/arm/src/lpc313x/lpc313x_vectors.S. With RIDE, I have to build NuttX
+ one time from the Cygwin command line in order to obtain the pre-built
+ startup object needed by RIDE.
+
+NuttX buildroot Toolchain
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+ A GNU GCC-based toolchain is assumed. The files */setenv.sh should
+ be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
+ different from the default in your PATH variable).
+
+ If you have no Cortex-M3 toolchain, one can be downloaded from the NuttX
+ SourceForge download site (https://sourceforge.net/project/showfiles.php?group_id=189573).
+ This GNU toolchain builds and executes in the Linux or Cygwin environment.
+
+ 1. You must have already configured Nuttx in <some-dir>/nuttx.
+
+ cd tools
+ ./configure.sh ea3131/<sub-dir>
+
+ 2. Download the latest buildroot package into <some-dir>
+
+ 3. unpack the buildroot tarball. The resulting directory may
+ have versioning information on it like buildroot-x.y.z. If so,
+ rename <some-dir>/buildroot-x.y.z to <some-dir>/buildroot.
+
+ 4. cd <some-dir>/buildroot
+
+ 5. cp configs/arm926t-defconfig-4.2.4 .config
+
+ 6. make oldconfig
+
+ 7. make
+
+ 8. Edit setenv.h, if necessary, so that the PATH variable includes
+ the path to the newly built binaries.
+
+ See the file configs/README.txt in the buildroot source tree. That has more
+ detailed PLUS some special instructions that you will need to follow if you are
+ building a Cortex-M3 toolchain for Cygwin under Windows.
+
+Boot Sequence
+^^^^^^^^^^^^^
+ LPC313x has on chip bootrom which loads properly formatted images from multiple
+ sources into SRAM. These sources include including SPI Flash, NOR Flash, UART,
+ USB, SD Card, and NAND Flash.
+
+ In all configurations, NuttX is loaded directly into ISRAM. NuttX is linked
+ to execute from ISRAM, regardless of the boot source.
+
+ARM/EA3131-specific Configuration Options
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ CONFIG_ARCH - Identifies the arch/ subdirectory. This should
+ be set to:
+
+ CONFIG_ARCH=arm
+
+ CONFIG_ARCH_family - For use in C code:
+
+ CONFIG_ARCH_ARM=y
+
+ CONFIG_ARCH_architecture - For use in C code:
+
+ CONFIG_ARCH_ARM926EJS=y
+
+ CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
+
+ CONFIG_ARCH_CHIP=lpc313x
+
+ CONFIG_ARCH_CHIP_name - For use in C code
+
+ CONFIG_ARCH_CHIP_LPC3131
+
+ CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ hence, the board that supports the particular chip or SoC.
+
+ CONFIG_ARCH_BOARD=ea3131
+
+ CONFIG_ARCH_BOARD_name - For use in C code
+
+ CONFIG_ARCH_BOARD_EA3131
+
+ CONFIG_ARCH_LOOPSPERMSEC - Must be calibrated for correct operation
+ of delay loops
+
+ CONFIG_ENDIAN_BIG - define if big endian (default is little
+ endian)
+
+ CONFIG_DRAM_SIZE - For most ARM9 architectures, this describes the
+ size of installed DRAM. For the LPC313X, it is used only to
+ deterimine how to map the executable regions. It is SDRAM size
+ only if you are executing out of the external SDRAM; or it could
+ be NOR FLASH size, external SRAM size, or internal SRAM size.
+
+ CONFIG_DRAM_START - The start address of installed DRAM (physical)
+
+ CONFIG_DRAM_VSTART - The startaddress of DRAM (virtual)
+
+ CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to boards that
+ have LEDs
+
+ CONFIG_ARCH_IRQPRIO - The LPC313x supports interrupt prioritization
+
+ CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt
+ stack. If defined, this symbol is the size of the interrupt
+ stack in bytes. If not defined, the user task stacks will be
+ used during interrupt handling.
+
+ CONFIG_ARCH_STACKDUMP - Do stack dumps after assertions
+
+ CONFIG_ARCH_BOOTLOADER - Set if you are using a bootloader.
+
+ CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to board architecture.
+
+ CONFIG_ARCH_BUTTONS - Enable support for buttons. Unique to board architecture.
+
+ CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that
+ cause a 100 second delay during boot-up. This 100 second delay
+ serves no purpose other than it allows you to calibratre
+ CONFIG_ARCH_LOOPSPERMSEC. You simply use a stop watch to measure
+ the 100 second delay then adjust CONFIG_ARCH_LOOPSPERMSEC until
+ the delay actually is 100 seconds.
+ CONFIG_ARCH_DMA - Support DMA initialization
+ CONFIG_ARCH_LOWVECTORS - define if vectors reside at address 0x0000:00000
+ Undefine if vectors reside at address 0xffff:0000
+ CONFIG_ARCH_ROMPGTABLE - A pre-initialized, read-only page table is available.
+ If defined, then board-specific logic must also define PGTABLE_BASE_PADDR,
+ PGTABLE_BASE_VADDR, and all memory section mapping in a file named
+ board_memorymap.h.
+
+ Individual subsystems can be enabled:
+
+ CONFIG_LPC313X_MCI, CONFIG_LPC313X_SPI, CONFIG_LPC313X_UART
+
+ xernal memory available on the board (see also CONFIG_MM_REGIONS)
+
+ CONFIG_LPC313X_EXTSRAM0 - Select if external SRAM0 is present
+ CONFIG_LPC313X_EXTSRAM0HEAP - Select if external SRAM0 should be
+ configured as part of the NuttX heap.
+ CONFIG_LPC313X_EXTSRAM0SIZE - Size (in bytes) of the installed
+ external SRAM0 memory
+ CONFIG_LPC313X_EXTSRAM1 - Select if external SRAM1 is present
+ CONFIG_LPC313X_EXTSRAM1HEAP - Select if external SRAM1 should be
+ configured as part of the NuttX heap.
+ CONFIG_LPC313X_EXTSRAM1SIZE - Size (in bytes) of the installed
+ external SRAM1 memory
+ CONFIG_LPC313X_EXTSDRAM - Select if external SDRAM is present
+ CONFIG_LPC313X_EXTSDRAMHEAP - Select if external SDRAM should be
+ configured as part of the NuttX heap.
+ CONFIG_LPC313X_EXTSDRAMSIZE - Size (in bytes) of the installed
+ external SDRAM memory
+ CONFIG_LPC313X_EXTNAND - Select if external NAND is present
+ CONFIG_LPC313X_EXTSDRAMSIZE - Size (in bytes) of the installed
+ external NAND memory
+
+ LPC313X specific device driver settings
+
+ CONFIG_UART_SERIAL_CONSOLE - selects the UART for the
+ console and ttys0
+ CONFIG_UART_RXBUFSIZE - Characters are buffered as received.
+ This specific the size of the receive buffer
+ CONFIG_UART_TXBUFSIZE - Characters are buffered before
+ being sent. This specific the size of the transmit buffer
+ CONFIG_UART_BAUD - The configure BAUD of the UART. Must be
+ CONFIG_UART_BITS - The number of bits. Must be either 7 or 8.
+ CONFIG_UART_PARTIY - 0=no parity, 1=odd parity, 2=even parity
+ CONFIG_UART_2STOP - Two stop bits
+
+Configurations
+^^^^^^^^^^^^^^
+
+Each EA3131 configuration is maintained in a sudirectory and can be
+selected as follow:
+
+ cd tools
+ ./configure.sh ea3131/<subdir>
+ cd -
+ . ./setenv.sh
+
+Where <subdir> is one of the following:
+
+ ostest:
+ This configuration directory, performs a simple OS test using
+ examples/ostest. By default, this project assumes that you are
+ using the DFU bootloader.
diff --git a/configs/ea3131/ostest/ld.script b/configs/ea3131/ostest/ld.script
index d98bffd95afb9afeaad29bf9476bedcfc41e3d4b..5eee3d3572b1f9e057e673103ada8470b9e175d2 100755
--- a/configs/ea3131/ostest/ld.script
+++ b/configs/ea3131/ostest/ld.script
@@ -33,14 +33,13 @@
*
****************************************************************************/
-/* The EA3131 has 512Kb of FLASH beginning at virtual address 0x0800:0000.
- * The LPC3131 has 192Kb of SRAM beginning at virtual address 0x1102:8000.
+/* The LPC3131 has 192Kb of ISRAM beginning at virtual address 0x1102:8000.
+ * All program segments are configured to execute from ISRAM.
*/
MEMORY
{
- flash (rx) : ORIGIN = 0x08000000, LENGTH = 512K
- sram (rwx) : ORIGIN = 0x11028000, LENGTH = 192K
+ isram (rwx) : ORIGIN = 0x11028000, LENGTH = 192K
}
OUTPUT_ARCH(arm)
@@ -61,7 +60,7 @@ SECTIONS
*(.gcc_except_table)
*(.gnu.linkonce.r.*)
_etext = ABSOLUTE(.);
- } > flash
+ } > isram
_eronly = ABSOLUTE(.);
@@ -71,17 +70,17 @@ SECTIONS
*(.gnu.linkonce.d.*)
CONSTRUCTORS
_edata = ABSOLUTE(.);
- } > sram AT > flash
+ } > isram AT > isram
.ARM.extab : {
*(.ARM.extab*)
- } >sram
+ } >isram
.ARM.exidx : {
__exidx_start = ABSOLUTE(.);
*(.ARM.exidx*)
__exidx_end = ABSOLUTE(.);
- } > sram
+ } > isram
.bss : {
_sbss = ABSOLUTE(.);
@@ -89,7 +88,7 @@ SECTIONS
*(.gnu.linkonce.b.*)
*(COMMON)
_ebss = ABSOLUTE(.);
- } > sram
+ } > isram
/* Stabs debugging sections. */
.stab 0 : { *(.stab) }
.stabstr 0 : { *(.stabstr) }