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

Change naming configs/ to boards in comments, Documentation, etc. Still a few more to go.

Browse Source
This commit is contained in:
Gregory Nutt 2019-08-05 07:13:48 -06:00
parent a1c991d921
commit 615c0ea7ee
513 changed files with 1336 additions and 1336 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/NXGraphicsSubsystem.html
View File

@ -960,7 +960,7 @@ struct nx_callback_s
<li>
<p>
The NX server may be started in your board startup logic by simply calling the function <code> nxmu_start()</code>.
The board startup logic usually resides the the <code>configs/<i>board</i>/src</code> directory.
The board startup logic usually resides the the <code>boards/<i>board</i>/src</code> directory.
The board startup logic can run automatically during the early system if <code>CONFIG_BOARD_LATE_INITIALIZE</code> is defined in the configuration.
Or, the board startup logic can execute under control of the application by calling the <code>boardctl(BOARDIOC_INIT, arg)</code> OS interface.
</p>
@ -4203,13 +4203,13 @@ static FAR const struct nx_fontpackage_s *g_fontpackages[] =
<p><b>Building <code>apps/examples/nx</code></b>.
NX testing was performed using <code>apps/examples/nx</code> with the
Linux/Cygwin-based NuttX simulator.
Configuration files for building this test can be found in <code>configs/sim/nx</code>
and <code>configs/sim/nx11</code>.
Configuration files for building this test can be found in <code>boards/sim/nx</code>
and <code>boards/sim/nx11</code>.
There are two alternative configurations for building the simulation:
</p>
<ol>
<li>
The configuration using the configuration file at <code>configs/sim/nx/defconfig</code>.
The configuration using the configuration file at <code>boards/sim/nx/defconfig</code>.
This default configuration exercises the NX logic a 8 BPP but provides no visual feedback.
In this configuration, a very simple, simulated framebuffer driver is used that is
based upon a simple region of memory posing as video memory.
@ -4224,7 +4224,7 @@ make
</li>
<li>
<p>
The preferred configuration is at <code>configs/sim/nx11/defconfig</code>.
The preferred configuration is at <code>boards/sim/nx11/defconfig</code>.
This configuration extends the test with a simulated framebuffer driver
that uses an X window as a framebuffer.
This is a superior test configuration because the X window appears at your desktop
@ -4270,7 +4270,7 @@ sudo ln -s libXext.so.6.4.0 libXext.so
</li>
<li><p>
Refer to the readme file in sim configuration
<a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sim/README.txt" target="_blank">README.txt</a> file for additional information.
<a href="https://bitbucket.org/nuttx/nuttx/boards/src/master/sim/README.txt" target="_blank">README.txt</a> file for additional information.
</p></li>
</ul>
</p>

36
Documentation/NuttShell.html
View File

@ -1164,8 +1164,8 @@ mount -t vfat /dev/ram1 /tmp
<p>
<b>NOTE</b>:
<code>apps/nshlib/rcS.template</code> generates the standard, default <code>nsh_romfsimg.h</code> file.
If <code>CONFIG_NSH_ARCHROMFS</code> is defined in the NuttX configuration file, then a custom, board-specific <code>nsh_romfsimg.h</code> file residing in <code>configs/&lt;board&gt;/include</code> will be used.
NOTE when the OS is configured, <code>include/arch/board</code> will be linked to <code>configs/&lt;board&gt;/include</code>.
If <code>CONFIG_NSH_ARCHROMFS</code> is defined in the NuttX configuration file, then a custom, board-specific <code>nsh_romfsimg.h</code> file residing in <code>boards/&lt;board&gt;/include</code> will be used.
NOTE when the OS is configured, <code>include/arch/board</code> will be linked to <code>boards/&lt;board&gt;/include</code>.
</p>
<p>
All of the startup-behavior is contained in <code>rcS.template</code>. The
@ -4022,7 +4022,7 @@ nsh&gt;
<p>
The behavior of NSH can be modified with the following settings in
the <code>configs/&lt;board-name&gt;/defconfig</code> file:
the <code>boards/&lt;board-name&gt;/defconfig</code> file:
</p>
<center><table width="100%">
@ -4545,7 +4545,7 @@ set FOOBAR ABC_${FOO}_${BAR}
<tr>
<td valign="top"><b><code>CONFIG_NSH_ARCHROMFS</code></b></td>
<td>
May be defined to specify an alternative ROMFS image that can be found at <code>configs/&lt;board&gt;/include/nsh_romfsimg.h</code>.
May be defined to specify an alternative ROMFS image that can be found at <code>boards/&lt;board&gt;/include/nsh_romfsimg.h</code>.
</td>
</tr>
<tr>
@ -4652,7 +4652,7 @@ set FOOBAR ABC_${FOO}_${BAR}
<li>
<p>
If you have C++ static initializers, it will call your implementation of <code>up_cxxinitialize()</code> which will, in turn, call those static initializers.
For the case of the STM3240G-EVAL board, the implementation of <code>up_cxxinitialize()</code> can be found at <code>nuttx/configs/stm3240g-eval/src/up_cxxinitialize.c</code>.
For the case of the STM3240G-EVAL board, the implementation of <code>up_cxxinitialize()</code> can be found at <code>nuttx/boards/stm3240g-eval/src/up_cxxinitialize.c</code>.
</p>
<li>
<p>
@ -4758,7 +4758,7 @@ mount -t vfat /dev/ram1 /tmp
<p>
<code>board_app_initialize()</code>:
Next any architecture-specific NSH initialization will be performed (if any).
For the STM3240G-EVAL, this architecture specific initialization can be found at <code>configs/stm3240g-eval/src/stm32_appinit.c</code>.
For the STM3240G-EVAL, this architecture specific initialization can be found at <code>boards/stm3240g-eval/src/stm32_appinit.c</code>.
This it does things like: (1) Initialize SPI devices, (2) Initialize SDIO, and (3) mount any SD cards that may be inserted.
</p>
<li>
@ -5156,7 +5156,7 @@ CONFIG_SCHED_WAITPID=y
<ol>
<li>
<p>
You can extend the initialization logic in <code>configs/stm3240g-eval/src/stm32_appinit.c</code>.
You can extend the initialization logic in <code>boards/stm3240g-eval/src/stm32_appinit.c</code>.
The logic there is called each time that NSH is started and is good place in particular for any device-related initialization.
</p>
<li>
@ -5273,13 +5273,13 @@ mount -t vfat /dev/ram1 /tmp
They might provide useful examples:
</p>
<ul>
<code>configs/hymini-stm32v/nsh2<br>
configs/ntosd-dm320/nsh<br>
configs/sim/nsh<br>
configs/sim/nsh2<br>
configs/sim/nx<br>
configs/sim/nx11<br>
configs/sim/touchscreen<br>
<code>boards/hymini-stm32v/nsh2<br>
boards/ntosd-dm320/nsh<br>
boards/sim/nsh<br>
boards/sim/nsh2<br>
boards/sim/nx<br>
boards/sim/nx11<br>
boards/sim/touchscreen<br>
</ul>
<p>
In most of these cases, the configuration sets up the <i>default</i> <code>/etc/init.d/rcS</code> script.
@ -5338,7 +5338,7 @@ mount -t vfat /dev/ram1 /tmp
</p>
<p>
To generate a custom <code>rcS</code> file a copy of <code>rcS.template</code> needs to be placed at <code>tools/</code> and changed according to the desired start-up behaviour.
Running <code>tools/mkromfsimg.h</code> creates <code>nsh_romfsimg.h</code> which needs to be copied to <code>apps/nshlib</code> OR if <code>CONFIG_NSH_ARCHROMFS</code> is defined to <code>configs/&lt;board&gt;/include</code>.
Running <code>tools/mkromfsimg.h</code> creates <code>nsh_romfsimg.h</code> which needs to be copied to <code>apps/nshlib</code> OR if <code>CONFIG_NSH_ARCHROMFS</code> is defined to <code>boards/&lt;board&gt;/include</code>.
</p>
</ol>
@ -5348,8 +5348,8 @@ mount -t vfat /dev/ram1 /tmp
</p>
<p>
If <code>CONFIG_NSH_ARCHROMFS</code> is defined in the NuttX configuration file, then a custom, board-specific <code>nsh_romfsimg.h</code> file residing in <code>configs/&lt;board&gt;/include</code>will be used.
NOTE when the OS is configured, <code>include/arch/board</code> will be linked to <code>configs/&lt;board&gt;/include</code>.
If <code>CONFIG_NSH_ARCHROMFS</code> is defined in the NuttX configuration file, then a custom, board-specific <code>nsh_romfsimg.h</code> file residing in <code>boards/&lt;board&gt;/include</code>will be used.
NOTE when the OS is configured, <code>include/arch/board</code> will be linked to <code>boards/&lt;board&gt;/include</code>.
</p>
<p>
@ -5693,7 +5693,7 @@ xxd -i romfs_img >nsh_romfsimg.h
</li>
</ol>
<p>
There is a good example of how to do this in the NSH simulation configuration at <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sim/nsh/">configs/sim/nsh</a>. The ROMFS support files are provided at <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sim/include/">configs/sim/include</a> and the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/sim/include/README.txt">README.txt</a> file at the location provides detailed information about creating and modifying the ROMFS file system.
There is a good example of how to do this in the NSH simulation configuration at <a href="https://bitbucket.org/nuttx/nuttx/boards/src/master/sim/nsh/">boards/sim/nsh</a>. The ROMFS support files are provided at <a href="https://bitbucket.org/nuttx/nuttx/boards/src/master/sim/include/">boards/sim/include</a> and the <a href="https://bitbucket.org/nuttx/nuttx/boards/src/master/sim/include/README.txt">README.txt</a> file at the location provides detailed information about creating and modifying the ROMFS file system.
</p>
<table width ="100%">

280
Documentation/NuttX.html
View File

File diff suppressed because it is too large Load Diff

2
Documentation/NuttXNxFlat.html
View File

@ -331,7 +331,7 @@
<code>cd </code>&lt;some-dir&gt;/buildroot</code>
</li>
<li>
Copy a configuration file into the top buildroot directory: <code>cp configs/abc-defconfig-x.y.z .config</code>.
Copy a configuration file into the top buildroot directory: <code>cp boards/abc-defconfig-x.y.z .config</code>.
</li>
<li>
Enable building of the NXFLAT tools by <code>make menuconfig</code>.

54
Documentation/NuttxPortingGuide.html
View File

@ -30,7 +30,7 @@
</ul>
<a href="#DirStructBinFmt">2.3 nuttx/binfmt/</a><br>
<a href="#DirStructAudio">2.4 nuttx/audio/</a><br>
<a href="#DirStructConfigs">2.5 nuttx/configs/</a>
<a href="#DirStructConfigs">2.5 nuttx/boards/</a>
<ul>
<a href="#configsdirectorystructure">2.5.1 Subdirectory Structure</a><br>
<a href="#summaryofconfigfiles">2.5.2 Summary of Files</a>
@ -260,7 +260,7 @@
into the build.
</p>
<p>
See also <code>arch/README.txt</code> and <code>configs/README.txt</code>.
See also <code>arch/README.txt</code> and <code>boards/README.txt</code>.
</p>
<table width ="100%">
@ -526,11 +526,11 @@
</p>
<p>
These board-specific configuration files can be found in the
<code>configs/</code><i>&lt;board-name&gt;</i><code>/</code> sub-directories and are discussed
<code>boards/</code><i>&lt;board-name&gt;</i><code>/</code> sub-directories and are discussed
in a paragraph <a href="#configsdirectorystructure">below</a>.
</p>
<p>
The directory <code>configs/stm32f4disovery/</code>, as an example, holds board-specific logic for the STM32F4 Discovery board and is selected via the <code>CONFIG_ARCH_BOARD=&quot;stm32f4discovery&quot;</code> configuration setting.
The directory <code>boards/stm32f4disovery/</code>, as an example, holds board-specific logic for the STM32F4 Discovery board and is selected via the <code>CONFIG_ARCH_BOARD=&quot;stm32f4discovery&quot;</code> configuration setting.
</p>
</li>
</ul>
@ -793,7 +793,7 @@
<h2>2.5 <a name="DirStructConfigs">nuttx/configs</a></h2>
<p>
The <code>configs/</code> subdirectory contains configuration data for each board.
The <code>boards/</code> subdirectory contains configuration data for each board.
These board-specific configurations plus the architecture-specific configurations in
the <code>arch/</code> subdirectory complete define a customized port of NuttX.
</p>
@ -801,7 +801,7 @@
<h3><a name="configsdirectorystructure">2.5.1 Subdirectory Structure</a></h3>
<p>
The configs directory contains board specific configuration files. Each board must
provide a subdirectory &lt;board-name&gt; under <code>configs/</code> with the following characteristics:
provide a subdirectory &lt;board-name&gt; under <code>boards/</code> with the following characteristics:
</p>
<ul><pre>
<i>&lt;board-name&gt;</i>
@ -850,7 +850,7 @@
</ul>
<h4><a name="boardconfigsubdirs">2.5.2.2 Board Specific Configuration Sub-Directories</a></h4>
<p>
The <code>configs/</code><i>&lt;board-name&gt;</i><code>/</code> sub-directory holds all of the
The <code>boards/</code><i>&lt;board-name&gt;</i><code>/</code> sub-directory holds all of the
files that are necessary to configure NuttX for the particular board.
A board may have various different configurations using the common source files.
Each board configuration is described by two files: <code>Make.defs</code> and <code>defconfig</code>.
@ -920,7 +920,7 @@
<h3><a name="supportedboards">2.5.3 Supported Boards</a></h3>
<p>
All of the specific boards supported by NuttX are identified in the <a href="https://bitbucket.org/nuttx/nuttx/configs/src/master/README.txt" target="_blank">README.txt</a> file.
All of the specific boards supported by NuttX are identified in the <a href="https://bitbucket.org/nuttx/nuttx/boards/src/master/README.txt" target="_blank">README.txt</a> file.
</p>
<h3><a name="newboardconfig">2.5.4 Adding a New Board Configuration</a></h3>
<p>
@ -928,14 +928,14 @@
Now, how do you hook this board into the configuration system so that you can select with <code>make menuconfig</code>?
</p>
<p>
You will need modify the file <code>configs/Kconfig</code>.
You will need modify the file <code>boards/Kconfig</code>.
Let's look at the STM32F4-Discovery configuration in the <code>Kconfig</code> file and see how we would add a new board directory to the configuration.
For this configuration let's say that you new board resides in the directory <code>configs/myboard</code>;
For this configuration let's say that you new board resides in the directory <code>boards/myboard</code>;
It uses an MCU selected with <code>CONFIG_ARCH_CHIP_MYMCU</code>; and you want the board to be selected with <code>CONFIG_ARCH_BOARD_MYBOARD</code>.
Then here is how you can clone the STM32F4-Discovery configuration in <code>configs/Kconfig</code> to support your new board configuration.
Then here is how you can clone the STM32F4-Discovery configuration in <code>boards/Kconfig</code> to support your new board configuration.
</p>
<p>
In <code>configs/Kconfig</code> for the stm32f4-discovery, you will see a configuration definition like this:
In <code>boards/Kconfig</code> for the stm32f4-discovery, you will see a configuration definition like this:
<p>
<ul><pre>
config ARCH_BOARD_STM32F4_DISCOVERY
@ -966,7 +966,7 @@ config ARCH_BOARD_MYBOARD
based on the MYMCU processor.
</pre></ul>
<p>
Later in the <code>configs/Kconfig</code> file, you will see a long, long string configuration with lots of defaults like this:
Later in the <code>boards/Kconfig</code> file, you will see a long, long string configuration with lots of defaults like this:
</p>
<ul><pre>
config ARCH_BOARD
@ -980,7 +980,7 @@ config ARCH_BOARD
</pre></ul>
<p>
This logic will assign string value to a configuration variable called <code>CONFIG_ARCH_BOARD</code> that will name the directory where the board-specific files reside.
In our case, these files reside in <code>configs/myboard</code> and we add the following to the long list of defaults (again in alphabetical order):
In our case, these files reside in <code>boards/myboard</code> and we add the following to the long list of defaults (again in alphabetical order):
</p>
<ul><pre>
default "myboard" if ARCH_BOARD_MYBOARD
@ -989,15 +989,15 @@ config ARCH_BOARD
Now the build system knows where to find your board configuration!
</p>
<p>
And finally, add something like this near the bottom of <code>configs/myboard</code>:
And finally, add something like this near the bottom of <code>boards/myboard</code>:
</p>
<ul><pre>
if ARCH_BOARD_MYBOARD
source "configs/myboard/Kconfig"
source "boards/myboard/Kconfig"
endif
</pre></ul>
<p>
This includes additional, board-specific configuration variable definitions in <code>configs/myboard/Kconfig</code>.
This includes additional, board-specific configuration variable definitions in <code>boards/myboard/Kconfig</code>.
</p>
<h2>2.6 <a name="DirStructCrypto">nuttx/crypto</a></h2>
@ -1555,13 +1555,13 @@ tools/
This could be done manually as follows:
</p>
<ul>
<li>Copy <code>configs/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]Make.defs</code> to <code>${TOPDIR}/Make.defs</code>,<li>
<li>Copy <code>configs/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]defconfig</code> to <code>${TOPDIR}/.config</code></li>
<li>Copy <code>boards/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]Make.defs</code> to <code>${TOPDIR}/Make.defs</code>,<li>
<li>Copy <code>boards/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]defconfig</code> to <code>${TOPDIR}/.config</code></li>
</ul>
<p>
Where <i>&lt;board-name&gt;</i> is the name of one of the sub-directories of the
NuttX <a href="#DirStructConfigs"><code>configs/</code></a> directory.
NuttX <a href="#DirStructConfigs"><code>boards/</code></a> directory.
This sub-directory name corresponds to one of the supported boards
identified <a href="#supportedboards">above</a>.
&lt;config-dir&gt; is the optional, specific configuration directory for the board.
@ -1705,8 +1705,8 @@ The specific environmental definitions are unique for each board but should incl
<li>Auto-generating the file <code>${TOPDIR}/.version</code> with version 0.0 if one does not exist.</li>
<li>Auto-generating the file <code>include/nuttx/version.h</code> using the <code>${TOPDIR}/.version</code> file.</li>
<li>Creating a link to <code>${TOPDIR}/arch/</code><i>&lt;arch-name&gt;</i><code>/include</code> at <code>${TOPDIR}/include/arch</code>.</li>
<li>Creating a link to <code>${TOPDIR}/configs/</code><i>&lt;board-name&gt;</i><code>/include</code> at <code>${TOPDIR}/include/arch/board</code>.</li>
<li>Creating a link to <code>${TOPDIR}/configs/</code><i>&lt;board-name&gt;</i><code>/src</code> at <code>${TOPDIR}/arch/</code><i>&lt;arch-name&gt;</i><code>/src/board</code></li>
<li>Creating a link to <code>${TOPDIR}/boards/</code><i>&lt;board-name&gt;</i><code>/include</code> at <code>${TOPDIR}/include/arch/board</code>.</li>
<li>Creating a link to <code>${TOPDIR}/boards/</code><i>&lt;board-name&gt;</i><code>/src</code> at <code>${TOPDIR}/arch/</code><i>&lt;arch-name&gt;</i><code>/src/board</code></li>
<li>Creating a link to <code>${APPDIR}/include</code> at <code>${TOPDIR}/include/apps</code></li>
<li>Creating make dependencies.
</ul>
@ -1762,7 +1762,7 @@ The specific environmental definitions are unique for each board but should incl
<b>Board-Specific Interfaces</b>.
Any interface which is unique to a board should be prefixed with the board name, for example <code>stm32f4discovery_</code>.
Sometimes the board name is too long so <code>stm32_</code> would be okay too.
These should be prototyped in <code>configs/&lt;board&gt;/src/&lt;board&gt;.h</code> and should not be used outside of that directory since board-specific definitions have no meaning outside of the board directory.
These should be prototyped in <code>boards/&lt;board&gt;/src/&lt;board&gt;.h</code> and should not be used outside of that directory since board-specific definitions have no meaning outside of the board directory.
</li>
<li>
<p>
@ -1787,7 +1787,7 @@ The specific environmental definitions are unique for each board but should incl
Keeping in the spirit of the layered architecture, these publicly visible header files must <i>not</i> export platform-specific definitions; Only platform-specific realizations of standardized declarations should be visible.
Those <i>standardized declarations</i> should appear in common header files such as those provided by <code>include/nuttx/arch.h</code> and <code>include/nuttx/board.h</code>.
Similarly, these publicly visible header file must <i>not</i> include files that reside in the inaccessible platform-specific source directories.
For example, the board-specific <code>configs/&lt;board&gt;/include/board.h</code> header file must never include microcontroller-specific header files that reside in <code>arch/&lt;arch&gt;/src/&lt;mcu&gt;</code>.
For example, the board-specific <code>boards/&lt;board&gt;/include/board.h</code> header file must never include microcontroller-specific header files that reside in <code>arch/&lt;arch&gt;/src/&lt;mcu&gt;</code>.
That practice will cause inclusion failures when the publicly visible file is included in common logic outside of the platform-specific source directories.
</p>
</li>
@ -5204,7 +5204,7 @@ void iob_dump(FAR const char *msg, FAR struct iob_s *iob, unsigned int len,
The controller-specific, &quot;upper half&quot; touchscreen drivers reside in the directory <code>drivers/input</code>.
</li>
<li><b>&quot;Lower Half&quot; Drivers</b>.
Platform-specific touchscreen drivers reside in either: (1) The <code>arch/</code><i>&lt;architecture&gt;</i><code>/src/</code><i>&lt;hardware&gt;</i> directory for the processor architectures that have build in touchscreen controllers or (2) the <code>configs/</code><i>&lt;board&gt;</i><code>/src/</code> directory for boards that use an external touchscreen controller chip.
Platform-specific touchscreen drivers reside in either: (1) The <code>arch/</code><i>&lt;architecture&gt;</i><code>/src/</code><i>&lt;hardware&gt;</i> directory for the processor architectures that have build in touchscreen controllers or (2) the <code>boards/</code><i>&lt;board&gt;</i><code>/src/</code> directory for boards that use an external touchscreen controller chip.
</li>
</ul>
@ -6074,7 +6074,7 @@ int kbd_decode(FAR struct lib_instream_s *stream, FAR struct kbd_getstate_s *sta
<li>
<p>
<b>Examples</b>:
<code>drivers/lcd/p14201.c</code>, <code>configs/sam3u-ek/src/up_lcd.c.</code>
<code>drivers/lcd/p14201.c</code>, <code>boards/sam3u-ek/src/up_lcd.c.</code>
See also the usage of the LCD driver in the <code>graphics/</code> directory.
</p>
</li>
@ -6366,7 +6366,7 @@ int kbd_decode(FAR struct lib_instream_s *stream, FAR struct kbd_getstate_s *sta
</p>
<p>
<b>Examples</b>:
The function <code>nsh_waiter()</code> in the file <code>configs/olimex-lpc1766stk/src/lpc17_40_appinit.c</code>.
The function <code>nsh_waiter()</code> in the file <code>boards/olimex-lpc1766stk/src/lpc17_40_appinit.c</code>.
</p>
</li>
<li>

342
Documentation/README.html
View File

@ -58,327 +58,327 @@ nuttx/
| `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/binfmt/libpcode/README.txt" target="_blank"><b><i>README.txt</i></b></a>
|- audio/
| `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/audio/README.txt" target="_blank"><b><i>README.txt</i></b></a>
|- configs/
|- boards/
| |- amber/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/amber/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/amber/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- arduino-mega2560/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/arduino-mega2560/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/arduino-mega2560/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- arduino-due/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/arduino-due/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/arduino-due/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- avr32dev1/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/avr32dev1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/avr32dev1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- axoloti/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/axoloti/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/axoloti/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- b-l475e-iot01a/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/b-l475e-iot01a/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/b-l475e-iot01a/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- bambino-200e/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/bambino-200e/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/bambino-200e/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- c5471evm/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/c5471evm/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/c5471evm/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- clicker2-stm32/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/clicker2-stm32/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/clicker2-stm32/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- cloudctrl/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/cloudctrl/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/cloudctrl/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- demo9s12ne64/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/demo9s12ne64/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/demo9s12ne64/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- dk-tm4c129x/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/dk-tm4c129x/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/dk-tm4c129x/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ea3131/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ea3131/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ea3131/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ea3152/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ea3152/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ea3152/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- eagle100/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/eagle100/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/eagle100/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- efm32-g8xx-stk/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/efm32-g8xx-stk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/efm32-g8xx-stk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- efm32gg-stk3700/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/efm32gg-stk3700/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/efm32gg-stk3700/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ekk-lm3s9b96/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ekk-lm3s9b96/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ekk-lm3s9b96/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ez80f910200kitg/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200kitg/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200kitg/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200kitg/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200kitg/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ez80f910200zco/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/ostest/README.txt" target="_blank">dhcpd/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/httpd/README.txt" target="_blank">httpd/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/nettest/README.txt" target="_blank">nettest/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/nsh/README.txt" target="_blank">nsh/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/poll/README.txt" target="_blank">poll/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ez80f910200zco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200zco/ostest/README.txt" target="_blank">dhcpd/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200zco/httpd/README.txt" target="_blank">httpd/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200zco/nettest/README.txt" target="_blank">nettest/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200zco/nsh/README.txt" target="_blank">nsh/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200zco/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200zco/poll/README.txt" target="_blank">poll/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ez80f910200zco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- fire-stm32v2/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/fire-stm32v2/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/fire-stm32v2/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- flipnclick-pic32mz/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/flipnclick-pic32mz/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/flipnclick-pic32mz/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- flipnclick-sam3x/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/flipnclick-sam3x/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/flipnclick-sam3x/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- freedom-k28f/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-k28f/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/freedom-k28f/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- freedom-k64f/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-k64f/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/freedom-k64f/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- freedom-k66f/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-k66f/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/freedom-k66f/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- freedom-kl25z/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-kl25z/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/freedom-kl25z/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- freedom-kl26z/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/freedom-kl26z/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/freedom-kl26z/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- gapuino/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/gapuino/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/gapuino/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- hymini-stm32v/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/hymini-stm32v/RIDE/README.txt" target="_blank">RIDE/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/hymini-stm32v/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/hymini-stm32v/RIDE/README.txt" target="_blank">RIDE/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/hymini-stm32v/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- imxrt1050-evk/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/imxrt1050-evk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/imxrt1050-evk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- kwikstik-k40/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/kwikstik-k40/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/kwikstik-k40/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- launchxl-cc1310/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/launchxl-cc1310/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/launchxl-cc1310/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- launchxl-cc1312r1/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/launchxl-cc1312r1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/launchxl-cc1312r1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- launchxl-tms57004/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/launchxl-tms57004/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/launchxl-tms57004/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lincoln60/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lincoln60/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/lincoln60/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lm3s6432-s2e/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lm3s6432-s2e/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/lm3s6432-s2e/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lm3s6965-ek/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lm3s6965-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/lm3s6965-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lm3s8962-ek/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lm3s8962-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/lm3s8962-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lpc4330-xplorer/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/llpc4330-xplorer/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/llpc4330-xplorer/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lpc4337-ws/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/llpc4337-ws/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/llpc4337-ws/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lpc4357-evb/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/llpc4357-evb/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/llpc4357-evb/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lpc4370-link2/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/llpc4370-link2/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/llpc4370-link2/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lpcxpresso-lpc1768/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpcxpresso-lpc1768/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/lpcxpresso-lpc1768/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- lpcxpresso-lpc54628/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/lpcxpresso-lpc54628/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/lpcxpresso-lpc54628/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- makerlisp/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/makerlisp/nsh/README.txt" target="_blank">nsh/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/makerlisp/README.txt" target="_blank"><b><i>README.txt</i></b></a>\
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/makerlisp/nsh/README.txt" target="_blank">nsh/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/makerlisp/README.txt" target="_blank"><b><i>README.txt</i></b></a>\
| |- maple/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/maple/README.txt" target="_blank"><b><i>README.txt</i></b></a>\
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/maple/README.txt" target="_blank"><b><i>README.txt</i></b></a>\
| |- max32660-evsys/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/max32660-evsys/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/max32660-evsys/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- mbed/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mbed/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/mbed/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- mcb1700/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mcb1700/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/mcb1700/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- mcu123-lpc214x/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mcu123-lpc214x/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/mcu123-lpc214x/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- metro-m4/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/metro-m4/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/metro-m4/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- micropendous3/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/micropendous3/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/micropendous3/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- mikroe-stm32f4/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mikroe-stm32f4/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/mikroe-stm32f4/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- mirtoo/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/mirtoo/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/mirtoo/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- misoc/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/misoc/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/misoc/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- moteino-mega/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/moteino-mega/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/moteino-mega/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ne64badge/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ne64badge/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ne64badge/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nrf52-generic/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nrf52-generic/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nrf52-generic/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ntosd-dm320/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ntosd-dm320/doc/README.txt" target="_blank">doc/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ntosd-dm320/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ntosd-dm320/doc/README.txt" target="_blank">doc/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ntosd-dm320/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nucleo-144/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-144/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-144/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- README.txt
| |- nucleo-f072rb/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f072rb/README.txt" target="_blank"><i>README.txt</i></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-f072rb/README.txt" target="_blank"><i>README.txt</i></a>
| |- nucleo-f091rc/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f091rc/README.txt" target="_blank"><i>README.txt</i></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-f091rc/README.txt" target="_blank"><i>README.txt</i></a>
| |- nucleo-f303re/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f303re/README.txt" target="_blank"><i>README.txt</i></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-f303re/README.txt" target="_blank"><i>README.txt</i></a>
| |- nucleo-f334r8/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f334r8/README.txt" target="_blank"><i>README.txt</i></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-f334r8/README.txt" target="_blank"><i>README.txt</i></a>
| |- nucleo-f4x1re/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f4x1re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-f4x1re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nucleo-f410rb/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f4x1re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-f4x1re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nucleo-f446re/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-f446re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-f446re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nucleo-l432kc/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-l432kc/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-l432kc/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nucleo-l452re/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-l452re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-l452re/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nucleo-l476rg/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-l476rg/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-l476rg/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nucleo-l496zg/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nucleo-l496zg/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nucleo-l496zg/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- nutiny-nuc120/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/nutiny-nuc120/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/nutiny-nuc120/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-efm32g880f129-stk/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-efm32g880f129-stk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-efm32g880f129-stk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-lpc1766stk/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-lpc1766stk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-lpc1766stk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-lpc2378/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-lpc2378/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-lpc2378/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-lpc-h3131/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-lpc-h3131/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-lpc-h3131/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-stm32-h405/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-h405/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-stm32-h405/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-stm32-h407/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-h407/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-stm32-h407/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-stm32-p107/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-p107/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-stm32-p107/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-stm32-p207/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-p207/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-stm32-p207/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-stm32-p407/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-stm32-p407/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-stm32-p407/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- olimex-strp711/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/olimex-strp711/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/olimex-strp711/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- omnibusf4/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/omnibusf4/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/omnibusf4/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- open1788/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/open1788/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/open1788/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- p112/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/p112/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/p112/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- pcduino-a10/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pcduino-pic32mx/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/pcduino-pic32mx/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- photon/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/photon/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/photon/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- pic32mx-starterkit/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pic32mx-starterkit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/pic32mx-starterkit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- pic32mx7mmb/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pic32mx7mmb/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/pic32mx7mmb/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- pic32mz-starterkit/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pic32mz-starterkit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/pic32mz-starterkit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- pnev5180b/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/pnev5180b/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/pnev5180b/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- qemu-i486/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/qemu-i486/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/qemu-i486/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sabre-6quad/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sabre-6quad/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sabre-6quad/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sama5d2-xult/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sama5d2-xult/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sama5d2-xult/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sama5d3x-ek/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sama5d3x-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sama5d3x-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sama5d3-xplained/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sama5d3-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sama5d3-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sama5d4-ek/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sama5d4-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sama5d4-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- samd20-xplained/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/samd20-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/samd20-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- samd21-xplained/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/samd21-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/samd21-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- saml21-xplained/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/saml21-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/saml21-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sam3u-ek/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam3u-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sam3u-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sam4cmp-db
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4cmp-d/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sam4cmp-d/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sam4e-ek/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4e-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sam4e-ek/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sam4l-xplained/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4l-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sam4l-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sam4s-xplained/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4s-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sam4s-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sam4s-xplained-pro/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sam4s-xplained-pro/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sam4s-xplained-pro/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- same70-xplained/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/same70-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/same70-xplained/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- samv71-xult/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/samv71-xult/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/samv71-xult/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- shenzhou/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/shenzhou/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/shenzhou/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sim/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sim/include/README.txt" target="_blank"><b><i>include/README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sim/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sim/include/README.txt" target="_blank"><b><i>include/README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sim/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- skp16c26/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/skp16c26/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/skp16c26/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- spresense/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/spresense/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/spresense/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm3210e-eval/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm3210e-eval/RIDE/README.txt" target="_blank">RIDE/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm3210e-eval/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm3210e-eval/RIDE/README.txt" target="_blank">RIDE/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm3210e-eval/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm3220g-eval/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm3220g-eval/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm3220g-eval/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm3240g-eval/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm3240g-eval/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm3240g-eval/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32_tiny/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32_tiny/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32_tiny/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f103-minumum/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f103-minumum/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f103-minumum/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f3discovery/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f3discovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f3discovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f4discovery/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f4discovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f4discovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f411e-disco/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f411e-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f411e-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f429i-disco/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f429i-disco/fb/README.txt" target="_blank"><i>fb/README.txt</i><</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f429i-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f429i-disco/fb/README.txt" target="_blank"><i>fb/README.txt</i><</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f429i-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f746g-disco/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f746g-disco-disco/fb/README.txt" target="_blank"><i>fb/README.txt</i><</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f746g-disco-disco/nxdemo/README.txt" target="_blank"><i>nxdemo/README.txt</i><</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f746g-disco-disco/nxterm/README.txt" target="_blank"><i>nxterm/README.txt</i><</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f746g-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f746g-disco-disco/fb/README.txt" target="_blank"><i>fb/README.txt</i><</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f746g-disco-disco/nxdemo/README.txt" target="_blank"><i>nxdemo/README.txt</i><</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f746g-disco-disco/nxterm/README.txt" target="_blank"><i>nxterm/README.txt</i><</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f746g-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f769i-disco/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f769i-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32f769i-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32l476-mdk/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32l476vg-mdk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32l476vg-mdk/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32l476vg-disco/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32l476vg-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32l476vg-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32l4r9ai-disco/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32l4r9ai-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32l4r9ai-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32ldiscovery/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32ldiscovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32ldiscovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32vldiscovery/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32vldiscovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/stm32vldiscovery/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- sure-pic32mx/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/sure-pic32mx/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/sure-pic32mx/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- teensy-2.0/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/teensy-2.0/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/teensy-2.0/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- teensy-3.1/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/teensy-3.1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/teensy-3.1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- teensy-lc/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/teensy-lc/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/teensy-lc/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- tm4c123g-launchpad/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/tm4c123g-launchpad/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/tm4c123g-launchpad/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- tm4c1294-launchpad/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/tm4c1294-launchpad/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/tm4c1294-launchpad/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- tms570ls31x-usb-kit/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/tms570ls31x-usb-kit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/tms570ls31x-usb-kit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- twr-k60n512/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/twr-k60n512/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/twr-k60n512/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- twr-k64f120m/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/twr-k64f120m/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/twr-k64f120m/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- "u-blox-c027/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/u-blox-c027/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/u-blox-c027/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- ubw32/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/ubw32/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/ubw32/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- us7032evb1/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/us7032evb1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/us7032evb1/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- viewtool-stm32f107/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/viewtool-stm32f107/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/viewtool-stm32f107/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- xmc4500-relax/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/xmc4500-relax/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/xmc4500-relax/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- z16f2800100zcog/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z16f2800100zcog/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z16f2800100zcog/pashello/README.txt" target="_blank">pashello/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z16f2800100zcog/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z16f2800100zcog/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z16f2800100zcog/pashello/README.txt" target="_blank">pashello/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z16f2800100zcog/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- z80sim/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z80sim/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z80sim/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- z8encore000zco/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z8encore000zco/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z8encore000zco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z8encore000zco/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z8encore000zco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- z8f64200100kit/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z8f64200100kit/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/z8f64200100kit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z8f64200100kit/ostest/README.txt" target="_blank">ostest/README.txt</a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/z8f64200100kit/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- zkit-arm-1769/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/zkit-arm-1769/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/zkit-arm-1769/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- zp214xpa/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/zp214xpa/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/zp214xpa/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/boards/README.txt" target="_blank"><b><i>README.txt</i></b></a>
|- drivers/
| |- eeprom/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/drivers/eeprom/README.txt" target="_blank"><b><i>README.txt</i></b></a>

22
README.txt
View File

@ -679,7 +679,7 @@ Instantiating "Canned" Configurations
"Canned" NuttX configuration files are retained in:
configs/<board-name>/<config-dir>
boards/<board-name>/<config-dir>
Where <board-name> is the name of your development board and <config-dir>
is the name of the sub-directory containing a specific configuration for
@ -706,8 +706,8 @@ Instantiating "Canned" Configurations
General information about configuring NuttX can be found in:
{TOPDIR}/configs/README.txt
{TOPDIR}/configs/<board-name>/README.txt
{TOPDIR}/boards/README.txt
{TOPDIR}/boards/<board-name>/README.txt
The Hidden Configuration Scripts:
@ -720,9 +720,9 @@ Instantiating "Canned" Configurations
Configuring NuttX requires only copying two files from the
<config-dir> to the directory where you installed NuttX (TOPDIR):
Copy configs/<board-name>/<config-dir>/Make.def to{TOPDIR}/Make.defs
Copy boards/<board-name>/<config-dir>/Make.def to{TOPDIR}/Make.defs
OR
Copy configs/<board-name>/scripts/Make.def to{TOPDIR}/Make.defs
Copy boards/<board-name>/scripts/Make.def to{TOPDIR}/Make.defs
Make.defs describes the rules needed by your tool chain to compile
and link code. You may need to modify this file to match the
@ -731,7 +731,7 @@ Instantiating "Canned" Configurations
it may use a common Make.defs file for the board in the scripts/
directory. The first takes precedence.
Copy configs/<board-name>/<config-dir>/defconfig to{TOPDIR}/.config
Copy boards/<board-name>/<config-dir>/defconfig to{TOPDIR}/.config
The defconfig file holds the actual build configuration. This
file is included by all other make files to determine what is
@ -1221,7 +1221,7 @@ Cross-Development Toolchains
In order to build NuttX for your board, you will have to obtain a cross-
compiler to generate code for your target CPU. For each board,
configuration, there is a README.txt file (at configs/<board-name>/README.txt).
configuration, there is a README.txt file (at boards/<board-name>/README.txt).
That README file contains suggestions and information about appropriate
tools and development environments for use with your board.
@ -1234,11 +1234,11 @@ NuttX Buildroot Toolchain
For many configurations, a DIY set of tools is available for NuttX. These
tools can be downloaded from the NuttX Bitbucket.org file repository. After
unpacking the buildroot tarball, you can find instructions for building
the tools in the buildroot/configs/README.txt file.
the tools in the buildroot/boards/README.txt file.
Check the README.txt file in the configuration directory for your board
to see if you can use the buildroot toolchain with your board (this
README.txt file is located in configs/<board-name>/README.txt).
README.txt file is located in boards/<board-name>/README.txt).
This toolchain is available for both the Linux and Cygwin development
environments.
@ -1312,7 +1312,7 @@ Building
make
At least one configuration (eagle100) requires additional command line
arguments on the make command. Read{TOPDIR}/configs/<board-name>/README.txt
arguments on the make command. Read{TOPDIR}/boards/<board-name>/README.txt
to see if that applies to your target.
Re-building
@ -1754,7 +1754,7 @@ nuttx/
|- binfmt/
| `-libpcode/
| `-README.txt
|- configs/
|- boards/
| |- amber/
| | `- README.txt
| |- arduino-mega2560/

12
TODO
View File

@ -4,7 +4,7 @@ NuttX TODO List (Last updated July 1, 2019)
This file summarizes known NuttX bugs, limitations, inconsistencies with
standards, things that could be improved, and ideas for enhancements. This
TODO list does not include issues associated with individual board ports. See
also the individual README.txt files in the configs/ sub-directories for
also the individual README.txt files in the boards/ sub-directories for
issues related to each board port.
nuttx/:
@ -81,7 +81,7 @@ o Task/Scheduler (sched/)
As of this writing, the basic feature implementation is
complete and much of the logic has been verified. The test
harness for the feature exists only for the NXP LPC3131 (see
configs/ea3131/pgnsh and locked directories). There are
boards/ea3131/pgnsh and locked directories). There are
some limitations of this testing so I still cannot say that
the feature is fully functional.
Status: Open. This has been put on the shelf for some time.
@ -283,7 +283,7 @@ o Task/Scheduler (sched/)
and sched_setaffinity(),
2018-09-15: This change has been completed for the case of
open() used within the OS. There are places under libs/ and
configs/ that have not been converted. I also note cases
boards/ that have not been converted. I also note cases
where fopen() is called under libs/libc/netdb/.
Status: Open
@ -987,7 +987,7 @@ o Kernel/Protected Build
by simply reading this variable.
"This one would be easy: Just a change to include/nuttx/userspace.h,
configs/*/kernel/up_userspace.c, libs/libc/,
boards/*/kernel/up_userspace.c, libs/libc/,
sched/sched_addreadytorun.c, and sched/sched_removereadytorun.c.
That would eliminate 59% of the syscalls."
@ -1788,7 +1788,7 @@ o USB (drivers/usbdev, drivers/usbhost)
Title: USB CDC/ACM HOST CLASS DRIVER
Description: A CDC/ACM host class driver has been added. This has been
testing by running the USB CDC/ACM host on an Olimex
LPC1766STK and using the configs/stm3210e-eval/usbserial
LPC1766STK and using the boards/stm3210e-eval/usbserial
configuration (using the CDC/ACM device side driver). There
are several unresolved issues that prevent the host driver
from being usable:
@ -2230,7 +2230,7 @@ o File system / Generic drivers (fs/, drivers/)
file being read is smaller than number bytes written to the
file. That test does write small files continuously until
file system is full and even the the error is rare. The
configs/sim/spiffs test can used to demonstrate the error.
boards/sim/spiffs test can used to demonstrate the error.
Status: Open
Priority: Medium. It is certain a file system failure, but I think that
the exposure in real world uses cases is very small.

2
arch/README.txt
View File

@ -32,7 +32,7 @@ o Board specific files. In order to be usable, the chip must be
peripheral LEDs, external peripherals (such as network, USB, etc.).
These board-specific configuration files can be found in the
configs/<board-name>/ sub-directories.
boards/<board-name>/ sub-directories.
This README will address the processor architecture specific files
that are contained in the arch/<arch-name>/ directory. The file

2
arch/arm/src/am335x/am335x_lcdc.c
View File

@ -514,7 +514,7 @@ static int am335x_lcdc_enableclk(void)
* 1b. The framebuffer character driver is initialized and calls
* up_fbinitialize().
* 2. The function up_fbinitialize() must reside in board specific logic
* under configs/. It must create the instance of struct
* under boards/. It must create the instance of struct
* am335x_panel_info_s and call this function with that instance.
*
* For a directly connected LCD, either (1) the struct am335x_panel_info_s

2
arch/arm/src/am335x/am335x_lcdc.h
View File

@ -196,7 +196,7 @@ struct am335x_panel_info_s
* 1b. The framebuffer character driver is initialized and calls
* up_fbinitialize().
* 2. The function up_fbinitialize() must reside in board specific logic
* under configs/. It must create the instance of struct
* under boards/. It must create the instance of struct
* am335x_panel_info_s and call this function with that instance.
*
* For a directly connected LCD, either (1) the struct am335x_panel_info_s

2
arch/arm/src/dm320/dm320_memorymap.h
View File

@ -60,7 +60,7 @@
* NOTE:
* 1. Most DM320 memory sections can be programmed to lie at different locations in
* the memory map. Therefore, much of the DM320 physical memory map is really
* board-specific and, as such, really belongs in the configs/<board>/include/board.h
* board-specific and, as such, really belongs in the boards/<board>/include/board.h
* file rather than here.
*
* To handle all cases, this file defines a "default" physical memory map, but

2
arch/arm/src/stm32/stm32_eth.c
View File

@ -84,7 +84,7 @@
* Pre-processor Definitions
****************************************************************************/
/* Configuration ************************************************************/
/* See configs/stm3240g-eval/README.txt for an explanation of the configuration
/* See boards/stm3240g-eval/README.txt for an explanation of the configuration
* settings.
*/

2
arch/arm/src/stm32f7/stm32_ethernet.c
View File

@ -90,7 +90,7 @@
#define MEMORY_SYNC() do { ARM_DSB(); ARM_ISB(); } while (0)
/* Configuration ************************************************************/
/* See configs/stm3240g-eval/README.txt for an explanation of the configuration
/* See boards/stm3240g-eval/README.txt for an explanation of the configuration
* settings.
*/

2
arch/arm/src/stm32h7/stm32_ethernet.c
View File

@ -92,7 +92,7 @@
/* Configuration ************************************************************/
/* See configs/stm3240g-eval/README.txt for an explanation of the
/* See boards/stm3240g-eval/README.txt for an explanation of the
* configuration settings.
*/

2
arch/avr/src/at32uc3/at32uc3.h
View File

@ -223,7 +223,7 @@ void up_consoleinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the
* directory configs/<board-name>/src.
* directory boards/<board-name>/src.
*
****************************************************************************/

2
arch/avr/src/at90usb/at90usb.h
View File

@ -128,7 +128,7 @@ void up_consoleinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the
* directory configs/<board-name>/src/.
* directory boards/<board-name>/src/.
*
****************************************************************************/

2
arch/avr/src/atmega/atmega.h
View File

@ -130,7 +130,7 @@ void up_consoleinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the
* directory configs/<board-name>/src.
* directory boards/<board-name>/src.
*
****************************************************************************/

2
arch/mips/src/pic32mx/pic32mx.h
View File

@ -234,7 +234,7 @@ void pic32mx_uartconfigure(uintptr_t uart_base, uint32_t baudrate,
*
* Description:
* This function must be provided by the board-specific logic in the directory
* configs/<board-name>/pic32_boot.c.
* boards/<board-name>/pic32_boot.c.
*
************************************************************************************/

2
arch/mips/src/pic32mz/pic32mz-lowinit.h
View File

@ -87,7 +87,7 @@ void pic32mz_lowinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the directory
* <nuttx>/configs/<board-name>/pic32mz_boot.c.
* <nuttx>/boards/<board-name>/pic32mz_boot.c.
*
************************************************************************************/

2
arch/renesas/include/README.txt
View File

@ -1,5 +1,5 @@
This directory contains header files common to all SH architectures.
Sub-directories within this directory contain header files unique to
specific SH chip architectures. At configuration time, additional directories
will be linked here: 'build' will be a link to the configs/*/include
will be linked here: 'build' will be a link to the boards/*/include
directory; 'chip' will be a link to the SH chip sub-directory.

2
arch/renesas/src/README.txt
View File

@ -3,5 +3,5 @@ architectures. The 'common' subdirectory contains source files shared by
all Renesas architectures; Source files unique to a specific Renesas chip
architecture are contained in a subdirectory named after the chip. At
configuration time, additional directories will be linked here: 'board'
will be a link to the configs/*/src directory; 'chip' will be a link to
will be a link to the boards/*/src directory; 'chip' will be a link to
the SH chip sub-directory.

2
arch/x86/src/common/up_internal.h
View File

@ -166,7 +166,7 @@ extern uint32_t _ebss; /* End+1 of .bss */
*
* Description:
* This function must be provided by the board-specific logic in the
* directory configs/<board-name>/src/.
* directory boards/<board-name>/src/.
*
****************************************************************************/

8
arch/z80/src/z180/README.txt
View File

@ -16,19 +16,19 @@ z180_rom.asm
Some architectures may have ROM located at address zero. In this case, a
special version of the "head" logic must be used. This special "head"
file is probably board-specific and, hence, belongs in the board-specific
configs/<board-name>/src directory. This file may, however, be used as
boards/<board-name>/src directory. This file may, however, be used as
a model for such a board-specific file.
z180_rom.S is enabled by specifying CONFIG_LINKER_ROM_AT_0000 in the
configuration file.
A board specific version in the configs/<board-name>/src directory can be
A board specific version in the boards/<board-name>/src directory can be
used by:
1. Define CONFIG_ARCH_HAVEHEAD
2. Add the board-specific head file, say <filename>.asm, to
configs/<board-name>/src
3. Add a file called Make.defs in the configs/<board-name>/src directory
boards/<board-name>/src
3. Add a file called Make.defs in the boards/<board-name>/src directory
containing the line: HEAD_ASRC = <file-name>.asm
Make.defs

8
arch/z80/src/z80/README.txt
View File

@ -16,19 +16,19 @@ z80_rom.asm
Some architectures may have ROM located at address zero. In this case, a
special version of the "head" logic must be used. This special "head"
file is probably board-specific and, hence, belongs in the board-specific
configs/<board-name>/src directory. This file may, however, be used as
boards/<board-name>/src directory. This file may, however, be used as
a model for such a board-specific file.
z80_rom.S is enabled by specifying CONFIG_LINKER_ROM_AT_0000 in the
configuration file.
A board specific version in the configs/<board-name>/src directory can be
A board specific version in the boards/<board-name>/src directory can be
used by:
1. Define CONFIG_ARCH_HAVEHEAD
2. Add the board-specific head file, say <filename>.asm, to
configs/<board-name>/src
3. Add a file called Make.defs in the configs/<board-name>/src directory
boards/<board-name>/src
3. Add a file called Make.defs in the boards/<board-name>/src directory
containing the line: HEAD_ASRC = <file-name>.asm
Make.defs

290
boards/README.txt
View File

@ -47,11 +47,11 @@ o Board specific files. In order to be usable, the chip must be
peripheral LEDs, external peripherals (such as network, USB, etc.).
These board-specific configuration files can be found in the
configs/<board-name>/ sub-directories and are discussed in this
boards/<board-name>/ sub-directories and are discussed in this
README. Additional configuration information may be available in
board-specific configs/<board-name>/README.txt files.
board-specific boards/<board-name>/README.txt files.
The configs/ subdirectory contains configuration data for each board. These
The boards/ subdirectory contains configuration data for each board. These
board-specific configurations plus the architecture-specific configurations in
the arch/ subdirectory completely define a customized port of NuttX.
@ -59,7 +59,7 @@ Directory Structure
^^^^^^^^^^^^^^^^^^^
The configs directory contains board specific configuration logic. Each
board must provide a subdirectory <board-name> under configs/ with the
board must provide a subdirectory <board-name> under boards/ with the
following characteristics:
@ -166,16 +166,16 @@ http://nuttx.org/Documentation/NuttXConfigVariables.html.
Supported Boards
^^^^^^^^^^^^^^^^
configs/amber
boards/amber
This is placeholder for the SoC Robotics Amber Web Server that is based
on the Atmel AVR ATMega128 MCU. There is not much there yet and what is
there is untested due to tool-related issues.
configs/arduino-due
boards/arduino-due
This sub-directory holds board support for the Arduino DUE board featuring
the Atmel ATSAM3X8E MCU running at 84 MHz.
configs/avr32dev1
boards/avr32dev1
This is a port of NuttX to the Atmel AVR32DEV1 board. That board is
based on the Atmel AT32UC3B0256 MCU and uses a specially patched
version of the GNU toolchain: The patches provide support for the
@ -183,17 +183,17 @@ configs/avr32dev1
Atmel website. STATUS: This port is functional but very basic. There
are configurations for NSH and the OS test.
configs/axoloti
boards/axoloti
Support for the Axoloti synthesizer board based on the STMicro
STM32F427IGH6 MCU. See: http://www.axoloti.com/
configs/b-l072z-lrwan1
boards/b-l072z-lrwan1
STMicro STM32L0 Discovery kit with LoRa/SigFox based on STM32L072CZ MCU.
configs/bambino-200e
boards/bambino-200e
Micromint Bambino board. This board is based on the LPC4330FBD144.
configs/c5471evm
boards/c5471evm
This is a port to the Spectrum Digital C5471 evaluation board. The
TMS320C5471 is a dual core processor from TI with an ARM7TDMI general
purpose processor and a c54 DSP. It is also known as TMS320DA180 or just DA180.
@ -209,51 +209,51 @@ configs launchxl_cc1312r1
Port to the TI SimpleLink CC1312R1 LaunchPad Evaluation Kit (LAUNCHXL-CC1312R1)
featuring the SimpleLinkCC1312R1 chip.
configs/clicker2-stm32
boards/clicker2-stm32
Mikroe Clicker2 STM32 board based on the STMicro STM32F407VGT6 MCU.
configs/cloudctrl
boards/cloudctrl
Darcy's CloudController board. This is a small network relay development
board. Based on the Shenzhou IV development board design. It is based on
the STM32F107VC MCU.
configs/demo9s12ne64
boards/demo9s12ne64
NXP/FreeScale DMO9S12NE64 board based on the MC9S12NE64 hcs12 cpu. This
port uses the m9s12x GCC toolchain. STATUS: (Still) under development; it
is code complete but has not yet been verified.
configs/dk-tm4c129x
boards/dk-tm4c129x
This is the port of NuttX to the Tiva® DK-TM4C129x Connected Development Kit. The
Tiva® DK-TM4C129x features the TM4C129XNCZAD MCU.
configs/ea3131
boards/ea3131
Embedded Artists EA3131 Development board. This board is based on the
an NXP LPC3131 MCU. This OS is built with the arm-nuttx-elf toolchain*.
STATUS: This port is complete and mature.
configs/ea3152
boards/ea3152
Embedded Artists EA3152 Development board. This board is based on the
an NXP LPC3152 MCU. This OS is built with the arm-nuttx-elf toolchain*.
STATUS: This port is has not be exercised well, but since it is
a simple derivative of the ea3131, it should be fully functional.
configs/eagle100
boards/eagle100
Micromint Eagle-100 Development board. This board is based on the
an ARM Cortex-M3 MCU, the Luminary LM3S6918. This OS is built with the
arm-nuttx-elf toolchain*. STATUS: This port is complete and mature.
configs/efm32-g8xx-stk
boards/efm32-g8xx-stk
The port of NuttX to the EFM32 Gecko Starter Kit (EFM32-G8XX-STK).
configs/efm32gg-stk3700
boards/efm32gg-stk3700
The port of NuttX to the EFM32 Giant Gecko Starter Kit
(EFM32GG-STK3700).
configs/ekk-lm3s9b96
boards/ekk-lm3s9b96
TI/Stellaris EKK-LM3S9B96 board. This board is based on the
an EKK-LM3S9B96 which is a Cortex-M3.
configs/esp-core
boards/esp-core
The ESP32 is a dual-core system from Expressif with two Harvard
architecture Xtensa LX6 CPUs. All embedded memory, external memory and
nd peripherals are located on the data bus and/or the instruction bus of
@ -261,179 +261,179 @@ configs/esp-core
CPUs is symmetric, meaning they use the same addresses to access the same
memory.
configs/ez80f0910200kitg
boards/ez80f0910200kitg
ez80Acclaim! Microcontroller. This port use the Zilog ez80f0910200kitg
development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
configs/ez80f0910200zco
boards/ez80f0910200zco
ez80Acclaim! Microcontroller. This port use the Zilog ez80f0910200zco
development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
configs/fire-stm32v2
boards/fire-stm32v2
A configuration for the M3 Wildfire STM32 board. This board is based on the
STM32F103VET6 chip. See http://firestm32.taobao.com . Version 2 and 3 of
the boards are supported but only version 2 has been tested.
configs/flipnclick-pic32mz
boards/flipnclick-pic32mz
Board support for the Mikroe Flip&Click PIC32MZ board. This board is an
chipKit Arduino-compatible board (but can also be used with the Mikroe
bootloader). It has with four Mikroe Click bus interfaces in addition to
standard Arduino connectors. This board features the Microchip
PIC32MZ2048EFH100 MCU running at 200 MHz (252Mhz capable).
configs/flipnclick-sam3x
boards/flipnclick-sam3x
Board support for the Mikroe Flip&Click STM32X board. This board is an
Arduino-Due work-alike with four Mikroe Click bus interfaces. Like the
Arduino DUE, this board features the Atmel ATSAM3X8E MCU running at 84
MHz.
configs/freedom-k28f
boards/freedom-k28f
This port uses the NXP/FreeScale FREEDOM-K28F development board. This
board uses the Kinetis K28F MK28FN2M0VMI15 Cortex-M4 MCU.
configs/freedom-k64f
boards/freedom-k64f
This port uses the NXP/FreeScale FREEDOM-K64F development board. This board
uses the Kinetis K64 MK64FN1M0VLL12 Cortex-M4 MCU.
configs/freedom-kl25z
configs/freedom-kl26z
boards/freedom-kl25z
boards/freedom-kl26z
These configurations are for the NXP/FreeScale Freedom KL25Z and very similar
KL26Z board. The Freedom-KL25Z features the K25Z120LE3AN chip; the
Freedom-KL26Z has the K26Z128VLH4 chip. These are separate configurations
because of minor differences in the on-board logic. Both include a
built-in SDA debugger.
configs/hymini-stm32v
boards/hymini-stm32v
A configuration for the HY-Mini STM32v board. This board is based on the
STM32F103VCT chip.
configs/kwikstik-k40.
boards/kwikstik-k40.
Kinetis K40 Cortex-M4 MCU. This port uses the NXP/FreeScale KwikStik-K40
development board.
configs/launchxl-tms57004
boards/launchxl-tms57004
TI Hercules TMS570LS04x/03x LaunchPad Evaluation Kit (LAUNCHXL-TMS57004)
featuring the Hercules TMS570LS0432PZ chip.
configs/lincoln60
boards/lincoln60
NuttX port to the Micromint Lincoln 60 board.
configs/lm3s6432-s2e
boards/lm3s6432-s2e
Stellaris RDK-S2E Reference Design Kit and the MDL-S2E Ethernet to
Serial module.
configs/lm3s6965-ek
boards/lm3s6965-ek
Stellaris LM3S6965 Evaluation Kit. This board is based on the
an ARM Cortex-M3 MCU, the Luminary/TI LM3S6965. This OS is built with the
arm-nuttx-elf toolchain*. STATUS: This port is complete and mature.
configs/lm3s8962-ek
boards/lm3s8962-ek
Stellaris LMS38962 Evaluation Kit.
configs/lm4f120-launchpad
boards/lm4f120-launchpad
This is the port of NuttX to the Stellaris LM4F120 LaunchPad. The
Stellaris® LM4F120 LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM® Cortex™-M4F-based microcontrollers from Texas
Instruments.
configs/lpcxpresso-lpc1768
boards/lpcxpresso-lpc1768
Embedded Artists base board with NXP LPCExpresso LPC1768. This board
is based on the NXP LPC1768. The Code Red toolchain is used by default.
STATUS: Under development.
configs/lpcxpresso-lpc54628
boards/lpcxpresso-lpc54628
NXP LPCExpresso LPC54628. This board is based on the NXP LPC54628.
configs/lpc4330-xplorer
boards/lpc4330-xplorer
NuttX port to the LPC4330-Xplorer board from NGX Technologies featuring
the NXP LPC4330FET100 MCU
configs/lpc4337-ws
boards/lpc4337-ws
NuttX port to the WaveShare LPC4337-ws board featuring the NXP LPC4337JBD144
MCU.
configs/lpc4357-evb
boards/lpc4357-evb
NuttX port to the LPC4357-EVB board from Embest featuring the NXP
LPC4357FET256 MCU. Based on the LPC4300 Xplorer port and provided by
Toby Duckworth.
configs/lpc4370-link2
boards/lpc4370-link2
NuttX port to the NXP LPC4370-Link2 development board featuring the NXP
LPC4370FET100 MCU. Based on the LPC4300 Xplorer port and provided by
Lok Tep.
configs/makerlisp
boards/makerlisp
This port use the MakerLips machine based on an eZ80F091 ez80Acclaim!
Microcontroller, and the Zilog ZDS-II Windows command line tools. The
development environment is Cygwin under Windows. A Windows native
development environment is available but has not been verified.
configs/maple
boards/maple
NuttX support for the LeafLab's Maple and Maple Mini boards. These boards
are based on the STM32F103RBT6 chip for the standard version and on the
STM32F103CBT6 for the mini version (See http://leaflabs.com/docs/hardware/maple.html)
configs/max32660-evsys
boards/max32660-evsys
The configurations in this directory support the Maxim Integrated
MAX32660-EVSYS board.
configs/mbed
boards/mbed
The configurations in this directory support the mbed board (http://mbed.org)
that features the NXP LPC1768 microcontroller. This OS is also built
with the arm-nuttx-elf toolchain*. STATUS: Contributed.
configs/mcb1700
boards/mcb1700
Board support for the Keil MCB1700
configs/metro-m4
boards/metro-m4
Th configurations in this directory are part of the port of NuttX to the
Adafruit Metro M4. The Metro M4 uses a Arduino form factor and and pinout.
It's powered with an ATSAMD51J19
configs/mikroe-stm32f4
boards/mikroe-stm32f4
This is the port of NuttX to the MikroElektronika Mikromedia for STM32F4
development board. Contributed by Ken Petit.
configs/misoc
boards/misoc
This directory holds the port to NuttX running on a Qemu LM32 system.
You can find the Qemu setup at https://bitbucket.org/key2/qemu
configs/mcu123-lpc214x
boards/mcu123-lpc214x
This port is for the NXP LPC2148 as provided on the mcu123.com
lpc214x development board. This OS is also built with the arm-nuttx-elf
toolchain*. The port supports serial, timer0, spi, and usb.
configs/micropendous3
boards/micropendous3
This is a port to the Opendous Micropendous 3 board. This board may
be populated with either an AVR AT90USB646, 647, 1286, or 1287 MCU.
Support is configured for the AT90USB647.
configs/mirtoo
boards/mirtoo
This is the port to the DTX1-4000L "Mirtoo" module. This module uses MicroChip
PIC32MX250F128D. See http://www.dimitech.com/ for further information.
configs/moteino-mega
boards/moteino-mega
This is placeholder for the LowPowerLab MoteinoMEGA that is based
on the Atmel AVR ATMega1284P MCU. There is not much there yet and what is
there is untested due to tool-related issues.
configs/moxa
boards/moxa
Moxa NP51x0 series of 2-port advanced RS-232/422/485 serial device servers.
configs/ne64badge
boards/ne64badge
Future Electronics Group NE64 /PoE Badge board based on the
MC9S12NE64 hcs12 cpu. This port uses the m9s12x GCC toolchain.
STATUS: Under development. The port is code-complete but has
not yet been fully tested.
configs/nrf52-generic
boards/nrf52-generic
NuttX port to the a generic NRF52. Support is in place for the NRF
PCA10040 board from Nordic Semiconductor or for the Adafruit NRF52
feather, both featuring the NRF52832 MCU.
configs/ntosd-dm320
boards/ntosd-dm320
This port uses the Neuros OSD v1.0 Dev Board with a GNU arm-nuttx-elf
toolchain*: see
@ -448,7 +448,7 @@ configs/ntosd-dm320
STATUS: This port is code complete, verified, and included in the
NuttX 0.2.1 release.
configs/nucleo-144
boards/nucleo-144
STMicro Nucleo-144 development board family. Included support for (1) the
Nucleo-F767ZG board featuring the STM32F746ZGT6U MCU. The STM32F746ZGT6U
is a 216MHz Cortex-M7 operation with 1024Kb Flash memory and 320Kb SRAM.
@ -456,92 +456,92 @@ configs/nucleo-144
STM32F767ZIT6 is a 216MHz Cortex-M7 operation with 2048Kb Flash memory
and 512Kb SRAM.
configs/nucleo-f072rb
boards/nucleo-f072rb
STMicro Nucleo F072RB board based on the STMicro STM32F072RBT6 MCU.
configs/nucleo-f4x1re
boards/nucleo-f4x1re
STMicro ST Nucleo F401RE and F411RE boards. See
http://mbed.org/platforms/ST-Nucleo-F401RE and
http://developer.mbed.org/platforms/ST-Nucleo-F411RE for more
information about these boards.
configs/nucleo-f410rb
boards/nucleo-f410rb
NuttX configuration for the STMicro NucleoF410RB board from ST Micro.
This board features the STM32F410RB 100MHz Cortex-M4 with 128 KB Flash
and 32 KB SRAM.
configs/nucleo-f303re
boards/nucleo-f303re
STMicro ST Nucleo F303RE board. Contributed by Paul Alexander Patience.
configs/nucleo-l073rz
boards/nucleo-l073rz
STMicro STM32L0 Discovery kit with LoRa/SigFox based on STM32L072CZ MCU.
configs/nutiny-nuc120
boards/nutiny-nuc120
This is the port of NuttX to the NuvoTon NuTiny-SDK-NUC120 board. This
board has the NUC120LE3AN chip with a built-in NuLink debugger.
configs/olimex-efm32g880f128-stk
boards/olimex-efm32g880f128-stk
This is the port of NuttX to the Olimex EFM32G880F128-STK development
board.
configs/olimex-lpc1766stk
boards/olimex-lpc1766stk
This port uses the Olimex LPC1766-STK board and a GNU GCC toolchain* under
Linux or Cygwin. STATUS: Complete and mature.
configs/olimex-lpc2378
boards/olimex-lpc2378
This port uses the Olimex-lpc2378 board and a GNU arm-nuttx-elf toolchain* under
Linux or Cygwin. STATUS: ostest and NSH configurations available.
This port for the NXP LPC2378 was contributed by Rommel Marcelo.
configs/olimex-stm32-h405
boards/olimex-stm32-h405
This port uses the Olimex STM32 H405 board and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the http://www.olimex.com for
further information. This board features the STMicro STM32F405RGT6 MCU.
Contributed by Martin Lederhilger.
configs/olimex-stm32-h407
boards/olimex-stm32-h407
This port uses the Olimex STM32 H407 board and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the http://www.olimex.com for
further information. This board features the STMicro STM32F407ZGT6 (144
pins). Contributed by Neil Hancock.
configs/olimex-stm32-e407
boards/olimex-stm32-e407
Olimex STM32 E407 board based on the STMicro STM32F407ZGT6 (144pins).
Contributed by Mateusz Szafoni.
configs/olimex-stm32-p107
boards/olimex-stm32-p107
This port uses the Olimex STM32-P107 board (STM32F107VC) and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the https://www.olimex.com/dev/stm32-p107.html
for further information. Contributed by Max Holtzberg.
configs/olimex-stm32-p207
boards/olimex-stm32-p207
This port uses the Olimex STM32-P207 board (STM32F207ZE) and a GNU arm-nuttx-elf
toolchain under Linux or Cygwin. See the https://www.olimex.com/dev/stm32-p207.html
for further information. Contributed by Martin Lederhilger.
configs/olimex-stm32-p407
boards/olimex-stm32-p407
This port uses the Olimex STM32-P407 board (STM32F407ZG) and a GNU arm-nuttx-elf
toolchain under Linux or Cygwin. See the https://www.olimex.com/dev/stm32-p407.html
for further information.
configs/olimexino-stm32
boards/olimexino-stm32
This port uses the Olimexino STM32 board (STM32F103RBT6) and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the http://www.olimex.com for further\
information. Contributed by David Sidrane.
configs/olimex-strp711
boards/olimex-strp711
This port uses the Olimex STR-P711 board and a GNU arm-nuttx-elf toolchain* under
Linux or Cygwin. See the http://www.olimex.com/dev/str-p711.html" for
further information. STATUS: Configurations for the basic OS test and NSH
are complete and verified.
configs/omnibusf4
boards/omnibusf4
Flight controllers compatible with the OMINBUSF4 Betaflight target
configs/or1k
boards/or1k
Generic OpenRISC board.
configs/pcduino-a10
boards/pcduino-a10
This directory contains the port of NuttX to the pcDuino v1 board
See http://www.pcduino.com/ for information about pcDuino Lite, v1,
and v2. These boards are based around the Allwinner A10 Cortex-A8 CPU.
@ -549,7 +549,7 @@ configs/pcduino-a10
differences are cosmetic. This port was developed on the v1 board, but
the others may be compatible.
configs/p112
boards/p112
The P112 is notable because it was the first of the hobbyist single board
computers to reach the production stage. The P112 hobbyist computers
were relatively widespread and inspired other hobbyist centered home brew
@ -576,22 +576,22 @@ configs/p112
Dave Brooks was successfully funded through Kickstarter for and another
run of P112 boards in November of 2012.
configs/photon
boards/photon
A configuration for the Photon Wifi board from Particle Devices
(https://www.particle.io). This board features the STM32F205RGY6 MCU from
STMicro.
configs/pic32mx-starterkit
boards/pic32mx-starterkit
This directory contains the port of NuttX to the Microchip PIC32 Ethernet
Starter Kit (DM320004) with the Multimedia Expansion Board (MEB, DM320005).
See www.microchip.com for further information.
configs/pic32mx7mmb
boards/pic32mx7mmb
This directory will (eventually) contain the port of NuttX to the
Mikroelektronika PIC32MX7 Multimedia Board (MMB). See
http://www.mikroe.com/ for further information.
configs/pic32mz-starterkit
boards/pic32mz-starterkit
This directory contains the port of NuttX to the Microchip PIC32MZ
Embedded Connectivity (EC) Starter Kit. There are two configurations of
the starter kit:
@ -603,26 +603,26 @@ configs/pic32mz-starterkit
See www.microchip.com for further information.
configs/pnev5180b
boards/pnev5180b
NXP Semiconductors' PN5180 NFC Frontend Development Kit. This board is
based on the NXP LPC1769 MCU.
configs/qemu-i486
boards/qemu-i486
Port of NuttX to QEMU in i486 mode. This port will also run on real i486
hardwared (Google the Bifferboard).
configs/nr5m100-nexys4
boards/nr5m100-nexys4
Port of NuttX to RISC-V platform on IQ-Analog NR5M100 RISC-V FPGA platform.
configs/sabre-6quad
boards/sabre-6quad
This directory holds a port of NuttX to the NXP/Freescale Sabre board
featuring the iMX 6Quad CPU.
configs/sama5d2-xult
boards/sama5d2-xult
This is the port of NuttX to the Atmel SAMA5D2-Xplained Ultra development
board. This board features the Atmel SAMA5D27. See http://www.atmel.com.
configs/sama5d3x-ek
boards/sama5d3x-ek
This is the port of NuttX to the Atmel SAMA5D3x-EK development boards
(where x=1,3,4, or 5). These boards feature the Atmel SAMA5D3
microprocessors. Four different SAMA5D3x-EK kits are available
@ -637,146 +637,146 @@ configs/sama5d3x-ek
are supported by NuttX with a simple reconfiguration of the processor
type.
configs/sama5d3-xplained
boards/sama5d3-xplained
This is the port of NuttX to the Atmel SAMA5D3x-Xplained development board.
This board features the Atmel SAMA5D36. See
http://www.atmel.com/devices/sama5d36.aspx.
configs/sama5d4-ek
boards/sama5d4-ek
This is the port of NuttX to the Atmel SAMA5D4-EK development board.
This board features the Atmel SAMA5D44. See http://www.atmel.com.
configs/samd20-xplained
boards/samd20-xplained
The port of NuttX to the Atmel SAMD20-Xplained Pro development board. This
board features the ATSAMD20J18A MCU (Cortex-M0+ with 256KB of FLASH and
32KB of SRAM).
configs/samd21-xplained
boards/samd21-xplained
The port of NuttX to the Atmel SAMD21-Xplained Pro development board. This
board features the ATSAMD21J18A MCU (Cortex-M0+ with 256KB of FLASH and
32KB of SRAM).
configs/sam3u-ek
boards/sam3u-ek
The port of NuttX to the Atmel SAM3U-EK development board.
configs/sam4cmp-db
boards/sam4cmp-db
The port of NuttX to the Atmel SAM4CMP-DB development board.
configs/sam4e-ek
boards/sam4e-ek
The port of NuttX to the Atmel SAM4E-EK development board. This board
features the SAM4E16 MCU running at up to 120MHz.
configs/sam4l-xplained
boards/sam4l-xplained
The port of NuttX to the Atmel SAM4L-Xplained development board.
configs/sam4s-xplained
boards/sam4s-xplained
The port of NuttX to the Atmel SAM4S-Xplained development board.
configs/sam4s-xplained-pro
boards/sam4s-xplained-pro
The port of NuttX to the Atmel SAM4S-Xplained Pro development board.
configs/same70-xplained
boards/same70-xplained
The port of NuttX to the Atmel SAME70 Xplained evaluation board.
configs/samv71-xult
boards/samv71-xult
The port of NuttX to the Atmel SAMV71 Xplained Ultra evaluation board.
configs/sim
boards/sim
A user-mode port of NuttX to the x86 Linux platform is available.
The purpose of this port is primarily to support OS feature development.
This port does not support interrupts or a real timer (and hence no
round robin scheduler) Otherwise, it is complete.
configs/shenzhou
boards/shenzhou
This is the port of NuttX to the Shenzhou development board from
www.armjishu.com. This board features the STMicro STM32F107VCT MCU.
configs/skp16c26
boards/skp16c26
Renesas M16C processor on the Renesas SKP16C26 StarterKit. This port
uses the GNU m32c toolchain. STATUS: The port is complete but untested
due to issues with compiler internal errors.
configs/stm3210e-eval
boards/stm3210e-eval
STMicro STM3210E-EVAL development board based on the STMicro STM32F103ZET6
microcontroller (ARM Cortex-M3). This port uses the GNU Cortex-M3
toolchain.
configs/stm3220g-eval
boards/stm3220g-eval
STMicro STM3220G-EVAL development board based on the STMicro STM32F407IG
microcontroller (ARM Cortex-M3).
configs/stm3240g-eval
boards/stm3240g-eval
STMicro STM3240G-EVAL development board based on the STMicro STM32F103ZET6
microcontroller (ARM Cortex-M4 with FPU). This port uses a GNU Cortex-M4
toolchain (such as CodeSourcery).
configs/stm32butterfly2
boards/stm32butterfly2
Kamami stm32butterfly2 development board with optional ETH phy. See
https://kamami.pl/zestawy-uruchomieniowe-stm32/178507-stm32butterfly2.html
configs/stm32f051-discovery
boards/stm32f051-discovery
STMicro STM32F051-Discovery board based on the STMicro ARCH_CHIP_STM32F051R8
MCU.
configs/stm32f072-discovery
boards/stm32f072-discovery
STMicro STM32F072-Discovery board based on the STMicro ARCH_CHIP_STM32F072RB
MCU.
configs/stm32f103-minimum
boards/stm32f103-minimum
Generic STM32F103C8T6 Minimum ARM Development Board.
configs/stm32f4discovery
boards/stm32f4discovery
STMicro STM32F4-Discovery board based on the STMIcro STM32F407VGT6 MCU.
configs/stm32f411e-disco
boards/stm32f411e-disco
This is a minimal configuration that supports low-level test of the
STMicro STM32F411E-Discovery Board.
configs/stm32f429i-disco
boards/stm32f429i-disco
STMicro STM32F429I-Discovery board based on the STMicro STM32F429ZIT6 MCU.
configs/stm32f746g-disco
boards/stm32f746g-disco
STMicro STM32F746G-DISCO development board featuring the STM32F746NGH6
MCU. The STM32F746NGH6 is a 216MHz Cortex-M7 operation with 1024Kb Flash
memory and 300Kb SRAM.
configs/stm32f746g-ws
boards/stm32f746g-ws
Waveshare STM32F746 development board featuring the STM32F746IG MCU.
configs/stm32l476-mdk
boards/stm32l476-mdk
Motorola Mods Development Board (MDK) features STM32L476ME MCU.
The STM32L476ME is a Cortex-M4 optimised for low-power operation
at up to 80MHz operation with 1024Kb Flash memory and 96+32Kb SRAM.
configs/stm32f769i-disco
boards/stm32f769i-disco
NuttX configurations for the STMicro STM32F769I-DISCO development board
featuring the STM32F769NIH6 MCU. The STM32F769NIH6 is a 216MHz Cortex-M7
operating with 2048K Flash memory and 512Kb SRAM.
configs/stm32l476vg-disco
boards/stm32l476vg-disco
STMicro STM32L476VG_DISCO development board featuring the STM32L476VG
MCU. The STM32L476VG is a Cortex-M4 optimised for low-power operation
at up to 80MHz operation with 1024Kb Flash memory and 96+32Kb SRAM.
configs/stm32ldiscovery
boards/stm32ldiscovery
STMicro STM32L-Discovery board based on the STMicro STM32L152RB MCU.
configs/stm32vldiscovery
boards/stm32vldiscovery
STMicro STM32VL-Discovery board based on the STMicro STM32F100RB MCU.
configs/sure-pic32mx
boards/sure-pic32mx
The "Advanced USB Storage Demo Board," Model DB-DP11215, from Sure
Electronics (http://www.sureelectronics.net/). This board features
the MicroChip PIC32MX440F512H. See also
http://www.sureelectronics.net/goods.php?id=1168 for further
information about the Sure DB-DP11215 board.
configs/teensy-2.0
boards/teensy-2.0
This is the port of NuttX to the PJRC Teensy++ 2.0 board. This board is
developed by http://pjrc.com/teensy/. The Teensy++ 2.0 is based
on an Atmel AT90USB1286 MCU.
configs/teensy-3.x
boards/teensy-3.x
This is the port of NuttX to the Teensy-3.1 from PJRC
(https://www.pjrc.com/). The Teensy-3.1 features the Freescale
MK30DX256VLH7 chip (now NXP). The MK30DX256VLH7 is a 64-pin Cortex-M4
@ -791,36 +791,36 @@ configs/teensy-3.x
Teensy-3.0). the primary difference is that the Teensy 3.0 has a
MK30DX128VLH5 with slightly less capability.
configs/teensy-lc
boards/teensy-lc
This is the port of nuttx for the Teensy LC board. The Teensy LC
is a DIP style breakout board for the MKL25Z64 and comes with a USB
based bootloader.
configs/tm4c123g-launchpad
boards/tm4c123g-launchpad
This is the port of NuttX to the Tiva® TM4C123G LaunchPad. The
Tiva® TM4C123G LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM® Cortex™-M4F-based microcontrollers from Texas
Instruments.
configs/tm4c1294-launchpad
boards/tm4c1294-launchpad
This is the port of NuttX to the Tiva® TM4C1294 LaunchPad. The
Tiva® TM4C123G LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM® Cortex™-M4F-based microcontrollers from Texas
Instruments.
configs/tms570ls31x-usb-kit
boards/tms570ls31x-usb-kit
TI Hercules TMS570LS31xx Evaluation Kit (TMDS570ls31xx USB Kit)
featuring the Hercules TMS570LS3137ZWT chip.
configs/twr-k60n512
boards/twr-k60n512
Kinetis K60 Cortex-M4 MCU. This port uses the FreeScale TWR-K60N512
development board.
configs/twr-k64f120m
boards/twr-k64f120m
Kinetis K64 Cortex-M4 MCU. This port uses the FreeScale TWR-K64F120M
development board.
configs/ubw32
boards/ubw32
This is the port to the Sparkfun UBW32 board. This port uses the original v2.4
board which is based on the MicroChip PIC32MX460F512L. See
@ -828,11 +828,11 @@ configs/ubw32
with this board http://www.sparkfun.com/products/9713. See also
http://www.schmalzhaus.com/UBW32/.
configs/us7032evb1
boards/us7032evb1
This is a port of the Hitachi SH-1 on the Hitachi SH-1/US7032EVB1 board.
STATUS: Work has just began on this port.
configs/viewtool-stm32f107
boards/viewtool-stm32f107
NuttX configurations for the ViewTool STM32F103/F107 V1.2 board. This
board may be fitted with either: (1) STM32F107VCT6 or (2) STM32F103VCT6.
See http://www.viewtool.com/ for further information.
@ -840,32 +840,32 @@ configs/viewtool-stm32f107
config/xmc4500-relax
Infineon XMC4000 Relax Lite v1
configs/z16f2800100zcog
boards/z16f2800100zcog
z16f Microcontroller. This port use the Zilog z16f2800100zcog
development kit and the Zilog ZDS-II Windows command line tools. The
development environment is Cygwin under WinXP.
configs/z80sim
boards/z80sim
z80 Microcontroller. This port uses a Z80 instruction set simulator
called z80sim. This port also uses the SDCC toolchain
(http://sdcc.sourceforge.net/") (verified with version 2.6.0).
configs/z8encore000zco
boards/z8encore000zco
z8Encore! Microcontroller. This port use the Zilog z8encore000zco
development kit, Z8F6403 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
configs/z8f64200100kit
boards/z8f64200100kit
z8Encore! Microcontroller. This port use the Zilog z8f64200100kit
development kit, Z8F6423 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
configs/zp214xpa
boards/zp214xpa
This port is for the NXP LPC2148 as provided on the The0.net
ZPA213X/4XPA development board. Includes support for the
UG-2864AMBAG01 OLED also from The0.net
configs/zkit-arm-1769
boards/zkit-arm-1769
Zilogic System's ARM development Kit, ZKIT-ARM-1769. This board is based
on the NXP LPC1769. The Nuttx Buildroot toolchain is used by default.
@ -874,8 +874,8 @@ Configuring NuttX
Configuring NuttX requires only copying
configs/<board-name>/<config-dir>/Make.def to ${TOPDIR}/Make.defs
configs/<board-name>/<config-dir>/defconfig to ${TOPDIR}/.config
boards/<board-name>/<config-dir>/Make.def to ${TOPDIR}/Make.defs
boards/<board-name>/<config-dir>/defconfig to ${TOPDIR}/.config
tools/configure.sh
There is a script that automates these steps. The following steps will

6
boards/amber/README.txt
View File

@ -289,7 +289,7 @@ NuttX buildroot Toolchain
4. cd <some-dir>/buildroot
5. cp configs/avr-defconfig-4.5.2 .config
5. cp boards/avr-defconfig-4.5.2 .config
6. make oldconfig
@ -298,7 +298,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
See the file configs/README.txt in the buildroot source tree. That has more
See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you
are building a toolchain for Cygwin under Windows.
@ -388,7 +388,7 @@ Amber Web Server Configuration Options
CONFIG_ARCH_CHIP_ATMEGA128=y
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=amber

2
boards/amber/scripts/amber.ld
View File

@ -1,5 +1,5 @@
/**************************************************************************************
* configs/amber/scripts/amber.ld
* boards/amber/scripts/amber.ld
*
* Copyright (C) 2011, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

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

@ -561,7 +561,7 @@ Arduino DUE-specific Configuration Options
CONFIG_ARCH_CHIP_SAM3X
CONFIG_ARCH_CHIP_ATSAM3X8E
CONFIG_ARCH_BOARD - Identifies the configs/ subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=arduino-due (for the Arduino Due development board)

2
boards/arduino-due/scripts/arduino-due.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/arduino-due/scripts/arduino-due.ld
* boards/arduino-due/scripts/arduino-due.ld
*
* Copyright (C) 2013, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/arduino-mega2560/scripts/flash.ld
View File

@ -1,5 +1,5 @@
/*******************************************************************************
* configs/arduino-mega2560/scripts/flash.ld
* boards/arduino-mega2560/scripts/flash.ld
*
* Copyright (C) 2015 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

6
boards/avr32dev1/README.txt
View File

@ -34,7 +34,7 @@ The only GPIO pin usage is for LEDs (2) and Buttons (2):
PIN 24 PB2 KEY1
PIN 25 PB3 KEY2
(See configs/avr32dev1/src/avr32dev1.h). And also for
(See boards/avr32dev1/src/avr32dev1.h). And also for
crystals (4), JTAG (1), and USB (1):
PIN 30 PA11 XIN32
@ -83,7 +83,7 @@ RS-232 drivers or connectors on board. I use an off-board MAX232
module that I got on eBay (search for MAX232 if you want to find
one). I connect the MAX232 board as follows:
In configs/avr32dev/include/board.h:
In boards/avr32dev/include/board.h:
#define PINMUX_USART1_RXD PINMUX_USART1_RXD_1
#define PINMUX_USART1_TXD PINMUX_USART1_TXD_1
@ -352,7 +352,7 @@ AVR32DEV1 Configuration Options
CONFIG_ARCH_CHIP_AT32UC3B0256
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=avr32dev1 (for the AV32DEV1 board)

2
boards/avr32dev1/scripts/avr32dev1.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/avr32dev1/scripts/avr32dev1.ld
* boards/avr32dev1/scripts/avr32dev1.ld
*
* Copyright (C) 2010, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/axoloti/scripts/gnu-elf.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/axoloti/scripts/gnu-elf.ld
* boards/axoloti/scripts/gnu-elf.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/axoloti/scripts/kernel-space.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/axoloti/scripts/kernel-space.ld
* boards/axoloti/scripts/kernel-space.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/axoloti/scripts/ld.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/axoloti/scripts/ld.script
* boards/axoloti/scripts/ld.script
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

4
boards/axoloti/scripts/memory.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/axoloti/scripts/memory.ld
* boards/axoloti/scripts/memory.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
@ -48,7 +48,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
* also configs/axoloti/scripts/kernel-space.ld). Allowing the
* also boards/axoloti/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*

2
boards/axoloti/scripts/user-space.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/axoloti/scripts/user-space.ld
* boards/axoloti/scripts/user-space.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/b-l072z-lrwan1/scripts/ld.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/b-l072z-lrwan1/scripts/ld.script
* boards/b-l072z-lrwan1/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt <gnutt@nuttx.org>

2
boards/b-l475e-iot01a/scripts/flash.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/b-l475e-iot01a/scripts/flash.ld
* boards/b-l475e-iot01a/scripts/flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
*

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

@ -126,7 +126,7 @@ the following lines in each Make.defs file:
Configuration Changes
---------------------
Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2
Below are all of the configuration changes that I had to make to boards/stm3240g-eval/nsh2
in order to successfully build NuttX using the Atollic toolchain WITH FPU support:
-CONFIG_ARCH_FPU=n : Enable FPU support
@ -173,7 +173,7 @@ Bambino-200e Configuration Options
CONFIG_ARCH_CHIP_LPC4330=y
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=bambino-200e (for the Bambino-200e board)

2
boards/bambino-200e/knsh/defconfig
View File

@ -38,7 +38,7 @@ CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x14040000
CONFIG_PASS1_BUILDIR="configs/bambino-200e/kernel"
CONFIG_PASS1_BUILDIR="boards/bambino-200e/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
CONFIG_PREALLOC_WDOGS=4

4
boards/bambino-200e/scripts/memory.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/stm32f4discovery/scripts/memory.ld
* boards/stm32f4discovery/scripts/memory.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
@ -47,7 +47,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
* also configs/stm32f4discovery/scripts/kernel-space.ld). Allowing the
* also boards/stm32f4discovery/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*

2
boards/bambino-200e/scripts/ramconfig.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/bambino-200e/scripts/ramconfig.ld
* boards/bambino-200e/scripts/ramconfig.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/bambino-200e/scripts/spificonfig.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/bambino-200e/scripts/spificonfig.ld
* boards/bambino-200e/scripts/spificonfig.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/bambino-200e/scripts/user-space.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/stm32f4discovery/scripts/user-space.ld
* boards/stm32f4discovery/scripts/user-space.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/beaglebone-black/scripts/sdram.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/beaglebone-black/scripts/sdram.ld
* boards/beaglebone-black/scripts/sdram.ld
*
* Copyright (C) 2018 Petro Karashchenko. All rights reserved.
* Author: Petro Karashchenko <petro.karashchenko@gmail.com>

4
boards/c5471evm/README.txt
View File

@ -21,7 +21,7 @@ Toolchain
4. cd <some-dir>/buildroot
5. cp configs/arm-defconfig .config
5. cp boards/arm-defconfig .config
6. make oldconfig
@ -63,7 +63,7 @@ ARM/C5471-specific Configuration Options
CONFIG_ARCH_CHIP_C5471
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=c5471evm (for the Spectrum Digital C5471 EVM)

2
boards/c5471evm/scripts/ld.script
View File

@ -1,5 +1,5 @@
/************************************************************
* configs/c5471evm/scripts/ld.script
* boards/c5471evm/scripts/ld.script
*
* Copyright (C) 2007, 2011-2012, 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

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

@ -75,7 +75,7 @@ Using JTAG
The Clicker2 comes with the mikroBootloader installed. That bootloader
has not been used and is possibly incompatible with the Clicker2-STM32
linker script at configs/clicker2-stm32/scripts/flash.ld. Often code must
linker script at boards/clicker2-stm32/scripts/flash.ld. Often code must
be built to execute at an offset in to FLASH when a bootloader is used.
Certainly that is the case for the ST-Micro DFU bootloader but I am not
aware of the requirements for use with the mikroBootloader.

2
boards/clicker2-stm32/knsh/defconfig
View File

@ -39,7 +39,7 @@ CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x08020000
CONFIG_PASS1_BUILDIR="configs/clicker2-stm32/kernel"
CONFIG_PASS1_BUILDIR="boards/clicker2-stm32/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
CONFIG_PREALLOC_WDOGS=8

2
boards/clicker2-stm32/scripts/flash.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/clicker2-stm32/scripts/flash.ld
* boards/clicker2-stm32/scripts/flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/clicker2-stm32/scripts/gnu-elf.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/clicker2-stm32/scripts/gnu-elf.ld
* boards/clicker2-stm32/scripts/gnu-elf.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/clicker2-stm32/scripts/kernel-space.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/clicker2-stm32/scripts/kernel-space.ld
* boards/clicker2-stm32/scripts/kernel-space.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

4
boards/clicker2-stm32/scripts/memory.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/clicker2-stm32/scripts/memory.ld
* boards/clicker2-stm32/scripts/memory.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
@ -47,7 +47,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
* also configs/clicker2-stm32/scripts/kernel-space.ld). Allowing the
* also boards/clicker2-stm32/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*

2
boards/clicker2-stm32/scripts/user-space.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/clicker2-stm32/scripts/user-space.ld
* boards/clicker2-stm32/scripts/user-space.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

4
boards/cloudctrl/README.txt
View File

@ -221,7 +221,7 @@ Cloudctrl-specific Configuration Options
CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=shenzhou (for the Cloudctrl development board)
@ -498,7 +498,7 @@ Where <subdir> is one of the following:
ADC_IN8 (PB0) CON5 CN14 Pin2
ADC_IN9 (PB1) CON5 CN14 Pin1
The signal selection is hard-coded in configs/shenzhou/src/up_adc.c: The
The signal selection is hard-coded in boards/shenzhou/src/up_adc.c: The
potentiometer input (only) is selected.
These selections will enable sampling the potentiometer input at 100Hz using

2
boards/cloudctrl/scripts/cloudctrl-dfu.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/cloudctrl/scripts/cloudctrl-dfu.ld
* boards/cloudctrl/scripts/cloudctrl-dfu.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/cloudctrl/scripts/cloudctrl.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/cloudctrl/scripts/cloudctrl.ld
* boards/cloudctrl/scripts/cloudctrl.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

6
boards/demo9s12ne64/README.txt
View File

@ -131,7 +131,7 @@ NuttX Buildroot Toolchain
4. cd <some-dir>/buildroot
5. cp configs/m9s12x-defconfig-3.3.6 .config
5. cp boards/m9s12x-defconfig-3.3.6 .config
6. make oldconfig
@ -145,7 +145,7 @@ NuttX Buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
See the file configs/README.txt in the buildroot source tree. That has more
See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@ -276,7 +276,7 @@ HCS12/DEMO9S12NEC64-specific Configuration Options
CONFIG_ARCH_CHIP_MCS92S12NEC64
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=demo9s12nec64

2
boards/demo9s12ne64/scripts/demo9s12ne64-banked.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/demo9s12ne64/ostest/demo9s12ne64-banked.ld
* boards/demo9s12ne64/ostest/demo9s12ne64-banked.ld
*
* Copyright (C) 2009, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/demo9s12ne64/scripts/demo9s12ne64-unbanked.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/demo9s12ne64/ostest/demo9s12ne64-banked.ld
* boards/demo9s12ne64/ostest/demo9s12ne64-banked.ld
*
* Copyright (C) 2009, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

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

@ -40,7 +40,7 @@ Using OpenOCD and GDB with ICDI
Building OpenOCD under Cygwin:
Refer to configs/olimex-lpc1766stk/README.txt
Refer to boards/olimex-lpc1766stk/README.txt
Installing OpenOCD in Linux:
@ -56,7 +56,7 @@ Using OpenOCD and GDB with ICDI
I have been using the on-board In-Circuit Debug Interface (ICDI) interface.
OpenOCD requires a configuration file. I keep the one I used last here:
configs/dk-tm4c129x/tools/dk-tm4c129x.cfg
boards/dk-tm4c129x/tools/dk-tm4c129x.cfg
However, the "correct" configuration script to use with OpenOCD may
change as the features of OpenOCD evolve. So you should at least
@ -74,7 +74,7 @@ Using OpenOCD and GDB with ICDI
- Possibly the value of OPENOCD_PATH and TARGET_PATH
- It assumes that the correct script to use is the one at
configs/dk-tm4c129x/tools/dk-tm4c129x.cfg
boards/dk-tm4c129x/tools/dk-tm4c129x.cfg
Starting OpenOCD
@ -84,7 +84,7 @@ Using OpenOCD and GDB with ICDI
oocd.sh $PWD
Assuming that you have included the path to the oocd.sh script,
configs/dk-tm4c129x/tools, in PATH variable.
boards/dk-tm4c129x/tools, in PATH variable.
Note that OpenOCD needs to be run with administrator privileges in
some environments (sudo).
@ -513,7 +513,7 @@ Temperature Sensor
More complex temperature sensor operations are also available. See the IOCTL
commands enumerated in include/nuttx/sensors/lm75.h. Also read the descriptions
of the tiva_tmp100_initialize() and tiva_tmp100_attach() interfaces in the
arch/board/board.h file (sames as configs/dk-tm4c129x/include/board.h).
arch/board/board.h file (sames as boards/dk-tm4c129x/include/board.h).
NSH Command Line Application
----------------------------
@ -562,7 +562,7 @@ DK-TM4129X Configuration Options
CONFIG_ARCH_CHIP_TM4C129XNC
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=dk-tm4c129x (for the DK-TM4129X)

2
boards/dk-tm4c129x/scripts/ld.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/dk-tm4c129x/scripts/ld.script
* boards/dk-tm4c129x/scripts/ld.script
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

24
boards/ea3131/README.txt
View File

@ -160,7 +160,7 @@ NuttX buildroot Toolchain
4. cd <some-dir>/buildroot
5. cp configs/arm926t-defconfig-4.2.4 .config
5. cp boards/arm926t-defconfig-4.2.4 .config
6. make oldconfig
@ -169,7 +169,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
See the file configs/README.txt in the buildroot source tree. That has more
See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@ -195,11 +195,11 @@ Image Format
it!
To work around both of these issues, I have created a small program under
configs/ea3131/tools to add the header. This program can be built under
boards/ea3131/tools to add the header. This program can be built under
either Linux or Cygwin (and probably other tool environments as well). That
tool can be built as follows:
- cd configs/ea3131/tools
- cd boards/ea3131/tools
- make
Then, to build the NuttX binary ready to load with the bootloader, just
@ -216,10 +216,10 @@ Image Format
to mklpc.sh in the final step.
2. You can instruct Symantec to ignore the errors and it will stop quarantining
the NXP program.
3. The CRC32 logic in configs/ea3131/tools doesn't seem to work. As a result,
3. The CRC32 logic in boards/ea3131/tools doesn't seem to work. As a result,
the CRC is currently disabled in the header:
RCS file: /cvsroot/nuttx/nuttx/configs/ea3131/tools/lpchdr.c,v
RCS file: /cvsroot/nuttx/nuttx/boards/ea3131/tools/lpchdr.c,v
retrieving revision 1.2
diff -r1.2 lpchdr.c
264c264
@ -262,7 +262,7 @@ Using OpenOCD and GDB
Then you should be able to start the OpenOCD daemon like:
configs/ea3131/tools/oocd.sh $PWD
boards/ea3131/tools/oocd.sh $PWD
Where it is assumed that you are executing oocd.sh from the top level
directory where NuttX is installed.
@ -383,16 +383,16 @@ On-Demand Paging
This example uses a two-pass build. The top-level Makefile recognizes the
configuration option CONFIG_BUILD_2PASS and will execute the Makefile in
configs/ea3131/locked/Makefile to build the first pass object, locked.r.
boards/ea3131/locked/Makefile to build the first pass object, locked.r.
This first pass object contains all of the code that must be in the locked
text region. The Makefile in arch/arm/src/Makefile then includes this 1st
pass in build, positioning it as controlled by configs/ea3131/scripts/pg-ld.script.
pass in build, positioning it as controlled by boards/ea3131/scripts/pg-ld.script.
Finishing the Example:
----------------------
This example is incomplete in that it does not have any media to reload the
page text region from: The file configs/ea3131/src/up_fillpage.c is only
page text region from: The file boards/ea3131/src/up_fillpage.c is only
a stub. That logic to actually reload the page from some storage medium
(among other things) would have to be implemented in order to complete this
example. At present, the example works correctly up to the point where
@ -438,7 +438,7 @@ On-Demand Paging
Alternative:
------------
I have implemented an alternative within configs/ea3131/src/up_fillpage.c
I have implemented an alternative within boards/ea3131/src/up_fillpage.c
which is probably only useful for testing. Here is the usage module
for this alternative
@ -495,7 +495,7 @@ ARM/EA3131-specific Configuration Options
CONFIG_ARCH_CHIP_LPC3131
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ea3131

2
boards/ea3131/locked/ld-locked.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/ea3131/locked/ld-locked.script
* boards/ea3131/locked/ld-locked.script
*
* Copyright (C) 2010 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/ea3131/pgnsh/defconfig
View File

@ -41,7 +41,7 @@ CONFIG_PAGING_NPPAGED=96
CONFIG_PAGING_NVPAGED=384
CONFIG_PAGING_PAGESIZE=1024
CONFIG_PAGING_STACKSIZE=2048
CONFIG_PASS1_BUILDIR="configs/ea3131/locked"
CONFIG_PASS1_BUILDIR="boards/ea3131/locked"
CONFIG_PASS1_OBJECT="locked.r"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4

2
boards/ea3131/scripts/ld.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/ea3131/scripts/ld.script
* boards/ea3131/scripts/ld.script
*
* Copyright (C) 2010-2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/ea3131/scripts/pg-ld.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/ea3131/scripts/pg-ld.script
* boards/ea3131/scripts/pg-ld.script
*
* Copyright (C) 2010, 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

16
boards/ea3152/README.txt
View File

@ -159,7 +159,7 @@ NuttX buildroot Toolchain
4. cd <some-dir>/buildroot
5. cp configs/arm926t-defconfig-4.2.4 .config
5. cp boards/arm926t-defconfig-4.2.4 .config
6. make oldconfig
@ -168,7 +168,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
See the file configs/README.txt in the buildroot source tree. That has more
See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@ -194,11 +194,11 @@ Image Format
it!
To work around both of these issues, I have created a small program under
configs/ea3152/tools to add the header. This program can be built under
boards/ea3152/tools to add the header. This program can be built under
either Linux or Cygwin (and probably other tool environments as well). That
tool can be built as follows:
- cd configs/ea3152/tools
- cd boards/ea3152/tools
- make
Then, to build the NuttX binary ready to load with the bootloader, just
@ -215,10 +215,10 @@ Image Format
to mklpc.sh in the final step.
2. You can instruct Symantec to ignore the errors and it will stop quarantining
the NXP program.
3. The CRC32 logic in configs/ea3152/tools doesn't seem to work. As a result,
3. The CRC32 logic in boards/ea3152/tools doesn't seem to work. As a result,
the CRC is currently disabled in the header:
RCS file: /cvsroot/nuttx/nuttx/configs/ea3152/tools/lpchdr.c,v
RCS file: /cvsroot/nuttx/nuttx/boards/ea3152/tools/lpchdr.c,v
retrieving revision 1.2
diff -r1.2 lpchdr.c
264c264
@ -261,7 +261,7 @@ Using OpenOCD and GDB
Then you should be able to start the OpenOCD daemon like:
configs/ea3152/tools/oocd.sh $PWD
boards/ea3152/tools/oocd.sh $PWD
Where it is assumed that you are executing oocd.sh from the top level
directory where NuttX is installed.
@ -301,7 +301,7 @@ ARM/EA3152-specific Configuration Options
CONFIG_ARCH_CHIP_LPC3152
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ea3152

2
boards/ea3152/scripts/ea3152.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/ea3152/scripts/ea3152.ld
* boards/ea3152/scripts/ea3152.ld
*
* Copyright (C) 2011-2012, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/eagle100/README.txt
View File

@ -91,7 +91,7 @@ Eagle100-specific Configuration Options
CONFIG_ARCH_CHIP_LM3S6918
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=eagle100 (for the MicroMint Eagle-100 development board)

2
boards/eagle100/scripts/ld.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/eagle100/scripts/ld.script
* boards/eagle100/scripts/ld.script
*
* Copyright (C) 2009, 2011-2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
* boards/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
*
* Copyright (C) 2012, 2014, 2017 Gregory Nutt. All rights reserved.
*

2
boards/efm32gg-stk3700/scripts/ld.script
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/efm32gg-stk3700/scripts/ld.script
* boards/efm32gg-stk3700/scripts/ld.script
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
*

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

@ -98,7 +98,7 @@ Stellaris EKK-LM3S9B96 Evaluation Kit Configuration Options
CONFIG_ARCH_CHIP_LM3S9B96
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ekk-lm3s9b96 (for the Stellaris EKK-LM3S9b96 Evaluation Kit)

2
boards/ekk-lm3s9b96/scripts/ekk-lm3s9b96.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/ekk-lm3s9b96/ostest/ekk-lm3s9b96.ld
* boards/ekk-lm3s9b96/ostest/ekk-lm3s9b96.ld
*
* Copyright (C) 2012, 2017 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt <gnutt@nuttx.org>

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

@ -277,7 +277,7 @@ OpenOCD for the ESP32
to reflect the physical JTAG adapter connected.
NOTE: A copy of this OpenOCD configuration file available in the NuttX
source tree at nuttx/configs/esp32-core/scripts/esp32.cfg . It has these
source tree at nuttx/boards/esp32-core/scripts/esp32.cfg . It has these
modifications:
- The referenced "set ESP32_RTOS none" line has been uncommented
@ -533,7 +533,7 @@ OpenOCD for the ESP32
I did the initial bring-up using the IRAM configuration and OpenOCD. Here
is a synopsis of my debug steps:
configs/esp32-core/nsh with
boards/esp32-core/nsh with
CONFIG_DEBUG_ASSERTIONS=y
CONFIG_DEBUG_FEATURES=y
@ -549,7 +549,7 @@ OpenOCD for the ESP32
Start OpenOCD:
cd ../openocde-esp32
cp ../nuttx/configs/esp32-core/scripts/esp32.cfg .
cp ../nuttx/boards/esp32-core/scripts/esp32.cfg .
sudo ./src/openocd -s ./tcl/ -f tcl/interface/ftdi/olimex-arm-usb-ocd.cfg -f ./esp32.cfg
Start GDB and load code:
@ -648,7 +648,7 @@ NOTES:
to provide that logic -- hopefully that is coming. As a
consequence, whatever clock setup was left when NuttX started is
used. For the case of execution out of IRAM with GDB, the
settings in configs/esp32-core/include/board.h work. To check
settings in boards/esp32-core/include/board.h work. To check
the timing, I use a stop watch and:
nsh> sleep 60

2
boards/esp32-core/scripts/esp32.template
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/elf32-core/scripts/esp32.template
* boards/elf32-core/scripts/esp32.template
* ESP32 Linker Script Memory Layout
*
* This file describes the memory layout (memory blocks) as virtual

2
boards/esp32-core/scripts/esp32_flash.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/elf32-core/scripts/esp32_flash.ld
* boards/elf32-core/scripts/esp32_flash.ld
****************************************************************************/
/* Default entry point: */

2
boards/esp32-core/scripts/esp32_iram.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/elf32-core/scripts/esp32_iram.ld
* boards/elf32-core/scripts/esp32_iram.ld
****************************************************************************/
/* Default entry point: */

2
boards/esp32-core/scripts/esp32_peripherals.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/elf32-core/scripts/esp32_peripherals.ld
* boards/elf32-core/scripts/esp32_peripherals.ld
****************************************************************************/
PROVIDE ( UART0 = 0x3ff40000 );

2
boards/esp32-core/scripts/esp32_rom.ld
View File

@ -1163,7 +1163,7 @@ PROVIDE ( r_lld_pdu_tx_prog = 0x4004b120 );
PROVIDE ( r_lld_pdu_tx_push = 0x4004b080 );
PROVIDE ( r_lld_ral_renew_req = 0x4004a73c );
/****************************************************************************
* configs/elf32-core/scripts/esp32_rom.ld
* boards/elf32-core/scripts/esp32_rom.ld
****************************************************************************/
PROVIDE ( r_lld_scan_start = 0x40048ee0 );

2
boards/ez80f910200kitg/README.txt
View File

@ -71,7 +71,7 @@ Other Versions
If you use any version of ZDS-II other than 5.1.1, 5.2.1, or 5.3.0 or
if you install ZDS-II at any location other than the default location,
you will have to modify three files: (1) arch/arm/z80/src/ez80/Kconfig,
(2) configs/ez80f910200kitg/scripts/Make.defs and, perhaps, (3)
(2) boards/ez80f910200kitg/scripts/Make.defs and, perhaps, (3)
arch/z80/src/ez80/Toolchain.defs.
Configuration Subdirectories

2
boards/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd
View File

@ -1,5 +1,5 @@
/****************************************************************************/
/* configs/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd */
/* boards/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd */
/* */
/* Copyright (C) 2008 Gregory Nutt. All rights reserved. */
/* Author: Gregory Nutt <gnutt@nuttx.org> */

2
boards/ez80f910200zco/README.txt
View File

@ -71,7 +71,7 @@ Other Versions
If you use any version of ZDS-II other than 5.1.1, 5.2.1, or 5.3.0 or
if you install ZDS-II at any location other than the default location,
you will have to modify three files: (1) arch/arm/z80/src/ez80/Kconfig,
(2) configs/ez80f910200zco/scripts/Make.defs and, perhaps, (3)
(2) boards/ez80f910200zco/scripts/Make.defs and, perhaps, (3)
arch/z80/src/ez80/Toolchain.defs.
Configurations

2
boards/ez80f910200zco/scripts/ez80f910200zco.linkcmd
View File

@ -1,5 +1,5 @@
/****************************************************************************/
/* configs/ez80f910200zco/scripts/ez80f910200zco.linkcmd */
/* boards/ez80f910200zco/scripts/ez80f910200zco.linkcmd */
/* */
/* Copyright (C) 2009, 2017 Gregory Nutt. All rights reserved. */
/* Author: Gregory Nutt <gnutt@nuttx.org> */

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

@ -228,13 +228,13 @@ OpenOCD
=======
I have also used OpenOCD with the M3 Wildfire. In this case, I used
the Olimex USB ARM OCD. See the script in configs/fire-stm32v2/tools/oocd.sh
the Olimex USB ARM OCD. See the script in boards/fire-stm32v2/tools/oocd.sh
for more information. Using the script:
1) Start the OpenOCD GDB server
cd <nuttx-build-directory>
configs/fire-stm32v2/tools/oocd.sh $PWD
boards/fire-stm32v2/tools/oocd.sh $PWD
2) Load Nuttx
@ -333,7 +333,7 @@ M3 Wildfire-specific Configuration Options
CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=fire-stm32v2 (for the M3 Wildfire development board)

2
boards/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
* boards/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
*
* Copyright (C) 2012, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/fire-stm32v2/scripts/fire-stm32v2.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/fire-stm32v2/scripts/fire-stm32v2.ld
* boards/fire-stm32v2/scripts/fire-stm32v2.ld
*
* Copyright (C) 2012, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

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

@ -1,4 +1,4 @@
configs/flipnclick-pic32mz README
boards/flipnclick-pic32mz README
===============================
This README file discusses the port of NuttX to the Mikroe Flip&Click

2
boards/flipnclick-pic32mz/scripts/c32-debug.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/flipnclick-pic32mz/nsh/c32-debug.ld
* boards/flipnclick-pic32mz/nsh/c32-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/flipnclick-pic32mz/scripts/mips-debug.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/flipnclick-pic32mz/nsh/mips-debug.ld
* boards/flipnclick-pic32mz/nsh/mips-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/flipnclick-pic32mz/scripts/pinguino-debug.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/flipnclick-pic32mz/nsh/mips-debug.ld
* boards/flipnclick-pic32mz/nsh/mips-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/flipnclick-pic32mz/scripts/xc32-debug.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/flipnclick-pic32mz/nsh/mips-debug.ld
* boards/flipnclick-pic32mz/nsh/mips-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

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

@ -470,7 +470,7 @@ Flip&Click SAM3X-specific Configuration Options
CONFIG_ARCH_CHIP_SAM3X
CONFIG_ARCH_CHIP_ATSAM3X8E
CONFIG_ARCH_BOARD - Identifies the configs/ subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=flipnclick-sam3x (for the Flip&Click SAM3X development board)

2
boards/flipnclick-sam3x/scripts/flash.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/flipnclick-sam3x/scripts/flash.ld
* boards/flipnclick-sam3x/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

2
boards/freedom-k28f/scripts/flash.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/freedom-k28f/scripts/flash.ld
* boards/freedom-k28f/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

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

@ -673,7 +673,7 @@ Freedom K64F Configuration Options
CONFIG_ARCH_CHIP_MK64FN1M0VLL12
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD="freedom-k64f" (for the Freedom K64F development board)

2
boards/freedom-k64f/scripts/flash.ld
View File

@ -1,5 +1,5 @@
/****************************************************************************
* configs/freedom-k64f/scripts/flash.ld
* boards/freedom-k64f/scripts/flash.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>

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