• State Not Answered
  • Replies 30 replies
  • Subscribers 68 subscribers
  • Views 1983 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 322171
Options

nRF5340 Audio DK: Audio Loosing sync both with I2S and U

Nambiar

Hi All,

       I have been using nRF5340 DK audio with toolchain Version 2.5.2 and using the Audio Demo (nrf5340_audio_dk_nrf5340_cpuapp_common) for gateway and headset (Broadcast source and Sink). I have not changed anything and used script to build and flash the binaries.

  • The source and sink is able to manage sync only for ~10s in I2S case (Audio in at Source using I2S). 
  • The source and sink is able to manage sync for ~ 1s in USB case.

This means audio plays for 10s/1s and then the sink is unable to get the audio afterwards.

As it is experimental SDK any suggestion to improve it or am I missing any configuration.

Regards

Sainath

Parents Reply
  • 0 in reply to Elfving

    Can you explain a bit more regarding your answer , In broadcast if ISOC (hope that is what you meant)  is prioritised, loosing sync would not happen. Doing the experiment in a controlled environment still results in this sync issue . Also checking the logs over the air . There are no failures or interference at the Source. Can you please check by doing the same experiment.?

Children
  • 0 in reply to Nambiar

    Yeah. So once again, this is strange, as we haven't seen this on our side. Though it could potentially happen with the current version of the controller, but it should not happen with the new SDC controller which we will be using for LE Audio in the next NCS version, 2.6.0. (Please ask your RSM for further details on when this releases).

    Are you able to wait to until 2.6.0 releases? We could potentially delve into details on this in NCS 2.5.2, but could also wait until NCS 2.6.0 releases and use that instead? If we were to find a clear issue with the old controller, it will either way not get any more bug fixes or features going forward. We'll continously work on the SDC controller though, and we'll have all the expertise for it in-house.

    Regards,

    Elfving

  • 0 in reply to Elfving

    Hi Elfving , Do you want me to check the latest NCS version 2.6.0-rc1, would it resolve my issue ? I can try that , can you point out a way to enable the controller logs as well , so that I can share that as well with you . Point me out with a set of configuration that can help you to analyse my issue in depth. I have an over the air sniffer, so quite sure about the Tx part of setup.

  • 0 in reply to Nambiar

    It might, but using something that isn't a tagged version is never the best choice.

    Could you contact your local RSM about when the next NCS version will be released? He is able to get more into the details about that. And let me know if you do not know who your local RSM is, and I can get you his contact info.

    Regards,

    Elfving

  • 0 in reply to Elfving

    Actually this one works smooth and have seen no sync issues . I have further queries on the same , will add it here tomorrow 

  • 0 in reply to Nambiar

    The BAP configuration of 48_4_1 or 48_4_2 is not explicitly mentioned in the KConfig of BAP  Module, any specific reason for it. Also from the spec it looks like the default BAP configuration is 48_4_2, am I right  . Also Is there any way to get the exact number of BIS events or ISOC SDU packet received, any interface to get this information?

Related