This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Current Consumption test on custom board using PPK

I am using PPK 1.1.0 to compute current draw on a custom hardware.

If I upload ble_app_hrs example on the nRF52-DK and measure it directly, I obtain average reading as 550 uA.

However, running the same application on my custom board yields 1.2 mA of current draw.

The custom board uses Raytac modules: MDBT42 and MDBT42V, and is powered using External DUT connector with SW2 set as External and SW4 set as Regulator.

Do you have any insights on this huge current draw?

Thank you.

Parents
  • Hey Rishi,

    1. Do you have any other circuits and devices on your custom PCB that can draw additional current?
      If this is the case then you need to electrically isolate the module from the rest of your board when measuring the current.
    2. Have you enabled any pull-ups, etc, on the module?
      If this is the case then you need to disable the pull-ups/downs before measurements.
    3. Are you running the example as provided or have you made any modification for your custom PCB?
    4. Can you show us your schematics and/or Layout files?

    Cheers,

    Håkon.

  • Hey Hakon,

    I have isolated the problem. I have a LIS2DH12 accelerometer in my design. Assembling this accelerometer along with three by-pass capacitors (0.1 uF, 0.1 uF, 10 uF) and two pull-up resistors (10K each) for SDA and SCL lines, increases the current consumption to 7 mA.

    Removing the pull-up resistors does not reduce the current consumption value either.

    I am not even using or enabling the accelerometer. It is just being powered by the VDD rail. I am running ble_app_hrs example.

    Any suggestions, what are the possible sources of this huge rise in current?

    Thanks.

  • Hey Rishi,

    My first thought is that there is a short circuit somewhere, either the LIS2DH12  footprint is wrong, the LIS2DH12 is mounted wrong, or the LIS2DH12 has an internal short circuit due to damage from ESD or kinetic impact. I suggest you write a simple application that tries to communicate with the LIS2DH12. If you are unable to read the device ID given the correct commands and a verified I2C communication, then the LIS2DH12 operating out of spec in some way or another.

    FYI: The nRF5 series SoCs have internal 13k pull-up/downs available on each GPIO so I believe you do not need external pull-ups on the SDA and SCL lines. 

    Cheers,

    Håkon.

Reply
  • Hey Rishi,

    My first thought is that there is a short circuit somewhere, either the LIS2DH12  footprint is wrong, the LIS2DH12 is mounted wrong, or the LIS2DH12 has an internal short circuit due to damage from ESD or kinetic impact. I suggest you write a simple application that tries to communicate with the LIS2DH12. If you are unable to read the device ID given the correct commands and a verified I2C communication, then the LIS2DH12 operating out of spec in some way or another.

    FYI: The nRF5 series SoCs have internal 13k pull-up/downs available on each GPIO so I believe you do not need external pull-ups on the SDA and SCL lines. 

    Cheers,

    Håkon.

Children
Related