VxWorks 6.0 and EPICS“a first look”.PPTVIP

VxWorks 6.0 and EPICS“a first look” Ernest L. Williams Jr. 27 April 2005 EPICS Collaboration Meeting @ SLAC Outline What is vxWorks 6.0? Maybe we will begin using the tools? Integration into the EPICS R3.14 build system. Running with EPICS, cool!! Issues/Concerns References What is vxWorks 6.0? An expensive new toy!! What is VxWorks 6.0? What is VxWorks 6.0 (Cont’d) What is VxWorks 6.0 (Cont’d) What is VxWorks 6.0 (Cont’d) What is VxWorks 6.0 (Cont’d) What is VxWorks 6.0 (Cont’d) What is VxWorks 6.0 (Cont’d) What is VxWorks 6.0 (Cont’d) New Tools “WindRiver Work Bench” Development environment revolves around ECLIPSE. A smart move by WindRiver We still like using the commandline but maybe we will begin to use some of the builtin tools that come bundled with “Workbench” Source Code Analyzer Debugger System Viewer Scope Tools Sergei and Tom use ECLIPSE; so it must be good! EPICS Integration BSP migration and flashing the IOC Simply re-compile the mv2100 BSP against vxWorks 6.0 If you want native support, then follow the BSP migration documenation. The mv5100 BSP has native support for vxWorks 6.0 The idea of the project facility is not too bad when done via command line. Use WRS workbench CLI to add components recommended by Andrew Johnson. /epics/base/T20xConfig.html vxprj component add INCLUDE_POSIX_TIMERS The GUI folks can use the workbench IDE to do this as well. EPICS Integration We begin by adding/modifying the EPICS build environment to support building vxWorks 6.0 targets. Supported cross targets at the SNS MVM2101 (vxWorks-mv2100_v6) MVME5110 (vxWorks-mv5100_v6) Changes to $(EPICS_BASE)/configure/CONFIG_SITE Add our two new cross targets Changes to $(EPICS_BASE)/configure/os Add CONFIG_SITE.linux-x86.vxWorks-mv2100_v6 Add CONFIG.Common.vxWorks-mv2100_v6 Add CONFIG_SITE.linux-x86.vxWorks-mv5100_v6 Add CONFIG.Common.vxWorks-mv5100_v6 Add CONFIG.Common.vxWorksCommon_v6 EPICS Integration EPICS Integration Running with EPICS R3.14.7 EPICS is running in ker