Searched refs:will (Results 651 – 675 of 1633) sorted by relevance
1...<<21222324252627282930>>...66
/Zephyr-latest/boards/microchip/mec172xevb_assy6906/support/ |
D | spi_cfg.txt | 11 ; is disabled. If PlatformID is enabled in OTP Boot-ROM will check the image
|
/Zephyr-latest/boards/microchip/mec172xmodular_assy6930/support/ |
D | spi_cfg.txt | 11 ; is disabled. If PlatformID is enabled in OTP Boot-ROM will check the image
|
D | spi_cfg_4MBit.txt | 11 ; is disabled. If PlatformID is enabled in OTP Boot-ROM will check the image
|
/Zephyr-latest/tests/drivers/gpio/gpio_basic_api/ |
D | README.txt | 15 will fail with an error like this:
|
/Zephyr-latest/boards/nxp/mimxrt1010_evk/ |
D | CMakeLists.txt | 31 "This timer will enable lower power modes, but at the cost of reduced "
|
/Zephyr-latest/boards/nxp/mimxrt1015_evk/ |
D | CMakeLists.txt | 30 "This timer will enable lower power modes, but at the cost of reduced "
|
/Zephyr-latest/boards/shields/lcd_par_s035/boards/ |
D | rd_rw612_bga.overlay | 71 * the minimum write duration will be 2x the module 80 * on the LCDIC will apply byte swapping in hardware, so the
|
/Zephyr-latest/samples/drivers/mbox_data/ |
D | README.rst | 13 Sample will ping-pong up to 4 bytes of data between two cores via two mbox channels. 68 Reset the board and the following message will appear on the corresponding
|
/Zephyr-latest/samples/boards/nordic/battery/ |
D | README.rst | 46 voltage will be fed from a regulator that provides a fixed voltage 48 configuration involving a regulator the measured voltage will be
|
/Zephyr-latest/boards/intel/socfpga/agilex5_socdk/doc/ |
D | index.rst | 45 NOTE: TODO, more details on dev kit will be updated as and when available. 55 Zephyr image will need to be loaded by Intel Arm Trusted Firmware (ATF).
|
/Zephyr-latest/boards/qemu/cortex_a53/doc/ |
D | index.rst | 6 This board configuration will use QEMU to emulate a generic Cortex-A53 hardware 68 This will build an image with the synchronization sample app, boot it using
|
/Zephyr-latest/boards/qemu/cortex_m0/doc/ |
D | index.rst | 6 This board configuration will use QEMU to emulate the 72 This will build an image with the synchronization sample app, boot it using
|
/Zephyr-latest/boards/arm/fvp_base_revc_2xaemv8a/doc/ |
D | index.rst | 9 This board configuration will use ARM Fixed Virtual Platforms(FVP) to emulate 83 This will build an image with the synchronization sample app.
|
/Zephyr-latest/modules/trusted-firmware-m/ |
D | Kconfig.tfm | 166 Instead the application will have to override the weak ARM 175 keys / data will be provisioned. The dummy IAK matches the IAK tested 241 will result in compilation error. 253 but hardware rollback protection will only apply when this value is incremented. 295 case MCUboot will be fetched by the TF-M build during 302 TF-M builds with BL2 will use the Zephyr's MCUboot version, 308 TF-M builds with BL2 will let the TF-M build to automatically 373 The regression tests will be included in the TF-M secure firmware. 380 The regression tests will be included in the TF-M non-secure 462 On some platforms this will release the UART from
|
/Zephyr-latest/doc/kernel/services/ |
D | polling.rst | 63 guarantee that it will be still available when :c:func:`k_sem_take` is 74 event a call to :c:func:`k_poll` will wait for its condition to be 147 Notice that the waiters will be served in first-come-first-serve order, 156 // -EADDRINUSE will not occur; the semaphore and/or data will be available 305 that is passed a signal will return after any code in the system calls 310 application will miss events. Best practice is always to reset the
|
/Zephyr-latest/doc/develop/west/ |
D | config.rst | 77 Doing the above means that commands like ``west update`` will look for the 82 To read ``zephyr.base``, the value which will be used as ``ZEPHYR_BASE`` if it 103 so that west will no longer print colored output for that user when run in any 233 :ref:`west-update` command will skip fetching 238 - String. If non-empty, ``west update`` will use its value as the 244 - String. If non-empty, ``west update`` will use its value as the 247 - Boolean. If ``true`` (the default), :ref:`west-update` will synchronize
|
/Zephyr-latest/boards/nordic/nrf52840dongle/doc/ |
D | index.rst | 134 that the button does not face up. You will have to push it from the outside 158 #. Flash it onto the board. Note :file:`/dev/ttyACM0` is for Linux; it will be 205 #. Flash it onto the board. Note :file:`/dev/ttyACM0` is for Linux; it will be 220 **Do not press RESET**; that will run the Nordic bootloader, which is 223 A serial port will enumerate on your board. On Windows, "MCUBOOT" should 260 computer. The device you just flashed will be listed with ``Zephyr`` in its 295 ``BOARD_HAS_NRF5_BOOTLOADER`` to be default ``n``, otherwise the code will be
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | workqueue.rst | 27 Regardless of workqueue thread priority the workqueue thread will yield 77 the preceding work items in its queue the thread will remove the next work 86 A work item will be **running** (:c:enumerator:`K_WORK_RUNNING`) when it is running 170 item in response to a **poll event** (see :ref:`polling_v2`), that will 179 * A pointer to an array of poll events that will trigger work item 263 item will silently fail to be submitted. 282 unchanged and the associated error message will not be printed. 332 the work completes; it will return immediately if the cancellation was 352 will not change the time at which the item will be submitted to its queue. 423 work thread to sleep will starve other work queue items, which may need to [all …]
|
/Zephyr-latest/doc/kernel/drivers/ |
D | index.rst | 50 number generators and will not provide cryptographically secure 126 Most drivers will be implementing a device-independent subsystem API. 155 A driver implementing a particular subsystem will define the real implementation 182 struct, they will always be included in the binary even if unused; 183 ``gc-sections`` linker option will always see at least one reference to 211 A driver implementing extensions to the subsystem will define the real 267 will have a different ``config`` struct and ``data`` struct. 346 function will be executed. Any driver will specify one of four 353 not yet available. The interrupt subsystem will be configured however 458 These drivers will need to use the ``DEVICE_MMIO_ROM`` and
|
/Zephyr-latest/subsys/bluetooth/host/classic/ |
D | Kconfig | 51 RX MTU will be truncated to account for the L2CAP PDU header. 116 not switch to alerting state before timeout, it will be 125 not switch to ringing state before timeout, it will be 134 call is not active before timeout, it will be stopped
|
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
D | csip.rst | 12 The client will typically be a resource-rich device, such as a smartphone 17 lock. This implementation will always try to connect to all the members of 30 initialized by calling :code:`csip_set_coordinator init`, which will start a discovery 174 If :code:`CONFIG_BT_CSIP_SET_MEMBER_NOTIFIABLE` is enabled, this will also notify connected
|
/Zephyr-latest/boards/snps/iotdk/doc/ |
D | index.rst | 165 IoT Development Kit, but it will load the application and immediately run. If 166 power is removed, the application will be lost since it wasn't written to flash. 168 Most of the time you will not be flashing your program but will instead debug
|
/Zephyr-latest/samples/kernel/metairq_dispatch/ |
D | README.rst | 43 priority will experience some load-dependent delays, as the CPU 63 native_sim platforms. In that emulation environment, threads will 65 k_busy_wait()) where they will voluntarily release the CPU. 83 Sample output shown below is from frdm_k64f. The numbers will
|
/Zephyr-latest/subsys/net/lib/mqtt_sn/ |
D | mqtt_sn_encoder.c | 65 LOG_DBG("Encode flags %d, %d, %d, %d, %d, %d", flags->dup, flags->retain, flags->will, in encode_flags() 70 b |= flags->will ? MQTT_SN_FLAGS_WILL : 0; in encode_flags() 117 struct mqtt_sn_flags flags = {.will = params->will, .clean_session = params->clean_session}; in mqtt_sn_encode_msg_connect()
|
/Zephyr-latest/lib/libc/picolibc/ |
D | Kconfig | 84 Compiler optimizations will be set to -Os independently of other 90 Compiler optimizations will be set to -O2 independently of other 96 Compiler optimizations will be set to -Og independently of other 102 Compiler optimizations will be set to -O0 independently of other
|
1...<<21222324252627282930>>...66