Power/current consumption

RE: Power/current consumption

Tron — Thu, 12 Dec 2019 09:59:31 GMT

I found the guilty part, it was the external flash that was not turned off. Sorry for the inconvenience.

RE: Power/current consumption

Tron — Thu, 12 Dec 2019 08:41:23 GMT

Hi again,

The software behaves excellently.

Running the device in debug mode seems to draw a lot more current.

Stopping the debugger on a random point in time, the breakpoint line is always on line 78 in cpu_idle.S, in the function z_arch_cpu_idle. This operation has been done 15 times, and no exceptions.

WFE/SEV?

RE: Power/current consumption

Sigurd — Wed, 11 Dec 2019 16:50:35 GMT

Does the application work as intended after updating to v1.1.0 ?

If you are using SES(Segger embedded studio), you can try to run the code in a debug-session. Let the code run, and then click pause/break, and check if the CPU is busy-looping somewhere. You might need to do it a couple of times. If the CPU is sleeping, you should see in the disassembly on the right side in the IDE, that WFE/SEV is executed.

RE: Power/current consumption

Tron — Tue, 10 Dec 2019 18:08:10 GMT

The current consumption doesn't peak. It is a (more or less) constant draw. It is basically the same application that drew currents in the µA range before the change to v1.1.0. I had to create a new directory when checking out the new version of the Nordic Connect SDK.

Yours,

Tron

RE: Power/current consumption

Sigurd — Tue, 10 Dec 2019 13:37:24 GMT

Hi,

[quote user=""]the device draws between 5 and 6 mA during sleep. [/quote]

Do you have a plot of the current consumption ? Is it a constant 5-6 mA baseline draw, or do you have higher peaks(range 40-50mA)(but the average is 5-6mA) ?

If it's a constant 5-6 mA, then it could be that the CPU is busy-looping/spinning somewhere, and not going to sleep.

If you have 40-50 mA peaks at a regular interval, it could be that the modem is sending or receiving data.

BR,

Sigurd