OrgApache/incubator-nuttx
OrgApache
/
incubator-nuttx
mirror of https://github.com/apache/incubator-nuttx.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Remove CONFIG_BUILTIN_APPS_START 

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5482 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2013-01-06 17:00:08 +00:00
parent e47a801fd1
commit 50a2131b78
1 changed files with 3 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
Documentation/NuttShell.html
View File

@ -3421,29 +3421,10 @@ context:
<p> <p>
<b>Other Uses of Built-In Application.</b> <b>Other Uses of Built-In Application.</b>
The primary purpose of builtin applications is to support command line execution of applications from NSH. The primary purpose of builtin applications is to support command line execution of applications from NSH.
However, there are two other uses of builtin applications that should be mentioned. However, there is one other use of builtin applications that should be mentioned.
</p> </p>
<ol> <ol>
<li>
<p>
<b>Built-In Application Start-Up <code>main()</code> function</b>.
A builtin application can even be used as the main, start-up entry point into your embedded software.
When the user defines this option in the NuttX configuration file:
</p>
<ul><pre>
CONFIG_BUILTIN_APP_START=&lt;application name&gt;
</pre></ul>
<p>
that application will be invoked immediately after system starts instead of the default <code>CONFIG_USER_ENTRYPOINT</code>() entry point.
Note that <code>&lt;application name&gt;</code> must be provided just as it would have been on the NSH command line.
For example, <code>hello</code> would result in <code>hello_main()</code> being started at power-up.
</p>
<p>
This option might be useful in some develop environments where you use NSH only during the debug phase, but want to eliminate NSH in the final product.
Setting <code>CONFIG_BUILTIN_APP_START</code> in this way will bypass NSH and execute your application just as if it were entered from the NSH command line.
</p>
<li> <li>
<p><b><i>binfs</i></b>. <p><b><i>binfs</i></b>.
<i>binfs</i> is a tiny file system located at <code>apps/builtin/binfs.c</code>. <i>binfs</i> is a tiny file system located at <code>apps/builtin/binfs.c</code>.
@ -3452,7 +3433,8 @@ CONFIG_BUILTIN_APP_START=&lt;application name&gt;
<i>binfs</i> will create a tiny pseudo-file system mounted at <code>/bin</code>. <i>binfs</i> will create a tiny pseudo-file system mounted at <code>/bin</code>.
Using <i>binfs</i>, you can see the available builtin applications by listing the contents of <code>/bin</code> directory. Using <i>binfs</i>, you can see the available builtin applications by listing the contents of <code>/bin</code> directory.
This gives some superficial Unix compatibility, but does not really add any new functionality. This gives some superficial Unix compatibility, but does not really add any new functionality.
</p> </p>
</li>
</ol> </ol>
<h3>4.3.2 Synchronous Built-In Applications</h3> <h3>4.3.2 Synchronous Built-In Applications</h3>
@ -3770,7 +3752,6 @@ mount -t vfat /dev/ram1 /tmp
<li><a href="#commands">Command summaries</a></li> <li><a href="#commands">Command summaries</a></li>
<li><a href="#custoncmds">Command table</a></li> <li><a href="#custoncmds">Command table</a></li>
<li><a href="#conditional">Conditional command execution</a></li> <li><a href="#conditional">Conditional command execution</a></li>
<li><a href="#custapps"><code>CONFIG_BUILTIN_APP_START</code></a></li>
<li><a href="#custinit"><code>CONFIG_DISABLE_MOUNTPOINT</code></a></li> <li><a href="#custinit"><code>CONFIG_DISABLE_MOUNTPOINT</code></a></li>
<li><a href="#custinit"><code>CONFIG_FS_ROMFS</code></a></li> <li><a href="#custinit"><code>CONFIG_FS_ROMFS</code></a></li>
<li><a href="#custinit"><code>CONFIG_NFILE_DESCRIPTORS</code></a></li> <li><a href="#custinit"><code>CONFIG_NFILE_DESCRIPTORS</code></a></li>