Can ThreadX Module export queue?

Question

Can ThreadX Module export queue?

HugPeter-9392 246

Hello

I wonder if it is a good idea or design when a ThreadX module creates a queue and then exports this queue to the residential application. E.g. by use of txm_module_application_request service and passing a pointer to the queue. The residential application uses this queue to send messages to the ThreadX module. Our software runs on cortex-m33, maybe also on cortex-m4.

Which is the recommended memory from which the queue (TX_QUEUE) and the queues buffer gets allocated? Why?

Makes it a difference when TrustZone is enabled?

Makes it a difference when the queue gets forwarded to another ThreadX module 2. Then the module 2 would send messages directly to module 1.

Thanks for support.

Peter

Rosa Alden 120 Reputation points

2023-05-26T16:24:24.74+00:00

Hello,

Yes, the ThreadX module can export a queue. ThreadX is a real-time operating system (RTOS) designed for embedded systems, and it provides various inter-thread communication mechanisms, including queues. A queue is a data structure that allows multiple threads to communicate by sending and receiving messages or data items.

In ThreadX, you can create and manage queues using the provided API functions. These functions enable you to initialize a queue, add data items to the queue (enqueue), retrieve data items from the queue (dequeue), and perform other operations such as checking the queue's status.

When you say "export" a queue, it's unclear what you mean. If you're referring to sharing or accessing a queue from external modules or threads, ThreadX allows you to pass queue references between threads or modules. This enables different parts of your system to interact with the same queue, facilitating communication and synchronization between threads.

Overall, ThreadX supports creating, managing and sharing queues, making it possible to export queues for inter-thread communication in embedded systems.

Answer accepted by question author

0 additional answers

Your answer

Rosa Alden 120 Reputation points

2023-05-26T16:24:24.74+00:00

Hello,

Yes, the ThreadX module can export a queue. ThreadX is a real-time operating system (RTOS) designed for embedded systems, and it provides various inter-thread communication mechanisms, including queues. A queue is a data structure that allows multiple threads to communicate by sending and receiving messages or data items.

In ThreadX, you can create and manage queues using the provided API functions. These functions enable you to initialize a queue, add data items to the queue (enqueue), retrieve data items from the queue (dequeue), and perform other operations such as checking the queue's status.

When you say "export" a queue, it's unclear what you mean. If you're referring to sharing or accessing a queue from external modules or threads, ThreadX allows you to pass queue references between threads or modules. This enables different parts of your system to interact with the same queue, facilitating communication and synchronization between threads.

Overall, ThreadX supports creating, managing and sharing queues, making it possible to export queues for inter-thread communication in embedded systems.

Answer 1

Scott Azure RTOS 4,051

Hi @HugPeter-9392 That is the preferred way to do it - have the module create a queue and share a pointer to that queue with the resident application. Any object (e.g. a queue) that a module creates will be allocated from the pool created by txm_module_manager_object_pool_create. Modules must use txm_module_object_allocate((void*)&queue_0, sizeof(TX_QUEUE)); to allocate the queue object. The queue buffer also needs to reside either in the module's data region or in a shared memory region, otherwise ThreadX will return an error. Alternatively, the resident application can create a queue and the module can use txm_module_object_pointer_get_extended to get a pointer to the queue for sending and receiving messages. This also applies to your last question about inter-module communication, one module can create a queue and the other can use txm_module_object_pointer_get_extended to get a pointer to that queue. See attachment for a module-module example. demo_module1.txt

Regarding TrustZone, ARM and Microsoft recommend running the RTOS and user application in non-secure space. Queues and their buffers would need to be created in non-secure space.

HugPeter-9392 246 Reputation points

2023-02-03T12:39:32.6+00:00

Thank you, very helpful. Today a new question raised in a different context.

Background

We will get a protocol stack of a third party. Our architecture says that protocol stacks should go into the residential application. The residential application sticks to a specific print. So the peripheral driver is also there.

On the same print different applications will be developed in the future. Therefore, the application logic is in a ThreadX module. Each application exposes different data on the communication stacks.

The protocol stack has an API that tightly sticks to the application specific data definition. This is the definition of the information that gets exposed on this protocol.

Question

Is it possible that a ThreadX module exports pointers to own RAM and ROM locations to the residential application? Are there restrictions that apply to these RAM and ROM locations?

Thanks for support.

Peter
Scott Azure RTOS 4,051 Reputation points

2023-02-03T18:28:28.8866667+00:00

Hi Peter,

The resident application has full access to all memory (including module memory), so a module can export pointers to the resident application.
HugPeter-9392 246 Reputation points

2023-02-03T19:05:32.8266667+00:00

Very fine. Thank you.

Share via

Can ThreadX Module export queue?

0 additional answers

Your answer