The power consumption is increased when application is migrated from SDK13.0.0(S132 4.0.3) to SDK15.0.0(S132 6.0.0)

RE: The power consumption is increased when application is migrated from SDK13.0.0(S132 4.0.3) to SDK15.0.0(S132 6.0.0)

Jørgen Holmefjord — Mon, 20 Aug 2018 15:55:26 GMT

This could be related to errata 89.

RE: The power consumption is increased when application is migrated from SDK13.0.0(S132 4.0.3) to SDK15.0.0(S132 6.0.0)

Peter Kenyon — Mon, 20 Aug 2018 14:52:33 GMT

Any more thoughts on this, I see a current consumption of 400+ uA just by enabling the spim driver (with no transfers), the current goes down when I call spim_deinit(), using the spi (no m) driver I do not see this behaviour but I was hoping to use easy DMA

RE: The power consumption is increased when application is migrated from SDK13.0.0(S132 4.0.3) to SDK15.0.0(S132 6.0.0)

Jørgen Holmefjord — Tue, 08 May 2018 09:26:15 GMT

Do the increased current come when only initializing SPIM, or do you have to do something more (starting transfer, etc.)? It sounds like your CPU is not able to go to sleep. I setup a test with the SPI example in SDK 15, where a application timer triggers a SPIM transfer every 5 ms. The average current consumption in ~44 µA:

RE: The power consumption is increased when application is migrated from SDK13.0.0(S132 4.0.3) to SDK15.0.0(S132 6.0.0)

chaoren2651 — Mon, 07 May 2018 13:20:38 GMT

Yes, I use SPIM peripheral with EasyDMA enabled and I use the nrfx legacy driver.

RE: The power consumption is increased when application is migrated from SDK13.0.0(S132 4.0.3) to SDK15.0.0(S132 6.0.0)

Jørgen Holmefjord — Mon, 07 May 2018 12:21:59 GMT

Hi,

Did you use SPIM peripheral (SPI with EasyDMA enabled) in SDK 13 as well (SPIx_USE_EASY_DMA set in sdk_config.h)? Are you using the nrfx legacy driver layer, or the new drivers directly?

Could you share code showing how you configure SPI and an example showing this issue?

Best regards,
Jørgen