Cannot use unicast_client and unicast_server in nRF5340 Audio DKs

Hi,

I have two nRF5340 DKs and want one to be server, one be client. I use NCS offcial code and simply buide them, however, "LED3 starts blinking green on every device to indicate the ongoing CPU activity on the application core" Both boards' LED3 is not blinky after I program the DK.

I am confused as "Building and programming using the nRF Connect for VS Code extension is currently not supported." Could you help me on this? I just want one board send out audio and one play it. Thank you so much!

Parents
  • Hello,

    I have two nRF5340 DKs

    Your title and text indicate two different boards. Are you using the nRF5340 DK or nRF5340 Audio DK?

    I have two nRF5340 DKs and want one to be server, one be client. I use NCS offcial code and simply buide them, however, "LED3 starts blinking green on every device to indicate the ongoing CPU activity on the application core" Both boards' LED3 is not blinky after I program the DK.

    You are using the documentation for the nRF5340 Audio applications while building the Zephyr samples BAP Unicast Audio Client and Server. The Zephyr samples does not configure LED3 to indicate application core activity.

    I am confused as "Building and programming using the nRF Connect for VS Code extension is currently not supported." Could you help me on this? I just want one board send out audio and one play it. Thank you so much!

    The nRF5340 Audio applications use command line or a python script to build and program the applications. This is to ease programming of multiple kits with a single command.

    You can also build and program the application with the VS Code extension, though. I shared this method in another ticket a few months ago:  RE: Building Audio Broadcast SDK example in VS Code . I used the nRF5340 Audio Broadcast Source as an example back then, but let me know if you have any issues with using the nrF Connect for VS Code extension to build the nRF5340 Audio Unicast Client or Server applications.

    Best regards,

    Maria

Reply
  • Hello,

    I have two nRF5340 DKs

    Your title and text indicate two different boards. Are you using the nRF5340 DK or nRF5340 Audio DK?

    I have two nRF5340 DKs and want one to be server, one be client. I use NCS offcial code and simply buide them, however, "LED3 starts blinking green on every device to indicate the ongoing CPU activity on the application core" Both boards' LED3 is not blinky after I program the DK.

    You are using the documentation for the nRF5340 Audio applications while building the Zephyr samples BAP Unicast Audio Client and Server. The Zephyr samples does not configure LED3 to indicate application core activity.

    I am confused as "Building and programming using the nRF Connect for VS Code extension is currently not supported." Could you help me on this? I just want one board send out audio and one play it. Thank you so much!

    The nRF5340 Audio applications use command line or a python script to build and program the applications. This is to ease programming of multiple kits with a single command.

    You can also build and program the application with the VS Code extension, though. I shared this method in another ticket a few months ago:  RE: Building Audio Broadcast SDK example in VS Code . I used the nRF5340 Audio Broadcast Source as an example back then, but let me know if you have any issues with using the nrF Connect for VS Code extension to build the nRF5340 Audio Unicast Client or Server applications.

    Best regards,

    Maria

Children
  • Hi,

    Thank you for your information! I am using two nRF5340 Audio DK.

    I have just finish program the boards, however, the two board cannot set up connection. Could you give me some advice, I have tried erase and download it for many times.

Related