...
Log into lcls-dev3 (ssh <user_name>@lcls-dev3)
Create an Epics Application ($EPICS_IOC_TOP)
Need to cross-compile the Epics Application for the desired target architecture
- Check st.cmd file for all vioc’s - verify that it calls rtPriortiesSetup.cmd, which sets the real-time priority for threads
- Each vioc directory needs a rtPriortiesSetup.cmd
- Create and Set-up a Directory Structure for cpu’s/vioc’s under $IOC_DATA
- Generate Create cpu-##-## directory (In this directory, screenlog.0 is generated automatically)
- Generate Create a vioc-##-## directory for each vioc running on this machine
- Under each vioc directory, create an autosave, autosave-req, and iocInfo directory
- screenlog.0 is generated automatically
- Create and Set-up Directory Structure for cpu’s/vioc’s under $IOC
- Generate cpu-##-## directory
- Generate Make a symbolic link named “startup.cmd” that points to “../skel/startup_cpu.cmd”
- Generate Create a “kernel-modules.cmd” file that is specific for your cpu Create
- Make a symbolic link for each vioc(s) hosted on the cpu (ln -s ../vioc-xx##-xx## vioc-xx##-xx##)
- Generate Create a vioc-##-## directory for each vioc running on this machine
- Generate Create a “screenrc” file that is name-specific for each vioc
- Generate Make a symbolic link named “startup.cmd” that points to “../skel/startup_vioc.cmd”
- Generate Make a symbolic link called “iocSpecificRelease” that follows the CRAM convention for pointing to an Epics application
How to CRAM your Epics Application:
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
- Commit screeniocs back into CVS
...