• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 426 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.

Original question:

CC2652R7: Periodic advertisement waveform of broadcaster.

CC2652R7: Periodic Advertiser setup

Garvit Periwal
Prodigy 210 points
Part Number: CC2652R7
Other Parts Discussed in Thread: ENERGYTRACE,

1) I have setup the device in periodic advertisement mode using the information in this thread - Link . While detecting it on a sniffer, I am receiving an error which indicates some issue with - Aux_Sync_Ind packet. How do I rectify this ? PFA the project I am using.

2) I want to calculate the energy consumption from these boards while working in periodic advertising mode. Currently the device is sending out ADV_EXT_IND and AUX_ADV_IND again and again after the specified advertising interval, I want to setup these boards such that when a scanner device has detected the periodic advertiser, it should stop sending out the above 2 indications and only AUX_SYNC_IND are sent after that. Basically I want the device to be registered with the scanner and just send out the sync packets after that.  How do I achieve this?

3) How to control the time interval between AUX_SYN_IND packets?

1830.simple_peripheral_LP_CC2652R7_tirtos7.zip

Regards,

Garvit

  • 0
    TI__Guru** 101460 points

    Hi Garvit,

    1) The issue with the packet is not obvious to me. Would you mind pointing more specifically to the "malformation"?

    2) Energy estimation can be done using EnergyTrace.
    Periodic Advertising does not enable communication from the scanner to the advertiser. It is then not possible for the advertiser to know a device is synchronized.

    3) This parameter can be set at the advertising set creation

        // Set event mask for set #3
  status = GapAdv_setEventMask(advHandleNCNS,
                               GAP_ADV_EVT_MASK_START_AFTER_ENABLE |
                               GAP_ADV_EVT_MASK_END_AFTER_DISABLE |
                               GAP_ADV_EVT_MASK_SET_TERMINATED);

  // Enable non connectable & non scannable advertising for set #3
  status = GapAdv_enable(advHandleNCNS, GAP_ADV_ENABLE_OPTIONS_USE_MAX , 0);
  
  // Set Periodic Advertising parameters
  GapAdv_periodicAdvParams_t perParams = {PERIDIC_ADV_INTERVAL_MIN,
                                                PERIDIC_ADV_INTERVAL_MAX, 0x40};
  status = GapAdv_SetPeriodicAdvParams(advHandleNCNS, &perParams);

    I hope this will help,

    Best regards,

  • 0 in reply to Clément
    Prodigy 210 points

    Hi Clement,

    Thanks for the quick response, Even I am not sure what the malformed packet means here. This is all I could see on the sniffer log - 

    Regarding the 2nd point, is it possible to achieve that state with the recently introduced PAwR advertising mode?

    Thanks,

    Garvit

  • 0 in reply to Garvit Periwal
    TI__Guru** 101460 points

    Hi,

    Do you manage to reproduce the malformed packet issue with other sniffers? The details provided by this sniffer are so limited that I cannot see what is wrong :/

    I am not sure it is Bluetooth compliant to stop advertising the extended advertisement when using Periodic Advertising. On the top of this, what would happen in case the sync is lost?
    I see you mentioned PAwR - PAwR is not meant to be used for this purpose either.

    Best regards,

  • 0 in reply to Clément
    Prodigy 210 points

    Clement are these information useful for debugging - 

    In few of the trials, I can see this information as well - "length of contained item exceeds length of containing item" 

    Regarding the loss of sync in periodic advertisements - Is their any criteria on how many packets a scanning device needs to miss to lose the synchronization or it happens as soon as a single sync packet is missed?

    Thanks,

    Garvit

     

  • 0 in reply to Garvit Periwal
    TI__Guru** 101460 points

    Hi Garvit,

    I am afraid I do not manage to reproduce the malformed issue with the Ellisys sniffer. I am not sure if this is caused by different parameters on my side or by the sniffer used. Could you please build for me an hexfile I can flash on the LP-CC2652R7 that reproduces the issue on your side?

    Garvit Periwal said:
    Regarding the loss of sync in periodic advertisements - Is their any criteria on how many packets a scanning device needs to miss to lose the synchronization or it happens as soon as a single sync packet is missed?

    The periodic synchronization timeout parameter (cf. BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 4, Part E, §7.8.67) defined when creating the sync (on the scanner side) is used to define when the sync is considered as lost.

    I hope this will help,

    Best regards,

  • 0 in reply to Clément
    Prodigy 210 points

    Hi Clement,

    Here is the hex file you asked for - 

    8510.Release.zip

    Thanks,

    Garvit

  • 0 in reply to Garvit Periwal
    TI__Guru**** 217467 points

    Hi Garvit,

    Clement is currently on holiday from Friday, May 17th to Monday, May 20th and will be returning to answer forum posts on Tuesday, May 21st in the order and priority in which they were received.  Thank you for your patience.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Intellectual 2880 points

    Hi Garvit,

    The packet is correctly formed; however, as you can see in the screenshot below, you're missing the field "Length" and "AD Type" before transmitting "PeriodicAdv" as described in the BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 3, Part C section 11 ADVERTISING AND SCAN RESPONSE DATA FORMAT.

    I hope this will help,

    Tanguy