diff --git a/configs/README.txt b/configs/README.txt index cbdb3d0072a..cfc90fa0f74 100644 --- a/configs/README.txt +++ b/configs/README.txt @@ -72,12 +72,10 @@ following characteristics: | `-- (board-specific source files) |-- | |-- Make.defs - | |-- defconfig - | `-- setenv.sh + | `-- defconfig |-- | |-- 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 (, -, .. 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 (, , .. 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///Make.def to ${TOPDIR}/Make.defs - configs///setenv.sh to ${TOPDIR}/setenv.sh configs///defconfig to ${TOPDIR}/.config tools/configure.sh diff --git a/configs/amber/README.txt b/configs/amber/README.txt index 752d4a840ac..d48090f237c 100644 --- a/configs/amber/README.txt +++ b/configs/amber/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/arduino-due/README.txt b/configs/arduino-due/README.txt index e886b558898..a5065b68051 100644 --- a/configs/arduino-due/README.txt +++ b/configs/arduino-due/README.txt @@ -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/ 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. diff --git a/configs/arduino-mega2560/README.txt b/configs/arduino-mega2560/README.txt index 7194f4e5a13..7663fdadbdc 100644 --- a/configs/arduino-mega2560/README.txt +++ b/configs/arduino-mega2560/README.txt @@ -51,7 +51,6 @@ Configurations cd tools ./configure.sh arduino-mega2560/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/avr32dev1/README.txt b/configs/avr32dev1/README.txt index 54ac9002708..8e6b639dec2 100644 --- a/configs/avr32dev1/README.txt +++ b/configs/avr32dev1/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/bambino-200e/README.txt b/configs/bambino-200e/README.txt index b6adcf8096c..d4105f0895f 100644 --- a/configs/bambino-200e/README.txt +++ b/configs/bambino-200e/README.txt @@ -380,7 +380,6 @@ as follow: cd tools ./configure.sh bambino-200e/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/c5471evm/README.txt b/configs/c5471evm/README.txt index 618b2ae1cec..36e6d7ce439 100644 --- a/configs/c5471evm/README.txt +++ b/configs/c5471evm/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/clicker2-stm32/README.txt b/configs/clicker2-stm32/README.txt index e265d475c0f..810072c99c6 100644 --- a/configs/clicker2-stm32/README.txt +++ b/configs/clicker2-stm32/README.txt @@ -163,11 +163,9 @@ Configurations cd tools ./configure.sh clicker2-stm32/ 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. diff --git a/configs/cloudctrl/README.txt b/configs/cloudctrl/README.txt index adce2658bae..ba2d8972ee9 100644 --- a/configs/cloudctrl/README.txt +++ b/configs/cloudctrl/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: @@ -802,7 +795,6 @@ Where is one of the following: 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... diff --git a/configs/demo9s12ne64/README.txt b/configs/demo9s12ne64/README.txt index 48080bed70f..b1b97145efd 100644 --- a/configs/demo9s12ne64/README.txt +++ b/configs/demo9s12ne64/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/dk-tm4c129x/README.txt b/configs/dk-tm4c129x/README.txt index bf81eb4f73b..291323da4ab 100644 --- a/configs/dk-tm4c129x/README.txt +++ b/configs/dk-tm4c129x/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/ea3131/README.txt b/configs/ea3131/README.txt index f69cb1fc519..0d966dafbc5 100644 --- a/configs/ea3131/README.txt +++ b/configs/ea3131/README.txt @@ -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= to make, where 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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/ea3152/README.txt b/configs/ea3152/README.txt index b9ada143ad3..1063a4292ac 100644 --- a/configs/ea3152/README.txt +++ b/configs/ea3152/README.txt @@ -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= to make, where 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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/eagle100/README.txt b/configs/eagle100/README.txt index 0b970355d75..f58ba90bb19 100644 --- a/configs/eagle100/README.txt +++ b/configs/eagle100/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/efm32-g8xx-stk/README.txt b/configs/efm32-g8xx-stk/README.txt index 3f569bcd81e..bd90ad93509 100644 --- a/configs/efm32-g8xx-stk/README.txt +++ b/configs/efm32-g8xx-stk/README.txt @@ -234,7 +234,6 @@ CONFIGURATIONS cd tools ./configure.sh efm32-g8xx-stk/ cd - - . ./setenv.sh If this is a Windows native build, then configure.bat should be used instead of configure.sh: diff --git a/configs/efm32gg-stk3700/README.txt b/configs/efm32gg-stk3700/README.txt index c554259255f..ec19a65f53f 100644 --- a/configs/efm32gg-stk3700/README.txt +++ b/configs/efm32gg-stk3700/README.txt @@ -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/ cd - - . ./setenv.sh If this is a Windows native build, then configure.bat should be used instead of configure.sh: diff --git a/configs/ekk-lm3s9b96/README.txt b/configs/ekk-lm3s9b96/README.txt index 977d3df9074..26ee59d69ea 100644 --- a/configs/ekk-lm3s9b96/README.txt +++ b/configs/ekk-lm3s9b96/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/esp32-core/README.txt b/configs/esp32-core/README.txt index 674fab89956..cde3295ff03 100644 --- a/configs/esp32-core/README.txt +++ b/configs/esp32-core/README.txt @@ -585,11 +585,9 @@ Configurations ./configure.sh esp32-core/ 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: diff --git a/configs/ez80f910200kitg/README.txt b/configs/ez80f910200kitg/README.txt index f72c8e8fd25..635992b5d3a 100644 --- a/configs/ez80f910200kitg/README.txt +++ b/configs/ez80f910200kitg/README.txt @@ -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 diff --git a/configs/ez80f910200kitg/scripts/setenv.bat b/configs/ez80f910200kitg/scripts/setenv.bat deleted file mode 100644 index 3a1b987b4d0..00000000000 --- a/configs/ez80f910200kitg/scripts/setenv.bat +++ /dev/null @@ -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 -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% diff --git a/configs/ez80f910200zco/README.txt b/configs/ez80f910200zco/README.txt index cf53682bcfa..d88114e8517 100644 --- a/configs/ez80f910200zco/README.txt +++ b/configs/ez80f910200zco/README.txt @@ -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 ^^^^^^^^^^^^^^ diff --git a/configs/ez80f910200zco/scripts/setenv.bat b/configs/ez80f910200zco/scripts/setenv.bat deleted file mode 100644 index 88fc6cbf312..00000000000 --- a/configs/ez80f910200zco/scripts/setenv.bat +++ /dev/null @@ -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 -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% diff --git a/configs/fire-stm32v2/README.txt b/configs/fire-stm32v2/README.txt index 3afb8126d3b..a422d00cf45 100644 --- a/configs/fire-stm32v2/README.txt +++ b/configs/fire-stm32v2/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/freedom-k64f/README.txt b/configs/freedom-k64f/README.txt index 20d41d5713a..cb04f040d41 100644 --- a/configs/freedom-k64f/README.txt +++ b/configs/freedom-k64f/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/freedom-k66f/README.txt b/configs/freedom-k66f/README.txt index 1dde7d71a6e..9d1d1b0ecb0 100644 --- a/configs/freedom-k66f/README.txt +++ b/configs/freedom-k66f/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/freedom-kl25z/README.txt b/configs/freedom-kl25z/README.txt index b5114b4d43c..d8b5da82a5b 100644 --- a/configs/freedom-kl25z/README.txt +++ b/configs/freedom-kl25z/README.txt @@ -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/ cd - - . ./setenv.sh If this is a Windows native build, then configure.bat should be used instead of configure.sh: diff --git a/configs/freedom-kl26z/README.txt b/configs/freedom-kl26z/README.txt index 6237f71ad9f..e23c202ac6f 100644 --- a/configs/freedom-kl26z/README.txt +++ b/configs/freedom-kl26z/README.txt @@ -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/ cd - - . ./setenv.sh If this is a Windows native build, then configure.bat should be used instead of configure.sh: diff --git a/configs/hymini-stm32v/README.txt b/configs/hymini-stm32v/README.txt index d477d6d8ee0..0ec19131129 100644 --- a/configs/hymini-stm32v/README.txt +++ b/configs/hymini-stm32v/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: @@ -594,9 +593,8 @@ Where 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 diff --git a/configs/kwikstik-k40/README.txt b/configs/kwikstik-k40/README.txt index 9586a43c90c..17c0d93526d 100644 --- a/configs/kwikstik-k40/README.txt +++ b/configs/kwikstik-k40/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/launchxl-tms57004/README.txt b/configs/launchxl-tms57004/README.txt index a229479fa8c..6c9568f913c 100644 --- a/configs/launchxl-tms57004/README.txt +++ b/configs/launchxl-tms57004/README.txt @@ -175,11 +175,9 @@ Configurations cd tools ./configure.sh launchxl-tms57004/ 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. diff --git a/configs/lincoln60/README.txt b/configs/lincoln60/README.txt index b5320549c01..4455198f7b3 100644 --- a/configs/lincoln60/README.txt +++ b/configs/lincoln60/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lm3s6432-s2e/README.txt b/configs/lm3s6432-s2e/README.txt index 5981dc790b7..51faa220499 100644 --- a/configs/lm3s6432-s2e/README.txt +++ b/configs/lm3s6432-s2e/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lm3s6965-ek/README.txt b/configs/lm3s6965-ek/README.txt index 3bec4c60755..02113d495bb 100644 --- a/configs/lm3s6965-ek/README.txt +++ b/configs/lm3s6965-ek/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lm3s8962-ek/README.txt b/configs/lm3s8962-ek/README.txt index 8c46c1db4ab..37d7c8b7440 100644 --- a/configs/lm3s8962-ek/README.txt +++ b/configs/lm3s8962-ek/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lm4f120-launchpad/README.txt b/configs/lm4f120-launchpad/README.txt index e90f68b16d8..432b8503a74 100644 --- a/configs/lm4f120-launchpad/README.txt +++ b/configs/lm4f120-launchpad/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lpc4330-xplorer/README.txt b/configs/lpc4330-xplorer/README.txt index 3afbe967ff0..c0be1084394 100644 --- a/configs/lpc4330-xplorer/README.txt +++ b/configs/lpc4330-xplorer/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lpc4337-ws/README.txt b/configs/lpc4337-ws/README.txt index a62558a8a08..d8ca540a69a 100644 --- a/configs/lpc4337-ws/README.txt +++ b/configs/lpc4337-ws/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lpc4357-evb/README.txt b/configs/lpc4357-evb/README.txt index c3febbec039..95955308cc6 100644 --- a/configs/lpc4357-evb/README.txt +++ b/configs/lpc4357-evb/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lpc4370-link2/README.txt b/configs/lpc4370-link2/README.txt index 9280b3258bd..d39515d7f06 100644 --- a/configs/lpc4370-link2/README.txt +++ b/configs/lpc4370-link2/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lpcxpresso-lpc1115/README.txt b/configs/lpcxpresso-lpc1115/README.txt index 168bed5198d..5b91b43a1fc 100644 --- a/configs/lpcxpresso-lpc1115/README.txt +++ b/configs/lpcxpresso-lpc1115/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/lpcxpresso-lpc1768/README.txt b/configs/lpcxpresso-lpc1768/README.txt index 36d5eead96f..534108b3099 100644 --- a/configs/lpcxpresso-lpc1768/README.txt +++ b/configs/lpcxpresso-lpc1768/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/maple/README.txt b/configs/maple/README.txt index b8d8a1fee93..076f7acb82f 100644 --- a/configs/maple/README.txt +++ b/configs/maple/README.txt @@ -111,11 +111,9 @@ Configurations cd tools ./configure.sh maple/ 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. diff --git a/configs/mbed/README.txt b/configs/mbed/README.txt index 40d99a661e0..c74cf4852fd 100644 --- a/configs/mbed/README.txt +++ b/configs/mbed/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the mbed subdirectories described in the following paragraph. diff --git a/configs/mcu123-lpc214x/README.txt b/configs/mcu123-lpc214x/README.txt index cae9bf9957e..de1780d8dcd 100644 --- a/configs/mcu123-lpc214x/README.txt +++ b/configs/mcu123-lpc214x/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/micropendous3/README.txt b/configs/micropendous3/README.txt index f270116f31b..b252ef207d4 100644 --- a/configs/micropendous3/README.txt +++ b/configs/micropendous3/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/mikroe-stm32f4/README.txt b/configs/mikroe-stm32f4/README.txt index 0348f0e18b7..54c4fd9ef57 100644 --- a/configs/mikroe-stm32f4/README.txt +++ b/configs/mikroe-stm32f4/README.txt @@ -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/ cd - - . ./setenv.sh If this is a Windows native build, then configure.bat should be used instead of configure.sh: diff --git a/configs/mirtoo/README.txt b/configs/mirtoo/README.txt index d97e6d198cc..29510b353a5 100644 --- a/configs/mirtoo/README.txt +++ b/configs/mirtoo/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the following: @@ -882,8 +881,8 @@ Where 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 diff --git a/configs/misoc/README.txt b/configs/misoc/README.txt index a241aba6b6a..b485dd1906c 100644 --- a/configs/misoc/README.txt +++ b/configs/misoc/README.txt @@ -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 diff --git a/configs/moteino-mega/README.txt b/configs/moteino-mega/README.txt index 9c3c03b1de9..71600becaa5 100644 --- a/configs/moteino-mega/README.txt +++ b/configs/moteino-mega/README.txt @@ -251,7 +251,6 @@ Common Configuration Notes cd tools ./configure.sh moteino-mega/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/mx1ads/README.txt b/configs/mx1ads/README.txt index f9133a8a6b8..283127e5800 100644 --- a/configs/mx1ads/README.txt +++ b/configs/mx1ads/README.txt @@ -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/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/ne64badge/README.txt b/configs/ne64badge/README.txt index 5eb2bc7d820..3f532cb7e3e 100644 --- a/configs/ne64badge/README.txt +++ b/configs/ne64badge/README.txt @@ -217,7 +217,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). @@ -250,8 +250,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 @@ -474,7 +474,6 @@ Common Configuration Notes cd tools ./configure.sh ne64badge/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/nr5m100-nexys4/README.txt b/configs/nr5m100-nexys4/README.txt index fc939aa4c60..88c488de683 100644 --- a/configs/nr5m100-nexys4/README.txt +++ b/configs/nr5m100-nexys4/README.txt @@ -235,12 +235,6 @@ can be selected as follow: cd tools ./configure.sh nr5m100-nexys4/ cd - - . ./setenv.sh - -If this is a Windows native build, then configure.bat should be used -instead of configure.sh: - - configure.bat nr5m100-nexys4\ Where is one of the following: diff --git a/configs/ntosd-dm320/README.txt b/configs/ntosd-dm320/README.txt index 3377ffdb78d..1d0a66305f5 100644 --- a/configs/ntosd-dm320/README.txt +++ b/configs/ntosd-dm320/README.txt @@ -67,12 +67,9 @@ GNU Toolchain Options CONFIG_ARM_TOOLCHAIN_CODESOURCERYW=y : CodeSourcery under Windows CONFIG_ARM_TOOLCHAIN_CODESOURCERYL=y : CodeSourcery under Linux CONFIG_ARM_TOOLCHAIN_DEVKITARM=y : devkitARM under Windows - CONFIG_ARM_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default) + 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. - The toolchain may also be set using the kconfig-mconf utility (make menuconfig) or by passing CONFIG_ARM_TOOLCHAIN= to make, where is one of CODESOURCERYW, CODESOURCERYL, DEVKITARM, BUILDROOT or GNU_EABI as described @@ -160,7 +157,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 ARM926 GCC toolchain (if different from the default). @@ -185,93 +182,93 @@ NuttX buildroot 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. ARM/DM320-specific Configuration Options ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - CONFIG_ARCH - Identifies the arch/ subdirectory. This should - be set to: + CONFIG_ARCH - Identifies the arch/ subdirectory. This should + be set to: - CONFIG_ARCH=arm + CONFIG_ARCH=arm - CONFIG_ARCH_family - For use in C code: + CONFIG_ARCH_family - For use in C code: - CONFIG_ARCH_ARM=y + CONFIG_ARCH_ARM=y - CONFIG_ARCH_architecture - For use in C code: + CONFIG_ARCH_architecture - For use in C code: - CONFIG_ARCH_ARM926EJS=y + CONFIG_ARCH_ARM926EJS=y - CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory + CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory - CONFIG_ARCH_CHIP=dm320 + CONFIG_ARCH_CHIP=dm320 - CONFIG_ARCH_CHIP_name - For use in C code + CONFIG_ARCH_CHIP_name - For use in C code - CONFIG_ARCH_CHIP_DM320 + CONFIG_ARCH_CHIP_DM320 - CONFIG_ARCH_BOARD - Identifies the configs subdirectory and - hence, the board that supports the particular chip or SoC. + CONFIG_ARCH_BOARD - Identifies the configs subdirectory and + hence, the board that supports the particular chip or SoC. - CONFIG_ARCH_BOARD=ntosd-dm320 + CONFIG_ARCH_BOARD=ntosd-dm320 - CONFIG_ARCH_BOARD_name - For use in C code + CONFIG_ARCH_BOARD_name - For use in C code - CONFIG_ARCH_BOARD_NTOSD_DM320 (for the Spectrum Digital C5471 EVM) + CONFIG_ARCH_BOARD_NTOSD_DM320 (for the Spectrum Digital C5471 EVM) - CONFIG_ARCH_LOOPSPERMSEC - Must be calibrated for correct operation - of delay loops + CONFIG_ARCH_LOOPSPERMSEC - Must be calibrated for correct operation + of delay loops - CONFIG_ENDIAN_BIG - define if big endian (default is little - endian) + CONFIG_ENDIAN_BIG - define if big endian (default is little + endian) - CONFIG_RAM_SIZE - Describes the installed DRAM. + CONFIG_RAM_SIZE - Describes the installed DRAM. - CONFIG_RAM_START - The start address of installed DRAM + CONFIG_RAM_START - The start address of installed DRAM - CONFIG_RAM_VSTART - The startaddress of DRAM (virtual) + CONFIG_RAM_VSTART - The startaddress of DRAM (virtual) - CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to boards that - have LEDs + 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_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_STACKDUMP - Do stack dumps after assertions - CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that - cause a 100 second delay during boot-up. This 100 second delay - serves no purpose other than it allows you to calibratre - CONFIG_ARCH_LOOPSPERMSEC. You simply use a stop watch to measure - the 100 second delay then adjust CONFIG_ARCH_LOOPSPERMSEC until - the delay actually is 100 seconds. + CONFIG_ARCH_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. DM320 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 + 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 DM320 USB Configuration - CONFIG_DM320_GIO_USBATTACH - GIO that detects USB attach/detach events - CONFIG_DM320_GIO_USBDPPULLUP - GIO - CONFIG_DMA320_USBDEV_DMA - Enable DM320-specific DMA support - CONFIG_DM320_GIO_USBATTACH=6 + CONFIG_DM320_GIO_USBATTACH + GIO that detects USB attach/detach events + CONFIG_DM320_GIO_USBDPPULLUP + GIO + CONFIG_DMA320_USBDEV_DMA + Enable DM320-specific DMA support + CONFIG_DM320_GIO_USBATTACH=6 Configurations ^^^^^^^^^^^^^^ @@ -285,7 +282,6 @@ Common Configuration Notes cd tools ./configure.sh ntosd-dm320/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/ntosd-dm320/doc/README.txt b/configs/ntosd-dm320/doc/README.txt index 758870b9caa..e3c24ea4a6b 100644 --- a/configs/ntosd-dm320/doc/README.txt +++ b/configs/ntosd-dm320/doc/README.txt @@ -50,10 +50,12 @@ General instructions. 6. Build Nuttx: cd nuttx - . ./setenv.sh make mv nuttx /tftpboot/nuttx.dm320 + You may also have to modify the PATH environment variable if your make cannot + find the tools. + 7. Configure the OSD u-boot: Neuros Devboard > set ipaddr yy.yy.yy.yy diff --git a/configs/nucleo-144/README.txt b/configs/nucleo-144/README.txt index 6226299546a..cb6d65692f0 100644 --- a/configs/nucleo-144/README.txt +++ b/configs/nucleo-144/README.txt @@ -193,7 +193,7 @@ IDEs Basic configuration & build steps ================================== - 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-M7 GCC toolchain (if different from the default in your PATH variable). diff --git a/configs/nucleo-f072rb/README.txt b/configs/nucleo-f072rb/README.txt index 118d24d9afb..3f4eecaabfb 100644 --- a/configs/nucleo-f072rb/README.txt +++ b/configs/nucleo-f072rb/README.txt @@ -198,11 +198,9 @@ Configurations cd tools ./configure.sh nucleo-f072rb/ 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. diff --git a/configs/nucleo-f4x1re/README.txt b/configs/nucleo-f4x1re/README.txt index 9ea6be28ab9..f22b3c6e19b 100644 --- a/configs/nucleo-f4x1re/README.txt +++ b/configs/nucleo-f4x1re/README.txt @@ -250,7 +250,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). diff --git a/configs/nucleo-l476rg/README.txt b/configs/nucleo-l476rg/README.txt index 72ab182d872..497035e4a84 100644 --- a/configs/nucleo-l476rg/README.txt +++ b/configs/nucleo-l476rg/README.txt @@ -232,7 +232,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). diff --git a/configs/nutiny-nuc120/README.txt b/configs/nutiny-nuc120/README.txt index c6f747d1674..90fabba39c2 100644 --- a/configs/nutiny-nuc120/README.txt +++ b/configs/nutiny-nuc120/README.txt @@ -35,7 +35,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). @@ -62,8 +62,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 @@ -271,12 +271,6 @@ can be selected as follow: cd tools ./configure.sh nutiny-nuc120/ cd - - . ./setenv.sh - -If this is a Windows native build, then configure.bat should be used -instead of configure.sh: - - configure.bat nutiny-nuc120\ Where is one of the following: diff --git a/configs/olimex-efm32g880f128-stk/README.txt b/configs/olimex-efm32g880f128-stk/README.txt index 9309a039768..6256fb82999 100644 --- a/configs/olimex-efm32g880f128-stk/README.txt +++ b/configs/olimex-efm32g880f128-stk/README.txt @@ -137,12 +137,6 @@ Configurations cd tools ./configure.sh olimex-efm32g880f128-stk/ cd - - . ./setenv.sh - - If this is a Windows native build, then configure.bat should be used - instead of configure.sh: - - configure.bat olimex-efm32g880f128-stk\ Where is one of the following: diff --git a/configs/olimex-lpc-h3131/README.txt b/configs/olimex-lpc-h3131/README.txt index f262ff93c79..e9f54bf84f6 100644 --- a/configs/olimex-lpc-h3131/README.txt +++ b/configs/olimex-lpc-h3131/README.txt @@ -55,9 +55,6 @@ GNU Toolchain Options CONFIG_ARM_TOOLCHAIN_GNU_EABIL : Generic arm-none-eabi toolchain for Linux CONFIG_ARM_TOOLCHAIN_GNU_EABIW : Generic arm-none-eabi toolchain for Windows - 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. - The toolchain may also be set using the kconfig-mconf utility (make menuconfig) or by passing CONFIG_ARM_TOOLCHAIN= to make, where is one of CODESOURCERYW, CODESOURCERYL, DEVKITARM, BUILDROOT or GNU_EABI as described @@ -145,7 +142,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). @@ -172,8 +169,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 @@ -260,17 +257,13 @@ Image Format - cd tools/ # Configure Nuttx - ./configure.sh olimex-lpc-h3131/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/olimex-lpc-h3131/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. Make sure 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/olimex-lpc-h3131/tools doesn't seem to @@ -504,11 +497,9 @@ Configurations cd tools ./configure.sh olimex-lpc-h3131/ 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. @@ -548,10 +539,6 @@ Configurations System Type -> Toolchain: CONFIG_ARM_TOOLCHAIN_GNU_EABIW=y : GNU EABI toolchain for windows - The setenv.sh file is available for you to use to set the PATH - variable. The path in the that file may not, however, be correct - for your installation. - Configuration sub-directories ----------------------------- diff --git a/configs/olimex-lpc1766stk/README.txt b/configs/olimex-lpc1766stk/README.txt index 1a96d8582a4..bf1d32b4f21 100644 --- a/configs/olimex-lpc1766stk/README.txt +++ b/configs/olimex-lpc1766stk/README.txt @@ -191,9 +191,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 @@ -257,7 +254,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). @@ -284,8 +281,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 @@ -346,8 +343,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 ^^^^ @@ -578,9 +575,8 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator configs/olimex-lpc1766stk/tools/oocd.sh $PWD - If you use the setenv.sh file, that the path to oocd.sh will be added - to your PATH environment variabl. So, in that case, the command simplifies - to just: + If you add the path to oocd.sh to your PATH environment variable, + the command simplifies to just: oocd.sh $PWD @@ -869,7 +865,6 @@ Common Configuration Notes cd tools ./configure.sh olimex-lpc1766stk/ cd - - . ./setenv.sh Where is one of the sub-directories identified in the following paragraphs. diff --git a/configs/olimex-stm32-p407/README.txt b/configs/olimex-stm32-p407/README.txt index 0302020f0b6..0692ffc5023 100644 --- a/configs/olimex-stm32-p407/README.txt +++ b/configs/olimex-stm32-p407/README.txt @@ -241,14 +241,12 @@ selected as follow: cd tools ./configure.sh olimex-stm32-p407/ cd - - . ./setenv.sh Where is one of the configuration sub-directories listed in the following section. -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. diff --git a/configs/olimex-strp711/README.txt b/configs/olimex-strp711/README.txt index f6034571934..572c2c6d04b 100644 --- a/configs/olimex-strp711/README.txt +++ b/configs/olimex-strp711/README.txt @@ -164,7 +164,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 ARM toolchain (if different from the default). @@ -190,8 +190,8 @@ NuttX buildroot 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. Linux OpenOCD with Wiggler JTAG ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -275,9 +275,8 @@ Windows OpenOCD will Olimex JTAG - If you are working under Linux you will need to change any occurances of `cygpath -w blablabla` to just blablabla - The setenv.sh file includes some environment varialble settings - that are needed by oocd.sh. If you have $PATH and other environment - variables set up, then you should be able to start the OpenOCD daemon like: + If you have $PATH and other environment variables set up, then you should + be able to start the OpenOCD daemon like: oocd.sh @@ -375,7 +374,6 @@ Common Configuration Notes: cd tools ./configure.sh olimex-strp711/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/olimex-strp711/scripts/oocd.sh b/configs/olimex-strp711/scripts/oocd.sh index 33924c93d16..845f9da3707 100755 --- a/configs/olimex-strp711/scripts/oocd.sh +++ b/configs/olimex-strp711/scripts/oocd.sh @@ -19,7 +19,6 @@ fi if [ -z $STR41XSCRIPTS ]; then echo "Environment variable $STR41XSCRIPTS is not defined" echo "Has NuttX been configured?" - echo "If so, try sourcing the setenv.sh script in the top-level directory" exit 1 fi diff --git a/configs/open1788/README.txt b/configs/open1788/README.txt index b8604d6346a..5dfd0d98f08 100644 --- a/configs/open1788/README.txt +++ b/configs/open1788/README.txt @@ -164,14 +164,13 @@ Using OpenOCD with the Olimex ARM-USB-OCD Starting OpenOCD Then you should be able to start the OpenOCD daemon as follows. This - assumes that you have already CD'ed to the NuttX build directory: + assumes that you have already CD'ed to the NuttX build directory and + that you have set the full path to the onfigs/open1788/tools in your + PATH environment variable: - . ./setenv.sh oocd.sh $PWD - The setenv.sh script is a convenience script that you may choose to - use or not. It simply sets up the PATH variable so that you can - automatically find oocd.sh. You could also do: + or, if the PATH variable is not so configured: configs/open1788/tools/oocd.sh $PWD diff --git a/configs/p112/ostest/setenv.bat b/configs/p112/ostest/setenv.bat deleted file mode 100644 index 01eb774dd56..00000000000 --- a/configs/p112/ostest/setenv.bat +++ /dev/null @@ -1,51 +0,0 @@ -@echo off - -rem configs/p112/ostest/setenv.bat -rem -rem Copyright (C) 2012, 2014 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -rem set PATH=C:\Program Files (x86)\SDCC/bin;%PATH% -set PATH=C:\Program Files\SDCC/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% diff --git a/configs/p112/scripts/setenv.bat b/configs/p112/scripts/setenv.bat deleted file mode 100644 index dc214445f18..00000000000 --- a/configs/p112/scripts/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/p112/scripts/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% diff --git a/configs/pcblogic-pic32mx/README.txt b/configs/pcblogic-pic32mx/README.txt index c98882584b8..777b5b9eaae 100644 --- a/configs/pcblogic-pic32mx/README.txt +++ b/configs/pcblogic-pic32mx/README.txt @@ -316,8 +316,7 @@ Loading NuttX with PICkit2 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 @@ -554,7 +553,6 @@ Configurations cd tools ./configure.sh pcblogic-pic32mx/ cd - - . ./setenv.sh Where is one of the following sub-directories. diff --git a/configs/pcduino-a10/README.txt b/configs/pcduino-a10/README.txt index b3c26c6267a..6a68047dfdb 100644 --- a/configs/pcduino-a10/README.txt +++ b/configs/pcduino-a10/README.txt @@ -329,11 +329,9 @@ Configurations cd tools ./configure.sh pcduino-a10/ 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. @@ -369,11 +367,6 @@ Configurations System Type -> Toolchain: CONFIG_ARMV7A_TOOLCHAIN_CODESOURCERYW=y : CodeSourcery for Windows - The setenv.sh file is available for you to use to set the PATH - variable. The path in the that file may not, however, be correct - for your installation. Try 'which arm-none-eabi-gcc' to make sure that - you are selecting the right tool. - Configuration Sub-directories ----------------------------- diff --git a/configs/pic32mx-starterkit/README.txt b/configs/pic32mx-starterkit/README.txt index 6a9d766607c..8f5bd3cdfa8 100644 --- a/configs/pic32mx-starterkit/README.txt +++ b/configs/pic32mx-starterkit/README.txt @@ -566,8 +566,7 @@ Creating Compatible NuttX HEX files 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 @@ -1019,7 +1018,6 @@ selected as follow: cd tools ./configure.sh pic32mx-starterkit/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/pic32mx7mmb/README.txt b/configs/pic32mx7mmb/README.txt index 9167670fdb3..b3b5d7400d8 100644 --- a/configs/pic32mx7mmb/README.txt +++ b/configs/pic32mx7mmb/README.txt @@ -301,8 +301,7 @@ Creating Compatible NuttX HEX files 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 @@ -597,7 +596,6 @@ selected as follow: cd tools ./configure.sh pic32mx7mmb/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/pic32mz-starterkit/README.txt b/configs/pic32mz-starterkit/README.txt index 4166a4728f6..567bcde739e 100644 --- a/configs/pic32mz-starterkit/README.txt +++ b/configs/pic32mz-starterkit/README.txt @@ -121,8 +121,7 @@ Creating Compatible NuttX HEX files 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 @@ -364,7 +363,6 @@ selected as follow: cd tools ./configure.sh pic32mz-starterkit/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/qemu-i486/README.txt b/configs/qemu-i486/README.txt index c91270f5689..bcc0da5ef48 100644 --- a/configs/qemu-i486/README.txt +++ b/configs/qemu-i486/README.txt @@ -99,9 +99,8 @@ Toolchains suspect that this was not necessary, but it was a simple work-around that allowed that person to build a work-able system. - In any event, the file */setenv.sh should be modified to point to the correct - path to the GCC toolchain (if different from the default in your PATH - variable). + In any event, the PATH environment variable should be modified to point to + the correct path to the GCC toolchain. Cygwin Buildroot Toolchain -------------------------- @@ -136,8 +135,8 @@ Buildroot Instructions 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 @@ -165,7 +164,6 @@ Common Configuration Notes cd tools ./configure.sh qemu-i486/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/sabre-6quad/README.txt b/configs/sabre-6quad/README.txt index a9703e5a28b..bff618371e3 100644 --- a/configs/sabre-6quad/README.txt +++ b/configs/sabre-6quad/README.txt @@ -582,11 +582,9 @@ can be selected as follow: cd tools ./configure.sh sabre-6quad/ 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. diff --git a/configs/sam3u-ek/README.txt b/configs/sam3u-ek/README.txt index 4c7f5137575..f210f1a7ccd 100644 --- a/configs/sam3u-ek/README.txt +++ b/configs/sam3u-ek/README.txt @@ -43,9 +43,6 @@ 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 - You may also have to modify the PATH in the setenv.h file if your make cannot - find the tools. - NOTE about Windows native toolchains ------------------------------------ @@ -115,7 +112,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). @@ -142,8 +139,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 @@ -204,8 +201,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. AtmelStudio6.1 ^^^^^^^^^^^^^^ @@ -408,11 +405,9 @@ Configurations cd tools ./configure.sh sam3u-ek/ 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. @@ -476,9 +471,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. @@ -699,16 +692,9 @@ Configurations 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... - NOTE: the use of the setenv.sh file is optional. All that it will - do is to adjust your PATH variable so that the build system can find - your tools. If you use it, you will most likely need to modify the - script so that it has the correct path to your tool binaries - directory. - 3. Install the nxwm unit test $ cd ~/nuttx-git/NxWidgets diff --git a/configs/sam4e-ek/README.txt b/configs/sam4e-ek/README.txt index 5f04cb5db41..aaf19d51c45 100644 --- a/configs/sam4e-ek/README.txt +++ b/configs/sam4e-ek/README.txt @@ -53,9 +53,6 @@ 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 - You may also have to modify the PATH in the setenv.h file if your - make cannot find the tools. - NOTE about Windows native toolchains ------------------------------------ @@ -121,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). @@ -148,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 @@ -210,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. Atmel Studio 6.1 ================ @@ -1230,11 +1227,9 @@ Configurations cd tools ./configure.sh sam4e-ek/ 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. @@ -1292,9 +1287,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. @@ -1625,16 +1618,9 @@ Configurations 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... - NOTE: the use of the setenv.sh file is optional. All that it will - do is to adjust your PATH variable so that the build system can find - your tools. If you use it, you will most likely need to modify the - script so that it has the correct path to your tool binaries - directory. - 3. Install the nxwm unit test $ cd ~/nuttx-git/NxWidgets diff --git a/configs/sam4l-xplained/README.txt b/configs/sam4l-xplained/README.txt index a52b8ae8c44..088db6a64e1 100644 --- a/configs/sam4l-xplained/README.txt +++ b/configs/sam4l-xplained/README.txt @@ -211,9 +211,6 @@ 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. - NOTE about Windows native toolchains ------------------------------------ @@ -283,7 +280,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). @@ -310,8 +307,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 @@ -372,8 +369,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 ^^^^ @@ -593,11 +590,9 @@ Configurations cd tools ./configure.sh sam4l-xplained/ 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. @@ -680,9 +675,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. diff --git a/configs/sam4s-xplained-pro/README.txt b/configs/sam4s-xplained-pro/README.txt index 83f19be9296..6747d99f291 100644 --- a/configs/sam4s-xplained-pro/README.txt +++ b/configs/sam4s-xplained-pro/README.txt @@ -104,7 +104,7 @@ GNU Toolchain Options 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 + have to modify the PATH environment variable if your make cannot find the tools. NOTE about Windows native toolchains @@ -177,7 +177,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). @@ -204,8 +204,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 @@ -266,15 +266,14 @@ 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 ^^^^^^^^^^^^^^^^ Buttons ------- - The SAM4S Xplained has two mechanical buttons. One button is the RESET button connected to the SAM4S reset line and the other is a generic user configurable button labeled BP2 and connected to GPIO PA5. When a button is pressed it @@ -282,7 +281,6 @@ Buttons and LEDs LEDs ---- -======================= There is one LED on board the SAM4S Xplained board Pro that can be controlled by software in the SAM4S: @@ -491,11 +489,9 @@ Configurations cd tools ./configure.shsam4s-xplained-pro/ 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. @@ -569,9 +565,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. diff --git a/configs/sam4s-xplained/README.txt b/configs/sam4s-xplained/README.txt index d5af219e241..6aab73ec5b5 100644 --- a/configs/sam4s-xplained/README.txt +++ b/configs/sam4s-xplained/README.txt @@ -103,10 +103,6 @@ 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. - NOTE about Windows native toolchains ------------------------------------ @@ -176,7 +172,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 +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 are @@ -265,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. Buttons and LEDs ^^^^^^^^^^^^^^^^ @@ -483,11 +479,9 @@ Configurations cd tools ./configure.shsam4s-xplained/ 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. @@ -561,9 +555,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. diff --git a/configs/sama5d2-xult/README.txt b/configs/sama5d2-xult/README.txt index 8f11cc1db50..cb48cc0a298 100644 --- a/configs/sama5d2-xult/README.txt +++ b/configs/sama5d2-xult/README.txt @@ -77,11 +77,9 @@ REVISIT: Unverified, cloned text from the SAMA5D4-EK README.txt cd tools ./configure.sh sama5d2-xult/dramboot 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. NOTE: Be aware that the default dramboot also disables the watchdog. Since you will not be able to re-enable the watchdog later, you may @@ -185,11 +183,9 @@ REVISIT: Unverified, cloned text from the SAMA5D4-EK README.txt cd tools ./configure.sh sama5d2-xult/at25boot 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. Then make AT25BOOT: @@ -916,11 +912,9 @@ Configurations cd tools ./configure.sh sama5d2-xult/ 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. @@ -962,10 +956,6 @@ Configurations tools. Try 'which arm-none-eabi-gcc' to make sure that you are selecting the right tool. - The setenv.sh file is available for you to use to set the PATH - variable. The path in the that file may not, however, be correct - for your installation. - See also the "NOTE about Windows native toolchains" in the section call "GNU Toolchain Options" above. diff --git a/configs/sama5d3-xplained/README.txt b/configs/sama5d3-xplained/README.txt index 89610babeda..a124cd728f3 100644 --- a/configs/sama5d3-xplained/README.txt +++ b/configs/sama5d3-xplained/README.txt @@ -179,7 +179,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). @@ -220,8 +220,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 @@ -257,8 +257,8 @@ NXFLAT Toolchain 7. make - 8. Edit setenv.h, if necessary, so that the PATH variable includes - the path to the newly built NXFLAT binaries. + 8. Make sure that the PATH variable includes the path to the newly built + NXFLAT binaries. NOTE: There are some known incompatibilities with 4.6.3 EABI toolchain and the NXFLAT tools. See the top-level TODO file (under "Binary @@ -2981,11 +2981,9 @@ Configurations cd tools ./configure.sh sama5d3-xplained/ 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 that the PATH environment variable include 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. @@ -3027,10 +3025,6 @@ Configurations tools. Try 'which arm-none-eabi-gcc' to make sure that you are selecting the right tool. - The setenv.sh file is available for you to use to set the PATH - variable. The path in the that file may not, however, be correct - for your installation. - See also the "NOTE about Windows native toolchains" in the section call "GNU Toolchain Options" above. diff --git a/configs/sama5d3x-ek/README.txt b/configs/sama5d3x-ek/README.txt index 73d3ef0b94d..1fa017aaf7b 100644 --- a/configs/sama5d3x-ek/README.txt +++ b/configs/sama5d3x-ek/README.txt @@ -201,7 +201,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). @@ -242,8 +242,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 @@ -279,8 +279,8 @@ NXFLAT Toolchain 7. make - 8. Edit setenv.h, if necessary, so that the PATH variable includes - the path to the newly built NXFLAT binaries. + 8. Make sure that the PATH variable includes the path to the newly built + NXFLAT binaries. NOTE: There are some known incompatibilities with 4.6.3 EABI toolchain and the NXFLAT tools. See the top-level TODO file (under "Binary @@ -372,11 +372,9 @@ Creating and Using NORBOOT cd tools ./configure.sh sama5d3x-ek/ 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. NOTE: Be aware that the default norboot also disables the watchdog. Since you will not be able to re-enable the watchdog later, you may @@ -3306,11 +3304,9 @@ Configurations cd tools ./configure.sh sama5d3x-ek/ 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. @@ -3352,10 +3348,6 @@ Configurations tools. Try 'which arm-none-eabi-gcc' to make sure that you are selecting the right tool. - The setenv.sh file is available for you to use to set the PATH - variable. The path in the that file may not, however, be correct - for your installation. - See also the "NOTE about Windows native toolchains" in the section call "GNU Toolchain Options" above. @@ -3805,16 +3797,9 @@ Configurations 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... - NOTE: the use of the setenv.sh file is optional. All that it will - do is to adjust your PATH variable so that the build system can find - your tools. If you use it, you will most likely need to modify the - script so that it has the correct path to your tool binaries - directory. - 3. Install the nxwm unit test $ cd ~/nuttx-git/NxWidgets diff --git a/configs/sama5d4-ek/README.txt b/configs/sama5d4-ek/README.txt index eec9b595109..bff91b7a06b 100644 --- a/configs/sama5d4-ek/README.txt +++ b/configs/sama5d4-ek/README.txt @@ -195,7 +195,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). @@ -236,8 +236,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 @@ -273,8 +273,8 @@ NXFLAT Toolchain 7. make - 8. Edit setenv.h, if necessary, so that the PATH variable includes - the path to the newly built NXFLAT binaries. + 8. Make sure that the PATH variable includes the path to the newly built + NXFLAT binaries. NOTE: There are some known incompatibilities with 4.6.3 EABI toolchain and the NXFLAT tools. See the top-level TODO file (under "Binary @@ -359,11 +359,9 @@ Creating and Using DRAMBOOT cd tools ./configure.sh sama5d4-ek/dramboot 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 that the PATH environment variable includes + the correct path to the directory than holds your toolchain binaries. NOTE: Be aware that the default dramboot also disables the watchdog. Since you will not be able to re-enable the watchdog later, you may @@ -466,11 +464,9 @@ Creating and Using AT25BOOT cd tools ./configure.sh sama5d4-ek/at25boot 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 that the PATH environment variable includes + the correct path to the directory than holds your toolchain binaries. Then make AT25BOOT: @@ -3592,11 +3588,9 @@ Configurations cd tools ./configure.sh sama5d4-ek/ 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 that 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. @@ -3638,10 +3632,6 @@ Configurations tools. Try 'which arm-none-eabi-gcc' to make sure that you are selecting the right tool. - The setenv.sh file is available for you to use to set the PATH - variable. The path in the that file may not, however, be correct - for your installation. - See also the "NOTE about Windows native toolchains" in the section call "GNU Toolchain Options" above. @@ -4165,8 +4155,7 @@ Configurations $ cd nuttx/tools : Go to the tools sub-directory $ ./configure.sh sama5d4-ek/kernel : Establish this configuration $ cd .. : Back to the NuttX build directory - : Edit setenv.sh to use the correct path - $ . ./setenv.sh : Set up the PATH variable + $ export PATH=???:$PATH : Set up the PATH variable $ make : Build the kerne with a dummy ROMFS image : This should create the nuttx ELF $ make export : Create the kernel export package @@ -4184,8 +4173,7 @@ Configurations $ cd nuttx/tools : Go to the tools sub-directory $ ./configure.sh sama5d4-ek/kernel : Establish this configuration $ cd .. : Back to the NuttX build directory - : Edit setenv.sh to use the correct path - $ . ./setenv.sh : Set up the PATH variable + $ export PATH=???:$PATH : Set up the PATH variable $ touch configs/sama5d4-ek/include/boot_romfsimg.h $ make : Build the kernel with a dummy ROMFS image : This should create the nuttx ELF @@ -4770,16 +4758,9 @@ Configurations b. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... - NOTE: the use of the setenv.sh file is optional. All that it - will do is to adjust your PATH variable so that the build system - can find your tools. If you use it, you will most likely need to - modify the script so that it has the correct path to your tool - binary directory. - c. Install the nxwm unit test $ cd ~/nuttx-git/NxWidgets diff --git a/configs/samd20-xplained/README.txt b/configs/samd20-xplained/README.txt index f489d6b6187..d79a298b697 100644 --- a/configs/samd20-xplained/README.txt +++ b/configs/samd20-xplained/README.txt @@ -291,9 +291,6 @@ 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 - You may also have to modify the PATH in the setenv.h file if your - make cannot find the tools. - NOTE about Windows native toolchains ------------------------------------ @@ -359,7 +356,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-M0 GCC toolchain (if different from the default in your PATH variable). @@ -386,8 +383,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 @@ -604,11 +601,9 @@ Configurations cd tools ./configure.sh samd20-xplained/ 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 that the PATH environment variable include 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. @@ -695,9 +690,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 called "GNU Toolchain Options" above. diff --git a/configs/samd21-xplained/README.txt b/configs/samd21-xplained/README.txt index c000821cb35..6ac8fafe393 100644 --- a/configs/samd21-xplained/README.txt +++ b/configs/samd21-xplained/README.txt @@ -466,11 +466,9 @@ Configurations cd tools ./configure.sh samd21-xplained/ 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 the PATH environment varaible include 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. @@ -557,9 +555,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 called "GNU Toolchain Options" above. diff --git a/configs/same70-xplained/README.txt b/configs/same70-xplained/README.txt index c95eef6e1bd..1b10b484b04 100644 --- a/configs/same70-xplained/README.txt +++ b/configs/same70-xplained/README.txt @@ -1099,11 +1099,9 @@ can be selected as follow: cd tools ./configure.sh same70-xplained/ 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 that the PATH environment variable include 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. @@ -1166,11 +1164,6 @@ NOTES: for the Cortex-M7, but is supported by at least this realeasse of the ARM GNU tools: - https://launchpadlibrarian.net/192228215/release.txt - - Current (2105-07-31) setenv.sh file are configured to use this - release: - https://launchpadlibrarian.net/209776344/release.txt That toolchain selection can easily be reconfigured using diff --git a/configs/saml21-xplained/README.txt b/configs/saml21-xplained/README.txt index 673b9e43b22..c55ff4fab88 100644 --- a/configs/saml21-xplained/README.txt +++ b/configs/saml21-xplained/README.txt @@ -272,9 +272,6 @@ 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 - You may also have to modify the PATH in the setenv.h file if your - make cannot find the tools. - NOTE about Windows native toolchains ------------------------------------ @@ -340,7 +337,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-M0 GCC toolchain (if different from the default in your PATH variable). @@ -367,8 +364,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 @@ -642,11 +639,9 @@ Configurations cd tools ./configure.sh saml21-xplained/ 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 that the PATH environmental 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. @@ -724,9 +719,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 called "GNU Toolchain Options" above. diff --git a/configs/samv71-xult/README.txt b/configs/samv71-xult/README.txt index c9638512594..182b0cc99aa 100644 --- a/configs/samv71-xult/README.txt +++ b/configs/samv71-xult/README.txt @@ -1597,11 +1597,9 @@ can be selected as follow: cd tools ./configure.sh samv71-xult/ 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 the PATH environment variable include 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. @@ -1636,11 +1634,6 @@ NOTES: for the Cortex-M7, but is supported by at least this realeasse of the ARM GNU tools: - https://launchpadlibrarian.net/192228215/release.txt - - Current (2105-07-31) setenv.sh file are configured to use this - release: - https://launchpadlibrarian.net/209776344/release.txt That toolchain selection can easily be reconfigured using @@ -2237,16 +2230,9 @@ Configuration sub-directories b. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... - NOTE: the use of the setenv.sh file is optional. All that it will - do is to adjust your PATH variable so that the build system can find - your tools. If you use it, you will most likely need to modify the - script so that it has the correct path to your tool binaries - directory. - c. Install the nxwm unit test $ cd HOME/NxWidgets @@ -2427,16 +2413,9 @@ Configuration sub-directories b. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... - NOTE: the use of the setenv.sh file is optional. All that it will - do is to adjust your PATH variable so that the build system can find - your tools. If you use it, you will most likely need to modify the - script so that it has the correct path to your tool binaries - directory. - c. Install the nxwm unit test $ cd HOME/NxWidgets diff --git a/configs/shenzhou/README.txt b/configs/shenzhou/README.txt index 1eeedcd252d..2fb9dd6eec7 100644 --- a/configs/shenzhou/README.txt +++ b/configs/shenzhou/README.txt @@ -219,9 +219,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 CodeSourcery (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux native toolchains. There are several limitations @@ -321,7 +318,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). @@ -357,14 +354,7 @@ 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. 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 @@ -425,8 +415,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 ==== @@ -738,7 +728,6 @@ can be selected as follow: cd tools ./configure.sh shenzhou/ cd - - . ./setenv.sh Where is one of the following: @@ -819,7 +808,6 @@ Where is one of the following: 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... diff --git a/configs/sim/README.txt b/configs/sim/README.txt index 816ed007437..15ec2078a8c 100644 --- a/configs/sim/README.txt +++ b/configs/sim/README.txt @@ -382,12 +382,6 @@ Common Configuration Information cd /tools ./configure.sh sim/ cd - - . ./setenv.sh - - If this is a Windows native build, then configure.bat should be used - instead of configure.sh: - - configure.bat sim\ Where is one of the following sub-directories. diff --git a/configs/spark/README.txt b/configs/spark/README.txt index c870066b9a6..3b8b0ebf6f7 100644 --- a/configs/spark/README.txt +++ b/configs/spark/README.txt @@ -73,9 +73,6 @@ GNU Toolchain Options CONFIG_ARMV7M_TOOLCHAIN_RAISONANCE=y : Raisonance RIDE7 under Windows CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=n : 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 @@ -191,7 +188,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). @@ -218,8 +215,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 @@ -280,8 +277,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 ============ diff --git a/configs/stm3210e-eval/README.txt b/configs/stm3210e-eval/README.txt index 9ca365c92cc..b622630f984 100644 --- a/configs/stm3210e-eval/README.txt +++ b/configs/stm3210e-eval/README.txt @@ -53,9 +53,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 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), 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 @@ -121,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). @@ -148,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 @@ -210,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. DFU and JTAG ============ @@ -701,7 +698,6 @@ can be selected as follow: cd tools ./configure.sh stm3210e-eval/ cd - - . ./setenv.sh Where is one of the following: @@ -748,9 +744,9 @@ Where is one of the following: apps/system/i2c =========== ======================= ================================ - (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 modify PATH environment variable to + to include the correct path to the binaries for whichever + toolchain you may use. (2) Since DfuSe is assumed, this configuration may only work under Cygwin without modification. (3) When any other device other than /dev/console is used for a user diff --git a/configs/stm3220g-eval/README.txt b/configs/stm3220g-eval/README.txt index aa4b365791f..69cded915fc 100644 --- a/configs/stm3220g-eval/README.txt +++ b/configs/stm3220g-eval/README.txt @@ -61,9 +61,6 @@ GNU Toolchain Options CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin (default) CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL : Generic arm-none-eabi 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. - The toolchain may also be set using the kconfig-mconf utility (make menuconfig) or by passing CONFIG_ARMV7M_TOOLCHAIN= to make, where is one of CODESOURCERYW, CODESOURCERYL, ATOLLOC, DEVKITARM, RAISONANCE, BUILDROOT or @@ -272,7 +269,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). @@ -299,8 +296,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 @@ -361,8 +358,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 ======== @@ -855,7 +852,6 @@ can be selected as follow: cd tools ./configure.sh stm3220g-eval/ cd - - . ./setenv.sh Where is one of the following: @@ -1172,7 +1168,6 @@ Where is one of the following: 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... diff --git a/configs/stm3240g-eval/README.txt b/configs/stm3240g-eval/README.txt index 4b9a1f3ce8f..fc01bae9082 100644 --- a/configs/stm3240g-eval/README.txt +++ b/configs/stm3240g-eval/README.txt @@ -61,9 +61,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 CodeSourcery (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux native toolchains. There are several limitations @@ -168,7 +165,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). @@ -195,8 +192,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 @@ -257,8 +254,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 ======== @@ -890,7 +887,6 @@ can be selected as follow: cd tools ./configure.sh stm3240g-eval/ cd - - . ./setenv.sh Where is one of the following: @@ -1467,7 +1463,6 @@ Where is one of the following: 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... diff --git a/configs/stm32_tiny/README.txt b/configs/stm32_tiny/README.txt index 7abbc4ccb0e..71fdfd472ee 100644 --- a/configs/stm32_tiny/README.txt +++ b/configs/stm32_tiny/README.txt @@ -57,9 +57,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 @@ -164,7 +161,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). @@ -191,8 +188,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 @@ -253,8 +250,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 ==== @@ -513,12 +510,6 @@ can be selected as follow: cd tools ./configure.sh STM32Tiny/ cd - - . ./setenv.sh - -If this is a Windows native build, then configure.bat should be used -instead of configure.sh: - - configure.bat STM32Tiny\ Where is one of the following: diff --git a/configs/stm32f103-minimum/README.txt b/configs/stm32f103-minimum/README.txt index 82f9f33ce89..91e08731f2e 100644 --- a/configs/stm32f103-minimum/README.txt +++ b/configs/stm32f103-minimum/README.txt @@ -528,12 +528,6 @@ Configurations cd tools ./configure.sh STM32F103 Minimum/ cd - - . ./setenv.sh - - If this is a Windows native build, then configure.bat should be used - instead of configure.sh: - - configure.bat STM32F103-Minimum\ Where is one of the following: diff --git a/configs/stm32f3discovery/README.txt b/configs/stm32f3discovery/README.txt index 8cb94aa2f70..c3783d1606e 100644 --- a/configs/stm32f3discovery/README.txt +++ b/configs/stm32f3discovery/README.txt @@ -53,9 +53,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 @@ -160,7 +157,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). @@ -187,8 +184,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 @@ -249,8 +246,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 ==== @@ -657,12 +654,6 @@ can be selected as follow: cd tools ./configure.sh STM32F3Discovery/ cd - - . ./setenv.sh - -If this is a Windows native build, then configure.bat should be used -instead of configure.sh: - - configure.bat STM32F3Discovery\ Where is one of the following: diff --git a/configs/stm32f429i-disco/README.txt b/configs/stm32f429i-disco/README.txt index 2b406e035cb..fc2719ad009 100644 --- a/configs/stm32f429i-disco/README.txt +++ b/configs/stm32f429i-disco/README.txt @@ -650,12 +650,6 @@ can be selected as follow: cd tools ./configure.sh STM32F429I-DISCO/ cd - - . ./setenv.sh - -If this is a Windows native build, then configure.bat should be used -instead of configure.sh: - - configure.bat STM32F429I-DISCO\ Where is one of the following: @@ -957,7 +951,6 @@ Where is one of the following: 2. Make the build context (only) $ cd .. - $ . ./setenv.sh $ make context ... diff --git a/configs/stm32f4discovery/README.txt b/configs/stm32f4discovery/README.txt index 472621c1fec..b748027d83e 100644 --- a/configs/stm32f4discovery/README.txt +++ b/configs/stm32f4discovery/README.txt @@ -74,9 +74,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 @@ -181,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). @@ -208,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 are @@ -270,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. LEDs ==== @@ -1217,12 +1214,6 @@ can be selected as follow: cd tools ./configure.sh STM32F4Discovery/ cd - - . ./setenv.sh - -If this is a Windows native build, then configure.bat should be used -instead of configure.sh: - - configure.bat STM32F4Discovery\ Where is one of the following: diff --git a/configs/stm32f4discovery/winbuild/setenv.bat b/configs/stm32f4discovery/winbuild/setenv.bat deleted file mode 100644 index 22fa1e599bb..00000000000 --- a/configs/stm32f4discovery/winbuild/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/stm32f4discovery/winbuild/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 CodeSourcey toolchain. See -rem http://www.mentor.com/embedded-software/codesourcery - -set PATH=C:\Program Files (x86)\CodeSourcery\Sourcery G++ Lite\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% diff --git a/configs/stm32f746g-disco/README.txt b/configs/stm32f746g-disco/README.txt index 47dc3a64688..a3477a5997f 100644 --- a/configs/stm32f746g-disco/README.txt +++ b/configs/stm32f746g-disco/README.txt @@ -465,12 +465,6 @@ Configurations cd tools ./configure.sh stm32f746g-disco/ cd - - . ./setenv.sh - - If this is a Windows native build, then configure.bat should be used - instead of configure.sh: - - configure.bat STM32F746G-DISCO\ Where is one of the sub-directories listed below. @@ -497,15 +491,10 @@ Configurations https://launchpad.net/gcc-arm-embedded As of this writing (2015-03-11), full support is difficult to find - for the Cortex-M7, but is supported by at least this realeasse of + for the Cortex-M7, but is supported by at least this realease of the ARM GNU tools: - https://launchpadlibrarian.net/192228215/release.txt - - Current (2105-07-31) setenv.sh file are configured to use this - release: - - https://launchpadlibrarian.net/209776344/release.txt + https://launchpadlibrarian.net/209776344/release.txt That toolchain selection can easily be reconfigured using 'make menuconfig'. Here are the relevant current settings: diff --git a/configs/stm32ldiscovery/README.txt b/configs/stm32ldiscovery/README.txt index 4158273b5ad..92fdb431114 100644 --- a/configs/stm32ldiscovery/README.txt +++ b/configs/stm32ldiscovery/README.txt @@ -218,9 +218,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 @@ -325,7 +322,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). @@ -352,8 +349,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 @@ -414,8 +411,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 ==== @@ -727,12 +724,6 @@ Configurations cd tools ./configure.sh STM32L-Discovery/ cd - - . ./setenv.sh - - If this is a Windows native build, then configure.bat should be used - instead of configure.sh: - - configure.bat STM32L-Discovery\ Where is one of the following sub-directories. diff --git a/configs/stm32vldiscovery/README.txt b/configs/stm32vldiscovery/README.txt index 963a85ff7cf..8d4923be717 100644 --- a/configs/stm32vldiscovery/README.txt +++ b/configs/stm32vldiscovery/README.txt @@ -51,9 +51,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.sh 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 @@ -153,7 +150,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). @@ -180,8 +177,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 @@ -242,8 +239,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 ==== @@ -447,7 +444,6 @@ and can be selected as follow: cd tools ./configure.sh stm32vldiscovery/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/sure-pic32mx/README.txt b/configs/sure-pic32mx/README.txt index 754005c541e..b8ca0cc7228 100644 --- a/configs/sure-pic32mx/README.txt +++ b/configs/sure-pic32mx/README.txt @@ -387,8 +387,7 @@ Loading NuttX with PICkit2 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 + # 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 @@ -635,7 +634,6 @@ Configurations cd tools ./configure.sh sure-pic32mx/ cd - - . ./setenv.sh Where is one of the following sub-directories. diff --git a/configs/teensy-2.0/README.txt b/configs/teensy-2.0/README.txt index b409268a652..105b2891572 100644 --- a/configs/teensy-2.0/README.txt +++ b/configs/teensy-2.0/README.txt @@ -215,9 +215,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. + Make sure that your PATH evirnoment variable includes the path the newly + built binaries. After configuring NuttX, make sure that CONFIG_AVR_BUILDROOT_TOOLCHAIN=y is set in your .config file. @@ -227,8 +226,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. + Make sure that your PATH evirnoment variable includes the path the WinAvR + binaries. After configuring NuttX, make sure that CONFIG_AVR_WINAVR_TOOLCHAIN=y is set in your .config file. @@ -319,8 +318,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 @@ -522,7 +521,6 @@ Common Configuration Notes cd tools ./configure.sh teensy-2.0/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/teensy-3.x/README.txt b/configs/teensy-3.x/README.txt index a43a0c08339..cdcfee7e62f 100644 --- a/configs/teensy-3.x/README.txt +++ b/configs/teensy-3.x/README.txt @@ -228,11 +228,9 @@ Configurations ./configure.sh teensy-3.x/ 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 that your 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: diff --git a/configs/tm4c123g-launchpad/README.txt b/configs/tm4c123g-launchpad/README.txt index e4554002cf7..cdb2d2ca898 100644 --- a/configs/tm4c123g-launchpad/README.txt +++ b/configs/tm4c123g-launchpad/README.txt @@ -291,9 +291,8 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator oocd.sh $PWD - The relative path to the oocd.sh script is configs/tm4c123g-launchpad/tools, - but that should have been added to your PATH variable when you sourced - the setenv.sh script. + The relative path to the oocd.sh script is configs/tm4c123g-launchpad/tools. + You may want to add that path to you PATH variable. Note that OpenOCD needs to be run with administrator privileges in some environments (sudo). @@ -368,9 +367,6 @@ 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. - NOTE: the CodeSourcery (for Windows), Atollic, devkitARM, and Code Red (for Windows) toolchains are Windows native toolchains. The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux native toolchains. There are several @@ -435,7 +431,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). @@ -462,8 +458,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 @@ -524,8 +520,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 ==== @@ -763,7 +759,6 @@ sub-directory and can be selected as follow: cd tools ./configure.sh tm4c123g-launchpad/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/tm4c1294-launchpad/README.txt b/configs/tm4c1294-launchpad/README.txt index b670121adea..1ed896c3e96 100644 --- a/configs/tm4c1294-launchpad/README.txt +++ b/configs/tm4c1294-launchpad/README.txt @@ -28,7 +28,6 @@ sub-directory and can be selected as follow: cd tools ./configure.sh tm4c1294-launchpad/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/twr-k60n512/README.txt b/configs/twr-k60n512/README.txt index 9c64cae46db..bf7ff26db39 100644 --- a/configs/twr-k60n512/README.txt +++ b/configs/twr-k60n512/README.txt @@ -312,9 +312,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 toolchains are Windows native toolchains. The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux native toolchains. There are several limitations @@ -378,7 +375,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). @@ -407,8 +404,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 @@ -469,8 +466,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. TWR-K60N512-specific Configuration Options ========================================== @@ -643,7 +640,6 @@ can be selected as follow: cd tools ./configure.sh twr-k60n512/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/twr-k64f120m/README.txt b/configs/twr-k64f120m/README.txt index cbb5a88b8d3..6c69686a849 100644 --- a/configs/twr-k64f120m/README.txt +++ b/configs/twr-k64f120m/README.txt @@ -442,9 +442,6 @@ GNU Toolchain Options CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : NuttX buildroot under Linux or Cygwin CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL=y : GCC (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 toolchains are Windows native toolchains. The CodeSourcey (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux native toolchains. There are several limitations @@ -508,9 +505,8 @@ IDEs NuttX EABI "buildroot" Toolchain ================================ - A GNU GCC-based toolchain is assumed. The files */setenv.sh should - be modified to point to the correct path to the Cortex-M4 GCC toolchain (if - different from the default in your PATH variable). + 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 you have no Cortex-M4 toolchain, one can be downloaded from the NuttX Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). @@ -537,8 +533,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 @@ -599,8 +595,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. TWR-K64F120M-specific Configuration Options ========================================== @@ -770,7 +766,6 @@ can be selected as follow: cd tools ./configure.sh twr-k64f120m/ cd .. - . ./setenv.sh Where is one of the following: diff --git a/configs/ubw32/README.txt b/configs/ubw32/README.txt index cbd4cad6e66..a1a77294ef3 100644 --- a/configs/ubw32/README.txt +++ b/configs/ubw32/README.txt @@ -326,8 +326,7 @@ Loading NuttX with PICkit2 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 + # 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 @@ -569,7 +568,6 @@ selected as follow: cd tools ./configure.sh ubw32/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/us7032evb1/README.txt b/configs/us7032evb1/README.txt index 15efbddfe00..eabbba14030 100644 --- a/configs/us7032evb1/README.txt +++ b/configs/us7032evb1/README.txt @@ -14,7 +14,7 @@ time being. 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). @@ -38,8 +38,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. shterm ^^^^^^ @@ -64,7 +64,6 @@ Common Configuration Notes cd tools ./configure.sh us7032evb1/ cd - - . ./setenv.sh Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/viewtool-stm32f107/README.txt b/configs/viewtool-stm32f107/README.txt index 04ff1afbb2a..31d5fc734ee 100644 --- a/configs/viewtool-stm32f107/README.txt +++ b/configs/viewtool-stm32f107/README.txt @@ -536,11 +536,9 @@ Configurations cd tools ./configure.sh viewtool-stm32f107/ 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 starting the build, make sure that your PATH environment variable + includes the correct path to your toolchain. 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. @@ -579,10 +577,6 @@ Configurations System Type -> Toolchain: CONFIG_ARMV7M_TOOLCHAIN_CODESOURCERYW=y : GNU EABI toolchain for windows - The setenv.sh file is available for you to use to set the PATH - variable. The path in the that file may not, however, be correct - for your installation. - See also the "NOTE about Windows native toolchains" in the section call "GNU Toolchain Options" above. diff --git a/configs/xmc4500-relax/README.txt b/configs/xmc4500-relax/README.txt index 9fb7e29c2e9..7c3e3d6ef60 100644 --- a/configs/xmc4500-relax/README.txt +++ b/configs/xmc4500-relax/README.txt @@ -84,11 +84,9 @@ Configurations cd tools ./configure.sh xmc5400-relax/ 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 starting the build, make sure that your PATH environment variable + includes the correct path to your toolchain. 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. diff --git a/configs/xtrs/README.txt b/configs/xtrs/README.txt index a1dc4e6b03d..d778f087f73 100644 --- a/configs/xtrs/README.txt +++ b/configs/xtrs/README.txt @@ -55,8 +55,9 @@ Configuring NuttX 1) From a POSIX window: cd tools ./configure.sh xtrs/ostest - 2) From a CMD.exe window - setenv.bat + 2) Modify your PATH environment variable to include the path to the + SDCC toolchain. + 3) From a CMD.exe window make If this is a Windows native build, then configure.bat should be used @@ -64,9 +65,6 @@ Configuring NuttX configure.bat xtrs\ostest - The setenv.bat will need to be updated to include the PATH to the XTRS - hex2cmd program. - NOTES: 1. This configuration uses the mconf-based configuration tool. See the @@ -91,8 +89,9 @@ Configuring NuttX 1) From a POSIX window: cd tools ./configure.sh xtrs/nsh - 2) From a CMD.exe window - setenv.bat + 2) Modify your PATH environment variable to include the path to the + SDCC toolchain. + 3) From a CMD.exe window make If this is a Windows native build, then configure.bat should be used @@ -100,9 +99,6 @@ Configuring NuttX configure.bat xtrs\nsh - The setenv.bat will need to be updated to include the PATH to the XTRS - hex2cmd program. - NOTES: 1. This configuration uses the mconf-based configuration tool. See the @@ -134,8 +130,9 @@ Configuring NuttX 1) From a POSIX window: cd tools ./configure.sh xtrs/pashello - 2) From a CMD.exe window - setenv.bat + 2) Modify your PATH environment variable to include the path to the + SDCC toolchain. + 3) From a CMD.exe window make If this is a Windows native build, then configure.bat should be used @@ -143,9 +140,6 @@ Configuring NuttX configure.bat xtrs\pashello - The setenv.bat will need to be updated to include the PATH to the XTRS - hex2cmd program. - NOTES: 1. This configuration uses the mconf-based configuration tool. See the @@ -195,11 +189,6 @@ in the .config file because the backslash may upset some Unix-based tools. This configuration will require a recent version of SDCC (ca. 3.2.1) for Linux or custom built for Cygwin (see below). -You cannot use the default setenv.bat in these Unix-like enviroments because -that is a Windows batch file. Use configs/z80sim/script/setenv.sh instead. -setenv.sh must include the path to the installation location of SDCC (probably -/usr/local/bin). - SDCC ^^^^ diff --git a/configs/xtrs/nsh/setenv.bat b/configs/xtrs/nsh/setenv.bat deleted file mode 100644 index 0df2ba4b66d..00000000000 --- a/configs/xtrs/nsh/setenv.bat +++ /dev/null @@ -1,54 +0,0 @@ -@echo off - -rem configs/xtrs/nsh/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% - -rem This is the location where the XTRS hex2cmd program is available -rem set PATH=????:%PATH% - -echo %PATH% diff --git a/configs/xtrs/ostest/setenv.bat b/configs/xtrs/ostest/setenv.bat deleted file mode 100644 index 38822dcc2d9..00000000000 --- a/configs/xtrs/ostest/setenv.bat +++ /dev/null @@ -1,54 +0,0 @@ -@echo off - -rem configs/xtrs/ostest/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% - -rem This is the location where the XTRS hex2cmd program is available -rem set PATH=????:%PATH% - -echo %PATH% diff --git a/configs/xtrs/pashello/setenv.bat b/configs/xtrs/pashello/setenv.bat deleted file mode 100644 index fbedd244a86..00000000000 --- a/configs/xtrs/pashello/setenv.bat +++ /dev/null @@ -1,54 +0,0 @@ -@echo off - -rem configs/xtrs/pashello/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% - -rem This is the location where the XTRS hex2cmd program is available -rem set PATH=????:%PATH% - -echo %PATH% diff --git a/configs/z16f2800100zcog/README.txt b/configs/z16f2800100zcog/README.txt index 02f7f84bfde..5875a15e0d9 100644 --- a/configs/z16f2800100zcog/README.txt +++ b/configs/z16f2800100zcog/README.txt @@ -64,17 +64,17 @@ Version 5.0.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 + to modify the versioning in the Make.defs file; if you want to build on a different platform, you will need to change the path in the ZDS binaries - in those same files. + in those that file and your PATH environment variable. Other Versions If you use any version of ZDS-II other than 5.0.1 or if you install ZDS-II at any location other than the default location, you will have to modify - two files: (1) configs/z16f2800100zcog/*/setenv.sh and (2) - configs/z16f2800100zcog/*/Make.defs. Simply edit these two files, changing - 5.0.1 to whatever. + configs/z16f2800100zcog/*/Make.defs. Simply edit that file, changing + 5.0.1 to whatever. Also make sure that your PATH environment variable + includes th correct path to the toolchain. Patches ======= @@ -104,7 +104,6 @@ The patch would be applied when NuttX is configured as follows: cd tools ./configure.sh z16f2800100zcog/nsh cd .. - . ./setenv.sh dopatch.sh make @@ -240,9 +239,7 @@ ostest 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/z16/src/nuttx.linkcmd that is autogenerated by arch/z16/src/Makefile. The basic problem is the spurious spaces and and carriage returns are generated at diff --git a/configs/z16f2800100zcog/scripts/setenv.bat b/configs/z16f2800100zcog/scripts/setenv.bat deleted file mode 100644 index 4ee67c97eba..00000000000 --- a/configs/z16f2800100zcog/scripts/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/z16f2800100zcog/scripts/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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_ZNEO_5.0.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% diff --git a/configs/z80sim/README.txt b/configs/z80sim/README.txt index b45c762cb65..45eb1d3109c 100644 --- a/configs/z80sim/README.txt +++ b/configs/z80sim/README.txt @@ -22,13 +22,13 @@ Configuring NuttX ostest This configuration performs a simple, minimal OS test using - examples/ostest. This can be configurated as follows: + examples/ostest. This can be configured as follows: 1) From a POSIX window: cd tools ./configure.sh z80sim/ostest - 2) From a CMD.exe window - setenv.bat + 2) Make sure that your PATH environment variable includes the path + to the SDCC toolchain. NOTES: @@ -56,8 +56,8 @@ Configuring NuttX 1) From a POSIX window: cd tools ./configure.sh z80sim/nsh - 2) From a CMD.exe window - setenv.bat + 2) Set the PATH environment variable to include the path to the SDCC + toolchain. NOTES: @@ -87,8 +87,8 @@ Configuring NuttX 1) From a POSIX window: cd tools ./configure.sh z80sim/pashello - 2) From a CMD.exe window - setenv.bat + 2) Set the PATH environment variable to include the path to the SDCC + toolchain. NOTES: @@ -141,11 +141,6 @@ in the .config file because the backslash may upset some Unix-based tools. This configuration will require a recent version of SDCC (ca. 3.2.1) for Linux or custom built for Cygwin (see below). -You cannot use the default setenv.bat in these Unix-like enviroments because -that is a Windows batch file. Use configs/z80sim/script/setenv.sh instead. -setenv.sh must include the path to the installation location of SDCC (probably -/usr/local/bin). - SDCC ^^^^ diff --git a/configs/z80sim/nsh/setenv.bat b/configs/z80sim/nsh/setenv.bat deleted file mode 100644 index 9ce941938bd..00000000000 --- a/configs/z80sim/nsh/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/z80sim/nsh/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% diff --git a/configs/z80sim/ostest/setenv.bat b/configs/z80sim/ostest/setenv.bat deleted file mode 100644 index e5c7ff5bf1b..00000000000 --- a/configs/z80sim/ostest/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/z80sim/ostest/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% diff --git a/configs/z80sim/pashello/setenv.bat b/configs/z80sim/pashello/setenv.bat deleted file mode 100644 index 59c372ddd90..00000000000 --- a/configs/z80sim/pashello/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/z80sim/pashello/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% diff --git a/configs/z80sim/scripts/setenv.bat b/configs/z80sim/scripts/setenv.bat deleted file mode 100644 index c266d1e8187..00000000000 --- a/configs/z80sim/scripts/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/z80sim/scripts/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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 SDCC toolchain for windows. - -set PATH=C:\Program Files (x86)\SDCC/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% diff --git a/configs/z8encore000zco/README.txt b/configs/z8encore000zco/README.txt index 85cb56f52c2..35e2484f2e3 100644 --- a/configs/z8encore000zco/README.txt +++ b/configs/z8encore000zco/README.txt @@ -34,15 +34,15 @@ Version 5.0.0 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 + to modify the versioning in the Make.defs file; if you want to build on a different platform, you will need to change the path in the ZDS binaries - in those same files. + in those that file and also in your patch variable. Other Versions If you use any version of ZDS-II other than 5.0.0 or if you install ZDS-II at any location other than the default location, you will have to modify - two files: (1) configs/z8encore000zco/*/setenv.sh and (2) - configs/z8encore000zco/*/Make.defs. + the configs/z8encore000zco/*/Make.defs file and your PATH environment + variable. Configuration Subdirectories ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -98,9 +98,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 diff --git a/configs/z8encore000zco/scripts/setenv.bat b/configs/z8encore000zco/scripts/setenv.bat deleted file mode 100644 index 407cca97fe0..00000000000 --- a/configs/z8encore000zco/scripts/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/z8encore000zco/scripts/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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_Z8Encore!_5.0.0\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% diff --git a/configs/z8f64200100kit/README.txt b/configs/z8f64200100kit/README.txt index 142ea785e15..69c69acdf92 100644 --- a/configs/z8f64200100kit/README.txt +++ b/configs/z8f64200100kit/README.txt @@ -34,15 +34,15 @@ Version 5.0.0 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 + to modify the versioning in the Make.defs file; if you want to build on a different platform, you will need to change the path in the ZDS binaries - in those same files. + in those that file and also in your PATH variable. Other Versions If you use any version of ZDS-II other than 5.0.0 or if you install ZDS-II at any location other than the default location, you will have to modify - two files: (1) configs/z8f64200100kit/*/setenv.sh and (2) - configs/z8f64200100kit/*/Make.defs. + the configs/z8f64200100kit/*/Make.defs file and also your PATH environment + variable. Configuration Subdirectories ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -98,9 +98,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 diff --git a/configs/z8f64200100kit/scripts/setenv.bat b/configs/z8f64200100kit/scripts/setenv.bat deleted file mode 100644 index e0526d988a8..00000000000 --- a/configs/z8f64200100kit/scripts/setenv.bat +++ /dev/null @@ -1,50 +0,0 @@ -@echo off - -rem configs/z8f64200100kit/scripts/setenv.bat -rem -rem Copyright (C) 2012 Gregory Nutt. All rights reserved. -rem Author: Gregory Nutt -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_Z8Encore!_5.0.0\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% diff --git a/configs/zkit-arm-1769/README.txt b/configs/zkit-arm-1769/README.txt index b645c7f6b24..3a26764bba8 100644 --- a/configs/zkit-arm-1769/README.txt +++ b/configs/zkit-arm-1769/README.txt @@ -171,9 +171,6 @@ GNU Toolchain Options CONFIG_ARMV7M_TOOLCHAIN_CODEREDL=y : Code Red toolchain under Linux CONFIG_ARMV7M_TOOLCHAIN_ATOLLIC=y : The Atollic toolchain - You may also have to modify the PATH in the setenv.h file if your make cannot - find the tools. - NOTE: the CodeSourcery (for Windows), devkitARM, and Code Red (for Windoes) are Windows native toolchains. The CodeSourcey (for Linux), Code Red (for Linux) and NuttX buildroot toolchains are Cygwin and/or Linux native toolchains. There @@ -208,9 +205,9 @@ GNU Toolchain Options NuttX buildroot Toolchain ^^^^^^^^^^^^^^^^^^^^^^^^^ - A GNU GCC-based toolchain is assumed. The files */setenv.sh should - be modified to point to the correct path to the Cortex-M3 GCC toolchain (if - different from the default in your PATH variable). + A GNU GCC-based toolchain is assumed. The PATH 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). If you have no Cortex-M3 toolchain, one can be downloaded from the NuttX Bitbucket download site (https://bitbucket.org/nuttx/nuttx/downloads/). @@ -235,8 +232,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 your 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 @@ -280,8 +277,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 ^^^^ @@ -521,7 +518,6 @@ selected as follow: cd tools ./configure.sh zkit-arm-1769/ cd - - . ./setenv.sh Where is one of the following: diff --git a/configs/zp214xpa/README.txt b/configs/zp214xpa/README.txt index 471d648e049..ca4f79038ee 100644 --- a/configs/zp214xpa/README.txt +++ b/configs/zp214xpa/README.txt @@ -236,9 +236,8 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator configs/zp214xpa/tools/oocd.sh $PWD - If you use the setenv.sh file, that the path to oocd.sh will be added - to your PATH environment variabl. So, in that case, the command simplifies - to just: + If you add that path to your PATH environment variable, ithe commandi + simplifies to just: oocd.sh $PWD @@ -288,7 +287,6 @@ Configurations: cd tools ./configure.sh zp214xpa/ cd - - . ./setenv.sh Where is one of the following: