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.

CC2640: The notification for the end of advertising on CC2640

Guru 16800 points
Part Number: CC2640
Other Parts Discussed in Thread: BLE-STACK

Hello,

Could you tell me the specification of the notification for the end of advertising from ICall on CC2640?

My customers found the notification from ICall despite there is no notification from the HCI layer.
It looks like unexpected behavior referring "Software Developer's Guide".
Their stack is v2.2.2 and they are using EWARM v8.0.

Best Regards,
Nomo

  • Hi Nomo,

    I don't understand your question. What is the name of the event you're referencing?
  • Hello Marie-san,

    I apologize to make you confused.
    They are checking the notification of HCI_EXT_AdvEventNoticeCmd and the notification of iCall for advertising.
    Despite the notification of HCI_EXT_AdvEventNoticeCmd, they can see the notification of iCall (Success).

    So, they want to know the specification of the notification of iCall.
    They think that it seems the notification of iCall for advertising only depends on the timer event.

    Best Regards,
    Nomo
  • Hi Nomo,

    I still don't understand anything. You can use HCI_EXT_AdvEventNoticeCmd() if you want to receive a SBP_ADV_CB_EVT every time an advertisement ends, but your device can advertise without receiving/subscribing to this event.

    If you want to make sure the device is advertising, you can use a sniffer or a smart phone with a BLE app.

    What are they trying to achieve?
  • Hello Marie-san,

    Thank you for your reply.
    They are trying to achieve combining simple_broadcaster and simple_observer.
    And they want to achieve advertising and scanning simultaneously.

    But sometimes advertising doesn't work correctly.

    Have you heard the failure for the system which is advertising and scanning simultaneously?

    Best Regards,
    Nomo
  • Hi Nomo,

    I would guess if the BLE-Stack wants to send an advertising packet at the same time as scanning (rx), it would cause an issue. What are the scanning and advertising parameters? (Scan duration, scan interval, scan window, advertising interval)
  • Hello Marie-san,

    Thank you for your reply.
    The parameters are following.

    Scan duration:
    They don't call GAP_DeviceDiscoveryCancel, it seems the scanning is working continuously.

    Scan interval: 512ms
    GAP_SetParamValue(TGAP_GEN_DISC_SCAN_INT, 512 / 0.625);

    Scan window: 20ms
    GAP_SetParamValue(TGAP_GEN_DISC_SCAN_WIND, 20 / 0.625);

    Advertising interval: 100ms
    GAP_SetParamValue(TGAP_GEN_DISC_ADV_INT_MIN, 100/0.625);
    GAP_SetParamValue(TGAP_GEN_DISC_ADV_INT_MAX, 100/0.625);


    Best Regards,
    Nomo
  • Hi Nomo,

    Scan window of 32 ms sounds like very little, are they able to discover the devices they want to?

    Maybe they should try setting the values less even, so that the advertising events will crash with the scan events less often?
  • Hello Marie-san,

    Thank you for your reply.
    I can understand it needs to adjust the settings such as scan window.

    Best Regards,
    Nomo