| /Zephyr-Core-3.5.0/drivers/can/ |
| D | Kconfig | 1 # CAN configuration options
7 # CAN options
9 menuconfig CAN config
10 bool "Controller Area Network (CAN) drivers"
12 Enable CAN Driver Configuration
14 if CAN
16 module = CAN
17 module-str = CAN
21 int "CAN driver init priority"
24 CAN driver device initialization priority.
[all …]
|
| D | can_stm32_bxcan.c | 8 #include <zephyr/drivers/can/transceiver.h>
18 #include <zephyr/drivers/can.h>
85 CAN_TypeDef *can; /*!< CAN Registers*/ member
86 CAN_TypeDef *master_can; /*!< CAN Registers for shared filter */
93 void (*config_irq)(CAN_TypeDef *can);
144 CAN_TypeDef *can = cfg->can; in can_stm32_rx_isr_handler() local
151 while (can->RF0R & CAN_RF0R_FMP0) { in can_stm32_rx_isr_handler()
152 mbox = &can->sFIFOMailBox[0]; in can_stm32_rx_isr_handler()
173 can->RF0R |= CAN_RF0R_RFOM0; in can_stm32_rx_isr_handler()
176 if (can->RF0R & CAN_RF0R_FOVR0) { in can_stm32_rx_isr_handler()
[all …]
|
| /Zephyr-Core-3.5.0/samples/net/sockets/can/ |
| D | README.rst | 1 .. zephyr:code-sample:: socket-can
5 Send and receive raw CAN frames using BSD sockets API.
10 The socket CAN sample is a server/client application that sends and receives
11 raw CAN frames using BSD socket API.
15 * Setup function which creates a CAN socket, binds it to a CAN network
16 interface, and then installs a CAN filter to the socket so that the
17 application can receive CAN frames.
18 * Receive function which starts to listen the CAN socket and prints
19 information about the CAN frames.
20 * Send function which starts to send raw CAN frames to the bus.
[all …]
|
| D | sample.yaml | 7 - can
9 depends_on: can
12 sample.net.sockets.can.one_socket:
19 - "(.*)\\[0\\] CAN frame: IDE 0x0 RTR 0x0 ID 0x1 DLC 0x8"
21 sample.net.sockets.can.two_sockets:
28 - "(.*)\\[0\\] CAN frame: IDE 0x0 RTR 0x0 ID 0x1 DLC 0x8"
30 - "(.*)\\[1\\] CAN frame: IDE 0x0 RTR 0x0 ID 0x1 DLC 0x8"
|
| /Zephyr-Core-3.5.0/samples/drivers/can/babbling/ |
| D | README.rst | 1 .. zephyr:code-sample:: can-babbling
2 :name: Controller Area Network (CAN) babbling node
5 Simulate a babbling CAN node.
11 transmitting CAN frames with identical - often high - priority. This constant babbling blocks CAN
12 bus access for any CAN frame with lower priority as these frames will loose the bus arbitration.
14 This sample application simulates a babbling CAN node. The properties of the CAN frames sent are
16 the CAN frame is of interest.
18 Being able to simulate a babbling CAN node is useful when examining the behavior of other nodes on
19 the same CAN bus when they constantly loose bus arbitration.
21 The source code for this sample application can be found at:
[all …]
|
| D | Kconfig | 7 hex "CAN ID"
12 Babbling node CAN ID.
15 bool "Use Extended (29-bit) CAN ID"
17 Babling node sends extended (29-bit) CAN ID frames.
25 bool "Send CAN-FD format frames"
28 Babbling node sends CAN-FD format frames.
31 int "Maximum number of CAN frames to enqueue"
35 Maximum number of CAN frames to enqueue for transmission.
|
| /Zephyr-Core-3.5.0/tests/drivers/can/api/src/ |
| D | common.h | 9 #include <zephyr/drivers/can.h>
33 * @brief Standard (11-bit) CAN IDs and masks used for testing.
43 * @brief Extended (29-bit) CAN IDs and masks used for testing.
60 * @brief Standard (11-bit) CAN ID frame 1.
65 * @brief Standard (11-bit) CAN ID frame 2.
70 * @brief Extended (29-bit) CAN ID frame 1.
75 * @brief Extended (29-bit) CAN ID frame 1.
80 * @brief Standard (11-bit) CAN ID RTR frame 1.
85 * @brief Extended (29-bit) CAN ID RTR frame 1.
90 * @brief Standard (11-bit) CAN ID frame 1 with CAN-FD payload.
[all …]
|
| D | canfd.c | 8 #include <zephyr/drivers/can.h>
26 zassert_equal(dev, can_dev, "CAN device does not match"); in tx_std_callback_1()
36 zassert_equal(dev, can_dev, "CAN device does not match"); in tx_std_callback_2()
45 zassert_equal(dev, can_dev, "CAN device does not match"); in rx_std_callback_1()
56 zassert_equal(dev, can_dev, "CAN device does not match"); in rx_std_callback_2()
68 zassert_equal(dev, can_dev, "CAN device does not match"); in rx_std_callback_fd_1()
80 zassert_equal(dev, can_dev, "CAN device does not match"); in rx_std_callback_fd_2()
87 * @brief Send a CAN test frame with asserts.
93 * @param frame Pointer to the CAN frame to send.
105 * @brief Send a CAN test frame with asserts.
[all …]
|
| D | classic.c | 8 #include <zephyr/drivers/can.h>
21 * @brief Standard (11-bit) CAN ID transmit callback 1.
31 zassert_equal(dev, can_dev, "CAN device does not match"); in tx_std_callback_1()
36 * @brief Standard (11-bit) CAN ID transmit callback 2.
46 zassert_equal(dev, can_dev, "CAN device does not match"); in tx_std_callback_2()
51 * @brief Extended (29-bit) CAN ID transmit callback 1.
61 zassert_equal(dev, can_dev, "CAN device does not match"); in tx_ext_callback_1()
66 * @brief Extended (29-bit) CAN ID transmit callback 2.
76 zassert_equal(dev, can_dev, "CAN device does not match"); in tx_ext_callback_2()
81 * @brief Standard (11-bit) CAN ID receive callback 1.
[all …]
|
| D | common.c | 8 #include <zephyr/drivers/can.h>
24 * @brief Standard (11-bit) CAN ID frame 1.
34 * @brief Standard (11-bit) CAN ID frame 2.
44 * @brief Extended (29-bit) CAN ID frame 1.
54 * @brief Extended (29-bit) CAN ID frame 1.
64 * @brief Standard (11-bit) CAN ID RTR frame 1.
74 * @brief Extended (29-bit) CAN ID RTR frame 1.
84 * @brief Standard (11-bit) CAN ID frame 1 with CAN-FD payload.
98 * @brief Standard (11-bit) CAN ID frame 1 with CAN-FD payload.
112 * @brief Standard (11-bit) CAN ID filter 1. This filter matches
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/devicetree/ |
| D | can.h | 3 * @brief CAN devicetree macro public API header file.
20 * @defgroup devicetree-can Devicetree CAN API
26 * @brief Get the maximum transceiver bitrate for a CAN controller
28 * The bitrate will be limited to the maximum bitrate supported by the CAN
29 * controller. If no CAN transceiver is present in the devicetree, the maximum
30 * bitrate will be that of the CAN controller.
34 * transceiver0: can-phy0 {
35 * compatible = "vnd,can-transceiver";
40 * can0: can@... {
41 * compatible = "vnd,can-controller";
[all …]
|
| /Zephyr-Core-3.5.0/tests/subsys/canbus/isotp/conformance/ |
| D | testcase.yaml | 6 # | 1 | Classical CAN only | CONFIG_CAN_FD_MODE=n | nucleo_f072 |
7 # | 2 | Classical CAN only | CONFIG_CAN_FD_MODE=y | nucleo_f072 |
8 # | 3 | Classical CAN + CAN-FD | CONFIG_CAN_FD_MODE=n | native_posix |
9 # | 4 | Classical CAN + CAN-FD | CONFIG_CAN_FD_MODE=y | native_posix |
12 # CAN-FD independent of CONFIG_CAN_FD_MODE configuration.
19 - can
21 depends_on: can
26 - can
31 depends_on: can
36 - can
[all …]
|
| /Zephyr-Core-3.5.0/dts/bindings/phy/ |
| D | can-transceiver-gpio.yaml | 4 description: Simple GPIO controlled CAN transceiver
6 compatible: "can-transceiver-gpio"
8 include: can-transceiver.yaml
14 GPIO to use to enable/disable the CAN transceiver. This GPIO is driven
15 active when the CAN transceiver is enabled and inactive when the CAN
21 GPIO to use to put the CAN transceiver into standby. This GPIO is driven
22 inactive when the CAN transceiver is enabled and active when the CAN
|
| /Zephyr-Core-3.5.0/doc/hardware/peripherals/canbus/ |
| D | controller.rst | 3 CAN Controller
14 Bosch CAN Specification, Bosch CAN with Flexible Data-Rate specification and the
16 CAN is mostly known for its application in the automotive domain. However, it
19 A CAN transceiver is an external device that converts the logic level signals
20 from the CAN controller to the bus-levels. The bus lines are called
21 CAN High (CAN H) and CAN Low (CAN L).
22 The transmit wire from the controller to the transceiver is called CAN TX,
23 and the receive wire is called CAN RX.
25 differentially between CAN H and CAN L.
26 The bus can be either in the recessive (logical one) or dominant (logical zero)
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/drivers/ |
| D | can.h | 26 * @brief CAN Interface
27 * @defgroup can_interface CAN Interface
33 * @name CAN frame definitions
38 * @brief Bit mask for a standard (11-bit) CAN identifier.
42 * @brief Maximum value for a standard (11-bit) CAN identifier.
46 * @brief Bit mask for an extended (29-bit) CAN identifier.
50 * @brief Maximum value for an extended (29-bit) CAN identifier.
54 * @brief Maximum data length code for CAN 2.0A/2.0B.
58 * @brief Maximum data length code for CAN-FD.
77 * @name CAN controller mode flags
[all …]
|
| /Zephyr-Core-3.5.0/samples/drivers/can/counter/ |
| D | README.rst | 1 .. zephyr:code-sample:: can-counter
2 :name: Controller Area Network (CAN) counter
5 Send and receive CAN messages.
10 This sample demonstrates how to use the Controller Area Network (CAN) API.
24 The sample can be built and executed for boards with a SoC that have an
25 integrated CAN controller or for boards with a SoC that has been augmented
26 with a stand alone CAN controller.
28 Integrated CAN controller
34 :zephyr-app: samples/drivers/can/counter
38 Stand alone CAN controller
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/drivers/can/ |
| D | transceiver.h | 17 * @brief CAN Transceiver Driver APIs
18 * @defgroup can_transceiver CAN Transceiver
30 * @brief Callback API upon enabling CAN transceiver
36 * @brief Callback API upon disabling CAN transceiver
49 * @brief Enable CAN transceiver
51 * Enable the CAN transceiver.
53 * @note The CAN transceiver is controlled by the CAN controller driver and
71 * @brief Disable CAN transceiver
73 * Disable the CAN transceiver.
75 * @note The CAN transceiver is controlled by the CAN controller driver and
|
| /Zephyr-Core-3.5.0/drivers/can/transceiver/ |
| D | Kconfig | 1 # CAN transceiver configuration options
6 menu "CAN transceiver drivers"
9 int "CAN transceiver driver init priority"
12 CAN transceiver device driver initialization priority.
15 bool "GPIO controlled CAN transceiver"
20 Enable support for GPIO controlled CAN transceivers.
|
| /Zephyr-Core-3.5.0/dts/bindings/can/ |
| D | can-controller.yaml | 1 # Common fields for CAN controllers
28 timing parameters. Default of 1 matches the default value previously used for all in-tree CAN
31 Applications can still manually set the SJW using the CAN timing APIs.
53 Actively controlled CAN transceiver.
56 transceiver0: can-phy0 {
57 compatible = "nxp,tja1040", "can-transceiver-gpio";
71 Passive CAN transceiver. The child node must be named "can-transceiver".
77 can-transceiver {
87 The maximum bitrate supported by the CAN transceiver in bits/s.
|
| /Zephyr-Core-3.5.0/samples/modules/canopennode/ |
| D | README.rst | 9 stack can be used in Zephyr.
23 * A board with CAN bus and flash support
24 * Host PC with CAN bus support
31 The :ref:`twr_ke18f` board is equipped with an onboard CAN
33 LEDs). The sample can be built and executed for the TWR-KE18F as
47 The :ref:`frdm_k64f` board does not come with an onboard CAN
48 transceiver. In order to use the CAN bus on the FRDM-K64F board, an
49 external CAN bus transceiver must be connected to ``PTB18``
53 The sample can be built and executed for the FRDM-K64F as follows:
66 The :ref:`stm32f072b_disco_board` board does not come with an onboard CAN
[all …]
|
| /Zephyr-Core-3.5.0/tests/drivers/can/api/ |
| D | testcase.yaml | 2 drivers.can.api:
5 - can
6 depends_on: can
8 drivers.can.api.twai:
11 - can
|
| /Zephyr-Core-3.5.0/tests/drivers/can/timing/src/ |
| D | main.c | 8 #include <zephyr/drivers/can.h>
25 * @brief Defines a set of CAN timing test values
32 /** Do these values represent an invalid CAN timing? */
37 * @brief List of CAN timing values to test.
61 * @brief List of CAN timing values to test for the data phase.
73 /** Invalid CAN-FD bitrate, valid sample point. */
79 * @brief Assert that a CAN timing struct matches the specified bitrate
81 * Assert that the values of a CAN timing struct matches the specified bitrate
82 * for a given CAN controller device instance.
85 * @param timing pointer to the CAN timing struct
[all …]
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/tests/drivers/can/shell/src/ |
| D | main.c | 9 #include <zephyr/drivers/can.h>
10 #include <zephyr/drivers/can/can_fake.h>
96 err = shell_execute_cmd(sh, "can start " FAKE_CAN_NAME); in ZTEST()
106 err = shell_execute_cmd(sh, "can stop " FAKE_CAN_NAME); in ZTEST()
116 err = shell_execute_cmd(sh, "can show " FAKE_CAN_NAME); in ZTEST()
130 err = shell_execute_cmd(sh, "can bitrate " FAKE_CAN_NAME); in ZTEST()
156 can_shell_test_bitrate("can bitrate " FAKE_CAN_NAME " 125000", 125000, 875); in ZTEST()
161 can_shell_test_bitrate("can bitrate " FAKE_CAN_NAME " 125000 750", 125000, 750); in ZTEST()
171 err = shell_execute_cmd(sh, "can dbitrate " FAKE_CAN_NAME); in ZTEST()
201 can_shell_test_dbitrate("can dbitrate " FAKE_CAN_NAME " 1000000", 1000000, 750); in ZTEST()
[all …]
|
| /Zephyr-Core-3.5.0/dts/bindings/regulator/ |
| D | regulator.yaml | 142 emergency shutdown. Zero can be passed to disable protection and value '1'
143 indicates that protection should be enabled but limit setting can be
150 probably is malfunctional and damage prevention is requested. Zero can be
152 should be enabled but limit setting can be omitted.
159 Recovery actions should be initiated. Zero can be passed to disable
161 limit setting can be omitted.
167 emergency shutdown. Zero can be passed to disable protection and value '1'
168 indicates that protection should be enabled but limit setting can be
175 probably is malfunctional and damage prevention is requested Zero can be
177 should be enabled but limit setting can be omitted. Limit is given as
[all …]
|
