• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 805 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.

Can I rebuild Codec Engine?

Flamingo
Expert 2290 points

Other Parts Discussed in Thread: OMAP-L137

I'm having lots of problems getting Engine_open to work. I hangs (currently while loading the server) or exits with no error message (SEM_pend status = 0?).

I'd like to add some GT trace statements in various places (Engine.c, possibly other packages).

I have the source, but I've seen nothing about how to do the build. I haven't seen a Makefile. Is it possible for a customer to build it?

 

  • 0
    TI__Genius 17205 points

    Flamingo said:
    Is it possible for a customer to build it?

    Officially, no.  This is mentioned in the release notes - Codec Engine is provided with non-rebuildable sources.  Rebuilding is not supported - mainly b/c there are lots of configurations (Linux, BIOS, WinCE, with/without DSP Link, etc) and devices, and support would be too high.

    Unofficially, depending on the release you have, you may have what you need to do the rebuild - every 'package' builds with package.bld script (just like the examples do).  You just need to get a config.bld script to define the right 'targets' and 'platforms' to build for, and use the same XDC tools build process the examples use.  I'd be supportive of a 'Hackers Guide to Rebuilding Codec Engine' wiki article - and would probably even help contribute to it - if anyone were so motivated to start one.  [;)]

    Since you're struggling with Engine_open(), what you may find useful is to turn on trace statements in DSP Link.  That _is_ rebuildable, and likely where any of your "additional CE trace" would point you anyway.  Typically, it's a config issue (e.g. memory map isn't right, etc).

    Chris

  • 0 in reply to Chris Ring
    Expert 2290 points

    The instructions I found for enabling trace in DSPLINK don't seem to apply to OMAP-L137. That is, the dsplinkcfg.pl perl script does not ask about enabling trace. Is there some easy way to enable trace in dsplink? (I rebuild it all the time, so I'm not terribly intimidated by it.)

  • 0 in reply to Flamingo
    Expert 2290 points

    Ah! I read the dsplinkcfg.pl script and found the line that says I should add the argument "--trace=1". That did it!.

  • 0
    TI__Mastermind 41665 points

    Flamingo said:
    I have the source, but I've seen nothing about how to do the build. I haven't seen a Makefile. Is it possible for a customer to build it?

    This is a bit out of date now, but since this thread shows up highly in Google I wanted to add to this thread that the ability to rebuild Codec Engine does exist, and there is a wiki article at http://tiexpressdsp.com/index.php/Rebuilding_Codec_Engine that gives some advice on how to do so (sort of a hacker's guide as Chris suggested), though it is not officially supported.