Searched refs:look (Results 26 – 50 of 108) sorted by relevance
12345
| /Zephyr-latest/samples/boards/phytec/reel_board/mesh_badge/ |
| D | README.rst | 21 #. On your phone, use the nRF Connect app to Scan for devices and look
|
| /Zephyr-latest/samples/subsys/usb/cdc_acm/ |
| D | README.rst | 91 For this example, it would look like this:
|
| /Zephyr-latest/doc/build/dts/ |
| D | troubleshooting.rst | 91 Now look for this node in :file:`<build>/zephyr/zephyr.dts`, which is the final
146 example, if your node's compatible is ``vnd,foo-device``, look for a file with this
171 Then you would look inside of :zephyr_file:`drivers/i2c` for the driver file
351 source file, ``compatible`` should look like ``"vnd,some-device"`` --
|
| D | bindings-syntax.rst | 17 The top level of a bindings file maps keys to values. The top-level keys look
75 :ref:`dt-binding-compat`. It should look like this in a binding file:
120 contain. For example, a binding for a UART peripheral might look something like
468 The binding would look like this:
514 of bus. For example, a binding for a SPI peripheral on an SoC would look like
|
| /Zephyr-latest/doc/develop/test/ |
| D | pytest.rst | 50 file can look like the following:
67 configuration file may look like this:
76 By default, pytest tries to look for tests in a ``pytest`` directory located next to a directory
|
| /Zephyr-latest/samples/net/sockets/http_get/ |
| D | README.rst | 82 Linux. (Note: if you look at the source, you will see that the code is
|
| /Zephyr-latest/doc/contribute/ |
| D | index.rst | 75 As you write documentation, it can be helpful to see how it will look when rendered.
|
| /Zephyr-latest/cmake/modules/ |
| D | configuration_files.cmake | 68 # If DTC_OVERLAY_FILE is not set by the user, look for SoC and board-specific overlays
|
| /Zephyr-latest/samples/subsys/fs/fs_sample/ |
| D | README.rst | 56 and DTS overlays need to be also selected. The command would look like this:
|
| /Zephyr-latest/samples/modules/lvgl/demos/ |
| D | README.rst | 19 Shows how the widgets look like out of the box using the built-in material theme.
|
| /Zephyr-latest/samples/subsys/ipc/rpmsg_service/ |
| D | README.rst | 140 The serial output should now look like this:
|
| /Zephyr-latest/doc/develop/languages/rust/ |
| D | index.rst | 40 to copy from a sample, but this will look something like:
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | target.cmake | 109 # look into changing to COMDAT groups.
|
| /Zephyr-latest/cmake/linker/xt-ld/ |
| D | target.cmake | 5 # When Toolchain home is defined, then we are cross-compiling, so only look
|
| /Zephyr-latest/boards/makerbase/mks_canable_v20/doc/ |
| D | index.rst | 22 It is very advisable to take a look in on user manual `MKS CANable V2.0 User Manual`_ and
|
| /Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
| D | index.rst | 19 It is recommended to look at precise description of a particular board target in ``.props``
162 It is advised to look for ``<board_name>_defconfig``, ``<board_name>.dts`` and
|
| /Zephyr-latest/boards/atmel/sam/sam_e70_xplained/doc/ |
| D | index.rst | 113 variable. OpenOCD will look for the appropriate interface
|
| /Zephyr-latest/boards/atmel/sam/sam_v71_xult/doc/ |
| D | index.rst | 116 variable. OpenOCD will look for the appropriate interface
|
| /Zephyr-latest/samples/boards/st/ccm/ |
| D | README.rst | 50 look like this:
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | README.rst | 94 The output to the console will look something like this
173 console will look something like this (file system contents will be
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | gap.rst | 48 For example, if you want to look only for devices with the name *test shell*:
54 Or if you want to look for devices at a very close range:
183 Let's now have a look at some extended advertising features. To enable extended advertising, use the
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfig.cmake | 135 # CMake finds packages will look all packages registered in the user package registry.
|
| D | ZephyrConfigVersion.cmake | 127 # CMake finds packages will look all packages registered in the user package registry.
|
| /Zephyr-latest/boards/silabs/dev_kits/sltb010a/doc/ |
| D | index.rst | 52 There are two variants of this board, "A" and "B". Please take a look at your PCB,
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 100 The best way to understand how, may be to look into how this is done in one of the examples
|
12345
