nRF5340 audio CONNECT_IND Question

Hi I am using nRF5340 audio DK (pca10121) and I was able to evaluate LC3 LE audio example code between nRF5340 audio DK gateway and nRF5340 audio DK headset.

Since Samsung Galaxy Buds2 Pro with LC3 support firmware released on 1/16/2023. I was able to use nRF Connect Desktop to pair with Samsung Galaxy Buds2 Pro. From Nordic BLE sniffer, I saw:

  1. Buds2 Pro broadcastED ADV_IND
  2. nRF Connect Desktop sent SCAN_REQ
  3. Buds2 Pro sent SCAN_RSP
  4. nRF Connect Desktop sent CONNECT_IND

This is a good case. I then compared to nRF5340 audio DK gateway firmware pairing to Buds2 Pro. The first 2 steps ADV_IND, SCAN_REQ and SCAN_RSP were identical which mean Buds2 Pro response with the correct SCAN_RSP. However, nRF5340 audio DK gateway firmware did NOT send CONNECT_IND. i browsed through the nRF5340 audio DK gateway firmware example code but I could not find where CONNECT_IND initiates. Please point me to the code area for this CONNECT_IND handling.

Second, what could be the reason. Thanks in advance,

Dennis 

Related