Searched refs:like (Results 1 – 25 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | zperf.rst | 17 an error message like this is printed and the server reported statistics
37 For TCP testing, the command line would look like this:
51 For TCP the zperf command would look like this:
66 or like this if you want to test TCP:
80 or like this for TCP:
|
| D | websocket.rst | 16 network protocols like MQTT.
29 protocols like MQTT. The Zephyr MQTT client library can be configured to use
42 The Websocket transport socket is then created like this:
|
| D | net_linkaddr.rst | 15 addresses are 6 bytes long like in Ethernet but for IEEE 802.15.4 the link
|
| /Zephyr-latest/samples/net/ptp/ |
| D | README.rst | 26 embedded device like Nucleo-H743-ZI, Nucleo-H745ZI-Q, Nucleo-F767ZI or
52 Compile the ``ptp4l`` daemon and start it like this:
66 When the Zephyr image is build, you can start it like this:
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-syntax.rst | 18 like this:
26 Descriptions which span multiple lines (like this) are OK,
45 # If the node describes bus hardware, like an SPI bus controller
46 # on an SoC, use 'bus:' to say which one, like this:
49 # If the node instead appears as a device on a bus, like an external
50 # SPI memory chip, use 'on-bus:' to say what type of bus, like this.
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
149 standard properties, like :ref:`reg <dt-important-props>`, whose meaning is
185 # Describes a property like 'current-speed = <115200>;'. We pretend that
[all …]
|
| D | zephyr-user-node.rst | 38 You can get the above property values in C/C++ code like this:
70 device pointers like this:
113 gpio_dt_spec`` in your source code, then use it like this:
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/ |
| D | README.rst | 31 Build the Zephyr version of the sockets/dumb_http_server_mt application like
46 Alternatively, a tool like ``curl`` can be used:
52 Finally, you can run an HTTP profiling/load tool like Apache Bench
|
| /Zephyr-latest/cmake/modules/ |
| D | pre_dt.cmake | 15 # implementation files (like bindings, vendor prefixes, etc.) are
50 # DTS directories can come from multiple places. Some places, like a
51 # user's CMakeLists.txt can preserve symbolic links. Others, like
|
| /Zephyr-latest/subsys/disk/ |
| D | Kconfig | 8 Enable disk access over a supported media backend like FLASH or RAM
|
| /Zephyr-latest/tests/arch/arm/arm_irq_vector_table/ |
| D | irq-vector-table.ld | 7 * table (like STM32F0). The symbol defined here is overriding the one in
|
| /Zephyr-latest/tests/drivers/i2s/i2s_speed/boards/ |
| D | mimxrt1170_evk_mimxrt1176_cm7.overlay | 11 /* Default DMA channel 0 and 1 maybe used by other peripherals like UART. */
|
| D | mimxrt1170_evk_mimxrt1176_cm7_B.overlay | 11 /* Default DMA channel 0 and 1 maybe used by other peripherals like UART. */
|
| /Zephyr-latest/dts/arm/st/f1/ |
| D | stm32f103Xe.dtsi | 5 * where 'x' is replaced for specific SoCs like {R,V,Z}
|
| D | stm32f103Xd.dtsi | 5 * where 'x' is replaced for specific SoCs like {R,V,Z}
|
| D | stm32f103Xb.dtsi | 5 * where 'x' is replaced for specific SoCs like {C,R,T,V}
|
| /Zephyr-latest/samples/net/sockets/can/ |
| D | README.rst | 28 You need a CANBUS enabled board like :zephyr:board:`nucleo_l432kc` or
34 Build the socket CAN sample application like this:
|
| /Zephyr-latest/boards/native/common/extra_args/ |
| D | Kconfig | 8 Extra command line options/arguments which will be handled like if they were passed to the
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | irq-vector-table-section.ld | 10 * table (like STM32F0). The symbol defined here is overriding the one in
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | network_monitoring.rst | 104 need to terminate the network connection like this.
124 To see the Zephyr console and shell, start Zephyr instance like this:
148 like 198.0.51.2:9000 or [2001:db8:100::2]:4242
162 setup command like this for IPv6-over-IPv4 tunnel
168 and like this for IPv4-over-IPv4 tunnel
176 The current monitoring configuration can be checked like this:
189 Then we need to enable the network packet monitoring like this:
207 The capture status can be checked again like this:
220 The monitoring can be disabled like this:
227 be cleared like this:
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | host.rst | 6 In some specific configurations, like when building for non-MCU x86 targets on
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.compat | 16 like read, write and poll.
|
| /Zephyr-latest/doc/develop/west/ |
| D | troubleshooting.rst | 12 verbose mode, like this:
19 something like this:
66 #. Look for a line in the output that looks like ``Location:
77 ``scripts`` to your :envvar:`PATH` using a command like this::
103 reports of this issue on other Linux distributions, like Arch Linux, either.
130 If you see an unexpected error like this when trying to run a Zephyr extension
131 command (like :ref:`west flash <west-flashing>`, :ref:`west build
160 separately, and looks like this for mainline Zephyr:
|
| /Zephyr-latest/scripts/ |
| D | requirements-build-test.txt | 3 # things used by twister or other things like code coverage or python
|
| /Zephyr-latest/doc/contribute/style/ |
| D | kconfig.rst | 10 * Use Statements like ``select`` carefully, see
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/ |
| D | README.rst | 33 Build the Zephyr version of the sockets/echo application like this:
46 Alternatively, a tool like ``curl`` can be used:
52 Finally, you can run an HTTP profiling/load tool like Apache Bench
|
12345678910>>...21
