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.

Confused by messageQ, syslink & .xe66

Hi people,

After reading the MCSDK 3.x UG I understood that messageQ had replaced syslink, at least for Keystone II (syslink is not mentioned once in the UG).

The MCSDK points me to the Matrix (App Launcher) User Guide, but this has .xe66 executables, which after searching around appear to be associated with syslink.

So, to launch applications from the App Launcher, do I rename my executables from .out to .xe66?  I have found 1/2 dozen queries re this in the forum but they don't resolve this for me.

Yours sincerely,

dazed and confused.

  • Bernard,

    The old SysLink 2.x component has been replaced by a new component called 'IPC 3.x'. Both components have a module called MessageQ, which should behave the same. The MCSDK ships with the new IPC 3.x component.

    The executable extension '.xe66' is a generic extension used for all DSP executables. It does not have a binding to either SysLink nor IPC. Executables built with either component might have the same extension. You can also name our executable with the '.out' extension.

    I don't know anything about the Matrix Application Launcher. Maybe someone on the MCSDK team can answer that question. But you can also launch your programs by connecting to your EVM and running them in the shell.

    ~Ramsey

  • Ramsey,

    Thanks,

    Bernard