Searched refs:looks (Results 1 – 25 of 58) sorted by relevance
123
| /Zephyr-latest/cmake/emu/ |
| D | custom.cmake | 3 # ${ZEPHYR_BASE}/CMakeLists.txt looks for ${ZEPHYR_BASE}/cmake/emu/${EMU_PLATFORM}.cmake
|
| /Zephyr-latest/samples/bluetooth/central_hr/ |
| D | README.rst | 11 application specifically looks for heart-rate monitors and reports the
|
| /Zephyr-latest/samples/bluetooth/central_ht/ |
| D | README.rst | 11 application specifically looks for health thermometer sensor and reports the
|
| /Zephyr-latest/samples/bluetooth/central_otc/ |
| D | README.rst | 11 application specifically looks for the OTS (Object Transfer) GATT Service.
|
| /Zephyr-latest/samples/sensor/qdec/ |
| D | README.rst | 27 For example, here's how the overlay file of an STM32F401 board looks like when
|
| /Zephyr-latest/doc/security/ |
| D | hardening-tool.rst | 20 tool looks at the KConfig options in the build target and provides tailored suggestions and
|
| /Zephyr-latest/samples/boards/st/ccm/ |
| D | README.rst | 37 For example the olimex STM32 E407 DTS file looks like this:
96 When the board is reset (without power-cycling), the output looks like this:
|
| /Zephyr-latest/samples/drivers/display/ |
| D | README.rst | 14 grey changes from black through to white. If the grey looks too green or red
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-intro.rst | 79 system looks for compatible bindings in the listed order and uses the first
112 The build system looks for bindings in :file:`dts/bindings`
|
| D | troubleshooting.rst | 70 ``<N>`` is 15, and your :file:`devicetree_generated.h` file looks like this,
98 looks like this:
162 Continuing the above example, if your devicetree node looks like this now:
181 :zephyr_file:`drivers/i2c/CMakeLists.txt` has a line that looks like this:
315 looks like this:
|
| /Zephyr-latest/boards/panasonic/pan1783/doc/ |
| D | index.rst | 22 The PAN1783A EVB essentially looks like a PAN1783 EVB, except that it is
|
| /Zephyr-latest/samples/basic/blinky/ |
| D | README.rst | 54 On GCC-based toolchains, the error looks like this:
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 66 The build system looks for snippets in these places:
78 For each directory in the list, the build system looks for
|
| /Zephyr-latest/doc/develop/west/ |
| D | troubleshooting.rst | 66 #. Look for a line in the output that looks like ``Location:
160 separately, and looks like this for mainline Zephyr:
|
| D | workspaces.rst | 183 A workspace using this topology looks like this:
270 A workspace using this topology looks like this:
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | preprocessor-functions.rst | 123 Assume that the devicetree for some board looks like this:
|
| /Zephyr-latest/samples/basic/button/ |
| D | README.rst | 110 After startup, the program looks up a predefined GPIO device, and configures the
|
| /Zephyr-latest/doc/develop/tools/ |
| D | stm32cubeide.rst | 120 When configuring your project you see an error that looks similar to:
|
| /Zephyr-latest/boards/shields/amg88xx/doc/ |
| D | index.rst | 151 When using the PAN1780 evaluation board the build invocation looks like this:
|
| /Zephyr-latest/cmake/modules/ |
| D | zephyr_module.cmake | 19 # It looks for: <module>/zephyr/module.yml or
|
| /Zephyr-latest/samples/boards/nxp/adsp/number_crunching/ |
| D | README.rst | 102 For NatureDSP, the output looks like this:
|
| /Zephyr-latest/lib/os/ |
| D | Kconfig.cbprintf | 163 flag, the packaging function no longer looks at the format strings
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | coap.rst | 205 Sample output of ttcn3 tests looks like this.
|
| /Zephyr-latest/doc/develop/test/ |
| D | coverage.rst | 199 Twister looks at the environment variable ``ZEPHYR_TOOLCHAIN_VARIANT``
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 168 node`_ that looks like the following into the board devicetree file:
|
123
