micro-ROS / micro-ROS/micro-ROS-Agent
micro-ROS Agent on Raspberry 5 with /dev/AMA0 does not work
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 201
- Forks
- 111
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 10
Description
Hello,
I have setup a micro ROS Agent on a Raspberry PI 5 and connected to microROS client with UART. The UART on the PI is connected to Pin14/Pin15 (Rx/Tx) with /dev/AMA0. Which does not work. I get no connection to client.
If I connect a FTDI USB-UART serial adapter the USB port and connect the agent to port /dev/ttyUSB0 it does work as expected.
The UART AMA0 connection to my PC does work, which I have tested with the minicom terminal and hTerm
This is my setup
- Hardware description: Raspberry Pi 5
- RTOS: Ubuntu 24.04
- Installation type: micro-ROS Agent
- Version or commit hash: micro-ROS iron
Does anyone have an idea why it does not work with the onboard UART. Are there any special settings I need to make?
many thanks in advanced
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 by checking the Raspberry Pi 5 onboard UART configuration for /dev/AMA0 and compare it with the working FTDI setup on /dev/ttyUSB0. Review the reported Ubuntu 24.04 and micro-ROS Iron setup, then verify that the Agent can establish a connection through the onboard UART without changing the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- raspberry-pi, ubuntu
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100