Andrew Johnson wrote:
Hi Dirk,
On Wednesday 19 August 2009 05:42:19 Dirk Zimoch wrote:
Generally, vxWorks 6 has some new features (e.g. real time
processes) which
are not used by EPICS. vxWorks 6 still supports running
applications, e.g.
EPICS, in "kernel space" (which is all you had in vxWorks 5).
However, the
vxWorks shell has changed a bit and not everything that worked in
vxWorks 5
startup scripts might work in vxWork 6 startup scripts (I had
difficulties
sourcing other scripts). I think I can tell more once I have the
MVME4100
running.
I wonder if your sourcing scripts problem is the the same issue we
found when we upgraded to vxWorks 5.5.2 - if you use the construct
ld < ioc.munch
in your startup script then all subsequent shell redirections to
source other scripts get ignored. The solution is to replace the
above line with this
ld 0, 0, "ioc.munch"
which permits later shell source commands to operate normally. I
think it's highly likely that Wind River broke both versions of the
target shell at the same time...
I am also not having problems with this.
However, in the beginning I bumped into this as well.
We are using vxWorks 6.6 on some projects here at SLAC:
Using the vxWorks project facility please do the following:
================================================================================
vxprj parameter set SHELL_COMPATIBLE TRUE
vxprj parameter set SHELL_TASK_OPTIONS "(VX_FP_TASK | VX_UNBREAKABLE |
COPROCS_ALL)"
=================================================================================
I had to make similar changes when I was at the SNS as well.
