micro-ROS / micro-ROS/micro_ros_renesas2estudio_component

Issues with MicroROS demo on Renesas JP177 + Turtlebot Demo

Open
#87 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
10
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Hi,
I am facing some issues with the turtlebot demo using Renesas JP177 board and Turtlebot demo's.
I am following the provided PDF documentation to build turtlebot3 using micro ros agent with JP177. I am constantly getting the following error. I tried on both windows and Ubuntu with FSP 3.3, 4.4 and 4.5 versions.

The following are the issues and errors i get. The issues are also mentione in detail on the Reneasa Engineering Community Issue : [LINK](https://community.renesas.com/mcu-mpu/ra/f/forum/31473/jp177-robotics-kit-turtlebot-microros-demo-s-not-workingl)

![Screenshot 2023-08-03 230818 png-640x480](https://github.com/micro-ROS/micro_ros_renesas2estudio_component/assets/111562774/5bccda21-fab9-4aaf-81f4-ff07e344c8fd)

![Screenshot 2023-08-03 122058 png-640x480](https://github.com/micro-ROS/micro_ros_renesas2estudio_component/assets/111562774/a4722c0b-bd6f-4dfd-bd60-f7233557b230)

![Screenshot from 2023-08-03 07-43-35 png-640x480](https://github.com/micro-ROS/micro_ros_renesas2estudio_component/assets/111562774/e872bd4b-2567-448b-a07f-d9b5a760beaa)
![Screenshot from 2023-08-02 00-18-45 png-1182x388](https://github.com/micro-ROS/micro_ros_renesas2estudio_component/assets/111562774/7c053703-87f2-4e03-b4f5-7845cb2f9699)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the provided PDF documentation and reproduce the TurtleBot3 micro-ROS agent setup on the Renesas JP177 board. Compare the reported screenshots and errors across Windows, Ubuntu, and the listed FSP versions, then use the linked Renesas Engineering Community issue for context. Done means identifying a reproducible cause and documenting or resolving it.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.