LAUNCHXL-CC26X2R1: Advertisement Packet and interval related queries

Rakesh Rajbhar

Intellectual 630 points

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I am working on cc2642 and for that, I am using LAUNCHXL-CC26X2R1.

I am using the below IDE and SDK.

- CCS 9.2.0

- simplelink_cc13x2_26x2_sdk_3_30_00_03

- using simple_peripheral_oad_onchip as a base code.

I want to send data in the advertisement packet at every 1 minute after the advertisement device will go in sleep.

I have configured the timer for 1 minute and after the timer expires am sending the updated advertisement packet.

I have attached the test file for your reference(Includes necessary functions only, not compilable).

I have below queries

1) Is my implementation correct for sending an updated packet at every 1 minute(although it works fine).

-> able to see updated packet on ble scanner app on every 1 minute.

-> but in my application central device is cc2642, in scanning mode.

2:) How GapAdv_enableOptions_t options in GapAdv_enable are different than the advertising interval which is configured in sysconfig primIntMin and primIntMax ?

-> In my application GapAdv_enable will be called only once so, after calling GapAdv_loadByBuffer(ADV_DATA2_LEN, advData1); my device will advertise until again timer expires.

-> primIntMin and primIntMax can be configured for about 10s only.

-> so how my device will go in sleep? when it is not advertising.

-> do I need to implement one more timer which disables advertising after some amount of time disables advertisement by calling GapAdv_disable?

3) in scanning side cc2642 which is in scanning mode, getting lots of packets and its hard to differentiate.

-> tried to use duplicate filtering enable the option, but no luck.

Please let me know if you need more information.

Thanks

over 5 years ago

0 Eirik V over 5 years ago

TI__Guru 56590 points

Hello Rakesh,

At first glance it looks ok.

advParams1 is generated from sysconfig into the file ti_ble_config.c that reside in the output build folder /syscfg.

primIntMin and primIntMax is bound by the Bluetooth Core SIG specification:

Bluetooth SIG Core Spec

The Idle thread and power driver will automatically set the device in standby if there are no ongoing operations (clock can tick automatically based on 32 kHz source while in standby):

http://dev.ti.com/tirex/explore/node?node=ALJuvum8Y71exvwoPdK5-g__pTTHBmu__LATEST

You can read up on use of white list in the Users Guide:

dev.ti.com/.../privacy.html

0 Rakesh Rajbhar over 5 years ago in reply to Eirik V

Intellectual 630 points

Hi Eirik,

Thanks for the prompt response,

I will read all these links and let you know if I will need any further help regarding those queries.

I have one more question regarding sysconfig.

-> As sysconfig generates ti_ble_config.c and defines and initialize advData1 array, and it defines its size in ti_ble_config.h (extern uint8_t advData1[30];), this size can be increased if i use more advertype ,

i want to send user data after manufacturer-specific adverttype, but its assigns only 2 bytes for user manufacturer id so how can i assign more length to advertData.

0 Rakesh Rajbhar over 5 years ago in reply to Rakesh Rajbhar

Intellectual 630 points

Hi, Any update on the above question?

0 Eirik V over 5 years ago in reply to Rakesh Rajbhar

TI__Guru 56590 points

0 Rakesh Rajbhar over 5 years ago in reply to Eirik V

Intellectual 630 points

Thanks, Eirik its worked!!!

0 Rakesh Rajbhar over 5 years ago in reply to Eirik V

Intellectual 630 points

Hi Eirik,

I have found one issue in sysconfig(SDK :- simplelink_cc13x2_26x2_sdk_3_30_00_03) while using it as you mentioned above.

There is a mistake in sysconfig related to the length of the data.

Case 1:

If we give "Additional data" field 0xAABBCCDDEE it will count, the length of the data as 0x08(line number 105) and it will generate the file with array initialized with 0x08 length for additional data including the length of the manufacturer-specific bytes so it is correct for this case.

case 2:

If I give the "Additional data" field 0xAABBCCDDEEFF00112233445566 so the length of the actual data will be (Manufacturer-specific Type + Company identifier + Additional data ) (1 + 2 + 13 = 16) so here in sysconfig it takes as 0x16 which is actually 22(in decimal)

And this difference in length creates the issue in an advertisement, the device is not advertising anymore.

0 Eirik V over 5 years ago in reply to Rakesh Rajbhar

TI__Guru 56590 points

It seems to be fixed in simplelink_cc13x2_26x2_sdk_3_40_00_02. Can you check?

0 Rakesh Rajbhar over 5 years ago in reply to Eirik V

Intellectual 630 points

Hi Eirik,

Currently, it is not possible for me to check the new SDK. the issue is fixed for me but I just wanted to flag the issue.

Bluetooth®︎

Bluetooth forum

LAUNCHXL-CC26X2R1: Advertisement Packet and interval related queries