summaryrefslogtreecommitdiffstats
path: root/low-can-binding/can/can-signals.hpp
diff options
context:
space:
mode:
authorRomain Forlot <romain.forlot@iot.bzh>2018-09-28 17:12:18 +0200
committerRomain Forlot <romain.forlot@iot.bzh>2018-12-14 08:58:56 +0000
commitea35eabeadce57e4f5015797fea530c5bb219fff (patch)
tree69fbb0f4e4d5528500873d122bc35b3423d7ca96 /low-can-binding/can/can-signals.hpp
parentb049485873e1692cc9e7857e91e017f86dd91218 (diff)
CAN FD implementation
Add a flag to CAN message definitions which set the message as using FD protocol if true. Use a new generated file with the new FD flag field on the message definitions. Change BCM socket "struct" using an union to store the CAN frames either using the FD struct or the classic non FD struct. A BCM socket can only one frame type once configured. Use as much as possible the "struct canfd_frame" in the binding and only make a difference before writing or reading the socket. From a memory point of view both struct are identical and only the last member differ and could hold more data with messages of 64 bytes long. So the canfd_frame is compatible with the can_frame and can be differentiated by a flag set in the can_id member. Remove now unused code processing can_frame. Keep the diagnostic manager using the classic CAN frame. Set the maximum number of frames that a BCM socket can handle to 257. Bug-AGL: SPEC-1980 Change-Id: Ifcc041281ea6745fc25cbd384743761f4446f489 Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
Diffstat (limited to 'low-can-binding/can/can-signals.hpp')
0 files changed, 0 insertions, 0 deletions