Subject: |
Problem with MVME162 and A24/D32 or D16 access to SIAM |
From: |
"Burkhard W. Kolb" <[email protected]> |
To: |
tech-talk Mailing List <[email protected]> |
Date: |
Fri, 03 Mar 2000 16:33:10 +0100 |
Hi,
I have a problem setting up a 162 cpu to work with the SIAM (Bira 7550) module.
This module allows A24 access only. It has an Status register (32 bits)
at its
base address and then various 16bit registers at +4... addresses. As far
as I
understand the BSP for the 162 (in syslib.c) the VME access in A24 mode is
word (16 bit) only. When the code accesses the statusregister with a long
pointer the VMEchip2 is supposed to break this into 2 cycles of 16 bit and
then fit the longword together from the two pieces, right?
When I print out the status register contents I get 0xcd55ffff. On a VMEbus
display I see the 0xffff and the last address being 0x00300002. But the word
0xcd55 is the (fixed) contents of the ID register of the module, at address
0x00300004.
Something wrong in the way the registers are setup for the VMEchip2?
Burkhard Kolb
GSI Darmstadt
HADES detector
- Replies:
- Re: Problem with MVME162 and A24/D32 or D16 access to SIAM Perry L. Anthony
- Re: Problem with MVME162 and A24/D32 or D16 access to SIAM Burkhard W. Kolb
- Navigate by Date:
- Prev:
CapFast Special Dr. Chong Lee
- Next:
Re: Problem with MVME162 and A24/D32 or D16 access to SIAM Perry L. Anthony
- 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:
CapFast Special Dr. Chong Lee
- Next:
Re: Problem with MVME162 and A24/D32 or D16 access to SIAM Perry L. Anthony
- 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
|