WEC7 i.MX6 system, Music Player plays mp3 but no audio output RRS feed

  • Question

  • I have i.MX6 system running Adeneo based BSP. When I play a mp3 file with the Music Player I get no sound.

    Diagnosis: Put scope on the speaker outputs across a 8 ohm load and no signal. Put scope on i.MX audmux port 3 outputs and no digital data is going to my Audio Codec. I check i.MX6 audmux settings for the output and I am in the process of checking SSI2 input settings. I have debugged the OS to the point where I see DMA being setup to transfer data to the serial input (SSI2). My configuration for the aud mux is SSI2->hardwired to Port 2 and then I route transmitted data from port2 to port3. The audmux port3 signals are connected to a WM8962 codec. The music player advances the play cursor but no sound. Next plan is to verify SSI settings and check the TXRXEN signal. Any other things I should check?

    I am using SSI2 -> port2 and setting audio mux setting for port3 to rcv from port2, Audio Mux Port 3 is getting clock and frame sync signals from the audio codec. I have verified the audio codec is supplying the correct clock and frame sync signals. I have verified during playback that data is being DMA'd into the SSI transmit shift FIFOs, that the data is being shifted in to the transmit register but no output data is being seen on the port 3 txd line.

    Thursday, December 7, 2017 1:46 PM


All replies

  • You know my answer...

    Seriously, when is it enough? You will keep encountering problem after problem after problem, only to discover the next thing that doesn't work. Convince your customer to move and save loads of time and money! Many have gone before you and not looked back.

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog:

    Microsoft Embedded Partner
    NXP Proven Partner
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here:

    Thursday, December 7, 2017 8:46 PM
  • I know!
    Thursday, December 7, 2017 8:51 PM
  • This turned out to be a hardware issue.
    Wednesday, January 31, 2018 7:43 PM