VxWorks: Unable to open startup script.

[khan...@gmail.com]

Hello,

I've set up my ROM boot for a start up script. But when it boots, it's
not able to open start up script and an
error message is printed on the console:

Unable to open start up script /flash/startup

This is how my ROM boot parameters look like:

boot device : tffs=0,0
unit number : 0
processor number : 0
host name : host
file name : /flash/side1/scmclobjs/vxWorks.st
inet on ethernet (e) : 10.207.101.55:0xffffff00
host inet (h) : 10.207.101.2
gateway inet (g) : 10.207.101.1
user (u) : isb
ftp password (pw) : common
flags (f) : 0x0
target name (tn) : isb000
start up (s) :/flash/startup

Please note that boot file and start up script both have the same root
but still the opening of
start up script fails. It's able to open vxWorks.st.

Any idea what's the problem here?

Thanks for your time.

[Michael R. Kesti]

khan...@gmail.com wrote:

What is the error message?

What version of VxWorks and Tornado or WorkBench are you using?

--
========================================================================
Michael Kesti | "And like, one and one don't make
| two, one and one make one."
mrkesti at hotmail dot com | - The Who, Bargain

[khan...@gmail.com]

On Aug 3, 9:33 pm, "Michael R. Kesti" <michaelke...@nospam.net> wrote:

>     mrkesti at hotmail dot com     |          - The Who, Bargain- Hide quoted text -
>
> - Show quoted text -

Thanks. The error message is:

Unable to open startup script /flash/<script file>

The VxWorks is 5.4.2.

[Michael R. Kesti]

khan...@gmail.com wrote:

I've used startup scripts only in VxWorks 6.x where one must configure
the kernel to include INCLUDE_STARTUP_SCRIPT. I suspect this is also
the case in 5.4.2. Does you kernel include INCLUDE_STARTUP_SCRIPT?

[khan...@gmail.com]

On Aug 3, 10:29 pm, "Michael R. Kesti" <michaelke...@nospam.net>

Yes, it does include INCLUDE_STARTUP_SCRIPT. If it hadn't, it'd not
call usrStartupScript function which
actually prints the error message regarding not able to open the start
up script. Thanx.

[doug65]

Hello, khank...@gmail.com

Regarding : Unable to open startup script /flash/<script file>

I worked around the same problem by using the full path name in the
startup script line.

I.e.,

[VxWorks Boot]: @

boot device : gei

unit number : 0
processor number : 0

host name : servodev
file name : c:/boot/vxServo.st
inet on ethernet (e) : 10.1.1.104
host inet (h) : 10.1.1.114
gateway inet (g) : 10.1.2.1
user (u) : doug
ftp password (pw) : gibs
flags (f) : 0x0
target name (tn) : target4
startup script (s) : servodev:c:/WindRiver/goc3

if I used startup script (s) : c:/WindRiver/goc3 , I would get the
same error message, even though the console prompt showed that I was
in the directory c:/WindRiver and the file, goc3 was present. I.e.,
after the error message, I'd do ..

-> goc3 and my startup script would work.

Please let us know if this works for you.

Thanks,

Doug

[khan...@gmail.com]

Thanks, Doug. Please note that my start up script is at the target
itself and not at the host. I've tried giving target name, drive name
etc. But it just
doesn't work.

[Kai]

Your problem is really strange. To configure the startup script, one
must configure

1 INCLUDE_STARTUP_SCRIPT component
2 the correct startup file in DEFAULT_BOOT_LINE or [vxworks boot]

pls make sure

1. u can access /flash/startup after vxworks boot
u canuse
> < /flash/startup
to test

2 if OK,
I guess maybe DEFAULT_BOOT_LINE shouldn't be larger than 255 bytes. If
so, the startup script can't be recognized, for example, only "/flash/
sta" is valid.

Hope this help.