Searched refs:has (Results 626 – 650 of 1361) sorted by relevance
1...<<21222324252627282930>>...55
/Zephyr-4.1.0/boards/nxp/rddrone_fmuk66/doc/ |
D | index.rst | 94 The K66F SoC has six UARTs. LPUART0 is configured for the console, UART0 is labeled Serial 2, 101 The K66F SoC has a USB OTG (USBOTG) controller that supports both
|
/Zephyr-4.1.0/boards/adafruit/nrf52_adafruit_feather/doc/ |
D | index.rst | 43 The `Adafruit Feather nRF52 Bluefruit Learning Guide`_ has detailed 64 This board version is the recommended one to use. It has the SWD header
|
/Zephyr-4.1.0/boards/st/nucleo_f411re/doc/ |
D | index.rst | 65 Nucleo F411RE Board has 8 GPIO controllers. These controllers are responsible for pin muxing, 104 Nucleo F411RE board has 3 UARTs. The Zephyr console output is assigned to UART2.
|
/Zephyr-4.1.0/boards/st/stm32f412g_disco/doc/ |
D | index.rst | 80 STM32F412G-DISCO Discovery kit has 8 GPIO controllers. These controllers are responsible for pin mu… 104 The STM32F412G Discovery kit has up to 4 UARTs. The Zephyr console output is assigned to UART2.
|
/Zephyr-4.1.0/boards/st/stm32f413h_disco/doc/ |
D | index.rst | 83 STM32F413H-DISCO Discovery kit has 8 GPIO controllers. These controllers are responsible for pin mu… 105 The STM32F413H-DISCO Discovery kit has up to 10 UARTs. The Zephyr console output is assigned to UAR…
|
/Zephyr-4.1.0/boards/st/stm32f469i_disco/doc/ |
D | index.rst | 80 STM32F469I-DISCO Discovery kit has 9 GPIO controllers. These controllers are responsible for pin mu… 110 The STM32F469 Discovery kit has up to 8 UARTs. The Zephyr console output is assigned to UART3.
|
/Zephyr-4.1.0/boards/st/nucleo_f446re/doc/ |
D | index.rst | 70 Nucleo F446RE Board has 8 GPIO controllers. These controllers are responsible for pin muxing, 116 Nucleo F446RE board has 2 UARTs and 4 USARTs. The Zephyr console output is assigned to UART2.
|
/Zephyr-4.1.0/boards/st/stm32f723e_disco/doc/ |
D | index.rst | 68 STM32F723E Discovery kit has 7 GPIO controllers. These controllers are responsible for pin muxing, 97 The STM32F723E Discovery kit has up to 8 UARTs. The Zephyr console output is assigned to UART6
|
/Zephyr-4.1.0/subsys/random/ |
D | Kconfig | 47 If the entropy support of the platform has sufficient performance 108 If the hardware entropy support of the platform has sufficient
|
/Zephyr-4.1.0/soc/silabs/ |
D | Kconfig | 132 Set if the SoC has a True Random Number Generator (TRNG) module. 300 If enabled, indicates that the SoC has a Radio PHY. 316 management, sending and receiving packets on radio phy. User has
|
/Zephyr-4.1.0/doc/connectivity/bluetooth/api/mesh/ |
D | provisioning.rst | 97 device packaging). Note that even if the unprovisioned device has specified 157 After the device has been successfully authenticated, the provisioner 182 attacks. In response, the Bluetooth SIG has reclassified these OOB methods as
|
/Zephyr-4.1.0/boards/nxp/mimxrt700_evk/doc/ |
D | index.rst | 9 The main-compute subsystem has a primary Arm® Cortex®-M33 running at 325 MHz, with an integrated 11 The sense-compute subsystem has a second Arm® Cortex®-M33 and an integrated Cadence® Tensilica® 108 The MIMXRT798 SoC has IOCON registers, which can be used to configure the
|
/Zephyr-4.1.0/doc/connectivity/bluetooth/shell/audio/ |
D | tbs.rst | 24 When the Bluetooth stack has been initialized (:code:`bt init`), 25 and a device has been connected, the telephone bearer service client can 35 the telephone bearers on the server. If the server has both GTBS and TBS,
|
/Zephyr-4.1.0/boards/adafruit/feather_esp32s3_tft/doc/ |
D | index.rst | 86 The `Adafruit Feather ESP32-S3 TFT User Guide`_ has detailed information about 219 After the board has automatically reset and booted, you should see the following 233 ESP32-S3 has a built-in JTAG circuitry and can be debugged without any
|
/Zephyr-4.1.0/doc/hardware/cache/ |
D | guide.rst | 97 Zephyr has the ability to automatically define an uncached region in memory and 140 processor has written to it and before a remote bus master reads from that 154 region. Invalidate the data cache of a buffer that a peripheral has written to
|
/Zephyr-4.1.0/doc/services/device_mgmt/ |
D | mcumgr_handlers.rst | 57 header file (as upstream Zephyr has) can be used to distribute group IDs more easily. 75 central index header file (as upstream Zephyr has) can be used to distribute event IDs more 91 this function handler has an optional notification callback feature that allows other parts of
|
/Zephyr-4.1.0/boards/antmicro/myra_sip_baseboard/doc/ |
D | index.rst | 210 The Myra SiP Baseboard has 5 U(S)ARTs. The Zephyr console output is assigned to LPUART1. The default 221 This board has a USB-JTAG interface and can be used with OpenOCD. 238 …The board has only one port that is used for both programming and the console. For this reason, it…
|
/Zephyr-4.1.0/boards/nxp/mimxrt1160_evk/doc/ |
D | index.rst | 77 This platform has the following external memories: 156 The MIMXRT1160 SoC has six pairs of pinmux/gpio controllers. 218 Only the first 16K of ocram2 has the correct MPU region attributes set to be 236 The MIMXRT1160 SoC has 12 UARTs. One is configured for the console and the
|
/Zephyr-4.1.0/arch/arm/core/ |
D | Kconfig | 61 # GDBSTUB has not yet been tested on Cortex M or R SoCs 214 still has the option to manually select the MPU-based 230 Code executing in Secure state has access to both the Secure 254 Code executing in Non-Secure state has no access to Secure
|
/Zephyr-4.1.0/doc/kernel/ |
D | timeutil.rst | 124 * A time scale is *continuous* if the representation has no abrupt changes in 149 time has a fixed offset from UT at any given instant, primarily 159 these scales assume that every day has exactly 86400 seconds. In normal use 191 The Zephyr tick counter has no concept of leap seconds or standard time
|
/Zephyr-4.1.0/doc/services/rtio/ |
D | index.rst | 94 In order to know when a sqe has completed there is a completion 129 SQE has not yet started, it's likely that a call to :c:func:`rtio_sqe_cancel` 145 The memory pool has 128 blocks, each block has the size of 16 bytes, and the data
|
/Zephyr-4.1.0/drivers/wifi/esp32/ |
D | Kconfig.esp32 | 106 is freed after the higher layer has successfully received the data frame. 125 The buffer is freed after the data frame has been sent by the WiFi driver. 200 …received. The MGMT buffer is freed after the MGMT data frame has been processed by the WiFi driver. 314 …during this period, the time will be refreshed. If the time is up, but the station still has packe… 322 Only for station in WIFI_PS_MIN_MODEM or WIFI_PS_MAX_MODEM. If no packet has been
|
/Zephyr-4.1.0/doc/releases/ |
D | release-notes-3.3.rst | 124 * Python's argparse argument parser usage in Zephyr scripts has been updated 165 it has too wide scope (full Backup RAM reset). Replaced by 292 * SPI DT :c:func:`spi_is_ready` function has been deprecated in favor of :c:func:`spi_is_ready_dt`. 294 * LwM2M APIs using string references as LwM2M paths has been deprecated in favor of functions 545 * The scratch partition has been removed for the following Nordic boards and 567 * The default console for the ``nrf52840dongle_nrf52840`` board has been 577 On some boards, previous PLL SAI configuration has been changed to above options, 598 * ``zephyr_code_relocate`` API has changed to accept a list of files to 604 has been fixed. 606 * Issue with board revision not being passed to sysbuild images has been [all …]
|
/Zephyr-4.1.0/doc/kernel/usermode/ |
D | syscalls.rst | 63 to determine the data types of its return value and arguments, and has some 266 the calling thread has permission on it. 269 calling thread has read or write permissions on the provided buffer. 273 Verification functions involve a great deal of boilerplate code which has been 284 has permissions on it, and that the object is initialized. 327 the calling thread has permissions on it, and that the driver has been 373 user thread that has access to the memory that parameter points to. If the 484 should never be used to verify if resource allocation has been successful. 618 thread is aborted, as the function has no return value.
|
/Zephyr-4.1.0/soc/espressif/common/ |
D | Kconfig | 13 ESP32 SoC has multiple revisions, some of which are not supported by the current
|
1...<<21222324252627282930>>...55