Home
last modified time | relevance | path

Searched full:itself (Results 1 – 25 of 480) sorted by relevance

12345678910>>...20

/Zephyr-latest/tests/ztest/fail/
DREADME.rst19 The binary by itself, when executed, will fail to run and return a code of ``1``. The main test
21 the output. The output itself cannot be printed to the log as it will confuse ``twister`` by
/Zephyr-latest/drivers/flash/
DKconfig.mcux104 flash itself.
113 flash itself.
/Zephyr-latest/doc/build/dts/
Dintro-scope-purpose.rst22 *devicetree bindings*. The sources contain the devicetree itself. The bindings
39 The API itself is based on C macros. The macro names all start with ``DT_``. In
/Zephyr-latest/boards/nxp/lpcxpresso11u68/
Dlpcxpresso11u68_defconfig6 # so that the application has more RAM for itself.
/Zephyr-latest/boards/weact/mini_stm32h7b0/
Dmini_stm32h7b0_defconfig19 # Logger cannot use itself to log
/Zephyr-latest/boards/qorvo/decawave_dwm1001_dev/doc/
Dindex.rst12 board, `Qorvo (Decawave) DWM1001 website`_ about the board itself, and `nRF52832 website`_ for the
13 official reference on the IC itself.
/Zephyr-latest/boards/qorvo/decawave_dwm3001cdk/doc/
Dindex.rst16 itself, and `nRF52833 website`_ for the official reference on the IC itself.
/Zephyr-latest/lib/libc/picolibc/
Derrno_wrap.c12 * Picolibc needs to be able to declare this itself so that the library
/Zephyr-latest/drivers/bluetooth/
DKconfig10 # Controller support is an HCI driver in itself, so these HCI driver
/Zephyr-latest/subsys/testsuite/arch/unit_testing/
DKconfig11 The unit_testing architecture identifies itself as X86 for basic
/Zephyr-latest/doc/contribute/
Dproposals_and_rfcs.rst24 include code changes to Zephyr itself.
43 The process in itself consists in creating a GitHub issue with the :ref:`RFC
/Zephyr-latest/cmake/
Dtarget_toolchain_flags.cmake5 # * The MD5 sum of the compiler itself. A MD5 checksum is taken of the content
8 # * The CMAKE_C_COMPILER itself. This may be a symlink, but it ensures that
/Zephyr-latest/modules/trusted-firmware-a/
DKconfig13 itself is to be executed in the Non-Secure Processing Environment.
/Zephyr-latest/tests/subsys/openthread/
Dradio_stub.c26 /* file itself */
/Zephyr-latest/subsys/net/l2/dummy/any/
DKconfig10 itself. It can be used for example to hook virtual interfaces
/Zephyr-latest/include/zephyr/
Dfatal.h57 * itself, and should not be considered recoverable. There is an assertion
60 * the kernel itself may be in an inconsistent state, with API calls to
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/bridge/
Dbrg_ivu.sh11 # 2. Provisioner configures itself and creates subnets equal to number of non-bridge devices.
Dbrg_persistent_storage.sh10 # 1. Tester configures itself and creates subnets equal to number of non-bridge nodes.
/Zephyr-latest/dts/bindings/mtd/
Dst,stm32-nv-flash.yaml2 STM32 flash memory. This binding is for the flash memory itself, not
/Zephyr-latest/subsys/bluetooth/services/nus/
DKconfig.nus14 the other services, where the Service is hosted by the subsystem itself.
/Zephyr-latest/boards/shields/nrf7002ek/boards/
Dnrf9160dk_nrf9160_ns.overlay15 * GPIO pin used by extender itself conflicts with Wi-Fi (0.6), so,
/Zephyr-latest/boards/
DKconfig.v223 Contains the qualifiers of the board being used without the name of the board itself.
/Zephyr-latest/boards/makerdiary/nrf52840_mdk_usb_dongle/
DKconfig.defconfig18 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/provision/
Dpb_remote_reprovision.sh8 # 1. A provisioner with the RPR client provisions itself;
/Zephyr-latest/doc/services/device_mgmt/
Ddfu.rst60 is the boot loader used with Zephyr. The source code itself is hosted in the
80 4. You need to build and flash MCUboot itself on your device

12345678910>>...20