Experimental Physics and
Industrial Control System

Dirk Zimoch <[email protected]> · Thu, 20 Aug 2009 13:35:18 +0200

Hi all,

All redirects don't work, neither "ld < library" nor "< script". The startup

script terminates after these redirects. I also found that a "cd" within the

startup script is reversed after the script ended.

I use
SHELL_COMPATIBLE TRUE

but SHELL_TASK_OPTIONS has the option VX_PRIVATE_ENV set. Maybe that is the

problem. I tried 6.2 and will try 6.7 soon.

Can anyone check these configs:
/* Shell default configuration */

#define SHELL_SECURE		FALSE
#define SHELL_START_AT_BOOT	TRUE
#define SHELL_COMPATIBLE	TRUE
#define SHELL_DEFAULT_CONFIG	\
"LINE_EDIT_MODE=,LINE_LENGTH=256,STRING_FREE=manual,INTERPRETER=,VXE_PATH=.;/romfs"
#define SHELL_FIRST_CONFIG	NULL
#define SHELL_REMOTE_CONFIG	NULL
#define SHELL_TASK_NAME_BASE	"tShell"
#define SHELL_TASK_PRIORITY	1

#define SHELL_TASK_OPTIONS (VX_FP_TASK | VX_UNBREAKABLE | COPROCS_ALL |

VX_PRIVATE_ENV)

I am using INCLUDE_SHELL but none of
INCLUDE_SHELL_VI_MODE	
INCLUDE_SHELL_EMACS_MODE
INCLUDE_SHELL_INTERP_C	
INCLUDE_SHELL_INTERP_CMD

Should I include any of these?

Dirk

Ernest L. Williams Jr. wrote:

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.

Sorry, I forgot to add you must rebuild your kernel after these changes:

vxprj build

Cheers,
Ernest

Thanks,
Ernest

- Andrew

--
Dr. Dirk Zimoch
Paul Scherrer Institut, WBGB/006
5232 Villigen PSI, Switzerland
Phone +41 56 310 5182

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System