I don't have a 162 manual so I don't know why you would need to change the
access mode from sup-data to usr-data. Also, does the 162 support D32
acceses on the back-plane (maybe it is only D16, I've seen some boards
that only do D16). Sorry I can't help more. Perry
On Mon, 6 Mar 2000, Burkhard W. Kolb wrote:
> Hi,
>
> thanks for the quick reply. I tried it out on Friday, but it made no change.
> I have to read the 162 manual more carefully. Don't I have to change in the
> drvSiam.c the line
> status = sysBusToLocalAdrs(VME_AM_STD_SUP_DATA,(char *)base_addr,...
> also then to ...VME_AM_STD_USR_DATA...?
>
> To the Epics/VxWorks community:
> Did anybody do this modification to the sysLib.c on the 162 for the SIAM
> or anything similar?
> Burkhard
>
- References:
- Re: Problem with MVME162 and A24/D32 or D16 access to SIAM Burkhard W. Kolb
- Navigate by Date:
- Prev:
Re: mv162 hangs on reboot Peregrine M. McGehee
- Next:
Re: Problem with MVME162 and A24/D32 or D16 access to SIAM Burkhard W. Kolb
- 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: Problem with MVME162 and A24/D32 or D16 access to SIAM Burkhard W. Kolb
- Next:
Re: Problem with MVME162 and A24/D32 or D16 access to SIAM Burkhard W. Kolb
- 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
|