Home
last modified time | relevance | path

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

12345678910>>...17

/Zephyr-Core-3.5.0/boards/arm/bl654_usb/
DKconfig.defconfig19 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
49 # Logger cannot use itself to log
/Zephyr-Core-3.5.0/tests/ztest/fail/
DREADME.rst18 The binary by itself, when executed, will fail to run and return a code of ``1``. The main test
20 the output. The output itself cannot be printed to the log as it will confuse ``twister`` by
/Zephyr-Core-3.5.0/boards/arm/nrf52840dongle_nrf52840/
DKconfig.defconfig19 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
54 # Logger cannot use itself to log
/Zephyr-Core-3.5.0/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-Core-3.5.0/drivers/flash/
DKconfig.mcux92 flash itself.
101 flash itself.
/Zephyr-Core-3.5.0/boards/arm/lpcxpresso11u68/
Dlpcxpresso11u68_defconfig7 # so that the application has more RAM for itself.
/Zephyr-Core-3.5.0/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-Core-3.5.0/boards/arm/decawave_dwm1001_dev/doc/
Dindex.rst15 …wave DWM1001 website`_ about the board itself, and `nRF52832 website`_ for the official reference …
/Zephyr-Core-3.5.0/boards/arm/degu_evk/
DKconfig.defconfig26 # Logger cannot use itself to log
/Zephyr-Core-3.5.0/boards/arm/xiao_ble/
Dxiao_ble_defconfig22 # Logger cannot use itself to log
Dxiao_ble_sense_defconfig22 # Logger cannot use itself to log
/Zephyr-Core-3.5.0/dts/bindings/mtd/
Dst,stm32-nv-flash.yaml2 STM32 flash memory. This binding is for the flash memory itself, not
/Zephyr-Core-3.5.0/drivers/bluetooth/
DKconfig10 # Controller support is an HCI driver in itself, so these HCI driver
/Zephyr-Core-3.5.0/subsys/testsuite/arch/unit_testing/
DKconfig11 The unit_testing architecture identifies itself as X86 for basic
/Zephyr-Core-3.5.0/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-Core-3.5.0/samples/net/eth_native_posix/src/
Dmain.c15 /* This application itself does nothing as there is net-shell that can be used
/Zephyr-Core-3.5.0/modules/trusted-firmware-a/
DKconfig13 itself is to be executed in the Non-Secure Processing Environment.
/Zephyr-Core-3.5.0/tests/subsys/openthread/
Dradio_stub.c25 /* file itself */
/Zephyr-Core-3.5.0/include/zephyr/
Dfatal.h56 * itself, and should not be considered recoverable. There is an assertion
59 * the kernel itself may be in an inconsistent state, with API calls to
/Zephyr-Core-3.5.0/boards/arm/adafruit_itsybitsy_nrf52840/
DKconfig.defconfig40 # Logger cannot use itself to log
/Zephyr-Core-3.5.0/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
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/provision/
Dpb_remote_reprovision.sh8 # 1. A provisioner with the RPR client provisions itself;
Dpb_remote_parallel.sh8 # 1. A provisioner with the RPR client provisions itself;
/Zephyr-Core-3.5.0/arch/arm/core/cortex_a_r/
Dswap.c15 * arch_swap() itself does not do much.
/Zephyr-Core-3.5.0/boards/arm/nrf52840_mdk_usb_dongle/
DKconfig.defconfig21 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION

12345678910>>...17