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.

VoLIB for TMS320C674x?

Other Parts Discussed in Thread: TMS320C6747

Hi Team,

 We are using tms320c6747 (in the evm omap l137/c6747) for voip application. We need packet loss concealment, acoustic echo cancellation/removal and other features listed under VoLIB. But unfortunately c674x has AER/AEC but not VoLIB.

Can you please let us know when you would be releasing VoLIB for TMS320C6747x?

Thanks.

  • Hi,

    To be precise, VoLIB offers line echo cancellation, not acoustic.  Acoustic echo cancellation is available via the AER component.  VoLIB does offer a component (PLC) for packet loss concealment.

    VoLIB and FaxLIB versions 2.0.0 will be released by early April.  VoLIB will not have explicit C674x support, but will support C64x+ in ELF format -- which may be used on C674x.  Is this acceptible?

    Regards,
    Charlie

  • Hi Charlie,

    Thanks for your reply.

    Actually we are working with AER to get it to work with C6747. Once this works we are planning to use PLC (in VoLIB) with C6747. Hence, I would let you know how it goes after I start to work on PLC (using ELF). By the way , is there any easy way to get the output in .elf instead of .out ? (My build properties/ c/c++build/c6000 compiler/runtime model options/ has only coffabi and eabi options (no elf options). If I use eabi instead of coffabi, will I be able to use PLC of VoLIB with c6747?)

    thanks.

  • Hi Tharangini,

    The upcoming VoLIB release (2.0.0) will provide all components in both ELF and COFF format.  You will need to use the EABI for ELF builds which will then allow you to use the PLC ELF library on C674x.

    Regards,
    Charlie

  • CharlieF,

    What time is the VoLIB release? And the released FaxLIB(2.0.0) still can't support c674x elf format, can you provide more detail informations about these two library? Thank you!