Searched refs:can (Results 251 – 275 of 2493) sorted by relevance
1...<<11121314151617181920>>...100
| /Zephyr-latest/boards/wch/linkw/doc/ |
| D | index.rst | 64 Applications for the ``linkw`` board target can be built and flashed
80 You can use ``minichlink`` to flash the board. Once ``minichlink`` has been set
94 This board can be debugged via OpenOCD or ``minichlink``.
106 You can build and flash the examples to make sure Zephyr is running
107 correctly on your board. The button and LED definitions can be found
|
| /Zephyr-latest/boards/mikroe/clicker_2/doc/ |
| D | mikroe_clicker_2.rst | 9 It can be powered either from a battery pack, such as a LiPo or from USB.
31 peripherals can be accessed using ``mikrobus_N_INTERFACE`` so e.g. the spi on
32 bus 2 can be found by the alias ``mikrobus_2_spi``. The counting corresponds
39 Applications for the ``mikroe_clicker_2`` board configuration can
78 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/wch/ch32v003f4p6_dev_board/doc/ |
| D | index.rst | 39 Applications for the ``ch32v003f4p6_dev_board`` board target can be built and
62 You can use ``minichlink`` to flash the board. Once ``minichlink`` has been set
76 This board can be debugged via OpenOCD or ``minichlink``.
88 You can build and flash the examples to make sure Zephyr is running
89 correctly on your board. The button and LED definition can be found
|
| /Zephyr-latest/boards/others/stm32f103_mini/doc/ |
| D | index.rst | 37 More information about STM32F103RC can be found here:
50 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
82 Applications for the ``stm32f103_mini`` board configuration can be built and
92 pattern, which can be triggered by using the BOOT0 pin.
109 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/phytec/phyboard_polis/doc/ |
| D | index.rst | 21 TPM chip further extend the range of applications that can be developed with
67 More information about the board can be found at the
98 The default configuration can be found in the defconfig file:
143 Another device can be connected via the expansion header (X8):
150 before you can use it on the M4-Core with Zephyr.
157 Zephyr LED) is configured to be the blue LED. The LED can also light up in red
164 created by NXP. You can find it here:
179 The Pinout of the phyBOARD-Polis can be found here:
195 This can be done with U-Boot or Phytec's Linux BSP via remoteproc.
200 You can read more about remoteproc in Phytec's BSP here: `Remoteproc BSP`_
[all …]
|
| /Zephyr-latest/boards/intel/socfpga/agilex_socdk/doc/ |
| D | index.rst | 43 The default configuration can be found in
59 Intel Arm Trusted Firmware (ATF) can be downloaded from github:
65 Zephyr image can be loaded in DDR memory at address 0x10000000 from
73 Zephyr applications running on the Cortex-A53 core can be tested by
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | zperf.rst | 24 zperf can be enabled in any application, a dedicated sample is also present
44 In the Zephyr console, zperf can be executed as follows:
59 config file, zperf can be started as follows:
102 iPerf output can be limited by using the -b option if Zephyr is not
|
| D | mqtt.rst | 19 library can be enabled with :kconfig:option:`CONFIG_MQTT_LIB` Kconfig option and
21 3.1.0 and 3.1.1. The Zephyr MQTT implementation can be used with either plain
46 Multiple MQTT client instances can be created in the application and managed
49 of the MQTT client and can be shared among MQTT clients:
71 The client context structure needs to be initialized and set up before it can be
94 After the configuration is set up, the MQTT client can connect to the MQTT broker.
130 The connection can be closed by calling the ``mqtt_disconnect`` function.
138 The Zephyr MQTT library can be used with TLS transport for secure communication
|
| /Zephyr-latest/samples/net/wpan_serial/ |
| D | README.rst | 17 a board. You can pick, for example, a transceiver such as a CC2520 or RF2xx
25 ModemManager is disabled, otherwise, it can interfere with serial
37 This is the standard default config. This can be used by itself for
68 Now you have a Contiki native board router. You can access its web-based
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 12 # For lists, items can also be appended using:
47 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
53 # Using the PROJECT_BRIEF tag one can provide an optional one line description
59 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
66 # With the PROJECT_ICON tag one can specify an icon that is included in the tabs
82 # option can be useful when feeding Doxygen a huge amount of source files, where
173 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
175 # part of the path. The tag can be used to show relative paths in the file list.
179 # Note that you can specify absolute paths here, but also relative paths, which
185 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
[all …]
|
| /Zephyr-latest/samples/net/lwm2m_client/ |
| D | README.rst | 22 The source code for this sample application can be found at:
44 - This overlay config can be added to enable LWM2M Bootstrap support.
47 - This overlay config can be added for OpenThread support.
50 - This overlay config can be added for DTLS support via MBEDTLS.
53 - This overlay config can be added to enable LWM2M Queue Mode support.
56 …- This overlay config can be used to stop LwM2M engine for periodically interrupting socket polls.…
78 You can now open a web browser to: http://localhost:8080 This is where you
79 can watch and manage connected LwM2M devices.
138 You can now open a web browser to: http://localhost:8888 The Demo Bootstrap
139 Server web UI will open, this is where you can configure your device for
[all …]
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 17 makes it easier to use ``west build`` and other commands with it. (You can
65 The build system looks for :file:`app.overlay` by default, but you can add
76 The build system looks for :file:`prj.conf` by default, but you can add more
93 Zephyr, then link them together into a final binary you can run on your board.
95 can use CMake directly also. Application build artifacts are always generated
205 In Zephyr, you can either use a reference workspace application or create your application by hand.
237 can now go into this directory and adapt its contents to suit your needs. Since
238 you are using an existing Zephyr workspace, you can use ``west build`` or any
244 You can also use the example-application repository as a starting point for
271 can then edit :file:`my-manifest-repo/west.yml` to your liking, changing the
[all …]
|
| /Zephyr-latest/boards/bytesatwork/bytesensi_l/doc/ |
| D | index.rst | 100 The byteSENSI-L board can be flashed with the SEGGER JLink programmer.
102 You can build and flash applications in the usual way. Here is an example for
114 Debugging your application can be done with ``west debug``.
|
| /Zephyr-latest/doc/services/modbus/ |
| D | index.rst | 14 Only one client may be present on the bus. Client can communicate with several
18 and can be found in the specification or documentation of the API below.
22 More information about Modbus and Modbus RTU can be found on the website
|
| /Zephyr-latest/samples/bluetooth/ |
| D | bluetooth.rst | 9 Many Bluetooth samples can be run on QEMU or :ref:`native_sim <native_sim>` with support for
13 Several of the bluetooth samples will build a Zephyr-based Controller that can
29 connections will fail. You can force a re-paring and new key to be created
|
| /Zephyr-latest/tests/arch/arm/arm_irq_vector_table/src/ |
| D | main.c | 8 #error project can only run on Cortex-M
|
| /Zephyr-latest/samples/bluetooth/hci_uart/ |
| D | README.rst | 30 This sample can be found under :zephyr_file:`samples/bluetooth/hci_uart` in the
37 controller and expose it to Linux's BlueZ. This can be very useful for testing
38 the Zephyr Link Layer with the BlueZ Host. The Zephyr Bluetooth LE controller can also
47 debugger interface and a CDC ACM serial port bridge. More information can be
121 The sample can be debugged using RTT since the UART is otherwise used by this
122 application. To enable debug over RTT the debug configuration file can be used.
133 The sample can be built with the support for the Bluetooth LE Direction Finding.
141 You can use following targets:
152 The sample can be configured to use a USB UART instead. See :zephyr_file:`samples/bluetooth/hci_uar…
162 keep the console logs, we can keep console on uart0 and the HCI on uart1 like
|
| /Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/src/ |
| D | main.c | 8 #error test can only run on Cortex-M MCUs
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 6 Sysbuild is a higher-level build system that can be used to combine multiple
11 For example, you can use sysbuild to build a Zephyr application together
16 additional projects as you want. The additional projects can be either Zephyr applications
55 - You can run sysbuild either with :ref:`west build
58 - You can use sysbuild to generate application images from each build system,
61 - You can configure sysbuild or any of the build systems it manages using
63 sysbuild can direct them to the right build system. In some cases, such as
66 - Sysbuild itself is also configured using Kconfig. For example, you can
87 As mentioned above, you can run sysbuild via ``west build`` or ``cmake``.
148 The environment variables, ``CMAKE_BUILD_PARALLEL_LEVEL`` and ``VERBOSE``, can be used to
[all …]
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 8 the Audio and Context Engine (ACE). These Xtensa-based ADSPs can be integrated
25 (`SOF`_) project. SOF can be built with either Zephyr or Cadence's proprietary
41 You can only flash Zephyr to the ADSP by using Zephyr's Python tool in a Linux
54 UP Xtreme users can refer to the `UP Community wiki`_ for help installing a
71 your system. You can either copy the executable to a directory in your PATH or
77 subdirectory. For a different configuration directory you can use:
123 to sign the binary yourself, you can invoke ``west sign`` directly. Read the
124 ``west`` logs to find the ``west sign`` invocation; you can copy and modify
134 ``west sign -h``. The WEST_CONFIG_LOCAL environment variable can point at a
137 - You can add or overwrite a ``$platform.toml`` file(s) in your
[all …]
|
| /Zephyr-latest/subsys/net/l2/ethernet/ |
| D | Kconfig | 32 Enable support net_mgmt Ethernet interface which can be used to
55 How many VLAN tags can be configured. If set to 0, then only
56 priority tagged VLAN frames with tag value 0 can be handled.
66 This can produce lot of output so it is disabled by default.
125 Enables Ethernet bridging where packets can be transparently
134 How many bridge interfaces are created. Each interface can bridge
143 How many Ethernet interfaces can be bridged together per each
159 This can produce lot of output so it is disabled by default.
|
| /Zephyr-latest/boards/raytac/mdbt50q_db_33/doc/ |
| D | index.rst | 25 More information about the board can be found at the `MDBT50Q-DB-33 website`_.
87 Applications for the ``raytac_mdbt50q_db_33/nrf52833`` board configuration can be
100 and configure all the necessary software. Further information can be
115 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
143 You can build and flash the examples to make sure Zephyr is running correctly on
144 your board. The button and LED definitions can be found in
150 Pins can be configured in the board pinctrl file. To see the available mappings,
153 only' can only be used in under-10KHz applications. They are not suitable for SPI, I2C,
|
| /Zephyr-latest/boards/raytac/mdbt50q_db_40/doc/ |
| D | index.rst | 25 More information about the board can be found at the `MDBT50Q-DB-40 website`_.
87 Applications for the ``raytac_mdbt50q_db_40/nrf52840`` board configuration can be
100 and configure all the necessary software. Further information can be
115 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
143 You can build and flash the examples to make sure Zephyr is running correctly on
144 your board. The button and LED definitions can be found in
150 Pins can be configured in the board pinctrl file. To see the available mappings,
153 only' can only be used in under-10KHz applications. They are not suitable for SPI, I2C,
|
| /Zephyr-latest/boards/shields/boostxl_ulpsense/doc/ |
| D | index.rst | 14 More information about the board can be found at the
20 This shield can be used with any TI LaunchPad |trade| development kit with
|
| /Zephyr-latest/drivers/gpio/ |
| D | Kconfig.it8xxx2 | 24 IT8XXX2 support 8 KSI pins and 18 KSO pins, all of them can be configured
28 KSO[17:16] corresponds to GPC5 and GPC3 pin, so they can be configured to
|
1...<<11121314151617181920>>...100
