Searched refs:can (Results 401 – 425 of 2493) sorted by relevance
1...<<11121314151617181920>>...100
| /Zephyr-latest/boards/ezurio/bl654_usb/doc/ |
| D | bl654_usb.rst | 29 More information about the BL654 USB adapter can be found on the `BL654 USB
68 Applications for the ``bl654_usb`` board configuration can be
71 board can be used for development. Documentation can be found at the :zephyr:board:`bl654_dvk`
145 You can build and flash the example to make sure Zephyr is running correctly on
146 your board. The LED definitions can be found in
|
| /Zephyr-latest/boards/renesas/ek_ra4m2/doc/ |
| D | index.rst | 66 Detailed hardware features for the RA4M2 MCU group can be found at `RA4M2 Group User's Manual Hardw…
75 Detailed hardware features for the EK-RA4M2 MCU can be found at `EK-RA4M2 - User's Manual`_
85 Applications for the ``ek_ra4m2`` board target configuration can be
93 Program can be flashed to EK-RA4M2 via the on-board SEGGER J-Link debugger.
111 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
122 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/doc/build/flashing/ |
| D | configuration.rst | 18 configuration can reside in the following files starting with the highest priority:
30 they apply to using a ``runners`` list value, this can contain ``all`` if it applies to all
32 Groups of board targets can be specified using the ``groups`` key which has a list of board
37 matches which form a singular group. A final parameter ``run`` can be set to ``first`` which
85 Commands that are supported by flash runners can be used as normal when flashing non-sysbuild
97 Once built with an nrf5340dk connected, the following command can be used to flash the board with
|
| /Zephyr-latest/boards/st/stm32g071b_disco/doc/ |
| D | index.rst | 12 user mode when associated with the STM32CubeMonUCPD software GUI and can be used
43 More information about the board can be found at the `STM32G071B-DISCO website`_.
46 More information about STM32G071RB can be found here:
60 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
91 Applications for the ``stm32g071b_disco`` board configuration can be built and
120 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/stm32h750b_dk/doc/ |
| D | index.rst | 27 More information about the board can be found at the `STM32H750B-DK website`_.
28 More information about STM32H750 can be found here:
55 The STM32H750B System Clock can be driven by an internal or external oscillator,
82 Alternatively, OpenOCD or JLink can also be used to flash the board using
100 You can then build and flash applications in the usual way.
118 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/renesas/ek_ra6m3/doc/ |
| D | index.rst | 61 Detailed hardware features for the RA6M3 MCU group can be found at `RA6M3 Group User's Manual Hardw…
70 Detailed hardware features for the EK-RA6M3 MCU can be found at `EK-RA6M3 - User's Manual`_
80 Applications for the ``ek_ra6m3`` board target configuration can be
88 Program can be flashed to EK-RA6M3 via the on-board SEGGER J-Link debugger.
106 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
117 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/boards/renesas/ek_ra6m4/doc/ |
| D | index.rst | 66 Detailed hardware features for the RA6M4 MCU group can be found at `RA6M4 Group User's Manual Hardw…
75 Detailed hardware features for the EK-RA6M4 MCU can be found at `EK-RA6M4 - User's Manual`_
85 Applications for the ``ek_ra6m4`` board target configuration can be
93 Program can be flashed to EK-RA6M4 via the on-board SEGGER J-Link debugger.
111 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
122 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/boards/st/nucleo_g031k8/doc/ |
| D | index.rst | 21 More information about the board can be found at the `Nucleo G031K8 website`_.
53 More information about STM32G031K8 can be found in the
64 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
84 Applications for the ``nucleo_g031k8`` board configuration can be built and
94 Alternatively, OpenOCD or JLink can also be used to flash the board using
117 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_g070rb/doc/ |
| D | index.rst | 24 More information about the board can be found at the `Nucleo G070RB website`_.
57 More information about STM32G070RB can be found here:
69 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
97 Applications for the ``nucleo_g070rb`` board configuration can be built and
107 Alternatively, OpenOCD, JLink, or pyOCD can also be used to flash the board using
131 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_g071rb/doc/ |
| D | index.rst | 24 More information about the board can be found at the `Nucleo G071RB website`_.
57 More information about STM32G071RB can be found here:
71 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
99 Applications for the ``nucleo_g071rb`` board configuration can be built and
109 Alternatively, OpenOCD, JLink, or pyOCD can also be used to flash the board using
133 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | dlist.rst | 25 :c:func:`sys_dlist_peek_prev`. These can all return NULL where
29 A dlist can be modified in constant time by removing a node with
34 As for slist, each node in a dlist can be processed in a natural code
61 can be trivially detected.
63 * The head and tail of the list can be detected by comparing the
71 Effectively, a dlist of N nodes can be thought of as a "ring" of "N+1"
|
| /Zephyr-latest/samples/net/sockets/big_http_download/ |
| D | README.rst | 15 transferred. Thus, it can serve as a "load testing" application for
18 The source code for this sample application can be found at:
44 The particular file selected is 6.7MB in size, so it can show how reliably
51 Thus the application can be used to test transfers of much larger amounts
54 You can edit the source code to issue a request to any other site on
96 The same application source code can be built for a POSIX system, e.g.
|
| /Zephyr-latest/samples/net/sockets/echo_server/ |
| D | README.rst | 15 The source code for this sample application can be found at:
42 improve connection reliability, acknowledgments can be enabled with shell
84 In a terminal window you can check if communication is happen:
106 The certificate used by the sample can be found in the sample's ``src``
114 There is one useful testing scenario that can be used with Linux host.
137 You can verify TLS communication with a Linux host as well. See
|
| /Zephyr-latest/boards/sifive/hifive_unleashed/doc/ |
| D | index.rst | 15 Applications for the ``hifive_unleashed`` board configuration can be built as
39 This board has USB-JTAG interface and this can be used with OpenOCD.
|
| /Zephyr-latest/boards/sifive/hifive_unmatched/doc/ |
| D | index.rst | 15 Applications for the ``hifive_unmatched`` board configuration can be built as
39 This board has USB-JTAG interface and this can be used with OpenOCD.
|
| /Zephyr-latest/boards/brcm/bcm958401m2/doc/ |
| D | index.rst | 34 The default configuration can be found in
53 Zephyr applications running on the M7 core can also be tested by observing UART console output.
|
| /Zephyr-latest/subsys/portability/cmsis_rtos_v1/ |
| D | Kconfig | 18 int "Max stack size threads can be allocated in CMSIS RTOS application"
22 Mention max stack size threads can be allocated in CMSIS RTOS application.
|
| /Zephyr-latest/samples/drivers/i2s/output/ |
| D | README.rst | 11 audio data. Currently, no codec is used with this sample. The I2S output can
28 The code can be found in :zephyr_file:`samples/drivers/i2s/output`.
|
| /Zephyr-latest/doc/services/serialization/ |
| D | index.rst | 6 Zephyr has support for several data serialization subsystems. These can be used to encode/decode
|
| /Zephyr-latest/doc/services/sensing/ |
| D | index.rst | 28 devices can use the Zephyr :ref:`sensor` API directly.
33 sensor device driver can focus on low layer device side works, can keep
45 Sensing subsystem can help build a unified Zephyr sensing architecture for
124 Then Applications can use :c:func:`sensing_open_sensor` to
132 Applications can use :c:func:`sensing_open_sensor_by_dt` to open a sensor instance directly with
161 ``Application clients`` can use :c:func:`sensing_open_sensor` to open a sensor instance
169 ``Sensor clients`` can get it's reporters' handlers via :c:func:`sensing_sensor_get_reporters`.
224 For example :c:struct:`sensing_sensor_value_3d_q31` can be used by 3D IMU sensors like
229 :c:struct:`sensing_sensor_value_uint32` can be used by
232 and :c:struct:`sensing_sensor_value_q31` can be used by
|
| /Zephyr-latest/boards/toradex/verdin_imx8mm/doc/ |
| D | index.rst | 55 More information about the board can be found at the
82 The default configuration can be found in the defconfig file:
101 example). You can change the UART by changing the ``zephyr,console`` and
124 which can be connected to the LED of the Verdin Development Board or changed in the
138 Stack Pointer, and get the M4 out of reset. The A53 can perform these steps at the
141 The M4 can use up to 3 different RAMs. These are the memory mapping for A53 and M4:
179 ``zephyr.bin`` to the eMMC (can be the FAT or EXT4 partition). You can do it
229 The M4-Core is now started up and running. You can see the output from Zephyr
235 MIMX8MM EVK board can be debugged by connecting an external JLink
237 the application can be debugged using the usual way.
|
| /Zephyr-latest/samples/subsys/usb/midi/ |
| D | README.rst | 10 This sample demonstrates how to implement a USB MIDI device. It can run on
25 The code can be found in :zephyr_file:`samples/subsys/usb/midi`.
39 with MIDI support. For example, on Linux, you can use alsa to access the device:
47 On Mac OS you can use the system tool "Audio MIDI Setup" to view the device,
|
| /Zephyr-latest/boards/shields/x_nucleo_53l0a1/doc/ |
| D | index.rst | 15 a cover glass are provided with the board, and can be fitted onto this center
18 Two VL53L0X satellites can be connected using the two 10 pin connectors.
26 More information about the board can be found at the
32 This shield can only be used with a development board that provides a
|
| /Zephyr-latest/boards/holyiot/yj16019/doc/ |
| D | index.rst | 47 Applications for the ``holyiot_yj16019`` board configuration can be
71 and configure all the necessary software. Further information can be
101 You can build and flash the examples to make sure Zephyr is running
102 correctly on your board. The button and LED definitions can be found
|
| /Zephyr-latest/samples/boards/nordic/nrfx_prs/ |
| D | README.rst | 21 - by pressing Button 1 user can request a transfer to be performed using the
23 - by pressing Button 2 user can switch between the two peripherals
31 for the UARTE), it can be checked that what is sent by a given peripheral
46 The code can be found in :zephyr_file:`samples/boards/nordic/nrfx_prs`.
|
1...<<11121314151617181920>>...100
