Searched refs:could (Results 76 – 100 of 320) sorted by relevance
12345678910>>...13
| /Zephyr-latest/doc/build/dts/ |
| D | dt-vs-kconfig.rst | 30 devicetree. This could include configuration such as the RX IRQ line's
|
| /Zephyr-latest/drivers/clock_control/ |
| D | Kconfig.stm32 | 31 Value of external high-speed clock (HSE). This symbol could be optionally
|
| /Zephyr-latest/samples/subsys/smf/smf_calculator/ |
| D | README.rst | 92 matrix area when pressed, rather than just the button that was selected. This could
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig | 41 paths in code that only serve such devices, and could be
62 such devices, and could be optimized-out by compiler in
|
| /Zephyr-latest/boards/st/stm32u083c_dk/doc/ |
| D | index.rst | 176 STM32U083C_DK System Clock could be driven by internal or external oscillator,
245 Default flasher for this board is openocd. It could be used in the usual way.
|
| /Zephyr-latest/boards/st/stm32h745i_disco/doc/ |
| D | index.rst | 82 STM32H745I-DISCO System Clock could be driven by an internal or external
103 - **Run time protection**: Interrupt-controller and GPIO configurations could be
|
| /Zephyr-latest/boards/st/nucleo_u083rc/doc/ |
| D | index.rst | 168 Nucleo U083RC System Clock could be driven by internal or external oscillator,
237 Default flasher for this board is openocd. It could be used in the usual way.
|
| /Zephyr-latest/boards/st/nucleo_u575zi_q/doc/ |
| D | index.rst | 180 Nucleo U575ZI Q System Clock could be driven by internal or external oscillator,
257 Default flasher for this board is openocd. It could be used in the usual way.
|
| /Zephyr-latest/boards/st/nucleo_wba52cg/doc/ |
| D | nucleo_wba52cg.rst | 177 Nucleo WBA52CG System Clock could be driven by internal or external oscillator,
191 It could be used for flash and debug using either OpenOCD or STM32Cube ecosystem tools.
|
| /Zephyr-latest/boards/st/nucleo_wba55cg/doc/ |
| D | nucleo_wba55cg.rst | 186 Nucleo WBA55CG System Clock could be driven by internal or external oscillator,
200 It could be used for flash and debug using either OpenOCD or STM32Cube ecosystem tools.
|
| /Zephyr-latest/boards/telink/tlsr9518adk80d/doc/ |
| D | index.rst | 51 - Maximum 3 GPIO pins could be configured to generate interrupts simultaneously. All pins must be r…
65 The following values also could be assigned to the system clock in the board DTS file
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | zephyr_package_search.cmake | 76 # NO_DEFAULT_PATH means explicit search and we could be part of a preference list.
|
| /Zephyr-latest/boards/franzininho/esp32s2_franzininho/doc/ |
| D | index.rst | 53 The board could be loaded using the single binary image, without 2nd stage bootloader.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | gatt.rst | 96 the same attribute are supported so there could be multiple ``notify`` callback
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | capture.rst | 30 network data could be captured although currently there is no support in the
|
| /Zephyr-latest/boards/fanke/fk750m1_vbt6/doc/ |
| D | index.rst | 71 The FK750M1-VBT6 System Clock could be driven by an internal or external oscillator,
|
| /Zephyr-latest/boards/makerbase/mks_canable_v20/doc/ |
| D | index.rst | 80 The board could be flashed using west.
|
| /Zephyr-latest/samples/net/dns_resolve/ |
| D | README.rst | 115 sending, then following config options could be set:
|
| /Zephyr-latest/boards/st/nucleo_f412zg/doc/ |
| D | index.rst | 106 Nucleo F412ZG System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.ll_sw_split | 372 recombining the AD Data and could return BT_HCI_ERR_PACKET_TOO_LONG
374 I.e. AD data in the last PDU could overflow due to the need to add
376 fragment length could be over 255 bytes needing additional chain PDU.
439 Advertising Data could be updated from zero to maximum support size.
548 reception. A peer device could scheduling multiple advertising sets
617 When enabled, this could result in an SDU being fragmented into
623 When disabled, TX SDUs could be shifted from their stream aligned
803 length could be updated from default 27 bytes to maximum support size.
817 length could be updated from default 27 bytes to maximum support size.
1121 interval could lock to a round robin pattern where in neither of the central
|
| /Zephyr-latest/doc/services/sensing/ |
| D | index.rst | 31 kernel space and could support various customizations and sensor
158 For a sensor instance, could have two kinds of clients:
|
| /Zephyr-latest/boards/st/nucleo_h745zi_q/doc/ |
| D | index.rst | 108 Nucleo H745ZI-Q System Clock could be driven by an internal or external
129 - **Run time protection**: Interrupt-controller and GPIO configurations could be
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_config_guide.rst | 143 If both network interface could use IPv4, then the setting should be
202 TCP connections could easily exhaust net_buf pool for the queued TX data.
248 option :kconfig:option:`CONFIG_NET_TC_RX_COUNT` could be set to 0.
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 105 precompiled binary form, typically for SoC peripherals. An example could be an
110 could be the firmware for the core running a Bluetooth LE Controller
111 * Miscellaneous binary data files. An example could be pre-trained neural
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 173 However, when sysbuild combines multiple Zephyr build systems, there could be
528 This could be useful, for example, if your board requires you to build and flash an
554 This could be useful, for example, if your main application requires another
656 A Kconfig fragment could look as:
774 images used by ``west flash``; this could be used if a specific flashing order
867 or include other configuration or images, an example could be to add support
|
12345678910>>...13
