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

RTOS/CC2642R: Unable to scan and find again a peripheral after its succesfull bonding and first disconnection

Federico B
Intellectual 310 points
Part Number: CC2642R

Tool/software: TI-RTOS

Hi to everybody,
I have two open questions which I'm not able to solve..
I'm working with CC2642 and simplelink_cc13x2_26x2_sdk_2_40_00_81.
I'm using a SPhone as a Master and a peripheral board (multi_role software based).

First question:

After a succesfull bonding through password request, if I drop the connection through the SPhone, I will never be able to find (with a new scan) the peripheral again (the drop connection is recognize corretly from the peripheral).
The only ways I'm able to find it again is powering OFF-ON the peripheral or reflashing it.
However I have noticed this behaviour using Samsung S4 mini: if I use Huwawei Mate 20 Pro the peripheral still be visible even after a succesfull bonding and its first disconnection.
I remeber there was a similar issue with CC2642 and SDK 1_35_00_33, fixed later with a new SDK version...
Anyway, do you have any idea or suggestion to avoid this problem with some SPhone ?

Second question:

With every SPhone I have tryied, if I delete into the SPhone the bonding made with the peripheral and I try a new connection between the SPhone and peripheral, there isn't any password request event from SPhone side AND there isn't any pairing event from Peripheral side during the connection(once bonded with a SPhone I should receive at least the GAPBOND_PAIRING_STATE_ENCRYPTED for every connection made with it).

It seems like the bonding is saved into the peripheral even if i've delete it from SPhone side...
How is possible to avoid this behaviour?

Many thanks in advance,
Federico

  • 0
    TI__Mastermind 38980 points

    Federico,

    Problem 1) After disconnecting, do you re-enable advertising?

    Problem 2) You need to delete the bond information on the TI device side as well. 

  • 0 in reply to Evan Wakefield
    Intellectual 310 points

    Hi Evan,

    thanks for your help.

    Problem 1) Yes, after the disconnection event,  the Adv is re-enabled. I'm sure about it because with other SPhone the Peripheral still be visible and connectable(Only from the SPhone which it was made the bonding is  not visible anymore).

    Problem 2) If after a succesfull bonding I drop the connection between the SPhone and Perihperal and only after the disconnection I'm going to delete the bonding information on the SPhone, how can I understand from peripheral side that I have to delete the bonding information? may be during the next connection?

    In case for some resaons I don't delete the bonding information on TI device but only on the SPhone side, I'm expecting during the next connection (with the same SPhone) to receive on Peripheral device a "pairing event" (or something different) but not the behaviours "just works" as it working now. Otherwise I'm not able to understand if that SPhone connection is acceptable or not for me(safety matters).

    Thanks for your advise,

    Federico       

  • 0 in reply to Federico B
    TI__Mastermind 38980 points

    Federico,

    Can you confirm if you still see the same issue on the SDK 3.20? 

    Also, please confirm that you are using Rev E silicon. 

  • 0 in reply to Evan Wakefield
    TI__Mastermind 38980 points

    Also please provide a sniffer log of the behavior you've described in problem 2. Idealistically an Ellisys log if possible. 

    What is your IO CAP, bond and MITM settings set to?