Home
last modified time | relevance | path

Searched refs:multi (Results 76 – 100 of 198) sorted by relevance

12345678

/Zephyr-latest/subsys/dfu/
DKconfig102 application is combined with MCUboot multi-image boot.
/Zephyr-latest/boards/shields/sparkfun_carrier_asset_tracker/doc/
Dindex.rst15 multi-regional use and GNSS capabilities via an integrated u-blox M8 GNSS
/Zephyr-latest/doc/build/sysbuild/
Dindex.rst93 Here is an example. For details, see :ref:`west-multi-domain-builds` in
113 Since sysbuild supports both single- and multi-image builds, this lets you
290 For more details, see :ref:`west-multi-domain-flashing`.
303 For more details, see :ref:`west-multi-domain-debugging`.
497 * A specific core on a physical board with a multi-core SoC, such as
729 Sometimes, in a multi-image build, you may want certain Zephyr applications to
771 You can include non-Zephyr applications in a multi-image build using the
/Zephyr-latest/doc/connectivity/bluetooth/
Dfeatures.rst42 * Concurrent multi-protocol support ready
/Zephyr-latest/doc/services/portability/posix/implementation/
Dindex.rst9 Unlike other multi-purpose POSIX operating systems
/Zephyr-latest/doc/services/storage/disk/
Dnvme.rst63 Note that NVME requires the target to support PCIe multi-vector MSI-X in order to function.
/Zephyr-latest/boards/beagle/beagleconnect_freedom/doc/
Dindex.rst7 Internet of Things board based on the SimpleLink multi-Standard CC1352P7 wireless MCU.
/Zephyr-latest/doc/hardware/peripherals/
Dmspi.rst6 The MSPI (multi-bit SPI) is provided as a generic API to accommodate
21 Zephyr's MSPI controller API may be used when a multi-bit SPI controller
/Zephyr-latest/doc/kernel/memory_management/
Dheap.rst115 applications that want to destroy a multi heap should simply ensure
124 uninspected by the multi heap code itself; instead it is passed to a
137 When unused, a multi heap may be freed via
/Zephyr-latest/boards/beagle/beagleplay/doc/
Dbeagleplay_cc1352p7.rst7 quad-core ARM Cortex-A53 SoC with an external TI SimpleLink multi-standard CC1352P7 wireless MCU
/Zephyr-latest/doc/build/dts/
Ddt-vs-kconfig.rst38 As another example, consider a device with a 2.4GHz, multi-protocol radio
/Zephyr-latest/tests/kernel/poll/src/
Dtest_poll.c628 static void multi(void *p1, void *p2, void *p3) in multi() function
673 multi, 0, 0, 0, main_low_prio - 1, in ZTEST()
/Zephyr-latest/boards/waveshare/rp2040_zero/doc/
Dindex.rst18 - 29 × multi-function GPIO pins (20× via edge pinout, others via solder points).
/Zephyr-latest/cmake/compiler/gcc/
Dtarget.cmake91 COMMAND ${CMAKE_C_COMPILER} ${TOOLCHAIN_C_FLAGS} --print-multi-directory
/Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/doc/
Dindex.rst254 Info : fpgasoc.cpu.0: MPIDR level2 0, cluster 0, core 0, multi core, no SMT
290 Info : fpgasoc.cpu.0: MPIDR level2 0, cluster 0, core 0, multi core, no SMT
317 Info : fpgasoc.cpu.0: MPIDR level2 0, cluster 0, core 0, multi core, no SMT
/Zephyr-latest/drivers/sensor/maxim/max30101/
DKconfig65 Set to operate in multi-LED mode. The green, red, and/or IR LED
/Zephyr-latest/samples/boards/nordic/mesh/onoff-app/
DREADME.rst10 This is a simple application demonstrating a Bluetooth Mesh multi-element node.
/Zephyr-latest/doc/services/portability/posix/conformance/
Dindex.rst147 design and capabilities. For example, multi-processing, ad-hoc memory-mapping, multiple users,
/Zephyr-latest/doc/services/input/
Dindex.rst19 multi-axis device have been reported.
/Zephyr-latest/doc/build/flashing/
Dconfiguration.rst9 configuring when commands are ran for groups of board targets. As an example: a multi-core SoC
/Zephyr-latest/lib/posix/options/
DKconfig.profile89 PSE52. Additionally, it includes interfaces for POSIX multi-processing, networking, pipes,
/Zephyr-latest/scripts/west_commands/completion/
Dwest-completion.zsh236 '--sysbuild[create multi-domain build system]'
237 '--no-sysbuild[do not create multi-domain build system]'
/Zephyr-latest/doc/hardware/arch/
Dx86.rst80 the necessary multi-level page tables for code execution and data access
/Zephyr-latest/samples/philosophers/
DREADME.rst10 An implementation of a solution to the Dining Philosophers problem (a classic multi-thread
/Zephyr-latest/doc/services/ipc/ipc_service/
Dipc_service.rst29 Endpoint prioritization and multi-instance ability highly depend on the backend

12345678