• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 619 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.

Link Arbiter Daemon Support in Codec Engine 3.x

RV
Expert 2030 points

Hi All,

 

What is the status for LAD support in CE version 3.x  for SYS/LINK and linux users ?

 

RV

  • 0
    TI__Mastermind 22760 points

    RV,

    The plan is not to have LAD support in CE 3.x.  For multi-process systems, someone will have to load and start the slave processor, and then apps will just attach to it. In this use case, Codec Engine would not load the slave.

    Regards,

        Janet

  • 0 in reply to janet
    Expert 2030 points

    Hi Janet,

    My primary use case is  running a DSP Codec Server on DSP and accessing it from Linux Arm A8.

    There might be more than one application using Codec engine in Linux, for example. Who then starts the codec server first time? Bootscript may be?

    Then, I am assuming, all the linux client side applications have to know and link to the stubs (at compile time) that are supported by the single DSP server binary that is currently running on the DSP for things to work properly.

    Also how is the DSP codec server shutdown handled?

    Regards

    RV

    PS: I also see http://processors.wiki.ti.com/index.php/Codec_Engine_Application_Developers_Guide mentions loading engine from a database. Lots of new api calls are listed as well. Hopefully more questions will be answered in the engine API guide.

  • 0 in reply to RV
    TI__Mastermind 22760 points

    RV,

    We haven't worked out all the details of how this will work yet, but you will need one app to load and start the DSP.  We may add a configuration parameter to Codec Engine specifying whether or not to load and start the DSP, so the other Codec Engine apps will not load the DSP when they are run.

    All host side apps need to link in the stubs. This happens automatically when using Engine.createFromServer() in the configuration file.  There is also a new API, Engine_addStubFxns(), to add stub functions to an internal table, in case Engine.createFromServer() is not used in configuration.

    Regards,

        Janet