| /Zephyr-Core-3.5.0/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-Core-3.5.0/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-Core-3.5.0/.github/workflows/ |
| 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 …]
|
| D | twister_tests_blackbox.yml | 2 # SPDX-License-Identifier: Apache-2.0
9 - main
11 - 'scripts/pylib/twister/**'
12 - 'scripts/twister'
13 - 'scripts/tests/twister_blackbox/**'
14 - '.github/workflows/twister_tests_blackbox.yml'
17 twister-tests:
19 runs-on: ${{ matrix.os }}
22 python-version: [3.8, 3.9, '3.10']
23 os: [ubuntu-22.04]
[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 | twister_tests.yml | 2 # SPDX-License-Identifier: Apache-2.0
9 - main
10 - v*-branch
12 - 'scripts/pylib/twister/**'
13 - 'scripts/twister'
14 - 'scripts/tests/twister/**'
15 - '.github/workflows/twister_tests.yml'
18 - main
19 - v*-branch
21 - 'scripts/pylib/twister/**'
[all …]
|
| /Zephyr-Core-3.5.0/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`
25 Follow these steps to build the DSA sample application:
27 .. zephyr-app-commands::
28 :zephyr-app: samples/net/dsa
31 :goals: build
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/samples/drivers/spi_flash_at45/ |
| D | README.rst | 1 .. zephyr:code-sample:: spi-flash-at45
3 :relevant-api: flash_interface
13 The sample writes a defined test region in the flash memory with bytes of
14 increasing (and overflowing at the 8-bit range) values and then reads it back
19 The :zephyr_file:`samples/drivers/spi_flash_at45/overlay-pm.conf` enables the
21 The :zephyr_file:`samples/drivers/spi_flash_at45/overlay-page_layout.conf`
25 the Read-Modify-Write functionality of DataFlash chips and does not perform
29 Requirements chapter
42 To build and flash the application:
44 .. zephyr-app-commands::
[all …]
|
| /Zephyr-Core-3.5.0/samples/boards/nrf/nrf_led_matrix/ |
| D | README.rst | 10 driver in action and to serve as a test ensuring that this driver is buildable
13 Requirements section in nRF LED matrix sample
19 overlay file with the corresponding ``"nordic,nrf-led-matrix"`` compatible
27 To build and flash the application:
29 .. zephyr-app-commands::
30 :zephyr-app: samples/boards/nrf/nrf_led_matrix
32 :goals: build flash
|
| /Zephyr-Core-3.5.0/doc/_scripts/ |
| D | redirects.py | 3 SPDX-License-Identifier: Apache-2.0
10 - Please keep this list sorted alphabetically.
11 - URLs must be relative to document root (with NO leading slash), and
30 ('guides/beyond-GSG', 'develop/beyond-GSG'),
32 ('guides/bluetooth/sm-pics', 'connectivity/bluetooth/sm-pics'),
33 ('guides/build/index', 'build/cmake/index'),
34 ('guides/build/kconfig/extensions', '/build/kconfig/extensions'),
35 ('guides/build/kconfig/menuconfig', '/build/kconfig/menuconfig'),
36 ('guides/build/kconfig/setting', '/build/kconfig/setting'),
37 ('guides/build/kconfig/tips', '/build/kconfig/tips'),
[all …]
|
| /Zephyr-Core-3.5.0/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
19 fact, Zephyr’s build system supports arbitrary use cases related to blobs. This
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
[all …]
|
| /Zephyr-Core-3.5.0/boards/shields/mikroe_adc_click/doc/ |
| D | index.rst | 9 The MikroElektronika ADC Click carries the `MCP3204`_ 12-bit
10 Analog-to-Digital converter in a `mikroBUS`_ |trade| form factor.
12 .. figure:: adc-click.jpg
18 Requirements section in MikroElektronika ADC Click
28 - `MCP3204 Datasheet`_
29 - `ADC Click`_
34 Set ``-DSHIELD=mikro_adc_click`` when you invoke ``west build``. For
37 .. zephyr-app-commands::
38 :zephyr-app: test/boards/board_shell
41 :goals: build
[all …]
|
| /Zephyr-Core-3.5.0/samples/sensor/vcnl4040/ |
| D | README.rst | 13 Requirements section in VCNL4040: proximity and ambient light sensor
22 - VCNL4040: https://www.vishay.com/docs/84274/vcnl4040.pdf
30 .. zephyr-app-commands::
32 :goals: build flash
38 .. code-block:: console
47 Polling mode test finished.
56 Threshold trigger test finished.
57 Trigger mode test finished.
|
| /Zephyr-Core-3.5.0/samples/net/sockets/echo/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-echo
3 :relevant-api: bsd_sockets
18 Requirements chapter
21 - :ref:`networking_with_host`
22 - or, a board with hardware networking
27 Build the Zephyr version of the sockets/echo application like this:
29 .. zephyr-app-commands::
30 :zephyr-app: samples/net/sockets/echo
32 :goals: build
38 .. code-block:: console
[all …]
|
| /Zephyr-Core-3.5.0/boards/xtensa/xt-sim/doc/ |
| D | index.rst | 1 .. _xt-sim:
10 synthesizable 32-bit RISC processor core. Processor and SOC vendors can select
14 For more information, see https://ip.cadence.com/ipportfolio/tensilica-ip/xtensa-customizable
16 .. figure:: img/xt-sim.jpg
18 :alt: Xtensa Xplorer (Eclipse base frontend for xt-sim)
27 - sample_controller
35 System requirements
44 Only Xtensa tools version ``RF-2016.4-linux`` or later are officially
47 In order to set up the Zephyr OS build system, a Linux 32-bit GCC compiler must
51 On Debian/Ubuntu systems, you can install ``gcc-multilib`` package as follows:
[all …]
|
| /Zephyr-Core-3.5.0/samples/sensor/wsen_itds/ |
| D | README.rst | 1 .. _wsen-itds:
3 WSEN-ITDS: 3-axis acceleration sensor
8 This sample periodically measures acceleration in 3-axis and die temperature for
10 is enabled with the sample frequency of 400Hz and 3-axis data is fetched based
13 Requirements section in WSEN-ITDS: 3-axis acceleration sensor
16 This sample uses the WSEN-ITDS sensor controlled using the I2C interface.
24 …- WSEN-ITDS: https://www.we-online.com/components/products/manual/2533020201601_WSEN-ITDS%20253302…
29 This project outputs sensor data to the console. It requires a WSEN-ITDS
32 .. zephyr-app-commands::
34 :goals: build flash
[all …]
|
| /Zephyr-Core-3.5.0/samples/shields/npm1300_ek/doc/ |
| D | index.rst | 13 - Regulators (BUCK1/2, LDO1/2)
14 - GPIO
16 Requirements section in nPM1300 EK sample
29 .. zephyr-app-commands::
30 :zephyr-app: samples/shields/npm1300_ek
32 :goals: build
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-Core-3.5.0/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…
|
| /Zephyr-Core-3.5.0/samples/boards/nrf/ieee802154/802154_rpmsg/ |
| D | README.rst | 1 .. _nrf-ieee802154-rpmsg-sample:
11 a part of `OpenAMP <https://github.com/OpenAMP/open-amp/>`__.
13 Requirements section in nRF IEEE 802.15.4: Serialization RPMsg
25 You can then build this application and flash it onto your board in
26 the usual way. See :ref:`boards` for board-specific building and
29 To test this sample, you need a separate device/CPU that acts as 802.15.4
|
| /Zephyr-Core-3.5.0/samples/ |
| D | sample_definition_and_criteria.rst | 11 Samples should be limited in scope and should focus only on demonstrating non-trivial or
30 2. Twister should be able to build every sample.
36 .. code-block:: yaml
41 - native_posix
47 - ".*Waited and joined with 3 threads"
51 * Do not mark the test as build only unless necessary.
52 * Any test case-specific configuration options are added using ``extra_args`` or
53 ``extra_configs`` options in the YAML file. The `prj.conf` file should have the in-common
78 * Samples must not test the negative or edge case behaviors.
85 HW requirements, and the expected sample output, if applicable.
[all …]
|
| /Zephyr-Core-3.5.0/samples/bluetooth/hci_rpmsg/ |
| D | README.rst | 1 .. _bluetooth-hci-rpmsg-sample:
11 a part of `OpenAMP <https://github.com/OpenAMP/open-amp/>`__.
13 Requirements section in Bluetooth: HCI RPMsg
26 You can then build this application and flash it onto your board in
27 the usual way. See :ref:`boards` for board-specific building and
30 To test this sample, you need a separate device/CPU that acts as Bluetooth
40 Refer to :ref:`bluetooth-samples` for general information about Bluetooth samples.
|
| /Zephyr-Core-3.5.0/samples/net/sockets/echo_async_select/ |
| D | README.rst | 1 .. zephyr:code-sample:: async-sockets-echo-select
3 :relevant-api: bsd_sockets
12 with non-blocking sockets and a ``select()`` call. This is a variant of
13 the :zephyr:code-sample:`async-sockets-echo` sample.
18 Requirements chapter
21 - :ref:`networking_with_host`
22 - or, a board with hardware networking (including 6LoWPAN)
27 Build the Zephyr version of the sockets/echo_async application like this:
29 .. zephyr-app-commands::
30 :zephyr-app: samples/net/sockets/echo_async_select
[all …]
|
| /Zephyr-Core-3.5.0/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', '-e', '-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-Core-3.5.0/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 1 # Configuration for the TF-M Module
5 # SPDX-License-Identifier: Apache-2.0
29 bool "Build with TF-M as the Secure Execution Environment"
37 When enabled, this option instructs the Zephyr build process to
38 additionally generate a TF-M image for the Secure Execution
40 itself is to be executed in the Non-Secure Processing Environment.
42 ensures that the Zephyr image is built as a Non-Secure image. Both
43 TF-M and Zephyr images, as well as the veneer object file that links
44 them, are generated during the normal Zephyr build process.
58 default "${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/bl2/ext/mcuboot/root-RSA-3072.pem"
[all …]
|
