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.

Building MCSDK MCASP_AudioExampleProject on OMAPL138

Other Parts Discussed in Thread: OMAPL138, SYSBIOS

Hello,

I build the Mcasp_AudioExampleProject of the MCSDK v1.1.0.2 (windows) with CCS v5.5.0.00077, but at the linking stage I get a such warning: 

<Linking>
warning #10247-D: creating output section ".fardata" without a SECTIONS specification
'Finished building target: MCASP_AudioExampleProject.out'
' '

At the end of the building I get output file that is a half as much than original from PDK (C:\ti\pdk_OMAPL138_1_01_00_02\packages\ti\drv\exampleProjects\bin\), about 1MB. It's strange.

I can debug this project through debugger well, but a program can't pass EDMA initialization.

Mcasp_AudioExampleProject has no any .cmd file. Is this normal? Other example projects (MCBSP) have a .cmd file.

What I need to do?

Regards,

Bakir

  • Hi Bakir,

    The McASP project use the SYSBIOS software (ie RTOS) and instead .cmd, you can see the .cfg file which tells you the memory configuration etc.,
    Mostly you can find .cmd fie in starterware code.

    Is that code running well ?

    What is happening while EDMA init ?
  • Thank you Titus for a such quick answer!

    Yes, this code is running well (in debug mode), but it fails to init EDMA.
    It can't successfully pass through edma3init() => EDMA3_DRV_create(). Especially program fails to check result of edma3MemZero() function. When I entering to edma3MemZero(), I execute all expressions, but there are no any changes in MemoryView. I can't understand why? I'm loading right compilled image.

    Best regards,
    Bakir

    I work with omapl138-lcdk board. And mcasp example has a such .cfg file (attached).

    audiosample.cfg

    Do I need to change it? Is it not ready-to-use?

  • Hi Bakir,

    Thanks for your update.

    McASP audio example demo should work perfectly fine since we have already tested the same from our end and we would be able to suceed indebugging the McASP example code for both pdk_OMAPL138_1_01_00_01 (mcsdk_1_01_00_01) and pdk_OMAPL138_1_01_00_02 (mcsdk_1_01_00_02).

    Both the above mcsdk versions (1.1.0.1 & 1.1.0.2) of McASP audio example demo works fine with CCS version: 5.4 but there are issues with CCSv5.5 on free run or  debugging the code, i mean, after loading the application image, it runs automatically and the control doesn't come to the code for debugging and i belive, the code is freezing somewhere.

    So, I would suggest you to downgrade the CCS version from 5.5 to 5.4, install and try the same demo.

    Note: While launching CCS debugger, please ensure to connect the ARM core first to make DSP out of reset before running the code and disconnect the ARM core, Then try reconnecting to the DSP core, reload the application image and run the application. You will succeed in hearing the audio output through Line OUT, provided when there is some input stream (mp3, aac etc) feeded through Line IN. This is because, OMAPL138 is an ARM boot device where in which arm boots first with its bootloader code and then it wakes up the DSP core letting it out of reset, so that, we are allowed to connect to the DSP core and run the application on the same.

    I would recommend you to ensure the above note is properly executed before running the McASP audio example project and you could succeed in debugging the MCSDK McASP audio example code.

    Thanks & regards,

    Sivaraj K

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

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

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

  • Hi Sivaraj,

    Thank you very much! I will downgrade my CCS.
    Could I install both versions v5.4 and v5.5 together?
    Could I install CCS v6? Off-line version has lesser size )

    Do you consider strange, that ==> my compilled in CCS v5.5 output file MCASP_AudioExampleProject.out = 1.05MB, although original MCASP_AudioExampleProject.out = 2.81MB?

    Best regards,
    Bakir
  • Hi,

    It would be better to install v5.4 only and try it as of now.

    Thanks & regards,
    Sivaraj K
  • Hi,

    I downgraded my CCS from v5.5 to v5.4. But I got the same result.

    Later I tried to reinstall the PDK packages. And this resolved the issue!!!

    Many thanks to good guys!

    Best regards,
    Bakir

  • Hi Sivaraj, Titus!

    I made MCSDK MCASP_AudioExampleProject well, and ported codec lib in it successfully.

    But when I insert coder and decoder functions into work loop, debugger outputs failure at  function createStreams() => namely at Mcasp_localConfigXmtSection() (it configures the transmit section of the MCASP: starts transmit high clock and clock):

    titi.sysbios.knl.Semaphore: line 207: assertion failure: A_badContext: bad calling context. Must be called from a Task.

    xdc.runtime.Error.raise: terminating execution

    My codec functions are called from a Task, from forever loop. What should I do to get rid of this failure?

    If there is no codec functions inserted, no any failures received.

    I read this Post:  , but don't know what to do in my case.

    Best regards,

    Bakir

  • Hi!

    All I need to do to get rid of this failure was removing "Agent" module from .cfg file of my project. This module is not supported in new SysBIOS versions.

    Thanks to all!
  • Hi Bakir,

    Thanks for your efforts.
    We appreciate posting the above fix which would really help other E2E community members facing the same issue.

    Thanks & regards,
    Sivaraj K