nRF9160 DK PSM/System OFF current too high

Hi,


OS: Windows 10
Editor: SEGGER Embedded Studio for ARM (Nordic Edition) V5.68 (64-bit)
nrfjprog version: 10.15.1
JLinkARM.dll version: 7.52b
nRF Connect SDK version: 1.6.0
nRF9160 modem firmware version: 1.2.7
nRF9160 DK version: 1.0.2

I was testing our custom FW on a nRF9160 DK and I noticed a high PSM power consumption. The DK was consuming around 70µA while our custom board consumes ~15µA.

I then got 1452.sysoff.hex file from this guide to check if everything is right and I noticed it is consuming around 70µA even in system off mode (~5µA on custom board):

Do you have any idea what could be causing this? I am supplying power with PPK2 source mode through the VDD_nRF-pin (P22) like shown here. I have made sure the board controller FW is the original one provided here. I have no USB cable or anything else attached to the DK. I have also tried removing the SIM-card and disconnecting the interface MCU by moving the IFMCU DISCONN-switch to the right position. Neither of these helped with the consumption.

As far as I know the current should only be going to nRF9160 when supplied through the VDD_nRF-pin and therefore only be a few microamps in both cases. Is there anything I need to change/check in addition to the things I have already done? Or is my DK faulty?

Thanks in advance!

Parents Reply
  • Hi,

    After some testing i might have had a similar situation happen to one of my test DK's. After change in modem firmware, it had average current of 65uA.

    I wiped the DK, flashed the AT client application, then wiped and reflash the system off hex file. Then the average current consumption was down to 2.10uA


    DK v1.0.0
    %HWVERSION: nRF9160 SICA BQA
    %SHORTSWVER: nrf9160_1.3.1
    avrg = 2.4uA

    downgrade to mfw 1.2.7, avrg = 65uA

    Cange application to AT client
    %HWVERSION: nRF9160 SICA BQA
    %SHORTSWVER: nrf9160_1.2.7
    avrg = 2.10uA

    Try to reprogram and reset the DK a couple of times, power cycle once or twice.

    I did only see this once on one of my test DK's, tested 3 diffrent DK's. So the issue seems to be fixable.


    Regards,
    Jonathan

Children
Related