Junbo-Zheng opened a new pull request, #21744:
URL: https://github.com/apache/nuttx/pull/21744

   
   ## Summary
   
   Use `init_main` as the init entrypoint, with the console shell
   started as an nxinit service from the `/etc/init.d/init.rc` baked
   into the ROMFS -- the same arrangement the esp32s3 boards already
   use after their "switch defconfigs to nxinit entrypoint"
   conversions.
   
   
   ## Impact
   
   - **Users**: the board boots through nxinit; the console NSH is now
     a supervised service (restarted on failure, `restart_period`
     1000 ms) instead of being the init task itself.  The interactive
     experience is unchanged.
   - **Build**: the esp32 common ROMFS packing gains the init.rc entry
     when `CONFIG_SYSTEM_NXINIT` is set; no other board changes.
   - **Hardware**: esp32-m5-stickc-plus only.
   - **Documentation**: None.
   - **Security & Compatibility**: None.
   
   ## Testing
   
   CMake build, flashed on an M5StickC Plus:
   
   ```
   cmake -B build -DBOARD_CONFIG=esp32-m5-stickc-plus:nsh -G Ninja
   cmake --build build -j
   ```
   
   ```
   nsh> ps
     TID   PID  PPID PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK        
    STACK COMMAND
       0     0     0   0 FIFO     Kthread   - Ready              
0000000000000000 0003040 Idle_Task
       2     2     0 100 RR       Task      - Waiting  Semaphore 
0000000000000000 0003008 init_main
       3     3     2 100 RR       Task      - Running            
0000000000000000 0008136 sh
   
   nsh> uname -a
   NuttX 12.13.0 3117ab10467 Nov 12 2026 10:06:46 xtensa esp32-m5-stickc-plus
   ```
   
   `reboot` comes back to the same state: init_main respawns the
   console service from `/etc/init.d/init.rc`.
   
   Signed-off-by: Junbo Zheng <[email protected]>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to