This is an automated email from the ASF dual-hosted git repository.

xiaoxiang781216 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nuttx.git

commit 51b6e4fb3c8f661ffbdc8512703a9d058eda5f07
Author: raiden00pl <[email protected]>
AuthorDate: Tue Nov 17 09:26:45 2026 +0100

    Documentation/stm32: Document the ostest configuration rule.
    
    Describe which STM32 board configurations enable ostest and how an
    ostest configuration is set up.
    
    Assisted-by: Claude Code:claude-opus-5-5
    Signed-off-by: raiden00pl <[email protected]>
---
 Documentation/guides/chip-specific/stm32_ports.rst | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/Documentation/guides/chip-specific/stm32_ports.rst 
b/Documentation/guides/chip-specific/stm32_ports.rst
index 712e86f9ec2..23585d3e06c 100644
--- a/Documentation/guides/chip-specific/stm32_ports.rst
+++ b/Documentation/guides/chip-specific/stm32_ports.rst
@@ -1149,6 +1149,23 @@ The board does not pass numeric divisors for the RCC 
code to convert into
 register fields.  The RCC code keeps reserved register bits at their reset
 value.
 
+Board configurations
+====================
+
+* ``nsh`` is NuttShell with the ``hello`` example.  It does not enable
+  ``ostest``.
+* ``ostest`` (``CONFIG_TESTING_OSTEST``) is enabled only in the ``ostest``
+  and ``jumbo`` configurations, and only on boards with at least 256 KB of
+  flash.
+* An ``ostest`` configuration is ``nsh`` plus ``ostest``: NSH with builtin
+  applications (``CONFIG_NSH_BUILTIN_APPS``) and
+  ``CONFIG_INIT_ENTRYPOINT="nsh_main"``.  ``ostest`` is run from NSH.
+* ``kostest`` configurations (``ostest`` in the protected build) are the
+  exception and start ``ostest_main`` directly.
+* Configurations for a specific feature do not enable ``ostest``.  The
+  exception is a configuration made to run ``ostest`` with that feature, for
+  example ``stm32f4discovery:sporadic``.
+
 Next steps
 ==========
 

Reply via email to