I suspect that the VXI backplane will not probe until the nivxi
library's initialization has been run.
I agree that, on certain processors and motherboards, that it's a good
idea to avoid the low logical address ranges depending on how VXI
interrupts are dispatched.
Jeff
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Monday, January 07, 2002 3:57 PM
> To: Jeff Hill
> Cc: 'John Faucett'; EPICS-tech-talk
> Subject: Re: VXI driver support
>
> Could there be a problem with using logical address 1? ISTR that LA's
map
> directly to interrupt vector numbers, and most processors tend to
reserve
> the lower numbered interrupt vectors for other things (I don't know
what
> CPU is used in an hkbaja60 though). Try switching to a logical
address
> above 0x40
>
> I'm not sure whether that would explain these symptoms or not though,
it
> might just mean that you couldn't connect an interrupt routine to that
> card, or it may be that it's only the MXI modules that have that
> restriction.
>
> - Andrew
> --
> Perfection is reached, not when there is no longer anything to add,
> but when there is no longer anything to take away.
> - Antoine de Saint-Exupery
- References:
- Re: VXI driver support Andrew Johnson
- Navigate by Date:
- Prev:
Re: VXI driver support Andrew Johnson
- Next:
Re: iocsh for Epics314b1 on win32 kuner
- 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:
Re: VXI driver support Andrew Johnson
- Next:
Re: VXI driver support John Faucett
- 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
|