What you describe applies only to the FLAT build. NuttX initialization is very different with the KERNEL builds (and a little different with PROTECTED builds). In the KERNEL build case, binaries can only be executed from a file system and, in that case initialization involves executing a file in the file system (per CONFIG_INIT_FILE mounted at CONFIG_INIT_MOUNT_TARGET). ________________________________ From: Tomek CEDRO <[email protected]> Sent: Monday, October 20, 2025 4:05 AM To: [email protected] <[email protected]> Subject: NuttX and Android System Init
Hello world :-) There is a very interesting and useful PR by @JianyuWang0623 that adds support for Android System Init functionality to NuttX [1][2] with working example on qemu [3]. This is alternative to SystemV Init and probably other init designs. Please help in reviewing the change :-) My only concern is naming convention here because just "system" and "system init" is used (i.e. CONFIG_SYSTEM_INIT, CONFIG_SYSTEM_SYSTEM). This may be a bit confusing because we do not know what init system standard is used and we silently assume Android. My proposition is to use "Android System Init" naming convention (i.e. CONFIG_SYSTEM_ANDROID_INIT or something like that), so things are self-explanatory, and other init systems may be used when necessary in future without confusion. I am not insisting here and will follow the community choice. Please let us know what you think :-) Thanks :-) Tomek [1] https://github.com/apache/nuttx-apps/pull/3192 [2] https://github.com/apache/nuttx/pull/17215 [3] https://github.com/apache/nuttx/pull/17215 -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
