This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/nuttx-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new af2ec0fec Publishing web: 16e1777b863bd27e3a00b7b779baf0131af07df6
docs: f57a5a68022684d76c435f8f91fc5d0338d158d3
af2ec0fec is described below
commit af2ec0fec84cc6965157389d02e9165238701f1b
Author: Alin Jerpelea <alin.jerpe...@sony.com>
AuthorDate: Fri May 16 00:31:11 2025 +0000
Publishing web: 16e1777b863bd27e3a00b7b779baf0131af07df6 docs:
f57a5a68022684d76c435f8f91fc5d0338d158d3
---
content/docs/10.0.0/index.html | 2 +-
content/docs/10.0.1/index.html | 2 +-
content/docs/10.1.0/index.html | 2 +-
content/docs/10.2.0/index.html | 2 +-
content/docs/10.3.0/index.html | 2 +-
content/docs/11.0.0/index.html | 2 +-
content/docs/12.0.0/index.html | 2 +-
content/docs/12.0.0/searchindex.js | 2 +-
content/docs/12.1.0/index.html | 2 +-
content/docs/12.1.0/searchindex.js | 2 +-
content/docs/12.2.0/index.html | 2 +-
content/docs/12.2.0/searchindex.js | 2 +-
content/docs/12.2.1/index.html | 2 +-
content/docs/12.2.1/searchindex.js | 2 +-
content/docs/12.3.0/index.html | 2 +-
content/docs/12.3.0/searchindex.js | 2 +-
content/docs/12.4.0/index.html | 2 +-
content/docs/12.4.0/searchindex.js | 2 +-
content/docs/12.5.0/index.html | 2 +-
content/docs/12.5.0/searchindex.js | 2 +-
content/docs/12.5.1/index.html | 2 +-
content/docs/12.5.1/searchindex.js | 2 +-
content/docs/12.6.0/index.html | 2 +-
content/docs/12.6.0/searchindex.js | 2 +-
content/docs/12.7.0/index.html | 2 +-
content/docs/12.7.0/searchindex.js | 2 +-
content/docs/12.8.0/index.html | 2 +-
content/docs/12.8.0/searchindex.js | 2 +-
content/docs/12.9.0/index.html | 2 +-
content/docs/12.9.0/searchindex.js | 2 +-
.../applications/examples/camera/index.rst.txt | 2 +-
.../applications/graphics/nxwm/cnxconsole.rst.txt | 2 +-
.../components/drivers/special/pci/index.rst.txt | 16 ++
.../components/drivers/thermal/index.rst.txt | 2 +-
.../_sources/components/filesystem/mnemofs.rst.txt | 4 +-
.../_sources/components/filesystem/tmpfs.rst.txt | 2 +-
.../_sources/components/libs/libc/index.rst.txt | 2 +-
.../components/nxgraphics/appendix.rst.txt | 8 +-
.../latest/_sources/components/syscall.rst.txt | 2 +-
.../_sources/contributing/coding_style.rst.txt | 4 +-
.../latest/_sources/debugging/coresight.rst.txt | 2 +-
.../guides/port_drivers_to_stm32f7.rst.txt | 4 +-
.../docs/latest/_sources/guides/pysimcoder.rst.txt | 2 +-
.../_sources/implementation/device_drivers.rst.txt | 2 +-
.../lpc31xx/boards/olimex-lpc-h3131/index.rst.txt | 2 +-
.../platforms/arm/nrf52/ieee802154.rst.txt | 4 +-
.../_sources/platforms/arm/s32k1xx/index.rst.txt | 2 +-
.../arm/stm32f4/boards/nucleo-f429zi/index.rst.txt | 210 +++++++++++++++++++++
.../stm32f4/boards/stm32f401rc-rs485/index.rst.txt | 2 +-
.../_sources/platforms/avr/atmega/index.rst.txt | 2 +-
.../intel64/boards/qemu-intel64/index.rst.txt | 5 +
.../latest/_sources/reference/os/mutex.rst.txt | 2 +-
.../latest/applications/examples/camera/index.html | 2 +-
.../applications/graphics/nxwm/cnxconsole.html | 2 +-
.../latest/components/drivers/special/index.html | 1 +
.../components/drivers/special/pci/index.html | 13 ++
.../latest/components/drivers/thermal/index.html | 2 +-
.../docs/latest/components/filesystem/mnemofs.html | 2 +-
.../docs/latest/components/filesystem/tmpfs.html | 2 +-
.../docs/latest/components/libs/libc/index.html | 2 +-
.../latest/components/nxgraphics/appendix.html | 8 +-
content/docs/latest/components/syscall.html | 2 +-
content/docs/latest/contributing/coding_style.html | 4 +-
content/docs/latest/debugging/coresight.html | 2 +-
.../latest/guides/port_drivers_to_stm32f7.html | 2 +-
content/docs/latest/guides/pysimcoder.html | 2 +-
.../docs/latest/implementation/device_drivers.html | 2 +-
content/docs/latest/index.html | 2 +-
content/docs/latest/introduction/resources.html | 2 +-
content/docs/latest/objects.inv | Bin 150617 -> 150725 bytes
.../arm/kinetis/boards/twr-k60n512/index.html | 2 +-
.../arm/kinetis/boards/twr-k64f120m/index.html | 2 +-
.../arm/lpc31xx/boards/olimex-lpc-h3131/index.html | 2 +-
.../latest/platforms/arm/nrf52/ieee802154.html | 4 +-
.../docs/latest/platforms/arm/s32k1xx/index.html | 2 +-
.../arm/samd2l2/boards/samd20-xplained/index.html | 2 +-
.../arm/samd2l2/boards/samd21-xplained/index.html | 2 +-
.../arm/stm32f4/boards/nucleo-f429zi/index.html | 200 ++++++++++++++++++++
.../stm32f4/boards/stm32f401rc-rs485/index.html | 2 +-
.../avr/at90usb/boards/micropendous3/index.html | 8 +-
.../avr/at90usb/boards/teensy-2.0/index.html | 6 +-
.../platforms/avr/atmega/boards/amber/index.html | 6 +-
.../docs/latest/platforms/avr/atmega/index.html | 2 +-
.../x86_64/intel64/boards/qemu-intel64/index.html | 6 +
content/docs/latest/reference/os/mutex.html | 2 +-
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 +-
87 files changed, 550 insertions(+), 99 deletions(-)
diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index bb3fe92d3..5ad55d553 100644
--- a/content/docs/10.0.0/index.html
+++ b/content/docs/10.0.0/index.html
@@ -207,7 +207,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 32-bit microcontroller
environments, the primary governing standards in NuttX are Posix and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:13</p>
+<p>Last Updated: 16 May 25 at 00:14</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.0.1/index.html b/content/docs/10.0.1/index.html
index 606f5d71d..faf66981b 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -243,7 +243,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 32-bit microcontroller
environments, the primary governing standards in NuttX are Posix and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:14</p>
+<p>Last Updated: 16 May 25 at 00:15</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.1.0/index.html b/content/docs/10.1.0/index.html
index 3c81429e3..6bc9c1f6d 100644
--- a/content/docs/10.1.0/index.html
+++ b/content/docs/10.1.0/index.html
@@ -243,7 +243,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:14</p>
+<p>Last Updated: 16 May 25 at 00:15</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.2.0/index.html b/content/docs/10.2.0/index.html
index ee345704e..dfd493fff 100644
--- a/content/docs/10.2.0/index.html
+++ b/content/docs/10.2.0/index.html
@@ -244,7 +244,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:14</p>
+<p>Last Updated: 16 May 25 at 00:15</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.3.0/index.html b/content/docs/10.3.0/index.html
index ee345704e..e1db462dc 100644
--- a/content/docs/10.3.0/index.html
+++ b/content/docs/10.3.0/index.html
@@ -244,7 +244,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:14</p>
+<p>Last Updated: 16 May 25 at 00:16</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/11.0.0/index.html b/content/docs/11.0.0/index.html
index 238aaa672..e1db462dc 100644
--- a/content/docs/11.0.0/index.html
+++ b/content/docs/11.0.0/index.html
@@ -244,7 +244,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:15</p>
+<p>Last Updated: 16 May 25 at 00:16</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.0.0/index.html b/content/docs/12.0.0/index.html
index 20e2382eb..4ab11be69 100644
--- a/content/docs/12.0.0/index.html
+++ b/content/docs/12.0.0/index.html
@@ -169,7 +169,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<section id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline"></a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:15</p>
+<p>Last Updated: 16 May 25 at 00:16</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.0.0/searchindex.js
b/content/docs/12.0.0/searchindex.js
index e0b6c3afe..af142b5f6 100644
--- a/content/docs/12.0.0/searchindex.js
+++ b/content/docs/12.0.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ No newline at end of file
+Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ No newline at end of file
diff --git a/content/docs/12.1.0/index.html b/content/docs/12.1.0/index.html
index a5180edd7..386a3c96b 100644
--- a/content/docs/12.1.0/index.html
+++ b/content/docs/12.1.0/index.html
@@ -169,7 +169,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<section id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline"></a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:15</p>
+<p>Last Updated: 16 May 25 at 00:17</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.1.0/searchindex.js
b/content/docs/12.1.0/searchindex.js
index e3a980891..c8886057b 100644
--- a/content/docs/12.1.0/searchindex.js
+++ b/content/docs/12.1.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ No newline at end of file
+Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ No newline at end of file
diff --git a/content/docs/12.2.0/index.html b/content/docs/12.2.0/index.html
index 31e798ca7..98c0f1873 100644
--- a/content/docs/12.2.0/index.html
+++ b/content/docs/12.2.0/index.html
@@ -170,7 +170,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<section id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this heading"></a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:16</p>
+<p>Last Updated: 16 May 25 at 00:17</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.2.0/searchindex.js
b/content/docs/12.2.0/searchindex.js
index b8ce5a00a..78796954f 100644
--- a/content/docs/12.2.0/searchindex.js
+++ b/content/docs/12.2.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index",
"applications/nsh/builtin", "applications/nsh/commands",
"applications/nsh/config", "applications/nsh/customizing",
"applications/nsh/index", "applications/nsh/installation",
"applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config",
"applications/nxdiag/index", "applications/wapi/commands",
"applications/wapi/index", "applications/wapi/wireless", "components/binfmt",
"components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index",
"applications/nsh/builtin", "applications/nsh/commands",
"applications/nsh/config", "applications/nsh/customizing",
"applications/nsh/index", "applications/nsh/installation",
"applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config",
"applications/nxdiag/index", "applications/wapi/commands",
"applications/wapi/index", "applications/wapi/wireless", "components/binfmt",
"components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.2.1/index.html b/content/docs/12.2.1/index.html
index 31e798ca7..98c0f1873 100644
--- a/content/docs/12.2.1/index.html
+++ b/content/docs/12.2.1/index.html
@@ -170,7 +170,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<section id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this heading"></a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:16</p>
+<p>Last Updated: 16 May 25 at 00:17</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.2.1/searchindex.js
b/content/docs/12.2.1/searchindex.js
index 00ea93fe0..f81d05d32 100644
--- a/content/docs/12.2.1/searchindex.js
+++ b/content/docs/12.2.1/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index",
"applications/nsh/builtin", "applications/nsh/commands",
"applications/nsh/config", "applications/nsh/customizing",
"applications/nsh/index", "applications/nsh/installation",
"applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config",
"applications/nxdiag/index", "applications/wapi/commands",
"applications/wapi/index", "applications/wapi/wireless", "components/binfmt",
"components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index",
"applications/nsh/builtin", "applications/nsh/commands",
"applications/nsh/config", "applications/nsh/customizing",
"applications/nsh/index", "applications/nsh/installation",
"applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config",
"applications/nxdiag/index", "applications/wapi/commands",
"applications/wapi/index", "applications/wapi/wireless", "components/binfmt",
"components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.3.0/index.html b/content/docs/12.3.0/index.html
index 04aa96ec1..8035b88a8 100644
--- a/content/docs/12.3.0/index.html
+++ b/content/docs/12.3.0/index.html
@@ -170,7 +170,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<section id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this heading"></a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:17</p>
+<p>Last Updated: 16 May 25 at 00:18</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.3.0/searchindex.js
b/content/docs/12.3.0/searchindex.js
index f54463e04..8f1ab4abf 100644
--- a/content/docs/12.3.0/searchindex.js
+++ b/content/docs/12.3.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index",
"applications/nsh/builtin", "applications/nsh/commands",
"applications/nsh/config", "applications/nsh/customizing",
"applications/nsh/index", "applications/nsh/installation",
"applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config",
"applications/nxdiag/index", "applications/wapi/commands",
"applications/wapi/index", "applications/wapi/wireless", "components/binfmt",
"components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index",
"applications/nsh/builtin", "applications/nsh/commands",
"applications/nsh/config", "applications/nsh/customizing",
"applications/nsh/index", "applications/nsh/installation",
"applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config",
"applications/nxdiag/index", "applications/wapi/commands",
"applications/wapi/index", "applications/wapi/wireless", "components/binfmt",
"components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.4.0/index.html b/content/docs/12.4.0/index.html
index 42b756bc4..76c3fad4d 100644
--- a/content/docs/12.4.0/index.html
+++ b/content/docs/12.4.0/index.html
@@ -177,7 +177,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:17</p>
+<p>Last Updated: 16 May 25 at 00:18</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.4.0/searchindex.js
b/content/docs/12.4.0/searchindex.js
index 242539597..95719fe3d 100644
--- a/content/docs/12.4.0/searchindex.js
+++ b/content/docs/12.4.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/coremark/index", "applications/benchmarks/index",
"applications/boot/index", "applications/boot/mcuboot/index",
"applications/boot/miniboot/index", "applications/canutils/candump/index",
"applications/canutils/canlib/index", "applications/canutils/cansend/index",
"applications/c [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/coremark/index", "applications/benchmarks/index",
"applications/boot/index", "applications/boot/mcuboot/index",
"applications/boot/miniboot/index", "applications/canutils/candump/index",
"applications/canutils/canlib/index", "applications/canutils/cansend/index",
"applications/c [...]
\ No newline at end of file
diff --git a/content/docs/12.5.0/index.html b/content/docs/12.5.0/index.html
index f338e7c28..b2fcc0976 100644
--- a/content/docs/12.5.0/index.html
+++ b/content/docs/12.5.0/index.html
@@ -177,7 +177,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:18</p>
+<p>Last Updated: 16 May 25 at 00:20</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.5.0/searchindex.js
b/content/docs/12.5.0/searchindex.js
index 299b5af7f..c55239383 100644
--- a/content/docs/12.5.0/searchindex.js
+++ b/content/docs/12.5.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/coremark/index", "applications/benchmarks/index",
"applications/boot/index", "applications/boot/mcuboot/index",
"applications/boot/miniboot/index", "applications/canutils/candump/index",
"applications/canutils/canlib/index", "applications/canutils/cansend/index",
"applications/c [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/coremark/index", "applications/benchmarks/index",
"applications/boot/index", "applications/boot/mcuboot/index",
"applications/boot/miniboot/index", "applications/canutils/candump/index",
"applications/canutils/canlib/index", "applications/canutils/cansend/index",
"applications/c [...]
\ No newline at end of file
diff --git a/content/docs/12.5.1/index.html b/content/docs/12.5.1/index.html
index dcb132b14..3ba078000 100644
--- a/content/docs/12.5.1/index.html
+++ b/content/docs/12.5.1/index.html
@@ -177,7 +177,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:20</p>
+<p>Last Updated: 16 May 25 at 00:21</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.5.1/searchindex.js
b/content/docs/12.5.1/searchindex.js
index 1f73cb5ce..ba485d940 100644
--- a/content/docs/12.5.1/searchindex.js
+++ b/content/docs/12.5.1/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/coremark/index", "applications/benchmarks/index",
"applications/boot/index", "applications/boot/mcuboot/index",
"applications/boot/miniboot/index", "applications/canutils/candump/index",
"applications/canutils/canlib/index", "applications/canutils/cansend/index",
"applications/c [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/coremark/index", "applications/benchmarks/index",
"applications/boot/index", "applications/boot/mcuboot/index",
"applications/boot/miniboot/index", "applications/canutils/candump/index",
"applications/canutils/canlib/index", "applications/canutils/cansend/index",
"applications/c [...]
\ No newline at end of file
diff --git a/content/docs/12.6.0/index.html b/content/docs/12.6.0/index.html
index 344e68cab..3abcb7419 100644
--- a/content/docs/12.6.0/index.html
+++ b/content/docs/12.6.0/index.html
@@ -178,7 +178,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:21</p>
+<p>Last Updated: 16 May 25 at 00:22</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.6.0/searchindex.js
b/content/docs/12.6.0/searchindex.js
index c8c5d27a2..3d38cce7b 100644
--- a/content/docs/12.6.0/searchindex.js
+++ b/content/docs/12.6.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/benchmarks/iozone/index",
"applications/bench [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/benchmarks/iozone/index",
"applications/bench [...]
\ No newline at end of file
diff --git a/content/docs/12.7.0/index.html b/content/docs/12.7.0/index.html
index 1b6e65daf..a5c254fe8 100644
--- a/content/docs/12.7.0/index.html
+++ b/content/docs/12.7.0/index.html
@@ -177,7 +177,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:23</p>
+<p>Last Updated: 16 May 25 at 00:24</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.7.0/searchindex.js
b/content/docs/12.7.0/searchindex.js
index 1e224fd03..80c4180de 100644
--- a/content/docs/12.7.0/searchindex.js
+++ b/content/docs/12.7.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/benchmarks/iozone/index",
"applications/bench [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/benchmarks/iozone/index",
"applications/bench [...]
\ No newline at end of file
diff --git a/content/docs/12.8.0/index.html b/content/docs/12.8.0/index.html
index 37fe414b2..00362e901 100644
--- a/content/docs/12.8.0/index.html
+++ b/content/docs/12.8.0/index.html
@@ -177,7 +177,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:24</p>
+<p>Last Updated: 16 May 25 at 00:25</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.8.0/searchindex.js
b/content/docs/12.8.0/searchindex.js
index 29f074dd2..2a57cb278 100644
--- a/content/docs/12.8.0/searchindex.js
+++ b/content/docs/12.8.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/benchmarks/iozone/index",
"applications/bench [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/benchmarks/iozone/index",
"applications/bench [...]
\ No newline at end of file
diff --git a/content/docs/12.9.0/index.html b/content/docs/12.9.0/index.html
index a1c313960..1887edd37 100644
--- a/content/docs/12.9.0/index.html
+++ b/content/docs/12.9.0/index.html
@@ -177,7 +177,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:26</p>
+<p>Last Updated: 16 May 25 at 00:27</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/12.9.0/searchindex.js
b/content/docs/12.9.0/searchindex.js
index 52a9e9ed4..a53f9c45a 100644
--- a/content/docs/12.9.0/searchindex.js
+++ b/content/docs/12.9.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/cyclictest/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/b [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index",
"applications/audioutils/index", "applications/audioutils/mml_parser/index",
"applications/audioutils/nxaudio/index",
"applications/benchmarks/cachespeed/index",
"applications/benchmarks/coremark-pro/index",
"applications/benchmarks/coremark/index",
"applications/benchmarks/cyclictest/index",
"applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index",
"applications/benchmarks/index", "applications/b [...]
\ No newline at end of file
diff --git
a/content/docs/latest/_sources/applications/examples/camera/index.rst.txt
b/content/docs/latest/_sources/applications/examples/camera/index.rst.txt
index 08ad07565..a2cd586f0 100644
--- a/content/docs/latest/_sources/applications/examples/camera/index.rst.txt
+++ b/content/docs/latest/_sources/applications/examples/camera/index.rst.txt
@@ -7,7 +7,7 @@ the command is as below.::
nsh> camera ([-jpg]) ([capture num])
- -jpg : this option is set for storing JPEG file into a strage.
+ -jpg : this option is set for storing JPEG file into a storage.
: If this option isn't set capturing raw RGB565 data in a file.
: raw RGB565 is default.
diff --git
a/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt
b/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt
index e96d2fb26..af399547d 100644
--- a/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt
+++ b/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt
@@ -125,7 +125,7 @@ Almost everything said here applies to mouse/touchscreen
input as well. If we
were to replace the names keyboard to mouse, kbdin to mousein, etc. you have a
pretty good description of how mouse/touchscreen input works.
-The mouse/touchscreen input is a little simpler, however: The main simplication
+The mouse/touchscreen input is a little simpler, however: The main
simplification
is that the additional complexities of the NxConsole and its special input
device
do not apply. Mouse/touchscreen input as always steered to widgets when the
callback is received in ``CCallback::newMouseEvent`` by an unconditional call
to
diff --git
a/content/docs/latest/_sources/components/drivers/special/pci/index.rst.txt
b/content/docs/latest/_sources/components/drivers/special/pci/index.rst.txt
index 1c598a910..99160423b 100644
--- a/content/docs/latest/_sources/components/drivers/special/pci/index.rst.txt
+++ b/content/docs/latest/_sources/components/drivers/special/pci/index.rst.txt
@@ -106,3 +106,19 @@ An example command to run the driver on ``x86_64`` looks
like this:
-nographic -serial mon:stdio -object can-bus,id=canbus0-bus \
-object can-host-socketcan,if=can0,canbus=canbus0-bus,id=canbus0-socketcan \
-device ctucan_pci,canbus0=canbus0-bus,canbus1=canbus0-bus
+
+xHCI over PCI
+-------------
+
+xHCI support was tested on x86_64 target, both on QEMU and real hardware.
+
+Known issues with this driver:
+
+- Currently only USB2.0 is supported, there is no USB3.0 support in NuttX yet.
+
+- USB HUB devices not supported yet
+
+To enable xHCI support on QEMU, we have to add ``-device qemu-xhci`` argument.
+All supported USB devices in QEMU can be found in
+`QEMU documentation
<https://qemu-project.gitlab.io/qemu/system/devices/usb.html>`_,
+but not all classes are supported in NuttX.
diff --git
a/content/docs/latest/_sources/components/drivers/thermal/index.rst.txt
b/content/docs/latest/_sources/components/drivers/thermal/index.rst.txt
index 5a32d629f..019c62ea2 100644
--- a/content/docs/latest/_sources/components/drivers/thermal/index.rst.txt
+++ b/content/docs/latest/_sources/components/drivers/thermal/index.rst.txt
@@ -18,7 +18,7 @@ Brief
- ``HOT``: When the device temperature reaches this trip point, stricter
temperature control (such as resource limiting) is required. If the current
temperature is equals to OR greater than temperature obtained last time, the
temperature control level is increased.
- ``CRITICAL``: Shut down / restart the device.
-#. ProcFS node supported, used for debugging, and we can get the binding info
between "Zone", "Cooling Decice", "Trip" and "Governor", temperature value and
cooling state; (for example, "Zone Device"(temperature sensor):
``/proc/thermal/cpu_thermal``), and write 0 or 1 to turn off or on the "Zone
Device";
+#. ProcFS node supported, used for debugging, and we can get the binding info
between "Zone", "Cooling Device", "Trip" and "Governor", temperature value and
cooling state; (for example, "Zone Device"(temperature sensor):
``/proc/thermal/cpu_thermal``), and write 0 or 1 to turn off or on the "Zone
Device";
Device Driver
=============
diff --git a/content/docs/latest/_sources/components/filesystem/mnemofs.rst.txt
b/content/docs/latest/_sources/components/filesystem/mnemofs.rst.txt
index e2d0d6709..9756d4471 100644
--- a/content/docs/latest/_sources/components/filesystem/mnemofs.rst.txt
+++ b/content/docs/latest/_sources/components/filesystem/mnemofs.rst.txt
@@ -148,7 +148,7 @@ of it was written properly. This helps in making it power
loss resilient.
The journal, when combined with CoW, plays another important role. In pure
CoW, any update to a CTZ file will result in it having a new location. This
-new location wil need to be updated in the parent, which itself will have a
+new location will need to be updated in the parent, which itself will have a
new location after the update, and so on till it reaches the root. The
journal stops this propagation immediately. When the journal is full above
a certain limit, it will flush, and apply all of these changes to the FS
@@ -261,4 +261,4 @@ VFS Method Layer
VFS method layer contains methods exposed to the VFS. This layer works with
the FS Object layer for direntry related tasks, or the LRU for file level
-read/write tasks.
\ No newline at end of file
+read/write tasks.
diff --git a/content/docs/latest/_sources/components/filesystem/tmpfs.rst.txt
b/content/docs/latest/_sources/components/filesystem/tmpfs.rst.txt
index 95fda02cf..1d0dacb49 100644
--- a/content/docs/latest/_sources/components/filesystem/tmpfs.rst.txt
+++ b/content/docs/latest/_sources/components/filesystem/tmpfs.rst.txt
@@ -2,7 +2,7 @@
TMPFS
=====
-NuttX TMPFS file system is a tiny dyamic RAM based file system.
+NuttX TMPFS file system is a tiny dynamic RAM based file system.
It can be enabled by adding ``CONFIG_FS_TMPFS=y`` to the configuration at
build time.
diff --git a/content/docs/latest/_sources/components/libs/libc/index.rst.txt
b/content/docs/latest/_sources/components/libs/libc/index.rst.txt
index 304df2334..fac61e12b 100644
--- a/content/docs/latest/_sources/components/libs/libc/index.rst.txt
+++ b/content/docs/latest/_sources/components/libs/libc/index.rst.txt
@@ -92,7 +92,7 @@ Each type field has a format as follows::
type name:
For all simpler types
formal type | actual type:
- For array types where the form of the formal (eg. int parm[2])
+ For array types where the form of the formal (eg. int param[2])
differs from the type of actual passed parameter (eg. int*). This
is necessary because you cannot do simple casts to array types.
formal type | union member actual type | union member fieldname:
diff --git
a/content/docs/latest/_sources/components/nxgraphics/appendix.rst.txt
b/content/docs/latest/_sources/components/nxgraphics/appendix.rst.txt
index 570e43982..08b116be5 100644
--- a/content/docs/latest/_sources/components/nxgraphics/appendix.rst.txt
+++ b/content/docs/latest/_sources/components/nxgraphics/appendix.rst.txt
@@ -572,8 +572,8 @@ Function Special Setup/Notes
``nx_lower()`` Change to ``CONFIG_EXAMPLES_NX_RAWWINDOWS=y`` in the
YES
``<NuttX-Directory>/.config`` file
``nx_modal()`` .
NO
-``nx_setvisibility()`` Exercized using Twm4Nx
YES, Informally
-``nx_ishidden()`` Exercized using Twm4Nx
YES, Informally
+``nx_setvisibility()`` Exercised using Twm4Nx
YES, Informally
+``nx_ishidden()`` Exercised using Twm4Nx
YES, Informally
``nx_fill()`` Change to ``CONFIG_EXAMPLES_NX_RAWWINDOWS=y`` in the
YES
``<NuttX-Directory>/.config`` file
``nx_getrectangle()`` .
YES
@@ -604,8 +604,8 @@ Function Special Setup/Notes
Verified
``nxtk_raise()`` . YES
``nxtk_lower()`` . YES
``nxtk_modal()`` . NO
-``nxtk_setvisibility()`` Exercized using Twm4Nx YES, informally
-``nxtk_ishidden()`` Exercized using Twm4Nx YES, informally
+``nxtk_setvisibility()`` Exercised using Twm4Nx YES, informally
+``nxtk_ishidden()`` Exercised using Twm4Nx YES, informally
``nxtk_fillwindow()`` . YES
``nxtk_getwindow()`` . NO
``nxtk_filltrapwindow()`` . NO
diff --git a/content/docs/latest/_sources/components/syscall.rst.txt
b/content/docs/latest/_sources/components/syscall.rst.txt
index 2ce0572a3..909f3cfe3 100644
--- a/content/docs/latest/_sources/components/syscall.rst.txt
+++ b/content/docs/latest/_sources/components/syscall.rst.txt
@@ -127,7 +127,7 @@ Each type field has a format as follows:
* formal type | actual type:
- For array types where the form of the formal (eg. ``int parm[2]``)
+ For array types where the form of the formal (eg. ``int param[2]``)
differs from the type of actual passed parameter (eg. ``int*``).
This is necessary because you cannot do simple casts to array types.
diff --git a/content/docs/latest/_sources/contributing/coding_style.rst.txt
b/content/docs/latest/_sources/contributing/coding_style.rst.txt
index 87ce5daf7..b1ab92c59 100644
--- a/content/docs/latest/_sources/contributing/coding_style.rst.txt
+++ b/content/docs/latest/_sources/contributing/coding_style.rst.txt
@@ -1228,8 +1228,8 @@ Structures
defining a structure within a type definition is discouraged. It is
preferred that the structure definition and the type definition be
separate definitions. In general, the NuttX coding style discourages
- any ``typdef``-ing of structures; normally the full structure name is
- used as types throughout the code. The reason for this is that is
+ any ``typedef``-ing of structures; normally the full structure name
+ is used as types throughout the code. The reason for this is that is
structure pointers may be forward referenced in header files without
having to include the file the provides the type definition. This
greatly reduces header file coupling.
diff --git a/content/docs/latest/_sources/debugging/coresight.rst.txt
b/content/docs/latest/_sources/debugging/coresight.rst.txt
index 9ece4ab75..865de2d8b 100644
--- a/content/docs/latest/_sources/debugging/coresight.rst.txt
+++ b/content/docs/latest/_sources/debugging/coresight.rst.txt
@@ -70,7 +70,7 @@ register with the framework for as long as they use the right
APIs:
``struct coresight_desc *desc`` describes the type of current coresight device
and where it connects to. When all the coresight devices are registered,
-devices throught the tracing stream path can be enablea by calling:
+devices through the tracing stream path can be enabled by calling:
.. c:function:: int coresight_enable(FAR struct coresight_dev_s *srcdev, FAR
struct coresight_dev_s *destdev);
diff --git
a/content/docs/latest/_sources/guides/port_drivers_to_stm32f7.rst.txt
b/content/docs/latest/_sources/guides/port_drivers_to_stm32f7.rst.txt
index aa6ec9c2d..0d5523206 100644
--- a/content/docs/latest/_sources/guides/port_drivers_to_stm32f7.rst.txt
+++ b/content/docs/latest/_sources/guides/port_drivers_to_stm32f7.rst.txt
@@ -249,7 +249,7 @@ the buffers to the Cortex-M7 D-Cache line size:
.. code-block:: c
- /* Buffers use fro DMA access must begin on an address aligned with the
+ /* Buffers used for DMA access must begin on an address aligned with the
* D-Cache line and must be an even multiple of the D-Cache line size.
* These size/alignment requirements are necessary so that D-Cache flush
* and invalidate operations will not have any additional effects.
@@ -439,4 +439,4 @@ Here is where the write buffer in clean prior to starting a
write DMA:
arch_clean_dcache((uintptr_t)priv->dev.d_buf,
(uintptr_t)priv->dev.d_buf + priv->dev.d_len);
...
- }
\ No newline at end of file
+ }
diff --git a/content/docs/latest/_sources/guides/pysimcoder.rst.txt
b/content/docs/latest/_sources/guides/pysimcoder.rst.txt
index 7ac3cce77..648c8bfb6 100644
--- a/content/docs/latest/_sources/guides/pysimcoder.rst.txt
+++ b/content/docs/latest/_sources/guides/pysimcoder.rst.txt
@@ -130,7 +130,7 @@ Using pysimCoder to design NuttX application
After running pysimCoder, separate blocks can be selected from the library
menu on the left hand side. The menu contains
several libraries, NuttX specific blocks can be found in library "NuttX". It
is also possible to use blocks from other
libraries like "input", "output", "math" and so on. Several blocks can have
specific parameter options and various number
-of inputs/outputs. Double left click on the block openes parameter settings
while single right click on the block leads
+of inputs/outputs. Double left click on the block opens parameter settings
while single right click on the block leads
to number of inputs/outputs setup. The pysimCoder interface can be seen in the
picture below.
.. figure:: image/interface.png
diff --git a/content/docs/latest/_sources/implementation/device_drivers.rst.txt
b/content/docs/latest/_sources/implementation/device_drivers.rst.txt
index 526c109a0..6a68d3087 100644
--- a/content/docs/latest/_sources/implementation/device_drivers.rst.txt
+++ b/content/docs/latest/_sources/implementation/device_drivers.rst.txt
@@ -60,7 +60,7 @@ The I2C Tool
Of course, like most rules, there are lots of violations. I2C is another bus
and
the the I2C "driver" is another transport similar in many ways to SPI. For I2C,
-there is an application at ``apps/system/i2c`` alled the "I2C tool" that will
allow
+there is an application at ``apps/system/i2c`` called the "I2C tool" that will
allow
you access I2C devices from the command line. This is not really just a test
tool
and not a real part of an application.
diff --git
a/content/docs/latest/_sources/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.rst.txt
b/content/docs/latest/_sources/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.rst.txt
index ef81e5c0e..61bb51371 100644
---
a/content/docs/latest/_sources/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.rst.txt
+++
b/content/docs/latest/_sources/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.rst.txt
@@ -854,7 +854,7 @@ configuration:
Since SDRAM is not currently working (see above) and NAND support
has not be integrated, the only really option is to put NSH "on a
- diet" to reduct the size so that it will fit into memory.
+ diet" to reduce the size so that it will fit into memory.
Here are a few things you can do:
diff --git
a/content/docs/latest/_sources/platforms/arm/nrf52/ieee802154.rst.txt
b/content/docs/latest/_sources/platforms/arm/nrf52/ieee802154.rst.txt
index ae80f6ebe..3748496e8 100644
--- a/content/docs/latest/_sources/platforms/arm/nrf52/ieee802154.rst.txt
+++ b/content/docs/latest/_sources/platforms/arm/nrf52/ieee802154.rst.txt
@@ -24,7 +24,7 @@ Work in progress features (some logic is present, but they
require more work):
* slotted CSMA-CA
* GTS
-Fetures not implemented:
+Features not implemented:
* enhanced ACK (Enh-ACK)
* enhanced beacon
@@ -40,5 +40,5 @@ This implementation reserves the following peripherals:
* ``TIMER0`` - used as high resolution timer for ACK, IFS and other radio
delays
-* ``RTC0`` - if superframe support is enabled, used as low power timer to hande
+* ``RTC0`` - if superframe support is enabled, used as low power timer to
handle
superframe events
diff --git a/content/docs/latest/_sources/platforms/arm/s32k1xx/index.rst.txt
b/content/docs/latest/_sources/platforms/arm/s32k1xx/index.rst.txt
index 32571a139..42017e67f 100644
--- a/content/docs/latest/_sources/platforms/arm/s32k1xx/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/arm/s32k1xx/index.rst.txt
@@ -91,7 +91,7 @@ Albeit the current implementation has some limitations:
* Max I2C speed of 400KHz
* Max transfer of 12 bytes (Could be extended by utilizing EDMA)
-* No abort on NACK reception, shifter simplies continues on
+* No abort on NACK reception, shifter simply continues
* No multi-master support
* No restart support
diff --git
a/content/docs/latest/_sources/platforms/arm/stm32f4/boards/nucleo-f429zi/index.rst.txt
b/content/docs/latest/_sources/platforms/arm/stm32f4/boards/nucleo-f429zi/index.rst.txt
index 9aac7d1b7..6cd589ae3 100644
---
a/content/docs/latest/_sources/platforms/arm/stm32f4/boards/nucleo-f429zi/index.rst.txt
+++
b/content/docs/latest/_sources/platforms/arm/stm32f4/boards/nucleo-f429zi/index.rst.txt
@@ -5,3 +5,213 @@ ST Nucleo F429ZI
.. tags:: chip:stm32, chip:stm32f4, chip:stm32f429
The Nucleo F429ZI is a member of the Nucleo-144 board family.
+
+This page discusses issues unique to NuttX configurations for the ST
+Nucleo F429ZI board from ST Micro. See
+
+ http://www.st.com/en/evaluation-tools/nucleo-f429zi.html
+
+NucleoF429ZI:
+
+- Microprocessor: 32-bit ARM Cortex M4 with 180 MHz max CPU frequency
+- Memory: 2 MB Flash and 256+4 KB SRAM including 64-Kbyte of core coupled
memory
+- ADC: 3x12-bit ADC with 24 channels
+- DMA: 16-stream DMA controller with FIFOs and burst support
+- Timers: Up to 17 timers: up to 12 16-bit, 2 32-bit timers, two
+ watchdog timers, and a SysTick timer
+- GPIO: Up to 168 I/O ports with interrupt capability
+- I2C: Up to 3 I2C interfaces
+- USARTs: Up to 4 USARTs
+- SPIs: Up to 6 SPIs (45 Mbit/s)
+
+
+See:
+ https://www.st.com/en/microcontrollers-microprocessors/stm32f429zi.html
+
+
+Hardware
+========
+
+Buttons
+-------
+
+B1 USER: the user button is connected to the I/O PC13 (pin 2) of the STM32
+microcontroller.
+
+LEDs
+----
+
+The Nucleo F410RB provide a single user LED, LD2. LD2
+is the green LED connected to Arduino signal D13 corresponding to MCU I/O
+PA5 (pin 21) or PB13 (pin 34) depending on the STM32target.
+
+- When the I/O is HIGH value, the LED is on.
+- When the I/O is LOW, the LED is off.
+
+These LEDs are not used by the board port unless CONFIG_ARCH_LEDS is
+defined. In that case, the usage by the board port is defined in
+include/board.h and src/sam_leds.c. The LEDs are used to encode OS-related
+events as follows when the red LED (PE24) is available::
+
+ SYMBOL Meaning LD2
+ ------------------- ----------------------- -----------
+ LED_STARTED NuttX has been started OFF
+ LED_HEAPALLOCATE Heap has been allocated OFF
+ LED_IRQSENABLED Interrupts enabled OFF
+ LED_STACKCREATED Idle stack created ON
+ LED_INIRQ In an interrupt No change
+ LED_SIGNAL In a signal handler No change
+ LED_ASSERTION An assertion failed No change
+ LED_PANIC The system has crashed Blinking
+ LED_IDLE MCU is is sleep mode Not used
+
+Thus if LD2, NuttX has successfully booted and is, apparently, running
+normally. If LD2 is flashing at approximately 2Hz, then a fatal error
+has been detected and the system has halted.
+
+Serial Consoles
+===============
+
+USART1
+------
+
+Pins and Connectors::
+
+ RXD: PA11 CN10 pin 14
+ PB7 CN7 pin 21
+ TXD: PA10 CN9 pin 3, CN10 pin 33
+ PB6 CN5 pin 3, CN10 pin 17
+
+ NOTE: You may need to edit the include/board.h to select different USART1
+ pin selections.
+
+TTL to RS-232 converter connection::
+
+ Nucleo CN10 STM32F429ZI
+ ----------- ------------
+ Pin 21 PA9 USART1_RX *Warning you make need to reverse RX/TX on
+ Pin 33 PA10 USART1_TX some RS-232 converters
+ Pin 20 GND
+ Pin 8 U5V
+
+To configure USART1 as the console::
+
+ CONFIG_STM32_USART1=y
+ CONFIG_USART1_SERIALDRIVER=y
+ CONFIG_USART1_SERIAL_CONSOLE=y
+ CONFIG_USART1_RXBUFSIZE=256
+ CONFIG_USART1_TXBUFSIZE=256
+ CONFIG_USART1_BAUD=115200
+ CONFIG_USART1_BITS=8
+ CONFIG_USART1_PARITY=0
+ CONFIG_USART1_2STOP=0
+
+USART2
+------
+
+Pins and Connectors::
+
+ RXD: PA3 CN9 pin 1 (See SB13, 14, 62, 63). CN10 pin 37
+ PD6
+ TXD: PA2 CN9 pin 2(See SB13, 14, 62, 63). CN10 pin 35
+ PD5
+
+ UART2 is the default in all of these configurations.
+
+TTL to RS-232 converter connection::
+
+ Nucleo CN9 STM32F429ZI
+ ----------- ------------
+ Pin 1 PA3 USART2_RX *Warning you make need to reverse RX/TX on
+ Pin 2 PA2 USART2_TX some RS-232 converters
+
+Solder Bridges. This configuration requires:
+
+- SB62 and SB63 Closed: PA2 and PA3 on STM32 MCU are connected to D1 and D0
+ (pin 7 and pin 8) on Arduino connector CN9 and ST Morpho connector CN10
+ as USART signals. Thus SB13 and SB14 should be OFF.
+
+- SB13 and SB14 Open: PA2 and PA3 on STM32F103C8T6 (ST-LINK MCU) are
+ disconnected to PA3 and PA2 on STM32 MCU.
+
+To configure USART2 as the console::
+
+ CONFIG_STM32_USART2=y
+ CONFIG_USART2_SERIALDRIVER=y
+ CONFIG_USART2_SERIAL_CONSOLE=y
+ CONFIG_USART2_RXBUFSIZE=256
+ CONFIG_USART2_TXBUFSIZE=256
+ CONFIG_USART2_BAUD=115200
+ CONFIG_USART2_BITS=8
+ CONFIG_USART2_PARITY=0
+ CONFIG_USART2_2STOP=0
+
+USART6
+------
+
+Pins and Connectors::
+
+ RXD: PC7 CN5 pin2, CN10 pin 19
+ PA12 CN10, pin 12
+ TXD: PC6 CN10, pin 4
+ PA11 CN10, pin 14
+
+To configure USART6 as the console::
+
+ CONFIG_STM32_USART6=y
+ CONFIG_USART6_SERIALDRIVER=y
+ CONFIG_USART6_SERIAL_CONSOLE=y
+ CONFIG_USART6_RXBUFSIZE=256
+ CONFIG_USART6_TXBUFSIZE=256
+ CONFIG_USART6_BAUD=115200
+ CONFIG_USART6_BITS=8
+ CONFIG_USART6_PARITY=0
+ CONFIG_USART6_2STOP=0
+
+Virtual COM Port
+----------------
+
+Yet another option is to use UART2 and the USB virtual COM port. This
+option may be more convenient for long term development, but is painful
+to use during board bring-up.
+
+Solder Bridges. This configuration requires:
+
+- SB62 and SB63 Open: PA2 and PA3 on STM32 MCU are disconnected to D1
+ and D0 (pin 7 and pin 8) on Arduino connector CN9 and ST Morpho
+ connector CN10.
+
+- SB13 and SB14 Closed: PA2 and PA3 on STM32F103C8T6 (ST-LINK MCU) are
+ connected to PA3 and PA2 on STM32 MCU to have USART communication
+ between them. Thus SB61, SB62 and SB63 should be OFF.
+
+Configuring USART2 is the same as given above.
+
+Question: What BAUD should be configure to interface with the Virtual
+COM port? 115200 8N1?
+
+Default:
+As shipped, SB62 and SB63 are open and SB13 and SB14 closed, so the
+virtual COM port is enabled.
+
+Configurations
+==============
+
+trace
+---
+
+Configures the trace located at apps/system/trace for the
+Nucleo-F429ZI board. The Configuration enables the serial interfaces
+on UART2. Support for builtin applications is enabled, and selected
+application trace.
+
+NOTES:
+
+1. This configuration uses the mconf-based configuration tool. To
+ change this configuration using that tool, you should:
+
+ a. Build and install the kconfig-mconf tool. See nuttx/README.txt
+ see additional README.txt files in the NuttX tools repository.
+
+ b. Execute 'make menuconfig' in nuttx/ in order to start the
+ reconfiguration process.
diff --git
a/content/docs/latest/_sources/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.rst.txt
b/content/docs/latest/_sources/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.rst.txt
index c7e25d9ad..000e07c9f 100644
---
a/content/docs/latest/_sources/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.rst.txt
+++
b/content/docs/latest/_sources/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.rst.txt
@@ -614,7 +614,7 @@ NSH commands::
Get the ip address assigned to eth0 and convert to hexadecimal, for example
192.168.1.2
becomes 0xC0A80102, than configure CONFIG_NETINIT_IPADDR and
CONFIG_EXAMPLES_TELNETD_IPADDR,
-also configure the router address, in this example it woukd be 0xC0A80101.
After theses changes
+also configure the router address, in this example it would be 0xC0A80101.
After these changes
rebuild and load the new firmware on your board::
nsh> mount -t procfs /proc
diff --git a/content/docs/latest/_sources/platforms/avr/atmega/index.rst.txt
b/content/docs/latest/_sources/platforms/avr/atmega/index.rst.txt
index 8151414c5..f9518c911 100644
--- a/content/docs/latest/_sources/platforms/avr/atmega/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/avr/atmega/index.rst.txt
@@ -34,7 +34,7 @@ AVR ATMega2560
--------------
Extension of the AVR architecture to support the
-ATMega2560 and specifi support for the Arduion MEGA2560 board were
+ATMega2560 and specific support for the Arduion MEGA2560 board were
contributed by Dimitry Kloper and first released in NuttX-7.14.
diff --git
a/content/docs/latest/_sources/platforms/x86_64/intel64/boards/qemu-intel64/index.rst.txt
b/content/docs/latest/_sources/platforms/x86_64/intel64/boards/qemu-intel64/index.rst.txt
index 2a1b6519a..c2e900415 100644
---
a/content/docs/latest/_sources/platforms/x86_64/intel64/boards/qemu-intel64/index.rst.txt
+++
b/content/docs/latest/_sources/platforms/x86_64/intel64/boards/qemu-intel64/index.rst.txt
@@ -181,6 +181,11 @@ Basic command to run the image without additional PCI
devices attached::
qemu-system-x86_64 -m 2G -cpu host -smp 4 -enable-kvm \
-kernel nuttx -nographic -serial mon:stdio
+Command to run the image with some xHCI devices attached::
+
+ qemu-system-x86_64 -m 4G -smp 4 -cpu host -enable-kvm \
+ -kernel nuttx -serial mon:stdio -chardev pty,id=ch1 \
+ -device qemu-xhci -device usb-mouse -device usb-kbd
knsh_romfs
----------
diff --git a/content/docs/latest/_sources/reference/os/mutex.rst.txt
b/content/docs/latest/_sources/reference/os/mutex.rst.txt
index e1e214c66..6bbb206be 100644
--- a/content/docs/latest/_sources/reference/os/mutex.rst.txt
+++ b/content/docs/latest/_sources/reference/os/mutex.rst.txt
@@ -108,7 +108,7 @@ Api description
:param mutex: mutex descriptor.
:return:
- if mutex is locked will return `ture`. if not will return `false`
+ if mutex is locked will return `true`. if not will return `false`
.. c:function:: void nxmutex_unlock(FAR mutex_t *mutex)
diff --git a/content/docs/latest/applications/examples/camera/index.html
b/content/docs/latest/applications/examples/camera/index.html
index 9fd406802..b80a835da 100644
--- a/content/docs/latest/applications/examples/camera/index.html
+++ b/content/docs/latest/applications/examples/camera/index.html
@@ -386,7 +386,7 @@
the command is as below.:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> camera ([-jpg]) ([capture num])
--jpg : this option is set for storing JPEG file into a strage.
+-jpg : this option is set for storing JPEG file into a storage.
: If this option isn't set capturing raw RGB565 data in a file.
: raw RGB565 is default.
diff --git a/content/docs/latest/applications/graphics/nxwm/cnxconsole.html
b/content/docs/latest/applications/graphics/nxwm/cnxconsole.html
index 07fe531e3..318b655ee 100644
--- a/content/docs/latest/applications/graphics/nxwm/cnxconsole.html
+++ b/content/docs/latest/applications/graphics/nxwm/cnxconsole.html
@@ -331,7 +331,7 @@ NxConsole gets its keyboard input.</p></li>
Almost everything said here applies to mouse/touchscreen input as well. If we
were to replace the names keyboard to mouse, kbdin to mousein, etc. you have a
pretty good description of how mouse/touchscreen input works.</p>
-<p>The mouse/touchscreen input is a little simpler, however: The main
simplication
+<p>The mouse/touchscreen input is a little simpler, however: The main
simplification
is that the additional complexities of the NxConsole and its special input
device
do not apply. Mouse/touchscreen input as always steered to widgets when the
callback is received in <code class="docutils literal notranslate"><span
class="pre">CCallback::newMouseEvent</span></code> by an unconditional call to
diff --git a/content/docs/latest/components/drivers/special/index.html
b/content/docs/latest/components/drivers/special/index.html
index 56d8a88ee..56fb9fdcc 100644
--- a/content/docs/latest/components/drivers/special/index.html
+++ b/content/docs/latest/components/drivers/special/index.html
@@ -434,6 +434,7 @@ and thus expose them to applications.</p>
<li class="toctree-l3"><a class="reference internal"
href="pci/index.html#intel-igc">Intel igc</a></li>
<li class="toctree-l3"><a class="reference internal"
href="pci/index.html#kvaser-pci-can-card">Kvaser PCI CAN card</a></li>
<li class="toctree-l3"><a class="reference internal"
href="pci/index.html#ctucanfd-pci-can-card">CTUCANFD PCI CAN card</a></li>
+<li class="toctree-l3"><a class="reference internal"
href="pci/index.html#xhci-over-pci">xHCI over PCI</a></li>
</ul>
</li>
</ul>
diff --git a/content/docs/latest/components/drivers/special/pci/index.html
b/content/docs/latest/components/drivers/special/pci/index.html
index a86f07d46..1c7e0fb21 100644
--- a/content/docs/latest/components/drivers/special/pci/index.html
+++ b/content/docs/latest/components/drivers/special/pci/index.html
@@ -320,6 +320,19 @@ sudo<span class="w"> </span>ip<span class="w">
</span>link<span class="w"> </spa
</pre></div>
</div>
</section>
+<section id="xhci-over-pci">
+<h3>xHCI over PCI<a class="headerlink" href="#xhci-over-pci" title="Permalink
to this heading"></a></h3>
+<p>xHCI support was tested on x86_64 target, both on QEMU and real
hardware.</p>
+<p>Known issues with this driver:</p>
+<ul class="simple">
+<li><p>Currently only USB2.0 is supported, there is no USB3.0 support in NuttX
yet.</p></li>
+<li><p>USB HUB devices not supported yet</p></li>
+</ul>
+<p>To enable xHCI support on QEMU, we have to add <code class="docutils
literal notranslate"><span class="pre">-device</span> <span
class="pre">qemu-xhci</span></code> argument.
+All supported USB devices in QEMU can be found in
+<a class="reference external"
href="https://qemu-project.gitlab.io/qemu/system/devices/usb.html";>QEMU
documentation</a>,
+but not all classes are supported in NuttX.</p>
+</section>
</section>
</section>
diff --git a/content/docs/latest/components/drivers/thermal/index.html
b/content/docs/latest/components/drivers/thermal/index.html
index f1501d161..c3f1914e2 100644
--- a/content/docs/latest/components/drivers/thermal/index.html
+++ b/content/docs/latest/components/drivers/thermal/index.html
@@ -231,7 +231,7 @@
</dd>
</dl>
</li>
-<li><p>ProcFS node supported, used for debugging, and we can get the binding
info between “Zone”, “Cooling Decice”, “Trip” and “Governor”, temperature value
and cooling state; (for example, “Zone Device”(temperature sensor): <code
class="docutils literal notranslate"><span
class="pre">/proc/thermal/cpu_thermal</span></code>), and write 0 or 1 to turn
off or on the “Zone Device”;</p></li>
+<li><p>ProcFS node supported, used for debugging, and we can get the binding
info between “Zone”, “Cooling Device”, “Trip” and “Governor”, temperature value
and cooling state; (for example, “Zone Device”(temperature sensor): <code
class="docutils literal notranslate"><span
class="pre">/proc/thermal/cpu_thermal</span></code>), and write 0 or 1 to turn
off or on the “Zone Device”;</p></li>
</ol>
</section>
<section id="device-driver">
diff --git a/content/docs/latest/components/filesystem/mnemofs.html
b/content/docs/latest/components/filesystem/mnemofs.html
index b0b6f0f02..d16a0b317 100644
--- a/content/docs/latest/components/filesystem/mnemofs.html
+++ b/content/docs/latest/components/filesystem/mnemofs.html
@@ -347,7 +347,7 @@ the journal. Each log in journal is followed by a checksum
to verify if all
of it was written properly. This helps in making it power loss resilient.</p>
<p>The journal, when combined with CoW, plays another important role. In pure
CoW, any update to a CTZ file will result in it having a new location. This
-new location wil need to be updated in the parent, which itself will have a
+new location will need to be updated in the parent, which itself will have a
new location after the update, and so on till it reaches the root. The
journal stops this propagation immediately. When the journal is full above
a certain limit, it will flush, and apply all of these changes to the FS
diff --git a/content/docs/latest/components/filesystem/tmpfs.html
b/content/docs/latest/components/filesystem/tmpfs.html
index 759eab6a2..8159ca246 100644
--- a/content/docs/latest/components/filesystem/tmpfs.html
+++ b/content/docs/latest/components/filesystem/tmpfs.html
@@ -223,7 +223,7 @@
<section id="tmpfs">
<h1>TMPFS<a class="headerlink" href="#tmpfs" title="Permalink to this
heading"></a></h1>
-<p>NuttX TMPFS file system is a tiny dyamic RAM based file system.</p>
+<p>NuttX TMPFS file system is a tiny dynamic RAM based file system.</p>
<p>It can be enabled by adding <code class="docutils literal
notranslate"><span class="pre">CONFIG_FS_TMPFS=y</span></code> to the
configuration at build time.</p>
<p>At runtime, simply use <code class="docutils literal notranslate"><span
class="pre">mount</span> <span class="pre">-t</span> <span
class="pre">tmpfs</span> <span class="pre">/tmp</span></code> to have a <code
class="docutils literal notranslate"><span class="pre">/tmp</span></code>
folder backed by TMPFS, then files and folders can be created under that
folder.</p>
<p>Be aware that TMPFS is backed by kernel memory thus don’t expect to store
big files on it and its size is limited by free kernel memory.</p>
diff --git a/content/docs/latest/components/libs/libc/index.html
b/content/docs/latest/components/libs/libc/index.html
index fa47cee34..98b87297e 100644
--- a/content/docs/latest/components/libs/libc/index.html
+++ b/content/docs/latest/components/libs/libc/index.html
@@ -288,7 +288,7 @@ Field 5 - N+5: The type of each of the N formal parameters
of the function
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>type name:
For all simpler types
formal type | actual type:
- For array types where the form of the formal (eg. int parm[2])
+ For array types where the form of the formal (eg. int param[2])
differs from the type of actual passed parameter (eg. int*). This
is necessary because you cannot do simple casts to array types.
formal type | union member actual type | union member fieldname:
diff --git a/content/docs/latest/components/nxgraphics/appendix.html
b/content/docs/latest/components/nxgraphics/appendix.html
index 258fad76e..8f7b81587 100644
--- a/content/docs/latest/components/nxgraphics/appendix.html
+++ b/content/docs/latest/components/nxgraphics/appendix.html
@@ -907,11 +907,11 @@ in the <code class="docutils literal notranslate"><span
class="pre"><NuttX-Di
<td><p>NO</p></td>
</tr>
<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">nx_setvisibility()</span></code></p></td>
-<td><p>Exercized using Twm4Nx</p></td>
+<td><p>Exercised using Twm4Nx</p></td>
<td><p>YES, Informally</p></td>
</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">nx_ishidden()</span></code></p></td>
-<td><p>Exercized using Twm4Nx</p></td>
+<td><p>Exercised using Twm4Nx</p></td>
<td><p>YES, Informally</p></td>
</tr>
<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">nx_fill()</span></code></p></td>
@@ -1007,11 +1007,11 @@ in the <code class="docutils literal notranslate"><span
class="pre"><NuttX-Di
<td><p>NO</p></td>
</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">nxtk_setvisibility()</span></code></p></td>
-<td><p>Exercized using Twm4Nx</p></td>
+<td><p>Exercised using Twm4Nx</p></td>
<td><p>YES, informally</p></td>
</tr>
<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">nxtk_ishidden()</span></code></p></td>
-<td><p>Exercized using Twm4Nx</p></td>
+<td><p>Exercised using Twm4Nx</p></td>
<td><p>YES, informally</p></td>
</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">nxtk_fillwindow()</span></code></p></td>
diff --git a/content/docs/latest/components/syscall.html
b/content/docs/latest/components/syscall.html
index 3f1307495..084d13fd5 100644
--- a/content/docs/latest/components/syscall.html
+++ b/content/docs/latest/components/syscall.html
@@ -303,7 +303,7 @@ See note below about variadic functions</p></li>
<p>For all simpler types</p>
</li>
<li><p>formal type | actual type:</p>
-<p>For array types where the form of the formal (eg. <code class="docutils
literal notranslate"><span class="pre">int</span> <span
class="pre">parm[2]</span></code>)
+<p>For array types where the form of the formal (eg. <code class="docutils
literal notranslate"><span class="pre">int</span> <span
class="pre">param[2]</span></code>)
differs from the type of actual passed parameter (eg. <code class="docutils
literal notranslate"><span class="pre">int*</span></code>).
This is necessary because you cannot do simple casts to array types.</p>
</li>
diff --git a/content/docs/latest/contributing/coding_style.html
b/content/docs/latest/contributing/coding_style.html
index 5580db490..42e757792 100644
--- a/content/docs/latest/contributing/coding_style.html
+++ b/content/docs/latest/contributing/coding_style.html
@@ -1455,8 +1455,8 @@ specific directories must be compatible with C89.</p></li>
defining a structure within a type definition is discouraged. It is
preferred that the structure definition and the type definition be
separate definitions. In general, the NuttX coding style discourages
-any <code class="docutils literal notranslate"><span
class="pre">typdef</span></code>-ing of structures; normally the full structure
name is
-used as types throughout the code. The reason for this is that is
+any <code class="docutils literal notranslate"><span
class="pre">typedef</span></code>-ing of structures; normally the full
structure name
+is used as types throughout the code. The reason for this is that is
structure pointers may be forward referenced in header files without
having to include the file the provides the type definition. This
greatly reduces header file coupling.</p></li>
diff --git a/content/docs/latest/debugging/coresight.html
b/content/docs/latest/debugging/coresight.html
index 3db466e9e..39afcf1e1 100644
--- a/content/docs/latest/debugging/coresight.html
+++ b/content/docs/latest/debugging/coresight.html
@@ -254,7 +254,7 @@ register with the framework for as long as they use the
right APIs:</p>
<p><code class="docutils literal notranslate"><span class="pre">struct</span>
<span class="pre">coresight_desc</span> <span class="pre">*desc</span></code>
describes the type of current coresight device
and where it connects to. When all the coresight devices are registered,
-devices throught the tracing stream path can be enablea by calling:</p>
+devices through the tracing stream path can be enabled by calling:</p>
<dl class="c function">
<dt class="sig sig-object c" id="c.coresight_enable">
<span class="kt"><span class="pre">int</span></span><span class="w">
</span><span class="sig-name descname"><span class="n"><span
class="pre">coresight_enable</span></span></span><span
class="sig-paren">(</span><span class="pre">FAR</span><span class="w">
</span><span class="k"><span class="pre">struct</span></span><span class="w">
</span><span class="n"><span class="pre">coresight_dev_s</span></span><span
class="w"> </span><span class="p"><span class="pre">*</span></span><span
class="n" [...]
diff --git a/content/docs/latest/guides/port_drivers_to_stm32f7.html
b/content/docs/latest/guides/port_drivers_to_stm32f7.html
index ded15dd66..0dad80edc 100644
--- a/content/docs/latest/guides/port_drivers_to_stm32f7.html
+++ b/content/docs/latest/guides/port_drivers_to_stm32f7.html
@@ -459,7 +459,7 @@ to the D-Cache line size.</p></li>
</ul>
<p>The following definitions were added to support aligning the sizes of
the buffers to the Cortex-M7 D-Cache line size:</p>
-<div class="highlight-c notranslate"><div
class="highlight"><pre><span></span><span class="w"> </span><span class="cm">/*
Buffers use fro DMA access must begin on an address aligned with the</span>
+<div class="highlight-c notranslate"><div
class="highlight"><pre><span></span><span class="cm">/* Buffers used for DMA
access must begin on an address aligned with the</span>
<span class="cm">* D-Cache line and must be an even multiple of the D-Cache
line size.</span>
<span class="cm">* These size/alignment requirements are necessary so that
D-Cache flush</span>
<span class="cm">* and invalidate operations will not have any additional
effects.</span>
diff --git a/content/docs/latest/guides/pysimcoder.html
b/content/docs/latest/guides/pysimcoder.html
index 846b8e872..bcd7255b2 100644
--- a/content/docs/latest/guides/pysimcoder.html
+++ b/content/docs/latest/guides/pysimcoder.html
@@ -424,7 +424,7 @@ designed with pysimCoder.</p>
<p>After running pysimCoder, separate blocks can be selected from the library
menu on the left hand side. The menu contains
several libraries, NuttX specific blocks can be found in library “NuttX”. It
is also possible to use blocks from other
libraries like “input”, “output”, “math” and so on. Several blocks can have
specific parameter options and various number
-of inputs/outputs. Double left click on the block openes parameter settings
while single right click on the block leads
+of inputs/outputs. Double left click on the block opens parameter settings
while single right click on the block leads
to number of inputs/outputs setup. The pysimCoder interface can be seen in the
picture below.</p>
<figure class="align-center" id="id1">
<a class="reference internal image-reference"
href="../_images/interface.png"><img alt="../_images/interface.png"
src="../_images/interface.png" style="width: 100%;" /></a>
diff --git a/content/docs/latest/implementation/device_drivers.html
b/content/docs/latest/implementation/device_drivers.html
index 5c22e4751..ab0dd73d8 100644
--- a/content/docs/latest/implementation/device_drivers.html
+++ b/content/docs/latest/implementation/device_drivers.html
@@ -239,7 +239,7 @@ possible to build any meaningless application with it.</p>
<h3>The I2C Tool<a class="headerlink" href="#the-i2c-tool" title="Permalink to
this heading"></a></h3>
<p>Of course, like most rules, there are lots of violations. I2C is another
bus and
the the I2C “driver” is another transport similar in many ways to SPI. For I2C,
-there is an application at <code class="docutils literal notranslate"><span
class="pre">apps/system/i2c</span></code> alled the “I2C tool” that will allow
+there is an application at <code class="docutils literal notranslate"><span
class="pre">apps/system/i2c</span></code> called the “I2C tool” that will allow
you access I2C devices from the command line. This is not really just a test
tool
and not a real part of an application.</p>
<p>And there is a fundamental flaw in the I2C tool: it uses NuttX internal
interfaces
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index f5f239dcd..2ac08f864 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -181,7 +181,7 @@ standards. Additional standard APIs from Unix and other
common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such
as fork()).</p>
-<p>Last Updated: 15 May 25 at 00:27</p>
+<p>Last Updated: 16 May 25 at 00:28</p>
<div class="toctree-wrapper compound">
<p class="caption" role="heading"><span class="caption-text">Table of
Contents</span></p>
<ul class="current">
diff --git a/content/docs/latest/introduction/resources.html
b/content/docs/latest/introduction/resources.html
index 9887971cc..3dd0635aa 100644
--- a/content/docs/latest/introduction/resources.html
+++ b/content/docs/latest/introduction/resources.html
@@ -1826,7 +1826,7 @@ can’t tell you which packages you should or should not
download).</p>
tools. There are, however, complexities in doing that because those tools
depend on the shell environment and use DLLs that are not found (at least
not without the correct setup).</p>
-<p>Host Compiler: I use the MingGW GCC compiler which can be downloaded from
+<p>Host Compiler: I use the MinGW GCC compiler which can be downloaded from
<a class="reference external"
href="http://www.mingw.org/";>http://www.mingw.org/</a>. If you are using
GNUWin32, then it is recommended
the you not install the optional MSYS components as there may be conflicts.</p>
<p>Kconfig-frontends: See the section entitled “NuttX Configuration Tool
diff --git a/content/docs/latest/objects.inv b/content/docs/latest/objects.inv
index 7719d5c67..8ed94c64a 100644
Binary files a/content/docs/latest/objects.inv and
b/content/docs/latest/objects.inv differ
diff --git
a/content/docs/latest/platforms/arm/kinetis/boards/twr-k60n512/index.html
b/content/docs/latest/platforms/arm/kinetis/boards/twr-k60n512/index.html
index 9f3b8d028..232546356 100644
--- a/content/docs/latest/platforms/arm/kinetis/boards/twr-k60n512/index.html
+++ b/content/docs/latest/platforms/arm/kinetis/boards/twr-k60n512/index.html
@@ -755,7 +755,7 @@ Where <subdir> is one of the following:
CONFIG_MMCSD_SDIO=y : Use the SDIO-based MMC/SD driver
CONFIG_MMCSD_NSLOTS=1 : One MMC/SD slot
- CONFIG_FAT=y : Eable FAT file system
+ CONFIG_FAT=y : Enable FAT file system
CONFIG_FAT_LCNAMES=y : FAT lower case name support
CONFIG_FAT_LFN=y : FAT long file name support
CONFIG_FAT_MAXFNAME=32 : Maximum length of a long file name
diff --git
a/content/docs/latest/platforms/arm/kinetis/boards/twr-k64f120m/index.html
b/content/docs/latest/platforms/arm/kinetis/boards/twr-k64f120m/index.html
index 753b8de6a..4a1bf9fd1 100644
--- a/content/docs/latest/platforms/arm/kinetis/boards/twr-k64f120m/index.html
+++ b/content/docs/latest/platforms/arm/kinetis/boards/twr-k64f120m/index.html
@@ -855,7 +855,7 @@ Where <subdir> is one of the following:
CONFIG_MMCSD_SDIO=y : Use the SDIO-based MMC/SD driver
CONFIG_MMCSD_NSLOTS=1 : One MMC/SD slot
- CONFIG_FAT=y : Eable FAT file system
+ CONFIG_FAT=y : Enable FAT file system
CONFIG_FAT_LCNAMES=n : FAT lower case name support
CONFIG_FAT_LFN=y : FAT long file name support
CONFIG_FAT_MAXFNAME=32 : Maximum length of a long file name
diff --git
a/content/docs/latest/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.html
b/content/docs/latest/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.html
index a641be5e8..d8ee0d1ff 100644
---
a/content/docs/latest/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.html
+++
b/content/docs/latest/platforms/arm/lpc31xx/boards/olimex-lpc-h3131/index.html
@@ -1088,7 +1088,7 @@ may outgrow the available SRAM; even if the code can be
loaded into
SRAM, it may still fail at runtime due to insufficient memory.</p>
<p>Since SDRAM is not currently working (see above) and NAND support
has not be integrated, the only really option is to put NSH “on a
-diet” to reduct the size so that it will fit into memory.</p>
+diet” to reduce the size so that it will fit into memory.</p>
<p>Here are a few things you can do:</p>
<ol class="arabic simple">
<li><p>Try using smaller stack sizes.</p></li>
diff --git a/content/docs/latest/platforms/arm/nrf52/ieee802154.html
b/content/docs/latest/platforms/arm/nrf52/ieee802154.html
index d2682e58f..24079553d 100644
--- a/content/docs/latest/platforms/arm/nrf52/ieee802154.html
+++ b/content/docs/latest/platforms/arm/nrf52/ieee802154.html
@@ -310,7 +310,7 @@ Help with development and testing will be appreciated ;)</p>
<li><p>slotted CSMA-CA</p></li>
<li><p>GTS</p></li>
</ul>
-<p>Fetures not implemented:</p>
+<p>Features not implemented:</p>
<ul class="simple">
<li><p>enhanced ACK (Enh-ACK)</p></li>
<li><p>enhanced beacon</p></li>
@@ -323,7 +323,7 @@ Help with development and testing will be appreciated ;)</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span
class="pre">RADIO</span></code> - used for radio operations</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">TIMER0</span></code> - used as high resolution timer for ACK, IFS
and other radio delays</p></li>
-<li><p><code class="docutils literal notranslate"><span
class="pre">RTC0</span></code> - if superframe support is enabled, used as low
power timer to hande
+<li><p><code class="docutils literal notranslate"><span
class="pre">RTC0</span></code> - if superframe support is enabled, used as low
power timer to handle
superframe events</p></li>
</ul>
</section>
diff --git a/content/docs/latest/platforms/arm/s32k1xx/index.html
b/content/docs/latest/platforms/arm/s32k1xx/index.html
index 7a78895b7..41ec57f6a 100644
--- a/content/docs/latest/platforms/arm/s32k1xx/index.html
+++ b/content/docs/latest/platforms/arm/s32k1xx/index.html
@@ -455,7 +455,7 @@ Albeit the current implementation has some limitations:</p>
<ul class="simple">
<li><p>Max I2C speed of 400KHz</p></li>
<li><p>Max transfer of 12 bytes (Could be extended by utilizing EDMA)</p></li>
-<li><p>No abort on NACK reception, shifter simplies continues on</p></li>
+<li><p>No abort on NACK reception, shifter simply continues</p></li>
<li><p>No multi-master support</p></li>
<li><p>No restart support</p></li>
</ul>
diff --git
a/content/docs/latest/platforms/arm/samd2l2/boards/samd20-xplained/index.html
b/content/docs/latest/platforms/arm/samd2l2/boards/samd20-xplained/index.html
index 00cd2f686..d01fce2cb 100644
---
a/content/docs/latest/platforms/arm/samd2l2/boards/samd20-xplained/index.html
+++
b/content/docs/latest/platforms/arm/samd2l2/boards/samd20-xplained/index.html
@@ -1128,7 +1128,7 @@ Configuration sub-directories
CONFIG_EXAMPLES_NXHELLO_BPP=1 : One bit per pixel
CONFIG_EXAMPLES_NXHELLO_EXTERNINIT=y : Special initialization is
required.
- * The OLED is monochrome so the only "colors" are blacka nd
white.
+ * The OLED is monochrome so the only "colors" are black and
white.
The default "colors" will give you while text on a black
background.
You can override the faults it you want black text on a while
background.
diff --git
a/content/docs/latest/platforms/arm/samd2l2/boards/samd21-xplained/index.html
b/content/docs/latest/platforms/arm/samd2l2/boards/samd21-xplained/index.html
index 4ba5ed454..17ec329c4 100644
---
a/content/docs/latest/platforms/arm/samd2l2/boards/samd21-xplained/index.html
+++
b/content/docs/latest/platforms/arm/samd2l2/boards/samd21-xplained/index.html
@@ -1001,7 +1001,7 @@ Configuration sub-directories
CONFIG_EXAMPLES_NXHELLO_BPP=1 : One bit per pixel
CONFIG_EXAMPLES_NXHELLO_EXTERNINIT=y : Special initialization is
required.
- * The OLED is monochrome so the only "colors" are blacka nd
white.
+ * The OLED is monochrome so the only "colors" are black and
white.
The default "colors" will give you while text on a black
background.
You can override the faults it you want black text on a while
background.
diff --git
a/content/docs/latest/platforms/arm/stm32f4/boards/nucleo-f429zi/index.html
b/content/docs/latest/platforms/arm/stm32f4/boards/nucleo-f429zi/index.html
index 6b555ceb9..364036ca7 100644
--- a/content/docs/latest/platforms/arm/stm32f4/boards/nucleo-f429zi/index.html
+++ b/content/docs/latest/platforms/arm/stm32f4/boards/nucleo-f429zi/index.html
@@ -299,6 +299,206 @@
<h1>ST Nucleo F429ZI<a class="headerlink" href="#st-nucleo-f429zi"
title="Permalink to this heading"></a></h1>
<p class="tags"><span>Tags: </span><a class="sd-sphinx-override sd-badge
sd-bg-secondary sd-bg-text-secondary reference internal"
href="../../../../../_tags/chip-stm32.html"><span
class="doc">chip:stm32</span></a><span> </span><a class="sd-sphinx-override
sd-badge sd-bg-secondary sd-bg-text-secondary reference internal"
href="../../../../../_tags/chip-stm32f4.html"><span
class="doc">chip:stm32f4</span></a><span> </span><a class="sd-sphinx-override
sd-badge sd-bg-secondary sd-bg-text-seco [...]
<p>The Nucleo F429ZI is a member of the Nucleo-144 board family.</p>
+<p>This page discusses issues unique to NuttX configurations for the ST
+Nucleo F429ZI board from ST Micro. See</p>
+<blockquote>
+<div><p><a class="reference external"
href="http://www.st.com/en/evaluation-tools/nucleo-f429zi.html";>http://www.st.com/en/evaluation-tools/nucleo-f429zi.html</a></p>
+</div></blockquote>
+<p>NucleoF429ZI:</p>
+<ul class="simple">
+<li><p>Microprocessor: 32-bit ARM Cortex M4 with 180 MHz max CPU
frequency</p></li>
+<li><p>Memory: 2 MB Flash and 256+4 KB SRAM including 64-Kbyte of core coupled
memory</p></li>
+<li><p>ADC: 3x12-bit ADC with 24 channels</p></li>
+<li><p>DMA: 16-stream DMA controller with FIFOs and burst support</p></li>
+<li><p>Timers: Up to 17 timers: up to 12 16-bit, 2 32-bit timers, two
+watchdog timers, and a SysTick timer</p></li>
+<li><p>GPIO: Up to 168 I/O ports with interrupt capability</p></li>
+<li><p>I2C: Up to 3 I2C interfaces</p></li>
+<li><p>USARTs: Up to 4 USARTs</p></li>
+<li><p>SPIs: Up to 6 SPIs (45 Mbit/s)</p></li>
+</ul>
+<dl class="simple">
+<dt>See:</dt><dd><p><a class="reference external"
href="https://www.st.com/en/microcontrollers-microprocessors/stm32f429zi.html";>https://www.st.com/en/microcontrollers-microprocessors/stm32f429zi.html</a></p>
+</dd>
+</dl>
+<section id="hardware">
+<h2>Hardware<a class="headerlink" href="#hardware" title="Permalink to this
heading"></a></h2>
+<section id="buttons">
+<h3>Buttons<a class="headerlink" href="#buttons" title="Permalink to this
heading"></a></h3>
+<p>B1 USER: the user button is connected to the I/O PC13 (pin 2) of the STM32
+microcontroller.</p>
+</section>
+<section id="leds">
+<h3>LEDs<a class="headerlink" href="#leds" title="Permalink to this
heading"></a></h3>
+<p>The Nucleo F410RB provide a single user LED, LD2. LD2
+is the green LED connected to Arduino signal D13 corresponding to MCU I/O
+PA5 (pin 21) or PB13 (pin 34) depending on the STM32target.</p>
+<ul class="simple">
+<li><p>When the I/O is HIGH value, the LED is on.</p></li>
+<li><p>When the I/O is LOW, the LED is off.</p></li>
+</ul>
+<p>These LEDs are not used by the board port unless CONFIG_ARCH_LEDS is
+defined. In that case, the usage by the board port is defined in
+include/board.h and src/sam_leds.c. The LEDs are used to encode OS-related
+events as follows when the red LED (PE24) is available:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>SYMBOL Meaning
LD2
+------------------- ----------------------- -----------
+LED_STARTED NuttX has been started OFF
+LED_HEAPALLOCATE Heap has been allocated OFF
+LED_IRQSENABLED Interrupts enabled OFF
+LED_STACKCREATED Idle stack created ON
+LED_INIRQ In an interrupt No change
+LED_SIGNAL In a signal handler No change
+LED_ASSERTION An assertion failed No change
+LED_PANIC The system has crashed Blinking
+LED_IDLE MCU is is sleep mode Not used
+</pre></div>
+</div>
+<p>Thus if LD2, NuttX has successfully booted and is, apparently, running
+normally. If LD2 is flashing at approximately 2Hz, then a fatal error
+has been detected and the system has halted.</p>
+</section>
+</section>
+<section id="serial-consoles">
+<h2>Serial Consoles<a class="headerlink" href="#serial-consoles"
title="Permalink to this heading"></a></h2>
+<section id="usart1">
+<h3>USART1<a class="headerlink" href="#usart1" title="Permalink to this
heading"></a></h3>
+<p>Pins and Connectors:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>RXD: PA11 CN10 pin 14
+ PB7 CN7 pin 21
+TXD: PA10 CN9 pin 3, CN10 pin 33
+ PB6 CN5 pin 3, CN10 pin 17
+
+NOTE: You may need to edit the include/board.h to select different USART1
+pin selections.
+</pre></div>
+</div>
+<p>TTL to RS-232 converter connection:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>Nucleo CN10 STM32F429ZI
+----------- ------------
+Pin 21 PA9 USART1_RX *Warning you make need to reverse RX/TX on
+Pin 33 PA10 USART1_TX some RS-232 converters
+Pin 20 GND
+Pin 8 U5V
+</pre></div>
+</div>
+<p>To configure USART1 as the console:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>CONFIG_STM32_USART1=y
+CONFIG_USART1_SERIALDRIVER=y
+CONFIG_USART1_SERIAL_CONSOLE=y
+CONFIG_USART1_RXBUFSIZE=256
+CONFIG_USART1_TXBUFSIZE=256
+CONFIG_USART1_BAUD=115200
+CONFIG_USART1_BITS=8
+CONFIG_USART1_PARITY=0
+CONFIG_USART1_2STOP=0
+</pre></div>
+</div>
+</section>
+<section id="usart2">
+<h3>USART2<a class="headerlink" href="#usart2" title="Permalink to this
heading"></a></h3>
+<p>Pins and Connectors:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>RXD: PA3 CN9 pin 1 (See SB13, 14, 62,
63). CN10 pin 37
+ PD6
+TXD: PA2 CN9 pin 2(See SB13, 14, 62, 63). CN10 pin 35
+ PD5
+
+UART2 is the default in all of these configurations.
+</pre></div>
+</div>
+<p>TTL to RS-232 converter connection:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>Nucleo CN9 STM32F429ZI
+----------- ------------
+Pin 1 PA3 USART2_RX *Warning you make need to reverse RX/TX on
+Pin 2 PA2 USART2_TX some RS-232 converters
+</pre></div>
+</div>
+<p>Solder Bridges. This configuration requires:</p>
+<ul class="simple">
+<li><p>SB62 and SB63 Closed: PA2 and PA3 on STM32 MCU are connected to D1 and
D0
+(pin 7 and pin 8) on Arduino connector CN9 and ST Morpho connector CN10
+as USART signals. Thus SB13 and SB14 should be OFF.</p></li>
+<li><p>SB13 and SB14 Open: PA2 and PA3 on STM32F103C8T6 (ST-LINK MCU) are
+disconnected to PA3 and PA2 on STM32 MCU.</p></li>
+</ul>
+<p>To configure USART2 as the console:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>CONFIG_STM32_USART2=y
+CONFIG_USART2_SERIALDRIVER=y
+CONFIG_USART2_SERIAL_CONSOLE=y
+CONFIG_USART2_RXBUFSIZE=256
+CONFIG_USART2_TXBUFSIZE=256
+CONFIG_USART2_BAUD=115200
+CONFIG_USART2_BITS=8
+CONFIG_USART2_PARITY=0
+CONFIG_USART2_2STOP=0
+</pre></div>
+</div>
+</section>
+<section id="usart6">
+<h3>USART6<a class="headerlink" href="#usart6" title="Permalink to this
heading"></a></h3>
+<p>Pins and Connectors:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>RXD: PC7 CN5 pin2, CN10 pin 19
+ PA12 CN10, pin 12
+TXD: PC6 CN10, pin 4
+ PA11 CN10, pin 14
+</pre></div>
+</div>
+<p>To configure USART6 as the console:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>CONFIG_STM32_USART6=y
+CONFIG_USART6_SERIALDRIVER=y
+CONFIG_USART6_SERIAL_CONSOLE=y
+CONFIG_USART6_RXBUFSIZE=256
+CONFIG_USART6_TXBUFSIZE=256
+CONFIG_USART6_BAUD=115200
+CONFIG_USART6_BITS=8
+CONFIG_USART6_PARITY=0
+CONFIG_USART6_2STOP=0
+</pre></div>
+</div>
+</section>
+<section id="virtual-com-port">
+<h3>Virtual COM Port<a class="headerlink" href="#virtual-com-port"
title="Permalink to this heading"></a></h3>
+<p>Yet another option is to use UART2 and the USB virtual COM port. This
+option may be more convenient for long term development, but is painful
+to use during board bring-up.</p>
+<p>Solder Bridges. This configuration requires:</p>
+<ul class="simple">
+<li><p>SB62 and SB63 Open: PA2 and PA3 on STM32 MCU are disconnected to D1
+and D0 (pin 7 and pin 8) on Arduino connector CN9 and ST Morpho
+connector CN10.</p></li>
+<li><p>SB13 and SB14 Closed: PA2 and PA3 on STM32F103C8T6 (ST-LINK MCU) are
+connected to PA3 and PA2 on STM32 MCU to have USART communication
+between them. Thus SB61, SB62 and SB63 should be OFF.</p></li>
+</ul>
+<p>Configuring USART2 is the same as given above.</p>
+<p>Question: What BAUD should be configure to interface with the Virtual
+COM port? 115200 8N1?</p>
+<p>Default:
+As shipped, SB62 and SB63 are open and SB13 and SB14 closed, so the
+virtual COM port is enabled.</p>
+</section>
+</section>
+<section id="configurations">
+<h2>Configurations<a class="headerlink" href="#configurations"
title="Permalink to this heading"></a></h2>
+<p>trace
+—</p>
+<p>Configures the trace located at apps/system/trace for the
+Nucleo-F429ZI board. The Configuration enables the serial interfaces
+on UART2. Support for builtin applications is enabled, and selected
+application trace.</p>
+<p>NOTES:</p>
+<ol class="arabic simple">
+<li><p>This configuration uses the mconf-based configuration tool. To
+change this configuration using that tool, you should:</p>
+<ol class="loweralpha simple">
+<li><p>Build and install the kconfig-mconf tool. See nuttx/README.txt
+see additional README.txt files in the NuttX tools repository.</p></li>
+<li><p>Execute ‘make menuconfig’ in nuttx/ in order to start the
+reconfiguration process.</p></li>
+</ol>
+</li>
+</ol>
+</section>
</section>
diff --git
a/content/docs/latest/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.html
b/content/docs/latest/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.html
index e55426255..03d58be63 100644
---
a/content/docs/latest/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.html
+++
b/content/docs/latest/platforms/arm/stm32f4/boards/stm32f401rc-rs485/index.html
@@ -989,7 +989,7 @@ nsh> ifcong
</div>
<p>Get the ip address assigned to eth0 and convert to hexadecimal, for example
192.168.1.2
becomes 0xC0A80102, than configure CONFIG_NETINIT_IPADDR and
CONFIG_EXAMPLES_TELNETD_IPADDR,
-also configure the router address, in this example it woukd be 0xC0A80101.
After theses changes
+also configure the router address, in this example it would be 0xC0A80101.
After these changes
rebuild and load the new firmware on your board:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> mount -t procfs /proc
nsh> telnetd
diff --git
a/content/docs/latest/platforms/avr/at90usb/boards/micropendous3/index.html
b/content/docs/latest/platforms/avr/at90usb/boards/micropendous3/index.html
index 4c12a77e2..f4ac020f0 100644
--- a/content/docs/latest/platforms/avr/at90usb/boards/micropendous3/index.html
+++ b/content/docs/latest/platforms/avr/at90usb/boards/micropendous3/index.html
@@ -204,7 +204,7 @@
<section id="micropendous3">
<h1>micropendous3<a class="headerlink" href="#micropendous3" title="Permalink
to this heading"></a></h1>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>README
-^^^^^
+^^^^^^
This is the README file for the port of NuttX to the Micropendous 3 board.
This board is develepmend by http://code.google.com/p/opendous/. The
@@ -546,9 +546,9 @@ Header File Installation
Build Notes:
- It may not necessary to have a built version of avr-lib; only header files
- are required. Bu if you choose to use the optimized libraru functions of
- the flowing point library, then you may have to build avr-lib from sources.
+ It may not be necessary to have a built version of avr-lib; only header files
+ are required. But if you choose to use the optimized library functions of
+ the floating point library, then you may have to build avr-lib from sources.
Below are instructions for building avr-lib from fresh sources:
1. Download the avr-libc package from:
diff --git
a/content/docs/latest/platforms/avr/at90usb/boards/teensy-2.0/index.html
b/content/docs/latest/platforms/avr/at90usb/boards/teensy-2.0/index.html
index 326508086..cbd6eff6f 100644
--- a/content/docs/latest/platforms/avr/at90usb/boards/teensy-2.0/index.html
+++ b/content/docs/latest/platforms/avr/at90usb/boards/teensy-2.0/index.html
@@ -555,9 +555,9 @@ Header File Installation
Build Notes:
- It may not necessary to have a built version of avr-lib; only header files
- are required. Bu if you choose to use the optimized libraru functions of
- the flowing point library, then you may have to build avr-lib from sources.
+ It may not be necessary to have a built version of avr-lib; only header files
+ are required. But if you choose to use the optimized library functions of
+ the floating point library, then you may have to build avr-lib from sources.
Below are instructions for building avr-lib from fresh sources:
1. Download the avr-libc package from:
diff --git a/content/docs/latest/platforms/avr/atmega/boards/amber/index.html
b/content/docs/latest/platforms/avr/atmega/boards/amber/index.html
index 3b00c1c05..25cf2edae 100644
--- a/content/docs/latest/platforms/avr/atmega/boards/amber/index.html
+++ b/content/docs/latest/platforms/avr/atmega/boards/amber/index.html
@@ -540,9 +540,9 @@ Header File Installation
Build Notes:
- It may not necessary to have a built version of avr-lib; only header files
- are required. Bu if you choose to use the optimized libraru functions of
- the flowing point library, then you may have to build avr-lib from sources.
+ It may not be necessary to have a built version of avr-lib; only header files
+ are required. But if you choose to use the optimized library functions of
+ the floating point library, then you may have to build avr-lib from sources.
Below are instructions for building avr-lib from fresh sources:
1. Download the avr-libc package from:
diff --git a/content/docs/latest/platforms/avr/atmega/index.html
b/content/docs/latest/platforms/avr/atmega/index.html
index 7492b5199..ec17ee56e 100644
--- a/content/docs/latest/platforms/avr/atmega/index.html
+++ b/content/docs/latest/platforms/avr/atmega/index.html
@@ -243,7 +243,7 @@ following features:</p>
<section id="avr-atmega2560">
<h2>AVR ATMega2560<a class="headerlink" href="#avr-atmega2560"
title="Permalink to this heading"></a></h2>
<p>Extension of the AVR architecture to support the
-ATMega2560 and specifi support for the Arduion MEGA2560 board were
+ATMega2560 and specific support for the Arduion MEGA2560 board were
contributed by Dimitry Kloper and first released in NuttX-7.14.</p>
<section id="clock-configuration">
<h3>Clock Configuration<a class="headerlink" href="#clock-configuration"
title="Permalink to this heading"></a></h3>
diff --git
a/content/docs/latest/platforms/x86_64/intel64/boards/qemu-intel64/index.html
b/content/docs/latest/platforms/x86_64/intel64/boards/qemu-intel64/index.html
index 1cbc233e0..e2bcfff6d 100644
---
a/content/docs/latest/platforms/x86_64/intel64/boards/qemu-intel64/index.html
+++
b/content/docs/latest/platforms/x86_64/intel64/boards/qemu-intel64/index.html
@@ -369,6 +369,12 @@ the default console on legacy UART0 port (base=0x3f8)</p>
-kernel nuttx -nographic -serial mon:stdio
</pre></div>
</div>
+<p>Command to run the image with some xHCI devices attached:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>qemu-system-x86_64 -m 4G -smp 4 -cpu host
-enable-kvm \
+-kernel nuttx -serial mon:stdio -chardev pty,id=ch1 \
+-device qemu-xhci -device usb-mouse -device usb-kbd
+</pre></div>
+</div>
</section>
<section id="knsh-romfs">
<h3>knsh_romfs<a class="headerlink" href="#knsh-romfs" title="Permalink to
this heading"></a></h3>
diff --git a/content/docs/latest/reference/os/mutex.html
b/content/docs/latest/reference/os/mutex.html
index d9b70c819..1259d1bbd 100644
--- a/content/docs/latest/reference/os/mutex.html
+++ b/content/docs/latest/reference/os/mutex.html
@@ -352,7 +352,7 @@ EAGAIN - The mutex is not available.</p>
</ul>
</dd>
<dt class="field-even">Returns<span class="colon">:</span></dt>
-<dd class="field-even"><p>if mutex is locked will return <cite>ture</cite>. if
not will return <cite>false</cite></p>
+<dd class="field-even"><p>if mutex is locked will return <cite>true</cite>. if
not will return <cite>false</cite></p>
</dd>
</dl>
</dd></dl>
diff --git a/content/docs/latest/searchindex.js
b/content/docs/latest/searchindex.js
index f927fc557..c3b3afdb9 100644
--- a/content/docs/latest/searchindex.js
+++ b/content/docs/latest/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["_tags/chip-a527", "_tags/chip-a64",
"_tags/chip-bcm2711", "_tags/chip-esp32", "_tags/chip-esp32a1s",
"_tags/chip-esp32picod4", "_tags/chip-esp32s2", "_tags/chip-esp32s3",
"_tags/chip-esp32wroom32", "_tags/chip-esp32wrover32", "_tags/chip-fpga",
"_tags/chip-imx8", "_tags/chip-imx93", "_tags/chip-nrf52",
"_tags/chip-nrf52832", "_tags/chip-nrf52840", "_tags/chip-nrf53",
"_tags/chip-nrf5340", "_tags/chip-nrf91", "_tags/chip-nrf9160",
"_tags/chip-rk3399", "_tags [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["_tags/chip-a527", "_tags/chip-a64",
"_tags/chip-bcm2711", "_tags/chip-esp32", "_tags/chip-esp32a1s",
"_tags/chip-esp32picod4", "_tags/chip-esp32s2", "_tags/chip-esp32s3",
"_tags/chip-esp32wroom32", "_tags/chip-esp32wrover32", "_tags/chip-fpga",
"_tags/chip-imx8", "_tags/chip-imx93", "_tags/chip-nrf52",
"_tags/chip-nrf52832", "_tags/chip-nrf52840", "_tags/chip-nrf53",
"_tags/chip-nrf5340", "_tags/chip-nrf91", "_tags/chip-nrf9160",
"_tags/chip-rk3399", "_tags [...]
\ No newline at end of file
diff --git a/content/feed.xml b/content/feed.xml
index 4f82e778b..ff812f6ce 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Thu, 15 May 2025 00:29:39 +0000</pubDate>
- <lastBuildDate>Thu, 15 May 2025 00:29:39 +0000</lastBuildDate>
+ <pubDate>Fri, 16 May 2025 00:30:54 +0000</pubDate>
+ <lastBuildDate>Fri, 16 May 2025 00:30:54 +0000</lastBuildDate>
<generator>Jekyll v4.3.2</generator>
<item>
