CC2340R5: I don't get any notifications when i write the value from central(cc1352) to peripheral(cc2340)

Hi !

If this works fine with the nRFConnect app, then the issue is probably from the CC1352 central. Did you use an example from the SDK to kickstart your project ? The chapter about GATT for user guide for the CC13XX_CC26XX SDK mentions that you need two things :
- Call GATT_RegisterForInd(selfEntity) initially (this is done in the SimpleCentral_init function in the SimpleCentral example of the SDK) 
- Add a filter for ATT_HANDLE_VALUE_NOTI events in your GATT handler (this is done in SimpleCentral_processGATTMsg in the SimpleCentral example of the SDK)
- Enable notifications by writing to the CCCD characteristic of the peripheral.

I would advise you to check if those steps are done in your project.

Additionally, the reason why the nRFConnect app may be because the nRF app tries to read all characteristics upon a connection to cache its value. If some characteristics have a authentication requirement, this will prompt the passkey. 

Kind regards,
Maxence

Dear Lea 
Thanks for the quick response,

1. I am working with:
   • Code Composer Studio: 12.0.0
   • SDK: simplelink_cc13xx_cc26xx_sdk_7_40_00_77
   • Example project: simple_central_CC1352R1_LAUNCHXL_tirtos7_ticlang
2. GATT_RegisterForMsgs(selfEntity);
   This function is available in SimpleCentral_init.
   
   
3. ATT_HANDLE_VALUE_NOTI is not handled in the default simple_central example, but I have modified
   static void SimpleCentral_processGATTMsg(gattMsgEvent_t *pMsg) as follows:

else if (pMsg->method == ATT_HANDLE_VALUE_NOTI)
    {
      attHandleValueNoti_t *n = &pMsg->msg.handleValueNoti;
      char line[3*ATT_MTU_SIZE+32];
      uint16_t off = 0;
      off += snprintf(line+off, sizeof(line)-off, "NOTI h=0x%04x len=%u: ", n->handle, n->len);
      for (uint16_t i = 0; i < n->len && off+3 < sizeof(line); i++)
        off += snprintf(line+off, sizeof(line)-off, "%02X ", n->pValue[i]);
      Display_printf(dispHandle, 0, 0, "%s", line);
    }
    else if (pMsg->method == ATT_HANDLE_VALUE_IND)
    {
      attHandleValueInd_t *ind = &pMsg->msg.handleValueInd;
      char line[3*ATT_MTU_SIZE+32];
      uint16_t off = 0;
      off += snprintf(line+off, sizeof(line)-off, "IND  h=0x%04x len=%u: ", ind->handle, ind->len);
      for (uint16_t i = 0; i < ind->len && off+3 < sizeof(line); i++)
        off += snprintf(line+off, sizeof(line)-off, "%02X ", ind->pValue[i]);
      Display_printf(dispHandle, 0, 0, "%s", line);
      ATT_HandleValueCfm(pMsg->connHandle);
    }

Please guide me find the mistake if i made.

regards
Surya

Hi !

Do you enable notifications by writing 0x01 0x00 to the CCCD of your notification characteristic ?

Kind regards,
Maxence

Hi Lea 
yes, i do as follows 

Function

if case is 
else if (discState == BLE_DISC_STATE_CHAR)

logic is 

Hi,

Do you have access to a sniffer ? That would be very useful for us to know if the notification is actually being sent by the peripheral.

If you don't have a sniffer, you can also send me the project folder for your central and peripheral, assuming that they can both be flashed on a launchpad so that I can reproduce your issue.

If your code for the peripheral and central cannot run on 2 launchpads, then you could try making a minimum reproducible example that I can have a look at.

Kind regards,
Maxence

Dear Lea 

Thank you for your continued support. I tested with a third-party peripheral device, so I don’t have the peripheral’s code. They suggested using only the nRF application, which works fine. However, I’m trying to implement the same functionality on a CC1352-based board (our own device). I can share my full project files for your review—please go through them and point out any mistakes or anything I may have missed.

Regards,
Surya

Hi,

You add me as a friend in the E2E forums and then you'll be able to send me your code in private messages once I accept your request.
I will test your code on the basic ble example of a CC2340 and see if I can reproduce your issue.

Kind regards,
Maxence

Hi,
Please accept the friend request.

regards
Surya

Hi, sorry but I did not receive a friend request. Could you re-try ?

Hi Lea 

i have resend the request, please check...



regards
Surya

Hi,

I added you

KR, Max

Hi,
Please check the personal message, i have shared my complete project file for your review.

regards
Surya

Hello Surya,

Unfortunately, Maxence is out of office for the next few weeks. However, I can help you out. If you could send me your project I can attempt to review it myself!

Best Regards,

Tarek D

Hello Tarek D 
Please accept the friend request.

regards
Surya

Hi Tarek D,
Please review the shared project file in personal message and let me know if I’ve made any mistakes, and advise me on how to resolve the issue.

Regards
Surya

Hello Surya,

Sounds good! i will take a look at it and get back to you. Expect an update by Tuesday!

Best Regards,

Tarek D

Hi Tarek D 
I hope you checked the shared code, please let me know the status.

Regards
Surya

Hello Tarek D 

Any update on my request???

Regards

Surya

Hello Surya,

Apologies for the delay here! I was able to take a look at your code, however I'm afraid the code has been modified too much to work with our generic basic_ble peripheral and will require a custom peripheral.

Since you mentioned that you don't have the peripheral project, could you send me .hex or .out file that I can flash the CC2340 with to be able to further analyze this code?

Best Regards,

Tarek D

Hello Tarek D 

• Please ignore the code I previously shared. I need the CC1352 to start scanning automatically on power-up, list all discovered devices with their addresses, send a connection request, perform passkey pairing, and then read the advertising data. You may provide a working example in your own style or guide me step by step to achieve this.

• I don’t have the CC2340 peripheral code. The instrument is from a third party, and their company policy does not allow them to share the firmware in any format.
  
  
  
  Regards
  Surya

Hi Tarek D Lea 

Any Update????



Regards
Surya

Dear Tarek D 
It's okay — I didn't get a response for the last 10 days, so I thought to move the CC1352 peripheral to a Raspberry Pi and ordered one online; it's currently in transit. Thanks for your reply. You shared the steps for a 16-bit UUID, but my device uses a 128-bit UUID. I'll try to modify the code for the 128-bit UUID and let you know the result. Thanks again for the suggestions.

Regards
Surya

Hello Tarek D 
As instructed, I attempted to change the following macro in ti_ble_config.h:

// TRUE to filter discovery results on desired service UUID
#define DEFAULT_DEV_DISC_BY_SVC_UUID    false

I changed it from false to true, but the change is automatically reverted when I build the project. I checked the SysConfig file for this setting but could not find it, so I redefined the macro in simple_central.c:

#undef DEFAULT_DEV_DISC_BY_SVC_UUID
#define DEFAULT_DEV_DISC_BY_SVC_UUID  true

I called the scan function at the end of SimpleCentral_init() and added an else branch to handle devices without the target UUID:

if (SimpleCentral_findSvcUuid128(pAdvRpt->pData, pAdvRpt->dataLen))
{
    SimpleCentral_addScanInfo(pAdvRpt->addr, pAdvRpt->addrType);
    Display_printf(dispHandle, SC_ROW_NON_CONN, 0,
                   "Discovered: %s", Util_convertBdAddr2Str(pAdvRpt->addr));
}
else
{
    char bdAddrStr[18];
    snprintf(bdAddrStr, sizeof(bdAddrStr), "%s", Util_convertBdAddr2Str(pAdvRpt->addr));
    Display_printf(dispHandle, 0, 0,
                   "NON_UUID_Discovered: %s:%s\r\n",
                   Util_convertBdAddr2Str(pAdvRpt->addr),
                   bdAddrStr);
}

The output prints only addresses. The cleaned log (control sequences removed) is below.

Initialized
Num Conns: 0
ID Addr: 0xFCA89BECB290
RP Addr: 0x46D282B625F4
*Simple Central*
Stop Discovering
Discovering...
NON_UUID_Discovered: 0x4340E9CD877A:0x4340E9CD877A
NON_UUID_Discovered: 0x49724D900285:0x49724D900285
NON_UUID_Discovered: 0x40791213A330:0x40791213A330
NON_UUID_Discovered: 0x707F5D1604C8:0x707F5D1604C8
NON_UUID_Discovered: 0x77FA82DD2698:0x77FA82DD2698
NON_UUID_Discovered: 0x50DAE68BE6AC:0x50DAE68BE6AC
RP Addr: 0x424704CFDBEE

Note: In previous code, after finding a known device address we call the following to connect and get UUID details:

if (knownPeerFound)
{
    knownPeerFound = false;

    uint8_t pairMode = GAPBOND_PAIRING_MODE_INITIATE;
    GAPBondMgr_SetParameter(GAPBOND_PAIRING_MODE, sizeof(uint8_t), &pairMode);
    uint8_t bondingEnabled = TRUE;
    GAPBondMgr_SetParameter(GAPBOND_BONDING_ENABLED, sizeof(uint8_t), &bondingEnabled);

    eraseBondByAddr(knownPeerAddrType, knownPeerAddr);

    status_t status = GapInit_connect(knownPeerAddrType & MASK_ADDRTYPE_ID,
                                      knownPeerAddr,
                                      DEFAULT_INIT_PHY,
                                      CONNECTION_TIMEOUT);

    if (status == SUCCESS)
    {
        Display_printf(dispHandle, 0, 0, "Connecting to FM_ADDR...");
    }
    else
    {
        Display_printf(dispHandle, 0, 0, "Connect failed");
    }

    break;
}

Please check and let me know what I should do next. my known device address is 

Regards
Surya

Dear Tarek D 

Thanks for your suggestions. I’ll explain what I need.

I am trying to connect to a CC2340-based flowmeter that uses a secure connection with a passkey.

I call GapScan_enable(0, 0, 0); at the end of SimpleCentral_init() so devices are listed when the system powers up. The advertisements are handled in SimpleCentral_processAppMsg() under case SC_EVT_ADV_REPORT:.

Because I couldn't find the macro in SysConfig, I redefined it as follows:

#undef DEFAULT_DEV_DISC_BY_SVC_UUID
#define DEFAULT_DEV_DISC_BY_SVC_UUID true

With that change I discover devices and handle them like this:

if (SimpleCentral_findSvcUuid128(pAdvRpt->pData, pAdvRpt->dataLen))
{
  SimpleCentral_addScanInfo(pAdvRpt->addr, pAdvRpt->addrType);
  Display_printf(dispHandle, SC_ROW_NON_CONN, 0, "Discovered: %s", Util_convertBdAddr2Str(pAdvRpt->addr));
}
else
{
  char bdAddrStr[18];
  snprintf(bdAddrStr, sizeof(bdAddrStr), "%s", Util_convertBdAddr2Str(pAdvRpt->addr));
  Display_printf(dispHandle, 0, 0, "NON_UUID_Discovered: %s:%s\r\n", Util_convertBdAddr2Str(pAdvRpt->addr), bdAddrStr);

  if (strcmp(bdAddrStr, FM_ADDR) == 0)
  {
    GapScan_disable();
    GapInit_connect(pAdvRpt->addrType & MASK_ADDRTYPE_ID, pAdvRpt->addr, DEFAULT_INIT_PHY, 0);
    Display_printf(dispHandle, SC_ROW_NON_CONN, 0, "Auto connecting to %s", bdAddrStr);
    SimpleCentral_addScanInfo(pAdvRpt->addr, pAdvRpt->addrType);
  }
}

I manually call the connect API as shown above. I then get GAP_LINK_ESTABLISHED_EVENT and see the connected message (Num Conns: 1).

The code then goes into SimpleCentral_processPairState() and reaches the GAPBOND_PAIRING_STATE_ENCRYPTED branch:

else if (state == GAPBOND_PAIRING_STATE_ENCRYPTED)
{
  if (status == SUCCESS)
  {
    Display_printf(dispHandle, SC_ROW_CUR_CONN, 0, "Encryption success");
    uint16_t pairConn = pPairData->connHandle;
    bStatus_t pairStatus = GAPBondMgr_Pair(pairConn);

    if (pairStatus == SUCCESS)
    {
      Display_printf(dispHandle, SC_ROW_CUR_CONN, 0, "Pairing initiated on connHandle=0x%04x", pairConn);
    }
    else
    {
      Display_printf(dispHandle, SC_ROW_CUR_CONN, 0, "Pairing initiation failed, GAPBondMgr_Pair returned=0x%02x", pairStatus);
    }

    Display_printf(dispHandle, SC_ROW_CUR_CONN, 0, "pPairData->connHandle=0x%04x pPairData->status=0x%02x",
                   pPairData->connHandle, pPairData->status);
  }
  else
  {
    Display_printf(dispHandle, SC_ROW_CUR_CONN, 0, "Encryption failed: %d", status);
  }

  GAPBondMgr_GetParameter(GAPBOND_PAIRING_MODE, &pairMode);

  if ((autoConnect) && (pairMode == GAPBOND_PAIRING_MODE_INITIATE))
  {
    SimpleCentral_autoConnect();
  }
}

I modified this function to handle pairing, but pairing fails.

Could you please guide me on how to initiate the connection with a passkey and complete pairing with the CC2340 flowmeter? Specifically, I need recommendations on:

• Where/how to supply the passkey during the pairing process.

• Any required GAPBondMgr configuration or callbacks to implement.

• Typical mistakes that cause pairing to fail in this flow (e.g., wrong pairing mode, missing IO-capability settings, address type mismatches).

Thanks in advance for your help.

Best regards,
Surya

Dear Team,
Please respond to my quires!!!!

regards
Surya

Dear Tarek D 

I enabled GAPBondMgr in SysConfig, but it did not initiate automatically. please advise how I can manually initiate pairing. Also, how can I obtain the connection handle (connHandle) required by the GAPBondMgr_Pair() function?

Please review my previous reply where I explained, step by step, what I tried and where it failed.

regards
Surya

Dear Tarek D ,

I received a GAP_LINK_ESTABLISHED_EVENT and can see numConn = 1 and the device address from the handler below. However, I’m unsure how to retrieve the connHandle for that connection. Could you please confirm the proper way to obtain or map the connection handle for the device (or point out where I should read it from in the event structure)?

Connected to 0x40791213A330
Num Conns: 1

For reference, the handler I’m using is the GAP_LINK_ESTABLISHED_EVENT case in SimpleCentral_processAppMsg().

Thanks,
Surya