Using the mbed-os-cellular-example, I’m checking to see if the processor can deep sleep at the end of the example. Invoking “sleep_manager_can_deep_sleep_test_check()” I see that deep sleep is not possible. I enabled the deep sleep profiling tool with “-DMBED_SLEEP_TRACING_ENABLED” and nothing prints out. I am using the MTS_DRAGONFLY_L471QG. Running a small example program, it is able to deep sleep and the profiling tool works… kind of. It at least sends out a massive amount of “LOCK:…” “UNLOCK”:…" messages. So I know the profiling tool works to some extent on this platform. Can anyone tell me what might block the profiling tool from printing?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| STM32 Not Entering Deep Sleep | 2 | 912 | May 25, 2020 | |
| NUCLEO_L073RZ no chance to Deep Sleep | 8 | 1099 | June 12, 2020 | |
| Mbed sleep manager with cellular and LWIP | 1 | 216 | November 25, 2020 | |
| Sleep/deepsleep and Serial class | 1 | 920 | August 21, 2019 | |
| NUCLEO-L031K6 low power on MBED OS 2 | 2 | 612 | March 15, 2021 |