Add support to the LPC4330-Xplorer port for the Code Red toolchain

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4920 42af7a65-404d-4744-a932-0658087f49c3

configs/lpc4330-xplorer/README.txt

@@ -132,16 +132,18 @@ GNU Toolchain Options
   The NuttX make system has been modified to support the following different
   toolchain options.
 
-  1. The CodeSourcery GNU toolchain,
+  1. The Code Red GNU toolchain,
-  2. The Atollic Toolchain,
+  2. The CodeSourcery GNU toolchain,
-  3. The devkitARM GNU toolchain,
+  3. The Atollic Toolchain,
-  4. The NuttX buildroot Toolchain (see below).
+  4. The devkitARM GNU toolchain,
+  5. 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 or devkitARM toolchain, you simply need add one of the
   following configuration options to your .config (or defconfig) file:
 
+    CONFIG_LPC32_CODEREDW=y       : Code Red "RedSuite" under Windows
     CONFIG_LPC43_CODESOURCERYW=y  : CodeSourcery under Windows
     CONFIG_LPC43_CODESOURCERYL=y  : CodeSourcery under Linux
     CONFIG_LPC43_ATOLLIC_LITE=y   : The free, "Lite" version of Atollic toolchain under Windows
@@ -152,8 +154,8 @@ GNU Toolchain Options
   If you are not using CONFIG_LPC43_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), Atollic and devkitARM toolchains are
+  NOTE: the Code Red, CodeSourcery (for Windows), Atollic and devkitARM toolchains
-  Windows native toolchains.  The CodeSourcery (for Linux) and NuttX buildroot
+  are Windows native toolchains.  The CodeSourcery (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:
 
@@ -187,6 +189,7 @@ GNU Toolchain Options
      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
 
+
   The CodeSourcery Toolchain (2009q1)
   -----------------------------------
   The CodeSourcery toolchain (2009q1) does not work with default optimization
@@ -238,8 +241,7 @@ 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
+  effort will be required to create the project .
-  in the RIDE subdirectory).
   
   Makefile Build
   --------------
@@ -257,13 +259,31 @@ IDEs
   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/lpc17xx,
+  3) Set up include pathes:  You will need include/, arch/arm/src/lpc43xx,
      arch/arm/src/common, arch/arm/src/armv7-m, 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/lpc17x/lpc17_vectors.S.
+  is arch/arm/src/common/up_vectors.S.
+
+Code Red IDE
+^^^^^^^^^^^^
+
+  Command Line Flash Programming
+  ------------------------------
+
+  The GCC toolchain in LPCXpresso can be used from the command line.  The
+  GDB configuration details for command line use are on Code Red Wiki:
+
+    http://support.code-red-tech.com/CodeRedWiki/UsingGDB
+
+  The driver for the LPC18xx and LPC43xx is (in my installation path):
+
+    /cygdrive/c/code_red/RedSuite_4.2.3_379/redsuite/bin/crt_emu_lpc18_43_nxp.exe
+
+  The 128K free version only supports the LPC-Link and RedProbe debug probes.
+  Other JTAG interfaces are supported in the full version.
 
 NuttX buildroot Toolchain
 =========================
@@ -512,39 +532,44 @@ LPC4330-Xplorer Configuration Options
        the delay actually is 100 seconds.
 
     Individual subsystems can be enabled:
-      CONFIG_LPC43_MAINOSC=y
+
-      CONFIG_LPC43_PLL0=y
+      CONFIG_LPC43_ADC0=y
-      CONFIG_LPC43_PLL1=n
+      CONFIG_LPC43_ADC1=y
-      CONFIG_LPC43_ETHERNET=n
+      CONFIG_LPC43_ATIMER=y
-      CONFIG_LPC43_USBHOST=n
+      CONFIG_LPC43_CAN1=y
-      CONFIG_LPC43_USBOTG=n
+      CONFIG_LPC43_CAN2=y
-      CONFIG_LPC43_USBDEV=n
+      CONFIG_LPC43_DAC=y
+      CONFIG_LPC43_EMC=y
+      CONFIG_LPC43_ETHERNET=y
+      CONFIG_LPC43_EVNTMNTR=y
+      CONFIG_LPC43_GPDMA=y
+      CONFIG_LPC43_I2C0=y
+      CONFIG_LPC43_I2C1=y
+      CONFIG_LPC43_I2S0=y
+      CONFIG_LPC43_I2S1=y
+      CONFIG_LPC43_LCD=y
+      CONFIG_LPC43_MCPWM=y
+      CONFIG_LPC43_QEI=y
+      CONFIG_LPC43_RIT=y
+      CONFIG_LPC43_RTC=y
+      CONFIG_LPC43_SCT=y
+      CONFIG_LPC43_SDMMC=y
+      CONFIG_LPC43_SPI=y
+      CONFIG_LPC43_SPIFI=y
+      CONFIG_LPC43_SSP0=y
+      CONFIG_LPC43_SSP1=y
+      CONFIG_LPC43_TMR0=y
+      CONFIG_LPC43_TMR1=y
+      CONFIG_LPC43_TMR2=y
+      CONFIG_LPC43_TMR3=y
       CONFIG_LPC43_USART0=y
-      CONFIG_LPC43_UART1=n
+      CONFIG_LPC43_UART1=y
-      CONFIG_LPC43_USART2=n
+      CONFIG_LPC43_USART2=y
-      CONFIG_LPC43_USART3=n
+      CONFIG_LPC43_USART3=y
-      CONFIG_LPC43_CAN1=n
+      CONFIG_LPC43_USB0=y
-      CONFIG_LPC43_CAN2=n
+      CONFIG_LPC43_USB1=y
-      CONFIG_LPC43_SPI=n
+      CONFIG_LPC43_USB1_ULPI=y
-      CONFIG_LPC43_SSP0=n
+      CONFIG_LPC43_WWDT=y
-      CONFIG_LPC43_SSP1=n
-      CONFIG_LPC43_I2C0=n
-      CONFIG_LPC43_I2C1=n
-      CONFIG_LPC43_I2S=n
-      CONFIG_LPC43_TMR0=n
-      CONFIG_LPC43_TMR1=n
-      CONFIG_LPC43_TMR2=n
-      CONFIG_LPC43_TMR3=n
-      CONFIG_LPC43_RIT=n
-      CONFIG_LPC43_PWM=n
-      CONFIG_LPC43_MCPWM=n
-      CONFIG_LPC43_QEI=n
-      CONFIG_LPC43_RTC=n
-      CONFIG_LPC43_WDT=n
-      CONFIG_LPC43_ADC=n
-      CONFIG_LPC43_DAC=n
-      CONFIG_LPC43_GPDMA=n
-      CONFIG_LPC43_FLASH=n
 
   LPC43xx specific device driver settings
 

configs/lpc4330-xplorer/ostest/Make.defs

@@ -37,6 +37,17 @@ include ${TOPDIR}/.config
 
 # Setup for the selected toolchain
 
+ifeq ($(CONFIG_LPC32_CODEREDW),y)
+  # Code Red RedSuite under Windows
+  CROSSDEV = arm-none-eabi-
+  ARCROSSDEV = arm-none-eabi-
+  WINTOOL = y
+ifeq ($(CONFIG_ARCH_FPU),y)
+  ARCHCPUFLAGS = -mcpu=cortex-m4 -mthumb -march=armv7e-m -mfpu=fpv4-sp-d16 -mfloat-abi=hard
+else
+  ARCHCPUFLAGS = -mcpu=cortex-m3 -mthumb -mfloat-abi=soft
+endif
+endif
 ifeq ($(CONFIG_LPC43_CODESOURCERYW),y)
   # CodeSourcery under Windows
   CROSSDEV = arm-none-eabi-

configs/lpc4330-xplorer/ostest/defconfig

@@ -124,47 +124,59 @@ CONFIG_BOOT_CS3FLASH=n
 #
 # Identify toolchain and linker options
 #
-CONFIG_LPC43_CODESOURCERYW=y
+CONFIG_LPC32_CODEREDW=y
+CONFIG_LPC43_CODESOURCERYW=n
 CONFIG_LPC43_CODESOURCERYL=n
 CONFIG_LPC43_ATOLLIC_LITE=n
 CONFIG_LPC43_ATOLLIC_PRO=n
 CONFIG_LPC43_DEVKITARM=n
 CONFIG_LPC43_BUILDROOT=n
 
+CONFIG_ARCH_STDARG_H=y
+
 #
 #  Individual subsystems can be enabled:
 #
 # Individual subsystems can be enabled:
 # (MAINOSC, PLL0, PLL1 and FLASH are controlled in board.h)
-CONFIG_LPC43_ETHERNET=n
+#
-CONFIG_LPC43_USBHOST=n
+CONFIG_LPC43_ADC0=n
-CONFIG_LPC43_USBOTG=n
+CONFIG_LPC43_ADC1=n
-CONFIG_LPC43_USBDEV=n
+CONFIG_LPC43_ATIMER=n
-CONFIG_LPC43_USART0=y
-CONFIG_LPC43_UART1=n
-CONFIG_LPC43_USART2=n
-CONFIG_LPC43_USART3=n
 CONFIG_LPC43_CAN1=n
 CONFIG_LPC43_CAN2=n
-CONFIG_LPC43_SPI=n
+CONFIG_LPC43_DAC=n
-CONFIG_LPC43_SSP0=n
+CONFIG_LPC43_EMC=n
-CONFIG_LPC43_SSP1=n
+CONFIG_LPC43_ETHERNET=n
+CONFIG_LPC43_EVNTMNTR=n
+CONFIG_LPC43_GPDMA=n
 CONFIG_LPC43_I2C0=n
 CONFIG_LPC43_I2C1=n
-CONFIG_LPC43_I2S=n
+CONFIG_LPC43_I2S0=n
+CONFIG_LPC43_I2S1=n
+CONFIG_LPC43_LCD=n
+CONFIG_LPC43_MCPWM=n
+CONFIG_LPC43_QEI=n
+CONFIG_LPC43_RIT=n
+CONFIG_LPC43_RTC=n
+CONFIG_LPC43_SCT=n
+CONFIG_LPC43_SDMMC=n
+CONFIG_LPC43_SPI=n
+CONFIG_LPC43_SPIFI=n
+CONFIG_LPC43_SSP0=n
+CONFIG_LPC43_SSP1=n
 CONFIG_LPC43_TMR0=n
 CONFIG_LPC43_TMR1=n
 CONFIG_LPC43_TMR2=n
 CONFIG_LPC43_TMR3=n
-CONFIG_LPC43_RIT=n
+CONFIG_LPC43_USART0=y
-CONFIG_LPC43_PWM=n
+CONFIG_LPC43_UART1=n
-CONFIG_LPC43_MCPWM=n
+CONFIG_LPC43_USART2=n
-CONFIG_LPC43_QEI=n
+CONFIG_LPC43_USART3=n
-CONFIG_LPC43_RTC=n
+CONFIG_LPC43_USB0=n
-CONFIG_LPC43_WDT=n
+CONFIG_LPC43_USB1=n
-CONFIG_LPC43_ADC=n
+CONFIG_LPC43_USB1_ULPI=n
-CONFIG_LPC43_DAC=n
+CONFIG_LPC43_WWDT=n
-CONFIG_LPC43_GPDMA=n
 
 #
 # LPC43xx specific serial device driver settings
@@ -357,6 +369,8 @@ CONFIG_HAVE_LIBM=n
 CONFIG_DEBUG=n
 CONFIG_DEBUG_VERBOSE=n
 CONFIG_DEBUG_SYMBOLS=n
+CONFIG_DEBUG_SCHED=n
+
 CONFIG_MM_REGIONS=2
 CONFIG_ARCH_LOWPUTC=y
 CONFIG_RR_INTERVAL=200

configs/lpc4330-xplorer/ostest/setenv.sh

@@ -47,10 +47,16 @@ if [ -z "${PATH_ORIG}" ]; then
   export PATH_ORIG="${PATH}"
 fi
 
+# This is the Cygwin path to the location where I installed the Code Red
+# toolchain under windows.  You will have to edit this if you install the
+# Code Red toolchain in any other location or if you install a different
+# version
+export TOOLCHAIN_BIN="/cygdrive/c/code_red/RedSuite_4.2.3_379/redsuite/Tools/bin"
+
 # This the Cygwin path to the location where I installed the CodeSourcery
 # toolchain under windows.  You will also have to edit this if you install
 # the CodeSourcery toolchain in any other location
-export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/CodeSourcery/Sourcery G++ Lite/bin"
+#export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/CodeSourcery/Sourcery G++ Lite/bin"
 
 # These are the Cygwin paths to the locations where I installed the Atollic
 # toolchain under windows.  You will also have to edit this if you install