CC2642R: Erroneous results with Find By Type Value request

Part Number: CC2642R

Tool/software:

Hello, I am an engineer at Zivix working on the Jamstik product which uses an Infineon bluetooth module. I am in communication with an engineer working on the Widi bud product using a TI CC2642R. Both products use the same BLE MIDI Service (UUID: 03B80E5A-EDE8-4B33-A751-6CE34EC4C700)

The Jamstik is a BLE peripheral, and the Widi Bud a BLE central.

I attempted to attach a wireshark capture to this thread, but I don't think it was successful. It shows an issue with Find By Type Value request. I have created a support ticket with Infineon and they believe their library is behaving correctly, and that this is an issue in the TI library. I would like to hear from you if you agree with that assessment.

From the wireshark capture

Frame 256: Widi Bud sends the "Find By Type Value Request, Primary Service, Handles: 0x0001..0xffff"

Frame 259: Jamstik responds with "Rcvd Find By Type Value Response"
Frame 260: Widi Bud sends "Find By Type Value request, Primary Service, Handles: 0x0014..0xffff"  (why not 0x0013?)
Frame 263: Jamstik responds with "Rcvd Find by type value response" for the entire group 0x0013-0x0016
The Widi Bud gets a failure here. The Widi engineer has shared this code with me, which is where the failure occurs

if(connList[connIndex].centralBLEState == BLE_STATE_DISCOVER_SERVICES

{

        // Service found, store handles

        if ((pMsg->method == ATT_FIND_BY_TYPE_VALUE_RSP) && (pMsg->msg.findByTypeValueRsp.numInfo > 0))

        {

            connList[connIndex].svcStartHdl = ATT_ATTR_HANDLE(pMsg->msg.findByTypeValueRsp.pHandlesInfo, 0);

            connList[connIndex].svcEndHdl   = ATT_GRP_END_HANDLE(pMsg->msg.findByTypeValueRsp.pHandlesInfo, 0);

        }

        // If procedure complete

        if (((pMsg->method == ATT_FIND_BY_TYPE_VALUE_RSP) && (pMsg->hdr.status == bleProcedureComplete)) || (pMsg->method == ATT_ERROR_RSP))

        {

          // services are discovered, discover now the characteristics

          startDiscoveringServicesAndChars(connIndex, BLE_DISC_STATE_CHAR_BY_UUID);

        }

}

  • Hi,

    Thank you for reaching out. Can you clarify which SDK version you are using as well as which example project you are working of? Can you try attaching the log in a reply to this message?

    Best Regards,

    Jan

  • Sorry about the delayed response. I emailed immediately, but the email has been bouncing back from TI. I'll copy and paste here.


    Here is the response from Jerome at Widi

    I’m using simplelink_cc13xx_cc26xx_sdk_6_41_00_17
    And I started from multi role project.
    I know there are newer versions of the SDK, but the last time I tried to upgrade there were some issues while booting the MCU.
  • Here's a link to the wireshark capture
    www.dropbox.com/.../widibud-studio.pcapng

  • Hi,

    Understood. There are several major SDK releases since the 6.41 release which may have had an impact on the beahvior. Can you share the issues you saw when booting from the MCU?

    Best Regards,

    Jan

  • Unfortunately we'll need to wait for Jerome at Widi to have more time. Here's his response:
    I can’t remember precisely what was the issue while booting.
    I did not spent too much time on this, as I was busy with other projects, and at that time, upgrading the SDK was not a priority.
    I’m currently still very busy, and I need to upgrade again the TI SDK, and reproduce the issue to investigate on what’s happening.
    I can work on this again, but I first need to find time.
    I’ll let you know when I find a time slot to work on this.
  • Hi,

    Understood, no worries! Please let us know when Jerome has had a chance to re-test the issue. If this takes more than 30 days from this post, then the thread will close, but you can open a related thread and we can continue to support there.

    Best Regards,

    Jan