apps/examples/hello.
The main routine for apps/examples/hello can be found in apps/examples/hello/main.c.
- When CONFIG_EXAMPLES_HELLO_BUILTIN is defined, this main routine simplifies to:
+ The main routine is:
int hello_main(int argc, char *argv[])
@@ -3165,10 +3165,8 @@ STACKSIZE = 2048
.context: -ifeq ($(CONFIG_EXAMPLES_HELLO_BUILTIN),y) $(call REGISTER,$(APPNAME),$(PRIORITY),$(STACKSIZE),$(APPNAME)_main) @touch $@ -endif@@ -3189,7 +3187,7 @@ endif CONFIG_BUILTIN_APP_START=<application name>
- that application will be invoked immediately after system starts instead of the normal, default user_start() entry point.
+ 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.
You replace the sample code at apps/examples/nsh/nsh_main.c with whatever start-up logic that you want.
NSH is a library at apps/nshlib.
- apps.examplex/nsh is just a tiny, example start-up function (user_start()) that that runs immediately and illustrates how to start NSH
- If you want something else to run immediately then you can write your write your own custom user_start() function and then start other tasks from your custom user_start().
+ apps.examplex/nsh is just a tiny, example start-up function (CONFIG_USER_ENTRYPOINT()) that that runs immediately and illustrates how to start NSH
+ If you want something else to run immediately then you can write your write your own custom CONFIG_USER_ENTRYPOINT() function and then start other tasks from your custom CONFIG_USER_ENTRYPOINT().
diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html
index bfde229edc9..532da8c16ce 100644
--- a/Documentation/NuttxPortingGuide.html
+++ b/Documentation/NuttxPortingGuide.html
@@ -4085,6 +4085,14 @@ build
CONFIG_SCHED_ONEXIT_MAX: By default if CONFIG_SCHED_ONEXIT is selected, only a single on_exit() function is supported.
That number can be increased by defined this setting to the number that you require.
CONFIG_USER_ENTRYPOINT: The name of the entry point for user
+ applications.
+ For the example applications this is of the form app_main
+ where app is the application name.
+ If not defined, CONFIG_USER_ENTRYPOINT defaults to
+ user_start.
+ @@ -5792,13 +5800,14 @@ build
CONFIG_IDLETHREAD_STACKSIZE: The size of the initial stack.
This is the thread that (1) performs the initial boot of the system up
- to the point where user_start() is spawned, and (2) there after is the
- IDLE thread that executes only when there is no other thread ready to
- run.
+ to the point where CONFIG_USER_ENTRYPOINT() is spawned,
+ and (2) there after is the IDLE thread that executes only when there
+ is no other thread ready to run.
CONFIG_USERMAIN_STACKSIZE: The size of the stack to allocate
- for the main user thread that begins at the user_start() entry point.
+ for the main user thread that begins at the CONFIG_USER_ENTRYPOINT()
+ entry point.
CONFIG_PTHREAD_STACK_MIN: Minimum pthread stack size
diff --git a/Documentation/UsbTrace.html b/Documentation/UsbTrace.html
index 6d170044f59..ec48e260dd7 100644
--- a/Documentation/UsbTrace.html
+++ b/Documentation/UsbTrace.html
@@ -150,7 +150,7 @@
user_start: Registering USB serial driverusbserial_main: Registering USB serial driveruser_start: Successfully registered the serial driverusbserial_main: Successfully registered the serial driveruser_start: ERROR: Failed to open /dev/ttyUSB0 for reading: 107usbserial_main: ERROR: Failed to open /dev/ttyUSB0 for reading: 107user_start: Not connected. Wait and try again.usbserial_main: Not connected. Wait and try again.