Searched refs:like (Results 76 – 100 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 13 additional build system settings, like this:
24 you can combine a snippet-specific devicetree overlay and a ``.conf`` file like
34 In addition, snippets can also be applied to sysbuild configuration like so:
51 overlays like this:
|
| /Zephyr-latest/samples/net/gptp/ |
| D | README.rst | 29 embedded device like NXP FRDM-K64F, Nucleo-H743-ZI, Nucleo-H745ZI-Q,
74 After downloading the source code, compile it like this in Linux:
138 Compile the ``ptp4l`` daemon and start it like this:
182 When the Zephyr image is build, you can start it like this:
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.esp32 | 23 MCUs like ESP32-Cx.
|
| /Zephyr-latest/soc/nordic/nrf91/ |
| D | Kconfig.soc | 32 # the nRF9120 SoC and additional components like PMIC, FEM, and XTAL,
|
| /Zephyr-latest/subsys/emul/ |
| D | Kconfig | 16 can be used just like a real hardware device.
|
| /Zephyr-latest/boards/segger/ip_k66f/ |
| D | linker.ld | 30 * interfaces created in tests/samples - like e.g. _net_if.static.eth_test)
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | socks5.rst | 28 by calling :c:func:`setsockopt()` like this:
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | attributes.rst | 10 Common configuration parameters like channel scale, sampling frequency, adjusting
|
| /Zephyr-latest/samples/net/sockets/net_mgmt/ |
| D | README.rst | 28 Build net-mgmt socket sample application like this:
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-syntax-structure.rst | 82 like this:
93 The DTS would look something like this:
164 parts of node names after an "at" sign (``@``), like ``40003000`` in
230 The recommended format is ``"vendor,device"``, like ``"avago,apds9960"``,
231 or a sequence of these, like ``"ti,hdc", "ti,hdc1010"``. The ``vendor``
237 It is also sometimes a value like ``gpio-keys``, ``mmio-sram``, or
261 - Devices accessed via memory-mapped I/O registers (like ``i2c@40003000``):
264 - I2C devices (like ``apds9960@39`` and its siblings):
425 blocks, like this:
|
| /Zephyr-latest/boards/gd/gd32f450i_eval/doc/ |
| D | index.rst | 68 (J1) which can be used with tools like Segger J-Link.
79 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/boards/gd/gd32f450z_eval/doc/ |
| D | index.rst | 66 (J1) which can be used with tools like Segger J-Link.
77 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/boards/gd/gd32f470i_eval/doc/ |
| D | index.rst | 67 (J1) which can be used with tools like Segger J-Link.
78 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | nothread.rst | 92 drivers. Bus-accessed devices like serial memories may not be
101 drivers. Bus-accessed devices like GPIO extenders may not be supported.
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | native_sim_setup.rst | 58 by running ``net-setup.sh`` like this:
85 The native_sim board will print a string like this when it starts:
91 You can manually connect to it like this:
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.at45 | 15 property set to "atmel,at45" and other required properties like
|
| /Zephyr-latest/cmake/bintools/arcmwdt/ |
| D | target.cmake | 27 # MWDT binutils don't support required features like section renaming, so we
|
| /Zephyr-latest/samples/drivers/misc/ft800/ |
| D | README.rst | 19 * Display with `FT800 EVE`_ like `VM800C board`_
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | gnss.rst | 10 navigation, like GPS (Global Positioning System). GNSS services
|
| D | w1.rst | 35 Zephyr's 1-Wire Master API is used to interact with 1-Wire slave devices like
49 This includes ROM commands like Match ROM, or Search ROM.
|
| /Zephyr-latest/samples/net/lldp/ |
| D | README.rst | 25 as described in :ref:`networking_with_qemu` or with embedded device like
|
| /Zephyr-latest/doc/kernel/ |
| D | timeutil.rst | 12 equivalent to this counter is something like ``CLOCK_MONOTONIC`` or, in Linux,
20 local time offsets like daylight saving time.
61 Sub-second timestamps like ``struct timespec`` can also use this to produce
64 The inverse transformation is not standardized: APIs like ``mktime()`` expect
127 to time scales that legally defined by civil authorities, like local
237 over a network using a protocol like NTP or PTP, or processing NMEA messages
|
| /Zephyr-latest/doc/develop/west/ |
| D | config.rst | 14 West's configuration file syntax is INI-like; here is an example file:
77 Doing the above means that commands like ``west update`` will look for the
90 -- and thus the behavior of commands like ``west update`` -- using:
96 This can be useful if you use commands like ``git worktree`` to create your own
97 zephyr directories, and want commands like ``west build`` to use them instead
177 each prefixed with ``+`` or ``-``, like this:
|
| /Zephyr-latest/lib/os/zvfs/ |
| D | Kconfig | 23 like read, write and poll.
|
| /Zephyr-latest/samples/net/syslog_net/ |
| D | README.rst | 46 Build syslog_net sample application like this:
|
12345678910>>...21
