• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 1545 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/CC2640R2F: How to enable ADV_EXT_IND with BLE5

Jon Richards
Prodigy 200 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2540

Tool/software: Code Composer Studio

I am using the LAUNCHXL-CC2640R2 with CCS 7.4.0.00015. Using simplelink_cc2640r2_sdk_1_50_00_71. I got the ble5_simple_peripheral_cc2640r2lp_app building and working. Using the SmartRF Packet Sniffer, with a CC2540 Dongle,  I can see the advertisements of type "ADV_IND".

I wish to use ADV_EXT_IND so I can send advertisements with a larger payload. How can I enable this in the simple peripheral sample? I don't see any way to use the extended advertisement features of BLE5.

  • 0
    TI__Mastermind 33460 points
    Hello,

    The simple_peripheral application will advertise on AE (using ADV_EXT_IND ) on the long range PHY by default.
    This is supported out of the box. You can see the advertisements being enabled in the processing for GAP_DEVICE_INIT_DONE_EVENT.

    However, the issue is that you cannot snif advertising extension packets using the CC2540 dongle and Smart RF Packet Sniffer. This program/hardware does not support Bluetooth 5.0 or advertising extensions.
  • 0 in reply to Sean2
    Prodigy 200 points
    If the simple_peripheral was advertising ADV_EXT_IND, why can the dongle see packets of 31 bytes or less as ADV_IND advertisements? Does the simple_peripheral firmware automatically switch to ADV_EXT_IND when the packets are > 31 bytes?
  • 0 in reply to Jon Richards
    TI__Mastermind 33460 points
    simple_peripheral will use two advertising sets. One is a legacy advertisement that will contain 31B of data in an ADV_IND packet and can be detected by the CC2540 sniffer, the second set is AE on a long range PHY that the CC2540 cannot detect.

    The type of advertisement is set via the advertisement parameters and controlled via the stack. On AE advertisement types you can use packets > 31B on legacy types you are limited to 31.
  • 0 in reply to Sean2
    Prodigy 200 points

    Thank you, I see in the code now where it is configuring the legacy and extended advertising modes. 

    My iPhone X, with ios11, can see the legacy advertisements, but cannot see the the extended advertising packets. Do you have any idea if the iPhone X/BLE5 implementation of BLE5 should be able to receive the extended advertisement packets? Maybe they left this out of their implementation.

    Jon

  • 0 in reply to Jon Richards
    TI__Mastermind 33460 points
    Hi Jon,

    To my knowledge, the current CoreBluetooth module and current generation of phones do not support scanning for advertising extension packets. The specification is still fairly new an adoption time in the mobile devices can lag a bit.

    One thing to note is that even devices that are 5.0 compliant may or may not support AE.
    It would be best to double check on the apple forums and developer pages to see when this feature is coming.