• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 643 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

sample not playing

NancyJ
Intellectual 995 points

Other Parts Discussed in Thread: OMAPL138

Hi all,

  • 0
    TI__Mastermind 35645 points

    Hi,

    Thanks for your post.

    Please refer to the omapl137 HW design guide, I would like to suggest to refer to schematics to check the audio hw section to find any changes.

    http://processors.wiki.ti.com/index.php/OMAP-L137_Hardware_Design_Guide

    Basically, i do not find any audio loopback examples based out of OMAPL137 other than biospsp. Alternatively, if you prefer, you could also try the attached OMAPL137 starterware audio example code and please find attached the "OMAPL137_McASP_EDMA_StarterWare.zip" below which would provide you a working McASP-EDMA audio loopback example for OMAPL137 platform. Actually, the sample example below is been modified by taking OMAPL138 McASP Starterware audio loopback example as reference and being modified the pinmux & platform level code changes appropriately to work for OMAPL137 platform.

    /cfs-file/__key/communityserver-discussions-components-files/791/6470.0160.OMAPL137_5F00_McASP_5F00_EDMA_5F00_StarterWare.zip

    Kindly look for the sample .CCS project path below to look for OMAPL137 McASP EDMA audio loopback example after extracting the above attached zip file:

    ~\OMAPL137_McASP_EDMA_StarterWare\build\c674x\cgt_ccs\omapl137\evmOMAPL137\mcasp\.ccsproject

    Thanks & regards,

    Sivaraj K

    ----------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    ----------------------------------------------------------------------------------------------------------

     

  • 0 in reply to NancyJ
    TI__Mastermind 35645 points

    Hi,

    Have you modified any on the biospsp code to your custom requirement? or running the example "as-is" with out any modification?

    If any code changes, please revert it back and execute the code "as-is" to see for the same issue which you are reporting.

    Please ensure whether the gel script added in target configuration file boots the DSP first and wakes- up the ARM which would print in the debug console when you try to connect the DSP target.

    I presume that, you ensure loading DSP-based application image and execute the same. Also, ensure connect the DSP first since OMAPL137 is a DSP-boot device and validate the GEL output on the console.

    After loading the application image, do you get control over the main() function in debug mode and you could also prefer debugging stepping in through desired part of the code whereever you guess the issue could be reproducible and validate the end to end coverage of application code. This would bring the origin of issue if any and provide more clarity to elloborate the insight of the issue through any screenshots if possible which would make us understand easy.

    Finally, you could hardreset the device and try to run the same application connecting the DSP target first which would probably fix the issue, i guess.

    Thanks & regards,

    Sivaraj K

    ----------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    ----------------------------------------------------------------------------------------------------------

  • 0 in reply to NancyJ
    TI__Mastermind 35645 points
    Hi,

    Glad, that your issue got fixed.

    Thanks for your update.

    Regards,
    Sivaraj K