CCS/LAUNCHXL-CC1352R1: Multi_role receive characteristic value with GetParameter

Hi Elin,

In setting the characteristic value, you will need to break it up by each byte and store it into a byte array. For example:

uint8_t Sensor1[SENSOR1_CHAR_LEN] = {0xD2, 0x04, 0x00, 0x00}; // 1234 in hex 0x04D2
                                                              // SENSOR1_CHAR_LEN is the length of your characteristic 
                                                              // since you had it as a uint32_t it would be 4 or sizeof(uint32_t)

AdcService_SetParameter(AS_SENSOR_1_ID, SENSOR1_CHAR_LEN, &Sensor1);

If you haven't yet, you will also need to make changes in your ReadAttrCB function in your profile to something similar to this:

      case AS_SENSOR_1_ID:
        *pLen = SENSOR1_CHAR_LEN;
        VOID memcpy( pValue, pAttr->pValue, SENSOR1_CHAR_LEN);
        break;

I would highly suggest you look at how SIMPLEPROFILE_CHAR5 is setup in simple_gatt_profile.c (simplelink_cc13x2_sdk_1_60_00_29\source\ti\ble5stack\profiles\simple_profile\cc26xx) and simple_gatt_profile.h (simplelink_cc13x2_sdk_1_60_00_29\source\ti\ble5stack\profiles\simple_profile). That characteristic is setup to send 5 bytes. You will basically want to copy that structure for your characteristics when it is more than a byte.

Now when using multi_role to read the characteristic from simple peripheral, you can't use AdcService_GetParameter. All that is doing is retrieving the characteristic values from multi_role's own GATT table. Instead you will need to use GATT_ReadCharValue as originally used in the multi_role_doGattRead function. When a readRsp is received in multi_role_processGATTMsg, that's where you'll need to process the read data. The following is what I am referring to in the multi_role_processGATTMsg function. I've added an example of what change you'd have to do to receive a characteristic of more than a byte:

static uint8_t multi_role_processGATTMsg(gattMsgEvent_t *pMsg)
{
 //...
 // Messages from GATT server
  if (linkDB_Up(pMsg->connHandle))
  {
    if ((pMsg->method == ATT_READ_RSP)   ||
        ((pMsg->method == ATT_ERROR_RSP) &&
         (pMsg->msg.errorRsp.reqOpcode == ATT_READ_REQ)))
    {
 //...
      else
      {
        uint32_t charReadValue = 0;
        // After a successful read, display the read value        
        if(pMsg->msg.readRsp.len == sizeof(uint32_t)){                   
          charReadValue = BUILD_UINT32(pMsg->msg.readRsp.pValue[0], pMsg->msg.readRsp.pValue[1], 
                          pMsg->msg.readRsp.pValue[2], pMsg->msg.readRsp.pValue[3]);
                         // Since the characteristic is sent per byte, you will need to reconstruct it to be 4 bytes
        }
        
        Display_printf(dispHandle, MR_ROW_CUR_CONN, 0, "Read rsp: %d", charReadValue);
      }
//...

I'd also highly suggest going through the Custom Profile SimpleLink Academy training. This will go through exercise that will help you understand this process: http://dev.ti.com/tirex/#/?link=Software%2FSimpleLink%20CC13x2%20SDK%2FSimpleLink%20Academy%2FBluetooth%205%2FCustom%20Profile

-Sy Su

Hi,

Thanks for the reply.

I’ve checked both the simple_gatt_profile.h/c several times and the Custom Profile without understanding how to solve my issue.

What’s the point of changing the code in ReadAttrCB? This is the code generated in Bluetooth Developer Studio:

    case AS_SENSOR_1_ID:
      valueLen = as_Sensor_1ValLen;

      Log_info4("ReadAttrCB : %s connHandle: %d offset: %d method: 0x%02x",
                 (IArg)"Sensor_1",
                 (IArg)connHandle,
                 (IArg)offset,
                 (IArg)method);
      /* Other considerations for Sensor 1 can be inserted here */
      break;

So do I call ReadAttrCB because I never enter it? And how do I call GATT_ReadCharValue? I don’t see how to link that function to my characteristics.

BR

Elin

Hi Sy Su,

Can I send you my workspace in a private message?

I don't understand how to solve the problem and it doesn't help when I try and change my service files.

BR
Elin

Hi Elin,

Have you already gone through all of the Bluetooth training modules in SimpleLink Academy to get an understanding of Bluetooth and the stack?
dev.ti.com/.../overview.html

In addition to that, reading through the Developing a Bluetooth Low Energy Application section in the stack's User's Guide: dev.ti.com/.../index-cc26x2.html

You are welcome to post your project so far in this thread.

-Sy Su

Hi Sy Su,

I have not gone through all training modules but I've read all of them and completed some of them.

I do not wish to post my project publicly since this can cause problems for this project in the future.

How is the charHandle changed to one of the sensors? Right now it isn't a handle to any of my characteristics since it does not enter "if(pMsg->msg.readRsp.len == sizeof(uint32_t))".

How is the charReadValue reconstructed in multi_role_processGATTMsg?

BR Elin 

Hi Sy Su, 

When I change the UUIDs for the service and the characteristic, the option "Read GATT" and "Write GATT" disappears from the options when working with a device. Can you help with that? 

Here is the project: ble5_multi_role_cc13x2r1lp_app.zip

BR Elin 

Elin,

The cause of this is occurring here in multi_role_doSelectConn: 

  if (connList[index].charHandle == 0)
  {
    // Initiate service discovery
    multi_role_enqueueMsg(MR_EVT_SVC_DISC, (void *)index);

    // Diable GATT Read/Write until simple service is found
    itemsToDisable = MR_ITEM_GATTREAD | MR_ITEM_GATTWRITE;
  }

Can you confirm you are getting a valid charHandle for your characteristic AS_SENSOR_1 in here?

      connList[connIndex].charHandle
        = BUILD_UINT16(pMsg->msg.readByTypeRsp.pDataList[3],
                       pMsg->msg.readByTypeRsp.pDataList[4]);

-Sy Su

Okay, so by removing that it should work?

Probably not since they are unchanged. How can I check that?

Elin

Elin,

You can check if they are changed or not by looking at my second question in my last post:

Check to see if you are receiving a valid charHandle at this point in your code. Search for the following lines, set a breakpoint and check the value of it while debugging the code. If you look through the code, the charHandle is initialized as 0 so if it is still 0 after the charHandle is stored then it is invalid.

connList[connIndex].charHandle
  = BUILD_UINT16(pMsg->msg.readByTypeRsp.pDataList[3],
                 pMsg->msg.readByTypeRsp.pDataList[4]);

-Sy Su