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.

Is codec engine a framework?

hi all

Is codec engine a framework?if so,what is the difference between the codec engine and xdias framework components?

http://focus.ti.com/docs/toolsw/folders/print/tmdmfp.html

This page describes the functions of them. They have the same functions of providing DMA and scratch memory resources .

Are they all residing in the environment of DM6446?

Thanks.

  • Baici, I think code engine overview will explain your first quesion.  I hope it is helpful.

    About the second question, I don't know what do you mean about "the environment of DM6446". Could you explain it?

    Thanks.

  • To add to Lorry's excellent suggestion, codec engine framework encompasses all the other software components you mentioned; codec engine framework depends on those components and cannot function without them (although the individual components can stand on their own).  More specifically, the flow from top-down looks something like codec-engine ---> XDM ---> XDAIS ---> Reference Frameworks and DSP/BIOS.

    And yes, all this software is included as part of DM6446 DVSDK.

  • Thank you all.

    My second question means whether both codec engine and xdais framework are in the SDK. And I konw the answer is yes.

    But in my opinion ,the flow from top-down looks something like codec-engine ---> Reference Frameworks and DSP/BIOS---> XDM ---> XDAIS.Because codec engine will call the functions of the Reference Frameworks to accomplish his mission,and Reference Frameworks will call the functions of XDM (ialg_fxns).Am I right?

  • Apologies, I should be using the term Framework Components instead of Refernce Framework; that said, DSP/BIOS is the operating system (OS) for the DSP and is more often than not, the bottom most software layer.   

    With regards to the framework components, it is a bit more complex than a simple top-down or bottom-up relationship.  I always thought of them as lower level (driver like) software to abstract specialty hardware such as DMA controller; this is why I think of it as lower level code along or right above the OS.  However, you are correct that Framework Components query the XDAIS algorithm to inquire about the resources it needs before separating them for the XDAIS algorithm; you see, one of the primary goals of the XDAIS standard is to allow algorithms from different vendors to integrate nicely into a common system; to accomplish this, all algorithms need to play nicely and ask (or more correctly tell when asked) the reference framework for the resources it needs.  That said, once the XDAIS algorithm is given a resource(e.g. DMA channel), it calls on (you guessed it) the framework components (e.g. ACPY3) to access that resource.  As you can see, the relationship is actually bi-directional. See the following doc for more details http://focus.ti.com/lit/an/spraag1a/spraag1a.pdf.

    In the end, these are just names; the important thing to note is that we provide the complete software framework and necessary documentation and examples to allow you to integrate your algorithm into this framework.