Request for feedback for CAN message structure

[Karel Gardas]

IIRC Pavel asked to always being on cc to get CAN related email right to 
his inbox instead of email list boxes...

On 6/20/22 18:37, Prashanth S wrote:
> Hi All,
> 
> This is a request for suggestions and feedback for the CAN message 
> structure.
> 
> *CAN message structure that represents the can messages from application 
> to driver:*
> 
> struct can_message {
> uint32_t timestamp;
> uint32_t id;                 // 32 bits to support extended id (29 bits)
> uint16_t flags;            // RTR | BRS | EXT ...
> uint8_t dlc;                 // (0 - 8) | 12 | 16 | 20 | 24 | 32 | 48 | 64
> uint8_t res;                 // reserved for alignment.
> uint8_t data[64];         // For supporting data transfer up to 64 bytes.
> };
> 
> This is the CAN messages structure created based on the suggestions in 
> the mail chain and looking through other CAN solutions (Nuttx, GRCAN, 
> LinCAN).
> 
> Regards
> Prashanth S
> 
> 
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel