Searched refs:could (Results 1 – 25 of 320) sorted by relevance
12345678910>>...13
| /Zephyr-latest/samples/net/openthread/coap/ |
| D | README.rst | 18 Once the network is operational, then the client could start interacting with
33 we could expect less overhead although this makes the application less portable.
87 A valid state could be child, router or leader.
89 Once Thread network is operational, you could start using client.
104 Although we use OpenThread CoAP API, we could interact with any CoAP client
131 Prefixes show the IPv6 prefies that could be used by device outside the
145 fd6f:cb3a:802:1:f0ec:c1e2:c1bb:744 is the IPv6 address that could be used
148 We could also check that we could access internet from Thread network:
158 If everything is working, then, we could start controlling the LED from a computer.
|
| /Zephyr-latest/subsys/sensing/ |
| D | Kconfig | 38 int "maximum sensitivity count one sensor could support"
42 This is the maximum sensitivity count one sensor could support,
43 some sensors such as ALS sensor could define different sensitivity for each data filed,
63 dispatch thread priority to ensure dispatch thread could fetch data as
|
| /Zephyr-latest/boards/ti/cc1352p7_launchpad/support/ |
| D | openocd.cfg | 1 # Serial could be found using the following command:
|
| /Zephyr-latest/boards/native/nrf_bsim/common/ |
| D | README.txt | 1 This folder contains components that could be
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32_common_core/boards/ |
| D | clear_msi.overlay | 8 * Warning: This overlay clears the msi clock back to a state equivalent to what could
|
| D | clear_f0_f1_f3_clocks.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| D | clear_f2_f4_f7_clocks.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| D | clear_clocks.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| /Zephyr-latest/soc/st/stm32/stm32wb0x/ |
| D | ram_sections.ld | 11 * SRAM0 unused, even though it could store data.
|
| /Zephyr-latest/doc/build/dts/ |
| D | main-example.dts | 7 * If you change it for one example, you could break others, so be careful.
|
| /Zephyr-latest/doc/project/ |
| D | issues.rst | 19 It could happen that the issue being reported is identified as a regression,
24 To identify the commit causing the regression, several methods could be used,
|
| /Zephyr-latest/samples/net/tftp_client/ |
| D | Kconfig | 19 When DNS resolver is enabled, DNS domain names could be used as well.
|
| /Zephyr-latest/doc/services/portability/ |
| D | cmsis_rtos_v1.rst | 9 microcontrollers alone, it could be easily extended to other microcontrollers
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32wba_core/boards/ |
| D | clear_clocks.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| /Zephyr-latest/samples/tfm_integration/tfm_regression_test/boards/ |
| D | nucleo_l552ze_q_stm32l552xx_ns.overlay | 8 /* This partition table could be used along with TFM configuration:
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32u5_core/boards/ |
| D | clear_clocks.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| /Zephyr-latest/samples/subsys/fs/fs_sample/ |
| D | Kconfig | 14 In case when no files could be listed, because there are none,
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 001_bug_report.md | 25 Please also mention any information which could help others to understand
69 Add any other context that could be relevant to your issue, such as pin setting,
|
| /Zephyr-latest/boards/shields/x_nucleo_idb05a1/doc/ |
| D | index.rst | 42 Shield configuration could be modified by moving resistors as
48 expansion board could be made:
53 You could check Figure 3 in `X-NUCLEO-IDB05A1 databrief`_ for more details.
|
| /Zephyr-latest/cmake/ |
| D | pristine.cmake | 3 # NB: This could be dangerous to execute.
|
| /Zephyr-latest/boards/nxp/lpcxpresso55s69/ |
| D | lpcxpresso55s69_lpc55s69_cpu1.dts | 33 * For example, SRAM0-3 could be allocated to cpu0 with only SRAM4
|
| /Zephyr-latest/soc/espressif/esp32/ |
| D | Kconfig | 77 Larger number of buffers could increase throughput somehow.
85 Larger number of buffers could increase throughput somehow.
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32h5_core/boards/ |
| D | clear_clocks.overlay | 9 * Warning: This overlay clears clocks back to a state equivalent to what could
|
| /Zephyr-latest/samples/boards/nordic/nrf_led_matrix/ |
| D | README.rst | 17 but it could be ported to any board with an nRF SoC and the proper number
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32h7_core/boards/ |
| D | clear_clocks.overlay | 8 * Warning: This overlay clears clocks back to a state equivalent to what could
|
12345678910>>...13
