Home
last modified time | relevance | path

Searched refs:using (Results 1676 – 1700 of 1710) sorted by relevance

1...<<616263646566676869

/Zephyr-4.1.0/doc/connectivity/bluetooth/autopts/
Dautopts-linux.rst126 ``192.168.56.0/21`` range to be assigned to host-only adapters, so if using a static address with
/Zephyr-4.1.0/doc/connectivity/bluetooth/
Dbluetooth-ctlr-arch.rst424 .. [2] When not using pre-defined PPI channels
/Zephyr-4.1.0/boards/nxp/mimxrt595_evk/doc/
Dindex.rst284 Remote debugging using :2331
/Zephyr-4.1.0/boards/nxp/mimxrt685_evk/doc/
Dindex.rst324 Remote debugging using :2331
/Zephyr-4.1.0/doc/connectivity/networking/api/
Dnet_l2.rst130 and fragments need to be compressed using a protocol like 6LoWPAN before being
Dhttp_server.rst79 using CMake:
/Zephyr-4.1.0/doc/kernel/usermode/
Doverview.rst139 granted by a supervisor thread using the memory domain APIs. Newly created
/Zephyr-4.1.0/doc/hardware/porting/
Dsoc_porting.rst256 The :file:`Kconfig` will often indicate given hardware support using a setting
/Zephyr-4.1.0/doc/build/kconfig/
Dtips.rst76 type phandle-array in the device binding, and using the
79 to other nodes in the system. Search the source code for drivers using these
198 An objection to using ``depends on`` here might be that configuration files
/Zephyr-4.1.0/boards/arm/v2m_musca_b1/doc/
Dindex.rst371 Connect the V2M Musca B1 to your host computer using the USB port. You should
/Zephyr-4.1.0/boards/nxp/mimxrt1160_evk/doc/
Dindex.rst272 core. When building using sysbuild targeting the M4 core, a minimal "launcher"
/Zephyr-4.1.0/boards/adi/max32675evkit/doc/
Dindex.rst390 be connected to the standard 2*5 pin debug connector (JH2) using an
/Zephyr-4.1.0/cmake/linker/armlink/
Dscatter_script.cmake8 # - Symbol translation using a steering file is configured.
/Zephyr-4.1.0/
DLICENSE150 appropriateness of using or redistributing the Work and assume any
DCMakeLists.txt32 You may be using a mix of symbolic links and real paths which causes \
763 # when using depend on directory level.
765 # using a trigger file.
2099 # If not using a separate target for generating logging dictionary
/Zephyr-4.1.0/dts/arm/st/l5/
Dstm32l5.dtsi138 /* using maximum erase time(ms) for 4K page, since
/Zephyr-4.1.0/doc/contribute/
Dexternal.rst143 documentation using a pre-defined template. This type of modules exists outside the
/Zephyr-4.1.0/modules/trusted-firmware-m/
DCMakeLists.txt529 The device will be provisioned using dummy keys and is NOT secure!
DKconfig.tfm339 Add sharing of application specific data using the same
/Zephyr-4.1.0/doc/security/
Dsecure-coding.rst116 be realized using the configuration management. Each functionality
/Zephyr-4.1.0/boards/st/steval_stwinbx1/doc/
Dindex.rst336 usb 3-1: new full-speed USB device number 16 using xhci_hcd
/Zephyr-4.1.0/doc/connectivity/bluetooth/shell/audio/
Dcap.rst200 The following commands will setup a CAP broadcast source using the 16_2_1 preset (defined by BAP):
/Zephyr-4.1.0/boards/phytec/reel_board/doc/
Dindex.rst482 when not using root for flashing.
/Zephyr-4.1.0/tests/cmake/zephyr_get/
DCMakeLists.txt195 # Environment is not cached when using MERGE.
/Zephyr-4.1.0/doc/build/dts/
Dintro-syntax-structure.rst402 You can write a phandle using ``&foo``, where ``foo`` is a :ref:`node label

1...<<616263646566676869