Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Sun, 1 May 2011 22:33:08 -0500

Hi Zen,

On Sunday, May 01, 2011 21:38:53 Szalata, Zenon M. wrote:
> Till, Thank you for your input.
> I understand your suggestion.
> There is another related issue, which I am not sure about.
> In the existing driver code, the task is created with a call to vxWorks
> routine taskSpawn(...).  Here is a code fragment:

Actually if you follow Till's suggestion properly you would replace *all* the 
calls to vxWorks-specific routines in the driver with their EPICS equivalents.  
Instead of taskSpawn() you use epicsThreadCreate(), etc.  This has the 
advantage that the resulting code can be compiled for and will run on RTEMS, 
but it is a bit more work since the EPICS versions are not all direct 
replacements for their vxWorks counterparts.  Eric Norum produced a Wiki page 
describing the conversions of the various routines, which you can read at this 
link:
http://www.aps.anl.gov/epics/wiki/index.php/How_to_make_your_EPICS_driver_operating_system_independent

If you don't want to put that much effort into this, on vxWorks you can just 
cast an epicsThreadId into an integer for use as a task-id in vxWorks routines 
and vice-versa.  That is not possible on other operating systems though.

HTH,

- Andrew (waiting for Obama's special news conference to start)

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System