Support for CAN FD transport for Zephyr 3.5.0, 3.6.0, and 3.7.0 #144
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
…CROROS_XRCE_DDS_HISTORIC if MICROROS_TRANSPORT_CAN_FD is selected
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Initial support for CAN FD transport currently for Zephyr 3.5.0 (which already reached End Of Life), 3.6.0, and 3.7.0 (latest release and latest LTS at this moment). Officially this repo is suppose to support Zephyr 3.1.0 , but I don't think it is worth it at this point, because it is very old and not supported by Zephyr anymore. However, I am open to add support for 3.1.0 and 2.7.5 (which is sill supported) if required. This was tested with Humble and Zephyr 3.5.0. I will test with Jazzy and Zephyr 3.7.0 as soon as possible.