|
Re: How to use thread in papyrus-rt application and are there more samples projects? [message #1737999 is a reply to message #1737922] |
Thu, 14 July 2016 19:34 |
|
I already provided an answer to those question to your previous question. I'm reproducing them here for completeness.
Note that the Top.Controller file is a temporary measure until we implement threading support within the Papyrus-RT. It is provided for experimentation only and it will be replaced once with implement a better thread mapping capability.
The Top.Controller file is used to map a capsule role to an OS thread.
The syntax within that file is "[capsule|capsulePart] = OSThreadName". Each assignment needs to be on its own line.
For example:
Top = TopController => The runtime creates the "TopController" OS thread and assigns the Top capsule it.
Top.pinger = =PingerController => The runtime creates the "PingerController" OS thread and assigns the "pinger" capsule part from the Top capsule to it.
The "LEDEmbedded" model was meant to illustrate a design pattern to interface to hardware and was not meant to be executable.
We have not yet decided how we will approach the concept of "logical threads" and handle its migration to Papyrus-RT. This will be implemented as part of the "thread mapping" capability mentioned above.
/Charles Rivet
|
|
|
Powered by
FUDForum. Page generated in 0.03307 seconds