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.

CC2640: My ios App no longer discovers the services of my CC2640

Part Number: CC2640

I am trying to use my new packet sniffer to figure out why my ios app no longer discovers the services of my CC2640.

I am getting a "Authentication is insufficient" error when didDiscoverServices is triggered in my ios app.

Here is a sniff (Keep Alive packets filtered out) of the connect attempts, on the LEFT is a capture when it was working and on the RIGHT is a current capture that is not working:

I can not figure or what code is responsible for sending out the ATT_Read_By_Type_Req that works and the ATT_Read_By_Group_Type_Req that does not.

Any ideas on what I can do and where (xcode or ccsv7) I have to do it to make this work again?

EDIT:

Unfortunately, that is the only capture I had taken before the ios App started discovering my peripheral with the "Authentication is insufficient" error.  I am not sure why the LEFT session does not include the 0x10 Group read of services, it must have since it had to have discovered the services in order to discover the characteristics (I think) and show the characteristic values on my iphone screen which my ios app was doing.

And, that LEFT side packet number 178 is the slave reporting the first characteristic value, so the LEFT side is either missing packets or shows the whole connection sequence that worked.

Thanks,

Dale

  • I really think this is a problem inside my ccs7 project since the ios Apps 'SimpleLink Starter' and 'LightBlue' both are able to connect but are not able to discover services which confirms my findings.
  • SOLVED!

    When I was trying to clean up my project, which began as a ProjectZero, I decided the reduce the number of characteristics that were defined.

    This involved combining some GATT features into the one remaining characteristic.  

    The culprit was that when I was trying to add a Notify property to a characteristic, I have to figure out where to add the GATT_PROP_NOTIFY.

    I had added it here for testing which did not work (but also caused the issues of this thread).  I forgot to remove the GATT_PROP_NOTIFY after I realized it did not work!!

    static gattAttribute_t Halo_ServiceAttrTbl[] =
    {
        // Halo_Service Service Declaration
        {
            { ATT_BT_UUID_SIZE, primaryServiceUUID },
            GATT_PERMIT_READ | GATT_PROP_NOTIFY,   //dale added  | GATT_PROP_NOTIFY  which DID NOT WORK and caused problems later 
            0,
            (uint8_t *)&HaloServiceDecl
        },

    Solution was to remove the above GATT_PROP_NOTIFY and all is well again.

  • Glad you solved the problem.