Searched refs:could (Results 226 – 250 of 320) sorted by relevance
12345678910>>...13
| /Zephyr-latest/boards/st/stm32n6570_dk/doc/ |
| D | index.rst | 102 STM32N6570_DK System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/boards/st/nucleo_h755zi_q/doc/ |
| D | index.rst | 121 - **Run time protection**: Interrupt-controller and GPIO configurations could be
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 208 translation we could support this.
254 being stored twice in the same CPU, wasting transistors that could
|
| /Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
| D | index.rst | 187 language options are still set in Zephyr generic code. It could be observed by
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tls_credentials_shell.rst | 258 Otherwise, the ``STRT`` format could be used for this purpose without base64 encoding.
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 187 *get* and *put* operations could be carried out as follows:
|
| /Zephyr-latest/boards/st/stm32h7s78_dk/doc/ |
| D | index.rst | 190 STM32H7S78-DK System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | timers.rst | 213 If the thread had no other work to do it could simply sleep
|
| /Zephyr-latest/drivers/bluetooth/hci/ |
| D | Kconfig | 355 More inforamtion about NXP Bluetooth profuct could be found on
|
| /Zephyr-latest/boards/st/nucleo_wb55rg/doc/ |
| D | nucleo_wb55rg.rst | 191 Nucleo WB55RG System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/boards/st/nucleo_l552ze_q/doc/ |
| D | nucleol552ze_q.rst | 216 Nucleo L552ZE Q System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/samples/net/sockets/http_server/ |
| D | README.rst | 123 us with an interactive configuration interface. Then we could navigate from the top-level
|
| /Zephyr-latest/boards/st/nucleo_h7s3l8/doc/ |
| D | index.rst | 172 Nucleo H7S3L8 System Clock could be driven by an internal or external
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 322 instance, to validate the GPIO driver, one could use the
421 memory as part of its logic. For example, it could be used to store some
422 counter value, and this could be meddled with by user threads that have access
|
| D | overview.rst | 18 could otherwise silently or spectacularly corrupt the system.
|
| /Zephyr-latest/boards/st/stm32h747i_disco/doc/ |
| D | index.rst | 151 - **Run time protection**: Interrupt-controller and GPIO configurations could be
|
| /Zephyr-latest/boards/st/stm32l562e_dk/doc/ |
| D | index.rst | 209 STM32L562E-DK System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/boards/espressif/esp32s3_eye/doc/ |
| D | index.rst | 141 The board could be loaded using the single binary image, without 2nd stage bootloader.
|
| /Zephyr-latest/boards/st/nucleo_h533re/doc/ |
| D | index.rst | 178 Nucleo H533RE System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/boards/st/nucleo_h563zi/doc/ |
| D | index.rst | 168 Nucleo H563ZI System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/boards/st/stm32wb5mmg/doc/ |
| D | stm32wb5mmg.rst | 194 STM32WB5MMG System Clock could be driven by internal or external oscillator,
|
| /Zephyr-latest/samples/net/lwm2m_client/ |
| D | README.rst | 210 You could get all parameters for existing OT network from your OTBR with
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 106 which could be interrupted on actual hardware, will stall the execution of
137 - This port is not meant to, and could not possibly help debug races between
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 156 currently running). As an example, this could be to reset mocks, reset emulators, flush the UART,
186 replicate without starting the process over. For example, one such state could be a power sequence.
|
| /Zephyr-latest/doc/_extensions/zephyr/kconfig/static/ |
| D | kconfig.mjs | 563 showError(`Kconfig database could not be loaded (${error})`);
|
12345678910>>...13
