This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 66%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDA%3C/text%3E%3C/svg%3E)
hi, I'm just curious why the kernel limits the message_size of queue to upper 16 32-bit word. What can I choose to do if the msg size is bigger than 16 32-bit word size?
It looks that simply disabling the size check code in _txe_queue_create dose not help.
Thanks in advance for your help.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello @duan allen Thanks for contributing to this forum, If the below response is helpful, please click "Accept Answer" and upvote it So that it is useful to others as well.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 6%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
Queues are designed to pass small messages or pointers to bigger messages. I suggest you pass a pointer.
Thanks Scott, so this behaves like queue by reference. Can I assume that TX won't dynamicly apply memory inside any API and to let user to manage this instead?
@duan allen correct - ThreadX does not dynamically allocate any memory. ThreadX always leaves that up to the user to manage.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 23%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Scott,
I also read about this message limitation in ThreadX/Azure RTOS. It becomes a real problem if I need to pass some bigger packets through a queue. So I wonder if an advanced RTOS like this offers some straight-forward way to manage the actual messages that the queue points to or does this really have to be implemented manually? If it has to be done manually, are there any examples?
Thanks in advance,
Anguel
Hi Anguel,
ThreadX does not offer any way to manage the messages the queue points to, and we do not have any examples of queuing longer messages.
I see, this is really a limitation, AFAIK FreeRTOS offers up to 1024 bytes. Is there maybe some way to connect or chain two queues together? I actually need just a few bytes more, because 64 bytes is my data payload. So I could post the instructions to a queue with just a few bytes and the data to another queue with 64 byte messages. Would that work somehow?
Yeah, use two queues, or two entries in one queue.