This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Effect of eCAN.MSGCTRL.DLC mismatching the actual number of incoming Bytes

Hello,

I´m working with F28069 and my CAN-communication just works fine. But after a little trying with different values in bitfield MSGCTRL.DLC I noticed no difference: Obviously, the Mailbox always 'triggers' and stores the incoming data, regardless of the actual number of Bytes, as long as the Message-ID is correct.

So my question is: what should happen if an incoming message has the correct ID, but a wrong number of Bytes?

best regards,

Stefan