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

tools/: Change preferred argument of configurations tools to use ':' as the delimiter between <board-name> and <config-name>. This is to emphasize that this is not a path; it is configuration specification.

Browse Source 
The legacy '/' delimiter is still supported but not recommend and not advertised.

Squashed commit of the following:

    Update configurations instructions in more README.txt files to show ':' delimiter vs '/' delimiter.
    Update configurations instructions in various README.txt file to show ':' delimiter vs '/' delimiter.
    tools:  Update all configuration-related tools to accept ':' separator between board and configuration name.
This commit is contained in:
Gregory Nutt 2019-08-05 16:53:39 -06:00
parent 0de938a190
commit 721994846c
147 changed files with 266 additions and 236 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/NXGraphicsSubsystem.html
View File

@ -4215,9 +4215,7 @@ static FAR const struct nx_fontpackage_s *g_fontpackages[] =
based upon a simple region of memory posing as video memory.
That default configuration can be built as follows:
<ul><pre>
cd &lt;NuttX-Directory&gt;/tools
./configure sim/nx
cd &lt;NuttX-Directory&gt;
tools/configure.sh sim:nx
make
./nuttx
</pre></ul>
@ -4232,9 +4230,7 @@ make
This preferred configuration can be built as follows:
</p>
<ul><pre>
cd &lt;NuttX-Directory&gt;/tools
./configure sim/nx11
cd &lt;NuttX-Directory&gt;
tools/configure sim:nx11
make
./nuttx
</pre></ul>

10
Documentation/NuttxPortingGuide.html
View File

@ -1488,7 +1488,7 @@ tools/
|-- cfgparser.h
|-- cmpconfig.c
|-- cnvwindeps.c
|-- configure.sh / configure.bat
|-- configure.sh / configure.bat / configure.c
|-- copydir.sh / copydir.bat
|-- define.sh / define.bat
|-- discovery.py
@ -1578,14 +1578,14 @@ tools/
accomplish the same configuration:
</p>
<ul><pre>
tools/configure.sh [OPTIONS] <i>&lt;board-name&gt;</i>[/<i>&lt;config-dir&gt;</i>]
tools/configure.sh [OPTIONS] <i>&lt;board-name&gt;</i>:<i>&lt;config-dir&gt;</i>
</pre></ul>
<p>
There is an alternative Windows batch file, <code>configure.bat</code>, that can be used instead of <code>configure.sh</code> in the windows native environment like:
</p>
<ul><pre>
tools\configure.bat <i>&lt;board-name&gt;</i>[\<i>&lt;config-dir&gt;</i>]
tools\configure.bat <i>&lt;board-name&gt;</i>:<i>&lt;config-dir&gt;</i>
</pre></ul>
<p>
See <code>tools/README.txt</code> for more information about these scripts.
@ -1594,7 +1594,7 @@ tools/
<ul><pre>
$ tools/configure.sh -h
USAGE: tools/configure.sh [-d] [-l|m|c|u|g|n] [-a &lt;app-dir&gt;] &lt;board-name&gt;/&lt;config-name&gt;
USAGE: tools/configure.sh [-d] [-l|m|c|u|g|n] [-a &lt;app-dir&gt;] &lt;board-name&gt;:&lt;config-name&gt;
Where:
-l selects the Linux (l) host environment.
@ -1616,7 +1616,7 @@ Where:
then you should also specify the location of the application directory on the command line like:
</p>
<ul><pre>
tools/configure.sh -a &lt;app-dir&gt; <i>&lt;board-name&gt;</i>[/<i>&lt;config-dir&gt;</i>]
tools/configure.sh -a &lt;app-dir&gt; <i>&lt;board-name&gt;</i>:<i>&lt;config-dir&gt;</i>
</pre></ul>
<p>

10
README.txt
View File

@ -691,12 +691,12 @@ Instantiating "Canned" Configurations
There is one tool for use with any Bash-like shell that does configuration
steps. It is used as follows:
tools/configure.sh <board-name>/<config-dir>
tools/configure.sh <board-name>:<config-dir>
There is an alternative Windows batch file that can be used in the windows
native environment like:
tools\configure.bat <board-name>\<config-dir>
tools\configure.bat <board-name>:<config-dir>
And, to make sure that other platforms are supported, there is also a
C program at tools/configure.c that can be compiled to establish the
@ -939,7 +939,7 @@ Make Sure that You are on the Right Platform
configurations. For example, if you are running on Linux and you
configure like this:
tools/configure.sh board/configuration
tools/configure.sh board:configuration
The you can use the following command to both (1) make sure that the
configuration is up to date, AND (2) the configuration is set up
@ -965,11 +965,11 @@ Make Sure that You are on the Right Platform
platform that you use, and uncompress and refresh the defconfig file all in
one command like:
tools/configure.sh -l board/configuration
tools/configure.sh -l board:configuration
For a Linux host or for a Windows/Cygwin host:
tools/configure.sh -h board/configuration
tools/configure.sh -h board:configuration
Other options are available from the help option built into the
script. You can see all options with:

2
binfmt/libpcode/README.txt
View File

@ -59,7 +59,7 @@ Here is a simple test configuration using the NuttX simulator:
1. Install the sim/nsh configuration:
cd tools
./configure.sh sim/nsh
./configure.sh sim:nsh
cd ..
2. Install p-code virtual machine as described above.

8
boards/README.txt
View File

@ -881,14 +881,12 @@ tools/configure.sh
There is a script that automates these steps. The following steps will
accomplish the same configuration:
cd tools
./configure.sh <board-name>/<config-dir>
tools/configure.sh <board-name>:<config-dir>
There is an alternative Windows batch file that can be used in the
windows native enironment like:
cd ${TOPDIR}\tools
configure.bat <board-name>\<config-dir>
tools\configure.bat <board-name>:<config-dir>
See tools/README.txt for more information about these scripts.
@ -897,7 +895,7 @@ tools/configure.sh
application directory on the command line like:
cd tools
./configure.sh -a <app-dir> <board-name>/<config-dir>
./configure.sh -a <app-dir> <board-name>:<config-dir>
Building Symbol Tables
^^^^^^^^^^^^^^^^^^^^^^

4
boards/amber/README.txt
View File

@ -274,7 +274,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
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:
@ -481,7 +481,7 @@ Common Configuration Notes
1. Each Amber Web Server configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh amber/<subdir>
tools/configure.sh amber:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

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

@ -637,7 +637,7 @@ Configurations
Each Arduino Due configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] arduino-due/<subdir>
tools/configure.sh [OPTIONS] arduino-due:<subdir>
Where typical options are -l to configure to build on Linux or -c to
configure for Cygwin under Linux. 'tools/configure.sh -h' will show

2
boards/arduino-mega2560/README.txt
View File

@ -48,7 +48,7 @@ Configurations
1. Each Arduino MEGA2560 configuration is maintained in a sub-directory
and can be selected as follow:
tools/configure.sh arduino-mega2560/<subdir>
tools/configure.sh arduino-mega2560:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/avr32dev1/README.txt
View File

@ -424,7 +424,7 @@ Common Configuration Notes
1. Each Atmel AVR32DEV configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh avr32dev1/<subdir>
tools/configure.sh avr32dev1:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/b-l475e-iot01a/README.txt
View File

@ -190,7 +190,7 @@ Configurations
Each B-L475E-IOT01A configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [-l|c|u|n] /b-l475e-iot01a/<subdir>
tools/configure.sh [-l|c|u|n] /b-l475e-iot01a:<subdir>
Where:
-l selects the Linux (l) host environment. The [-c|u|n] options

2
boards/bambino-200e/README.txt
View File

@ -340,7 +340,7 @@ Configurations
Each Bambino-200e configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh bambino-200e/<subdir>
tools/configure.sh bambino-200e:<subdir>
Where <subdir> is one of the following:

2
boards/beaglebone-black/README.txt
View File

@ -169,7 +169,7 @@ Configurations
Each Beaglebone Black configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] beaglebone-black/<subdir>
tools/configure.sh [OPTIONS] beaglebone-black:<subdir>
Where [OPTIONS] include -l to configure for a Linux host platform and
-c means to configure for a Windows Cygwin host platform. -h will give

4
boards/c5471evm/README.txt
View File

@ -13,7 +13,7 @@ Toolchain
1. You must have already configured Nuttx in <some-dir>nuttx.
tools/configure.sh c5471evm/<sub-dir>
tools/configure.sh c5471evm:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -122,7 +122,7 @@ Common Configuration Notes
1. Each C5471 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh c5471evm/<subdir>
tools/configure.sh c5471evm:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/clicker2-stm32/README.txt
View File

@ -160,7 +160,7 @@ Configurations
Each Clicker2 configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh clicker2-stm32/<subdir>
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.

2
boards/cloudctrl/README.txt
View File

@ -465,7 +465,7 @@ Configurations
Each Cloudctrl configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh shenzhou/<subdir>
tools/configure.sh shenzhou:<subdir>
Where <subdir> is one of the following:

4
boards/demo9s12ne64/README.txt
View File

@ -121,7 +121,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh demo9s12nec64/<sub-dir>
tools/configure.sh demo9s12nec64:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -356,7 +356,7 @@ Common Configuration Notes
1. Each Freescale HCS12 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh demo9s12nec64/<subdir>
tools/configure.sh demo9s12nec64:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/dk-tm4c129x/README.txt
View File

@ -647,7 +647,7 @@ Configurations
Each DK-TM4C129X configuration is maintained in a
sub-directory and can be selected as follow:
tools/configure.sh dk-tm4c129x/<subdir>
tools/configure.sh dk-tm4c129x:<subdir>
Where <subdir> is one of the following:

6
boards/ea3131/README.txt
View File

@ -150,7 +150,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh ea3131/<sub-dir>
tools/configure.sh ea3131:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -205,7 +205,7 @@ Image Format
Then, to build the NuttX binary ready to load with the bootloader, just
following these steps:
- tools/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)
@ -591,7 +591,7 @@ Common Configuration Notes
1. Each EA3131 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh ea3131/<subdir>
tools/configure.sh ea3131:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

6
boards/ea3152/README.txt
View File

@ -149,7 +149,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh ea3152/<sub-dir>
tools/configure.sh ea3152:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -204,7 +204,7 @@ Image Format
Then, to build the NuttX binary ready to load with the bootloader, just
following these steps:
- tools/configure.sh ea3152/ostest # (using the ostest configuration for this example)
- 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)
@ -394,7 +394,7 @@ Configurations
Each EA3152 configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh ea3152/<subdir>
tools/configure.sh ea3152:<subdir>
Where <subdir> is one of the following:

2
boards/eagle100/README.txt
View File

@ -186,7 +186,7 @@ Common Configuration Notes
1. Each Eagle-100 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh eagle100/<subdir>
tools/configure.sh eagle100:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/efm32-g8xx-stk/README.txt
View File

@ -231,7 +231,7 @@ CONFIGURATIONS
Each EFM32 Gecko Starter Kit configuration is maintained in a sub-directory
and can be selected as follow:
tools/configure.sh efm32-g8xx-stk/<subdir>
tools/configure.sh efm32-g8xx-stk:<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

2
boards/efm32gg-stk3700/README.txt
View File

@ -183,7 +183,7 @@ Configurations
Each EFM32 Giant Gecko Starter Kit configuration is maintained in a sub-
directory and can be selected as follow:
tools/configure.sh efm32gg-stk3700/<subdir>
tools/configure.sh efm32gg-stk3700:<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

2
boards/ekk-lm3s9b96/README.txt
View File

@ -190,7 +190,7 @@ Configurations
Each Stellaris EKK-LM3S9b96 Evaluation Kit configuration is maintained in a
sub-directory and can be selected as follow:
tools/configure.sh ekk-lm3s9b96/<subdir>
tools/configure.sh ekk-lm3s9b96:<subdir>
Where <subdir> is one of the following:

2
boards/esp32-core/README.txt
View File

@ -577,7 +577,7 @@ Configurations
Each ESP32 core configuration is maintained in sub-directories and
can be selected as follow:
tools/configure.sh esp32-core/<subdir>
tools/configure.sh esp32-core:<subdir>
make oldconfig
Before building, make sure the PATH environment variable includes the

2
boards/ez80f910200kitg/README.txt
View File

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

2
boards/ez80f910200zco/README.txt
View File

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

2
boards/fire-stm32v2/README.txt
View File

@ -560,7 +560,7 @@ Configurations
Each M3 Wildfire configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh fire-stm32v2/<subdir>
tools/configure.sh fire-stm32v2:<subdir>
Where <subdir> is one of the following:

2
boards/flipnclick-pic32mz/README.txt
View File

@ -356,7 +356,7 @@ Information Common to All Configurations
1. Each PIC32MZ configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh flipnclick-pic32mz/<subdir>
tools/configure.sh flipnclick-pic32mz:<subdir>
Where typical options are -l to configure to build on Linux or -c to
configure for Cygwin under Linux. 'tools/configure.sh -h' will show

2
boards/flipnclick-sam3x/README.txt
View File

@ -546,7 +546,7 @@ Configurations
Each Flip&Click SAM3X configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] flipnclick-sam3x/<subdir>
tools/configure.sh [OPTIONS] flipnclick-sam3x:<subdir>
Where typical options are -l to configure to build on Linux or -c to
configure for Cygwin under Linux. 'tools/configure.sh -h' will show

2
boards/freedom-k64f/README.txt
View File

@ -809,7 +809,7 @@ Configurations
Each Freedom K64F configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh freedom-k64f/<subdir>
tools/configure.sh freedom-k64f:<subdir>
Where <subdir> is one of the following:

2
boards/freedom-k66f/README.txt
View File

@ -816,7 +816,7 @@ Configurations
Each Freedom K66F configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh freedom-K66F/<subdir>
tools/configure.sh freedom-K66F:<subdir>
Where <subdir> is one of the following:

4
boards/freedom-kl25z/README.txt
View File

@ -44,7 +44,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh freedom-kl25z/<sub-dir>
tools/configure.sh freedom-kl25z:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -274,7 +274,7 @@ Configurations
Each FREEDOM-KL25Z configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh freedom-kl25z/<subdir>
tools/configure.sh freedom-kl25z:<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

4
boards/freedom-kl26z/README.txt
View File

@ -44,7 +44,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh freedom-kl26z/<sub-dir>
tools/configure.sh freedom-kl26z:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -252,7 +252,7 @@ Configurations
Each FREEDOM-KL26Z configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh freedom-kl26z/<subdir>
tools/configure.sh freedom-kl26z:<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

2
boards/gapuino/README.txt
View File

@ -46,7 +46,7 @@ Configurations
Each gapuino configuration is maintained in a sub-directory and can
be selected as follow:
tools/configure.sh gapuino/<subdir>
tools/configure.sh gapuino:<subdir>
Where <subdir> is one of the following:

2
boards/hymini-stm32v/README.txt
View File

@ -354,7 +354,7 @@ NOTES:
Each HY-MiniSTM32V configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh hymini-stm32v/<subdir>
tools/configure.sh hymini-stm32v:<subdir>
Where <subdir> is one of the following:

2
boards/imxrt1050-evk/README.txt
View File

@ -116,7 +116,7 @@ Configurations
Each i.MX RT 10050 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] imxrt1050-evk/<subdir>
tools/configure.sh [OPTIONS] imxrt1050-evk:<subdir>
Where typical options are -l to configure to build on Linux or -c to
configure for Cygwin under Linux. 'tools/configure.sh -h' will show

2
boards/imxrt1060-evk/README.txt
View File

@ -134,7 +134,7 @@ Configurations
Each i.MX RT 1060 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] imxrt1060-evk/<subdir>
tools/configure.sh [OPTIONS] imxrt1060-evk:<subdir>
Where typical options are -l to configure to build on Linux or -c to
configure for Cygwin under Linux. 'tools/configure.sh -h' will show

2
boards/kwikstik-k40/README.txt
View File

@ -306,7 +306,7 @@ Configurations
Each KwikStik-K40 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh kwikstik-k40/<subdir>
tools/configure.sh kwikstik-k40:<subdir>
Where <subdir> is one of the following:

2
boards/launchxl-tms57004/README.txt
View File

@ -172,7 +172,7 @@ Configurations
Each LaunchXL-TMS50704 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh launchxl-tms57004/<subdir>
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.

4
boards/lc823450-xgevk/README.txt
View File

@ -163,7 +163,7 @@ nsh> wdog
IPL2 is the 2nd boot loader based on NuttX and can be built as follows.
$ make distclean
$ ./tools/configure.sh lc823450-xgevk/ipl2
$ ./tools/configure.sh lc823450-xgevk:ipl2
$ make V=1
$ MakeIPL2 ./nuttx.bin 0 2 0 0 0
$ cp LC8234xx_17S_start_data.boot_bin /tmp/
@ -172,7 +172,7 @@ To write the IPL2 (LC8234xx_17S_start_data.boot_bin),
firstly build USB configuration image.
$ make distclean
$ ./tools/configure.sh lc823450-xgevk/usb
$ ./tools/configure.sh lc823450-xgevk:usb
$ make V=1
Load the nuttx.bin with openocd + gdb

2
boards/lincoln60/README.txt
View File

@ -272,7 +272,7 @@ Configurations
Each Lincoln 60 configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh lincoln60/<subdir>
tools/configure.sh lincoln60:<subdir>
Where <subdir> is one of the following:

2
boards/lm3s6432-s2e/README.txt
View File

@ -195,7 +195,7 @@ Configurations
Each Stellaris MDL-S2E Reference Design configuration is maintained in a
sub-directory and can be selected as follow:
tools/configure.sh lm3s6432-s2e/<subdir>
tools/configure.sh lm3s6432-s2e:<subdir>
Where <subdir> is one of the following:

2
boards/lm3s6965-ek/README.txt
View File

@ -333,7 +333,7 @@ Configurations
Each Stellaris LM3S6965 Evaluation Kit configuration is maintained in a
sub-directory and can be selected as follow:
tools/configure.sh lm3s6965-ek/<subdir>
tools/configure.sh lm3s6965-ek:<subdir>
Where <subdir> is one of the following:

2
boards/lm3s8962-ek/README.txt
View File

@ -253,7 +253,7 @@ Configurations
Each Stellaris LM3S8962 Evaluation Kit configuration is maintained in a
sub-directory and can be selected as follow:
tools/configure.sh lm3s8962-ek/<subdir>
tools/configure.sh lm3s8962-ek:<subdir>
Where <subdir> is one of the following:

2
boards/lm4f120-launchpad/README.txt
View File

@ -462,7 +462,7 @@ Configurations
Each LM4F120 LaunchPad configuration is maintained in a
sub-directory and can be selected as follow:
tools/configure.sh lm4f120-launchpad/<subdir>
tools/configure.sh lm4f120-launchpad:<subdir>
Where <subdir> is one of the following:

2
boards/lpc4330-xplorer/README.txt
View File

@ -591,7 +591,7 @@ Configurations
Each LPC4330-Xplorer configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh lpc4330-xplorer/<subdir>
tools/configure.sh lpc4330-xplorer:<subdir>
Where <subdir> is one of the following:

2
boards/lpc4337-ws/README.txt
View File

@ -630,7 +630,7 @@ Configurations
Each LPC4337-ws configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh LPC4337-ws/<subdir>
tools/configure.sh LPC4337-ws:<subdir>
Where <subdir> is one of the following:

2
boards/lpc4357-evb/README.txt
View File

@ -627,7 +627,7 @@ Configurations
Each LPC4357-EVB configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh lpc4357-evb/<subdir>
tools/configure.sh lpc4357-evb:<subdir>
Where <subdir> is one of the following:

2
boards/lpc4370-link2/README.txt
View File

@ -630,7 +630,7 @@ Configurations
Each LPC4370-Link2 configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh LPC4370-Link2/<subdir>
tools/configure.sh LPC4370-Link2:<subdir>
Where <subdir> is one of the following:

2
boards/lpcxpresso-lpc1768/README.txt
View File

@ -557,7 +557,7 @@ Configurations
Each LPCXpresso configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh lpcxpresso-lpc1768/<subdir>
tools/configure.sh lpcxpresso-lpc1768:<subdir>
Where <subdir> is one of the following:

2
boards/lpcxpresso-lpc54628/README.txt
View File

@ -135,7 +135,7 @@ Configurations
Each LPCXpresso-LPC54628 configuration is maintained in a sub-directory
and can be selected as follow:
.tools/configure.sh [OPTIONS] lpcxpresso-lpc54628/<subdir>
.tools/configure.sh [OPTIONS] lpcxpresso-lpc54628:<subdir>
See '.tools/configure.sh -h' for a list of all options. The most typical
are -l to select the Linux host or -c to select the Windows Cygwin host.

2
boards/makerlisp/README.txt
View File

@ -218,7 +218,7 @@ Common Configuration Notes
in subdirectories. To configure any specific configuration, do the
following steps:
tools/configure.sh [OPTIONS] makerlisp/<sub-directory>
tools/configure.sh [OPTIONS] makerlisp:<sub-directory>
make
Where <sub-directory> is the specific board configuration that you

2
boards/maple/README.txt
View File

@ -108,7 +108,7 @@ Configurations
Each Maple configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh maple/<subdir>
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.

2
boards/mbed/README.txt
View File

@ -245,7 +245,7 @@ Configurations
Each mbed configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh mbed/<subdir>
tools/configure.sh mbed:<subdir>
Where <subdir> is one of the mbed subdirectories described in the
following paragraph.

2
boards/mcb1700/README.txt
View File

@ -246,7 +246,7 @@ Configurations
Each mcb1700 configuration is maintained in a sub-directory and can be selected
as follow:
tools/configure.sh mcb1700/<subdir>
tools/configure.sh mcb1700:<subdir>
Where <subdir> is one of the mcb1700 subdirectories described in the
following paragraph.

4
boards/mcu123-lpc214x/README.txt
View File

@ -89,7 +89,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh eagle100/<sub-dir>
tools/configure.sh eagle100:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -308,7 +308,7 @@ Configurations
1. Each NXP LPC214x configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh mcu123-lpc214x/<subdir>
tools/configure.sh mcu123-lpc214x:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/metro-m4/README.txt
View File

@ -277,7 +277,7 @@ Configurations
Each Adafruit Metro M4 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] metro-m4/<subdir>
tools/configure.sh [OPTIONS] metro-m4:<subdir>
Do 'tools/configure.sh -h' for the list of options. If you are building
under Windows with Cygwin, you would need the -c option, for example.

4
boards/micropendous3/README.txt
View File

@ -287,7 +287,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
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:
@ -501,7 +501,7 @@ Common Configuration Notes
1. Each Micropendous3 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh micropendous3/<subdir>
tools/configure.sh micropendous3:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/mikroe-stm32f4/README.txt
View File

@ -466,7 +466,7 @@ Configurations
Each Mikroe-STM32F4 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh mikroe-stm32f4/<subdir>
tools/configure.sh mikroe-stm32f4:<subdir>
If this is a Windows native build, then configure.bat should be used
instead of configure.sh:

2
boards/mirtoo/README.txt
View File

@ -831,7 +831,7 @@ Configurations
Each PIC32MX configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh mirtoo/<subdir>
tools/configure.sh mirtoo:<subdir>
Where <subdir> is one of the following:

2
boards/misoc/README.txt
View File

@ -20,7 +20,7 @@ Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
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

2
boards/moteino-mega/README.txt
View File

@ -241,7 +241,7 @@ Common Configuration Notes
1. Each MoteinoMEGA configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh moteino-mega/<subdir>
tools/configure.sh moteino-mega:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

4
boards/ne64badge/README.txt
View File

@ -228,7 +228,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh ne64badge/<sub-dir>
tools/configure.sh ne64badge:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -463,7 +463,7 @@ Common Configuration Notes
1. Each Freescale HCS12 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh ne64badge/<subdir>
tools/configure.sh ne64badge:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/nr5m100-nexys4/README.txt
View File

@ -232,7 +232,7 @@ Configurations
Each nr5m100-nexys4 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh nr5m100-nexys4/<subdir>
tools/configure.sh nr5m100-nexys4:<subdir>
Where <subdir> is one of the following:

2
boards/nrf52-generic/README.txt
View File

@ -94,7 +94,7 @@ Configurations
Each configuration is maintained in a sub-directory and can be selected as
follow:
tools/configure.sh nrf52-generic/<subdir>
tools/configure.sh nrf52-generic:<subdir>
Where <subdir> is one of the following:

4
boards/ntosd-dm320/README.txt
View File

@ -166,7 +166,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>nuttx.
tools/configure.sh ntosd-dm320/<sub-dir>
tools/configure.sh ntosd-dm320:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -271,7 +271,7 @@ Common Configuration Notes
1. Each Neuros OSD configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh ntosd-dm320/<subdir>
tools/configure.sh ntosd-dm320:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/ntosd-dm320/doc/README.txt
View File

@ -38,7 +38,7 @@ General instructions.
4. Configure NuttX:
cd <directory>/nuttx/tools
./configure.sh ntosd-dm320
./configure.sh ntosd-dm320:nsh
5. Build the toolchain:

6
boards/nucleo-144/README.txt
View File

@ -207,7 +207,7 @@ Basic configuration & build steps
different from the default in your PATH variable).
- Configures nuttx creating .config file in the nuttx directory.
$ tools/configure.sh nucleo-f746zg/nsh
$ 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.
@ -514,7 +514,7 @@ f7xx-nsh:
b. If this is the initial configuration then execute
./tools/configure.sh nucleo-144/nsh
./tools/configure.sh nucleo-144:nsh
in nuttx/ in order to start configuration process.
Caution: Doing this step more than once will overwrite .config with
@ -579,7 +579,7 @@ f7xx-evalos:
b. If this is the initial configuration then execute
./tools/configure.sh nucleo-144/evalos
./tools/configure.sh nucleo-144:evalos
in nuttx/ in order to start configuration process.
Caution: Doing this step more than once will overwrite .config with

2
boards/nucleo-f072rb/README.txt
View File

@ -209,7 +209,7 @@ Configurations
Each configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh nucleo-f072rb/<subdir>
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.

2
boards/nucleo-f091rc/README.txt
View File

@ -195,7 +195,7 @@ Configurations
Each configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh nucleo-f091rc/<subdir>
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.

4
boards/nucleo-f446re/README.txt
View File

@ -237,7 +237,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
$ tools/configure.sh nucleo-f446re/nsh
$ tools/configure.sh nucleo-f446re:nsh
$ make qconfig
$ V=1 make context all 2>&1 | tee mout
@ -280,7 +280,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768/<sub-dir>
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>
2. Download the latest buildroot package into <some-dir>

4
boards/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.
$ 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,7 +305,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768/<sub-dir>
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>
2. Download the latest buildroot package into <some-dir>

2
boards/nucleo-h743zi/README.txt
View File

@ -105,7 +105,7 @@ Configurations
Each Nucleo-H743ZI configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [options] viewtool-stm32f107/<subdir>
tools/configure.sh [options] viewtool-stm32f107:<subdir>
Where options should specify the host build platform (-l for Linux, -c for
Cygwin under Windows, etc.). Try 'tools/configure.sh -h' for the complete

4
boards/nucleo-l432kc/README.txt
View File

@ -230,7 +230,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
$ tools/configure.sh nucleo-l432kc/nsh
$ tools/configure.sh nucleo-l432kc:nsh
$ make qconfig
$ V=1 make context all 2>&1 | tee mout
@ -273,7 +273,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768/<sub-dir>
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>
2. Download the latest buildroot package into <some-dir>

2
boards/nucleo-l452re/README.txt
View File

@ -201,7 +201,7 @@ Configurations
Each configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh nucleo-l452re/<subdir>
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.

4
boards/nucleo-l476rg/README.txt
View File

@ -243,7 +243,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
$ tools/configure.sh nucleo-l476rg/nsh
$ tools/configure.sh nucleo-l476rg:nsh
$ make qconfig
$ V=1 make context all 2>&1 | tee mout
@ -286,7 +286,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768/<sub-dir>
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>
2. Download the latest buildroot package into <some-dir>

2
boards/nucleo-l496zg/README.txt
View File

@ -318,7 +318,7 @@ nsh:
b. If this is the initial configuration then execute
./tools/configure.sh nucleo-l496zg/nsh
./tools/configure.sh nucleo-l496zg:nsh
in nuttx/ in order to start configuration process.
Caution: Doing this step more than once will overwrite .config with

4
boards/nutiny-nuc120/README.txt
View File

@ -45,7 +45,7 @@ NuttX Buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh nutiny-nuc120/<sub-dir>
tools/configure.sh nutiny-nuc120:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -260,7 +260,7 @@ Configurations
Each NuTiny-SDK-NUC120 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh nutiny-nuc120/<subdir>
tools/configure.sh nutiny-nuc120:<subdir>
Where <subdir> is one of the following:

2
boards/olimex-efm32g880f128-stk/README.txt
View File

@ -134,7 +134,7 @@ Configurations
Each EFM32G880F128-STK configuration is maintained in a sub-director
and can be selected as follow:
tools/configure.sh olimex-efm32g880f128-stk/<subdir>
tools/configure.sh olimex-efm32g880f128-stk:<subdir>
Where <subdir> is one of the following:

6
boards/olimex-lpc-h3131/README.txt
View File

@ -152,7 +152,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
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>
@ -253,7 +253,7 @@ Image Format
Then, to build the NuttX binary ready to load with the bootloader, just
following these steps:
- tools/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)
@ -488,7 +488,7 @@ Configurations
Each LPC-H3131 configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh olimex-lpc-h3131/<subdir>
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.

2
boards/olimex-lpc1766stk/README.txt
View File

@ -682,7 +682,7 @@ Common Configuration Notes
1. Each Olimex LPC1766-STK configuration is maintained in a
sub-directory and can be selected as follow:
tools/configure.sh olimex-lpc1766stk/<subdir>
tools/configure.sh olimex-lpc1766stk:<subdir>
Where <subdir> is one of the sub-directories identified in the following
paragraphs.

2
boards/olimex-stm32-e407/README.txt
View File

@ -11,7 +11,7 @@ Configurations
Each Olimex-STM32-E407 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] olimex-stm32-e407/<subdir>
tools/configure.sh [OPTIONS] olimex-stm32-e407:<subdir>
Typical options include -l for a Linux host platform or -c for Cygwin
host platform. See 'tools/configure.sh -h' for other options. And

2
boards/olimex-stm32-p407/README.txt
View File

@ -327,7 +327,7 @@ Information Common to All Configurations
Each Olimex STM32-P407 configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh olimex-stm32-p407/<subdir>
tools/configure.sh olimex-stm32-p407:<subdir>
Where <subdir> is one of the configuration sub-directories listed in the
following section.

4
boards/olimex-strp711/README.txt
View File

@ -173,7 +173,7 @@ NuttX buildroot Toolchain
1. You must have already configured Nuttx in <some-dir>nuttx.
tools/configure.sh olimex-strp711/<sub-dir>
tools/configure.sh olimex-strp711:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -370,7 +370,7 @@ Common Configuration Notes:
1. Each Olimex STRP711 configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh olimex-strp711/<subdir>
tools/configure.sh olimex-strp711:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/pcduino-a10/README.txt
View File

@ -326,7 +326,7 @@ Configurations
Each pcDuino configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh [OPTIONS] pcduino-a10/<subdir>
tools/configure.sh [OPTIONS] pcduino-a10:<subdir>
Where [OPTIONS] include -l to configure for a Linux host platform and
-c means to configure for a Windows Cygwin host platform. -h will give

2
boards/photon/README.txt
View File

@ -32,7 +32,7 @@ Selecting the Photon board on NuttX
2) Enter inside nuttx/tools and configure to use the Photon board:
$ cd nuttx
$ tools/configure.sh photon/wlan
$ tools/configure.sh photon:wlan
Configuring NuttX to use your Wireless Router (aka Access Point)
================================================================

2
boards/pic32mx-starterkit/README.txt
View File

@ -1003,7 +1003,7 @@ Configurations
Each PIC32MX configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh pic32mx-starterkit/<subdir>
tools/configure.sh pic32mx-starterkit:<subdir>
Where <subdir> is one of the following:

2
boards/pic32mx7mmb/README.txt
View File

@ -585,7 +585,7 @@ Configurations
Each PIC32MX configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh pic32mx7mmb/<subdir>
tools/configure.sh pic32mx7mmb:<subdir>
Where <subdir> is one of the following:

2
boards/pic32mz-starterkit/README.txt
View File

@ -363,7 +363,7 @@ Information Common to All Configurations
Each PIC32MZ configuration is maintained in a sub-directory and can be
selected as follow:
tools/configure.sh [OPTIONS] pic32mz-starterkit/<subdir>
tools/configure.sh [OPTIONS] pic32mz-starterkit:<subdir>
Where typical options are -l to configure to build on Linux or -c to
configure for Cygwin under Linux. 'tools/configure.sh -h' will show

2
boards/pnev5180b/README.txt
View File

@ -79,7 +79,7 @@ Each PNEV5180B configuration is maintained in a sub-directory and can be
selected as follow:
cd tools
./configure.sh pnev5180b/<subdir>
./configure.sh pnev5180b:<subdir>
cd -
Where <subdir> is one of the following:

4
boards/qemu-i486/README.txt
View File

@ -118,7 +118,7 @@ Buildroot Instructions
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh qemu-i486/<sub-dir>
tools/configure.sh qemu-i486:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -160,7 +160,7 @@ Common Configuration Notes
1. Each Qemu-i486 Web Server configuration is maintained in a sub-directory
and can be selected as follow:
tools/configure.sh qemu-i486/<subdir>
tools/configure.sh qemu-i486:<subdir>
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.

2
boards/sabre-6quad/README.txt
View File

@ -674,7 +674,7 @@ Information Common to All Configurations
Each Sabre-6Quad configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh sabre-6quad/<subdir>
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.

2
boards/sam3u-ek/README.txt
View File

@ -205,7 +205,7 @@ Configurations
Each SAM3U-EK configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh sam3u-ek/<subdir>
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.

2
boards/sam4e-ek/README.txt
View File

@ -1025,7 +1025,7 @@ Configurations
Each SAM4E-EK configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh sam4e-ek/<subdir>
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.

2
boards/sam4l-xplained/README.txt
View File

@ -382,7 +382,7 @@ Configurations
Each SAM4L Xplained Pro configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh sam4l-xplained/<subdir>
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.

2
boards/sam4s-xplained-pro/README.txt
View File

@ -273,7 +273,7 @@ Configurations
Each SAM4S Xplained configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.shsam4s-xplained-pro/<subdir>
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.

2
boards/sam4s-xplained/README.txt
View File

@ -268,7 +268,7 @@ Configurations
Each SAM4S Xplained configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.shsam4s-xplained/<subdir>
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.

2
boards/sama5d2-xult/README.txt
View File

@ -720,7 +720,7 @@ Configurations
Each SAMA5D2-XULT configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh sama5d2-xult/<subdir>
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.

6
boards/sama5d3-xplained/README.txt
View File

@ -189,7 +189,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh sama5d3-xplained/<sub-dir>
tools/configure.sh sama5d3-xplained:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -239,7 +239,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh sama5d3-xplained/<sub-dir>
tools/configure.sh sama5d3-xplained:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -2967,7 +2967,7 @@ Configurations
Each SAMA5D3-Xplained configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh sama5d3-xplained/<subdir>
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.

8
boards/sama5d3x-ek/README.txt
View File

@ -211,7 +211,7 @@ NuttX EABI "buildroot" Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh sama5d3x-ek/<sub-dir>
tools/configure.sh sama5d3x-ek:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -261,7 +261,7 @@ NXFLAT Toolchain
1. You must have already configured Nuttx in <some-dir>/nuttx.
tools/configure.sh sama5d3x-ek/<sub-dir>
tools/configure.sh sama5d3x-ek:<sub-dir>
2. Download the latest buildroot package into <some-dir>
@ -367,7 +367,7 @@ Creating and Using NORBOOT
the norboot configuration and setup the PATH variable in order to do
the build:
tools/configure.sh sama5d3x-ek/<subdir>
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.
@ -3290,7 +3290,7 @@ Configurations
Each SAMA5D3x-EK configuration is maintained in a sub-directory and
can be selected as follow:
tools/configure.sh sama5d3x-ek/<subdir>
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.

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