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.

I need a eabi format AEC-AER c674x library on DM8168

Deal all,

    I got a aec-aer c674x library from TI website, and I try to use c6runlib to build a arm-size callable aec dsp library.

After trying, I got a "undefined symbol" error during linking. And I found that c6runlib in ezsdk_5_01_01_80 uses eabi format,

whereas aec-aer c674x library uses default coffabi format. Therefore, I hope that TI can provide eabi format aer c674x library,

Thank You!

  • Hello Eric,

    Could you please explain a bit more about what you are trying to do? For example:

    1. Are you trying to run AER on a DSP within a chip that has both ARM and DSP cores? If yes, which one? Some OMAP or other product? What is the ARM core that you have there?
    2. For AER applications you will have two interfaces: "near-end" TDM interface which is connected to your A/D, D/A and transducers (mic/spk) and "far-end" TDM or PKT interface which is exchanging signals with voice enc/dec. How do you plan to connect the near-end TDM interface? To the DSP or to the ARM? Keep in mind that on the near-end, Tx/Rx have to be in sync prior to providing them to aerSendIn() function.
    3. If you plan to handle all I/O on ARM side, you may be able to just create arm callable DSP library and do this (provided you sync'ed signals properly prior to passing them to the DSP). In this scenario, you are using the DSP as an accelerator to off-load ARM from doing the AER processing. However, if you plan to handle some of the I/O (e.g. A/D, D/A traffic) on the DSP, you will not be able to do this with just an arm-callable lib since you would need to implement a small application on the DSP that would integrate AER and properly route near-end signals.

    Please provide more info regarding this so we can answer your question properly.

    Finally, regarding the library format, I am assuming you are referring to the COFF and ELF formats of C674x library. (There are no other formats available.) The ELF format was not provided for C674x in the initial release of AER. It will be provided in the next release which should happen later this year.

    Until then, you may need to look if there is a version of c6runlib that could work with the COFF format for the DSP code. I guess that the object code format for the DSP and for the ARM do not have to be the same. These are two separate cores. You may have DSP code in COFF format and ARM code in ELF format and that should be perfectly fine. Question is just if you can find the utility that could take the COFF DSP code and create arm-callable library that is in your target format (COFF or ELF). I do not see much reason for object code formats on ARM and DSP to be the same (other than simplicity of implementing tools).

    Please let us know if this would answer your questions and feel free to ask additional questions.

    Regards,
    Bogdan

     

  • Hi Bogdan,

    Thanks for your answering. let me explain more detail information:

    I am developing video conference system on TI DM8168 platform which includes one arm cortex A8 processor and one C674x DSP processor. I plan to handle all I/O on ARM side and utilize c674x DSP to process aec (acoustic echo cancellation).

    In DM8168 ezsdk_5_01_01_80, TI provides the c6runlib tool (http://focus.ti.com/docs/toolsw/folders/print/c6run-dsparmtool.html) to build a arm-side callable dsp library , and we got a aec-aer c674x library from TI website (http://focus.ti.com/docs/toolsw/folders/print/telecomlib.html#supportandcommunity).  Therefore, I try to use c6runlib tool to build this aec-aer c674x library as a arm-side callable dsp library.

    The default cl6x compiler flag  includes  "--abi=eabi" in c6run_dir/platforms/TI816x/platform.mak. When I try to compile without --abi=eabi, it occurs some errors as follows:

    error #10016-D: --retain=*(xdc.meta) not supported when producing TI-COFF
       output files
    error #10016-D: --dynamic=exe not supported when producing TI-COFF output
       files
    error #10016-D: --retain=*(xdc.meta) not supported when producing TI-COFF
       output files
    fatal error #10011: cannot continue with specified options; aborting

    Therefore, I need someone familiar with c6run to help me building a arm callable COFF format dsp library, or I can wait for the release of the ELF format AER. So which month will TI release it this year?

    Thank You!

  • Hello Eric,

    Thanks for the additional info. I have forwarded your question regarding c6runlib tool to a few people and we will post the answer here once we get more information. The next release of AER will happen in Q4. We do not have the firm date yet. We will know more about the schedule by the end of July.

    Regards,
    Bogdan

  • Hi Bogdan,

    I posted related issue on DM8168 processor forum (http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/122547/438050.aspx#438050). From Joern's replying,  it seems that only ELF format is planned to be supported on DM816x, C6A816x sdk regarding to Chris Ring's comment about COFF/ELF here. Maybe you can check it with Chris Ring. And If so, I hope you can update the schedule of next release of AER afterward.

    Thank You. 

  • Hello Eric,

    The next release of AER will be 16.0.0 and the Beta should happen by the end of September. The GA should be done by the end of year. So, the ELF support for C674x will be added to that one.

    Best Regards,
    Bogdan