EPICS: vxWorks IOC: Difference between revisions
Jump to navigation
Jump to search
Line 37: | Line 37: | ||
gmake | gmake | ||
It creates useful ''cdCommands'' file. File ''st.cmd' in the same directory contains an example of startup | It creates useful ''cdCommands'' file. File ''st.cmd' in the same directory contains an example of startup script. Uncommect followibg line | ||
cd "/usr/local/clas/devel/R3.14.8.2/base-3.14.8.2/iocBoot/iocsy527" | |||
and boot. Everything looks good. |
Revision as of 20:19, 2 October 2007
VxWorks IOCs are normally running in VME crate controllers.
first experience
cd $EPICS_BASE ./bin/solaris-sparc/makeBaseApp.pl -b $EPICS_BASE -t ioc iocsy527 ./bin/solaris-sparc/makeBaseApp.pl -b $EPICS_BASE -i -t ioc iocsy527 The following target architectures are available in base: solaris-sparc vxWorks-ppc604_long solaris-x86 linux-x86 What architecture do you want to use? vxWorks-ppc604_long The following applications are available: caclient caserver ioc ioccamac iocCore1 iocCore iochv iocsy527 ioctest support What application should the IOC(s) boot? The default uses the IOC's name, even if not listed above. Application name? iocsy527
It creates directories iocsy527App and iocBoot/iocsy527.
cd iocsy527App gmake
It compiles both unix and vxWorks versions.
cd ../iocBoot/iocsy527 gmake
It creates useful cdCommands file. File st.cmd' in the same directory contains an example of startup script. Uncommect followibg line
cd "/usr/local/clas/devel/R3.14.8.2/base-3.14.8.2/iocBoot/iocsy527"
and boot. Everything looks good.