Searched refs:will (Results 451 – 475 of 1633) sorted by relevance
1...<<11121314151617181920>>...66
| /Zephyr-latest/doc/services/retention/ |
| D | index.rst | 31 you are using, there is a zephyr driver which can be used which will use some
33 child node of this device 1 or more times - note that the memory region will
94 /* If omitted, there will be no
121 will be set on the area, and it will be marked as valid from that point
191 which will allow rebooting directly into the serial recovery mode by using:
|
| /Zephyr-latest/samples/bluetooth/hci_uart/ |
| D | README.rst | 62 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
71 Depending on the serial port you are using you will need to modify the
76 If using the BBC micro:bit you will need to modify the baudrate argument
95 In order to use the HCI UART controller with BlueZ you will need to attach it
104 Depending on the serial port you are using you will need to modify the
109 If using the BBC micro:bit you will need to modify the baudrate argument
|
| /Zephyr-latest/subsys/net/lib/coap/ |
| D | Kconfig | 25 information will be sent in a single IP packet (can be multiple
26 fragments depends on MTU size). This will be useful in mesh kind
66 If enabled, the initial ACK timeout will be randomized, as specified
67 in RFC 7252, i.e. will be a random number between ACK_TIMEOUT and
70 will be fixed to the value of COAP_INIT_ACK_TIMEOUT_MS option.
232 Static memory will be reserved for pending messages. The total size is equal to
|
| /Zephyr-latest/boards/nxp/ls1046ardb/doc/ |
| D | index.rst | 94 This will build an image with the synchronization sample app.
109 It will display the following console output:
126 This will build an image with the synchronization sample app.
134 It will display the following console output:
154 This will build an image with the synchronization sample app.
162 It will display the following console output:
|
| /Zephyr-latest/doc/services/shell/ |
| D | index.rst | 64 Enabling :kconfig:option:`CONFIG_SHELL_BACKEND_TELNET` will allow users to use telnet
74 This will give the telnet client access to a very limited set of supported commands but
76 option. This will allow the client to be in character mode (character at a time),
77 similar to a UART backend in that regard. This will make the client send a character
79 considerably. For that cost, it will enable the line editing,
146 * Now you should have a network connection to RTT that will let you enter input
169 * Now you should have a network connection to RTT that will let you enter input
399 as one argument. If shell won't find a handler it will display an error message.
408 /* Below code will execute "clear" command on a DUMMY backend */
411 /* Below code will execute "shell colors off" command on
[all …]
|
| /Zephyr-latest/boards/native/native_sim/doc/ |
| D | index.rst | 30 | Some components, code, options names, and documentation will still use the old native_posix
31 names. But all components which worked with native_posix will work with native_sim.
95 Application tests using the :ref:`ztest framework<test-framework>` will exit after all
131 Note that you will need the ASan library installed in your system.
160 The 32 bit version, ``native_sim``, is the default target, which will compile
179 By default it will be compiled with the host C library (:kconfig:option:`CONFIG_EXTERNAL_LIBC`),
183 :ref:`Picolibc <c_library_picolibc>` will be selected by default instead.
186 you will build your code in a more similar way as when building for the embedded target,
187 you will be able to test your code interacting with that C library,
188 and there will be no conflicts with the :ref:`POSIX OS abstraction<posix_support>` shim,
[all …]
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 17 must be provided. Interrupts are available. Kernel objects will most
22 Many drivers and subsystems will not work with this option
88 highest priority) that a thread will acquire as part of
97 threads at these priorities will always be scheduled before
106 that user code will not be executed (on the current CPU)
118 single priority will choose the next expiring deadline and
125 When true, the application will have access to the
145 threads have a single "assigned" CPU and they will never be
311 When selected, the scheduler ready queue will be implemented
314 Choose this on systems with constrained code size that will
[all …]
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 89 device its possible one chain will have to wait for another to complete.
97 sqe. A chain of sqe will however ensure ordering and failure cascading.
130 will remove the SQE and never run it. If, however, the SQE already started
131 running, the cancel request will be ignored.
136 In some cases requests to read may not know how much data will be produced.
180 Finally, the consumer will be able to access the allocated buffer via
220 driver doesn't support the RTIO APIs, it will set the submit function to
225 the ``iodev_submit`` function will defer to a work item which will perform a blocking I2C
|
| /Zephyr-latest/boards/altr/max10/doc/ |
| D | index.rst | 33 You will need the Altera Quartus SDK in order to work with this device. The
107 port on the board (it will show up in /dev as a ttyUSB node), and then running
139 The usual ``flash`` target will work with the ``altera_max10`` board
153 will immediately boot.
159 The SDK included the nios2-download tool which will let you flash a kernel
199 You will see output similar to the following:
263 nios2-download (which errors out if it finds sections outside of SRAM) it will
287 And then load the kernel image over the wire. The CPU will not start from the
288 reset vector, instead it will boot from the __start symbol:
|
| /Zephyr-latest/samples/subsys/input/input_dump/ |
| D | README.rst | 28 After starting, the sample will print any input event in the console.
|
| /Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/boards/ |
| D | nucleo_h563zi.overlay | 18 /* Configure sleep pinctrl configuration which will be used when
|
| /Zephyr-latest/samples/bluetooth/periodic_adv/ |
| D | README.rst | 24 Zephyr tree that will scan and establish a periodic advertising synchronization
|
| /Zephyr-latest/dts/common/nordic/ |
| D | nrf52840_partition.dtsi | 40 * Storage partition will be used by FCB/LittleFS/NVS
|
| /Zephyr-latest/samples/drivers/led/led_strip/boards/ |
| D | esp32c3_devkitm.overlay | 21 chain-length = <1>; /* arbitrary; change at will */
|
| D | esp32s2_saola.overlay | 21 chain-length = <1>; /* arbitrary; change at will */
|
| D | esp32s3_devkitm_procpu.overlay | 21 chain-length = <1>; /* arbitrary; change at will */
|
| /Zephyr-latest/tests/subsys/logging/log_switch_format/ |
| D | Kconfig | 10 log messages. It will not output any logs.
|
| /Zephyr-latest/samples/bluetooth/iso_broadcast_benchmark/ |
| D | README.rst | 58 The receiver will output statistics for overall (since boot), current sync
90 The broadcaster will ask if any changes to the current settings are wanted.
91 If y/Y is chosen, then it will create a prompt to enter changes to the settings,
92 otherwise continue with the current settings. The broadcaster will then start
|
| /Zephyr-latest/subsys/net/l2/wifi/ |
| D | Kconfig | 9 Enabling this config will increase the net_mgmt event size
47 RF transmissions. This doesn't guarantee that passive scan will be used,
110 will prevent the AP from sending null data frames to the stations after
120 Maximum number of stations allowed in station table. New stations will be
|
| /Zephyr-latest/samples/bluetooth/mtu_update/ |
| D | README.rst | 37 will exchange their MTUs and choose the minimum of the two. Thus the two MTU can
54 The resulting L2CAP RX MTU will be the value of this Kconfig symbol minus the
70 The two devices will connect only if they are close to each other, because of
83 should subscribe and then the peripheral will send a large notification. Right
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 23 - Each release period will consist of a development phase followed by a
24 stabilization phase. Release candidates will be tagged during the
26 changes such as bug fixes and documentation will be merged unless granted a
62 (and all of the major changes) will be merged during this time.
65 the release owner will declare that the development phase is over and releases the first
68 will be called 3.1.0-rc1. The -rc1 release is the signal that the time to merge
79 On occasion, more significant changes and new features will be allowed, but such
87 As fixes make their way into the mainline, the patch rate will slow over time.
89 series will get up to somewhere between -rc4 and -rc6 before the code base is
101 for a release. This will help define when a release is "done" in terms that most
[all …]
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 81 Inclusion of binary blobs will taint the Zephyr build. The definition of
84 in the context of Zephyr, a tainted image will be one that includes binary blobs
87 Tainting will be communicated to the user in the following manners:
89 - One or more Kconfig options ``TAINT_BLOBS_*`` will be set to ``y``
90 - The Zephyr build system, during its configuration phase, will issue a warning.
91 It will be possible to disable the warning using Kconfig
92 - The ``west spdx`` command will include the tainted status in its output
93 - The kernel's default fatal error handler will also explicitly print out the
118 Note that just because a blob has an acceptable type does not imply that it will
202 This does not imply that issues which require blobs to reproduce will be closed
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | access.rst | 56 will be passed to the model.
66 A model will process all messages addressed to the unicast address of their
68 list). Additionally, the model will process packets addressed to any group or
88 will use the publication parameters configured by the
92 the mesh network than the individual nodes will.
99 :c:member:`bt_mesh_model_pub.update` callback will be called right before the
121 extends another in the same element, the two models will share subscription
154 data by calling :c:func:`bt_mesh_model_data_store_schedule`. The stack will
157 running, the stack will call the :c:member:`bt_mesh_model_cb.pending_store`
212 They are used to represent the new content of the mirrored pages when the Composition Data will
[all …]
|
| /Zephyr-latest/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | README.rst | 176 ``west flash`` will automatically detect slot-0 address and confirm the image.
183 will be used and the image won't be runnable.
189 with your choice of tool's ``echo`` functionality, which will
263 boots, see the instructions in the tool of your choice. Upon reboot, MCUBoot will swap to the new
274 check the documentation in the tool of your choice. Upon reset MCUboot will swap slot-0 and
280 The new image is now loaded into slot-0, but it will be swapped back into slot-1 on the next
284 slot-0 then the procedure will not complete successfully since the hash values
285 for both slots will be identical.
|
| /Zephyr-latest/samples/net/lwm2m_client/ |
| D | README.rst | 90 The sample will start and automatically connect to the Leshan Demo Server with
139 Server web UI will open, this is where you can configure your device for
168 The sample will start and automatically connect to the Leshan Demo Bootstrap
169 Server to obtain the LwM2M Server information. After that, the sample will
193 Note: If not provisioned (fully erased before flash), device will form
230 With Queue Mode enabled, the LWM2M client will register with "UDP with Queue
231 Mode" binding. The LWM2M engine will notify the application with
233 is closed so it can e. g. turn the radio off. The next RX window will be open
|
1...<<11121314151617181920>>...66
