nuttx/Documentation/applications/testing/ostest/index.rst
Tomasz 'CeDeROM' CEDRO 3efaf80d3d boards/xtensa/esp32s3: New board WaveShare ESP32-S3-Touch-LCD-1.28 (WIP).
* Initial experimental / work in progress implementation.
* New board name is esp32s3-ws-lcd128.
* Supports Kconfig delectable w/wo touch variants (lcd gpios difference).
* IMU QMI8658 bringups is put into esp32s3/common/src to share with other
  boards. Pin defines are located at <board>include/board.h and referenced
  with `#include <arch/board/board.h>`.
* Supported configurations: nsh, ostest, coremark, touch-lvgl, notouch-lvgl,
  imu-qmi8658, watchdog.
* Does not have touch panel driver yet.
* Created board documentation. Added sphinx inline cross-references.
* TODO: Fix SPI GC9A01A LCD pixel format colors.
* TODO: Create I2C CST816S touch panel driver.

Signed-off-by: Tomasz 'CeDeROM' CEDRO <tomek@cedro.info>
2026-04-24 16:27:08 +08:00

35 lines
1.7 KiB
ReStructuredText
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

.. _ostest:
==================
``ostest`` OS test
==================
This is the NuttX _qualification_ suite. It attempts to exercise a broad set of
OS functionality. Its coverage is not very extensive as of this writing, but it
is used to qualify each NuttX release.
The behavior of the ``ostest`` can be modified with the following settings in the
``boards/<arch>/<chip>/<board>/configs/<config>/defconfig`` file:
- ``CONFIG_NSH_BUILTIN_APPS`` – Build the OS test example as an NSH built-in
application.
- ``CONFIG_TESTING_OSTEST_LOOPS`` – Used to control the number of executions of
the test. If undefined, the test executes one time. If defined to be zero,
the test runs forever.
- ``CONFIG_TESTING_OSTEST_STACKSIZE`` – Used to create the ostest task. Default is
``8192``.
- ``CONFIG_TESTING_OSTEST_NBARRIER_THREADS`` – Specifies the number of threads to
create in the barrier test. The default is 8 but a smaller number may be
needed on systems without sufficient memory to start so many threads.
- ``CONFIG_TESTING_OSTEST_RR_RANGE`` – During round-robin scheduling test two
threads are created. Each of the threads searches for prime numbers in the
configurable range, doing that configurable number of times. This value
specifies the end of search range and together with number of runs allows to
configure the length of this test – it should last at least a few tens of
seconds. Allowed values ``[1; 32767]``, default ``10000``.
- ``CONFIG_TESTING_OSTEST_RR_RUNS`` – During round-robin scheduling test two
threads are created. Each of the threads searches for prime numbers in the
configurable range, doing that configurable number of times.