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

What is special about the Syslink Message Queue name?

Lee Holeva
Genius 4615 points

In the Syslink sample code the Message Queue name is given in the MessageApp_common.cfg.xs file as:

Program.global.MSGQ_NAME      =      "MSGQ_";

I tried changing this name in the .cfg file of my DSP code, consisting of largely copy-and-past from the MessageQ sample, and the MessageQ_create function failed to create the host's queue.  I changed the name back to waht it is in the sample, and the code worked.  What is going on?

Lee Holeva

 

  • TI__Mastermind 18260 points

    Strange, I wouldn't expect the name to matter much.  This name goes into a global variable (named MSGQ_NAME) and is then used in a sprintf() to construct the local MessageQ name which is then passed to the host so that the host knows what name to look up in the MessageQ_open() call.

    Can you verify that the name is as expected when passed to MessageQ_create()?

    If this problem still persists, can you attach the DSP code and config files?

    Regards,

    - Rob