I'm trying to bring up an exiting EPICS application
on a PowerPC (Kinetic Systems V151 VXI)
running EPICS R3.13.2 and vxWorks 5.3.1
The existing software has been successully running
on an niCpu030 under EPICS R3.13.1 and vxWorks 5.3.1
for quite awhile.
I've run into a number issues with this PowerPC (VXI module):
1) missing lib vix functions such as SetMODID
2) missing or renamed unsolicited interrupt handlers
excStub and excIntStub.
(from devlib.c defaultHandlerNames[])
3) Is anything else tobe used in place of intHandlerCreate()
for powerPC...or is this handled in some other way?
4) sysBusTas() seems to be different for the PowerPC but
I can't find out what the difference is in the WindRiver
manuals. Does anyone know how this function differs for the
PPC? When calling sysBusTas() from the allenBradley driver
the following occurs:
SC_LOCK: calling sysBusTas 0xfcc0011d
alignment
Exception current instruction address: 0x0016f1a8
Machine Status Register: 0x0000b130
Data Access Register: 0xfcc0011d
Condition Register: 0x44000080
Data storage interrupt Register: 0x000000a0
Task: 0x1c2f2f8 "abScan00"
filename="../taskwd.c" line number=175
task 1c2f2f8 abScan00 suspended
initPeriodic: menuScan not present
value = 0 = 0x0
If anyone else has run into these problems with the PowerPC
I'd appreciate the any insite you gained.
- Thanks,
Kristi Luchini
- Replies:
- Re: VXI Kinetic Systems V151 cpu - PowerPC Andrew Johnson
- Navigate by Date:
- Prev:
Re: mv162 hangs on reboot Garrett D. Rinehart
- Next:
Re: VXI Kinetic Systems V151 cpu - PowerPC Andrew Johnson
- 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
- Navigate by Thread:
- Prev:
IOC Crash with CA Messages saa
- Next:
Re: VXI Kinetic Systems V151 cpu - PowerPC Andrew Johnson
- 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
|