EPICS on RTEMS

[John Sinclair <sinclairjw@ornl.gov>]

I am beginning to do some VME access from an EPICS application on RTEMS. 
As a first check, I
added a bit of vme access code to a device support function only to see 
if the application would
build. The code merely calls devRegisterAddress using atVMEA16 as the 
address type.

The build fails with the following errors:

/home/sinclair/rtemsEpics/supTop/R3.14.9/base/lib/RTEMS-mvme2100//libCom.a(devLibOSD.o): 
In function `rtmsDevInit':
../../../src/libCom/osi/os/RTEMS/devLibOSD.c:105: undefined reference to 
`bspExtInit'
/home/sinclair/rtemsEpics/supTop/R3.14.9/base/lib/RTEMS-mvme2100//libCom.a(devLibOSD.o): 
In function `rtmsDevWriteProbe':
../../../src/libCom/osi/os/RTEMS/devLibOSD.c:253: undefined reference to 
`bspExtMemProbe'
/home/sinclair/rtemsEpics/supTop/R3.14.9/base/lib/RTEMS-mvme2100//libCom.a(devLibOSD.o): 
In function `rtmsDevReadProbe':
../../../src/libCom/osi/os/RTEMS/devLibOSD.c:234: undefined reference to 
`bspExtMemProbe'

---------------------------

I have built an application using the generic RTEMS build scheme (no 
EPICS) that accesses the VMEbus without problems.

Any ideas as to what configuration pieces are missing?

- John Sinclair

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature