Searched refs:will (Results 1251 – 1275 of 1633) sorted by relevance
1...<<51525354555657585960>>...66
| /Zephyr-latest/boards/arduino/nano_33_ble/ |
| D | arduino_nano_33_ble-common.dtsi | 133 * Storage partition will be used by FCB/LittleFS/NVS
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf54l15bsim.rst | 58 and will use the same drivers as the nrf54l15dk targets for these.
|
| /Zephyr-latest/lib/cpp/ |
| D | Kconfig | 64 a subsystem or an application. This will also include a full C
|
| /Zephyr-latest/boards/olimex/stm32_h405/doc/ |
| D | index.rst | 153 interface. You will need to use ST tools or an external JTAG probe.
|
| /Zephyr-latest/boards/ezurio/mg100/ |
| D | mg100.dts | 209 * Storage partition will be used by FCB/NVS
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 87 it will be received by thread B if thread B tries to receive a message
89 The exchange will not occur if thread B tries to receive a message
101 other work (such as gather data that will be used in the next message)
326 thread Y, an incoming message from thread Y to any thread will be given
327 to thread B and thread A will continue to wait.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 29 …PI <conn_mgr_control_api>` functions can be called on the iface, and they will be translated to th…
35 This binding structure will contain a reference to the bound iface, the connectivity implementation…
184 However, it relies on trust that all connectivity implementations will faithfully implement the fea…
297 However, bear in mind that blocking during this callback will delay system init, so still consider …
331 For example, do not use :c:func:`net_if_get_default` under the assumption that the bound iface will…
|
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | Kconfig | 84 LwM2M messages with a big body that exceed the block size will be split
300 LwM2M will use the validation buffer during the write operation, to
432 object will store before ignoring new values.
440 device object will store before ignoring new values.
511 send the update. When both values are set, smallest period will be used.
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig | 33 it only states that write of a random information will require
121 Size of the buffer used for flash commands, will determine the
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.hl7800 | 36 then it will be set.
372 CTS pulses shorter than this value will be ignored.
|
| /Zephyr-latest/boards/seeed/xiao_esp32s3/doc/ |
| D | index.rst | 172 With ``--sysbuild`` option the bootloader will be re-build and re-flash
209 The usual ``flash`` target will work with the ``xiao_esp32s3`` board
|
| /Zephyr-latest/doc/services/mem_mgmt/ |
| D | index.rst | 30 :dtcompatible:`zephyr,memory-region` that will result (only when supported
145 provided functions, the library will take care of allocating memory from the
|
| /Zephyr-latest/boards/heltec/heltec_wireless_stick_lite_v3/doc/ |
| D | index.rst | 216 With ``--sysbuild`` option the bootloader will be re-build and re-flash
242 The usual ``flash`` target will work with the ``heltec_wireless_stick_lite_v3`` board
|
| /Zephyr-latest/boards/phytec/phyboard_pollux/doc/ |
| D | index.rst | 140 At compilation time you have to choose which memory region will be used. This
144 **By default Zephyr will use the TCM memory region.** You can configure it
|
| /Zephyr-latest/boards/andestech/adp_xc7k_ae350/doc/ |
| D | index.rst | 209 For debugging zephyr applications or burning them into a flash, you will need to
256 To run ICEman commands as a normal user, you will need to install the
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wroom/doc/ |
| D | index.rst | 180 With ``--sysbuild`` option the bootloader will be re-build and re-flash
206 The usual ``flash`` target will work with the ``esp32_devkitc_wroom`` board
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wrover/doc/ |
| D | index.rst | 180 With ``--sysbuild`` option the bootloader will be re-build and re-flash
206 The usual ``flash`` target will work with the ``esp32_devkitc_wrover`` board
|
| /Zephyr-latest/boards/m5stack/m5stack_cores3/doc/ |
| D | index.rst | 136 With ``--sysbuild`` option the bootloader will be re-build and re-flash
173 The usual ``flash`` target will work with the ``m5stack_cores3/esp32s3/procpu`` board
|
| /Zephyr-latest/boards/olimex/olimex_esp32_evb/doc/ |
| D | index.rst | 172 With ``--sysbuild`` option the bootloader will be re-build and re-flash
198 The usual ``flash`` target will work with the ``olimex_esp32_evb`` board
|
| /Zephyr-latest/boards/olimex/olimexino_stm32/doc/ |
| D | index.rst | 352 You will need to solder, unsolder, or cut them in order to
442 the binary image, or it will interfere with the flashing
|
| /Zephyr-latest/boards/espressif/esp32c3_rust/doc/ |
| D | index.rst | 213 With ``--sysbuild`` option the bootloader will be re-build and re-flash
239 The usual ``flash`` target will work with the ``esp32c3_rust`` board
|
| /Zephyr-latest/boards/nxp/mimxrt1020_evk/doc/ |
| D | index.rst | 200 oscillator on the board will be used as a source for the GPT timer to
239 Regardless of your choice in debug probe, we will use the OpenSDA
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | bap.rst | 172 The command :code:`bap create_broadcast_sink` will either use existing periodic advertising
225 The command :code:`bap create_sink_by_name` will start scanning and sync to the periodic
557 Sink streams will have to be started by the unicast server, and source streams will have to be
|
| D | mcp.rst | 43 An active player will have a *current track*. This is the track that
52 The media player is in a *state*, which will be one of playing,
91 giving the command :code:`mcc discover_mcs`. This will store the
414 The server will give debug output related to the various operations
|
| /Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
| D | index.rst | 40 which options are configured and so will be used on invocation of the simulator.
117 This will build an image with the synchronization sample app, boot it using
189 it will produce the following output (the ``nsim/nsim_hs5x/smp`` configuration was used for that
221 Without :envvar:`NSIM_MULTICORE` environment variable set to 1, MDB will simulate 2 separate
|
1...<<51525354555657585960>>...66
