Troubleshooting nRF5340 Board: LED and Audio Output Issues

Hello everyone,

I'm currently working with an nRF5340 board and have successfully completed the building process using the command

python3 buildprog.py -c both -b debug -d both

I also completed the programming phase with

python3 buildprog.py -c both -b debug -d both -p --recover_on_fail. 

However, during testing, I encountered the following issues:

  1. The rgb2 light does not illuminate or flash, even though LEDs 1 and 3 on the gateway board do flash. Similarly, on the headset board, LEDs 1 and 3 flash, and LED 2 is constantly on.
  2. When I switch the audio output on my MacBook from the speakers to nRF Audio USB, I briefly hear the audio playback, but then there's no sound afterward. However, when I press the BTN 4 button on the gateway, the test sound occurs as expected. 

Could anyone please help me identify where the problem might be? Any advice or suggestions would be greatly appreciated.

Thank you in advance for your assistance!

  • Hello, 

    Due to Christmas holiday in our technical support team we are lower staffed than normal, this may cause some delays in our answers. Sorry for the inconvenience. 


    I will have a look at your issue and get back to you. Are you able tell me what version of the nRF Connect SDK you are building with?

    Thanks.

    Kind regards,
    Øyvind

  • Hello Øyvind, 

    Thank you for the reply!

    I have initiated the setup using the following commands:

    1. west init -m github.com/.../sdk-nrf --mr v2.5.1
    2. west update

    After executing these commands, is the nRF Connect SDK considered fully installed, or is there an additional step required through the Toolchain Manager in the nRF Connect for Desktop application?

    I noticed that the Toolchain Manager currently lists nRF Connect SDK v1.9.1 as the latest available version, which seems to be out of sync with the version I am attempting to install (v2.5.1). Could you please advise if the installation via the command line with West is sufficient, or if I should also perform any steps through the Toolchain Manager?

    Thank you for your guidance.

    Best regards,

    Runqi

  • HI Runqi, 

    I'm currently using nRF Connect SDK v2.5.0 installed through Toolchain Manager v1.3.0 in the nRF Connect for Desktop app v4.3.0. Tested on Windows 11 without issues but can do a test on a Macbook Air M2 as well to be sure. 

    Anything from the build log of python3 buildprog.py -c both -b debug -d both -p --recover_on_fail that indicates a failure

    Have you configured the tools\buildprog\nrf5340_audio_dk_devices.json correctly?

    runqi said:
    After executing these commands, is the nRF Connect SDK considered fully installed, or is there an additional step required through the Toolchain Manager in the nRF Connect for Desktop application?

    This should be sufficient. And as you pointed out, you are able to build without issues so if should work. 

  • Hi Øyvind,

    In an effort to sync our environments, I have now switched my SDK version to 2.5.0 to match yours. I've followed all the steps successfully, and the final outcome is as shown in the attached screenshot:

    I briefly hear the audio playback, then there's no sound afterward just like before. 

    I have made another attempt by setting AUDIO_SOURCE_GATEWAY to AUDIO_SOURCE_I2S. After doing so, I connected the gateway to my MacBook using a 3.5mm audio cable, and I'm happy to report that the sound is now working properly.

    I am starting to wonder if the problem could be related to the USB audio output on the MacBook or if there could be another cause. If you have any insights or troubleshooting steps I could try, that would be incredibly helpful.

    Additionally, I have a question regarding the nRF Connect Desktop v4.3.0: in the Toolchain Manager v1.3.0, the latest version of nRF Connect SDK available is v1.9.1, not v2.5.0 as in your case:

    Thank you once again for your assistance.

    Best regards,

    Runqi

  • Hello Runqi, 

    Unfortunately there is an issue with USB on MacOS - see known issues. The current work-around seems to be using audio cable. 

    Kind regards,
    Øyvind

Related