For a more comprehensive overview and detailed questions, please refer to the following page:
FAQ for working with 64-bit linuxRT OS and EPICS R3-14-12-4_1-0
...
...
Create an Epics Application ($EPICS_IOC_TOP)
Need to cross-compile for target architecture
...
Update $IOC/All/Dev screeniocs
...
Update information pertaining to which vioc’s are running on a cpu and currently the application each vioc is running
...
How to CRAM your Epics Application:
How to commit screeniocs back into CVS:
cvs status <file_name>
cvs commit <file_name>
From the command line, start a linuxRT Epics Application manually (must run on a linuxRT machine)
ssh laci@ioc-b34-cd46 or ssh laci@cpu-b34-fb01
- cd to to the epics application directory structure and run the st.cmd for a linuxRT application
- ./st.cmd (first line of st.cmd must have !# for this to execute epics application binary ex: !# ../../bin/linuxRT_glibc-x86_64/fastFeedback)
How to boot-up in the foreground versus background:
The following scripts are located under the directory $IOC/common
> (1) In the foreground w/screens
linuxRT_viocConsole.sh vioc-b34-fb01
> (2) In the background w/screens
linuxRT_startup_vioc.sh vioc-b34-fb01
> (3) In the foreground without screens
linuxRT_startupConsole.sh vioc-b34-fb01
If using the screen program:
ctrl a d : detach from the screen session
ctrl a { : scroll up through the start-up messages.
Common Linux Commands Used
mkdir <directory_for_cpu/vioc>
ln -s <path_to_desired_file> <symbolic_link_name>
rm <symbolic_link_name> (WARNING: Make sure you are not removing the entire directory. rm <symbolic_link_name/> will remove the directory that the symbolic link points too)
grep -r <search_term> . (recursively search through directories starting in your currently working directory)
man <linux_command> (linux documentation)
LinuxRT startup scripts
[cpu]/startup.cmd
A link to skel/startup_cpu.cmd or a real file.
Calls $IOC/common/linuxRT_startup_cpu.sh to set up environment & hardware.
If using a real file, optionally create a list of screenrc VIOCs to start up
If using a real file, optionally create a list of the executables to start them with
Calls $IOC/common/linuxRT_cpu_load_viocs to start the listed VIOCs or extract the list from screeniocs
[cpu]/kernel-modules.cmd
Called by $IOC/common/linuxRT_startup_cpu.sh to load kernel modules.
Custom for each CPU. May contain other related commands.
$IOC/common/linuxRT_startup_cpu.sh
Load environment
mount nfs dir
load kernel modules with [cpu]/kernel-modules.cmd
start CA repeater
$IOC/common/linuxRT_cpu_load_viocs.sh
If a list of IOCs to start up is defined as an environment variable, use it. Otherwise use screeniocs.
if there is a list of executables in an environment variable to go with the list of IOCs, use it.
For each ioc, call linuxRT_startup_vioc.sh iocDirName epicsApp
$IOC/common/linuxRT_startup_ioc.sh iocName [epicsApp]
Set ulimits
set umask
cd to the vioc directory
If the exececutable name was passed as the second argument, use that.
Otherwise, check screeniocs to determine the epicsApp.
Otherwise look for a #! at the top of ioc/startup.cmd to determine the epicsApp.
Otherwise look for a #! at the top of ioc/iocSpecificRelease/iocBoot/[iocName]/st.cmd to determine the epicsApp.
run startup.cmd using screen and epicsApp
References:
How the initial boot-up process works:
https://confluence.slac.stanford.edu/pages/viewpage.action?pageId=181538610
How to CRAM your Epics Application:
Additional Information on Cross-compiling Epics Applications:
...
References (documents need to be updated)
How-To setup the CPU and IOC boot directories
The instructions differ between production and development due to permission restrictions in production.
Production: lcls, facet, spear, acctest
Example Development DHCP snipped
host cpu-b024-pm01 {
hardware ethernet 74:FE:48:16:3D:D5;
fixed-address 134.79.217.162;
option host-name "cpu-b024-pm01"
if ( substring( option vendor-class-identifier, 0, 5 ) = "udhcp" ) {
filename "/afs/slac.stanford.edu/g/lcls/epics/iocCommon/cpu-b024-pm01/startup.cmd";
option root-path "afsnfs:/afs/slac.stanford.edu:/afs/slac.stanford.edu";
}
}
Development:
Example LCLS DHCP snippet:
host cpu-li10-pm01 { hardware ethernet 74:FE:48:55:1D:A9; fixed-address 172.27.72.103; option host-name "cpu-li10-pm01"; if ( substring( option vendor-class-identifier, 0, 5 ) = "udhcp" ) { filename "/usr/local/facet/epics/iocCommon/cpu-li10-pm01/startup.cmd"; option root-path "mccfs2:/export/mccfs/usr/local:/usr/local"; } }
4.Create the <cpu>.ipxe file at:
for LinuxRT: $TFTPBOOT/linuxRT/boot/ipxe/<cpu>.ipxe
for Centos7: $TFTPBOOT/boot/ipxe/<cpu>.ipxe
for 64-bit cpu: cp example.ipxe <cpu>.ipxe
for 32-bit cpu: cp example-32bit.ipxe <cpu>.ipxe
Note: the buildroot version in the IPXE file must match the IOC Application buildroot version defined in configure/CONFIG_SITE
5. Setup CPU Boot directory files:
Original Method: (steps 3b and 3c)
6.. Setup ioc directory files
6. Modify $EPICS_IOCS/screeniocs – Please note that this is a symbolic link to a CVS:
IOC Applications Specific RT constraints:
How-to Release a LinuxRT IOC Application:
How-to boot a linuxRT IOC from a Linux Host :
How-to boot an IOC from the linuxRT host
The following scripts are located under the directory $IOC/common and should be in PATH on the CPU.
How to connect to CPU from a Linux host:
Use either iocConsole or ssh to CPU as follows:
How to check if IOC is running on the linuxRT CPU:
Note: The "screen" program supports multi-display mode. When you attach an existing screen session, you can use "-x". It allows an user to attach to "a not detached screen session." The -r option allows a user to attach to a "detached screen session".
Additional References:
