micro-ROS / micro-ROS/micro_ros_zephyr_module
Zephyr Version / PR for CAN-FD transport
- Dominant language
- C
- Stars
- 92
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
I have written an implementation for CAN-FD transport for Zephyr, since the Agent already supports it.
And it is working very well. Significantly better than USB-CDC and UART for what I have personally tested. I would be happy to submit a PR for it. However, I wrote using Zephyr 3.5, and this module is officially only supported for 2.7.5 and 3.1. The CAN api changed slightly on 3.3, only the frame and filter structs , I think, thus my implementation won't work right away. I don't have problems modifying in to work with 3.1. However, I would like to know from the maintainers, what is the roadmap with respect to Zephyr versions and microROS distros , because 3.1 is quite old now, and EOL. Will rolling be updated to the latest Zephyr version (3.6 at this moment ) ?. That way , I will just submit my current implementation and we can backport it to Humble and Iron. Otherwise, I will submit the PR for 3.1. I would just like to get some feedback about what would the maintainers prefer.
Contributor guide
Research direction
Start by reviewing the existing Zephyr transport support and the CAN-FD implementation referenced in the issue, then confirm which Zephyr versions and micro-ROS distros are supported. A contribution would be complete when maintainers choose the target version and the implementation is adapted for that supported API, with validation against the relevant transport behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100