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/05/13 00:45:56 UTC
[incubator-nuttx-website] branch asf-site updated: Publishing web:
1a68dd3405cfbf4f87c58d8ba31efe69f551d462 docs:
4befbdfa4ba22dfd8fd9875db49842854cc258a1
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 667870b Publishing web: 1a68dd3405cfbf4f87c58d8ba31efe69f551d462 docs: 4befbdfa4ba22dfd8fd9875db49842854cc258a1
667870b is described below
commit 667870bee3232c26ade54958903e0afeaa49cebe
Author: Brennan <ba...@brennanashton.com>
AuthorDate: Thu May 13 00:45:07 2021 +0000
Publishing web: 1a68dd3405cfbf4f87c58d8ba31efe69f551d462 docs: 4befbdfa4ba22dfd8fd9875db49842854cc258a1
---
content/docs/10.0.0/index.html | 2 +-
content/docs/10.0.1/index.html | 2 +-
.../latest/_images/ESP32-C3-DevKitC-02-v1.1.png | Bin 0 -> 1227567 bytes
.../latest/_images/ESP32-C3-DevKitM-1-v1.0.png | Bin 0 -> 1529086 bytes
.../docs/latest/_images/imxrt1060-evk-front.jpg | Bin 0 -> 109235 bytes
.../arm/imxrt/boards/imxrt1020-evk/index.rst.txt | 103 ++++
.../arm/imxrt/boards/imxrt1050-evk/index.rst.txt | 129 +++++
.../arm/imxrt/boards/imxrt1060-evk/index.rst.txt | 200 +++++++
.../arm/imxrt/boards/imxrt1064-evk/index.rst.txt | 277 +++++++++
.../esp32c3/boards/esp32c3-devkit/index.rst.txt | 97 ++++
.../platforms/risc-v/esp32c3/index.rst.txt | 127 +++++
content/docs/latest/index.html | 2 +-
content/docs/latest/objects.inv | Bin 31720 -> 32544 bytes
.../{teensy-4.x => imxrt1020-evk}/index.html | 207 +++----
.../{teensy-4.x => imxrt1050-evk}/index.html | 246 ++++----
.../{teensy-4.x => imxrt1060-evk}/index.html | 296 +++++++---
.../arm/imxrt/boards/imxrt1064-evk/index.html | 625 +++++++++++++++++++++
.../arm/imxrt/boards/teensy-4.x/index.html | 8 +-
content/docs/latest/platforms/arm/imxrt/index.html | 12 +-
content/docs/latest/platforms/index.html | 5 +
.../docs/latest/platforms/risc-v/bl602/index.html | 5 +-
.../esp32c3/boards/esp32c3-devkit/index.html | 330 +++++++++++
.../latest/platforms/risc-v/esp32c3/index.html | 445 +++++++++++++++
content/docs/latest/platforms/risc-v/index.html | 2 +
content/docs/latest/platforms/xtensa/index.html | 4 +-
content/docs/latest/reference/user/07_signals.html | 2 +-
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 +-
28 files changed, 2825 insertions(+), 307 deletions(-)
diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index 98b2791..5ed55c2 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: 12 May 21 at 00:34</p>
+<p>Last Updated: 13 May 21 at 00:42</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 d831c80..643ccd4 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: 12 May 21 at 00:34</p>
+<p>Last Updated: 13 May 21 at 00:42</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/_images/ESP32-C3-DevKitC-02-v1.1.png b/content/docs/latest/_images/ESP32-C3-DevKitC-02-v1.1.png
new file mode 100644
index 0000000..88a8994
Binary files /dev/null and b/content/docs/latest/_images/ESP32-C3-DevKitC-02-v1.1.png differ
diff --git a/content/docs/latest/_images/ESP32-C3-DevKitM-1-v1.0.png b/content/docs/latest/_images/ESP32-C3-DevKitM-1-v1.0.png
new file mode 100644
index 0000000..ad0c387
Binary files /dev/null and b/content/docs/latest/_images/ESP32-C3-DevKitM-1-v1.0.png differ
diff --git a/content/docs/latest/_images/imxrt1060-evk-front.jpg b/content/docs/latest/_images/imxrt1060-evk-front.jpg
new file mode 100644
index 0000000..b0335a3
Binary files /dev/null and b/content/docs/latest/_images/imxrt1060-evk-front.jpg differ
diff --git a/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1020-evk/index.rst.txt b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1020-evk/index.rst.txt
new file mode 100644
index 0000000..922e062
--- /dev/null
+++ b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1020-evk/index.rst.txt
@@ -0,0 +1,103 @@
+===============
+i.MX RT1020 EVK
+===============
+
+`i.MX RT1020 EVK <https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt1020-evaluation-kit:MIMXRT1020-EVK>`_
+is an evaluation kit by NXP company. This kit uses the i.MX RT1020 crossover MCU in LQFP144 package with ARM Cortex M7 core.
+
+Features
+========
+
+- Processor
+ - MIMXRT1021DAG5A processor
+- Memory
+ - 256 Mb SDRAM memory
+ - 64 Mb QSPI Flash
+ - TF socket for SD card
+- Display and Audio
+ - Audio CODEC
+ - 4-pole audio headphone jack
+ - External speaker connection
+ - Microphone
+- Connectivity
+ - Micro USB host and OTG connectors
+ - Ethernet (10/100T) connector
+ - CAN transceivers
+ - Arduino® interface
+
+Serial Console
+==============
+
+The EVK default console is on LPUART1, which is multiplexed onto
+the debug port (either OpenSDA or SEGGER JLink).
+
+It runs at 115200,n,8,1.
+
+LEDs and Buttons
+================
+
+LEDs
+----
+
+There is one user accessible LED status indicator located on the 1020-EVK,
+USERLED. The function of the LEDs include:
+
+=== ============ ======
+Pin Description Colour
+=== ============ ======
+D3 Power Supply Green
+D5 User LED Green
+D15 Reset LED Red
+=== ============ ======
+
+This LED is 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/imxrt_autoleds.c. The LED is used to encode
+OS-related events as documented in board.h
+
+================ ======================= =====
+SYMBOL Meaning LED
+================ ======================= =====
+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 N/C
+LED_SIGNAL In a signal handler N/C
+LED_ASSERTION An assertion failed N/C
+LED_PANIC The system has crashed FLASH
+================ ======================= =====
+
+Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
+2Hz, then a fatal error has been detected and the system has halted.
+
+
+Buttons
+-------
+
+This IMXRT board has three external buttons
+
+=== ============== ========================
+SW2 (IRQ88, ONOFF) Not on a GPIO, No muxing
+SW3 (IRQ88, POR) Not on a GPIO, No muxing
+SW4 (IRQ88, USER) Wakeup, GPIO5-0
+=== ============== ========================
+
+Configurations
+==============
+
+netnsh
+------
+
+This configuration is similar to the nsh configuration except that is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
+focused on network-related testing.
+
+nsh
+---
+
+Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.
diff --git a/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1050-evk/index.rst.txt b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1050-evk/index.rst.txt
new file mode 100644
index 0000000..ad90ec8
--- /dev/null
+++ b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1050-evk/index.rst.txt
@@ -0,0 +1,129 @@
+===============
+i.MX RT1050 EVK
+===============
+
+`i.MX RT1050 EVK <https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt1050-evaluation-kit:MIMXRT1050-EVK>`_
+is an evaluation kit by NXP company. This kit uses the i.MX RT1050 crossover MCU with ARM Cortex M7 core.
+
+Features
+========
+
+- Processor
+ - MIMXRT1052DVL6A processor
+- Memory
+ - 256 Mb SDRAM memory
+ - 512 Mb Hyper Flash
+ - Footprint for QSPI Flash
+ - TF socket for SD card
+- Display and Audio
+ - Parallel LCD connector
+ - Camera connector
+ - Audio CODEC
+ - 4-pole audio headphone jack
+ - External speaker connection
+ - Microphone
+ - SPDIF connector
+- Connectivity
+ - Micro USB host and OTG connectors
+ - Ethernet (10/100T) connector
+ - CAN transceivers
+ - Arduino® interface
+
+Serial Console
+==============
+
+Virtual console port provided by OpenSDA:
+
+========= ============= ==========
+UART1_TXD GPIO_AD_B0_12 LPUART1_TX
+UART1_RXD GPIO_AD_B0_13 LPUART1_RX
+========= ============= ==========
+
+Arduino RS-232 Shield:
+
+=== == ======= ============= ==========
+J22 D0 UART_RX GPIO_AD_B1_07 LPUART3_RX
+J22 D1 UART_TX GPIO_AD_B1_06 LPUART3_TX
+=== == ======= ============= ==========
+
+LEDs and buttons
+================
+
+LEDs
+----
+
+There are four LED status indicators located on the EVK Board. The
+functions of these LEDs include:
+
+=== ============
+Pin Description
+=== ============
+D3 Power Supply
+D15 Reset LED
+D16 OpenSDA
+D18 User LED
+=== ============
+
+Only a single LED, D18, is under software control. It connects to
+GPIO_AD_B0_09 which is shared with JTAG_TDI and ENET_RST
+
+This LED is 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/imxrt_autoleds.c. The LED is used to encode
+OS-related events as follows:
+
+================ ======================= =====
+SYMBOL Meaning LED
+================ ======================= =====
+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 N/C
+LED_SIGNAL In a signal handler N/C
+LED_ASSERTION An assertion failed N/C
+LED_PANIC The system has crashed FLASH
+================ ======================= =====
+
+Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
+2Hz, then a fatal error has been detected and the system has halted.
+
+Buttons
+-------
+
+There are four user interface switches on the MIMXRT1050 EVK Board:
+
+ - SW1: Power Switch (slide switch)
+ - SW2: ON/OFF Button
+ - SW3: Reset button
+ - SW8: User button
+
+Only the user button is available to the software. It is sensed on the
+WAKEUP pin which will be pulled low when the button is pressed.
+
+Configurations
+==============
+
+knsh
+----
+
+This is identical to the nsh configuration below except that NuttX
+is built as a protected mode, monolithic module and the user applications
+are built separately. For further information about compiling and
+running this configuration please refer to imxrt1064-evk documentation.
+
+netnsh
+------
+
+This configuration is similar to the nsh configuration except that is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
+focused on network-related testing.
+
+nsh
+---
+
+Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.
diff --git a/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1060-evk/index.rst.txt b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1060-evk/index.rst.txt
new file mode 100644
index 0000000..8ee9eee
--- /dev/null
+++ b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1060-evk/index.rst.txt
@@ -0,0 +1,200 @@
+===============
+i.MX RT1060 EVK
+===============
+
+`i.MX RT1060 EVK <https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/mimxrt1060-evk-i-mx-rt1060-evaluation-kit:MIMXRT1060-EVK>`_
+is an evaluation kit by NXP company. This kit uses the i.MX RT1060 crossover MCU with ARM Cortex M7 core.
+
+.. figure:: imxrt1060-evk-front.jpg
+ :align: center
+ :width: 50%
+
+ i.MX RT1060 EVK
+
+Features
+========
+
+- Processor
+ - MIMXRT1062DVL6A processor
+- Memory
+ - 1 Mb OCRAM memory
+ - 256 Mb SDRAM memory
+ - 512 Mb Hyper Flash - Populated but 0 ohm DNP
+ - 64 Mb QSPI Flash
+ - TF socket for SD card
+- Display and Audio
+ - Parallel LCD connector
+ - Camera connector
+ - Audio CODEC
+ - 4-pole audio headphone jack
+ - External speaker connection
+ - Microphone
+ - SPDIF connector
+- Connectivity
+ - Micro USB host and OTG connectors
+ - Ethernet (10/100T) connector
+ - CAN transceivers (including one CAN FD)
+ - Arduino® interface
+- Sensors
+ - FXOS8700CQ 6-Axis Ecompass (3-Axis Mag, 3-Axis Accel)
+
+Serial Console
+==============
+
+Virtual console port provided by OpenSDA:
+
+========= ============= ==========
+UART1_TXD GPIO_AD_B0_12 LPUART1_TX
+UART1_RXD GPIO_AD_B0_13 LPUART1_RX
+========= ============= ==========
+
+Arduino RS-232 Shield:
+
+=== == ======= ============= ==========
+J22 D0 UART_RX GPIO_AD_B1_07 LPUART3_RX
+J22 D1 UART_TX GPIO_AD_B1_06 LPUART3_TX
+=== == ======= ============= ==========
+
+LEDs and buttons
+================
+
+LEDs
+----
+
+There are four LED status indicators located on the EVK Board. The
+functions of these LEDs include:
+
+=== ============
+Pin Description
+=== ============
+D3 Power Supply
+D18 User LED
+D20 OpenSDA
+D21 Reset LED
+=== ============
+
+Only a single LED, D18, is under software control. It connects to
+GPIO_AD_B0_09 which is shared with JTAG_TDI and ENET_RST
+
+This LED is 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/imxrt_autoleds.c. The LED is used to encode
+OS-related events as follows:
+
+================ ======================= =====
+SYMBOL Meaning LED
+================ ======================= =====
+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 N/C
+LED_SIGNAL In a signal handler N/C
+LED_ASSERTION An assertion failed N/C
+LED_PANIC The system has crashed FLASH
+================ ======================= =====
+
+Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
+2Hz, then a fatal error has been detected and the system has halted.
+
+Buttons
+-------
+
+There are five user interface switches on the MIMXRT1050 EVK Board:
+
+ - SW1: Power Switch (slide switch fir power from J2)
+ - SW2: ON/OFF Button
+ - SW3: Power-on Reset button state forces to reset the system power except SNVS domain
+ - SW9: Reset button
+ - SW8: User button GPIO5-00
+
+Only the user button is available to the software. It is sensed on the
+WAKEUP pin which will be pulled low when the button is pressed.
+
+
+J-Link External Debug Probe
+===========================
+
+Install the J-Link Debug Host Tools and make sure they are in your search path.
+
+Attach a J-Link 20-pin connector to J21. Check that jumpers J47 and J48 are
+off (they are on by default when boards ship from the factory) to ensure SWD
+signals are disconnected from the OpenSDA microcontroller.
+
+Configurations
+==============
+
+can
+---
+
+This is an nsh configuration (see below) with added support of CAN driver.
+FlexCAN3 is chosen as default, the change can be made at System type peripheral
+selection. Please note that only FlexCAN3 and FlexCAN2 is available on this board.
+
+Bitrate and sample point can be also changed at System type peripheral selection,
+basic values are 1 MHz for bitrate and 0.80 for sample point. The FlexCAN driver
+for imxrt runs at 80 MHz clock frequency.
+
+The configuration also includes CAN utilities as candump and cansend.
+
+canfd
+-----
+
+This is an nsh configuration (see below) with added support of CAN_FD driver.
+FlexCAN3 is chosen as default, please note that only FlexCAN3 is capable of
+providing CAN_FD support.
+
+Bitrate and sample point can be also changed at System type peripheral selection,
+basic values are 1 MHz for bitrate and 0.80 for sample point for arbitration phase
+and 4 MHz (bitrate) and 0.90 (sample point) for data phase. The FlexCAN driver
+for imxrt runs at 80 MHz clock frequency.
+
+The configuration also includes CAN utilities as candump and cansend.
+
+knsh
+----
+
+This is identical to the nsh configuration below except that NuttX
+is built as a protected mode, monolithic module and the user applications
+are built separately. For further information about compiling and
+running this configuration please refer to imxrt1064-evk documentation.
+
+netnsh
+------
+
+This configuration is similar to the nsh configuration except that is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
+focused on network-related testing.
+
+nsh
+---
+
+Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.
+
+lvgl
+----
+
+Configures the Littlev graphic library (lvgl) demo located under
+examples/lvgldemo. This configuration needs the optional LCD model
+RK043FN02H-CT from NXP. The LCD panel comes with the integrated
+capacitive touchscreen sensor FT5336GQQ connected to the LPI2C1 bus,
+address 0x38. NuttX support such touchscreen device via the driver
+ft5x06 (drivers/input/ft5x06.c). At the moment only the polling
+method is available, the board features an interrupt line connected
+to the touchscreen sensor IC.
+
+IMXRT1060 MCU provides the integrated LCD driver.
+
+The LCD panel features:
+ - size 4.3"
+ - resolution 480×272 RGB
+ - backlight driver
+ - dimensions [mm]: 105.5 (W) x 67.2(H) x 4.35(D) Max.
+
+To run the lvgl demo please type "lvgldemo" at nsh prompt::
+
+ nsh> lvgldemo
diff --git a/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1064-evk/index.rst.txt b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1064-evk/index.rst.txt
new file mode 100644
index 0000000..34aaa7c
--- /dev/null
+++ b/content/docs/latest/_sources/platforms/arm/imxrt/boards/imxrt1064-evk/index.rst.txt
@@ -0,0 +1,277 @@
+===============
+i.MX RT1064 EVK
+===============
+
+`i.MX RT1064 EVK <https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/mimxrt1064-evk-i-mx-rt1064-evaluation-kit:MIMXRT1064-EVK>`_
+is an evaluation kit by NXP company. This kit uses the i.MX RT1064 crossover MCU with ARM Cortex M7 core.
+
+Features
+========
+
+- Processor
+ - MIMXRT1066DVL6A processor
+- Memory
+ - 1 Mb OCRAM memory
+ - 256 Mb SDRAM memory
+ - 512 Mb Hyper Flash - Populated but 0 ohm DNP
+ - 64 Mb QSPI Flash
+ - TF socket for SD card
+- Display and Audio
+ - Parallel LCD connector
+ - Camera connector
+ - Audio CODEC
+ - 4-pole audio headphone jack
+ - External speaker connection
+ - Microphone
+ - SPDIF connector
+- Connectivity
+ - Micro USB host and OTG connectors
+ - Ethernet (10/100T) connector
+ - CAN transceivers
+ - Arduino® interface
+- Sensors
+ - FXOS8700CQ 6-Axis Ecompass (3-Axis Mag, 3-Axis Accel)
+
+Serial Console
+==============
+
+Virtual console port provided by OpenSDA:
+
+========= ============= ==========
+UART1_TXD GPIO_AD_B0_12 LPUART1_TX
+UART1_RXD GPIO_AD_B0_13 LPUART1_RX
+========= ============= ==========
+
+Arduino RS-232 Shield:
+
+=== == ======= ============= ==========
+J22 D0 UART_RX GPIO_AD_B1_07 LPUART3_RX
+J22 D1 UART_TX GPIO_AD_B1_06 LPUART3_TX
+=== == ======= ============= ==========
+
+LEDs and buttons
+================
+
+LEDs
+----
+
+There are four LED status indicators located on the EVK Board. The
+functions of these LEDs include:
+
+=== ============
+Pin Description
+=== ============
+D3 Power Supply
+D18 User LED
+D20 OpenSDA
+D21 Reset LED
+=== ============
+
+Only a single LED, D18, is under software control. It connects to
+GPIO_AD_B0_09 which is shared with JTAG_TDI and ENET_RST
+
+This LED is 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/imxrt_autoleds.c. The LED is used to encode
+OS-related events as follows:
+
+================ ======================= =====
+SYMBOL Meaning LED
+================ ======================= =====
+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 N/C
+LED_SIGNAL In a signal handler N/C
+LED_ASSERTION An assertion failed N/C
+LED_PANIC The system has crashed FLASH
+================ ======================= =====
+
+Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
+2Hz, then a fatal error has been detected and the system has halted.
+
+Buttons
+-------
+
+There are five user interface switches on the MIMXRT1050 EVK Board:
+
+ - SW1: Power Switch (slide switch fir power from J2)
+ - SW2: ON/OFF Button
+ - SW3: Power-on Reset button state forces to reset the system power except SNVS domain
+ - SW9: Reset button
+ - SW8: User button GPIO5-00
+
+Only the user button is available to the software. It is sensed on the
+WAKEUP pin which will be pulled low when the button is pressed.
+
+
+J-Link External Debug Probe
+===========================
+
+Install the J-Link Debug Host Tools and make sure they are in your search path.
+
+Attach a J-Link 20-pin connector to J21. Check that jumpers J47 and J48 are
+off (they are on by default when boards ship from the factory) to ensure SWD
+signals are disconnected from the OpenSDA microcontroller.
+
+Configurations
+==============
+
+can
+---
+
+This is an nsh configuration (see below) with added support of CAN driver.
+FlexCAN3 is chosen as default, the change can be made at System type peripheral
+selection. Please note that only FlexCAN3 and FlexCAN2 is available on this board.
+
+Bitrate and sample point can be also changed at System type peripheral selection,
+basic values are 1 MHz for bitrate and 0.80 for sample point. The FlexCAN driver
+for imxrt runs at 80 MHz clock frequency.
+
+The configuration also includes CAN utilities as candump and cansend.
+
+canfd
+-----
+
+This is an nsh configuration (see below) with added support of CAN_FD driver.
+FlexCAN3 is chosen as default, please note that only FlexCAN3 is capable of
+providing CAN_FD support.
+
+Bitrate and sample point can be also changed at System type peripheral selection,
+basic values are 1 MHz for bitrate and 0.80 for sample point for arbitration phase
+and 4 MHz (bitrate) and 0.90 (sample point) for data phase. The FlexCAN driver
+for imxrt runs at 80 MHz clock frequency.
+
+The configuration also includes CAN utilities as candump and cansend.
+
+knsh
+----
+
+This is identical to the nsh configuration below except that NuttX
+is built as a protected mode, monolithic module and the user applications
+are built separately. It is recommends to use a special make command;
+not just 'make' but make with the following two arguments:
+
+.. code-block:: console
+
+ $ make pass1 pass2
+
+In the normal case (just 'make'), make will attempt to build both user-
+and kernel-mode blobs more or less interleaved. This actual works!
+However, for me it is very confusing so I prefer the above make command:
+Make the user-space binaries first (pass1), then make the kernel-space
+binaries (pass2)
+
+NOTES:
+
+At the end of the build, there will be several files in the top-level
+NuttX build directory:
+
+PASS1:
+ - nuttx_user.elf - The pass1 user-space ELF file
+ - nuttx_user.hex - The pass1 Intel HEX format file (selected in defconfig)
+ - User.map - Symbols in the user-space ELF file
+
+PASS2:
+ - nuttx - The pass2 kernel-space ELF file
+ - nuttx.hex - The pass2 Intel HEX file (selected in defconfig)
+ - System.map - Symbols in the kernel-space ELF file
+
+The J-Link programmer will except files in .hex, .mot, .srec, and .bin
+formats.
+
+Combining .hex files. If you plan to use the .hex files with your
+debugger or FLASH utility, then you may need to combine the two hex
+files into a single .hex file. Here is how you can do that.
+
+The 'tail' of the nuttx.hex file should look something like this
+(with my comments added beginning with #):
+
+.. code-block:: console::
+
+ $ tail nuttx.hex
+ #xx xxxx 00 data records
+ ...
+ :10 C93C 00 000000000040184000C2010000000000 90
+ :10 C94C 00 2400080000801B4000C01B4000001C40 5D
+ :10 C95C 00 00401C4000000C4050BF0060FF000100 74
+ #xx xxxx 05 Start Linear Address Record
+ :04 0000 05 6000 02C1 D4
+ #xx xxxx 01 End Of File record
+ :00 0000 01 FF
+
+Use an editor such as vi to remove the 05 and 01 records.
+
+The 'head' of the nuttx_user.hex file should look something like
+this (again with my comments added beginning with #):
+
+.. code-block:: console::
+
+ $ head nuttx_user.hex
+ #xx xxxx 04 Extended Linear Address Record
+ :02 0000 04 6020 7A
+ #xx xxxx 00 data records
+ :10 0000 00 8905206030002060F2622060FC622060 80
+ :10 0010 00 0000242008002420080024205C012420 63
+ :10 0020 00 140024203D0020603100206071052060 14
+ ...
+
+Nothing needs to be done here. The nuttx_user.hex file should
+be fine.
+
+Combine the edited nuttx.hex and un-edited nuttx_user.hex
+file to produce a single combined hex file:
+
+.. code-block:: console::
+
+ $ cat nuttx.hex nuttx_user.hex >combined.hex
+
+Then use the combined.hex file with the to write the FLASH image.
+If you do this a lot, you will probably want to invest a little time
+to develop a tool to automate these steps.
+
+STATUS: This configuration was added on 8 June 2018 primarily to assure
+that all of the components are in place to support the PROTECTED mode
+build. This configuration, however, has not been verified as of this
+writing.
+
+netnsh
+------
+
+This configuration is similar to the nsh configuration except that is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
+focused on network-related testing.
+
+nsh
+---
+
+Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.
+
+lvgl
+----
+
+Configures the Littlev graphic library (lvgl) demo located under
+examples/lvgldemo. This configuration needs the optional LCD model
+RK043FN02H-CT from NXP. The LCD panel comes with the integrated
+capacitive touchscreen sensor FT5336GQQ connected to the LPI2C1 bus,
+address 0x38. NuttX support such touchscreen device via the driver
+ft5x06 (drivers/input/ft5x06.c). At the moment only the polling
+method is available, the board features an interrupt line connected
+to the touchscreen sensor IC.
+
+IMXRT1064 MCU provides the integrated LCD driver.
+
+The LCD panel features:
+ - size 4.3"
+ - resolution 480×272 RGB
+ - backlight driver
+ - dimensions [mm]: 105.5 (W) x 67.2(H) x 4.35(D) Max.
+
+To run the lvgl demo please type "lvgldemo" at nsh prompt::
+
+ nsh> lvgldemo
diff --git a/content/docs/latest/_sources/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.rst.txt b/content/docs/latest/_sources/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.rst.txt
new file mode 100644
index 0000000..180245a
--- /dev/null
+++ b/content/docs/latest/_sources/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.rst.txt
@@ -0,0 +1,97 @@
+===============
+ESP32-C3 DevKit
+===============
+
+The ESP32-C3 DevKit is an entry-level development board equipped with either
+an ESP32-C3-WROOM-02 or an ESP32-C3-MINI-1.
+ESP32-C3-WROOM-02 and ESP32-C3-MINI-1 are SoMs based on the RISC-V ESP32-C3 CPU.
+
+Most of the I/O pins are broken out to the pin headers on both sides for easy
+interfacing. Developers can either connect peripherals with jumper wires or
+mount ESP32-C3 DevKit on a breadboard.
+
+.. list-table::
+ :align: center
+
+ * - .. figure:: ESP32-C3-DevKitC-02-v1.1.png
+ :align: center
+
+ ESP32-C3-DevKitC-02
+
+ - .. figure:: ESP32-C3-DevKitM-1-v1.0.png
+ :align: center
+
+ ESP32-C3-DevKitM-1
+
+Buttons and LEDs
+================
+
+Buttons
+-------
+There are two buttons labeled Boot and RST. The RST button is not available
+to software. It pulls the chip enable line that doubles as a reset line.
+
+The BOOT button is connected to IO9. On reset it is used as a strapping
+pin to determine whether the chip boots normally or into the serial
+bootloader. After reset, however, the BOOT button can be used for software
+input.
+
+LEDs
+----
+There is one on-board LED that indicates the presence of power.
+Another WS2812 LED is connected to GPIO8 and is available for software.
+
+Configurations
+==============
+
+nsh
+---
+
+Basic configuration to run the NuttShell (nsh).
+
+gpio
+____
+
+This is a test for the GPIO driver. It uses GPIO1 and GPIO2 as outputs and
+GPIO9 as an interrupt pin.
+
+At the nsh, we can turn the outputs on and off with the following::
+
+ nsh> gpio -o 1 /dev/gpout0
+ nsh> gpio -o 1 /dev/gpout1
+
+ nsh> gpio -o 0 /dev/gpout0
+ nsh> gpio -o 0 /dev/gpout1
+
+We can use the interrupt pin to send a signal when the interrupt fires::
+
+ nsh> gpio -w 14 /dev/gpint2
+
+The pin is configured as a rising edge interrupt, so after issuing the
+above command, connect it to 3.3V.
+
+watchdog
+--------
+
+This configuration tests the watchdog timers. It includes the 2 MWDTS,
+adds driver support, registers the WDTs as devices and includes the watchdog
+example application.
+
+To test it, just run the following command::
+
+ nsh> wdog -i /dev/watchdogX
+
+Where X is the watchdog instance.
+
+watcher
+-------
+
+This configuration tests the watchdog timers in the capture mode.
+It includes the 2 MWDTS, adds driver support, registers the WDTs as devices
+and includes the watcher and watched example applications.
+
+To test it, just run the following command::
+
+ nsh> watcher
+ nsh> watched
+
diff --git a/content/docs/latest/_sources/platforms/risc-v/esp32c3/index.rst.txt b/content/docs/latest/_sources/platforms/risc-v/esp32c3/index.rst.txt
new file mode 100644
index 0000000..3a9c9ca
--- /dev/null
+++ b/content/docs/latest/_sources/platforms/risc-v/esp32c3/index.rst.txt
@@ -0,0 +1,127 @@
+==================
+Espressif ESP32-C3
+==================
+
+The ESP32-C3 is an ultra-low-power and highly integrated SoC with a RISC-V
+core and supports 2.4 GHz Wi-Fi and Bluetooth Low Energy.
+
+* Address Space
+ - 800 KB of internal memory address space accessed from the instruction bus
+ - 560 KB of internal memory address space accessed from the data bus
+ - 1016 KB of peripheral address space
+ - 8 MB of external memory virtual address space accessed from the instruction bus
+ - 8 MB of external memory virtual address space accessed from the data bus
+ - 480 KB of internal DMA address space
+* Internal Memory
+ - 384 KB ROM
+ - 400 KB SRAM (16 KB can be configured as Cache)
+ - 8 KB of SRAM in RTC
+* External Memory
+ - Up to 16 MB of external flash
+* Peripherals
+ - 35 peripherals
+* GDMA
+ - 7 modules are capable of DMA operations.
+
+ESP32-C3 Toolchain
+==================
+
+A generic RISC-V toolchain can be used to build ESP32-C3 projects.
+SiFive's toolchain can be downloaded from: https://static.dev.sifive.com/dev-tools/riscv64-unknown-elf-gcc-8.3.0-2019.08.0-x86_64-linux-ubuntu14.tar.gz
+
+Second stage bootloader and partition table
+===========================================
+
+The NuttX port for now relies on IDF's second stage bootloader to carry on some hardware
+initializations. The binaries for the bootloader and the partition table can be found in
+this repository: https://github.com/espressif/esp-nuttx-bootloader
+That repository contains a dummy IDF project that's used to build the bootloader and
+partition table, these are then presented as Github assets and can be downloaded
+from: https://github.com/espressif/esp-nuttx-bootloader/releases
+Download ``bootloader-esp32c3.bin`` and ``partition-table-esp32c3.bin`` and place them
+in a folder, the path to this folder will be used later to program them. This
+can be: ``../esp-bins``
+
+Building and flashing
+=====================
+
+First make sure that ``esptool.py`` is installed. This tool is used to convert
+the ELF to a compatible ESP32 image and to flash the image into the board.
+It can be installed with: ``pip install esptool``.
+
+Configure the NUttX project: ``./tools/configure.sh esp32c3-devkit:nsh``
+Run ``make`` to build the project. Note that the conversion mentioned above is
+included in the build process.
+The `esptool.py` command to flash all the binaries is::
+
+ esptool.py --chip esp32c3 --port /dev/ttyUSBXX --baud 921600 write_flash 0x0 bootloader.bin 0x8000 partition-table.bin 0x10000 nuttx.bin
+
+However, this is also included in the build process and we can build and flash with::
+
+ make download ESPTOOL_PORT=<port> ESPTOOL_BINDIR=../esp-bins
+
+Where ``<port>`` is typically ``/dev/ttyUSB0`` or similar and ``../esp-bins`` is
+the path to the folder containing the bootloader and the partition table
+for the ESP32-C3 as explained above.
+Note that this step is required only one time. Once the bootloader and partition
+table are flashed, we don't need to flash them again. So subsequent builds
+would just require: ``make download ESPTOOL_PORT=/dev/ttyUSBXX``
+
+Debugging with OpenOCD
+======================
+
+Download and build OpenOCD from Espressif, that can be found in
+https://github.com/espressif/openocd-esp32
+
+If you have an ESP32-C3 ECO3, no external JTAG is required to debug, the ESP32-C3
+integrates a USB-to-JTAG adapter.
+
+OpenOCD can then be used::
+
+ openocd -c 'set ESP_RTOS none' -f board/esp32c3-builtin.cfg
+
+For versions prior to ESP32-C3 ECO3, an external JTAG adapter is needed.
+It can be connected as follows::
+
+ TMS -> GPIO4
+ TDI -> GPIO5
+ TCK -> GPIO6
+ TDO -> GPIO7
+
+Furthermore, an efuse needs to be burnt to be able to debug::
+
+ espefuse.py -p <port> burn_efuse DIS_USB_JTAG
+
+OpenOCD can then be used::
+
+ openocd -c 'set ESP_RTOS none' -f board/esp32c3-ftdi.cfg
+
+Peripheral Support
+==================
+
+The following list indicates the state of peripherals' support in NuttX:
+
+========== ======= =====
+Peripheral Support NOTES
+========== ======= =====
+GPIO Yes
+UART Yes
+SPI Yes
+I2C Yes
+DMA Yes
+Wifi Yes
+SPIFLASH Yes
+Timers Yes
+Watchdog Yes
+RTC No
+RNG Yes
+AES No
+eFuse No
+ADC No
+Bluetooth No
+LED_PWM No
+SHA No
+RSA No
+========== ======= =====
+
+
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index 17cde7b..a276f3f 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: 12 May 21 at 00:34</p>
+<p>Last Updated: 13 May 21 at 00:43</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/objects.inv b/content/docs/latest/objects.inv
index 0a7b9f8..d25193b 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/imxrt/boards/teensy-4.x/index.html b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1020-evk/index.html
similarity index 63%
copy from content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
copy to content/docs/latest/platforms/arm/imxrt/boards/imxrt1020-evk/index.html
index 7f4d903..7fa977d 100644
--- a/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
+++ b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1020-evk/index.html
@@ -26,7 +26,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>Teensy-4.x — NuttX latest documentation</title>
+ <title>i.MX RT1020 EVK — NuttX latest documentation</title>
@@ -61,7 +61,7 @@
<link rel="index" title="Index" href="../../../../../genindex.html" />
<link rel="search" title="Search" href="../../../../../search.html" />
- <link rel="next" title="Nordic nRF52" href="../../../nrf52/index.html" />
+ <link rel="next" title="i.MX RT1050 EVK" href="../imxrt1050-evk/index.html" />
<link rel="prev" title="i.MX RT" href="../../index.html" />
</head>
@@ -131,7 +131,11 @@
<li class="toctree-l4"><a class="reference internal" href="../../index.html#data-and-instruction-cache">Data and Instruction Cache</a></li>
<li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
<li class="toctree-l4 current"><a class="reference internal" href="../../index.html#supported-boards">Supported Boards</a><ul class="current">
-<li class="toctree-l5 current"><a class="current reference internal" href="#">Teensy-4.x</a></li>
+<li class="toctree-l5 current"><a class="current reference internal" href="#">i.MX RT1020 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1050-evk/index.html">i.MX RT1050 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1060-evk/index.html">i.MX RT1060 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1064-evk/index.html">i.MX RT1064 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../teensy-4.x/index.html">Teensy-4.x</a></li>
</ul>
</li>
</ul>
@@ -204,13 +208,13 @@
<li><a href="../../index.html">i.MX RT</a> »</li>
- <li>Teensy-4.x</li>
+ <li>i.MX RT1020 EVK</li>
<li class="wy-breadcrumbs-aside">
- <a href="../../../../../_sources/platforms/arm/imxrt/boards/teensy-4.x/index.rst.txt" rel="nofollow"> View page source</a>
+ <a href="../../../../../_sources/platforms/arm/imxrt/boards/imxrt1020-evk/index.rst.txt" rel="nofollow"> View page source</a>
</li>
@@ -223,65 +227,94 @@
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
- <div class="section" id="teensy-4-x">
-<h1>Teensy-4.x<a class="headerlink" href="#teensy-4-x" title="Permalink to this headline">¶</a></h1>
-<p>The <a class="reference external" href="https://www.pjrc.com/store/teensy40.html">Teensy 4.0</a> and <a class="reference external" href="https://www.pjrc.com/store/teensy41.html">Teensy 4.1</a>
-are development boards from PJRC. Both boards use i.MX RT1060 MCU, feature several I/Os pins and on-board LED.</p>
+ <div class="section" id="i-mx-rt1020-evk">
+<h1>i.MX RT1020 EVK<a class="headerlink" href="#i-mx-rt1020-evk" title="Permalink to this headline">¶</a></h1>
+<p><a class="reference external" href="https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt1020-evaluation-kit:MIMXRT1020-EVK">i.MX RT1020 EVK</a>
+is an evaluation kit by NXP company. This kit uses the i.MX RT1020 crossover MCU in LQFP144 package with ARM Cortex M7 core.</p>
<div class="section" id="features">
<h2>Features<a class="headerlink" href="#features" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li><dl class="simple">
<dt>Processor</dt><dd><ul>
-<li><p>MIMXRT1062DVL6A processor</p></li>
+<li><p>MIMXRT1021DAG5A processor</p></li>
</ul>
</dd>
</dl>
</li>
<li><dl class="simple">
<dt>Memory</dt><dd><ul>
-<li><p>1 MB RAM memory</p></li>
-<li><p>2 MB Flash (Teensy 4.0)</p></li>
-<li><p>8 MB Flash (Teensy 4.1)</p></li>
-<li><p>1 SDIO (4 bit) native SD</p></li>
+<li><p>256 Mb SDRAM memory</p></li>
+<li><p>64 Mb QSPI Flash</p></li>
+<li><p>TF socket for SD card</p></li>
</ul>
</dd>
</dl>
</li>
<li><dl class="simple">
-<dt>Connectivity</dt><dd><ul>
-<li><p>Micro USB host</p></li>
-<li><p>CAN transceivers</p></li>
-<li><p>UART, SPI, I2C</p></li>
-<li><p>PWM output pins</p></li>
-<li><p>10/100 Mb Ethernet (Teensy 4.1 only)</p></li>
-<li><p>Digital audio in/out</p></li>
+<dt>Display and Audio</dt><dd><ul>
+<li><p>Audio CODEC</p></li>
+<li><p>4-pole audio headphone jack</p></li>
+<li><p>External speaker connection</p></li>
+<li><p>Microphone</p></li>
</ul>
</dd>
</dl>
</li>
-</ul>
-</div>
-<div class="section" id="leds">
-<h2>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h2>
-<p>There are two LED status indicators located on the Teensy-4.x board.
-The functions of these LEDs include:</p>
-<ul class="simple">
<li><dl class="simple">
-<dt>RED LED (loading status)</dt><dd><ul>
-<li><p>dim: ready</p></li>
-<li><p>bright: writing</p></li>
-<li><p>blink: no USB</p></li>
+<dt>Connectivity</dt><dd><ul>
+<li><p>Micro USB host and OTG connectors</p></li>
+<li><p>Ethernet (10/100T) connector</p></li>
+<li><p>CAN transceivers</p></li>
+<li><p>Arduino® interface</p></li>
</ul>
</dd>
</dl>
</li>
-<li><p>USER LED (D3)</p></li>
</ul>
-<p>Only a single LED, D3, is under software control.</p>
+</div>
+<div class="section" id="serial-console">
+<h2>Serial Console<a class="headerlink" href="#serial-console" title="Permalink to this headline">¶</a></h2>
+<p>The EVK default console is on LPUART1, which is multiplexed onto
+the debug port (either OpenSDA or SEGGER JLink).</p>
+<p>It runs at 115200,n,8,1.</p>
+</div>
+<div class="section" id="leds-and-buttons">
+<h2>LEDs and Buttons<a class="headerlink" href="#leds-and-buttons" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="leds">
+<h3>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h3>
+<p>There is one user accessible LED status indicator located on the 1020-EVK,
+USERLED. The function of the LEDs include:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 14%" />
+<col style="width: 57%" />
+<col style="width: 29%" />
+</colgroup>
+<thead>
+<tr class="row-odd"><th class="head"><p>Pin</p></th>
+<th class="head"><p>Description</p></th>
+<th class="head"><p>Colour</p></th>
+</tr>
+</thead>
+<tbody>
+<tr class="row-even"><td><p>D3</p></td>
+<td><p>Power Supply</p></td>
+<td><p>Green</p></td>
+</tr>
+<tr class="row-odd"><td><p>D5</p></td>
+<td><p>User LED</p></td>
+<td><p>Green</p></td>
+</tr>
+<tr class="row-even"><td><p>D15</p></td>
+<td><p>Reset LED</p></td>
+<td><p>Red</p></td>
+</tr>
+</tbody>
+</table>
<p>This LED is not used by the board port unless CONFIG_ARCH_LEDS is
-defined. In that case, the usage by the board port is defined in
+defined. In that case, the usage by the board port is defined in
include/board.h and src/imxrt_autoleds.c. The LED is used to encode
-OS-related events as follows:</p>
+OS-related events as documented in board.h</p>
<table class="docutils align-default">
<colgroup>
<col style="width: 36%" />
@@ -329,77 +362,51 @@ OS-related events as follows:</p>
</tr>
</tbody>
</table>
-<p>Thus if the LED is statically on, NuttX has successfully booted and is,
-apparently, running normally. If the LED is flashing at approximately
+<p>Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
2Hz, then a fatal error has been detected and the system has halted.</p>
</div>
-<div class="section" id="configurations">
-<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
-<div class="section" id="nsh-4-0">
-<h3>nsh-4.0<a class="headerlink" href="#nsh-4-0" title="Permalink to this headline">¶</a></h3>
-<p>Configures the NuttShell (nsh) located at examples/nsh for Teensy 4.0.
-This NSH configuration is focused on low level, command-line driver testing.
-Built-in applications are supported, but none are enabled. NutShells then
-runs on USB console.</p>
-</div>
-<div class="section" id="nsh-4-1">
-<h3>nsh-4.1<a class="headerlink" href="#nsh-4-1" title="Permalink to this headline">¶</a></h3>
-<p>Configures the NuttShell (nsh) located at examples/nsh for Teensy 4.1.
-This NSH configuration is focused on low level, command-line driver testing.
-Built-in applications are supported, but none are enabled. NutShells then
-runs USB console.</p>
+<div class="section" id="buttons">
+<h3>Buttons<a class="headerlink" href="#buttons" title="Permalink to this headline">¶</a></h3>
+<p>This IMXRT board has three external buttons</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 7%" />
+<col style="width: 34%" />
+<col style="width: 59%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><p>SW2</p></td>
+<td><p>(IRQ88, ONOFF)</p></td>
+<td><p>Not on a GPIO, No muxing</p></td>
+</tr>
+<tr class="row-even"><td><p>SW3</p></td>
+<td><p>(IRQ88, POR)</p></td>
+<td><p>Not on a GPIO, No muxing</p></td>
+</tr>
+<tr class="row-odd"><td><p>SW4</p></td>
+<td><p>(IRQ88, USER)</p></td>
+<td><p>Wakeup, GPIO5-0</p></td>
+</tr>
+</tbody>
+</table>
</div>
-<div class="section" id="can-4-1">
-<h3>can-4.1<a class="headerlink" href="#can-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-CAN driver. All FlexCANs (CAN1, CAN2, CAN3) are chosen as default. FlexCAN3
-is FD capable. Please note that device driver name if counted from zero.
-That means for CAN1 -> can0, CAN2 -> can1 and CAN3 -> can2</p>
-<p>Bitrate and sample point can be also changed at System type peripheral selection,
-basic values are 1 MHz for bitrate and 0.80 for sample point. The FlexCAN driver
-for imxrt runs at 80 MHz clock frequency.</p>
-<p>The configuration also includes CAN utilities as candump and cansend.</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 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>
+<div class="section" id="configurations">
+<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="netnsh">
+<h3>netnsh<a class="headerlink" href="#netnsh" title="Permalink to this headline">¶</a></h3>
<p>This configuration is similar to the nsh configuration except that is
-has networking enabled, both IPv4 and IPv6. This NSH configuration is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
focused on network-related testing.</p>
-<p>This configuration cannot be changed to Teensy 4.0 as this board does
-not have Ethernet capability.</p>
-</div>
-<div class="section" id="sd-4-1">
-<h3>sd-4.1<a class="headerlink" href="#sd-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-connecting micro SD card.</p>
-<p>You can mount micro SD card by:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>mount -t vfat /dev/mmcsd0 /mnt
-</pre></div>
-</div>
-<p>This configuration cannot be changed to Teensy 4.0 as this board does
-not have micro SD card slot.</p>
-</div>
-<div class="section" id="lcd-4-1">
-<h3>lcd-4.1<a class="headerlink" href="#lcd-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-connecting LCD TFT display with ST7789 controller. You can run framebuffer demo
-by starting “fb” in console. The LCD display is connected via SPI4.</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>
-</div>
</div>
-<div class="section" id="flash">
-<h2>Flash<a class="headerlink" href="#flash" title="Permalink to this headline">¶</a></h2>
-<p>Teensy 4.x boards does not have debugger therefore external firmware has to be used to load NuttX.
-<a class="reference external" href="https://www.pjrc.com/teensy/loader_cli.html">Teensy Loader</a> can be installed and then NuttX can be loaded by:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>teensy_loader_cli --mcu<span class="o">=</span>TEENSY41 -v -w nuttx.hex
-</pre></div>
+<div class="section" id="nsh">
+<h3>nsh<a class="headerlink" href="#nsh" title="Permalink to this headline">¶</a></h3>
+<p>Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.</p>
</div>
-<p>For Teensy 4.0 board, switch <code class="docutils literal notranslate"><span class="pre">--mcu=TEENSY41</span></code> to <code class="docutils literal notranslate"><span class="pre">--mcu=TEENSY40</span></code>.</p>
</div>
</div>
@@ -409,7 +416,7 @@ selecting <code class="docutils literal notranslate"><span class="pre">CONFIG_TE
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
- <a href="../../../nrf52/index.html" class="btn btn-neutral float-right" title="Nordic nRF52" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../imxrt1050-evk/index.html" class="btn btn-neutral float-right" title="i.MX RT1050 EVK" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
<a href="../../index.html" class="btn btn-neutral float-left" title="i.MX RT" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
diff --git a/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1050-evk/index.html
similarity index 62%
copy from content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
copy to content/docs/latest/platforms/arm/imxrt/boards/imxrt1050-evk/index.html
index 7f4d903..d24acfa 100644
--- a/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
+++ b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1050-evk/index.html
@@ -26,7 +26,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>Teensy-4.x — NuttX latest documentation</title>
+ <title>i.MX RT1050 EVK — NuttX latest documentation</title>
@@ -61,8 +61,8 @@
<link rel="index" title="Index" href="../../../../../genindex.html" />
<link rel="search" title="Search" href="../../../../../search.html" />
- <link rel="next" title="Nordic nRF52" href="../../../nrf52/index.html" />
- <link rel="prev" title="i.MX RT" href="../../index.html" />
+ <link rel="next" title="i.MX RT1060 EVK" href="../imxrt1060-evk/index.html" />
+ <link rel="prev" title="i.MX RT1020 EVK" href="../imxrt1020-evk/index.html" />
</head>
<body class="wy-body-for-nav">
@@ -131,7 +131,11 @@
<li class="toctree-l4"><a class="reference internal" href="../../index.html#data-and-instruction-cache">Data and Instruction Cache</a></li>
<li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
<li class="toctree-l4 current"><a class="reference internal" href="../../index.html#supported-boards">Supported Boards</a><ul class="current">
-<li class="toctree-l5 current"><a class="current reference internal" href="#">Teensy-4.x</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1020-evk/index.html">i.MX RT1020 EVK</a></li>
+<li class="toctree-l5 current"><a class="current reference internal" href="#">i.MX RT1050 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1060-evk/index.html">i.MX RT1060 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1064-evk/index.html">i.MX RT1064 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../teensy-4.x/index.html">Teensy-4.x</a></li>
</ul>
</li>
</ul>
@@ -204,13 +208,13 @@
<li><a href="../../index.html">i.MX RT</a> »</li>
- <li>Teensy-4.x</li>
+ <li>i.MX RT1050 EVK</li>
<li class="wy-breadcrumbs-aside">
- <a href="../../../../../_sources/platforms/arm/imxrt/boards/teensy-4.x/index.rst.txt" rel="nofollow"> View page source</a>
+ <a href="../../../../../_sources/platforms/arm/imxrt/boards/imxrt1050-evk/index.rst.txt" rel="nofollow"> View page source</a>
</li>
@@ -223,63 +227,135 @@
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
- <div class="section" id="teensy-4-x">
-<h1>Teensy-4.x<a class="headerlink" href="#teensy-4-x" title="Permalink to this headline">¶</a></h1>
-<p>The <a class="reference external" href="https://www.pjrc.com/store/teensy40.html">Teensy 4.0</a> and <a class="reference external" href="https://www.pjrc.com/store/teensy41.html">Teensy 4.1</a>
-are development boards from PJRC. Both boards use i.MX RT1060 MCU, feature several I/Os pins and on-board LED.</p>
+ <div class="section" id="i-mx-rt1050-evk">
+<h1>i.MX RT1050 EVK<a class="headerlink" href="#i-mx-rt1050-evk" title="Permalink to this headline">¶</a></h1>
+<p><a class="reference external" href="https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt1050-evaluation-kit:MIMXRT1050-EVK">i.MX RT1050 EVK</a>
+is an evaluation kit by NXP company. This kit uses the i.MX RT1050 crossover MCU with ARM Cortex M7 core.</p>
<div class="section" id="features">
<h2>Features<a class="headerlink" href="#features" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li><dl class="simple">
<dt>Processor</dt><dd><ul>
-<li><p>MIMXRT1062DVL6A processor</p></li>
+<li><p>MIMXRT1052DVL6A processor</p></li>
</ul>
</dd>
</dl>
</li>
<li><dl class="simple">
<dt>Memory</dt><dd><ul>
-<li><p>1 MB RAM memory</p></li>
-<li><p>2 MB Flash (Teensy 4.0)</p></li>
-<li><p>8 MB Flash (Teensy 4.1)</p></li>
-<li><p>1 SDIO (4 bit) native SD</p></li>
+<li><p>256 Mb SDRAM memory</p></li>
+<li><p>512 Mb Hyper Flash</p></li>
+<li><p>Footprint for QSPI Flash</p></li>
+<li><p>TF socket for SD card</p></li>
</ul>
</dd>
</dl>
</li>
<li><dl class="simple">
-<dt>Connectivity</dt><dd><ul>
-<li><p>Micro USB host</p></li>
-<li><p>CAN transceivers</p></li>
-<li><p>UART, SPI, I2C</p></li>
-<li><p>PWM output pins</p></li>
-<li><p>10/100 Mb Ethernet (Teensy 4.1 only)</p></li>
-<li><p>Digital audio in/out</p></li>
+<dt>Display and Audio</dt><dd><ul>
+<li><p>Parallel LCD connector</p></li>
+<li><p>Camera connector</p></li>
+<li><p>Audio CODEC</p></li>
+<li><p>4-pole audio headphone jack</p></li>
+<li><p>External speaker connection</p></li>
+<li><p>Microphone</p></li>
+<li><p>SPDIF connector</p></li>
</ul>
</dd>
</dl>
</li>
-</ul>
-</div>
-<div class="section" id="leds">
-<h2>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h2>
-<p>There are two LED status indicators located on the Teensy-4.x board.
-The functions of these LEDs include:</p>
-<ul class="simple">
<li><dl class="simple">
-<dt>RED LED (loading status)</dt><dd><ul>
-<li><p>dim: ready</p></li>
-<li><p>bright: writing</p></li>
-<li><p>blink: no USB</p></li>
+<dt>Connectivity</dt><dd><ul>
+<li><p>Micro USB host and OTG connectors</p></li>
+<li><p>Ethernet (10/100T) connector</p></li>
+<li><p>CAN transceivers</p></li>
+<li><p>Arduino® interface</p></li>
</ul>
</dd>
</dl>
</li>
-<li><p>USER LED (D3)</p></li>
</ul>
-<p>Only a single LED, D3, is under software control.</p>
+</div>
+<div class="section" id="serial-console">
+<h2>Serial Console<a class="headerlink" href="#serial-console" title="Permalink to this headline">¶</a></h2>
+<p>Virtual console port provided by OpenSDA:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 28%" />
+<col style="width: 41%" />
+<col style="width: 31%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><p>UART1_TXD</p></td>
+<td><p>GPIO_AD_B0_12</p></td>
+<td><p>LPUART1_TX</p></td>
+</tr>
+<tr class="row-even"><td><p>UART1_RXD</p></td>
+<td><p>GPIO_AD_B0_13</p></td>
+<td><p>LPUART1_RX</p></td>
+</tr>
+</tbody>
+</table>
+<p>Arduino RS-232 Shield:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 9%" />
+<col style="width: 6%" />
+<col style="width: 20%" />
+<col style="width: 37%" />
+<col style="width: 29%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><p>J22</p></td>
+<td><p>D0</p></td>
+<td><p>UART_RX</p></td>
+<td><p>GPIO_AD_B1_07</p></td>
+<td><p>LPUART3_RX</p></td>
+</tr>
+<tr class="row-even"><td><p>J22</p></td>
+<td><p>D1</p></td>
+<td><p>UART_TX</p></td>
+<td><p>GPIO_AD_B1_06</p></td>
+<td><p>LPUART3_TX</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="leds-and-buttons">
+<h2>LEDs and buttons<a class="headerlink" href="#leds-and-buttons" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="leds">
+<h3>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h3>
+<p>There are four LED status indicators located on the EVK Board. The
+functions of these LEDs include:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 20%" />
+<col style="width: 80%" />
+</colgroup>
+<thead>
+<tr class="row-odd"><th class="head"><p>Pin</p></th>
+<th class="head"><p>Description</p></th>
+</tr>
+</thead>
+<tbody>
+<tr class="row-even"><td><p>D3</p></td>
+<td><p>Power Supply</p></td>
+</tr>
+<tr class="row-odd"><td><p>D15</p></td>
+<td><p>Reset LED</p></td>
+</tr>
+<tr class="row-even"><td><p>D16</p></td>
+<td><p>OpenSDA</p></td>
+</tr>
+<tr class="row-odd"><td><p>D18</p></td>
+<td><p>User LED</p></td>
+</tr>
+</tbody>
+</table>
+<p>Only a single LED, D18, is under software control. It connects to
+GPIO_AD_B0_09 which is shared with JTAG_TDI and ENET_RST</p>
<p>This LED is not used by the board port unless CONFIG_ARCH_LEDS is
-defined. In that case, the usage by the board port is defined in
+defined. In that case, the usage by the board port is defined in
include/board.h and src/imxrt_autoleds.c. The LED is used to encode
OS-related events as follows:</p>
<table class="docutils align-default">
@@ -329,77 +405,47 @@ OS-related events as follows:</p>
</tr>
</tbody>
</table>
-<p>Thus if the LED is statically on, NuttX has successfully booted and is,
-apparently, running normally. If the LED is flashing at approximately
+<p>Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
2Hz, then a fatal error has been detected and the system has halted.</p>
</div>
-<div class="section" id="configurations">
-<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
-<div class="section" id="nsh-4-0">
-<h3>nsh-4.0<a class="headerlink" href="#nsh-4-0" title="Permalink to this headline">¶</a></h3>
-<p>Configures the NuttShell (nsh) located at examples/nsh for Teensy 4.0.
-This NSH configuration is focused on low level, command-line driver testing.
-Built-in applications are supported, but none are enabled. NutShells then
-runs on USB console.</p>
+<div class="section" id="buttons">
+<h3>Buttons<a class="headerlink" href="#buttons" title="Permalink to this headline">¶</a></h3>
+<p>There are four user interface switches on the MIMXRT1050 EVK Board:</p>
+<blockquote>
+<div><ul class="simple">
+<li><p>SW1: Power Switch (slide switch)</p></li>
+<li><p>SW2: ON/OFF Button</p></li>
+<li><p>SW3: Reset button</p></li>
+<li><p>SW8: User button</p></li>
+</ul>
+</div></blockquote>
+<p>Only the user button is available to the software. It is sensed on the
+WAKEUP pin which will be pulled low when the button is pressed.</p>
</div>
-<div class="section" id="nsh-4-1">
-<h3>nsh-4.1<a class="headerlink" href="#nsh-4-1" title="Permalink to this headline">¶</a></h3>
-<p>Configures the NuttShell (nsh) located at examples/nsh for Teensy 4.1.
-This NSH configuration is focused on low level, command-line driver testing.
-Built-in applications are supported, but none are enabled. NutShells then
-runs USB console.</p>
</div>
-<div class="section" id="can-4-1">
-<h3>can-4.1<a class="headerlink" href="#can-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-CAN driver. All FlexCANs (CAN1, CAN2, CAN3) are chosen as default. FlexCAN3
-is FD capable. Please note that device driver name if counted from zero.
-That means for CAN1 -> can0, CAN2 -> can1 and CAN3 -> can2</p>
-<p>Bitrate and sample point can be also changed at System type peripheral selection,
-basic values are 1 MHz for bitrate and 0.80 for sample point. The FlexCAN driver
-for imxrt runs at 80 MHz clock frequency.</p>
-<p>The configuration also includes CAN utilities as candump and cansend.</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 causes problems with FlexCAN.</p>
+<div class="section" id="configurations">
+<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="knsh">
+<h3>knsh<a class="headerlink" href="#knsh" title="Permalink to this headline">¶</a></h3>
+<p>This is identical to the nsh configuration below except that NuttX
+is built as a protected mode, monolithic module and the user applications
+are built separately. For further information about compiling and
+running this configuration please refer to imxrt1064-evk documentation.</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>
+<div class="section" id="netnsh">
+<h3>netnsh<a class="headerlink" href="#netnsh" title="Permalink to this headline">¶</a></h3>
<p>This configuration is similar to the nsh configuration except that is
-has networking enabled, both IPv4 and IPv6. This NSH configuration is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
focused on network-related testing.</p>
-<p>This configuration cannot be changed to Teensy 4.0 as this board does
-not have Ethernet capability.</p>
-</div>
-<div class="section" id="sd-4-1">
-<h3>sd-4.1<a class="headerlink" href="#sd-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-connecting micro SD card.</p>
-<p>You can mount micro SD card by:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>mount -t vfat /dev/mmcsd0 /mnt
-</pre></div>
-</div>
-<p>This configuration cannot be changed to Teensy 4.0 as this board does
-not have micro SD card slot.</p>
-</div>
-<div class="section" id="lcd-4-1">
-<h3>lcd-4.1<a class="headerlink" href="#lcd-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-connecting LCD TFT display with ST7789 controller. You can run framebuffer demo
-by starting “fb” in console. The LCD display is connected via SPI4.</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>
-</div>
</div>
-<div class="section" id="flash">
-<h2>Flash<a class="headerlink" href="#flash" title="Permalink to this headline">¶</a></h2>
-<p>Teensy 4.x boards does not have debugger therefore external firmware has to be used to load NuttX.
-<a class="reference external" href="https://www.pjrc.com/teensy/loader_cli.html">Teensy Loader</a> can be installed and then NuttX can be loaded by:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>teensy_loader_cli --mcu<span class="o">=</span>TEENSY41 -v -w nuttx.hex
-</pre></div>
+<div class="section" id="nsh">
+<h3>nsh<a class="headerlink" href="#nsh" title="Permalink to this headline">¶</a></h3>
+<p>Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.</p>
</div>
-<p>For Teensy 4.0 board, switch <code class="docutils literal notranslate"><span class="pre">--mcu=TEENSY41</span></code> to <code class="docutils literal notranslate"><span class="pre">--mcu=TEENSY40</span></code>.</p>
</div>
</div>
@@ -409,8 +455,8 @@ selecting <code class="docutils literal notranslate"><span class="pre">CONFIG_TE
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
- <a href="../../../nrf52/index.html" class="btn btn-neutral float-right" title="Nordic nRF52" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
- <a href="../../index.html" class="btn btn-neutral float-left" title="i.MX RT" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="../imxrt1060-evk/index.html" class="btn btn-neutral float-right" title="i.MX RT1060 EVK" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../imxrt1020-evk/index.html" class="btn btn-neutral float-left" title="i.MX RT1020 EVK" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
<hr/>
diff --git a/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1060-evk/index.html
similarity index 52%
copy from content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
copy to content/docs/latest/platforms/arm/imxrt/boards/imxrt1060-evk/index.html
index 7f4d903..f63497c 100644
--- a/content/docs/latest/platforms/arm/imxrt/boards/teensy-4.x/index.html
+++ b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1060-evk/index.html
@@ -26,7 +26,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>Teensy-4.x — NuttX latest documentation</title>
+ <title>i.MX RT1060 EVK — NuttX latest documentation</title>
@@ -61,8 +61,8 @@
<link rel="index" title="Index" href="../../../../../genindex.html" />
<link rel="search" title="Search" href="../../../../../search.html" />
- <link rel="next" title="Nordic nRF52" href="../../../nrf52/index.html" />
- <link rel="prev" title="i.MX RT" href="../../index.html" />
+ <link rel="next" title="i.MX RT1064 EVK" href="../imxrt1064-evk/index.html" />
+ <link rel="prev" title="i.MX RT1050 EVK" href="../imxrt1050-evk/index.html" />
</head>
<body class="wy-body-for-nav">
@@ -131,7 +131,11 @@
<li class="toctree-l4"><a class="reference internal" href="../../index.html#data-and-instruction-cache">Data and Instruction Cache</a></li>
<li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
<li class="toctree-l4 current"><a class="reference internal" href="../../index.html#supported-boards">Supported Boards</a><ul class="current">
-<li class="toctree-l5 current"><a class="current reference internal" href="#">Teensy-4.x</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1020-evk/index.html">i.MX RT1020 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1050-evk/index.html">i.MX RT1050 EVK</a></li>
+<li class="toctree-l5 current"><a class="current reference internal" href="#">i.MX RT1060 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1064-evk/index.html">i.MX RT1064 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../teensy-4.x/index.html">Teensy-4.x</a></li>
</ul>
</li>
</ul>
@@ -204,13 +208,13 @@
<li><a href="../../index.html">i.MX RT</a> »</li>
- <li>Teensy-4.x</li>
+ <li>i.MX RT1060 EVK</li>
<li class="wy-breadcrumbs-aside">
- <a href="../../../../../_sources/platforms/arm/imxrt/boards/teensy-4.x/index.rst.txt" rel="nofollow"> View page source</a>
+ <a href="../../../../../_sources/platforms/arm/imxrt/boards/imxrt1060-evk/index.rst.txt" rel="nofollow"> View page source</a>
</li>
@@ -223,10 +227,14 @@
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
- <div class="section" id="teensy-4-x">
-<h1>Teensy-4.x<a class="headerlink" href="#teensy-4-x" title="Permalink to this headline">¶</a></h1>
-<p>The <a class="reference external" href="https://www.pjrc.com/store/teensy40.html">Teensy 4.0</a> and <a class="reference external" href="https://www.pjrc.com/store/teensy41.html">Teensy 4.1</a>
-are development boards from PJRC. Both boards use i.MX RT1060 MCU, feature several I/Os pins and on-board LED.</p>
+ <div class="section" id="i-mx-rt1060-evk">
+<h1>i.MX RT1060 EVK<a class="headerlink" href="#i-mx-rt1060-evk" title="Permalink to this headline">¶</a></h1>
+<p><a class="reference external" href="https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/mimxrt1060-evk-i-mx-rt1060-evaluation-kit:MIMXRT1060-EVK">i.MX RT1060 EVK</a>
+is an evaluation kit by NXP company. This kit uses the i.MX RT1060 crossover MCU with ARM Cortex M7 core.</p>
+<div class="figure align-center" id="id2">
+<a class="reference internal image-reference" href="../../../../../_images/imxrt1060-evk-front.jpg"><img alt="../../../../../_images/imxrt1060-evk-front.jpg" src="../../../../../_images/imxrt1060-evk-front.jpg" style="width: 50%;" /></a>
+<p class="caption"><span class="caption-text">i.MX RT1060 EVK</span><a class="headerlink" href="#id2" title="Permalink to this image">¶</a></p>
+</div>
<div class="section" id="features">
<h2>Features<a class="headerlink" href="#features" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
@@ -239,47 +247,127 @@ are development boards from PJRC. Both boards use i.MX RT1060 MCU, feature sever
</li>
<li><dl class="simple">
<dt>Memory</dt><dd><ul>
-<li><p>1 MB RAM memory</p></li>
-<li><p>2 MB Flash (Teensy 4.0)</p></li>
-<li><p>8 MB Flash (Teensy 4.1)</p></li>
-<li><p>1 SDIO (4 bit) native SD</p></li>
+<li><p>1 Mb OCRAM memory</p></li>
+<li><p>256 Mb SDRAM memory</p></li>
+<li><p>512 Mb Hyper Flash - Populated but 0 ohm DNP</p></li>
+<li><p>64 Mb QSPI Flash</p></li>
+<li><p>TF socket for SD card</p></li>
</ul>
</dd>
</dl>
</li>
<li><dl class="simple">
-<dt>Connectivity</dt><dd><ul>
-<li><p>Micro USB host</p></li>
-<li><p>CAN transceivers</p></li>
-<li><p>UART, SPI, I2C</p></li>
-<li><p>PWM output pins</p></li>
-<li><p>10/100 Mb Ethernet (Teensy 4.1 only)</p></li>
-<li><p>Digital audio in/out</p></li>
+<dt>Display and Audio</dt><dd><ul>
+<li><p>Parallel LCD connector</p></li>
+<li><p>Camera connector</p></li>
+<li><p>Audio CODEC</p></li>
+<li><p>4-pole audio headphone jack</p></li>
+<li><p>External speaker connection</p></li>
+<li><p>Microphone</p></li>
+<li><p>SPDIF connector</p></li>
</ul>
</dd>
</dl>
</li>
+<li><dl class="simple">
+<dt>Connectivity</dt><dd><ul>
+<li><p>Micro USB host and OTG connectors</p></li>
+<li><p>Ethernet (10/100T) connector</p></li>
+<li><p>CAN transceivers (including one CAN FD)</p></li>
+<li><p>Arduino® interface</p></li>
</ul>
-</div>
-<div class="section" id="leds">
-<h2>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h2>
-<p>There are two LED status indicators located on the Teensy-4.x board.
-The functions of these LEDs include:</p>
-<ul class="simple">
+</dd>
+</dl>
+</li>
<li><dl class="simple">
-<dt>RED LED (loading status)</dt><dd><ul>
-<li><p>dim: ready</p></li>
-<li><p>bright: writing</p></li>
-<li><p>blink: no USB</p></li>
+<dt>Sensors</dt><dd><ul>
+<li><p>FXOS8700CQ 6-Axis Ecompass (3-Axis Mag, 3-Axis Accel)</p></li>
</ul>
</dd>
</dl>
</li>
-<li><p>USER LED (D3)</p></li>
</ul>
-<p>Only a single LED, D3, is under software control.</p>
+</div>
+<div class="section" id="serial-console">
+<h2>Serial Console<a class="headerlink" href="#serial-console" title="Permalink to this headline">¶</a></h2>
+<p>Virtual console port provided by OpenSDA:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 28%" />
+<col style="width: 41%" />
+<col style="width: 31%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><p>UART1_TXD</p></td>
+<td><p>GPIO_AD_B0_12</p></td>
+<td><p>LPUART1_TX</p></td>
+</tr>
+<tr class="row-even"><td><p>UART1_RXD</p></td>
+<td><p>GPIO_AD_B0_13</p></td>
+<td><p>LPUART1_RX</p></td>
+</tr>
+</tbody>
+</table>
+<p>Arduino RS-232 Shield:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 9%" />
+<col style="width: 6%" />
+<col style="width: 20%" />
+<col style="width: 37%" />
+<col style="width: 29%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><p>J22</p></td>
+<td><p>D0</p></td>
+<td><p>UART_RX</p></td>
+<td><p>GPIO_AD_B1_07</p></td>
+<td><p>LPUART3_RX</p></td>
+</tr>
+<tr class="row-even"><td><p>J22</p></td>
+<td><p>D1</p></td>
+<td><p>UART_TX</p></td>
+<td><p>GPIO_AD_B1_06</p></td>
+<td><p>LPUART3_TX</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="leds-and-buttons">
+<h2>LEDs and buttons<a class="headerlink" href="#leds-and-buttons" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="leds">
+<h3>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h3>
+<p>There are four LED status indicators located on the EVK Board. The
+functions of these LEDs include:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 20%" />
+<col style="width: 80%" />
+</colgroup>
+<thead>
+<tr class="row-odd"><th class="head"><p>Pin</p></th>
+<th class="head"><p>Description</p></th>
+</tr>
+</thead>
+<tbody>
+<tr class="row-even"><td><p>D3</p></td>
+<td><p>Power Supply</p></td>
+</tr>
+<tr class="row-odd"><td><p>D18</p></td>
+<td><p>User LED</p></td>
+</tr>
+<tr class="row-even"><td><p>D20</p></td>
+<td><p>OpenSDA</p></td>
+</tr>
+<tr class="row-odd"><td><p>D21</p></td>
+<td><p>Reset LED</p></td>
+</tr>
+</tbody>
+</table>
+<p>Only a single LED, D18, is under software control. It connects to
+GPIO_AD_B0_09 which is shared with JTAG_TDI and ENET_RST</p>
<p>This LED is not used by the board port unless CONFIG_ARCH_LEDS is
-defined. In that case, the usage by the board port is defined in
+defined. In that case, the usage by the board port is defined in
include/board.h and src/imxrt_autoleds.c. The LED is used to encode
OS-related events as follows:</p>
<table class="docutils align-default">
@@ -329,77 +417,101 @@ OS-related events as follows:</p>
</tr>
</tbody>
</table>
-<p>Thus if the LED is statically on, NuttX has successfully booted and is,
-apparently, running normally. If the LED is flashing at approximately
+<p>Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
2Hz, then a fatal error has been detected and the system has halted.</p>
</div>
-<div class="section" id="configurations">
-<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
-<div class="section" id="nsh-4-0">
-<h3>nsh-4.0<a class="headerlink" href="#nsh-4-0" title="Permalink to this headline">¶</a></h3>
-<p>Configures the NuttShell (nsh) located at examples/nsh for Teensy 4.0.
-This NSH configuration is focused on low level, command-line driver testing.
-Built-in applications are supported, but none are enabled. NutShells then
-runs on USB console.</p>
+<div class="section" id="buttons">
+<h3>Buttons<a class="headerlink" href="#buttons" title="Permalink to this headline">¶</a></h3>
+<p>There are five user interface switches on the MIMXRT1050 EVK Board:</p>
+<blockquote>
+<div><ul class="simple">
+<li><p>SW1: Power Switch (slide switch fir power from J2)</p></li>
+<li><p>SW2: ON/OFF Button</p></li>
+<li><p>SW3: Power-on Reset button state forces to reset the system power except SNVS domain</p></li>
+<li><p>SW9: Reset button</p></li>
+<li><p>SW8: User button GPIO5-00</p></li>
+</ul>
+</div></blockquote>
+<p>Only the user button is available to the software. It is sensed on the
+WAKEUP pin which will be pulled low when the button is pressed.</p>
+</div>
</div>
-<div class="section" id="nsh-4-1">
-<h3>nsh-4.1<a class="headerlink" href="#nsh-4-1" title="Permalink to this headline">¶</a></h3>
-<p>Configures the NuttShell (nsh) located at examples/nsh for Teensy 4.1.
-This NSH configuration is focused on low level, command-line driver testing.
-Built-in applications are supported, but none are enabled. NutShells then
-runs USB console.</p>
+<div class="section" id="j-link-external-debug-probe">
+<h2>J-Link External Debug Probe<a class="headerlink" href="#j-link-external-debug-probe" title="Permalink to this headline">¶</a></h2>
+<p>Install the J-Link Debug Host Tools and make sure they are in your search path.</p>
+<p>Attach a J-Link 20-pin connector to J21. Check that jumpers J47 and J48 are
+off (they are on by default when boards ship from the factory) to ensure SWD
+signals are disconnected from the OpenSDA microcontroller.</p>
</div>
-<div class="section" id="can-4-1">
-<h3>can-4.1<a class="headerlink" href="#can-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-CAN driver. All FlexCANs (CAN1, CAN2, CAN3) are chosen as default. FlexCAN3
-is FD capable. Please note that device driver name if counted from zero.
-That means for CAN1 -> can0, CAN2 -> can1 and CAN3 -> can2</p>
+<div class="section" id="configurations">
+<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="can">
+<h3>can<a class="headerlink" href="#can" title="Permalink to this headline">¶</a></h3>
+<p>This is an nsh configuration (see below) with added support of CAN driver.
+FlexCAN3 is chosen as default, the change can be made at System type peripheral
+selection. Please note that only FlexCAN3 and FlexCAN2 is available on this board.</p>
<p>Bitrate and sample point can be also changed at System type peripheral selection,
basic values are 1 MHz for bitrate and 0.80 for sample point. The FlexCAN driver
for imxrt runs at 80 MHz clock frequency.</p>
<p>The configuration also includes CAN utilities as candump and cansend.</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 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>
-<p>This configuration is similar to the nsh configuration except that is
-has networking enabled, both IPv4 and IPv6. This NSH configuration is
-focused on network-related testing.</p>
-<p>This configuration cannot be changed to Teensy 4.0 as this board does
-not have Ethernet capability.</p>
</div>
-<div class="section" id="sd-4-1">
-<h3>sd-4.1<a class="headerlink" href="#sd-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-connecting micro SD card.</p>
-<p>You can mount micro SD card by:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>mount -t vfat /dev/mmcsd0 /mnt
-</pre></div>
+<div class="section" id="canfd">
+<h3>canfd<a class="headerlink" href="#canfd" title="Permalink to this headline">¶</a></h3>
+<p>This is an nsh configuration (see below) with added support of CAN_FD driver.
+FlexCAN3 is chosen as default, please note that only FlexCAN3 is capable of
+providing CAN_FD support.</p>
+<p>Bitrate and sample point can be also changed at System type peripheral selection,
+basic values are 1 MHz for bitrate and 0.80 for sample point for arbitration phase
+and 4 MHz (bitrate) and 0.90 (sample point) for data phase. The FlexCAN driver
+for imxrt runs at 80 MHz clock frequency.</p>
+<p>The configuration also includes CAN utilities as candump and cansend.</p>
</div>
-<p>This configuration cannot be changed to Teensy 4.0 as this board does
-not have micro SD card slot.</p>
+<div class="section" id="knsh">
+<h3>knsh<a class="headerlink" href="#knsh" title="Permalink to this headline">¶</a></h3>
+<p>This is identical to the nsh configuration below except that NuttX
+is built as a protected mode, monolithic module and the user applications
+are built separately. For further information about compiling and
+running this configuration please refer to imxrt1064-evk documentation.</p>
</div>
-<div class="section" id="lcd-4-1">
-<h3>lcd-4.1<a class="headerlink" href="#lcd-4-1" title="Permalink to this headline">¶</a></h3>
-<p>This is an nsh configuration (see above) for Teensy-4.x with added support of
-connecting LCD TFT display with ST7789 controller. You can run framebuffer demo
-by starting “fb” in console. The LCD display is connected via SPI4.</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>
+<div class="section" id="netnsh">
+<h3>netnsh<a class="headerlink" href="#netnsh" title="Permalink to this headline">¶</a></h3>
+<p>This configuration is similar to the nsh configuration except that is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
+focused on network-related testing.</p>
</div>
+<div class="section" id="nsh">
+<h3>nsh<a class="headerlink" href="#nsh" title="Permalink to this headline">¶</a></h3>
+<p>Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.</p>
</div>
-<div class="section" id="flash">
-<h2>Flash<a class="headerlink" href="#flash" title="Permalink to this headline">¶</a></h2>
-<p>Teensy 4.x boards does not have debugger therefore external firmware has to be used to load NuttX.
-<a class="reference external" href="https://www.pjrc.com/teensy/loader_cli.html">Teensy Loader</a> can be installed and then NuttX can be loaded by:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>teensy_loader_cli --mcu<span class="o">=</span>TEENSY41 -v -w nuttx.hex
+<div class="section" id="lvgl">
+<h3>lvgl<a class="headerlink" href="#lvgl" title="Permalink to this headline">¶</a></h3>
+<p>Configures the Littlev graphic library (lvgl) demo located under
+examples/lvgldemo. This configuration needs the optional LCD model
+RK043FN02H-CT from NXP. The LCD panel comes with the integrated
+capacitive touchscreen sensor FT5336GQQ connected to the LPI2C1 bus,
+address 0x38. NuttX support such touchscreen device via the driver
+ft5x06 (drivers/input/ft5x06.c). At the moment only the polling
+method is available, the board features an interrupt line connected
+to the touchscreen sensor IC.</p>
+<p>IMXRT1060 MCU provides the integrated LCD driver.</p>
+<dl class="simple">
+<dt>The LCD panel features:</dt><dd><ul class="simple">
+<li><p>size 4.3”</p></li>
+<li><p>resolution 480×272 RGB</p></li>
+<li><p>backlight driver</p></li>
+<li><p>dimensions [mm]: 105.5 (W) x 67.2(H) x 4.35(D) Max.</p></li>
+</ul>
+</dd>
+</dl>
+<p>To run the lvgl demo please type “lvgldemo” at nsh prompt:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh> lvgldemo
</pre></div>
</div>
-<p>For Teensy 4.0 board, switch <code class="docutils literal notranslate"><span class="pre">--mcu=TEENSY41</span></code> to <code class="docutils literal notranslate"><span class="pre">--mcu=TEENSY40</span></code>.</p>
+</div>
</div>
</div>
@@ -409,8 +521,8 @@ selecting <code class="docutils literal notranslate"><span class="pre">CONFIG_TE
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
- <a href="../../../nrf52/index.html" class="btn btn-neutral float-right" title="Nordic nRF52" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
- <a href="../../index.html" class="btn btn-neutral float-left" title="i.MX RT" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="../imxrt1064-evk/index.html" class="btn btn-neutral float-right" title="i.MX RT1064 EVK" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../imxrt1050-evk/index.html" class="btn btn-neutral float-left" title="i.MX RT1050 EVK" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
<hr/>
diff --git a/content/docs/latest/platforms/arm/imxrt/boards/imxrt1064-evk/index.html b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1064-evk/index.html
new file mode 100644
index 0000000..5c64347
--- /dev/null
+++ b/content/docs/latest/platforms/arm/imxrt/boards/imxrt1064-evk/index.html
@@ -0,0 +1,625 @@
+<!--
+ Documentation/_templates/layout.html
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership. The
+ ASF licenses this file to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance with the
+ License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ License for the specific language governing permissions and limitations
+ under the License.
+-->
+
+
+
+<!DOCTYPE html>
+<html class="writer-html5" lang="en" >
+<head>
+ <meta charset="utf-8" />
+
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+
+ <title>i.MX RT1064 EVK — NuttX latest documentation</title>
+
+
+
+ <link rel="stylesheet" href="../../../../../_static/css/theme.css" type="text/css" />
+ <link rel="stylesheet" href="../../../../../_static/pygments.css" type="text/css" />
+ <link rel="stylesheet" href="../../../../../_static/tabs.css" type="text/css" />
+ <link rel="stylesheet" href="../../../../../_static/custom.css" type="text/css" />
+
+
+
+ <link rel="shortcut icon" href="../../../../../_static/favicon.ico"/>
+
+
+
+
+
+
+
+
+ <!--[if lt IE 9]>
+ <script src="../../../../../_static/js/html5shiv.min.js"></script>
+ <![endif]-->
+
+
+ <script type="text/javascript" id="documentation_options" data-url_root="../../../../../" src="../../../../../_static/documentation_options.js"></script>
+ <script src="../../../../../_static/jquery.js"></script>
+ <script src="../../../../../_static/underscore.js"></script>
+ <script src="../../../../../_static/doctools.js"></script>
+
+ <script type="text/javascript" src="../../../../../_static/js/theme.js"></script>
+
+
+ <link rel="index" title="Index" href="../../../../../genindex.html" />
+ <link rel="search" title="Search" href="../../../../../search.html" />
+ <link rel="next" title="Teensy-4.x" href="../teensy-4.x/index.html" />
+ <link rel="prev" title="i.MX RT1060 EVK" href="../imxrt1060-evk/index.html" />
+</head>
+
+<body class="wy-body-for-nav">
+
+
+ <div class="wy-grid-for-nav">
+
+ <nav data-toggle="wy-nav-shift" class="wy-nav-side">
+ <div class="wy-side-scroll">
+ <div class="wy-side-nav-search" >
+
+
+ <a href="../../../../../index.html" class="icon icon-home"> NuttX
+
+
+
+
+ <img src="../../../../../_static/NuttX.png" class="logo" alt="Logo"/>
+
+ </a>
+
+ <!-- this version selector is quite ugly, should be probably replaced by something
+ more modern -->
+
+ <div class="version-selector">
+ <select onchange="javascript:location.href = this.value;">
+
+ <option value="../../../../../../latest" selected="selected">latest</option>
+
+ <option value="../../../../../../10.0.0" >10.0.0</option>
+
+ <option value="../../../../../../10.0.1" >10.0.1</option>
+
+ </select>
+ </div>
+
+
+<div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../../../search.html" method="get">
+ <input type="text" name="q" placeholder="Search docs" />
+ <input type="hidden" name="check_keywords" value="yes" />
+ <input type="hidden" name="area" value="default" />
+ </form>
+</div>
+
+ </div>
+
+
+ <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
+
+
+
+
+
+
+ <p class="caption"><span class="caption-text">Table of Contents</span></p>
+<ul class="current">
+<li class="toctree-l1"><a class="reference internal" href="../../../../../index.html">Home</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../introduction/index.html">Introduction</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../quickstart/index.html">Getting Started</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../introduction/inviolables.html">The Inviolable Principles of NuttX</a></li>
+<li class="toctree-l1 current"><a class="reference internal" href="../../../../index.html">Supported Platforms</a><ul class="current">
+<li class="toctree-l2 current"><a class="reference internal" href="../../../index.html">ARM</a><ul class="current">
+<li class="toctree-l3 current"><a class="reference internal" href="../../index.html">i.MX RT</a><ul class="current">
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#supported-mcus">Supported MCUs</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#data-and-instruction-cache">Data and Instruction Cache</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
+<li class="toctree-l4 current"><a class="reference internal" href="../../index.html#supported-boards">Supported Boards</a><ul class="current">
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1020-evk/index.html">i.MX RT1020 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1050-evk/index.html">i.MX RT1050 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1060-evk/index.html">i.MX RT1060 EVK</a></li>
+<li class="toctree-l5 current"><a class="current reference internal" href="#">i.MX RT1064 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../teensy-4.x/index.html">Teensy-4.x</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l3"><a class="reference internal" href="../../../nrf52/index.html">Nordic nRF52</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="../../../../risc-v/index.html">RISC-V</a></li>
+<li class="toctree-l2"><a class="reference internal" href="../../../../xtensa/index.html">Xtensa</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../components/index.html">OS Components</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../applications/index.html">Applications</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../reference/index.html">API Reference</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../faq/index.html">FAQ</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../guides/index.html">Guides</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../contributing/index.html">Contributing</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../glossary.html">Glossary</a></li>
+</ul>
+
+
+
+ </div>
+
+ </div>
+ </nav>
+
+ <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
+
+
+ <nav class="wy-nav-top" aria-label="top navigation">
+
+ <i data-toggle="wy-nav-top" class="fa fa-bars"></i>
+ <a href="../../../../../index.html">NuttX</a>
+
+ </nav>
+
+
+ <div class="wy-nav-content">
+
+ <div class="rst-content">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<div role="navigation" aria-label="breadcrumbs navigation">
+
+ <ul class="wy-breadcrumbs">
+
+ <li><a href="../../../../../index.html" class="icon icon-home"></a> »</li>
+
+ <li><a href="../../../../index.html">Supported Platforms</a> »</li>
+
+ <li><a href="../../../index.html">ARM</a> »</li>
+
+ <li><a href="../../index.html">i.MX RT</a> »</li>
+
+ <li>i.MX RT1064 EVK</li>
+
+
+ <li class="wy-breadcrumbs-aside">
+
+
+ <a href="../../../../../_sources/platforms/arm/imxrt/boards/imxrt1064-evk/index.rst.txt" rel="nofollow"> View page source</a>
+
+
+ </li>
+
+ </ul>
+
+
+ <hr/>
+</div>
+ <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
+ <div itemprop="articleBody">
+
+ <div class="section" id="i-mx-rt1064-evk">
+<h1>i.MX RT1064 EVK<a class="headerlink" href="#i-mx-rt1064-evk" title="Permalink to this headline">¶</a></h1>
+<p><a class="reference external" href="https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/mimxrt1064-evk-i-mx-rt1064-evaluation-kit:MIMXRT1064-EVK">i.MX RT1064 EVK</a>
+is an evaluation kit by NXP company. This kit uses the i.MX RT1064 crossover MCU with ARM Cortex M7 core.</p>
+<div class="section" id="features">
+<h2>Features<a class="headerlink" href="#features" title="Permalink to this headline">¶</a></h2>
+<ul class="simple">
+<li><dl class="simple">
+<dt>Processor</dt><dd><ul>
+<li><p>MIMXRT1066DVL6A processor</p></li>
+</ul>
+</dd>
+</dl>
+</li>
+<li><dl class="simple">
+<dt>Memory</dt><dd><ul>
+<li><p>1 Mb OCRAM memory</p></li>
+<li><p>256 Mb SDRAM memory</p></li>
+<li><p>512 Mb Hyper Flash - Populated but 0 ohm DNP</p></li>
+<li><p>64 Mb QSPI Flash</p></li>
+<li><p>TF socket for SD card</p></li>
+</ul>
+</dd>
+</dl>
+</li>
+<li><dl class="simple">
+<dt>Display and Audio</dt><dd><ul>
+<li><p>Parallel LCD connector</p></li>
+<li><p>Camera connector</p></li>
+<li><p>Audio CODEC</p></li>
+<li><p>4-pole audio headphone jack</p></li>
+<li><p>External speaker connection</p></li>
+<li><p>Microphone</p></li>
+<li><p>SPDIF connector</p></li>
+</ul>
+</dd>
+</dl>
+</li>
+<li><dl class="simple">
+<dt>Connectivity</dt><dd><ul>
+<li><p>Micro USB host and OTG connectors</p></li>
+<li><p>Ethernet (10/100T) connector</p></li>
+<li><p>CAN transceivers</p></li>
+<li><p>Arduino® interface</p></li>
+</ul>
+</dd>
+</dl>
+</li>
+<li><dl class="simple">
+<dt>Sensors</dt><dd><ul>
+<li><p>FXOS8700CQ 6-Axis Ecompass (3-Axis Mag, 3-Axis Accel)</p></li>
+</ul>
+</dd>
+</dl>
+</li>
+</ul>
+</div>
+<div class="section" id="serial-console">
+<h2>Serial Console<a class="headerlink" href="#serial-console" title="Permalink to this headline">¶</a></h2>
+<p>Virtual console port provided by OpenSDA:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 28%" />
+<col style="width: 41%" />
+<col style="width: 31%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><p>UART1_TXD</p></td>
+<td><p>GPIO_AD_B0_12</p></td>
+<td><p>LPUART1_TX</p></td>
+</tr>
+<tr class="row-even"><td><p>UART1_RXD</p></td>
+<td><p>GPIO_AD_B0_13</p></td>
+<td><p>LPUART1_RX</p></td>
+</tr>
+</tbody>
+</table>
+<p>Arduino RS-232 Shield:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 9%" />
+<col style="width: 6%" />
+<col style="width: 20%" />
+<col style="width: 37%" />
+<col style="width: 29%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><p>J22</p></td>
+<td><p>D0</p></td>
+<td><p>UART_RX</p></td>
+<td><p>GPIO_AD_B1_07</p></td>
+<td><p>LPUART3_RX</p></td>
+</tr>
+<tr class="row-even"><td><p>J22</p></td>
+<td><p>D1</p></td>
+<td><p>UART_TX</p></td>
+<td><p>GPIO_AD_B1_06</p></td>
+<td><p>LPUART3_TX</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="leds-and-buttons">
+<h2>LEDs and buttons<a class="headerlink" href="#leds-and-buttons" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="leds">
+<h3>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h3>
+<p>There are four LED status indicators located on the EVK Board. The
+functions of these LEDs include:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 20%" />
+<col style="width: 80%" />
+</colgroup>
+<thead>
+<tr class="row-odd"><th class="head"><p>Pin</p></th>
+<th class="head"><p>Description</p></th>
+</tr>
+</thead>
+<tbody>
+<tr class="row-even"><td><p>D3</p></td>
+<td><p>Power Supply</p></td>
+</tr>
+<tr class="row-odd"><td><p>D18</p></td>
+<td><p>User LED</p></td>
+</tr>
+<tr class="row-even"><td><p>D20</p></td>
+<td><p>OpenSDA</p></td>
+</tr>
+<tr class="row-odd"><td><p>D21</p></td>
+<td><p>Reset LED</p></td>
+</tr>
+</tbody>
+</table>
+<p>Only a single LED, D18, is under software control. It connects to
+GPIO_AD_B0_09 which is shared with JTAG_TDI and ENET_RST</p>
+<p>This LED is 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/imxrt_autoleds.c. The LED is used to encode
+OS-related events as follows:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 36%" />
+<col style="width: 52%" />
+<col style="width: 11%" />
+</colgroup>
+<thead>
+<tr class="row-odd"><th class="head"><p>SYMBOL</p></th>
+<th class="head"><p>Meaning</p></th>
+<th class="head"><p>LED</p></th>
+</tr>
+</thead>
+<tbody>
+<tr class="row-even"><td><p>LED_STARTED</p></td>
+<td><p>NuttX has been started</p></td>
+<td><p>OFF</p></td>
+</tr>
+<tr class="row-odd"><td><p>LED_HEAPALLOCATE</p></td>
+<td><p>Heap has been allocated</p></td>
+<td><p>OFF</p></td>
+</tr>
+<tr class="row-even"><td><p>LED_IRQSENABLED</p></td>
+<td><p>Interrupts enabled</p></td>
+<td><p>OFF</p></td>
+</tr>
+<tr class="row-odd"><td><p>LED_STACKCREATED</p></td>
+<td><p>Idle stack created</p></td>
+<td><p>ON</p></td>
+</tr>
+<tr class="row-even"><td><p>LED_INIRQ</p></td>
+<td><p>In an interrupt</p></td>
+<td><p>N/C</p></td>
+</tr>
+<tr class="row-odd"><td><p>LED_SIGNAL</p></td>
+<td><p>In a signal handler</p></td>
+<td><p>N/C</p></td>
+</tr>
+<tr class="row-even"><td><p>LED_ASSERTION</p></td>
+<td><p>An assertion failed</p></td>
+<td><p>N/C</p></td>
+</tr>
+<tr class="row-odd"><td><p>LED_PANIC</p></td>
+<td><p>The system has crashed</p></td>
+<td><p>FLASH</p></td>
+</tr>
+</tbody>
+</table>
+<p>Thus if the LED is statically on, NuttX has successfully booted and is,
+apparently, running normally. If the LED is flashing at approximately
+2Hz, then a fatal error has been detected and the system has halted.</p>
+</div>
+<div class="section" id="buttons">
+<h3>Buttons<a class="headerlink" href="#buttons" title="Permalink to this headline">¶</a></h3>
+<p>There are five user interface switches on the MIMXRT1050 EVK Board:</p>
+<blockquote>
+<div><ul class="simple">
+<li><p>SW1: Power Switch (slide switch fir power from J2)</p></li>
+<li><p>SW2: ON/OFF Button</p></li>
+<li><p>SW3: Power-on Reset button state forces to reset the system power except SNVS domain</p></li>
+<li><p>SW9: Reset button</p></li>
+<li><p>SW8: User button GPIO5-00</p></li>
+</ul>
+</div></blockquote>
+<p>Only the user button is available to the software. It is sensed on the
+WAKEUP pin which will be pulled low when the button is pressed.</p>
+</div>
+</div>
+<div class="section" id="j-link-external-debug-probe">
+<h2>J-Link External Debug Probe<a class="headerlink" href="#j-link-external-debug-probe" title="Permalink to this headline">¶</a></h2>
+<p>Install the J-Link Debug Host Tools and make sure they are in your search path.</p>
+<p>Attach a J-Link 20-pin connector to J21. Check that jumpers J47 and J48 are
+off (they are on by default when boards ship from the factory) to ensure SWD
+signals are disconnected from the OpenSDA microcontroller.</p>
+</div>
+<div class="section" id="configurations">
+<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="can">
+<h3>can<a class="headerlink" href="#can" title="Permalink to this headline">¶</a></h3>
+<p>This is an nsh configuration (see below) with added support of CAN driver.
+FlexCAN3 is chosen as default, the change can be made at System type peripheral
+selection. Please note that only FlexCAN3 and FlexCAN2 is available on this board.</p>
+<p>Bitrate and sample point can be also changed at System type peripheral selection,
+basic values are 1 MHz for bitrate and 0.80 for sample point. The FlexCAN driver
+for imxrt runs at 80 MHz clock frequency.</p>
+<p>The configuration also includes CAN utilities as candump and cansend.</p>
+</div>
+<div class="section" id="canfd">
+<h3>canfd<a class="headerlink" href="#canfd" title="Permalink to this headline">¶</a></h3>
+<p>This is an nsh configuration (see below) with added support of CAN_FD driver.
+FlexCAN3 is chosen as default, please note that only FlexCAN3 is capable of
+providing CAN_FD support.</p>
+<p>Bitrate and sample point can be also changed at System type peripheral selection,
+basic values are 1 MHz for bitrate and 0.80 for sample point for arbitration phase
+and 4 MHz (bitrate) and 0.90 (sample point) for data phase. The FlexCAN driver
+for imxrt runs at 80 MHz clock frequency.</p>
+<p>The configuration also includes CAN utilities as candump and cansend.</p>
+</div>
+<div class="section" id="knsh">
+<h3>knsh<a class="headerlink" href="#knsh" title="Permalink to this headline">¶</a></h3>
+<p>This is identical to the nsh configuration below except that NuttX
+is built as a protected mode, monolithic module and the user applications
+are built separately. It is recommends to use a special make command;
+not just ‘make’ but make with the following two arguments:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>make pass1 pass2
+</pre></div>
+</div>
+<p>In the normal case (just ‘make’), make will attempt to build both user-
+and kernel-mode blobs more or less interleaved. This actual works!
+However, for me it is very confusing so I prefer the above make command:
+Make the user-space binaries first (pass1), then make the kernel-space
+binaries (pass2)</p>
+<p>NOTES:</p>
+<p>At the end of the build, there will be several files in the top-level
+NuttX build directory:</p>
+<dl class="simple">
+<dt>PASS1:</dt><dd><ul class="simple">
+<li><p>nuttx_user.elf - The pass1 user-space ELF file</p></li>
+<li><p>nuttx_user.hex - The pass1 Intel HEX format file (selected in defconfig)</p></li>
+<li><p>User.map - Symbols in the user-space ELF file</p></li>
+</ul>
+</dd>
+<dt>PASS2:</dt><dd><ul class="simple">
+<li><p>nuttx - The pass2 kernel-space ELF file</p></li>
+<li><p>nuttx.hex - The pass2 Intel HEX file (selected in defconfig)</p></li>
+<li><p>System.map - Symbols in the kernel-space ELF file</p></li>
+</ul>
+</dd>
+</dl>
+<p>The J-Link programmer will except files in .hex, .mot, .srec, and .bin
+formats.</p>
+<p>Combining .hex files. If you plan to use the .hex files with your
+debugger or FLASH utility, then you may need to combine the two hex
+files into a single .hex file. Here is how you can do that.</p>
+<p>The ‘tail’ of the nuttx.hex file should look something like this
+(with my comments added beginning with #):</p>
+<div class="highlight-console:: notranslate"><div class="highlight"><pre><span></span>$ tail nuttx.hex
+#xx xxxx 00 data records
+...
+:10 C93C 00 000000000040184000C2010000000000 90
+:10 C94C 00 2400080000801B4000C01B4000001C40 5D
+:10 C95C 00 00401C4000000C4050BF0060FF000100 74
+#xx xxxx 05 Start Linear Address Record
+:04 0000 05 6000 02C1 D4
+#xx xxxx 01 End Of File record
+:00 0000 01 FF
+</pre></div>
+</div>
+<p>Use an editor such as vi to remove the 05 and 01 records.</p>
+<p>The ‘head’ of the nuttx_user.hex file should look something like
+this (again with my comments added beginning with #):</p>
+<div class="highlight-console:: notranslate"><div class="highlight"><pre><span></span>$ head nuttx_user.hex
+#xx xxxx 04 Extended Linear Address Record
+:02 0000 04 6020 7A
+#xx xxxx 00 data records
+:10 0000 00 8905206030002060F2622060FC622060 80
+:10 0010 00 0000242008002420080024205C012420 63
+:10 0020 00 140024203D0020603100206071052060 14
+...
+</pre></div>
+</div>
+<p>Nothing needs to be done here. The nuttx_user.hex file should
+be fine.</p>
+<p>Combine the edited nuttx.hex and un-edited nuttx_user.hex
+file to produce a single combined hex file:</p>
+<div class="highlight-console:: notranslate"><div class="highlight"><pre><span></span>$ cat nuttx.hex nuttx_user.hex >combined.hex
+</pre></div>
+</div>
+<p>Then use the combined.hex file with the to write the FLASH image.
+If you do this a lot, you will probably want to invest a little time
+to develop a tool to automate these steps.</p>
+<p>STATUS: This configuration was added on 8 June 2018 primarily to assure
+that all of the components are in place to support the PROTECTED mode
+build. This configuration, however, has not been verified as of this
+writing.</p>
+</div>
+<div class="section" id="netnsh">
+<h3>netnsh<a class="headerlink" href="#netnsh" title="Permalink to this headline">¶</a></h3>
+<p>This configuration is similar to the nsh configuration except that is
+has networking enabled, both IPv4 and IPv6. This NSH configuration is
+focused on network-related testing.</p>
+</div>
+<div class="section" id="nsh">
+<h3>nsh<a class="headerlink" href="#nsh" title="Permalink to this headline">¶</a></h3>
+<p>Configures the NuttShell (nsh) located at examples/nsh. This NSH
+configuration is focused on low level, command-line driver testing.
+Built-in applications are supported, but none are enabled. This
+configuration does not support a network.</p>
+</div>
+<div class="section" id="lvgl">
+<h3>lvgl<a class="headerlink" href="#lvgl" title="Permalink to this headline">¶</a></h3>
+<p>Configures the Littlev graphic library (lvgl) demo located under
+examples/lvgldemo. This configuration needs the optional LCD model
+RK043FN02H-CT from NXP. The LCD panel comes with the integrated
+capacitive touchscreen sensor FT5336GQQ connected to the LPI2C1 bus,
+address 0x38. NuttX support such touchscreen device via the driver
+ft5x06 (drivers/input/ft5x06.c). At the moment only the polling
+method is available, the board features an interrupt line connected
+to the touchscreen sensor IC.</p>
+<p>IMXRT1064 MCU provides the integrated LCD driver.</p>
+<dl class="simple">
+<dt>The LCD panel features:</dt><dd><ul class="simple">
+<li><p>size 4.3”</p></li>
+<li><p>resolution 480×272 RGB</p></li>
+<li><p>backlight driver</p></li>
+<li><p>dimensions [mm]: 105.5 (W) x 67.2(H) x 4.35(D) Max.</p></li>
+</ul>
+</dd>
+</dl>
+<p>To run the lvgl demo please type “lvgldemo” at nsh prompt:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh> lvgldemo
+</pre></div>
+</div>
+</div>
+</div>
+</div>
+
+
+ </div>
+
+ </div>
+ <footer>
+ <div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
+ <a href="../teensy-4.x/index.html" class="btn btn-neutral float-right" title="Teensy-4.x" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../imxrt1060-evk/index.html" class="btn btn-neutral float-left" title="i.MX RT1060 EVK" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ </div>
+
+ <hr/>
+
+ <div role="contentinfo">
+ <p>
+ © Copyright 2020, The Apache Software Foundation.
+
+ </p>
+ </div>
+
+</footer>
+ </div>
+ </div>
+
+ </section>
+
+ </div>
+
+
+ <script type="text/javascript">
+ jQuery(function () {
+ SphinxRtdTheme.Navigation.enable(true);
+ });
+ </script>
+
+
+
+
+
+
+</body>
+</html>
\ No newline at end of file
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 7f4d903..ce0dc53 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
@@ -62,7 +62,7 @@
<link rel="index" title="Index" href="../../../../../genindex.html" />
<link rel="search" title="Search" href="../../../../../search.html" />
<link rel="next" title="Nordic nRF52" href="../../../nrf52/index.html" />
- <link rel="prev" title="i.MX RT" href="../../index.html" />
+ <link rel="prev" title="i.MX RT1064 EVK" href="../imxrt1064-evk/index.html" />
</head>
<body class="wy-body-for-nav">
@@ -131,6 +131,10 @@
<li class="toctree-l4"><a class="reference internal" href="../../index.html#data-and-instruction-cache">Data and Instruction Cache</a></li>
<li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
<li class="toctree-l4 current"><a class="reference internal" href="../../index.html#supported-boards">Supported Boards</a><ul class="current">
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1020-evk/index.html">i.MX RT1020 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1050-evk/index.html">i.MX RT1050 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1060-evk/index.html">i.MX RT1060 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="../imxrt1064-evk/index.html">i.MX RT1064 EVK</a></li>
<li class="toctree-l5 current"><a class="current reference internal" href="#">Teensy-4.x</a></li>
</ul>
</li>
@@ -410,7 +414,7 @@ selecting <code class="docutils literal notranslate"><span class="pre">CONFIG_TE
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
<a href="../../../nrf52/index.html" class="btn btn-neutral float-right" title="Nordic nRF52" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
- <a href="../../index.html" class="btn btn-neutral float-left" title="i.MX RT" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="../imxrt1064-evk/index.html" class="btn btn-neutral float-left" title="i.MX RT1064 EVK" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
<hr/>
diff --git a/content/docs/latest/platforms/arm/imxrt/index.html b/content/docs/latest/platforms/arm/imxrt/index.html
index b328e1b..d51a3ff 100644
--- a/content/docs/latest/platforms/arm/imxrt/index.html
+++ b/content/docs/latest/platforms/arm/imxrt/index.html
@@ -61,7 +61,7 @@
<link rel="index" title="Index" href="../../../genindex.html" />
<link rel="search" title="Search" href="../../../search.html" />
- <link rel="next" title="Teensy-4.x" href="boards/teensy-4.x/index.html" />
+ <link rel="next" title="i.MX RT1020 EVK" href="boards/imxrt1020-evk/index.html" />
<link rel="prev" title="ARM" href="../index.html" />
</head>
@@ -150,6 +150,10 @@
</ul>
</li>
<li class="toctree-l4"><a class="reference internal" href="#supported-boards">Supported Boards</a><ul>
+<li class="toctree-l5"><a class="reference internal" href="boards/imxrt1020-evk/index.html">i.MX RT1020 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="boards/imxrt1050-evk/index.html">i.MX RT1050 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="boards/imxrt1060-evk/index.html">i.MX RT1060 EVK</a></li>
+<li class="toctree-l5"><a class="reference internal" href="boards/imxrt1064-evk/index.html">i.MX RT1064 EVK</a></li>
<li class="toctree-l5"><a class="reference internal" href="boards/teensy-4.x/index.html">Teensy-4.x</a></li>
</ul>
</li>
@@ -494,6 +498,10 @@ for i.MX RT in NuttX</p>
<h2>Supported Boards<a class="headerlink" href="#supported-boards" title="Permalink to this headline">¶</a></h2>
<div class="toctree-wrapper compound">
<ul>
+<li class="toctree-l1"><a class="reference internal" href="boards/imxrt1020-evk/index.html">i.MX RT1020 EVK</a></li>
+<li class="toctree-l1"><a class="reference internal" href="boards/imxrt1050-evk/index.html">i.MX RT1050 EVK</a></li>
+<li class="toctree-l1"><a class="reference internal" href="boards/imxrt1060-evk/index.html">i.MX RT1060 EVK</a></li>
+<li class="toctree-l1"><a class="reference internal" href="boards/imxrt1064-evk/index.html">i.MX RT1064 EVK</a></li>
<li class="toctree-l1"><a class="reference internal" href="boards/teensy-4.x/index.html">Teensy-4.x</a></li>
</ul>
</div>
@@ -506,7 +514,7 @@ for i.MX RT in NuttX</p>
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
- <a href="boards/teensy-4.x/index.html" class="btn btn-neutral float-right" title="Teensy-4.x" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="boards/imxrt1020-evk/index.html" class="btn btn-neutral float-right" title="i.MX RT1020 EVK" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
<a href="../index.html" class="btn btn-neutral float-left" title="ARM" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
diff --git a/content/docs/latest/platforms/index.html b/content/docs/latest/platforms/index.html
index 3e90c1f..494bb18 100644
--- a/content/docs/latest/platforms/index.html
+++ b/content/docs/latest/platforms/index.html
@@ -212,6 +212,10 @@ series and boards supported in NuttX:</p>
<ul>
<li class="toctree-l1"><a class="reference internal" href="arm/index.html">ARM</a><ul>
<li class="toctree-l2"><a class="reference internal" href="arm/imxrt/index.html">i.MX RT</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="arm/imxrt/boards/imxrt1020-evk/index.html">i.MX RT1020 EVK</a></li>
+<li class="toctree-l3"><a class="reference internal" href="arm/imxrt/boards/imxrt1050-evk/index.html">i.MX RT1050 EVK</a></li>
+<li class="toctree-l3"><a class="reference internal" href="arm/imxrt/boards/imxrt1060-evk/index.html">i.MX RT1060 EVK</a></li>
+<li class="toctree-l3"><a class="reference internal" href="arm/imxrt/boards/imxrt1064-evk/index.html">i.MX RT1064 EVK</a></li>
<li class="toctree-l3"><a class="reference internal" href="arm/imxrt/boards/teensy-4.x/index.html">Teensy-4.x</a></li>
</ul>
</li>
@@ -224,6 +228,7 @@ series and boards supported in NuttX:</p>
</li>
<li class="toctree-l1"><a class="reference internal" href="risc-v/index.html">RISC-V</a><ul>
<li class="toctree-l2"><a class="reference internal" href="risc-v/bl602/index.html">Bouffalo Lab BL602</a></li>
+<li class="toctree-l2"><a class="reference internal" href="risc-v/esp32c3/index.html">Espressif ESP32-C3</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="xtensa/index.html">Xtensa</a><ul>
diff --git a/content/docs/latest/platforms/risc-v/bl602/index.html b/content/docs/latest/platforms/risc-v/bl602/index.html
index e210566..aa055c2 100644
--- a/content/docs/latest/platforms/risc-v/bl602/index.html
+++ b/content/docs/latest/platforms/risc-v/bl602/index.html
@@ -61,7 +61,7 @@
<link rel="index" title="Index" href="../../../genindex.html" />
<link rel="search" title="Search" href="../../../search.html" />
- <link rel="next" title="Xtensa" href="../../xtensa/index.html" />
+ <link rel="next" title="Espressif ESP32-C3" href="../esp32c3/index.html" />
<link rel="prev" title="RISC-V" href="../index.html" />
</head>
@@ -135,6 +135,7 @@
<li class="toctree-l4"><a class="reference internal" href="#peripheral-support">Peripheral Support</a></li>
</ul>
</li>
+<li class="toctree-l3"><a class="reference internal" href="../esp32c3/index.html">Espressif ESP32-C3</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="../../xtensa/index.html">Xtensa</a></li>
@@ -237,7 +238,7 @@
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
- <a href="../../xtensa/index.html" class="btn btn-neutral float-right" title="Xtensa" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../esp32c3/index.html" class="btn btn-neutral float-right" title="Espressif ESP32-C3" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
<a href="../index.html" class="btn btn-neutral float-left" title="RISC-V" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
diff --git a/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.html b/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.html
new file mode 100644
index 0000000..e1089c2
--- /dev/null
+++ b/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.html
@@ -0,0 +1,330 @@
+<!--
+ Documentation/_templates/layout.html
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership. The
+ ASF licenses this file to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance with the
+ License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ License for the specific language governing permissions and limitations
+ under the License.
+-->
+
+
+
+<!DOCTYPE html>
+<html class="writer-html5" lang="en" >
+<head>
+ <meta charset="utf-8" />
+
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+
+ <title>ESP32-C3 DevKit — NuttX latest documentation</title>
+
+
+
+ <link rel="stylesheet" href="../../../../../_static/css/theme.css" type="text/css" />
+ <link rel="stylesheet" href="../../../../../_static/pygments.css" type="text/css" />
+ <link rel="stylesheet" href="../../../../../_static/tabs.css" type="text/css" />
+ <link rel="stylesheet" href="../../../../../_static/custom.css" type="text/css" />
+
+
+
+ <link rel="shortcut icon" href="../../../../../_static/favicon.ico"/>
+
+
+
+
+
+
+
+
+ <!--[if lt IE 9]>
+ <script src="../../../../../_static/js/html5shiv.min.js"></script>
+ <![endif]-->
+
+
+ <script type="text/javascript" id="documentation_options" data-url_root="../../../../../" src="../../../../../_static/documentation_options.js"></script>
+ <script src="../../../../../_static/jquery.js"></script>
+ <script src="../../../../../_static/underscore.js"></script>
+ <script src="../../../../../_static/doctools.js"></script>
+
+ <script type="text/javascript" src="../../../../../_static/js/theme.js"></script>
+
+
+ <link rel="index" title="Index" href="../../../../../genindex.html" />
+ <link rel="search" title="Search" href="../../../../../search.html" />
+</head>
+
+<body class="wy-body-for-nav">
+
+
+ <div class="wy-grid-for-nav">
+
+ <nav data-toggle="wy-nav-shift" class="wy-nav-side">
+ <div class="wy-side-scroll">
+ <div class="wy-side-nav-search" >
+
+
+ <a href="../../../../../index.html" class="icon icon-home"> NuttX
+
+
+
+
+ <img src="../../../../../_static/NuttX.png" class="logo" alt="Logo"/>
+
+ </a>
+
+ <!-- this version selector is quite ugly, should be probably replaced by something
+ more modern -->
+
+ <div class="version-selector">
+ <select onchange="javascript:location.href = this.value;">
+
+ <option value="../../../../../../latest" selected="selected">latest</option>
+
+ <option value="../../../../../../10.0.0" >10.0.0</option>
+
+ <option value="../../../../../../10.0.1" >10.0.1</option>
+
+ </select>
+ </div>
+
+
+<div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../../../search.html" method="get">
+ <input type="text" name="q" placeholder="Search docs" />
+ <input type="hidden" name="check_keywords" value="yes" />
+ <input type="hidden" name="area" value="default" />
+ </form>
+</div>
+
+ </div>
+
+
+ <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
+
+
+
+
+
+
+ <p class="caption"><span class="caption-text">Table of Contents</span></p>
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../index.html">Home</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../introduction/index.html">Introduction</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../quickstart/index.html">Getting Started</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../introduction/inviolables.html">The Inviolable Principles of NuttX</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../index.html">Supported Platforms</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../components/index.html">OS Components</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../applications/index.html">Applications</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../reference/index.html">API Reference</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../faq/index.html">FAQ</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../guides/index.html">Guides</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../contributing/index.html">Contributing</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../../../glossary.html">Glossary</a></li>
+</ul>
+
+
+
+ </div>
+
+ </div>
+ </nav>
+
+ <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
+
+
+ <nav class="wy-nav-top" aria-label="top navigation">
+
+ <i data-toggle="wy-nav-top" class="fa fa-bars"></i>
+ <a href="../../../../../index.html">NuttX</a>
+
+ </nav>
+
+
+ <div class="wy-nav-content">
+
+ <div class="rst-content">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<div role="navigation" aria-label="breadcrumbs navigation">
+
+ <ul class="wy-breadcrumbs">
+
+ <li><a href="../../../../../index.html" class="icon icon-home"></a> »</li>
+
+ <li>ESP32-C3 DevKit</li>
+
+
+ <li class="wy-breadcrumbs-aside">
+
+
+ <a href="../../../../../_sources/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.rst.txt" rel="nofollow"> View page source</a>
+
+
+ </li>
+
+ </ul>
+
+
+ <hr/>
+</div>
+ <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
+ <div itemprop="articleBody">
+
+ <div class="section" id="esp32-c3-devkit">
+<h1>ESP32-C3 DevKit<a class="headerlink" href="#esp32-c3-devkit" title="Permalink to this headline">¶</a></h1>
+<p>The ESP32-C3 DevKit is an entry-level development board equipped with either
+an ESP32-C3-WROOM-02 or an ESP32-C3-MINI-1.
+ESP32-C3-WROOM-02 and ESP32-C3-MINI-1 are SoMs based on the RISC-V ESP32-C3 CPU.</p>
+<p>Most of the I/O pins are broken out to the pin headers on both sides for easy
+interfacing. Developers can either connect peripherals with jumper wires or
+mount ESP32-C3 DevKit on a breadboard.</p>
+<table class="docutils align-center">
+<colgroup>
+<col style="width: 50%" />
+<col style="width: 50%" />
+</colgroup>
+<tbody>
+<tr class="row-odd"><td><div class="figure align-center" id="id1">
+<img alt="../../../../../_images/ESP32-C3-DevKitC-02-v1.1.png" src="../../../../../_images/ESP32-C3-DevKitC-02-v1.1.png" />
+<p class="caption"><span class="caption-text">ESP32-C3-DevKitC-02</span><a class="headerlink" href="#id1" title="Permalink to this image">¶</a></p>
+</div>
+</td>
+<td><div class="figure align-center" id="id2">
+<img alt="../../../../../_images/ESP32-C3-DevKitM-1-v1.0.png" src="../../../../../_images/ESP32-C3-DevKitM-1-v1.0.png" />
+<p class="caption"><span class="caption-text">ESP32-C3-DevKitM-1</span><a class="headerlink" href="#id2" title="Permalink to this image">¶</a></p>
+</div>
+</td>
+</tr>
+</tbody>
+</table>
+<div class="section" id="buttons-and-leds">
+<h2>Buttons and LEDs<a class="headerlink" href="#buttons-and-leds" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="buttons">
+<h3>Buttons<a class="headerlink" href="#buttons" title="Permalink to this headline">¶</a></h3>
+<p>There are two buttons labeled Boot and RST. The RST button is not available
+to software. It pulls the chip enable line that doubles as a reset line.</p>
+<p>The BOOT button is connected to IO9. On reset it is used as a strapping
+pin to determine whether the chip boots normally or into the serial
+bootloader. After reset, however, the BOOT button can be used for software
+input.</p>
+</div>
+<div class="section" id="leds">
+<h3>LEDs<a class="headerlink" href="#leds" title="Permalink to this headline">¶</a></h3>
+<p>There is one on-board LED that indicates the presence of power.
+Another WS2812 LED is connected to GPIO8 and is available for software.</p>
+</div>
+</div>
+<div class="section" id="configurations">
+<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this headline">¶</a></h2>
+<div class="section" id="nsh">
+<h3>nsh<a class="headerlink" href="#nsh" title="Permalink to this headline">¶</a></h3>
+<p>Basic configuration to run the NuttShell (nsh).</p>
+<div class="section" id="gpio">
+<h4>gpio<a class="headerlink" href="#gpio" title="Permalink to this headline">¶</a></h4>
+<p>This is a test for the GPIO driver. It uses GPIO1 and GPIO2 as outputs and
+GPIO9 as an interrupt pin.</p>
+<p>At the nsh, we can turn the outputs on and off with the following:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh> gpio -o 1 /dev/gpout0
+nsh> gpio -o 1 /dev/gpout1
+
+nsh> gpio -o 0 /dev/gpout0
+nsh> gpio -o 0 /dev/gpout1
+</pre></div>
+</div>
+<p>We can use the interrupt pin to send a signal when the interrupt fires:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh> gpio -w 14 /dev/gpint2
+</pre></div>
+</div>
+<p>The pin is configured as a rising edge interrupt, so after issuing the
+above command, connect it to 3.3V.</p>
+</div>
+</div>
+<div class="section" id="watchdog">
+<h3>watchdog<a class="headerlink" href="#watchdog" title="Permalink to this headline">¶</a></h3>
+<p>This configuration tests the watchdog timers. It includes the 2 MWDTS,
+adds driver support, registers the WDTs as devices and includes the watchdog
+example application.</p>
+<p>To test it, just run the following command:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh> wdog -i /dev/watchdogX
+</pre></div>
+</div>
+<p>Where X is the watchdog instance.</p>
+</div>
+<div class="section" id="watcher">
+<h3>watcher<a class="headerlink" href="#watcher" title="Permalink to this headline">¶</a></h3>
+<p>This configuration tests the watchdog timers in the capture mode.
+It includes the 2 MWDTS, adds driver support, registers the WDTs as devices
+and includes the watcher and watched example applications.</p>
+<p>To test it, just run the following command:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh> watcher
+nsh> watched
+</pre></div>
+</div>
+</div>
+</div>
+</div>
+
+
+ </div>
+
+ </div>
+ <footer>
+
+ <hr/>
+
+ <div role="contentinfo">
+ <p>
+ © Copyright 2020, The Apache Software Foundation.
+
+ </p>
+ </div>
+
+</footer>
+ </div>
+ </div>
+
+ </section>
+
+ </div>
+
+
+ <script type="text/javascript">
+ jQuery(function () {
+ SphinxRtdTheme.Navigation.enable(true);
+ });
+ </script>
+
+
+
+
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/content/docs/latest/platforms/risc-v/esp32c3/index.html b/content/docs/latest/platforms/risc-v/esp32c3/index.html
new file mode 100644
index 0000000..24b550c
--- /dev/null
+++ b/content/docs/latest/platforms/risc-v/esp32c3/index.html
@@ -0,0 +1,445 @@
+<!--
+ Documentation/_templates/layout.html
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership. The
+ ASF licenses this file to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance with the
+ License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ License for the specific language governing permissions and limitations
+ under the License.
+-->
+
+
+
+<!DOCTYPE html>
+<html class="writer-html5" lang="en" >
+<head>
+ <meta charset="utf-8" />
+
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+
+ <title>Espressif ESP32-C3 — NuttX latest documentation</title>
+
+
+
+ <link rel="stylesheet" href="../../../_static/css/theme.css" type="text/css" />
+ <link rel="stylesheet" href="../../../_static/pygments.css" type="text/css" />
+ <link rel="stylesheet" href="../../../_static/tabs.css" type="text/css" />
+ <link rel="stylesheet" href="../../../_static/custom.css" type="text/css" />
+
+
+
+ <link rel="shortcut icon" href="../../../_static/favicon.ico"/>
+
+
+
+
+
+
+
+
+ <!--[if lt IE 9]>
+ <script src="../../../_static/js/html5shiv.min.js"></script>
+ <![endif]-->
+
+
+ <script type="text/javascript" id="documentation_options" data-url_root="../../../" src="../../../_static/documentation_options.js"></script>
+ <script src="../../../_static/jquery.js"></script>
+ <script src="../../../_static/underscore.js"></script>
+ <script src="../../../_static/doctools.js"></script>
+
+ <script type="text/javascript" src="../../../_static/js/theme.js"></script>
+
+
+ <link rel="index" title="Index" href="../../../genindex.html" />
+ <link rel="search" title="Search" href="../../../search.html" />
+ <link rel="next" title="Xtensa" href="../../xtensa/index.html" />
+ <link rel="prev" title="Bouffalo Lab BL602" href="../bl602/index.html" />
+</head>
+
+<body class="wy-body-for-nav">
+
+
+ <div class="wy-grid-for-nav">
+
+ <nav data-toggle="wy-nav-shift" class="wy-nav-side">
+ <div class="wy-side-scroll">
+ <div class="wy-side-nav-search" >
+
+
+ <a href="../../../index.html" class="icon icon-home"> NuttX
+
+
+
+
+ <img src="../../../_static/NuttX.png" class="logo" alt="Logo"/>
+
+ </a>
+
+ <!-- this version selector is quite ugly, should be probably replaced by something
+ more modern -->
+
+ <div class="version-selector">
+ <select onchange="javascript:location.href = this.value;">
+
+ <option value="../../../../latest" selected="selected">latest</option>
+
+ <option value="../../../../10.0.0" >10.0.0</option>
+
+ <option value="../../../../10.0.1" >10.0.1</option>
+
+ </select>
+ </div>
+
+
+<div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <input type="text" name="q" placeholder="Search docs" />
+ <input type="hidden" name="check_keywords" value="yes" />
+ <input type="hidden" name="area" value="default" />
+ </form>
+</div>
+
+ </div>
+
+
+ <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
+
+
+
+
+
+
+ <p class="caption"><span class="caption-text">Table of Contents</span></p>
+<ul class="current">
+<li class="toctree-l1"><a class="reference internal" href="../../../index.html">Home</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../introduction/index.html">Introduction</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../quickstart/index.html">Getting Started</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../introduction/inviolables.html">The Inviolable Principles of NuttX</a></li>
+<li class="toctree-l1 current"><a class="reference internal" href="../../index.html">Supported Platforms</a><ul class="current">
+<li class="toctree-l2"><a class="reference internal" href="../../arm/index.html">ARM</a></li>
+<li class="toctree-l2 current"><a class="reference internal" href="../index.html">RISC-V</a><ul class="current">
+<li class="toctree-l3"><a class="reference internal" href="../bl602/index.html">Bouffalo Lab BL602</a></li>
+<li class="toctree-l3 current"><a class="current reference internal" href="#">Espressif ESP32-C3</a><ul>
+<li class="toctree-l4"><a class="reference internal" href="#esp32-c3-toolchain">ESP32-C3 Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#second-stage-bootloader-and-partition-table">Second stage bootloader and partition table</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#building-and-flashing">Building and flashing</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#debugging-with-openocd">Debugging with OpenOCD</a></li>
+<li class="toctree-l4"><a class="reference internal" href="#peripheral-support">Peripheral Support</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="../../xtensa/index.html">Xtensa</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="../../../components/index.html">OS Components</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../applications/index.html">Applications</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../reference/index.html">API Reference</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../faq/index.html">FAQ</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../guides/index.html">Guides</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../contributing/index.html">Contributing</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../../../glossary.html">Glossary</a></li>
+</ul>
+
+
+
+ </div>
+
+ </div>
+ </nav>
+
+ <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
+
+
+ <nav class="wy-nav-top" aria-label="top navigation">
+
+ <i data-toggle="wy-nav-top" class="fa fa-bars"></i>
+ <a href="../../../index.html">NuttX</a>
+
+ </nav>
+
+
+ <div class="wy-nav-content">
+
+ <div class="rst-content">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<div role="navigation" aria-label="breadcrumbs navigation">
+
+ <ul class="wy-breadcrumbs">
+
+ <li><a href="../../../index.html" class="icon icon-home"></a> »</li>
+
+ <li><a href="../../index.html">Supported Platforms</a> »</li>
+
+ <li><a href="../index.html">RISC-V</a> »</li>
+
+ <li>Espressif ESP32-C3</li>
+
+
+ <li class="wy-breadcrumbs-aside">
+
+
+ <a href="../../../_sources/platforms/risc-v/esp32c3/index.rst.txt" rel="nofollow"> View page source</a>
+
+
+ </li>
+
+ </ul>
+
+
+ <hr/>
+</div>
+ <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
+ <div itemprop="articleBody">
+
+ <div class="section" id="espressif-esp32-c3">
+<h1>Espressif ESP32-C3<a class="headerlink" href="#espressif-esp32-c3" title="Permalink to this headline">¶</a></h1>
+<p>The ESP32-C3 is an ultra-low-power and highly integrated SoC with a RISC-V
+core and supports 2.4 GHz Wi-Fi and Bluetooth Low Energy.</p>
+<ul class="simple">
+<li><p>Address Space
+- 800 KB of internal memory address space accessed from the instruction bus
+- 560 KB of internal memory address space accessed from the data bus
+- 1016 KB of peripheral address space
+- 8 MB of external memory virtual address space accessed from the instruction bus
+- 8 MB of external memory virtual address space accessed from the data bus
+- 480 KB of internal DMA address space</p></li>
+<li><p>Internal Memory
+- 384 KB ROM
+- 400 KB SRAM (16 KB can be configured as Cache)
+- 8 KB of SRAM in RTC</p></li>
+<li><p>External Memory
+- Up to 16 MB of external flash</p></li>
+<li><p>Peripherals
+- 35 peripherals</p></li>
+<li><p>GDMA
+- 7 modules are capable of DMA operations.</p></li>
+</ul>
+<div class="section" id="esp32-c3-toolchain">
+<h2>ESP32-C3 Toolchain<a class="headerlink" href="#esp32-c3-toolchain" title="Permalink to this headline">¶</a></h2>
+<p>A generic RISC-V toolchain can be used to build ESP32-C3 projects.
+SiFive’s toolchain can be downloaded from: <a class="reference external" href="https://static.dev.sifive.com/dev-tools/riscv64-unknown-elf-gcc-8.3.0-2019.08.0-x86_64-linux-ubuntu14.tar.gz">https://static.dev.sifive.com/dev-tools/riscv64-unknown-elf-gcc-8.3.0-2019.08.0-x86_64-linux-ubuntu14.tar.gz</a></p>
+</div>
+<div class="section" id="second-stage-bootloader-and-partition-table">
+<h2>Second stage bootloader and partition table<a class="headerlink" href="#second-stage-bootloader-and-partition-table" title="Permalink to this headline">¶</a></h2>
+<p>The NuttX port for now relies on IDF’s second stage bootloader to carry on some hardware
+initializations. The binaries for the bootloader and the partition table can be found in
+this repository: <a class="reference external" href="https://github.com/espressif/esp-nuttx-bootloader">https://github.com/espressif/esp-nuttx-bootloader</a>
+That repository contains a dummy IDF project that’s used to build the bootloader and
+partition table, these are then presented as Github assets and can be downloaded
+from: <a class="reference external" href="https://github.com/espressif/esp-nuttx-bootloader/releases">https://github.com/espressif/esp-nuttx-bootloader/releases</a>
+Download <code class="docutils literal notranslate"><span class="pre">bootloader-esp32c3.bin</span></code> and <code class="docutils literal notranslate"><span class="pre">partition-table-esp32c3.bin</span></code> and place them
+in a folder, the path to this folder will be used later to program them. This
+can be: <code class="docutils literal notranslate"><span class="pre">../esp-bins</span></code></p>
+</div>
+<div class="section" id="building-and-flashing">
+<h2>Building and flashing<a class="headerlink" href="#building-and-flashing" title="Permalink to this headline">¶</a></h2>
+<p>First make sure that <code class="docutils literal notranslate"><span class="pre">esptool.py</span></code> is installed. This tool is used to convert
+the ELF to a compatible ESP32 image and to flash the image into the board.
+It can be installed with: <code class="docutils literal notranslate"><span class="pre">pip</span> <span class="pre">install</span> <span class="pre">esptool</span></code>.</p>
+<p>Configure the NUttX project: <code class="docutils literal notranslate"><span class="pre">./tools/configure.sh</span> <span class="pre">esp32c3-devkit:nsh</span></code>
+Run <code class="docutils literal notranslate"><span class="pre">make</span></code> to build the project. Note that the conversion mentioned above is
+included in the build process.
+The <cite>esptool.py</cite> command to flash all the binaries is:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>esptool.py --chip esp32c3 --port /dev/ttyUSBXX --baud 921600 write_flash 0x0 bootloader.bin 0x8000 partition-table.bin 0x10000 nuttx.bin
+</pre></div>
+</div>
+<p>However, this is also included in the build process and we can build and flash with:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>make download ESPTOOL_PORT=<port> ESPTOOL_BINDIR=../esp-bins
+</pre></div>
+</div>
+<p>Where <code class="docutils literal notranslate"><span class="pre"><port></span></code> is typically <code class="docutils literal notranslate"><span class="pre">/dev/ttyUSB0</span></code> or similar and <code class="docutils literal notranslate"><span class="pre">../esp-bins</span></code> is
+the path to the folder containing the bootloader and the partition table
+for the ESP32-C3 as explained above.
+Note that this step is required only one time. Once the bootloader and partition
+table are flashed, we don’t need to flash them again. So subsequent builds
+would just require: <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">download</span> <span class="pre">ESPTOOL_PORT=/dev/ttyUSBXX</span></code></p>
+</div>
+<div class="section" id="debugging-with-openocd">
+<h2>Debugging with OpenOCD<a class="headerlink" href="#debugging-with-openocd" title="Permalink to this headline">¶</a></h2>
+<p>Download and build OpenOCD from Espressif, that can be found in
+<a class="reference external" href="https://github.com/espressif/openocd-esp32">https://github.com/espressif/openocd-esp32</a></p>
+<p>If you have an ESP32-C3 ECO3, no external JTAG is required to debug, the ESP32-C3
+integrates a USB-to-JTAG adapter.</p>
+<p>OpenOCD can then be used:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>openocd -c 'set ESP_RTOS none' -f board/esp32c3-builtin.cfg
+</pre></div>
+</div>
+<p>For versions prior to ESP32-C3 ECO3, an external JTAG adapter is needed.
+It can be connected as follows:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>TMS -> GPIO4
+TDI -> GPIO5
+TCK -> GPIO6
+TDO -> GPIO7
+</pre></div>
+</div>
+<p>Furthermore, an efuse needs to be burnt to be able to debug:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>espefuse.py -p <port> burn_efuse DIS_USB_JTAG
+</pre></div>
+</div>
+<p>OpenOCD can then be used:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>openocd -c 'set ESP_RTOS none' -f board/esp32c3-ftdi.cfg
+</pre></div>
+</div>
+</div>
+<div class="section" id="peripheral-support">
+<h2>Peripheral Support<a class="headerlink" href="#peripheral-support" title="Permalink to this headline">¶</a></h2>
+<p>The following list indicates the state of peripherals’ support in NuttX:</p>
+<table class="docutils align-default">
+<colgroup>
+<col style="width: 45%" />
+<col style="width: 32%" />
+<col style="width: 23%" />
+</colgroup>
+<thead>
+<tr class="row-odd"><th class="head"><p>Peripheral</p></th>
+<th class="head"><p>Support</p></th>
+<th class="head"><p>NOTES</p></th>
+</tr>
+</thead>
+<tbody>
+<tr class="row-even"><td><p>GPIO</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>UART</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>SPI</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>I2C</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>DMA</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>Wifi</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>SPIFLASH</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>Timers</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>Watchdog</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>RTC</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>RNG</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>AES</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>eFuse</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>ADC</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>Bluetooth</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>LED_PWM</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-even"><td><p>SHA</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>RSA</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+
+
+ </div>
+
+ </div>
+ <footer>
+ <div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
+ <a href="../../xtensa/index.html" class="btn btn-neutral float-right" title="Xtensa" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../bl602/index.html" class="btn btn-neutral float-left" title="Bouffalo Lab BL602" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ </div>
+
+ <hr/>
+
+ <div role="contentinfo">
+ <p>
+ © Copyright 2020, The Apache Software Foundation.
+
+ </p>
+ </div>
+
+</footer>
+ </div>
+ </div>
+
+ </section>
+
+ </div>
+
+
+ <script type="text/javascript">
+ jQuery(function () {
+ SphinxRtdTheme.Navigation.enable(true);
+ });
+ </script>
+
+
+
+
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/content/docs/latest/platforms/risc-v/index.html b/content/docs/latest/platforms/risc-v/index.html
index 7ceda05..bc3b0fa 100644
--- a/content/docs/latest/platforms/risc-v/index.html
+++ b/content/docs/latest/platforms/risc-v/index.html
@@ -128,6 +128,7 @@
<li class="toctree-l2"><a class="reference internal" href="../arm/index.html">ARM</a></li>
<li class="toctree-l2 current"><a class="current reference internal" href="#">RISC-V</a><ul>
<li class="toctree-l3"><a class="reference internal" href="bl602/index.html">Bouffalo Lab BL602</a></li>
+<li class="toctree-l3"><a class="reference internal" href="esp32c3/index.html">Espressif ESP32-C3</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="../xtensa/index.html">Xtensa</a></li>
@@ -215,6 +216,7 @@
<div class="toctree-wrapper compound">
<ul>
<li class="toctree-l1"><a class="reference internal" href="bl602/index.html">Bouffalo Lab BL602</a></li>
+<li class="toctree-l1"><a class="reference internal" href="esp32c3/index.html">Espressif ESP32-C3</a></li>
</ul>
</div>
</div>
diff --git a/content/docs/latest/platforms/xtensa/index.html b/content/docs/latest/platforms/xtensa/index.html
index e44270a..6111801 100644
--- a/content/docs/latest/platforms/xtensa/index.html
+++ b/content/docs/latest/platforms/xtensa/index.html
@@ -62,7 +62,7 @@
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Espressif ESP32" href="esp32/index.html" />
- <link rel="prev" title="Bouffalo Lab BL602" href="../risc-v/bl602/index.html" />
+ <link rel="prev" title="Espressif ESP32-C3" href="../risc-v/esp32c3/index.html" />
</head>
<body class="wy-body-for-nav">
@@ -226,7 +226,7 @@
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
<a href="esp32/index.html" class="btn btn-neutral float-right" title="Espressif ESP32" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
- <a href="../risc-v/bl602/index.html" class="btn btn-neutral float-left" title="Bouffalo Lab BL602" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="../risc-v/esp32c3/index.html" class="btn btn-neutral float-left" title="Espressif ESP32-C3" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
<hr/>
diff --git a/content/docs/latest/reference/user/07_signals.html b/content/docs/latest/reference/user/07_signals.html
index 564d55f..0abf94c 100644
--- a/content/docs/latest/reference/user/07_signals.html
+++ b/content/docs/latest/reference/user/07_signals.html
@@ -471,7 +471,7 @@ name.</p>
<dl class="c function">
<dt id="c.sigaction">
-<span class="pre">int</span> <code class="sig-name descname"><span class="pre">sigaction</span></code><span class="sig-paren">(</span><span class="pre">int</span> <em><span class="pre">signo</span></em>, <em class="property"><span class="pre">const</span></em> <em class="property"><span class="pre">struct</span></em> <a class="reference internal" href="structures.html#c.sigaction" title="sigaction"><span class="pre">sigaction</span></a> <span class="pre">*</span><em><span class="pre">act [...]
+<span class="pre">int</span> <code class="sig-name descname"><span class="pre">sigaction</span></code><span class="sig-paren">(</span><span class="pre">int</span> <em><span class="pre">signo</span></em>, <em class="property"><span class="pre">const</span></em> <em class="property"><span class="pre">struct</span></em> <a class="reference internal" href="structures.html#c.sigaction" title="sigaction"><span class="pre">sigaction</span></a> <span class="pre">*</span><em><span class="pre">act [...]
<dd><p>Allows the calling task to examine and/or
specify the action to be associated with a specific signal.</p>
<p>The structure sigaction, used to describe an action to be taken, is
diff --git a/content/docs/latest/searchindex.js b/content/docs/latest/searchindex.js
index f7df5eb..615d0ac 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 3298d0d..7b5374d 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, 12 May 2021 00:36:29 +0000</pubDate>
- <lastBuildDate>Wed, 12 May 2021 00:36:29 +0000</lastBuildDate>
+ <pubDate>Thu, 13 May 2021 00:45:05 +0000</pubDate>
+ <lastBuildDate>Thu, 13 May 2021 00:45:05 +0000</lastBuildDate>
<generator>Jekyll v3.8.5</generator>
<item>