Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Run
uname -m on your Arm-based Linux host. You should see aarch64.After starting the demo publisher, run
docker exec ros2_test bash -lc 'source /opt/ros/humble/setup.bash && ros2 node list && ros2 topic list'. You should see /chatter, /parameter_events, and /rosout. You can expect an empty node list because the publisher runs as a hidden node.Look for
D2D mode: skipping registry registration, using presence announcements in the adapter log. Then, run .venv/bin/python client.py with the client environment settings. You should discover rpi5-d2d, and get_ros_topics should return /chatter.Use
rpi5 with ROS_CONTAINER=ros2_test and WORKSPACE_SETUP=/opt/ros/humble/setup.bash. You can validate the shared inspection RPCs without PuppyPi hardware. You can expect ros_ok: false in get_status because the robot packages are absent.Use
rpi_camera for the Raspberry Pi 5 camera example. Run ./ros2-device-connect/start_camera_ros2.sh to start the pi_ros container and /image_raw publisher, then run DEVICE_PROFILE=rpi_camera ./ros2-device-connect/start_d2d.sh. For other hardware, create or edit a profiles/<name>.env file to select the driver, container, and ROS 2 setup scripts.