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 8f2fcca Publishing web: 42e9e27963415ec1359277228669d6b9c71c48d1
docs: e87a20e648843ce53237fdb398417868685af2a1
8f2fcca is described below
commit 8f2fcca899428bdd9b7ea12bc8bbc1dcc3d50fba
Author: Alin <[email protected]>
AuthorDate: Sat Jun 18 00:15:26 2022 +0000
Publishing web: 42e9e27963415ec1359277228669d6b9c71c48d1 docs:
e87a20e648843ce53237fdb398417868685af2a1
---
content/docs/10.0.0/index.html | 2 +-
content/docs/10.0.1/index.html | 2 +-
content/docs/10.1.0/index.html | 2 +-
content/docs/10.2.0/index.html | 2 +-
content/docs/10.3.0/index.html | 2 +-
content/docs/latest/_images/esp32-s3-devkitc-1.png | Bin 0 -> 479204 bytes
content/docs/latest/_images/esp32s3_eye.png | Bin 0 -> 196123 bytes
.../esp32s3/boards/esp32s3-devkit/index.rst.txt | 57 +++
.../esp32s3/boards/esp32s3-eye/index.rst.txt | 93 ++++
.../platforms/xtensa/esp32s3/index.rst.txt | 184 ++++++++
content/docs/latest/components/index.html | 4 +-
content/docs/latest/index.html | 2 +-
content/docs/latest/objects.inv | Bin 33688 -> 34050 bytes
content/docs/latest/platforms/index.html | 5 +
.../xtensa/esp32/boards/esp32-devkitc/index.html | 1 +
.../esp32/boards/esp32-wrover-kit/index.html | 5 +-
.../docs/latest/platforms/xtensa/esp32/index.html | 1 +
.../boards/esp32s3-devkit}/index.html | 197 ++------
.../boards/esp32s3-eye}/index.html | 227 +++------
.../platforms/xtensa/{esp32 => esp32s3}/index.html | 510 +++------------------
content/docs/latest/platforms/xtensa/index.html | 2 +
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 +-
23 files changed, 531 insertions(+), 773 deletions(-)
diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index 0eb61ef..43d019f 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: 17 June 22 at 00:10</p>
+<p>Last Updated: 18 June 22 at 00:12</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 3b77c58..31157b1 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -217,7 +217,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: 17 June 22 at 00:11</p>
+<p>Last Updated: 18 June 22 at 00:12</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.1.0/index.html b/content/docs/10.1.0/index.html
index d0438ca..00b098d 100644
--- a/content/docs/10.1.0/index.html
+++ b/content/docs/10.1.0/index.html
@@ -217,7 +217,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: 17 June 22 at 00:11</p>
+<p>Last Updated: 18 June 22 at 00:12</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.2.0/index.html b/content/docs/10.2.0/index.html
index fc8ae89..baa08aa 100644
--- a/content/docs/10.2.0/index.html
+++ b/content/docs/10.2.0/index.html
@@ -218,7 +218,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: 17 June 22 at 00:12</p>
+<p>Last Updated: 18 June 22 at 00:13</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.3.0/index.html b/content/docs/10.3.0/index.html
index fc8ae89..baa08aa 100644
--- a/content/docs/10.3.0/index.html
+++ b/content/docs/10.3.0/index.html
@@ -218,7 +218,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: 17 June 22 at 00:12</p>
+<p>Last Updated: 18 June 22 at 00:13</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-s3-devkitc-1.png
b/content/docs/latest/_images/esp32-s3-devkitc-1.png
new file mode 100644
index 0000000..628672a
Binary files /dev/null and b/content/docs/latest/_images/esp32-s3-devkitc-1.png
differ
diff --git a/content/docs/latest/_images/esp32s3_eye.png
b/content/docs/latest/_images/esp32s3_eye.png
new file mode 100644
index 0000000..4d5a7c3
Binary files /dev/null and b/content/docs/latest/_images/esp32s3_eye.png differ
diff --git
a/content/docs/latest/_sources/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.rst.txt
b/content/docs/latest/_sources/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.rst.txt
new file mode 100644
index 0000000..a5e69ec
--- /dev/null
+++
b/content/docs/latest/_sources/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.rst.txt
@@ -0,0 +1,57 @@
+==============
+ESP32S3-DevKit
+==============
+
+The `ESP32S3 DevKit
<https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html>`_
is a development board for the ESP32-S3 SoC from Espressif, based on a
ESP32-S3-WROOM-1 module.
+
+.. list-table::
+ :align: center
+
+ * - .. figure:: esp32-s3-devkitc-1.png
+ :align: center
+
+Features
+========
+
+ - ESP32-S3-WROOM-1 Module
+ - USB-to-UART bridge via micro USB port
+ - Power LED
+ - EN and BOOT buttons (BOOT accessible to user)
+ - SPI FLASH (size varies according to model
+
+Serial Console
+==============
+
+UART0 is, by default, the serial console. It connects to the on-board
+CP2102 converter and is available on the USB connector USB CON8 (J1).
+
+It will show up as /dev/ttyUSB[n] where [n] will probably be 0.
+
+Buttons and LEDs
+================
+
+Buttons
+-------
+
+There are two buttons labeled Boot and EN. The EN button is not available
+to software. It pulls the chip enable line that doubles as a reset line.
+
+The BOOT button is connected to IO0. 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 are several on-board LEDs for that indicate the presence of power
+and USB activity. None of these are available for use by software.
+
+Configurations
+==============
+
+nsh
+---
+
+Basic NuttShell configuration (console enabled in UART0, exposed via
+USB connection by means of CP2102 converter, at 115200 bps).
diff --git
a/content/docs/latest/_sources/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.rst.txt
b/content/docs/latest/_sources/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.rst.txt
new file mode 100644
index 0000000..6d6c13d
--- /dev/null
+++
b/content/docs/latest/_sources/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.rst.txt
@@ -0,0 +1,93 @@
+=============
+ESP32-S3-EYE
+=============
+
+The `ESP32-S3-EYE
<https://github.com/espressif/esp-who/blob/master/docs/en/get-started/ESP32-S3-EYE_Getting_Started_Guide.md>`_
is a small-sized AI development board from Espressif featuring the ESP32-S3
CPU with a 2-Megapixel camera, an LCD display, a microphone, an 8 MB Octal
PSRAM and an 8 MB flash.
+
+.. list-table::
+ :align: center
+
+ * - .. figure:: esp32s3_eye.png
+ :align: center
+
+Features
+========
+
+ - ESP32-S3 WROOM-1 Module
+ - USB micro USB port (it uses internal USB JTAG SERIAL device for flashing)
+ - Power LED
+ - LCD Display
+ - 2-MP Camera
+ - MEMS Microphone
+ - 8MB Octal PSRAM
+ - 8MB SPI Flash
+ - RST and BOOT buttons (BOOT accessible to user)
+
+Configurations
+==============
+
+nsh
+---
+
+Basic NuttShell configuration (console enabled in USB JTAG SERIAL Device,
exposed via
+USB connection at 9600 bps).
+
+You can configure this board profile this way:
+
+ $ cd nuttxspace/nuttx
+ $ ./tools/configure.sh esp32s3-eye:nsh
+
+Flashing
+========
+
+Because ESP32-S3 doesn't use an external USB/Serial chip like others ESP32
+boards you should put it in programming mode this way:
+
+ 1) Press and hold BOOT and RESET (RST) buttons at same time;
+ 2) Release the RESET button and keep BOOT button pressed;
+ 3) After one or more seconds release the BOOT button;
+ 4) Run the flashing command: make flash ESPTOOL_PORT=/dev/ttyACM0
+
+Serial Console
+==============
+
+The internal USB JTAG SERIAL Device, by default, is used as serial console.
+It is normally detected by Linux host as a USB CDC/ACM serial device.
+
+It will show up as /dev/ttyACM[n] where [n] will probably be 0.
+
+You can use minicom with /dev/ttyACM0 port at 9600 8n1 or picocom this way:
+
+ $ picocom -b9600 /dev/ttyACM0
+
+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 IO0. 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 are several on-board LEDs for that indicate the presence of power
+and USB activity. None of these are available for use by software.
+
+Pin Mapping
+===========
+
+.. todo:: To be updated
+
+===== ========== ==========
+Pin Signal Notes
+===== ========== ==========
+? ? ?
+===== ========== ==========
+
diff --git
a/content/docs/latest/_sources/platforms/xtensa/esp32s3/index.rst.txt
b/content/docs/latest/_sources/platforms/xtensa/esp32s3/index.rst.txt
new file mode 100644
index 0000000..0b511e7
--- /dev/null
+++ b/content/docs/latest/_sources/platforms/xtensa/esp32s3/index.rst.txt
@@ -0,0 +1,184 @@
+==================
+Espressif ESP32-S3
+==================
+
+The ESP32-S3 is a series of single and dual-core SoCs from Espressif
+based on Harvard architecture Xtensa LX7 CPUs and with on-chip support
+for Bluetooth and Wi-Fi.
+
+All embedded memory, external memory and peripherals are located on the
+data bus and/or the instruction bus of these CPUs. With some minor
+exceptions, the address mapping of two CPUs is symmetric, meaning they
+use the same addresses to access the same memory. Multiple peripherals in
+the system can access embedded memory via DMA.
+
+On dual-core SoCs, the two CPUs are typically named "PRO_CPU" and "APP_CPU"
+(for "protocol" and "application"), however for most purposes the
+two CPUs are interchangeable.
+
+Toolchain
+=========
+
+You can use the prebuilt `toolchain
<https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/tools/idf-tools.html#xtensa-esp32s3-elf>`__
+for Xtensa architecture and `OpenOCD
<https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/tools/idf-tools.html#openocd-esp32>`__
+for ESP32-S3 by Espressif.
+
+For flashing firmware, you will need to install ``esptool.py`` by running::
+
+ $ pip install esptool
+
+Building from source
+--------------------
+
+You can also build the toolchain yourself. The steps to
+build the toolchain with crosstool-NG on Linux are as follows
+
+.. code-block:: console
+
+ $ git clone https://github.com/espressif/crosstool-NG.git
+ $ cd crosstool-NG
+ $ git submodule update --init
+
+ $ ./bootstrap && ./configure --enable-local && make
+
+ $ ./ct-ng xtensa-esp32s3-elf
+ $ ./ct-ng build
+
+ $ chmod -R u+w builds/xtensa-esp32s3-elf
+
+ $ export PATH="crosstool-NG/builds/xtensa-esp32-elf/bin:$PATH"
+
+These steps are given in the setup guide in
+`ESP-IDF documentation
<https://docs.espressif.com/projects/esp-idf/en/latest/get-started/linux-setup-scratch.html>`_.
+
+Flashing
+========
+
+Firmware for ESP32-S3 is flashed via the USB/UART or internal USB DEVICE JTAG
interface using the
+``esptool.py`` tool.
+It's a two step process where the first converts the ELF file into a ESP32-S3
compatible binary
+and the second flashes it to the board. These steps are included into the
build system and you can
+flash your NuttX firmware simply by running::
+
+ $ make flash ESPTOOL_PORT=<port>
+
+where ``<port>`` is typically ``/dev/ttyUSB0`` or similar. You can change the
baudrate by passing ``ESPTOOL_BAUD``.
+
+Bootloader and partitions
+-------------------------
+
+ESP32-S3 requires a bootloader to be flashed as well as a set of FLASH
partitions. This is only needed the first time
+(or any time you which to modify either of these). An easy way is to use
prebuilt binaries for NuttX `from here
<https://github.com/espressif/esp-nuttx-bootloader>`_. In there you will find
instructions to rebuild these if necessary.
+Once you downloaded both binaries, you can flash them by adding an
``ESPTOOL_BINDIR`` parameter, pointing to the directory where these binaries
were downloaded:
+
+.. code-block:: console
+
+ $ make flash ESPTOOL_PORT=<port> ESPTOOL_BINDIR=<dir>
+
+.. note:: It is recommended that if this is the first time you are using the
board with NuttX that you perform a complete SPI FLASH erase.
+
+ .. code-block:: console
+
+ $ esptool.py erase_flash
+
+Peripheral Support
+==================
+
+The following list indicates the state of peripherals' support in NuttX:
+
+========== ======= =====
+Peripheral Support NOTES
+========== ======= =====
+GPIO Yes
+UART Yes
+SPI Yes
+I2C No
+CAN/TWAI No
+DMA Yes
+Wifi No
+SPIFLASH Yes
+SPIRAM Yes
+Timers Yes
+Watchdog Yes
+RTC No
+RNG No
+AES No
+eFuse No
+ADC No
+Bluetooth No
+SDIO No
+SD/MMC No
+I2S No
+LCD No
+CAMERA No
+LED_PWM No
+RMT No
+MCPWM No
+Pulse_CNT No
+SHA No
+RSA No
+USB SERIAL Yes
+USB OTG No
+========== ======= =====
+
+Memory Map
+==========
+
+Address Mapping
+---------------
+
+================== ========== ========== =============== ===============
+BUS TYPE START LAST DESCRIPTION NOTES
+================== ========== ========== =============== ===============
+To be added
+================== ========== ========== =============== ===============
+
+Embedded Memory
+---------------
+
+=========== ========== ========== =============== ===============
+BUS TYPE START LAST DESCRIPTION NOTES
+=========== ========== ========== =============== ===============
+To be added
+=========== ========== ========== =============== ===============
+
+Boundary Address (Embedded)
+---------------------------
+
+====================== ========== ========== =============== ===============
+BUS TYPE START LAST DESCRIPTION NOTES
+====================== ========== ========== =============== ===============
+To be added
+====================== ========== ========== =============== ===============
+
+External Memory
+---------------
+
+=========== ========== ========== =============== ===============
+BUS TYPE START LAST DESCRIPTION NOTES
+=========== ========== ========== =============== ===============
+To be added
+=========== ========== ========== =============== ===============
+
+Boundary Address (External)
+---------------------------
+
+To be added
+
+Linker Segments
+---------------
+
++---------------------+------------+------------+------+------------------------------+
+| DESCRIPTION | START | END | ATTR | LINKER SEGMENT NAME
|
++=====================+============+============+======+==============================+
+| To be added | | | |
|
++---------------------+------------+------------+------+------------------------------+
+
+Supported Boards
+================
+
+.. toctree::
+ :glob:
+ :maxdepth: 1
+
+ boards/*/*
diff --git a/content/docs/latest/components/index.html
b/content/docs/latest/components/index.html
index 53b722b..19b2e6d 100644
--- a/content/docs/latest/components/index.html
+++ b/content/docs/latest/components/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="Power Management" href="power.html" />
- <link rel="prev" title="ESP-WROVER-KIT"
href="../platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html" />
+ <link rel="prev" title="ESP32-S3-EYE"
href="../platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html" />
</head>
<body class="wy-body-for-nav">
@@ -274,7 +274,7 @@
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer
navigation">
<a href="power.html" class="btn btn-neutral float-right" title="Power
Management" accesskey="n" rel="next">Next <span class="fa
fa-arrow-circle-right" aria-hidden="true"></span></a>
- <a href="../platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html"
class="btn btn-neutral float-left" title="ESP-WROVER-KIT" accesskey="p"
rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span>
Previous</a>
+ <a href="../platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html"
class="btn btn-neutral float-left" title="ESP32-S3-EYE" 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/index.html b/content/docs/latest/index.html
index fc8ae89..baa08aa 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -218,7 +218,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: 17 June 22 at 00:12</p>
+<p>Last Updated: 18 June 22 at 00:13</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 a10b684..5e9ca5b 100644
Binary files a/content/docs/latest/objects.inv and
b/content/docs/latest/objects.inv differ
diff --git a/content/docs/latest/platforms/index.html
b/content/docs/latest/platforms/index.html
index 1240ca4..0840514 100644
--- a/content/docs/latest/platforms/index.html
+++ b/content/docs/latest/platforms/index.html
@@ -259,6 +259,11 @@ series and boards supported in NuttX:</p>
<li class="toctree-l3"><a class="reference internal"
href="xtensa/esp32/boards/esp32-wrover-kit/index.html">ESP-WROVER-KIT</a></li>
</ul>
</li>
+<li class="toctree-l2"><a class="reference internal"
href="xtensa/esp32s3/index.html">Espressif ESP32-S3</a><ul>
+<li class="toctree-l3"><a class="reference internal"
href="xtensa/esp32s3/boards/esp32s3-devkit/index.html">ESP32S3-DevKit</a></li>
+<li class="toctree-l3"><a class="reference internal"
href="xtensa/esp32s3/boards/esp32s3-eye/index.html">ESP32-S3-EYE</a></li>
+</ul>
+</li>
</ul>
</li>
</ul>
diff --git
a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html
b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html
index 48909cd..03b64cb 100644
--- a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html
@@ -156,6 +156,7 @@
</li>
</ul>
</li>
+<li class="toctree-l3"><a class="reference internal"
href="../../../esp32s3/index.html">Espressif ESP32-S3</a></li>
</ul>
</li>
</ul>
diff --git
a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
index 2eb74e7..54bde3e 100644
---
a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
+++
b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/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="OS Components"
href="../../../../../components/index.html" />
+ <link rel="next" title="Espressif ESP32-S3"
href="../../../esp32s3/index.html" />
<link rel="prev" title="ESP32 DevKitC" href="../esp32-devkitc/index.html"
/>
</head>
@@ -156,6 +156,7 @@
</li>
</ul>
</li>
+<li class="toctree-l3"><a class="reference internal"
href="../../../esp32s3/index.html">Espressif ESP32-S3</a></li>
</ul>
</li>
</ul>
@@ -431,7 +432,7 @@ https://github.com/lvgl/lvgl
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer
navigation">
- <a href="../../../../../components/index.html" class="btn btn-neutral
float-right" title="OS Components" accesskey="n" rel="next">Next <span
class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../../../esp32s3/index.html" class="btn btn-neutral
float-right" title="Espressif ESP32-S3" accesskey="n" rel="next">Next <span
class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
<a href="../esp32-devkitc/index.html" class="btn btn-neutral
float-left" title="ESP32 DevKitC" 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/xtensa/esp32/index.html
b/content/docs/latest/platforms/xtensa/esp32/index.html
index dd31a33..47ad27a 100644
--- a/content/docs/latest/platforms/xtensa/esp32/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/index.html
@@ -170,6 +170,7 @@
</li>
</ul>
</li>
+<li class="toctree-l3"><a class="reference internal"
href="../esp32s3/index.html">Espressif ESP32-S3</a></li>
</ul>
</li>
</ul>
diff --git
a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.html
similarity index 54%
copy from
content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
copy to
content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.html
index 2eb74e7..ded69f0 100644
---
a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
+++
b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.html
@@ -26,7 +26,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>ESP-WROVER-KIT — NuttX latest documentation</title>
+ <title>ESP32S3-DevKit — 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="OS Components"
href="../../../../../components/index.html" />
- <link rel="prev" title="ESP32 DevKitC" href="../esp32-devkitc/index.html"
/>
+ <link rel="next" title="ESP32-S3-EYE" href="../esp32s3-eye/index.html" />
+ <link rel="prev" title="Espressif ESP32-S3" href="../../index.html" />
</head>
<body class="wy-body-for-nav">
@@ -136,22 +136,15 @@
<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="../../../../sim/index.html">Simulators</a></li>
<li class="toctree-l2 current"><a class="reference internal"
href="../../../index.html">Xtensa</a><ul class="current">
-<li class="toctree-l3 current"><a class="reference internal"
href="../../index.html">Espressif ESP32</a><ul class="current">
+<li class="toctree-l3"><a class="reference internal"
href="../../../esp32/index.html">Espressif ESP32</a></li>
+<li class="toctree-l3 current"><a class="reference internal"
href="../../index.html">Espressif ESP32-S3</a><ul class="current">
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#toolchain">Toolchain</a></li>
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#flashing">Flashing</a></li>
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#peripheral-support">Peripheral Support</a></li>
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#memory-map">Memory Map</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#bit-timers">64-bit Timers</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#watchdog-timers">Watchdog Timers</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#smp">SMP</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#wi-fi">Wi-Fi</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#wi-fi-softap">Wi-Fi SoftAP</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#bluetooth">Bluetooth</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#using-qemu">Using QEMU</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#things-to-do">Things to Do</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="../esp32-devkitc/index.html">ESP32 DevKitC</a></li>
-<li class="toctree-l5 current"><a class="current reference internal"
href="#">ESP-WROVER-KIT</a></li>
+<li class="toctree-l5 current"><a class="current reference internal"
href="#">ESP32S3-DevKit</a></li>
+<li class="toctree-l5"><a class="reference internal"
href="../esp32s3-eye/index.html">ESP32-S3-EYE</a></li>
</ul>
</li>
</ul>
@@ -218,15 +211,15 @@
<li><a href="../../../index.html">Xtensa</a> »</li>
- <li><a href="../../index.html">Espressif ESP32</a> »</li>
+ <li><a href="../../index.html">Espressif ESP32-S3</a> »</li>
- <li>ESP-WROVER-KIT</li>
+ <li>ESP32S3-DevKit</li>
<li class="wy-breadcrumbs-aside">
- <a
href="../../../../../_sources/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.rst.txt"
rel="nofollow"> View page source</a>
+ <a
href="../../../../../_sources/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.rst.txt"
rel="nofollow"> View page source</a>
</li>
@@ -239,23 +232,16 @@
<div role="main" class="document" itemscope="itemscope"
itemtype="http://schema.org/Article";>
<div itemprop="articleBody">
- <div class="section" id="esp-wrover-kit">
-<h1>ESP-WROVER-KIT<a class="headerlink" href="#esp-wrover-kit"
title="Permalink to this headline">¶</a></h1>
-<p>The <a class="reference external"
href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-wrover-kit.html";>ESP-WROVER-KIT</a>
is a development board for the ESP32 SoC from Espressif, based on a
ESP32-WROVER-B module.</p>
+ <div class="section" id="esp32s3-devkit">
+<h1>ESP32S3-DevKit<a class="headerlink" href="#esp32s3-devkit"
title="Permalink to this headline">¶</a></h1>
+<p>The <a class="reference external"
href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html";>ESP32S3
DevKit</a> is a development board for the ESP32-S3 SoC from Espressif, based
on a ESP32-S3-WROOM-1 module.</p>
<table class="docutils align-center">
<colgroup>
-<col style="width: 50%" />
-<col style="width: 50%" />
+<col style="width: 100%" />
</colgroup>
<tbody>
-<tr class="row-odd"><td><div class="figure align-center" id="id2">
-<img alt="../../../../../_images/esp-wrover-kit-v4.1-layout-back.png"
src="../../../../../_images/esp-wrover-kit-v4.1-layout-back.png" />
-<p class="caption"><span class="caption-text">ESP-WROVER-KIT board layout -
front</span><a class="headerlink" href="#id2" title="Permalink to this
image">¶</a></p>
-</div>
-</td>
-<td><div class="figure align-center" id="id3">
-<img alt="../../../../../_images/esp-wrover-kit-v4.1-layout-front.png"
src="../../../../../_images/esp-wrover-kit-v4.1-layout-front.png" />
-<p class="caption"><span class="caption-text">ESP-WROVER-KIT board layout -
back</span><a class="headerlink" href="#id3" title="Permalink to this
image">¶</a></p>
+<tr class="row-odd"><td><div class="figure align-center">
+<img alt="../../../../../_images/esp32-s3-devkitc-1.png"
src="../../../../../_images/esp32-s3-devkitc-1.png" />
</div>
</td>
</tr>
@@ -265,162 +251,43 @@
<h2>Features<a class="headerlink" href="#features" title="Permalink to this
headline">¶</a></h2>
<blockquote>
<div><ul class="simple">
-<li><p>ESP32-WROVER-B module</p></li>
-<li><p>LCD screen</p></li>
-<li><p>MicroSD card slot</p></li>
+<li><p>ESP32-S3-WROOM-1 Module</p></li>
+<li><p>USB-to-UART bridge via micro USB port</p></li>
+<li><p>Power LED</p></li>
+<li><p>EN and BOOT buttons (BOOT accessible to user)</p></li>
+<li><p>SPI FLASH (size varies according to model</p></li>
</ul>
</div></blockquote>
-<p>Its another distinguishing feature is the embedded FTDI FT2232HL chip,
-an advanced multi-interface USB bridge. This chip enables to use JTAG
-for direct debugging of ESP32 through the USB interface without a separate
-JTAG debugger. ESP-WROVER-KIT makes development convenient, easy, and
-cost-effective.</p>
-<p>Most of the ESP32 I/O pins are broken out to the board’s pin headers for
easy access.</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>UART0 is, by default, the serial console. It connects to the on-board
-FT2232HL converter and is available on the USB connector USB CON8 (J5).</p>
-<p>It will show up as /dev/ttyUSB[n] where [n] will probably be 1, since
-the first interface ([n] == 0) is dedicated to the USB-to-JTAG interface.</p>
+<p>UART0 is, by default, the serial console. It connects to the on-board
+CP2102 converter and is available on the USB connector USB CON8 (J1).</p>
+<p>It will show up as /dev/ttyUSB[n] where [n] will probably be 0.</p>
</div>
<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 EN. The EN 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 IO0. On reset it is used as a strapping
+<p>There are two buttons labeled Boot and EN. The EN 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 IO0. 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
+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 are several on-board LEDs for that indicate the presence of power
-and USB activity.</p>
-<p>There is an RGB LED available for software.</p>
+and USB activity. None of these are available for use by software.</p>
</div>
</div>
-<div class="section" id="pin-mapping">
-<h2>Pin Mapping<a class="headerlink" href="#pin-mapping" title="Permalink to
this headline">¶</a></h2>
-<table class="docutils align-default">
-<colgroup>
-<col style="width: 13%" />
-<col style="width: 63%" />
-<col style="width: 25%" />
-</colgroup>
-<thead>
-<tr class="row-odd"><th class="head"><p>Pin</p></th>
-<th class="head"><p>Signal</p></th>
-<th class="head"><p>Notes</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="row-even"><td><p>0</p></td>
-<td><p>RGB LED Red / BOOT Button</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>2</p></td>
-<td><p>RGB LED Green</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>4</p></td>
-<td><p>RGB LED Blue</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>5</p></td>
-<td><p>LCD Backlight</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>18</p></td>
-<td><p>LCD Reset</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>19</p></td>
-<td><p>LCD Clock</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>21</p></td>
-<td><p>LCD D/C</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>22</p></td>
-<td><p>LCD CS</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>23</p></td>
-<td><p>LCD MOSI</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>25</p></td>
-<td><p>LCD MISO</p></td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</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 NuttShell configuration (console enabled in UART0, exposed via
-USB connection by means of FT2232HL converter, at 115200 bps).</p>
-</div>
-<div class="section" id="wapi">
-<h3>wapi<a class="headerlink" href="#wapi" title="Permalink to this
headline">¶</a></h3>
-<p>Enables Wi-Fi support.</p>
-</div>
-<div class="section" id="gpio">
-<h3>gpio<a class="headerlink" href="#gpio" title="Permalink to this
headline">¶</a></h3>
-<p>This is a test for the GPIO driver. It includes the 3 LEDs and one,
arbitrary, GPIO.
-For this example, GPIO22 was used.
-At the nsh, we can turn LEDs on and off with the following:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> gpio -o 1 /dev/gpio0
-nsh> gpio -o 0 /dev/gpio0
-</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/gpio2
-</pre></div>
-</div>
-<p>The pin is configured to as a rising edge interrupt, so after issuing the
-above command, connect it to 3.3V.</p>
-</div>
-<div class="section" id="spiflash">
-<h3>spiflash<a class="headerlink" href="#spiflash" title="Permalink to this
headline">¶</a></h3>
-<p>This config tests the external SPI that comes with an ESP32 module connected
-through SPI1.</p>
-<p>By default a SmartFS file system is selected.
-Once booted you can use the following commands to mount the file system:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>mksmartfs /dev/smart0
-mount -t smartfs /dev/smart0 /mnt
-</pre></div>
-</div>
-<p>Note that <cite>mksmartfs</cite> is only needed the first time.</p>
-</div>
-<div class="section" id="nx">
-<h3>nx<a class="headerlink" href="#nx" title="Permalink to this
headline">¶</a></h3>
-<p>This config adds a set of tests using the graphic examples at
<cite>apps/example/nx</cite>.</p>
-<p>This configuration illustrates the use of the LCD with the lower performance
-SPI interface.</p>
-</div>
-<div class="section" id="lvgl">
-<h3>lvgl<a class="headerlink" href="#lvgl" title="Permalink to this
headline">¶</a></h3>
-<p>This is a demonstration of the LVGL graphics library running on the NuttX
LCD
-driver. You can find LVGL here:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>https://www.lvgl.io/
-https://github.com/lvgl/lvgl
-</pre></div>
-</div>
-<p>This configuration uses the LVGL demonstration at
<cite>apps/examples/lvgldemo</cite>.</p>
-</div>
-</div>
-<div class="section" id="external-devices">
-<h2>External devices<a class="headerlink" href="#external-devices"
title="Permalink to this headline">¶</a></h2>
-<div class="section" id="bmp180">
-<h3>BMP180<a class="headerlink" href="#bmp180" title="Permalink to this
headline">¶</a></h3>
-<p>When using BMP180 (enabling <code class="docutils literal
notranslate"><span class="pre">CONFIG_SENSORS_BMP180</span></code>), it’s
expected this device is wired to I2C0 bus.</p>
+USB connection by means of CP2102 converter, at 115200 bps).</p>
</div>
</div>
</div>
@@ -431,8 +298,8 @@ https://github.com/lvgl/lvgl
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer
navigation">
- <a href="../../../../../components/index.html" class="btn btn-neutral
float-right" title="OS Components" accesskey="n" rel="next">Next <span
class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
- <a href="../esp32-devkitc/index.html" class="btn btn-neutral
float-left" title="ESP32 DevKitC" accesskey="p" rel="prev"><span class="fa
fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="../esp32s3-eye/index.html" class="btn btn-neutral
float-right" title="ESP32-S3-EYE" 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="Espressif ESP32-S3" 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/xtensa/esp32/boards/esp32-wrover-kit/index.html
b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html
similarity index 57%
copy from
content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
copy to
content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html
index 2eb74e7..046abba 100644
---
a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html
@@ -26,7 +26,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>ESP-WROVER-KIT — NuttX latest documentation</title>
+ <title>ESP32-S3-EYE — NuttX latest documentation</title>
@@ -62,7 +62,7 @@
<link rel="index" title="Index" href="../../../../../genindex.html" />
<link rel="search" title="Search" href="../../../../../search.html" />
<link rel="next" title="OS Components"
href="../../../../../components/index.html" />
- <link rel="prev" title="ESP32 DevKitC" href="../esp32-devkitc/index.html"
/>
+ <link rel="prev" title="ESP32S3-DevKit"
href="../esp32s3-devkit/index.html" />
</head>
<body class="wy-body-for-nav">
@@ -136,22 +136,15 @@
<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="../../../../sim/index.html">Simulators</a></li>
<li class="toctree-l2 current"><a class="reference internal"
href="../../../index.html">Xtensa</a><ul class="current">
-<li class="toctree-l3 current"><a class="reference internal"
href="../../index.html">Espressif ESP32</a><ul class="current">
+<li class="toctree-l3"><a class="reference internal"
href="../../../esp32/index.html">Espressif ESP32</a></li>
+<li class="toctree-l3 current"><a class="reference internal"
href="../../index.html">Espressif ESP32-S3</a><ul class="current">
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#toolchain">Toolchain</a></li>
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#flashing">Flashing</a></li>
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#peripheral-support">Peripheral Support</a></li>
<li class="toctree-l4"><a class="reference internal"
href="../../index.html#memory-map">Memory Map</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#bit-timers">64-bit Timers</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#watchdog-timers">Watchdog Timers</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#smp">SMP</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#wi-fi">Wi-Fi</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#wi-fi-softap">Wi-Fi SoftAP</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#bluetooth">Bluetooth</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#using-qemu">Using QEMU</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="../../index.html#things-to-do">Things to Do</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="../esp32-devkitc/index.html">ESP32 DevKitC</a></li>
-<li class="toctree-l5 current"><a class="current reference internal"
href="#">ESP-WROVER-KIT</a></li>
+<li class="toctree-l5"><a class="reference internal"
href="../esp32s3-devkit/index.html">ESP32S3-DevKit</a></li>
+<li class="toctree-l5 current"><a class="current reference internal"
href="#">ESP32-S3-EYE</a></li>
</ul>
</li>
</ul>
@@ -218,15 +211,15 @@
<li><a href="../../../index.html">Xtensa</a> »</li>
- <li><a href="../../index.html">Espressif ESP32</a> »</li>
+ <li><a href="../../index.html">Espressif ESP32-S3</a> »</li>
- <li>ESP-WROVER-KIT</li>
+ <li>ESP32-S3-EYE</li>
<li class="wy-breadcrumbs-aside">
- <a
href="../../../../../_sources/platforms/xtensa/esp32/boards/esp32-wrover-kit/index.rst.txt"
rel="nofollow"> View page source</a>
+ <a
href="../../../../../_sources/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.rst.txt"
rel="nofollow"> View page source</a>
</li>
@@ -239,23 +232,16 @@
<div role="main" class="document" itemscope="itemscope"
itemtype="http://schema.org/Article";>
<div itemprop="articleBody">
- <div class="section" id="esp-wrover-kit">
-<h1>ESP-WROVER-KIT<a class="headerlink" href="#esp-wrover-kit"
title="Permalink to this headline">¶</a></h1>
-<p>The <a class="reference external"
href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-wrover-kit.html";>ESP-WROVER-KIT</a>
is a development board for the ESP32 SoC from Espressif, based on a
ESP32-WROVER-B module.</p>
+ <div class="section" id="esp32-s3-eye">
+<h1>ESP32-S3-EYE<a class="headerlink" href="#esp32-s3-eye" title="Permalink to
this headline">¶</a></h1>
+<p>The <a class="reference external"
href="https://github.com/espressif/esp-who/blob/master/docs/en/get-started/ESP32-S3-EYE_Getting_Started_Guide.md";>ESP32-S3-EYE</a>
is a small-sized AI development board from Espressif featuring the ESP32-S3
CPU with a 2-Megapixel camera, an LCD display, a microphone, an 8 MB Octal
PSRAM and an 8 MB flash.</p>
<table class="docutils align-center">
<colgroup>
-<col style="width: 50%" />
-<col style="width: 50%" />
+<col style="width: 100%" />
</colgroup>
<tbody>
-<tr class="row-odd"><td><div class="figure align-center" id="id2">
-<img alt="../../../../../_images/esp-wrover-kit-v4.1-layout-back.png"
src="../../../../../_images/esp-wrover-kit-v4.1-layout-back.png" />
-<p class="caption"><span class="caption-text">ESP-WROVER-KIT board layout -
front</span><a class="headerlink" href="#id2" title="Permalink to this
image">¶</a></p>
-</div>
-</td>
-<td><div class="figure align-center" id="id3">
-<img alt="../../../../../_images/esp-wrover-kit-v4.1-layout-front.png"
src="../../../../../_images/esp-wrover-kit-v4.1-layout-front.png" />
-<p class="caption"><span class="caption-text">ESP-WROVER-KIT board layout -
back</span><a class="headerlink" href="#id3" title="Permalink to this
image">¶</a></p>
+<tr class="row-odd"><td><div class="figure align-center">
+<img alt="../../../../../_images/esp32s3_eye.png"
src="../../../../../_images/esp32s3_eye.png" />
</div>
</td>
</tr>
@@ -265,50 +251,82 @@
<h2>Features<a class="headerlink" href="#features" title="Permalink to this
headline">¶</a></h2>
<blockquote>
<div><ul class="simple">
-<li><p>ESP32-WROVER-B module</p></li>
-<li><p>LCD screen</p></li>
-<li><p>MicroSD card slot</p></li>
+<li><p>ESP32-S3 WROOM-1 Module</p></li>
+<li><p>USB micro USB port (it uses internal USB JTAG SERIAL device for
flashing)</p></li>
+<li><p>Power LED</p></li>
+<li><p>LCD Display</p></li>
+<li><p>2-MP Camera</p></li>
+<li><p>MEMS Microphone</p></li>
+<li><p>8MB Octal PSRAM</p></li>
+<li><p>8MB SPI Flash</p></li>
+<li><p>RST and BOOT buttons (BOOT accessible to user)</p></li>
</ul>
</div></blockquote>
-<p>Its another distinguishing feature is the embedded FTDI FT2232HL chip,
-an advanced multi-interface USB bridge. This chip enables to use JTAG
-for direct debugging of ESP32 through the USB interface without a separate
-JTAG debugger. ESP-WROVER-KIT makes development convenient, easy, and
-cost-effective.</p>
-<p>Most of the ESP32 I/O pins are broken out to the board’s pin headers for
easy access.</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">
+<h3>nsh<a class="headerlink" href="#nsh" title="Permalink to this
headline">¶</a></h3>
+<p>Basic NuttShell configuration (console enabled in USB JTAG SERIAL Device,
exposed via
+USB connection at 9600 bps).</p>
+<p>You can configure this board profile this way:</p>
+<blockquote>
+<div><p>$ cd nuttxspace/nuttx
+$ ./tools/configure.sh esp32s3-eye:nsh</p>
+</div></blockquote>
+</div>
+</div>
+<div class="section" id="flashing">
+<h2>Flashing<a class="headerlink" href="#flashing" title="Permalink to this
headline">¶</a></h2>
+<p>Because ESP32-S3 doesn’t use an external USB/Serial chip like others ESP32
+boards you should put it in programming mode this way:</p>
+<blockquote>
+<div><ol class="arabic simple">
+<li><p>Press and hold BOOT and RESET (RST) buttons at same time;</p></li>
+<li><p>Release the RESET button and keep BOOT button pressed;</p></li>
+<li><p>After one or more seconds release the BOOT button;</p></li>
+<li><p>Run the flashing command: make flash ESPTOOL_PORT=/dev/ttyACM0</p></li>
+</ol>
+</div></blockquote>
</div>
<div class="section" id="serial-console">
<h2>Serial Console<a class="headerlink" href="#serial-console"
title="Permalink to this headline">¶</a></h2>
-<p>UART0 is, by default, the serial console. It connects to the on-board
-FT2232HL converter and is available on the USB connector USB CON8 (J5).</p>
-<p>It will show up as /dev/ttyUSB[n] where [n] will probably be 1, since
-the first interface ([n] == 0) is dedicated to the USB-to-JTAG interface.</p>
+<p>The internal USB JTAG SERIAL Device, by default, is used as serial console.
+It is normally detected by Linux host as a USB CDC/ACM serial device.</p>
+<p>It will show up as /dev/ttyACM[n] where [n] will probably be 0.</p>
+<p>You can use minicom with /dev/ttyACM0 port at 9600 8n1 or picocom this
way:</p>
+<blockquote>
+<div><p>$ picocom -b9600 /dev/ttyACM0</p>
+</div></blockquote>
</div>
<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 EN. The EN 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 IO0. On reset it is used as a strapping
+<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 IO0. 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
+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 are several on-board LEDs for that indicate the presence of power
-and USB activity.</p>
-<p>There is an RGB LED available for software.</p>
+and USB activity. None of these are available for use by software.</p>
</div>
</div>
<div class="section" id="pin-mapping">
<h2>Pin Mapping<a class="headerlink" href="#pin-mapping" title="Permalink to
this headline">¶</a></h2>
+<div class="admonition-todo admonition" id="id2">
+<p class="admonition-title">Todo</p>
+<p>To be updated</p>
+</div>
<table class="docutils align-default">
<colgroup>
-<col style="width: 13%" />
-<col style="width: 63%" />
-<col style="width: 25%" />
+<col style="width: 20%" />
+<col style="width: 40%" />
+<col style="width: 40%" />
</colgroup>
<thead>
<tr class="row-odd"><th class="head"><p>Pin</p></th>
@@ -317,112 +335,13 @@ and USB activity.</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><p>0</p></td>
-<td><p>RGB LED Red / BOOT Button</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>2</p></td>
-<td><p>RGB LED Green</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>4</p></td>
-<td><p>RGB LED Blue</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>5</p></td>
-<td><p>LCD Backlight</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>18</p></td>
-<td><p>LCD Reset</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>19</p></td>
-<td><p>LCD Clock</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>21</p></td>
-<td><p>LCD D/C</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>22</p></td>
-<td><p>LCD CS</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>23</p></td>
-<td><p>LCD MOSI</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>25</p></td>
-<td><p>LCD MISO</p></td>
-<td></td>
+<tr class="row-even"><td><p>?</p></td>
+<td><p>?</p></td>
+<td><p>?</p></td>
</tr>
</tbody>
</table>
</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 NuttShell configuration (console enabled in UART0, exposed via
-USB connection by means of FT2232HL converter, at 115200 bps).</p>
-</div>
-<div class="section" id="wapi">
-<h3>wapi<a class="headerlink" href="#wapi" title="Permalink to this
headline">¶</a></h3>
-<p>Enables Wi-Fi support.</p>
-</div>
-<div class="section" id="gpio">
-<h3>gpio<a class="headerlink" href="#gpio" title="Permalink to this
headline">¶</a></h3>
-<p>This is a test for the GPIO driver. It includes the 3 LEDs and one,
arbitrary, GPIO.
-For this example, GPIO22 was used.
-At the nsh, we can turn LEDs on and off with the following:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> gpio -o 1 /dev/gpio0
-nsh> gpio -o 0 /dev/gpio0
-</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/gpio2
-</pre></div>
-</div>
-<p>The pin is configured to as a rising edge interrupt, so after issuing the
-above command, connect it to 3.3V.</p>
-</div>
-<div class="section" id="spiflash">
-<h3>spiflash<a class="headerlink" href="#spiflash" title="Permalink to this
headline">¶</a></h3>
-<p>This config tests the external SPI that comes with an ESP32 module connected
-through SPI1.</p>
-<p>By default a SmartFS file system is selected.
-Once booted you can use the following commands to mount the file system:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>mksmartfs /dev/smart0
-mount -t smartfs /dev/smart0 /mnt
-</pre></div>
-</div>
-<p>Note that <cite>mksmartfs</cite> is only needed the first time.</p>
-</div>
-<div class="section" id="nx">
-<h3>nx<a class="headerlink" href="#nx" title="Permalink to this
headline">¶</a></h3>
-<p>This config adds a set of tests using the graphic examples at
<cite>apps/example/nx</cite>.</p>
-<p>This configuration illustrates the use of the LCD with the lower performance
-SPI interface.</p>
-</div>
-<div class="section" id="lvgl">
-<h3>lvgl<a class="headerlink" href="#lvgl" title="Permalink to this
headline">¶</a></h3>
-<p>This is a demonstration of the LVGL graphics library running on the NuttX
LCD
-driver. You can find LVGL here:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>https://www.lvgl.io/
-https://github.com/lvgl/lvgl
-</pre></div>
-</div>
-<p>This configuration uses the LVGL demonstration at
<cite>apps/examples/lvgldemo</cite>.</p>
-</div>
-</div>
-<div class="section" id="external-devices">
-<h2>External devices<a class="headerlink" href="#external-devices"
title="Permalink to this headline">¶</a></h2>
-<div class="section" id="bmp180">
-<h3>BMP180<a class="headerlink" href="#bmp180" title="Permalink to this
headline">¶</a></h3>
-<p>When using BMP180 (enabling <code class="docutils literal
notranslate"><span class="pre">CONFIG_SENSORS_BMP180</span></code>), it’s
expected this device is wired to I2C0 bus.</p>
-</div>
-</div>
</div>
@@ -432,7 +351,7 @@ https://github.com/lvgl/lvgl
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer
navigation">
<a href="../../../../../components/index.html" class="btn btn-neutral
float-right" title="OS Components" accesskey="n" rel="next">Next <span
class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
- <a href="../esp32-devkitc/index.html" class="btn btn-neutral
float-left" title="ESP32 DevKitC" accesskey="p" rel="prev"><span class="fa
fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="../esp32s3-devkit/index.html" class="btn btn-neutral
float-left" title="ESP32S3-DevKit" 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/xtensa/esp32/index.html
b/content/docs/latest/platforms/xtensa/esp32s3/index.html
similarity index 51%
copy from content/docs/latest/platforms/xtensa/esp32/index.html
copy to content/docs/latest/platforms/xtensa/esp32s3/index.html
index dd31a33..8e5b780 100644
--- a/content/docs/latest/platforms/xtensa/esp32/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s3/index.html
@@ -26,7 +26,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>Espressif ESP32 — NuttX latest documentation</title>
+ <title>Espressif ESP32-S3 — 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="ESP32 DevKitC"
href="boards/esp32-devkitc/index.html" />
- <link rel="prev" title="Xtensa" href="../index.html" />
+ <link rel="next" title="ESP32S3-DevKit"
href="boards/esp32s3-devkit/index.html" />
+ <link rel="prev" title="ESP-WROVER-KIT"
href="../esp32/boards/esp32-wrover-kit/index.html" />
</head>
<body class="wy-body-for-nav">
@@ -136,7 +136,8 @@
<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="../../sim/index.html">Simulators</a></li>
<li class="toctree-l2 current"><a class="reference internal"
href="../index.html">Xtensa</a><ul class="current">
-<li class="toctree-l3 current"><a class="current reference internal"
href="#">Espressif ESP32</a><ul>
+<li class="toctree-l3"><a class="reference internal"
href="../esp32/index.html">Espressif ESP32</a></li>
+<li class="toctree-l3 current"><a class="current reference internal"
href="#">Espressif ESP32-S3</a><ul>
<li class="toctree-l4"><a class="reference internal"
href="#toolchain">Toolchain</a><ul>
<li class="toctree-l5"><a class="reference internal"
href="#building-from-source">Building from source</a></li>
</ul>
@@ -155,17 +156,9 @@
<li class="toctree-l5"><a class="reference internal"
href="#linker-segments">Linker Segments</a></li>
</ul>
</li>
-<li class="toctree-l4"><a class="reference internal" href="#bit-timers">64-bit
Timers</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="#watchdog-timers">Watchdog Timers</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#smp">SMP</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="#wi-fi">Wi-Fi</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="#wi-fi-softap">Wi-Fi SoftAP</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="#bluetooth">Bluetooth</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#using-qemu">Using
QEMU</a></li>
-<li class="toctree-l4"><a class="reference internal"
href="#things-to-do">Things to Do</a></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/esp32-devkitc/index.html">ESP32 DevKitC</a></li>
-<li class="toctree-l5"><a class="reference internal"
href="boards/esp32-wrover-kit/index.html">ESP-WROVER-KIT</a></li>
+<li class="toctree-l5"><a class="reference internal"
href="boards/esp32s3-devkit/index.html">ESP32S3-DevKit</a></li>
+<li class="toctree-l5"><a class="reference internal"
href="boards/esp32s3-eye/index.html">ESP32-S3-EYE</a></li>
</ul>
</li>
</ul>
@@ -232,13 +225,13 @@
<li><a href="../index.html">Xtensa</a> »</li>
- <li>Espressif ESP32</li>
+ <li>Espressif ESP32-S3</li>
<li class="wy-breadcrumbs-aside">
- <a href="../../../_sources/platforms/xtensa/esp32/index.rst.txt"
rel="nofollow"> View page source</a>
+ <a href="../../../_sources/platforms/xtensa/esp32s3/index.rst.txt"
rel="nofollow"> View page source</a>
</li>
@@ -251,10 +244,10 @@
<div role="main" class="document" itemscope="itemscope"
itemtype="http://schema.org/Article";>
<div itemprop="articleBody">
- <div class="section" id="espressif-esp32">
-<h1>Espressif ESP32<a class="headerlink" href="#espressif-esp32"
title="Permalink to this headline">¶</a></h1>
-<p>The ESP32 is a series of single and dual-core SoCs from Espressif
-based on Harvard architecture Xtensa LX6 CPUs and with on-chip support
+ <div class="section" id="espressif-esp32-s3">
+<h1>Espressif ESP32-S3<a class="headerlink" href="#espressif-esp32-s3"
title="Permalink to this headline">¶</a></h1>
+<p>The ESP32-S3 is a series of single and dual-core SoCs from Espressif
+based on Harvard architecture Xtensa LX7 CPUs and with on-chip support
for Bluetooth and Wi-Fi.</p>
<p>All embedded memory, external memory and peripherals are located on the
data bus and/or the instruction bus of these CPUs. With some minor
@@ -266,9 +259,9 @@ the system can access embedded memory via DMA.</p>
two CPUs are interchangeable.</p>
<div class="section" id="toolchain">
<h2>Toolchain<a class="headerlink" href="#toolchain" title="Permalink to this
headline">¶</a></h2>
-<p>You can use the prebuilt <a class="reference external"
href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-tools.html#xtensa-esp32-elf";>toolchain</a>
-for Xtensa architecture and <a class="reference external"
href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-tools.html#openocd-esp32";>OpenOCD</a>
-for ESP32 by Espressif.</p>
+<p>You can use the prebuilt <a class="reference external"
href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/tools/idf-tools.html#xtensa-esp32s3-elf";>toolchain</a>
+for Xtensa architecture and <a class="reference external"
href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/tools/idf-tools.html#openocd-esp32";>OpenOCD</a>
+for ESP32-S3 by Espressif.</p>
<p>For flashing firmware, you will need to install <code class="docutils
literal notranslate"><span class="pre">esptool.py</span></code> by running:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ pip install esptool
</pre></div>
@@ -279,15 +272,14 @@ for ESP32 by Espressif.</p>
build the toolchain with crosstool-NG on Linux are as follows</p>
<div class="highlight-console notranslate"><div
class="highlight"><pre><span></span><span class="gp">$ </span>git clone
https://github.com/espressif/crosstool-NG.git
<span class="gp">$ </span><span class="nb">cd</span> crosstool-NG
-<span class="gp">$ </span>git checkout esp-2021r1
<span class="gp">$ </span>git submodule update --init
<span class="gp">$ </span>./bootstrap <span class="o">&&</span>
./configure --enable-local <span class="o">&&</span> make
-<span class="gp">$ </span>./ct-ng xtensa-esp32-elf
+<span class="gp">$ </span>./ct-ng xtensa-esp32s3-elf
<span class="gp">$ </span>./ct-ng build
-<span class="gp">$ </span>chmod -R u+w builds/xtensa-esp32-elf
+<span class="gp">$ </span>chmod -R u+w builds/xtensa-esp32s3-elf
<span class="gp">$ </span><span class="nb">export</span> <span
class="nv">PATH</span><span class="o">=</span><span
class="s2">"crosstool-NG/builds/xtensa-esp32-elf/bin:</span><span
class="nv">$PATH</span><span class="s2">"</span>
</pre></div>
@@ -298,8 +290,9 @@ build the toolchain with crosstool-NG on Linux are as
follows</p>
</div>
<div class="section" id="flashing">
<h2>Flashing<a class="headerlink" href="#flashing" title="Permalink to this
headline">¶</a></h2>
-<p>Firmware for ESP32 is flashed via the USB/UART interface using the <code
class="docutils literal notranslate"><span class="pre">esptool.py</span></code>
tool.
-It’s a two step process where the first converts the ELF file into a
ESP32-compatible binary
+<p>Firmware for ESP32-S3 is flashed via the USB/UART or internal USB DEVICE
JTAG interface using the
+<code class="docutils literal notranslate"><span
class="pre">esptool.py</span></code> tool.
+It’s a two step process where the first converts the ELF file into a ESP32-S3
compatible binary
and the second flashes it to the board. These steps are included into the
build system and you can
flash your NuttX firmware simply by running:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ make flash ESPTOOL_PORT=<port>
@@ -308,7 +301,7 @@ flash your NuttX firmware simply by running:</p>
<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.
You can change the baudrate by passing <code class="docutils literal
notranslate"><span class="pre">ESPTOOL_BAUD</span></code>.</p>
<div class="section" id="bootloader-and-partitions">
<h3>Bootloader and partitions<a class="headerlink"
href="#bootloader-and-partitions" title="Permalink to this headline">¶</a></h3>
-<p>ESP32 requires a bootloader to be flashed as well as a set of FLASH
partitions. This is only needed the first time
+<p>ESP32-S3 requires a bootloader to be flashed as well as a set of FLASH
partitions. This is only needed the first time
(or any time you which to modify either of these). An easy way is to use
prebuilt binaries for NuttX <a class="reference external"
href="https://github.com/espressif/esp-nuttx-bootloader";>from here</a>. In
there you will find instructions to rebuild these if necessary.
Once you downloaded both binaries, you can flash them by adding an <code
class="docutils literal notranslate"><span
class="pre">ESPTOOL_BINDIR</span></code> parameter, pointing to the directory
where these binaries were downloaded:</p>
<div class="highlight-console notranslate"><div
class="highlight"><pre><span></span><span class="gp">$ </span>make flash <span
class="nv">ESPTOOL_PORT</span><span class="o">=</span><port> <span
class="nv">ESPTOOL_BINDIR</span><span class="o">=</span><dir>
@@ -316,8 +309,7 @@ Once you downloaded both binaries, you can flash them by
adding an <code class="
</div>
<div class="admonition note">
<p class="admonition-title">Note</p>
-<p>It is recommended that if this is the first time you are using the board
with NuttX that you perform a complete
-SPI FLASH erase.</p>
+<p>It is recommended that if this is the first time you are using the board
with NuttX that you perform a complete SPI FLASH erase.</p>
<div class="highlight-console notranslate"><div
class="highlight"><pre><span></span><span class="gp">$ </span>esptool.py
erase_flash
</pre></div>
</div>
@@ -353,19 +345,19 @@ SPI FLASH erase.</p>
<td></td>
</tr>
<tr class="row-odd"><td><p>I2C</p></td>
-<td><p>Yes</p></td>
+<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-even"><td><p>DMA</p></td>
-<td><p>Yes</p></td>
+<tr class="row-even"><td><p>CAN/TWAI</p></td>
+<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-odd"><td><p>Wifi</p></td>
+<tr class="row-odd"><td><p>DMA</p></td>
<td><p>Yes</p></td>
<td></td>
</tr>
-<tr class="row-even"><td><p>Ethernet</p></td>
-<td><p>Yes</p></td>
+<tr class="row-even"><td><p>Wifi</p></td>
+<td><p>No</p></td>
<td></td>
</tr>
<tr class="row-odd"><td><p>SPIFLASH</p></td>
@@ -385,19 +377,19 @@ SPI FLASH erase.</p>
<td></td>
</tr>
<tr class="row-odd"><td><p>RTC</p></td>
-<td><p>Yes</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><p>No</p></td>
<td></td>
</tr>
<tr class="row-odd"><td><p>AES</p></td>
-<td><p>Yes</p></td>
+<td><p>No</p></td>
<td></td>
</tr>
<tr class="row-even"><td><p>eFuse</p></td>
-<td><p>Yes</p></td>
+<td><p>No</p></td>
<td></td>
</tr>
<tr class="row-odd"><td><p>ADC</p></td>
@@ -405,7 +397,7 @@ SPI FLASH erase.</p>
<td></td>
</tr>
<tr class="row-even"><td><p>Bluetooth</p></td>
-<td><p>Yes</p></td>
+<td><p>No</p></td>
<td></td>
</tr>
<tr class="row-odd"><td><p>SDIO</p></td>
@@ -420,6 +412,14 @@ SPI FLASH erase.</p>
<td><p>No</p></td>
<td></td>
</tr>
+<tr class="row-even"><td><p>LCD</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>CAMERA</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
<tr class="row-even"><td><p>LED_PWM</p></td>
<td><p>No</p></td>
<td></td>
@@ -444,6 +444,14 @@ SPI FLASH erase.</p>
<td><p>No</p></td>
<td></td>
</tr>
+<tr class="row-even"><td><p>USB SERIAL</p></td>
+<td><p>Yes</p></td>
+<td></td>
+</tr>
+<tr class="row-odd"><td><p>USB OTG</p></td>
+<td><p>No</p></td>
+<td></td>
+</tr>
</tbody>
</table>
</div>
@@ -468,62 +476,12 @@ SPI FLASH erase.</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><p>Data</p></td>
-<td><p>0x3F400000</p></td>
-<td><p>0x3F7FFFFF</p></td>
-<td><p>External Memory</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>Data</p></td>
-<td><p>0x3F800000
-0x3FC00000</p></td>
-<td><p>0x3FBFFFFF
-0x3FEFFFFF</p></td>
-<td><p>External Memory</p></td>
-<td><p>Reserved</p></td>
-</tr>
-<tr class="row-even"><td><p>Data</p></td>
-<td><p>0x3FF00000</p></td>
-<td><p>0x3FF7FFFF</p></td>
-<td><p>Peripheral</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>Data</p></td>
-<td><p>0x3FF80000</p></td>
-<td><p>0x3FFFFFFF</p></td>
-<td><p>Embedded Memory</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>Instruction</p></td>
-<td><p>0x40000000</p></td>
-<td><p>0x400C1FFF</p></td>
-<td><p>Embedded Memory</p></td>
+<tr class="row-even"><td><p>To be added</p></td>
<td></td>
-</tr>
-<tr class="row-odd"><td><p>Instruction</p></td>
-<td><p>0x400C2000</p></td>
-<td><p>0x40BFFFFF</p></td>
-<td><p>External Memory</p></td>
<td></td>
-</tr>
-<tr class="row-even"><td><p>.</p></td>
-<td><p>0x40C00000</p></td>
-<td><p>0x4FFFFFFF</p></td>
<td></td>
-<td><p>Reserved</p></td>
-</tr>
-<tr class="row-odd"><td><p>Data / Instruction</p></td>
-<td><p>0x50000000</p></td>
-<td><p>0x50001FFF</p></td>
-<td><p>Embedded Memory</p></td>
<td></td>
</tr>
-<tr class="row-even"><td><p>.</p></td>
-<td><p>0x50002000</p></td>
-<td><p>0xFFFFFFFF</p></td>
-<td></td>
-<td><p>Reserved</p></td>
-</tr>
</tbody>
</table>
</div>
@@ -546,41 +504,11 @@ SPI FLASH erase.</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><p>Data</p></td>
-<td><p>0x3ff80000</p></td>
-<td><p>0x3ff81fff</p></td>
-<td><p>RTC FAST Memory</p></td>
-<td><p>PRO_CPU Only</p></td>
-</tr>
-<tr class="row-odd"><td><p>.</p></td>
-<td><p>0x3ff82000</p></td>
-<td><p>0x3ff8ffff</p></td>
+<tr class="row-even"><td><p>To be added</p></td>
+<td></td>
<td></td>
-<td><p>Reserved</p></td>
-</tr>
-<tr class="row-even"><td><p>Data</p></td>
-<td><p>0x3ff90000</p></td>
-<td><p>0x3ff9ffff</p></td>
-<td><p>Internal ROM 1</p></td>
<td></td>
-</tr>
-<tr class="row-odd"><td><p>.</p></td>
-<td><p>0x3ffa0000</p></td>
-<td><p>0x3ffadfff</p></td>
<td></td>
-<td><p>Reserved</p></td>
-</tr>
-<tr class="row-even"><td><p>Data</p></td>
-<td><p>0x3ffae000</p></td>
-<td><p>0x3ffdffff</p></td>
-<td><p>Internal SRAM 2</p></td>
-<td><p>DMA</p></td>
-</tr>
-<tr class="row-odd"><td><p>Data</p></td>
-<td><p>0x3ffe0000</p></td>
-<td><p>0x3fffffff</p></td>
-<td><p>Internal SRAM 1</p></td>
-<td><p>DMA</p></td>
</tr>
</tbody>
</table>
@@ -604,64 +532,10 @@ SPI FLASH erase.</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><p>Instruction</p></td>
-<td><p>0x40000000</p></td>
-<td><p>0x40007fff</p></td>
-<td><p>Internal ROM 0</p></td>
-<td><p>Remap</p></td>
-</tr>
-<tr class="row-odd"><td><p>Instruction</p></td>
-<td><p>0x40008000</p></td>
-<td><p>0x4005ffff</p></td>
-<td><p>Internal ROM 0</p></td>
+<tr class="row-even"><td><p>To be added</p></td>
<td></td>
-</tr>
-<tr class="row-even"><td><p>.</p></td>
-<td><p>0x40060000</p></td>
-<td><p>0x4006ffff</p></td>
<td></td>
-<td><p>Reserved</p></td>
-</tr>
-<tr class="row-odd"><td><p>Instruction</p></td>
-<td><p>0x40070000</p></td>
-<td><p>0x4007ffff</p></td>
-<td><p>Internal SRAM 0</p></td>
-<td><p>Cache</p></td>
-</tr>
-<tr class="row-even"><td><p>Instruction</p></td>
-<td><p>0x40080000</p></td>
-<td><p>0x4009ffff</p></td>
-<td><p>Internal SRAM 0</p></td>
-<td></td>
-</tr>
-<tr class="row-odd"><td><p>Instruction</p></td>
-<td><p>0x400a0000</p></td>
-<td><p>0x400affff</p></td>
-<td><p>Internal SRAM 1</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>Instruction</p></td>
-<td><p>0x400b0000</p></td>
-<td><p>0x400b7FFF</p></td>
-<td><p>Internal SRAM 1</p></td>
-<td><p>Remap</p></td>
-</tr>
-<tr class="row-odd"><td><p>Instruction</p></td>
-<td><p>0x400b8000</p></td>
-<td><p>0x400bffff</p></td>
-<td><p>Internal SRAM 1</p></td>
<td></td>
-</tr>
-<tr class="row-even"><td><p>Instruction</p></td>
-<td><p>0x400c0000</p></td>
-<td><p>0x400c1FFF</p></td>
-<td><p>RTC FAST Memory</p></td>
-<td><p>PRO_CPU Only</p></td>
-</tr>
-<tr class="row-odd"><td><p>Data / Instruction</p></td>
-<td><p>0x50000000</p></td>
-<td><p>0x50001fff</p></td>
-<td><p>RTC SLOW Memory</p></td>
<td></td>
</tr>
</tbody>
@@ -686,24 +560,18 @@ SPI FLASH erase.</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><p>Data</p></td>
-<td><p>0x3f400000</p></td>
-<td><p>0x3f7fffff</p></td>
-<td><p>External Flash</p></td>
-<td><p>Read</p></td>
-</tr>
-<tr class="row-odd"><td><p>Data</p></td>
-<td><p>0x3f800000</p></td>
-<td><p>0x3fbfffff</p></td>
-<td><p>External SRAM</p></td>
-<td><p>Read and Write</p></td>
+<tr class="row-even"><td><p>To be added</p></td>
+<td></td>
+<td></td>
+<td></td>
+<td></td>
</tr>
</tbody>
</table>
</div>
<div class="section" id="boundary-address-external">
<h3>Boundary Address (External)<a class="headerlink"
href="#boundary-address-external" title="Permalink to this headline">¶</a></h3>
-<p>Instruction 0x400c2000 0x40bfffff 11512 KB External Flash Read</p>
+<p>To be added</p>
</div>
<div class="section" id="linker-segments">
<h3>Linker Segments<a class="headerlink" href="#linker-segments"
title="Permalink to this headline">¶</a></h3>
@@ -724,262 +592,22 @@ SPI FLASH erase.</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><dl class="simple">
-<dt>FLASH mapped data:</dt><dd><ul class="simple">
-<li><p>.rodata</p></li>
-<li><p>Constructors
-/destructors</p></li>
-</ul>
-</dd>
-</dl>
-</td>
-<td><p>0x3f400010</p></td>
-<td><p>0x3fc00010</p></td>
-<td><p>R</p></td>
-<td><p>drom0_0_seg</p></td>
-</tr>
-<tr class="row-odd"><td><dl class="simple">
-<dt>COMMON data RAM:</dt><dd><ul class="simple">
-<li><p>.bss/.data</p></li>
-</ul>
-</dd>
-</dl>
-</td>
-<td><p>0x3ffb0000</p></td>
-<td><p>0x40000000</p></td>
-<td><p>RW</p></td>
-<td><p>dram0_0_seg (NOTE 1,2,3)</p></td>
-</tr>
-<tr class="row-even"><td><dl class="simple">
-<dt>IRAM for PRO cpu:</dt><dd><ul class="simple">
-<li><p>Interrupt Vectors</p></li>
-<li><p>Low level
-handlers</p></li>
-<li><p>Xtensa/Espressif
-libraries</p></li>
-</ul>
-</dd>
-</dl>
-</td>
-<td><p>0x40080000</p></td>
-<td><p>0x400a0000</p></td>
-<td><p>RX</p></td>
-<td><p>iram0_0_seg</p></td>
-</tr>
-<tr class="row-odd"><td><dl class="simple">
-<dt>RTC fast memory:</dt><dd><ul class="simple">
-<li><p>.rtc.text
-(unused?)</p></li>
-</ul>
-</dd>
-</dl>
-</td>
-<td><p>0x400c0000</p></td>
-<td><p>0x400c2000</p></td>
-<td><p>RWX</p></td>
-<td><p>rtc_iram_seg (PRO_CPU only)</p></td>
-</tr>
-<tr class="row-even"><td><dl class="simple">
-<dt>FLASH:</dt><dd><ul class="simple">
-<li><p>.text</p></li>
-</ul>
-</dd>
-</dl>
-</td>
-<td><p>0x400d0018</p></td>
-<td><p>0x40400018</p></td>
-<td><p>RX</p></td>
-<td><p>iram0_2_seg (actually FLASH)</p></td>
-</tr>
-<tr class="row-odd"><td><dl class="simple">
-<dt>RTC slow memory:</dt><dd><ul class="simple">
-<li><p>.rtc.data/rodata
-(unused?)</p></li>
-</ul>
-</dd>
-</dl>
-</td>
-<td><p>0x50000000</p></td>
-<td><p>0x50001000</p></td>
-<td><p>RW</p></td>
-<td><p>rtc_slow_seg (NOTE 4)</p></td>
+<tr class="row-even"><td><p>To be added</p></td>
+<td></td>
+<td></td>
+<td></td>
+<td></td>
</tr>
</tbody>
</table>
-<div class="admonition note">
-<p class="admonition-title">Note</p>
-<ol class="arabic simple">
-<li><p>Linker script will reserve space at the beginning of the segment
-for BT and at the end for trace memory.</p></li>
-<li><p>Heap ends at the top of dram_0_seg.</p></li>
-<li><p>Parts of this region is reserved for the ROM bootloader.</p></li>
-<li><p>Linker script will reserve space at the beginning of the segment
-for co-processor reserve memory and at the end for ULP coprocessor
-reserve memory.</p></li>
-</ol>
-</div>
-</div>
</div>
-<div class="section" id="bit-timers">
-<h2>64-bit Timers<a class="headerlink" href="#bit-timers" title="Permalink to
this headline">¶</a></h2>
-<p>ESP32 has 4 generic timers of 64 bits (2 from Group 0 and 2 from Group 1).
They’re
-accessible as character drivers, the configuration along with a guidance on how
-to run the example and the description of the application level interface
-can be found <a class="reference internal"
href="../../../components/drivers/character/timer.html"><span
class="doc">here</span></a>.</p>
-</div>
-<div class="section" id="watchdog-timers">
-<h2>Watchdog Timers<a class="headerlink" href="#watchdog-timers"
title="Permalink to this headline">¶</a></h2>
-<p>ESP32 has 3 WDTs. 2 MWDTS from the Timers Module and 1 RWDT from the RTC
Module
-(Currently not supported yet). They’re accessible as character drivers,
-The configuration along with a guidance on how to run the example and the
description
-of the application level interface can be found
-<a class="reference internal"
href="../../../components/drivers/character/watchdog.html"><span
class="doc">here</span></a>.</p>
-</div>
-<div class="section" id="smp">
-<h2>SMP<a class="headerlink" href="#smp" title="Permalink to this
headline">¶</a></h2>
-<p>The ESP32 has 2 CPUs. Support is included for testing an SMP configuration.
-That configuration is still not yet ready for usage but can be enabled with
-the following configuration settings,
-in <span class="menuselection">RTOS Features ‣ Tasks and Scheduling</span>,
with:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>CONFIG_SPINLOCK=y
-CONFIG_SMP=y
-CONFIG_SMP_NCPUS=2
-</pre></div>
-</div>
-<p>Debug Tip: During debug session, OpenOCD may mysteriously switch from one
-CPU to another. This behavior can be eliminated by uncommenting one of the
-following in <code class="docutils literal notranslate"><span
class="pre">scripts/esp32.cfg</span></code>:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span># Only configure the PRO CPU
-#set ESP32_ONLYCPU 1
-# Only configure the APP CPU
-#set ESP32_ONLYCPU 2
-</pre></div>
-</div>
-</div>
-<div class="section" id="wi-fi">
-<h2>Wi-Fi<a class="headerlink" href="#wi-fi" title="Permalink to this
headline">¶</a></h2>
-<p>A standard network interface will be configured and can be initialized such
as:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> ifup wlan0
-nsh> wapi psk wlan0 mypasswd 3
-nsh> wapi essid wlan0 myssid 1
-nsh> renew wlan0
-</pre></div>
-</div>
-<p>In this case a connection to AP with SSID <code class="docutils literal
notranslate"><span class="pre">myssid</span></code> is done, using <code
class="docutils literal notranslate"><span class="pre">mypasswd</span></code> as
-password. IP address is obtained via DHCP using <code class="docutils literal
notranslate"><span class="pre">renew</span></code> command. You can check
-the result by running <code class="docutils literal notranslate"><span
class="pre">ifconfig</span></code> afterwards.</p>
-<div class="admonition tip">
-<p class="admonition-title">Tip</p>
-<p>Boards usually expose a <code class="docutils literal notranslate"><span
class="pre">wapi</span></code> defconfig which enables Wi-Fi</p>
-</div>
-</div>
-<div class="section" id="wi-fi-softap">
-<h2>Wi-Fi SoftAP<a class="headerlink" href="#wi-fi-softap" title="Permalink to
this headline">¶</a></h2>
-<p>It is possible to use ESP32 as an Access Point (SoftAP). Actually there are
some
-boards with a <code class="docutils literal notranslate"><span
class="pre">sta_softap</span></code> which enables this support.</p>
-<p>If you are using this board config profile you can run these commands to be
able
-to connect your smartphone or laptop to your board:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> ifup wlan1
-nsh> dhcpd_start wlan1
-nsh> wapi psk wlan0 mypasswd 1
-nsh> wapi essid wlan1 nuttxap 1
-</pre></div>
-</div>
-<p>In this case, you are creating the access point <code class="docutils
literal notranslate"><span class="pre">nuttxapp</span></code> in your board and
to
-connect to it on your smartphone you will be required to type the password
<code class="docutils literal notranslate"><span
class="pre">mypasswd</span></code>.
-The <code class="docutils literal notranslate"><span
class="pre">dhcpd_start</span></code> is necessary to let your board to
associate an IP to your smartphone.</p>
-</div>
-<div class="section" id="bluetooth">
-<h2>Bluetooth<a class="headerlink" href="#bluetooth" title="Permalink to this
headline">¶</a></h2>
-<p>These are the steps to test Bluetooth Low Energy (BLE) scan on ESP32 (i.e.
Devkit board).
-First configure to use the BLE board profile:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ make distclean
-$ ./tools/configure.sh esp32-devkitc:ble
-$ make flash ESPTOOL_PORT=/dev/ttyUSB0
-</pre></div>
-</div>
-<p>Enter in the NSH shell using your prefered serial console tool and run the
scan command:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>NuttShell (NSH) NuttX-10.2.0
-nsh> ifconfig
-bnep0 Link encap:UNSPEC at DOWN
- inet addr:0.0.0.0 DRaddr:0.0.0.0 Mask:0.0.0.0
-
-wlan0 Link encap:Ethernet HWaddr ac:67:b2:53:8b:ec at UP
- inet addr:10.0.0.2 DRaddr:10.0.0.1 Mask:255.255.255.0
-
-nsh> bt bnep0 scan start
-nsh> bt bnep0 scan stop
-nsh> bt bnep0 scan get
-Scan result:
-1. addr: 63:14:2f:b9:9f:83 type: 1
- rssi: -90
- response type: 3
- advertiser data: 1e ff 06 00 01 09 20 02 7c 33 a3 a7 cd c9 44 5b
-2. addr: 52:ca:05:b5:ad:77 type: 1
- rssi: -82
- response type: 3
- advertiser data: 1e ff 06 00 01 09 20 02 03 d1 21 57 bf 19 b3 7a
-3. addr: 46:8e:b2:cd:94:27 type: 1
- rssi: -92
- response type: 2
- advertiser data: 02 01 1a 09 ff c4 00 10 33 14 12 16 80 02 0a d4
-4. addr: 46:8e:b2:cd:94:27 type: 1
- rssi: -92
- response type: 4
- advertiser data: 18 09 5b 4c 47 5d 20 77 65 62 4f 53 20 54 56 20
-5. addr: 63:14:2f:b9:9f:83 type: 1
- rssi: -80
- response type: 3
- advertiser data: 1e ff 06 00 01 09 20 02 7c 33 a3 a7 cd c9 44 5b
-nsh>
-</pre></div>
-</div>
-</div>
-<div class="section" id="using-qemu">
-<h2>Using QEMU<a class="headerlink" href="#using-qemu" title="Permalink to
this headline">¶</a></h2>
-<p>First follow the instructions <a class="reference external"
href="https://github.com/espressif/qemu/wiki";>here</a> to build QEMU.</p>
-<p>Enable the <code class="docutils literal notranslate"><span
class="pre">ESP32_QEMU_IMAGE</span></code> config found in <span
class="menuselection">Board Selection ‣ ESP32 binary image for QEMU</span>.</p>
-<p>Download the bootloader and the partition table from <a class="reference
external"
href="https://github.com/espressif/esp-nuttx-bootloader/releases";>https://github.com/espressif/esp-nuttx-bootloader/releases</a>
-and place them in a directory, say <code class="docutils literal
notranslate"><span class="pre">../esp-bins</span></code>.</p>
-<p>Build and generate the QEMU image:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ make ESPTOOL_BINDIR=../esp-bins
-</pre></div>
-</div>
-<p>A QEMU-compatible <code class="docutils literal notranslate"><span
class="pre">nuttx.merged.bin</span></code> binary image will be created. It can
be run as:</p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ qemu-system-xtensa -nographic -machine
esp32 -drive file=nuttx.merged.bin,if=mtd,format=raw
-</pre></div>
-</div>
-</div>
-<div class="section" id="things-to-do">
-<h2>Things to Do<a class="headerlink" href="#things-to-do" title="Permalink to
this headline">¶</a></h2>
-<ol class="arabic">
-<li><p>Lazy co-processor save logic supported by Xtensa. That logic works like
this:</p>
-<ol class="loweralpha simple">
-<li><p>CPENABLE is set to zero on each context switch, disabling all co-
-processors.</p></li>
-<li><p>If/when the task attempts to use the disabled co-processor, an
-exception occurs</p></li>
-<li><p>The co-processor exception handler re-enables the co-processor.</p></li>
-</ol>
-<p>Instead, the NuttX logic saves and restores CPENABLE on each context
-switch. This has disadvantages in that (1) co-processor context will
-be saved and restored even if the co-processor was never used, and (2)
-tasks must explicitly enable and disable co-processors.</p>
-</li>
-<li><p>Currently the Xtensa port copies register state save information from
-the stack into the TCB. A more efficient alternative would be to just
-save a pointer to a register state save area in the TCB. This would
-add some complexity to signal handling and also to up_initialstate().
-But the performance improvement might be worth the effort.</p></li>
-<li><p>See SMP-related issues above</p></li>
-</ol>
</div>
<div class="section" id="supported-boards">
<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/esp32-devkitc/index.html">ESP32 DevKitC</a></li>
-<li class="toctree-l1"><a class="reference internal"
href="boards/esp32-wrover-kit/index.html">ESP-WROVER-KIT</a></li>
+<li class="toctree-l1"><a class="reference internal"
href="boards/esp32s3-devkit/index.html">ESP32S3-DevKit</a></li>
+<li class="toctree-l1"><a class="reference internal"
href="boards/esp32s3-eye/index.html">ESP32-S3-EYE</a></li>
</ul>
</div>
</div>
@@ -991,8 +619,8 @@ But the performance improvement might be worth the
effort.</p></li>
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer
navigation">
- <a href="boards/esp32-devkitc/index.html" class="btn btn-neutral
float-right" title="ESP32 DevKitC" 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="Xtensa" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left"
aria-hidden="true"></span> Previous</a>
+ <a href="boards/esp32s3-devkit/index.html" class="btn btn-neutral
float-right" title="ESP32S3-DevKit" accesskey="n" rel="next">Next <span
class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="../esp32/boards/esp32-wrover-kit/index.html" class="btn
btn-neutral float-left" title="ESP-WROVER-KIT" 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/xtensa/index.html
b/content/docs/latest/platforms/xtensa/index.html
index 771a587..c435616 100644
--- a/content/docs/latest/platforms/xtensa/index.html
+++ b/content/docs/latest/platforms/xtensa/index.html
@@ -137,6 +137,7 @@
<li class="toctree-l2"><a class="reference internal"
href="../sim/index.html">Simulators</a></li>
<li class="toctree-l2 current"><a class="current reference internal"
href="#">Xtensa</a><ul>
<li class="toctree-l3"><a class="reference internal"
href="esp32/index.html">Espressif ESP32</a></li>
+<li class="toctree-l3"><a class="reference internal"
href="esp32s3/index.html">Espressif ESP32-S3</a></li>
</ul>
</li>
</ul>
@@ -222,6 +223,7 @@
<div class="toctree-wrapper compound">
<ul>
<li class="toctree-l1"><a class="reference internal"
href="esp32/index.html">Espressif ESP32</a></li>
+<li class="toctree-l1"><a class="reference internal"
href="esp32s3/index.html">Espressif ESP32-S3</a></li>
</ul>
</div>
</div>
diff --git a/content/docs/latest/searchindex.js
b/content/docs/latest/searchindex.js
index b6c154e..07b63d4 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 61695d5..1389e07 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>Fri, 17 Jun 2022 00:14:50 +0000</pubDate>
- <lastBuildDate>Fri, 17 Jun 2022 00:14:50 +0000</lastBuildDate>
+ <pubDate>Sat, 18 Jun 2022 00:15:23 +0000</pubDate>
+ <lastBuildDate>Sat, 18 Jun 2022 00:15:23 +0000</lastBuildDate>
<generator>Jekyll v3.8.5</generator>
<item>
