diff --git a/Documentation/NuttShell.html b/Documentation/NuttShell.html index 7ad96da79b6..95a75b22c51 100644 --- a/Documentation/NuttShell.html +++ b/Documentation/NuttShell.html @@ -3421,29 +3421,10 @@ context:
Other Uses of Built-In Application. 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.
- Built-In Application Start-Up main() function.
- 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:
-
-CONFIG_BUILTIN_APP_START=<application name> --
- that application will be invoked immediately after system starts instead of the default CONFIG_USER_ENTRYPOINT() entry point.
- Note that <application name> must be provided just as it would have been on the NSH command line.
- For example, hello would result in hello_main() being started at power-up.
-
- 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 CONFIG_BUILTIN_APP_START in this way will bypass NSH and execute your application just as if it were entered from the NSH command line.
-
binfs.
binfs is a tiny file system located at apps/builtin/binfs.c.
@@ -3452,7 +3433,8 @@ CONFIG_BUILTIN_APP_START=<application name>
binfs will create a tiny pseudo-file system mounted at /bin.
Using binfs, you can see the available builtin applications by listing the contents of /bin directory.
This gives some superficial Unix compatibility, but does not really add any new functionality.
-
CONFIG_BUILTIN_APP_STARTCONFIG_DISABLE_MOUNTPOINTCONFIG_FS_ROMFSCONFIG_NFILE_DESCRIPTORS