Home
last modified time | relevance | path

Searched refs:using (Results 1576 – 1600 of 1710) sorted by relevance

1...<<616263646566676869

/Zephyr-4.1.0/boards/witte/linum/doc/
Dindex.rst147 The LINUM-STM32H753BI has a ethernet connection using the transceiver KSZ8081RNACA.
/Zephyr-4.1.0/cmake/modules/
DFindZephyr-sdk.cmake7 # It is possible to control the behavior of the Zephyr-SDK package using
/Zephyr-4.1.0/doc/build/dts/
Dintro-input-output.rst54 :file:`BOARD.dts` can be extended or modified using *overlays*. Overlays are
/Zephyr-4.1.0/boards/adi/max32662evkit/doc/
Dindex.rst223 be connected to the standard 2*5 pin debug connector (J3) using an
/Zephyr-4.1.0/boards/adi/max32672fthr/doc/
Dindex.rst6 sensor solutions using the MAX32672 Arm® Cortex®-M4. The board also includes the MAX8819 PMIC for
/Zephyr-4.1.0/boards/ti/cc1352p7_launchpad/doc/
Dindex.rst103 console using the XDS110 application serial port.
/Zephyr-4.1.0/doc/kernel/object_cores/
Dindex.rst73 An object type is defined using a global variable of type
/Zephyr-4.1.0/doc/kernel/services/data_passing/
Dfifos.rst71 A FIFO is defined using a variable of type :c:struct:`k_fifo`.
Dmailboxes.rst36 Messages exchanged using a mailbox are handled non-anonymously,
118 A mailbox is defined using a variable of type :c:struct:`k_mbox`.
357 producing thread, using the immediate data retrieval technique. The message
/Zephyr-4.1.0/arch/arm/core/cortex_a_r/
DKconfig11 # select which core they are using without having to select all the options
/Zephyr-4.1.0/boards/nxp/mimxrt685_evk/
Dmimxrt685_evk_mimxrt685s_cm33.dts409 /* Disable this node if not using USB and need another MPU region */
/Zephyr-4.1.0/
DCODE_OF_CONDUCT.md55 Examples of representing our community include using an official e-mail address,
/Zephyr-4.1.0/boards/nxp/frdm_ke17z512/doc/
Dindex.rst80 The KE17Z9 SoC is configured to run at 48 MHz using the FIRC.
/Zephyr-4.1.0/boards/nxp/usb_kw24d512/doc/
Dindex.rst152 The console is available using `Segger RTT`_.
/Zephyr-4.1.0/boards/adi/max32655fthr/doc/
Dindex.rst6 ultra low-power wireless solutions using MAX32655 Arm© Cortex®-M4F and Bluetooth® 5.2 Low Energy (L…
/Zephyr-4.1.0/boards/nxp/mimxrt1050_evk/doc/
Dindex.rst308 setup of the board using hyperflash.
416 Remote debugging using :2331
/Zephyr-4.1.0/doc/releases/
Drelease-notes-1.5.rst258 * ``ZEP-695`` - FatFs doesn't compile using Newlib
277 * ``ZEP-467`` - Hang using UART and console.
/Zephyr-4.1.0/doc/connectivity/networking/conn_mgr/
Dimplementation.rst22 …plementations to be :ref:`defined <conn_mgr_impl_defining>` at build time using :c:macro:`CONN_MGR…
26 Once defined, you can reference implementations by name and bind them to any unbound iface using :c…
120 If you are using :c:macro:`CONN_MGR_CONN_DECLARE_PUBLIC`, declare this type alongside the declarati…
/Zephyr-4.1.0/modules/hal_nordic/nrfx/
DCMakeLists.txt189 # is using hfpll as CPU clock source (true for all existing devices).
/Zephyr-4.1.0/drivers/serial/
DKconfig131 Module implements handling of reception of variable length data using
/Zephyr-4.1.0/samples/drivers/dac/
DREADME.rst5 Generate an analog sawtooth signal using the DAC driver API.
/Zephyr-4.1.0/subsys/llext/
DKconfig59 flags. Some platforms can benefit from using -fPIC instead, in which case
/Zephyr-4.1.0/boards/raytac/mdbt53v_db_40/doc/
Dindex.rst7 using Nordic Semiconductor nRF5340 ARM Cortex-M33 SoC. Its design concept is to connect all
/Zephyr-4.1.0/boards/weact/mini_stm32h743/doc/
Dindex.rst130 the device using the west tool or the STM32CubeProgrammer.
/Zephyr-4.1.0/boards/nordic/nrf52833dk/doc/
Dindex.rst231 while using the nRF52833 Development Kit (PCA10100).

1...<<616263646566676869