1 year ago.
Sleep/deep sleep profiling tool not generating trace o/p when trying to profile NRF52_DK
I followed the steps below to enable Sleep/Deep Sleep profiling.
"To enable the tracing, all you need to do is to define MBED_SLEEP_TRACING_ENABLED macro. You can do it by modifying your mbed_app.json config file or appending -DMBED_SLEEP_TRACING_ENABLED to mbed compile command."
Neither of the ways mentioned above is resulting in the sleep trace o/p on the UART interface, when the application is running. Is there anything else I need to do get the trace o/p.
I am using mbed-os 5.8.0
Question relating to:
11 months, 4 weeks ago.
We've taken another look at this and the tracer output is gated by DEVICE_STDIO_MESSAGES as the sleep tracer utilizes debug():
It's not clear why the nRF52 doesn't include "STDIO_MESSAGES" in the targets.json file, but you can try adding this in with the other "device_has" parameters for the MCU_NRF52832. You should then see the output being generated by the tracer.
Ralph, Team Mbed
1 year ago.
It seems that the sleep/ deep sleep profiling tool does not work for the NRF52_DK. We are currently working on a fix for that issue. We will update you once we have a patch for this problem.
Please let me know if you have any questions!
- Peter, team Mbed
If this solved your question, please make sure to click the "Thanks" link below!
You need to log in to post a question