sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove instructures to CD to tools/ before running ./configure.sh

Browse Source 
Squashed commit of the following:

    configs/*/README.txt: Replace each occurrence of './configure.sh' with 'tools/configure.sh'
    configs/*/README.txt:  Remove 'cd ..' after each './configure.sh'
    configs/*/README.txt:  Remove 'cd -' after each './configure.sh'
    configs/*/README.txt:  Remove 'cd tools' before each './configure.sh'
    configs/README.txt:  Remove instruction to CD tools/ before running configure.sh.
This commit is contained in:
Gregory Nutt 2018-05-09 11:41:46 -06:00
parent 0b6ccfe769
commit e4922ed9f0
115 changed files with 182 additions and 481 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
configs/amber/README.txt
View File

@ -274,8 +274,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh amber/<sub-dir>
tools/configure.sh amber/<sub-dir>
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/<subdir>
cd -
tools/configure.sh amber/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
configs/arduino-due/README.txt
View File

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

4
configs/arduino-mega2560/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh arduino-mega2560/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/avr32dev1/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh avr32dev1/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/bambino-200e/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh bambino-200e/<subdir>
Where <subdir> is one of the following:

7
configs/c5471evm/README.txt
View File

@ -13,8 +13,7 @@ Toolchain
1. You must have already configured Nuttx in <some-dir>nuttx.
cd tools
./configure.sh c5471evm/<sub-dir>
tools/configure.sh c5471evm/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh c5471evm/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/clicker2-stm32/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh clicker2-stm32/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

10
configs/cloudctrl/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh shenzhou/<subdir>
Where <subdir> is one of the following:
@ -545,14 +543,12 @@ Where <subdir> 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

7
configs/demo9s12ne64/README.txt
View File

@ -121,8 +121,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh demo9s12nec64/<sub-dir>
tools/configure.sh demo9s12nec64/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh demo9s12nec64/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/dk-tm4c129x/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh dk-tm4c129x/<subdir>
Where <subdir> is one of the following:

10
configs/ea3131/README.txt
View File

@ -150,8 +150,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh ea3131/<sub-dir>
tools/configure.sh ea3131/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh ea3131/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

16
configs/ea3152/README.txt
View File

@ -149,8 +149,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh ea3152/<sub-dir>
tools/configure.sh ea3152/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh ea3152/<subdir>
Where <subdir> is one of the following:

4
configs/eagle100/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh eagle100/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/efm32-g8xx-stk/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh efm32-g8xx-stk/<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

4
configs/efm32gg-stk3700/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh efm32gg-stk3700/<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

4
configs/ekk-lm3s9b96/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh ekk-lm3s9b96/<subdir>
Where <subdir> is one of the following:

4
configs/esp32-core/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh esp32-core/<subdir>
make oldconfig
Before building, make sure the PATH environment variable includes the

4
configs/ez80f910200kitg/README.txt
View File

@ -78,9 +78,7 @@ Variations on the basic ez80f910200kitg configuration are maintained
in subdirectories. To configure any specific configuration, do the
following steps:
cd <nuttx-top-directory>/tools
./configure.sh ez80f910200kitg/<sub-directory>
cd <nuttx-top-directory>
tools/configure.sh ez80f910200kitg/<sub-directory>
make
Where <sub-directory> is the specific board configuration that you

4
configs/ez80f910200zco/README.txt
View File

@ -82,9 +82,7 @@ Common Configuration Notes
in subdirectories. To configure any specific configuration, do the
following steps:
cd <nuttx-top-directory>/tools
./configure.sh ez80f910200zco/<sub-directory>
cd <nuttx-top-directgory>
tools/configure.sh ez80f910200zco/<sub-directory>
make
Where <sub-directory> is the specific board configuration that you

4
configs/fire-stm32v2/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh fire-stm32v2/<subdir>
Where <subdir> is one of the following:

4
configs/freedom-k64f/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh freedom-k64f/<subdir>
Where <subdir> is one of the following:

4
configs/freedom-k66f/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh freedom-K66F/<subdir>
Where <subdir> is one of the following:

7
configs/freedom-kl25z/README.txt
View File

@ -44,8 +44,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh freedom-kl25z/<sub-dir>
tools/configure.sh freedom-kl25z/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh freedom-kl25z/<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

7
configs/freedom-kl26z/README.txt
View File

@ -44,8 +44,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh freedom-kl26z/<sub-dir>
tools/configure.sh freedom-kl26z/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh freedom-kl26z/<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

4
configs/hymini-stm32v/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh hymini-stm32v/<subdir>
Where <subdir> is one of the following:

10
configs/indium-f7/README.txt
View File

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

4
configs/kwikstik-k40/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh kwikstik-k40/<subdir>
Where <subdir> is one of the following:

4
configs/launchxl-tms57004/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh launchxl-tms57004/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

6
configs/lincoln60/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lincoln60/<subdir>
Where <subdir> is one of the following:

4
configs/lm3s6432-s2e/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lm3s6432-s2e/<subdir>
Where <subdir> is one of the following:

4
configs/lm3s6965-ek/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lm3s6965-ek/<subdir>
Where <subdir> is one of the following:

4
configs/lm3s8962-ek/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lm3s8962-ek/<subdir>
Where <subdir> is one of the following:

4
configs/lm4f120-launchpad/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lm4f120-launchpad/<subdir>
Where <subdir> is one of the following:

4
configs/lpc4330-xplorer/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lpc4330-xplorer/<subdir>
Where <subdir> is one of the following:

4
configs/lpc4337-ws/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh LPC4337-ws/<subdir>
Where <subdir> is one of the following:

4
configs/lpc4357-evb/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lpc4357-evb/<subdir>
Where <subdir> is one of the following:

4
configs/lpc4370-link2/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh LPC4370-Link2/<subdir>
Where <subdir> is one of the following:

4
configs/lpcxpresso-lpc1115/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lpcxpresso-lpc1115/<subdir>
Where <subdir> is one of the following:

4
configs/lpcxpresso-lpc1768/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh lpcxpresso-lpc1768/<subdir>
Where <subdir> is one of the following:

4
configs/maple/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh maple/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

6
configs/mbed/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh mbed/<subdir>
Where <subdir> is one of the mbed subdirectories described in the
following paragraph.

6
configs/mcb1700/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh mcb1700/<subdir>
Where <subdir> is one of the mcb1700 subdirectories described in the
following paragraph.

7
configs/mcu123-lpc214x/README.txt
View File

@ -89,8 +89,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh eagle100/<sub-dir>
tools/configure.sh eagle100/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh mcu123-lpc214x/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

7
configs/micropendous3/README.txt
View File

@ -287,8 +287,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh micropendous3/<sub-dir>
tools/configure.sh micropendous3/<sub-dir>
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/<subdir>
cd -
tools/configure.sh micropendous3/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/mikroe-stm32f4/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh mikroe-stm32f4/<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

4
configs/mirtoo/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh mirtoo/<subdir>
Where <subdir> is one of the following:

3
configs/misoc/README.txt
View File

@ -20,8 +20,7 @@ Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh misoc/<sub-dir>
tools/configure.sh misoc/<sub-dir>
make oldconfig context
2. Clone the latest buildroot package into <some-dir>/buildroot

4
configs/moteino-mega/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh moteino-mega/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

7
configs/ne64badge/README.txt
View File

@ -228,8 +228,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh ne64badge/<sub-dir>
tools/configure.sh ne64badge/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh ne64badge/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/nr5m100-nexys4/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh nr5m100-nexys4/<subdir>
Where <subdir> is one of the following:

4
configs/nrf52-pca10040/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh nrf52-pca10040/<subdir>
Where <subdir> is one of the following:

7
configs/ntosd-dm320/README.txt
View File

@ -166,8 +166,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>nuttx.
cd tools
./configure.sh ntosd-dm320/<sub-dir>
tools/configure.sh ntosd-dm320/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh ntosd-dm320/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
configs/nucleo-144/README.txt
View File

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

4
configs/nucleo-f072rb/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh nucleo-f072rb/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

4
configs/nucleo-f091rc/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh nucleo-f091rc/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

5
configs/nucleo-f4x1re/README.txt
View File

@ -260,7 +260,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/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 <some-dir>/nuttx.
cd tools
./configure.sh lpcxpresso-lpc1768/<sub-dir>
tools/configure.sh lpcxpresso-lpc1768/<sub-dir>
2. Download the latest buildroot package into <some-dir>

3
configs/nucleo-l432kc/README.txt
View File

@ -273,8 +273,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh lpcxpresso-lpc1768/<sub-dir>
tools/configure.sh lpcxpresso-lpc1768/<sub-dir>
2. Download the latest buildroot package into <some-dir>

4
configs/nucleo-l452re/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh nucleo-l452re/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

3
configs/nucleo-l476rg/README.txt
View File

@ -285,8 +285,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh lpcxpresso-lpc1768/<sub-dir>
tools/configure.sh lpcxpresso-lpc1768/<sub-dir>
2. Download the latest buildroot package into <some-dir>

7
configs/nutiny-nuc120/README.txt
View File

@ -45,8 +45,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh nutiny-nuc120/<sub-dir>
tools/configure.sh nutiny-nuc120/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh nutiny-nuc120/<subdir>
Where <subdir> is one of the following:

4
configs/olimex-efm32g880f128-stk/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh olimex-efm32g880f128-stk/<subdir>
Where <subdir> is one of the following:

10
configs/olimex-lpc-h3131/README.txt
View File

@ -152,8 +152,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh olimex-lpc-h3131/<sub-dir>
tools/configure.sh olimex-lpc-h3131/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh olimex-lpc-h3131/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

6
configs/olimex-lpc1766stk/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh olimex-lpc1766stk/<subdir>
Where <subdir> is one of the sub-directories identified in the following
paragraphs.

4
configs/olimex-stm32-p407/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh olimex-stm32-p407/<subdir>
Where <subdir> is one of the configuration sub-directories listed in the
following section.

7
configs/olimex-strp711/README.txt
View File

@ -173,8 +173,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>nuttx.
cd tools
./configure.sh olimex-strp711/<sub-dir>
tools/configure.sh olimex-strp711/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh olimex-strp711/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/pcblogic-pic32mx/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh pcblogic-pic32mx/<subdir>
Where <subdir> is one of the following sub-directories.

7
configs/photon/README.txt
View File

@ -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)
================================================================

4
configs/pic32mx-starterkit/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh pic32mx-starterkit/<subdir>
Where <subdir> is one of the following:

4
configs/pic32mx7mmb/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh pic32mx7mmb/<subdir>
Where <subdir> is one of the following:

7
configs/qemu-i486/README.txt
View File

@ -118,8 +118,7 @@ Buildroot Instructions
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh qemu-i486/<sub-dir>
tools/configure.sh qemu-i486/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh qemu-i486/<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
configs/sabre-6quad/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh sabre-6quad/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

11
configs/sam3u-ek/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh sam3u-ek/<subdir>
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

11
configs/sam4e-ek/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh sam4e-ek/<subdir>
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

6
configs/sam4l-xplained/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh sam4l-xplained/<subdir>
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.

6
configs/sam4s-xplained-pro/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.shsam4s-xplained-pro/<subdir>
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.

6
configs/sam4s-xplained/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.shsam4s-xplained/<subdir>
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.

12
configs/sama5d2-xult/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh sama5d2-xult/<subdir>
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.

10
configs/sama5d3-xplained/README.txt
View File

@ -189,8 +189,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh sama5d3-xplained/<sub-dir>
tools/configure.sh sama5d3-xplained/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -240,8 +239,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh sama5d3-xplained/<sub-dir>
tools/configure.sh sama5d3-xplained/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh sama5d3-xplained/<subdir>
Before building, make sure that the PATH environment variable include the
correct path to the directory than holds your toolchain binaries.

23
configs/sama5d3x-ek/README.txt
View File

@ -211,8 +211,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh sama5d3x-ek/<sub-dir>
tools/configure.sh sama5d3x-ek/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -262,8 +261,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh sama5d3x-ek/<sub-dir>
tools/configure.sh sama5d3x-ek/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh sama5d3x-ek/<subdir>
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 <nuttx>
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/<subdir>
cd -
tools/configure.sh sama5d3x-ek/<subdir>
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

32
configs/sama5d4-ek/README.txt
View File

@ -205,8 +205,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh sama5d4-ek/<sub-dir>
tools/configure.sh sama5d4-ek/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -256,8 +255,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh sama5d4-ek/<sub-dir>
tools/configure.sh sama5d4-ek/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh sama5d4-ek/<subdir>
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

9
configs/samd20-xplained/README.txt
View File

@ -366,8 +366,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh samd20-xplained/<sub-dir>
tools/configure.sh samd20-xplained/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh samd20-xplained/<subdir>
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.

6
configs/samd21-xplained/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh samd21-xplained/<subdir>
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.

4
configs/same70-xplained/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh same70-xplained/<subdir>
Before building, make sure that the PATH environment variable include the
correct path to the directory than holds your toolchain binaries.

9
configs/saml21-xplained/README.txt
View File

@ -347,8 +347,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
cd tools
./configure.sh saml21-xplained/<sub-dir>
tools/configure.sh saml21-xplained/<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -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/<subdir>
cd -
tools/configure.sh saml21-xplained/<subdir>
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.

10
configs/samv71-xult/README.txt
View File

@ -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

9
configs/shenzhou/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh shenzhou/<subdir>
Where <subdir> is one of the following:
@ -562,14 +560,11 @@ Where <subdir> 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

4
configs/sim/README.txt
View File

@ -422,9 +422,7 @@ Common Configuration Information
1. Each configuration is maintained in a sub-directory and can be selected
as follow:
cd <nuttx-directory>/tools
./configure.sh sim/<subdir>
cd -
tools/configure.sh sim/<subdir>
Where <subdir> is one of the following sub-directories.

6
configs/skp16c26/README.txt
View File

@ -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 <nuttx-dir>/tools
./configure.sh <nuttx-configuration>
cd <nuttx-dir>
tools/configure.sh <nuttx-configuration>
4. Configure and Make the buildroot
cd buildroot
cd <buildroot-dir>
cp configs/m32c-defconfig-4.2.4 .config
make oldconfig
make

4
configs/stm3210e-eval/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh stm3210e-eval/<subdir>
Where <subdir> is one of the following:

9
configs/stm3220g-eval/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh stm3220g-eval/<subdir>
Where <subdir> is one of the following:
@ -817,14 +815,11 @@ Where <subdir> 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

4
configs/stm3240g-eval/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh stm3240g-eval/<subdir>
Where <subdir> is one of the following:

4
configs/stm32_tiny/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh STM32Tiny/<subdir>
Where <subdir> is one of the following:

4
configs/stm32f103-minimum/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh STM32F103 Minimum/<subdir>
Where <subdir> is one of the following:

4
configs/stm32f3discovery/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh STM32F3Discovery/<subdir>
Where <subdir> is one of the following:

9
configs/stm32f4discovery/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh STM32F4Discovery/<subdir>
Where <subdir> 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 <nuttx-directory>/tools
./configure.sh sim/cxxtest
tools/configure.sh sim/cxxtest
NOTES:

4
configs/stm32f746g-disco/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh stm32f746g-disco/<subdir>
Where <subdir> is one of the sub-directories listed below.

4
configs/stm32f769i-disco/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh stm32f769i-disco/<subdir>
Where <subdir> is one of the sub-directories listed below.

4
configs/stm32ldiscovery/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh STM32L-Discovery/<subdir>
Where <subdir> is one of the following sub-directories.

4
configs/stm32vldiscovery/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh stm32vldiscovery/<subdir>
Where <subdir> is one of the following:

4
configs/sure-pic32mx/README.txt
View File

@ -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/<subdir>
cd -
tools/configure.sh sure-pic32mx/<subdir>
Where <subdir> is one of the following sub-directories.

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