Searched refs:can (Results 301 – 325 of 2493) sorted by relevance
1...<<11121314151617181920>>...100
| /Zephyr-latest/boards/st/nucleo_l011k4/doc/ |
| D | index.rst | 20 More information about the board can be found at the `Nucleo L011K4 website`_.
52 More information about STM32L011K4 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_l011k4`` 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_l031k6/doc/ |
| D | index.rst | 20 More information about the board can be found at the `Nucleo L031K6 website`_.
52 More information about STM32L031K6 can be found in the
63 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
83 Applications for the ``nucleo_l031k6`` board configuration can be built and
93 Alternatively, OpenOCD or JLink can also be used to flash the board using
116 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_l053r8/doc/ |
| D | index.rst | 20 More information about the board can be found at the `Nucleo L053R8 website`_.
53 More information about STM32L053R8 can be found in the
65 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
93 Applications for the ``nucleo_l053r8`` board configuration can be built and
103 Alternatively, OpenOCD or JLink can also be used to flash the board using
126 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/panasonic/panb511evb/support/ |
| D | nrf54l15_cpuflpr.JLinkScript | 2 // Base address where DMI registers can be found in the APB address space
|
| /Zephyr-latest/boards/nordic/nrf54l15dk/support/ |
| D | nrf54l_05_10_15_cpuflpr.JLinkScript | 2 // Base address where DMI registers can be found in the APB address space
|
| /Zephyr-latest/samples/modules/canopennode/boards/ |
| D | stm32h573i_dk.overlay | 7 /* do not use the NOR octoflash for nvs can storage */
|
| /Zephyr-latest/tests/arch/common/ramfunc/src/ |
| D | main.c | 10 #error test can only run on Cortex-M MCUs and RISC-V
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | i3c.rst | 7 peripheral interface bus. Devices on the bus can operate in
32 separate structures to keep track of device status. This can be done
52 :c:macro:`DEVICE_DT_INST_DEFINE` can be used, and the initialization
58 :c:func:`i3c_addr_slots_init`. These two structures can also be used
76 This function can be used if the controller does not require
111 * If there is no match, depending on policy, it can be
112 assigned a free address, or the device driver can stop
119 * This step can be skipped if there is no connected devices
142 If a target device can generate In-Band Interrupt (IBI),
148 programmed so that the controller can recognize incoming IBIs
[all …]
|
| /Zephyr-latest/boards/others/neorv32/doc/ |
| D | index.rst | 21 The ``neorv32`` board target can be used a generic definition for NEORV32
22 based boards. Customization to fit custom NEORV32 implementations can be done
32 behavior can be overridden by setting the ``clock-frequency`` property of the ``cpu0`` devicetree
51 instruction memory can be overridden by changing the ``reg`` property of the
58 byte internal data memory (DMEM). The size of the data memory can be overridden
70 standard NEORV32 bootloader. The baudrate can be changed by modifying the
78 support can be enabled by setting the ``status`` property of the ``trng``
120 JTAGs can be used by providing further arguments when flashing. Here is an
149 can be passed at build time:
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 23 You can combine settings whenever they appear under the same keys. For example,
24 you can combine a snippet-specific devicetree overlay and a ``.conf`` file like
34 In addition, snippets can also be applied to sysbuild configuration like so:
73 Additional directories can be added manually at CMake time.
89 The :file:`snippet.yml` files can be nested anywhere underneath these
95 For example, in a zephyr module named ``baz``, you can add this to your
120 The same can be achieved with west as follows:
199 You can write settings that only apply to some boards.
227 You can enclose the board name in slashes (``/``) to match the name against a
|
| /Zephyr-latest/samples/net/gptp/ |
| D | README.rst | 13 user can monitor gPTP functionality.
15 The source code for this sample application can be found at:
21 For generic host connectivity, that can be used for debugging purposes, see
52 :zephyr_file:`samples/net/vlan/vlan-setup-linux.sh` provides a script that can be
62 daemon that can be run in Linux host and which can act as a grandmaster for
126 One can enable debug prints by setting
164 After that you can start ptp4l daemon for both interfaces. Please use two
182 When the Zephyr image is build, you can start it like this:
|
| /Zephyr-latest/samples/bluetooth/hci_uart_3wire/ |
| D | README.rst | 30 This sample can be found under :zephyr_file:`samples/bluetooth/hci_uart_3wire` 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:
157 keep the console logs, we can keep console on uart0 and the HCI on uart1 like
|
| /Zephyr-latest/boards/others/promicro_nrf52840/doc/ |
| D | index.rst | 27 More information about the original board can be found at the
30 Information about clones can be found at `Clone Wiki`_.
46 * LED0 = P0.15, can be any color.
51 Applications for the ``promicro_nrf52840/nrf52840`` board target can be
85 PyOCD and openOCD can be used to flash and debug this board.
|
| /Zephyr-latest/boards/renesas/da14695_dk_usb/doc/ |
| D | index.rst | 66 The DA14695 Development Kit USB has one LED and one push button which can be used
80 Applications for the ``da14695_dk_usb`` board configuration can be
90 by using dedicated `eZFlashCLI`_ tool that takes care of writing header and can
92 on `ezFlashCLI`_ to install the tool. Once installed, flashing can be done in the
105 Application can be debugged in the usual way once DA14695 Development Kit USB
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf54l15bsim.rst | 32 of available RAM and RRAM either can be simulated using the nrf54l15bsim.
75 You can follow the instructions from the :ref:`nrf52_bsim board <nrf52bsim_build_and_run>`.
86 own interconnect master ports can, in principle, access any other peripheral or RAM area.
90 can be labeled as restricted for secure or non secure access.
93 As crypto library, Mbed TLS can be used with its SW crypto backend.
|
| /Zephyr-latest/samples/sensor/fdc2x1x/ |
| D | README.rst | 17 technique that can be applied to a variety of applications ranging from proximity
23 architecture, performance can be maintained even in presence of high-noise environments.
30 Connect supply **VDD** and **GND**. The supply voltage can be in
45 This sample outputs sensor data to the console and can be read by any serial
50 you can use as a reference for other platforms.
|
| /Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
| D | index.rst | 6 This platform can be used to run Zephyr RTOS on the widest possible range of Synopsys RISC-V proces…
40 there might be exceptions from that, especially for newly added targets. You can check supported
43 I.e. for the ``nsim_arc_v/rmx100`` board we can check :zephyr_file:`boards/snps/nsim/arc_v/nsim_arc…
45 The supported toolchains are listed in ``toolchain:`` array in ``.yaml`` file, where we can find:
47 * **zephyr** - implies RISC-V GNU toolchain from Zephyr SDK. You can find more information about
52 SDK yet. You can find more information about its usage here: :ref:`here <other_x_compilers>`.
53 * **arcmwdt** - implies proprietary ARC MWDT toolchain. You can find more information about its
58 samples can be only built with either GNU or MWDT toolchain due to some features limited to a
88 You can get more details about the building process by running build in verbose mode. It can be
117 In terminal two, connect to the GDB server using RISC-V GDB. You can find it in Zephyr SDK:
[all …]
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 11 devices which are idle or not used independently of the system state. It can be
61 when they do not. Therefore, applications can not manually suspend or resume a
62 device. An application can, however, decide when to disable or enable runtime
63 power management for a device. This can be useful, for example, if an
76 example, if a bus device is used by multiple sensors, we can keep the bus active
87 Until this feature is added, devices can manually *get* or *put* their
90 The :c:func:`pm_device_runtime_get` function can be used by a device driver to
93 :c:func:`pm_device_runtime_put` function can be used to indicate that the device
97 illustrates how a device can use this API and the expected sequence of events.
108 slow bus. For this reason the device drivers can also make use of the
[all …]
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | timers.rst | 8 is reached it can perform an application-defined action,
9 or it can simply record the expiration and wait for the application
19 Any number of timers can be defined (limited only by available RAM). Each timer
38 If no expiry function is required a ``NULL`` function can be specified.
42 If no stop function is required a ``NULL`` function can be specified.
47 A timer must be initialized before it can be used. This specifies its
68 A running timer can be stopped in mid-countdown, if desired.
75 A running timer can be restarted in mid-countdown, if desired.
80 A timer's status can be read directly at any time to determine how many times
83 The amount of time remaining before the timer expires can also be read;
[all …]
|
| /Zephyr-latest/boards/nxp/mr_canhubk3/ |
| D | mr_canhubk3.dts | 155 can_phy0: can-phy0 {
156 compatible = "nxp,tja1443", "can-transceiver-gpio";
163 can_phy1: can-phy1 {
164 compatible = "nxp,tja1443", "can-transceiver-gpio";
171 can_phy2: can-phy2 {
172 compatible = "nxp,tja1463", "can-transceiver-gpio";
179 can_phy3: can-phy3 {
180 compatible = "nxp,tja1463", "can-transceiver-gpio";
187 can_phy4: can-phy4 {
188 compatible = "nxp,tja1153", "can-transceiver-gpio";
[all …]
|
| /Zephyr-latest/boards/shields/rk043fn02h_ct/doc/ |
| D | index.rst | 10 capacitive touch panel from Rocktech. This LCD panel can work with several i.MX
13 More information about the shield can be found at the `RK043FN02H-CT product
84 This shield can only be used with a board which provides a configuration
|
| /Zephyr-latest/boards/shields/rk043fn66hs_ctg/doc/ |
| D | index.rst | 10 capacitive touch panel from Rocktech. This LCD panel can work with several i.MX
13 More information about the shield can be found at the `RK043FN66HS-CTG product
84 This shield can only be used with a board which provides a configuration
|
| /Zephyr-latest/boards/qemu/riscv32_xip/doc/ |
| D | index.rst | 11 Applications for the ``qemu_riscv32_xip`` board configuration can be built and run in
18 While this board is emulated and you can't "flash" it, you can use this
|
| /Zephyr-latest/boards/qemu/riscv64/doc/ |
| D | index.rst | 20 Applications for the ``qemu_riscv64`` board configuration can be built and run in
27 While this board is emulated and you can't "flash" it, you can use this
|
| /Zephyr-latest/boards/qemu/riscv32e/doc/ |
| D | index.rst | 11 Applications for the ``qemu_riscv32e`` board configuration can be built and run in
18 While this board is emulated and you can't "flash" it, you can use this
|
1...<<11121314151617181920>>...100
