Home
last modified time | relevance | path

Searched refs:tests (Results 976 – 1000 of 1029) sorted by relevance

1...<<31323334353637383940>>...42

/Zephyr-latest/tests/bsim/bluetooth/ll/advx/src/
Dmain.c1856 struct bst_test_list *test_advx_install(struct bst_test_list *tests) in test_advx_install() argument
1858 return bst_add_tests(tests, test_def); in test_advx_install()
/Zephyr-latest/samples/tfm_integration/tfm_ipc/
DREADME.rst86 dual core ARM Cortex-M33 setup, also allows you to run TF-M tests using QEMU if
/Zephyr-latest/drivers/flash/
DKconfig113 read/write/erase tests with speed output.
/Zephyr-latest/boards/nxp/imx8mm_evk/doc/
Dindex.rst146 Use this configuration to run basic Zephyr applications and kernel tests,
/Zephyr-latest/boards/antmicro/myra_sip_baseboard/doc/
Dindex.rst240 running twister tests on the device. You should then also use the ``--flash-before`` and
/Zephyr-latest/tests/drivers/build_all/gpio/
Dapp.overlay9 * with real-world devicetree nodes, to allow these tests to run on
/Zephyr-latest/subsys/net/ip/
DKconfig810 Used for self-contained networking tests that do not require a
911 # If we are running network tests found in tests/net, then the NET_TEST is
912 # set and in that case we default to Dummy L2 layer as typically the tests
/Zephyr-latest/doc/project/
Dproject_roles.rst334 * Architectures, core components, sub-systems, samples, tests
338 * Boards (incl relevant samples, tests), SoCs (incl DTS)
/Zephyr-latest/doc/releases/
Drelease-notes-3.6.rst1309 * Bluetooth split stacks tests, where the BT host and controller are run in separate MCUs, are
1311 Several other runtime AMP tests based on these targets have been added to CI, including tests
1314 * Runtime UART tests have been added to CI based on the :ref:`nrf52_bsim<nrf52_bsim>` target.
1315 These include tests of the nRFx UART driver and networked BT stack tests with the host and
Dmigration-guide-3.5.rst100 * ``psa-arch-tests``
102 * ``tf-m-tests``
Drelease-notes-1.7.rst437 * ``ZEP-1778`` - tests/power: multicore case won't work as expected
452 * ``ZEP-1864`` - llvm icx build warning in tests/drivers/uart/*
Drelease-notes-4.0.rst927 * Run Wi-Fi tests together with network tests.
1090 * Updated MQTT tests to be self-contained, no longer requiring external broker.
1544 * Together with the deprecation of ``native_posix``, many tests which were
1547 * Extended the tests of counter_basic_api with a testcase for counters without alarms
Drelease-notes-1.5.rst262 * ``ZEP-708`` - tests/kernel/test_ipm fails on Arduino 101
/Zephyr-latest/doc/connectivity/networking/
Doverview.rst177 ``tests/net/``
/Zephyr-latest/doc/services/llext/
Dbuild.rst182 tests:
/Zephyr-latest/boards/native/nrf_bsim/doc/
Dnrf52_bsim.rst118 most Zephyr samples and tests.
/Zephyr-latest/boards/nxp/imx8mp_evk/doc/
Dindex.rst133 Use this configuration to run basic Zephyr applications and kernel tests,
/Zephyr-latest/doc/develop/west/
Dzephyr-cmds.rst192 west twister -T tests/ztest/base
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst641 A list of unit tests for the Cortex-M porting and miscellaneous features
642 is present in :file:`tests/arch/arm/`. The tests suites are continuously
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-arch.rst208 ``tests/bluetooth/``
/Zephyr-latest/boards/nxp/imx95_evk/doc/
Dindex.rst152 Use this configuration to run basic Zephyr applications and kernel tests,
/Zephyr-latest/doc/services/logging/
Dindex.rst785 Benchmark numbers from :zephyr_file:`tests/subsys/logging/log_benchmark` performed
821 .. [#f2] Logging subsystem memory footprint in :zephyr_file:`tests/subsys/logging/log_benchmark`
839 :zephyr_file:`tests/subsys/logging/log_stack` test is used to characterize stack usage depending
/Zephyr-latest/doc/connectivity/networking/api/
Dlwm2m.rst734 when a server side tests would require those. It is assumed that not all tests are able to trigger
/Zephyr-latest/boards/snps/em_starterkit/doc/
Dindex.rst168 You can try many of the sample applications or tests, but let us discuss
/Zephyr-latest/subsys/bluetooth/host/
DKconfig57 # needed e.g. for unit tests. This default will also server as
1044 bool "Bluetooth SMP self tests executed on init"
1047 This option enables SMP self-tests executed on startup

1...<<31323334353637383940>>...42