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

CC1352P: Peripheral device getting disconnected from central

Venu Aditya
Prodigy 40 points
Part Number: CC1352P
Other Parts Discussed in Thread: SIMPLELINK-CC13X2-26X2-SDK

Hi,

I'm using CC1352R1(peripheral) REV C and CC1352P1(central) REV E. When I run the peripheral and central examples from the sdk on respective launchpads(V2.4 for peripheral and V3.1 for central), the peripheral is getting disconnected. But it seems central device "doesn't know" about the disconnection as it is not printing "device address is disconnected" which is in GAP_LINK_TERMINATED_EVENT case. It seems this is the only way the central device knows that the peripheral is disconnected.

Is it a bug in the stack? If not, how to overcome it?

  • 0
    TI__Genius 14845 points

    Hi Venu,

    I will try and reproduce the issue. I will post an update as soon as I can. 

    Thanks,
    Elin

  • 0
    TI__Genius 14845 points

    Hi Venu, 

    Are you using the default simple_peripheral and simple_central from the SDK, or have you added your own logic?

    There is a newer SDK available here: http://www.ti.com/tool/SIMPLELINK-CC13X2-26X2-SDK
    Can you test the simple_peripheral and simple_central projects from the newest SDK and see if you see the same issue?

    Thanks, 
    Elin

  • 0 in reply to Elin W
    Prodigy 40 points

    Hi Elin,

    Sorry for the late reply. I've been waiting for the hardware to arrive at my desk. 

    So here is what I've done. 

    I've used the latest version of SIMPLELINK-CC13X2-26X2-SDK i.e v3.3. I've imported the simple central and simple peripheral codes to my custom hardware boards which are based on CC1352R1. In the central device I've made the the following changes(purpose for making those changes is to connect to the peripheral device automatically without using the buttons as done in the example):

    -> when the device is initialized, it goes into  GAP_DEVICE_INIT_DONE_EVENT of SimpleCentral_processGapMsg() function. There I am calling the SimpleCentral_doDiscoverDevices(1) API

    -> In SC_EVT_ADV_REPORT case of SimpleCentral_processAppMsg() function, I've used Simple_doConnect(1) API if the MAC address matches my desired peripheral's MAC ID.

    -> In GAP_LINK_ESTABLISHED_EVENT case of SimpleCentral_processGapMsg() function, I used SimpleCentral_doConnectconn(0).

    By doing this the central device should connect to the peripheral automatically without using buttons which was working fine with 3.1 sdk in the custom hardware. 

    But,

    In 3.3 sdk central device is discovering and connecting but immediately disconnecting. How do I destroy this monster. 

  • 0 in reply to Venu Aditya
    TI__Genius 14845 points

    Hi Venu, 

    This looks like a different issue than you originally had. Did you try using your modified projects on the Launchpads?

           If yes; did you get the same result?
           If not; can you flash the applications and see if you see the same issue using the launchpads?

    Thanks, 
    Elin