Searched refs:will (Results 976 – 1000 of 1633) sorted by relevance
1...<<31323334353637383940>>...66
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.fs | 53 Directory to which log files will be written.
|
| /Zephyr-latest/drivers/wifi/winc1500/ |
| D | Kconfig.winc1500 | 46 Set the number of buffer the driver will have access to in each of
|
| /Zephyr-latest/soc/nxp/imxrt/ |
| D | Kconfig.defconfig | 34 # Disable systick if using MCUX_GPT_TIMER, as they will conflict
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt118x/ |
| D | Kconfig | 55 value, this will make ROM could get the user image start address.
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.nrf_rram | 66 This is a multiplier that will be divided by 10 that is applied
|
| /Zephyr-latest/soc/espressif/esp32c2/ |
| D | Kconfig.mac | 22 a custom universal MAC address range, the correct setting will depend on the allocation of MAC
|
| /Zephyr-latest/soc/espressif/esp32c3/ |
| D | Kconfig.mac | 22 a custom universal MAC address range, the correct setting will depend on the allocation of MAC
|
| /Zephyr-latest/soc/espressif/esp32c6/ |
| D | Kconfig.mac | 22 a custom universal MAC address range, the correct setting will depend on the allocation of MAC
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | sdhc.rst | 40 controllers will support applying all I/O settings. For example, SPI mode
|
| D | i3c.rst | 100 * If there is a device waiting for address, it will send
162 * If controller hardware makes use of IBI slots, this will remove
217 * Can be zero if static address is not used. Address will be
221 this will be the address of the device after SETDASA
311 any calls to I2C API will need to look up the corresponding device
|
| /Zephyr-latest/boards/ruuvi/ruuvitag/ |
| D | ruuvi_ruuvitag.dts | 134 * Storage partition will be used by FCB/LittleFS/NVS
|
| /Zephyr-latest/samples/subsys/ipc/ipc_service/multi_endpoint/ |
| D | README.rst | 26 After resetting the board, the following message will appear on the corresponding
|
| /Zephyr-latest/drivers/crypto/ |
| D | Kconfig | 59 Enable mbedTLS shim layer compliant with crypto APIs. You will need
|
| /Zephyr-latest/cmake/toolchain/cross-compile/ |
| D | target.cmake | 4 # When using cross-compile, the generic toolchain will be identical to the
|
| /Zephyr-latest/samples/boards/espressif/xt_wdt/ |
| D | README.rst | 13 The app will ask for the crystal removal to simulate a crystal failure and trigger
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.dwmac | 49 of a full-size packet to be transmitted or the packet will be
|
| /Zephyr-latest/samples/drivers/can/babbling/ |
| D | README.rst | 12 bus access for any CAN frame with lower priority as these frames will loose the bus arbitration.
|
| /Zephyr-latest/include/zephyr/arch/posix/ |
| D | linker.ld | 93 * line switch: The script will now augment the default SECTIONS instead of
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/support/ |
| D | openocd_rv32m1_vega_zero_riscy.cfg | 32 # If ADBG_USE_HISPEED is set (options bit 1), status bits will be skipped
|
| /Zephyr-latest/boards/ezurio/bl654_sensor_board/ |
| D | bl654_sensor_board.dts | 143 * Storage partition will be used by FCB/LittleFS/NVS
|
| /Zephyr-latest/doc/develop/west/ |
| D | release-notes.rst | 105 - All west commands will now output log messages from west API modules at
141 - The :ref:`west-apis` are now declared stable. Any breaking changes will be
279 reading ``self.config`` will abort the program.
307 object. Usually this will be done via ``self.config`` from a ``WestCommand``
399 - ``west update`` now supports a ``--fetch-opt`` option that will be passed to
421 defaults to ``master``. Instead, the command will query the repository for
454 The new behavior will take effect if ``manifest: version:`` is not given or
485 other manual edits in configuration files will be removed when setting a
503 will be acted upon by the following commands: ``west update``, ``west list``,
636 it will continue to be included in the distribution, but will be removed
[all …]
|
| D | built-in.rst | 56 The ``--mf`` option defaults to ``west.yml``. Since west v0.10.1, west will use
119 To avoid unnecessary fetches, ``west update`` will not fetch project
139 typically a safe operation that will not modify any of your local branches.
142 ``HEAD`` checked out by west, then git will warn you that you've left
157 ``west update --rebase`` will fail in projects that have git conflicts
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 308 of the selecting and selected symbol will never drift out of sync, e.g. when
360 In this case, ``FOO`` will end up with this definition:
462 As long as ``CUSTOM_STACK_SIZE`` is disabled, ``STACK_SIZE`` will ignore the
510 The Kconfig definitions below will hide the ``FOO_DEVICE_FREQUENCY`` symbol and
590 In the ``menuconfig`` interface, this will be displayed as follows:
610 This means a construct like this will fail:
644 right after the symbol it depends on. It will then be shown indented relative
792 That is, FOO will be set to ``n`` in the example below. If the ``default n`` was
805 In the following example FOO will get the value ``y``.
875 "Foo" as the prompt, instead of "Enable Foo support" or the like. It will
[all …]
|
| /Zephyr-latest/doc/connectivity/usb/device/ |
| D | usb_device.rst | 32 :ref:`usb_device_next_api`, will become the default in Zephyr v4.1.0.
62 the first interface, then the Linux btusb driver will claim both the first and
186 does not call ``read()``) will be echoed back. This issue is especially visible
192 the best indication that host application has opened the tty device, Zephyr will
201 as (invalid) command and user will see garbage as a result. While minicom does
202 disable ECHO by default, on exit with reset it will restore the termios settings
204 open the tty device, the exit with reset will enable ECHO back and thus set up
312 issue will be fixed in the HID class implementation for the new USB support.
377 Typically, users will need to add a configuration file overlay to the build,
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 42 Here are the main ways you will use phandles.
146 to a GPIO on your SoC. You will typically need to provide that GPIO's
153 In the devicetree, there will be a node that represents the GPIO controller
290 Therefore, almost all GPIO controller nodes you will see in practice will look
|
1...<<31323334353637383940>>...66
