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>

1 files changed, 1 insertions, 1 deletions

diff --git a/low-can-binding/can/can-encoder.hpp b/low-can-binding/can/can-encoder.hpp
index c79e2245..f8398836 100644
--- a/low-can-binding/can/can-encoder.hpp
+++ b/low-can-binding/can/can-encoder.hpp
@@ -24,7 +24,7 @@
 class encoder_t
 {
 public:
-	static const can_frame build_frame(const std::shared_ptr<can_signal_t>& signal, uint64_t value);
+	static const canfd_frame build_frame(const std::shared_ptr<can_signal_t>& signal, uint64_t value);
 	static uint64_t encode_state(const can_signal_t& signal, const std::string& value, bool* send);
 	static uint64_t encode_boolean(const can_signal_t& signal, bool value, bool* send);
 	static uint64_t encode_number(const can_signal_t& signal, float value, bool* send);