This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2640: Current consumption rise in timer interrupt

Part Number: CC2640

Our customer is evaluating the evaluation board current consumption using a current waveform analyzer.

In the test result, when CC2640 is in active mode the current is around 1.9mA.

But a periodically pulse with 5.9mA height and very short duration is observed at the same time.

In the test software, a 50ms periodically timer interrupt is enabled.

If the period setting is changed from 50ms to 100ms the current pulse period also change from 50ms to 100ms.

Is it possible this current consumption is related in the MCU hardware?

  • Thank you for your information.
    Now I have basic understanding about the current consumption of various settings.

    Our test software only process when there is timer interrupt or UART data receive. (BLE function is not initialized.)
    I thought most of the time CC2640 is in IDLE mode.

    I find the current level of standby VDDR recharge is similar to the current pulse in our test result.
    Is it possible that the VDDR recharge is enabled even CC2640 didn't enter Standby mode?

    If I avoid CC2640 entering Standby mode and IDLE mode the 5.9mA current pulse is gone.
    Power_setConstraint(PowerCC26XX_SB_DISALLOW);
    Power_setConstraint(PowerCC26XX_IDLE_PD_DISALLOW);

    But if I only avoid CC2640 entering Standby mode the 5.9mA current pulse is still exist.
    Power_setConstraint(PowerCC26XX_SB_DISALLOW);
    //Power_setConstraint(PowerCC26XX_IDLE_PD_DISALLOW);
  • The recharge pulses is only there when in standby. Please state what HW you are running on and what SDK version etc. I would recommend that you start by measuring the current consumption on an unmodified code example from the SDK to make sure that your test setup is OK and that you are measuring the correct current. Once that is done, you can start measuring on your own code. When we do not know what HW you are running and what exactly your code is doing, it is not possible to answer why you are measuring the currents that you are doing.

    BR

    Siri