1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: EPICS on RTEMS |
From: | Eric Norum <[email protected]> |
To: | John Sinclair <[email protected]> |
Cc: | EPICS Tech-Talk <[email protected]> |
Date: | Wed, 2 May 2007 13:47:34 -0500 |
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
-- Eric Norum <[email protected]> Advanced Photon Source Argonne National Laboratory (630) 252-4793