Test Tone in NCS Audio Application Not Working?

Hello,

In previous NCS versions I know I have heard the test tone triggered by button 4 on Audio DK work out of the box.

I am currently experimenting with NCS v3.2.1/0 and when I press button 4 I do not hear a test tone on the headset device?

I can see the debug print increment the test tone frequency but no tone is heard in the mix. Just the music streamed from my gateway to the headset.

Is anyone else having this issue? I am using a regular Audio DK and the Audio application with no modifications.

Regards,

Erick

Parents
  • I can hear the test tone on a unicast headset when pressing button 4 on a unicast gateway. After review the documentation that is the correct behavior and I was previously mistaken. That being said I do see the debug prints for test tone on the unicast headset when I press button 4. Should it be mixing in a test tone? Is it possible to change things to do so?

Reply
  • I can hear the test tone on a unicast headset when pressing button 4 on a unicast gateway. After review the documentation that is the correct behavior and I was previously mistaken. That being said I do see the debug prints for test tone on the unicast headset when I press button 4. Should it be mixing in a test tone? Is it possible to change things to do so?

Children
  • Hello Erick,

    I am not sure I follow. 

    You expected the button 4 to generate a tone on the headset device? But you do see that pressing the button 4 on the broadcast device will play the test tone on the heaset device? Is this correct?

    erickcinco said:
    That being said I do see the debug prints for test tone on the unicast headset when I press button 4. Should it be mixing in a test tone?

    What do you mean? What is your goal?

    erickcinco said:
    Is it possible to change things to do so?

    Probably, but I am not sure what you want to do.

    Best regards,

    Edvin

  • Hi Edvin,

    My main goal was to trigger test tone generation on the headset independent of connection to a unicast client (gateway) so I could debug why I was not seeing data out when working with an external codec.

    I was hoping to press button 4 on the unicast server (headset) and see the test tone logic flow however that is not what the application is set up to do. Button 4 does not do ANYTHING on a unicast client application; which is fine because I figured out how I could trigger it!

    What I figured out is that you CAN get test tone generation and playback on the unicast client by going through the shell interface.

    audio_system start

    test nrf_tone_start 1000 100 1

    Some feedback on the documentation. I had assumed that DOUT on P10 meant literally DOUT from the microcontroller but in actuality what is labeled as DIN is DOUT from the microcontroller. 

    HW_CODEC_DIN has a clear description "Audio serial port data input of hardware codec".

    It would be nice if P10 DIN had the same description so it is not confused with DIN from the microcontroller.

    P10 DIN == HW_CODEC_DIN == DOUT from microcontroller

    and

    P10 DOUT == HW_CODEC_DOUT == DIN to microcontroller.

    I was able to successfully use an external codec (WM8904) with the Audio DK after realizing I had these wires swapped.

    We can close this ticket.

Related