2023-07-12 03:49 AM
Hello,
I know this is a bit of an edge case but during some testing today I noticed that the low level CAN drivers that come packaged with SPC5 studio only use the DLC field to work out how many bytes are in a recieved CAN the message. This isn't strictly correct as ISO 11898-1:2003 permits a standard CAN frame to have a DLC of > 8 which should be interpreted as a message containing the maximum 8 bytes. Unfortunately this ended up causing a hard-fault for me as the driver was trying to work on 64 bytes when only 8 had arrived. I have patched this locally by also checking the EDL bit when working out the frame size and thought this is something you may want to include in future.
Many thanks,
Owen
Solved! Go to Solution.
2023-08-29 05:33 AM
Hello ,
These drivers are following the license SLA0098 http://download.spc5studio.com/updates/LICENSE.pdf
The CAN Drivers have been developed as example.
No problem to update it ;)
For yopur info , AUTOSAR MCAL (Microcontroller Abstraction Layer) CAN drivers are designed to follow the ISO 11898-1 standard.
Best Regards
Erwan
2023-08-29 05:33 AM
Hello ,
These drivers are following the license SLA0098 http://download.spc5studio.com/updates/LICENSE.pdf
The CAN Drivers have been developed as example.
No problem to update it ;)
For yopur info , AUTOSAR MCAL (Microcontroller Abstraction Layer) CAN drivers are designed to follow the ISO 11898-1 standard.
Best Regards
Erwan