Home
last modified time | relevance | path

Searched refs:running (Results 1 – 25 of 581) sorted by relevance

12345678910>>...24

/Zephyr-Core-3.7.0/samples/net/cellular_modem/server/
Dte_udp_echo.py10 self.running = True
17 self.running = False
25 while self.running:
Dte_udp_receive.py44 self.running = True
52 self.running = False
60 while self.running:
/Zephyr-Core-3.7.0/soc/st/stm32/stm32wbax/hci_if/
Dhost_stack_if.c36 uint8_t running = 0x0; in ble_ctlr_stack_handler() local
40 running = BleStack_Process(); in ble_ctlr_stack_handler()
49 if (running == BLE_SLEEPMODE_RUNNING) { in ble_ctlr_stack_handler()
/Zephyr-Core-3.7.0/tests/kernel/context/
DREADME.txt100 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
122 thread (q order: 4, t/o: 1750) is running
DKconfig9 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-Core-3.7.0/arch/posix/core/
Dposix_core.c61 bool running; /* Is this the currently running thread */ member
99 threads_table[this_th_nbr].running = false; in abort_tail()
116 threads_table[this_th_nbr].running = false; in posix_wait_until_allowed()
132 threads_table[this_th_nbr].running = true; in posix_wait_until_allowed()
306 threads_table[thread_idx].running = false; in posix_thread_starter()
363 threads_table[t_slot].running = false; in posix_new_thread()
/Zephyr-Core-3.7.0/boards/st/nucleo_h503rb/support/
Dopenocd.cfg12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
/Zephyr-Core-3.7.0/boards/st/stm32h573i_dk/support/
Dopenocd.cfg12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
/Zephyr-Core-3.7.0/boards/st/nucleo_h533re/support/
Dopenocd.cfg12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
/Zephyr-Core-3.7.0/boards/st/nucleo_h563zi/support/
Dopenocd.cfg12 # connect_assert_srst needed if low power mode application running (WFI...)
17 # Due to the use of connect_assert_srst, running gdb requires
/Zephyr-Core-3.7.0/doc/hardware/arch/
Dsemihost.rst9 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-Core-3.7.0/doc/develop/getting_started/
Dinstallation_win.rst11 If you are running a recent version of Windows 10 you can make use of the
26 running in the "About your PC" section of the System Settings.
27 If you are running an older Windows 10 build you might need to install
/Zephyr-Core-3.7.0/samples/bluetooth/bthome_sensor_template/
DREADME.rst12 …for example `Home Assistant <https://www.home-assistant.io/>`_ with the BTHome integration running.
21 When the sample is running, navigate to Devices & Services under settings in Home
/Zephyr-Core-3.7.0/samples/boards/nrf/clock_skew/src/
Dmain.c101 bool running; in show_clocks() local
104 running = nrf_clock_is_running(NRF_CLOCK, NRF_CLOCK_DOMAIN_LFCLK, in show_clocks()
107 running ? "Running" : "Off", lfsrc_s[src.lf]); in show_clocks()
109 running = nrf_clock_is_running(NRF_CLOCK, NRF_CLOCK_DOMAIN_HFCLK, in show_clocks()
112 running ? "Running" : "Off", hfsrc_s[src.hf]); in show_clocks()
/Zephyr-Core-3.7.0/samples/net/dhcpv4_client/
DREADME.rst26 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 :ref:`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-Core-3.7.0/boards/st/stm32h7s78_dk/support/
Dopenocd.cfg16 # connect_assert_srst needed if low power mode application running (WFI...)
35 # Due to the use of connect_assert_srst, running gdb requires
/Zephyr-Core-3.7.0/scripts/native_simulator/common/src/
Dnct.c98 bool running; /* Is this the currently running thread */ member
142 tt_el->running = false; in abort_tail()
159 tt_el->running = false; in nct_wait_until_allowed()
174 tt_el->running = true; in nct_wait_until_allowed()
376 tt_el->running = false; in nct_thread_starter()
468 tt_el->running = false; in nct_new_thread()
/Zephyr-Core-3.7.0/arch/common/
DKconfig10 Semihosting is a mechanism that enables code running on an ARM or
12 a host computer that is running a debugger.
/Zephyr-Core-3.7.0/samples/net/cloud/mqtt_azure/
DKconfig43 Provide proxy address if you are running this application
50 Provide proxy port if you are running this application
/Zephyr-Core-3.7.0/tests/net/lib/lwm2m/lwm2m_rd_client/src/
Dstubs.c151 static bool running; variable
156 while (running) { in service_work_fn()
190 running = true; in test_lwm2m_engine_start_service()
202 running = false; in test_lwm2m_engine_stop_service()
/Zephyr-Core-3.7.0/boards/nordic/nrf54h20dk/doc/
Dindex.rst20 Extensions, running at up to 320 MHz, referred to as the **application core**
22 Extensions, running at up to 256 MHz, referred to as the **radio core**.
126 building and running. Debugging is for now limited to the application and radio
139 #. Build the sample by running the following command:
155 You can build and flash the examples to make sure Zephyr is running correctly on
/Zephyr-Core-3.7.0/tests/drivers/build_all/sensor/
DCMakeLists.txt7 # Exclude main when running the generic test because ztest supplies its own
/Zephyr-Core-3.7.0/samples/subsys/task_wdt/boards/
Dnucleo_f401re.overlay10 * Thus, use the IWDG instead for running this sample.
Dnucleo_f411re.overlay10 * Thus, use the IWDG instead for running this sample.
/Zephyr-Core-3.7.0/tests/lib/p4workq/src/
Dmain.c26 bool running; member
46 item->running = false; in stress_sub()
57 titem->running = true; in stress_handler()

12345678910>>...24