micro-ROS / micro-ROS/micro_ros_stm32cubemx_utils
rclc_support_init() Function doesnt work and give me an RCL_RET_ERROR back
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 275
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
Hello Microros or ROS2 Community,
Im using Ubuntu 22.04 LTS on an Raspberry Pi 4.0 (Compute Module). Im using a STM32F767ZI with the STM32CubeIDE Version 1.7 with microros stack (micro_ros_stm32cubemx_utils). I can compile and flash the MCU with docker. It still works.
The problem is, that the rclc_support_init() function doesn`t initialize rcl and doesn´t create some support data structures. Cause They give me a RCL_RET_ERROR back.
Thats the reason i cant create my Publisher.
And so, the communication between both devices doesn´t work with the Agent and the XRCE-DDS-Client on stm32.
In the github Issues I found 3 times the same problem, but they have no solution.
Issue 1: https://github.com/micro-ROS/micro_ro...
Issue 2: https://github.com/micro-ROS/micro_ro...
Issue 3: https://github.com/micro-ROS/micro_ro...
Can anyone help me with this problem? Or get anyone a solution for this problem?
Thank you for your help,
Your Microros Developer Marcel.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the STM32CubeIDE project using micro_ros_stm32cubemx_utils and trace the call to rclc_support_init(), recording the returned RCL_RET_ERROR and surrounding initialization state. Compare the setup with issues 107, 82, and 85, then reproduce the failure on the STM32F767ZI workflow. Done means rclc_support_init() succeeds and publisher creation and Agent/XRCE-DDS communication work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, docker
- Domain
- embedded-iot, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100