Searched refs:can (Results 376 – 400 of 2493) sorted by relevance
1...<<11121314151617181920>>...100
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-tools.rst | 6 This page lists and describes tools that can be used to assist during Bluetooth
43 tools that can be used to debug and interact with Zephyr's Bluetooth Host and
52 recent version or to obtain all of its tools you can follow the steps below:
61 You can then find :file:`btattach`, :file:`btmgt` and :file:`btproxy` in the
64 You'll need to enable BlueZ's experimental features so you can access its
131 Once the hardware is connected and ready to use, you can then proceed to
166 Depending on which hardware you have available, you can choose between two
182 In order to see those logs, you can use the built-in ``btmon`` tool from BlueZ:
235 If UART is not available (or you still want non-binary logs), you can set
249 controller. This controller can be connected over an HCI TCP server.
[all …]
|
| /Zephyr-latest/doc/develop/west/ |
| D | workspaces.rst | 47 You can use west to fetch from private repositories. There is nothing
54 You can either enter the password manually or use any of the `credential
72 In general, you can store your credentials on disk using the "store" git
93 On GitHub, you can set up a `personal access token`_ to use in place of your
98 You can use the Git credential store to authenticate with a GitHub PAT
105 If you don't want to store any credentials on the file system, you can store
108 If you setup fetching via SSH, you can use Git URL rewrite feature. The following
126 password, you can avoid entering it manually every time using `ssh-agent`_.
139 Projects can be located anywhere inside the workspace, but they may not
201 └── west.yml # This can be partially imported with lower precedence or ignored.
[all …]
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 14 using Sphinx to create a formatted standalone website. Developers can
16 Sphinx installed) they can :ref:`build the documentation <zephyr_doc>` locally
17 to generate the documentation in HTML or PDF format. The HTML content can
21 You can read details about `reStructuredText`_
40 preferred. Extra indenting can (unintentionally) change the way content
147 can indicate the list items should be rendered in multiple columns with
198 | body row 2 | ... | ... | you can |
213 | body row 2 | ... | ... | you can |
257 columns, you can specify ``:widths: 1 2 2``. If you'd like the browser
259 can use ``:widths: auto``.
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | design.rst | 39 particular compatible are enabled. This can and should be done with devicetree
43 generated and maintained by hand. This can and should be obtained from the
57 Zephyr's binding language *semantics* can support Zephyr-specific attributes,
65 :file:`dtlib.py` can parse ``dtc`` output, and ``dtc`` can parse
|
| /Zephyr-latest/boards/nordic/nrf5340_audio_dk/doc/ |
| D | index.rst | 12 You can use this board for developing LE-Audio-compatible applications that support Auracast™,
38 More information about the board can be found at the `nRF5340 Audio DK website`_. The `nRF5340 Audi…
73 and configure all the necessary software. Further information can be
74 found in :ref:`nordic_segger_flashing`. Then you can build and flash
93 information on how to install the nRF Command Line Tools can be
|
| /Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
| D | Kconfig | 33 Some backend layers can define their own buffer, so the size can be zero to
46 Some backend layers can define their own buffer, so the size can be zero to
106 EC_HOST_CMD_IN_PROGRESS status. The saved status can be get with the
|
| /Zephyr-latest/boards/st/nucleo_wb05kz/doc/ |
| D | index.rst | 11 More information about the board can be found on the `Nucleo WB05KZ webpage`_.
24 More information about STM32WB05KZV can be found here:
68 Applications for the ``nucleo_w05kz`` board target can be built and flashed
78 Alternatively, OpenOCD can also be used to flash the board using the
113 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_wb09ke/doc/ |
| D | index.rst | 11 More information about the board can be found on the `Nucleo WB09KE webpage`_.
24 More information about STM32WB09KEV can be found here:
68 Applications for the ``nucleo_w09ke`` board target can be built and flashed
78 Alternatively, OpenOCD can also be used to flash the board using the
113 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_wb07cc/doc/ |
| D | index.rst | 11 More information about the board can be found on the `Nucleo WB07CC webpage`_.
24 More information about STM32WB07CCV can be found here:
68 Applications for the ``nucleo_wb07cc`` board target can be built and flashed
78 Alternatively, OpenOCD can also be used to flash the board using the
113 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/samples/net/cloud/tagoio_http_post/ |
| D | README.rst | 12 values to simulate a real device. This can be used to speed-up development
15 The source code for this sample application can be found at:
45 You can use this application on a supported board with ethernet port. There
61 :zephyr:board:`disco_l475_iot1` or you can add a shield like
99 You can experiment the TagoIO mobile application on your cellphone or tablet.
|
| /Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/ |
| D | README.rst | 15 necessarily require changes to the firmware. As such, one firmware image can be
28 Alternative configurations can only be applied if the device driver using the
52 You can build this application for the nRF52840 DK as follows:
60 The sample can also support other nRF based boards if you provide a Devicetree
70 default configuration to a virtual COM port (as in the nRF52840 DK), you can
|
| /Zephyr-latest/boards/u-blox/ubx_evkninab3/doc/ |
| D | index.rst | 36 can be found at the `u-blox website`_.
212 Applications for the ``ubx_evkninab3/nrf52840`` board configuration can be
221 and configure all the necessary software. Further information can be
235 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
262 You can build and flash the examples to make sure Zephyr is running correctly on
263 your board. The button and LED definitions can be found in
269 The following approach can be used when an application needs to use
315 Pins can be configured in the board pinctrl file. To see the available mappings,
318 can only be used in under-10KHz applications. They are not suitable for 115200 speed of UART.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | http_server.rst | 20 background thread. The application can control the server activity with
34 but the content within the filesystem can be changed dynamically. This means that
35 the files can be created, modified or deleted by some other code outside the HTTP
112 Alternatively, an HTTPS service can be defined with
130 The ``_res_fallback`` parameter can be used when defining an HTTP/HTTPS service to
132 URL. This can be used for example to serve an index page for all unknown paths
172 Once HTTP(s) service is defined, resources can be registered for it with
175 Application can enable resource wildcard support by enabling
197 example shows how gzip compressed webpage can be defined as a static resource
220 example, a gzip compressed webpage can be generated during build, by adding the
[all …]
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | workqueue.rst | 16 Any number of workqueues can be defined (limited only by available RAM). Each
31 A workqueue must be initialized before it can be used. This sets its queue to
63 Any number of **work items** can be defined. Each work item is referenced
71 A work item must be initialized before it can be used. This records the work
90 A work item can be in multiple states; for example it can be:
101 A handler function can use any kernel API available to threads. However,
106 The single argument that is passed to a handler function can be ignored if it
108 the work it is to perform, the work item can be embedded in a larger data
109 structure. The handler function can then use the argument value to compute the
137 only after a specified period of time, rather than immediately. This can be
[all …]
|
| D | index.rst | 19 Any number of threads can be defined by an application (limited only by
26 The **size** of the stack area can be tailored to conform to the actual needs
34 Up to 3 **argument values** can be passed to this function.
46 * An **execution mode**, which can either be supervisor or user mode.
62 A thread must be created before it can be used. The kernel initializes
67 to start thread execution immediately. Alternatively, the kernel can be
75 re-spawned before it can be used.
89 This can be accomplished with the :c:func:`k_thread_join` API. This
95 be made of the thread struct. The memory of such a struct can then be
111 A thread can also be aborted by another thread (or by itself)
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | cap.rst | 10 aid. The Acceptor can initialize a Coordinated Set Identification Service instance, if it is in
16 When the Bluetooth stack has been initialized (:code:`bt init`), the Acceptor can be registered by
41 This command can modify the currently used SIRK. To get the new RSI to advertise on air,
54 This command can get the currently used SIRK.
66 The Initiator will typically be a resource-rich device, such as a phone or PC. The Initiator can
67 discover CAP Acceptors's CAS and optional CSIS services. The CSIS service can be read to provide
68 information about other CAP Acceptors in the same Coordinated Set. The Initiator can execute
75 When the Bluetooth stack has been initialized (:code:`bt init`), the Initiator can discover CAS and
172 :code:`cap_initiator unicast_start` command can be used to put one or more streams into the
182 To stop all the streams that has been started, the :code:`cap_initiator unicast_stop` command can be
[all …]
|
| /Zephyr-latest/boards/microchip/mec172xmodular_assy6930/doc/ |
| D | mec172xmodular_assy6930.rst | 6 Microchip MEC172X series microcontrollers. This board can work standalone
129 Windows version can be found at the `SF100 Product page`_.
131 Linux version source code can be found at `SF100 Linux GitHub`_.
158 SPI flash can be found in the same folder. If needed, a custom SPI image
159 configuration file can be specified to override the default one.
177 For programming you can use Dediprog SF100 or a similar tool for flashing SPI chips.
208 can find the image generation tool. This binary image can be used
253 #. If you can't program the board using Dediprog, disconnect and reconnect cable connected to
256 #. If Dediprog can't detect the onboard flash, press the board's ``S1`` Reset button and try again.
|
| /Zephyr-latest/boards/st/nucleo_h503rb/doc/ |
| D | index.rst | 38 More information about the board can be found at the `NUCLEO_H503RB website`_.
110 More information about STM32H533RE can be found here:
154 You can do it by removing ``SB38`` jumper on the back side of the board.
155 VBAT can be provided via the left ST Morpho connector's pin 33.
163 Applications for the ``nucleo_h503rb`` board can be built and
171 You can check `OpenOCD official Github mirror`_.
174 Once it is done, you can set the OPENOCD and OPENOCD_DEFAULT_PATH variables in
191 Alternatively, OpencOCD or pyOCD can also be used to flash the board using
200 which can be done by executing the following commands:
236 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_f070rb/doc/ |
| D | index.rst | 20 More information about the board can be found at the `Nucleo F070RB website`_.
53 More information about STM32F070RB can be found in
65 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
95 Applications for the ``nucleo_f070rb`` board configuration can be built and
105 Alternatively, OpenOCD or JLink can also be used to flash the board using
128 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_f072rb/doc/ |
| D | index.rst | 20 More information about the board can be found at the `Nucleo F072RB website`_.
52 More information about STM32F072RB can be found in
64 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
94 Applications for the ``nucleo_f072rb`` board configuration can be built and
104 Alternatively, OpenOCD or JLink can also be used to flash the board using
127 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_f103rb/doc/ |
| D | index.rst | 20 More information about the board can be found at the `Nucleo F103RB website`_.
53 More information about STM32F103RB can be found here:
66 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
96 Applications for the ``nucleo_f103rb`` board configuration can be built and
106 Alternatively, OpenOCD or JLink can also be used to flash the board using
129 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_f334r8/doc/ |
| D | index.rst | 21 More information about the board can be found at the `Nucleo F334R8 website`_.
54 More information about STM32F334R8 can be found in the
66 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
96 Applications for the ``nucleo_f334r8`` board configuration can be built and
106 Alternatively, OpenOCD, JLink, or pyOCD can also be used to flash the board using
132 You can debug an application in the usual way. Here is an example for
|
| /Zephyr-latest/boards/st/nucleo_f091rc/doc/ |
| D | index.rst | 20 More information about the board can be found at the `Nucleo F091RC website`_.
53 More information about STM32F091RC can be found in the
65 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
98 Applications for the ``nucleo_f091rc`` board configuration can be built and
108 Alternatively, OpenOCD or JLink 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/renesas/ek_ra4e2/doc/ |
| D | index.rst | 65 Detailed hardware features for the RA4E2 MCU group can be found at `RA4E2 Group User's Manual Hardw…
74 Detailed hardware features for the EK-RA4E2 MCU can be found at `EK-RA4E2 - User's Manual`_
84 Applications for the ``ek_ra4e2`` board target configuration can be
92 Program can be flashed to EK-RA4E2 via the on-board SEGGER J-Link debugger.
110 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
121 **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_ra4m3/doc/ |
| D | index.rst | 64 Detailed hardware features for the RA4M3 MCU group can be found at `RA4M3 Group User's Manual Hardw…
73 Detailed hardware features for the EK-RA4M3 MCU can be found at `EK-RA4M3 - User's Manual`_
83 Applications for the ``ek_ra4m3`` board target configuration can be
91 Program can be flashed to EK-RA4M3 via the on-board SEGGER J-Link debugger.
109 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
120 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
1...<<11121314151617181920>>...100
