PITZ Laser Beam Line Control

Back to Index

LBL Startup procedure and files

At power-up the MV162 CPU starts the boot procedure executing a set of commands read in from the internal boot ROM. Some necessary parameters are set and the VxWorks operating system (including POSIX timer) is loaded. Finally a Startup script is executed which loads the LBL server executable(s) and starts its operation.

The contents of the internal boot ROM and hence the name and place of the Startup script may be changed by special commands using the CPU console.

The Startup script 

itself contains

  • a number of routeAdd and hostAdd command lines to tell the operating system which external hosts are allowed to communicate with the LBL CPU
  • the command line setting the server's working directory. This is extremely important because this is the place where the TINE system as well as the LBL server are looking for all the configuration files.
  • the command lines to load and spawn the time server program which gets and updates regularly the actual time from the central time server at DESY Zeuthen.
  • and finally the command lines to load and spawn the LBL server executable. As soon as the server is spawned it starts the LBL server configuration.

It is clear from the above that the user is completely free to make his own decision according to his taste for the places where to put the Startup script, the working directory and the executables, as long as those places are accessible by the CPU. 

An example of a Startup script can be find at page end.

At present, the following 

File scheme for the LBL server 

has been adopted :

  • The directory LBLPath holds everything we need in three sub-directories : 
         LBLPath/common
         LBLPath/work and 
         LBLPath/nettime    .

  • The sub-directory LBLPath/common holds the Startup script with the name netset.cmd. Also it holds some special files and directories which are described elsewhere (cf.  LBL server output). 

  • The directory LBLPath/work/config is defined as the working directory.

  • The directory LBLPath/work/project holds the LBL server project in terms of the WindRiver Tornado 2.0 development system, which automatically means that the LBL server executable is in LBLPath/work/project/MC68040gnu, its name is BEAMLINE.out.

  • The source code of the LBL server is contained in LBLPath/work/source.

  • In the same manner, the sub-directory LBLPath/nettime holds the LBL time server, the executable being in LBLPath/nettime/project/MC68040gnu with the name NETTIME.out. It does not need any configuration files.

In fact, there is a fourth sub-directory LBLPath/dev with the same structure as LBLPath/work. As the reader may guess, it holds a development version of the LBL server. By changing a few lines in the Startup script and rebooting the CPU it is possible to switch back and forth between working and development versions of the LBL server.

 

Example: Startup script

routeAdd "141.34.100.17","141.34.30.1"
routeAdd "141.34.30.11","141.34.30.1"
routeAdd "141.34.30.13","141.34.30.1"
routeAdd "141.34.30.12","141.34.30.1"
routeAdd "141.34.100.28","141.34.30.1"
routeAdd "141.34.3.155","141.34.30.1"
routeAdd "131.169.150.130","141.34.30.1"
routeAdd "141.34.1.22","141.34.30.1"
routeAdd "141.34.20.156","141.34.30.1"
hostAdd "paris","141.34.100.17"
hostAdd "corvus","141.34.30.11"
hostAdd "bubo","141.34.30.13"
hostAdd "aquila","141.34.30.12"
hostAdd "ventus","141.34.100.28"
hostAdd "znpgut","141.34.3.155"
hostAdd "timesrv.ifh.de","141.34.1.22"
hostAdd "mstntduval02.desy.de","131.169.150.130"
hostAdd "znphomerl.ifh.de","141.34.20.156"
cd "LBLPath/work/config"
ld < LBLPath/nettime/project/MC68040gnu/NETTIME.out
sp mytime
ld < LBLPath/work/project/MC68040gnu/BEAMLINE.out
sp RPCServer

Back to Index

Last update by R. Leiste on 16.12.2003 (leiste@ifh.de)