| /Zephyr-latest/scripts/ |
| D | requirements.txt | 1 -r requirements-base.txt
2 -r requirements-build-test.txt
3 -r requirements-run-test.txt
4 -r requirements-extras.txt
5 -r requirements-compliance.txt
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 1 .. _code-documentation:
12 generates either an on-line documentation browser (in HTML) and/or provides
17 Reference to Requirements
20 APIs for the most part document the implementation of requirements or advertised
23 using custom _doxygen_ tags that reference requirements maintained somewhere
26 Test Documentation
29 To help understand what each test does and which functionality it tests we also
30 document all test code using the same tools and in the same context and generate
34 the original requirements.
40 Test Code
[all …]
|
| /Zephyr-latest/tests/arch/arm/arm_thread_swap_tz/ |
| D | Kconfig | 1 # SPDX-License-Identifier: Apache-2.0
8 Redefine this with looser requirements, so the EXC_RETURN value can
9 be checked in the test. This essentially tests that the official
10 requirements are sane.
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 5 subsystem. The tests run on the BabbleSim simulator, using the BabbleSim test
11 src/ directory containing the necessary test harnesses to execute the tests.
13 There's only a single test application for all the Bluetooth Mesh BabbleSim
14 tests. The test application is built from this directory, and includes all test
15 harnesses in every build. The overlying bsim test framework selects the harness
16 to use at runtime, using the test identifiers passed in the test scripts.
21 The Bluetooth Mesh tests have no extra requirements, and can be run using the
30 Individual test harnesses can be run outside of ``RunTest()`` by setting the
36 When running test applications independently, make sure to assign the original
37 device number with -dXXX to the process.
[all …]
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | test_bossac.py | 3 # Copyright (c) 2020-2021 Gerson Fernando Budke <nandojve@gmail.com>
5 # SPDX-License-Identifier: Apache-2.0
18 pytest.skip("skipping Linux-only bossac tests", allow_module_level=True)
20 TEST_BOSSAC_PORT = 'test-bossac-serial'
27 ['stty', '-F', TEST_BOSSAC_PORT, 'raw', 'ispeed', '115200',
28 'ospeed', '115200', 'cs8', '-cstopb', 'ignpar', 'eol', '255',
30 ['bossac', '-p', TEST_BOSSAC_PORT, '-R', '-w', '-v',
31 '-b', RC_KERNEL_BIN],
35 ['stty', '-F', TEST_BOSSAC_PORT, 'raw', 'ispeed', TEST_BOSSAC_SPEED,
36 'ospeed', TEST_BOSSAC_SPEED, 'cs8', '-cstopb', 'ignpar', 'eol', '255',
[all …]
|
| /Zephyr-latest/.github/workflows/ |
| D | twister_tests.yml | 2 # SPDX-License-Identifier: Apache-2.0
9 - main
10 - v*-branch
11 - collab-*
13 - 'scripts/pylib/**'
14 - 'scripts/twister'
15 - 'scripts/tests/twister/**'
16 - '.github/workflows/twister_tests.yml'
17 - 'scripts/schemas/twister/'
20 - main
[all …]
|
| D | twister_tests_blackbox.yml | 2 # SPDX-License-Identifier: Apache-2.0
9 - main
10 - collab-*
11 - v*-branch
13 - 'scripts/pylib/twister/**'
14 - 'scripts/twister'
15 - 'scripts/tests/twister_blackbox/**'
16 - '.github/workflows/twister_tests_blackbox.yml'
19 twister-tests:
21 runs-on: ${{ matrix.os }}
[all …]
|
| D | pylib_tests.yml | 2 # SPDX-License-Identifier: Apache-2.0
9 - main
10 - v*-branch
12 - 'scripts/pylib/build_helpers/**'
13 - '.github/workflows/pylib_tests.yml'
16 - main
17 - v*-branch
19 - 'scripts/pylib/build_helpers/**'
20 - '.github/workflows/pylib_tests.yml'
23 pylib-tests:
[all …]
|
| D | scripts_tests.yml | 2 # SPDX-License-Identifier: Apache-2.0
9 - main
10 - v*-branch
12 - 'scripts/build/**'
13 - '.github/workflows/scripts_tests.yml'
16 - main
17 - v*-branch
19 - 'scripts/build/**'
20 - '.github/workflows/scripts_tests.yml'
23 scripts-tests:
[all …]
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 9 This document is the safety documentation providing an overview over the safety-relevant activities
26 This document is a living document and may evolve over time as new requirements, guidelines, or
43 code base is pre-existing, we use the route 3s/1s approach defined by the IEC 61508 standard.
46 *Assessment of non-compliant development. Which is basically the route 1s with existing
50 *Compliant development. Compliance with the requirements of this standard for the avoidance and
57 electrical, electronic, and programmable electronic safety-related systems. Here's an overview of
69 includes the identification of safety requirements, the development of a safety plan, and the
74 safety-related system to ensure that it meets the specified SIL and other safety requirements.
79 documentation process to ensure that all aspects of the safety-related system are fully
80 documented and that there is full traceability from the safety requirements to the final system
[all …]
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/ |
| D | README | 1 # Test a timer implementations variance and long term drift
8 Timers are meant to be precise and accurate. This test validates an implementation is both.
10 --------------------------------------------------------------------------------
15 collect samples. The "kernel.timer.timer_behavior_external" test will toggle a
16 GPIO pin on every cycle - first cycle will be a rising edge. This test expects
18 necessary statistics that the test will use to assert the test status.
23 "test-kernel-timer-behavior-external", with property "timeout-gpios" being the
28 In order to get data from the external tool, the test expects a Python module,
31 run(seconds: float, options: str) -> {}, int
48 to account for expected drift in the test and between the DUT and the external
[all …]
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 1 Thread-Metric RTOS Test Suite
4 1. Thread-Metric Test Suite
6 The Thread-Metric test suite consists of 8 distinct RTOS
8 of an RTOS. The test measures the total number of RTOS events
12 1.1. Basic Processing Test
14 This is the baseline test consisting of a single thread. This
15 should execute the same on every operating system. Test values
17 relative to the difference between the values of this test.
19 1.2. Cooperative Scheduling Test
21 This test consists of 5 threads created at the same priority that
[all …]
|
| /Zephyr-latest/samples/sensor/vcnl4040/ |
| D | README.rst | 1 .. zephyr:code-sample:: vcml4040
3 :relevant-api: sensor_interface
15 Requirements chapter
24 - VCNL4040: https://www.vishay.com/docs/84274/vcnl4040.pdf
32 .. zephyr-app-commands::
33 :zephyr-app: samples/sensor/vcnl4040/
40 .. code-block:: console
49 Polling mode test finished.
58 Threshold trigger test finished.
59 Trigger mode test finished.
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 1 .. _bin-blobs:
12 Zephyr supports downloading and using third-party binary blobs via its built-in
15 `upstream (vanilla) Zephyr <https://github.com/zephyrproject-rtos/zephyr>`_.
18 the support for binary blobs in forks or third-party distributions of Zephyr. In
21 therefore free to create Zephyr-based downstream software which uses binary
22 blobs if they cannot meet the requirements described in this page.
30 click-through or other EULA-like workflow when users fetch and install blobs.
35 Blobs must be hosted on the Internet and managed by third-party infrastructure.
45 Blobs are fetched from official third-party sources by the :ref:`west blobs
46 <west-blobs>` command.
[all …]
|
| /Zephyr-latest/samples/bluetooth/st_ble_sensor/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_st_ble_sensor
3 :relevant-api: bt_gatt bluetooth
5 Export vendor-specific GATT services over Bluetooth.
10 This application demonstrates Bluetooth LE peripheral by exposing vendor-specific
15 Requirements chapter
29 After connected, tap LED image on Android to test LED service.
30 Push SW0 button on embedded device to test button service.
32 See :zephyr:code-sample-category:`bluetooth` samples for details.
|
| /Zephyr-latest/samples/net/dsa/ |
| D | README.rst | 1 .. zephyr:code-sample:: dsa
3 :relevant-api: DSA
5 Test and debug Distributed Switch Architecture
15 Requirements chapter
18 - :ref:`networking_with_host`
27 .. zephyr-app-commands::
28 :zephyr-app: samples/net/dsa
|
| /Zephyr-latest/boards/shields/npm1300_ek/doc/ |
| D | index.rst | 9 The nPM1300 EK lets you test different functions and features of the nPM1300
12 Requirements section in nPM1300 EK
24 The shield can be used in any application by setting ``--shield npm1300_ek``
25 when invoking ``west build``. You can check :zephyr:code-sample:`npm1300_ek` for a
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 11 Samples should be limited in scope and should focus only on demonstrating non-trivial or
19 1. Samples must not be used to test features or verify platforms
34 :zephyr_file:`tests/` folder. In a sample, the only thing you test is
44 .. code-block:: yaml
49 - native_sim
51 - kernel
52 - condition_variables
57 - ".*Waited and joined with 3 threads"
59 * Do not mark the test as build only. A sample should be able to build *and*
69 never be used to test functionality of the subsystem or module the sample
[all …]
|
| /Zephyr-latest/boards/shields/npm6001_ek/doc/ |
| D | index.rst | 9 The nPM6001 EK lets you test different functions and features of the nPM6001
18 Requirements section in nPM6001 EK
30 The shield can be used in any application by setting ``--shield npm6001_ek``
31 when invoking ``west build``. You can check :zephyr:code-sample:`npm6001_ek` for a
37 - `nPM6001 EK Manual <https://infocenter.nordicsemi.com/topic/ug_npm6001_ek/UG/nPM6001_EK/intro.htm…
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/priv_beacon/ |
| D | proxy_adv_multi_subnet_coex.sh | 3 # SPDX-License-Identifier: Apache-2.0
7 # Test Proxy advertisement Coex
9 # This test verifies correct Proxy advertisement behavior for a device
10 # where the Proxy adv requirements changes over time, both for single
29 # Test procedure:
30 # 1. (0-20 seconds) A single subnet is active on the TX device with GATT
33 # 2. (20-50 seconds) Two additional subnets are added to the TX device. RX
36 # 3. (50-110 seconds) The second subnet enables Node Identity. RX device
39 # 4. (110-130 seconds) The first and second subnet gets solicited. RX device
41 # 5. (130-150 seconds) The second and third subnet are disabled on the TX
|
| /Zephyr-latest/samples/boards/nordic/nrf_led_matrix/ |
| D | README.rst | 1 .. zephyr:code-sample:: nrf_led_matrix
10 driver in action and to serve as a test ensuring that this driver is buildable
13 Requirements chapter
19 overlay file with the corresponding ``"nordic,nrf-led-matrix"`` compatible
29 .. zephyr-app-commands::
30 :zephyr-app: samples/boards/nordic/nrf_led_matrix
|
| /Zephyr-latest/samples/shields/npm1300_ek/doc/ |
| D | index.rst | 1 .. zephyr:code-sample:: npm1300_ek
13 - Regulators (BUCK1/2, LDO1/2)
14 - GPIO
16 Requirements chapter
29 .. zephyr-app-commands::
30 :zephyr-app: samples/shields/npm1300_ek
37 provided to test the PMIC. Below you can find details for each subcommand.
42 The ``regulator`` shell interface provides several subcommand to test
45 .. code-block:: bash
53 .. code-block:: bash
[all …]
|
| /Zephyr-latest/samples/bluetooth/broadcaster_multiple/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_broadcaster_multiple
3 :relevant-api: bluetooth
13 This sample advertises two non-connectable non-scannable advertising sets with
22 Requirements chapter
33 To test this sample use the Observer sample with Extended Scanning enabled,
37 See :zephyr:code-sample-category:`Bluetooth samples section <bluetooth>` for details.
|
| /Zephyr-latest/boards/shields/npm1100_ek/doc/ |
| D | index.rst | 9 The nPM1100 EK lets you test different functions and features of the nPM1100
18 Requirements section in nPM1100 EK
26 +-----------+--------------+
31 +-----------+--------------+
36 The shield can be used in any application by setting ``--shield npm1100_ek``
42 - `nPM1100 EK Manual <https://infocenter.nordicsemi.com/topic/ug_npm1100_ek/UG/nPM1100_EK/intro.htm…
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | README.md | 12 pip install -r $ZEPHYR_BASE/scripts/requirements-build-test.txt
28 coverage run -m pytest $ZEPHYR_BASE/scripts/tests/twister/
34 coverage report -m $ZEPHYR_BASE/scripts/pylib/twister/
40 coverage report -m $ZEPHYR_BASE/scripts/twister
53 - conftest.py: Contains common fixtures for use in testing the twister tool.
54 - test_twister.py : Contains basic testcases for environment variables, verifying testcase & platfo…
55 - test_testsuite_class.py : Contains testcases for Testsuite class (except reporting functionality)…
56 - test_testinstance.py : Contains testcases for Testinstance and Testcase class.
57 - test_reporting_testsuite.py : Contains testcases for reporting functionality of Testsuite class o…
|
