nRF52832 SPI Slave Pulls Excessive Idle Current

RE: nRF52832 SPI Slave Pulls Excessive Idle Current

Jørgen Holmefjord — Mon, 23 Jul 2018 11:50:56 GMT

It seems the number in the PS have not been updated.

The follwing workaround is proposed to achieve low current consumption for SPIS:

A possible workaround is to not enable but instead use wake on pin on the CSN pin, then let that event wake the CPU which in turn enables the SPI. Of course this then has to happen before the first SPI clock after CSN low.

You can use PPI to connect the GPIOTE event from the CSN pin wakeup to the ENABLE task of the SPIS peripheral. With this workaround, the numbers should be OK.

RE: nRF52832 SPI Slave Pulls Excessive Idle Current

r-summers — Thu, 19 Jul 2018 06:42:49 GMT

Hey there Jørgen,

I wanted to check back to see if you've heard back about this IDLE current issue.

Thank you,

Ryan Summers

RE: nRF52832 SPI Slave Pulls Excessive Idle Current

Jørgen Holmefjord — Thu, 14 Jun 2018 12:58:20 GMT

I have forwarded the inquiry internally. I will get back to you as soon as I have an answer.

RE: nRF52832 SPI Slave Pulls Excessive Idle Current

r-summers — Thu, 14 Jun 2018 12:33:25 GMT

Hey there Jørgen,

I was wondering if you had any luck in figuring out where the 1 uA IDLE current was measured.

Thanks for looking into this matter,

Ryan Summers

RE: nRF52832 SPI Slave Pulls Excessive Idle Current

Jørgen Holmefjord — Wed, 06 Jun 2018 13:16:43 GMT

Hi,

I'm seeing similar measurements on my board. I will check internally how the 1 µA IDLE current measurement is obtained.

Best regards,
Jørgen