diff --git a/configs/amber/README.txt b/configs/amber/README.txt index d48090f237c..ecc627d6d3f 100644 --- a/configs/amber/README.txt +++ b/configs/amber/README.txt @@ -274,8 +274,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh amber/ + tools/configure.sh amber/ NOTE: you also must copy avr-libc header files into the NuttX include directory with command perhaps like: @@ -489,9 +488,7 @@ Common Configuration Notes 1. Each Amber Web Server configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh amber/ - cd - + tools/configure.sh amber/ 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 0de6bcb4d22..a81bd42ad92 100644 --- a/configs/arduino-due/README.txt +++ b/configs/arduino-due/README.txt @@ -715,7 +715,7 @@ Configurations This re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. diff --git a/configs/arduino-mega2560/README.txt b/configs/arduino-mega2560/README.txt index 7663fdadbdc..3a7f6293431 100644 --- a/configs/arduino-mega2560/README.txt +++ b/configs/arduino-mega2560/README.txt @@ -48,9 +48,7 @@ Configurations 1. Each Arduino MEGA2560 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh arduino-mega2560/ - cd - + tools/configure.sh arduino-mega2560/ 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 8e6b639dec2..2ce95ccce40 100644 --- a/configs/avr32dev1/README.txt +++ b/configs/avr32dev1/README.txt @@ -431,9 +431,7 @@ Common Configuration Notes 1. Each Atmel AVR32DEV configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh avr32dev1/ - cd - + tools/configure.sh avr32dev1/ 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 9231b80c476..9fea0f32520 100644 --- a/configs/bambino-200e/README.txt +++ b/configs/bambino-200e/README.txt @@ -377,9 +377,7 @@ Configurations Each Bambino-200e configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh bambino-200e/ - cd - + tools/configure.sh bambino-200e/ Where is one of the following: diff --git a/configs/c5471evm/README.txt b/configs/c5471evm/README.txt index 36e6d7ce439..cde2f7bdc4d 100644 --- a/configs/c5471evm/README.txt +++ b/configs/c5471evm/README.txt @@ -13,8 +13,7 @@ Toolchain 1. You must have already configured Nuttx in nuttx. - cd tools - ./configure.sh c5471evm/ + tools/configure.sh c5471evm/ 2. Download the latest buildroot package into @@ -130,9 +129,7 @@ Common Configuration Notes 1. Each C5471 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh c5471evm/ - cd - + tools/configure.sh c5471evm/ 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 6e2086f8e13..ce9d9be82a0 100644 --- a/configs/clicker2-stm32/README.txt +++ b/configs/clicker2-stm32/README.txt @@ -160,9 +160,7 @@ Configurations Each Clicker2 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh clicker2-stm32/ - cd - + tools/configure.sh clicker2-stm32/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/cloudctrl/README.txt b/configs/cloudctrl/README.txt index 486b2693c0a..e3f7a85210d 100644 --- a/configs/cloudctrl/README.txt +++ b/configs/cloudctrl/README.txt @@ -468,9 +468,7 @@ Configurations Each Cloudctrl configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh shenzhou/ - cd - + tools/configure.sh shenzhou/ Where is one of the following: @@ -545,14 +543,12 @@ Where is one of the following: 1. Intall the nxwm configuration - $ cd ~/nuttx-code/tools - $ ./configure.sh shenzhou/nxwm + $ cd ~/nuttx-code + $ tools/configure.sh shenzhou/nxwm 2. Make the build context (only) - $ cd .. $ make context - ... 3. Install the nxwm unit test diff --git a/configs/demo9s12ne64/README.txt b/configs/demo9s12ne64/README.txt index b1b97145efd..7ab6261482b 100644 --- a/configs/demo9s12ne64/README.txt +++ b/configs/demo9s12ne64/README.txt @@ -121,8 +121,7 @@ NuttX Buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh demo9s12nec64/ + tools/configure.sh demo9s12nec64/ 2. Download the latest buildroot package into @@ -364,9 +363,7 @@ Common Configuration Notes 1. Each Freescale HCS12 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh demo9s12nec64/ - cd - + tools/configure.sh demo9s12nec64/ 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 b0c0ac557f7..0efdca5dfba 100644 --- a/configs/dk-tm4c129x/README.txt +++ b/configs/dk-tm4c129x/README.txt @@ -656,9 +656,7 @@ Configurations Each DK-TM4C129X configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh dk-tm4c129x/ - cd - + tools/configure.sh dk-tm4c129x/ Where is one of the following: diff --git a/configs/ea3131/README.txt b/configs/ea3131/README.txt index f79a7ca9efa..99a05b26600 100644 --- a/configs/ea3131/README.txt +++ b/configs/ea3131/README.txt @@ -150,8 +150,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh ea3131/ + tools/configure.sh ea3131/ 2. Download the latest buildroot package into @@ -206,8 +205,7 @@ Image Format Then, to build the NuttX binary ready to load with the bootloader, just following these steps: - - cd tools/ # Configure Nuttx - - ./configure.sh ea3131/nsh # (using the nsh configuration for this example) + - tools/configure.sh ea3131/nsh # (using the nsh configuration for this example) - cd .. # Set up environment - make # Make NuttX. This will produce nuttx.bin - mklpc.sh # Make the bootloader binary (nuttx.lpc) @@ -597,9 +595,7 @@ Common Configuration Notes 1. Each EA3131 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh ea3131/ - cd - + tools/configure.sh ea3131/ 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 eae46d2e3f1..3a6c80b6365 100644 --- a/configs/ea3152/README.txt +++ b/configs/ea3152/README.txt @@ -149,8 +149,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh ea3152/ + tools/configure.sh ea3152/ 2. Download the latest buildroot package into @@ -205,11 +204,10 @@ Image Format Then, to build the NuttX binary ready to load with the bootloader, just following these steps: - - cd tools/ # Configure Nuttx - - ./configure.sh ea3152/ostest # (using the ostest configuration for this example) - - cd .. # Set up environment - - make # Make NuttX. This will produce nuttx.bin - - mklpc.sh # Make the bootloader binary (nuttx.lpc) + - tools/configure.sh ea3152/ostest # (using the ostest configuration for this example) + - cd .. # Set up environment + - make # Make NuttX. This will produce nuttx.bin + - mklpc.sh # Make the bootloader binary (nuttx.lpc) NOTES: @@ -400,9 +398,7 @@ Configurations Each EA3152 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh ea3152/ - cd - + tools/configure.sh ea3152/ Where is one of the following: diff --git a/configs/eagle100/README.txt b/configs/eagle100/README.txt index 8c379b10dfe..6e19c1159b0 100644 --- a/configs/eagle100/README.txt +++ b/configs/eagle100/README.txt @@ -193,9 +193,7 @@ Common Configuration Notes 1. Each Eagle-100 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh eagle100/ - cd - + tools/configure.sh eagle100/ 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 bd90ad93509..60df7277f8e 100644 --- a/configs/efm32-g8xx-stk/README.txt +++ b/configs/efm32-g8xx-stk/README.txt @@ -231,9 +231,7 @@ CONFIGURATIONS Each EFM32 Gecko Starter Kit configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh efm32-g8xx-stk/ - cd - + tools/configure.sh efm32-g8xx-stk/ 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 ec19a65f53f..8d7d6fc56e6 100644 --- a/configs/efm32gg-stk3700/README.txt +++ b/configs/efm32gg-stk3700/README.txt @@ -183,9 +183,7 @@ 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 - + tools/configure.sh efm32gg-stk3700/ 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 8e4b3da0004..8f7b3645c95 100644 --- a/configs/ekk-lm3s9b96/README.txt +++ b/configs/ekk-lm3s9b96/README.txt @@ -197,9 +197,7 @@ Configurations Each Stellaris EKK-LM3S9b96 Evaluation Kit configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh ekk-lm3s9b96/ - cd - + tools/configure.sh ekk-lm3s9b96/ Where is one of the following: diff --git a/configs/esp32-core/README.txt b/configs/esp32-core/README.txt index 782bed7232a..a0d606941ed 100644 --- a/configs/esp32-core/README.txt +++ b/configs/esp32-core/README.txt @@ -575,9 +575,7 @@ Configurations Each ESP32 core configuration is maintained in sub-directories and can be selected as follow: - cd tools - ./configure.sh esp32-core/ - cd - + tools/configure.sh esp32-core/ make oldconfig Before building, make sure the PATH environment variable includes the diff --git a/configs/ez80f910200kitg/README.txt b/configs/ez80f910200kitg/README.txt index 635992b5d3a..0872dd52af4 100644 --- a/configs/ez80f910200kitg/README.txt +++ b/configs/ez80f910200kitg/README.txt @@ -78,9 +78,7 @@ Variations on the basic ez80f910200kitg configuration are maintained in subdirectories. To configure any specific configuration, do the following steps: - cd /tools - ./configure.sh ez80f910200kitg/ - cd + tools/configure.sh ez80f910200kitg/ make Where is the specific board configuration that you diff --git a/configs/ez80f910200zco/README.txt b/configs/ez80f910200zco/README.txt index a1c6ce5777b..08d809cfa30 100644 --- a/configs/ez80f910200zco/README.txt +++ b/configs/ez80f910200zco/README.txt @@ -82,9 +82,7 @@ Common Configuration Notes in subdirectories. To configure any specific configuration, do the following steps: - cd /tools - ./configure.sh ez80f910200zco/ - cd + tools/configure.sh ez80f910200zco/ make Where is the specific board configuration that you diff --git a/configs/fire-stm32v2/README.txt b/configs/fire-stm32v2/README.txt index dbcf912a22e..575c07d7fc0 100644 --- a/configs/fire-stm32v2/README.txt +++ b/configs/fire-stm32v2/README.txt @@ -563,9 +563,7 @@ Configurations Each M3 Wildfire configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh fire-stm32v2/ - cd - + tools/configure.sh fire-stm32v2/ Where is one of the following: diff --git a/configs/freedom-k64f/README.txt b/configs/freedom-k64f/README.txt index 9e164040e21..c706e95499a 100644 --- a/configs/freedom-k64f/README.txt +++ b/configs/freedom-k64f/README.txt @@ -818,9 +818,7 @@ Configurations Each Freedom K64F configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh freedom-k64f/ - cd - + tools/configure.sh freedom-k64f/ Where is one of the following: diff --git a/configs/freedom-k66f/README.txt b/configs/freedom-k66f/README.txt index 632b662f127..50ff26bd4a7 100644 --- a/configs/freedom-k66f/README.txt +++ b/configs/freedom-k66f/README.txt @@ -825,9 +825,7 @@ Configurations Each Freedom K66F configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh freedom-K66F/ - cd - + tools/configure.sh freedom-K66F/ Where is one of the following: diff --git a/configs/freedom-kl25z/README.txt b/configs/freedom-kl25z/README.txt index b043df61448..e69ec67d9d6 100644 --- a/configs/freedom-kl25z/README.txt +++ b/configs/freedom-kl25z/README.txt @@ -44,8 +44,7 @@ NuttX Buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh freedom-kl25z/ + tools/configure.sh freedom-kl25z/ 2. Download the latest buildroot package into @@ -282,9 +281,7 @@ Configurations Each FREEDOM-KL25Z configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh freedom-kl25z/ - cd - + tools/configure.sh freedom-kl25z/ 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 e23c202ac6f..073316f50a8 100644 --- a/configs/freedom-kl26z/README.txt +++ b/configs/freedom-kl26z/README.txt @@ -44,8 +44,7 @@ NuttX Buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh freedom-kl26z/ + tools/configure.sh freedom-kl26z/ 2. Download the latest buildroot package into @@ -260,9 +259,7 @@ Configurations Each FREEDOM-KL26Z configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh freedom-kl26z/ - cd - + tools/configure.sh freedom-kl26z/ 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 6726c459928..e0ed4cf7210 100644 --- a/configs/hymini-stm32v/README.txt +++ b/configs/hymini-stm32v/README.txt @@ -357,9 +357,7 @@ NOTES: Each HY-MiniSTM32V configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh hymini-stm32v/ - cd - + tools/configure.sh hymini-stm32v/ Where is one of the following: diff --git a/configs/indium-f7/README.txt b/configs/indium-f7/README.txt index 236bcc0df26..11830ea9402 100644 --- a/configs/indium-f7/README.txt +++ b/configs/indium-f7/README.txt @@ -54,7 +54,7 @@ Basic configuration & build steps different from the default in your PATH variable). - Configures nuttx creating .config file in the nuttx directory. - $ cd tools && ./configure.sh indium-f7/f7nn-nsh && cd .. + $ tools/configure.sh indium-f7/f7nn-nsh - Refreshes the .config file with the latest available configurations. $ make oldconfig - Select the features you want in the build. @@ -202,8 +202,8 @@ f7xx-nsh: see additional README.txt files in the NuttX tools repository. b. If this is the intall configuration then Execute - 'cd tools && ./configure.sh indium-f7/nsh && cd ..' - in nuttx/ in order to start configuration process. + 'tools/configure.sh indium-f7/nsh' in nuttx/ in order to start the + configuration process. Caution: Doing this step more than once will overwrite .config with the contents of the indium-f7/nsh/defconfig file. @@ -264,8 +264,8 @@ f7xx-evalos: see additional README.txt files in the NuttX tools repository. b. If this is the intall configuration then Execute - 'cd tools && ./configure.sh indium-f7/evalos && cd ..' - in nuttx/ in order to start configuration process. + 'tools/configure.sh indium-f7/evalos' in nuttx/ in order to start + configuration process. Caution: Doing this step more than once will overwrite .config with the contents of the indium-f7/evalos/defconfig file. diff --git a/configs/kwikstik-k40/README.txt b/configs/kwikstik-k40/README.txt index be1c79b041a..91b38cc909d 100644 --- a/configs/kwikstik-k40/README.txt +++ b/configs/kwikstik-k40/README.txt @@ -313,9 +313,7 @@ Configurations Each KwikStik-K40 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh kwikstik-k40/ - cd - + tools/configure.sh kwikstik-k40/ Where is one of the following: diff --git a/configs/launchxl-tms57004/README.txt b/configs/launchxl-tms57004/README.txt index cbcb01eb8b1..86057e31cc3 100644 --- a/configs/launchxl-tms57004/README.txt +++ b/configs/launchxl-tms57004/README.txt @@ -172,9 +172,7 @@ Configurations Each LaunchXL-TMS50704 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh launchxl-tms57004/ - cd - + tools/configure.sh launchxl-tms57004/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/lincoln60/README.txt b/configs/lincoln60/README.txt index d90a11e6a00..23f147c7c3b 100644 --- a/configs/lincoln60/README.txt +++ b/configs/lincoln60/README.txt @@ -248,9 +248,7 @@ host operations. To make these modifications, do the following: 1. First configure to build the NSH configuration from the top-level NuttX directory: - cd tools ./configure lincoln60/nsh - cd .. 2. Then edit the top-level .config file to enable USB host. Make the following changes: @@ -277,9 +275,7 @@ Configurations Each Lincoln 60 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lincoln60/ - cd - + tools/configure.sh lincoln60/ Where is one of the following: diff --git a/configs/lm3s6432-s2e/README.txt b/configs/lm3s6432-s2e/README.txt index 3a29a55d35e..3d36afe085c 100644 --- a/configs/lm3s6432-s2e/README.txt +++ b/configs/lm3s6432-s2e/README.txt @@ -202,9 +202,7 @@ Configurations Each Stellaris MDL-S2E Reference Design configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lm3s6432-s2e/ - cd - + tools/configure.sh lm3s6432-s2e/ Where is one of the following: diff --git a/configs/lm3s6965-ek/README.txt b/configs/lm3s6965-ek/README.txt index 1eb8346ed78..f6a4d1dc5b2 100644 --- a/configs/lm3s6965-ek/README.txt +++ b/configs/lm3s6965-ek/README.txt @@ -340,9 +340,7 @@ Configurations Each Stellaris LM3S6965 Evaluation Kit configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lm3s6965-ek/ - cd - + tools/configure.sh lm3s6965-ek/ Where is one of the following: diff --git a/configs/lm3s8962-ek/README.txt b/configs/lm3s8962-ek/README.txt index aec451404fb..26408a5ddfd 100644 --- a/configs/lm3s8962-ek/README.txt +++ b/configs/lm3s8962-ek/README.txt @@ -260,9 +260,7 @@ Configurations Each Stellaris LM3S8962 Evaluation Kit configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lm3s8962-ek/ - cd - + tools/configure.sh lm3s8962-ek/ Where is one of the following: diff --git a/configs/lm4f120-launchpad/README.txt b/configs/lm4f120-launchpad/README.txt index f4e93aec067..b6cbdb37711 100644 --- a/configs/lm4f120-launchpad/README.txt +++ b/configs/lm4f120-launchpad/README.txt @@ -469,9 +469,7 @@ Configurations Each LM4F120 LaunchPad configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lm4f120-launchpad/ - cd - + tools/configure.sh lm4f120-launchpad/ Where is one of the following: diff --git a/configs/lpc4330-xplorer/README.txt b/configs/lpc4330-xplorer/README.txt index 7477f8e40eb..05eda5cf2ac 100644 --- a/configs/lpc4330-xplorer/README.txt +++ b/configs/lpc4330-xplorer/README.txt @@ -629,9 +629,7 @@ Configurations Each LPC4330-Xplorer configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lpc4330-xplorer/ - cd - + tools/configure.sh lpc4330-xplorer/ Where is one of the following: diff --git a/configs/lpc4337-ws/README.txt b/configs/lpc4337-ws/README.txt index e55ccf876d5..e60a035e1fd 100644 --- a/configs/lpc4337-ws/README.txt +++ b/configs/lpc4337-ws/README.txt @@ -668,9 +668,7 @@ Configurations Each LPC4337-ws configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh LPC4337-ws/ - cd - + tools/configure.sh LPC4337-ws/ Where is one of the following: diff --git a/configs/lpc4357-evb/README.txt b/configs/lpc4357-evb/README.txt index 0b1a7cbce63..cc8fe714d0d 100644 --- a/configs/lpc4357-evb/README.txt +++ b/configs/lpc4357-evb/README.txt @@ -665,9 +665,7 @@ Configurations Each LPC4357-EVB configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lpc4357-evb/ - cd - + tools/configure.sh lpc4357-evb/ Where is one of the following: diff --git a/configs/lpc4370-link2/README.txt b/configs/lpc4370-link2/README.txt index 573ed26d254..5ebc1a9daf0 100644 --- a/configs/lpc4370-link2/README.txt +++ b/configs/lpc4370-link2/README.txt @@ -668,9 +668,7 @@ Configurations Each LPC4370-Link2 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh LPC4370-Link2/ - cd - + tools/configure.sh LPC4370-Link2/ Where is one of the following: diff --git a/configs/lpcxpresso-lpc1115/README.txt b/configs/lpcxpresso-lpc1115/README.txt index 7780bb9ec73..e168415e2af 100644 --- a/configs/lpcxpresso-lpc1115/README.txt +++ b/configs/lpcxpresso-lpc1115/README.txt @@ -508,9 +508,7 @@ Configurations Each LPCXpresso configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lpcxpresso-lpc1115/ - cd - + tools/configure.sh lpcxpresso-lpc1115/ Where is one of the following: diff --git a/configs/lpcxpresso-lpc1768/README.txt b/configs/lpcxpresso-lpc1768/README.txt index 319ad11a133..9f8f4271a10 100644 --- a/configs/lpcxpresso-lpc1768/README.txt +++ b/configs/lpcxpresso-lpc1768/README.txt @@ -560,9 +560,7 @@ Configurations Each LPCXpresso configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh lpcxpresso-lpc1768/ - cd - + tools/configure.sh lpcxpresso-lpc1768/ Where is one of the following: diff --git a/configs/maple/README.txt b/configs/maple/README.txt index 076f7acb82f..6e3fe9f7ec9 100644 --- a/configs/maple/README.txt +++ b/configs/maple/README.txt @@ -108,9 +108,7 @@ Configurations Each Maple configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh maple/ - cd - + tools/configure.sh maple/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/mbed/README.txt b/configs/mbed/README.txt index 2ed02719f27..736941b24c9 100644 --- a/configs/mbed/README.txt +++ b/configs/mbed/README.txt @@ -211,9 +211,7 @@ USB Host Configuration 1. First configure to build the NSH configuration from the top-level NuttX directory: - cd tools ./configure mbed/nsh - cd .. 2. Then edit the top-level .config file to enable USB host. Make the following changes using 'make menuconfig': @@ -250,9 +248,7 @@ Configurations Each mbed configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh mbed/ - cd - + tools/configure.sh mbed/ Where is one of the mbed subdirectories described in the following paragraph. diff --git a/configs/mcb1700/README.txt b/configs/mcb1700/README.txt index 5abfa00c55c..b0e34a9ed8c 100644 --- a/configs/mcb1700/README.txt +++ b/configs/mcb1700/README.txt @@ -212,9 +212,7 @@ USB Host Configuration 1. First configure to build the NSH configuration from the top-level NuttX directory: - cd tools ./configure mcb1700/nsh - cd .. 2. Then edit the top-level .config file to enable USB host. Make the following changes using 'make menuconfig': @@ -251,9 +249,7 @@ Configurations Each mcb1700 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh mcb1700/ - cd - + tools/configure.sh mcb1700/ Where is one of the mcb1700 subdirectories described in the following paragraph. diff --git a/configs/mcu123-lpc214x/README.txt b/configs/mcu123-lpc214x/README.txt index adec6ffeaf3..89cf5d44f30 100644 --- a/configs/mcu123-lpc214x/README.txt +++ b/configs/mcu123-lpc214x/README.txt @@ -89,8 +89,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh eagle100/ + tools/configure.sh eagle100/ 2. Download the latest buildroot package into @@ -316,9 +315,7 @@ Configurations 1. Each NXP LPC214x configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh mcu123-lpc214x/ - cd - + tools/configure.sh mcu123-lpc214x/ 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 b252ef207d4..a1de34a219c 100644 --- a/configs/micropendous3/README.txt +++ b/configs/micropendous3/README.txt @@ -287,8 +287,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh micropendous3/ + tools/configure.sh micropendous3/ NOTE: you also must copy avr-libc header files into the NuttX include directory with command perhaps like: @@ -509,9 +508,7 @@ Common Configuration Notes 1. Each Micropendous3 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh micropendous3/ - cd - + tools/configure.sh micropendous3/ 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 ba8785879e4..773613a7b56 100644 --- a/configs/mikroe-stm32f4/README.txt +++ b/configs/mikroe-stm32f4/README.txt @@ -475,9 +475,7 @@ Configurations Each Mikroe-STM32F4 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh mikroe-stm32f4/ - cd - + tools/configure.sh mikroe-stm32f4/ 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 dc71ee19331..390541a7a8c 100644 --- a/configs/mirtoo/README.txt +++ b/configs/mirtoo/README.txt @@ -838,9 +838,7 @@ Configurations Each PIC32MX configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh mirtoo/ - cd - + tools/configure.sh mirtoo/ Where is one of the following: diff --git a/configs/misoc/README.txt b/configs/misoc/README.txt index b485dd1906c..e2aadb91739 100644 --- a/configs/misoc/README.txt +++ b/configs/misoc/README.txt @@ -20,8 +20,7 @@ Buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh misoc/ + tools/configure.sh misoc/ make oldconfig context 2. Clone the latest buildroot package into /buildroot diff --git a/configs/moteino-mega/README.txt b/configs/moteino-mega/README.txt index 71600becaa5..d9334f950e1 100644 --- a/configs/moteino-mega/README.txt +++ b/configs/moteino-mega/README.txt @@ -248,9 +248,7 @@ Common Configuration Notes 1. Each MoteinoMEGA configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh moteino-mega/ - cd - + tools/configure.sh moteino-mega/ 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 3f532cb7e3e..aba98ed3be2 100644 --- a/configs/ne64badge/README.txt +++ b/configs/ne64badge/README.txt @@ -228,8 +228,7 @@ NuttX Buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh ne64badge/ + tools/configure.sh ne64badge/ 2. Download the latest buildroot package into @@ -471,9 +470,7 @@ Common Configuration Notes 1. Each Freescale HCS12 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh ne64badge/ - cd - + tools/configure.sh ne64badge/ 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 09a0ebfa23a..7f9b5e4456d 100644 --- a/configs/nr5m100-nexys4/README.txt +++ b/configs/nr5m100-nexys4/README.txt @@ -232,9 +232,7 @@ Configurations Each nr5m100-nexys4 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh nr5m100-nexys4/ - cd - + tools/configure.sh nr5m100-nexys4/ Where is one of the following: diff --git a/configs/nrf52-pca10040/README.txt b/configs/nrf52-pca10040/README.txt index 3d2b3bc6f1d..83452680bd0 100644 --- a/configs/nrf52-pca10040/README.txt +++ b/configs/nrf52-pca10040/README.txt @@ -90,9 +90,7 @@ Configurations Each PCA10040 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh nrf52-pca10040/ - cd - + tools/configure.sh nrf52-pca10040/ Where is one of the following: diff --git a/configs/ntosd-dm320/README.txt b/configs/ntosd-dm320/README.txt index 5c2af4b5ca0..96c7adbe870 100644 --- a/configs/ntosd-dm320/README.txt +++ b/configs/ntosd-dm320/README.txt @@ -166,8 +166,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in nuttx. - cd tools - ./configure.sh ntosd-dm320/ + tools/configure.sh ntosd-dm320/ 2. Download the latest buildroot package into @@ -279,9 +278,7 @@ Common Configuration Notes 1. Each Neuros OSD configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh ntosd-dm320/ - cd - + tools/configure.sh ntosd-dm320/ Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/nucleo-144/README.txt b/configs/nucleo-144/README.txt index cf6ac8da624..fdccb3bc2de 100644 --- a/configs/nucleo-144/README.txt +++ b/configs/nucleo-144/README.txt @@ -205,7 +205,7 @@ Basic configuration & build steps different from the default in your PATH variable). - Configures nuttx creating .config file in the nuttx directory. - $ cd tools && ./configure.sh nucleo-f746zg/nsh && cd .. + $ tools/configure.sh nucleo-f746zg/nsh - Refreshes the .config file with the latest available configurations. $ make oldconfig - Select the features you want in the build. diff --git a/configs/nucleo-f072rb/README.txt b/configs/nucleo-f072rb/README.txt index a7e39499b96..5f9a494cea3 100644 --- a/configs/nucleo-f072rb/README.txt +++ b/configs/nucleo-f072rb/README.txt @@ -209,9 +209,7 @@ Configurations Each configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh nucleo-f072rb/ - cd - + tools/configure.sh nucleo-f072rb/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/nucleo-f091rc/README.txt b/configs/nucleo-f091rc/README.txt index 0937488eecc..8c3fc3bd353 100644 --- a/configs/nucleo-f091rc/README.txt +++ b/configs/nucleo-f091rc/README.txt @@ -195,9 +195,7 @@ Configurations Each configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh nucleo-f091rc/ - cd - + tools/configure.sh nucleo-f091rc/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/nucleo-f4x1re/README.txt b/configs/nucleo-f4x1re/README.txt index e74a2ecb7de..f7283c909d0 100644 --- a/configs/nucleo-f4x1re/README.txt +++ b/configs/nucleo-f4x1re/README.txt @@ -260,7 +260,7 @@ NuttX EABI "buildroot" Toolchain 1. You must have already configured Nuttx in /nuttx. - $ (cd tools; ./configure.sh nucleo-f4x1re/f401-nsh) + $ tools/configure.sh nucleo-f4x1re/f401-nsh $ make qconfig $ V=1 make context all 2>&1 | tee mout @@ -305,8 +305,7 @@ NXFLAT Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh lpcxpresso-lpc1768/ + tools/configure.sh lpcxpresso-lpc1768/ 2. Download the latest buildroot package into diff --git a/configs/nucleo-l432kc/README.txt b/configs/nucleo-l432kc/README.txt index a922e176386..a55a1ed0e08 100644 --- a/configs/nucleo-l432kc/README.txt +++ b/configs/nucleo-l432kc/README.txt @@ -273,8 +273,7 @@ NXFLAT Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh lpcxpresso-lpc1768/ + tools/configure.sh lpcxpresso-lpc1768/ 2. Download the latest buildroot package into diff --git a/configs/nucleo-l452re/README.txt b/configs/nucleo-l452re/README.txt index 54f05051ee5..8ac1c7ac486 100644 --- a/configs/nucleo-l452re/README.txt +++ b/configs/nucleo-l452re/README.txt @@ -201,9 +201,7 @@ Configurations Each configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh nucleo-l452re/ - cd - + tools/configure.sh nucleo-l452re/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/nucleo-l476rg/README.txt b/configs/nucleo-l476rg/README.txt index 0f971123c18..b1a1f9b6ac6 100644 --- a/configs/nucleo-l476rg/README.txt +++ b/configs/nucleo-l476rg/README.txt @@ -285,8 +285,7 @@ NXFLAT Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh lpcxpresso-lpc1768/ + tools/configure.sh lpcxpresso-lpc1768/ 2. Download the latest buildroot package into diff --git a/configs/nutiny-nuc120/README.txt b/configs/nutiny-nuc120/README.txt index 90fabba39c2..8da136768df 100644 --- a/configs/nutiny-nuc120/README.txt +++ b/configs/nutiny-nuc120/README.txt @@ -45,8 +45,7 @@ NuttX Buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh nutiny-nuc120/ + tools/configure.sh nutiny-nuc120/ 2. Download the latest buildroot package into @@ -268,9 +267,7 @@ Configurations Each NuTiny-SDK-NUC120 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh nutiny-nuc120/ - cd - + tools/configure.sh 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 6256fb82999..b861b2459fb 100644 --- a/configs/olimex-efm32g880f128-stk/README.txt +++ b/configs/olimex-efm32g880f128-stk/README.txt @@ -134,9 +134,7 @@ Configurations Each EFM32G880F128-STK configuration is maintained in a sub-director and can be selected as follow: - cd tools - ./configure.sh olimex-efm32g880f128-stk/ - cd - + tools/configure.sh 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 9a4644abc73..9aff9821b31 100644 --- a/configs/olimex-lpc-h3131/README.txt +++ b/configs/olimex-lpc-h3131/README.txt @@ -152,8 +152,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh olimex-lpc-h3131/ + tools/configure.sh olimex-lpc-h3131/ 2. Download the latest buildroot package into @@ -254,8 +253,7 @@ Image Format Then, to build the NuttX binary ready to load with the bootloader, just following these steps: - - cd tools/ # Configure Nuttx - - ./configure.sh olimex-lpc-h3131/ostest # (using the ostest configuration for this example) + - tools/configure.sh olimex-lpc-h3131/ostest # (using the ostest configuration for this example) - cd .. # Set up environment - make # Make NuttX. This will produce nuttx.bin - mklpc.sh # Make the bootloader binary (nuttx.lpc) @@ -494,9 +492,7 @@ Configurations Each LPC-H3131 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh olimex-lpc-h3131/ - cd - + tools/configure.sh olimex-lpc-h3131/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/olimex-lpc1766stk/README.txt b/configs/olimex-lpc1766stk/README.txt index 63b7de124e1..f43a2fa5d9a 100644 --- a/configs/olimex-lpc1766stk/README.txt +++ b/configs/olimex-lpc1766stk/README.txt @@ -631,9 +631,7 @@ USB host operations. To make these modifications, do the following: 1. First configure to build the NSH configuration from the top-level NuttX directory: - cd tools ./configure olimex-lpc1766stk/nsh - cd .. 2. Modify the top-level .config file to enable USB host using: @@ -673,9 +671,7 @@ Common Configuration Notes 1. Each Olimex LPC1766-STK configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh olimex-lpc1766stk/ - cd - + tools/configure.sh olimex-lpc1766stk/ 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 f7c2f6ce8e8..3129d73a3ab 100644 --- a/configs/olimex-stm32-p407/README.txt +++ b/configs/olimex-stm32-p407/README.txt @@ -238,9 +238,7 @@ Information Common to All Configurations Each Olimex STM32-P407 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh olimex-stm32-p407/ - cd - + tools/configure.sh olimex-stm32-p407/ Where is one of the configuration sub-directories listed in the following section. diff --git a/configs/olimex-strp711/README.txt b/configs/olimex-strp711/README.txt index 572c2c6d04b..68345b94dca 100644 --- a/configs/olimex-strp711/README.txt +++ b/configs/olimex-strp711/README.txt @@ -173,8 +173,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in nuttx. - cd tools - ./configure.sh olimex-strp711/ + tools/configure.sh olimex-strp711/ 2. Download the latest buildroot package into @@ -371,9 +370,7 @@ Common Configuration Notes: 1. Each Olimex STRP711 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh olimex-strp711/ - cd - + tools/configure.sh olimex-strp711/ Where is one of the configuration sub-directories described in the following paragraph. diff --git a/configs/pcblogic-pic32mx/README.txt b/configs/pcblogic-pic32mx/README.txt index aa8ffbd0748..a254778b638 100644 --- a/configs/pcblogic-pic32mx/README.txt +++ b/configs/pcblogic-pic32mx/README.txt @@ -547,9 +547,7 @@ Configurations Each PIC32MX configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh pcblogic-pic32mx/ - cd - + tools/configure.sh pcblogic-pic32mx/ Where is one of the following sub-directories. diff --git a/configs/photon/README.txt b/configs/photon/README.txt index 4b761752273..4d10743c74b 100644 --- a/configs/photon/README.txt +++ b/configs/photon/README.txt @@ -32,12 +32,7 @@ Selecting the Photon board on NuttX 2) Enter inside nuttx/tools and configure to use the Photon board: $ cd nuttx - $ cd tools - $ ./configure.sh photon/wlan - - Now please return to root of nuttx/ directory: - - $ cd .. + $ tools/configure.sh photon/wlan Configuring NuttX to use your Wireless Router (aka Access Point) ================================================================ diff --git a/configs/pic32mx-starterkit/README.txt b/configs/pic32mx-starterkit/README.txt index be4cd8480ca..eb75f17b6fc 100644 --- a/configs/pic32mx-starterkit/README.txt +++ b/configs/pic32mx-starterkit/README.txt @@ -1012,9 +1012,7 @@ Configurations Each PIC32MX configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh pic32mx-starterkit/ - cd - + tools/configure.sh pic32mx-starterkit/ Where is one of the following: diff --git a/configs/pic32mx7mmb/README.txt b/configs/pic32mx7mmb/README.txt index 18cf3671408..6f896131777 100644 --- a/configs/pic32mx7mmb/README.txt +++ b/configs/pic32mx7mmb/README.txt @@ -594,9 +594,7 @@ Configurations Each PIC32MX configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh pic32mx7mmb/ - cd - + tools/configure.sh pic32mx7mmb/ Where is one of the following: diff --git a/configs/qemu-i486/README.txt b/configs/qemu-i486/README.txt index bcc0da5ef48..096960f8c37 100644 --- a/configs/qemu-i486/README.txt +++ b/configs/qemu-i486/README.txt @@ -118,8 +118,7 @@ Buildroot Instructions 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh qemu-i486/ + tools/configure.sh qemu-i486/ 2. Download the latest buildroot package into @@ -161,9 +160,7 @@ Common Configuration Notes 1. Each Qemu-i486 Web Server configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh qemu-i486/ - cd - + tools/configure.sh qemu-i486/ 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 f16dc761139..030c78f89cb 100644 --- a/configs/sabre-6quad/README.txt +++ b/configs/sabre-6quad/README.txt @@ -633,9 +633,7 @@ Information Common to All Configurations Each Sabre-6Quad configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sabre-6quad/ - cd - + tools/configure.sh sabre-6quad/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/sam3u-ek/README.txt b/configs/sam3u-ek/README.txt index 4f63108cbd0..076ebec019d 100644 --- a/configs/sam3u-ek/README.txt +++ b/configs/sam3u-ek/README.txt @@ -212,9 +212,7 @@ Configurations Each SAM3U-EK configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sam3u-ek/ - cd - + tools/configure.sh sam3u-ek/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -275,7 +273,7 @@ Configurations This re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. @@ -496,14 +494,11 @@ Configurations 1. Intall the nxwm configuration - $ cd ~/nuttx-git/nuttx/tools - $ ./configure.sh sam3u-ek/nxwm + $ tools/configure.sh sam3u-ek/nxwm 2. Make the build context (only) - $ cd .. $ make context - ... 3. Install the nxwm unit test diff --git a/configs/sam4e-ek/README.txt b/configs/sam4e-ek/README.txt index e676d794652..9ec33a15ab4 100644 --- a/configs/sam4e-ek/README.txt +++ b/configs/sam4e-ek/README.txt @@ -1036,9 +1036,7 @@ Configurations Each SAM4E-EK configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sam4e-ek/ - cd - + tools/configure.sh sam4e-ek/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -1093,7 +1091,7 @@ Configurations This re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam4e-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam4e-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. @@ -1423,14 +1421,11 @@ Configurations 1. Install the nxwm configuration - $ cd ~/nuttx-git/nuttx/tools - $ ./configure.sh sam4e-ek/nxwm + $ tools/configure.sh sam4e-ek/nxwm 2. Make the build context (only) - $ cd .. $ make context - ... 3. Install the nxwm unit test diff --git a/configs/sam4l-xplained/README.txt b/configs/sam4l-xplained/README.txt index 7178b3e31df..ba4982bde62 100644 --- a/configs/sam4l-xplained/README.txt +++ b/configs/sam4l-xplained/README.txt @@ -389,9 +389,7 @@ Configurations Each SAM4L Xplained Pro configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sam4l-xplained/ - cd - + tools/configure.sh sam4l-xplained/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -471,7 +469,7 @@ Configurations This re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. diff --git a/configs/sam4s-xplained-pro/README.txt b/configs/sam4s-xplained-pro/README.txt index 6b62f3fcdcd..a0cc4a2cd61 100644 --- a/configs/sam4s-xplained-pro/README.txt +++ b/configs/sam4s-xplained-pro/README.txt @@ -280,9 +280,7 @@ Configurations Each SAM4S Xplained configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.shsam4s-xplained-pro/ - cd - + tools/configure.shsam4s-xplained-pro/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -353,7 +351,7 @@ Configurations This re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. diff --git a/configs/sam4s-xplained/README.txt b/configs/sam4s-xplained/README.txt index 9dd7f85cfad..a3d24fd2296 100644 --- a/configs/sam4s-xplained/README.txt +++ b/configs/sam4s-xplained/README.txt @@ -275,9 +275,7 @@ Configurations Each SAM4S Xplained configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.shsam4s-xplained/ - cd - + tools/configure.shsam4s-xplained/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -348,7 +346,7 @@ Configurations This re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. diff --git a/configs/sama5d2-xult/README.txt b/configs/sama5d2-xult/README.txt index e1733553568..361e74a9a9a 100644 --- a/configs/sama5d2-xult/README.txt +++ b/configs/sama5d2-xult/README.txt @@ -74,9 +74,7 @@ REVISIT: Unverified, cloned text from the SAMA5D4-EK README.txt the dramboot configuration and setup the PATH variable in order to do the build: - cd tools - ./configure.sh sama5d2-xult/dramboot - cd - + tools/configure.sh sama5d2-xult/dramboot Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -180,9 +178,7 @@ REVISIT: Unverified, cloned text from the SAMA5D4-EK README.txt the AT25BOOT configuration and setup the PATH variable in order to do the build: - cd tools - ./configure.sh sama5d2-xult/at25boot - cd - + tools/configure.sh sama5d2-xult/at25boot Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -909,9 +905,7 @@ Configurations Each SAMA5D2-XULT configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sama5d2-xult/ - cd - + tools/configure.sh sama5d2-xult/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/sama5d3-xplained/README.txt b/configs/sama5d3-xplained/README.txt index 8711ba449b6..0d3ab36cbcc 100644 --- a/configs/sama5d3-xplained/README.txt +++ b/configs/sama5d3-xplained/README.txt @@ -189,8 +189,7 @@ NuttX EABI "buildroot" Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh sama5d3-xplained/ + tools/configure.sh sama5d3-xplained/ 2. Download the latest buildroot package into @@ -240,8 +239,7 @@ NXFLAT Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh sama5d3-xplained/ + tools/configure.sh sama5d3-xplained/ 2. Download the latest buildroot package into @@ -2978,9 +2976,7 @@ Configurations Each SAMA5D3-Xplained configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sama5d3-xplained/ - cd - + tools/configure.sh sama5d3-xplained/ Before building, make sure that the PATH environment variable include the correct path to the directory than holds your toolchain binaries. diff --git a/configs/sama5d3x-ek/README.txt b/configs/sama5d3x-ek/README.txt index 26007c8f921..f45d2fb1e8d 100644 --- a/configs/sama5d3x-ek/README.txt +++ b/configs/sama5d3x-ek/README.txt @@ -211,8 +211,7 @@ NuttX EABI "buildroot" Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh sama5d3x-ek/ + tools/configure.sh sama5d3x-ek/ 2. Download the latest buildroot package into @@ -262,8 +261,7 @@ NXFLAT Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh sama5d3x-ek/ + tools/configure.sh sama5d3x-ek/ 2. Download the latest buildroot package into @@ -369,9 +367,7 @@ Creating and Using NORBOOT the norboot configuration and setup the PATH variable in order to do the build: - cd tools - ./configure.sh sama5d3x-ek/ - cd - + tools/configure.sh sama5d3x-ek/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -401,9 +397,7 @@ Creating and Using NORBOOT cd make distclean # Remove the norboot configuration - cd tools - ./configure.sh sama5d3x-ek/nsh # Establish the NSH configuration - cd - + tools/configure.sh sama5d3x-ek/nsh # Establish the NSH configuration make # Build the NSH configuration Then use SAM-BA to write the nuttx.bin binary into NOR FLASH. This @@ -3301,9 +3295,7 @@ Configurations Each SAMA5D3x-EK configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sama5d3x-ek/ - cd - + tools/configure.sh sama5d3x-ek/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -3791,14 +3783,11 @@ Configurations 1. Install the nxwm configuration - $ cd ~/nuttx-git/nuttx/tools - $ ./configure.sh sama5d3x-ek/nxwm + $ tools/configure.sh sama5d3x-ek/nxwm 2. Make the build context (only) - $ cd .. $ make context - ... 3. Install the nxwm unit test diff --git a/configs/sama5d4-ek/README.txt b/configs/sama5d4-ek/README.txt index 66779056b49..3a5cb4412ca 100644 --- a/configs/sama5d4-ek/README.txt +++ b/configs/sama5d4-ek/README.txt @@ -205,8 +205,7 @@ NuttX EABI "buildroot" Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh sama5d4-ek/ + tools/configure.sh sama5d4-ek/ 2. Download the latest buildroot package into @@ -256,8 +255,7 @@ NXFLAT Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh sama5d4-ek/ + tools/configure.sh sama5d4-ek/ 2. Download the latest buildroot package into @@ -356,9 +354,7 @@ Creating and Using DRAMBOOT the dramboot configuration and setup the PATH variable in order to do the build: - cd tools - ./configure.sh sama5d4-ek/dramboot - cd - + tools/configure.sh sama5d4-ek/dramboot Before building, make sure that the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -461,9 +457,7 @@ Creating and Using AT25BOOT the AT25BOOT configuration and setup the PATH variable in order to do the build: - cd tools - ./configure.sh sama5d4-ek/at25boot - cd - + tools/configure.sh sama5d4-ek/at25boot Before building, make sure that the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -3584,9 +3578,7 @@ Configurations Each SAMA4D4-EK configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sama5d4-ek/ - cd - + tools/configure.sh sama5d4-ek/ Before building, make sure that the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. @@ -4166,9 +4158,8 @@ Configurations 6a. General build directions (boot from SD card): - $ cd nuttx/tools : Go to the tools sub-directory - $ ./configure.sh sama5d4-ek/kernel : Establish this configuration - $ cd .. : Back to the NuttX build directory + $ cd nuttx : Go to the NuttX build directory + $ tools/configure.sh sama5d4-ek/kernel : Establish this configuration $ export PATH=???:$PATH : Set up the PATH variable $ make : Build the kerne with a dummy ROMFS image : This should create the nuttx ELF @@ -4184,9 +4175,7 @@ Configurations 6b. General build directions (boot from ROMFS image): - $ cd nuttx/tools : Go to the tools sub-directory - $ ./configure.sh sama5d4-ek/kernel : Establish this configuration - $ cd .. : Back to the NuttX build directory + $ tools/configure.sh sama5d4-ek/kernel : Establish this configuration $ 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 @@ -4764,14 +4753,11 @@ Configurations a. Install the nxwm configuration - $ cd ~/nuttx-git/nuttx/tools - $ ./configure.sh sama5d4-ek/nxwm + $ tools/configure.sh sama5d4-ek/nxwm b. Make the build context (only) - $ cd .. $ make context - ... c. Install the nxwm unit test diff --git a/configs/samd20-xplained/README.txt b/configs/samd20-xplained/README.txt index c8af7952be1..5b8d0be219d 100644 --- a/configs/samd20-xplained/README.txt +++ b/configs/samd20-xplained/README.txt @@ -366,8 +366,7 @@ NuttX EABI "buildroot" Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh samd20-xplained/ + tools/configure.sh samd20-xplained/ 2. Download the latest buildroot package into @@ -598,9 +597,7 @@ Configurations Each SAMD20 Xplained Pro configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh samd20-xplained/ - cd - + tools/configure.sh samd20-xplained/ Before building, make sure that the PATH environment variable include the correct path to the directory than holds your toolchain binaries. @@ -684,7 +681,7 @@ Configurations Any re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. diff --git a/configs/samd21-xplained/README.txt b/configs/samd21-xplained/README.txt index 3f3624ff181..a3bd5582dbc 100644 --- a/configs/samd21-xplained/README.txt +++ b/configs/samd21-xplained/README.txt @@ -463,9 +463,7 @@ Configurations Each SAMD21 Xplained Pro configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh samd21-xplained/ - cd - + tools/configure.sh samd21-xplained/ Before building, make sure the PATH environment varaible include the correct path to the directory than holds your toolchain binaries. @@ -549,7 +547,7 @@ Configurations Any re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. diff --git a/configs/same70-xplained/README.txt b/configs/same70-xplained/README.txt index 9695034a64c..b9ad71b801b 100644 --- a/configs/same70-xplained/README.txt +++ b/configs/same70-xplained/README.txt @@ -1233,9 +1233,7 @@ Information Common to All Configurations Each SAME70-XPLD configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh same70-xplained/ - cd - + tools/configure.sh same70-xplained/ Before building, make sure that the PATH environment variable include the correct path to the directory than holds your toolchain binaries. diff --git a/configs/saml21-xplained/README.txt b/configs/saml21-xplained/README.txt index 88323bfd534..81d5c391137 100644 --- a/configs/saml21-xplained/README.txt +++ b/configs/saml21-xplained/README.txt @@ -347,8 +347,7 @@ NuttX EABI "buildroot" Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh saml21-xplained/ + tools/configure.sh saml21-xplained/ 2. Download the latest buildroot package into @@ -636,9 +635,7 @@ Configurations Each SAML21 Xplained Pro configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh saml21-xplained/ - cd - + tools/configure.sh saml21-xplained/ Before building, make sure that the PATH environmental variable includes the correct path to the directory than holds your toolchain binaries. @@ -713,7 +710,7 @@ Configurations Any re-configuration should be done before making NuttX or else the subsequent 'make' will fail. If you have already attempted building NuttX then you will have to 1) 'make distclean' to remove the old - configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start + configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start with a fresh configuration, and 3) perform the configuration changes above. diff --git a/configs/samv71-xult/README.txt b/configs/samv71-xult/README.txt index d6586383ccb..62730da9823 100644 --- a/configs/samv71-xult/README.txt +++ b/configs/samv71-xult/README.txt @@ -2390,14 +2390,11 @@ Configuration sub-directories a. Install the VNC nxwm configuration - $ cd HOME/nuttx/tools - $ ./configure.sh samv71-xult/vnc + $ tools/configure.sh samv71-xult/vnc b. Make the build context (only) - $ cd .. $ make context - ... c. Install the nxwm unit test @@ -2573,14 +2570,11 @@ Configuration sub-directories a. Install the nxwm configuration - $ cd HOME/nuttx/tools - $ ./configure.sh samv71-xult/nxwm + $ tools/configure.sh samv71-xult/nxwm b. Make the build context (only) - $ cd .. $ make context - ... c. Install the nxwm unit test diff --git a/configs/shenzhou/README.txt b/configs/shenzhou/README.txt index b76c2f9ef60..0ce6e28d4bf 100644 --- a/configs/shenzhou/README.txt +++ b/configs/shenzhou/README.txt @@ -485,9 +485,7 @@ Configurations Each Shenzhou configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh shenzhou/ - cd - + tools/configure.sh shenzhou/ Where is one of the following: @@ -562,14 +560,11 @@ Where is one of the following: 1. Intall the nxwm configuration - $ cd ~/nuttx-code/tools - $ ./configure.sh shenzhou/nxwm + $ tools/configure.sh shenzhou/nxwm 2. Make the build context (only) - $ cd .. $ make context - ... 3. Install the nxwm unit test diff --git a/configs/sim/README.txt b/configs/sim/README.txt index 07ed0791237..2bce934816d 100644 --- a/configs/sim/README.txt +++ b/configs/sim/README.txt @@ -422,9 +422,7 @@ Common Configuration Information 1. Each configuration is maintained in a sub-directory and can be selected as follow: - cd /tools - ./configure.sh sim/ - cd - + tools/configure.sh sim/ Where is one of the following sub-directories. diff --git a/configs/skp16c26/README.txt b/configs/skp16c26/README.txt index 864c01faf8a..271924dc385 100644 --- a/configs/skp16c26/README.txt +++ b/configs/skp16c26/README.txt @@ -65,12 +65,12 @@ NOTE: See the toolchain issues above -- you may not want to waste your time. 3. Make sure that NuttX is configured - cd /tools - ./configure.sh + cd + tools/configure.sh 4. Configure and Make the buildroot - cd buildroot + cd cp configs/m32c-defconfig-4.2.4 .config make oldconfig make diff --git a/configs/stm3210e-eval/README.txt b/configs/stm3210e-eval/README.txt index 97ae979d1cf..4d4b72efc06 100644 --- a/configs/stm3210e-eval/README.txt +++ b/configs/stm3210e-eval/README.txt @@ -501,9 +501,7 @@ Configurations Each STM3210E-EVAL configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh stm3210e-eval/ - cd - + tools/configure.sh stm3210e-eval/ Where is one of the following: diff --git a/configs/stm3220g-eval/README.txt b/configs/stm3220g-eval/README.txt index d1f5d9ae0d5..d566b75c94a 100644 --- a/configs/stm3220g-eval/README.txt +++ b/configs/stm3220g-eval/README.txt @@ -504,9 +504,7 @@ Configurations Each STM3220G-EVAL configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh stm3220g-eval/ - cd - + tools/configure.sh stm3220g-eval/ Where is one of the following: @@ -817,14 +815,11 @@ Where is one of the following: 1. Install the nxwm configuration - $ cd ~/nuttx-code/nuttx/tools - $ ./configure.sh stm3220g-eval/nxwm + $ tools/configure.sh stm3220g-eval/nxwm 2. Make the build context (only) - $ cd .. $ make context - ... 3. Install the nxwm unit test diff --git a/configs/stm3240g-eval/README.txt b/configs/stm3240g-eval/README.txt index 4d7069c8788..23137cfd647 100644 --- a/configs/stm3240g-eval/README.txt +++ b/configs/stm3240g-eval/README.txt @@ -644,9 +644,7 @@ Configurations Each STM3240G-EVAL configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh stm3240g-eval/ - cd - + tools/configure.sh stm3240g-eval/ Where is one of the following: diff --git a/configs/stm32_tiny/README.txt b/configs/stm32_tiny/README.txt index f52599d0746..4d570dfd2f8 100644 --- a/configs/stm32_tiny/README.txt +++ b/configs/stm32_tiny/README.txt @@ -272,9 +272,7 @@ Configurations Each STM32Tiny configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh STM32Tiny/ - cd - + tools/configure.sh STM32Tiny/ Where is one of the following: diff --git a/configs/stm32f103-minimum/README.txt b/configs/stm32f103-minimum/README.txt index 4fd6b08531b..8bf07fca4ef 100644 --- a/configs/stm32f103-minimum/README.txt +++ b/configs/stm32f103-minimum/README.txt @@ -704,9 +704,7 @@ Configurations Each STM32F103 Minimum configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh STM32F103 Minimum/ - cd - + tools/configure.sh STM32F103 Minimum/ Where is one of the following: diff --git a/configs/stm32f3discovery/README.txt b/configs/stm32f3discovery/README.txt index 8e44b0d350e..0c4956715a6 100644 --- a/configs/stm32f3discovery/README.txt +++ b/configs/stm32f3discovery/README.txt @@ -416,9 +416,7 @@ Configurations Each STM32F3Discovery configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh STM32F3Discovery/ - cd - + tools/configure.sh STM32F3Discovery/ Where is one of the following: diff --git a/configs/stm32f4discovery/README.txt b/configs/stm32f4discovery/README.txt index 2b8c96efe47..92fb04a43e6 100644 --- a/configs/stm32f4discovery/README.txt +++ b/configs/stm32f4discovery/README.txt @@ -1106,7 +1106,7 @@ Enter inside NuttX and compile it: $ cd ../nuttx - $ ./tools/configure.sh stm32f4discovery/testlibcxx + $ tools/configure.sh stm32f4discovery/testlibcxx Copy files Refreshing... @@ -1170,9 +1170,7 @@ Common Information Each STM32F4Discovery configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh STM32F4Discovery/ - cd - + tools/configure.sh STM32F4Discovery/ Where is one of the sub-directories listed in the next paragraph @@ -1197,8 +1195,7 @@ Configuration Sub-directories test is used to verify the uClibc++ port to NuttX. This configuration may be selected as follows: - cd /tools - ./configure.sh sim/cxxtest + tools/configure.sh sim/cxxtest NOTES: diff --git a/configs/stm32f746g-disco/README.txt b/configs/stm32f746g-disco/README.txt index 774ec7a7575..e0b4589cb56 100644 --- a/configs/stm32f746g-disco/README.txt +++ b/configs/stm32f746g-disco/README.txt @@ -462,9 +462,7 @@ Configurations Each STM32F746G-DISCO configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh stm32f746g-disco/ - cd - + tools/configure.sh stm32f746g-disco/ Where is one of the sub-directories listed below. diff --git a/configs/stm32f769i-disco/README.txt b/configs/stm32f769i-disco/README.txt index e3921dab2fa..23f3a9eaabe 100644 --- a/configs/stm32f769i-disco/README.txt +++ b/configs/stm32f769i-disco/README.txt @@ -103,9 +103,7 @@ Configurations Each STM32F769I-DISCO configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh stm32f769i-disco/ - cd - + tools/configure.sh stm32f769i-disco/ Where is one of the sub-directories listed below. diff --git a/configs/stm32ldiscovery/README.txt b/configs/stm32ldiscovery/README.txt index 40a3917dfd2..966415e5bf3 100644 --- a/configs/stm32ldiscovery/README.txt +++ b/configs/stm32ldiscovery/README.txt @@ -486,9 +486,7 @@ Configurations Each STM32L-Discovery configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh STM32L-Discovery/ - cd - + tools/configure.sh STM32L-Discovery/ Where is one of the following sub-directories. diff --git a/configs/stm32vldiscovery/README.txt b/configs/stm32vldiscovery/README.txt index d2f8af10bb6..8dc62c0d658 100644 --- a/configs/stm32vldiscovery/README.txt +++ b/configs/stm32vldiscovery/README.txt @@ -211,9 +211,7 @@ Configurations Each STMicro STM32F100RC generic configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh stm32vldiscovery/ - cd - + tools/configure.sh stm32vldiscovery/ Where is one of the following: diff --git a/configs/sure-pic32mx/README.txt b/configs/sure-pic32mx/README.txt index eb1fd9af914..e8cbda1b055 100644 --- a/configs/sure-pic32mx/README.txt +++ b/configs/sure-pic32mx/README.txt @@ -628,9 +628,7 @@ Configurations Each PIC32MX configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh sure-pic32mx/ - cd - + tools/configure.sh sure-pic32mx/ 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 105b2891572..0869d970d49 100644 --- a/configs/teensy-2.0/README.txt +++ b/configs/teensy-2.0/README.txt @@ -296,8 +296,7 @@ NuttX buildroot Toolchain 1. You must have already configured Nuttx in /nuttx. - cd tools - ./configure.sh Teensy++/ + tools/configure.sh Teensy++/ NOTE: you also must copy avr-libc header files into the NuttX include directory with command perhaps like: @@ -518,9 +517,7 @@ Common Configuration Notes 1. Each Teensy++ configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh teensy-2.0/ - cd - + tools/configure.sh teensy-2.0/ 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 3770f667a80..05e2e7dc944 100644 --- a/configs/teensy-3.x/README.txt +++ b/configs/teensy-3.x/README.txt @@ -224,9 +224,7 @@ Configurations Each Teensy-3.x configurations are maintained in sub-directories and can be selected as follow: - cd tools - ./configure.sh teensy-3.x/ - cd - + tools/configure.sh teensy-3.x/ make oldconfig Before building, make sure that your PATH environment variable includes diff --git a/configs/tm4c123g-launchpad/README.txt b/configs/tm4c123g-launchpad/README.txt index 1912056a61a..3c388fe62f1 100644 --- a/configs/tm4c123g-launchpad/README.txt +++ b/configs/tm4c123g-launchpad/README.txt @@ -561,9 +561,7 @@ Configurations Each TM4C123G LaunchPad configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh tm4c123g-launchpad/ - cd - + tools/configure.sh tm4c123g-launchpad/ Where is one of the following: diff --git a/configs/tm4c1294-launchpad/README.txt b/configs/tm4c1294-launchpad/README.txt index 9c3be1b7db4..5f949f8ecc0 100644 --- a/configs/tm4c1294-launchpad/README.txt +++ b/configs/tm4c1294-launchpad/README.txt @@ -25,9 +25,7 @@ Configurations Each EK-TM4C1294XL configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh tm4c1294-launchpad/ - cd - + tools/configure.sh tm4c1294-launchpad/ Where is one of the following: diff --git a/configs/tms570ls31x-usb-kit/README.txt b/configs/tms570ls31x-usb-kit/README.txt index b9eac6e43dd..7b72e558364 100644 --- a/configs/tms570ls31x-usb-kit/README.txt +++ b/configs/tms570ls31x-usb-kit/README.txt @@ -79,9 +79,7 @@ Configurations Each TMS570LS31X Usb Kit configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh tms570ls31x-usb-kit/ - cd - + tools/configure.sh tms570ls31x-usb-kit/ Before building, make sure the PATH environment variable includes the correct path to the directory than holds your toolchain binaries. diff --git a/configs/twr-k60n512/README.txt b/configs/twr-k60n512/README.txt index 490848b91b9..d7b2df13106 100644 --- a/configs/twr-k60n512/README.txt +++ b/configs/twr-k60n512/README.txt @@ -449,9 +449,7 @@ Configurations Each TWR-K60N512 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh twr-k60n512/ - cd - + tools/configure.sh twr-k60n512/ Where is one of the following: diff --git a/configs/twr-k64f120m/README.txt b/configs/twr-k64f120m/README.txt index c151120a9a5..4a379a7dae6 100644 --- a/configs/twr-k64f120m/README.txt +++ b/configs/twr-k64f120m/README.txt @@ -574,9 +574,7 @@ Configurations Each TWR-K64F120M configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh twr-k64f120m/ - cd .. + tools/configure.sh twr-k64f120m/ Where is one of the following: diff --git a/configs/ubw32/README.txt b/configs/ubw32/README.txt index f3a0296c69f..3c0af99a5f0 100644 --- a/configs/ubw32/README.txt +++ b/configs/ubw32/README.txt @@ -562,9 +562,7 @@ Configurations Each PIC32MX configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh ubw32/ - cd - + tools/configure.sh ubw32/ Where is one of the following: diff --git a/configs/us7032evb1/README.txt b/configs/us7032evb1/README.txt index eabbba14030..6e882d99243 100644 --- a/configs/us7032evb1/README.txt +++ b/configs/us7032evb1/README.txt @@ -23,8 +23,7 @@ Toolchain 1. You must have already configured Nuttx in nuttx. - cd tools - ./configure.sh us7032evb1/ + tools/configure.sh us7032evb1/ 2. Download the latest buildroot package into @@ -61,9 +60,7 @@ Common Configuration Notes 1. Each SH-1 configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh us7032evb1/ - cd - + tools/configure.sh us7032evb1/ 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 89dfe7ac471..12c3d6b8169 100644 --- a/configs/viewtool-stm32f107/README.txt +++ b/configs/viewtool-stm32f107/README.txt @@ -733,9 +733,7 @@ Configurations Each SAM3U-EK configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh viewtool-stm32f107/ - cd - + tools/configure.sh viewtool-stm32f107/ Before starting the build, make sure that your PATH environment variable includes the correct path to your toolchain. diff --git a/configs/z16f2800100zcog/README.txt b/configs/z16f2800100zcog/README.txt index aff6105296b..e3414462ab5 100644 --- a/configs/z16f2800100zcog/README.txt +++ b/configs/z16f2800100zcog/README.txt @@ -101,9 +101,7 @@ that directory is also a bash script that will apply that patch for you. The patch would be applied when NuttX is configured as follows: - cd tools - ./configure.sh z16f2800100zcog/nsh - cd .. + tools/configure.sh z16f2800100zcog/nsh dopatch.sh make @@ -134,9 +132,7 @@ Variations on the basic z8f162800100zcog configuration are maintained in subdirectories. To configure any specific configuration, do the following steps: - cd /tools - ./configure.sh z16f2800100zcog/ - cd + tools/configure.sh z16f2800100zcog/ make Where is the specific board configuration that you diff --git a/configs/z8encore000zco/README.txt b/configs/z8encore000zco/README.txt index 35e2484f2e3..f4470e9d63d 100644 --- a/configs/z8encore000zco/README.txt +++ b/configs/z8encore000zco/README.txt @@ -55,9 +55,7 @@ Variations on the basic z8encore000zco configuration are maintained in subdirectories. To configure any specific configuration, do the following steps: - cd /tools - ./configure.sh z8encore000zco/ - cd + tools/configure.sh z8encore000zco/ make Where is the specific board configuration that you diff --git a/configs/z8f64200100kit/README.txt b/configs/z8f64200100kit/README.txt index 69c69acdf92..e0dbcee016f 100644 --- a/configs/z8f64200100kit/README.txt +++ b/configs/z8f64200100kit/README.txt @@ -55,9 +55,7 @@ Variations on the basic z8f64200100kit configuration are maintained in subdirectories. To configure any specific configuration, do the following steps: - cd /tools - ./configure.sh z8f64200100kit/ - cd + tools/configure.sh z8f64200100kit/ make Where is the specific board configuration that you diff --git a/configs/zkit-arm-1769/README.txt b/configs/zkit-arm-1769/README.txt index 615c67f5be0..e9a8794d5e2 100644 --- a/configs/zkit-arm-1769/README.txt +++ b/configs/zkit-arm-1769/README.txt @@ -371,9 +371,7 @@ Configurations Each ZKit-ARM configuration is maintained in a sudirectory and can be selected as follow: - cd tools - ./configure.sh zkit-arm-1769/ - cd - + tools/configure.sh zkit-arm-1769/ Where is one of the following: diff --git a/configs/zp214xpa/README.txt b/configs/zp214xpa/README.txt index d2943d62df1..9b1f56d3640 100644 --- a/configs/zp214xpa/README.txt +++ b/configs/zp214xpa/README.txt @@ -284,9 +284,7 @@ Configurations: Each NXP LPC214x configuration is maintained in a sub-directory and can be selected as follow: - cd tools - ./configure.sh zp214xpa/ - cd - + tools/configure.sh zp214xpa/ Where is one of the following: