| /Zephyr-latest/tests/kernel/workq/work_queue/ |
| D | README.txt | 9 Building and Running Project:
37 - Running test item 1
41 - Running test item 2
45 - Running test item 3
46 - Running test item 4
47 - Running test item 5
48 - Running test item 6
69 - Running delayed test item 1
70 - Running delayed test item 2
71 - Running delayed test item 3
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | dma.rst | 62 RUNNING [label=Running,shape=box];
67 CONFIGURED -> RUNNING [label=dma_start];
71 RUNNING -> CONFIGURED [label=dma_stop];
72 RUNNING -> RUNNING [label=dma_start];
73 RUNNING -> RUNNING [label=dma_resume, headport=w];
74 RUNNING -> SUSPENDED [label=dma_suspend];
77 SUSPENDED -> RUNNING [label=dma_resume];
|
| /Zephyr-latest/tests/bluetooth/classic/sdp_c/ |
| D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
31 Building and Running
34 Running on mimxrt1170_evk@B/mimxrt1176/cm7 argument
37 Running the test suite on :ref:`mimxrt1170_evk` relies on configuration of ``bumble``.
52 Running on Hardware argument
55 Running the test suite on hardware requires a HCI transport connected to the host PC.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /Zephyr-latest/samples/drivers/dac/ |
| D | README.rst | 12 Building and Running
21 Building and Running for ST Nucleo L073RZ
32 Building and Running for ST Nucleo L152RE
43 Building and Running for ST Nucleo F767ZI
54 Building and Running for ST Disco F3
65 Building and Running for ST Nucleo F429ZI
76 Building and Running for STM32L562E DK
87 Building and Running for ST Nucleo L552ZE Q
98 Building and Running for NXP TWR-KE18F
112 Building and Running for NXP FRDM-K64F
[all …]
|
| /Zephyr-latest/tests/kernel/context/ |
| D | README.txt | 57 Building and Running Project:
100 thread (q order: 2, t/o: 500) is running
102 thread (q order: 3, t/o: 750) is running
104 thread (q order: 0, t/o: 1000) is running
106 thread (q order: 6, t/o: 1250) is running
108 thread (q order: 1, t/o: 1500) is running
110 thread (q order: 4, t/o: 1750) is running
112 thread (q order: 5, t/o: 2000) is running
116 thread (q order: 3, t/o: 750) is running
118 thread (q order: 0, t/o: 1000) is running
[all …]
|
| D | Kconfig | 9 The platform may have some component running in the background while the k_cpu_idle test is
10 running causing the CPU to awake. With this option we allow for a maximum number of wakes
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 10 host PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
43 Building and Running
46 Running on native_sim argument
49 Running the test suite on :ref:`native_sim` relies on the `Linux SocketCAN`_ virtual CAN driver
52 On the host PC, a virtual SocketCAN interface needs to be created and brought up before running the
83 Running on Hardware argument
86 Running the test suite on hardware requires a physical CAN adapter connected to the host PC. The CAN
113 Twister. Below is an example for running on the :zephyr:board:`lpcxpresso55s36`:
|
| /Zephyr-latest/samples/bluetooth/bthome_sensor_template/ |
| D | README.rst | 16 …for example `Home Assistant <https://www.home-assistant.io/>`_ with the BTHome integration running.
18 Building and Running
25 When the sample is running, navigate to Devices & Services under settings in Home
|
| /Zephyr-latest/tests/net/trickle/src/ |
| D | main.c | 121 zassert_true(net_trickle_is_running(&t1), "Trickle 1 not running"); in test_trickle_1_status()
132 zassert_true(net_trickle_is_running(&t2), "Trickle 2 not running"); in test_trickle_2_status()
147 zassert_true(net_trickle_is_running(&t1), "Trickle 1 not running"); in test_trickle_1_wait()
159 zassert_true(net_trickle_is_running(&t1), "Trickle 1 not running"); in test_trickle_1_wait_long()
174 zassert_true(net_trickle_is_running(&t2), "Trickle 2 not running"); in test_trickle_2_wait()
179 zassert_false(net_trickle_is_running(&t1), "Trickle 1 running"); in test_trickle_1_stopped()
184 zassert_true(net_trickle_is_running(&t2), "Trickle 2 is not running"); in test_trickle_2_inc()
190 zassert_true(net_trickle_is_running(&t1), "trickle 1 is not running"); in test_trickle_1_update()
|
| /Zephyr-latest/samples/net/sockets/echo_client/ |
| D | overlay-linux.conf | 1 # Include this overlay when the echo-server is running on Linux and
2 # echo-client is running on Qemu.
|
| /Zephyr-latest/samples/net/cellular_modem/server/ |
| D | te_udp_echo.py | 10 self.running = True
17 self.running = False
25 while self.running:
|
| /Zephyr-latest/samples/boards/renesas/openamp_linux_zephyr/ |
| D | sample.yaml | 2 description: Enable message exchange between two cores, with the application core running Linux
3 and the real-time core running Zephyr, using the OpenAMP library.
|
| /Zephyr-latest/samples/net/sockets/http_client/ |
| D | README.rst | 21 Building and Running
25 running it inside QEMU as described in :ref:`networking_with_qemu`.
50 running ``west build`` or ``cmake``.
59 Running http-server in Linux Host
83 Note that ``http-server.py`` must be running in the Linux host terminal window
|
| /Zephyr-latest/samples/net/sockets/websocket_client/ |
| D | README.rst | 22 Building and Running
26 running it inside QEMU as described in :ref:`networking_with_qemu`.
51 running ``west build`` or ``cmake``.
57 Running websocket-server in Linux Host
89 Note that ``zephyr-websocket-server.py`` or ``websocketd`` must be running in
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/device/ |
| D | binary_adapter.py | 36 """Generate and set command which will be used during running device."""
46 log_command(logger, 'Running command', self.command, level=logging.DEBUG)
50 msg = f'Running subprocess failed due to SubprocessError {exc}'
54 msg = f'Running subprocess failed due to file not found: {exc.filename}'
58 msg = f'Running subprocess failed {exc}'
87 logger.debug('Running subprocess finished with return code %s', return_code)
|
| /Zephyr-latest/samples/sensor/mcux_acmp/ |
| D | README.rst | 24 Building and Running
27 Building and Running for TWR-KE18F
38 Building and Running for MIMXRT1170-EVK
49 Building and Running for FRDM-KE17Z
60 Building and Running for FRDM-KE17Z512
71 Building and Running for MIMXRT1180-EVK
|
| /Zephyr-latest/samples/net/ipv4_autoconf/ |
| D | README.rst | 20 Building and Running
23 These are instructions for how to use this sample application running
30 Running Avahi client in Linux Host
66 To verify the Zephyr application is running and has configured an IP address
|
| /Zephyr-latest/boards/st/stm32h573i_dk/support/ |
| D | openocd.cfg | 12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
|
| /Zephyr-latest/boards/st/nucleo_h533re/support/ |
| D | openocd.cfg | 12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
|
| /Zephyr-latest/boards/st/nucleo_h503rb/support/ |
| D | openocd.cfg | 12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
|
| /Zephyr-latest/boards/st/nucleo_h563zi/support/ |
| D | openocd.cfg | 12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt11xx/ |
| D | sysbuild.cmake | 27 # for the application running on the CM4 core
31 # Enable CONFIG_SECOND_CORE_MCUX for the image running on the CM7 core
33 # Set the initial include path for the image running on the CM7 core to
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | semihost.rst | 9 Semihosting is a mechanism that enables code running on ARM and RISC-V targets
11 running a debugger or emulator.
26 directory of the running process.
57 Additional functionality is available by running semihosting instructions
|
| /Zephyr-latest/samples/net/dhcpv4_client/ |
| D | README.rst | 19 Building and Running
22 Running DHCPv4 client in Linux Host
26 QEMU on a Linux host to negotiate IP address from DHCPv4 server (kea) running
94 To verify the Zephyr application client is running and has received
105 These are instructions for how to use this sample application running on
106 :zephyr:board:`frdm_k64f` board to negotiate IP address from DHCPv4 server (kea) running
187 To verify the Zephyr application client is running and has received
201 This sample application running on Arm FVP board can negotiate IP
202 address from DHCPv4 server running on Arm FVP, so there is no extra
|
| /Zephyr-latest/scripts/west_commands/ |
| D | run_tests.py | 7 # A convenience script provided for running tests on the runners
33 print(f'Running mypy from {here}:\n\t' +
37 print(f'Running pytest from {here}:\n\t' +
|
