CONFIG_ISOTP_REQUIRE_RX_PADDING

Require padding for received messages

Type: bool

Help

If enabled, SFs and the last CF must always have a DLC of 8 bytes
(for classic CAN) and unused bytes must be padded by the sending
device. This setting allows to be compliant to AUTOSAR Specification
of CAN Transport Layer.

By default, received CAN frames with or without padding are accepted.

Direct dependencies

ISOTP

(Includes any dependencies from ifs and menus.)

Defaults

No defaults. Implicitly defaults to n.

Kconfig definition

At <Zephyr>/subsys/canbus/isotp/Kconfig:51

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:44 → <Zephyr>/subsys/Kconfig:11 → <Zephyr>/subsys/canbus/Kconfig:9

Menu path: (Top) → Sub Systems and OS Services → Controller Area Network (CAN) bus subsystem → ISO-TP Transport [EXPERIMENTAL]

config ISOTP_REQUIRE_RX_PADDING
    bool "Require padding for received messages"
    depends on ISOTP
    help
      If enabled, SFs and the last CF must always have a DLC of 8 bytes
      (for classic CAN) and unused bytes must be padded by the sending
      device. This setting allows to be compliant to AUTOSAR Specification
      of CAN Transport Layer.

      By default, received CAN frames with or without padding are accepted.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)