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/CC2640: pending notification causes higher current consumption

Part Number: CC2640


Tool/software: TI-RTOS

Hello,

I am running some current consumption tests on a design based on the SimpleBLEPeripheral project and I am experiencing some unexpected behaviour:

Stack: ble_cc26xx_2_01_01_44627

Connection Interval: 162*1.25ms

Timeout: 5000ms

Slave Latency: 0

Link is encrypted.

There is some data generated in a periodic event (1s) that is written in a characteristic via the following line.

Batmon_setParameter((uint8_t) BATMON_VOLTAGE,(uint8_t) BATMON_VOLTAGE_LEN, (void*)voltagedata);

When notifications are enabled for that characteristic the current consumtion stays higher than expected until the next connection event. See attached pictures.

When the caracteristic configuration is set to "00:00" the current consumption stays low between the call of ICall_wait() and the next connection event. Also all the connections have the same distance to each other. When notification is enabled but the line "Batmon_setParameter((uint8_t) BATMON_VOLTAGE,(uint8_t) BATMON_VOLTAGE_LEN, (void*)voltagedata);" is commented out, everything is as expected, too.

The unexpected behaviour can be observed for other characteristics with notifications enabled, too.

I doubt, that this behaviour is intended.

Thanks

Thomas