micro-ROS / micro-ROS/micro_ros_stm32cubemx_utils
embeddedRTPS example with NUCLEO-F767ZI
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 275
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
Issue template
- Hardware description: NUCLEO-F767ZIT6
- RTOS: FreeRTOS
- Installation type: STM32CubeIDE, micro_ros_stm32cubemx_utils
- Version or commit hash: galactic
Steps to reproduce the issue
Follow the embeddedRTPS instructions md.
Expected behavior
Visible with either ros2 topic list or Wireshark, or respond to listener on ROS2 side.
Actual behavior
No evidence that it works, but no error on the microcontroller side when monitored with PuTTY.
Additional information
I've double checked that I followed the instructions correctly. The only step I'm unsure about is 5. LwIP -> General Settings -> IP Address Settings (Set here the board address and mask). I used the following settings:
IP: 192.168.001.086
Netmask: 255.255.255.000
Gateway: 192.168.001.001
With ifconfig I see that my own IP and netmask are 192.168.1.84 and 255.255.255.0, respectively for enp3s0. With ip r I see that my gateway is 192.168.1.1. Not sure if I'm supposed to mimic the settings like this.
I made sure to disable WiFi and export FAST-DDS for ros2 topic list and listener. I don't have the board and the computer in an isolated network, but shouldn't I at least be able to see packets from 192.168.1.86 with Wireshark?
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 with embeddedrtps.md and the supplied ping_test_f7.zip, then review the NUCLEO-F767ZI, FreeRTOS, STM32CubeIDE, and LwIP settings described in the report. Reproduce the setup and determine whether the board becomes visible through Wireshark or responds to ROS 2 discovery and topic commands; document the cause and a verified working configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100