• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 344 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SIMPLELINK-CC13X2-26X2-SDK: How to include the AdvA field in advertisement packets

Yuto Hori
Prodigy 400 points
Part Number: SIMPLELINK-CC13X2-26X2-SDK
Other Parts Discussed in Thread: CC2642R-Q1

Hi team,

Customer uses SIMPLELINK-CC13X2-26X2-SDK for CC2642R-Q1.

When sending Non-Connectable, Non-Scannable, Undirected advertisement packets over Coded(S8)PHY, is it possible to include the AdvA field in the Primary Packet(ADV_EXT_IND) and Secondary Packet(AUX_ADV_IND)?
　
If yes, please let us know how to set it up.

Your support is highly appreciated.

  • 0
    TI__Prodigy 251 points

    Hi Yuto,

    I'm currently looking how this could be made possible. Would you help me understand the reasoning behind the desire to send the advertiser’s device address in both ADV_EXT_IND and AUX_ADV_IND? Is there an issue where transmitting the advertiser’s device address in either ADV_EXT_IND or AUX_ADV_IND is not sufficient?

     

    In the Bluetooth Core Specification v5.3 Volume 6, Part B, 2.3.1.6 (page 2684) AUX_ADV_IND's Table 2.5 states that this field is optional if the corresponding field in the ADV_EXT_IND PDU is not present, otherwise it is reserved for future use. So I am thinking that it is not possible since the field is included in the ADV_EXT_IND PDU field in your described scenario.

    I can also point you to Volume 6, Part B, 2.3.1.5 (page 2682) that describes the available options for the ADV_EXT_IND PDU.

    Also, I am including a link to the site where you can download v5.3 of the Bluetooth Core Spec. for referencing as needed.
    https://www.bluetooth.com/specifications/specs/core-specification-5-3/

    Below is also a printout of the tables on those pages for convenience. 

  • 0
    TI__Prodigy 251 points

    Hey Yuto, 

    I am under the impression that this is currently set up in our simple_peripherial example in the SDK. Are you able to get into the non-connectable, non-scannable, unidirected, Coded S8 Phy mode? If so, the ADV_EXT_IND and AUX_ADV_IND packets should contain the AdvA field when using the simple_peripherial example. If it would be helpful I can include which parts of that example are relevant for enabling the AdvA field in both packets.