Searched refs:like (Results 101 – 125 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/samples/subsys/canbus/isotp/ |
| D | README.rst | 20 Use these instructions with integrated CAN controller like in the NXP TWR-KE18F
|
| /Zephyr-latest/samples/subsys/console/getline/ |
| D | README.rst | 41 line does not include any special "end of line" characters (like LF, CR,
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 13 Some commands you can run when using west with Zephyr, like the ones used to
16 help for them shows up like this in ``west --help``:
176 multiple files, your :file:`west-commands.yml` will look something like this:
211 like this:
228 same thing in the manifest's ``self`` section, like this:
|
| D | basics.rst | 22 :file:`zephyrproject` as well as all its subfolders, looks like this:
54 -- it could be anything, like ``z``, ``my-zephyr-workspace``, etc.)
107 like :ref:`west build <west-building>`. Defining these as extensions keeps
135 You will typically run it once, like this:
|
| D | workspaces.rst | 99 (Personal Access Token) like so:
183 A workspace using this topology looks like this:
229 project itself, like this:
270 A workspace using this topology looks like this:
331 <west-workspace>` a git repository, like this example:
343 You may be able to make something like this "work" for yourself and your own
|
| /Zephyr-latest/doc/build/dts/ |
| D | design.rst | 64 source-compatible with other tools like `dtc`_ in both directions:
70 devicetree for common elements like interrupts and buses.
|
| D | api-usage.rst | 44 files to give nodes names that match the SoC datasheet, like ``i2c1``,
49 special ``/aliases`` node. This is sometimes done by applications (like
91 Non-alphanumeric characters like dash (``-``) and the at sign (``@``) in
114 /* Use something like this instead: */
197 Its properties can be accessed like this:
318 There are also hardware-specific shorthands like :c:macro:`DT_GPIO_CTLR_BY_IDX`,
354 compatible with less typing, like this:
|
| D | phandles.rst | 76 properties like ``pinctrl-0``, ``pinctrl-1`` etc. may contain multiple
111 Usually, properties with this type are written like ``phandle-array-prop`` in
149 metadata about the GPIO, like whether it is active low or high, what kind of
158 Instead, you would use a phandle-array property, like this:
291 like this:
349 in a specifier by name using devicetree APIs like these:
|
| /Zephyr-latest/doc/hardware/emulator/ |
| D | index.rst | 26 Drivers which are specific to some platform, like for example the
61 * Allow emulating external buses like I2C or SPI and peripherals connected to them.
|
| /Zephyr-latest/doc/develop/sca/ |
| D | polyspace.rst | 9 guidelines like MISRA C and CERT C, find CWEs, detect bugs and calculate
11 the absence of run-time errors like array out of bounds access, overflows,
|
| D | cpptest.rst | 32 To import and generate a report file, something like the following should work.
|
| /Zephyr-latest/subsys/net/ip/ |
| D | CMakeLists.txt | 69 # To get private includes like net_shell.h
|
| /Zephyr-latest/doc/services/ |
| D | notify.rst | 10 suited to a callback notification, and operations like enabling clocks
|
| /Zephyr-latest/samples/net/virtual/ |
| D | README.rst | 42 an Ethernet network interface. Build the sample application like this:
|
| /Zephyr-latest/samples/sensor/tmp116/ |
| D | README.rst | 56 The output should look like this:
|
| /Zephyr-latest/samples/subsys/zbus/remote_mock/ |
| D | README.rst | 70 correct port destination (in Linux is something like ``/dev/tty...`` or in Windows ``COM...``).
72 From the remote mock (Python script), you would see something like this:
|
| /Zephyr-latest/samples/subsys/zbus/uart_bridge/ |
| D | README.rst | 75 correct port destination (in Linux is something like ``/dev/tty...`` or in Windows ``COM...``).
77 From the serial decoder (Python script), you would see something like this:
|
| /Zephyr-latest/boards/shields/mikroe_wifi_bt_click/doc/ |
| D | index.rst | 40 Sometimes boards declare standard headers like Arduino R3 but don't
48 preference, or to one Espressif programming boards like ESP-Prog. Install
|
| /Zephyr-latest/cmake/modules/ |
| D | FindTargetTools.cmake | 42 # like Linux.cmake or Windows-gcc.cmake. If your target is an embedded
54 # which can be used to modify settings like compiler flags etc. for
|
| /Zephyr-latest/samples/modules/lvgl/demos/ |
| D | README.rst | 13 …The music player demo shows what kind of modern, smartphone-like user interfaces can be created on…
19 Shows how the widgets look like out of the box using the built-in material theme.
|
| /Zephyr-latest/doc/develop/languages/rust/ |
| D | index.rst | 8 that eliminates common bugs like null pointer dereferencing and data races at compile time.
40 to copy from a sample, but this will look something like:
|
| /Zephyr-latest/samples/basic/button/ |
| D | README.rst | 80 - ``PIN`` should be a pin number, like ``8`` or ``0``
86 "pin" and "flags" like so:
|
| /Zephyr-latest/doc/services/modbus/ |
| D | index.rst | 9 with different physical interfaces, like RS485 or RS232.
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | gnu_arm_embedded.rst | 52 …- Set :envvar:`GNUARMEMB_TOOLCHAIN_PATH` to the brew installation directory (something like ``/usr…
|
| /Zephyr-latest/modules/nanopb/ |
| D | Kconfig | 9 # Nanopb requires c_std_11 compiler features like _Static_assert
|
12345678910>>...21
