CC2652R: BLE Continuous Scan and Connection Termination.

Stuart Baker

Part Number: CC2652R

I am using the SDK version 3.10. I've noticed that if I enable continuous BLE scanning, and subsequently make a connection (as a master), scanning continues as expected. However, as soon as a device connection is terminated, scanning no longer occurs (though no scanning callbacks are produced to indicate that scanning is no longer ocuring). The only way to start scanning again is to disable the current scan and start a new scan.

Is this behavior intentional? What is the intent behind it?

Thanks,

Stuart

over 6 years ago

0 J Lindh over 6 years ago

TI__Guru 57865 points

Hi Stuart,

Assigning an expert to comment.

0 Marie H over 6 years ago

TI__Guru* 83691 points

Hi Stuart,

Sorry for the late answer.

Yes this is intentional/just how the LL works. I would recommend as a best practice to disable scanning before initiating a connection, then re-start scanning after the connection has been established.

0 Marie H over 6 years ago

TI__Guru* 83691 points

Hi Stuart,

I am seeing the same thing as you. I have filed a bug report.

0 Stuart Baker over 6 years ago in reply to Marie H

TI__Genius 10790 points

Marie provided the additional advice (offline) that an acceptable workaround is to call GapScan_disable() and then GapScan_enable() when a link termination event occurs.

Thanks,

Stuart

Bluetooth®︎

Bluetooth forum

CC2652R: BLE Continuous Scan and Connection Termination.