Searched refs:like (Results 126 – 150 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/samples/sensor/qdec/ |
| D | README.rst | 27 For example, here's how the overlay file of an STM32F401 board looks like when
|
| /Zephyr-latest/doc/build/dts/ |
| D | macros.bnf | 4 ; like CONFIG_SRAM_BASE_ADDRESS, etc. It only describes the
29 ; the dt-name in this case is something like "spi" or "i2c".
62 ; dt-name in this case is something like "vnd_device".
99 ; The node's status macro; dt-name in this case is something like "okay"
122 ; The following examples assume something like this:
161 ; The following examples assume something like this:
242 ; subvalue that deserves its own macro, like the macros for an array
246 ; looks like this:
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 55 potentially involving multiple peripheral IPs like bus and DMA controllers.
119 effect every io device can be viewed as an independent, event driven actor like
120 object, that accepts a never ending queue of I/O like requests. How the iodev
167 by calling :c:func:`rtio_sqe_rx_buf` like so:
205 RTIO is useful in cases where concurrent or batch like I/O flows are useful.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | capture.rst | 22 network traffic for a given network interface. If you would like to capture
33 The cooked mode capture works like this:
|
| D | coap.rst | 84 using MQTT-like wildcard style:
99 with resource path like '/some_resource/+/#'.
205 Sample output of ttcn3 tests looks like this.
|
| /Zephyr-latest/boards/nxp/rd_rw612_bga/doc/ |
| D | index.rst | 98 display sample can be built for this board like so:
113 for a list). The display sample can be built for this module like so:
129 display sample can be built for the module like so:
|
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | native_simulator_sb_extensions.cmake | 14 # This will allow other tools, like twister, or the bsim test scripts, as well as users to find
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.swo | 44 Use UART-like NRZ encoding. This is the most common option, but requires the SWO output
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt5xx/ |
| D | Kconfig.defconfig | 50 # enable the Flash subsystem, however we would like to
|
| /Zephyr-latest/samples/net/zperf/ |
| D | README.rst | 17 an error message like this is printed and the server reported statistics
|
| /Zephyr-latest/samples/net/mdns_responder/ |
| D | README.rst | 25 Build and run the mdns-responder sample application like this:
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 67 control an RGB LED, avoid creating an option like ``MY_PWM_DEVICE_NAME``. See
112 ``select`` might seem like a generally useful feature at first, but can cause
269 The alternative would be to have dependencies like the following, possibly
316 you like. They're a great tool for simplifying Kconfig files.
318 - An exemption are buses like I2C and SPI, and following the same thought
319 process things like MFD as well. Drivers on these buses should use
467 especially true when making moderately complex changes like these.
481 :file:`zephyr/.config` are ignored by Kconfig, like for other configuration
610 This means a construct like this will fail:
672 issues, like unused symbols and symbols that are impossible to enable. Use
[all …]
|
| D | setting.rst | 37 The symbol is shown like this in ``menuconfig``, where it can be toggled:
78 respectively. The ``FPU`` symbol from the example above could be enabled like
87 A boolean symbol can also be set to ``n`` with a comment formatted like
101 Other symbol types are assigned like this:
174 variable like this ``\${ZEPHYR_<module>_MODULE_DIR}/<path-to>/<file>``
209 This can be done like this:
|
| /Zephyr-latest/boards/udoo/udoo_neo_full/doc/ |
| D | index.rst | 148 The M4 core can use up to 5 different RAMs (some other types of memory like
205 but its purpose is to load UDOO Neo "Arduino-like" sketches, so it doesn't
213 functionality is specific for the UDOO Neo "Arduino-like" sketches, it is not
225 If the output looks like below, the mqx_upload_on_m4SoloX could not read
227 loaded application is not a UDOO Neo "Arduino-like" sketch and ignores the
|
| /Zephyr-latest/soc/intel/apollo_lake/doc/ |
| D | supported_features.txt | 41 ``up_squared.overlay``), with contents like this:
|
| /Zephyr-latest/boards/intel/common/ |
| D | net_boot.rst | 41 #. TFTP root should be looking like:
|
| /Zephyr-latest/doc/develop/west/ |
| D | index.rst | 21 Since west v0.8, you can also run west like this::
|
| /Zephyr-latest/lib/libc/newlib/ |
| D | CMakeLists.txt | 32 # define __LINUX_ERRNO_EXTENSIONS__ so we get errno defines like -ESHUTDOWN
|
| /Zephyr-latest/samples/net/ipv4_autoconf/ |
| D | README.rst | 53 Once IPv4 LL has completed probing and announcement, details are shown like this:
|
| /Zephyr-latest/samples/net/sockets/echo_service/ |
| D | README.rst | 32 Build the Zephyr version of the sockets/echo_service application like this:
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 168 node`_ that looks like the following into the board devicetree file:
204 This specifies how Arduino pin references like ``<&arduino_header 11
205 0>`` are converted to SOC gpio pin references like ``<&gpiob 4 0>``.
|
| /Zephyr-latest/boards/mxchip/az3166_iotdevkit/doc/ |
| D | index.rst | 8 include an OLED screen, headphone output, stereo microphone and abundant sensors like humidity &
|
| /Zephyr-latest/subsys/usb/usb_c/ |
| D | Kconfig | 23 like VBUS and TCPC.
|
| /Zephyr-latest/samples/basic/servo_motor/ |
| D | README.rst | 26 will need to do something like this:
|
| /Zephyr-latest/samples/sensor/grow_r502a/ |
| D | README.rst | 14 #. Shows the sensor device's configurations like baud rate, library size, address and data packet s…
|
12345678910>>...21
