Searched refs:will (Results 1176 – 1200 of 1633) sorted by relevance
1...<<41424344454647484950>>...66
| /Zephyr-latest/boards/adi/max32672evkit/doc/ |
| D | index.rst | 236 connector CN1. The blue VBUS LED (DS1) and the green 3.3V LED will illuminate
257 a current source or sink on that GPIO. For these measurements, the board will be needed to be
291 This pulls P0_10 low and, upon a power cycle or reset, the device will enter boot loader mode.
|
| /Zephyr-latest/boards/nordic/nrf5340dk/doc/ |
| D | index.rst | 205 The Zephyr build system will perform the following steps automatically:
240 the Secure application will have to set the IDAU (SPU) configuration to allow
266 protection is active, you will need to recover the chip before reflashing.
|
| /Zephyr-latest/boards/nxp/mimxrt1040_evk/doc/ |
| D | index.rst | 182 oscillator on the board will be used as a source for the GPT timer to
232 Regardless of your choice in debug probe, we will use the OpenSDA
290 and the LED will not turn off. Samples and applications using USER_LED D8,
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig | 48 of which will need to be configured.
62 Enabling this setting will turn on VERY heavy debugging from the
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | mutexes.rst | 66 This means the kernel will *temporarily* elevate the thread's priority
85 involved. However, if multiple mutexes are involved, sub-optimal behavior will
|
| /Zephyr-latest/samples/drivers/dac/ |
| D | README.rst | 191 Bridge the JP23 to DAC with the jumper cap, then DAC output will available on JP7.
238 .. note:: If the DAC is not supported, the output will be an error message.
|
| /Zephyr-latest/boards/seeed/xiao_esp32c6/doc/ |
| D | index.rst | 151 With ``--sysbuild`` option the bootloader will be re-build and re-flash
177 The usual ``flash`` target will work with the ``xiao_esp32c6`` board
|
| /Zephyr-latest/cmake/ |
| D | llext-edk.cmake | 60 # files coming from build/zephyr/generated will end up at
64 # Finally, everything else (such as external libs not at any of those places) will end up
|
| /Zephyr-latest/boards/m5stack/m5stickc_plus/doc/ |
| D | index.rst | 154 With ``--sysbuild`` option the bootloader will be re-build and re-flash
180 The usual ``flash`` target will work with the ``m5stickc_plus`` board
|
| /Zephyr-latest/boards/mediatek/ |
| D | index.rst | 87 tools (e.g. from Cadence) will be able to use them as-is. Zephyr
143 After this completes, you will find your toolchain in ``~/x-tools``
|
| /Zephyr-latest/boards/heltec/heltec_wifi_lora32_v2/doc/ |
| D | index.rst | 109 With ``--sysbuild`` option the bootloader will be re-build and re-flash
135 The usual ``flash`` target will work with the ``heltec_wifi_lora32_v2`` board
|
| /Zephyr-latest/boards/others/esp32c3_supermini/doc/ |
| D | index.rst | 166 With ``--sysbuild`` option the bootloader will be re-build and re-flash
192 The usual ``flash`` target will work with the ``esp32c3_supermini`` board
|
| /Zephyr-latest/boards/espressif/esp32s2_saola/doc/ |
| D | index.rst | 165 With ``--sysbuild`` option the bootloader will be re-build and re-flash
191 The usual ``flash`` target will work with the ``esp32s2_saola`` board
|
| /Zephyr-latest/boards/nxp/rd_rw612_bga/doc/ |
| D | index.rst | 216 ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin`` will be linked
226 ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_wifi_a2.bin`` will be linked
|
| /Zephyr-latest/boards/espressif/esp32s2_devkitc/doc/ |
| D | index.rst | 165 With ``--sysbuild`` option the bootloader will be re-build and re-flash
191 The usual ``flash`` target will work with the ``esp32s2_devkitc`` board
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 66 API. Unless a global override is set, the module logging level will be honored.
125 be allocated thread context will block for up to
237 will be generated:
249 across the system enabling logs will lead to flooding. The logger provides the tools
341 a feature which will wake up processing thread when certain amount of log messages are
482 particular source will be buffered.
640 * If domains have different timestamp sources, messages will be
711 Therefore, log messages with ``long double`` will not display the correct
739 a JSON database file, named :file:`log_dictionary.json`, will be created
836 which includes string formatting. In case of that mode, stack usage will depend on which backends
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_config_guide.rst | 139 This tells how many network interfaces there will be in the system
140 that will have IPv4 enabled.
177 that a segment will be buffered awaiting retransmission:
184 With the default value of 9, the IP stack will try to
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 36 gives basic requirements that a developer working on the project will
41 should have. This knowledge will be necessary for the review process
234 This team will be established according to the Zephyr Project charter.
262 field to allow the Zephyr Security Subcommittee to add additional users that will
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | CMakeLists.txt | 227 "restriction will be removed once licensing issues have been resolved."
353 # A dependency on tfm_s.hex for zephyr.elf will not cause a Zephyr re-link when
356 # updated when there are changes in tfm itself, this again will trigger an re-link
529 The device will be provisioned using dummy keys and is NOT secure!
|
| /Zephyr-latest/boards/microchip/mec15xxevb_assy6853/doc/ |
| D | index.rst | 285 #. Connect programmer to the header J6 on the Assy6791 board, it will flash the SPI NOR chip ``U3``
350 #. The file :file:`spi_image.bin` will be created if the build system
381 till the whole west process will not be finished successfully.
391 Result will be the same.
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/doc/ |
| D | index.rst | 298 The Zephyr build system will perform the following steps automatically:
331 application core, the Secure application will have to set the IDAU
357 read-back protection is active, you will need to recover the chip
400 Many of the Bluetooth examples will work on the BL5340 DVK.
|
| /Zephyr-latest/arch/riscv/ |
| D | Kconfig | 41 When is enabled, calls to `arch_current_thread()` & `k_sched_current_thread_query()` will
177 architecture code will allocate space for these members in
178 a "struct soc_esf" type (typedefed to soc_esf_t), which will
184 The generic architecture IRQ wrapper will also call
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_0.rst | 546 application registers a callback, the callback will be called when this command
780 | | will be used. |
883 | | If there is no query, then response will |
988 In case when MCUboot is application bootloader, empty request will
1039 version than the currently running application, it will not be used for an update by MCUboot.
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig | 35 i.e. without a MAC stack (the net L2 layer for 802.15.4 will not
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.nor | 75 When CONFIG_FLASH_PAGE_LAYOUT is used this driver will support
|
1...<<41424344454647484950>>...66
