canio: Add support for i.MX 10xx series of chips #9982
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This code clears the "frame available" flag, which allows the CPU to read and serve the next entry of the Rx FIFO. Without that, the CPU would never advance in the Rx FIFO and will serve the oldest mailbox over and over, until the Rx FIFO overflows.
For instance, i.MX RT1011 and 1015 don't have CAN interfaces
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #8151
First of all, I'd like to thank @qutefox for the initial work!
What I've done is:
STATICtostatic)[3,2,1,0,7,6,5,4])Notes
The original author was working with Sparkfun's Teensy micromod, where I have a Teensky 4.1. I suppose that it's safe to enable canio for all i.MX-based boards, but didn't want to do so without proper testing. (Edit: not all boards, I discovered thanks to CI that 1010/1011/1015 don't have a CAN interface).
The link https://mcuxpresso.nxp.com/en/select_config_tools_data is dead, so I was unable to download the required config tools data, and thus I wasn't able to check the generated
periph.c.