1 / 5

EPICS 3.14 VME/VXI Support Solution: Unbundling Hardware Support, VxWorks Dynamic Loading, and Registry Build Environmen

This update to EPICS 3.14 introduces solutions for unbundle all hardware support, VxWorks dynamic loading, and registry build environment changes. It also includes a simpler configuration process and support for the VxWorks shell and interrupt level. Converting R3.13 IOC applications to 3.14 is supported with minimal changes.

willae
Download Presentation

EPICS 3.14 VME/VXI Support Solution: Unbundling Hardware Support, VxWorks Dynamic Loading, and Registry Build Environmen

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EPICS base 3.14OSI: Operating System Independent Support Marty Kraimer

  2. Major Problems 3.13=>3.14 VME/VXI: Solution: unbundle all hardware support VxWorks Libraries: Solution: base supplied OSI libraries VxWorks dynamic loading: solution: Registry Build Environment Major changes Actually simpler than 3.13 Configure instead of config VxWorks shell: Solution: iocsh Interrupt Level support Use global mutex if OS doesn't support

  3. Operating System Independent Interfaces epicsRing rngLib Generic epicsTimer WdLib,epicsTimer Generic epicsAssert epicsAssert Default, vxWorks epicsEvent semLib RTEMS,WIN32,POSIX,vxWorks epicsFindSymbol SymFindByName Default,vxWorks epicsInterrupt intLib RTEMS,default,vxWorks epicsMutex semLib RTEMS,WIN32,POSIX,vxWorks epicsThread taskLib RTEMS,WIN32,POSIX,vxWorks epicsTime tickLib,osiTime RTEMS,WIN32,POSIX,vxWorks OsiPoolStatus memLib RTEMS,WIN32,default,vxWorks osiProcess osiProcess RTEMS,WIN32,POSIX,vxWorks osiSigPipeIgnore osiSigPipeIgnore WIN32,default,POSIX,vxWorks osiSock osiSock Many

  4. Some Details Registry vxWorks symFindByName – bind to global symbol. iocCore dynamically binds record/device/driver/etc support. While building application: A perl program generates a C function C function is linked with application. During startup the C function is called. It registers the support. Build Environment Extensive changes, more functionality, easier to use. iocsh – simple command interpreter, built in commands. Interrupt Level Support iocCore has minimal use. vxWorks,RTEMS real support. Default uses global mutex.

  5. Compatibility Converting R3.13 IOC applications to 3.14. The old 3.13 build rules are still supported. Using old build rules requires few changes.However all hardware support is unbundled. Ultimately must convert to new rules. Old CA client interface still supported Many CA client applications have been built with 3.14.

More Related