Searched refs:these (Results 251 – 275 of 642) sorted by relevance
1...<<11121314151617181920>>...26
| /Zephyr-latest/boards/qemu/cortex_a53/doc/ |
| D | index.rst | 9 This configuration provides support for an ARM Cortex-A53 CPU and these
|
| /Zephyr-latest/boards/arm/fvp_base_revc_2xaemv8a/doc/ |
| D | index.rst | 13 these devices:
|
| /Zephyr-latest/cmake/compiler/clang/ |
| D | compiler_flags.cmake | 14 # But clang has problems compiling these with -fno-freestanding.
|
| /Zephyr-latest/boards/qemu/cortex_m0/doc/ |
| D | index.rst | 9 This configuration provides support for an ARM Cortex-M0 CPU and these devices:
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_timeout.rst | 30 the remaining time for these extended-duration timeouts.
|
| /Zephyr-latest/doc/services/debugging/ |
| D | debugmon.rst | 60 After these steps use regular gdb commands to debug your program.
|
| /Zephyr-latest/arch/x86/core/ |
| D | Kconfig.intel64 | 57 # the assembler. For now, we require that these values be specified manually,
|
| /Zephyr-latest/samples/net/sockets/http_client/ |
| D | README.rst | 40 ``overlay-tls.conf`` overlay file enabled using these commands:
|
| /Zephyr-latest/samples/net/sockets/websocket_client/ |
| D | README.rst | 41 ``overlay-tls.conf`` overlay file enabled using these commands:
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.toolchain | 9 # Use these features with caution as doing so might introduce unwanted, unexpected, or undefined
|
| /Zephyr-latest/samples/bluetooth/mesh/ |
| D | README.rst | 64 bind a dummy Application key to these models.
|
| /Zephyr-latest/samples/bluetooth/mesh_demo/ |
| D | README.rst | 25 addresses in the range of 0x0001-0x0009 for the micro:bit since these
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 342 in the appropriate location. The CMake ``find_package`` mechanism will search for these files with
344 version checking implemented for these packages. This also means that these packages cannot be
365 If you want to completely disable the search for these packages, you can use the special CMake
418 The following is an overview of the files in these directories:
|
| /Zephyr-latest/boards/weact/mini_stm32h7b0/doc/ |
| D | index.rst | 123 To activate the bootloader, follow these steps:
129 Upon successful execution of these steps, the device will transition into
|
| /Zephyr-latest/boards/weact/stm32h5_core/doc/ |
| D | index.rst | 113 To activate the bootloader, follow these steps:
119 Upon successful execution of these steps, the device will transition into
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 64 the ``BOARD`` variable, these are shared among multiple build systems.
175 To handle this, sysbuild has namespaces for configuration variables. You can use these
177 application managed by sysbuild using the information in these sections.
430 For the main application (as is the same without using sysbuild) these can be
431 ran normally without any prefix. For other images (including sysbuild), these
447 and ``bl2_ram_report``. To run these build targets, the build directory of the
790 (in some order) before doing the same for ``my_sample``, when building these
800 (in some order), when flashing these domains in a single invocation.
831 instead these must be set by using a :ref:`a module <modules_build_settings>` or by using a custom
|
| /Zephyr-latest/soc/atmel/sam0/common/ |
| D | Kconfig.samd2x | 10 Wait states to set for NVM. Consult the datasheet as these are highly
|
| /Zephyr-latest/boards/silabs/radio_boards/slwrb4161a/doc/ |
| D | index.rst | 24 For more information about the EFR32MG12 SoC and BRD4170A board, refer to these
|
| /Zephyr-latest/boards/silabs/radio_boards/slwrb4170a/doc/ |
| D | index.rst | 24 For more information about the EFR32MG12 SoC and BRD4170A board, refer to these
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.stm32 | 84 to option and control registers until reset. Disabling access to these
|
| /Zephyr-latest/boards/waveshare/rp2040_zero/doc/ |
| D | index.rst | 33 …2040 SoC can be routed to various pins on the board. The configuration of these routes can be modi…
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr-user-node.rst | 131 :c:func:`gpio_pin_configure_dt` for details on these APIs.)
|
| /Zephyr-latest/boards/ronoth/lodev/ |
| D | ronoth_lodev.dts | 8 * Note: SPI2 and several GPIOs are not available in the S76S - these are connected
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | dfu.rst | 18 device. For information on these protocols and frameworks please refer to the
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | cadence_xcc.rst | 29 #. :ref:`Set these environment variables <env_vars>`:
|
1...<<11121314151617181920>>...26
