Basic FDCAN Driver Class #5
Open
Conversation
This file contains hidden or 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
-uses dedicated RX buffers (must configure in ioc file) -send/receive functionality
-Added documentation
-renamed some things -Automatically initializes filter and buffer parameters in the peripheral -Added log index support, so message IDs are only required on setup
Basic RX boolean semaphore
…red for automatic node detection
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.
Header and source file for FDCAN driver. Supports sending and receiving byte data over FDCAN. Can pre-register log types before sending and receiving.
Also includes an example main file for testing via loopback. To verify, set a breakpoint in the final if statement in the main loop.
Integration Instructions (full instructions in the working documentation)
LogInitStructs. Each element takes the size in bytes of the log, along with its starting message ID. Must make sure that messages longer than 64 bytes do not overlap- every 64 bytes takes one additional message ID.SendByLogIndexto send data as a registered log, or useSendByMsgIDto manually send a custom-length message. Use eitherReceiveFirstLogFromRXBuforReceiveLogTypeFromRXBufto read received logs.