Thanks for the suggestion, I submitted an issue on the GitHub: Issue 60
Furthermore I did some testing and found that changing FLEXCAN_MB_ID_IDEXT() to (filter_id & 0x1FFFFFFF) seems to have solved the issue in this...
Ah yes, I see what you mean. FLEXCAN_MB_ID_IDEXT() and FLEXCAN_MB_ID_IDSTD() are for separate banks of bits within the ID field. I didn't catch this the first time and it makes sense based on how it's laid out in HW....
Hello,
Recently I was working with the FlexCAN_t4 library but I encountered some behaviour that I was not expecting based on how I understand the filtering to work. I made a test script that displays the behaviour...