Home
last modified time | relevance | path

Searched refs:could (Results 151 – 175 of 320) sorted by relevance

12345678910>>...13

/Zephyr-latest/boards/st/stm32f429i_disc1/doc/
Dindex.rst105 The STM32F429I-DISC1 System Clock could be driven by an internal or external oscillator,
/Zephyr-latest/boards/witte/linum/doc/
Dindex.rst300 Linum H753ZI System Clock could be driven by an internal or external
/Zephyr-latest/
DCODE_OF_CONDUCT.md36 * Other conduct which could reasonably be considered inappropriate in a
/Zephyr-latest/boards/lilygo/ttgo_t8c3/doc/
Dindex.rst80 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/lilygo/ttgo_t8s3/doc/
Dindex.rst93 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/espressif/esp32s2_devkitc/doc/
Dindex.rst69 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/espressif/esp32s2_saola/doc/
Dindex.rst69 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/st/nucleo_f746zg/doc/
Dindex.rst116 Nucleo F746ZG System Clock could be driven by an internal or external
/Zephyr-latest/boards/st/nucleo_f767zi/doc/
Dindex.rst122 Nucleo F767ZI System Clock could be driven by an internal or external
/Zephyr-latest/boards/st/nucleo_h743zi/doc/
Dindex.rst110 Nucleo H743ZI System Clock could be driven by an internal or external
/Zephyr-latest/boards/adi/eval_adin2111ebz/doc/
Dindex.rst108 EVAL-ADIN2111EBZ System Clock could be driven by an internal or external oscillator, as well as the
/Zephyr-latest/boards/ti/cc1352p7_launchpad/doc/
Dindex.rst121 …Until its support get merged, we have to builld a downstream version that could found `here <https…
/Zephyr-latest/lib/os/
DKconfig.cbprintf40 GCC's __udivdi3 helper could end up being pulled into the
/Zephyr-latest/boards/st/nucleo_l432kc/doc/
Dindex.rst125 Nucleo L432KC System Clock could be driven by internal or external oscillator,
/Zephyr-latest/boards/st/nucleo_l433rc_p/doc/
Dindex.rst128 Nucleo L433RC-P System Clock could be driven by internal or external oscillator,
/Zephyr-latest/doc/build/dts/
Dphandles.rst52 controller that receives the asserted interrupt. In this case, you could
266 With that, if ``phandle-array-prop-2`` has specifier space ``bob``, we could
/Zephyr-latest/doc/services/shell/
Dindex.rst291 be a set of pairs: (string: gain_value, int: value) where int value could
748 in the system. The shell instance could have a slow transport or could
750 set too high, the logger thread could be blocked and impact other logger
/Zephyr-latest/doc/kernel/services/threads/
Dworkqueue.rst45 which could introduce delays.
454 to notify the application that the work could not be performed.
475 happens the work will not be executed, which could cause a subsystem that is
525 A rare case where you could safely use :c:func:`k_work_is_pending` is as a
/Zephyr-latest/boards/heltec/heltec_wifi_lora32_v2/doc/
Dindex.rst45 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/arduino/opta/doc/
Dindex.rst94 - **Run time protection**: Interrupt-controller and GPIO configurations could be
/Zephyr-latest/boards/dptechnics/walter/doc/
Dindex.rst83 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/lilygo/ttgo_lora32/doc/
Dindex.rst81 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/we/orthosie1ev/doc/
Dindex.rst70 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/m5stack/m5stickc_plus/doc/
Dindex.rst90 The board could be loaded using the single binary image, without 2nd stage bootloader.
/Zephyr-latest/boards/espressif/esp32c3_devkitm/doc/
Dindex.rst70 The board could be loaded using the single binary image, without 2nd stage bootloader.

12345678910>>...13