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 2024/04/23 00:30:43 UTC

(nuttx-website) branch asf-site updated: Publishing web: ce5ab6cc062dbbe6065b26acd6a7b45062848749 docs: 530f5cd3244f8c9b2de0df8f1a011827ea5950cc

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/nuttx-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 66e77d654 Publishing web: ce5ab6cc062dbbe6065b26acd6a7b45062848749 docs: 530f5cd3244f8c9b2de0df8f1a011827ea5950cc
66e77d654 is described below

commit 66e77d65449ad5466d91956417de36d99c75b267
Author: Alin Jerpelea <al...@sony.com>
AuthorDate: Tue Apr 23 00:19:02 2024 +0000

    Publishing web: ce5ab6cc062dbbe6065b26acd6a7b45062848749 docs: 530f5cd3244f8c9b2de0df8f1a011827ea5950cc
---
 content/docs/10.0.0/index.html                     |   2 +-
 content/docs/10.0.0/searchindex.js                 |   2 +-
 content/docs/10.0.1/index.html                     |   2 +-
 content/docs/10.0.1/searchindex.js                 |   2 +-
 content/docs/10.1.0/index.html                     |   2 +-
 content/docs/10.1.0/searchindex.js                 |   2 +-
 content/docs/10.2.0/index.html                     |   2 +-
 content/docs/10.2.0/searchindex.js                 |   2 +-
 content/docs/10.3.0/index.html                     |   2 +-
 content/docs/10.3.0/searchindex.js                 |   2 +-
 content/docs/11.0.0/index.html                     |   2 +-
 content/docs/11.0.0/searchindex.js                 |   2 +-
 content/docs/12.0.0/index.html                     |   2 +-
 content/docs/12.0.0/searchindex.js                 |   2 +-
 content/docs/12.1.0/index.html                     |   2 +-
 content/docs/12.1.0/searchindex.js                 |   2 +-
 content/docs/12.2.0/index.html                     |   2 +-
 content/docs/12.2.0/searchindex.js                 |   2 +-
 content/docs/12.2.1/index.html                     |   2 +-
 content/docs/12.2.1/searchindex.js                 |   2 +-
 content/docs/12.3.0/index.html                     |   2 +-
 content/docs/12.3.0/searchindex.js                 |   2 +-
 content/docs/12.4.0/index.html                     |   2 +-
 content/docs/12.4.0/searchindex.js                 |   2 +-
 content/docs/12.5.0/index.html                     |   2 +-
 content/docs/12.5.0/searchindex.js                 |   2 +-
 content/docs/12.5.1/index.html                     |   2 +-
 content/docs/12.5.1/searchindex.js                 |   2 +-
 .../platforms/risc-v/esp32c3/index.rst.txt         | 123 ++++++-----
 .../platforms/risc-v/esp32c6/index.rst.txt         |  82 ++++----
 .../platforms/risc-v/esp32h2/index.rst.txt         |  76 +++----
 .../_sources/platforms/xtensa/esp32/index.rst.txt  |  60 +++++-
 .../platforms/xtensa/esp32s2/index.rst.txt         |  68 ++++--
 .../platforms/xtensa/esp32s3/index.rst.txt         | 172 ++++++++--------
 content/docs/latest/index.html                     |   2 +-
 content/docs/latest/objects.inv                    | Bin 114749 -> 114815 bytes
 .../esp32c3/boards/esp32c3-generic/index.html      |   2 +-
 .../latest/platforms/risc-v/esp32c3/index.html     |  65 +++---
 .../esp32c6/boards/esp32c6-devkitc/index.html      |   2 +-
 .../esp32c6/boards/esp32c6-devkitm/index.html      |   2 +-
 .../latest/platforms/risc-v/esp32c6/index.html     |  56 +++--
 .../esp32h2/boards/esp32h2-devkit/index.html       |   2 +-
 .../latest/platforms/risc-v/esp32h2/index.html     |  48 ++---
 .../xtensa/esp32/boards/esp32-2432S028/index.html  |   2 +-
 .../xtensa/esp32/boards/esp32-audio-kit/index.html |   2 +-
 .../xtensa/esp32/boards/esp32-devkitc/index.html   |   2 +-
 .../esp32/boards/esp32-ethernet-kit/index.html     |   2 +-
 .../xtensa/esp32/boards/esp32-lyrat/index.html     |   2 +-
 .../xtensa/esp32/boards/esp32-pico-kit/index.html  |   2 +-
 .../esp32/boards/esp32-wrover-kit/index.html       |   2 +-
 .../docs/latest/platforms/xtensa/esp32/index.html  |  53 ++++-
 .../esp32s2/boards/esp32s2-kaluga-1/index.html     |   2 +-
 .../esp32s2/boards/esp32s2-saola-1/index.html      |   2 +-
 .../latest/platforms/xtensa/esp32s2/index.html     |  61 ++++--
 .../esp32s3/boards/esp32s3-devkit/index.html       |   5 +-
 .../xtensa/esp32s3/boards/esp32s3-eye/index.html   |   5 +-
 .../latest/platforms/xtensa/esp32s3/index.html     | 228 ++++++++-------------
 content/docs/latest/searchindex.js                 |   2 +-
 content/feed.xml                                   |   4 +-
 59 files changed, 626 insertions(+), 566 deletions(-)

diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index cbaeec5ba..db8e88235 100644
--- a/content/docs/10.0.0/index.html
+++ b/content/docs/10.0.0/index.html
@@ -131,7 +131,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 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: 22 April 24 at 00:10</p>
+<p>Last Updated: 23 April 24 at 00:10</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.0.0/searchindex.js b/content/docs/10.0.0/searchindex.js
index a0c3a1fc2..2d0a7a97b 100644
--- a/content/docs/10.0.0/searchindex.js
+++ b/content/docs/10.0.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
diff --git a/content/docs/10.0.1/index.html b/content/docs/10.0.1/index.html
index 8667a0d42..2a03be8f1 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -159,7 +159,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 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: 22 April 24 at 00:10</p>
+<p>Last Updated: 23 April 24 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.0.1/searchindex.js b/content/docs/10.0.1/searchindex.js
index e6e6023bf..eedeb0443 100644
--- a/content/docs/10.0.1/searchindex.js
+++ b/content/docs/10.0.1/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
diff --git a/content/docs/10.1.0/index.html b/content/docs/10.1.0/index.html
index 52824741f..dcd8566a1 100644
--- a/content/docs/10.1.0/index.html
+++ b/content/docs/10.1.0/index.html
@@ -158,7 +158,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:11</p>
+<p>Last Updated: 23 April 24 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.1.0/searchindex.js b/content/docs/10.1.0/searchindex.js
index 58d8177fa..4d6a56cfb 100644
--- a/content/docs/10.1.0/searchindex.js
+++ b/content/docs/10.1.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ 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 [...]
\ No newline at end of file
diff --git a/content/docs/10.2.0/index.html b/content/docs/10.2.0/index.html
index 6cdc47b6f..30cfe1073 100644
--- a/content/docs/10.2.0/index.html
+++ b/content/docs/10.2.0/index.html
@@ -159,7 +159,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:11</p>
+<p>Last Updated: 23 April 24 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.2.0/searchindex.js b/content/docs/10.2.0/searchindex.js
index e02328130..7b1a6877b 100644
--- a/content/docs/10.2.0/searchindex.js
+++ b/content/docs/10.2.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ 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 [...]
\ No newline at end of file
diff --git a/content/docs/10.3.0/index.html b/content/docs/10.3.0/index.html
index 6cdc47b6f..30cfe1073 100644
--- a/content/docs/10.3.0/index.html
+++ b/content/docs/10.3.0/index.html
@@ -159,7 +159,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:11</p>
+<p>Last Updated: 23 April 24 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.3.0/searchindex.js b/content/docs/10.3.0/searchindex.js
index 7b583aaeb..85c36f809 100644
--- a/content/docs/10.3.0/searchindex.js
+++ b/content/docs/10.3.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ 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 [...]
\ No newline at end of file
diff --git a/content/docs/11.0.0/index.html b/content/docs/11.0.0/index.html
index 6cdc47b6f..30cfe1073 100644
--- a/content/docs/11.0.0/index.html
+++ b/content/docs/11.0.0/index.html
@@ -159,7 +159,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:11</p>
+<p>Last Updated: 23 April 24 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/11.0.0/searchindex.js b/content/docs/11.0.0/searchindex.js
index 571de583f..72df15334 100644
--- a/content/docs/11.0.0/searchindex.js
+++ b/content/docs/11.0.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ 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 [...]
\ No newline at end of file
diff --git a/content/docs/12.0.0/index.html b/content/docs/12.0.0/index.html
index adf03a63b..5d10d36c3 100644
--- a/content/docs/12.0.0/index.html
+++ b/content/docs/12.0.0/index.html
@@ -159,7 +159,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:11</p>
+<p>Last Updated: 23 April 24 at 00:12</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.0.0/searchindex.js b/content/docs/12.0.0/searchindex.js
index 4b9f4420b..6c6f8d1a6 100644
--- a/content/docs/12.0.0/searchindex.js
+++ b/content/docs/12.0.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ 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 [...]
\ No newline at end of file
diff --git a/content/docs/12.1.0/index.html b/content/docs/12.1.0/index.html
index 62078abce..e3e7a0eb0 100644
--- a/content/docs/12.1.0/index.html
+++ b/content/docs/12.1.0/index.html
@@ -159,7 +159,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:12</p>
+<p>Last Updated: 23 April 24 at 00:12</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.1.0/searchindex.js b/content/docs/12.1.0/searchindex.js
index 483052e3b..c730e1754 100644
--- a/content/docs/12.1.0/searchindex.js
+++ b/content/docs/12.1.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ 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 [...]
\ No newline at end of file
diff --git a/content/docs/12.2.0/index.html b/content/docs/12.2.0/index.html
index 1936032b7..1ecec6cf5 100644
--- a/content/docs/12.2.0/index.html
+++ b/content/docs/12.2.0/index.html
@@ -162,7 +162,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:12</p>
+<p>Last Updated: 23 April 24 at 00:12</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.2.0/searchindex.js b/content/docs/12.2.0/searchindex.js
index 29864dfcd..aff98ad6d 100644
--- a/content/docs/12.2.0/searchindex.js
+++ b/content/docs/12.2.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.2.1/index.html b/content/docs/12.2.1/index.html
index 1936032b7..1ecec6cf5 100644
--- a/content/docs/12.2.1/index.html
+++ b/content/docs/12.2.1/index.html
@@ -162,7 +162,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:12</p>
+<p>Last Updated: 23 April 24 at 00:12</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.2.1/searchindex.js b/content/docs/12.2.1/searchindex.js
index 20b381ac5..0129ca1d4 100644
--- a/content/docs/12.2.1/searchindex.js
+++ b/content/docs/12.2.1/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.3.0/index.html b/content/docs/12.3.0/index.html
index 1c3c105b8..2a3291984 100644
--- a/content/docs/12.3.0/index.html
+++ b/content/docs/12.3.0/index.html
@@ -162,7 +162,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:12</p>
+<p>Last Updated: 23 April 24 at 00:12</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.3.0/searchindex.js b/content/docs/12.3.0/searchindex.js
index 4021b67e3..d4ff05ce6 100644
--- a/content/docs/12.3.0/searchindex.js
+++ b/content/docs/12.3.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.4.0/index.html b/content/docs/12.4.0/index.html
index 37089e2fb..1941eecea 100644
--- a/content/docs/12.4.0/index.html
+++ b/content/docs/12.4.0/index.html
@@ -169,7 +169,7 @@ standards. Additional standard APIs from Unix and other common RTOS’s (such as
 VxWorks) are adopted for functionality not available under these standards, or
 for functionality that is not appropriate for deeply-embedded environments (such
 as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:13</p>
+<p>Last Updated: 23 April 24 at 00:13</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.4.0/searchindex.js b/content/docs/12.4.0/searchindex.js
index 7e1275543..43665a817 100644
--- a/content/docs/12.4.0/searchindex.js
+++ b/content/docs/12.4.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
diff --git a/content/docs/12.5.0/index.html b/content/docs/12.5.0/index.html
index e2071e81f..87aa12de2 100644
--- a/content/docs/12.5.0/index.html
+++ b/content/docs/12.5.0/index.html
@@ -169,7 +169,7 @@ standards. Additional standard APIs from Unix and other common RTOS’s (such as
 VxWorks) are adopted for functionality not available under these standards, or
 for functionality that is not appropriate for deeply-embedded environments (such
 as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:14</p>
+<p>Last Updated: 23 April 24 at 00:14</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.5.0/searchindex.js b/content/docs/12.5.0/searchindex.js
index ecc295941..5034d1bcb 100644
--- a/content/docs/12.5.0/searchindex.js
+++ b/content/docs/12.5.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
diff --git a/content/docs/12.5.1/index.html b/content/docs/12.5.1/index.html
index 9f43ba3de..a74d30640 100644
--- a/content/docs/12.5.1/index.html
+++ b/content/docs/12.5.1/index.html
@@ -169,7 +169,7 @@ standards. Additional standard APIs from Unix and other common RTOS’s (such as
 VxWorks) are adopted for functionality not available under these standards, or
 for functionality that is not appropriate for deeply-embedded environments (such
 as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:15</p>
+<p>Last Updated: 23 April 24 at 00:15</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.5.1/searchindex.js b/content/docs/12.5.1/searchindex.js
index 20dde04d6..e07b13f96 100644
--- a/content/docs/12.5.1/searchindex.js
+++ b/content/docs/12.5.1/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
diff --git a/content/docs/latest/_sources/platforms/risc-v/esp32c3/index.rst.txt b/content/docs/latest/_sources/platforms/risc-v/esp32c3/index.rst.txt
index de181ca69..0f06329e4 100644
--- a/content/docs/latest/_sources/platforms/risc-v/esp32c3/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/risc-v/esp32c3/index.rst.txt
@@ -35,16 +35,16 @@ check for the current compiler version being used. For instance:
 
 .. code-block::
 
-   ###############################################################################
-   # Build image for tool required by RISCV builds
-   ###############################################################################
-   FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
-   # Download the latest RISCV GCC toolchain prebuilt by xPack
-   RUN mkdir riscv-none-elf-gcc && \
-   curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz" \
-   | tar -C riscv-none-elf-gcc --strip-components 1 -xz
+  ###############################################################################
+  # Build image for tool required by RISCV builds
+  ###############################################################################
+  FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
+  # Download the latest RISCV GCC toolchain prebuilt by xPack
+  RUN mkdir riscv-none-elf-gcc && \
+  curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz" \
+  | tar -C riscv-none-elf-gcc --strip-components 1 -xz
 
-It uses the xPack's prebuilt toolchain based on GCC 12.3.0.
+It uses the xPack's prebuilt toolchain based on GCC 13.2.0-2.
 
 Installing
 ----------
@@ -53,60 +53,60 @@ First, create a directory to hold the toolchain:
 
 .. code-block:: console
 
-   $ mkdir -p /path/to/your/toolchain/riscv-none-elf-gcc
+  $ mkdir -p /path/to/your/toolchain/riscv-none-elf-gcc
 
 Download and extract toolchain:
 
 .. code-block:: console
 
-   $ curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz" \
-   | tar -C /path/to/your/toolchain/riscv-none-elf-gcc --strip-components 1 -xz
+  $ curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz" \
+  | tar -C /path/to/your/toolchain/riscv-none-elf-gcc --strip-components 1 -xz
 
 Add the toolchain to your `PATH`:
 
 .. code-block:: console
 
-   $ echo "export PATH=/path/to/your/toolchain/riscv-none-elf-gcc/bin:$PATH" >> ~/.bashrc
+  $ echo "export PATH=/path/to/your/toolchain/riscv-none-elf-gcc/bin:$PATH" >> ~/.bashrc
 
 You can edit your shell's rc files if you don't use bash.
 
-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``
+Second stage bootloader
+=======================
+
+Nuttx can boot the ESP32-H2 directly using the so-called "Simple Boot". 
+An externally-built 2nd stage bootloader is not required in this case as all
+functions required to boot the device are built within Nuttx. Simple boot does not
+require any specific configuration (it is selectable by default if no other
+2nd stage bootloader is used).
+
+If other features, like `Secure Boot and Flash Encryption`_, are required, an
+externally-built 2nd stage bootloader is needed. The bootloader is built using
+the ``make bootloader`` command. This command generates the firmware in the
+``nuttx`` folder. The ``ESPTOOL_BINDIR`` is used in the ``make flash`` command
+to specify the path to the bootloader. For compatibility among other SoCs and
+future options of 2nd stage bootloaders, the commands ``make bootloader`` and
+the ``ESPTOOL_BINDIR`` option (for the ``make flash``) can be used even if no
+externally-built 2nd stage bootloader is being built (they will be ignored if
+Simple Boot is used, for instance).
 
 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.
+First, make sure that ``esptool.py`` is installed.  This tool is used to convert
+the ELF to a compatible ESP32-C3 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``
+Configure the NuttX project: ``./tools/configure.sh esp32c3-generic: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
+The ``esptool.py`` is used to flash all the binaries. However, this is also
+included in the build process and we can build and flash with::
 
-However, this is also included in the build process and we can build and flash with::
+  make flash ESPTOOL_PORT=<port> ESPTOOL_BINDIR=./
 
-   make flash 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 flash ESPTOOL_PORT=/dev/ttyUSBXX``
+Where ``<port>`` is typically ``/dev/ttyUSB0`` or similar and ``./`` is
+the path to the folder containing the externally-built 2nd stage bootloader for
+the ESP32-C3 as explained above.
 
 Debugging with OpenOCD
 ======================
@@ -119,7 +119,7 @@ integrates a USB-to-JTAG adapter.
 
 OpenOCD can then be used::
 
-   openocd -c 'set ESP_RTOS none' -f board/esp32c3-builtin.cfg
+  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::
@@ -213,24 +213,24 @@ of flash will not be sufficient to recover most flash contents.
 Prerequisites
 -------------
 
-First of all, we need to install ``imgtool`` (a MCUboot utility application to manipulate binary
-images) and ``esptool`` (the ESP32-C3 toolkit)::
+First of all, we need to install ``imgtool`` (the MCUboot utility application to manipulate binary
+images)::
 
-    $ pip install imgtool esptool
+  $ pip install imgtool
 
 We also need to make sure that the python modules are added to ``PATH``::
 
-    $ echo "PATH=$PATH:/home/$USER/.local/bin" >> ~/.bashrc
+  $ echo "PATH=$PATH:/home/$USER/.local/bin" >> ~/.bashrc
 
 Now, we will create a folder to store the generated keys (such as ``~/signing_keys``)::
 
-    $ mkdir ~/signing_keys && cd ~/signing_keys
+  $ mkdir ~/signing_keys && cd ~/signing_keys
 
 With all set up, we can now generate keys to sign the bootloader and application binary images,
 respectively, of the compiled project::
 
-    $ espsecure.py generate_signing_key --version 2 bootloader_signing_key.pem
-    $ imgtool keygen --key app_signing_key.pem --type rsa-3072
+  $ espsecure.py generate_signing_key --version 2 bootloader_signing_key.pem
+  $ imgtool keygen --key app_signing_key.pem --type rsa-3072
 
 .. important:: The contents of the key files must be stored securely and kept secret.
 
@@ -239,19 +239,14 @@ Enabling Secure Boot and Flash Encryption
 
 To enable Secure Boot for the current project, go to the project's NuttX directory, execute ``make menuconfig`` and the following steps:
 
-   1. Enable experimental features in :menuselection:`Build Setup --> Show experimental options`;
-
-   2. Enable MCUboot in :menuselection:`Application Configuration --> Bootloader Utilities --> MCUboot`;
-
-   3. Change image type to ``MCUboot-bootable format`` in :menuselection:`System Type --> Application Image Configuration --> Application Image Format`;
-
-   4. Enable building MCUboot from the source code by selecting ``Build binaries from source``;
-      in :menuselection:`System Type --> Application Image Configuration --> Source for bootloader binaries`;
-
-   5. Enable Secure Boot in :menuselection:`System Type --> Application Image Configuration --> Enable hardware Secure Boot in bootloader`;
-
-   6. If you want to protect the SPI Bus against data sniffing, you can enable Flash Encryption in
-      :menuselection:`System Type --> Application Image Configuration --> Enable Flash Encryption on boot`.
+  1. Enable experimental features in :menuselection:`Build Setup --> Show experimental options`;
+  2. Enable MCUboot in :menuselection:`Application Configuration --> Bootloader Utilities --> MCUboot`;
+  3. Change image type to ``MCUboot-bootable format`` in :menuselection:`System Type --> Application Image Configuration --> Application Image Format`;
+  4. Enable building MCUboot from the source code by selecting ``Build binaries from source``;
+     in :menuselection:`System Type --> Application Image Configuration --> Source for bootloader binaries`;
+  5. Enable Secure Boot in :menuselection:`System Type --> Application Image Configuration --> Enable hardware Secure Boot in bootloader`;
+  6. If you want to protect the SPI Bus against data sniffing, you can enable Flash Encryption in
+     :menuselection:`System Type --> Application Image Configuration --> Enable Flash Encryption on boot`.
 
 Now you can design an update and confirm agent to your application. Check the `MCUboot design guide <https://docs.mcuboot.com/design.html>`_ and the
 `MCUboot Espressif port documentation <https://docs.mcuboot.com/readme-espressif.html>`_ for
@@ -279,7 +274,7 @@ Supported Boards
 ================
 
 .. toctree::
-   :glob:
-   :maxdepth: 1
+  :glob:
+  :maxdepth: 1
 
-   boards/*/*
+  boards/*/*
diff --git a/content/docs/latest/_sources/platforms/risc-v/esp32c6/index.rst.txt b/content/docs/latest/_sources/platforms/risc-v/esp32c6/index.rst.txt
index 07d5bca9d..93c845c20 100644
--- a/content/docs/latest/_sources/platforms/risc-v/esp32c6/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/risc-v/esp32c6/index.rst.txt
@@ -33,16 +33,16 @@ check for the current compiler version being used. For instance:
 
 .. code-block::
 
-   ###############################################################################
-   # Build image for tool required by RISCV builds
-   ###############################################################################
-   FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
-   # Download the latest RISCV GCC toolchain prebuilt by xPack
-   RUN mkdir riscv-none-elf-gcc && \
-   curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz" \
-   | tar -C riscv-none-elf-gcc --strip-components 1 -xz
+  ###############################################################################
+  # Build image for tool required by RISCV builds
+  ###############################################################################
+  FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
+  # Download the latest RISCV GCC toolchain prebuilt by xPack
+  RUN mkdir riscv-none-elf-gcc && \
+  curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz" \
+  | tar -C riscv-none-elf-gcc --strip-components 1 -xz
 
-It uses the xPack's prebuilt toolchain based on GCC 12.3.0.
+It uses the xPack's prebuilt toolchain based on GCC 13.2.0-2.
 
 Installing
 ----------
@@ -51,60 +51,52 @@ First, create a directory to hold the toolchain:
 
 .. code-block:: console
 
-   $ mkdir -p /path/to/your/toolchain/riscv-none-elf-gcc
+  $ mkdir -p /path/to/your/toolchain/riscv-none-elf-gcc
 
 Download and extract toolchain:
 
 .. code-block:: console
 
-   $ curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz" \
-   | tar -C /path/to/your/toolchain/riscv-none-elf-gcc --strip-components 1 -xz
+  $ curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz" \
+  | tar -C /path/to/your/toolchain/riscv-none-elf-gcc --strip-components 1 -xz
 
 Add the toolchain to your `PATH`:
 
 .. code-block:: console
 
-   $ echo "export PATH=/path/to/your/toolchain/riscv-none-elf-gcc/bin:$PATH" >> ~/.bashrc
+  $ echo "export PATH=/path/to/your/toolchain/riscv-none-elf-gcc/bin:$PATH" >> ~/.bashrc
 
 You can edit your shell's rc files if you don't use bash.
 
-Second stage bootloader and partition table
-===========================================
+Second stage bootloader
+=======================
 
-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-esp32c6.bin`` and ``partition-table-esp32c6.bin`` and place them
-in a folder, the path to this folder will be used later to program them. This
-can be: ``../esp-bins``
+Nuttx can boot the ESP32-H2 directly using the so-called "Simple Boot". 
+An externally-built 2nd stage bootloader is not required in this case as all
+functions required to boot the device are built within Nuttx. Simple boot does not
+require any specific configuration (it is selectable by default if no other
+2nd stage bootloader is used). For compatibility among other SoCs and future options
+of 2nd stage bootloaders, the commands ``make bootloader`` and the ``ESPTOOL_BINDIR``
+option (for the ``make flash``) are kept (and ignored if Simple Boot is used).
 
 Building and flashing
 =====================
 
-First make sure that ``esptool.py`` is installed.  This tool is used to convert
+First, make sure that ``esptool.py`` is installed.  This tool is used to convert
 the ELF to a compatible ESP32-C6 image and to flash the image into the board.
 It can be installed with: ``pip install esptool``.
 
-Configure the NuttX project: ``./tools/configure.sh esp32c6-devkitc:nsh`` or
-``./tools/configure.sh esp32c6-devkitm: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::
+Configure the NuttX project: ``./tools/configure.sh esp32c6-devkitc:nsh``
+Run ``make`` to build the project.  Note that the conversion mentioned above is
+included in the build process.
+The ``esptool.py`` is used to flash all the binaries. However, this is also
+included in the build process and we can build and flash with::
 
-     esptool.py --chip esp32c6 --port /dev/ttyUSBXX --baud 921600 write_flash 0x0 bootloader.bin 0x8000 partition-table.bin 0x10000 nuttx.bin
+  make flash ESPTOOL_PORT=<port> ESPTOOL_BINDIR=./
 
-However, this is also included in the build process and we can build and flash with::
-
-   make flash 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-C6 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 flash ESPTOOL_PORT=/dev/ttyUSBXX``
+Where ``<port>`` is typically ``/dev/ttyUSB0`` or similar and ``./`` is
+the path to the folder containing the externally-built 2nd stage bootloader for
+the ESP32-C6 as explained above.
 
 Debugging with OpenOCD
 ======================
@@ -112,12 +104,12 @@ Debugging with OpenOCD
 Download and build OpenOCD from Espressif, that can be found in
 https://github.com/espressif/openocd-esp32
 
-You don not need an external JTAG is to debug, the ESP32-C6 integrates a
+You do not need an external JTAG to debug, the ESP32-C6 integrates a
 USB-to-JTAG adapter.
 
 OpenOCD can then be used::
 
-   openocd -c 'set ESP_RTOS none' -f board/esp32c6-builtin.cfg
+  openocd -c 'set ESP_RTOS none' -f board/esp32c6-builtin.cfg
 
 If you want to debug with an external JTAG adapter it can
 be connected as follows::
@@ -179,7 +171,7 @@ Supported Boards
 ================
 
 .. toctree::
-   :glob:
-   :maxdepth: 1
+  :glob:
+  :maxdepth: 1
 
-   boards/*/*
+  boards/*/*
diff --git a/content/docs/latest/_sources/platforms/risc-v/esp32h2/index.rst.txt b/content/docs/latest/_sources/platforms/risc-v/esp32h2/index.rst.txt
index de5945a74..1c1010689 100644
--- a/content/docs/latest/_sources/platforms/risc-v/esp32h2/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/risc-v/esp32h2/index.rst.txt
@@ -28,21 +28,21 @@ ESP32-H2 Toolchain
 
 A generic RISC-V toolchain can be used to build ESP32-H2 projects. It's recommended to use the same
 toolchain used by NuttX CI. Please refer to the Docker
-`container <https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile>`_ and
+`container <https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile>`_ and 
 check for the current compiler version being used. For instance:
 
 .. code-block::
 
-   ###############################################################################
-   # Build image for tool required by RISCV builds
-   ###############################################################################
-   FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
-   # Download the latest RISCV GCC toolchain prebuilt by xPack
-   RUN mkdir riscv-none-elf-gcc && \
-   curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz" \
-   | tar -C riscv-none-elf-gcc --strip-components 1 -xz
+  ###############################################################################
+  # Build image for tool required by RISCV builds
+  ###############################################################################
+  FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
+  # Download the latest RISCV GCC toolchain prebuilt by xPack
+  RUN mkdir riscv-none-elf-gcc && \
+  curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz" \
+  | tar -C riscv-none-elf-gcc --strip-components 1 -xz
 
-It uses the xPack's prebuilt toolchain based on GCC 12.3.0.
+It uses the xPack's prebuilt toolchain based on GCC 13.2.0-2.
 
 Installing
 ----------
@@ -51,60 +51,52 @@ First, create a directory to hold the toolchain:
 
 .. code-block:: console
 
-   $ mkdir -p /path/to/your/toolchain/riscv-none-elf-gcc
+  $ mkdir -p /path/to/your/toolchain/riscv-none-elf-gcc
 
 Download and extract toolchain:
 
 .. code-block:: console
 
-   $ curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz" \
-   | tar -C /path/to/your/toolchain/riscv-none-elf-gcc --strip-components 1 -xz
+  $ curl -s -L "https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz" \
+  | tar -C /path/to/your/toolchain/riscv-none-elf-gcc --strip-components 1 -xz
 
 Add the toolchain to your `PATH`:
 
 .. code-block:: console
 
-   $ echo "export PATH=/path/to/your/toolchain/riscv-none-elf-gcc/bin:$PATH" >> ~/.bashrc
+  $ echo "export PATH=/path/to/your/toolchain/riscv-none-elf-gcc/bin:$PATH" >> ~/.bashrc
 
 You can edit your shell's rc files if you don't use bash.
 
-Second stage bootloader and partition table
-===========================================
+Second stage bootloader
+=======================
 
-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-esp32h2.bin`` and ``partition-table-esp32h2.bin`` and place them
-in a folder, the path to this folder will be used later to program them. This
-can be: ``../esp-bins``
+Nuttx can boot the ESP32-H2 directly using the so-called "Simple Boot". 
+An externally-built 2nd stage bootloader is not required in this case as all
+functions required to boot the device are built within Nuttx. Simple boot does not
+require any specific configuration (it is selectable by default if no other
+2nd stage bootloader is used). For compatibility among other SoCs and future options
+of 2nd stage bootloaders, the commands ``make bootloader`` and the ``ESPTOOL_BINDIR``
+option (for the ``make flash``) are kept (and ignored if Simple Boot is used).
 
 Building and flashing
 =====================
 
-First make sure that ``esptool.py`` is installed.  This tool is used to convert
+First, make sure that ``esptool.py`` is installed.  This tool is used to convert
 the ELF to a compatible ESP32-H2 image and to flash the image into the board.
 It can be installed with: ``pip install esptool``.
 
 Configure the NuttX project: ``./tools/configure.sh esp32h2-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::
+The ``esptool.py`` is used to flash all the binaries. However, this is also
+included in the build process and we can build and flash with::
 
-     esptool.py --chip esp32h2 --port /dev/ttyUSBXX --baud 921600 write_flash 0x0 bootloader.bin 0x8000 partition-table.bin 0x10000 nuttx.bin
+  make flash ESPTOOL_PORT=<port> ESPTOOL_BINDIR=./
 
-However, this is also included in the build process and we can build and flash with::
-
-   make flash 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-H2 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 flash ESPTOOL_PORT=/dev/ttyUSBXX``
+Where ``<port>`` is typically ``/dev/ttyUSB0`` or similar and ``./`` is
+the path to the folder containing the externally-built 2nd stage bootloader for
+the ESP32-H2 as explained above.
 
 Debugging with OpenOCD
 ======================
@@ -117,7 +109,7 @@ USB-to-JTAG adapter.
 
 OpenOCD can then be used::
 
-   openocd -c 'set ESP_RTOS none' -f board/esp32h2-builtin.cfg
+  openocd -c 'set ESP_RTOS none' -f board/esp32h2-builtin.cfg
 
 If you want to debug with an external JTAG adapter it can
 be connected as follows::
@@ -179,7 +171,7 @@ Supported Boards
 ================
 
 .. toctree::
-   :glob:
-   :maxdepth: 1
+  :glob:
+  :maxdepth: 1
 
-   boards/*/*
+  boards/*/*
diff --git a/content/docs/latest/_sources/platforms/xtensa/esp32/index.rst.txt b/content/docs/latest/_sources/platforms/xtensa/esp32/index.rst.txt
index f81ce33d7..dce0af96c 100644
--- a/content/docs/latest/_sources/platforms/xtensa/esp32/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/xtensa/esp32/index.rst.txt
@@ -16,16 +16,61 @@ 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
-=========
+ESP32 Toolchain
+==================
+
+The toolchain used to build ESP32 firmware can be either downloaded or built from the sources.
+It is **highly** recommended to use (download or build) the same toolchain version that is being
+used by the NuttX CI.
+
+Please refer to the Docker
+`container <https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile>`_ and
+check for the current compiler version being used. For instance:
+
+.. code-block::
+
+  ###############################################################################
+  # Build image for tool required by ESP32 builds
+  ###############################################################################
+  FROM nuttx-toolchain-base AS nuttx-toolchain-esp32
+  # Download the latest ESP32 GCC toolchain prebuilt by Espressif
+  RUN mkdir -p xtensa-esp32-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32-elf-gcc --strip-components 1 -xJ
+
+  RUN mkdir -p xtensa-esp32s2-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32s2-elf-gcc --strip-components 1 -xJ
+
+  RUN mkdir -p xtensa-esp32s3-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32s3-elf-gcc --strip-components 1 -xJ
+
+For ESP32, the toolchain version is based on GGC 12.2.0 (``xtensa-esp32-elf-12.2.0_20230208``)
+
+The prebuilt Toolchain (Recommended)
+------------------------------------
 
-You can use the prebuilt `toolchain <https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-tools.html#xtensa-esp32-elf>`__
-for Xtensa architecture and `OpenOCD <https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-tools.html#openocd-esp32>`__
-for ESP32 by Espressif.
+First, create a directory to hold the toolchain:
+
+.. code-block:: console
+
+  $ mkdir -p /path/to/your/toolchain/xtensa-esp32-elf-gcc
+
+Download and extract toolchain:
+
+.. code-block:: console
+
+  $ curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+  | tar -C xtensa-esp32-elf-gcc --strip-components 1 -xJ
+
+Add the toolchain to your `PATH`:
+
+.. code-block:: console
 
-For flashing firmware, you will need to install ``esptool.py`` by running::
+  $ echo "export PATH=/path/to/your/toolchain/xtensa-esp32-elf-gcc/bin:$PATH" >> ~/.bashrc
 
-    $ pip install esptool
+You can edit your shell's rc files if you don't use bash.
 
 Building from source
 --------------------
@@ -37,7 +82,6 @@ build the toolchain with crosstool-NG on Linux are as follows
 
   $ git clone https://github.com/espressif/crosstool-NG.git
   $ cd crosstool-NG
-  $ git checkout esp-2021r1
   $ git submodule update --init
 
   $ ./bootstrap && ./configure --enable-local && make
diff --git a/content/docs/latest/_sources/platforms/xtensa/esp32s2/index.rst.txt b/content/docs/latest/_sources/platforms/xtensa/esp32s2/index.rst.txt
index d61a41d08..9ef5adad1 100644
--- a/content/docs/latest/_sources/platforms/xtensa/esp32s2/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/xtensa/esp32s2/index.rst.txt
@@ -9,16 +9,61 @@ All embedded memory, external memory and peripherals are located on the
 data bus and/or the instruction bus of the CPU. Multiple peripherals in
 the system can access embedded memory via DMA.
 
-Toolchain
-=========
+ESP32-S2 Toolchain
+==================
+
+The toolchain used to build ESP32-S2 firmware can be either downloaded or built from the sources.
+It is **highly** recommended to use (download or build) the same toolchain version that is being
+used by the NuttX CI.
+
+Please refer to the Docker
+`container <https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile>`_ and
+check for the current compiler version being used. For instance:
+
+.. code-block::
+
+  ###############################################################################
+  # Build image for tool required by ESP32 builds
+  ###############################################################################
+  FROM nuttx-toolchain-base AS nuttx-toolchain-esp32
+  # Download the latest ESP32 GCC toolchain prebuilt by Espressif
+  RUN mkdir -p xtensa-esp32-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32-elf-gcc --strip-components 1 -xJ
+
+  RUN mkdir -p xtensa-esp32s2-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32s2-elf-gcc --strip-components 1 -xJ
+
+  RUN mkdir -p xtensa-esp32s3-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32s3-elf-gcc --strip-components 1 -xJ
+
+For ESP32-S2, the toolchain version is based on GGC 12.2.0 (``xtensa-esp32s2-elf-12.2.0_20230208``)
+
+The prebuilt Toolchain (Recommended)
+------------------------------------
+
+First, create a directory to hold the toolchain:
 
-You can use the prebuilt `toolchain <https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/tools/idf-tools.html#xtensa-esp32-elf>`__
-for Xtensa architecture and `OpenOCD <https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/tools/idf-tools.html#openocd-esp32>`__
-for ESP32-S2 by Espressif.
+.. code-block:: console
+
+  $ mkdir -p /path/to/your/toolchain/xtensa-esp32s2-elf-gcc
+
+Download and extract toolchain:
+
+.. code-block:: console
+
+  $ curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+  | tar -C xtensa-esp32s2-elf-gcc --strip-components 1 -xJ
+
+Add the toolchain to your `PATH`:
+
+.. code-block:: console
 
-For flashing firmware, you will need to install ``esptool.py`` by running::
+  $ echo "export PATH=/path/to/your/toolchain/xtensa-esp32s2-elf-gcc/bin:$PATH" >> ~/.bashrc
 
-    $ pip install esptool
+You can edit your shell's rc files if you don't use bash.
 
 Building from source
 --------------------
@@ -30,20 +75,19 @@ build the toolchain with crosstool-NG on Linux are as follows
 
   $ git clone https://github.com/espressif/crosstool-NG.git
   $ cd crosstool-NG
-  $ git checkout esp-2021r1
   $ git submodule update --init
 
   $ ./bootstrap && ./configure --enable-local && make
 
-  $ ./ct-ng xtensa-esp32-elf
+  $ ./ct-ng xtensa-esp32s2-elf
   $ ./ct-ng build
 
-  $ chmod -R u+w builds/xtensa-esp32-elf
+  $ chmod -R u+w builds/xtensa-esp32s2-elf
 
   $ export PATH="crosstool-NG/builds/xtensa-esp32-elf/bin:$PATH"
 
-Alternatively, you may follow the steps in
-`ESP-IDF documentation <https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/get-started/linux-macos-setup.html>`_.
+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
 ========
diff --git a/content/docs/latest/_sources/platforms/xtensa/esp32s3/index.rst.txt b/content/docs/latest/_sources/platforms/xtensa/esp32s3/index.rst.txt
index dba6372b6..a1ee72b32 100644
--- a/content/docs/latest/_sources/platforms/xtensa/esp32s3/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/xtensa/esp32s3/index.rst.txt
@@ -16,16 +16,61 @@ 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
-=========
+ESP32-S3 Toolchain
+==================
+
+The toolchain used to build ESP32-S3 firmware can be either downloaded or built from the sources.
+It is **highly** recommended to use (download or build) the same toolchain version that is being
+used by the NuttX CI.
+
+Please refer to the Docker
+`container <https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile>`_ and
+check for the current compiler version being used. For instance:
+
+.. code-block::
+
+  ###############################################################################
+  # Build image for tool required by ESP32 builds
+  ###############################################################################
+  FROM nuttx-toolchain-base AS nuttx-toolchain-esp32
+  # Download the latest ESP32 GCC toolchain prebuilt by Espressif
+  RUN mkdir -p xtensa-esp32-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32-elf-gcc --strip-components 1 -xJ
+
+  RUN mkdir -p xtensa-esp32s2-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32s2-elf-gcc --strip-components 1 -xJ
 
-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.
+  RUN mkdir -p xtensa-esp32s3-elf-gcc && \
+    curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+    | tar -C xtensa-esp32s3-elf-gcc --strip-components 1 -xJ
+
+For ESP32-S3, the toolchain version is based on GGC 12.2.0 (``xtensa-esp32s3-elf-12.2.0_20230208``)
+
+The prebuilt Toolchain (Recommended)
+------------------------------------
+
+First, create a directory to hold the toolchain:
+
+.. code-block:: console
 
-For flashing firmware, you will need to install ``esptool.py`` by running::
+  $ mkdir -p /path/to/your/toolchain/xtensa-esp32s3-elf-gcc
 
-    $ pip install esptool
+Download and extract toolchain:
+
+.. code-block:: console
+
+  $ curl -s -L "https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz" \
+  | tar -C xtensa-esp32s3-elf-gcc --strip-components 1 -xJ
+
+Add the toolchain to your `PATH`:
+
+.. code-block:: console
+
+  $ echo "export PATH=/path/to/your/toolchain/xtensa-esp32s3-elf-gcc/bin:$PATH" >> ~/.bashrc
+
+You can edit your shell's rc files if you don't use bash.
 
 Building from source
 --------------------
@@ -51,36 +96,52 @@ build the toolchain with crosstool-NG on Linux are as follows
 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``.
+Building and flashing NuttX
+===========================
 
 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:
+Nuttx can boot the ESP32-S3 directly using the so-called "Simple Boot". An externally-built
+2nd stage bootloader is not required in this case as all functions required to boot the device
+are built within Nuttx. Simple boot does not require any specific configuration (it is selectable
+by default if no other 2nd stage bootloader is used).
 
-.. code-block:: console
+If other features are required, an externally-built 2nd stage bootloader is needed. The bootloader
+is built using the ``make bootloader`` command. This command generates the firmware in the
+``nuttx`` folder. The ``ESPTOOL_BINDIR`` is used in the ``make flash`` command to specify the path
+to the bootloader. For compatibility among other SoCs and future options of 2nd stage bootloaders,
+the commands ``make bootloader`` and the ``ESPTOOL_BINDIR`` option (for the ``make flash``) can be
+used even if no externally-built 2nd stage bootloader is being built (they will be ignored if
+Simple Boot is used, for instance)::
 
-   $ make flash ESPTOOL_PORT=<port> ESPTOOL_BINDIR=<dir>
+  $ make bootloader
 
-.. 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.
+.. note:: It is recommended that if this is the first time you are using the board with NuttX to
+   perform a complete SPI FLASH erase.
 
-   .. code-block:: console
+    .. code-block:: console
 
       $ esptool.py erase_flash
 
+Building and Flashing
+---------------------
+
+First, make sure that ``esptool.py`` is installed.  This tool is used to convert the ELF to a
+compatible ESP32-S3 image and to flash the image into the board.
+It can be installed with: ``pip install esptool``.
+
+It's a two-step process where the first converts the ELF file into an ESP32-S3 compatible binary
+and the second flashes it to the board. These steps are included in the build system and it is
+possible to build and flash the NuttX firmware simply by running::
+
+    $ make flash ESPTOOL_PORT=<port> ESPTOOL_BINDIR=./
+
+where ``<port>`` is typically ``/dev/ttyUSB0`` or similar. ``ESPTOOL_BINDIR=./`` is the path of the
+externally-built 2nd stage bootloader and the partition table (if applicable): when built using the
+``make bootloader``, these files are placed into ``nuttx`` folder. ``ESPTOOL_BAUD`` is able to
+change the flash baudrate if desired.
+
 Peripheral Support
 ==================
 
@@ -169,64 +230,11 @@ using WPA2.
 
 The ``dhcpd_start`` is necessary to let your board to associate an IP to your smartphone.
 
-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
+  :glob:
+  :maxdepth: 1
 
-   boards/*/*
+  boards/*/*
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index 89a8849b5..cfa963ca4 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -170,7 +170,7 @@ standards. Additional standard APIs from Unix and other common RTOS’s (such as
 VxWorks) are adopted for functionality not available under these standards, or
 for functionality that is not appropriate for deeply-embedded environments (such
 as fork()).</p>
-<p>Last Updated: 22 April 24 at 00:16</p>
+<p>Last Updated: 23 April 24 at 00:16</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/latest/objects.inv b/content/docs/latest/objects.inv
index 4d12319a5..5ec413701 100644
Binary files a/content/docs/latest/objects.inv and b/content/docs/latest/objects.inv differ
diff --git a/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-generic/index.html b/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-generic/index.html
index bd348ed45..4abbccae1 100644
--- a/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-generic/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-generic/index.html
@@ -133,7 +133,7 @@
 <li class="toctree-l3"><a class="reference internal" href="../../../esp32c3-legacy/index.html">Espressif ESP32-C3 (Legacy)</a></li>
 <li class="toctree-l3 current"><a class="reference internal" href="../../index.html">Espressif ESP32-C3</a><ul class="current">
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-c3-toolchain">ESP32-C3 Toolchain</a></li>
-<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader-and-partition-table">Second stage bootloader and partition table</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader">Second stage bootloader</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#building-and-flashing">Building and flashing</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#debugging-with-openocd">Debugging with OpenOCD</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
diff --git a/content/docs/latest/platforms/risc-v/esp32c3/index.html b/content/docs/latest/platforms/risc-v/esp32c3/index.html
index 86b773488..e97973713 100644
--- a/content/docs/latest/platforms/risc-v/esp32c3/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32c3/index.html
@@ -136,7 +136,7 @@
 <li class="toctree-l5"><a class="reference internal" href="#installing">Installing</a></li>
 </ul>
 </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="#second-stage-bootloader">Second stage bootloader</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>
@@ -247,11 +247,11 @@ check for the current compiler version being used. For instance:</p>
 FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
 # Download the latest RISCV GCC toolchain prebuilt by xPack
 RUN mkdir riscv-none-elf-gcc &amp;&amp; \
-curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz&quot; \
+curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz&quot; \
 | tar -C riscv-none-elf-gcc --strip-components 1 -xz
 </pre></div>
 </div>
-<p>It uses the xPack’s prebuilt toolchain based on GCC 12.3.0.</p>
+<p>It uses the xPack’s prebuilt toolchain based on GCC 13.2.0-2.</p>
 <section id="installing">
 <h3>Installing<a class="headerlink" href="#installing" title="Permalink to this heading"></a></h3>
 <p>First, create a directory to hold the toolchain:</p>
@@ -259,7 +259,7 @@ curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/rel
 </pre></div>
 </div>
 <p>Download and extract toolchain:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz&quot;</span><span class="w"> </span><span class="se">\</span>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz&quot;</span><span class="w"> </span><span class="se">\</span>
 <span class="p">|</span><span class="w"> </span>tar<span class="w"> </span>-C<span class="w"> </span>/path/to/your/toolchain/riscv-none-elf-gcc<span class="w"> </span>--strip-components<span class="w"> </span><span class="m">1</span><span class="w"> </span>-xz
 </pre></div>
 </div>
@@ -270,40 +270,39 @@ curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/rel
 <p>You can edit your shell’s rc files if you don’t use bash.</p>
 </section>
 </section>
-<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 heading"></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>
+<section id="second-stage-bootloader">
+<h2>Second stage bootloader<a class="headerlink" href="#second-stage-bootloader" title="Permalink to this heading"></a></h2>
+<p>Nuttx can boot the ESP32-H2 directly using the so-called “Simple Boot”.
+An externally-built 2nd stage bootloader is not required in this case as all
+functions required to boot the device are built within Nuttx. Simple boot does not
+require any specific configuration (it is selectable by default if no other
+2nd stage bootloader is used).</p>
+<p>If other features, like <a class="reference internal" href="#secure-boot-and-flash-encryption">Secure Boot and Flash Encryption</a>, are required, an
+externally-built 2nd stage bootloader is needed. The bootloader is built using
+the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">bootloader</span></code> command. This command generates the firmware in the
+<code class="docutils literal notranslate"><span class="pre">nuttx</span></code> folder. The <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BINDIR</span></code> is used in the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">flash</span></code> command
+to specify the path to the bootloader. For compatibility among other SoCs and
+future options of 2nd stage bootloaders, the commands <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">bootloader</span></code> and
+the <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BINDIR</span></code> option (for the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">flash</span></code>) can be used even if no
+externally-built 2nd stage bootloader is being built (they will be ignored if
+Simple Boot is used, for instance).</p>
 </section>
 <section id="building-and-flashing">
 <h2>Building and flashing<a class="headerlink" href="#building-and-flashing" title="Permalink to this heading"></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.
+<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-C3 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>
+<p>Configure the NuttX project: <code class="docutils literal notranslate"><span class="pre">./tools/configure.sh</span> <span class="pre">esp32c3-generic: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 <code class="docutils literal notranslate"><span class="pre">esptool.py</span></code> 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
+The <code class="docutils literal notranslate"><span class="pre">esptool.py</span></code> is used to flash all the binaries. 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 flash ESPTOOL_PORT=&lt;port&gt; ESPTOOL_BINDIR=./
 </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 flash ESPTOOL_PORT=&lt;port&gt; ESPTOOL_BINDIR=../esp-bins
-</pre></div>
-</div>
-<p>Where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</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">flash</span> <span class="pre">ESPTOOL_PORT=/dev/ttyUSBXX</span></code></p>
+<p>Where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</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">./</span></code> is
+the path to the folder containing the externally-built 2nd stage bootloader for
+the ESP32-C3 as explained above.</p>
 </section>
 <section id="debugging-with-openocd">
 <h2>Debugging with OpenOCD<a class="headerlink" href="#debugging-with-openocd" title="Permalink to this heading"></a></h2>
@@ -473,9 +472,9 @@ Re-flashing an encrypted system is complicated and not always possible. You can
 </section>
 <section id="prerequisites">
 <h3>Prerequisites<a class="headerlink" href="#prerequisites" title="Permalink to this heading"></a></h3>
-<p>First of all, we need to install <code class="docutils literal notranslate"><span class="pre">imgtool</span></code> (a MCUboot utility application to manipulate binary
-images) and <code class="docutils literal notranslate"><span class="pre">esptool</span></code> (the ESP32-C3 toolkit):</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>$ pip install imgtool esptool
+<p>First of all, we need to install <code class="docutils literal notranslate"><span class="pre">imgtool</span></code> (the MCUboot utility application to manipulate binary
+images):</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>$ pip install imgtool
 </pre></div>
 </div>
 <p>We also need to make sure that the python modules are added to <code class="docutils literal notranslate"><span class="pre">PATH</span></code>:</p>
diff --git a/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitc/index.html b/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitc/index.html
index 8519d235e..51c037d79 100644
--- a/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitc/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitc/index.html
@@ -134,7 +134,7 @@
 <li class="toctree-l3"><a class="reference internal" href="../../../esp32c3/index.html">Espressif ESP32-C3</a></li>
 <li class="toctree-l3 current"><a class="reference internal" href="../../index.html">Espressif ESP32-C6</a><ul class="current">
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-c6-toolchain">ESP32-C6 Toolchain</a></li>
-<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader-and-partition-table">Second stage bootloader and partition table</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader">Second stage bootloader</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#building-and-flashing">Building and flashing</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#debugging-with-openocd">Debugging with OpenOCD</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
diff --git a/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitm/index.html b/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitm/index.html
index 1fa7b2d86..2b024a3e6 100644
--- a/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitm/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32c6/boards/esp32c6-devkitm/index.html
@@ -134,7 +134,7 @@
 <li class="toctree-l3"><a class="reference internal" href="../../../esp32c3/index.html">Espressif ESP32-C3</a></li>
 <li class="toctree-l3 current"><a class="reference internal" href="../../index.html">Espressif ESP32-C6</a><ul class="current">
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-c6-toolchain">ESP32-C6 Toolchain</a></li>
-<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader-and-partition-table">Second stage bootloader and partition table</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader">Second stage bootloader</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#building-and-flashing">Building and flashing</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#debugging-with-openocd">Debugging with OpenOCD</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
diff --git a/content/docs/latest/platforms/risc-v/esp32c6/index.html b/content/docs/latest/platforms/risc-v/esp32c6/index.html
index d83e348c4..79e0af30f 100644
--- a/content/docs/latest/platforms/risc-v/esp32c6/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32c6/index.html
@@ -137,7 +137,7 @@
 <li class="toctree-l5"><a class="reference internal" href="#installing">Installing</a></li>
 </ul>
 </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="#second-stage-bootloader">Second stage bootloader</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>
@@ -241,11 +241,11 @@ check for the current compiler version being used. For instance:</p>
 FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
 # Download the latest RISCV GCC toolchain prebuilt by xPack
 RUN mkdir riscv-none-elf-gcc &amp;&amp; \
-curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz&quot; \
+curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz&quot; \
 | tar -C riscv-none-elf-gcc --strip-components 1 -xz
 </pre></div>
 </div>
-<p>It uses the xPack’s prebuilt toolchain based on GCC 12.3.0.</p>
+<p>It uses the xPack’s prebuilt toolchain based on GCC 13.2.0-2.</p>
 <section id="installing">
 <h3>Installing<a class="headerlink" href="#installing" title="Permalink to this heading"></a></h3>
 <p>First, create a directory to hold the toolchain:</p>
@@ -253,7 +253,7 @@ curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/rel
 </pre></div>
 </div>
 <p>Download and extract toolchain:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz&quot;</span><span class="w"> </span><span class="se">\</span>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz&quot;</span><span class="w"> </span><span class="se">\</span>
 <span class="p">|</span><span class="w"> </span>tar<span class="w"> </span>-C<span class="w"> </span>/path/to/your/toolchain/riscv-none-elf-gcc<span class="w"> </span>--strip-components<span class="w"> </span><span class="m">1</span><span class="w"> </span>-xz
 </pre></div>
 </div>
@@ -264,46 +264,38 @@ curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/rel
 <p>You can edit your shell’s rc files if you don’t use bash.</p>
 </section>
 </section>
-<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 heading"></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-esp32c6.bin</span></code> and <code class="docutils literal notranslate"><span class="pre">partition-table-esp32c6.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>
+<section id="second-stage-bootloader">
+<h2>Second stage bootloader<a class="headerlink" href="#second-stage-bootloader" title="Permalink to this heading"></a></h2>
+<p>Nuttx can boot the ESP32-H2 directly using the so-called “Simple Boot”.
+An externally-built 2nd stage bootloader is not required in this case as all
+functions required to boot the device are built within Nuttx. Simple boot does not
+require any specific configuration (it is selectable by default if no other
+2nd stage bootloader is used). For compatibility among other SoCs and future options
+of 2nd stage bootloaders, the commands <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">bootloader</span></code> and the <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BINDIR</span></code>
+option (for the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">flash</span></code>) are kept (and ignored if Simple Boot is used).</p>
 </section>
 <section id="building-and-flashing">
 <h2>Building and flashing<a class="headerlink" href="#building-and-flashing" title="Permalink to this heading"></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
+<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-C6 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">esp32c6-devkitc:nsh</span></code> or
-<code class="docutils literal notranslate"><span class="pre">./tools/configure.sh</span> <span class="pre">esp32c6-devkitm:nsh``Run</span> <span class="pre">``make</span></code> to build the project.
-Note that the conversion mentioned above is included in the build process.
-The <code class="docutils literal notranslate"><span class="pre">esptool.py</span></code> command to flash all the binaries is:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>esptool.py --chip esp32c6 --port /dev/ttyUSBXX --baud 921600 write_flash 0x0 bootloader.bin 0x8000 partition-table.bin 0x10000 nuttx.bin
+<p>Configure the NuttX project: <code class="docutils literal notranslate"><span class="pre">./tools/configure.sh</span> <span class="pre">esp32c6-devkitc: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 <code class="docutils literal notranslate"><span class="pre">esptool.py</span></code> is used to flash all the binaries. 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 flash ESPTOOL_PORT=&lt;port&gt; ESPTOOL_BINDIR=./
 </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 flash ESPTOOL_PORT=&lt;port&gt; ESPTOOL_BINDIR=../esp-bins
-</pre></div>
-</div>
-<p>Where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</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-C6 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">flash</span> <span class="pre">ESPTOOL_PORT=/dev/ttyUSBXX</span></code></p>
+<p>Where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</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">./</span></code> is
+the path to the folder containing the externally-built 2nd stage bootloader for
+the ESP32-C6 as explained above.</p>
 </section>
 <section id="debugging-with-openocd">
 <h2>Debugging with OpenOCD<a class="headerlink" href="#debugging-with-openocd" title="Permalink to this heading"></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>You don not need an external JTAG is to debug, the ESP32-C6 integrates a
+<p>You do not need an external JTAG to debug, the ESP32-C6 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 &#39;set ESP_RTOS none&#39; -f board/esp32c6-builtin.cfg
diff --git a/content/docs/latest/platforms/risc-v/esp32h2/boards/esp32h2-devkit/index.html b/content/docs/latest/platforms/risc-v/esp32h2/boards/esp32h2-devkit/index.html
index 4bf3c0f35..1cc91e030 100644
--- a/content/docs/latest/platforms/risc-v/esp32h2/boards/esp32h2-devkit/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32h2/boards/esp32h2-devkit/index.html
@@ -135,7 +135,7 @@
 <li class="toctree-l3"><a class="reference internal" href="../../../esp32c6/index.html">Espressif ESP32-C6</a></li>
 <li class="toctree-l3 current"><a class="reference internal" href="../../index.html">Espressif ESP32-H2</a><ul class="current">
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-h2-toolchain">ESP32-H2 Toolchain</a></li>
-<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader-and-partition-table">Second stage bootloader and partition table</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#second-stage-bootloader">Second stage bootloader</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#building-and-flashing">Building and flashing</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#debugging-with-openocd">Debugging with OpenOCD</a></li>
 <li class="toctree-l4"><a class="reference internal" href="../../index.html#peripheral-support">Peripheral Support</a></li>
diff --git a/content/docs/latest/platforms/risc-v/esp32h2/index.html b/content/docs/latest/platforms/risc-v/esp32h2/index.html
index a49d24391..69d1190e7 100644
--- a/content/docs/latest/platforms/risc-v/esp32h2/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32h2/index.html
@@ -138,7 +138,7 @@
 <li class="toctree-l5"><a class="reference internal" href="#installing">Installing</a></li>
 </ul>
 </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="#second-stage-bootloader">Second stage bootloader</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>
@@ -240,11 +240,11 @@ check for the current compiler version being used. For instance:</p>
 FROM nuttx-toolchain-base AS nuttx-toolchain-riscv
 # Download the latest RISCV GCC toolchain prebuilt by xPack
 RUN mkdir riscv-none-elf-gcc &amp;&amp; \
-curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz&quot; \
+curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz&quot; \
 | tar -C riscv-none-elf-gcc --strip-components 1 -xz
 </pre></div>
 </div>
-<p>It uses the xPack’s prebuilt toolchain based on GCC 12.3.0.</p>
+<p>It uses the xPack’s prebuilt toolchain based on GCC 13.2.0-2.</p>
 <section id="installing">
 <h3>Installing<a class="headerlink" href="#installing" title="Permalink to this heading"></a></h3>
 <p>First, create a directory to hold the toolchain:</p>
@@ -252,7 +252,7 @@ curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/rel
 </pre></div>
 </div>
 <p>Download and extract toolchain:</p>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v12.3.0-2/xpack-riscv-none-elf-gcc-12.3.0-2-linux-x64.tar.gz&quot;</span><span class="w"> </span><span class="se">\</span>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/download/v13.2.0-2/xpack-riscv-none-elf-gcc-13.2.0-2-linux-x64.tar.gz&quot;</span><span class="w"> </span><span class="se">\</span>
 <span class="p">|</span><span class="w"> </span>tar<span class="w"> </span>-C<span class="w"> </span>/path/to/your/toolchain/riscv-none-elf-gcc<span class="w"> </span>--strip-components<span class="w"> </span><span class="m">1</span><span class="w"> </span>-xz
 </pre></div>
 </div>
@@ -263,40 +263,32 @@ curl -s -L &quot;https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/rel
 <p>You can edit your shell’s rc files if you don’t use bash.</p>
 </section>
 </section>
-<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 heading"></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-esp32h2.bin</span></code> and <code class="docutils literal notranslate"><span class="pre">partition-table-esp32h2.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>
+<section id="second-stage-bootloader">
+<h2>Second stage bootloader<a class="headerlink" href="#second-stage-bootloader" title="Permalink to this heading"></a></h2>
+<p>Nuttx can boot the ESP32-H2 directly using the so-called “Simple Boot”.
+An externally-built 2nd stage bootloader is not required in this case as all
+functions required to boot the device are built within Nuttx. Simple boot does not
+require any specific configuration (it is selectable by default if no other
+2nd stage bootloader is used). For compatibility among other SoCs and future options
+of 2nd stage bootloaders, the commands <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">bootloader</span></code> and the <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BINDIR</span></code>
+option (for the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">flash</span></code>) are kept (and ignored if Simple Boot is used).</p>
 </section>
 <section id="building-and-flashing">
 <h2>Building and flashing<a class="headerlink" href="#building-and-flashing" title="Permalink to this heading"></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
+<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-H2 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">esp32h2-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 <code class="docutils literal notranslate"><span class="pre">esptool.py</span></code> command to flash all the binaries is:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>esptool.py --chip esp32h2 --port /dev/ttyUSBXX --baud 921600 write_flash 0x0 bootloader.bin 0x8000 partition-table.bin 0x10000 nuttx.bin
+The <code class="docutils literal notranslate"><span class="pre">esptool.py</span></code> is used to flash all the binaries. 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 flash ESPTOOL_PORT=&lt;port&gt; ESPTOOL_BINDIR=./
 </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 flash ESPTOOL_PORT=&lt;port&gt; ESPTOOL_BINDIR=../esp-bins
-</pre></div>
-</div>
-<p>Where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</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-H2 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">flash</span> <span class="pre">ESPTOOL_PORT=/dev/ttyUSBXX</span></code></p>
+<p>Where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</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">./</span></code> is
+the path to the folder containing the externally-built 2nd stage bootloader for
+the ESP32-H2 as explained above.</p>
 </section>
 <section id="debugging-with-openocd">
 <h2>Debugging with OpenOCD<a class="headerlink" href="#debugging-with-openocd" title="Permalink to this heading"></a></h2>
diff --git a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-2432S028/index.html b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-2432S028/index.html
index abb219ac6..4bacaf83a 100644
--- a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-2432S028/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-2432S028/index.html
@@ -134,7 +134,7 @@
 <li class="toctree-l2"><a class="reference internal" href="../../../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="../../index.html#toolchain">Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-toolchain">ESP32 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>
diff --git a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html
index ad9efc9c9..e0ffb5155 100644
--- a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html
@@ -134,7 +134,7 @@
 <li class="toctree-l2"><a class="reference internal" href="../../../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="../../index.html#toolchain">Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-toolchain">ESP32 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>
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 a0f75ab3c..38a64e1d4 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
@@ -134,7 +134,7 @@
 <li class="toctree-l2"><a class="reference internal" href="../../../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="../../index.html#toolchain">Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-toolchain">ESP32 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>
diff --git a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-ethernet-kit/index.html b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-ethernet-kit/index.html
index c8feb27af..93adae34f 100644
--- a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-ethernet-kit/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-ethernet-kit/index.html
@@ -134,7 +134,7 @@
 <li class="toctree-l2"><a class="reference internal" href="../../../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="../../index.html#toolchain">Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-toolchain">ESP32 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>
diff --git a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-lyrat/index.html b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-lyrat/index.html
index 9bdb95582..29febdeaf 100644
--- a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-lyrat/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-lyrat/index.html
@@ -134,7 +134,7 @@
 <li class="toctree-l2"><a class="reference internal" href="../../../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="../../index.html#toolchain">Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-toolchain">ESP32 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>
diff --git a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-pico-kit/index.html b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-pico-kit/index.html
index c6c7912d8..2cf91342e 100644
--- a/content/docs/latest/platforms/xtensa/esp32/boards/esp32-pico-kit/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/boards/esp32-pico-kit/index.html
@@ -134,7 +134,7 @@
 <li class="toctree-l2"><a class="reference internal" href="../../../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="../../index.html#toolchain">Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-toolchain">ESP32 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>
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 f2e51c8f4..31a540005 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
@@ -134,7 +134,7 @@
 <li class="toctree-l2"><a class="reference internal" href="../../../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="../../index.html#toolchain">Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#esp32-toolchain">ESP32 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>
diff --git a/content/docs/latest/platforms/xtensa/esp32/index.html b/content/docs/latest/platforms/xtensa/esp32/index.html
index 11449c0b7..fc237467a 100644
--- a/content/docs/latest/platforms/xtensa/esp32/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/index.html
@@ -134,7 +134,8 @@
 <li class="toctree-l2"><a class="reference internal" href="../../x86_64/index.html">Intel 80x86_64</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-l4"><a class="reference internal" href="#toolchain">Toolchain</a><ul>
+<li class="toctree-l4"><a class="reference internal" href="#esp32-toolchain">ESP32 Toolchain</a><ul>
+<li class="toctree-l5"><a class="reference internal" href="#the-prebuilt-toolchain-recommended">The prebuilt Toolchain (Recommended)</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#building-from-source">Building from source</a></li>
 </ul>
 </li>
@@ -240,22 +241,56 @@ the system can access embedded memory via DMA.</p>
 <p>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.</p>
-<section id="toolchain">
-<h2>Toolchain<a class="headerlink" href="#toolchain" title="Permalink to this heading"></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>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
+<section id="esp32-toolchain">
+<h2>ESP32 Toolchain<a class="headerlink" href="#esp32-toolchain" title="Permalink to this heading"></a></h2>
+<p>The toolchain used to build ESP32 firmware can be either downloaded or built from the sources.
+It is <strong>highly</strong> recommended to use (download or build) the same toolchain version that is being
+used by the NuttX CI.</p>
+<p>Please refer to the Docker
+<a class="reference external" href="https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile">container</a> and
+check for the current compiler version being used. For instance:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>###############################################################################
+# Build image for tool required by ESP32 builds
+###############################################################################
+FROM nuttx-toolchain-base AS nuttx-toolchain-esp32
+# Download the latest ESP32 GCC toolchain prebuilt by Espressif
+RUN mkdir -p xtensa-esp32-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32-elf-gcc --strip-components 1 -xJ
+
+RUN mkdir -p xtensa-esp32s2-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32s2-elf-gcc --strip-components 1 -xJ
+
+RUN mkdir -p xtensa-esp32s3-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32s3-elf-gcc --strip-components 1 -xJ
 </pre></div>
 </div>
+<p>For ESP32, the toolchain version is based on GGC 12.2.0 (<code class="docutils literal notranslate"><span class="pre">xtensa-esp32-elf-12.2.0_20230208</span></code>)</p>
+<section id="the-prebuilt-toolchain-recommended">
+<h3>The prebuilt Toolchain (Recommended)<a class="headerlink" href="#the-prebuilt-toolchain-recommended" title="Permalink to this heading"></a></h3>
+<p>First, create a directory to hold the toolchain:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>mkdir<span class="w"> </span>-p<span class="w"> </span>/path/to/your/toolchain/xtensa-esp32-elf-gcc
+</pre></div>
+</div>
+<p>Download and extract toolchain:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot;</span><span class="w"> </span><span class="se">\</span>
+<span class="p">|</span><span class="w"> </span>tar<span class="w"> </span>-C<span class="w"> </span>xtensa-esp32-elf-gcc<span class="w"> </span>--strip-components<span class="w"> </span><span class="m">1</span><span class="w"> </span>-xJ
+</pre></div>
+</div>
+<p>Add the toolchain to your <cite>PATH</cite>:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span><span class="nb">echo</span><span class="w"> </span><span class="s2">&quot;export PATH=/path/to/your/toolchain/xtensa-esp32-elf-gcc/bin:</span><span class="nv">$PATH</span><span class="s2">&quot;</span><span class="w"> </span>&gt;&gt;<span class="w"> </span>~/.bashrc
+</pre></div>
+</div>
+<p>You can edit your shell’s rc files if you don’t use bash.</p>
+</section>
 <section id="building-from-source">
 <h3>Building from source<a class="headerlink" href="#building-from-source" title="Permalink to this heading"></a></h3>
 <p>You can also build the toolchain yourself. The steps to
 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<span class="w"> </span>clone<span class="w"> </span>https://github.com/espressif/crosstool-NG.git
 <span class="gp">$ </span><span class="nb">cd</span><span class="w"> </span>crosstool-NG
-<span class="gp">$ </span>git<span class="w"> </span>checkout<span class="w"> </span>esp-2021r1
 <span class="gp">$ </span>git<span class="w"> </span>submodule<span class="w"> </span>update<span class="w"> </span>--init
 
 <span class="gp">$ </span>./bootstrap<span class="w"> </span><span class="o">&amp;&amp;</span><span class="w"> </span>./configure<span class="w"> </span>--enable-local<span class="w"> </span><span class="o">&amp;&amp;</span><span class="w"> </span>make
diff --git a/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-kaluga-1/index.html b/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-kaluga-1/index.html
index a1f258250..4c2f1c2a3 100644
--- a/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-kaluga-1/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-kaluga-1/index.html
@@ -135,7 +135,7 @@
 <li class="toctree-l2 current"><a class="reference internal" href="../../../index.html">Xtensa</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-S2</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#esp32-s2-toolchain">ESP32-S2 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>
diff --git a/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-saola-1/index.html b/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-saola-1/index.html
index 391507fc6..a99d9ba4f 100644
--- a/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-saola-1/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s2/boards/esp32s2-saola-1/index.html
@@ -135,7 +135,7 @@
 <li class="toctree-l2 current"><a class="reference internal" href="../../../index.html">Xtensa</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-S2</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#esp32-s2-toolchain">ESP32-S2 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>
diff --git a/content/docs/latest/platforms/xtensa/esp32s2/index.html b/content/docs/latest/platforms/xtensa/esp32s2/index.html
index 42d52af63..21a4c3b53 100644
--- a/content/docs/latest/platforms/xtensa/esp32s2/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s2/index.html
@@ -135,7 +135,8 @@
 <li class="toctree-l2 current"><a class="reference internal" href="../index.html">Xtensa</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="current reference internal" href="#">Espressif ESP32-S2</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#toolchain">Toolchain</a><ul>
+<li class="toctree-l4"><a class="reference internal" href="#esp32-s2-toolchain">ESP32-S2 Toolchain</a><ul>
+<li class="toctree-l5"><a class="reference internal" href="#the-prebuilt-toolchain-recommended">The prebuilt Toolchain (Recommended)</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#building-from-source">Building from source</a></li>
 </ul>
 </li>
@@ -220,36 +221,70 @@ architecture Xtensa LX7 CPU and with on-chip support for Wi-Fi.</p>
 <p>All embedded memory, external memory and peripherals are located on the
 data bus and/or the instruction bus of the CPU. Multiple peripherals in
 the system can access embedded memory via DMA.</p>
-<section id="toolchain">
-<h2>Toolchain<a class="headerlink" href="#toolchain" title="Permalink to this heading"></a></h2>
-<p>You can use the prebuilt <a class="reference external" href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/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/esp32s2/api-guides/tools/idf-tools.html#openocd-esp32">OpenOCD</a>
-for ESP32-S2 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
+<section id="esp32-s2-toolchain">
+<h2>ESP32-S2 Toolchain<a class="headerlink" href="#esp32-s2-toolchain" title="Permalink to this heading"></a></h2>
+<p>The toolchain used to build ESP32-S2 firmware can be either downloaded or built from the sources.
+It is <strong>highly</strong> recommended to use (download or build) the same toolchain version that is being
+used by the NuttX CI.</p>
+<p>Please refer to the Docker
+<a class="reference external" href="https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile">container</a> and
+check for the current compiler version being used. For instance:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>###############################################################################
+# Build image for tool required by ESP32 builds
+###############################################################################
+FROM nuttx-toolchain-base AS nuttx-toolchain-esp32
+# Download the latest ESP32 GCC toolchain prebuilt by Espressif
+RUN mkdir -p xtensa-esp32-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32-elf-gcc --strip-components 1 -xJ
+
+RUN mkdir -p xtensa-esp32s2-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32s2-elf-gcc --strip-components 1 -xJ
+
+RUN mkdir -p xtensa-esp32s3-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32s3-elf-gcc --strip-components 1 -xJ
 </pre></div>
 </div>
+<p>For ESP32-S2, the toolchain version is based on GGC 12.2.0 (<code class="docutils literal notranslate"><span class="pre">xtensa-esp32s2-elf-12.2.0_20230208</span></code>)</p>
+<section id="the-prebuilt-toolchain-recommended">
+<h3>The prebuilt Toolchain (Recommended)<a class="headerlink" href="#the-prebuilt-toolchain-recommended" title="Permalink to this heading"></a></h3>
+<p>First, create a directory to hold the toolchain:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>mkdir<span class="w"> </span>-p<span class="w"> </span>/path/to/your/toolchain/xtensa-esp32s2-elf-gcc
+</pre></div>
+</div>
+<p>Download and extract toolchain:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot;</span><span class="w"> </span><span class="se">\</span>
+<span class="p">|</span><span class="w"> </span>tar<span class="w"> </span>-C<span class="w"> </span>xtensa-esp32s2-elf-gcc<span class="w"> </span>--strip-components<span class="w"> </span><span class="m">1</span><span class="w"> </span>-xJ
+</pre></div>
+</div>
+<p>Add the toolchain to your <cite>PATH</cite>:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span><span class="nb">echo</span><span class="w"> </span><span class="s2">&quot;export PATH=/path/to/your/toolchain/xtensa-esp32s2-elf-gcc/bin:</span><span class="nv">$PATH</span><span class="s2">&quot;</span><span class="w"> </span>&gt;&gt;<span class="w"> </span>~/.bashrc
+</pre></div>
+</div>
+<p>You can edit your shell’s rc files if you don’t use bash.</p>
+</section>
 <section id="building-from-source">
 <h3>Building from source<a class="headerlink" href="#building-from-source" title="Permalink to this heading"></a></h3>
 <p>You can also build the toolchain yourself. The steps to
 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<span class="w"> </span>clone<span class="w"> </span>https://github.com/espressif/crosstool-NG.git
 <span class="gp">$ </span><span class="nb">cd</span><span class="w"> </span>crosstool-NG
-<span class="gp">$ </span>git<span class="w"> </span>checkout<span class="w"> </span>esp-2021r1
 <span class="gp">$ </span>git<span class="w"> </span>submodule<span class="w"> </span>update<span class="w"> </span>--init
 
 <span class="gp">$ </span>./bootstrap<span class="w"> </span><span class="o">&amp;&amp;</span><span class="w"> </span>./configure<span class="w"> </span>--enable-local<span class="w"> </span><span class="o">&amp;&amp;</span><span class="w"> </span>make
 
-<span class="gp">$ </span>./ct-ng<span class="w"> </span>xtensa-esp32-elf
+<span class="gp">$ </span>./ct-ng<span class="w"> </span>xtensa-esp32s2-elf
 <span class="gp">$ </span>./ct-ng<span class="w"> </span>build
 
-<span class="gp">$ </span>chmod<span class="w"> </span>-R<span class="w"> </span>u+w<span class="w"> </span>builds/xtensa-esp32-elf
+<span class="gp">$ </span>chmod<span class="w"> </span>-R<span class="w"> </span>u+w<span class="w"> </span>builds/xtensa-esp32s2-elf
 
 <span class="gp">$ </span><span class="nb">export</span><span class="w"> </span><span class="nv">PATH</span><span class="o">=</span><span class="s2">&quot;crosstool-NG/builds/xtensa-esp32-elf/bin:</span><span class="nv">$PATH</span><span class="s2">&quot;</span>
 </pre></div>
 </div>
-<p>Alternatively, you may follow the steps in
-<a class="reference external" href="https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/get-started/linux-macos-setup.html">ESP-IDF documentation</a>.</p>
+<p>These steps are given in the setup guide in
+<a class="reference external" href="https://docs.espressif.com/projects/esp-idf/en/latest/get-started/linux-setup-scratch.html">ESP-IDF documentation</a>.</p>
 </section>
 </section>
 <section id="flashing">
diff --git a/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.html b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.html
index 1502e3d4d..1c289455a 100644
--- a/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-devkit/index.html
@@ -136,10 +136,9 @@
 <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="../../../esp32s2/index.html">Espressif ESP32-S2</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#esp32-s3-toolchain">ESP32-S3 Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#building-and-flashing-nuttx">Building and flashing NuttX</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 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="#">ESP32S3-DevKit</a></li>
 <li class="toctree-l5"><a class="reference internal" href="../esp32s3-eye/index.html">ESP32-S3-EYE</a></li>
diff --git a/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html
index a0a2af716..5a1a73db7 100644
--- a/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s3/boards/esp32s3-eye/index.html
@@ -136,10 +136,9 @@
 <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="../../../esp32s2/index.html">Espressif ESP32-S2</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#esp32-s3-toolchain">ESP32-S3 Toolchain</a></li>
+<li class="toctree-l4"><a class="reference internal" href="../../index.html#building-and-flashing-nuttx">Building and flashing NuttX</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 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="../esp32s3-devkit/index.html">ESP32S3-DevKit</a></li>
 <li class="toctree-l5 current"><a class="current reference internal" href="#">ESP32-S3-EYE</a></li>
diff --git a/content/docs/latest/platforms/xtensa/esp32s3/index.html b/content/docs/latest/platforms/xtensa/esp32s3/index.html
index 89b3b59ff..80a60dcb1 100644
--- a/content/docs/latest/platforms/xtensa/esp32s3/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32s3/index.html
@@ -136,12 +136,14 @@
 <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="../esp32s2/index.html">Espressif ESP32-S2</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-l4"><a class="reference internal" href="#esp32-s3-toolchain">ESP32-S3 Toolchain</a><ul>
+<li class="toctree-l5"><a class="reference internal" href="#the-prebuilt-toolchain-recommended">The prebuilt Toolchain (Recommended)</a></li>
 <li class="toctree-l5"><a class="reference internal" href="#building-from-source">Building from source</a></li>
 </ul>
 </li>
-<li class="toctree-l4"><a class="reference internal" href="#flashing">Flashing</a><ul>
+<li class="toctree-l4"><a class="reference internal" href="#building-and-flashing-nuttx">Building and flashing NuttX</a><ul>
 <li class="toctree-l5"><a class="reference internal" href="#bootloader-and-partitions">Bootloader and partitions</a></li>
+<li class="toctree-l5"><a class="reference internal" href="#building-and-flashing">Building and Flashing</a></li>
 </ul>
 </li>
 <li class="toctree-l4"><a class="reference internal" href="#peripheral-support">Peripheral Support</a><ul>
@@ -149,15 +151,6 @@
 <li class="toctree-l5"><a class="reference internal" href="#wi-fi-softap">Wi-Fi SoftAP</a></li>
 </ul>
 </li>
-<li class="toctree-l4"><a class="reference internal" href="#memory-map">Memory Map</a><ul>
-<li class="toctree-l5"><a class="reference internal" href="#address-mapping">Address Mapping</a></li>
-<li class="toctree-l5"><a class="reference internal" href="#embedded-memory">Embedded Memory</a></li>
-<li class="toctree-l5"><a class="reference internal" href="#boundary-address-embedded">Boundary Address (Embedded)</a></li>
-<li class="toctree-l5"><a class="reference internal" href="#external-memory">External Memory</a></li>
-<li class="toctree-l5"><a class="reference internal" href="#boundary-address-external">Boundary Address (External)</a></li>
-<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="#supported-boards">Supported Boards</a><ul>
 <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>
@@ -220,15 +213,50 @@ the system can access embedded memory via DMA.</p>
 <p>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.</p>
-<section id="toolchain">
-<h2>Toolchain<a class="headerlink" href="#toolchain" title="Permalink to this heading"></a></h2>
-<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
+<section id="esp32-s3-toolchain">
+<h2>ESP32-S3 Toolchain<a class="headerlink" href="#esp32-s3-toolchain" title="Permalink to this heading"></a></h2>
+<p>The toolchain used to build ESP32-S3 firmware can be either downloaded or built from the sources.
+It is <strong>highly</strong> recommended to use (download or build) the same toolchain version that is being
+used by the NuttX CI.</p>
+<p>Please refer to the Docker
+<a class="reference external" href="https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile">container</a> and
+check for the current compiler version being used. For instance:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>###############################################################################
+# Build image for tool required by ESP32 builds
+###############################################################################
+FROM nuttx-toolchain-base AS nuttx-toolchain-esp32
+# Download the latest ESP32 GCC toolchain prebuilt by Espressif
+RUN mkdir -p xtensa-esp32-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32-elf-gcc --strip-components 1 -xJ
+
+RUN mkdir -p xtensa-esp32s2-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s2-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32s2-elf-gcc --strip-components 1 -xJ
+
+RUN mkdir -p xtensa-esp32s3-elf-gcc &amp;&amp; \
+  curl -s -L &quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot; \
+  | tar -C xtensa-esp32s3-elf-gcc --strip-components 1 -xJ
+</pre></div>
+</div>
+<p>For ESP32-S3, the toolchain version is based on GGC 12.2.0 (<code class="docutils literal notranslate"><span class="pre">xtensa-esp32s3-elf-12.2.0_20230208</span></code>)</p>
+<section id="the-prebuilt-toolchain-recommended">
+<h3>The prebuilt Toolchain (Recommended)<a class="headerlink" href="#the-prebuilt-toolchain-recommended" title="Permalink to this heading"></a></h3>
+<p>First, create a directory to hold the toolchain:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>mkdir<span class="w"> </span>-p<span class="w"> </span>/path/to/your/toolchain/xtensa-esp32s3-elf-gcc
 </pre></div>
 </div>
+<p>Download and extract toolchain:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>curl<span class="w"> </span>-s<span class="w"> </span>-L<span class="w"> </span><span class="s2">&quot;https://github.com/espressif/crosstool-NG/releases/download/esp-12.2.0_20230208/xtensa-esp32s3-elf-12.2.0_20230208-x86_64-linux-gnu.tar.xz&quot;</span><span class="w"> </span><span class="se">\</span>
+<span class="p">|</span><span class="w"> </span>tar<span class="w"> </span>-C<span class="w"> </span>xtensa-esp32s3-elf-gcc<span class="w"> </span>--strip-components<span class="w"> </span><span class="m">1</span><span class="w"> </span>-xJ
+</pre></div>
+</div>
+<p>Add the toolchain to your <cite>PATH</cite>:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span><span class="nb">echo</span><span class="w"> </span><span class="s2">&quot;export PATH=/path/to/your/toolchain/xtensa-esp32s3-elf-gcc/bin:</span><span class="nv">$PATH</span><span class="s2">&quot;</span><span class="w"> </span>&gt;&gt;<span class="w"> </span>~/.bashrc
+</pre></div>
+</div>
+<p>You can edit your shell’s rc files if you don’t use bash.</p>
+</section>
 <section id="building-from-source">
 <h3>Building from source<a class="headerlink" href="#building-from-source" title="Permalink to this heading"></a></h3>
 <p>You can also build the toolchain yourself. The steps to
@@ -251,32 +279,50 @@ build the toolchain with crosstool-NG on Linux are as follows</p>
 <a class="reference external" href="https://docs.espressif.com/projects/esp-idf/en/latest/get-started/linux-setup-scratch.html">ESP-IDF documentation</a>.</p>
 </section>
 </section>
-<section id="flashing">
-<h2>Flashing<a class="headerlink" href="#flashing" title="Permalink to this heading"></a></h2>
-<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=&lt;port&gt;
-</pre></div>
-</div>
-<p>where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</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>
+<section id="building-and-flashing-nuttx">
+<h2>Building and flashing NuttX<a class="headerlink" href="#building-and-flashing-nuttx" title="Permalink to this heading"></a></h2>
 <section id="bootloader-and-partitions">
 <h3>Bootloader and partitions<a class="headerlink" href="#bootloader-and-partitions" title="Permalink to this heading"></a></h3>
-<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<span class="w"> </span>flash<span class="w"> </span><span class="nv">ESPTOOL_PORT</span><span class="o">=</span>&lt;port&gt;<span class="w"> </span><span class="nv">ESPTOOL_BINDIR</span><span class="o">=</span>&lt;dir&gt;
+<p>Nuttx can boot the ESP32-S3 directly using the so-called “Simple Boot”. An externally-built
+2nd stage bootloader is not required in this case as all functions required to boot the device
+are built within Nuttx. Simple boot does not require any specific configuration (it is selectable
+by default if no other 2nd stage bootloader is used).</p>
+<p>If other features are required, an externally-built 2nd stage bootloader is needed. The bootloader
+is built using the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">bootloader</span></code> command. This command generates the firmware in the
+<code class="docutils literal notranslate"><span class="pre">nuttx</span></code> folder. The <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BINDIR</span></code> is used in the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">flash</span></code> command to specify the path
+to the bootloader. For compatibility among other SoCs and future options of 2nd stage bootloaders,
+the commands <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">bootloader</span></code> and the <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BINDIR</span></code> option (for the <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">flash</span></code>) can be
+used even if no externally-built 2nd stage bootloader is being built (they will be ignored if
+Simple Boot is used, for instance):</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>$ make bootloader
 </pre></div>
 </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>
-<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>esptool.py<span class="w"> </span>erase_flash
+<p>It is recommended that if this is the first time you are using the board with NuttX to
+perform a complete SPI FLASH erase.</p>
+<blockquote>
+<div><div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>esptool.py<span class="w"> </span>erase_flash
 </pre></div>
 </div>
+</div></blockquote>
+</div>
+</section>
+<section id="building-and-flashing">
+<h3>Building and Flashing<a class="headerlink" href="#building-and-flashing" title="Permalink to this heading"></a></h3>
+<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-S3 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>It’s a two-step process where the first converts the ELF file into an ESP32-S3 compatible binary
+and the second flashes it to the board. These steps are included in the build system and it is
+possible to build and flash the NuttX firmware simply by running:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>$ make flash ESPTOOL_PORT=&lt;port&gt; ESPTOOL_BINDIR=./
+</pre></div>
 </div>
+<p>where <code class="docutils literal notranslate"><span class="pre">&lt;port&gt;</span></code> is typically <code class="docutils literal notranslate"><span class="pre">/dev/ttyUSB0</span></code> or similar. <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BINDIR=./</span></code> is the path of the
+externally-built 2nd stage bootloader and the partition table (if applicable): when built using the
+<code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">bootloader</span></code>, these files are placed into <code class="docutils literal notranslate"><span class="pre">nuttx</span></code> folder. <code class="docutils literal notranslate"><span class="pre">ESPTOOL_BAUD</span></code> is able to
+change the flash baudrate if desired.</p>
 </section>
 </section>
 <section id="peripheral-support">
@@ -466,118 +512,6 @@ for more information.</p>
 <p>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>
 </section>
 </section>
-<section id="memory-map">
-<h2>Memory Map<a class="headerlink" href="#memory-map" title="Permalink to this heading"></a></h2>
-<section id="address-mapping">
-<h3>Address Mapping<a class="headerlink" href="#address-mapping" title="Permalink to this heading"></a></h3>
-<table class="docutils align-default">
-<thead>
-<tr class="row-odd"><th class="head"><p>BUS TYPE</p></th>
-<th class="head"><p>START</p></th>
-<th class="head"><p>LAST</p></th>
-<th class="head"><p>DESCRIPTION</p></th>
-<th class="head"><p>NOTES</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="row-even"><td><p>To be added</p></td>
-<td></td>
-<td></td>
-<td></td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</section>
-<section id="embedded-memory">
-<h3>Embedded Memory<a class="headerlink" href="#embedded-memory" title="Permalink to this heading"></a></h3>
-<table class="docutils align-default">
-<thead>
-<tr class="row-odd"><th class="head"><p>BUS TYPE</p></th>
-<th class="head"><p>START</p></th>
-<th class="head"><p>LAST</p></th>
-<th class="head"><p>DESCRIPTION</p></th>
-<th class="head"><p>NOTES</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="row-even"><td><p>To be added</p></td>
-<td></td>
-<td></td>
-<td></td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</section>
-<section id="boundary-address-embedded">
-<h3>Boundary Address (Embedded)<a class="headerlink" href="#boundary-address-embedded" title="Permalink to this heading"></a></h3>
-<table class="docutils align-default">
-<thead>
-<tr class="row-odd"><th class="head"><p>BUS TYPE</p></th>
-<th class="head"><p>START</p></th>
-<th class="head"><p>LAST</p></th>
-<th class="head"><p>DESCRIPTION</p></th>
-<th class="head"><p>NOTES</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="row-even"><td><p>To be added</p></td>
-<td></td>
-<td></td>
-<td></td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</section>
-<section id="external-memory">
-<h3>External Memory<a class="headerlink" href="#external-memory" title="Permalink to this heading"></a></h3>
-<table class="docutils align-default">
-<thead>
-<tr class="row-odd"><th class="head"><p>BUS TYPE</p></th>
-<th class="head"><p>START</p></th>
-<th class="head"><p>LAST</p></th>
-<th class="head"><p>DESCRIPTION</p></th>
-<th class="head"><p>NOTES</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="row-even"><td><p>To be added</p></td>
-<td></td>
-<td></td>
-<td></td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</section>
-<section id="boundary-address-external">
-<h3>Boundary Address (External)<a class="headerlink" href="#boundary-address-external" title="Permalink to this heading"></a></h3>
-<p>To be added</p>
-</section>
-<section id="linker-segments">
-<h3>Linker Segments<a class="headerlink" href="#linker-segments" title="Permalink to this heading"></a></h3>
-<table class="docutils align-default">
-<thead>
-<tr class="row-odd"><th class="head"><p>DESCRIPTION</p></th>
-<th class="head"><p>START</p></th>
-<th class="head"><p>END</p></th>
-<th class="head"><p>ATTR</p></th>
-<th class="head"><p>LINKER SEGMENT NAME</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="row-even"><td><p>To be added</p></td>
-<td></td>
-<td></td>
-<td></td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</section>
-</section>
 <section id="supported-boards">
 <h2>Supported Boards<a class="headerlink" href="#supported-boards" title="Permalink to this heading"></a></h2>
 <div class="toctree-wrapper compound">
diff --git a/content/docs/latest/searchindex.js b/content/docs/latest/searchindex.js
index 4d263feca..54de049f0 100644
--- a/content/docs/latest/searchindex.js
+++ b/content/docs/latest/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/cachespeed/index", "applications/benchmarks/coremark-pro/index", "applications/benchmarks/coremark/index", "applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index", "applications/benchmarks/index", "applications/benchmarks/iozone/index", "applications/bench [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/cachespeed/index", "applications/benchmarks/coremark-pro/index", "applications/benchmarks/coremark/index", "applications/benchmarks/dhrystone/index", "applications/benchmarks/fio/index", "applications/benchmarks/index", "applications/benchmarks/iozone/index", "applications/bench [...]
\ No newline at end of file
diff --git a/content/feed.xml b/content/feed.xml
index 16e9cfc55..9d6a40962 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>Mon, 22 Apr 2024 00:18:38 +0000</pubDate>
-    <lastBuildDate>Mon, 22 Apr 2024 00:18:38 +0000</lastBuildDate>
+    <pubDate>Tue, 23 Apr 2024 00:18:52 +0000</pubDate>
+    <lastBuildDate>Tue, 23 Apr 2024 00:18:52 +0000</lastBuildDate>
     <generator>Jekyll v4.3.2</generator>
     
       <item>