Currently NuttX has many initialization options each one used for some specific case, but at least CONFIG_NSH_ARCHINIT that is used to do drivers initialization when NSH is enabled could be removed in favor of some generic option like BOARD_LATE_INITIALIZATION that will work for all applications (inclusive to NSH itself).
Currently NuttX has many initialization options each one used for some specific case, but at least CONFIG_NSH_ARCHINIT that is used to do drivers initialization when NSH is enabled could be removed in favor of some generic option like BOARD_LATE_INITIALIZATION that will work for all applications (inclusive to NSH itself).
I raised this question some time ago here: https://github.com/apache/nuttx/issues/10821 but didn't heard anything from my peers.
But now that @0528Mike came with this PR: https://github.com/apache/nuttx/pull/11306 we could fix this issue merging CONFIG_NSH_ARCHINIT and BOARD_LATE_INITIALIZATION to avoid issues like this faced from a NuttX user: https://github.com/apache/nuttx/issues/10821 and for many people that want to user their application as ENTRYPOINT on NuttX.