I am trying to send CAN messages with extended IDs, but they appear to be set to standard IDs even though I have enabled them as extended.
The CAN ID is 0x1CFF3225, but when receiving the message the ID is 0x255.
I have enabled extended ID in the mail box configuration block as shown below. I noticed that in the generated code (on the right) shows that the msg_id_type is FLEXCAN_MSG_ID_STD (it should be FLEXCAN_MSG_ID_EXT)...
I also enabled extended ID in the send block as shown below...
I am using Model-Based Design Toolbox for S32K1xx Series Version 4.3.0
It seems that there is a bug and extended ID option is not being set in the generated code ?
How can I fix this ?
Solved! Go to Solution.
Hello @johngreenjets ,
Indeed. the Extended ID option from FCAN_MBConfig block doesn't function as expected, the msg_id_type is always set to standard ID.
To apply the attached cumulative patch NXP_MBDToolbox_S32K1xx_4.3.1_patch_20230830.zip follow these steps:
Regards,
Paul
Can someone from NXP please respond to this post ?
I raised an NXP support ticket at the beginning of June, but got the following response...
"An apology for the inconvenience.
But everything about MBDT is resolved in the community you are using. Sometimes they take time to respond, but they do respond.
I thank you in advance for your patience."
Hello @johngreenjets ,
Indeed. the Extended ID option from FCAN_MBConfig block doesn't function as expected, the msg_id_type is always set to standard ID.
To apply the attached cumulative patch NXP_MBDToolbox_S32K1xx_4.3.1_patch_20230830.zip follow these steps:
Regards,
Paul
There appears to be a bug with this patch.
The issue is explained in the following post, for which I have found a potential work around....