SPI instance taking up a lot of power when enabled.

[Jay_Shah]

SDK version: 15.3

Soft-device version: 6.1.1

Hi,

I've been working on a low power application where every 10's of uA is important. My application requires SPI as Master on nRF52832 but as soon as I enable my SPI my current shoots up to mA range from uA. 

I used "SPI"example present in "..\nRF5_SDK_15.3.0_59ac345\examples\peripheral" to understand the configuration of SPI. Could you please tell my why would this happen?

I read a couple of articles where people faced similar current consumption issue. Or do I have to do some disabling of SPI to save power?

[Jay_Shah]

Hi,

I had figured it out on my own and had done the implementation with SW timer. 

There's a weird thing that I'm noticing that, the current consumption is not same in every transaction.

I make a transaction in every 2 seconds, sometimes the current consumption is as low as 1.3mA and sometimes it's as high as 7mA. RF and data logging is disabled only SPI is running on every 2 second interrupt.

What is the number shall I believe?

Test Setup:

1.  I'm using nRF52DK with PPK.

2.  PPK is in DK mode and powered by DK.

3.  DK is powered using USB (I understand that the document mentions that there will be uncertainty in measurements when powered with USB), but will the number be that bad? I've done my previous analysis with an Oscilloscope and that time it was powered with USB only so I want to keep the setup same by only swapping Oscilloscope with PPK.

[Stian Røed Hafskjold]

So when you get an interrupt the CPU wakes up and starts the SPI transfer. The CPU is on for a very sort time, but the run current can be as high as 8mA, depending on configuration.: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/cpu.html?cp=3_1_0_6_1#topic

The resolution on the PPK is probably not good enough to capture every CPU spike, but only the actual SPI run current which is 1.2-2mA depending on configuration. That's probably why the peak current is varying.

Can you try to use the trigger window instead? It has a higher resolution.