-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
micro-ROS-Agent on ARM32v7 (Odroid XU4) #221
Comments
No we don't, the approach shall be to build the agent in the required platform |
Ok, I managed to make an image with micro-ros-agent. It doesn't work as expected. I mean, it works but once connected to my custom board (stm32f777) I get this:
On 1709577585.490859 I reset my board and then the connection is established again. In my board some object fail when I try to create them. |
Ok, I isolate the problem. whats the difference between humble and iron docker image? |
You need to have the same ROS 2 distro in all parts of your system. Humble and Iron may not be intercompatible. |
That's right, but I have used humble for the static library and humble for the agent and it doesn't work. Then changed to iron agent and it started working. |
Is there any Iron node in your ROS 2 dataspace while you are running micro-ROS Humble? |
No, I just trying to get micros-ros working right now. |
So in that case, I need a replicator to have the same error on my local setup. |
I have a custom board based on stm32f777. I'm not sure how you can replicate it. BTW USB transport define a 2048 buffer size. I have to increase to 4096 in order to get it working. I was having issue on the node creation function, after that change using USB is working just fine. |
Hi, I need to use micro-ros-agent on docker on an ARM32v7. I build a docker image with ros2 humble from source, using it as base image, do I need to just follow the steps for build micro-ros-agent? (https://micro.ros.org/docs/tutorials/core/first_application_linux/) in a new dockerfile? don't you provide such an image, right?
The text was updated successfully, but these errors were encountered: