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.

CC2640R2F: BQB Certification fail

Part Number: CC2640R2F

Hi team,

Customer is doing BQB certification. However, they meet connection problem about security.The CC2640R2 device is fail to connect to the PTS host. But this CC2640R2 device works well while connecting to smart phone (iOS or Android).

Below is the error message. 

Attachment is test log from test lab.

4760.log_from_lab.zip

Below list the bonding parameters in the FW code.

// Default GAP pairing mode

#define DEFAULT_PAIRING_MODE                  GAPBOND_PAIRING_MODE_INITIATE

 

// Default MITM mode (TRUE to require passcode or OOB when pairing)

#define DEFAULT_MITM_MODE                     FALSE

 

// Default bonding mode, TRUE to bond

#define DEFAULT_BONDING_MODE                  TRUE

 

// Default GAP bonding I/O capabilities

#define DEFAULT_IO_CAPABILITIES               GAPBOND_IO_CAP_NO_INPUT_NO_OUTPUT  // GAPBOND_IO_CAP_KEYBOARD_ONLY

 

    // Setup the GAP Bond Manager

    {

        uint8_t pairMode           = DEFAULT_PAIRING_MODE;

        uint8_t mitm               = DEFAULT_MITM_MODE;

        uint8_t ioCap              = DEFAULT_IO_CAPABILITIES;

        uint8_t bonding            = DEFAULT_BONDING_MODE;

        uint8_t scMode             = GAPBOND_SECURE_CONNECTION_NONE;

        //uint8_t removeWhenListFull = TRUE;

 

        GAPBondMgr_SetParameter(GAPBOND_PAIRING_MODE, sizeof(uint8_t), &pairMode);

        GAPBondMgr_SetParameter(GAPBOND_MITM_PROTECTION, sizeof(uint8_t), &mitm);

        GAPBondMgr_SetParameter(GAPBOND_IO_CAPABILITIES, sizeof(uint8_t), &ioCap);

        GAPBondMgr_SetParameter(GAPBOND_BONDING_ENABLED, sizeof(uint8_t), &bonding);

        GAPBondMgr_SetParameter(GAPBOND_SECURE_CONNECTION, sizeof(uint8_t), &scMode);

        //GAPBondMgr_SetParameter( GAPBOND_LRU_BOND_REPLACEMENT, sizeof(uint8_t), &removeWhenListFull );

    }

Attachment list the content of the build_components.opt file.

/* BLE Host Build Components */

-DBROADCASTER_CFG=0x01
-DOBSERVER_CFG=0x02
-DPERIPHERAL_CFG=0x04
-DCENTRAL_CFG=0x08

/* BLE Controller Build Components */

-DADV_NCONN_CFG=0x01
-DADV_CONN_CFG=0x02
-DSCAN_CFG=0x04
-DINIT_CFG=0x08

/* Possible BLE Controller Pre-Defined Combinations */

-DADV_CFG=ADV_NCONN_CFG+ADV_CONN_CFG
-DLINK_CFG=ADV_CONN_CFG+INIT_CFG
-DFULL_CFG=INIT_CFG+SCAN_CFG+ADV_NCONN_CFG+ADV_CONN_CFG

/*
BLE Core Spec V4.1 Host Feature Partition Build Components
Note: Shared with Controller Feature Partitions
*/

-DL2CAP_COC_CFG=0x80
-DHOST_V41_MASK=0x80

/*
BLE Core Spec V4.1 Controller Feature Partition Build Components
Note: Shared with Host Feature Partitions
*/

-DPING_CFG=0x01
-DSLV_FEAT_EXCHG_CFG=0x02
-DCONN_PARAM_REQ_CFG=0x04
-DLOW_DUTY_CYCLE_DIRECTED_CFG=0x08
-DDTM_625US_TX_CFG=0x10
-DFRAG_CFG=0x20
-DMST_SLV_CFG=0x40
-DV41_CTRL_CFG=0x47
-DCTRL_V41_MASK=0x7F

/* BLE Core Spec V4.2 Feature Partition Build Components */

-DPRIVACY_1_2_CFG=0x01
-DSECURE_CONNS_CFG=0x02
-DEXT_DATA_LEN_CFG=0x04

/* BLE Vendor Specific Feature Partition Build Components */

-DSCAN_EVT_NOTICE_CFG=0x01
-DSCAN_REQ_RPT_CFG=0x02

/* BLESTACK Fixes Partition Build Components */

-DBLESTACK_1079=0x01
-DBLESTACK_1091=0x02
-DBLESTACK_1100=0x04
-DBLESTACK_1307=0x08
-DBLESTACK_1448=0x10

Please help clarify what's the problem. Thank you.

  • Jerry,

    Which SDK are they using?

  • Hi Evan,

    simplelink_cc13x2_26x2_sdk_4_10_00_78

  • Hello Jerry,

    I am working to find the appropriate expert to help you. This may take some time to reach the right person depending on availability. Please expect an update by 7/24. I appreciate your patience.

    In the meantime, please indicate the following:

    • The SDK version you're using
    • The role the TI device is performing (Central, Peripheral, Broadcaster, Observer)
    • Are you using an example project (i.e. simple_peripheral)

    This particular issue will likely require more debugging from our customer. Please recommend the Debugging section on our User's Guide, in particular, the section on how to use digital GPIO to map the RF activity. Also, a packet sniffer log I'm sure will be helpful.

    Regards,

    Luis

  • Hi Luis,

    • The SDK version you're using:

    simplelink_cc13x2_26x2_sdk_4_10_00_78

    • The role the TI device is performing (Central, Peripheral, Broadcaster, Observer)

    Peripheral

    • Are you using an example project (i.e. simple_peripheral)

    HID_ADV_REMOTE

    Below is reply from Evan,

    Looking into this more, this is related to the Battery Service which is a GATT profile. We do not have a test for this, but the customer should be able to make any amendments necessary since this is technically an application file that the customer owns.

     Also, the attachment on E2E effectively just looks like a bunch of random files of stuff. I’m not familiar if the file is corrupted or if I need a particular tool to view them.

  • Hi Luis, Evan,

    Attach the PTS logs. Currently, lab do three profile test. All meet below error.

    - Unexpected ATT Disconnect received.

    - FAIL: Security failed. PTS hasn't received access confirmation or encryption change event.

    - Paring process is done. Access is granted.

    - Fail verdict returned from APICOM, see log for more details.

    PTS_logs.zip

  • Jerry,


    Each of these are PTS logs of a GATT profile in the customers application. Can you tell me what the expectation is here as this is code mainly owned by the customer? There are 30ish logs attached in that ZIP. Do they have one in particular they want us to look at? 

    Secondary to this, it seems in one of the logs i opened briefly, that the connection actually fails to be established with the TI device. Have they debuged this and reproduced this on their side any?

  • Hi Evan,

    Yes, the problem is " the connection actually fails to be established with the TI device."

    It looks the logs are duplicated inside each folder.

    Customer will try another lab to clarify if the lab's problem.

    Please stop support here. I will update later when I get further information from customer.

    Thank you. 

  • Hi Evan & team,

    Customer find the problem & this can be closed.

    Thank you.