Home
last modified time | relevance | path

Searched refs:their (Results 226 – 250 of 360) sorted by relevance

12345678910>>...15

/Zephyr-latest/doc/build/cmake/
Dindex.rst75 scripts also do some processing of their own, which is explained here.
158 together to bind potential system call functions with their
/Zephyr-latest/doc/contribute/documentation/
Dguidelines.rst22 and about `Sphinx extensions`_ from their respective websites.
186 There are a few ways to create tables, each with their limitations or
492 showcasing an interactive session with command(s) and their output.
515 * - An interactive shell session with command(s) and their output
529 * - An interactive Zephyr shell session, with commands and their outputs
/Zephyr-latest/doc/kernel/services/threads/
Dindex.rst188 require their regions to be of some power of two in size, and aligned to its
280 according to their normal priority, but also have the special ability
296 threads and run on their own stack (which must be allocated normally),
/Zephyr-latest/boards/vcc-gnd/yd_esp32/doc/
Dindex.rst16 Shanghai-based Chinese company, and is manufactured by TSMC using their 40nm
/Zephyr-latest/boards/seeed/lora_e5_dev_board/doc/
Dlora_e5_dev_board.rst135 A list of the devices and their power rails:
/Zephyr-latest/arch/xtensa/
DKconfig39 SoC or boards might define their own __start by setting this setting
/Zephyr-latest/doc/services/mem_mgmt/
Dindex.rst55 list of memory regions and their attributes are compiled in a user-accessible
/Zephyr-latest/doc/build/kconfig/
Dmenuconfig.rst29 configuration file only lists symbols that differ from their default value.
/Zephyr-latest/tests/ztest/error_hook/
DREADME.txt18 of defining their own.
/Zephyr-latest/doc/introduction/
Dindex.rst95 needs them, and to specify their quantity and size.
/Zephyr-latest/doc/build/dts/
Dintro-syntax-structure.rst56 Devicetree nodes have *paths* identifying their locations in the tree. Like
401 - Property values refer to other nodes in the devicetree by their *phandles*.
/Zephyr-latest/modules/trusted-firmware-m/
DKconfig.tfm323 Alternatively, applications can point to their own paths for Ethos-U driver.
333 to their own checkout of this library, or set to DOWNLOAD to allow
/Zephyr-latest/doc/contribute/coding_guidelines/
Dindex.rst977 …hall not result in accesses beyond the bounds of the objects referenced by their pointer parameters
1089 their documentation from being generated. Their absence also prevents use of
1235 to their inclusion, should be modified to use module-specific versions of the macro name that
1254 9899:2011 standard, also known as C11, and their extensions:
1336 :ref:`common libc <c_library_common>` to ensure their availability across
1343 coding practices and it should not be assumed that their use in the Zephyr
1413 toolchains that come with their own C standard libraries.
/Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/
Dindex.rst11 their SWD interface, using an external adapter.
/Zephyr-latest/boards/st/stm32h745i_disco/doc/
Dindex.rst9 The full range of hardware features available on the board helps users enhance their application
/Zephyr-latest/boards/st/stm32h7b3i_dk/doc/
Dindex.rst15 their application development by an evaluation of almost all peripherals (such as
/Zephyr-latest/arch/arm64/core/
DKconfig212 instruction set to use 64-bit registers for their processing. The AArch32
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_handlers.rst11 :c:enum:`mcumgr_group_t` contains the management groups available in Zephyr with their
/Zephyr-latest/boards/espressif/esp32c6_devkitc/doc/
Dindex.rst229 OpenOCD that are not upstreamed yet. Espressif maintains their own fork of
/Zephyr-latest/doc/hardware/arch/
Darm-scmi.rst177 their own definition of :code:`pinctrl_configure_pins`, which should
/Zephyr-latest/doc/develop/west/
Dbasics.rst183 exist are updated in place by fetching and checking out their respective Git
/Zephyr-latest/kernel/
DKconfig.vm27 as their physical address (demand paging at runtime may later modify
/Zephyr-latest/doc/services/tracing/
Dindex.rst39 to enable additional tracing functions (or provide their own backend), zephyr
622 their usage. Currently, the following lists can be enabled::
647 Note that each list can be enabled or disabled via their tracing
/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt34 their ring field of the PTE that loaded them, via a simple translation
137 the data TLB, such that instruction fetches always find their TLB
/Zephyr-latest/doc/safety/
Dsafety_overview.rst85 overall safety. By following the standard, organizations can ensure that their safety-related
249 components, including their associated interfaces. This ensures that the components have no

12345678910>>...15