This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP L138 example levearging the DSP for audio processing

An example application using DSP-side audio driver running concurrently with a Linux application on the ARM core is available at:

http://software-dl.ti.com/dsps/dsps_public_sw/apps_processors/Audio_soc_example/1_00/index_FDS.html

Detailed information regarding the example application can be found in the Release Notes or at the Audio Soc Example wiki topic.

Future OMAP-L1xx SDK releases, will distributed this example as part of the SDK package.

  • Hi,

    I am experiencing intermittent run time behavior with the example application, To be sure it is not a problem with build or hardware I used this script to test the samples:

    sudo ./loopgpp dspbios/loop.out 1024 1000 0

    sudo ./messagegpp dspbios/message.out 10000 0

    sudo ./scalegpp dspbios/scale.out 1024 10000

    sudo ./ringiogpp dspbios/ringio.out 10240 10240 0

    sudo ./mplistgpp dspbios/mplist.out 10000 100 0

    sudo ./mpcsxfergpp dspbios/mpcsxfer.out 128 10000 0

    sudo ./messagemultigpp dspbios/messagemulti.out 10000 1 0

    The script runs without error. 
    The audioSoc example loads and either hangs or completes with a looping buffer sound, like the DMA is still transferring the same contents.
    Here is where it hangs sometimes:
    DSP message located
    Entered POOL_writeback ()
    poolId [0x0]
    buf [0x4098d400]
    size [0x1000]
    Leaving POOL_writeback () status [0x8000]
    Entered MSGQ_get ()
    msgqQueue [0x10000]
    timeout [0xffffffff]
    msg [0xbecdab60]
    Entered DRV_Invoke ()
    drvObj [0x37178]
    cmdId [0x6f0b]
    arg1 [0xbecdab2c]
    arg2 [0x0]
    Thanks

     

     

     

  • Hello,

    The ARM side is waiting on a MSGQ_get API call. This call waits till it gets a MSGQ from DSP/other process on GPP. Looks like the DSP (I am assuming the MSGQ is posted from DSP) is not sending a message. You will need to debug why the DSP is not posting the message.Has the DSP gone to weeds or has it hung somewhere or has it crashed before the MSGQ_put happend?

    Can you connect to CCS and see what is happening on the DSP which is causing MSGQ_put to not happen. Look at  Debugging using CCS

    Deepali