Problems with 20719 Watch Example Reference Code

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
ChCh_3584941
Level 4
Level 4
50 sign-ins 25 replies posted 25 sign-ins

As noted in another recent question:  https://community.infineon.com/t5/Bluetooth-SDK/a2dp-sink-cant-t-connect-to-20719-a2dp-source/td-p/3... the Watch Example provided as reference code for A2DP implementation seems to have problems with the connection sequence, and it appears that the code does not actually perform to the Bluetooth Specification.  Can you explain the apparent deficiencies or provide examples of compliant code?  

As noted in the referenced post above, the connection sequence always seems to  fail for a previously paired device.  And we do not seem to be able to get SBC output to play on Airpods at all.

0 Likes
1 Solution
advait_kulkarni
Moderator
Moderator
Moderator
25 likes received 250 sign-ins 100 solutions authored

Hi @ChCh_3584941 ,

As mentioned in the internal case management, the latest update is that the fix for the loudness issue is provided in the latest release on github and we were also able to test the airpods with it. Please let us know your test results in the case.

Thanks and regards,

Advait Kulkarni

View solution in original post

0 Likes
5 Replies
advait_kulkarni
Moderator
Moderator
Moderator
25 likes received 250 sign-ins 100 solutions authored

Hi @ChCh_3584941 ,

Can you please explain the exact issue that you are facing? Is it the same issue in the previous thread and hence the steps to reproduce are also the same? 

Thanks and regards,

Advait Kulkarni

0 Likes
dastarling
Level 1
Level 1
First reply posted Welcome!

Advait,

Let me work on explaining the details, since I am working on this feature. The issue that we see seems to be the same as the noted thread.  In the case where the device is the initiator, the Watch demo does not seem to be quite correct.

The first issue is that the advertised capabilities of the Source device (Watch demo) does not match the A2DP specification.  For example:

/* SBC codec capabilities */
static const wiced_bt_a2d_sbc_cie_t av_sbc_caps =
{
/* samp_freq */ (A2D_SBC_IE_SAMP_FREQ_16|A2D_SBC_IE_SAMP_FREQ_32|A2D_SBC_IE_SAMP_FREQ_44|A2D_SBC_IE_SAMP_FREQ_48),
/* ch_mode */

(A2D_SBC_IE_CH_MD_MONO | A2D_SBC_IE_CH_MD_JOINT), // A2D_SBC_IE_CH_MD_DUAL | A2D_SBC_IE_CH_MD_STEREO
/* block_len */

(A2D_SBC_IE_BLOCKS_16), //A2D_SBC_IE_BLOCKS_8|A2D_SBC_IE_BLOCKS_12|A2D_SBC_IE_BLOCKS_16|
/* num_subbands */

(A2D_SBC_IE_SUBBAND_8), //A2D_SBC_IE_SUBBAND_4|A2D_SBC_IE_SUBBAND_8
/* alloc_mthd */

(A2D_SBC_IE_ALLOC_MD_S), //A2D_SBC_IE_ALLOC_MD_S|A2D_SBC_IE_ALLOC_MD_L
/* max_bitpool */

(AV_SBC_MAX_BITPOOL), //A2D_SBC_IE_MAX_BITPOOL
/* min_bitpool */

(A2D_SBC_IE_MIN_BITPOOL) //A2D_SBC_IE_MIN_BITPOOL
};

Let's just take one field the alloc_mthd.  We are specifying that we only support the SNR method, but the A2DP standard says that we MUST support Loudness method.  When we send this to some devices, the responding configuration data is malformed with the alloc method set to 0x00 which is not valid.  The block length also does not indicate that we support all block lengths as required by the A2DP specification.

The other issue that is seen is that the code and thus my derived code is very sensitive to timing differences of the messages coming from the peer device in initiator mode. There are a few notes to this issue in the sample code, but no actual code to address those cases.

In the case of Airpods, we can connect, pair and open a connection, but have not been able to get audio using the SBC codec.  This happens on our internal firwmware, and the Watch Demo.  Using the Watch demo with the control program, I can play tones on all other devices, but no sound with come out of the Airpods with the same setup at the other peer devices (speakers, headphones)

0 Likes
ChCh_3584941
Level 4
Level 4
50 sign-ins 25 replies posted 25 sign-ins

Hi @advait_kulkarni  Any feedback / update on this?

0 Likes
ChCh_3584941
Level 4
Level 4
50 sign-ins 25 replies posted 25 sign-ins

It's been more than two weeks with no response.  ...?

0 Likes
advait_kulkarni
Moderator
Moderator
Moderator
25 likes received 250 sign-ins 100 solutions authored

Hi @ChCh_3584941 ,

As mentioned in the internal case management, the latest update is that the fix for the loudness issue is provided in the latest release on github and we were also able to test the airpods with it. Please let us know your test results in the case.

Thanks and regards,

Advait Kulkarni

0 Likes