apache / apache/mynewt-nimble

How to trace function calls in controller code

Open
#1,638 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
893
Forks
512
Avg merge
13d 31m
Merged PRs (30d)
7

Description

Hi, I am trying to trace function calls in the stack controller part. I planned to printf some log when a certain function is called and find out the relationship of different functions.

But I notice that there is no logging output under `Mynewt/repos/apache-mynewt-nimble/nimble/controller/src` directory. When I added `MODLOG_DFLT` in functions like `ble_ll_rx_end`, the peripheral failed in connection establishment due to unknown reason (but it worked in `ble_ll_rx_pkt_in`). I wonder whether there is a way to print logging information from the controller part, or how I can trace the function calls at runtime.

Highly appreciate!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in Mynewt/repos/apache-mynewt-nimble/nimble/controller/src and compare the logging behavior of ble_ll_rx_end with ble_ll_rx_pkt_in. Investigate how controller runtime logging is configured and why adding MODLOG_DFLT affects connection establishment. Done means documenting a reliable way to trace controller calls without breaking peripheral connections.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.