CC2650STK: Supervision Timeout with CC2640

Steffen Rentz

Part Number: CC2650STK
Other Parts Discussed in Thread: CC2640, , CC2650

Dear TI Community,

We are developing a Firmware for a customer board which with a CC2640. We ported the CC2650STK SensorTag firmware on this board but now we could observe a strange issue:

The firmware is running on the customers board; as a central device we use the SmartRF06 with CC2650EM. In btool we set the following Connection Parameters:

Connection Interval: 1600 (2000 ms)

Slave Latency: 4

Supervision Timeout: 3200 (32 000 ms)

When connecting to the customer’s board we get a supervision timeout after 32 seconds. Even though we measured a connection event every 2 seconds.

The same firmware running on the CC2650 SensorTag gets no Supervision Timeout and the connection stays stable all the time.

Could anyone explain this?

Unfortunately we don’t have a USB dongle, so we cannot use TI’s Packet sniffer.

Thanks

Steffen

over 8 years ago

0 Christin Lee over 8 years ago

TI__Guru 56335 points

How did you measure there is a connection? Did you toggle IO? Did you use range extender to track the radio activities?

0 Steffen Rentz over 8 years ago in reply to Christin Lee

Intellectual 370 points

We have a Keysight Power Analyzer which measures the connection events. The peaks always come exactly in the same interval as setup as Connection Interval.
A breakpoint in SensorTagConnectionControl_update() showed the current values: 1600,0,3200 (Connection Interval, Slave Latency, Supervision Timeout).

0 Steffen Rentz over 8 years ago in reply to Christin Lee

Intellectual 370 points

Hi Christin,
I have a suspicion:
The TI SensorTag is powered by a 3V battery. The customer’s board has a 3 V battery too but the voltage input of the CC2640 is reduced to 1.8V by some voltage dividers.
The function AONBatMonBatteryVoltageGet() returned 850 (on the SensorTag) and just 461 (on the customer’s board).
Could it be that this is not enough for longer connection intervals?
Regards
Steffen

0 Christin Lee over 8 years ago in reply to Steffen Rentz

TI__Guru 56335 points

It could be devices might end up stuck in reset after a while. When the radio turns on, 1.8- internalResistorFromBat*6mA could easily trigger BOD.

I would recommend you to use a oscilloscope and set VDDS to trigger at 1.79V to see if that happens.

0 Steffen Rentz over 8 years ago in reply to Christin Lee

Intellectual 370 points

Hi Christin,

A reset after a BOD would break a debug connection, right?

That is not the case - the debug connection stays running all the time.

In debug I can see that the device receives a Supervision Timeout and restarts Advertising.

Regards

Steffen

0 Christin Lee over 8 years ago in reply to Steffen Rentz

TI__Guru 56335 points

Can you implement range extender on your custom program and track the radio activities?
processors.wiki.ti.com/.../CC26xx_Range_Extender_Control

0 Steffen Rentz over 8 years ago in reply to Christin Lee

Intellectual 370 points

Unfortunately I don’t have an external range extender that I could connect to my board.

Regards
Steffen

0 Christin Lee over 8 years ago in reply to Steffen Rentz

TI__Guru 56335 points

You don't need external component. This is just to route the PA and LNA activities to IOs. And then you can track the PA/LNA activities through logic analyzer.

0 Steffen Rentz over 8 years ago in reply to Christin Lee

Intellectual 370 points

I added
IOCPortConfigureSet(IOID_7, IOC_PORT_RFC_GPO0, IOC_IOMODE_NORMAL);
IOCPortConfigureSet(IOID_9, IOC_PORT_RFC_GPO1, IOC_IOMODE_NORMAL);
to my firmware.
I could see that the power consumption is higher now.
However the Supervision Timeout still occurs.
Regards
Steffen

Bluetooth®︎

Bluetooth forum

CC2650STK: Supervision Timeout with CC2640