App unusual current draw

RE: App unusual current draw

rookie — Fri, 26 Jul 2019 22:17:09 GMT

Hi - I identified this current is coming from a peripheral, not the nrf chip. Closing this ticket. Thanks!

RE: App unusual current draw

Jørgen Holmefjord — Fri, 26 Jul 2019 15:30:21 GMT

Unless you have initialized it in your application, it should not be enabled only by setting that in sdk_config.h. The clock might, however, be enabled by other peripherals that require the clock to run.

It looks a bit strange that it produces spikes, and that it suddenly stops. If you could provide a project, that would help a lot.

RE: App unusual current draw

rookie — Thu, 25 Jul 2019 14:07:21 GMT

I'm running this on a custom board, I will share a smaller project in a bit (but to produce the first graph it's just the first small snippet). I was going through the sdk_config.h file after you mentioned that the HF clock may be on.

This is my clock setting part of the config file,

// <e> CLOCK_ENABLED - nrf_drv_clock - CLOCK peripheral driver
//==========================================================
#ifndef CLOCK_ENABLED
#define CLOCK_ENABLED 1
#endif
// <o> CLOCK_CONFIG_XTAL_FREQ  - HF XTAL Frequency

// <0=> Default (64 MHz)

#ifndef CLOCK_CONFIG_XTAL_FREQ
#define CLOCK_CONFIG_XTAL_FREQ 0
#endif

// <o> CLOCK_CONFIG_LF_SRC  - LF Clock Source

// <0=> RC
// <1=> XTAL
// <2=> Synth

#ifndef CLOCK_CONFIG_LF_SRC
#define CLOCK_CONFIG_LF_SRC 1
#endif

RE: App unusual current draw

Jørgen Holmefjord — Thu, 25 Jul 2019 13:30:25 GMT

Hi,

5-600 µA sounds like the HFCLK/Timer is running. I would recommend that you try commenting out parts of your application to figure out exactly what peripheral is causing the increased current consumption.

Are you running this on a nRF52 DK or a custom board? If running on a DK, can you upload the project for debugging?

Best regards,
Jørgen