Searched refs:has (Results 526 – 550 of 1361) sorted by relevance
1...<<21222324252627282930>>...55
/Zephyr-4.1.0/boards/st/b_l072z_lrwan1/doc/ |
D | index.rst | 116 B-L072Z-LRWAN1 Discovery kit has GPIO controllers. These controllers are responsible for pin muxing, 141 B-L072Z-LRWAN1 Discovery board has 2 U(S)ARTs. The Zephyr console output is assigned to UART2. 147 B-L072Z-LRWAN1 Discovery board has 1 USB device controller. However,
|
/Zephyr-4.1.0/boards/ezurio/bl654_sensor_board/doc/ |
D | bl654_sensor_board.rst | 10 This sensor board has the following features: 61 The BL654 Sensor Board has an on-board Bosch BME280 138 programmer which has a 9-pin ARM debug port can be used with a Tag-Connect
|
/Zephyr-4.1.0/boards/ezurio/bt510/doc/ |
D | bt510.rst | 8 The sensor has the following features: 155 for a suitable driver IC. The USB-SWD programming board has an in-built UART connected 181 of connecting an external debugger. The USB-SWD programmer board has a CMSIS debugger
|
/Zephyr-4.1.0/doc/connectivity/networking/api/ |
D | coap.rst | 26 On top of CoAP, Zephyr has support for LWM2M "Lightweight Machine 2 Machine" 149 libcoap has a script (``examples/etsi_coaptest.sh``) to test coap-server functionality 166 Eclipse has TTCN3 based tests to run against CoAP implementations.
|
/Zephyr-4.1.0/doc/develop/test/ |
D | coverage.rst | 35 device has enough RAM when enabling the coverage for it. For example a small device 59 has been printed: 176 environment has directories with symlinks then, to avoid incomplete ``gcovr`` reports,
|
/Zephyr-4.1.0/boards/nxp/frdm_mcxn236/doc/ |
D | index.rst | 99 The MCX-N236 SoC has 6 gpio controllers and has pinmux registers which 119 The FRDM-MCXN236 SoC has 8 FLEXCOMM interfaces for serial communication.
|
/Zephyr-4.1.0/boards/nxp/mimxrt1024_evk/doc/ |
D | index.rst | 63 This platform has the following external memories: 128 The MIMXRT1024 SoC has five pairs of pinmux/gpio controllers. 196 The MIMXRT1024 SoC has eight UARTs. One is configured for the console and the
|
/Zephyr-4.1.0/doc/connectivity/bluetooth/api/mesh/ |
D | brg_cfg.rst | 48 A Subnet Bridge node is a node in a Bluetooth Mesh network that belongs to multiple subnets and has 53 The Subnet Bridge node has a primary subnet, based on the primary NetKey, which handles the 87 The Subnet Bridge has the following states:
|
D | blob_srv.rst | 49 Once the transfer has been set up on the BLOB Transfer Server, it's ready for receiving the BLOB. 92 complete. If the BLOB Transfer Client has already given up the transfer, the BLOB Transfer Server
|
/Zephyr-4.1.0/doc/services/logging/ |
D | cs_stm.rst | 11 access the STM without being aware of each other. Each core has 65536 stimulus ports (identical 18 Local domain (each core) has access to its own set of STMESP peripherals. Each set has registers fo… 78 STM logging has 2 modes of operations: 114 When using logs, this method has the following advantages: 182 removed from the binary. This mode uses more read-only memory and has lower throughput because
|
/Zephyr-4.1.0/samples/net/dhcpv4_client/ |
D | README.rst | 94 To verify the Zephyr application client is running and has received 187 To verify the Zephyr application client is running and has received
|
/Zephyr-4.1.0/samples/subsys/modbus/rtu_server/ |
D | README.rst | 16 This sample has been tested with the nRF52840-DK and FRDM-K64F boards, 17 but it should work with any board that has a free UART interface or USB
|
/Zephyr-4.1.0/cmake/modules/ |
D | FindDeprecated.cmake | 10 # has been deprecated for two releases. 22 # # This code has been deprecated after Zephyr x.y
|
D | boards.cmake | 59 # Check that BOARD has been provided, and that it has not changed. 145 message(WARNING "BOARD_DIR: ${BOARD_DIR} has been moved or deleted. " 217 "This indicates the board has been removed, renamed, or placed at a new location.\n"
|
/Zephyr-4.1.0/doc/_extensions/zephyr/domain/static/js/ |
D | board-catalog.js | 21 if (hashParams.has(param)) { 33 if (hashParams.has("features")) {
|
/Zephyr-4.1.0/boards/dragino/lsn50/doc/ |
D | index.rst | 86 Dragino LSN50 Board has GPIO controllers. These controllers are responsible for pin muxing, 110 Dragino LSN50 board has 2 U(S)ARTs. The Zephyr console output is assigned to UART1.
|
/Zephyr-4.1.0/boards/dragino/nbsn95/doc/ |
D | index.rst | 85 Dragino NBSN95 Board has GPIO controllers. These controllers are responsible for pin muxing, 109 Dragino NBSN95 board has 2 U(S)ARTs. The Zephyr console output is assigned to UART1.
|
/Zephyr-4.1.0/tests/bsim/bluetooth/mesh/ |
D | README.rst | 10 mesh subsystem, and each folder has a corresponding test_<subfolder>.c under the 109 has been called - otherwise, it will fail.
|
/Zephyr-4.1.0/boards/st/nucleo_f410rb/doc/ |
D | index.rst | 65 Nucleo F410RB Board has 8 GPIO controllers. These controllers are responsible for pin muxing, 109 Nucleo F410RB board has 3 USARTs. The Zephyr console output is assigned to UART2.
|
/Zephyr-4.1.0/boards/others/black_f407zg_pro/doc/ |
D | index.rst | 90 BLACK_F407ZG_PRO has 7 GPIO controllers. These controllers are responsible for pin 128 BLACK_F407ZG_PRO has up to 6 UARTs. The Zephyr console output is assigned to UART2.
|
/Zephyr-4.1.0/boards/st/stm32f072_eval/doc/ |
D | index.rst | 76 STM32F072-EVAL Discovery kit has 6 GPIO controllers. These controllers are responsible for pin muxi… 106 STM32F072-EVAL Discovery kit has up to 4 UARTs. The Zephyr console output is assigned to UART2.
|
/Zephyr-4.1.0/doc/build/dts/ |
D | macros.bnf | 31 ; The reg property is special and has its own macros. 275 ; has path-id "_S_foo_123_S_bar_baz". 293 ; The 'zephyr,console' property has prop-id 'zephyr_console'. 294 ; 'WHY,AM_I_SHOUTING' has prop-id 'why_am_i_shouting'. 344 ; Declares that a compatible has at least one node on a bus. 349 ; Declares that a compatible has at least one status "okay" node. 376 ; Node device@123 has these alternate-id values:
|
/Zephyr-4.1.0/doc/safety/ |
D | safety_overview.rst | 198 and tracing in hand, it can now be verified whether the functionality has been tested and 209 and has a high (ideally 100%) test coverage, it has the additional advantage of quickly detecting 236 approach has been pursued in the Zephyr project from the beginning with its layered architecture. 238 into layers. As a result, each layer can be assigned a specific role in the system. This model has 293 #. This section describes the certification side. At this point, the code base has to be in an 310 circumstances, specifically when something has been identified during the certification process
|
/Zephyr-4.1.0/boards/nxp/mimxrt1040_evk/doc/ |
D | index.rst | 7 extended temperature range up to 125° C. The i.MX RT1040 MCU has a compact 68 This platform has the following external memories: 132 The MIMXRT1040 SoC has five pairs of pinmux/gpio controllers. 190 The MIMXRT1040 SoC has eight UARTs. ``LPUART1`` is configured for the console,
|
/Zephyr-4.1.0/doc/kernel/usermode/ |
D | overview.rst | 35 memory that has an incompatible policy, such as attempting to write to a 119 starvation. Zephyr has no thread priority aging and a user thread of a 153 another thread that is either in supervisor mode or has permission on both 155 The creation of new threads has an option to automatically inherit
|
1...<<21222324252627282930>>...55