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: Communication Issue

Part Number: CC2640R2F

Hi team,

Here's an issue: The slave cc2640r2f7*7 has failed to communicate with the host notify, while the same slave program can communicate with the cell phone successfully; and cc2640r2f4 *4 has successfully communicated with the same program host.

The following table is the process of printing the connection when the host connects the slave:

Normal slave Abnormal slave Successful after the abnormal slave reburn program 

SC_EVT_SCAN_DISABLED

Initiate service discovery

Discovering...

SC_EVT_ADV_REPORT

SC_EVT_ADV_REPORT

SC_EVT_ADV_REPORT

groupMember: 0x010203040501

SC_EVT_ADV_REPORT

SC_EVT_SCAN_DISABLED

AutoConnect: Number of members in the group 1

Initiate service discovery

HCI_GAP_EVENT_EVENT:3e

numConn:1

SC_EVT_PAIR_STATE

Pairing started

Initiate service discovery

BLE_DISC_STATE_MTU

HCI_GAP_EVENT_EVENT:3e

Service found, store handles

If procedure complete

BLE_DISC_STATE_CHAR

SBC_NOTI_ENABLE_EVT

Notification success:0

SC_EVT_SCAN_DISABLED

Initiate service discovery

Discovering...

SC_EVT_ADV_REPORT

groupMember: 0x010203040507

SC_EVT_ADV_REPORT

SC_EVT_SCAN_DISABLED

AutoConnect: Number of members in the group 1

Initiate service discovery

HCI_GAP_EVENT_EVENT:3e

numConn:1

Initiate service discovery

HCI_GAP_EVENT_EVENT:f

SC_EVT_PAIR_STATE

HCI_GAP_EVENT_EVENT:3e

GAP_LINK_TERMINATED_EVENT

0x010203040507 is disconnectedNum Conns: 0

HCI_GAP_EVENT_EVENT:3e

numConn:1

Initiate service discovery

HCI_GAP_EVENT_EVENT:f

SC_EVT_SCAN_DISABLED
Initiate service discovery
Discovering...
SC_EVT_ADV_REPORT
groupMember: 0x010203040507
SC_EVT_ADV_REPORT
SC_EVT_SCAN_DISABLED
AutoConnect: Number of members in the group 1
Initiate service discovery
HCI_GAP_EVENT_EVENT:3e
numConn:1
SC_EVT_PAIR_STATE
Pairing started
Initiate service discovery
BLE_DISC_STATE_MTU
HCI_GAP_EVENT_EVENT:3e
Service found, store handles
If procedure complete
BLE_DISC_STATE_CHAR
SBC_NOTI_ENABLE_EVT
Notification success:0

The difference is that after starting the discovery service, the slave that failed to connect cannot get the char of the characteristic value.

Debug output HCI_GAP_EVENT_EVENT:f is HCI_COMMAND_STATUS_EVENT_CODE (HCI Commands Events). The cmdopcode code is 0x406 (HCI_DISCONNECT).

Could you please help to check this case? Thanks!

Best Regards,

Cherry

  • Hey Cherry,

    I've assigned your post to an expert who can help. In the meantime, can you clarify some things below for us?

    • Which SDK version is the customer using?
    • Is the customer experiencing this issue on a launchpad, or some custom hardware?
    • What projects has the customer based their application from? Is this behavior reproducible using host_test and launchpads?
    • You mention
      • Which indicates that the issue does not happen all the time. Is this the case? How often is this issue reproduced?
    • If you have sniffer logs to share of the behavior (preferably on an Ellisys or Frontline sniffer), this would help us understand what is happening over the air.
  • Hi Ammar,

    Thanks for your reply, since the reply button below is not working, so the latest info will be updated here:

    When the GAP_BOND_MGR is burned from the slave but not masked, the transmit characteristic cannot be performed, the GAP_BOND_MGR is reburned and masked, or the host program needs to be reburned to properly transmit the characteristic value. The characteristic value can be sent even if the program is changed.

    That is, when the GAP_BOND_MGR is burned but not masked, the host program must also be rewritten.

    The customer suspect if the host has any power-down saving link parameters.

    The slave is simplelink_cc2640r2_sdk_4_20_00_04, which masks keys, menus, displays, pairing, and so on. The host is Simplelink_cc13x2_26x2_sdk_4_30_00_54, and only the connection characteristic value is sent.

    Thanks!

    Best Regards,

    Cherry

  • Hi,

    May I know is there any updates?

    Thanks and Best Regards,

    Cherry

  • Hi Cherry,

    Based off the logs you've sent it looks like the Abnormal Central Device tries to pair but fails. Can you take a sniffer log to confirm this? This will help us understand why the pairing is rejected.

    Best,

    Nate