CC2642R-Q1: Direct Advertisement Procedure

Pavan Pinapatruni

Part Number: CC2642R-Q1

I tried do direct advertisement from peripheral by triggering after normal connection establishment by terminating existing connections by following below steps

1. disable existing longRange and legacy advertisements

2. terminate existing connections

3. create new advertisement parameters set with event props as (connectable, legacy, directed) with new legacy handle

4. through gapadv_setparameter api I am setting peer addr of central in rev order.

5. not loading any advertise data or scan response data

6. setting mask

7. enable advertisement of new legacy handle

These are the exact steps I do

But I can't see any advertisement in central through nrf App though I have central mac address in reverse format.

I check through sniffer ADV_DIRECT_IND is released by peripheral.

I exactly can't figure out what kind of basic step I am missing out. If someone can guide me step to step procedure to be followed for direct advertisement in this it would be helpful.

Thanks in advance.

11 months ago

0 Evan Wakefield 11 months ago

TI__Mastermind 38580 points

Hi there,
Before going too far into the details, can you please provide the SDK version you are using?

To be clear, you are not having an issue sending out the directed advertisement from your TI peripheral device as confirmed by the sniffer, but are having an issue with the nRF application/phone to see the advertisement?

0 Pavan Pinapatruni 11 months ago in reply to Evan Wakefield

Prodigy 20 points

Hi,

thank you for reply I am using simplelink_cc13xx_cc26xx_sdk_6_20_00_29 sdk version

Is there any way to make adv visible to phone, or any step am I missing? I am asking this because I don't have any sequence for this I just followed steps in internet.

0 Evan Wakefield 11 months ago in reply to Pavan Pinapatruni

TI__Mastermind 38580 points

Hi Venkata,

It's possible that the phone is filtering directed advertisements. There are a number of filter options supported in Bluetooth. You can find some of the options we have which are reflections of the Bluetooth LE specification: https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_6_40_00_13/docs/ble5stack/ble_user_guide/html/ble-stack-5.x/gap-cc13xx_cc26xx.html#filter-by-ll-filter-policy

I would review your mobile device manufacturers Bluetooth libraries to understand what options you might have and start here first.

Bluetooth®︎

Bluetooth forum

CC2642R-Q1: Direct Advertisement Procedure