Searched refs:locate (Results 1 – 23 of 23) sorted by relevance
/Zephyr-latest/tests/arch/arm/arm_custom_interrupt/ |
D | README.txt | 8 option. It will locate a unused interrupt to trigger via software and test
|
/Zephyr-latest/share/sysbuild/ |
D | Kconfig.v2 | 9 This option holds the name of the board and is used to locate the files
|
/Zephyr-latest/subsys/bluetooth/audio/ |
D | Kconfig.csip | 75 to locate members and decrypt the SIRK, and thus won't work
|
/Zephyr-latest/boards/waveshare/rp2040_zero/doc/ |
D | index.rst | 123 In alternative you can locate the generated file at ``build/zephyr/zephyr.uf2 file`` and simply dra…
|
/Zephyr-latest/cmake/modules/ |
D | configuration_files.cmake | 8 # Also, locate the appropriate application config directory.
|
D | FindZephyr-sdk.cmake | 66 message(STATUS "ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK")
|
/Zephyr-latest/share/zephyr-package/cmake/ |
D | zephyr_package_search.cmake | 46 # to locate in-project-tree Zephyr candidates.
|
D | ZephyrConfigVersion.cmake | 5 # The purpose of the version file is to ensure that CMake find_package can correctly locate a
|
/Zephyr-latest/samples/net/cloud/mqtt_azure/ |
D | README.rst | 59 On your Linux host computer, open a terminal window, locate the source code
|
/Zephyr-latest/samples/net/mqtt_sn_publisher/ |
D | README.rst | 83 Then, locate your zephyr directory and type:
|
/Zephyr-latest/doc/develop/api/ |
D | design_guidelines.rst | 28 context that allows a shared callback function to locate additional
|
/Zephyr-latest/boards/ |
D | Kconfig | 8 This option holds the name of the board and is used to locate the files
|
/Zephyr-latest/soc/microchip/mec/ |
D | Kconfig | 14 to RAM using a TAG to locate a Header which specifies the location and
|
/Zephyr-latest/doc/develop/ |
D | env_vars.rst | 221 will try to locate those programs automatically, but may rely on additional
|
/Zephyr-latest/doc/develop/west/ |
D | troubleshooting.rst | 218 variable <env_vars>` to locate a workspace elsewhere on your system.
|
D | build-flash-debug.rst | 395 west whenever it needs to create or locate a build folder. The currently
|
D | release-notes.rst | 240 variable to locate the workspace.
|
/Zephyr-latest/doc/hardware/porting/ |
D | soc_porting.rst | 124 locate such SoC in a common tree.
|
/Zephyr-latest/samples/net/mqtt_publisher/ |
D | README.rst | 91 On your Linux host computer, open a terminal window, locate the source code
|
/Zephyr-latest/boards/acrn/acrn/doc/ |
D | index.rst | 81 Next, locate the load address of the Zephyr image and its entry point
|
/Zephyr-latest/doc/build/cmake/ |
D | index.rst | 251 locate the devices actually present in the application.
|
/Zephyr-latest/subsys/debug/ |
D | Kconfig | 355 locate. At -O1 and above gcc will enable -fomit-frame-pointer
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 220 Understanding the Zephyr source tree can help locate the code 370 repository. Use the search filters and labels to locate PRs related to changes
|