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.

RTOS/LAUNCHXL-CC2640R2: Cannot connect BLE again, after CC2640R2 is awakened from standby mode?

Part Number: LAUNCHXL-CC2640R2

Tool/software: TI-RTOS

Hi TI,

I've tried to use

"Power_releaseConstraint(PowerCC26XX_SB_DISALLOW)"

to allow the CC2640R2 go into the standby mode.

However, I'm trying to use

"Power_setConstraint(PowerCC26XX_SB_DISALLOW)"

in the button interrupt codes to awaken the CC2640R2. But, CC2640R2 cannot connect BLE again.

What happens? The manual says the RF Core is one of CC2640R2's peripherals and it's disabled in standby mode.

But why the RF Core doesn't work again when I awaken the CC2640R2 from standby mode?

Thanks.

  • Is there a particular reason why you're doing this?

    The device will go into stand by as soon as there's no longer any events or work that needs to be done. The stack will wake up the processor to keep the BLE connection alive - and then go back to standby.

    Are you seeing a connection being maintained once you release the constraint?

    Regards,
    Rebel
  • Hi Rebel,

    1.About the particular reason:
    Yes. When BLE is disconnected, it must be standby to maintain the longest battery duration. However, it cannot be shutdown because the SRAM must be maintained.

    2.About connection:
    No. No connection found, and even the CC2640R2 isn't advertising again.
    I only set the power constraint on the disconnected status(and the CC2640R2 is only advertising), and I release the power constraint when the user hit its button.
    If "only releasing the power constraint" cannot wake the CC2640R2, which command is missing?

    Thanks.
    Best Regards