>Are there any special configuration changes to EPICS or the vxWorks kernel
>when using the hknitro60? We're getting access violations that appear
>to be related to interrupts when we start monitoring. This might be
>a 68060-related issue. I know that vxworks doesn't use separate interrupt
>stacks when a 68060 is used.
>
>I just want to make sure that I'm not tracking something that has already
>been addressed before.
What is 'monitoring'??
What addresses are you getting errors on?
Should these be otherwise valid addresses?
The stack stuff should be OK, I'd do a "checkStack" and "memShow 1" to
see if vxWorks is sane before and after these obscure IRQs.
I have run a software-only EPICS database on the nitro-60 using NO
other VME hardware in the crate and it appeared to run OK. The only
reason for alterations to the vxWorks kernel would be determined
entirely by the other hardware you wish to use in the crate.
I am not entirely sure, but I believe that the A16 area to be safe
as-shipped. Your A24 and A32 regions probably require some hackery in
the sysLib.c file.
--John Winans
- References:
- Hknitro60 + epics Greg Greene
- Navigate by Date:
- Prev:
Re: COMMUNICATION between EPICS and the Allen Bradley SLC 500 Marty Kraimer
- Next:
Re: SNL exit question Jeff Hill
- 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:
Hknitro60 + epics Greg Greene
- Next:
RE: COMMUNICATION between EPICS and the Allen Bradley SLC 500 415
- 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
|