• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 252 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.

How is codec found under DM6467T EVM demo environment

Helmut Forren
Mastermind 6805 points

I have a DM6467T EVM that boots up to run the demos, I believe starting with the "interface" program and able to run the "encodedecode" program.

Meanwhile, I can look at the encodedecode source code ("a 'code' mouthful said the woodchuck ;)") and see some things.  In encodedecode.cfg, there's var demoEngine = Engine.createFromServer("encodedecode","./bin/cs.x64P","ti.sdo.server.ds");  As I read the doc, I think this means cs.x64P is the "codec server".

I'm always confused about what exists, is used on, is made for, belongs to, or whatever with respect to the development host and the target.  I see that the last two parameters to createFromServer are consistent with folders on the development host and NOT on the target.  Therefore, encodedecode.cfg must be used at what I'll call "build time" by the development host.

So back to the target, is simply cs.x64P that exists at /opt/dvsdk/dm6467/cs.x64P the codec server and is the actual codec embedded in it?

Next, this means that if I want to quick-and-dirty substitute a different codec for encodedecode to use, I need to effect a change in cs.x64P existing on the target?  I would probably do this by changing those second two parameters of encodedecode.cfg.  Then I'd go about creating my own ???.x64P.  And I'm hoping that this is exactly what I've already been trying to do, with different forum thread help requests, under the guise of "building my own codec server".  I.E. the "output" from "build my own codec server" is eventually nothing more than this file existing on the target. (I guess a package is the direct output, but once encodedecode is configured to use it, I end up with automagically or else just copy over the .x64P file to the same folder as encodedecode.)

Thanks,

Helmut

 

  • 0
    TI__Expert 3220 points

    Hello,

    Yes, cs.x64P is the codec server. A codec server is essentially a DSP image with the frameworks, RTOS and codecs in it. For information on how to add a codec (contained in a "codec package") to a server you can use the wizards, and if you use DVSDK 4.00 there is a section in the Software Developer's Guide which showcases how to add mp3 to the server.

    The first parameter to createFromServer() is a string name with which the engine (in this case remote server, doesn't have to be) is identified. You'll use this from the Engine_open() call in your app. Each codec is also has a string name which is used to identify the codec when instantiating it, the wizards will help you understand this.

    The default location of the codec server is in the same directory as the application, you can override this using: demoEngine.server = "/target/path/to/cs.x64P"; in your cfg file.

    Regards, Niclas

  • 0 in reply to Niclas
    TI__Genius 17205 points

    FYI, more Engine.createFromServer() details here.

    Another article that may help you understand the big picture is Codec Engine Roles.

    Chris

  • 0 in reply to Chris Ring
    Mastermind 6805 points

    Thanks, Niclas & Chris.

    Niclas, it helps to know what the final outcome will be.  Please note I'm already part way through creating a codec server.  Just trying to get past one really bad hangup for the past two days.  Wanted to triple check that there was a rainbow at the end of the pot of gold (realized my error half way through typing analogy, but left it for humor, I actually meant gold...rainbow).

    Chris, Thanks for hanging in there with me.  I had found your first link already, but not the second.  I'll read over your second (Codec Engine Roles).   Still very stuck on building DSP Link on WindowsXP for DM6467T EVM running Arago Linux.  ref: http://e2e.ti.com/support/embedded/f/355/t/88501.aspx

    -Helmut