Home
last modified time | relevance | path

Searched refs:will (Results 676 – 700 of 1633) sorted by relevance

1...<<21222324252627282930>>...66

/Zephyr-latest/boards/st/b_u585i_iot02a/doc/
Dindex.rst223 will set platform option bytes config and erase platform (among others,
224 option bit TZEN will be set).
231 Please note that, after having run a TFM sample on the board, you will need to
235 Also note that, even then, TZEN will remain set, and you will need to use
340 If you have flashed a sample to the board that enables TrustZone, you will need
354 some memory regions won't be erasable and mass erase will fail (step 4).
356 The following command sequence will fully deactivate TZ:
/Zephyr-latest/drivers/ieee802154/
DKconfig.uart_pipe17 This option assure the driver will process just frames addressed to him.
/Zephyr-latest/samples/drivers/mspi/mspi_async/
DREADME.rst18 The application will build only for a target that has a :ref:`devicetree <dt-guide>`
/Zephyr-latest/drivers/audio/
DKconfig.dmic_mcux23 a buffer will always be in the RX queue.
/Zephyr-latest/boards/common/
Drenode_robot.board.cmake10 # RESULTS_DIR: directory in which Robot artifacts will be generated after running a testsuite
/Zephyr-latest/lib/posix/options/
DKconfig.c_lib_ext8 Select 'y' here and Zephyr will provide an implementation of the POSIX_C_LIB_EXT Option
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig116 mesh-specific workqueue. This will ensure that messages are always sent.
134 will be affected by other users on the system work queue, resulting in
183 messages, the stack will use the main advertising set to relay
191 value. This in turn will result in increase of the power
199 otherwise a shared advertising set will be used.
206 otherwise a shared advertising set will be used. Using the separate
513 feature of specification, set to zero will not allow send any
525 feature of specification, set to zero will not allow receive any
539 Outgoing messages will allocate their segments at the start of the
613 segmented message to a unicast address that the stack will send if no
[all …]
/Zephyr-latest/doc/build/dts/
Dhowtos.rst135 :c:func:`uart_configure`. Similar code will work for other device types; just
152 devicetree. In some situations your code will compile but it will fail to link
237 If you don't set :makevar:`DTC_OVERLAY_FILE`, the build system will follow
241 #. If the file :file:`socs/<SOC>_<BOARD_QUALIFIERS>.overlay` exists, it will be used.
242 #. If the file :file:`boards/<BOARD>.overlay` exists, it will be used in addition to the above.
244 and :file:`boards/<BOARD>_<revision>.overlay` exists, it will be used in addition to the above.
247 #. Otherwise, if :file:`<BOARD>.overlay` exists, it will be used, and the build
248 system will stop looking for more files.
249 #. Otherwise, if :file:`app.overlay` exists, it will be used.
252 will still allow the build system to automatically use devicetree overlays
[all …]
Dbindings-syntax.rst148 The one exception is that the build system will always generate macros for
249 Adding ``required: true`` to a property definition will fail the build if a
314 - a catch-all for more complex types (no macros will be generated)
323 The tooling will report a warning if the devicetree includes the property that
335 The optional ``default:`` setting gives a value that will be used if the
347 If property ``foo`` is missing in a matching node, then the output will be as
351 Note that combining ``default:`` with ``required: true`` will raise an error.
358 will raise an error.
395 "gpio", so that ``foo-gpios`` will have specifier space "gpio" rather than
495 will apply to the ``grandchild`` node in this DTS:
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dccp.rst12 The telephone bearer service client will typically exist on a resource
14 laptops. The call control client will also thus typically be the advertiser.
27 will start a discovery for the TBS UUIDs and store the handles, and optionally
31 will take an index (starting from 0) as input. Joining calls require at least 2
34 A server will also have a GTBS instance, which is an abstraction layer for all
/Zephyr-latest/doc/develop/west/
Dtroubleshooting.rst41 for a password when you run it directly, you will be able to run ``west
68 will be different on your computer.
82 will be different on your system.
155 the west extension command. If set, west will use :envvar:`ZEPHYR_BASE` to
203 you will get the "already in a workspace" error message discussed next).
/Zephyr-latest/doc/releases/
Dmigration-guide-3.7.rst54 is enabled by default so that downstream applications will continue to compile, a warning message
55 will be generated during CMake configuration time.
56 This Kconfig will be deprecated and eventually removed in the future, developers are advised to
68 ``include/zephyr/sys/`` into ``include/zephyr/arch/``. Out-of-tree source files will need to
116 * TLS/X509/PK/MD modules will use PSA crypto APIs instead of legacy ones as soon
168 Thus, all boards using NXP's ENET peripheral will need to align to this binding
198 :dtcompatible:`nxp,lptmr`. The old string will be usable for a short time, but
199 should be replaced for it will be removed in the future.
307 * Automatic bus recovery will always be enabled upon driver initialization regardless of Kconfig
309 will be started at this point.
[all …]
/Zephyr-latest/subsys/llext/
DKconfig116 Name will be used when generating the EDK file, as <name>.tar.xz.
117 It will also be used, normalized, as the prefix for the variable
126 to be used by userspace only extensions, this option will make EDK stubs
/Zephyr-latest/soc/nuvoton/npcx/
DKconfig47 This selects the max clock rate that will be used for loading firmware
127 When enabled, the header will be verified at boot using a crc
133 When enabled, the firmware image will be verified at boot using a
/Zephyr-latest/doc/connectivity/networking/
Dnative_sim_setup.rst36 For the steps below, you will need three terminal windows:
85 The native_sim board will print a string like this when it starts:
133 ``echo-client`` applications will communicate over localhost/loopback
/Zephyr-latest/doc/
DCMakeLists.txt40 message(WARNING "LaTeX components not found. PDF build will not be available.")
83 # The function will create two targets for the doc build system.
87 # Both targets will produce same result, but target 2 must have no dependencies.
/Zephyr-latest/doc/services/storage/disk/
Daccess.rst26 Init/deinit IOCTL calls are balanced, so a disk will not de-initialize until
32 each disk driver may handle differently, but it will always return
88 The SD card will be automatically detected and initialized by the
/Zephyr-latest/tests/bsim/bluetooth/mesh/
DREADME.rst107 will run until the mesh_test module's ``FAIL`` macro is called, or until the
108 test times out. At the test timeout, the test will pass if the ``PASS()`` macro
109 has been called - otherwise, it will fail.
/Zephyr-latest/drivers/sensor/vishay/vcnl36825t/
DKconfig25 standard types will deactivate the other interrupt.
/Zephyr-latest/soc/espressif/esp32c3/
DKconfig34 If enabled, the MAC and baseband of Wi-Fi and Bluetooth will be powered
/Zephyr-latest/doc/services/debugging/
Dsymtab.rst6 The Symtab module, when enabled, will generate full symbol table during the Zephyr linking
/Zephyr-latest/boards/microchip/mec1501modular_assy6885/
DCMakeLists.txt26 …neration tool (${EVERGLADES_SPI_GEN_FILENAME}) is not available. SPI Image will not be generated.")
/Zephyr-latest/boards/microchip/mec15xxevb_assy6853/
DCMakeLists.txt26 …neration tool (${EVERGLADES_SPI_GEN_FILENAME}) is not available. SPI Image will not be generated.")
/Zephyr-latest/samples/drivers/kscan/
DREADME.rst11 Callbacks are registered that will write to the console indicating KSCAN events.
/Zephyr-latest/drivers/bluetooth/hci/
DCMakeLists.txt7 This is only for building (CI) purposes and will not work on a real device.

1...<<21222324252627282930>>...66