CC2640: STANDBY wake-up with BLE issue

Anton Zyma

Part Number: CC2640

Hi!

I'm working with modified Project_zero example (TI_RTOS is used) and need to put the MCU into STANDBY mode by event (BLE) and wake up on Sensor Controller ALERT.

I use the following code for testing purposes. It is called at the beginning of ProjectZero_taskFxn once (before loop).

  UInt keyHwi = Hwi_disable();
  scifOsalEnableTaskAlertInt();
  UInt keyTask = Task_disable();

  Semaphore_pend(sem, Semaphore_PendState_WAIT_FOREVER);
  testFlag = 1;
  RF_cancelCmd(h, ch, mode)
  RF_postCmd(h, pOp, ePri, pCb, bmEvent)
  
  Task_restore(keyTask);
  Hwi_restore(keyHwi);

Everything works when Power_setConstraint(PowerCC26XX_SB_DISALLOW); is used (i.e. the deepest sleep mode MCU can achieve is the IDLE mode). In this case device starts advertising after Sensor Controller interrupt is generated.

When STANDBY is allowed it looks like the MCU doesn't wake up. I assume, the problem here is that RFCORE power domain is not restarted after the Sensor Controller event wakes up the MCU.
Am I correct? If yes, could you provide any example on how to perform this re-initialization?

Regards,
Anton.

over 4 years ago

0 Clément over 4 years ago

TI__Guru** 101490 points

Hi Anton,

Generally speaking, you should not access the RF driver when the BLE stack is running. In addition, the power driver is already responsible to set the device in the lowest power mode possible. Here the issue rather looks like the RF Core has nothing to do (i.e. no Bluetooth operations are expected) when the device is woken up.

In your case, when you want to set the device in standby mode, I would recommend to stop advertising and scanning and terminate all the BLE connections. The power driver will then set the device in standby mode.

When you wish to resume to active mode (i.e. when the sensor controller wakes up the device), you can re-enable advertising / scanning.

I hope this will help,

Regards,

0 Anton Zyma over 4 years ago in reply to Clément

Prodigy 10 points

Hi Clement,
thank you for reply.

I've also tried to exclude BLE from that just to check if the MCU wakes up from Sensor controller alert and the affect is the same:
MCU wakes up from IDLE state, but not from the STANDBY.

How can I ensure that Sensor controller event works?

Regards

0 Markel Robregado over 4 years ago in reply to Anton Zyma

Guru 86765 points

See, this post.

e2e.ti.com/.../cc2650-calling-simplebleperipheral_enqueuemsg-from-simple_gatt_profile-c

0 Mikael Hansson over 4 years ago

Prodigy 110 points

Hi all,

I'm the project manager of this "modified Project_zero example" with very limited technical knowledge.

Therefor I do have one single question concerning functionality only:

Can a motion sensor connected to mcu cc2640r2f (over i2c; GPIO 9 & 10) wake up the mcu from STANDBY?

All suggestions and solutions appreciated. Thx!

0 Clément over 4 years ago in reply to Mikael Hansson

TI__Guru** 101490 points

Hi,

Short answer is yes.

In details, the sensor controller of CC2640R2F has an I2C master interface. That way, the sensor controller can wake-up the device when needed.

Best regards,

0 Anton Zyma over 4 years ago in reply to Clément

Prodigy 10 points

Hi Clement!
Thank you for reply.

If the hardware I2C is used in the main application and bit-banging I2C for sensor controller. Am I correct if I say that these interfaces may interfere each other and it is better to use Sensor Controller in all power modes?

0 Clément over 4 years ago in reply to Anton Zyma

TI__Guru** 101490 points

Hi,

Correct, it would be easier to use the sensor controller to handle I2C communication in all the power modes.

Regards,

0 Markel Robregado over 4 years ago in reply to Clément

Guru 86765 points

Clément said:
That way, the sensor controller can wake-up the device when needed.

This is new to me. From my experience with sensor controller after SensorController_taskalertCallback(), still need to queue or post an event to wake the device from sleep mode..

-kel

0 Clément over 4 years ago in reply to Markel Robregado

TI__Guru** 101490 points

Hi,

Markel Robregado said:
This is new to me. From my experience with sensor controller after SensorController_taskalertCallback(), still need to queue or post an event to wake the device from sleep mode..

Technically, the main core is already active when you execute SensorController_taskalertCallback(). That being said, you are right, we strongly recommend to only post a semaphore or a message within SensorController_taskalertCallback(). That way the code executed in the callback remains short.

Regards,

Bluetooth®︎

Bluetooth forum

CC2640: STANDBY wake-up with BLE issue