1 year, 11 months 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

Thanks, Ajay

Question relating to:

The nRF52 Development Kit is a single-board development kit for Bluetooth Smart, ANT and 2.4GHz proprietary applications using the nRF52 Series SoC. This kit supports both development for nRF52832 SoCs.

How do you "modify mbed_app.json" to add this macro? I'm struggling over this for days now...

posted by Matthieu Labas 17 Apr 2019

2 Answers

1 year, 10 months ago.

Hi Ajay,

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

You will also likely need this PR which was recently merged and will be incorporated in Mbed v5.10.2:

posted by Ralph Fulchiero 15 Oct 2018
1 year, 11 months ago.

Hello Ajay,

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!