Exit from debug mode

[Jérémy Michaud]

Hello,

I did some power measurement on the nrf52 DK with the Nordic profiler kit and the result was way more than what we could expect from a nrf52 (about 1 mA). Even in power off mode, it still needs about this amount of current.

After a search on the devzone, I discovered that it could be because the nrf52 is in debug mode. In this mode, the nrf52 never goes on power down mode et consume way more than in normal mode.

I tried to power reset the chip in order to enter normal mode. But I didn't work.

I also tried nrfjprog --pinreset, but it didn't change anything either.

Finally, I saw on that thread that the code to know whether the debug mode is enabled or not is :

if (DWT->CYCCNT != 0) { bsp_board_led_on(LED); }

And the LED is always on when I run this code.

Is there a solution to exit the debug mode ?

[Jérémy Michaud]

Hello, thank you for this answer. I tried it but unfortunately, it didn't work.

I did a couple of tests to be more precise about my issue.

First of all, I discovered that when I press the reset button, It works when the Profiler kit is unplugged but not when it is plugged.

Secondly, I am not sure if this problem is linked to debug mode or another issue. I found the codeif (DWT->CYCCNT != 0) { bsp_board_led_on(LED); } on the devzone but I am not actually sure whether this is the right way of doing it or not.

To be sure of the problem, I installed the latest version of the SDK (14.0.0) and I flashed the S132 (5.0.0) to the nrf52 DK. Then I flashed the ble_app_hrs example. I opened the profiler kit sotfware and I have an average consumption of about 1 mA :

And when I am in power off mode, the average consumption is about 700 uA :

I think these values are far away from what it should be, but it could be linked to another problem.

[Jérémy Michaud]

I tried this, but even if I call sd_power_system_off(), the consumption doesn't go lower than 7 mA which is way more than the 300 nA announced by Nordic.

When I press the reset button when the DK is connected to the Profiler kit, it doesn't reset.

Now my question is: do I have too much consumption because I am using armGCC or because I have an issue with debug mode (or low power mode)?

If it's linked to armGCC, it there a way to have the same consumption on armGCC than on Keil?

And if it's linked to the debug mode, how can I fix this issue?

To figure out what is the problem, could you maybe send me a hex example that has low power consumption so I can compare?

Thank you in advance.