Searched refs:will (Results 701 – 725 of 1633) sorted by relevance
1...<<21222324252627282930>>...66
| /Zephyr-latest/boards/microchip/mec172xevb_assy6906/ |
| D | CMakeLists.txt | 26 … Generation tool (${MEC172X_SPI_GEN_FILENAME}) is not available. SPI Image will not be generated.")
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | kobject-rom.ld | 10 * space needs to be reserved for the rodata that will be
|
| /Zephyr-latest/subsys/bluetooth/services/ots/ |
| D | Kconfig | 21 from all other objects, for easy exposure to a client. Enabling this will use one of the
101 # RX MTU will be truncated to account for the L2CAP PDU and SDU header.
|
| /Zephyr-latest/boards/shields/ls0xx_generic/doc/ |
| D | index.rst | 16 to a gpio. If devicetree contains ``disp-en-gpios`` then it will be set to
28 When ``extcomin-gpios`` is defined, driver starts a thread which will
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.nrf | 66 This is maximum time, in ms, that NVMC will use to erase part
77 This is a multiplier that will be divided by 10 that is applied
|
| /Zephyr-latest/samples/subsys/debug/fuzz/ |
| D | README.rst | 31 Over 10-20 seconds or so (runtimes can be quite variable) you will see
46 INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | dfu.rst | 65 1. You will need to define the flash partitions required by MCUboot; see
67 2. You will have to specify your flash partition as the chosen code partition
|
| /Zephyr-latest/doc/develop/sca/ |
| D | codechecker.rst | 49 - Perform a cleanup after parsing/storing. This will remove all ``plist`` files.
58 - By default, CodeChecker identified issues will not fail the build, set this option to fail
|
| /Zephyr-latest/samples/net/sockets/echo_async/ |
| D | README.rst | 45 After a connection is made, the application will echo back any line sent to
62 Linux. (Note: if you look at the source, you will see that the code is
|
| /Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
| D | aarch32.rst | 45 When FVP is launched with ``-a, --application FILE`` option, the kernel will be
88 This will build an image with the synchronization sample app.
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 75 this class will be instantiated and used when your extension is run.
131 ``WestCommand`` will reject unknown arguments by default. If you want to be
168 - It's a small optimization, since your code will only be imported if it is
171 So, unless your command is explicitly run, west will just load the
176 multiple files, your :file:`west-commands.yml` will look something like this:
239 and the project which contains its code will now also show up in the ``west
|
| D | manifest.rst | 106 metadata. We'll discuss it soon, but first we will describe the ``remotes``
152 over SSH as well. Anything acceptable to Git will work.
197 Locally, this project will be cloned at path ``extra/project-1`` relative to
202 default. The current tip of this branch will be fetched and checked out as a
210 default. It will be cloned into a directory named ``proj2``. The commit
211 pointed to by the ``v1.3`` tag will be checked out when west updates the
214 - ``proj3`` has an explicit ``url``, so it will be fetched from
217 Its local path defaults to its name, ``proj3``. Commit ``abcde413a111`` will
221 Sometimes we'll refer to the ``defaults`` subsection; it will be described
243 If the project has a ``remote``, that remote's ``url-base`` will be
[all …]
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 85 configuration macros for the SoC. The :file:`soc.h` will often be included in
196 CPU cluster will often have its own :file:`.dtsi` file.
199 :file:`<soc>_<cluster>.dtsi`. A :file:`<soc>_<cluster>.dtsi` file will look
256 The :file:`Kconfig` will often indicate given hardware support using a setting
290 file. This will usually be in the form of ``SOC_<SOC_NAME>_<CLUSTER>`` so for
292 will look like:
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 30 will be declared in some header under ``include/`` or in another
79 the kernel configuration) will instead point to a special verification for
102 Note that not all syscalls will be included in the final binaries.
108 will always have their syscalls present in final binaries.
117 user mode, or exclusively in supervisor mode. The system will look for
119 :c:macro:`__ZEPHYR_USER__`, typically these will be added to the compiler
132 there will be a CPU exception as soon as it tries to do something it isn't
167 will be invoked instead.
192 return value. Depending on context it will either directly call the
218 Additional arguments will need to be passed in an array in the source memory
[all …]
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.df | 176 If this feature is not enabled, the Radio initialization procedure will
209 will have no effect.
219 is 1 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
230 is 1 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
242 is 2 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
253 is 2 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
295 is a loss in accuracy. This conversion may be used only if you are sure samples will not
|
| /Zephyr-latest/soc/ite/ec/it8xxx2/ |
| D | Kconfig | 29 This option is selected by a variable of which soc, and will
35 This option is selected by a variable of which soc, and will
145 The clock_frequency of ite,it8xxx2-i2c node (i2c0, i2c1, and i2c2) will
183 If enabled, Instruction Local Memory (ILM) will be configured to execute
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 83 system will look for :file:`snippet.yml` files underneath the following
103 And then any :file:`snippet.yml` files in ``baz/snippets`` will
130 ``CONFIG_FOO=2`` in the above example, the resulting final configuration will
203 application with both :file:`prj.conf` and :file:`boards/foo.conf` files will
|
| /Zephyr-latest/subsys/net/lib/sockets/ |
| D | Kconfig | 39 API call will timeout if we have not received SYN-ACK from
139 configuration, so that Maximum Fragment Length (MFL) will be sent to
167 from connecting. Value of 0 indicates no timeout - resources will be
196 DTLS sockets is disabled. In result, sendmsg() will only accept msghdr
262 means that TLS will be offloaded as well (if supported by offloaded
264 means that native TLS will be used.
296 will be fed to sockets unchanged as provided by the driver.
411 The net-shell "net sockets" command will use this functionality
|
| /Zephyr-latest/snippets/xen_dom0/boards/ |
| D | qemu_cortex_a53.overlay | 10 /* Xen consoleio will be used */
|
| /Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/ |
| D | app.overlay | 43 /* Circular reference, macros will figure it out and
|
| /Zephyr-latest/boards/segger/ip_k66f/ |
| D | linker.ld | 24 * lan{123} shall be placed afterwards (sorted) so the order will be
|
| /Zephyr-latest/samples/subsys/console/echo/ |
| D | README.rst | 34 keyboard, and they will be echoed back to the terminal program you are using.
|
| /Zephyr-latest/samples/subsys/input/draw_touch_events/ |
| D | README.rst | 9 This sample will draw a small plus in the last touched coordinates, that way you can check
|
| /Zephyr-latest/samples/net/lldp/ |
| D | Kconfig | 6 # This sample application will have three network interfaces.
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt6xx/ |
| D | Kconfig | 63 cleared, the CACHE64 controller will be disabled during SOC init
|
1...<<21222324252627282930>>...66
