Searched refs:testing (Results 176 – 200 of 295) sorted by relevance
12345678910>>...12
| /Zephyr-latest/tests/drivers/build_all/dac/ |
| D | app.overlay | 6 * Application overlay for testing driver builds
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.mcux_elcdif | 75 Rotate display by 0 degrees. Primarily useful for testing,
|
| /Zephyr-latest/samples/net/telnet/ |
| D | README.rst | 31 To use QEMU for testing, follow the :ref:`networking_with_qemu` guide.
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_setup.rst | 135 When you are finished with network testing using QEMU, you should stop
138 network interfaces. For example, stop them if you switch from testing
|
| D | eth_bridge_native_sim_setup.rst | 13 This setup is useful when testing the Ethernet bridging feature that can be enabled with
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 194 …twister -p intel_adsp/cavs25 --device-testing --device-serial-pty="$ZEPHYR_BASE/soc/intel/intel_ad…
205 …twister -p intel_adsp/cavs25 --device-testing --device-serial-pty="$ZEPHYR_BASE/soc/intel/intel_ad…
212 twister -p intel_adsp/cavs25 --hardware-map cavs.map --device-testing -T samples/hello_world
|
| /Zephyr-latest/samples/net/dhcpv4_client/ |
| D | README.rst | 29 To use QEMU for testing, follow the :ref:`networking_with_qemu` guide.
|
| /Zephyr-latest/boards/ti/sk_am62/doc/ |
| D | index.rst | 72 The testing requires the binary to be copied to the SD card to allow the A53 cores to load it while…
|
| /Zephyr-latest/samples/drivers/clock_control_litex/ |
| D | README.rst | 17 * Optional: clock output signals redirected to output pins for testing
|
| /Zephyr-latest/samples/subsys/modbus/rtu_server/ |
| D | README.rst | 47 it can, apart from testing the server implementation, also be used practically
|
| /Zephyr-latest/boards/espressif/esp32s3_eye/doc/ |
| D | index.rst | 113 - Four strapping pins led out from the main board. They can be used as testing points.
119 - LCD_RST testing point. You can use it to reset the LCD display with control signals.
|
| /Zephyr-latest/boards/native/native_sim/doc/ |
| D | index.rst | 24 developing and testing application code which would require them.
203 For developing and testing SW which requires specific HW, while retaining the
231 This is desirable when running in a debugger or testing in batch, but not if
390 instead of a virtual network, facilitating testing without the need for extra
411 This alternative option is mainly aimed for testing Bluetooth connectivity over
528 The ``STDINOUT`` option can be used for automated testing, such as when piping other processes'
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 25 purposes (e.g. for testing, or to reserve a physical CPU for running
221 handler and will instead spin in its idle loop, testing the scheduler
225 IPI, and this code will only be used for testing purposes or on
302 complicated than simply testing the thread pointer for equality with a
|
| /Zephyr-latest/boards/fanke/fk7b0m1_vbt6/doc/ |
| D | index.rst | 19 and testing of peripherals and functionalities.
|
| /Zephyr-latest/doc/build/signing/ |
| D | index.rst | 33 and testing
|
| /Zephyr-latest/boards/phytec/phyboard_electra/doc/ |
| D | index.rst | 104 Therefore, the testing requires the binary to be copied to the SD card to allow the A53 cores to
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 36 It is the smallest subdivision of testing in Zephyr.
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.smp | 75 to check if schedule IPI has called or not, for testing
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 19 There are roughly 4 scenarios we care about testing with
|
| /Zephyr-latest/samples/net/mqtt_sn_publisher/ |
| D | README.rst | 38 - LAN for testing purposes (Ethernet)
|
| /Zephyr-latest/tests/drivers/build_all/display/ |
| D | app.overlay | 6 * Application overlay for testing driver builds
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 232 well as the module integration testing are successful.
235 and testing the module codebase with the zephyr main tree.
236 This includes occasional advanced testing of the module's codebase
237 in addition to the testing performed by Zephyr's CI.
360 All Zephyr modules should provide some level of **integration** testing,
375 default manifest, shall provide some level of integration testing.
382 The purpose of integration testing is not to provide functional verification
383 of the module; this should be part of the testing framework of the external
387 testing infrastructure but are written explicitly for Zephyr. These tests
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.6.rst | 13 infrastructure, and testing.
271 * ``ZEP-1140`` - Add a unified kernel version of power_mgr sample app for testing PM code with the …
342 * ``ZEP-1227`` - ztest native testing not working in unified kernel
|
| /Zephyr-latest/boards/phytec/phyboard_lyra/doc/ |
| D | phyboard_lyra_am62xx_m4.rst | 98 Therefore, the testing requires the binary to be copied to the SD card to allow the A53 cores to
|
| /Zephyr-latest/drivers/hwinfo/ |
| D | Kconfig | 26 Enable hwinfo Shell for testing.
|
12345678910>>...12
