Searched full:like (Results 1 – 25 of 995) sorted by relevance
12345678910>>...40
| /Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/bridge/ |
| D | brg_net_key_refresh.sh | 37 # d. Messaging is verified like in step 4b.
40 # f Messaging is verified like in step 4b.
42 # 6. Messaging is verified like in step 4b.
44 # 8. Messaging is verified like in step 4b.
46 # 10. Messaging is verified like in step 4b.
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | panasonic,reduced-arduino-header.yaml | 34 1. Power Supply header exactly, like on Arduino UNO layout.
36 2. Analog Input header, like on Arduino UNO layout, but A4 and A5 are
39 3. 8-pin header (opposite Analog Input). Digital input signals, like on
43 4. 10-pin header (opposite Power Supply). Digital input signals, like on
|
| /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:
|
| /Zephyr-latest/boards/native/native_posix/doc/ |
| D | index.rst | 21 which will set its configuration to mimic a native_posix-like configuration.
24 Just like with :ref:`native_sim<native_sim>` you can build your Zephyr application
26 and can debug and instrument it like any other Linux program.
71 Now you have a Linux executable, ``./build/zephyr/zephyr.exe``, you can use just like any
74 You can run, debug, build it with sanitizers or with coverage just like with
83 Just like :ref:`native_sim<native_sim>`, ``native_posix`` comes with two targets:
|
| /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.
51 # Like 'compatible', this key also influences the way nodes match
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
[all …]
|
| 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 …]
|
| /Zephyr-latest/dts/bindings/dma/ |
| D | st,stm32-dma.yaml | 10 V1 like stm32F4 or stm32F2 socs, they include FIFO control registers
11 or V2 like stm32L4 soc or stm322WB, some also have DMAMUX controller
12 or V2bis like stm32F1 or stm32L1, where requests are multiplexed
|
| D | silabs,ldma.yaml | 9 functions like scatter-gather.
11 It is present on silabs radio board devices like EFR32xG21
|
| /Zephyr-latest/dts/bindings/i2c/ |
| D | nordic,nrf-twim.yaml | 9 multiple I2C peripherals, like a TWIM and a TWIS. You can choose
11 and "status" to "okay", e.g. using an overlay file like this one:
38 This property must be provided when interacting with devices like
57 like the DPS310 sensor driver, to not work.
|
| D | nordic,nrf-twi.yaml | 9 I2C peripherals (like TWI or TWIM), the corresponding devicetree
13 its "status" to "okay", e.g. using an overlay file like this:
31 documents TWI support, like this:
|
| D | st,stm32-i2c-v2.yaml | 30 with a tool like STM32CubeMX or directly from I2C_TIMINGR register
37 The resulting table entries should look like <periph_clock
|
| /Zephyr-latest/subsys/mgmt/osdp/ |
| D | Kconfig.pd | 105 - 02: Like 01, plus: The PD accepts configuration of the encoding of the
108 - 03: Like 02, plus: PD supports supervised monitoring. The operating mode
110 - 04: Like 03, plus: the PD supports custom End-Of-Line settings within
131 - 02: Like 01, plus: The PD is able to accept configuration of the Output
138 - 03: Like 01, plus: The PD is able to accept timed commands to the
141 - 04: Like 02 and 03 - normal/inverted drive and timed operation.
161 - 03: like 02, plus bi-color LEDs
162 - 04: like 02, plus tri-color LEDs
|
| /Zephyr-latest/dts/bindings/pinctrl/ |
| D | nuvoton,numaker-pinctrl.yaml | 10 so you can modify it like this:
31 number N, like this example you could place in your board's DTS file:
74 it's enough to drive most components, like as LED, CAN transceiver and so on.
85 Fast slew rate could support fast speed pins, like as SPI CLK up to 50MHz.
|
| D | silabs,gecko-pinctrl.yaml | 11 so you can modify it like this:
20 /* You can put this in places like a board-pinctrl.dtsi file in
51 for some number N, like this example you could place in your board's DTS
|
| /Zephyr-latest/scripts/dts/ |
| D | gen_dts_cmake.py | 12 The generated CMake file looks like this:
32 like this:
38 which can be read in source code using C APIs like
86 # In what looks like an undocumented implementation detail, CMake
94 # without conversion to lowercase-and-underscores like we have to
134 # with a name like 'DT_PROP|<path>|<property>'.
|
| /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/dts/bindings/pwm/ |
| D | st,stm32-pwm.yaml | 28 - flags : combination of standard flags like PWM_POLARITY_NORMAL
29 or specific flags like STM32_PWM_COMPLEMENTARY. As an example,
|
| /Zephyr-latest/subsys/usb/device_next/ |
| D | usbd_desc.h | 29 * This removes all loose descriptors like string descriptors.
30 * Descriptors like configuration, or interface are not touched
|
| /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/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/samples/boards/st/ccm/ |
| D | README.rst | 17 are initialized. Like the normal data section the initial
21 should be initialized to 0. Like the normal bss section they
37 For example the olimex STM32 E407 DTS file looks like this:
50 look like this:
96 When the board is reset (without power-cycling), the output looks like this:
|
| /Zephyr-latest/.github/workflows/ |
| D | stale_issue.yml | 16 would like to have the label removed otherwise this pull request will automatically be
20 would like to have the label removed otherwise this issue will automatically be closed in
|
| /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:
|
12345678910>>...40
