Home
last modified time | relevance | path

Searched refs:has (Results 601 – 625 of 1361) sorted by relevance

1...<<21222324252627282930>>...55

/Zephyr-4.1.0/boards/nordic/nrf54l20pdk/doc/
Dindex.rst28 nRF54L20 PDK has two crystal oscillators:
/Zephyr-4.1.0/doc/hardware/peripherals/
Dsmbus.rst23 Zephyr has API for the Controller role.
Di2c.rst22 support the target mode. Zephyr has API for both roles.
/Zephyr-4.1.0/doc/connectivity/networking/
Darmfvp_user_networking_setup.rst34 need any configurations on the host system. This feature has been enabled in
/Zephyr-4.1.0/boards/fanke/fk7b0m1_vbt6/
Dfk7b0m1_vbt6.dts117 has-dpd;
/Zephyr-4.1.0/doc/services/virtualization/
Divshmem.rst35 the :kconfig:option:`CONFIG_IVSHMEM_MSI_X_VECTORS` has to be tweaked to the number of
/Zephyr-4.1.0/boards/actinius/icarus_som_dk/
Dactinius_icarus_som_dk_common.dtsi144 has-dpd;
/Zephyr-4.1.0/boards/adafruit/qt_py_esp32s3/
Dadafruit_qt_py_esp32s3_procpu.dts128 * Unlike some of the other Adafruit boards, the neopixel on this board has
/Zephyr-4.1.0/boards/actinius/icarus_bee/
Dactinius_icarus_bee_common.dtsi145 has-dpd;
/Zephyr-4.1.0/doc/connectivity/bluetooth/api/mesh/
Ddfu.rst88 time-consuming Distribution stage. Once the firmware has been uploaded to the Distributor, the
100 mesh network perform other duties. Once the firmware image has been transferred to the Target
126 well as any preparation the Target node has to make before the image is applied. Typical metadata
290 Once the Distributor has stored a firmware image and received a list of Target nodes, the Initiator
311 #. Once the BLOB transfer has been received, the Target nodes' applications verify that the firmware
317 If the distribution procedure completed with at least one Target node reporting that the image has
350 each Target node, and scans through the list to make sure that the new firmware ID has replaced
365 request has timed out, the distribution procedure is cancelled. After this the distribution
/Zephyr-4.1.0/doc/project/
Drelease_process.rst69 new features has passed, and that the time to stabilize the next release of the
70 code base has begun.
207 v[Major].[Minor+1] has started. For example, v1.7.99 will be tagged at the
257 Zephyr LTS development cycle differs from regular releases and has an extended
418 Each release has a GitHub issue associated with it that contains the full
462 #. Verify that the tag has been signed correctly, ``git show`` for the
482 When all final release criteria has been met and the final release notes
500 #. Verify that the tag has been signed correctly, ``git show`` for the
/Zephyr-4.1.0/doc/releases/
Drelease-notes-3.2.rst48 * The :kconfig:option:`CONFIG_LEGACY_INCLUDE_PATH` option has been disabled by
62 * :zephyr_file:`include/zephyr/zephyr.h` has been deprecated in favor of
74 to :zephyr_file:`include/zephyr/net/socketcan.h`, the SocketCAN ``struct can_frame`` has been
75 renamed to :c:struct:`socketcan_frame`, and the SocketCAN ``struct can_filter`` has been renamed
79 * The CAN controller ``struct zcan_frame`` has been renamed to :c:struct:`can_frame`, and ``struct
80 zcan_filter`` has been renamed to :c:struct:`can_filter`.
90 * The error code for :c:func:`can_send` when the CAN controller is in bus off state has been
347 * The handling of GATT multiple notifications has been rewritten, and is now
508 * A driver for bridging from ``native_posix`` to Linux SocketCAN has been added.
509 * A driver for the Espressif ESP32 TWAI has been added. See the
[all …]
/Zephyr-4.1.0/samples/subsys/shell/fs/
DREADME.rst89 'prj_flash_load.conf' configuration file. It has defined a larger RX buffer.
96 Once the board has booted, you will be presented with a shell prompt.
/Zephyr-4.1.0/boards/shields/amg88xx/doc/
Dindex.rst60 These shields can only be used with a board that has Arduino connectors and
121 The wiring has to be done according to
/Zephyr-4.1.0/boards/silabs/dev_kits/sltb004a/doc/
Dindex.rst51 The EFR32MG12 SoC has eight gpio controllers (PORTA, PORTB, PORTC, PORTD,
103 The EFR32MG12 SoC has four USARTs and one Low Energy UARTs (LEUART with 9600
/Zephyr-4.1.0/boards/silabs/starter_kits/slstk3402a/doc/
Dindex.rst52 The EFM32PG12 SoC has twelve GPIO controllers (PORTA to PORTL), but only four
96 The EFM32PG12 SoC has four USARTs and one Low Energy UART (LEUART).
/Zephyr-4.1.0/boards/phytec/phyboard_electra/doc/
Dindex.rst74 The board has 2GB of DDR RAM available. This board configuration
86 The phyCORE-AM64x has a heartbeat LED connected to gpio6. It's configured
/Zephyr-4.1.0/cmake/flash/
DCMakeLists.txt121 # Usually, the runner has arguments. Append them to runners.yaml,
187 # This script will print an error message and fail if <target> has added
/Zephyr-4.1.0/boards/blues/swan_r5/doc/
Dindex.rst20 The board has three independent power options---USB, Battery, or Line
156 Swan has 4 U(S)ARTs. The Zephyr console output is
/Zephyr-4.1.0/boards/seeed/xiao_esp32c3/doc/
Dindex.rst15 has an USB-C port for programming and debugging, integrated battery charging
151 After the board has automatically reset and booted, you should see the following
/Zephyr-4.1.0/kernel/
DKconfig.smp75 to check if schedule IPI has called or not, for testing
92 IPIs to specific CPUs then this has the potential to significantly
/Zephyr-4.1.0/boards/96boards/stm32_sensor_mez/doc/
Dindex.rst127 96Boards STM32 Sensor Mezzanine board has up to 3 I2Cs. The default I2C
139 96Boards STM32 Sensor Mezzanine board has 3 SPIs. SPI1 is used in slave mode
/Zephyr-4.1.0/boards/st/stm32f072b_disco/doc/
Dindex.rst70 STM32F072B-DISCO Discovery kit has 6 GPIO controllers. These controllers are
104 STM32F072B-DISCO Discovery kit has up to 4 UARTs. The Zephyr console output
/Zephyr-4.1.0/boards/96boards/carbon/doc/
Dnrf51822.rst23 The 96Boards Carbon nRF51 has two external oscillators. The frequency
61 96Boards Carbon nRF51 has one SPI, which for providing Bluetooth
/Zephyr-4.1.0/doc/services/llext/
Dload.rst12 which has a set of function pointers that provide the necessary functionality
48 function can be used to minimize boilerplate code. This function has a

1...<<21222324252627282930>>...55