• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 295 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.

LAUNCHXL-CC26X2R1: Coexistence Request pin Output signaling.

ASD D
Intellectual 360 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSCONFIG, , CC2640

I implement Coexistence feature in LAUNCHXL-CC26X2R1 board using Sysconfig Tool configuration ,and  I am using 1-wire request mode and use DIO7(Which is connected to led) for Request pin mapping.

After implementation I tested Request pin output During BLE advertisement period and BLE connected stage by Observing LED is connected to Request pin.

Observation:

If the advertisement interval is 5 sec then the request LED Blink with 5 sec delay (during advertisement period,not connected),

But in the connected stage of BLE Observe continuos LED blinking with around 100ms delay.

May I know what is the expected result in both connected stage and non connected stage from Request pin?

Note:simplelink_cc13x2_26x2_sdk_4_40_00_44 is used ,and IAR IDE is used

  • 0
    TI__Mastermind 42320 points

    Hi,

    Thank you for reaching out to us. The request pin is an output pin used to request use of the frequency band to perform any RF activity. In 1-wire request mode, the request signal will go active shortly before any RF activity is performed by the BLE side. Based on the provided information, it seems that the 100ms delay may be the connection interval selected for the connection. Can you verify if the connection interval is 100ms? If this is the case, then every time a connection event occurs there will be some RF activity which would correspond to the behavior you see.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Intellectual 360 points

    Hi,

    Thank you for the information,Below cases are confirmed.

    1.broadcast stage -> request pin toggle based on advertisement frequency.

    2.connected stage -> request pin toggles based on connection interval set.

    3.Connection establishment stage -> ?

     Observation:

    In connection establishment stage I observed request pin is toggling too frequently (when i compared with connected state).

    so based on which parameter, request pin is toggling in  connection establishment stage ?

    NOTE:

    For example: I tested with 500ms connection interval in connected state and I could observe toggling in 500ms. But in connection establishment state it is not 500ms( too frequent)

     

  • 0 in reply to ASD D
    TI__Mastermind 42320 points

    Hi,

    During connection establishment, the peripheral and the central devices perform some back and forth communication to configure the parameters necessary for the connection to the established. These events tend to happen very quickly. To verify this, I recommend taking a BLE sniffer trace as well as a logic trace of the device during connection establishment. You should see that the RF activity from the peripheral should correspond to the LED toggling.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Intellectual 360 points

    I have TI SmartRF sniffer ,but when I try to catch details during connection interval .

    Observation:

    There is no separate information for connection parameter configuration during connection establishment.only change I observe is Adv PDU type is changed.

    May I know how to view connection establishment details in TI SmartRF sniffer?I am new with this Tool.

    Is sniffer 2 is needed for this (currently I am using cc2640 dongle) ?

    May I know ,What is the time taken for performing configuration of the parameters necessary for the connection establishment?

  • 0 in reply to ASD D
    TI__Mastermind 42320 points

    Hi,

    The TI SmartRF sniffer can only sniff advertising packets. In this case, we need to sniff all the BLE traffic in order to determine what is going on exactly during connection establishment. To measure the BLE traffic, then you would need a dedicated BLE traffic sniffer such as an Ellisys or a Frontline sniffer. Having these sniffer will allow for greater debugging capabilities in BLE development. The time for connection establishment, should be the time between the connection is initiated and when the GAP_LINK_ESTABLISHED_EVENT is received on the device.

    Best Regards,

    Jan