Application stuck on "Waiting for device"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, docker-compose
- Domain
- devops, embedded-iot
Research direction
Start by reproducing the issue with docker-compose up -d on the stated Ubuntu VM and inspect the application output while the board is connected. Verify whether the device is recognized and whether the expected ROS 2 topics and LED subscriptions become available; the issue provides no file or test entry point.
Written by the indexing model from the issue text.
Description
Issue template
- Hardware description: STM32L4 IoT Disovery Kit
- RTOS: Zephyr 10.2.0
- Installation type: Installed through https://github.com/micro-ROS/micro-ROS_sensors_demo
- Version or commit hash: 7fd84a2664fbfcc8aaccd4c483b3e87114272673
Steps to reproduce the issue
Run the application on an Ubuntu 22.04.3 VM on a Windows 11 machine
Launch the application normally through "Docker-compose up -d"
Expected behavior
Board is recognized
Actual behavior
App stuck on "Waiting for device"
Additional information
I've tried everything that came to mind, the connection is there, the firmware is properly configured and the board is recognized. I granted every access permission I could think of, as well.
I'd really appreciate any help or advice, and please let me know if you'd like me to provide more information.
Update: After days of trying, it magically seems to have resolved itself. However, when I list the ros2 topics in my terminal, nothing seems to appear. When I try to publish on the LEDs, it can't find any subscriptions either.
- Dominant language
- C
- Stars
- 101
- Forks
- 35
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 3
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.
More from micro-ROS/micro-ROS-demos
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
micro-ROS/micro-ROS-demos#97 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
micro-ROS/micro-ROS-demos#83 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
micro-ROS/micro-ROS-demos#81 · 11 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
micro-ROS/micro-ROS-demos#74 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
micro-ROS/micro-ROS-demos#64 ·
All issues in micro-ROS/micro-ROS-demos
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·