| /Zephyr-latest/drivers/can/ |
| D | can_stm32_bxcan.c | 66 CAN_TypeDef *can; /*!< CAN Registers*/ member
69 void (*config_irq)(CAN_TypeDef *can);
118 CAN_TypeDef *can = cfg->can; in can_stm32_rx_isr_handler() local
125 while (can->RF0R & CAN_RF0R_FMP0) { in can_stm32_rx_isr_handler()
126 mbox = &can->sFIFOMailBox[0]; in can_stm32_rx_isr_handler()
147 can->RF0R |= CAN_RF0R_RFOM0; in can_stm32_rx_isr_handler()
150 if (can->RF0R & CAN_RF0R_FOVR0) { in can_stm32_rx_isr_handler()
161 CAN_TypeDef *can = cfg->can; in can_stm32_get_state() local
166 } else if (can->ESR & CAN_ESR_BOFF) { in can_stm32_get_state()
168 } else if (can->ESR & CAN_ESR_EPVF) { in can_stm32_get_state()
[all …]
|
| D | Kconfig | 30 Default initial CAN bitrate in bits/s. This can be overridden per CAN controller using the
38 Default initial CAN data phase bitrate in bits/s. This can be overridden per CAN controller
110 the "-object can-host-socketcan" qemu command line option. The CAN interface must be
113 source "drivers/can/Kconfig.sam"
114 source "drivers/can/Kconfig.sam0"
115 source "drivers/can/Kconfig.stm32"
116 source "drivers/can/Kconfig.mcux"
117 source "drivers/can/Kconfig.mcp2515"
118 source "drivers/can/Kconfig.mcan"
119 source "drivers/can/Kconfig.rcar"
[all …]
|
| /Zephyr-latest/tests/drivers/can/host/pytest/ |
| D | test_can.py | 12 import can
13 from can import BusABC, CanProtocol
22 can.Message(arbitration_id=0x10,
27 can.Message(arbitration_id=0x20,
33 can.Message(arbitration_id=0x30,
39 can.Message(arbitration_id=0x40,
46 can.Message(arbitration_id=0x50,
59 def check_rx(tx: can.Message, rx: can.Message) -> None:
72 def skip_if_unsupported(can_dut: BusABC, can_host: BusABC, msg: can.Message) -> None:
80 def test_dut_to_host(self, can_dut: BusABC, can_host: BusABC, msg: can.Message) -> None:
[all …]
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 9 This test suite uses `python-can`_ for testing Controller Area Network (CAN) communication between a
17 * The python-can library installed on the host PC.
20 The Zephyr end of the CAN fixture can be configured as follows:
24 :kconfig:option:`CONFIG_CAN_DEFAULT_BITRATE_DATA`, but can be overridden on a board level using
29 The host end of the CAN fixture can be configured through python-can. Available configuration
30 options depend on the type of host CAN adapter used. The python-can library provides a lot of
31 flexibility for configuration as decribed in the `python-can configuration`_ page, all centered
32 around the concept of a configuration "context. The configuration context for this test suite can be
35 * By default, the python-can configuration context is not specified, causing python-can to use the
37 * A specific configuration context can be provided along with the ``can`` fixture separated by a
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | shell.rst | 13 The CAN shell provides a ``can`` command with a set of subcommands for the :ref:`shell <shell_api>`
15 interface without having to write a dedicated application. The CAN shell can also be enabled in
28 ``can`` command:
34 in the ``can show`` subcommand. This depends on :kconfig:option:`CONFIG_STATS` being enabled as
36 * :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE` enables the ``can recover`` subcommand.
49 :kconfig:option:`CONFIG_SHELL_HELP` is disabled). The built-in help messages can be printed by
50 passing ``-h`` or ``--help`` to the ``can`` command or any of its subcommands. All subcommands also
55 also supports tab-completion. A list of all devices available can be obtained using the ``device
57 all use the device name ``can@0``.
62 The properties of a given CAN controller can be inspected using the ``can show`` subcommand as shown
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_stats.rst | 14 Individual component statistics for IPv4 or IPv6 can be turned off
19 can be controlled by :kconfig:option:`CONFIG_NET_STATISTICS_PER_INTERFACE` option.
21 The :kconfig:option:`CONFIG_NET_STATISTICS_USER_API` option can be set if the
26 The :kconfig:option:`CONFIG_NET_STATISTICS_ETHERNET` option can be set to collect
29 Ethernet device driver can collect Ethernet device specific statistics.
30 These statistics can then be transferred to application for processing.
32 If the :kconfig:option:`CONFIG_NET_SHELL` option is set, then network shell can
|
| /Zephyr-latest/samples/net/sockets/can/ |
| D | README.rst | 1 .. zephyr:code-sample:: socket-can
17 application can receive CAN frames.
22 The source code for this sample application can be found at:
23 :zephyr_file:`samples/net/sockets/can`.
37 :zephyr-app: samples/net/sockets/can
46 :zephyr-app: samples/net/sockets/can
|
| /Zephyr-latest/drivers/crypto/ |
| D | Kconfig.si32 | 13 int "Maximum of sessions the Si32 driver can handle"
17 This can be used to tweak the amount of sessions the driver
18 can handle in parallel.
|
| D | Kconfig.mcux_dcp | 15 int "Maximum number of sessions NXP DCP crypto driver can handle"
20 This can be used to tweak the amount of sessions the driver
21 can handle in parallel.
|
| D | Kconfig.stm32 | 16 int "Maximum of sessions STM32 crypto driver can handle"
20 This can be used to tweak the amount of sessions the driver
21 can handle in parallel.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | l2cap.rst | 6 L2CAP layer enables connection-oriented channels which can be enable with the
16 whenever an incoming data has been received. Data received this way can be
24 For sending data the :c:func:`bt_l2cap_chan_send` API can be used noting that
28 Servers can be registered using :c:func:`bt_l2cap_server_register` API passing
34 Client channels can be initiated with use of :c:func:`bt_l2cap_chan_connect`
35 API and can be disconnected with the :c:func:`bt_l2cap_chan_disconnect` API.
36 Note that the later can also disconnect channel instances created by servers.
|
| D | gatt.rst | 10 Services can be registered using :c:func:`bt_gatt_service_register` API
13 can be used to declare a service.
15 Attributes can be declared using the :c:struct:`bt_gatt_attr` struct or using
47 callbacks can be set to NULL if the attribute permission don't allow their
58 Attribute value changes can be notified using :c:func:`bt_gatt_notify` API,
64 Client procedures can be enabled with the configuration option:
67 Discover procedures can be initiated with the use of
79 more attributes can be set, though setting multiple handles requires the option:
85 or :c:func:`bt_gatt_write_without_response_cb` APIs can be used, with the
88 Subscriptions to notification and indication can be initiated with use of
[all …]
|
| /Zephyr-latest/samples/net/sockets/http_server/ |
| D | README.rst | 12 The server supports the HTTP/1.1 protocol which can also be upgraded to HTTP/2,
32 - This overlay config can be added for IEEE 802.15.4 support.
35 - This overlay config can be added for connecting via network USB.
43 When the server is up, we can make requests to the server using either HTTP/1.1 or
90 The server sample contains several parameters that can be customized based on
96 clients that the server can handle simultaneously.
99 streams that can be established per client.
106 URL that the server can process.
112 To customize these options, we can run ``west build -t menuconfig``, which provides
119 You can use a simple Websocket client application like this to test the Websocket
[all …]
|
| /Zephyr-latest/boards/ruuvi/ruuvitag/doc/ |
| D | index.rst | 10 More information about the board can be found at the
87 * 10 = P0.04 = GPIO (can be used as a GPIO / ADC pin)
88 * 11 = P0.05 = GPIO (can be used as a GPIO / ADC pin)
90 * 13 = P0.19 = LED2 (green) / GPIO (can be used as a GPIO pin but the LED will blink)
91 * 14 = P0.17 = LED1 (red) / GPIO (can be used as a GPIO pin but the LED will blink)
92 * 15 = P0.13 = Button / GPIO (can be used as a GPIO pin)
98 * 21 = P0.18 = SWO / GPIO (can be used as a GPIO pin)
99 * 22 = P0.21 = Reset / GPIO (can be used as a GPIO pin if no need to reset the device)
101 * 24 = P0.31 = GPIO (can be used as a GPIO / ADC pin)
102 * 25 = P0.30 = GPIO (can be used as a GPIO / ADC pin)
[all …]
|
| /Zephyr-latest/dts/arm/atmel/ |
| D | same5x.dtsi | 32 can0: can@42000000 {
33 compatible = "atmel,sam0-can";
45 can1: can@42000400 {
46 compatible = "atmel,sam0-can";
|
| D | samc21.dtsi | 51 can0: can@42001c00 {
52 compatible = "atmel,sam0-can";
64 can1: can@42002000 {
65 compatible = "atmel,sam0-can";
|
| /Zephyr-latest/boards/microchip/m2gl025_miv/doc/ |
| D | index.rst | 7 The Mi-V RISC-V soft CPU can be deployed on the MGL025 board.
8 More information can be found on
17 Applications for the ``m2gl025_miv`` board configuration can be built as usual
29 You can get them as a part of SoftConsole SDK.
30 Download and installation instructions can be found on
34 With the necessary tools installed, you can connect to the board using OpenOCD.
45 the board. You can use the RISC-V GDB from a toolchain delivered with
|
| /Zephyr-latest/boards/microchip/mpfs_icicle/doc/ |
| D | index.rst | 7 The E51 RISC-V CPU can be deployed on the mpfs_icicle board.
8 More information can be found on the `Microchip website <https://www.microchip.com/en-us/product/MP…
16 Applications for the ``mpfs_icicle`` board configuration can be built as usual
34 You can get them as a part of SoftConsole SDK.
35 Download and installation instructions can be found on
39 With the necessary tools installed, you can connect to the board using OpenOCD.
50 the board. You can use the RISC-V GDB from a toolchain delivered with
|
| /Zephyr-latest/samples/drivers/can/ |
| D | index.rst | 1 .. zephyr:code-sample-category:: can
5 These samples demonstrate how to use the :ref:`can` driver API.
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | overview.rst | 14 configuration options. You can minimize system memory consumption by enabling
16 can be disabled if not needed.
19 can be enabled or disabled depending on networking needs.
21 * Developer can set the number of unicast and multicast IPv6 addresses that
23 * The IPv6 address for the device can be set either statically or
27 IPv6 prefix count can be configured at build time.
28 * The IPv6 neighbor cache can be disabled if not needed, and its size can be
39 only IPv6. IPv4 can be used in Ethernet based networks. By default
44 * The IPv4 address can also be configured manually. Static IPv4 addresses
52 The developer can send UDP datagrams (client side support) or create a
[all …]
|
| /Zephyr-latest/samples/drivers/dac/ |
| D | README.rst | 23 The sample can be built and executed for the
34 The sample can be built and executed for the
45 The sample can be built and executed for the
56 The sample can be built and executed for the
67 The sample can be built and executed for the
78 The sample can be built and executed for the
89 The sample can be built and executed for the
100 The sample can be built and executed for the :zephyr:board:`twr_ke18f` as
114 The sample can be built and executed for the :zephyr:board:`frdm_k64f` as
128 DAC. Note this is not populated by default. The sample can be built and
[all …]
|
| /Zephyr-latest/samples/modules/canopennode/ |
| D | README.rst | 9 stack can be used in Zephyr.
40 LEDs). The sample can be built and executed for the TWR-KE18F as
60 The sample can be built and executed for the FRDM-K64F as follows:
79 The sample can be built and executed for the STM32F072RB Discovery as follows:
98 The sample can be built and executed for the STM32F3 Discovery as follows:
117 The sample can be built for boards without a flash storage partition by using a different configura…
128 CANopen communication between the host PC and Zephyr can be
132 python-can backend as follows:
136 pip3 install --user canopen python-can
138 Next, configure python-can to use your CAN adapter through its
[all …]
|
| /Zephyr-latest/tests/boot/with_mcumgr/ |
| D | README.rst | 6 (more information can be found :ref:`here <integration_with_pytest>`)
11 More information about MCUmgr can be found here :ref:`mcu_mgr`.
25 Test scripts can be found in ``pytest`` directory. To list available
26 scenarios with described procedures, one can use a pytest command:
|
| /Zephyr-latest/samples/net/prometheus/ |
| D | README.rst | 12 By integrating this library into your code, you can expose internal metrics
33 When the server is up, we can make requests to the server using HTTP/1.1.
45 The server sample contains several parameters that can be customized based on
51 clients that the server can handle simultaneously.
54 streams that can be established per client.
61 URL that the server can process.
63 To customize these options, we can run ``west build -t menuconfig``, which provides
88 to the defined scrape configuration. You can verify that your server's metrics are
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | comparator.rst | 13 Comparators can typically set a trigger which triggers on output changes. This trigger can
14 either invoke a callback, or its status can be polled.
23 Embedded comparators can typically be configured at runtime. When enabled, an initial
24 configuration must be provided using the devicetree. At runtime, comparators can have their
60 The power management shell can optionally be enabled alongside the comparator shell.
|
