Searched refs:has (Results 1176 – 1200 of 1361) sorted by relevance
1...<<41424344454647484950>>...55
/Zephyr-latest/lib/os/ |
D | Kconfig.cbprintf | 22 formatting capability is substituted. This has a much smaller code
|
/Zephyr-latest/samples/modules/tflite-micro/magic_wand/train/ |
D | README.md | 88 model has a smaller size and lower latency.
|
/Zephyr-latest/samples/sensor/bme280/ |
D | README.rst | 40 sure this node has ``status = "okay";``, then build and run with:
|
/Zephyr-latest/samples/subsys/llext/shell_loader/ |
D | README.rst | 153 Once the board has booted, you will be presented with a shell prompt.
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | slist.rst | 54 similarly, but has a more complicated implementation that requires an
|
/Zephyr-latest/boards/microchip/mec15xxevb_assy6853/doc/ |
D | index.rst | 9 The MEC152x has superseded the MEC1501 in production. MEC152x is identical to 10 MEC150x except for an enhanced Boot-ROM SPI loader. The SPI image format has
|
/Zephyr-latest/boards/phytec/phyboard_polis/doc/ |
D | index.rst | 156 Zephyr has the 3-color status LED configured. The led0 alias (the standard 193 the A53-Core has to load the program for the M4-Core to the right memory
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-le-host.rst | 115 API. The :c:struct:`bt_conn_auth_cb` struct that's passed to this API has 141 Mesh has its own security solution through a process called
|
/Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
D | implementation.rst | 37 …hen be iterated over to find out what (if any) connectivity implementation has been bound to a giv… 432 If the underlying technology has no mechanism to retry connection attempts, or would give up on the… 454 If the connection attempt crosses this threshold, but the configured timeout has not yet elapsed, o…
|
/Zephyr-latest/doc/develop/application/ |
D | index.rst | 91 Once an application has been defined, you will use CMake to generate a **build 514 #. If your application has its own kernel configuration options, 521 An (unlikely) advanced use case would be if your application has its own 749 build system has defined CMake functions that give application build 970 The Zephyr build system has support for specifying multiple hardware revisions 986 Check your board's documentation for details on whether it has multiple 1055 Zephyr has built-in emulator support for QEMU.
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.11.rst | 227 * :github:`2994` - The build system crashes when GCCARMEMB_TOOLCHAIN_PATH has a space in it 278 * :github:`4025` - Upgrade to TinyCrypt 0.2.7 has significant API changes 419 * :github:`5772` - sanitycheck crashes if ZEPHYR_BASE has symlinks in its path 425 * :github:`5817` - socket.h: Using #define for POSIX redefinition of zsock\_ functions has unintend…
|
/Zephyr-latest/soc/ite/ec/it8xxx2/ |
D | Kconfig | 195 has more reliable performance characteristics than executing directly from
|
/Zephyr-latest/subsys/bluetooth/audio/ |
D | Kconfig.mcs | 112 group object has more records than this, the remaining records in the
|
/Zephyr-latest/boards/arduino/nano_33_ble/doc/ |
D | index.rst | 87 CMSIS-DAP. This board has the SWD connector for debugging but exposes it as
|
/Zephyr-latest/boards/microchip/mec1501modular_assy6885/doc/ |
D | index.rst | 34 2) Mated mode with another platform that has a high density MECC connector.
|
/Zephyr-latest/boards/lilygo/ttgo_lora32/doc/ |
D | index.rst | 190 After the board has automatically reset and booted, you should see the following
|
/Zephyr-latest/boards/we/orthosie1ev/doc/ |
D | index.rst | 175 After the board has automatically reset and booted, you should see the following
|
/Zephyr-latest/boards/weact/mini_stm32h743/doc/ |
D | index.rst | 79 MiniSTM32H743 Core board has 5 GPIO controllers. These controllers are responsible for pin muxing,
|
/Zephyr-latest/boards/ezurio/mg100/doc/ |
D | index.rst | 11 full Bluetooth 5 connectivity, and dual-mode LTE-M/NB-IoT capabilities. The MG100 has full regulato…
|
/Zephyr-latest/boards/m5stack/m5stickc_plus/doc/ |
D | index.rst | 199 After the board has automatically reset and booted, you should see the following
|
/Zephyr-latest/boards/espressif/esp32c3_devkitm/doc/ |
D | index.rst | 175 After the board has automatically reset and booted, you should see the following
|
/Zephyr-latest/boards/espressif/esp32c3_rust/doc/ |
D | index.rst | 220 After the board has automatically reset and booted, you should see the following
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | coap_server.rst | 29 their respective linker sections. If you would have a service ``my_service`` it has to be
|
D | net_mgmt.rst | 38 available procedure requests depend on what has been implemented in
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | core.rst | 90 If other stack configuration has to be stored, the delay defined by
|
1...<<41424344454647484950>>...55