You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by gi...@apache.org on 2021/04/29 00:14:37 UTC
[incubator-nuttx-website] branch asf-site updated: Publishing web:
d7e0482dfe46b581ceed012309c52de3f59e2a49 docs:
26f09cec6dfbc6b44d3b99e765d29d53d956fa52
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/incubator-nuttx-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e5e98e3 Publishing web: d7e0482dfe46b581ceed012309c52de3f59e2a49 docs: 26f09cec6dfbc6b44d3b99e765d29d53d956fa52
e5e98e3 is described below
commit e5e98e35a11b044109997630d3c9bd707faa4c86
Author: Abdelatif <ab...@espressif.com>
AuthorDate: Thu Apr 29 00:13:22 2021 +0000
Publishing web: d7e0482dfe46b581ceed012309c52de3f59e2a49 docs: 26f09cec6dfbc6b44d3b99e765d29d53d956fa52
---
content/docs/10.0.0/index.html | 2 +-
content/docs/10.0.1/index.html | 2 +-
.../latest/_sources/applications/nsh/login.rst.txt | 2 +-
.../components/drivers/character/foc.rst.txt | 2 +-
.../components/drivers/character/watchdog.rst.txt | 22 +++++++++++-----------
.../_sources/components/nxgraphics/nxtk.rst.txt | 4 ++--
.../_sources/contributing/documentation.rst.txt | 6 +++---
.../latest/_sources/contributing/workflow.rst.txt | 4 ++--
.../latest/_sources/guides/tasktraceuser.rst.txt | 4 ++--
.../_sources/introduction/detailed_support.rst.txt | 16 +++++++++++++++-
.../latest/_sources/introduction/resources.rst.txt | 2 +-
.../arm/imxrt/boards/teensy-4.x/index.rst.txt | 2 +-
.../_sources/platforms/arm/imxrt/index.rst.txt | 12 ++++++------
.../_sources/platforms/arm/nrf52/index.rst.txt | 10 +++++-----
.../latest/_sources/quickstart/compiling.rst.txt | 6 +++---
.../latest/_sources/quickstart/running.rst.txt | 16 ++++++++--------
.../latest/_sources/reference/os/wqueue.rst.txt | 2 +-
.../reference/user/01_task_control.rst.txt | 2 +-
content/docs/latest/applications/nsh/login.html | 2 +-
.../latest/components/drivers/character/foc.html | 2 +-
.../components/drivers/character/watchdog.html | 2 +-
.../docs/latest/components/nxgraphics/nxtk.html | 4 ++--
.../docs/latest/contributing/documentation.html | 6 +++---
content/docs/latest/contributing/workflow.html | 4 ++--
content/docs/latest/guides/tasktraceuser.html | 4 ++--
content/docs/latest/index.html | 2 +-
.../docs/latest/introduction/detailed_support.html | 14 +++++++++++++-
content/docs/latest/introduction/resources.html | 2 +-
.../arm/imxrt/boards/teensy-4.x/index.html | 2 +-
content/docs/latest/platforms/arm/imxrt/index.html | 12 ++++++------
content/docs/latest/platforms/arm/nrf52/index.html | 2 +-
content/docs/latest/quickstart/compiling.html | 2 +-
content/docs/latest/quickstart/running.html | 2 +-
content/docs/latest/reference/os/wqueue.html | 2 +-
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 ++--
36 files changed, 106 insertions(+), 80 deletions(-)
diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index 6836fd2..150fd82 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: 28 April 21 at 00:11</p>
+<p>Last Updated: 29 April 21 at 00:11</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 bd2aad2..e5ad85b 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -211,7 +211,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: 28 April 21 at 00:11</p>
+<p>Last Updated: 29 April 21 at 00:11</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/latest/_sources/applications/nsh/login.rst.txt b/content/docs/latest/_sources/applications/nsh/login.rst.txt
index 6aabfc3..01d5386 100644
--- a/content/docs/latest/_sources/applications/nsh/login.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/login.rst.txt
@@ -57,7 +57,7 @@ credentials at login time:
This is not very flexible since there can be only one user and the
password is fixed in the FLASH image. This option is also not very
secure because a malicious user could get the password by just
- looking at the ``.text`` stings in the flash image.
+ looking at the ``.text`` strings in the flash image.
#. NSH can also be configured to defer the entire user credential
verification to platform-specific logic with this setting::
diff --git a/content/docs/latest/_sources/components/drivers/character/foc.rst.txt b/content/docs/latest/_sources/components/drivers/character/foc.rst.txt
index 1a1612a..f4dd710 100644
--- a/content/docs/latest/_sources/components/drivers/character/foc.rst.txt
+++ b/content/docs/latest/_sources/components/drivers/character/foc.rst.txt
@@ -17,7 +17,7 @@ The Nuttx FOC driver is split into two parts:
#. An "upper half", generic driver that provides the common FOC
interface to application level code,
-#. A "lower half", platform-specific driver that implemets
+#. A "lower half", platform-specific driver that implements
the low-level logic to implement the FOC functionality
Files supporting FOC can be found in the following locations:
diff --git a/content/docs/latest/_sources/components/drivers/character/watchdog.rst.txt b/content/docs/latest/_sources/components/drivers/character/watchdog.rst.txt
index b4e8e53..287aa45 100644
--- a/content/docs/latest/_sources/components/drivers/character/watchdog.rst.txt
+++ b/content/docs/latest/_sources/components/drivers/character/watchdog.rst.txt
@@ -65,7 +65,7 @@ Enabling the Watchdog Support and Example in ``menuconfing``
4. Include the Debug Watchdog Feature
In order to get the watchdog timer status, you need to enable it. For production code and for your application you may disable it.
-
+
Go into menu :menuselection:`Build Setup --> Debug Options` and press :kbd:`Enter`. Then enable:
- [x] Enable Debug Features
@@ -79,7 +79,7 @@ The previously selected example will basically do the following:
* Open the watchdog device
* Set the watchdog timeout
* Start the watchdog timer
-* Ping (feed the dog) during the ``pingtime`` with a delay of ``pingdelay`` and print out the wdt status in case debug was enabled.
+* Ping (feed the dog) during the ``pingtime`` with a delay of ``pingdelay`` and print out the wdt status in case debug was enabled.
* Enter into an endless loop without pinging. It will cause the watchdog timer to reset the chip on timeout, i.e., after timer expiration.
@@ -136,7 +136,7 @@ This command gets the status of the watchdog timer. It receives a writeable poin
.. c:macro:: WDIOC_SETTIMEOUT
-This command sets the timeout value, i.e., the value that will trigger the reset or interrupt. The argument is a ``uint32_t`` value in miliseconds.
+This command sets the timeout value, i.e., the value that will trigger the reset or interrupt. The argument is a ``uint32_t`` value in milliseconds.
.. c:macro:: WDIOC_CAPTURE
@@ -153,12 +153,12 @@ This command registers an user callback that will be triggered on timeout. It re
.. c:macro:: WDIOC_KEEPALIVE
- This command resets the watchdog timer AKA '**ping**", "**kick**", "**pet**", "**feed**" the dog".
+ This command resets the watchdog timer AKA '**ping**", "**kick**", "**pet**", "**feed**" the dog".
Enable Built in System Monitoring to reset the watchdog
-------------------------------------------------------
-The auto-monitor provides an OS-internal mechanism to automatically start and repeatedly reset the watchdog.
+The auto-monitor provides an OS-internal mechanism to automatically start and repeatedly reset the watchdog.
To enable it, follow the next instructions:
@@ -181,16 +181,16 @@ To enable it, follow the next instructions:
After selecting the option you may want to configure some parameters:
* **Timeout**: It is the watchdog timer expiration time in seconds.
- * **Keep a live interval**: This is the interval in which the watchdog will be fed. It is in seconds. It can't be bigger than the timeout. If this interval is equal to timeout interval, than this interval will automatically change to half timeout.
+ * **Keep a live interval**: This is the interval in which the watchdog will be fed. It is in seconds. It can't be bigger than the timeout. If this interval is equal to timeout interval, than this interval will automatically change to half timeout.
* **Keep alive by**: This is a choice to determine who is going to feed the dog. There are 4 possible choices that are described as follows.
- ``Capture callback``: This choice registers a watchdog timer callback to reset the watchdog every time it expires, i.e., on timeout.
+ ``Capture callback``: This choice registers a watchdog timer callback to reset the watchdog every time it expires, i.e., on timeout.
``Timer callback``: This choice also uses a timer callback to reset the watchdog, but it will reset the watchdog every "keep a live interval".
``Worker callback``: This choice uses a Work Queue to reset the watchdog every "keep a live interval". This choice depends on having the Low or High Priority Work Queue enabled.
- If only the High Priority Work Queue is enabled, this one will be used, otherwise Low Priority Work Queue is used.
-
+ If only the High Priority Work Queue is enabled, this one will be used, otherwise Low Priority Work Queue is used.
+
So, before enabling it, go into menu :menuselection:`RTOS Features --> Work queue support` and press :kbd:`Enter`.
- [x] Low priority (kernel) worker thread
@@ -200,5 +200,5 @@ To enable it, follow the next instructions:
Go into menu :menuselection:`Device Drivers` and enable:
- [x] Power Management Support
-
-After selecting one of these choices, the chip will keep itself alive by one of these options.
+
+After selecting one of these choices, the chip will keep itself alive by one of these options.
diff --git a/content/docs/latest/_sources/components/nxgraphics/nxtk.rst.txt b/content/docs/latest/_sources/components/nxgraphics/nxtk.rst.txt
index 6ff4a02..22378b9 100644
--- a/content/docs/latest/_sources/components/nxgraphics/nxtk.rst.txt
+++ b/content/docs/latest/_sources/components/nxgraphics/nxtk.rst.txt
@@ -500,9 +500,9 @@ these sub-windows to be managed more-or-less independently:
:param rect:
The location within the toolbar window to be retrieved.
:param plane:
- TSpecifies the color plane to get from.
+ Specifies the color plane to get from.
:param dest:
- TThe location to copy the memory region.
+ The location to copy the memory region.
:param deststride:
The width, in bytes, of the dest memory.
diff --git a/content/docs/latest/_sources/contributing/documentation.rst.txt b/content/docs/latest/_sources/contributing/documentation.rst.txt
index a430716..6f57b1d 100644
--- a/content/docs/latest/_sources/contributing/documentation.rst.txt
+++ b/content/docs/latest/_sources/contributing/documentation.rst.txt
@@ -24,7 +24,7 @@ go into ``Documentation`` directory. Then,
$ pip3 install pipenv
$ pipenv install
- $ # activate the virtual environent
+ $ # activate the virtual environment
$ pipenv shell
2. Build documentation:
@@ -82,7 +82,7 @@ sometimes Sphinx's approach is used over standard RST since it is more powerful
Documentation Conventions
=========================
-While RST/Sphinx provide many ways to do things, it is best to follow a given convention to mantain consistency and avoid
+While RST/Sphinx provide many ways to do things, it is best to follow a given convention to maintain consistency and avoid
pitfalls. For this reason, documentation changes should follow the following set of conventions.
Indentation
@@ -180,7 +180,7 @@ Tips
Spacing
-------
-If you are getting formatting errors, be sure to provide the appropiate spacing between a directive and its content.
+If you are getting formatting errors, be sure to provide the appropriate spacing between a directive and its content.
Generally, you should follow this format:
.. code-block:: RST
diff --git a/content/docs/latest/_sources/contributing/workflow.rst.txt b/content/docs/latest/_sources/contributing/workflow.rst.txt
index 574c873..d6bf888 100644
--- a/content/docs/latest/_sources/contributing/workflow.rst.txt
+++ b/content/docs/latest/_sources/contributing/workflow.rst.txt
@@ -13,7 +13,7 @@ You should be aware of the following:
automatically during CI to ensure conformance.
Note that not all existing files in the repository are already adapted to conform to the standard as this is an ongoing effort. Thus,
- if you're submitting a patch to an existing file you may have to make the file conform to the standard, even if you are not reponsible
+ if you're submitting a patch to an existing file you may have to make the file conform to the standard, even if you are not responsible
for those standard violations.
It is also appreciated that you separate any styling fixes in a separate commit from the functional changes so that these are more
@@ -37,6 +37,6 @@ You should be aware of the following:
- If this is from an inactive project, it may be considered for inclusion in NuttX, provided that licensing terms allow to do so
and it is deemed of sufficient value to be included, considering that this code will have to be maintained in NuttX afterwards.
- Note that it is undesireable to included non Apache 2.0 Licensed code inside the repository, even if the license itself allows it
+ Note that it is undesirable to included non Apache 2.0 Licensed code inside the repository, even if the license itself allows it
(for example BSD License).
diff --git a/content/docs/latest/_sources/guides/tasktraceuser.rst.txt b/content/docs/latest/_sources/guides/tasktraceuser.rst.txt
index 293c3ff..a04c160 100644
--- a/content/docs/latest/_sources/guides/tasktraceuser.rst.txt
+++ b/content/docs/latest/_sources/guides/tasktraceuser.rst.txt
@@ -109,7 +109,7 @@ After getting the trace, the following command displays the accumulated trace da
nsh> trace dump
-This will be get the trace results like the followings:
+This will get the trace results like the following:
.. code-block::
@@ -266,7 +266,7 @@ The default value is given by the kernel configuration ``CONFIG_SCHED_INSTRUMENT
- ``-a`` : Disable recording the system call arguments.
- ``+i`` : Enable interrupt trace.
- It records the event of enter/leave interrupt handler which is occured while the tracing.
+ It records the event of enter/leave interrupt handler which occurred while tracing.
All IRQs are recorded by default. ``trace irq`` command can filter the IRQs to be recorded.
- ``-i`` : Disable interrupt trace.
diff --git a/content/docs/latest/_sources/introduction/detailed_support.rst.txt b/content/docs/latest/_sources/introduction/detailed_support.rst.txt
index 5285540..65ab059 100644
--- a/content/docs/latest/_sources/introduction/detailed_support.rst.txt
+++ b/content/docs/latest/_sources/introduction/detailed_support.rst.txt
@@ -2464,7 +2464,7 @@ Also refer to the NuttX board
file for further information about the current state of the port.
NuttX-9.0 added basic support for Microchip SAME54 Xplained Pro board.
-An ethernet driver was also added to the SAME5x familly.
+An ethernet driver was also added to the SAME5x family.
STMicro STM32 F72x/F73x
-----------------------
@@ -3095,7 +3095,21 @@ All three boards are based on the eZ80F091 part and all use the Zilog
ZDS-II Windows command line tools. The development environment is either
Windows native or Cygwin or MSYS2 under Windows.
+It is also possible to compile using ``clang`` and the GNU ``binutils``
+toolchain. You must have a variant of ``clang`` that supports the eZ80,
+and an install of ``binutils`` built with Z80 support.
+``clang`` with eZ80 support is available as part of the Texas Instruments
+CE 85+ unofficial `toolchain <https://ce-programming.github.io/toolchain/>`
+and requires a further `patch <https://github.com/codebje/ez80-toolchain/tree/master/clang>`
+to support GNU assembler syntax.
+
+GNU ``binutils`` supports the Z80 family. It will require compilation with
+appropriate configuration to enable support.
+
+C intrinsics are also required. Some may be found in the Zilog ZDS-II
+distribution, requiring some modification to build with the GNU assembler.
+Additional intrinsics for 64-bit support must be supplied.
Zilog Z8Encore!
===============
diff --git a/content/docs/latest/_sources/introduction/resources.rst.txt b/content/docs/latest/_sources/introduction/resources.rst.txt
index 0ac8cf4..4ef40af 100644
--- a/content/docs/latest/_sources/introduction/resources.rst.txt
+++ b/content/docs/latest/_sources/introduction/resources.rst.txt
@@ -13,7 +13,7 @@ Here's a list of Apache NuttX resources that you might find helpful:
* `Apache NuttX mailing list <https://nuttx.apache.org/community/>`_ – a very active mailing list, the place to get help with your application or any questions you have about NuttX.
* `Apache NuttX YouTube channel <https://www.youtube.com/channel/UC0QciIlcUnjJkL5yJJBmluw/videos>`_ – Alan Carvalho de Assis's YouTube channel on NuttX. It's a source of a lot of great practical information.
* `Apache NuttX Coding Standard <https://cwiki.apache.org/confluence/display/NUTTX/Coding+Standard>`_ — How code should look when you submit new files or modify existing ones.
- * `Apache NuttX Code Contribution Guidlines <https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow>`_ — The full workflow to follow for submitting code with all the details.
+ * `Apache NuttX Code Contribution Guidelines <https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow>`_ — The full workflow to follow for submitting code with all the details.
* Git
diff --git a/content/docs/latest/_sources/platforms/arm/imxrt/boards/teensy-4.x/index.rst.txt b/content/docs/latest/_sources/platforms/arm/imxrt/boards/teensy-4.x/index.rst.txt
index 5745d30..447f62e 100644
--- a/content/docs/latest/_sources/platforms/arm/imxrt/boards/teensy-4.x/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/arm/imxrt/boards/teensy-4.x/index.rst.txt
@@ -96,7 +96,7 @@ This configuration can be easily changed to work with Teensy 4.0 by
selecting ``CONFIG_TEENSY_40=y``.
This configuration runs over LPUART1 (pins 24 and 25 on Teensy). Communication
-over USB console can be turn on, but it couses problems with FlexCAN.
+over USB console can be turn on, but it causes problems with FlexCAN.
netnsh-4.1
----------
diff --git a/content/docs/latest/_sources/platforms/arm/imxrt/index.rst.txt b/content/docs/latest/_sources/platforms/arm/imxrt/index.rst.txt
index 6a0f9b3..f694e89 100644
--- a/content/docs/latest/_sources/platforms/arm/imxrt/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/arm/imxrt/index.rst.txt
@@ -69,7 +69,7 @@ range of supply voltage (rail-to-rail operation).
ADC
---
-ADC driver with the successive approximation analog/digital convertor. The lower-half of
+ADC driver with the successive approximation analog/digital converter. The lower-half of
this driver is initialize by calling :c:func:`imxrt_adcinitialize`.
CAN
@@ -82,7 +82,7 @@ calling :c:func:`imxrt_cannitialize()`.
There is an booting option that automatically provides initialization of network interface
in the early stages of booting and therefore calling :c:func:`imxrt_cannitialize()` via
-board specific logic is not neccessary. This however works only when there is only one
+board specific logic is not necessary. This however works only when there is only one
interface in the chip. For running more interfaces (like CAN and Ethernet), network late
initialization must be turn on by CONFIG_NETDEV_LATEINIT and board specific logic must call
lower-half part of drivers.
@@ -95,7 +95,7 @@ CMOS Sensor interface which enables the chip to connect directly to external CMO
DAC
---
-Digital/analog convertor for external signal is only supported in i.MX RT1170 MCU. It is 12 bit
+Digital/analog converter for external signal is only supported in i.MX RT1170 MCU. It is 12 bit
lower power, general purpose DAC.
eLCDIF
@@ -117,7 +117,7 @@ by calling :c:func:`imxrt_netnitialize`.
There is an booting option that automatically provides initialization of network interface
in the early stages of booting and therefore calling :c:func:`imxrt_cannitialize()` via
-board specific logic is not neccessary. This however works only when there is only one
+board specific logic is not necessary. This however works only when there is only one
interface in the chip. For running more interfaces (like CAN and Ethernet), network late
initialization must be turn on by CONFIG_NETDEV_LATEINIT and board specific logic must call
lower-half part of drivers.
@@ -137,7 +137,7 @@ done by :c:func:`imxrt_gpio_write` function and reading is done by :c:func:`imxr
MCUs i.MX RT1060 and higher includes both standard speed GPIOs (1-5) and high speed
GPIOS (6-9). Regular and high speed GPIO share the same pins (GPIO1 is with GPIO6 etc),
-therefore IOMUXC_GPR_GPR26-29 registers are used to determine what modue is used for the
+therefore IOMUXC_GPR_GPR26-29 registers are used to determine what module is used for the
GPIO pins.
@@ -160,7 +160,7 @@ Synchronous audio interface provided by I2C module. Supported in i.MX RT1015 and
SPDIF
-----
-Sony/Philips digital interface audio block. It is a stereo transciever that allows the
+Sony/Philips digital interface audio block. It is a stereo transceiver that allows the
processor to receive and transmit digital audio. Supported in i.MX RT1010 and higher.
SPI
diff --git a/content/docs/latest/_sources/platforms/arm/nrf52/index.rst.txt b/content/docs/latest/_sources/platforms/arm/nrf52/index.rst.txt
index fee6e80..582de9c 100644
--- a/content/docs/latest/_sources/platforms/arm/nrf52/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/arm/nrf52/index.rst.txt
@@ -63,7 +63,7 @@ GPIO/GPIOTE
-----------
Pins can be configured/operated using ``nrf52_gpio_*`` functions. Interrupts are
-handled via the GPIOTE peripheral in one of two ways: via a GPIOTE channel or via
+handled via the GPIOTE peripheral in one of two ways: via a GPIOTE channel or via
PORT events. The former allows for simultaneous rising/falling edge-sensitive interrupts
per-pin. However, as there are a limited number of channels (and sometimes these
are used by some drivers for specific tasks), it may not always be possible to use
@@ -88,7 +88,7 @@ is initialized by calling :c:func:`nrf52_adcinitialize`.
I2C
---
-I2C is supported both in polling and interrupt mode (via EasyDMA).
+I2C is supported both in polling and interrupt mode (via EasyDMA).
.. note:: The I2C peripheral does not support sending two transfers without sending
a START nor RSTART. For this reason, this is supported via an internal buffer where
@@ -105,7 +105,7 @@ SPI is supported both in polling and interrupt-based (via EasyDMA) mode. The lat
supports arbitrarily long transfers using Nordic's list-mode EasyDMA (intermediate
transfers are currently still manually started).
-It is possible to use SPI without either MOSI/MISO pin defined by simply not providing
+It is possible to use SPI without either MOSI/MISO pin defined by simply not providing
the relevant ``BOARD_SPI*_MISO/MOSI_PIN`` definition.
This implementation support power management hooks, which will disable SPI peripheral when
@@ -115,7 +115,7 @@ UART
----
UART is implemented using polling. UARTE EasyDMA feature is not yet supported.
-This may introduce a large number of interrupts which may be undesireable.
+This may introduce a large number of interrupts which may be undesirable.
PPI
---
@@ -166,7 +166,7 @@ you need to call :c:func:`nrf52_sdc_initialize` on boot, which will initialize t
SDC support involves registering various high-priority zero-latency interrupts and thus requires
enabling BASEPRI and high-priority interrupt support. On supported boards, a sample ``sdc`` configuration
-is provided with settings already set.
+is provided with settings already set.
Note that in this case, some peripherals (mostly those related to BLE) will be unavailable. Some PPI
channels will also be ocuppied (``NRF52_PPI_NUM_CONFIGURABLE_CHANNELS`` will be set accordingly in this case).
diff --git a/content/docs/latest/_sources/quickstart/compiling.rst.txt b/content/docs/latest/_sources/quickstart/compiling.rst.txt
index c2a2ae4..0aef207 100644
--- a/content/docs/latest/_sources/quickstart/compiling.rst.txt
+++ b/content/docs/latest/_sources/quickstart/compiling.rst.txt
@@ -21,7 +21,7 @@ a pre-existing configuration. To list all supported configurations you can do:
$ ./tools/configure.sh -L | less
The output is in the format ``<board name>:<board configuration>``. You will see that
-generally all boards support the ``nsh`` configuration which is a good sarting point
+generally all boards support the ``nsh`` configuration which is a good starting point
since it enables booting into the interactive command line
:doc:`/applications/nsh/index`.
@@ -43,7 +43,7 @@ configuration system with:
$ cd nuttx/
$ make menuconfig
-
+
Modifying the configuration is covered in :doc:`configuring`.
Build NuttX
@@ -66,7 +66,7 @@ To clean the build, you can do:
.. code-block:: console
$ make clean
-
+
.. tip::
To increase build speed (or of any other target such as ``clean``), you can
diff --git a/content/docs/latest/_sources/quickstart/running.rst.txt b/content/docs/latest/_sources/quickstart/running.rst.txt
index dd07a6e..6deb17d 100644
--- a/content/docs/latest/_sources/quickstart/running.rst.txt
+++ b/content/docs/latest/_sources/quickstart/running.rst.txt
@@ -11,7 +11,7 @@ which also integrates the debugger/programmer in the board itself exposed via US
connector.
A good choice is a Nucleo or Discovery board from ST Microelectronics,
-as there is a wide choice of suported boards for the STM32 architecture in NuttX.
+as there is a wide choice of supported boards for the STM32 architecture in NuttX.
Also, these boards expose an UART port over the USB connection which allows you
to interact with NuttX via the interactive console without any extra hardware.
For the purposes of this guide, we will use the Nucleo F103RB board.
@@ -25,7 +25,7 @@ of programmers and target microcontrollers.
You should note that ``openocd`` project has not made stable releases for long
time and support for newer hardware will probably be only available in the
-latest Git version, so it is actually recommended to install latest development
+latest Git version, so it is actually recommended to install latest development
version.
.. tabs::
@@ -37,7 +37,7 @@ version.
.. tab:: Install latest version from source
.. code-block:: console
-
+
$ git clone git://git.code.sf.net/p/openocd/code openocd
$ cd openocd
$ ./bootstrap
@@ -46,7 +46,7 @@ version.
The resulting installation will be under ``openocd/install``. You can add
``openocd/install/bin`` to your ``PATH``.
-
+
Now, to flash the binary to your board, connect the USB cable and do:
.. code-block:: console
@@ -72,15 +72,15 @@ if you don't see anything):
.. code-tab:: console gtkterm (GUI)
$ gtkterm -s 115200 -p /dev/ttyUSB0
-
+
.. tip::
You may have to add yourself to the ``dialout`` group on Linux to have permission
to access serial ports:
-
+
.. code-block:: console
-
+
$ gpasswd -a <user> dialout
-
+
Where ``<user>`` is your username. You will need to log out from your desktop
for the change to have effect.
diff --git a/content/docs/latest/_sources/reference/os/wqueue.rst.txt b/content/docs/latest/_sources/reference/os/wqueue.rst.txt
index d22291b..d026d32 100644
--- a/content/docs/latest/_sources/reference/os/wqueue.rst.txt
+++ b/content/docs/latest/_sources/reference/os/wqueue.rst.txt
@@ -60,7 +60,7 @@ to match the highest priority client.
**Configuration Options**.
-- ``CONFIG_SCHED_HPWORK``. Enables the hight priority work queue.
+- ``CONFIG_SCHED_HPWORK``. Enables the high priority work queue.
- ``CONFIG_SCHED_HPNTHREADS``. The number of threads in the
high-priority queue's thread pool. Default: 1
- ``CONFIG_SCHED_HPWORKPRIORITY``. The execution priority of the
diff --git a/content/docs/latest/_sources/reference/user/01_task_control.rst.txt b/content/docs/latest/_sources/reference/user/01_task_control.rst.txt
index 3b4566f..63a23be 100644
--- a/content/docs/latest/_sources/reference/user/01_task_control.rst.txt
+++ b/content/docs/latest/_sources/reference/user/01_task_control.rst.txt
@@ -199,7 +199,7 @@ Functions
- Deletion of self is supported, but only because ``task_delete()``
will re-direct processing to ``exit()``.
-.. :c:funcion:: int task_restart(pid_t pid)
+.. :c:function:: int task_restart(pid_t pid)
This function *restarts* a task. The task is first
terminated and then reinitialized with same ID, priority, original entry
diff --git a/content/docs/latest/applications/nsh/login.html b/content/docs/latest/applications/nsh/login.html
index c744a29..fad757a 100644
--- a/content/docs/latest/applications/nsh/login.html
+++ b/content/docs/latest/applications/nsh/login.html
@@ -278,7 +278,7 @@ CONFIG_NSH_LOGIN_PASSWORD="Administrator"
<p>This is not very flexible since there can be only one user and the
password is fixed in the FLASH image. This option is also not very
secure because a malicious user could get the password by just
-looking at the <code class="docutils literal notranslate"><span class="pre">.text</span></code> stings in the flash image.</p>
+looking at the <code class="docutils literal notranslate"><span class="pre">.text</span></code> strings in the flash image.</p>
</li>
<li><p>NSH can also be configured to defer the entire user credential
verification to platform-specific logic with this setting:</p>
diff --git a/content/docs/latest/components/drivers/character/foc.html b/content/docs/latest/components/drivers/character/foc.html
index 454b5fe..f9d10d1 100644
--- a/content/docs/latest/components/drivers/character/foc.html
+++ b/content/docs/latest/components/drivers/character/foc.html
@@ -251,7 +251,7 @@ quadrature current (Iq) in powered device.</p>
<ol class="arabic simple">
<li><p>An “upper half”, generic driver that provides the common FOC
interface to application level code,</p></li>
-<li><p>A “lower half”, platform-specific driver that implemets
+<li><p>A “lower half”, platform-specific driver that implements
the low-level logic to implement the FOC functionality</p></li>
</ol>
<p>Files supporting FOC can be found in the following locations:</p>
diff --git a/content/docs/latest/components/drivers/character/watchdog.html b/content/docs/latest/components/drivers/character/watchdog.html
index 296d24d..9e77a74 100644
--- a/content/docs/latest/components/drivers/character/watchdog.html
+++ b/content/docs/latest/components/drivers/character/watchdog.html
@@ -382,7 +382,7 @@ the dog will starve and the chip will trigger an interrupt or reset.</p>
<code class="sig-name descname"><span class="pre">WDIOC_SETTIMEOUT</span></code><a class="headerlink" href="#c.WDIOC_SETTIMEOUT" title="Permalink to this definition">¶</a><br /></dt>
<dd></dd></dl>
-<p>This command sets the timeout value, i.e., the value that will trigger the reset or interrupt. The argument is a <code class="docutils literal notranslate"><span class="pre">uint32_t</span></code> value in miliseconds.</p>
+<p>This command sets the timeout value, i.e., the value that will trigger the reset or interrupt. The argument is a <code class="docutils literal notranslate"><span class="pre">uint32_t</span></code> value in milliseconds.</p>
<dl class="c macro">
<dt id="c.WDIOC_CAPTURE">
<code class="sig-name descname"><span class="pre">WDIOC_CAPTURE</span></code><a class="headerlink" href="#c.WDIOC_CAPTURE" title="Permalink to this definition">¶</a><br /></dt>
diff --git a/content/docs/latest/components/nxgraphics/nxtk.html b/content/docs/latest/components/nxgraphics/nxtk.html
index 597b17c..11a9cd0 100644
--- a/content/docs/latest/components/nxgraphics/nxtk.html
+++ b/content/docs/latest/components/nxgraphics/nxtk.html
@@ -826,8 +826,8 @@ the top window.</p>
<li><p><strong>hfwnd</strong> – A handle previously returned by
<code class="docutils literal notranslate"><span class="pre">`nxtk_openwindow()</span></code> <#nxtkopenwindow>`__.</p></li>
<li><p><strong>rect</strong> – The location within the toolbar window to be retrieved.</p></li>
-<li><p><strong>plane</strong> – TSpecifies the color plane to get from.</p></li>
-<li><p><strong>dest</strong> – TThe location to copy the memory region.</p></li>
+<li><p><strong>plane</strong> – Specifies the color plane to get from.</p></li>
+<li><p><strong>dest</strong> – The location to copy the memory region.</p></li>
<li><p><strong>deststride</strong> – The width, in bytes, of the dest memory.</p></li>
</ul>
</dd>
diff --git a/content/docs/latest/contributing/documentation.html b/content/docs/latest/contributing/documentation.html
index 1b15b6e..e357408 100644
--- a/content/docs/latest/contributing/documentation.html
+++ b/content/docs/latest/contributing/documentation.html
@@ -251,7 +251,7 @@ project <a class="reference external" href="https://github.com/pyenv/pyenv#insta
<blockquote>
<div><div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>pip3 install pipenv
<span class="gp">$ </span>pipenv install
-<span class="gp">$ </span><span class="c1"># activate the virtual environent</span>
+<span class="gp">$ </span><span class="c1"># activate the virtual environment</span>
<span class="gp">$ </span>pipenv shell
</pre></div>
</div>
@@ -307,7 +307,7 @@ sometimes Sphinx’s approach is used over standard RST since it is more powerfu
</div>
<div class="section" id="documentation-conventions">
<h2>Documentation Conventions<a class="headerlink" href="#documentation-conventions" title="Permalink to this headline">¶</a></h2>
-<p>While RST/Sphinx provide many ways to do things, it is best to follow a given convention to mantain consistency and avoid
+<p>While RST/Sphinx provide many ways to do things, it is best to follow a given convention to maintain consistency and avoid
pitfalls. For this reason, documentation changes should follow the following set of conventions.</p>
<div class="section" id="indentation">
<h3>Indentation<a class="headerlink" href="#indentation" title="Permalink to this headline">¶</a></h3>
@@ -387,7 +387,7 @@ Systems) use the <a class="reference external" href="https://github.com/executab
<h2>Tips<a class="headerlink" href="#tips" title="Permalink to this headline">¶</a></h2>
<div class="section" id="spacing">
<h3>Spacing<a class="headerlink" href="#spacing" title="Permalink to this headline">¶</a></h3>
-<p>If you are getting formatting errors, be sure to provide the appropiate spacing between a directive and its content.
+<p>If you are getting formatting errors, be sure to provide the appropriate spacing between a directive and its content.
Generally, you should follow this format:</p>
<div class="highlight-RST notranslate"><div class="highlight"><pre><span></span><span class="p">..</span> <span class="ow">directive</span><span class="p">::</span>
diff --git a/content/docs/latest/contributing/workflow.html b/content/docs/latest/contributing/workflow.html
index 32dccd2..3297f80 100644
--- a/content/docs/latest/contributing/workflow.html
+++ b/content/docs/latest/contributing/workflow.html
@@ -222,7 +222,7 @@ will be reviewed and checked using Continuous Integration (CI) practices.</p>
or complete patchsets using <code class="docutils literal notranslate"><span class="pre">checkpatch</span></code> script (both found in <code class="docutils literal notranslate"><span class="pre">tools</span></code> subdirectory of NuttX repository). This check will also run
automatically during CI to ensure conformance.</p>
<p>Note that not all existing files in the repository are already adapted to conform to the standard as this is an ongoing effort. Thus,
-if you’re submitting a patch to an existing file you may have to make the file conform to the standard, even if you are not reponsible
+if you’re submitting a patch to an existing file you may have to make the file conform to the standard, even if you are not responsible
for those standard violations.</p>
<p>It is also appreciated that you separate any styling fixes in a separate commit from the functional changes so that these are more
easily readable during review.</p>
@@ -241,7 +241,7 @@ changes required in third-party code for NuttX support are to be implemented in
it is acceptable to include a patch to be applied to this third-party code, which will be pulled during built.</p></li>
<li><p>If this is from an inactive project, it may be considered for inclusion in NuttX, provided that licensing terms allow to do so
and it is deemed of sufficient value to be included, considering that this code will have to be maintained in NuttX afterwards.</p>
-<p>Note that it is undesireable to included non Apache 2.0 Licensed code inside the repository, even if the license itself allows it
+<p>Note that it is undesirable to included non Apache 2.0 Licensed code inside the repository, even if the license itself allows it
(for example BSD License).</p>
</li>
</ul>
diff --git a/content/docs/latest/guides/tasktraceuser.html b/content/docs/latest/guides/tasktraceuser.html
index a4a1be3..c347703 100644
--- a/content/docs/latest/guides/tasktraceuser.html
+++ b/content/docs/latest/guides/tasktraceuser.html
@@ -333,7 +333,7 @@ After getting the trace, the following command displays the accumulated trace da
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh> trace dump
</pre></div>
</div>
-<p>This will be get the trace results like the followings:</p>
+<p>This will get the trace results like the following:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span><noname>-1 [0] 7.640000000: sys_close()
<noname>-1 [0] 7.640000000: sys_close -> 0
<noname>-1 [0] 7.640000000: sys_sched_lock()
@@ -446,7 +446,7 @@ All system calls are recorded by default. <code class="docutils literal notransl
It records the arguments passed to the issued system call to the trace data.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">-a</span></code> : Disable recording the system call arguments.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">+i</span></code> : Enable interrupt trace.
-It records the event of enter/leave interrupt handler which is occured while the tracing.
+It records the event of enter/leave interrupt handler which occurred while tracing.
All IRQs are recorded by default. <code class="docutils literal notranslate"><span class="pre">trace</span> <span class="pre">irq</span></code> command can filter the IRQs to be recorded.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">-i</span></code> : Disable interrupt trace.</p></li>
</ul>
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index 68aed6d..ba74c52 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -212,7 +212,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: 28 April 21 at 00:12</p>
+<p>Last Updated: 29 April 21 at 00:11</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/latest/introduction/detailed_support.html b/content/docs/latest/introduction/detailed_support.html
index 70fe266..c821dbc 100644
--- a/content/docs/latest/introduction/detailed_support.html
+++ b/content/docs/latest/introduction/detailed_support.html
@@ -2605,7 +2605,7 @@ Also refer to the NuttX board
<a class="reference external" href="https://github.com/apache/incubator-nuttx/blob/master/boards/arm/samd5e5/metro-m4/README.txt">README</a>
file for further information about the current state of the port.</p>
<p>NuttX-9.0 added basic support for Microchip SAME54 Xplained Pro board.
-An ethernet driver was also added to the SAME5x familly.</p>
+An ethernet driver was also added to the SAME5x family.</p>
</div>
<div class="section" id="stmicro-stm32-f72x-f73x">
<h3>STMicro STM32 F72x/F73x<a class="headerlink" href="#stmicro-stm32-f72x-f73x" title="Permalink to this headline">¶</a></h3>
@@ -3162,6 +3162,18 @@ ports:</p>
<p>All three boards are based on the eZ80F091 part and all use the Zilog
ZDS-II Windows command line tools. The development environment is either
Windows native or Cygwin or MSYS2 under Windows.</p>
+<p>It is also possible to compile using <code class="docutils literal notranslate"><span class="pre">clang</span></code> and the GNU <code class="docutils literal notranslate"><span class="pre">binutils</span></code>
+toolchain. You must have a variant of <code class="docutils literal notranslate"><span class="pre">clang</span></code> that supports the eZ80,
+and an install of <code class="docutils literal notranslate"><span class="pre">binutils</span></code> built with Z80 support.</p>
+<p><code class="docutils literal notranslate"><span class="pre">clang</span></code> with eZ80 support is available as part of the Texas Instruments
+CE 85+ unofficial <cite>toolchain <https://ce-programming.github.io/toolchain/></cite>
+and requires a further <cite>patch <https://github.com/codebje/ez80-toolchain/tree/master/clang></cite>
+to support GNU assembler syntax.</p>
+<p>GNU <code class="docutils literal notranslate"><span class="pre">binutils</span></code> supports the Z80 family. It will require compilation with
+appropriate configuration to enable support.</p>
+<p>C intrinsics are also required. Some may be found in the Zilog ZDS-II
+distribution, requiring some modification to build with the GNU assembler.
+Additional intrinsics for 64-bit support must be supplied.</p>
</div>
<div class="section" id="zilog-z8encore">
<h2>Zilog Z8Encore!<a class="headerlink" href="#zilog-z8encore" title="Permalink to this headline">¶</a></h2>
diff --git a/content/docs/latest/introduction/resources.html b/content/docs/latest/introduction/resources.html
index dc66f10..43adfc2 100644
--- a/content/docs/latest/introduction/resources.html
+++ b/content/docs/latest/introduction/resources.html
@@ -226,7 +226,7 @@
<li><p><a class="reference external" href="https://nuttx.apache.org/community/">Apache NuttX mailing list</a> – a very active mailing list, the place to get help with your application or any questions you have about NuttX.</p></li>
<li><p><a class="reference external" href="https://www.youtube.com/channel/UC0QciIlcUnjJkL5yJJBmluw/videos">Apache NuttX YouTube channel</a> – Alan Carvalho de Assis’s YouTube channel on NuttX. It’s a source of a lot of great practical information.</p></li>
<li><p><a class="reference external" href="https://cwiki.apache.org/confluence/display/NUTTX/Coding+Standard">Apache NuttX Coding Standard</a> — How code should look when you submit new files or modify existing ones.</p></li>
-<li><p><a class="reference external" href="https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow">Apache NuttX Code Contribution Guidlines</a> — The full workflow to follow for submitting code with all the details.</p></li>
+<li><p><a class="reference external" href="https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow">Apache NuttX Code Contribution Guidelines</a> — The full workflow to follow for submitting code with all the details.</p></li>
</ul>
</li>
<li><p>Git</p>
diff --git a/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html b/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
index b15db5a..7f4d903 100644
--- a/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
+++ b/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
@@ -362,7 +362,7 @@ for imxrt runs at 80 MHz clock frequency.</p>
<p>This configuration can be easily changed to work with Teensy 4.0 by
selecting <code class="docutils literal notranslate"><span class="pre">CONFIG_TEENSY_40=y</span></code>.</p>
<p>This configuration runs over LPUART1 (pins 24 and 25 on Teensy). Communication
-over USB console can be turn on, but it couses problems with FlexCAN.</p>
+over USB console can be turn on, but it causes problems with FlexCAN.</p>
</div>
<div class="section" id="netnsh-4-1">
<h3>netnsh-4.1<a class="headerlink" href="#netnsh-4-1" title="Permalink to this headline">¶</a></h3>
diff --git a/content/docs/latest/platforms/arm/imxrt/index.html b/content/docs/latest/platforms/arm/imxrt/index.html
index 481febf..b328e1b 100644
--- a/content/docs/latest/platforms/arm/imxrt/index.html
+++ b/content/docs/latest/platforms/arm/imxrt/index.html
@@ -396,7 +396,7 @@ range of supply voltage (rail-to-rail operation).</p>
</div>
<div class="section" id="adc">
<h3>ADC<a class="headerlink" href="#adc" title="Permalink to this headline">¶</a></h3>
-<p>ADC driver with the successive approximation analog/digital convertor. The lower-half of
+<p>ADC driver with the successive approximation analog/digital converter. The lower-half of
this driver is initialize by calling <code class="xref c c-func docutils literal notranslate"><span class="pre">imxrt_adcinitialize()</span></code>.</p>
</div>
<div class="section" id="can">
@@ -407,7 +407,7 @@ works beyond SocketCAN driver layout. The lower-half of this driver is initializ
calling <code class="xref c c-func docutils literal notranslate"><span class="pre">imxrt_cannitialize()</span></code>.</p>
<p>There is an booting option that automatically provides initialization of network interface
in the early stages of booting and therefore calling <code class="xref c c-func docutils literal notranslate"><span class="pre">imxrt_cannitialize()</span></code> via
-board specific logic is not neccessary. This however works only when there is only one
+board specific logic is not necessary. This however works only when there is only one
interface in the chip. For running more interfaces (like CAN and Ethernet), network late
initialization must be turn on by CONFIG_NETDEV_LATEINIT and board specific logic must call
lower-half part of drivers.</p>
@@ -418,7 +418,7 @@ lower-half part of drivers.</p>
</div>
<div class="section" id="dac">
<h3>DAC<a class="headerlink" href="#dac" title="Permalink to this headline">¶</a></h3>
-<p>Digital/analog convertor for external signal is only supported in i.MX RT1170 MCU. It is 12 bit
+<p>Digital/analog converter for external signal is only supported in i.MX RT1170 MCU. It is 12 bit
lower power, general purpose DAC.</p>
</div>
<div class="section" id="elcdif">
@@ -436,7 +436,7 @@ of this driver is initialize by calling <code class="xref c c-func docutils lite
by calling <code class="xref c c-func docutils literal notranslate"><span class="pre">imxrt_netnitialize()</span></code>.</p>
<p>There is an booting option that automatically provides initialization of network interface
in the early stages of booting and therefore calling <code class="xref c c-func docutils literal notranslate"><span class="pre">imxrt_cannitialize()</span></code> via
-board specific logic is not neccessary. This however works only when there is only one
+board specific logic is not necessary. This however works only when there is only one
interface in the chip. For running more interfaces (like CAN and Ethernet), network late
initialization must be turn on by CONFIG_NETDEV_LATEINIT and board specific logic must call
lower-half part of drivers.</p>
@@ -453,7 +453,7 @@ This module is supported in i.MX RT1010 and higher.</p>
done by <code class="xref c c-func docutils literal notranslate"><span class="pre">imxrt_gpio_write()</span></code> function and reading is done by <code class="xref c c-func docutils literal notranslate"><span class="pre">imxrt_gpio_read()</span></code>.</p>
<p>MCUs i.MX RT1060 and higher includes both standard speed GPIOs (1-5) and high speed
GPIOS (6-9). Regular and high speed GPIO share the same pins (GPIO1 is with GPIO6 etc),
-therefore IOMUXC_GPR_GPR26-29 registers are used to determine what modue is used for the
+therefore IOMUXC_GPR_GPR26-29 registers are used to determine what module is used for the
GPIO pins.</p>
</div>
<div class="section" id="i2c">
@@ -471,7 +471,7 @@ as a slave. The lower-half of this driver is initialize by calling <code class="
</div>
<div class="section" id="spdif">
<h3>SPDIF<a class="headerlink" href="#spdif" title="Permalink to this headline">¶</a></h3>
-<p>Sony/Philips digital interface audio block. It is a stereo transciever that allows the
+<p>Sony/Philips digital interface audio block. It is a stereo transceiver that allows the
processor to receive and transmit digital audio. Supported in i.MX RT1010 and higher.</p>
</div>
<div class="section" id="spi">
diff --git a/content/docs/latest/platforms/arm/nrf52/index.html b/content/docs/latest/platforms/arm/nrf52/index.html
index 99db280..47ee758 100644
--- a/content/docs/latest/platforms/arm/nrf52/index.html
+++ b/content/docs/latest/platforms/arm/nrf52/index.html
@@ -419,7 +419,7 @@ entering either SLEEP or STANDBY modes and reconfigure it when going back to NOR
<div class="section" id="uart">
<h3>UART<a class="headerlink" href="#uart" title="Permalink to this headline">¶</a></h3>
<p>UART is implemented using polling. UARTE EasyDMA feature is not yet supported.
-This may introduce a large number of interrupts which may be undesireable.</p>
+This may introduce a large number of interrupts which may be undesirable.</p>
</div>
<div class="section" id="ppi">
<h3>PPI<a class="headerlink" href="#ppi" title="Permalink to this headline">¶</a></h3>
diff --git a/content/docs/latest/quickstart/compiling.html b/content/docs/latest/quickstart/compiling.html
index 1fb9e68..f95d744 100644
--- a/content/docs/latest/quickstart/compiling.html
+++ b/content/docs/latest/quickstart/compiling.html
@@ -229,7 +229,7 @@ a pre-existing configuration. To list all supported configurations you can do:</
</div>
</div></blockquote>
<p>The output is in the format <code class="docutils literal notranslate"><span class="pre"><board</span> <span class="pre">name>:<board</span> <span class="pre">configuration></span></code>. You will see that
-generally all boards support the <code class="docutils literal notranslate"><span class="pre">nsh</span></code> configuration which is a good sarting point
+generally all boards support the <code class="docutils literal notranslate"><span class="pre">nsh</span></code> configuration which is a good starting point
since it enables booting into the interactive command line
<a class="reference internal" href="../applications/nsh/index.html"><span class="doc">NuttShell (NSH)</span></a>.</p>
<p>To choose a configuration you pass the <code class="docutils literal notranslate"><span class="pre"><board</span> <span class="pre">name>:<board</span> <span class="pre">configuration></span></code> option
diff --git a/content/docs/latest/quickstart/running.html b/content/docs/latest/quickstart/running.html
index cebd8a8..26c81d1 100644
--- a/content/docs/latest/quickstart/running.html
+++ b/content/docs/latest/quickstart/running.html
@@ -221,7 +221,7 @@ binary. As an easy start, it is recommended that you choose a well supported boa
which also integrates the debugger/programmer in the board itself exposed via USB
connector.</p>
<p>A good choice is a Nucleo or Discovery board from ST Microelectronics,
-as there is a wide choice of suported boards for the STM32 architecture in NuttX.
+as there is a wide choice of supported boards for the STM32 architecture in NuttX.
Also, these boards expose an UART port over the USB connection which allows you
to interact with NuttX via the interactive console without any extra hardware.
For the purposes of this guide, we will use the Nucleo F103RB board.</p>
diff --git a/content/docs/latest/reference/os/wqueue.html b/content/docs/latest/reference/os/wqueue.html
index 7482aad..c6c2949 100644
--- a/content/docs/latest/reference/os/wqueue.html
+++ b/content/docs/latest/reference/os/wqueue.html
@@ -287,7 +287,7 @@ priority of the lower priority worker thread can then be adjusted
to match the highest priority client.</p>
<p><strong>Configuration Options</strong>.</p>
<ul class="simple">
-<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_SCHED_HPWORK</span></code>. Enables the hight priority work queue.</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_SCHED_HPWORK</span></code>. Enables the high priority work queue.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_SCHED_HPNTHREADS</span></code>. The number of threads in the
high-priority queue’s thread pool. Default: 1</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_SCHED_HPWORKPRIORITY</span></code>. The execution priority of the
diff --git a/content/docs/latest/searchindex.js b/content/docs/latest/searchindex.js
index 54fc043..0aff99a 100644
--- a/content/docs/latest/searchindex.js
+++ b/content/docs/latest/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/feed.xml b/content/feed.xml
index 564bbbe..bada719 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>Wed, 28 Apr 2021 00:13:44 +0000</pubDate>
- <lastBuildDate>Wed, 28 Apr 2021 00:13:44 +0000</lastBuildDate>
+ <pubDate>Thu, 29 Apr 2021 00:13:20 +0000</pubDate>
+ <lastBuildDate>Thu, 29 Apr 2021 00:13:20 +0000</lastBuildDate>
<generator>Jekyll v3.8.5</generator>
<item>