micro-ROS / micro-ROS/micro_ros_renesas_demos

Issue when adding "std_msgs/Header header" to custom message

Open
#130 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
8
Forks
8
PR merge metrics
No merged PRs in 30d

Description

## Issue template

- Hardware description: RA6M5
- RTOS: Baremetal
- Installation type:
- Version or commit hash: humble

#### Steps to reproduce the issue
After adding `std_msg/Header header` to a custom message. The Linux agent is printing the following:

![image](https://github.com/micro-ROS/micro_ros_renesas_demos/assets/23290872/0eedcd0c-1f8b-4485-b2bc-416ad17ef699)

The custom message works fine without this the 'std_msg/header header'.

#### Additional information

custom message:
![image](https://github.com/micro-ROS/micro_ros_renesas_demos/assets/23290872/3cda9239-5d12-42b4-92d3-97f824fc362e)

cmake file:
![image](https://github.com/micro-ROS/micro_ros_renesas_demos/assets/23290872/f0999007-3326-4fd6-9cec-5b49a442d736)

xml:
![image](https://github.com/micro-ROS/micro_ros_renesas_demos/assets/23290872/0c53b41c-9745-4712-937b-52e0c837a327)

Any ideas would be appreciated :)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the custom message, CMake file, and XML configuration shown in the issue, then reproduce the failure after adding the Header field on the RA6M5 bare-metal setup. Compare the Linux agent output with the working message without the field; done means the custom message builds and runs correctly with Header included.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.