Lines Matching refs:can
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
69 uart:~$ can show can@0
102 The CAN controller mode and timing can only be changed while the CAN controller is stopped, which
110 The classic CAN bitrate/CAN FD arbitration phase bitrate can be configured using the ``can bitrate``
115 uart:~$ can bitrate can@0 125000
118 If :kconfig:option:`CONFIG_CAN_FD_MODE` is enabled, the data phase bitrate can be configured using
119 the ``can dbitrate`` subcommand as shown below. The bitrate is specified in bits per second.
123 uart:~$ can dbitrate can@0 1000000
130 It is also possible to configure the raw bit timing using the ``can timing`` and ``can dtiming``
137 The CAN shell allows for setting the mode of the CAN controller using the ``can mode``
142 uart:~$ can mode can@0 loopback
145 The subcommand accepts multiple modes given on the same command line (e.g. ``can mode can@0 fd
146 loopback`` for setting CAN FD and loopback mode). Vendor-specific modes can be specified in
152 After the timing and mode has been configured as needed, the CAN controller can be started using the
153 ``can start`` subcommand as shown below. This will enable reception and transmission of CAN frames.
157 uart:~$ can start can@0
158 starting can@0
160 Prior to reconfiguring the timing or mode, the CAN controller needs to be stopped using the ``can
165 uart:~$ can stop can@0
166 stopping can@0
172 added using the ``can filter add`` subcommand as shown below. The subcommand accepts a CAN ID in
179 uart:~$ can filter add can@0 010
233 Configured CAN RX filters can be removed again using the ``can filter remove`` subcommand as shown
234 below. The filter ID is the ID returned by the ``can filter add`` subcommand (0 in the example
239 uart:~$ can filter remove can@0 0
245 CAN frames can be queued for transmission using the ``can send`` subcommand as shown below. The
252 uart:~$ can send can@0 010 1 2 3 4 5 6 7 8
259 The ``can recover`` subcommand can be used for initiating manual recovery from a CAN bus-off event
264 uart:~$ can recover can@0