Searched refs:could (Results 51 – 75 of 320) sorted by relevance
12345678910>>...13
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | CMakeLists.txt | 5 "default value change could change Zephyr Bluetooth "
|
| /Zephyr-latest/samples/sysbuild/hello_world/ |
| D | README.rst | 12 scenarios could include boards embedding multiple SoCs. When building with
|
| /Zephyr-latest/cmake/ |
| D | target_toolchain_flags.cmake | 14 # methods, where an upgraded compiler could have same signature due to ccache
|
| /Zephyr-latest/drivers/bluetooth/hci/ |
| D | Kconfig.nxp | 87 Details of the module could be fond on https://www.nxp.com/products/
|
| /Zephyr-latest/boards/nxp/frdm_mcxn947/ |
| D | frdm_mcxn947_mcxn947_cpu0.dtsi | 46 * For example, SRAM0-6 could be allocated to cpu0 with only SRAM7
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfigVersion.cmake | 116 …# This means this Zephyr is likely the correct one, but there could be an alternative installed al…
125 # Checking for installed candidates which could also be an workspace candidates.
|
| /Zephyr-latest/doc/services/portability/ |
| D | cmsis_rtos_v2.rst | 9 microcontrollers alone, it could be easily extended to other microcontrollers
|
| /Zephyr-latest/samples/subsys/logging/dictionary/ |
| D | README.rst | 12 in hexadecimal so it could be run in terminal.
|
| /Zephyr-latest/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 13 example, one could use the sample in
|
| /Zephyr-latest/drivers/espi/ |
| D | Kconfig | 77 This depends on SPI boot configuration. It could be either very
78 early in the flow after the VW channel is configured. Or it could be
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.nrfx | 52 Default mode could miscount bytes when interrupt was not handled on time
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.cc13xx_cc26xx | 27 replying it could not send the packet.
|
| D | Kconfig.nrf5 | 38 the system. One example of external radio IRQ provider could be
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | adopted_deviations.ecl | 42 …Chainging the generators could be dangerous and the advantages in enforcing the rule do not outwei…
|
| /Zephyr-latest/samples/net/prometheus/ |
| D | README.rst | 64 us with an interactive configuration interface. Then we could navigate from the top-level
|
| /Zephyr-latest/boards/nxp/lpcxpresso55s69/ |
| D | lpcxpresso55s69_lpc55s69_cpu0.dts | 83 * For example, SRAM0-3 could be allocated to cpu0 with only SRAM4
|
| /Zephyr-latest/cmake/modules/ |
| D | west.cmake | 94 # That's fine; west is optional, so could be custom Zephyr project.
|
| /Zephyr-latest/boards/waveshare/esp32s3_touch_lcd_1_28/doc/ |
| D | index.rst | 82 The board could be loaded using the single binary image, without 2nd stage bootloader.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_pkt_filter.rst | 73 Another (less efficient) way to achieve the same result could be:
|
| /Zephyr-latest/samples/net/sockets/txtime/ |
| D | Kconfig | 11 The value depends on your network setup. This could be
|
| /Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/ |
| D | README.rst | 58 :kconfig:option:`CONFIG_DEBUG` could be enabled to allow debug. Note that debug mode prevents
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 62 one described above. Generic functionalities that could be reused among
119 Alternatively, it could be set by default in a project's CMakeLists.txt:
|
| /Zephyr-latest/doc/develop/west/ |
| D | west-apis.rst | 142 failure in this zephyr documentation that could not be fixed without
433 The *remote* attribute was removed. Its semantics could no longer
441 releases, it could be a string or ``None``.
|
| /Zephyr-latest/boards/st/nucleo_u031r8/doc/ |
| D | index.rst | 155 Nucleo U031R8 System Clock could be driven by internal or external oscillator,
224 Default flasher for this board is openocd. It could be used in the usual way.
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 222 In this case, the application CMakeLists.txt could be written as:
307 Such a CMakeLists.txt could look as:
335 application-specific package could override the workspace settings, if needed.
370 An example folder structure could look like this:
|
12345678910>>...13
