Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-05-21 13:13:08 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

configs: Remove all setenv.bat files. Remove all references to setenv.sh and setenv.bat from all config README files.

Browse Source
This commit is contained in:
Gregory Nutt
2017-04-26 10:12:13 -06:00
parent 1620ff05f4
commit 9aac1dd44d
132 changed files with 581 additions and 1805 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configs/README.txt
+6 -15
View File
@@ -72,12 +72,10 @@ following characteristics:
| `-- (board-specific source files)
|-- <config1-dir>
| |-- Make.defs
| |-- defconfig
| `-- setenv.sh
| `-- defconfig
|-- <config2-dir>
| |-- Make.defs
| |-- defconfig
| `-- setenv.sh
| `-- defconfig
...
Summary of Files
@@ -101,10 +99,10 @@ src/Makefile -- This makefile will be invoked to build the board specific
and distclean.
A board may have various different configurations using these common source
files. Each board configuration is described by three files: Make.defs,
defconfig, and setenv.sh. Typically, each set of configuration files is
retained in a separate configuration sub-directory (<config1-dir>,
<config2-dir>, .. in the above diagram).
files. Each board configuration is described by two files: Make.defs and
defconfig. Typically, each set of configuration files is retained in a
separate configuration sub-directory (<config1-dir>, <config2-dir>, .. in
the above diagram).
Make.defs -- This makefile fragment provides architecture and
tool-specific build options. It will be included by all other
@@ -141,12 +139,6 @@ defconfig -- This is a configuration file similar to the Linux
(2) to generate include/nuttx/config.h which is included by
most C files in the system.
setenv.sh -- This is a script that you can include that will be installed at
the toplevel of the directory structure and can be sourced to set any
necessary environment variables. You will most likely have to customize the
default setenv.sh script in order for it to work correctly in your
environment.
Configuration Variables
^^^^^^^^^^^^^^^^^^^^^^^
@@ -816,7 +808,6 @@ Configuring NuttX
Configuring NuttX requires only copying
configs/<board-name>/<config-dir>/Make.def to ${TOPDIR}/Make.defs
configs/<board-name>/<config-dir>/setenv.sh to ${TOPDIR}/setenv.sh
configs/<board-name>/<config-dir>/defconfig to ${TOPDIR}/.config
tools/configure.sh
configs/amber/README.txt
+6 -8
View File
@@ -199,9 +199,8 @@ Buildroot:
http://bitbucket.org/nuttx/buildroot/downloads/. See the
following section for details on building this toolchain.
It is assumed in some places that buildroot toolchain is available
at ../buildroot/build_avr. Edit the setenv.sh file if
this is not the case.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
After configuring NuttX, make sure that CONFIG_AVR_BUILDROOT_TOOLCHAIN=y is set in your
.config file.
@@ -211,8 +210,8 @@ WinAVR:
For Cygwin development environment on Windows machines, you can use
WinAVR: http://sourceforge.net/projects/winavr/files/
It is assumed in some places that WinAVR is installed at C:/WinAVR. Edit the
setenv.sh file if this is not the case.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
After configuring NuttX, make sure that CONFIG_AVR_WINAVR_TOOLCHAIN=y is set in your
.config file.
@@ -297,8 +296,8 @@ NuttX buildroot Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
@@ -493,7 +492,6 @@ Common Configuration Notes
cd tools
./configure.sh amber/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/arduino-due/README.txt
+10 -15
View File
@@ -275,9 +275,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL=y : Generic GCC ARM EABI toolchain for Linux
CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIW=y : Generic GCC ARM EABI toolchain for Windows
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also
have to modify the PATH in the setenv.h file if your make cannot find the
tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE about Windows native toolchains
------------------------------------
@@ -348,7 +347,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -375,8 +374,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -437,8 +436,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
Buttons and LEDs
^^^^^^^^^^^^^^^^
@@ -849,11 +848,9 @@ Configurations
cd tools
./configure.sh arduino-due/<subdir>
cd -
. ./setenv.sh
Before sourcing the setenv.sh file above, you should examine it and perform
edits as necessary so that BUILDROOT_BIN is the correct path to the directory
than holds your toolchain binaries.
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.
And then build NuttX by simply typing the following. At the conclusion of
the make, the nuttx binary will reside in an ELF file called, simply, nuttx.
@@ -930,9 +927,7 @@ Configurations
Also, make sure that your PATH variable has the new path to your
Atmel tools. Try 'which arm-none-eabi-gcc' to make sure that you
are selecting the right tool. setenv.sh is available for you to
use to set or PATH variable. The path in the that file may not,
however, be correct for your installation.
are selecting the right tool.
See also the "NOTE about Windows native toolchains" in the section call
"GNU Toolchain Options" above.
configs/arduino-mega2560/README.txt
-1
View File
@@ -51,7 +51,6 @@ Configurations
cd tools
./configure.sh arduino-mega2560/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/avr32dev1/README.txt
+2 -5
View File
@@ -228,10 +228,8 @@ AVR32 Bootloader
driver in the FLIP usb directory. Then in the bin directory where
you installed FLIP, you will also find batchisp.exe.
NOTE: The AVR32DEV1 setenv.sh files will add the path to the BatchISP
bin directory to the Cygwin PATH variable. If you use a different
version of FLIP or if you install FLIP in a different location, you
will need to modify the setenv.sh files.
NOTE: You will need to set the PATH environment variable to include the
path to the BatchISP bin directory.
Notes from "AVR32 UC3 USB DFU Bootloader" (doc7745.pdf)
@@ -436,7 +434,6 @@ Common Configuration Notes
cd tools
./configure.sh avr32dev1/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/bambino-200e/README.txt
-1
View File
@@ -380,7 +380,6 @@ as follow:
cd tools
./configure.sh bambino-200e/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/c5471evm/README.txt
+3 -4
View File
@@ -4,7 +4,7 @@ README
Toolchain
^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the SH toolchain (if
different from the default).
@@ -28,8 +28,8 @@ Toolchain
7. make
8. Edit setenv.h so that the PATH variable includes the path to the
newly built binaries.
8. Make sure that the PATH variable includes the path to the newly built
binaries.
Issues
^^^^^^
@@ -133,7 +133,6 @@ Common Configuration Notes
cd tools
./configure.sh c5471evm/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/clicker2-stm32/README.txt
+2 -4
View File
@@ -163,11 +163,9 @@ Configurations
cd tools
./configure.sh clicker2-stm32/<subdir>
cd -
. ./setenv.sh
Before sourcing the setenv.sh file above, you should examine it and
perform edits as necessary so that TOOLCHAIN_BIN is the correct path
to the directory than holds your toolchain binaries.
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.
And then build NuttX by simply typing the following. At the conclusion of
the make, the nuttx binary will reside in an ELF file called, simply, nuttx.
configs/cloudctrl/README.txt
+7 -15
View File
@@ -202,8 +202,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_RAISONANCE=y : Raisonance RIDE7 under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you change the default toolchain, then you may also have to modify the PATH in
the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows), Atollic, devkitARM, and Raisonance toolchains are
Windows native toolchains. The CodeSourcery (for Linux) and NuttX buildroot
@@ -304,7 +304,7 @@ IDEs
NuttX EABI buildroot Toolchain
==============================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -340,14 +340,8 @@ NuttX EABI buildroot Toolchain
-CONFIG_ARMV7M_TOOLCHAIN_CODESOURCERYW=y
+CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y
9. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
-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"
-#export TOOLCHAIN_BIN="${WD}/../buildroot/build_arm_nofpu/staging_dir/bin"
+export TOOLCHAIN_BIN="${WD}/../buildroot/build_arm_nofpu/staging_dir/bin"
9. Set the the PATH variable so tht it 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
@@ -408,8 +402,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
LEDs
====
@@ -721,7 +715,6 @@ can be selected as follow:
cd tools
./configure.sh shenzhou/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
@@ -802,7 +795,6 @@ Where <subdir> is one of the following:
2. Make the build context (only)
$ cd ..
$ . ./setenv.sh
$ make context
...
configs/demo9s12ne64/README.txt
+3 -4
View File
@@ -110,7 +110,7 @@ Development Environment
NuttX Buildroot Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the HC12 GCC toolchain (if
different from the default in your PATH variable).
@@ -143,8 +143,8 @@ NuttX Buildroot Toolchain
directory manually. For example, binutils-2.18 can be found here:
http://ftp.gnu.org/gnu/binutils/
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
@@ -367,7 +367,6 @@ Common Configuration Notes
cd tools
./configure.sh demo9s12nec64/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/dk-tm4c129x/README.txt
+2 -4
View File
@@ -83,9 +83,8 @@ Using OpenOCD and GDB with ICDI
oocd.sh $PWD
The relative path to the oocd.sh script is configs/dk-tm4c129x/tools,
but that should have been added to your PATH variable when you sourced
the setenv.sh script.
Assuming that you have included the path to the oocd.sh script,
configs/dk-tm4c129x/tools, in PATH variable.
Note that OpenOCD needs to be run with administrator privileges in
some environments (sudo).
@@ -660,7 +659,6 @@ sub-directory and can be selected as follow:
cd tools
./configure.sh dk-tm4c129x/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/ea3131/README.txt
+7 -11
View File
@@ -50,8 +50,8 @@ GNU Toolchain Options
CONFIG_ARM_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
CONFIG_ARM_TOOLCHAIN_GNU_EABIL : Generic arm-none-eabi toolchain
If you are not using CONFIG_ARM_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
The toolchain may also be set using the kconfig-mconf utility (make menuconfig) or by
passing CONFIG_ARM_TOOLCHAIN=<toolchain> to make, where <toolchain> is one
@@ -140,7 +140,7 @@ IDEs
NuttX buildroot Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -167,8 +167,8 @@ NuttX buildroot Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
@@ -209,16 +209,13 @@ Image Format
- cd tools/ # Configure Nuttx
- ./configure.sh ea3131/nsh # (using the nsh configuration for this example)
- cd .. # Set up environment
- . ./setenv.sh # (see notes below)
- make # Make NuttX. This will produce nuttx.bin
- mklpc.sh # Make the bootloader binary (nuttx.lpc)
NOTES:
1. setenv.sh just sets up pathes to the toolchain and also to
configs/ea3131/tools where mklpc.sh resides. Use of setenv.sh is optional.
If you don't use setenv.sh, then just set your PATH variable appropriately or
use the full path to mklpc.sh in the final step.
1. You will need to set your PATH variable appropriately or use the full path
to mklpc.sh in the final step.
2. You can instruct Symantec to ignore the errors and it will stop quarantining
the NXP program.
3. The CRC32 logic in configs/ea3131/tools doesn't seem to work. As a result,
@@ -603,7 +600,6 @@ Common Configuration Notes
cd tools
./configure.sh ea3131/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/ea3152/README.txt
+7 -11
View File
@@ -49,8 +49,8 @@ GNU Toolchain Options
CONFIG_ARM_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
CONFIG_ARM_TOOLCHAIN_GNU_EABIL : Generic arm-none-eabi toolchain
If you are not using CONFIG_ARM_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
The toolchain may also be set using the kconfig-mconf utility (make menuconfig)
or by passing CONFIG_ARM_TOOLCHAIN=<toolchain> to make, where <toolchain> is one
@@ -139,7 +139,7 @@ IDEs
NuttX buildroot Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -166,8 +166,8 @@ NuttX buildroot Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
@@ -208,16 +208,13 @@ Image Format
- cd tools/ # Configure Nuttx
- ./configure.sh ea3152/ostest # (using the ostest configuration for this example)
- cd .. # Set up environment
- . ./setenv.sh # (see notes below)
- make # Make NuttX. This will produce nuttx.bin
- mklpc.sh # Make the bootloader binary (nuttx.lpc)
NOTES:
1. setenv.sh just sets up pathes to the toolchain and also to
configs/ea3152/tools where mklpc.sh resides. Use of setenv.sh is optional.
If you don't use setenv.sh, then just set your PATH variable appropriately or
use the full path to mklpc.sh in the final step.
1. You will need to set your PATH variable appropriately or use the full path
to mklpc.sh in the final step.
2. You can instruct Symantec to ignore the errors and it will stop quarantining
the NXP program.
3. The CRC32 logic in configs/ea3152/tools doesn't seem to work. As a result,
@@ -406,7 +403,6 @@ selected as follow:
cd tools
./configure.sh ea3152/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/eagle100/README.txt
+7 -8
View File
@@ -38,8 +38,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows) and devkitARM are Windows native toolchains.
The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux
@@ -74,7 +74,7 @@ GNU Toolchain Options
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -101,8 +101,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -155,8 +155,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
Ethernet-Bootloader
^^^^^^^^^^^^^^^^^^^
@@ -345,7 +345,6 @@ Common Configuration Notes
cd tools
./configure.sh eagle100/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/efm32-g8xx-stk/README.txt
-1
View File
@@ -234,7 +234,6 @@ CONFIGURATIONS
cd tools
./configure.sh efm32-g8xx-stk/<subdir>
cd -
. ./setenv.sh
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:
configs/efm32gg-stk3700/README.txt
+1 -1
View File
@@ -179,13 +179,13 @@ USING THE J-LINK GDB SERVER
Configurations
==============
Each EFM32 Giant Gecko Starter Kit configuration is maintained in a sub-
directory and can be selected as follow:
cd tools
./configure.sh efm32gg-stk3700/<subdir>
cd -
. ./setenv.sh
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:
configs/ekk-lm3s9b96/README.txt
+7 -8
View File
@@ -107,8 +107,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows) and devkitARM are Windows native toolchains.
The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux
@@ -178,7 +178,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -205,8 +205,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -267,8 +267,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
Stellaris EKK-LM3S9B96 Evaluation Kit Configuration Options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -397,7 +397,6 @@ sub-directory and can be selected as follow:
cd tools
./configure.sh ekk-lm3s9b96/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/esp32-core/README.txt
+2 -4
View File
@@ -585,11 +585,9 @@ Configurations
./configure.sh esp32-core/<subdir>
cd -
make oldconfig
. ./setenv.sh
Before sourcing the setenv.sh file above, you should examine it and
perform edits as necessary so that TOOLCHAIN_BIN is the correct path to
the directory than holds your toolchain binaries.
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:
configs/ez80f910200kitg/README.txt
+7 -8
View File
@@ -49,9 +49,9 @@ Version 5.1.1
Paths were also updated that are specific to a 32-bit toolchain running on
a 64 bit windows platform. Change to a different toolchain, you will need
to modify the versioning in Make.defs and setenv.sh; if you want to build
on a different platform, you will need to change the path in the ZDS binaries
in those same files.
to modify the versioning in Make.defs; if you want to build on a different
platform, you will need to change the path in the ZDS binaries in that files
and also in your PATH environment variable.
Version 5.2.1
@@ -63,8 +63,9 @@ Version 5.2.1
Other Versions
If you use any version of ZDS-II other than 5.1.1 or 5.2.1 or if you install
ZDS-II at any location other than the default location, you will have to
modify one or more of three files: (1) configs/ez80f910200kitg/*/setenv.sh,
(2) configs/ez80f910200kitg/*/Make.defs, and arch/z80/src/ez80/Toolchain.defs.
modify one or two files: (1) configs/ez80f910200kitg/*/Make.defs and
(2) arch/z80/src/ez80/Toolchain.defs. You probably have to modify the
path to your toolchain in the PATH environment variable.
Configuration Subdirectories
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -120,9 +121,7 @@ available:
will need to use the short 8.3 filenames to avoid spaces. On my
PC, C:\PROGRA~1\ is is C:\Program Files\ and C:\PROGRA~2\ is
C:\Program Files (x86)\
b. You can't use setenv.sh in the native Windows environment. Try
scripts/setenv.bat instead.
c. At present, the native Windows build fails at the final link stages.
b. At present, the native Windows build fails at the final link stages.
The failure is due to problems in arch/z80/src/nuttx.linkcmd that
is autogenerated by arch/z80/src/Makefile.zdsii. The basic problem
is the spurious spaces and and carrirage returns are generated at
configs/ez80f910200kitg/scripts/setenv.bat
-50
View File
@@ -1,50 +0,0 @@
@echo off
rem configs/ez80f810200kitg/scripts/setenv.bat
rem
rem Copyright (C) 2012 Gregory Nutt. All rights reserved.
rem Author: Gregory Nutt <gnutt@nuttx.org>
rem
rem Redistribution and use in source and binary forms, with or without
rem modification, are permitted provided that the following conditions
rem are met:
rem
rem 1. Redistributions of source code must retain the above copyright
rem notice, this list of conditions and the following disclaimer.
rem 2. Redistributions in binary form must reproduce the above copyright
rem notice, this list of conditions and the following disclaimer in
rem the documentation and/or other materials provided with the
rem distribution.
rem 3. Neither the name NuttX nor the names of its contributors may be
rem used to endorse or promote products derived from this software
rem without specific prior written permission.
rem
rem THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
rem "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
rem LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
rem FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
rem COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
rem INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
rem BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
rem OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
rem AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
rem LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
rem ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
rem POSSIBILITY OF SUCH DAMAGE.
rem This is the location where I installed in the MinGW compiler. With
rem this configuration, it is recommended that you do NOT install the
rem MSYS tools; they conflict with the GNUWin32 tools. See
rem http://www.mingw.org/ for further info.
set PATH=C:\MinGW\bin;%PATH%
rem This is the location where I installed the ZDS-II toolchain.
set PATH=C:\Program Files (x86)\ZiLOG\ZDSII_eZ80Acclaim!_5.1.1\bin;%PATH%
rem This is the location where I installed the GNUWin32 tools. See
rem http://gnuwin32.sourceforge.net/.
set PATH=C:\gnuwin32\bin;%PATH%
echo %PATH%
configs/ez80f910200zco/README.txt
+6 -5
View File
@@ -49,9 +49,9 @@ Version 5.1.1
Paths were also updated that are specific to a 32-bit toolchain running on
a 64 bit windows platform. Change to a different toolchain, you will need
to modify the versioning in Make.defs and setenv.sh; if you want to build
on a different platform, you will need to change the path in the ZDS binaries
in those same files.
to modify the versioning in Make.defs; if you want to build on a different
platform, you will need to change the path the the ZDS binaries in that
files as well as in your PATH environment variable.
Version 5.2.1
@@ -63,8 +63,9 @@ Version 5.2.1
Other Versions
If you use any version of ZDS-II other than 5.1.1 or 5.2.1 or if you install
ZDS-II at any location other than the default location, you will have to
modify one or more of three files: (1) configs/ez80f910200zco/*/setenv.sh,
(2) configs/ez80f910200zco/*/Make.defs, and arch/z80/src/ez80/Toolchain.defs.
modify one or two files: (2) configs/ez80f910200zco/*/Make.defs and (2)
arch/z80/src/ez80/Toolchain.defs. You may also have to modify you PATH
environment variable.
Configurations
^^^^^^^^^^^^^^
configs/ez80f910200zco/scripts/setenv.bat
-50
View File
@@ -1,50 +0,0 @@
@echo off
rem configs/ez80f910200zco/scripts/setenv.bat
rem
rem Copyright (C) 2012 Gregory Nutt. All rights reserved.
rem Author: Gregory Nutt <gnutt@nuttx.org>
rem
rem Redistribution and use in source and binary forms, with or without
rem modification, are permitted provided that the following conditions
rem are met:
rem
rem 1. Redistributions of source code must retain the above copyright
rem notice, this list of conditions and the following disclaimer.
rem 2. Redistributions in binary form must reproduce the above copyright
rem notice, this list of conditions and the following disclaimer in
rem the documentation and/or other materials provided with the
rem distribution.
rem 3. Neither the name NuttX nor the names of its contributors may be
rem used to endorse or promote products derived from this software
rem without specific prior written permission.
rem
rem THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
rem "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
rem LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
rem FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
rem COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
rem INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
rem BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
rem OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
rem AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
rem LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
rem ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
rem POSSIBILITY OF SUCH DAMAGE.
rem This is the location where I installed in the MinGW compiler. With
rem this configuration, it is recommended that you do NOT install the
rem MSYS tools; they conflict with the GNUWin32 tools. See
rem http://www.mingw.org/ for further info.
set PATH=C:\MinGW\bin;%PATH%
rem This is the location where I installed the ZDS-II toolchain.
set PATH=C:\Program Files (x86)\ZiLOG\ZDSII_eZ80Acclaim!_5.1.1\bin;%PATH%
rem This is the location where I installed the GNUWin32 tools. See
rem http://gnuwin32.sourceforge.net/.
set PATH=C:\gnuwin32\bin;%PATH%
echo %PATH%
configs/fire-stm32v2/README.txt
+7 -8
View File
@@ -194,8 +194,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_RAISONANCE=y : Raisonance RIDE7 under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you change the default toolchain, then you may also have to modify the PATH in
the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows), Atollic, devkitARM, and Raisonance toolchains are
Windows native toolchains. The CodeSourcery (for Linux) and NuttX buildroot
@@ -296,7 +296,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -323,8 +323,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -385,8 +385,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
DFU and JTAG
============
@@ -801,7 +801,6 @@ can be selected as follow:
cd tools
./configure.sh fire-stm32v2/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/freedom-k64f/README.txt
+2 -4
View File
@@ -626,9 +626,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may
also have to modify the PATH in the setenv.h file if your make cannot
find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: Using native Windows toolchains under Cygwin has some limitations.
This incuudes the CodeSourcery (for Windows) and devkitARM toolchains are
@@ -822,7 +821,6 @@ can be selected as follow:
cd tools
./configure.sh freedom-k64f/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/freedom-k66f/README.txt
+2 -4
View File
@@ -629,9 +629,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may
also have to modify the PATH in the setenv.h file if your make cannot
find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: Using native Windows toolchains under Cygwin has some limitations.
This incuudes the CodeSourcery (for Windows) and devkitARM toolchains are
@@ -829,7 +828,6 @@ can be selected as follow:
cd tools
./configure.sh freedom-K66F/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/freedom-kl25z/README.txt
+3 -4
View File
@@ -34,7 +34,7 @@ GNU Toolchain Options
NuttX Buildroot Toolchain
=========================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M0 GCC toolchain (if
different from the default in your PATH variable).
@@ -61,8 +61,8 @@ NuttX Buildroot Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -285,7 +285,6 @@ can be selected as follow:
cd tools
./configure.sh freedom-kl25z/<subdir>
cd -
. ./setenv.sh
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:
configs/freedom-kl26z/README.txt
+3 -4
View File
@@ -34,7 +34,7 @@ GNU Toolchain Options
NuttX Buildroot Toolchain
=========================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M0 GCC toolchain (if
different from the default in your PATH variable).
@@ -61,8 +61,8 @@ NuttX Buildroot Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -263,7 +263,6 @@ can be selected as follow:
cd tools
./configure.sh freedom-kl26z/<subdir>
cd -
. ./setenv.sh
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:
configs/hymini-stm32v/README.txt
+9 -11
View File
@@ -50,8 +50,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_RAISONANCE=y : Raisonance RIDE7 under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable 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
@@ -118,7 +118,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -145,8 +145,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -207,8 +207,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
ST Bootloader
=============
@@ -557,7 +557,6 @@ can be selected as follow:
cd tools
./configure.sh hymini-stm32v/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
@@ -594,9 +593,8 @@ Where <subdir> is one of the following:
apps/examples/nximage
=========== ======================= ================================
(1) You will probably need to modify nsh/setenv.sh or nsh2/setenv.sh
to set up the correct PATH variable for whichever toolchain you
may use.
(1) You will probably need to the PATH environment variable to set
up the correct PATH variable for whichever toolchain you may use.
(2) When any other device other than /dev/console is used for a user
interface, (1) linefeeds (\n) will not be expanded to carriage return
/ linefeeds \r\n). You will need to configure your terminal program
configs/kwikstik-k40/README.txt
+7 -8
View File
@@ -175,8 +175,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows) and devkitARM toolchains are
Windows native toolchains. The CodeSourcey (for Linux) and NuttX buildroot
@@ -241,7 +241,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M4 GCC toolchain (if
different from the default in your PATH variable).
@@ -270,8 +270,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -332,8 +332,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
KwikStik-K40-specific Configuration Options
============================================
@@ -507,7 +507,6 @@ can be selected as follow:
cd tools
./configure.sh kwikstik-k40/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/launchxl-tms57004/README.txt
+2 -4
View File
@@ -175,11 +175,9 @@ Configurations
cd tools
./configure.sh launchxl-tms57004/<subdir>
cd -
. ./setenv.sh
Before sourcing the setenv.sh file above, you should examine it and perform
edits as necessary so that TOOLCHAIN_BIN is the correct path to the directory
than holds your toolchain binaries.
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.
And then build NuttX by simply typing the following. At the conclusion of
the make, the nuttx binary will reside in an ELF file called, simply, nuttx.
configs/lincoln60/README.txt
+7 -8
View File
@@ -82,8 +82,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows)and devkitARM are Windows native toolchains.
The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or
@@ -148,7 +148,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -175,8 +175,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -237,8 +237,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
Lincoln 60 Configuration Options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -473,7 +473,6 @@ as follow:
cd tools
./configure.sh lincoln60/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lm3s6432-s2e/README.txt
+7 -8
View File
@@ -102,8 +102,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows) and devkitARM are Windows native toolchains.
The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux
@@ -168,7 +168,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -199,8 +199,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -261,8 +261,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
Stellaris MDL-S2E Reference Design Configuration Options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -400,7 +400,6 @@ sub-directory and can be selected as follow:
cd tools
./configure.sh lm3s6432-s2e/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lm3s6965-ek/README.txt
+7 -8
View File
@@ -211,8 +211,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows) and devkitARM are Windows native toolchains.
The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux
@@ -282,7 +282,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -309,8 +309,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -371,8 +371,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
USB Device Controller Functions
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -540,7 +540,6 @@ sub-directory and can be selected as follow:
cd tools
./configure.sh lm3s6965-ek/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lm3s8962-ek/README.txt
+7 -8
View File
@@ -131,8 +131,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows) and devkitARM are Windows native toolchains.
The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux
@@ -186,7 +186,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -213,8 +213,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -275,8 +275,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
USB Device Controller Functions
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -444,7 +444,6 @@ sub-directory and can be selected as follow:
cd tools
./configure.sh lm3s8962-ek/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lm4f120-launchpad/README.txt
+9 -11
View File
@@ -192,9 +192,8 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
oocd.sh $PWD
The relative path to the oocd.sh script is configs/lm4f120-launchpad/tools,
but that should have been added to your PATH variable when you sourced
the setenv.sh script.
provided that you have the path to the oocd.sh script, configs/lm4f120-launchpad/tools,
added to your PATH variable.
Note that OpenOCD needs to be run with administrator privileges in
some environments (sudo).
@@ -269,8 +268,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_OABI_TOOLCHAIN=y : If you use an older, OABI buildroot toolchain
If you change the default toolchain, then you may also have to modify the PATH in
the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows), Atollic, devkitARM, and Code Red (for Windows)
toolchains are Windows native toolchains. The CodeSourcey (for Linux) and NuttX
@@ -336,7 +335,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -363,8 +362,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -425,8 +424,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
LEDs
^^^^
@@ -671,7 +670,6 @@ sub-directory and can be selected as follow:
cd tools
./configure.sh lm4f120-launchpad/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lpc4330-xplorer/README.txt
+11 -12
View File
@@ -155,8 +155,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the Code Red, CodeSourcery (for Windows), Atollic and devkitARM toolchains
are Windows native toolchains. The CodeSourcery (for Linux) and NuttX buildroot
@@ -282,13 +282,13 @@ Code Red IDE/Tools
(The "free" RedSuite version has a download limit of 8K; the "free" LPCXpresso
version has a download limit of 128K).
NOTE that the following alias is defined in the setenv.sh file and
can be used to enter the boot mode with a simpler command:
NOTE that the following alias may be defined to enter the boot mode with a
simpler command:
alias lpc43xx='${SCRIPT_BIN}/Scripts/bootLPCXpresso.cmd winusb'
Be default, the setenv.sh scripts uses the LPCXpresso path shown above.
Once setenv.sh has been sources, then entering boot mode becomes simply:
You may also have to modify the PATH environment variable if your make cannot
find the tools.
$ lpc43xx
Booting LPC-Link with LPCXpressoWIN.enc
@@ -453,7 +453,7 @@ Code Red IDE/Tools
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -480,8 +480,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -542,8 +542,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
Serial Console
==============
@@ -867,7 +867,6 @@ as follow:
cd tools
./configure.sh lpc4330-xplorer/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lpc4337-ws/README.txt
+11 -12
View File
@@ -151,8 +151,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the Code Red, CodeSourcery (for Windows), Atollic and devkitARM toolchains
are Windows native toolchains. The CodeSourcery (for Linux) and NuttX buildroot
@@ -278,13 +278,13 @@ Code Red IDE/Tools
(The "free" RedSuite version has a download limit of 8K; the "free" LPCXpresso
version has a download limit of 128K).
NOTE that the following alias is defined in the setenv.sh file and
can be used to enter the boot mode with a simpler command:
NOTE that the following alias may be defined to enter the boot mode with a
simpler command:
alias lpc43xx='${SCRIPT_BIN}/Scripts/bootLPCXpresso.cmd winusb'
Be default, the setenv.sh scripts uses the LPCXpresso path shown above.
Once setenv.sh has been sources, then entering boot mode becomes simply:
You may also have to modify the PATH environment variable if your make cannot
find the tools.
$ lpc43xx
Booting LPC-Link with LPCXpressoWIN.enc
@@ -449,7 +449,7 @@ Code Red IDE/Tools
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -476,8 +476,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -538,8 +538,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
LED and Pushbuttons
===================
@@ -906,7 +906,6 @@ as follow:
cd tools
./configure.sh LPC4337-ws/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lpc4357-evb/README.txt
+11 -12
View File
@@ -148,8 +148,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the Code Red, CodeSourcery (for Windows), Atollic and devkitARM toolchains
are Windows native toolchains. The CodeSourcery (for Linux) and NuttX buildroot
@@ -275,13 +275,13 @@ Code Red IDE/Tools
(The "free" RedSuite version has a download limit of 8K; the "free" LPCXpresso
version has a download limit of 128K).
NOTE that the following alias is defined in the setenv.sh file and
can be used to enter the boot mode with a simpler command:
NOTE that the following alias may be defined to enter the boot mode with a
simpler command:
alias lpc43xx='${SCRIPT_BIN}/Scripts/bootLPCXpresso.cmd winusb'
Be default, the setenv.sh scripts uses the LPCXpresso path shown above.
Once setenv.sh has been sources, then entering boot mode becomes simply:
You may also have to modify the PATH environment variable if your make cannot
find the tools.
$ lpc43xx
Booting LPC-Link with LPCXpressoWIN.enc
@@ -446,7 +446,7 @@ Code Red IDE/Tools
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -473,8 +473,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -535,8 +535,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
LED and Pushbuttons
===================
@@ -903,7 +903,6 @@ as follow:
cd tools
./configure.sh lpc4357-evb/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lpc4370-link2/README.txt
+11 -12
View File
@@ -151,8 +151,8 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT, then you may also have to modify
the PATH in the setenv.h file if your make cannot find the tools.
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the Code Red, CodeSourcery (for Windows), Atollic and devkitARM toolchains
are Windows native toolchains. The CodeSourcery (for Linux) and NuttX buildroot
@@ -278,13 +278,13 @@ Code Red IDE/Tools
(The "free" RedSuite version has a download limit of 8K; the "free" LPCXpresso
version has a download limit of 128K).
NOTE that the following alias is defined in the setenv.sh file and
can be used to enter the boot mode with a simpler command:
NOTE that the following alias may be defined to enter the boot mode with a
simpler command:
alias lpc43xx='${SCRIPT_BIN}/Scripts/bootLPCXpresso.cmd winusb'
Be default, the setenv.sh scripts uses the LPCXpresso path shown above.
Once setenv.sh has been sources, then entering boot mode becomes simply:
You may also have to modify the PATH environment variable if your make cannot
find the tools.
$ lpc43xx
Booting LPC-Link with LPCXpressoWIN.enc
@@ -449,7 +449,7 @@ Code Red IDE/Tools
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -476,8 +476,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -538,8 +538,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
LED and Pushbuttons
===================
@@ -906,7 +906,6 @@ as follow:
cd tools
./configure.sh LPC4370-Link2/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lpcxpresso-lpc1115/README.txt
+6 -7
View File
@@ -91,7 +91,7 @@ GNU Toolchain Options
CONFIG_ARMV6M_TOOLCHAIN_CODEREDW=n : Code Red toolchain under Windows
CONFIG_ARMV6M_TOOLCHAIN_CODEREDL=y : Code Red toolchain under Linux
You may also have to modify the PATH in the setenv.h file if your make cannot
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows), devkitARM, and Code Red (for Windoes)
@@ -234,7 +234,7 @@ Code Red IDE
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -261,8 +261,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -323,8 +323,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
Using OpenOCD
^^^^^^^^^^^^^
@@ -676,7 +676,6 @@ selected as follow:
cd tools
./configure.sh lpcxpresso-lpc1115/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/lpcxpresso-lpc1768/README.txt
+6 -7
View File
@@ -258,7 +258,7 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_CODEREDW=n : Code Red toolchain under Windows
CONFIG_ARMV7M_TOOLCHAIN_CODEREDL=y : Code Red toolchain under Linux
You may also have to modify the PATH in the setenv.h file if your make cannot
You may also have to modify the PATH environment variable if your make cannot
find the tools.
NOTE: the CodeSourcery (for Windows), devkitARM, and Code Red (for Windoes)
@@ -398,7 +398,7 @@ Code Red IDE
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -425,8 +425,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -487,8 +487,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
LEDs
^^^^
@@ -728,7 +728,6 @@ selected as follow:
cd tools
./configure.sh lpcxpresso-lpc1768/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
configs/maple/README.txt
+2 -4
View File
@@ -111,11 +111,9 @@ Configurations
cd tools
./configure.sh maple/<subdir>
cd -
. ./setenv.sh
Before sourcing the setenv.sh file above, you should examine it and perform
edits as necessary so that TOOLCHAIN_BIN is the correct path to the directory
than holds your toolchain binaries.
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.
And then build NuttX by simply typing the following. At the conclusion of
the make, the nuttx binary will reside in an ELF file called, simply, nuttx.
configs/mbed/README.txt
+5 -9
View File
@@ -45,9 +45,6 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you are not using CONFIG_ARMV7M_TOOLCHAIN_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)and devkitARM 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
@@ -111,7 +108,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -138,8 +135,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you
@@ -200,8 +197,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
mbed Configuration Options
^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -446,7 +443,6 @@ Configurations
cd tools
./configure.sh mbed/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the mbed subdirectories described in the
following paragraph.
configs/mcu123-lpc214x/README.txt
+3 -4
View File
@@ -79,7 +79,7 @@ GNU Toolchain Options
NuttX buildroot Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -106,8 +106,8 @@ NuttX buildroot Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
@@ -320,7 +320,6 @@ Configurations
cd tools
./configure.sh mcu123-lpc214x/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/micropendous3/README.txt
+6 -8
View File
@@ -212,9 +212,8 @@ Buildroot:
http://bitbucket.org/nuttx/buildroot/downloads/. See the
following section for details on building this toolchain.
It is assumed in some places that buildroot toolchain is available
at ../buildroot/build_avr. Edit the setenv.sh file if
this is not the case.
Before building, make sure that the path to the new toolchain is included
in your PATH environment variable.
After configuring NuttX, make sure that CONFIG_AVR_BUILDROOT_TOOLCHAIN=y is set in your
.config file.
@@ -224,8 +223,8 @@ WinAVR:
For Cygwin development environment on Windows machines, you can use
WinAVR: http://sourceforge.net/projects/winavr/files/
It is assumed in some places that WinAVR is installed at C:/WinAVR. Edit the
setenv.sh file if this is not the case.
Before building, make sure that the path to the new toolchain is included
in your PATH environment variable.
After configuring NuttX, make sure that CONFIG_AVR_WINAVR_TOOLCHAIN=y is set in your
.config file.
@@ -310,8 +309,8 @@ NuttX buildroot Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
@@ -513,7 +512,6 @@ Common Configuration Notes
cd tools
./configure.sh micropendous3/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/mikroe-stm32f4/README.txt
+5 -9
View File
@@ -69,9 +69,6 @@ GNU Toolchain Options
CONFIG_ARMV7M_TOOLCHAIN_RAISONANCE=y : Raisonance RIDE7 under Windows
CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default)
If you change the default toolchain, 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, 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
@@ -176,7 +173,7 @@ IDEs
NuttX EABI "buildroot" Toolchain
================================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the Cortex-M3 GCC toolchain (if
different from the default in your PATH variable).
@@ -203,8 +200,8 @@ NuttX EABI "buildroot" Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly built binaries.
8. Make sure 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
details PLUS some special instructions that you will need to follow if you are
@@ -265,8 +262,8 @@ NXFLAT Toolchain
7. make
8. Edit setenv.h, if necessary, so that the PATH variable includes
the path to the newly builtNXFLAT binaries.
8. Make sure that the PATH variable includes the path to the newly built
NXFLAT binaries.
LEDs
====
@@ -716,7 +713,6 @@ can be selected as follow:
cd tools
./configure.sh mikroe-stm32f4/<subdir>
cd -
. ./setenv.sh
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:
configs/mirtoo/README.txt
+7 -8
View File
@@ -360,7 +360,7 @@ Toolchains
CONFIG_MIPS32_TOOLCHAIN_MICROCHIPOPENL - microchipOpen toolchain for Linux
And set the path appropriately in the setenv.sh file.
And set the path appropriately in the PATH environment variable.
Building MicrochipOpen (on Linux)
---------------------------------
@@ -399,8 +399,9 @@ Toolchains
CONFIG_MIPS32_TOOLCHAIN_PINGUINOW - Pinguino mips-elf toolchain for Windows
CONFIG_MIPS32_TOOLCHAIN_GNU_ELF - mips-elf toolchain for Linux or OS X
And set the path appropriately in the setenv.sh file. These tool configurations
are untested -- expect some additional integration issues. Good luck!
And set the path appropriately in the PATH environment variable. These tool
configurations are untested -- expect some additional integration issues.
Good luck!
This configuration will also work with any generic mips-elf GCC past version
4.6 or so.
@@ -488,8 +489,7 @@ Loading NuttX with ICD3
To use this file, you need to do the following things:
. ./setenv.sh # Source setenv.sh. Among other this, this script
# will add the NuttX tools/pic32mx directory to your
export PATH=??? # Add the NuttX tools/pic32mx directory to your
# PATH variable
make # Build nuttx and nuttx.hex
mkpichex $PWD # Convert addresses in nuttx.hex. $PWD is the path
@@ -844,7 +844,6 @@ selected as follow:
cd tools
./configure.sh mirtoo/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
@@ -882,8 +881,8 @@ Where <subdir> is one of the following:
To switch to the Linux C32 toolchain you will have to change (1) the
toolchain selection in .config (after configuration) and (2) the
path to the toolchain in setenv.sh. See notes above with regard to
the XC32 toolchain.
path to the toolchain in the PATH environment variable. See notes above
with regard to the XC32 toolchain.
4. PGA117 Support
configs/misoc/README.txt
+3 -5
View File
@@ -10,7 +10,7 @@ Misoc README
Buildroot Toolchain
===================
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the LM32 GCC toolchain (if
different from the default in your PATH variable).
@@ -48,10 +48,8 @@ Buildroot Toolchain
../buildroot/build_lm32/staging_dir/bin
The setenv.sh files in these sub-directories are already set to use
the relative path. It you choose to install the buildroot package
in some other location, you may need to edit the setenv.h file so
that the PATH variable includes the path to the newly built binaries.
Make sure that he 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
configs/moteino-mega/README.txt
-1
View File
@@ -251,7 +251,6 @@ Common Configuration Notes
cd tools
./configure.sh moteino-mega/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
configs/mx1ads/README.txt
+3 -4
View File
@@ -4,7 +4,7 @@ README
Toolchain
^^^^^^^^^
A GNU GCC-based toolchain is assumed. The files */setenv.sh should
A GNU GCC-based toolchain is assumed. The PATH environment variable should
be modified to point to the correct path to the ARM920T GCC toolchain (if
different from the default).
@@ -28,8 +28,8 @@ Toolchain
7. make
8. Edit setenv.h so that the PATH variable includes the path to the
newly built binaries.
8. Make sure that the PATH variable includes the path to the newly built
binaries.
Issues
^^^^^^
@@ -146,7 +146,6 @@ Common Configuration Notes
cd tools
./configure.sh imxads/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

Some files were not shown because too many files have changed in this diff Show More