• State Verified Answer
  • Replies 2 replies
  • Subscribers 72 subscribers
  • Views 83 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 342628
Options

nrf5340 Audio DK dosen't work。

Allen23122452121
Hi:
  I purchased the nRF5340 Audio DK and used NCS 2.5.0. After flashing the unicast_audio_client example (zephyr/samples/bluetooth/unicast_audio_client), it failed to run without any code modifications. The error message is as follows:
*** Booting nRF Connect SDK v2.5.0 ***
Initializing
[00:00:00.281,433] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.281,494] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.281,494] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
[00:00:00.283,569] <inf> bt_hci_core: Identity: E1:CB:17:32:BF:ED (random)
[00:00:00.283,599] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x2102, manufacturer 0x0059
[00:00:00.283,599] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x2102
Initialized
Waiting for connection
[00:00:00.285,888] <wrn> bt_hci_core: opcode 0x2041 status 0x01
Scanning failed to start (err -5)
I tried several other audio-related examples, and they all reported similar errors. Then, I tried the "multiple_adv_sets" example, and it was able to run successfully.
Looking forward to your reply.
Parents
  • +1

    Hello,

      I purchased the nRF5340 Audio DK and used NCS 2.5.0. After flashing the unicast_audio_client example (zephyr/samples/bluetooth/unicast_audio_client), it failed to run without any code modifications.

    In older versions of nRF Connect SDK, the Zephyr samples does not support the nRF5340 Audio DK. The supported code for the Audio DK is the nRF5340 Audio application, found in nrf/applications/nrf5340_audio. Because this version of the application uses a dedicated LE Audio controller which is distributed as a .hex, the building and running instructions in the sample documentation needs to be followed (command line, script).

    However, v2.5.0 is quite old, and several improvements have been introduced with SDK releases. Please use the newest tagged release, which is v2.9.1 as I am writing this.

    Here are some highlights from the updates after v2.5.0:

    • The SoftDevice Controller supports isochronous streams.
    • Zephyr samples support the Audio DK.
    • LE Audio profiles are close to compliance.

    Best regards,

    Maria

Reply
  • +1

    Hello,

      I purchased the nRF5340 Audio DK and used NCS 2.5.0. After flashing the unicast_audio_client example (zephyr/samples/bluetooth/unicast_audio_client), it failed to run without any code modifications.

    In older versions of nRF Connect SDK, the Zephyr samples does not support the nRF5340 Audio DK. The supported code for the Audio DK is the nRF5340 Audio application, found in nrf/applications/nrf5340_audio. Because this version of the application uses a dedicated LE Audio controller which is distributed as a .hex, the building and running instructions in the sample documentation needs to be followed (command line, script).

    However, v2.5.0 is quite old, and several improvements have been introduced with SDK releases. Please use the newest tagged release, which is v2.9.1 as I am writing this.

    Here are some highlights from the updates after v2.5.0:

    • The SoftDevice Controller supports isochronous streams.
    • Zephyr samples support the Audio DK.
    • LE Audio profiles are close to compliance.

    Best regards,

    Maria

Children
Related
Terms of service