Searched refs:like (Results 26 – 50 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/samples/net/tftp_client/ |
| D | README.rst | 34 Build the tftp-client sample application like this:
47 Build the tftp-client sample application for :ref:`native_sim <native_sim>` like this:
56 Download and run a TFTP server (like TFTPd), then create file1.bin (with data) and newfile.bin.
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 40 CMake prints the input and output file locations like this:
125 on user input like in a shell application. In this case you can get the
134 You can then use ``uart_dev`` with :ref:`uart_api` API functions like
139 that the node has ``status = "okay"``, like this:
162 successfully, the last thing to check is if the device is ready, like this:
203 Make note of the path to the node you want to find, like ``/flash@0``. Search
204 for the node's output in the file, which starts with something like this if the
230 like ``\${ZEPHYR_<module>_MODULE_DIR}/<path-to>/dts.overlay``
273 finds in the configuration phase, like this:
350 child device on an existing bus node, do something like this:
[all …]
|
| D | troubleshooting.rst | 37 This usually happens on a line like this:
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:
174 ``DT_DRV_COMPAT`` is not set, you can use information like driver file names as
181 :zephyr_file:`drivers/i2c/CMakeLists.txt` has a line that looks like this:
193 adding a line like this to your application's :file:`prj.conf` file and then
315 looks like this:
351 source file, ``compatible`` should look like ``"vnd,some-device"`` --
360 If you're using an API like :c:func:`DT_INST_PROP`, you must define
|
| /Zephyr-latest/samples/modules/lvgl/screen_transparency/ |
| D | README.rst | 11 screens that support transparency, like OSD overlays.
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 44 # Quoting is optional and works like in Unix shells
51 In order to support quoting, values are parsed by Python's ``shlex.split()`` like in
55 above has the same effect as appending them on command line after ``--`` like this:
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | promiscuous.rst | 29 First the promiscuous mode needs to be turned ON by the application like this:
58 Finally the promiscuous mode can be turned OFF by the application like this:
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | designware_arc_mwdt.rst | 12 A Zephyr SDK is used as a source of tools like device tree compiler (DTC), QEMU, etc...
14 objcopy might be used for some steps like device tree preprocessing and ``.bin`` file
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 002_enhancement.md | 15 **Describe the solution you'd like**
|
| D | 004_feature_request.md | 15 **Describe the solution you'd like**
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/hfc_multilink/dut/ |
| D | CMakeLists.txt | 10 # like scanning, setting up a connection, querying the peer for a given
|
| /Zephyr-latest/tests/bsim/bluetooth/host/scan/slow/ |
| D | CMakeLists.txt | 9 # like scanning, setting up a connection, querying the peer for a given
|
| /Zephyr-latest/tests/bsim/bluetooth/samples/battery_service/ |
| D | CMakeLists.txt | 15 # like scanning, setting up a connection, querying the peer for a given
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/ |
| D | CMakeLists.txt | 7 # You can name the project however you like. Having a unique name is encouraged.
11 # like scanning, setting up a connection, querying the peer for a given
|
| /Zephyr-latest/samples/subsys/fs/fs_sample/ |
| D | Kconfig | 17 showing how file system works on non-SD devices like internal
|
| /Zephyr-latest/samples/boards/st/uart/circular_dma/ |
| D | README.rst | 41 # like Aldus PageMaker including versions of Lorem Ipsum."
49 like Aldus PageMaker including versions of Lorem Ipsum.
|
| /Zephyr-latest/samples/basic/custom_dts_binding/ |
| D | README.rst | 15 This is in contrast to other embedded environments like Arduino, where e.g. the direction (input /
18 For typical use cases like LEDs or buttons, the existing :dtcompatible:`gpio-leds` or
|
| /Zephyr-latest/samples/net/cloud/tagoio_http_post/ |
| D | README.rst | 46 are many like :zephyr:board:`sam4e_xpro`, :zephyr:board:`sam_v71_xult`,
60 To enable WIFI support, you need a board with an embedded WIFI support like
61 :zephyr:board:`disco_l475_iot1` or you can add a shield like
|
| /Zephyr-latest/snippets/cdc-acm-console/ |
| D | README.rst | 28 device node with driver support. This should look roughly like this in
|
| /Zephyr-latest/boards/wch/ch32v003evt/ |
| D | ch32v003evt.dts | 27 * board to a suitable GPIO pin (like PD4) and then change
|
| /Zephyr-latest/soc/antmicro/myra/ |
| D | Kconfig.soc | 5 # the STM32G491REI6 MCU and additional components like FRAM. So for
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.xtensa | 24 need synchronization, like the timer subsystem!). In
|
| /Zephyr-latest/soc/oct/osd32mp15x/ |
| D | Kconfig.soc | 5 # the STM32MP15 MCU and additional components like EEPROM. So for
|
| /Zephyr-latest/lib/libc/picolibc/ |
| D | CMakeLists.txt | 16 # define __LINUX_ERRNO_EXTENSIONS__ so we get errno defines like -ESHUTDOWN
|
| /Zephyr-latest/subsys/shell/modules/kernel_service/ |
| D | Kconfig | 14 This shell provides access to basic kernel data like version, uptime
|
| /Zephyr-latest/samples/subsys/zbus/benchmark/ |
| D | README.rst | 30 The result would be something like:
61 An example of execution using the ``nrf52dk/nrf52832`` board would generate a file like this:
|
12345678910>>...21
