Experimental Physics and
Industrial Control System

Ron Sluiter <[email protected]> · Mon, 29 Aug 2016 15:32:13 -0500

Since this problem recently arose again and I failed to document it when

it was originally resolved, I am responding to my own message from two

years ago.

The error messages below are caused by a mismatch between the running

version of VxWorks and the tool chain used to build EPICSbase. For

example, build EPICSbase using a VxWorks 6.9.3 toolchain and then load

it into a VME crate running VxWorks 6.9.4.1 and you will get the error

messages below. The reverse also fails; build EPICSbase under 6.9.4.1

and try running it under VxWorks 6.9.3; same errors messages.

The root cause of this problem is that Intel Wind River Systems made

changes to some data structures (the specifics of which I no longer

recall) that EPICS uses between VxWorks 6.9.3 and 6.9.4.1. Binary

compatibility is apparently not guaranteed between "maintenance"

versions of VxWorks.

Ron

On 8/25/2014 2:41 PM, Ron Sluiter wrote:

We recently tested VxWorks 6.9.4.1 for the 1st time on a teststand and

found some new EPICS error messages that we have not seen before.

osiSockDiscoverBroadcastAddresses(): status: 0x08x, ifconf.ifc_len: -1

osiSockDiscoverBroadcastAddresses(): unable to fetch network

interface configuration

and,

osiLocalAddr(): SIOCGIFCONF ioctl failed because "S_errno_ENXIO"

These error messages appeared only once after iocInit and had no

discernible effect on IOC performance. We are using base-3.14.12.3.

Is anyone else using VxWorks 6.9.4.1?

Are other VxWorks 6.9.4.1 users seeing these error messages?

Ron

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System