ahed aladwan wrote:
>
> When the master (PPC MVME2304, vxWork 5.3.1) reads the data from the
> slave (A16, D16, address mod is 0x2D or 0x29), it seems that for some
> addresses the master get the data for the next address (+ 1 byte), using
> a logic analyzer to check the master read cycle (attached pdf file), I
> have noticed that because the master apply address pipelining
> (forcasting) and the slave dosen't latch the data (or address), I got
> wrong data.
> But what I can't understand why this happens only for some addresses but
> not all, espicialy the base address (status register) (ISEQ has no clue)
Are you sure it's always the next address, or just on addresses that have
a particular address line low (or high)? This sounds like one of the
address lines is floating high, which would explain why some registers
read OK (where that address line is driven high anyway) and some don't
(where the line needs to be low).
This is an indication that the module doesn't meet the VME spec, which
does allow for address pipelining. PowerPC CPU modules using the Universe
chip generate rather different signal timings to the older 68K-based
interfaces, and some boards aren't properly designed to the spec, just to
what the manufacturer thinks the signals do.
- Andrew
--
Larry McVoy: "Learn how to think in C++ but don't ever program in it."
- References:
- Re: ISEG VHQ204L Driver ahed aladwan
- Navigate by Date:
- Prev:
Tornado-2 arp-table Bernd Schoeneburg
- Next:
RE: ISEG VHQ204L Driver 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:
Re: ISEG VHQ204L Driver ahed aladwan
- Next:
RE: ISEG VHQ204L Driver 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
|