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/01/22 00:19:26 UTC
(nuttx-website) branch asf-site updated: Publishing web: b5839eef93f7280871281371cee9248b373c78cd docs: 282feec9a3560304b1248e6df8063ea510909fab
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 7d58221d Publishing web: b5839eef93f7280871281371cee9248b373c78cd docs: 282feec9a3560304b1248e6df8063ea510909fab
7d58221d is described below
commit 7d58221db83790be82914bc0029ca192daa10b03
Author: Alin Jerpelea <al...@sony.com>
AuthorDate: Mon Jan 22 00:14:35 2024 +0000
Publishing web: b5839eef93f7280871281371cee9248b373c78cd docs: 282feec9a3560304b1248e6df8063ea510909fab
---
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 +-
.../_sources/applications/nsh/config.rst.txt | 32 +-
.../_sources/applications/nsh/installation.rst.txt | 174 ---------
.../latest/_sources/applications/nsh/nsh.rst.txt | 120 -------
.../docs/latest/_sources/guides/etcromfs.rst.txt | 177 ++++++++++
content/docs/latest/_sources/guides/index.rst.txt | 1 +
.../docs/latest/_sources/guides/pysimcoder.rst.txt | 2 +-
.../platforms/sim/sim/boards/sim/index.rst.txt | 2 +-
.../x86_64/qemu/boards/qemu-intel64/index.rst.txt | 163 ++++++++-
content/docs/latest/applications/nsh/config.html | 55 +--
content/docs/latest/applications/nsh/index.html | 6 +-
.../docs/latest/applications/nsh/installation.html | 180 +---------
content/docs/latest/applications/nsh/nsh.html | 129 -------
content/docs/latest/glossary.html | 4 +-
content/docs/latest/guides/automounter.html | 1 +
content/docs/latest/guides/citests.html | 1 +
content/docs/latest/guides/coredump.html | 1 +
content/docs/latest/guides/cortexmhardfaults.html | 1 +
content/docs/latest/guides/cpp_cmake.html | 1 +
content/docs/latest/guides/customapps.html | 1 +
content/docs/latest/guides/customboards.html | 1 +
content/docs/latest/guides/drivers.html | 1 +
content/docs/latest/guides/etcromfs.html | 389 +++++++++++++++++++++
content/docs/latest/guides/gdbwithpython.html | 1 +
content/docs/latest/guides/index.html | 8 +
content/docs/latest/guides/minidumpserver.html | 1 +
content/docs/latest/guides/nestedinterrupts.html | 1 +
content/docs/latest/guides/nfs.html | 1 +
content/docs/latest/guides/ofloader.html | 1 +
content/docs/latest/guides/pysimcoder.html | 3 +-
content/docs/latest/guides/qemugdb.html | 1 +
content/docs/latest/guides/rndis.html | 1 +
content/docs/latest/guides/simulator.html | 1 +
content/docs/latest/guides/stackrecord.html | 5 +-
content/docs/latest/guides/stm32ccm.html | 1 +
content/docs/latest/guides/stm32nullpointer.html | 1 +
content/docs/latest/guides/tasktrace.html | 1 +
content/docs/latest/guides/tasktraceinternal.html | 1 +
content/docs/latest/guides/tasktraceuser.html | 1 +
content/docs/latest/guides/testingtcpip.html | 1 +
content/docs/latest/guides/usbtrace.html | 1 +
.../docs/latest/guides/zerolatencyinterrupts.html | 1 +
content/docs/latest/index.html | 3 +-
content/docs/latest/objects.inv | Bin 109863 -> 110116 bytes
.../renesas/rx65n/boards/rx65n-grrose/index.html | 2 +-
.../renesas/rx65n/boards/rx65n-rsk2mb/index.html | 2 +-
.../esp32c3/boards/esp32c3-devkit/index.html | 2 +-
.../latest/platforms/sim/sim/boards/sim/index.html | 4 +-
.../x86_64/qemu/boards/qemu-intel64/index.html | 328 ++++++++---------
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 +-
72 files changed, 959 insertions(+), 906 deletions(-)
diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index 8de1bc89..002f96fc 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: 21 January 24 at 00:11</p>
+<p>Last Updated: 22 January 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 e618a9d8..efbf43bb 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 1de6e581..cbe57c60 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -153,7 +153,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: 21 January 24 at 00:11</p>
+<p>Last Updated: 22 January 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.1/searchindex.js b/content/docs/10.0.1/searchindex.js
index a80f2513..cb9e1fe9 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 0796f313..d05354e2 100644
--- a/content/docs/10.1.0/index.html
+++ b/content/docs/10.1.0/index.html
@@ -152,7 +152,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: 21 January 24 at 00:11</p>
+<p>Last Updated: 22 January 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.1.0/searchindex.js b/content/docs/10.1.0/searchindex.js
index 44b1099d..60dc2a55 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 c4b5ad5c..d34fddaf 100644
--- a/content/docs/10.2.0/index.html
+++ b/content/docs/10.2.0/index.html
@@ -153,7 +153,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: 21 January 24 at 00:11</p>
+<p>Last Updated: 22 January 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 eabfffaf..7c7caa05 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 c25645de..d34fddaf 100644
--- a/content/docs/10.3.0/index.html
+++ b/content/docs/10.3.0/index.html
@@ -153,7 +153,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: 21 January 24 at 00:12</p>
+<p>Last Updated: 22 January 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 d943db99..f0c4faf2 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 c25645de..d34fddaf 100644
--- a/content/docs/11.0.0/index.html
+++ b/content/docs/11.0.0/index.html
@@ -153,7 +153,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: 21 January 24 at 00:12</p>
+<p>Last Updated: 22 January 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 2fd6b509..798e8d70 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 6bb1a122..6f2be740 100644
--- a/content/docs/12.0.0/index.html
+++ b/content/docs/12.0.0/index.html
@@ -153,7 +153,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: 21 January 24 at 00:12</p>
+<p>Last Updated: 22 January 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/12.0.0/searchindex.js b/content/docs/12.0.0/searchindex.js
index 0c635ab7..043b8e18 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 8143bd4c..170947cc 100644
--- a/content/docs/12.1.0/index.html
+++ b/content/docs/12.1.0/index.html
@@ -153,7 +153,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: 21 January 24 at 00:12</p>
+<p>Last Updated: 22 January 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/12.1.0/searchindex.js b/content/docs/12.1.0/searchindex.js
index 857f880e..50fb00dc 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 d474f141..a0a377c3 100644
--- a/content/docs/12.2.0/index.html
+++ b/content/docs/12.2.0/index.html
@@ -156,7 +156,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: 21 January 24 at 00:12</p>
+<p>Last Updated: 22 January 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 ea76d871..d7698599 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 08ec01a5..a0a377c3 100644
--- a/content/docs/12.2.1/index.html
+++ b/content/docs/12.2.1/index.html
@@ -156,7 +156,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: 21 January 24 at 00:13</p>
+<p>Last Updated: 22 January 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 4a3e8b27..f6b58a25 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 38b28350..d315b03b 100644
--- a/content/docs/12.3.0/index.html
+++ b/content/docs/12.3.0/index.html
@@ -156,7 +156,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: 21 January 24 at 00:13</p>
+<p>Last Updated: 22 January 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 df17f8dc..b2fcbd5c 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/latest/_sources/applications/nsh/config.rst.txt b/content/docs/latest/_sources/applications/nsh/config.rst.txt
index b4dfa9cd..93a0b195 100644
--- a/content/docs/latest/_sources/applications/nsh/config.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/config.rst.txt
@@ -299,12 +299,6 @@ Configuration Description
registered as ``/dev/mmcsd``\ *N* where *N* is the minor number.
Default is zero.
- ``CONFIG_NSH_ROMFSETC`` Mount a ROMFS file system at ``/etc`` and provide a system init
- script at ``/etc/init.d.rc.sysinit`` and a startup script at
- ``/etc/init.d/rcS``.
- The default system init script will mount a FAT FS RAMDISK at
- ``/tmp`` but the logic is `easily extensible <#startupscript>`__.
-
``CONFIG_NSH_CONSOLE`` If ``CONFIG_NSH_CONSOLE`` is set to *y*, then a serial console
front-end is selected.
@@ -451,44 +445,20 @@ Configuration Description
is indicated.
============================================== ============================================================
-If ``CONFIG_NSH_ROMFSETC`` is selected, then the following additional
+If ``CONFIG_ETC_ROMFS`` is selected, then the following additional
configuration setting apply:
============================== ==============================================================
Configuration Description
============================== ==============================================================
-``CONFIG_NSH_ARCHROMFS`` May be defined to specify an alternative ROMFS image
- that can be found at ``boards/<arch>/<chip>/<board>/include/nsh_romfsimg.h``.
-``CONFIG_NSH_ROMFSMOUNTPT`` The default mountpoint for the ROMFS volume is ``"/etc"``,
- but that can be changed with this setting. This must be a
- absolute path beginning with '``/``' and enclosed in quotes.
``CONFIG_NSH_SYSINITSCRIPT`` This is the relative path to the system init script within the
mountpoint. The default is ``"init.d/rc.sysinit"``. This is a relative
path and must not start with '``/``' but must be enclosed in quotes.
``CONFIG_NSH_INITSCRIPT`` This is the relative path to the startup script within the
mountpoint. The default is ``"init.d/rcS"``. This is a relative
path and must not start with '``/``' but must be enclosed in quotes.
-``CONFIG_NSH_ROMFSDEVNO`` This is the minor number of the ROMFS block device.
- The default is '``0``' corresponding to ``/dev/ram0``.
-``CONFIG_NSH_ROMFSSECTSIZE`` This is the sector size to use with the ROMFS volume. Since the
- default volume is very small, this defaults to 64 but should
- be increased if the ROMFS volume were to be become large.
- Any value selected must be a power of 2.
============================== ==============================================================
-When the default ``rc.sysinit`` file used when ``CONFIG_NSH_ROMFSETC`` is
-selected, it will mount a FAT FS under ``/tmp``. The following
-selections describe that FAT FS.
-
-============================== =======================================================
-Configuration Description
-============================== =======================================================
-``CONFIG_NSH_FATDEVNO`` This is the minor number of the FAT FS block device.
- The default is '``1``' corresponding to ``/dev/ram1``.
-``CONFIG_NSH_FATSECTSIZE`` This is the sector size use with the FAT FS. Default is 512.
-============================== =======================================================
-
-
Common Problems
===============
diff --git a/content/docs/latest/_sources/applications/nsh/installation.rst.txt b/content/docs/latest/_sources/applications/nsh/installation.rst.txt
index 4633460f..a88a7275 100644
--- a/content/docs/latest/_sources/applications/nsh/installation.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/installation.rst.txt
@@ -27,177 +27,3 @@ increasing difficulty:
create the start-up script. It is sufficiently complex that is
deserves its own paragraph
-NuttShell Start up Scripts
---------------------------
-
-First of all you should look at `NSH Start-Up Script <#startupscript>`__
-paragraph. Most everything you need to know can be found there. That
-information will be repeated and extended here for completeness.
-
-**NSH Start-Up Script**. NSH supports options to provide a start up
-script for NSH. The start-up script contains any command support by NSH
-(i.e., that you see when you enter 'nsh> help'). In general this
-capability is enabled with ``CONFIG_NSH_ROMFSETC=y``, but has several
-other related configuration options as described with the `NSH-specific
-configuration settings <#nshconfiguration>`__ paragraph. This capability
-also depends on:
-
- - ``CONFIG_DISABLE_MOUNTPOINT=n``. If mount point support is disabled,
- then you cannot mount *any* file systems.
-
- - ``CONFIG_FS_ROMFS`` enabled. This option enables ROMFS file system
- support.
-
-**Default Start-Up Behavior**. The implementation that is provided is
-intended to provide great flexibility for the use of Start-Up files.
-This paragraph will discuss the general behavior when all of the
-configuration options are set to the default values.
-
-In this default case, enabling ``CONFIG_NSH_ROMFSETC`` will cause NSH to
-behave as follows at NSH start-up time:
-
- - NSH will create a read-only RAM disk (a ROM disk), containing a tiny
- ROMFS file system containing the following::
-
- `--init.d/
- `-- rcS
- `-- rc.sysinit
-
- Where ``rcS`` is the NSH start-up script.
- Where ``rc.sysinit`` is the NSH system-init script.
-
- - NSH will then mount the ROMFS file system at ``/etc``, resulting in::
-
- |--dev/
- | `-- ram0
- `--etc/
- `--init.d/
- `-- rcS
- `-- rc.sysinit
-
- - By default, the contents of ``rc.sysinit`` script are::
-
- # Create a RAMDISK and mount it at /tmp
-
- mkrd -m 1 -s 512 1024
- mkfatfs /dev/ram1
- mount -t vfat /dev/ram1 /tmp
-
- - NSH will execute the script at ``/etc/init.d/rc.sysinit`` at system
- init (before the first NSH prompt). After execution of the script,
- the root FS will look like::
-
- |--dev/
- | |-- ram0
- | `-- ram1
- |--etc/
- | `--init.d/
- | `-- rcS
- | `-- rc.sysinit
- `--tmp/
-
-**Example Configurations**. Here are some configurations that have
-``CONFIG_NSH_ROMFSETC=y`` in the NuttX configuration file. They might
-provide useful examples:
-
- - ``boards/arm/stm32/hymini-stm32v/nsh2``
- - ``boards/arm/dm320/ntosd-dm320/nsh``
- - ``boards/sim/sim/sim/nsh``
- - ``boards/sim/sim/sim/nsh2``
- - ``boards/sim/sim/sim/nx``
- - ``boards/sim/sim/sim/nx11``
- - ``boards/sim/sim/sim/touchscreen``
-
-In most of these cases, the configuration sets up the *default*
-``/etc/init.d/rc.sysinit`` and ``/etc/init.d/rcS`` script. The default
-script is here: ``apps/nshlib/rc.sysinit.template`` and
-``apps/nshlib/rcS.template``. (The funny values in the rc.sysinit.template
-like ``XXXMKRDMINORXXX`` get replaced via ``sed`` at build time). This
-default configuration creates a ramdisk and mounts it at ``/tmp`` as
-discussed above.
-
-If that default behavior is not what you want, then you can provide your
-own custom ``rc.sysinit`` and ``rcS`` script by defining
-``CONFIG_NSH_ARCHROMFS=y`` in the configuration file.
-
-**Modifying the ROMFS Image**. The contents of the ``/etc`` directory
-are retained in the file ``apps/nshlib/nsh_romfsimg.h`` OR, if
-``CONFIG_NSH_ARCHROMFS`` is defined,
-``include/arch/board/nsh_romfsimg.h``. In order to modify the start-up
-behavior, there are three things to study:
-
- #. **Configuration Options.** The additional ``CONFIG_NSH_ROMFSETC``
- configuration options discussed with the other `NSH-specific
- configuration settings <#nshconfiguration>`__.
-
- #. ``tools/mkromfsimg.sh`` **Script**. The script
- ``tools/mkromfsimg.sh`` creates ``nsh_romfsimg.h``. It is not
- automatically executed. If you want to change the configuration
- settings associated with creating and mounting the ``/tmp``
- directory, then it will be necessary to re-generate this header file
- using the ``tools/mkromfsimg.sh`` script.
-
- The behavior of this script depends upon several things:
-
- #. The configuration settings then installed configuration.
-
- #. The ``genromfs`` tool(available from
- `http://romfs.sourceforge.net <http://romfs.sourceforge.net/>`__)
- or included within the NuttX buildroot toolchain. There is also a
- snapshot available in the NuttX tools repository
- `here <https://bitbucket.org/nuttx/tools/src/master/genromfs-0.5.2.tar.gz>`__.
-
- #. The ``xxd`` tool that is used to generate the C header files (xxd
- is a normal part of a complete Linux or Cygwin installation,
- usually as part of the ``vi`` package).
-
- #. The file ``apps/nshlib/rc.sysinit.template`` (OR, if
- ``CONFIG_NSH_ARCHROMFS`` is defined
- ``include/arch/board/rc.sysinit.template``.
-
- The file ``apps/nshlib/rcS.template`` (OR, if
- ``CONFIG_NSH_ARCHROMFS`` is defined
- ``include/arch/board/rcs.template``.
-
- #. ``rc.sysinit.template``. The file ``apps/nshlib/rc.sysinit.template``
- contains the general form of the ``rc.sysinit`` file; configured values
- are plugged into this template file to produce the final ``rc.sysinit`` file.
-
- ``rcS.template``. The file ``apps/nshlib/rcS.template`` contains the
- general form of the ``rcS`` file; configured values are plugged into
- this template file to produce the final ``rcS`` file.
-
- To generate a custom ``rc.sysinit`` and ``rcS`` file a copy of
- ``rc.sysinit.template`` and ``rcS.template`` needs to
- be placed at ``tools/`` and changed according to the desired start-up
- behaviour. Running ``tools/mkromfsimg.h`` creates ``nsh_romfsimg.h``
- which needs to be copied to ``apps/nshlib`` OR if
- ``CONFIG_NSH_ARCHROMFS`` is defined to
- ``boards/<arch>/<chip>/<board>/include``.
-
-``rc.sysinit.template``. The default ``rc.sysinit.template``,
-``apps/nshlib/rc.sysinit.template``, generates the standard, default
-``apps/nshlib/nsh_romfsimg.h`` file.
-
-``rcS.template``. The default ``rcS.template``,
-``apps/nshlib/rcS.template``, generates the standard, default
-``apps/nshlib/nsh_romfsimg.h`` file.
-
-If ``CONFIG_NSH_ARCHROMFS`` is defined in the NuttX configuration file,
-then a custom, board-specific ``nsh_romfsimg.h`` file residing in
-``boards/<arch>/<chip>/<board>/include``\ will be used. NOTE when the OS
-is configured, ``include/arch/board`` will be linked to
-``boards/<arch>/<chip>/<board>/include``.
-
-All of the startup-behavior is contained in ``rc.sysinit.template`` and
-``rcS.template``. The role of ``mkromfsimg.sh`` script is to (1) apply
-the specific configuration settings to ``rc.sysinit.template`` to create
-the final ``rc.sysinit``, and ``rcS.template`` to create the final ``rcS``,
-and (2) to generate the header file ``nsh_romfsimg.h`` containing the ROMFS file
-system image. To do this, ``mkromfsimg.sh`` uses two tools that must be
-installed in your system:
-
- #. The ``genromfs`` tool that is used to generate the ROMFS file system
- image.
-
- #. The ``xxd`` tool that is used to create the C header file.
diff --git a/content/docs/latest/_sources/applications/nsh/nsh.rst.txt b/content/docs/latest/_sources/applications/nsh/nsh.rst.txt
index d69aefb4..3398e40f 100644
--- a/content/docs/latest/_sources/applications/nsh/nsh.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/nsh.rst.txt
@@ -261,123 +261,3 @@ Environment Variables
========== ================================================
-NSH Start-Up Script
-===================
-
-**NSH Start-Up Script**. NSH supports options to provide a start
-up script for NSH. In general this capability is enabled with
-``CONFIG_NSH_ROMFSETC``, but has several other related
-configuration options as described with the
-:doc:`NSH specific configuration settings <config>`.
-This capability also depends on:
-
- - ``CONFIG_DISABLE_MOUNTPOINT`` not set
- - ``CONFIG_FS_ROMFS`` enabled
-
-**Default Start-Up Behavior**. The implementation that is provided
-is intended to provide great flexibility for the use of Start-Up
-files. This paragraph will discuss the general behavior when all
-of the configuration options are set to the default values.
-
-In this default case, enabling ``CONFIG_NSH_ROMFSETC`` will cause
-NSH to behave as follows at NSH startup time:
-
- - NSH will create a read-only RAM disk (a ROM disk), containing a
- tiny ROMFS file system containing the following::
-
- `--init.d/
- `-- rcS
- `-- rc.sysinit
-
- Where rcS is the NSH start-up script.
- Where rc.sysinit is the NSH system init script.
-
- - NSH will then mount the ROMFS file system at ``/etc``,
- resulting in::
-
- |--dev/
- | `-- ram0
- `--etc/
- `--init.d/
- `-- rcS
- `-- rc.sysinit
-
- - By default, the contents of rc.sysinit script are::
-
- # Create a RAMDISK and mount it at XXXRDMOUNTPOINTXXX
-
- mkrd -m 1 -s 512 1024
- mkfatfs /dev/ram1
- mount -t vfat /dev/ram1 /tmp
-
- - NSH will execute the script at ``/etc/init.d/rc.sysinit`` at
- system init script(before the first NSH prompt). After
- execution of the script, the root FS will look like::
-
- |--dev/
- | |-- ram0
- | `-- ram1
- |--etc/
- | `--init.d/
- | `-- rcS
- | `-- rc.sysinit
- `--tmp/
-
-**Modifying the ROMFS Image**. The contents of the ``/etc``
-directory are retained in the file ``apps/nshlib/nsh_romfsimg.h``
-OR, if ``CONFIG_NSH_ARCHROMFS`` is defined,
-``include/arch/board/rcs.template``). In order to modify the
-start-up behavior, there are three things to study:
-
- #. **Configuration Options.** The additional
- ``CONFIG_NSH_ROMFSETC`` configuration options discussed with
- the other :doc:`NSH specific configuration settings <config>`.
- #. `tools/mkromfsimg.sh`` **Script**. The script
- ``tools/mkromfsimg.sh`` creates ``nsh_romfsimg.h``. It is not
- automatically executed. If you want to change the configuration
- settings associated with creating and mounting the ``/tmp``
- directory, then it will be necessary to re-generate this header
- file using the ``tools/mkromfsimg.sh`` script.
-
- The behavior of this script depends upon three things:
-
- - The configuration settings then installed configuration.
- - The ``genromfs`` tool (available from
- http://romfs.sourceforge.net).
- - The file ``apps/nshlib/rc.sysinit.template`` (OR, if
- ``CONFIG_NSH_ARCHROMFS`` is defined
- ``include/arch/board/rc.sysinit.template``.
- The file ``apps/nshlib/rcS.template`` (OR, if
- ``CONFIG_NSH_ARCHROMFS`` is defined
- ``include/arch/board/rcs.template``.
-
- #. ``rc.sysinit.template``: The file ``apps/nshlib/rc.sysinit.template``
- contains the general form of the ``rc.sysinit`` file; configured
- values are plugged into this template file to produce the final
- ``rc.sysinit`` file.
-
- ``rcS.template``: The file ``apps/nshlib/rcS.template``
- contains the general form of the ``rcS`` file; configured
- values are plugged into this template file to produce the final
- ``rcS`` file.
-
-.. note::
- ``apps/nshlib/rcS.template`` and ``apps/nshlib/rc.sysinit.template``
- generates the standard, default ``nsh_romfsimg.h`` file.
- If ``CONFIG_NSH_ARCHROMFS`` is defined in the NuttX configuration
- file, then a custom, board-specific ``nsh_romfsimg.h`` file residing
- in the ``boards/<arch>/<chip>/<board>/include`` directory will be
- used. NOTE when the OS is configured, ``include/arch/board`` will be
- linked to ``boards/<arch>/<chip>/<board>/include``.
-
-All of the startup-behavior is contained in ``rc.sysinit.template``
-and ``rcS.template``. The role of ``mkromfsimg.sh`` is to (1) apply
-the specific configuration settings to ``rc.sysinit.template`` to create
-the final ``rc.sysinit``, and ``rc.sysinit.template`` to create the final
-``rcS`` and (2) to generate the header file ``nsh_romfsimg.h``
-containing the ROMFS file system image.
-
-**Further Information**. See the section on
-:doc:`Customizing the NuttShell <customizing>` for additional, more detailed
-information about the NSH start-up script and how to modify it.
-
diff --git a/content/docs/latest/_sources/guides/etcromfs.rst.txt b/content/docs/latest/_sources/guides/etcromfs.rst.txt
new file mode 100644
index 00000000..aee60257
--- /dev/null
+++ b/content/docs/latest/_sources/guides/etcromfs.rst.txt
@@ -0,0 +1,177 @@
+=========================
+etc romfs
+=========================
+The ROMFS image is the contents of the ``/etc`` directory, including the start-up script
+contains any command support by Nuttx, and other customized contents needed.
+
+Configuration
+=============
+
+.. code-block:: console
+
+ CONFIG_NSH_ROMFS /* Mount a ROMFS file system at "/etc" and provide a system init script at
+ "/etc/init.d.rc.sysinit" and a startup script at "etc/init.d/rcS". */
+ CONFIG_ETC_ROMFSMOUNTPT /* The default mountpoint for the ROMFS volume is "/etc", but that can be
+ changed with this setting. This must be a absolute path beginning with '/'
+ and enclosed in quotes. */
+ CONFIG_ETC_ROMFSDEVNO /* This is the minor number of the ROMFS block device. The default is '0'
+ corresponding to "/dev/ram0". */
+ CONFIG_ETC_ROMFSSECTSIZE /* This is the sector size to use with the ROMFS volume. Since the default volume
+ is very small, this defaults to 64 but should be increased if the ROMFS volume
+ were to be become large. Any value selected must be a power of 2. */
+
+This capability also depends on:
+
+.. code-block:: console
+
+ CONFIG_DISABLE_MOUNTPOINT /* If mount point support is disabled, then you cannot mount any file systems. */
+ CONFIG_FS_ROMFS /* This option enables ROMFS file system support. */
+
+Start up Scripts
+================
+
+**Start-Up Script**. The start-up script contains any command support by Nuttx
+(i.e., that you see when you enter 'nsh> help'). The implementation that is provided is
+intended to provide great flexibility for the use of Start-Up files.
+This paragraph will discuss the general behavior when all of the
+configuration options are set to the default values.
+
+In this default case, enabling ``CONFIG_ETC_ROMFS`` will cause Nuttx to
+behave as follows at Nuttx start-up time:
+
+ - Nuttx will create a read-only RAM disk (a ROM disk), containing a tiny
+ ROMFS file system containing the following::
+
+ `--init.d/
+ `-- rcS
+ `-- rc.sysinit
+
+ Where ``rcS`` is the start-up script.
+ Where ``rc.sysinit`` is the system-init script.
+
+ - Nuttx will then mount the ROMFS file system at ``/etc``, resulting in::
+
+ |--dev/
+ | `-- ram0
+ `--etc/
+ `--init.d/
+ `-- rcS
+ `-- rc.sysinit
+
+ - By default, the contents of ``rc.sysinit`` script are::
+
+ # Create a RAMDISK and mount it at /tmp
+
+ mkrd -m 1 -s 512 1024
+ mkfatfs /dev/ram1
+ mount -t vfat /dev/ram1 /tmp
+
+ - NSH will execute the script at ``/etc/init.d/rc.sysinit`` at system
+ init (before the first NSH prompt). After execution of the script,
+ the root FS will look like::
+
+ |--dev/
+ | |-- ram0
+ | `-- ram1
+ |--etc/
+ | `--init.d/
+ | `-- rcS
+ | `-- rc.sysinit
+ `--tmp/
+
+**Example Configurations**. Here are some configurations that have
+``CONFIG_ETC_ROMFS=y`` in the NuttX configuration file. They might
+provide useful examples:
+
+ - ``boards/arm/stm32/hymini-stm32v/nsh2``
+ - ``boards/arm/dm320/ntosd-dm320/nsh``
+ - ``boards/sim/sim/sim/nsh``
+ - ``boards/sim/sim/sim/nsh2``
+ - ``boards/sim/sim/sim/nx``
+ - ``boards/sim/sim/sim/nx11``
+ - ``boards/sim/sim/sim/touchscreen``
+
+In most of these cases, the configuration sets up the *default*
+``/etc/init.d/rc.sysinit`` and ``/etc/init.d/rcS`` script. The default
+script is here: ``apps/nshlib/rc.sysinit.template`` and
+``apps/nshlib/rcS.template``. (The funny values in the rc.sysinit.template
+like ``XXXMKRDMINORXXX`` get replaced via ``sed`` at build time). This
+default configuration creates a ramdisk and mounts it at ``/tmp`` as
+discussed above.
+
+Customizing Start up Scripts
+============================
+
+In order to modify the start-up behavior, there are three things to study:
+
+ #. **Configuration Options.** The additional ``CONFIG_ETC_ROMFS``
+ configuration options discussed with `Configuration`
+
+ #. ``tools/mkromfsimg.sh`` **Script**. The script
+ ``tools/mkromfsimg.sh`` creates ``etc_romfs.c``. It is not
+ automatically executed. If you want to change the configuration
+ settings associated with creating and mounting the ``/tmp``
+ directory, then it will be necessary to re-generate this header file
+ using the ``tools/mkromfsimg.sh`` script.
+
+ The behavior of this script depends upon several things:
+
+ #. The configuration settings then installed configuration.
+
+ #. The ``genromfs`` tool(available from
+ `http://romfs.sourceforge.net <http://romfs.sourceforge.net/>`__)
+ or included within the NuttX buildroot toolchain. There is also a
+ snapshot available in the NuttX tools repository
+ `here <https://bitbucket.org/nuttx/tools/src/master/genromfs-0.5.2.tar.gz>`__.
+
+ #. The ``xxd`` tool that is used to generate the C header files (xxd
+ is a normal part of a complete Linux or Cygwin installation,
+ usually as part of the ``vi`` package).
+
+ #. The file ``include/arch/board/rc.sysinit.template`` and
+ the file ``include/arch/board/rcs.template``
+
+ #. ``rc.sysinit.template``. The file ``apps/nshlib/rc.sysinit.template``
+ contains the general form of the ``rc.sysinit`` file; configured values
+ are plugged into this template file to produce the final ``rc.sysinit`` file.
+
+ ``rcS.template``. The file ``apps/nshlib/rcS.template`` contains the
+ general form of the ``rcS`` file; configured values are plugged into
+ this template file to produce the final ``rcS`` file.
+
+ To generate a custom ``rc.sysinit`` and ``rcS`` file a copy of
+ ``rc.sysinit.template`` and ``rcS.template`` needs to
+ be placed at ``tools/`` and changed according to the desired start-up
+ behaviour. Running ``tools/mkromfsimg.h`` creates ``etc_romfs.c``
+ which needs to be copied to ``arch/board/src`` and compiled in Makefile
+
+All of the startup-behavior is contained in ``rc.sysinit.template`` and
+``rcS.template``. The role of ``mkromfsimg.sh`` script is to (1) apply
+the specific configuration settings to ``rc.sysinit.template`` to create
+the final ``rc.sysinit``, and ``rcS.template`` to create the final ``rcS``,
+and (2) to generate the source file ``etc_romfs.c`` containing the ROMFS file
+system image. To do this, ``mkromfsimg.sh`` uses two tools that must be
+installed in your system:
+
+ #. The ``genromfs`` tool that is used to generate the ROMFS file system
+ image.
+
+ #. The ``xxd`` tool that is used to create the C header file.
+
+Customizing ROMFS Image
+=======================
+
+The ROMFS image can be generated from the content in the corresponding
+``board/arch/board/board/src/etc`` directory, and added by Makefile.
+
+**Example Configurations**. Here are some configurations that have
+``CONFIG_ETC_ROMFS=y`` in the NuttX configuration file. They might
+provide useful examples:
+
+ - ``boards/risc-v/bl808/ox64/src/etc``
+ - ``boards/risc-v/qemu-rv/rv-virt/src/etc``
+ - ``boards/risc-v/esp32c3/esp32c3-devkit/src/etc``
+ - ``boards/risc-v/k230/canmv230/src/etc``
+ - ``boards/risc-v/jh7110/star64/src/etc``
+ - ``boards/arm64/rk3399/nanopi_m4/src/etc``
+ - ``boards/sim/sim/sim/src/etc``
diff --git a/content/docs/latest/_sources/guides/index.rst.txt b/content/docs/latest/_sources/guides/index.rst.txt
index 9f092e14..01e11755 100644
--- a/content/docs/latest/_sources/guides/index.rst.txt
+++ b/content/docs/latest/_sources/guides/index.rst.txt
@@ -30,3 +30,4 @@ Guides
stm32nullpointer.rst
stm32ccm.rst
stackrecord.rst
+ etcromfs.rst
diff --git a/content/docs/latest/_sources/guides/pysimcoder.rst.txt b/content/docs/latest/_sources/guides/pysimcoder.rst.txt
index 991c8023..f202b1a1 100644
--- a/content/docs/latest/_sources/guides/pysimcoder.rst.txt
+++ b/content/docs/latest/_sources/guides/pysimcoder.rst.txt
@@ -49,7 +49,7 @@ with NuttX. The list is the following:
``CONFIG_ARCH_RAMVECTORS=y`` ``CONFIG_NSH_FILE_APPS=y``
``CONFIG_BOARDCTL_APP_SYMTAB=y`` ``CONFIG_NSH_LINELEN=64``
``CONFIG_BOARDCTL_OS_SYMTAB=y`` ``CONFIG_NSH_READLINE=y``
-``CONFIG_BUILTIN=y`` ``CONFIG_NSH_ROMFSETC=y``
+``CONFIG_BUILTIN=y`` ``CONFIG_ETC_ROMFS=y``
``CONFIG_ELF=y`` ``CONFIG_PSEUDOTERM=y``
``CONFIG_FS_BINFS=y`` ``CONFIG_PTHREAD_CLEANUP_STACKSIZE=1``
``CONFIG_FS_PROCFS=y`` ``CONFIG_PTHREAD_MUTEX_TYPES=y``
diff --git a/content/docs/latest/_sources/platforms/sim/sim/boards/sim/index.rst.txt b/content/docs/latest/_sources/platforms/sim/sim/boards/sim/index.rst.txt
index d5c5efa6..bc2a6fa9 100644
--- a/content/docs/latest/_sources/platforms/sim/sim/boards/sim/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/sim/sim/boards/sim/index.rst.txt
@@ -1043,7 +1043,7 @@ NOTES
@@ -117,7 +117,8 @@
/* Execute the startup script */
- #ifdef CONFIG_NSH_ROMFSETC
+ #ifdef CONFIG_ETC_ROMFS
- nsh_script(&pstate->cn_vtbl, "init", NSH_INITPATH);
+// REMOVE ME
+// nsh_script(&pstate->cn_vtbl, "init", NSH_INITPATH);
diff --git a/content/docs/latest/_sources/platforms/x86_64/qemu/boards/qemu-intel64/index.rst.txt b/content/docs/latest/_sources/platforms/x86_64/qemu/boards/qemu-intel64/index.rst.txt
index 04bcc426..74c43491 100644
--- a/content/docs/latest/_sources/platforms/x86_64/qemu/boards/qemu-intel64/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/x86_64/qemu/boards/qemu-intel64/index.rst.txt
@@ -2,6 +2,165 @@
qemu-intel64
============
-.. include:: README.txt
- :literal:
+This page file describes the contents of the build configurations available
+for the NuttX QEMU x86_64 port.
+Creating a bootable disk
+========================
+
+This build supports multiboot2, which means that usual multiboot2 bootlaoders,
+e.g. grub can be used. To create a bootable disk with grub2, create a directory
+named ``iso`` with grub configuration file and the compiled ``nuttx.elf``.
+
+Directory and file hierarchy::
+
+ - iso/
+ - boot/
+ - grub/
+ - grub.cfg
+ - nuttx.elf
+
+The grub.cfg should contain the boot entry of NuttX::
+
+ set timeout=0
+ set default=0
+ menuentry "kernel" {
+ multiboot2 /boot/nuttx.elf
+ }
+
+Making the disk
+---------------
+
+Use the following command to create the disk.
+P.S. In some distros, ``grub-mkrescue`` is called ``grub2-mkrescue``::
+
+ grub-mkrescue -o boot.iso iso
+
+QEMU/KVM
+========
+
+QEMU is a generic and open source machine emulator and virtual machine. Here are
+some links (which will probably be mostly outdated by the time your read this):
+
+* Home Page: http://wiki.qemu.org/Main_Page
+* Downloads: http://wiki.qemu.org/Download
+* Documentation: http://wiki.qemu.org/Manual
+
+KVM is the Linux kernel hypervisor.
+It supports creations of virtual machines in Linux systems.
+It is usually coupled with Qemu as its I/O supporting layer.
+
+The qemu can be build from source or downloaded from distro repositories.
+However, a modern CPU and KVM support are mandatory because the X2APIC is not
+available in pure emulator mode.
+This mean using this build with qemu in windows or old x86 machine can be
+frustrating. In such case, looks the next section and use bochs emulator instead.
+
+Running QEMU
+------------
+
+In the top-level NuttX directory::
+
+ qemu-system-x86_64 -cpu host -enable-kvm -m 2G -cdrom boot.iso -nographic -serial mon:stdio
+
+This multiplex the qemu console and COM1 to your console.
+
+Use control-a 1 and 2 to switch between.
+Use control-a x to terminate the emulation.
+
+P.S. Make sure that you CPU supports the mandatory features. Look at Real machine
+section for more information.
+
+Bochs
+=====
+
+Bochs is also a generic and open source machine emulator and virtualizer.
+It does very comprehensive emulation of x86 platform, even the state-of-art processors.
+Here are some links (which will probably be mostly outdated by the time your read this):
+
+* Home Page: http://bochs.sourceforge.net
+
+The bochs can be build from source.
+Unlike qemu, it does not rely on KVM to support modern hardware features,
+therefore it can also be used under Windows.
+When building bochs, remember to enable x86-64 support with ``--enable-x86-64``.
+If you also want support for SIMD instructions, enable them with ``--enable-avx --enable-evex``.
+
+Running Bochs
+-------------
+
+First edit/check the ``.bochsrc``
+You can create one in the top-level NuttX directory or bochs will use the one in your $HOME.
+Remember to change the CPU model to one with mandatory features and enable the COM port.
+
+* Find and edit (You might adjust the IPS as you machine perform)::
+
+ cpu: model=broadwell_ult, count=1, ips=50000000, reset_on_triple_fault=0, ignore_bad_msrs=0, msrs="msrs.def"
+ ata0-master: type=cdrom, path="<PATH TO boot.iso>", status=inserted
+
+* Add::
+
+ com1: enabled=1, mode=file, dev=com1.out
+
+* In the top-level NuttX directory::
+
+ bochs
+
+The emulator will drop into debugger mode.
+Enter ``c`` to start the emulation.
+COM port output will be in the com1.out file.
+
+Real machine
+============
+
+This port should work on real x86-64 machine with a proper CPU.
+The mandatory CPU features are:
+
+* TSC DEADLINE or APIC timer
+* PCID
+* X2APIC
+
+WARNING: IF you use TSC DEADLINE, make sure that your CPU's TSC DEADLINE timer
+is not buggy!
+
+Toolchains
+==========
+
+Currently, only the Linux GCC toolchain is tested.
+While building on a modern x86_64 PC, the default system GCC can be used.
+
+Configurations
+==============
+
+Common Configuration Notes
+--------------------------
+
+1. Each Qemu-intel64 configuration is maintained in a sub-directory
+ and can be selected as follow::
+
+ tools/configure.sh qemu-intel64:<subdir>
+
+ Where ``<subdir>`` is one of the configuration sub-directories described in
+ the following paragraph.
+
+2. These configurations use the mconf-based configuration tool. To
+ change a configurations using that tool, you should:
+
+ a. Build and install the kconfig-mconf tool. See nuttx/README.txt
+ see additional README.txt files in the NuttX tools repository.
+
+ b. Execute ``make menuconfig`` in nuttx/ in order to start the
+ reconfiguration process.
+
+3. By default, all configurations assume the Linux. This is easily
+ reconfigured::
+
+ CONFIG_HOST_LINUX=y
+
+Configuration Sub-Directories
+-----------------------------
+
+ostest
+------
+
+The "standard" NuttX examples/ostest configuration.
diff --git a/content/docs/latest/applications/nsh/config.html b/content/docs/latest/applications/nsh/config.html
index ee4aeac4..fc4c182e 100644
--- a/content/docs/latest/applications/nsh/config.html
+++ b/content/docs/latest/applications/nsh/config.html
@@ -751,14 +751,7 @@ the MMC/SD minor number, i.e., the MMC/SD block driver will be
registered as <code class="docutils literal notranslate"><span class="pre">/dev/mmcsd</span></code><em>N</em> where <em>N</em> is the minor number.
Default is zero.</p></td>
</tr>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code></p></td>
-<td><p>Mount a ROMFS file system at <code class="docutils literal notranslate"><span class="pre">/etc</span></code> and provide a system init
-script at <code class="docutils literal notranslate"><span class="pre">/etc/init.d.rc.sysinit</span></code> and a startup script at
-<code class="docutils literal notranslate"><span class="pre">/etc/init.d/rcS</span></code>.
-The default system init script will mount a FAT FS RAMDISK at
-<code class="docutils literal notranslate"><span class="pre">/tmp</span></code> but the logic is <a class="reference external" href="#startupscript">easily extensible</a>.</p></td>
-</tr>
-<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_CONSOLE</span></code></p></td>
+<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_CONSOLE</span></code></p></td>
<td><p>If <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_CONSOLE</span></code> is set to <em>y</em>, then a serial console
front-end is selected.</p>
<p>Normally, the serial console device is a UART and RS-232
@@ -803,7 +796,7 @@ Default: Only USB errors are traced.</p>
</ul>
</td>
</tr>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ALTCONDEV</span></code> and</p></td>
+<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ALTCONDEV</span></code> and</p></td>
<td><p>If <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_CONSOLE</span></code> is set <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_CONDEV</span></code>
to <em>y</em>, then <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ALTCONDEV</span></code> may also
be selected to enable use of an alternate character device to
@@ -832,12 +825,12 @@ console device.</p></li>
</ul>
</td>
</tr>
-<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_TELNET</span></code></p></td>
+<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_TELNET</span></code></p></td>
<td><p>If <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_TELNET</span></code> is set to <em>y</em>, then a TELNET server
front-end is selected. When this option is provided, you may log
into NuttX remotely using telnet in order to access NSH.</p></td>
</tr>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHINIT</span></code></p></td>
+<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHINIT</span></code></p></td>
<td><p>Set <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHINIT</span></code> if your board provides architecture
specific initialization via the board-specific function
<code class="docutils literal notranslate"><span class="pre">board_app_initialize()</span></code>. This function will be called early in
@@ -976,7 +969,7 @@ is indicated.</p></td>
</tr>
</tbody>
</table>
-<p>If <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code> is selected, then the following additional
+<p>If <code class="docutils literal notranslate"><span class="pre">CONFIG_ETC_ROMFS</span></code> is selected, then the following additional
configuration setting apply:</p>
<table class="docutils align-default">
<thead>
@@ -985,15 +978,6 @@ configuration setting apply:</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code></p></td>
-<td><p>May be defined to specify an alternative ROMFS image
-that can be found at <code class="docutils literal notranslate"><span class="pre">boards/<arch>/<chip>/<board>/include/nsh_romfsimg.h</span></code>.</p></td>
-</tr>
-<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSMOUNTPT</span></code></p></td>
-<td><p>The default mountpoint for the ROMFS volume is <code class="docutils literal notranslate"><span class="pre">"/etc"</span></code>,
-but that can be changed with this setting. This must be a
-absolute path beginning with ‘<code class="docutils literal notranslate"><span class="pre">/</span></code>’ and enclosed in quotes.</p></td>
-</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_SYSINITSCRIPT</span></code></p></td>
<td><p>This is the relative path to the system init script within the
mountpoint. The default is <code class="docutils literal notranslate"><span class="pre">"init.d/rc.sysinit"</span></code>. This is a relative
@@ -1004,35 +988,6 @@ path and must not start with ‘<code class="docutils literal notranslate"><span
mountpoint. The default is <code class="docutils literal notranslate"><span class="pre">"init.d/rcS"</span></code>. This is a relative
path and must not start with ‘<code class="docutils literal notranslate"><span class="pre">/</span></code>’ but must be enclosed in quotes.</p></td>
</tr>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSDEVNO</span></code></p></td>
-<td><p>This is the minor number of the ROMFS block device.
-The default is ‘<code class="docutils literal notranslate"><span class="pre">0</span></code>’ corresponding to <code class="docutils literal notranslate"><span class="pre">/dev/ram0</span></code>.</p></td>
-</tr>
-<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSSECTSIZE</span></code></p></td>
-<td><p>This is the sector size to use with the ROMFS volume. Since the
-default volume is very small, this defaults to 64 but should
-be increased if the ROMFS volume were to be become large.
-Any value selected must be a power of 2.</p></td>
-</tr>
-</tbody>
-</table>
-<p>When the default <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> file used when <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code> is
-selected, it will mount a FAT FS under <code class="docutils literal notranslate"><span class="pre">/tmp</span></code>. The following
-selections describe that FAT FS.</p>
-<table class="docutils align-default">
-<thead>
-<tr class="row-odd"><th class="head"><p>Configuration</p></th>
-<th class="head"><p>Description</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_FATDEVNO</span></code></p></td>
-<td><p>This is the minor number of the FAT FS block device.
-The default is ‘<code class="docutils literal notranslate"><span class="pre">1</span></code>’ corresponding to <code class="docutils literal notranslate"><span class="pre">/dev/ram1</span></code>.</p></td>
-</tr>
-<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_FATSECTSIZE</span></code></p></td>
-<td><p>This is the sector size use with the FAT FS. Default is 512.</p></td>
-</tr>
</tbody>
</table>
</section>
diff --git a/content/docs/latest/applications/nsh/index.html b/content/docs/latest/applications/nsh/index.html
index f5c409e3..49294845 100644
--- a/content/docs/latest/applications/nsh/index.html
+++ b/content/docs/latest/applications/nsh/index.html
@@ -201,7 +201,6 @@ starts a given task instead of the main <code class="docutils literal notranslat
<li class="toctree-l2"><a class="reference internal" href="nsh.html#built-in-variables">Built-In Variables</a></li>
<li class="toctree-l2"><a class="reference internal" href="nsh.html#current-working-directory">Current Working Directory</a></li>
<li class="toctree-l2"><a class="reference internal" href="nsh.html#environment-variables">Environment Variables</a></li>
-<li class="toctree-l2"><a class="reference internal" href="nsh.html#nsh-start-up-script">NSH Start-Up Script</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="commands.html">Commands</a><ul>
@@ -307,10 +306,7 @@ starts a given task instead of the main <code class="docutils literal notranslat
<li class="toctree-l2"><a class="reference internal" href="builtin.html#synchronous-built-in-applications">Synchronous Built-In Applications</a></li>
</ul>
</li>
-<li class="toctree-l1"><a class="reference internal" href="installation.html">Customizing NSH Initialization</a><ul>
-<li class="toctree-l2"><a class="reference internal" href="installation.html#nuttshell-start-up-scripts">NuttShell Start up Scripts</a></li>
-</ul>
-</li>
+<li class="toctree-l1"><a class="reference internal" href="installation.html">Customizing NSH Initialization</a></li>
<li class="toctree-l1"><a class="reference internal" href="login.html">Shell Login</a><ul>
<li class="toctree-l2"><a class="reference internal" href="login.html#enabling-shell-logins">Enabling Shell Logins</a></li>
<li class="toctree-l2"><a class="reference internal" href="login.html#verification-of-credentials">Verification of Credentials</a></li>
diff --git a/content/docs/latest/applications/nsh/installation.html b/content/docs/latest/applications/nsh/installation.html
index e8ac03a0..5c9ea0f2 100644
--- a/content/docs/latest/applications/nsh/installation.html
+++ b/content/docs/latest/applications/nsh/installation.html
@@ -136,10 +136,7 @@
<li class="toctree-l3"><a class="reference internal" href="customizing.html">The NSH Library and NSH Initialization</a></li>
<li class="toctree-l3"><a class="reference internal" href="customizing.html#nsh-commands">NSH Commands</a></li>
<li class="toctree-l3"><a class="reference internal" href="builtin.html">NSH “Built-In” Applications</a></li>
-<li class="toctree-l3 current"><a class="current reference internal" href="#">Customizing NSH Initialization</a><ul>
-<li class="toctree-l4"><a class="reference internal" href="#nuttshell-start-up-scripts">NuttShell Start up Scripts</a></li>
-</ul>
-</li>
+<li class="toctree-l3 current"><a class="current reference internal" href="#">Customizing NSH Initialization</a></li>
<li class="toctree-l3"><a class="reference internal" href="login.html">Shell Login</a></li>
<li class="toctree-l3"><a class="reference internal" href="running_apps.html">Running Applications from NSH</a></li>
</ul>
@@ -212,181 +209,6 @@ create the start-up script. It is sufficiently complex that is
deserves its own paragraph</p></li>
</ol>
</div></blockquote>
-<section id="nuttshell-start-up-scripts">
-<h2>NuttShell Start up Scripts<a class="headerlink" href="#nuttshell-start-up-scripts" title="Permalink to this heading"></a></h2>
-<p>First of all you should look at <a class="reference external" href="#startupscript">NSH Start-Up Script</a>
-paragraph. Most everything you need to know can be found there. That
-information will be repeated and extended here for completeness.</p>
-<p><strong>NSH Start-Up Script</strong>. NSH supports options to provide a start up
-script for NSH. The start-up script contains any command support by NSH
-(i.e., that you see when you enter ‘nsh> help’). In general this
-capability is enabled with <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC=y</span></code>, but has several
-other related configuration options as described with the <a class="reference external" href="#nshconfiguration">NSH-specific
-configuration settings</a> paragraph. This capability
-also depends on:</p>
-<blockquote>
-<div><ul class="simple">
-<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_DISABLE_MOUNTPOINT=n</span></code>. If mount point support is disabled,
-then you cannot mount <em>any</em> file systems.</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_FS_ROMFS</span></code> enabled. This option enables ROMFS file system
-support.</p></li>
-</ul>
-</div></blockquote>
-<p><strong>Default Start-Up Behavior</strong>. The implementation that is provided is
-intended to provide great flexibility for the use of Start-Up files.
-This paragraph will discuss the general behavior when all of the
-configuration options are set to the default values.</p>
-<p>In this default case, enabling <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code> will cause NSH to
-behave as follows at NSH start-up time:</p>
-<blockquote>
-<div><ul>
-<li><p>NSH will create a read-only RAM disk (a ROM disk), containing a tiny
-ROMFS file system containing the following:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>`--init.d/
- `-- rcS
- `-- rc.sysinit
-</pre></div>
-</div>
-<p>Where <code class="docutils literal notranslate"><span class="pre">rcS</span></code> is the NSH start-up script.
-Where <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> is the NSH system-init script.</p>
-</li>
-<li><p>NSH will then mount the ROMFS file system at <code class="docutils literal notranslate"><span class="pre">/etc</span></code>, resulting in:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>|--dev/
-| `-- ram0
-`--etc/
- `--init.d/
- `-- rcS
- `-- rc.sysinit
-</pre></div>
-</div>
-</li>
-<li><p>By default, the contents of <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> script are:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span># Create a RAMDISK and mount it at /tmp
-
-mkrd -m 1 -s 512 1024
-mkfatfs /dev/ram1
-mount -t vfat /dev/ram1 /tmp
-</pre></div>
-</div>
-</li>
-<li><p>NSH will execute the script at <code class="docutils literal notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> at system
-init (before the first NSH prompt). After execution of the script,
-the root FS will look like:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>|--dev/
-| |-- ram0
-| `-- ram1
-|--etc/
-| `--init.d/
-| `-- rcS
-| `-- rc.sysinit
-`--tmp/
-</pre></div>
-</div>
-</li>
-</ul>
-</div></blockquote>
-<p><strong>Example Configurations</strong>. Here are some configurations that have
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC=y</span></code> in the NuttX configuration file. They might
-provide useful examples:</p>
-<blockquote>
-<div><ul class="simple">
-<li><p><code class="docutils literal notranslate"><span class="pre">boards/arm/stm32/hymini-stm32v/nsh2</span></code></p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">boards/arm/dm320/ntosd-dm320/nsh</span></code></p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nsh</span></code></p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nsh2</span></code></p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nx</span></code></p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nx11</span></code></p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/touchscreen</span></code></p></li>
-</ul>
-</div></blockquote>
-<p>In most of these cases, the configuration sets up the <em>default</em>
-<code class="docutils literal notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> and <code class="docutils literal notranslate"><span class="pre">/etc/init.d/rcS</span></code> script. The default
-script is here: <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code> and
-<code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code>. (The funny values in the rc.sysinit.template
-like <code class="docutils literal notranslate"><span class="pre">XXXMKRDMINORXXX</span></code> get replaced via <code class="docutils literal notranslate"><span class="pre">sed</span></code> at build time). This
-default configuration creates a ramdisk and mounts it at <code class="docutils literal notranslate"><span class="pre">/tmp</span></code> as
-discussed above.</p>
-<p>If that default behavior is not what you want, then you can provide your
-own custom <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> and <code class="docutils literal notranslate"><span class="pre">rcS</span></code> script by defining
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS=y</span></code> in the configuration file.</p>
-<p><strong>Modifying the ROMFS Image</strong>. The contents of the <code class="docutils literal notranslate"><span class="pre">/etc</span></code> directory
-are retained in the file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/nsh_romfsimg.h</span></code> OR, if
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined,
-<code class="docutils literal notranslate"><span class="pre">include/arch/board/nsh_romfsimg.h</span></code>. In order to modify the start-up
-behavior, there are three things to study:</p>
-<blockquote>
-<div><ol class="arabic">
-<li><p><strong>Configuration Options.</strong> The additional <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code>
-configuration options discussed with the other <a class="reference external" href="#nshconfiguration">NSH-specific
-configuration settings</a>.</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> <strong>Script</strong>. The script
-<code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> creates <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code>. It is not
-automatically executed. If you want to change the configuration
-settings associated with creating and mounting the <code class="docutils literal notranslate"><span class="pre">/tmp</span></code>
-directory, then it will be necessary to re-generate this header file
-using the <code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> script.</p>
-<p>The behavior of this script depends upon several things:</p>
-<ol class="arabic">
-<li><p>The configuration settings then installed configuration.</p></li>
-<li><p>The <code class="docutils literal notranslate"><span class="pre">genromfs</span></code> tool(available from
-<a class="reference external" href="http://romfs.sourceforge.net/">http://romfs.sourceforge.net</a>)
-or included within the NuttX buildroot toolchain. There is also a
-snapshot available in the NuttX tools repository
-<a class="reference external" href="https://bitbucket.org/nuttx/tools/src/master/genromfs-0.5.2.tar.gz">here</a>.</p></li>
-<li><p>The <code class="docutils literal notranslate"><span class="pre">xxd</span></code> tool that is used to generate the C header files (xxd
-is a normal part of a complete Linux or Cygwin installation,
-usually as part of the <code class="docutils literal notranslate"><span class="pre">vi</span></code> package).</p></li>
-<li><p>The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code> (OR, if
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
-<code class="docutils literal notranslate"><span class="pre">include/arch/board/rc.sysinit.template</span></code>.</p>
-<p>The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code> (OR, if
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
-<code class="docutils literal notranslate"><span class="pre">include/arch/board/rcs.template</span></code>.</p>
-</li>
-</ol>
-</li>
-<li><p><code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code>. The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code>
-contains the general form of the <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> file; configured values
-are plugged into this template file to produce the final <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> file.</p>
-<p><code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>. The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code> contains the
-general form of the <code class="docutils literal notranslate"><span class="pre">rcS</span></code> file; configured values are plugged into
-this template file to produce the final <code class="docutils literal notranslate"><span class="pre">rcS</span></code> file.</p>
-<p>To generate a custom <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> and <code class="docutils literal notranslate"><span class="pre">rcS</span></code> file a copy of
-<code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> and <code class="docutils literal notranslate"><span class="pre">rcS.template</span></code> needs to
-be placed at <code class="docutils literal notranslate"><span class="pre">tools/</span></code> and changed according to the desired start-up
-behaviour. Running <code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.h</span></code> creates <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code>
-which needs to be copied to <code class="docutils literal notranslate"><span class="pre">apps/nshlib</span></code> OR if
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined to
-<code class="docutils literal notranslate"><span class="pre">boards/<arch>/<chip>/<board>/include</span></code>.</p>
-</li>
-</ol>
-</div></blockquote>
-<p><code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code>. The default <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code>,
-<code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code>, generates the standard, default
-<code class="docutils literal notranslate"><span class="pre">apps/nshlib/nsh_romfsimg.h</span></code> file.</p>
-<p><code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>. The default <code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>,
-<code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code>, generates the standard, default
-<code class="docutils literal notranslate"><span class="pre">apps/nshlib/nsh_romfsimg.h</span></code> file.</p>
-<p>If <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined in the NuttX configuration file,
-then a custom, board-specific <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code> file residing in
-<code class="docutils literal notranslate"><span class="pre">boards/<arch>/<chip>/<board>/include</span></code>will be used. NOTE when the OS
-is configured, <code class="docutils literal notranslate"><span class="pre">include/arch/board</span></code> will be linked to
-<code class="docutils literal notranslate"><span class="pre">boards/<arch>/<chip>/<board>/include</span></code>.</p>
-<p>All of the startup-behavior is contained in <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> and
-<code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>. The role of <code class="docutils literal notranslate"><span class="pre">mkromfsimg.sh</span></code> script is to (1) apply
-the specific configuration settings to <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> to create
-the final <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code>, and <code class="docutils literal notranslate"><span class="pre">rcS.template</span></code> to create the final <code class="docutils literal notranslate"><span class="pre">rcS</span></code>,
-and (2) to generate the header file <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code> containing the ROMFS file
-system image. To do this, <code class="docutils literal notranslate"><span class="pre">mkromfsimg.sh</span></code> uses two tools that must be
-installed in your system:</p>
-<blockquote>
-<div><ol class="arabic simple">
-<li><p>The <code class="docutils literal notranslate"><span class="pre">genromfs</span></code> tool that is used to generate the ROMFS file system
-image.</p></li>
-<li><p>The <code class="docutils literal notranslate"><span class="pre">xxd</span></code> tool that is used to create the C header file.</p></li>
-</ol>
-</div></blockquote>
-</section>
</section>
diff --git a/content/docs/latest/applications/nsh/nsh.html b/content/docs/latest/applications/nsh/nsh.html
index 47909f07..870cd802 100644
--- a/content/docs/latest/applications/nsh/nsh.html
+++ b/content/docs/latest/applications/nsh/nsh.html
@@ -138,7 +138,6 @@
<li class="toctree-l4"><a class="reference internal" href="#built-in-variables">Built-In Variables</a></li>
<li class="toctree-l4"><a class="reference internal" href="#current-working-directory">Current Working Directory</a></li>
<li class="toctree-l4"><a class="reference internal" href="#environment-variables">Environment Variables</a></li>
-<li class="toctree-l4"><a class="reference internal" href="#nsh-start-up-script">NSH Start-Up Script</a></li>
</ul>
</li>
<li class="toctree-l3"><a class="reference internal" href="commands.html">Commands</a></li>
@@ -474,134 +473,6 @@ for executable, binary programs working directory</p></td>
</tbody>
</table>
</section>
-<section id="nsh-start-up-script">
-<h2>NSH Start-Up Script<a class="headerlink" href="#nsh-start-up-script" title="Permalink to this heading"></a></h2>
-<p><strong>NSH Start-Up Script</strong>. NSH supports options to provide a start
-up script for NSH. In general this capability is enabled with
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code>, but has several other related
-configuration options as described with the
-<a class="reference internal" href="config.html"><span class="doc">NSH specific configuration settings</span></a>.
-This capability also depends on:</p>
-<blockquote>
-<div><ul class="simple">
-<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_DISABLE_MOUNTPOINT</span></code> not set</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">CONFIG_FS_ROMFS</span></code> enabled</p></li>
-</ul>
-</div></blockquote>
-<p><strong>Default Start-Up Behavior</strong>. The implementation that is provided
-is intended to provide great flexibility for the use of Start-Up
-files. This paragraph will discuss the general behavior when all
-of the configuration options are set to the default values.</p>
-<p>In this default case, enabling <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code> will cause
-NSH to behave as follows at NSH startup time:</p>
-<blockquote>
-<div><ul>
-<li><p>NSH will create a read-only RAM disk (a ROM disk), containing a
-tiny ROMFS file system containing the following:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>`--init.d/
- `-- rcS
- `-- rc.sysinit
-</pre></div>
-</div>
-<p>Where rcS is the NSH start-up script.
-Where rc.sysinit is the NSH system init script.</p>
-</li>
-<li><p>NSH will then mount the ROMFS file system at <code class="docutils literal notranslate"><span class="pre">/etc</span></code>,
-resulting in:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>|--dev/
-| `-- ram0
-`--etc/
- `--init.d/
- `-- rcS
- `-- rc.sysinit
-</pre></div>
-</div>
-</li>
-<li><p>By default, the contents of rc.sysinit script are:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span># Create a RAMDISK and mount it at XXXRDMOUNTPOINTXXX
-
-mkrd -m 1 -s 512 1024
-mkfatfs /dev/ram1
-mount -t vfat /dev/ram1 /tmp
-</pre></div>
-</div>
-</li>
-<li><p>NSH will execute the script at <code class="docutils literal notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> at
-system init script(before the first NSH prompt). After
-execution of the script, the root FS will look like:</p>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>|--dev/
-| |-- ram0
-| `-- ram1
-|--etc/
-| `--init.d/
-| `-- rcS
-| `-- rc.sysinit
-`--tmp/
-</pre></div>
-</div>
-</li>
-</ul>
-</div></blockquote>
-<p><strong>Modifying the ROMFS Image</strong>. The contents of the <code class="docutils literal notranslate"><span class="pre">/etc</span></code>
-directory are retained in the file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/nsh_romfsimg.h</span></code>
-OR, if <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined,
-<code class="docutils literal notranslate"><span class="pre">include/arch/board/rcs.template</span></code>). In order to modify the
-start-up behavior, there are three things to study:</p>
-<blockquote>
-<div><ol class="arabic">
-<li><p><strong>Configuration Options.</strong> The additional
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code> configuration options discussed with
-the other <a class="reference internal" href="config.html"><span class="doc">NSH specific configuration settings</span></a>.</p></li>
-<li><p><cite>tools/mkromfsimg.sh`</cite> <strong>Script</strong>. The script
-<code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> creates <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code>. It is not
-automatically executed. If you want to change the configuration
-settings associated with creating and mounting the <code class="docutils literal notranslate"><span class="pre">/tmp</span></code>
-directory, then it will be necessary to re-generate this header
-file using the <code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> script.</p>
-<p>The behavior of this script depends upon three things:</p>
-<ul class="simple">
-<li><p>The configuration settings then installed configuration.</p></li>
-<li><p>The <code class="docutils literal notranslate"><span class="pre">genromfs</span></code> tool (available from
-<a class="reference external" href="http://romfs.sourceforge.net">http://romfs.sourceforge.net</a>).</p></li>
-<li><p>The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code> (OR, if
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
-<code class="docutils literal notranslate"><span class="pre">include/arch/board/rc.sysinit.template</span></code>.
-The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code> (OR, if
-<code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
-<code class="docutils literal notranslate"><span class="pre">include/arch/board/rcs.template</span></code>.</p></li>
-</ul>
-</li>
-<li><p><code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code>: The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code>
-contains the general form of the <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> file; configured
-values are plugged into this template file to produce the final
-<code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> file.</p>
-<p><code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>: The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code>
-contains the general form of the <code class="docutils literal notranslate"><span class="pre">rcS</span></code> file; configured
-values are plugged into this template file to produce the final
-<code class="docutils literal notranslate"><span class="pre">rcS</span></code> file.</p>
-</li>
-</ol>
-</div></blockquote>
-<div class="admonition note">
-<p class="admonition-title">Note</p>
-<p><code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code> and <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code>
-generates the standard, default <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code> file.
-If <code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined in the NuttX configuration
-file, then a custom, board-specific <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code> file residing
-in the <code class="docutils literal notranslate"><span class="pre">boards/<arch>/<chip>/<board>/include</span></code> directory will be
-used. NOTE when the OS is configured, <code class="docutils literal notranslate"><span class="pre">include/arch/board</span></code> will be
-linked to <code class="docutils literal notranslate"><span class="pre">boards/<arch>/<chip>/<board>/include</span></code>.</p>
-</div>
-<p>All of the startup-behavior is contained in <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code>
-and <code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>. The role of <code class="docutils literal notranslate"><span class="pre">mkromfsimg.sh</span></code> is to (1) apply
-the specific configuration settings to <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> to create
-the final <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code>, and <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> to create the final
-<code class="docutils literal notranslate"><span class="pre">rcS</span></code> and (2) to generate the header file <code class="docutils literal notranslate"><span class="pre">nsh_romfsimg.h</span></code>
-containing the ROMFS file system image.</p>
-<p><strong>Further Information</strong>. See the section on
-<a class="reference internal" href="customizing.html"><span class="doc">Customizing the NuttShell</span></a> for additional, more detailed
-information about the NSH start-up script and how to modify it.</p>
-</section>
</section>
diff --git a/content/docs/latest/glossary.html b/content/docs/latest/glossary.html
index f06d807e..caf8237a 100644
--- a/content/docs/latest/glossary.html
+++ b/content/docs/latest/glossary.html
@@ -44,7 +44,7 @@
<script src="_static/js/theme.js"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
- <link rel="prev" title="Run time stack statistics" href="guides/stackrecord.html" />
+ <link rel="prev" title="etc romfs" href="guides/etcromfs.html" />
</head>
<body class="wy-body-for-nav">
@@ -394,7 +394,7 @@
</div>
</div>
<footer><div class="rst-footer-buttons" role="navigation" aria-label="Footer">
- <a href="guides/stackrecord.html" class="btn btn-neutral float-left" title="Run time stack statistics" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="guides/etcromfs.html" class="btn btn-neutral float-left" title="etc romfs" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
</div>
<hr/>
diff --git a/content/docs/latest/guides/automounter.html b/content/docs/latest/guides/automounter.html
index 1d97be51..0cb669d3 100644
--- a/content/docs/latest/guides/automounter.html
+++ b/content/docs/latest/guides/automounter.html
@@ -146,6 +146,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/citests.html b/content/docs/latest/guides/citests.html
index 2a2e5763..ed313127 100644
--- a/content/docs/latest/guides/citests.html
+++ b/content/docs/latest/guides/citests.html
@@ -145,6 +145,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/coredump.html b/content/docs/latest/guides/coredump.html
index 02c993be..d9b21b56 100644
--- a/content/docs/latest/guides/coredump.html
+++ b/content/docs/latest/guides/coredump.html
@@ -147,6 +147,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/cortexmhardfaults.html b/content/docs/latest/guides/cortexmhardfaults.html
index 6754a2c9..4418821d 100644
--- a/content/docs/latest/guides/cortexmhardfaults.html
+++ b/content/docs/latest/guides/cortexmhardfaults.html
@@ -151,6 +151,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/cpp_cmake.html b/content/docs/latest/guides/cpp_cmake.html
index 143299a8..13c00576 100644
--- a/content/docs/latest/guides/cpp_cmake.html
+++ b/content/docs/latest/guides/cpp_cmake.html
@@ -146,6 +146,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/customapps.html b/content/docs/latest/guides/customapps.html
index 5b5a709e..398160de 100644
--- a/content/docs/latest/guides/customapps.html
+++ b/content/docs/latest/guides/customapps.html
@@ -165,6 +165,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/customboards.html b/content/docs/latest/guides/customboards.html
index b377f1ab..d7394d8d 100644
--- a/content/docs/latest/guides/customboards.html
+++ b/content/docs/latest/guides/customboards.html
@@ -145,6 +145,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/drivers.html b/content/docs/latest/guides/drivers.html
index e1238565..7d5ae907 100644
--- a/content/docs/latest/guides/drivers.html
+++ b/content/docs/latest/guides/drivers.html
@@ -148,6 +148,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/etcromfs.html b/content/docs/latest/guides/etcromfs.html
new file mode 100644
index 00000000..07e5cd4a
--- /dev/null
+++ b/content/docs/latest/guides/etcromfs.html
@@ -0,0 +1,389 @@
+<!--
+ Documentation/_templates/layout.html
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership. The
+ ASF licenses this file to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance with the
+ License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ License for the specific language governing permissions and limitations
+ under the License.
+-->
+
+<!DOCTYPE html>
+<html class="writer-html5" lang="en" >
+<head>
+ <meta charset="utf-8" /><meta name="generator" content="Docutils 0.18.1: http://docutils.sourceforge.net/" />
+
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+ <title>etc romfs — NuttX latest documentation</title>
+ <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
+ <link rel="stylesheet" href="../_static/css/theme.css" type="text/css" />
+ <link rel="stylesheet" href="../_static/copybutton.css" type="text/css" />
+ <link rel="stylesheet" href="../_static/tabs.css" type="text/css" />
+ <link rel="stylesheet" href="../_static/custom.css" type="text/css" />
+ <link rel="shortcut icon" href="../_static/favicon.ico"/>
+ <!--[if lt IE 9]>
+ <script src="../_static/js/html5shiv.min.js"></script>
+ <![endif]-->
+
+ <script src="../_static/jquery.js"></script>
+ <script src="../_static/_sphinx_javascript_frameworks_compat.js"></script>
+ <script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script>
+ <script src="../_static/doctools.js"></script>
+ <script src="../_static/sphinx_highlight.js"></script>
+ <script src="../_static/clipboard.min.js"></script>
+ <script src="../_static/copybutton.js"></script>
+ <script src="../_static/js/theme.js"></script>
+ <link rel="index" title="Index" href="../genindex.html" />
+ <link rel="search" title="Search" href="../search.html" />
+ <link rel="next" title="Glossary" href="../glossary.html" />
+ <link rel="prev" title="Run time stack statistics" href="stackrecord.html" />
+</head>
+
+<body class="wy-body-for-nav">
+ <div class="wy-grid-for-nav">
+ <nav data-toggle="wy-nav-shift" class="wy-nav-side">
+ <div class="wy-side-scroll">
+ <div class="wy-side-nav-search" >
+
+ <a href="../index.html" class="icon icon-home"> NuttX
+
+
+
+ </a>
+
+ <!-- this version selector is quite ugly, should be probably replaced by something
+ more modern -->
+
+ <div class="version-selector">
+ <select onchange="javascript:location.href = this.value;">
+
+ <option value="../../latest" selected="selected">latest</option>
+
+ <option value="../../10.0.0" >10.0.0</option>
+
+ <option value="../../10.0.1" >10.0.1</option>
+
+ <option value="../../10.1.0" >10.1.0</option>
+
+ <option value="../../10.2.0" >10.2.0</option>
+
+ <option value="../../10.3.0" >10.3.0</option>
+
+ <option value="../../11.0.0" >11.0.0</option>
+
+ <option value="../../12.0.0" >12.0.0</option>
+
+ <option value="../../12.1.0" >12.1.0</option>
+
+ <option value="../../12.2.0" >12.2.0</option>
+
+ <option value="../../12.2.1" >12.2.1</option>
+
+ <option value="../../12.3.0" >12.3.0</option>
+
+ </select>
+ </div>
+
+
+<div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../search.html" method="get">
+ <input type="text" name="q" placeholder="Search docs" aria-label="Search docs" />
+ <input type="hidden" name="check_keywords" value="yes" />
+ <input type="hidden" name="area" value="default" />
+ </form>
+</div>
+
+ </div><div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu">
+ <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
+<ul class="current">
+<li class="toctree-l1"><a class="reference internal" href="../index.html">Home</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../introduction/index.html">Introduction</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../quickstart/index.html">Getting Started</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../contributing/index.html">Contributing</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../introduction/inviolables.html">The Inviolable Principles of NuttX</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../platforms/index.html">Supported Platforms</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../components/index.html">OS Components</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../applications/index.html">Applications</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../implementation/index.html">Implementation Details</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../reference/index.html">API Reference</a></li>
+<li class="toctree-l1"><a class="reference internal" href="../faq/index.html">FAQ</a></li>
+<li class="toctree-l1 current"><a class="reference internal" href="index.html">Guides</a><ul class="current">
+<li class="toctree-l2"><a class="reference internal" href="nfs.html">NFS Client How-To</a></li>
+<li class="toctree-l2"><a class="reference internal" href="usbtrace.html">USB Device Trace</a></li>
+<li class="toctree-l2"><a class="reference internal" href="simulator.html">Simulator</a></li>
+<li class="toctree-l2"><a class="reference internal" href="qemugdb.html">How to debug NuttX using QEMU and GDB</a></li>
+<li class="toctree-l2"><a class="reference internal" href="rndis.html">How to use RNDIS</a></li>
+<li class="toctree-l2"><a class="reference internal" href="drivers.html">Drivers</a></li>
+<li class="toctree-l2"><a class="reference internal" href="tasktrace.html">Task Trace</a></li>
+<li class="toctree-l2"><a class="reference internal" href="cpp_cmake.html">C++ Example using CMake</a></li>
+<li class="toctree-l2"><a class="reference internal" href="pysimcoder.html">pysimCoder integration with NuttX</a></li>
+<li class="toctree-l2"><a class="reference internal" href="customboards.html">Custom Boards How-To</a></li>
+<li class="toctree-l2"><a class="reference internal" href="customapps.html">Custom Apps How-to</a></li>
+<li class="toctree-l2"><a class="reference internal" href="citests.html">Running CI Test Locally</a></li>
+<li class="toctree-l2"><a class="reference internal" href="zerolatencyinterrupts.html">High Performance, Zero Latency Interrupts</a></li>
+<li class="toctree-l2"><a class="reference internal" href="nestedinterrupts.html">Nested Interrupts</a></li>
+<li class="toctree-l2"><a class="reference internal" href="cortexmhardfaults.html">Analyzing Cortex-M Hardfaults</a></li>
+<li class="toctree-l2"><a class="reference internal" href="coredump.html">Core Dump</a></li>
+<li class="toctree-l2"><a class="reference internal" href="minidumpserver.html">minidumpserver</a></li>
+<li class="toctree-l2"><a class="reference internal" href="gdbwithpython.html">GDB with Python</a></li>
+<li class="toctree-l2"><a class="reference internal" href="ofloader.html">Open Flash Loader</a></li>
+<li class="toctree-l2"><a class="reference internal" href="testingtcpip.html">Testing TCP/IP Network Stacks</a></li>
+<li class="toctree-l2"><a class="reference internal" href="automounter.html">Auto-Mounter</a></li>
+<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
+<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
+<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2 current"><a class="current reference internal" href="#">etc romfs</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="#configuration">Configuration</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#start-up-scripts">Start up Scripts</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#customizing-start-up-scripts">Customizing Start up Scripts</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#customizing-romfs-image">Customizing ROMFS Image</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
+</ul>
+
+ </div>
+ </div>
+ </nav>
+
+ <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap"><nav class="wy-nav-top" aria-label="Mobile navigation menu" >
+ <i data-toggle="wy-nav-top" class="fa fa-bars"></i>
+ <a href="../index.html">NuttX</a>
+ </nav>
+
+ <div class="wy-nav-content">
+ <div class="rst-content">
+ <div role="navigation" aria-label="Page navigation">
+ <ul class="wy-breadcrumbs">
+ <li><a href="../index.html" class="icon icon-home" aria-label="Home"></a></li>
+ <li class="breadcrumb-item"><a href="index.html">Guides</a></li>
+ <li class="breadcrumb-item active">etc romfs</li>
+ <li class="wy-breadcrumbs-aside">
+ <a href="../_sources/guides/etcromfs.rst.txt" rel="nofollow"> View page source</a>
+ </li>
+ </ul>
+ <hr/>
+</div>
+ <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
+ <div itemprop="articleBody">
+
+ <section id="etc-romfs">
+<h1>etc romfs<a class="headerlink" href="#etc-romfs" title="Permalink to this heading"></a></h1>
+<p>The ROMFS image is the contents of the <code class="docutils literal notranslate"><span class="pre">/etc</span></code> directory, including the start-up script
+contains any command support by Nuttx, and other customized contents needed.</p>
+<section id="configuration">
+<h2>Configuration<a class="headerlink" href="#configuration" title="Permalink to this heading"></a></h2>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">CONFIG_NSH_ROMFS /* Mount a ROMFS file system at "/etc" and provide a system init script at</span>
+<span class="go"> "/etc/init.d.rc.sysinit" and a startup script at "etc/init.d/rcS". */</span>
+<span class="go">CONFIG_ETC_ROMFSMOUNTPT /* The default mountpoint for the ROMFS volume is "/etc", but that can be</span>
+<span class="go"> changed with this setting. This must be a absolute path beginning with '/'</span>
+<span class="go"> and enclosed in quotes. */</span>
+<span class="go">CONFIG_ETC_ROMFSDEVNO /* This is the minor number of the ROMFS block device. The default is '0'</span>
+<span class="go"> corresponding to "/dev/ram0". */</span>
+<span class="go">CONFIG_ETC_ROMFSSECTSIZE /* This is the sector size to use with the ROMFS volume. Since the default volume</span>
+<span class="go"> is very small, this defaults to 64 but should be increased if the ROMFS volume</span>
+<span class="go"> were to be become large. Any value selected must be a power of 2. */</span>
+</pre></div>
+</div>
+<p>This capability also depends on:</p>
+<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">CONFIG_DISABLE_MOUNTPOINT /* If mount point support is disabled, then you cannot mount any file systems. */</span>
+<span class="go">CONFIG_FS_ROMFS /* This option enables ROMFS file system support. */</span>
+</pre></div>
+</div>
+</section>
+<section id="start-up-scripts">
+<h2>Start up Scripts<a class="headerlink" href="#start-up-scripts" title="Permalink to this heading"></a></h2>
+<p><strong>Start-Up Script</strong>. The start-up script contains any command support by Nuttx
+(i.e., that you see when you enter ‘nsh> help’). The implementation that is provided is
+intended to provide great flexibility for the use of Start-Up files.
+This paragraph will discuss the general behavior when all of the
+configuration options are set to the default values.</p>
+<p>In this default case, enabling <code class="docutils literal notranslate"><span class="pre">CONFIG_ETC_ROMFS</span></code> will cause Nuttx to
+behave as follows at Nuttx start-up time:</p>
+<blockquote>
+<div><ul>
+<li><p>Nuttx will create a read-only RAM disk (a ROM disk), containing a tiny
+ROMFS file system containing the following:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>`--init.d/
+ `-- rcS
+ `-- rc.sysinit
+</pre></div>
+</div>
+<p>Where <code class="docutils literal notranslate"><span class="pre">rcS</span></code> is the start-up script.
+Where <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> is the system-init script.</p>
+</li>
+<li><p>Nuttx will then mount the ROMFS file system at <code class="docutils literal notranslate"><span class="pre">/etc</span></code>, resulting in:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>|--dev/
+| `-- ram0
+`--etc/
+ `--init.d/
+ `-- rcS
+ `-- rc.sysinit
+</pre></div>
+</div>
+</li>
+<li><p>By default, the contents of <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> script are:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span># Create a RAMDISK and mount it at /tmp
+
+mkrd -m 1 -s 512 1024
+mkfatfs /dev/ram1
+mount -t vfat /dev/ram1 /tmp
+</pre></div>
+</div>
+</li>
+<li><p>NSH will execute the script at <code class="docutils literal notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> at system
+init (before the first NSH prompt). After execution of the script,
+the root FS will look like:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>|--dev/
+| |-- ram0
+| `-- ram1
+|--etc/
+| `--init.d/
+| `-- rcS
+| `-- rc.sysinit
+`--tmp/
+</pre></div>
+</div>
+</li>
+</ul>
+</div></blockquote>
+<p><strong>Example Configurations</strong>. Here are some configurations that have
+<code class="docutils literal notranslate"><span class="pre">CONFIG_ETC_ROMFS=y</span></code> in the NuttX configuration file. They might
+provide useful examples:</p>
+<blockquote>
+<div><ul class="simple">
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/arm/stm32/hymini-stm32v/nsh2</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/arm/dm320/ntosd-dm320/nsh</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nsh</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nsh2</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nx</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/nx11</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/touchscreen</span></code></p></li>
+</ul>
+</div></blockquote>
+<p>In most of these cases, the configuration sets up the <em>default</em>
+<code class="docutils literal notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> and <code class="docutils literal notranslate"><span class="pre">/etc/init.d/rcS</span></code> script. The default
+script is here: <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code> and
+<code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code>. (The funny values in the rc.sysinit.template
+like <code class="docutils literal notranslate"><span class="pre">XXXMKRDMINORXXX</span></code> get replaced via <code class="docutils literal notranslate"><span class="pre">sed</span></code> at build time). This
+default configuration creates a ramdisk and mounts it at <code class="docutils literal notranslate"><span class="pre">/tmp</span></code> as
+discussed above.</p>
+</section>
+<section id="customizing-start-up-scripts">
+<h2>Customizing Start up Scripts<a class="headerlink" href="#customizing-start-up-scripts" title="Permalink to this heading"></a></h2>
+<p>In order to modify the start-up behavior, there are three things to study:</p>
+<blockquote>
+<div><ol class="arabic">
+<li><p><strong>Configuration Options.</strong> The additional <code class="docutils literal notranslate"><span class="pre">CONFIG_ETC_ROMFS</span></code>
+configuration options discussed with <cite>Configuration</cite></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> <strong>Script</strong>. The script
+<code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> creates <code class="docutils literal notranslate"><span class="pre">etc_romfs.c</span></code>. It is not
+automatically executed. If you want to change the configuration
+settings associated with creating and mounting the <code class="docutils literal notranslate"><span class="pre">/tmp</span></code>
+directory, then it will be necessary to re-generate this header file
+using the <code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.sh</span></code> script.</p>
+<p>The behavior of this script depends upon several things:</p>
+<ol class="arabic simple">
+<li><p>The configuration settings then installed configuration.</p></li>
+<li><p>The <code class="docutils literal notranslate"><span class="pre">genromfs</span></code> tool(available from
+<a class="reference external" href="http://romfs.sourceforge.net/">http://romfs.sourceforge.net</a>)
+or included within the NuttX buildroot toolchain. There is also a
+snapshot available in the NuttX tools repository
+<a class="reference external" href="https://bitbucket.org/nuttx/tools/src/master/genromfs-0.5.2.tar.gz">here</a>.</p></li>
+<li><p>The <code class="docutils literal notranslate"><span class="pre">xxd</span></code> tool that is used to generate the C header files (xxd
+is a normal part of a complete Linux or Cygwin installation,
+usually as part of the <code class="docutils literal notranslate"><span class="pre">vi</span></code> package).</p></li>
+<li><p>The file <code class="docutils literal notranslate"><span class="pre">include/arch/board/rc.sysinit.template</span></code> and
+the file <code class="docutils literal notranslate"><span class="pre">include/arch/board/rcs.template</span></code></p></li>
+</ol>
+</li>
+<li><p><code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code>. The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rc.sysinit.template</span></code>
+contains the general form of the <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> file; configured values
+are plugged into this template file to produce the final <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> file.</p>
+<p><code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>. The file <code class="docutils literal notranslate"><span class="pre">apps/nshlib/rcS.template</span></code> contains the
+general form of the <code class="docutils literal notranslate"><span class="pre">rcS</span></code> file; configured values are plugged into
+this template file to produce the final <code class="docutils literal notranslate"><span class="pre">rcS</span></code> file.</p>
+<p>To generate a custom <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code> and <code class="docutils literal notranslate"><span class="pre">rcS</span></code> file a copy of
+<code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> and <code class="docutils literal notranslate"><span class="pre">rcS.template</span></code> needs to
+be placed at <code class="docutils literal notranslate"><span class="pre">tools/</span></code> and changed according to the desired start-up
+behaviour. Running <code class="docutils literal notranslate"><span class="pre">tools/mkromfsimg.h</span></code> creates <code class="docutils literal notranslate"><span class="pre">etc_romfs.c</span></code>
+which needs to be copied to <code class="docutils literal notranslate"><span class="pre">arch/board/src</span></code> and compiled in Makefile</p>
+</li>
+</ol>
+</div></blockquote>
+<p>All of the startup-behavior is contained in <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> and
+<code class="docutils literal notranslate"><span class="pre">rcS.template</span></code>. The role of <code class="docutils literal notranslate"><span class="pre">mkromfsimg.sh</span></code> script is to (1) apply
+the specific configuration settings to <code class="docutils literal notranslate"><span class="pre">rc.sysinit.template</span></code> to create
+the final <code class="docutils literal notranslate"><span class="pre">rc.sysinit</span></code>, and <code class="docutils literal notranslate"><span class="pre">rcS.template</span></code> to create the final <code class="docutils literal notranslate"><span class="pre">rcS</span></code>,
+and (2) to generate the source file <code class="docutils literal notranslate"><span class="pre">etc_romfs.c</span></code> containing the ROMFS file
+system image. To do this, <code class="docutils literal notranslate"><span class="pre">mkromfsimg.sh</span></code> uses two tools that must be
+installed in your system:</p>
+<blockquote>
+<div><ol class="arabic simple">
+<li><p>The <code class="docutils literal notranslate"><span class="pre">genromfs</span></code> tool that is used to generate the ROMFS file system
+image.</p></li>
+<li><p>The <code class="docutils literal notranslate"><span class="pre">xxd</span></code> tool that is used to create the C header file.</p></li>
+</ol>
+</div></blockquote>
+</section>
+<section id="customizing-romfs-image">
+<h2>Customizing ROMFS Image<a class="headerlink" href="#customizing-romfs-image" title="Permalink to this heading"></a></h2>
+<p>The ROMFS image can be generated from the content in the corresponding
+<code class="docutils literal notranslate"><span class="pre">board/arch/board/board/src/etc</span></code> directory, and added by Makefile.</p>
+<p><strong>Example Configurations</strong>. Here are some configurations that have
+<code class="docutils literal notranslate"><span class="pre">CONFIG_ETC_ROMFS=y</span></code> in the NuttX configuration file. They might
+provide useful examples:</p>
+<blockquote>
+<div><ul class="simple">
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/risc-v/bl808/ox64/src/etc</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/risc-v/qemu-rv/rv-virt/src/etc</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/risc-v/esp32c3/esp32c3-devkit/src/etc</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/risc-v/k230/canmv230/src/etc</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/risc-v/jh7110/star64/src/etc</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/arm64/rk3399/nanopi_m4/src/etc</span></code></p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">boards/sim/sim/sim/src/etc</span></code></p></li>
+</ul>
+</div></blockquote>
+</section>
+</section>
+
+
+ </div>
+ </div>
+ <footer><div class="rst-footer-buttons" role="navigation" aria-label="Footer">
+ <a href="stackrecord.html" class="btn btn-neutral float-left" title="Run time stack statistics" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
+ <a href="../glossary.html" class="btn btn-neutral float-right" title="Glossary" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ </div>
+
+ <hr/>
+
+ <div role="contentinfo">
+ <p>© Copyright 2023, The Apache Software Foundation.</p>
+ </div>
+
+
+
+</footer>
+ </div>
+ </div>
+ </section>
+ </div>
+ <script>
+ jQuery(function () {
+ SphinxRtdTheme.Navigation.enable(true);
+ });
+ </script>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/content/docs/latest/guides/gdbwithpython.html b/content/docs/latest/guides/gdbwithpython.html
index e618d042..dc19f280 100644
--- a/content/docs/latest/guides/gdbwithpython.html
+++ b/content/docs/latest/guides/gdbwithpython.html
@@ -146,6 +146,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/index.html b/content/docs/latest/guides/index.html
index b5bb5f78..cb7c4914 100644
--- a/content/docs/latest/guides/index.html
+++ b/content/docs/latest/guides/index.html
@@ -141,6 +141,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
@@ -404,6 +405,13 @@
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html#notice">Notice</a></li>
</ul>
</li>
+<li class="toctree-l1"><a class="reference internal" href="etcromfs.html">etc romfs</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html#configuration">Configuration</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html#start-up-scripts">Start up Scripts</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html#customizing-start-up-scripts">Customizing Start up Scripts</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html#customizing-romfs-image">Customizing ROMFS Image</a></li>
+</ul>
+</li>
</ul>
</div>
</section>
diff --git a/content/docs/latest/guides/minidumpserver.html b/content/docs/latest/guides/minidumpserver.html
index 09efda16..a6651cde 100644
--- a/content/docs/latest/guides/minidumpserver.html
+++ b/content/docs/latest/guides/minidumpserver.html
@@ -147,6 +147,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/nestedinterrupts.html b/content/docs/latest/guides/nestedinterrupts.html
index 34e33628..92e66afd 100644
--- a/content/docs/latest/guides/nestedinterrupts.html
+++ b/content/docs/latest/guides/nestedinterrupts.html
@@ -148,6 +148,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/nfs.html b/content/docs/latest/guides/nfs.html
index 605fa5bc..01727a6f 100644
--- a/content/docs/latest/guides/nfs.html
+++ b/content/docs/latest/guides/nfs.html
@@ -147,6 +147,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/ofloader.html b/content/docs/latest/guides/ofloader.html
index 0609b5f7..b105a8e3 100644
--- a/content/docs/latest/guides/ofloader.html
+++ b/content/docs/latest/guides/ofloader.html
@@ -147,6 +147,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/pysimcoder.html b/content/docs/latest/guides/pysimcoder.html
index a1f5777f..95525758 100644
--- a/content/docs/latest/guides/pysimcoder.html
+++ b/content/docs/latest/guides/pysimcoder.html
@@ -146,6 +146,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
@@ -246,7 +247,7 @@ with NuttX. The list is the following:</p>
<td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_READLINE=y</span></code></p></td>
</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_BUILTIN=y</span></code></p></td>
-<td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC=y</span></code></p></td>
+<td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_ETC_ROMFS=y</span></code></p></td>
</tr>
<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_ELF=y</span></code></p></td>
<td><p><code class="docutils literal notranslate"><span class="pre">CONFIG_PSEUDOTERM=y</span></code></p></td>
diff --git a/content/docs/latest/guides/qemugdb.html b/content/docs/latest/guides/qemugdb.html
index 3d911237..7ac7fd80 100644
--- a/content/docs/latest/guides/qemugdb.html
+++ b/content/docs/latest/guides/qemugdb.html
@@ -146,6 +146,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/rndis.html b/content/docs/latest/guides/rndis.html
index 1e02b256..5817a4fa 100644
--- a/content/docs/latest/guides/rndis.html
+++ b/content/docs/latest/guides/rndis.html
@@ -146,6 +146,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/simulator.html b/content/docs/latest/guides/simulator.html
index 55346265..425596a3 100644
--- a/content/docs/latest/guides/simulator.html
+++ b/content/docs/latest/guides/simulator.html
@@ -149,6 +149,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/stackrecord.html b/content/docs/latest/guides/stackrecord.html
index 792aef96..dd38b659 100644
--- a/content/docs/latest/guides/stackrecord.html
+++ b/content/docs/latest/guides/stackrecord.html
@@ -44,7 +44,7 @@
<script src="../_static/js/theme.js"></script>
<link rel="index" title="Index" href="../genindex.html" />
<link rel="search" title="Search" href="../search.html" />
- <link rel="next" title="Glossary" href="../glossary.html" />
+ <link rel="next" title="etc romfs" href="etcromfs.html" />
<link rel="prev" title="STM32 CCM Allocator" href="stm32ccm.html" />
</head>
@@ -148,6 +148,7 @@
<li class="toctree-l3"><a class="reference internal" href="#notice">Notice</a></li>
</ul>
</li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
@@ -261,7 +262,7 @@ the entry function with the noinstrument_function flag to prevent instrumentatio
</div>
<footer><div class="rst-footer-buttons" role="navigation" aria-label="Footer">
<a href="stm32ccm.html" class="btn btn-neutral float-left" title="STM32 CCM Allocator" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
- <a href="../glossary.html" class="btn btn-neutral float-right" title="Glossary" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
+ <a href="etcromfs.html" class="btn btn-neutral float-right" title="etc romfs" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
</div>
<hr/>
diff --git a/content/docs/latest/guides/stm32ccm.html b/content/docs/latest/guides/stm32ccm.html
index 9bc92480..cca99c46 100644
--- a/content/docs/latest/guides/stm32ccm.html
+++ b/content/docs/latest/guides/stm32ccm.html
@@ -147,6 +147,7 @@
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/stm32nullpointer.html b/content/docs/latest/guides/stm32nullpointer.html
index ba182c01..9a9b83b3 100644
--- a/content/docs/latest/guides/stm32nullpointer.html
+++ b/content/docs/latest/guides/stm32nullpointer.html
@@ -148,6 +148,7 @@
</li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/tasktrace.html b/content/docs/latest/guides/tasktrace.html
index 6da9e6bd..5a8bbf1f 100644
--- a/content/docs/latest/guides/tasktrace.html
+++ b/content/docs/latest/guides/tasktrace.html
@@ -145,6 +145,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/tasktraceinternal.html b/content/docs/latest/guides/tasktraceinternal.html
index 7bb97031..80e4ea93 100644
--- a/content/docs/latest/guides/tasktraceinternal.html
+++ b/content/docs/latest/guides/tasktraceinternal.html
@@ -160,6 +160,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/tasktraceuser.html b/content/docs/latest/guides/tasktraceuser.html
index 39b2d8d9..42a06740 100644
--- a/content/docs/latest/guides/tasktraceuser.html
+++ b/content/docs/latest/guides/tasktraceuser.html
@@ -166,6 +166,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/testingtcpip.html b/content/docs/latest/guides/testingtcpip.html
index 4dbee29a..b58af84b 100644
--- a/content/docs/latest/guides/testingtcpip.html
+++ b/content/docs/latest/guides/testingtcpip.html
@@ -147,6 +147,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/usbtrace.html b/content/docs/latest/guides/usbtrace.html
index 7c813091..cdfbd921 100644
--- a/content/docs/latest/guides/usbtrace.html
+++ b/content/docs/latest/guides/usbtrace.html
@@ -141,6 +141,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/guides/zerolatencyinterrupts.html b/content/docs/latest/guides/zerolatencyinterrupts.html
index 2cb4e51a..68d6c639 100644
--- a/content/docs/latest/guides/zerolatencyinterrupts.html
+++ b/content/docs/latest/guides/zerolatencyinterrupts.html
@@ -155,6 +155,7 @@
<li class="toctree-l2"><a class="reference internal" href="stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index 4583c64a..1d8bce9b 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -163,7 +163,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: 21 January 24 at 00:13</p>
+<p>Last Updated: 22 January 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">
@@ -316,6 +316,7 @@ as fork()).</p>
<li class="toctree-l2"><a class="reference internal" href="guides/stm32nullpointer.html">STM32 Null Pointer Detection</a></li>
<li class="toctree-l2"><a class="reference internal" href="guides/stm32ccm.html">STM32 CCM Allocator</a></li>
<li class="toctree-l2"><a class="reference internal" href="guides/stackrecord.html">Run time stack statistics</a></li>
+<li class="toctree-l2"><a class="reference internal" href="guides/etcromfs.html">etc romfs</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="glossary.html">Glossary</a></li>
diff --git a/content/docs/latest/objects.inv b/content/docs/latest/objects.inv
index 497a75db..cf67116e 100644
Binary files a/content/docs/latest/objects.inv and b/content/docs/latest/objects.inv differ
diff --git a/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-grrose/index.html b/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-grrose/index.html
index f73ed83c..ffb64aeb 100644
--- a/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-grrose/index.html
+++ b/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-grrose/index.html
@@ -607,7 +607,7 @@ endif
--------
This directory contains logic to support a custom ROMFS system-init script
and start-up script. These scripts are used by by the NSH when it starts
- provided that CONFIG_NSH_ARCHROMFS=y. These scripts provide a ROMFS volume
+ provided that CONFIG_ETC_ROMFS=y. These scripts provide a ROMFS volume
that will be mounted at /etc and will look like this at run-time:
NuttShell (NSH) NuttX-8.2
diff --git a/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-rsk2mb/index.html b/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-rsk2mb/index.html
index 05d24db2..c5cb1d50 100644
--- a/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-rsk2mb/index.html
+++ b/content/docs/latest/platforms/renesas/rx65n/boards/rx65n-rsk2mb/index.html
@@ -579,7 +579,7 @@ endif
--------
This directory contains logic to support a custom ROMFS system-init script
and start-up script. These scripts are used by by the NSH when it starts
- provided that CONFIG_NSH_ARCHROMFS=y. These scripts provide a ROMFS volume
+ provided that CONFIG_ETC_ROMFS=y. These scripts provide a ROMFS volume
that will be mounted at /etc and will look like this at run-time:
NuttShell (NSH) NuttX-8.2
diff --git a/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.html b/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.html
index 1eea67f3..a600512a 100644
--- a/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.html
+++ b/content/docs/latest/platforms/risc-v/esp32c3/boards/esp32c3-devkit/index.html
@@ -716,7 +716,7 @@ nsh> renew wlan0
--------
This directory contains logic to support a custom ROMFS system-init script
and start-up script. These scripts are used by by the NSH when it starts
- provided that CONFIG_NSH_ARCHROMFS=y. These scripts provide a ROMFS volume
+ provided that CONFIG_ETC_ROMFS=y. These scripts provide a ROMFS volume
that will be mounted at /etc and will look like this at run-time:
NuttShell (NSH) NuttX-10.1.0-RC1
diff --git a/content/docs/latest/platforms/sim/sim/boards/sim/index.html b/content/docs/latest/platforms/sim/sim/boards/sim/index.html
index 06f5a728..f9a1986a 100644
--- a/content/docs/latest/platforms/sim/sim/boards/sim/index.html
+++ b/content/docs/latest/platforms/sim/sim/boards/sim/index.html
@@ -1196,7 +1196,7 @@ apps/nshlib/nsh_consolemain.c like:</p>
@@ -117,7 +117,8 @@
/* Execute the startup script */
- #ifdef CONFIG_NSH_ROMFSETC
+ #ifdef CONFIG_ETC_ROMFS
- nsh_script(&pstate->cn_vtbl, "init", NSH_INITPATH);
+// REMOVE ME
+// nsh_script(&pstate->cn_vtbl, "init", NSH_INITPATH);
@@ -1967,7 +1967,7 @@ Then you can use /dev/ttyACM to transfer data.</p>
--------
This directory contains logic to support a custom ROMFS system-init script
and start-up script. These scripts are used by by the NSH when it starts
- provided that CONFIG_NSH_ARCHROMFS=y. These scripts provide a ROMFS volume
+ provided that CONFIG_ETC_ROMFS=y. These scripts provide a ROMFS volume
that will be mounted at /etc and will look like this at run-time:
NuttShell (NSH) NuttX-7.31
diff --git a/content/docs/latest/platforms/x86_64/qemu/boards/qemu-intel64/index.html b/content/docs/latest/platforms/x86_64/qemu/boards/qemu-intel64/index.html
index 967fc3c3..331f01be 100644
--- a/content/docs/latest/platforms/x86_64/qemu/boards/qemu-intel64/index.html
+++ b/content/docs/latest/platforms/x86_64/qemu/boards/qemu-intel64/index.html
@@ -179,192 +179,164 @@
<section id="qemu-intel64">
<h1>qemu-intel64<a class="headerlink" href="#qemu-intel64" title="Permalink to this heading"></a></h1>
-<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>README
-======
-
-This README file describes the contents of the build configurations available
-for the NuttX QEMU x86_64 port.
-
-Contents
-========
-
- * Creating a bootable disk
- * QEMU/KVM
- - Running QEMU/KVM
- * Bochs
- - Building Bochs
- - Running Bochs
- * Real machine
- * Toolchain
- * FAQ
- * Configurations
- - ostest
-
-Creating a bootable disk
-========================
-
-This build supports multiboot2, which means that usual multiboot2 bootlaoders, e.g. grub can be used.
-To create a bootable disk with grub2, create a directory named `iso` with grub configuration file and the compiled nuttx.elf.
-
-##### Directory and file hierarchy
-```
- - iso/
- - boot/
- - grub/
- - grub.cfg
- - nuttx.elf
-```
-
-##### grub.cfg
-
-The grub.cfg should contain the boot entry of NuttX.
-```
-set timeout=0
+<p>This page file describes the contents of the build configurations available
+for the NuttX QEMU x86_64 port.</p>
+<section id="creating-a-bootable-disk">
+<h2>Creating a bootable disk<a class="headerlink" href="#creating-a-bootable-disk" title="Permalink to this heading"></a></h2>
+<p>This build supports multiboot2, which means that usual multiboot2 bootlaoders,
+e.g. grub can be used. To create a bootable disk with grub2, create a directory
+named <code class="docutils literal notranslate"><span class="pre">iso</span></code> with grub configuration file and the compiled <code class="docutils literal notranslate"><span class="pre">nuttx.elf</span></code>.</p>
+<p>Directory and file hierarchy:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>- iso/
+ - boot/
+ - grub/
+ - grub.cfg
+ - nuttx.elf
+</pre></div>
+</div>
+<p>The grub.cfg should contain the boot entry of NuttX:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>set timeout=0
set default=0
menuentry "kernel" {
multiboot2 /boot/nuttx.elf
}
-```
-
-##### Making the disk
-
-Use the following command to create the disk.
-P.S. In some distros, `grub-mkrescue` is called `grub2-mkrescue`
-```
-grub-mkrescue -o boot.iso iso
-```
-
-QEMU/KVM
-====
-
-QEMU is a generic and open source machine emulator and virtual machine. Here are
-some links (which will probably be mostly outdated by the time your read this):
-
- Home Page: http://wiki.qemu.org/Main_Page
- Downloads: http://wiki.qemu.org/Download
- Documentation: http://wiki.qemu.org/Manual
-
-KVM is the Linux kernel hypervisor.
+</pre></div>
+</div>
+<section id="making-the-disk">
+<h3>Making the disk<a class="headerlink" href="#making-the-disk" title="Permalink to this heading"></a></h3>
+<p>Use the following command to create the disk.
+P.S. In some distros, <code class="docutils literal notranslate"><span class="pre">grub-mkrescue</span></code> is called <code class="docutils literal notranslate"><span class="pre">grub2-mkrescue</span></code>:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>grub-mkrescue -o boot.iso iso
+</pre></div>
+</div>
+</section>
+</section>
+<section id="qemu-kvm">
+<h2>QEMU/KVM<a class="headerlink" href="#qemu-kvm" title="Permalink to this heading"></a></h2>
+<p>QEMU is a generic and open source machine emulator and virtual machine. Here are
+some links (which will probably be mostly outdated by the time your read this):</p>
+<ul class="simple">
+<li><p>Home Page: <a class="reference external" href="http://wiki.qemu.org/Main_Page">http://wiki.qemu.org/Main_Page</a></p></li>
+<li><p>Downloads: <a class="reference external" href="http://wiki.qemu.org/Download">http://wiki.qemu.org/Download</a></p></li>
+<li><p>Documentation: <a class="reference external" href="http://wiki.qemu.org/Manual">http://wiki.qemu.org/Manual</a></p></li>
+</ul>
+<p>KVM is the Linux kernel hypervisor.
It supports creations of virtual machines in Linux systems.
-It is usually coupled with Qemu as its I/O supporting layer.
-
-The qemu can be build from source or downloaded from distro repositories.
-However, a modern CPU and KVM support are mandatory because the X2APIC is not available
-in pure emulator mode.
-This mean using this build with qemu in windows or old x86 machine can be frustrating.
-In such case, looks the next section and use bochs emulator instead.
-
-Running QEMU
-------------
-
- In the top-level NuttX directory:
-
- qemu-system-x86_64 -cpu host -enable-kvm -m 2G -cdrom boot.iso -nographic -serial mon:stdio
-
- This multiplex the qemu console and COM1 to your console.
- Use control-a 1 and 2 to switch between.
- Use control-a x to terminate the emulation.
-
- P.S. Make sure that you CPU supports the mandatory features. Look at Real machine
- section for more information.
-
-Bochs
-=====
-
-Bochs is also a generic and open source machine emulator and virtualizer.
+It is usually coupled with Qemu as its I/O supporting layer.</p>
+<p>The qemu can be build from source or downloaded from distro repositories.
+However, a modern CPU and KVM support are mandatory because the X2APIC is not
+available in pure emulator mode.
+This mean using this build with qemu in windows or old x86 machine can be
+frustrating. In such case, looks the next section and use bochs emulator instead.</p>
+<section id="running-qemu">
+<h3>Running QEMU<a class="headerlink" href="#running-qemu" title="Permalink to this heading"></a></h3>
+<p>In the top-level NuttX directory:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>qemu-system-x86_64 -cpu host -enable-kvm -m 2G -cdrom boot.iso -nographic -serial mon:stdio
+</pre></div>
+</div>
+<p>This multiplex the qemu console and COM1 to your console.</p>
+<p>Use control-a 1 and 2 to switch between.
+Use control-a x to terminate the emulation.</p>
+<p>P.S. Make sure that you CPU supports the mandatory features. Look at Real machine
+section for more information.</p>
+</section>
+</section>
+<section id="bochs">
+<h2>Bochs<a class="headerlink" href="#bochs" title="Permalink to this heading"></a></h2>
+<p>Bochs is also a generic and open source machine emulator and virtualizer.
It does very comprehensive emulation of x86 platform, even the state-of-art processors.
-Here are some links (which will probably be mostly outdated by the time your read this):
-
- Home Page: http://bochs.sourceforge.net
-
-The bochs can be build from source.
-Unlike qemu, it does not rely on KVM to support modern hardware features, therefore it can
-also be used under Windows.
-When building bochs, remember to enable x86-64 support with "--enable-x86-64".
-If you also want support for SIMD instructions, enable them with "--enable-avx --enable-evex".
-
-Running Bochs
-------------
-
- First edit/check the .bochsrc
- You can create one in the top-level NuttX directory or bochs will use the one in your $HOME.
- Remember to change the CPU model to one with mandatory features and enable the COM port.
-
- * Find and edit (You might adjust the IPS as you machine perform):
- ```
- cpu: model=broadwell_ult, count=1, ips=50000000, reset_on_triple_fault=0, ignore_bad_msrs=0, msrs="msrs.def" a
- ata0-master: type=cdrom, path="<PATH TO boot.iso>", status=inserted
-
- ```
-
- * Add:
- ```
- com1: enabled=1, mode=file, dev=com1.out
- ```
-
- In the top-level NuttX directory:
-
- ```
- bochs
- ```
-
- The emulator will drop into debugger mode.
- Enter 'c' to start the emulation.
- COM port output will be in the com1.out file.
-
-Real machine
-============
-
-This port should work on real x86-64 machine with a proper CPU.
-The mandatory CPU features are:
- * TSC DEADLINE or APIC timer
- * PCID
- * X2APIC
-
-WARNING: IF you use TSC DEADLINE, make sure that your CPU's TSC DEADLINE timer is not buggy!
-
-Toolchains
-==========
-
- Currently, only the Linux GCC toolchain is tested.
- While building on a modern x86_64 PC, the default system GCC can be used.
-
-Configurations
-==============
-
-Common Configuration Notes
---------------------------
-
- 1. Each Qemu-intel64 configuration is maintained in a sub-directory
- and can be selected as follow:
-
- tools/configure.sh qemu-intel64:<subdir>
-
- Where <subdir> is one of the configuration sub-directories described in
- the following paragraph.
-
- 2. These configurations use the mconf-based configuration tool. To
- change a configurations using that tool, you should:
-
- a. Build and install the kconfig-mconf tool. See nuttx/README.txt
- see additional README.txt files in the NuttX tools repository.
-
- b. Execute 'make menuconfig' in nuttx/ in order to start the
- reconfiguration process.
-
- 3. By default, all configurations assume the Linux. This is easily
- reconfigured:
-
- CONFIG_HOST_LINUX=y
-
-Configuration Sub-Directories
------------------------------
-
- ostest
-
- The "standard" NuttX examples/ostest configuration.
+Here are some links (which will probably be mostly outdated by the time your read this):</p>
+<ul class="simple">
+<li><p>Home Page: <a class="reference external" href="http://bochs.sourceforge.net">http://bochs.sourceforge.net</a></p></li>
+</ul>
+<p>The bochs can be build from source.
+Unlike qemu, it does not rely on KVM to support modern hardware features,
+therefore it can also be used under Windows.
+When building bochs, remember to enable x86-64 support with <code class="docutils literal notranslate"><span class="pre">--enable-x86-64</span></code>.
+If you also want support for SIMD instructions, enable them with <code class="docutils literal notranslate"><span class="pre">--enable-avx</span> <span class="pre">--enable-evex</span></code>.</p>
+<section id="running-bochs">
+<h3>Running Bochs<a class="headerlink" href="#running-bochs" title="Permalink to this heading"></a></h3>
+<p>First edit/check the <code class="docutils literal notranslate"><span class="pre">.bochsrc</span></code>
+You can create one in the top-level NuttX directory or bochs will use the one in your $HOME.
+Remember to change the CPU model to one with mandatory features and enable the COM port.</p>
+<ul>
+<li><p>Find and edit (You might adjust the IPS as you machine perform):</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>cpu: model=broadwell_ult, count=1, ips=50000000, reset_on_triple_fault=0, ignore_bad_msrs=0, msrs="msrs.def"
+ata0-master: type=cdrom, path="<PATH TO boot.iso>", status=inserted
+</pre></div>
+</div>
+</li>
+<li><p>Add:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>com1: enabled=1, mode=file, dev=com1.out
+</pre></div>
+</div>
+</li>
+<li><p>In the top-level NuttX directory:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>bochs
+</pre></div>
+</div>
+</li>
+</ul>
+<p>The emulator will drop into debugger mode.
+Enter <code class="docutils literal notranslate"><span class="pre">c</span></code> to start the emulation.
+COM port output will be in the com1.out file.</p>
+</section>
+</section>
+<section id="real-machine">
+<h2>Real machine<a class="headerlink" href="#real-machine" title="Permalink to this heading"></a></h2>
+<p>This port should work on real x86-64 machine with a proper CPU.
+The mandatory CPU features are:</p>
+<ul class="simple">
+<li><p>TSC DEADLINE or APIC timer</p></li>
+<li><p>PCID</p></li>
+<li><p>X2APIC</p></li>
+</ul>
+<p>WARNING: IF you use TSC DEADLINE, make sure that your CPU’s TSC DEADLINE timer
+is not buggy!</p>
+</section>
+<section id="toolchains">
+<h2>Toolchains<a class="headerlink" href="#toolchains" title="Permalink to this heading"></a></h2>
+<p>Currently, only the Linux GCC toolchain is tested.
+While building on a modern x86_64 PC, the default system GCC can be used.</p>
+</section>
+<section id="configurations">
+<h2>Configurations<a class="headerlink" href="#configurations" title="Permalink to this heading"></a></h2>
+<section id="common-configuration-notes">
+<h3>Common Configuration Notes<a class="headerlink" href="#common-configuration-notes" title="Permalink to this heading"></a></h3>
+<ol class="arabic">
+<li><p>Each Qemu-intel64 configuration is maintained in a sub-directory
+and can be selected as follow:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>tools/configure.sh qemu-intel64:<subdir>
+</pre></div>
+</div>
+<p>Where <code class="docutils literal notranslate"><span class="pre"><subdir></span></code> is one of the configuration sub-directories described in
+the following paragraph.</p>
+</li>
+<li><p>These configurations use the mconf-based configuration tool. To
+change a configurations using that tool, you should:</p>
+<ol class="loweralpha simple">
+<li><p>Build and install the kconfig-mconf tool. See nuttx/README.txt
+see additional README.txt files in the NuttX tools repository.</p></li>
+<li><p>Execute <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">menuconfig</span></code> in nuttx/ in order to start the
+reconfiguration process.</p></li>
+</ol>
+</li>
+<li><p>By default, all configurations assume the Linux. This is easily
+reconfigured:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>CONFIG_HOST_LINUX=y
</pre></div>
</div>
+</li>
+</ol>
+</section>
+<section id="configuration-sub-directories">
+<h3>Configuration Sub-Directories<a class="headerlink" href="#configuration-sub-directories" title="Permalink to this heading"></a></h3>
+</section>
+<section id="ostest">
+<h3>ostest<a class="headerlink" href="#ostest" title="Permalink to this heading"></a></h3>
+<p>The “standard” NuttX examples/ostest configuration.</p>
+</section>
+</section>
</section>
diff --git a/content/docs/latest/searchindex.js b/content/docs/latest/searchindex.js
index 47c58a7e..6b35a6c0 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/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/feed.xml b/content/feed.xml
index abcaafae..dbadf2a7 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>Sun, 21 Jan 2024 00:15:19 +0000</pubDate>
- <lastBuildDate>Sun, 21 Jan 2024 00:15:19 +0000</lastBuildDate>
+ <pubDate>Mon, 22 Jan 2024 00:14:29 +0000</pubDate>
+ <lastBuildDate>Mon, 22 Jan 2024 00:14:29 +0000</lastBuildDate>
<generator>Jekyll v4.3.2</generator>
<item>