Home
last modified time | relevance | path

Searched refs:has (Results 126 – 150 of 1361) sorted by relevance

12345678910>>...55

/Zephyr-4.1.0/boards/atmel/sam0/samd20_xpro/doc/
Dindex.rst31 The `Microchip website`_ has detailed information about board
43 The SAMD20 MCU has 6 SERCOM based USARTs. One of the USARTs
50 The SAMD20 MCU has 6 SERCOM based SPIs. On the SAM D20 Xplained Pro,
/Zephyr-4.1.0/doc/connectivity/bluetooth/shell/audio/
Dgmap.rst5 Unlike most other low-layer profiles, GMAP is a profile that exists and has a service (GMAS) on all
12 When the Bluetooth stack has been initialized (:code:`bt init`), the GMAS can be registered by
46 (some logging has been omitted for clarity):
/Zephyr-4.1.0/boards/atmel/sam0/samr34_xpro/doc/
Dindex.rst36 The SAM R34 Xplained Pro evaluation kit has 3 GPIO controllers. These
74 The SAMR34 MCU has six SERCOM based USARTs with one configured as USART in
82 The SAMR34 MCU has 3 TCC based PWM units with up to 4 outputs each and a period
89 The SAMR34 MCU has 6 SERCOM based SPIs, with two configured as SPI in this BSP.
/Zephyr-4.1.0/boards/beagle/beagley_ai/doc/
Dindex.rst11 BeagleY-AI is powered by TI AM67A (J722S) SoC, which has two domains (Main,
36 a level or a pulse (both active-high). The VIM has two interrupt outputs per core
61 an A53 core has to load the program for the R5 core to the right memory
71 Note that BeagleY-AI has 4GB of DDR.
/Zephyr-4.1.0/boards/others/stm32_min_dev/doc/
Dindex.rst24 port for a specific board. Most of the GPIOs on the STM32 SoC has been exposed
27 Each board vendor has their own variations in pin mapping on their boards'
111 STM32 Minimum Development Board has 3 U(S)ARTs. The Zephyr console output is
117 The board has one on-board LED that is connected to PB12/PC13 on the black/blue
/Zephyr-4.1.0/boards/circuitdojo/feather/doc/
Dindex.rst49 The nRF9160 Feather has everything you know and love about
72 The nRF9160 Feather has a 2 pin battery connector on board. Lithium Polymer batteries >
78 The nRF9160 Feather has a built-in nano SIM (4FF) holder located
85 circuitdojo_feather_nrf9160 has a Tag Connect TC2030-CTX-NL. It can be used
/Zephyr-4.1.0/doc/services/resource_management/
Dindex.rst27 which has a binary state. Example applications are power rails, clocks,
30 The manager has the following properties:
50 cancellation has no effect on the in-progress transition.
52 progress: when the service has turned off successfully it will be
/Zephyr-4.1.0/lib/libc/
DKconfig24 Selected when the target has at least one C library that offers a
33 Selected when the target has support for the minimal C library
42 Selected when the target has support for the newlib C library
52 Selected when the target has support for picolibc.
/Zephyr-4.1.0/soc/nordic/nrf53/
DCMakeLists.txt14 application has the system clock disabled (CONFIG_SYS_CLOCK_EXISTS=n).
/Zephyr-4.1.0/share/sysbuild/images/bootloader/
DKconfig52 in main application if MCUboot has been built with MCUBOOT_DOWNGRADE_PREVENTION.
59 in main application if MCUboot has been built with MCUBOOT_DOWNGRADE_PREVENTION.
75 has been built with MCUBOOT_DOWNGRADE_PREVENTION.
101 will boot the application with the higher version from either slot, as long as it has
120 mode so that the bootloader is able to function until the application has booted.
125 MCUboot will only boot slot0_partition for the main application but has an entrance
/Zephyr-4.1.0/doc/releases/
Dmigration-guide-3.5.rst20 * The kernel :c:func:`k_mem_slab_free` function has changed its signature, now
37 * The default C library used on most targets has changed from the built-in
73 * Picolibc has four different printf/scanf variants supported in Zephyr,
138 * The RAM disk driver has been changed to support multiple instances and instantiation
160 * The ``zephyr,gpio-keys`` binding has been merged into
161 :dtcompatible:`gpio-keys` and the callback definition has been renamed from
166 previous implementation, any application using them has to be changed
178 (compatible with) SH1106. This has been replaced by a dedicated dts
220 * The LPC55XXX series SOC (except LPC55S06) default main clock has been
225 * The Kconfig option ``CONFIG_GPIO_NCT38XX_INTERRUPT`` has been renamed to
[all …]
/Zephyr-4.1.0/subsys/bluetooth/audio/
DKconfig.mctl44 # TODO: Remove dependency on BT_MCC once MCC has been reworked
53 # TODO: Remove dependency on BT_MCC_OTS once MCC has been reworked
/Zephyr-4.1.0/subsys/logging/backends/
DKconfig.swo28 frequency SWO operation. In this case the frequency has to be set
35 by the SWO viewer program has to match.
/Zephyr-4.1.0/boards/bbc/microbit/doc/
Dindex.rst10 The board is 4 cm × 5 cm and has an ARM Cortex-M0 processor, accelerometer and
21 The micro:bit has the following physical features:
/Zephyr-4.1.0/boards/vngiotlab/nrf52_vbluno52/doc/
Dindex.rst21 The VBLUno52 board has two external oscillators. The frequency of
49 The VBLUno52 board has an on-board DAPLink (CMSIS-DAP) interface for flashing and debugging.
/Zephyr-4.1.0/arch/arm/core/
Dvector_table.ld42 * For AArch32 (A/R), VBAR has Bits [4:0] = RES0.
43 * For AArch32 (M), VTOR has Bits [6:0] = RES0. Thus, vector start address
/Zephyr-4.1.0/doc/services/serialization/
Dnanopb.rst63 Nanopb has `generator options <https://jpa.kapsi.fi/nanopb/docs/reference.html#generator-options>`_
67 The internal CMake generator has an extension to configure ``*.options.in`` files automatically
/Zephyr-4.1.0/tests/subsys/fs/littlefs/
DCMakeLists.txt10 # a file has not been opened for.
/Zephyr-4.1.0/drivers/mdio/
DKconfig.nxp_enet19 Time in microseconds before an MDIO transaction that has not
/Zephyr-4.1.0/boards/nordic/nrf9161dk/
Dnrf9161dk_nrf9161_common_0_7_0.dtsi24 has-dpd;
/Zephyr-4.1.0/share/zephyr-package/cmake/
DZephyrConfigVersion.cmake9 # A better match would be an installed Zephyr that has a common index with current source dir.
35 # First check to see if user has provided a Zephyr base manually and it is first run (cache not set…
66 # package file is returned. This Zephyr version has already been printed
80 # User has pointed to a different Zephyr installation, so don't use this version
129 # another package has a common path with the current sample, and if so, we
/Zephyr-4.1.0/tests/drivers/can/host/
DREADME.rst15 The test suite has the following prerequisites:
70 Once the virtual SocketCAN interface has been created, brought up, and configured the test suite can
77 After the test suite has completed, the virtual SocketCAN interface can be removed again:
112 Once the SocketCAN interface has been brought up and configured the test suite can be launched using
119 After the test suite has completed, the SocketCAN interface can be brought down again:
/Zephyr-4.1.0/samples/subsys/modbus/tcp_gateway/
DREADME.rst16 This sample has been tested with FRDM-K64F board,
17 but it should work with any board or shield that has a network interface.
20 with another board that has been prepared according to the instructions in
/Zephyr-4.1.0/samples/boards/renesas/openamp_linux_zephyr/
DCMakeLists.txt13 # and rpmsg buffers. The METAL_MAX_DEVICE_REGIONS has to be redefined to add a
/Zephyr-4.1.0/boards/native/common/sdl/
DKconfig10 This option specifies that the target board has SDL support

12345678910>>...55