• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 53 subscribers
  • Views 453 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CCS/CC2642R: SPI

CCS/CC2642R: Power Consumption of BLE 5.0

KAHSAY TEREFE GASHAYE
Prodigy 75 points
Part Number: CC2642R

Tool/software: Code Composer Studio

I am currently trying to do a test for the power consumption of BLE5.0 based on the simple peripheral example available on the SDK. But I have some difficulties on:

- How to remove periodic events

- How to make unused GPIOs as an output and low.

The SDK version that I am using is simplelink_cc26x2_sdk_2_30_00_34 and my CCS version is 8.2. I really appreciate if someone could help me on this.

Thanks

  • 0
    TI__Mastermind 25045 points
    Hello,

    Please take a look at this Application Report www.ti.com/.../swra478c.pdf it uses the simple_peripheral as baseline. Specifically please look into Table 5.

    Best regards,

    David
  • 0 in reply to DavidL
    Prodigy 75 points

    Hi DavidL, I have tried to use the BLESimplePeripheral example on SimpleLink CC26X2 SDK 2.30.00.34. What I have observed is that the static power consumption is approximately 135 mA. Here I also need how to disable the external flash on this SDK as I am not able to find a solution for the error raised when I use the same way as described in the document.

    I couldn't find the exact substitution for BLE5.0 for the connection parameter update (#define DEFAULT_ENABLE_UPDATE_REQUEST GAPROLE_LINK_PARAM_UPDATE_WAIT_REMOTE_PARAMS)

  • 0 in reply to KAHSAY TEREFE GASHAYE
    TI__Mastermind 25045 points
    Hello,

    135mA does not seem to be correct. Let me run a quick test and I'll report back my numbers.

    Thanks,

    David
  • 0 in reply to DavidL
    TI__Mastermind 25045 points

    Hello,

     Appologies for the late response: And this is what I'm measuring with the Launchapd without jumpers and configuring the I/Os as:

    const PIN_Config MyBoardGpioInitTable[] = {
    IOID_0  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_1  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_2  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_3  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_4  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_5  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_6  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_7  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_8  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_9  | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_10 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_11 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_12 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_13 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_14 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_15 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_16 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_17 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_18 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_19 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_20 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_21 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_22 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_23 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_24 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_25 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_26 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_27 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_28 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_29 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,
    IOID_30 | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_DIS | PIN_GPIO_LOW | PIN_PUSHPULL |PIN_NOPULL | PIN_DRVSTR_MIN,

    PIN_TERMINATE
};

    1. Baseline (without any BLE Tasks) ~1uA

      /* Initialize ICall module */
//dl  ICall_init();

  /* Start tasks of external images - Priority 5 */
//dl  ICall_createRemoteTasks();

#ifdef PTM_MODE
  /* Start task for NPI task */
  NPITask_createTask(ICALL_SERVICE_CLASS_BLE);
#endif // PTM_MODE

//dl  SimplePeripheral_createTask();

  /* enable interrupts and start SYS/BIOS */
  BIOS_start();

    2.  Using OoB example configuration with some of the App Note recommendations:

    Advertising ~600uA (100ms Advertising window)

    Connected ~900uA (30ms connection interval)

    These numbers can be improved changing connection parameters. Are you using a LP or your custom HW? Please try to get a baseline as I did on #1.

      Hopefully this helps.

        David

  • 0 in reply to DavidL
    TI__Mastermind 25045 points
    Forgot to mentioned that the "Measuring Current Consumption (Bluetooth Low Energy and Proprietary)" App Note got updated a few days ago. You can find the Rev. D here www.ti.com/.../swra478

    Best regards,

    David