dave
--
=============================================================
Dave Reid da...@radonc.washington.edu
UW Medical Center (206)548-4536
Radiation Oncology Dept.
Seattle, WA
The following code illustrates a basic startup script showing
a few of things that can be added:
----------------------------------------------------
#
# VxWorks startup script
#
# Add user login names and passwords
loginUserAdd "user1", "rQrTEzeRze"
# Set the shell prompt and the login text
shellPromptSet "vxWorks ->"
loginStringSet "MVME147 vxWorks\n\nlogin: "
# Add a machine to the host table
hostAdd ("lws1", "172.71.4.4")
# Define the backspace as the delete key
tyBackspaceSet 0177
# Change directory to the application and load it
cd "/system_code/v1.1"
ld < syscode
# Run the application
sp maintask
-----------------------------------------------------
Things to note are:
1. You need to put the location of the startup script
in the boot parameters, for example:
boot device : ln
processor number : 0
host name : Mars
file name : /system_code/vxWorks
inet on ethernet (e) : 172.71.9.222:ffff0000
inet on backplane :
host inet (h) : 172.71.9.70
gateway inet (g) :
user (u) : user1
ftp password (pw) :
flags : 0x08
target name (tn) : Phobos
startup script : /system_code/sc.stp <<<<<
other (o) :
2. The user name (u) above should be the name of a user
that has access to files in the /system-code directory
since VxWorks uses the username to 'login' and get the
file (see the manual).
3. The user has a '.rhosts' file in their root directory
containing the target name of the VxWorks rack (again
see the manual).
Hope that helps. :)
Gareth Jones
RGO Technology Division
And path for the script as boot parameter during auto count-down
time.
As far as your symbol errors during ld, make sure your vxWorks
symbol table is downloaded. I think it's INCLUDE_SYM_TBL.
Note also that when you load your application this way, you
can no longer debug it using Tornado's GUI, as the target server
on your host PC doesn't have any of your application's symbols
(well, I use 1.0; perhaps 1.0.1 has a work-around already).
Raymond Yeung