Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Micro ros agent stopped at set_verbose_level

Open
  • Is something wrong?
#133 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
embedded-iot

Research direction

Start by comparing the Zephyr first-application RTOS tutorial with the board entry in CMakeLists.txt and the UART fd change in microro_tranpsort.h, then run the shown micro_ros_agent serial command. Confirm whether the agent proceeds past set_verbose_level and whether the expected /microROS/ping topic appears; document the board, UART, and transport settings that reproduce the result.

Written by the indexing model from the issue text.

Description

Issue template

  • Hardware description: Wio LoRa E5 dev board
  • Zephyr
  • Version or commit hash: Humble

Steps to reproduce the issue

I reproduce steps like on website https://micro.ros.org/docs/tutorials/core/first_application_rtos/zephyr/
I tried pin_pong app and int32_publisher but I used serial config
But to run it on my board I added my board name in CMakeList.txt and also changed in microro_tranpsort.h fd:

    // Set the UART used for communication. e.g. {.fd = 0} leads to UART_0 being used.
    static zephyr_transport_params_t default_params = {.fd = 0};

to .fd=1.
I flash the board by st-link, but for connection I use UART-USB concerter

ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_c68cb4bd91ecec11be34ac0ead51a8b2-if00-port0
Actual behavior
[1612884194.563610] info     | TermiosAgentLinux.cpp | init                     | running...             | fd: 3
[1612884194.563954] info     | Root.cpp           | set_verbose_level        | logger setup           | verbose_level: 6
Expected bahviour

I want to have a new publisher ping in ros2 topics, but for now i only have 2 default. This is what I expect:

user@user:~$ ros2 topic echo /microROS/ping
stamp:
  sec: 20
  nanosec: 867000000
frame_id: '1344887256_1085377743'
---
stamp:
  sec: 25
  nanosec: 942000000
frame_id: '730417256_1085377743'
---
Additional information

Is there anything to add or what should I change?
I think the problem is in connection between board and my pc, I work on ubnutu 22.04.3, but I don't know why it's starts to running because if there wasn't connection it would show waiting for connection

Dominant language
C
Stars
92
Forks
56
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from micro-ROS/micro_ros_zephyr_module

All issues in micro-ROS/micro_ros_zephyr_module

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.