update toolchain info

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

4 files changed, 202 insertions, 23 deletions

diff --git a/nuttx/configs/avr32dev1/README.txt b/nuttx/configs/avr32dev1/README.txt
new file mode 100755
index 000000000..fa10f90aa
--- /dev/null
+++ b/nuttx/configs/avr32dev1/README.txt
@@ -0,0 +1,170 @@
+README

+^^^^^^

+

+This is the README file for the NuttX port to the Atmel AVR32DEV1 board.

+

+Contents

+^^^^^^^^

+

+ * Toolchains

+ * Development Environment

+ * GNU Toolchains

+

+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. Testing was performed using the Cygwin

+  environment.

+

+GNU Toolchains

+^^^^^^^^^^^^^^

+

+The build logic in these directories assume that you are using the GNU

+toolchain with the Atmel patches.  The patch file, pre-patched tool sources,

+and pre-built binaries are available from the Atmel website.

+

+  CONFIG_AVR32_AVRTOOLSW=y  # Use the windows version

+  CONFIG_AVR32_AVRTOOLSL=y  # Ue the Linux version

+

+NOTE: The NuttX builtroot cannot be used to build the AVR32 toolchain.

+This is because the Atmel patches that add support for the AVR32 are not

+included in the NuttX buildroot.

+

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

+  

+  Makefile Build

+  --------------

+  Under Eclipse, it is pretty easy to set up an "empty makefile project" and

+  simply use the NuttX makefile to build the system.  That is almost for free

+  under Linux.  Under Windows, you will need to set up the "Cygwin GCC" empty

+  makefile project in order to work with Windows (Google for "Eclipse Cygwin" -

+  there is a lot of help on the internet).

+

+  Native Build

+  ------------

+  Here are a few tips 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/lm3s,

+     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/lm3s/lm3s_vectors.S.

+

+AVR32DEV1 Configuration Options

+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

+

+	CONFIG_ARCH - Identifies the arch/ subdirectory.  This should

+	   be set to:

+

+	   CONFIG_ARCH=avr

+

+	CONFIG_ARCH_family - For use in C code:

+

+	   CONFIG_ARCH_AVR=y

+

+	CONFIG_ARCH_architecture - For use in C code:

+

+	   CONFIG_ARCH_AVR32=y

+

+	CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory

+

+	   CONFIG_ARCH_CHIP=at91uc3

+

+	CONFIG_ARCH_CHIP_name - For use in C code to identify the exact

+	   chip:

+

+	   CONFIG_ARCH_CHIP_AT91UC3B0256

+

+	CONFIG_ARCH_BOARD - Identifies the configs subdirectory and

+	   hence, the board that supports the particular chip or SoC.

+

+	   CONFIG_ARCH_BOARD=avr32dev1 (for the AV32DEV1 board)

+

+	CONFIG_ARCH_BOARD_name - For use in C code

+

+	   CONFIG_ARCH_BOARD_AVR32DEV1

+

+	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 - Describes the installed DRAM (SRAM in this case):

+

+	   CONFIG_DRAM_SIZE=0x00010000 (64Kb)

+

+	CONFIG_DRAM_START - The start address of installed DRAM

+

+	   CONFIG_DRAM_START=0x20000000

+

+	CONFIG_DRAM_END - Last address+1 of installed RAM

+

+	   CONFIG_DRAM_END=(CONFIG_DRAM_START+CONFIG_DRAM_SIZE)

+

+	CONFIG_ARCH_IRQPRIO - The AT91UC3B0256 supports interrupt prioritization

+

+	   CONFIG_ARCH_IRQPRIO=y

+

+	CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to boards that

+	   have LEDs

+

+	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_LEDS -  Use LEDs to show state. 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.

+

+  AT91UC3B0256 specific device driver settings

+

+	CONFIG_UARTn_SERIAL_CONSOLE - selects the UARTn for the

+	   console and ttys0 (default is the UART0).

+	CONFIG_UARTn_RXBUFSIZE - Characters are buffered as received.

+	   This specific the size of the receive buffer

+	CONFIG_UARTn_TXBUFSIZE - Characters are buffered before

+	   being sent.  This specific the size of the transmit buffer

+	CONFIG_UARTn_BAUD - The configure BAUD of the UART.  Must be

+	CONFIG_UARTn_BITS - The number of bits.  Must be either 7 or 8.

+	CONFIG_UARTn_PARTIY - 0=no parity, 1=odd parity, 2=even parity

+	CONFIG_UARTn_2STOP - Two stop bits

+

+Configurations

+^^^^^^^^^^^^^^

+

+Each Stellaris LM3S6965 Evaluation Kit configuration is maintained in a

+sudirectory and can be selected as follow:

+

+	cd tools

+	./configure.sh avr32dev1/<subdir>

+	cd -

+	. ./setenv.sh

+

+Where <subdir> is one of the following:

+

+  ostest:

+    This configuration directory, performs a simple OS test using

+    examples/ostest.

+

+

diff --git a/nuttx/configs/avr32dev1/ostest/Make.defs b/nuttx/configs/avr32dev1/ostest/Make.defs
index acbe503fb..e9f384ead 100755
--- a/nuttx/configs/avr32dev1/ostest/Make.defs
+++ b/nuttx/configs/avr32dev1/ostest/Make.defs
@@ -37,11 +37,16 @@ include ${TOPDIR}/.config
 
 # Setup for the selected toolchain
 
-ifeq ($(CONFIG_AVR32_CODESOURCERYW),y)
-  # CodeSourcery under Windows
-  CROSSDEV = avr32-elf-
+ifeq ($(CONFIG_AVR32_AVRTOOLSW),y)
+  # AVR Tools under Windows
+  CROSSDEV = avr32-
   WINTOOL = y
-  ARCHCPUFLAGS = 
+  ARCHCPUFLAGS = -march=uc -mpart=uc3b0256
+endif
+ifeq ($(CONFIG_AVR32_AVRTOOLSL),y)
+  # AVR Tools under Linux
+  CROSSDEV = avr32-
+  ARCHCPUFLAGS = -march=uc -mpart=uc3b0256
 endif
 
 ifeq ($(WINTOOL),y)
@@ -52,7 +57,6 @@ ifeq ($(WINTOOL),y)
   ARCHINCLUDES = -I. -isystem "${shell cygpath -w $(TOPDIR)/include}"
   ARCHXXINCLUDES = -I. -isystem "${shell cygpath -w $(TOPDIR)/include}" -isystem "${shell cygpath -w $(TOPDIR)/include/cxx}"
   ARCHSCRIPT = -T "${shell cygpath -w $(TOPDIR)/configs/$(CONFIG_ARCH_BOARD)/ostest/ld.script}"
-  MAXOPTIMIZATION = -O2
 else
   # Linux/Cygwin-native toolchain 
   MKDEP = $(TOPDIR)/tools/mkdeps.sh
@@ -76,34 +80,31 @@ ARCHCCMAJOR = ${shell echo $(ARCHCCVERSION) | cut -d'.' -f1}
 ifeq ("${CONFIG_DEBUG_SYMBOLS}","y")
   ARCHOPTIMIZATION = -g
 else
-  ARCHOPTIMIZATION = $(MAXOPTIMIZATION) -fno-strict-aliasing -fno-strength-reduce -fomit-frame-pointer
+  ARCHOPTIMIZATION = -Os -ffunction-sections -fdata-sections -fno-strict-aliasing
 endif
 
-ARCHCFLAGS = -fno-builtin
+ARCHCFLAGS = -fno-builtin -muse-rodata-section
 ARCHCXXFLAGS = -fno-builtin -fno-exceptions
 ARCHWARNINGS = -Wall -Wstrict-prototypes -Wshadow
 ARCHWARNINGSXX = -Wall -Wshadow
 ARCHDEFINES =
-ARCHPICFLAGS = -fpic -msingle-pic-base -mpic-register=r10
-
-CFLAGS = $(ARCHCFLAGS) $(ARCHWARNINGS) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHINCLUDES) $(ARCHDEFINES) -pipe
-CPICFLAGS = $(ARCHPICFLAGS) $(CFLAGS)
-CXXFLAGS = $(ARCHCXXFLAGS) $(ARCHWARNINGSXX) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHXXINCLUDES) $(ARCHDEFINES) -pipe
-CXXPICFLAGS = $(ARCHPICFLAGS) $(CXXFLAGS)
+ARCHNOPICFLAGS = -fno-pic
+ARCHPICFLAGS = -fpic
+ARCHALLCFLAGS = $(ARCHCFLAGS) $(ARCHWARNINGS) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHINCLUDES) $(ARCHDEFINES) -pipe
+ARCHALLCXXFLAGS = $(ARCHCXXFLAGS) $(ARCHWARNINGSXX) $(ARCHOPTIMIZATION) $(ARCHCPUFLAGS) $(ARCHXXINCLUDES) $(ARCHDEFINES) -pipe
+
+CFLAGS = $(ARCHNOPICFLAGS) $(ARCHALLCFLAGS)
+CPICFLAGS = $(ARCHPICFLAGS) $(ARCHALLCFLAGS)
+CXXFLAGS = $(ARCHNOPICFLAGS) $(ARCHALLCXXFLAGS)
+CXXPICFLAGS = $(ARCHPICFLAGS) $(ARCHALLCXXFLAGS)
 CPPFLAGS = $(ARCHINCLUDES) $(ARCHDEFINES)
-AFLAGS = $(CFLAGS) -D__ASSEMBLY__
-
-NXFLATLDFLAGS1 = -r -d -warn-common
-NXFLATLDFLAGS2 = $(NXFLATLDFLAGS1) -T$(TOPDIR)/binfmt/libnxflat/gnu-nxflat.ld -no-check-sections
-LDNXFLATFLAGS = -e main -s 2048
+AFLAGS = $(ARCHALLCFLAGS) -D__ASSEMBLY__
 
 OBJEXT = .o
 LIBEXT = .a
 EXEEXT =
 
-ifneq ($(CROSSDEV),avr32-elf-)
-  LDFLAGS += -nostartfiles -nodefaultlibs
-endif
+LDFLAGS += -nostartfiles -nodefaultlibs
 ifeq ($(CONFIG_DEBUG_SYMBOLS),y)
   LDFLAGS += -g
 endif
diff --git a/nuttx/configs/avr32dev1/ostest/defconfig b/nuttx/configs/avr32dev1/ostest/defconfig
index 4ffdae906..bf6fa61ff 100755
--- a/nuttx/configs/avr32dev1/ostest/defconfig
+++ b/nuttx/configs/avr32dev1/ostest/defconfig
@@ -93,6 +93,9 @@ CONFIG_ARCH_DMA=n
 # Identify toolchain and linker options
 #
 
+CONFIG_AVR32_AVRTOOLSW=y
+CONFIG_AVR32_AVRTOOLSL=n
+
 #
 #  Individual subsystems can be enabled:
 #
diff --git a/nuttx/configs/avr32dev1/ostest/setenv.sh b/nuttx/configs/avr32dev1/ostest/setenv.sh
index d691a05f7..079fe51cb 100755
--- a/nuttx/configs/avr32dev1/ostest/setenv.sh
+++ b/nuttx/configs/avr32dev1/ostest/setenv.sh
@@ -37,11 +37,16 @@ if [ "$(basename $0)" = "setenv.sh" ] ; then
   exit 1
 fi
 
+#
+# This PATH setup assumes that you are using versin 2.1.4 of the Atmel
+# AVR GNU tools installed at the default location on Windows.
+#
+
 if [ -z "${PATH_ORIG}" ]; then export PATH_ORIG="${PATH}"; fi
 
 WD=`pwd`
 
-export BUILDROOT_BIN="${WD}/../buildroot/build_arm_nofpu/staging_dir/bin"
-export PATH="${BUILDROOT_BIN}:/sbin:/usr/sbin:${PATH_ORIG}"
+export AVRTOOLS_BIN="/cygdrive/c/Program Files/Atmel/AVR Tools/AVR32 Toolchain/bin/"
+export PATH="${AVRTOOLS_BIN}:/sbin:/usr/sbin:${PATH_ORIG}"
 
 echo "PATH : ${PATH}"