Lines Matching +full:kconfig +full:- +full:ext
21 In order to enable the CAN shell, the following :ref:`Kconfig <kconfig>` options must be enabled:
23 * :kconfig:option:`CONFIG_SHELL`
24 * :kconfig:option:`CONFIG_CAN`
25 * :kconfig:option:`CONFIG_CAN_SHELL`
27 The following :ref:`Kconfig <kconfig>` options enable additional subcommands and features of the
30 * :kconfig:option:`CONFIG_CAN_FD_MODE` enables CAN FD specific subcommands (e.g. for setting the
32 * :kconfig:option:`CONFIG_CAN_RX_TIMESTAMP` enables printing of timestamps for received CAN frames.
33 * :kconfig:option:`CONFIG_CAN_STATS` enables printing of various statistics for the CAN controller
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.
38 For example, building the :zephyr:code-sample:`hello_world` sample for the :zephyr:board:`frdm_k64f…
41 .. zephyr-app-commands::
42 :zephyr-app: samples/hello_world
44 …:gen-args: -DCONFIG_SHELL=y -DCONFIG_CAN=y -DCONFIG_CAN_SHELL=y -DCONFIG_STATS=y -DCONFIG_CAN_STAT…
48 interact with the shell. The CAN shell comes with built-in help (unless
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
51 support tab-completion of their arguments.
55 also supports tab-completion. A list of all devices available can be obtained using the ``device
56 list`` shell command when :kconfig:option:`CONFIG_DEVICE_SHELL` is enabled. The examples below
67 .. code-block:: console
73 max ext filters: 15
74 capabilities: normal loopback listen-only fd
93 The statistics are only printed if :kconfig:option:`CONFIG_CAN_STATS` is enabled.
103 is the initial setting upon boot-up. The initial CAN controller mode is set to ``normal`` and the
104 initial timing is set according to the ``bitrate``, ``sample-point``, ``bitrate-data``, and
105 ``sample-point-data`` :ref:`devicetree` properties.
113 .. code-block:: console
118 If :kconfig:option:`CONFIG_CAN_FD_MODE` is enabled, the data phase bitrate can be configured using
121 .. code-block:: console
140 .. code-block:: console
146 loopback`` for setting CAN FD and loopback mode). Vendor-specific modes can be specified in
155 .. code-block:: console
163 .. code-block:: console
177 .. code-block:: console
180 …adding filter with standard (11-bit) CAN ID 0x010, CAN ID mask 0x7ff, data frames 1, RTR frames 0,…
187 .. code-block:: console
190 can0 -- 010 [8] 01 02 03 04 05 06 07 08
191 can0 B- 010 [08] 01 02 03 04 05 06 07 08
193 can0 -- 00000010 [0]
194 can0 -- 010 [1] 20
195 can0 -- 010 [8] remote transmission request
207 in error-passive state.
208 * ``-``: Unset flag.
212 * ``010``: The standard (11-bit) CAN ID of the frame in hexadecimal format, here 10h.
213 * ``00000010``: The extended (29-bit) CAN ID of the frame in hexadecimal format, here 10h.
230 If :kconfig:option:`CONFIG_CAN_RX_TIMESTAMP` is enabled, each line will be prepended with a
231 timestamp from the free-running timestamp counter in the CAN controller.
237 .. code-block:: console
250 .. code-block:: console
253 enqueuing CAN frame #2 with standard (11-bit) CAN ID 0x010, RTR 0, CAN FD 0, BRS 0, DLC 8
259 The ``can recover`` subcommand can be used for initiating manual recovery from a CAN bus-off event
262 .. code-block:: console
271 The ``recover`` subcommand is only available if :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE`