• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 273 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.

IPC Examples Confusion

MikeH
Guru 15580 points
Other Parts Discussed in Thread: OMAP-L138, SYSBIOS

I am attempting to learn SYSBIOS by using the examples in C:\Program Files (x86)\Texas Instruments\ipc_1_21_02_23\packages\ti\sdo\ipc\examples\multicore\evmOMAPL138. I come from a background of using DSP/BIO on my DSP (6748 on the OMAP-L138) and am familiar with .cfg files and the use of XGCONF to view and modify the BIOS configurations. However, the "notify" example includes a notify_common_cfg.xs file. I have scoured both the SYSBIOS User Guide and the IPC User Guide but find no mention of "common" files, much less "cfg.xs" files. Can someone explain what the "common" file is for and how it is generated? And were it is documented?

Thx,

MikeH

 

  • 0
    Genius 4375 points

    There's nothing special about the name 'notify_common.cfg.xs.': it is just a name given to a XDCScript file that is shared by both notify_dsp.cfg and notify_arm.cfg.  By convention, BIOS & IPC use the '.cfg.xs' extension when a .cfg script is included by other .cfg scripts.  notify_common.cfg.xs could be renamed to notify_common.cfg or even notify_common.txt as long as the correct file name is used in xdc.loadCapsule.

    I.e. in notify_dsp.cfg:

    xdc.loadCapsule("notify_common.cfg.xs");

    We have chosen to put configuration that is common to both the ARM and the DSP in a common config file to highlight the fact that both images share certain common configuration (i.e. SharedRegion, Ipc,etc).  Copying-&-pasting the entire contents of the .cfg.xs into the line containing xdc.loadCapsule would result in semantically identical configuration.

    I agree, IPC could better describe the various files that comprise each example.  I've filed an enhancement request against this (SDOCM00079341).

    Shreyas