Exit from debug mode

RE: Exit from debug mode

Bjørn Kvaale — Mon, 06 Nov 2017 11:40:13 GMT

Great! Good to hear that it all worked out in the end. Have a nice day Jeremy. :)

RE: Exit from debug mode

Jérémy Michaud — Mon, 06 Nov 2017 10:58:32 GMT

Hello,

I opened a case like you said and we found out that my PCA10040 is broken somehow.

Thank you for your help!

Jérémy

RE: Exit from debug mode

Stian Røed Hafskjold — Mon, 16 Oct 2017 12:10:10 GMT

Based on the previous comments here, I believe that the PPK is showing the wrong numbers, and that the current consumption itself is fine.

Can you check the version number written on the PPK?
Get the latest SW from here: www.nordicsemi.com/.../Power-Profiler-Kit
And, flash the PPK with the FW hex that follows the SW package.

If it is still showing the wrong numbers please open up a new case in MyPage support portal, www.nordicsemi.com/.../Contact-Support-Team, and link to this Devzone thread, and write that Stian wants to take the case.

RE: Exit from debug mode

Bjørn Kvaale — Fri, 13 Oct 2017 12:29:14 GMT

By power cycling, I just mean: turn the nrf52 DK off, remove the power source (e.g. battery), then attaching the power source again & turning the DK on again. I am pretty sure it's normal that the reset button doesn't work when you attach the PPK to the DK. This is because the reset button on the nrf52 goes via the SWD interface on the nrf52 chip. Once you attach a PPK, the SWD interface is connected to the nrf52 chip on the PPK, not on the DK.

RE: Exit from debug mode

Jérémy Michaud — Fri, 13 Oct 2017 07:22:31 GMT

Ok, thank you for your procedure, I just checked everything:

cut SB9 on the dev kit : [ OK ]
set SW2 and SW4 in the DK position on the PPK : [ OK ]
connected the USB cable to the DK and not the PPK : [ OK ]
and power cycled the DK after flashing the hex file? : [ Not sure ]

What do you mean with the last point? Power off and on again? If that is the case, yes I did.

I want again to say that when my DK is connected to the PPK, the reset button doesn't work anymore. Is it normal?

RE: Exit from debug mode

Bjørn Kvaale — Tue, 10 Oct 2017 13:15:03 GMT

Just talked to our current measurement expert. He thinks it is correct that your ampere meter shows 0 A, as the advertising intervals are quite long. So most likely, the PPK is showing a wrong current consumption. He tested the same hex file I posted and got a normal idle current of a few uA between the radio events. From the plots you posted, you're getting a current consumption of about 600 uA between radio events. That's a big offset.

Have you checked that you have:

cut SB9 on the dev kit
set SW2 and SW4 in the DK position on the PPK
connected the USB cable to the DK and not the PPK
and power cycled the DK after flashing the hex file?

Also, which version of the PPK are you currently using? Which version of the PPK software are you using?

RE: Exit from debug mode

Bjørn Kvaale — Tue, 10 Oct 2017 12:18:24 GMT

The consumption of 800 uA: is this during advertising or when you are connected to your smartphone? And I assume you are not pressing a button while you are measuring current, right? By pushing a button at the same time, this could lead to the 200 uA difference between our current measurements (see this post).

RE: Exit from debug mode

Jérémy Michaud — Fri, 06 Oct 2017 08:04:05 GMT

I just tried your example but I have a consumption of 800 uA. I also tried the to measure it with a multimeter but I have a consumption of 0 but I cut the bridge SB9 so I guess my multimeter is not precise enough.

RE: Exit from debug mode

Bjørn Kvaale — Fri, 29 Sep 2017 11:47:09 GMT

Hey Jérémy. I got a tip from a colleague here at Nordic. If you have a multimeter, could you measure the current over the P22 pins? This is to make sure that it's not the PPK that is measuring an incorrect current...

RE: Exit from debug mode

Bjørn Kvaale — Thu, 28 Sep 2017 06:16:36 GMT

I do not think the current consumption is related to armGCC. But just to test, I will send you the hex file that I have compiled in Keil and the softdevice you should flash over to your nrf52DK. Just click on this link. Hope that helps! Let me know how it goes.

RE: Exit from debug mode

Jérémy Michaud — Thu, 28 Sep 2017 05:45:19 GMT

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.

RE: Exit from debug mode

Bjørn Kvaale — Fri, 22 Sep 2017 13:54:41 GMT

You could check out this amazing devzone post. Not sure if it will help with armGCC, but you might be able to reduce power consumption.

RE: Exit from debug mode

Jérémy Michaud — Fri, 22 Sep 2017 10:28:44 GMT

Do you know if there is a way of reducing power consumption with armGCC?

RE: Exit from debug mode

Bjørn Kvaale — Thu, 21 Sep 2017 06:47:17 GMT

I have flashed the ble_app_template_pca10040_s132.hex using nrfgostudio and am looking at the PPK current consumption. I get an average current consumption of 605 uA when advertising. Running the ble_app_hrs example using the same method, I got an average current consumption of 599 uA during advertising. Once connected, the average current consumption drops to 500 uA. So it seems that when the hex file is directly flashed to the nrf52dk using nrfgostudio, the current consumption is higher. Unsure why this is. My current was a lot lower when built and flashed via Keil.

RE: Exit from debug mode

Jérémy Michaud — Thu, 21 Sep 2017 04:40:57 GMT

I followed it, but the result is the same.

RE: Exit from debug mode

Bjørn Kvaale — Wed, 20 Sep 2017 06:57:37 GMT

Just follow this guide. Go to the quick start tab.

RE: Exit from debug mode

Jérémy Michaud — Wed, 20 Sep 2017 05:53:10 GMT

I don't have a Keil license so I cannot compile ble_app_hrs. But I tried to directly flash the ble_app_template_pca10040_s132.hex and I have the same result basically. Yes, I think I set up the PPK board correctly, but maybe could you tell me how to set it up? To be sure that it is right configured. Thank you

RE: Exit from debug mode

Bjørn Kvaale — Mon, 04 Sep 2017 13:40:08 GMT

I just tried the same example you tried with the ppk using sdk 14 and the ble_app_hrs example. I am getting an average current consumption of 2.72 uA, which is a lot lower than the 1 mA you report. I flashed the softdevice (S132) using nrfgostudio (first erased the application and softdevice memory) and compiled and flashed the ble_app_hrs example using Keil. I then connected to the nrf toolbox app on my iPhone and ran the HRM example. Could you try this again using Keil? It seems very weird that you are getting such a high current consumption. Are you sure you have set up the PPK board correctly? Hope this helps a bit!

RE: Exit from debug mode

Bjørn Kvaale — Mon, 04 Sep 2017 11:19:28 GMT

You could try to run the example on Keil to see if that helps, but I am uncertain if it will. I am looking at the issue right now. I'll get back to you soon.

RE: Exit from debug mode

Jérémy Michaud — Thu, 31 Aug 2017 09:31:12 GMT

I tried it both on the nRF52832 DK and the nRF52840 Preview DK but the result is the same.

I also found on the header file components\libraries\util\app_util_platform.h a macro named NRF_BREAKPOINT_COND and the code if (CoreDebug->DHCSR & CoreDebug_DHCSR_C_DEBUGEN_Msk) to determinate whether the debugger is connected or not. I tried it on the main function but it never goes inside the if statement.

Do you need more information? Do you have maybe some code I can try to determinate more precisely the problem?

By the way, I am using arm GCC but I can try to run the example on Keil if that could help.

Thank you for your help

RE: Exit from debug mode

Bjørn Kvaale — Fri, 25 Aug 2017 11:43:06 GMT

That's strange. I'll take a more in depth look at this issue next week.

RE: Exit from debug mode

Jérémy Michaud — Thu, 24 Aug 2017 09:47:11 GMT

NRF_POWER->RESET is not defined on the SDK, so I did *((uint32_t *) 0x40000544) = 1; instead. It should be the same, right ?

RE: Exit from debug mode

Jérémy Michaud — Thu, 24 Aug 2017 09:45:01 GMT

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.

RE: Exit from debug mode

Bjørn Kvaale — Wed, 23 Aug 2017 10:49:51 GMT

I believe I found the problem. Check out this devzone question. It seems when you use nrfgoStudio to enable the reset pin, the chip remains in debug mode after programming.

Try adding NRF_POWER->RESET =1; to your code instead (for example 1st line in main() function) to set the reset register to 1 (How to reset the nrf52 board). Then you should be able to do a pin reset. Hope that helps!

RE: Exit from debug mode

Jérémy Michaud — Wed, 23 Aug 2017 09:37:40 GMT

I oppen the nRFgo Studio application, pressed to the "enable reset pin" button and pressed the reset button of the nrf52. I also tried to switch it off an on again.