Home
last modified time | relevance | path

Searched refs:runs (Results 76 – 100 of 165) sorted by relevance

1234567

/Zephyr-latest/doc/connectivity/networking/
Dqemu_user_setup.rst20 By default, QEMU uses the ``10.0.2.X/24`` network and runs a gateway at
/Zephyr-latest/doc/connectivity/networking/api/
Dcapture.rst90 The interface 2 is a virtual interface that runs on top of interface 1. The
/Zephyr-latest/doc/services/storage/disk/
Daccess.rst66 interface. Example uses pin ``PA27`` for chip select, and runs the SPI bus
/Zephyr-latest/samples/subsys/llext/edk/
DREADME.rst22 subscribing to events. Extension ``kext1`` runs in a kernel thread, albeit similar
/Zephyr-latest/doc/develop/west/
Dextensions.rst122 # This gets called when the user runs the command, e.g.:
161 runs ``west my-command-name``, since:
Dbuild-flash-debug.rst60 be compiled there after ``west build`` runs CMake to create a build system in
220 <build-dir>`` on subsequent runs to do incremental builds.
259 ``build.cmake-args`` configuration option. Whenever ``west build`` runs CMake
523 Note the capital H in the short option name. This re-runs the build
640 Note the capital H in the short option name. This re-runs the build
/Zephyr-latest/doc/
Dglossary.rst34 of the system, initializes it, and runs as the system's sole application.
103 A system thread that runs when there are no other threads ready to run.
/Zephyr-latest/boards/silabs/starter_kits/slstk3402a/doc/
Dindex.rst43 Code that is built for the Jade Gecko also runs on an equivalent Pearl Gecko.
/Zephyr-latest/arch/x86/zefi/
DREADME.txt89 It runs completely standalone, writing output to the current
/Zephyr-latest/doc/develop/test/
Dtwister_statuses.rst18 of Instances and Cases after the conclusion of their Twister runs.
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-arch.rst70 possible power consumption, since everything runs on a single IC.
167 SPI), while the Controller build runs either the
/Zephyr-latest/boards/beagle/beaglev_fire/doc/
Dindex.rst102 owner-hart: u54_1 # Primary hart that runs Zephyr
/Zephyr-latest/doc/services/device_mgmt/
Dec_host_cmd.rst79 The chip that runs Zephyr is a SPI slave and the ``cs-gpios`` property is used to point our CS pin.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_cli.rst120 The transfer runs until it either completes successfully for at least one Target node, or it is
/Zephyr-latest/samples/shields/x_nucleo_iks02a1/microphone/
DREADME.rst39 This sample runs with X-NUCLEO-IKS02A1 stacked on any board with a matching
/Zephyr-latest/boards/acrn/acrn/doc/
Dindex.rst8 ACRN hypervisor supports a hybrid scenario where Zephyr runs in a so-called
157 VM1's configuration so it runs on CPU2 and CPU3. If your ACRN setup has
/Zephyr-latest/doc/build/dts/
Dintro-input-output.rst40 describe the CPU or system-on-chip Zephyr runs on, perhaps by including other
/Zephyr-latest/boards/nxp/mimxrt1015_evk/doc/
Dindex.rst8 board design and layout for customers. The i.MX RT1015 runs on the Arm®
/Zephyr-latest/boards/ti/cc1352p7_launchpad/doc/
Dindex.rst124 …ence, we provide a `prebuilt binary <https://github.com/anobli/openocd/actions/runs/10566225265>`_.
/Zephyr-latest/samples/kernel/metairq_dispatch/
DREADME.rst47 thread always runs immediately after the ISR. It shows reliable,
/Zephyr-latest/samples/boards/nxp/mimxrt595_evk/system_off/
DREADME.rst87 These steps use the blhost tool that runs on a host computer running
/Zephyr-latest/doc/develop/debug/
Dindex.rst127 GDB provides a curses-based interface that runs in the terminal. Pass the ``--tui``
163 :command:`gdb` will not print the system console output as the application runs,
/Zephyr-latest/boards/arduino/nano_33_ble/doc/
Dindex.rst154 userScript Optional | Set user script that runs after system script execute done.
/Zephyr-latest/subsys/net/lib/dhcpv4/
DKconfig149 case it runs out of free addresses to assign.
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst116 known that all the code inside a particular C file runs exclusively in
130 all the code runs in supervisor mode and all APIs just directly call the
136 code runs in user mode and system calls are unconditionally made.
251 The verification function runs on the kernel side when a user thread makes

1234567