...
| Panel |
|---|
5. What do I do if I need a new module or a specific version for an existing module built for the new base?Contact Murali or Ernest to have them built and installed.Murali has a python script that The python script makeModules.py in /afs/slac/g/lcls/tools/script automatically discovers the module dependencies and builds them an entire module tree in the correct order for all targets. As of date this script is 'reasonably' functional. TO DO list: Make this script user-friendly but as of date Contact Murali or Ernest to have the modules built and installed in the meanwhile. |
| Panel |
|---|
6. Where and how do I create a new EPICS application? How do I setup a new IOC to use linuxRT-86 OS?(a) Create directories and files as shown below using ioc-b34-bd32 as an example: $IOC/ioc-b34-bd32 $IOC_DATA/ioc-b34-bd32 $IOC_DATA/ioc-b34-bd32/screenlog.0 $IOC_DATA/vioc-b34-bd32 $IOC_DATA/vioc-b34-bd32/autosave $IOC_DATA/vioc-b34-bd32/autosave-req $IOC_DATA/vioc-b34-bd32/iocInfo Note to Ernest: Please create above directories automatically via TO DO list: Generate a script to create above directories automatically via a single python or perl script. $APP/Test (look at this as an example) Now create your EPICS application called 'MyTest' as below using standard templates and scripts in a sandbox area called Development. As MyTest development continues, this is where you will be creating/checking out from CVS, several versions of your MyTest application. Now create a sandbox area for MyTest. mkdir Development (c) cd Development You are currently in: /afs/slac/g/lcls/epics/R3-14-12-3_1-0/iocTop/Test/Development This is the top directory for MyTest and referred as $(TOP). (d) Using a perl script that automates the process, create MyTest: The perl script had populated your application using icdTemplates module that provides templates that are used by ICD to support our style of IOC Application Building for the facilities we support. The location for icdTemplates module was set as below when you sourced go_epics_3-14-12-3_1-0.bash. EPICS_MBA_TEMPLATE_TOP=/afs/slac/g/lcls/epics/R3-14-12-3_1-0/modules/icdTemplates/icdTemplates-R1-0-1 If you would like to know more about makeBaseApp.pl, type: makeBaseApp.pl -help (e) Now, open the configure/RELEASE file. (i) Notice how the following line appears towards the beginning: The above sets the paths for EPICS base, modules, packages, tools etc. to point to version R3-14-12-3_1-0. (ii) The file has the following line towards the end of it: # Location of Linux Kernel Modules: LINUX_KERNEL_MODULES=$(PACKAGE_SITE_TOP)/linuxKernel_Modules (iii) configure/RELEASE file may need some modifications from what was automatically generated: They must also have been built for the linuxRT-x86 target. If something is missing, contact Ernest. For EVENT module, Kukhee recommends us to use event-R4-1-3 or greater with this base. (f) Open MyTestApp/src/Makefile and notice that the IOC application is referred to as 'MyTest". (g) Now it is time to add your linuxRT-x86 virtual ioc (vioc) startup scripts. vioc-b34-bd32 is used here as an example. makeBaseApp.pl -i -t slac vioc-b34-bd32 Two files are modified based on this selection. (1) vioc-b34-my01/st.cmd (2) vioc-b34-my01/Makefile. When prompted with 'Application name?' type 'MyTest'. This will use the application name MyTest that was created in MyTestApp/src/Makefile as described in step (f). If you just hit 'Enter' without specifying your application name, then your ioc name vioc-b34-bd32 will be used as the default for the dbd file in the st.cmd Open iocBoot/vioc-b34-bd32/Makefile and notice that ARCH is set to linuxRT-x86. (h) If you have an EVR in your system, uncomment the following lines in MyTestApp/src/Makefile:
# MyTest_DBD += evrSupport.dbd Ensure the following lines are not commented as well: MyTest_LIBS += evrSupport .... ifeq ($(T_A),linuxRT-x86) For a PMC EVR230 or PCI-e EVR300 that is installed in your system, the above is all you need. Replace the macros in the EPICS database files, or add more databases and modify MyTestApp/Db/Makefile as needed. (i) Now 'make' your application from the top level directory $(TOP) to ensure your changes to RELEASE files are good: There should be no build errors. Having tested this phase, you can now uninstall the binaries and cleanup the make-generated files using the following command: Do the above before committing the files to CVS. Currently Ernest is working on changes to the icdTemplates module that provides default templates. Until he is done with that work, we have to manually make several changes to the MyTestApp/Db/* files and iocBoot/vioc-b34-bd32/st.cmd. For now, follow the example MyTest and create similar database files and st.cmd. The EVR-related screens have been added for vioc-b34-bd32. You can see them when the vioc-b34-bd32 is running as follows from lcls-dev2: lclshome -> User Dev Displays.... -> Test IOCs/Dev Event IOCs.... The buttons for the various panels for VIOC:B34:BD32 are towards the bottom of this screen. For easy access to your IOC's EVR panels in LCLSDEV, add the necessary buttons to this page. The 'Pattern' button brings up the 'Pattern Diagnostics' screen. 'PMC EVR:B34:BD32' button brings up the Low Level 'Diagnostics' screen for EVR;B34:BD32 'Triggers' button brings up 'Trigger Configuration' setup screen. (c) Add your application to CVS and commit the source files. Ernest has created some slides that explains some guidelines for importing new applications into CVS: |
...
