Hardware message objects are allocated as follows:
1 - Single TX object
2..32 - RX objects TX priority is defined by the message object number, not by the CAN ID (chapter 16.7.3.5 of the user manual), hence we can't use more than one object because that would cause priority inversion on long transfers.
Hardware message objects are allocated as follows:
1 - Single TX object
2..32 - RX objects TX priority is defined by the message object number, not by the CAN ID (chapter 16.7.3.5 of the user manual), hence we can't use more than one object because that would cause priority inversion on long transfers.
This site uses cookies to store information on your computer.
By continuing to use our site, you consent to our cookies.
If you are not happy with the use of these cookies, please review our
Cookie Policy
to learn how they can be disabled.
By disabling cookies, some features of the site will not work.
Access Warning
You do not have the correct permissions to perform this operation.