• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 242 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.

syslink configuration questions

james conway
Intellectual 780 points

Other Parts Discussed in Thread: OMAP3530

I’m migrating from dsplink to syslink on a 814x. platform. The previous platform was an OMAP3530 that had dsplink configured to use only the PROC component on the HLOS. The only functionality required from dsplink was to load the DSP image, take the DSP out of reset, and read/write memory shared between the DSP and host. Consequently, the DSP code did not use dsplink at all.

It appears that the syslink ProcMgr component provides the same functionality as dsplink’s PROC component. I’m trying figure out how to configure syslink on the HLOS  so that only the ProcMgr component is installed. How is this accomplished?

 If only the ProcMgr is used on the HLOS, is it still necessary to configure IPC on the RTOS? If so, what component is required?

  • 0
    TI__Mastermind 18260 points

    It is currently not possible to build SysLink with a subset of capabilities.  Both the HLOS user & kernel sides of SysLink contain high-level "setup" functions which in turn setup lower-level modules, all without configuration support for disabling/enabling the lower-level modules.  ProcMgr itself needs many of these lower-level modules.  While it would be technically feasible to author SysLink source code that doesn't reference unused modules, this is not the way it is currently written.

    However, the RTOS side does not need to have any SysLink or Ipc stuff if you don't use Ipc content.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Intellectual 780 points

    Rob,

    Thanks for the clarification.

    Jim