The NRF5340 broadcast audio sink sample doesn't work out of the box

Hello experts,

I'm trying to run the BLE Audio broadcast examples between two NRF5340DK. I managed to build and run the broadcast source by following Maria's comment here: Unable to create broadcast source when running broadcast_audio_source sample on nRF5340-DK 

I also added the following configs to the broadcast sink's prj.conf file. With these additions, I could build and flash the broadcast sink too, both the APP and NET cores. (Removing either of these two flags resulted in a runtime error.)

CONFIG_NCS_INCLUDE_RPMSG_CHILD_IMAGE=n
CONFIG_BT_HCI_VS_EXT=n
But I get the following output:
*** Booting nRF Connect SDK v2.5.1 ***
[00:00:00.522,033] <wrn> bt_hci_core: Controller to host flow control not supported
[00:00:00.527,191] <inf> bt_hci_core: Identity: DD:7D:FD:9D:38:F8 (random)
[00:00:00.527,191] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0d60, manufacturer 0x07e8
[00:00:00.527,221] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0x0d60
Bluetooth initialized
Starting advertising
Waiting for Broadcast Assistant
No Broadcast Assistant connected
Scanning for broadcast sources
Found broadcaster with ID 0x4BCAF2 and addr 16:47:3B:43:A6:18 (random) and sid 0x00
Broadcast source found, waiting for PA sync
Attempting to PA sync to the broadcaster with id 0x4BCAF2
[00:00:05.580,566] <wrn> bt_hci_core: opcode 0x2044 status 0x11
Could not create Broadcast PA sync: -5, resetting
I probably missed something because it feels strange that the example fails and needs manual fixes.
What could be the issue? Do I have to add the periodic advertising sync related configs?  
Parents
  • Hello,

    We will take a look at your question tomorrow.

    Kenneth

  • Hi,

    Could you please specify the samples which you used? Are they Zephyr samples - Broadcast Audio Source and Broadcast Audio Sink?

    Best regards,
    Dejan

  • Hello,

    Yes, these are the two samples. I used the vscode nRF Connect plugin to create new projects. These are the steps I did for building and programming the sink sample. (The source sample is very similar) 

    1. Installed the SDK/Toolchains using the nRF Connect Toolchain manager. (Installed and using SDK v2.5.1)

    2. Open vscode

    3. In the nRF Connect plugin tab: Create new application -> Copy a sample -> Selected zephyr/samples/bluetooth/broadcast_audio_sink

    4. Added the CONFIG_NCS_INCLUDE_RPMSG_CHILD_IMAGE=n and CONFIG_BT_HCI_VS_EXT=n to the prj.conf file.

    5. Created a new build configuration for nrf5340dk_nrf5340_cpuapp

    6. Built the project

    7. Programmed the ble5-ctr-rpmsg_3424.hex from the SDK into the Network core, using the command line.

    8. Programmed the previously built (step 6.) project's hex to the Application core, using vscode.

    After these steps, I got the above-mentioned output.

    I assume both the network and application cores are programmed correctly because when I missed any of these steps then I did not get any UART output, or got a runtime error message about endpoint binding failure.

Reply
  • Hello,

    Yes, these are the two samples. I used the vscode nRF Connect plugin to create new projects. These are the steps I did for building and programming the sink sample. (The source sample is very similar) 

    1. Installed the SDK/Toolchains using the nRF Connect Toolchain manager. (Installed and using SDK v2.5.1)

    2. Open vscode

    3. In the nRF Connect plugin tab: Create new application -> Copy a sample -> Selected zephyr/samples/bluetooth/broadcast_audio_sink

    4. Added the CONFIG_NCS_INCLUDE_RPMSG_CHILD_IMAGE=n and CONFIG_BT_HCI_VS_EXT=n to the prj.conf file.

    5. Created a new build configuration for nrf5340dk_nrf5340_cpuapp

    6. Built the project

    7. Programmed the ble5-ctr-rpmsg_3424.hex from the SDK into the Network core, using the command line.

    8. Programmed the previously built (step 6.) project's hex to the Application core, using vscode.

    After these steps, I got the above-mentioned output.

    I assume both the network and application cores are programmed correctly because when I missed any of these steps then I did not get any UART output, or got a runtime error message about endpoint binding failure.

Children
  • I did the same, but gets the same error : 

    in broadcast_audio_sink sample :

    *** Booting nRF Connect SDK v2.5.2 ***
    [00:00:00.275,756] <wrn> bt_hci_core: Controller to host flow control not supported
    [00:00:00.280,914] <inf> bt_hci_core: Identity: FA:FC:27:CB:2B:F5 (random)
    [00:00:00.280,944] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0d60, manufacturer 0x07e8
    [00:00:00.280,975] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0x0d60
    Bluetooth initialized
    Starting advertising
    Waiting for Broadcast Assistant
    No Broadcast Assistant connected
    Scanning for broadcast sources
    Found broadcaster with ID 0x583D11 and addr 36:63:FB:9F:A8:EE (random) and sid 0x00
    Broadcast source found, waiting for PA sync
    Attempting to PA sync to the broadcaster with id 0x583D11
    [00:00:05.407,531] <wrn> bt_hci_core: opcode 0x2044 status 0x11
    Could not create Broadcast PA sync: -5, resetting

    And the broadcast_audio_source working perfect. 

  • Hi  and Ajaysinh,

    I have reproduced reported issue in NCS v2.5.1. Replacing the line 

    create_params.options = BT_LE_PER_ADV_SYNC_OPT_FILTER_DUPLICATE;

    with 
    create_params.options = BT_LE_PER_ADV_SYNC_OPT_NONE;

    in the sample's main.c file (function pa_sync_create()) should fix the problem.

    Best regards,
    Dejan

Related