Home
last modified time | relevance | path

Searched refs:inside (Results 51 – 75 of 141) sorted by relevance

123456

/Zephyr-latest/share/zephyr-package/cmake/
DZephyrConfig.cmake136 # As this code is processed inside registered packages, we simply test if another package has a
DZephyrConfigVersion.cmake128 # As this code is processed inside registered packages, we simply test if
/Zephyr-latest/doc/connectivity/networking/
Dnetworking_with_multiple_instances.rst11 Zephyr instances. The Zephyr instances could be running inside QEMU
/Zephyr-latest/doc/develop/languages/c/
Dindex.rst106 * allocate memory blocks inside the ``z_malloc_partition`` memory partition
/Zephyr-latest/doc/develop/west/
Dwhy.rst57 would still need to be inside the main zephyr Git tree
Dwithout-west.rst35 :term:`west manifest` file inside that repository.
Dworkspaces.rst139 Projects can be located anywhere inside the workspace, but they may not
144 projects must have paths inside the workspace.
Dzephyr-cmds.rst219 You can print the offset of the descriptors inside the image using::
/Zephyr-latest/doc/hardware/arch/
Dx86.rst33 space before ``vm_enter`` inside :file:`arch/x86/core/ia32/crt0.S`.
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr.rst31 The management subsystem is located in :zephyr_file:`subsys/mgmt/` inside of
/Zephyr-latest/doc/develop/test/
Dtwister_statuses.rst28 ``Harness`` is a Python class inside Twister that allows us
/Zephyr-latest/scripts/ci/
Dpylintrc166 yield-inside-async-function,
/Zephyr-latest/boards/cdns/xt-sim/doc/
Dindex.rst121 sections that should be added to the default linker script linker.ld (inside
/Zephyr-latest/doc/services/debugging/
Dcoredump.rst234 You can use ``target remote |`` to start the custom GDB server from inside
410 as implemented in step 3 (inside :c:func:`arch_coredump_info_dump`).
/Zephyr-latest/doc/build/dts/
Dintro-input-output.rst26 The devicetree files inside the :file:`zephyr` directory look like this:
Dtroubleshooting.rst140 - Look inside that directory for relevant files until you figure out what the
171 Then you would look inside of :zephyr_file:`drivers/i2c` for the driver file
/Zephyr-latest/arch/arm/core/cortex_a_r/
DKconfig12 # related to that core. Everything else is captured inside the if
/Zephyr-latest/doc/kernel/usermode/
Dmemory_domain.rst235 which need to be placed inside a partition are tagged with their destination
262 /* The global variable var1 will be inside the bounds of my_partition
267 /* The global variable var2 will be inside the bounds of my_partition
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Ddfu_srv.rst119 the swap. This restart can be performed from inside the apply callback, or done asynchronously.
/Zephyr-latest/samples/net/gptp/
DREADME.rst27 A good way to run this sample is to run this gPTP application inside
/Zephyr-latest/doc/kernel/memory_management/
Dvirtual_memory.rst178 * The address returned is inside the virtual address space between
/Zephyr-latest/doc/hardware/peripherals/
Dmspi.rst34 MSPI bus inside the device driver initialization function:
/Zephyr-latest/doc/services/tfm/
Dbuild.rst62 key, which is stored inside the secure bootloader firmware image.
/Zephyr-latest/doc/develop/
Dbeyond-GSG.rst130 repository, switch branches in it, or perform a ``git bisect`` inside of
194 ``west boards`` from anywhere inside the ``zephyrproject`` directory for
/Zephyr-latest/doc/services/ipc/ipc_service/backends/
Dipc_service_icbmsg.rst191 (the same as inside received control message).
228 The data message starts with a header inside ``block number``.

123456