Searched refs:above (Results 126 – 150 of 381) sorted by relevance
12345678910>>...16
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | sockets.rst | 35 Based on the namespacing requirements above, these operations are by
44 Another entailment of the design requirements above is that the Zephyr
216 The above indicates the importance of the socket priority. If multiple socket
|
| D | capture.rst | 97 The above IP addresses might change if you change the addresses in the
|
| /Zephyr-latest/boards/nordic/nrf52840dongle/doc/ |
| D | index.rst | 187 #. Reset the board into the Nordic bootloader as described above.
218 button pressed down. See above for a picture showing where SW1 is.
277 You can then sign and flash it using the steps above.
|
| /Zephyr-latest/boards/arm/mps3/doc/ |
| D | index.rst | 112 west build -b {BOARD qualifier from table above} samples/hello_world -t run
169 west build -b {BOARD qualifier from table above} samples/hello_world -t run
179 Board qualifier must include the board name as mentioned above.
|
| /Zephyr-latest/doc/build/dts/ |
| D | api-usage.rst | 139 the :ref:`example devicetree <dt-node-main-ex>` above:
155 :ref:`above example <dt-node-main-ex>`:
182 as shown above. It will expand to either 0 or 1 depending on if the property
376 Convenience macros built on top of the above APIs are also defined to help
|
| /Zephyr-latest/doc/project/ |
| D | modifying_contributions.rst | 52 Developers should try to limit the above practice to pull requests identified
|
| D | project_roles.rst | 154 * The above applies to elected TSC Project roles that may be defined
302 * We Introduce an area/subsystem hierarchy to address the above point
335 * In the above case, platform-specific PRs may be
385 most of the conditions listed above.
|
| /Zephyr-latest/boards/digilent/arty_a7/doc/ |
| D | index.rst | 68 In addition to the above, the ``arty_a7/designstart_fpga_cortex_m3`` board configuration
180 above steps. It was merely written to internal block RAM in the FPGA. It will
|
| /Zephyr-latest/doc/develop/west/ |
| D | workspaces.rst | 233 # Equivalent to the above, but with manually maintained Zephyr modules.
256 imported projects separately. In the above example, using ``import`` means
323 as shown :ref:`above <west-t2>` for the T2 topology, with the same caveats.
|
| D | basics.rst | 93 manifest file and can be located anywhere inside the workspace. In the above
173 #. Finding the topdir. In the ``west init`` example above, that
|
| /Zephyr-latest/boards/waveshare/esp32s3_touch_lcd_1_28/doc/ |
| D | index.rst | 104 It is recommended running the command above after :file:`west update`.
|
| /Zephyr-latest/samples/drivers/video/capture/ |
| D | README.rst | 73 a video software pattern generator is supported by the above build commands without
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | guide.rst | 47 As mentioned above, globally disabling data caching can have a significant
120 See note above regarding possible limitations on MPU regions. The ``nocache``
|
| /Zephyr-latest/doc/hardware/emulator/ |
| D | bus_emulators.rst | 48 Using the above framework we can test an entire application (e.g. Embedded
174 the example above, ``<&i2c1 0x20>`` will forward all read/write operations
|
| /Zephyr-latest/doc/services/binary_descriptors/ |
| D | index.rst | 60 Putting it all together, here is what the example above would look like in memory
71 the example above, a descriptor can be generated from any string or integer, with any
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_handlers.rst | 53 value 0 and an unknown error code with the value 1. The above example then adds an error code of
89 The above code creates 2 function handlers, ``test`` which supports read requests and takes 2
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 91 The above figure illustrates some states, from (a) to (d), for channels from ``C1`` to ``C5``,
201 The figure above illustrates the actions performed during the VDED execution when T1 publishes to
355 On the above code, the :c:func:`zbus_obs_attach_to_thread` will set the ``s1`` observer with
569 following code builds on the examples above and publishes to channel ``acc_chan``. The code is
611 For example, the following code builds on the examples above and forces a notification for the
630 channel or observer on the same call. The following code builds on the examples above and displays
783 The following code builds on the examples above and claims the ``acc_chan`` to set the ``user_data``
786 described above.
849 * :zephyr:code-sample:`zbus-hello-world` illustrates the code used above in action;
|
| /Zephyr-latest/samples/subsys/zbus/remote_mock/ |
| D | README.rst | 66 Note the run command above prints the value of pts port because it is running in
|
| /Zephyr-latest/samples/subsys/zbus/uart_bridge/ |
| D | README.rst | 71 Note the run command above prints the value of pts port because it is running in
|
| /Zephyr-latest/drivers/sensor/adi/adxl372/ |
| D | Kconfig | 61 Number of multiples of 3.3 ms activity timer for which above threshold
|
| /Zephyr-latest/samples/boards/nxp/s32/netc/ |
| D | README.rst | 114 The above commands must be run as priviledged user.
|
| /Zephyr-latest/doc/services/retention/ |
| D | blinfo.rst | 61 Once the above devicetree configuration is applied, MCUboot needs to be
|
| /Zephyr-latest/samples/basic/button/ |
| D | README.rst | 77 The above situation is for the common case where:
|
| /Zephyr-latest/boards/01space/esp32c3_042_oled/doc/ |
| D | index.rst | 89 It is recommended running the command above after :file:`west update`.
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 28 Hold Esc + Refresh (the arrow-in-a-circle "reload" key above "3") and
185 (*As above: note that we have introduced a hostname of "crouton" to
213 chromebook directly, but not advisable. Remember the discussion above
363 the Crouton environment installed above. Copy them:
|
12345678910>>...16
