LAUNCHXL-CC26X2R1: Ble simple central example modified code gap termination event not generating?

Hi Vadivelan,

I'm not sure I understand your question entirely. What I think you're saying is that when you call the GapInit_connect function in your second code block, you are able to connect briefly, but then the connection is terminated and you aren't observing the GAP_LINK_TERMINATED_EVENT. Is that the problem you're seeing?

If so, it may be possible that your application is getting stuck somewhere that is making it unable to maintain the connection interval with your device. I would recommend debugging your project and pausing its execution when the connection is terminated. This may give you some insight into where the connection is breaking.

Best,

Nate

connection is happening and termination also happening perfectly but termination event not triggering 

Sorry for that, but what you said is not an issue !!

if possible please can we have one sync up now

To join the video meeting,

Hi Vadivelan,

Unfortunately we do not offer personal video debugging support. It would be impossible for us to be able to support all of our customers this way. If you want more hands on support, you'll have to go through your local field applications engineer.

You are more than welcome to share screenshots or describe your problems in greater detail. I will be happy to assist you and point you to the resources available to help you resolve your issue.

Best,

Nate

ok try to understand the issue 

 simple central scanning the particular devices  as bellow code we are receiving address of the device in this pAdvRpt->addr

case SC_EVT_ADV_REPORT:
{

GapScan_Evt_AdvRpt_t* pAdvRpt;
pAdvRpt = (GapScan_Evt_AdvRpt_t*) (pMsg->pData);

if( (*((pAdvRpt->pData)+2) == 0x41) || (*((pAdvRpt->pData)+2) == 0x4D) )
{

memcpy(&AddrLis, pAdvRpt->addr, B_ADDR_LEN);

GapScan_disable("");
// Establish a connection to the device
// GapInit_connect(pAdvRpt->addrType & MASK_ADDRTYPE_ID, pAdvRpt->addr,
// INIT_PHY_1M, 0);

 I'm copying that into buffer send the data to uart  another controller will receive and again it will send back same device address 

that address I'm collecting to the global buffer and then in uart read callback function inside  enqueued was called SC_CONN_EVT

this on i was created  

( SimpleCentral_enqueueMsg(SC_CONN_EVT,0, NULL);

 whenever the above function is called it's gonna trigger the below code 

  static void SimpleCentral_processAppMsg(scEvt_t *pMsg)
  {
    case  SC_CONN_EVT:
              {
                  uint8_t vs[4]={0};
                      vs[0]=0x65;
                      vs[1]=0x65;
                      vs[2]=0x65;

                     SendDataToUart(vs,sizeof(vs));
              uint8_t addrType=0x0;
                  GapInit_connect(addrType & MASK_ADDRTYPE_ID,addrr,INIT_PHY_1M,0);
                  break;
              }
    }

then connection happen and some parameter updates  after that I'm terminating the connection 

using gap_terminate function 

after terminate GAP_LINK_TERMINATED_EVENT:  gap event has to trigger but it's not triggering 

note(if I called gapinit_connect function inside the SC_EVT_ADV_REPORT means there is no problem not facing any issue )

now tell me?

Hi Vadivelan,

What function are you calling to terminate the connection? I see in simple_central you can use SimpleCentral_doDisconnect(), which should work. Once disconnected, you should observe a GAP_LINK_TERMINATED_EVENT triggered from the Stack Library. Perhaps you can pause execution of your code when this termination event happens to see where you code goes instead of the GAP_LINK_TERMINATED_EVENT case in SimpleCentral_processGapMsg?

Best,

Nate

What function are you calling to terminate the connection?

GAP_TerminateLinkReq(scConnHandle, HCI_DISCONNECT_REMOTE_USER_TERM);

I think still do not understand my question?

please check this one code follow let me know