Searched refs:like (Results 51 – 75 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/ |
| D | .gitlint | 1 # All these sections are optional, edit this file as you like.
38 # python like regex (https://docs.python.org/2/library/re.html) that the
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | health_srv.rst | 17 alter the behavior of the node, like power outages or faulty peripherals.
36 through some physical behavior like blinking, playing a sound or vibrating.
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 007_ext-source.md | 21 Describe whether you'd like to integrate this external component in the main tree
71 Version or SHA you would like to integrate initially
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | iar_arm_toolchain.rst | 16 A Zephyr SDK is used as a source of tools like device tree compiler (DTC), QEMU, etc… Even though
18 be used for some steps like device tree preprocessing and .bin file generation.
|
| /Zephyr-latest/include/zephyr/drivers/misc/ |
| D | README | 15 layer graphic operations like widgets, shapes, fonts, text, or bitmaps
|
| /Zephyr-latest/tests/drivers/gpio/gpio_basic_api/ |
| D | README.txt | 15 will fail with an error like this:
|
| /Zephyr-latest/boards/shields/nrf7002eb/doc/ |
| D | index.rst | 10 compatible Nordic host boards, like the Thingy53, using the Nordic edge-connector.
50 edge-connector on some boards, like earlier revisions of the Thingy53 than v1.0.0.
|
| /Zephyr-latest/samples/userspace/shared_mem/ |
| D | README.rst | 11 simulating an enigma-like machine, but the implementation of the
36 are the input and output of the enigma-like machine. The second
|
| /Zephyr-latest/boards/gd/gd32vf103c_starter/doc/ |
| D | index.rst | 55 (JP1) which can be used with tools like Segger J-Link.
66 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | sockets.rst | 23 names like ``close()``, which may be part of libc or other POSIX
40 functions like ``close()`` and ``fcntl()`` (which may conflict with
47 for calls like ``recv()`` and ``send()`` to actually process (receive
55 among sockets, files, special devices (like stdin/stdout), etc. Internally,
102 array) looks like this:
139 Once configured, socket can be used just like a regular TCP socket.
157 external IP stack and expose socket-like API.
|
| /Zephyr-latest/drivers/pm_cpu_ops/ |
| D | Kconfig | 38 like 'warm' and 'cold' reset commands.
|
| /Zephyr-latest/drivers/wifi/eswifi/ |
| D | Kconfig.eswifi | 40 It can be increased to handle larger messages, like scan results.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-4.2.rst | 5 features. If you feel like something new can be useful to a user, put it
6 under "Other Enhancements" in the first paragraph, if you feel like something
76 like you need to add more details, add them in the API documentation code
|
| /Zephyr-latest/samples/net/dhcpv4_client/ |
| D | README.rst | 82 are shown like this:
174 are shown like this:
215 are shown like this:
|
| /Zephyr-latest/samples/boards/st/ccm/ |
| D | README.rst | 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/tests/bsim/bluetooth/host/misc/sample_test/ |
| D | README.rst | 17 like setting up a connection, getting the GATT handle of a characteristic, etc..
|
| /Zephyr-latest/tests/boot/with_mcumgr/ |
| D | README.rst | 23 like ``erase``) to use sysbuild.
|
| /Zephyr-latest/samples/subsys/usb/midi/ |
| D | README.rst | 18 that carries MIDI1 messages, pretty much like a standard USB-MIDI in/out adapter
51 support; like your favorite Digital Audio Workstation or synthetizer. If you
|
| /Zephyr-latest/boards/gd/gd32f350r_eval/doc/ |
| D | index.rst | 59 (J3) which can be used with tools like Segger J-Link.
70 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/boards/gd/gd32f450v_start/doc/ |
| D | index.rst | 56 (JP100) which can be used with tools like Segger J-Link.
67 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/boards/gd/gd32l233r_eval/doc/ |
| D | index.rst | 54 which can be used with tools like Segger J-Link(latest version required).
65 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/boards/gd/gd32vf103v_eval/doc/ |
| D | index.rst | 62 (JP1) which can be used with tools like Segger J-Link.
73 terminal should be something like ``/dev/ttyUSB0``. For example:
|
| /Zephyr-latest/samples/net/sockets/coap_download/ |
| D | README.rst | 25 Build the CoAP download sample application like this:
62 Build and run the coap_download sample application for native_sim like this:
|
| /Zephyr-latest/samples/basic/blinky/ |
| D | README.rst | 54 On GCC-based toolchains, the error looks like this:
63 To add support for your board, add something like this to your devicetree:
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 59 Your SoC directory should look like this:
158 In general, :file:`<soc>.dtsi` should look like this:
188 pre SoC series, like this: :file:`<VENDOR>/<SERIES>/<soc>.dtsi`.
230 A :file:`Kconfig.soc` may look like this:
275 or ``if SOC_SERIES_<SERIES_NAME>`` / ``endif``, like this:
292 will look like:
|
12345678910>>...21
