VME Boot File -- For Experts |
|
~paronl/daq/VXWORKS, and the name of the
bootfile for a given VME crate is the node name of the crate followed
by .boot. Special-purpose bootfiles may have additional
characters between the two.
Generally you should not modify the contents of an existing bootfile, but make a new bootfile with the changes you want and use that.
To change which bootfile the VME crate uses, change the crate's boot parameters.
Here is the present content of a typical bootfile,
~paronl/daq/VXWORKS/halladaq6.boot. The text in red
after the pound signs are comments and are not present in the actual
file.
#Allow telnet to this crate loginUserAdd "paronl", "SbdedReRQ9" #Load and spawn CODA routines cd "/apps/coda/1.4.2/VXWORKS68K51/bin" ld < coda_roc taskSpawn "ROC",110,spTaskOptions,8000,roc_coda #set up names for Hall A hosts hostAdd "adaqh2.jlab.org","129.57.164.3" hostAdd "adaqh2","129.57.164.3" hostAdd "adaqh3.jlab.org","129.57.164.5" hostAdd "adaqh3","129.57.164.5" hostAdd "adaqh4.jlab.org","129.57.164.7" hostAdd "adaqh4","129.57.164.7" #Load HAPPEX routines cd "~paronl/bin" ld < common_vme.o ld < bmwClient.o ld < initVme.o #commented out lines #cd "~paronl/src/bmw/" # load dummy server for test purposes #ld < bmwServer.o #sp bmwServer #cd "~paronl/daq" #do boot time initialization for HAPPEX initVme "~paronl/daq/vmeConfig_halladaq6" #scaler server is not normally needed but included here for tests # load scaler server ld < ~paronl/src/bobscaler/scaser.o taskSpawn "scalServ",100,spTaskOptions,10000,bobServer