Page History

...

1. Log into lcls-dev3  (ssh <user_name>@lcls-dev3)
   
   

2. Create an Epics Application ($EPICS_IOC_TOP)

1. Need to cross-compile the Epics Application for the desired target architecture

2. Check st.cmd file for all vioc’s - verify that it calls rtPriortiesSetup.cmd, which sets the real-time priority for threads
3. Each vioc directory needs a rtPriortiesSetup.cmd
   
3. Create and Set-up a  Directory Structure for cpu’s/vioc’s  under $IOC_DATA
   1. Generate Create cpu-##-## directory (In this directory, screenlog.0 is generated automatically)
   2. Generate Create a vioc-##-## directory for each vioc running on this machine
      1. Under each vioc directory, create an autosave, autosave-req, and iocInfo directory
      2. screenlog.0 is generated automatically
         
         
4.   Create and Set-up Directory Structure for cpu’s/vioc’s under $IOC
   1. Generate cpu-##-## directory
      1. Generate Make a symbolic link named “startup.cmd” that points to “../skel/startup_cpu.cmd”
      2. Generate Create a “kernel-modules.cmd” file that is specific for your cpu Create
      3. Make a symbolic link for each vioc(s) hosted on the cpu (ln -s ../vioc-xx##-xx## vioc-xx##-xx##)
         
         
   2.  Generate  Create a vioc-##-## directory for each vioc running on this machine
      1.  Generate  Create a “screenrc” file that is name-specific for each vioc
      2.  Generate  Make a symbolic link named “startup.cmd” that points to “../skel/startup_vioc.cmd”
      3.  Generate  Make a symbolic link called “iocSpecificRelease” that follows the CRAM convention for pointing to an Epics application
         How to CRAM your Epics Application:
         
         

5. Update $IOC/All/Dev screeniocs

   1. Update information pertaining to which vioc’s are running on a cpu and currently the application each vioc is running

   2. Commit screeniocs back into CVS

...