• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 285 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.

About MSGQ

Kaiqi Yang
Expert 1015 points

We know that MSGQ is a variable-length messaging protocol,is there any size limit of the message in MSGQ?

  • 0
    TI__Guru* 84110 points

    The message is contained within the struct that you define using the prescribed header:

    typedef struct MyMsg {
        MSGQ_MsgHeader header;
        ...
    } MyMsg;

    The C compiler may have limitations on the size of a struct. Please refer to the appropriate C Compiler User's Guide for your version of the compiler.

    The MSGQ_getMsgSize function returns the size of the message as a 16-bit short, so this may represent an effective upper limit of 65535 bytes, or more likely 65532 bytes.

    You can always pass a pointer to a large block if you wish.

    Regards,
    RandyP

     

    If you need more help, please reply back. If this answers the question, please click  Verify Answer  , below.

  • 0 in reply to RandyP
    Prodigy 110 points

    HI，RandyP：

            Now，I am facing to same questions,I want to extend the buf in msgq.

    My  program below:

    #define dsp_arm_datasize 256

    typedef struct ControlMsg
    {
    MSGQ_MsgHeader header;
    Uint16 command;
    Char8 arg1[ARG_SIZE];
    // Uint32 arg2[128];
    Uint16 arg2[dsp_arm_datasize];
    } ControlMsg;

    But when I extend the dsp_arm_datasize,  the program can not go well. 

    How can I extend the buffer of dsp send to arm in this way?

    Best regards！


  • 0 in reply to xiaohuan lee
    TI__Guru* 84110 points

    Xiaohuan Lee,

    Please post your question on a new thread in the BIOS Forum, found under Tools & Software. You may wish to post a link to the new thread here, for reference.

    On your new thread, please include the device part number, the version of CCS and the version of BIOS that you are using.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Prodigy 110 points

    Hi  RandyP:

          I post a new in this address: http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/254962.aspx 

    Best regards!