You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 21
Next »
How-To setup the CPU and IOC boot directories:
The instructions differ between production and development due to permission restrictions in production.
Production: lcls, lcls2, facet, testfac
- Send email to Ken Brobeck requesting:
- create controls infrastructure for a new linuxRT CPU and IOC to a specific facility production server.
- includes $IOC_DATA/<cpu,ioc> directories
- includes $IOC_DATA/<ioc>/<autosave,autosave-req,restore,iocInfo,archive> directories
- add CPU boot information to the DHCP configuration file, and reboot the DHCP server. Ken will need the following details:
- Which facility the CPU will boot (e.g. facet, lcls, lcls2, testfac). Thins indicates the path to the startup.cmd script and the DHCP server.
- MAC Address of the CPU
- The CPU EPICS target architecture (e.g. linuxRT-x86,linuxRT-x86_64,etc)
- Proceed to Development Step #3
Development: dev
- Create the $IOC_DATA directory for your cpu and iocs as follows:
- cd $IOC_DATA
- Create the $EPICS_IOCS cpu and ioc boot directories
- cd $EPICS_IOCS
- mkdir cpu-<area>-<subsystem-prefix><2-digit#>
- mkdir sioc-<area>-<subsystem-prefix><2-digit#>
- Setup cpu directory files
- cd cpu-<area>-<subsystem-prefix><2-digit#>
- Setup relative symbolic links to the common startup script and EPICS version:.
- ln -s ../common/st.cmd.linuxRT.cpu startup.cmd
- ln -s ../common/bin/<epics base version> epicsSpecificRelease
- Generate the file kernel-module.cmd. This file load kernels modules and drivers: kernel-modules.cmd
- for examples click here.
- Setup ioc directory files
- cd sioc-<area>-<subsystem-prefix><2-digit#>
- cp ../template/startup.cmd.linuxRT startup.cmd
- edit startup.cmd
- replace <ioc> with your ioc name.
- change path of the EPICS_IOC_APP in your st,cmd file is in a non-standard location.
- cp ../template/screenrc screenrc
- edit screenrc and replace <ioc> with your ioc name.
- Setup a relative symbolic link to the TOP of the IOC Application release.
- ln -s ../../iocTop/<app>/<version> iocSpecificRelease
- Modify $EPICS_IOCS/screeniocs
- add line for cpu
format: cpu-<area>-<subsystem-prefix><2-digit #> <ts> <ts port #t> <screen host> [ # comment] - add line for each ioc
format: sioc-<area>-<subsystem prefix><2-digit #> cpu-<area>-<subsystem-prefix><2-digit #> <account> [ # comment] - The "comment" field in screeeniocsis optional and must be precede but "#".
IOC Applications Specific RT constraints:
- Create script <app>/iocBoot/<ioc>/rtPriortiesSetup.cmd to set real-time priorities for threads
- Load rtPriortiesSetup.cmd from <app>/iocBoot/<ioc>/st.cmd
-
LinuxRT Upgrade IOC Application release:
How-to start your linuxRT EPICS Application:
- Start ioc from the Linux:
- Start ioc from Linux manually in foreground:
- ssh laci@<cpu> -or- iocConsole <cpu> (from facet server use flaci)
- check if ioc is running : screen -ls
- If it's not running then manually start ioc.
- cd <app>/iocBoot/<ioc>
- ./st.cmd
How-to boot a linuxRT ioc from the <cpu>:
The following scripts are located under the directory $IOC/common and should be in PATH
- In the foreground w/screens
- linuxRT_viocConsole.sh <ioc>
- In the background w/screens
- linuxRT_startup_vioc.sh <ioc>
- In the foreground without screens
- linuxRT_startupConsole.sh <ioc>
How-to use screen program:
Additional References: