The 0xfbff address is specific to the mv2700, I think. I'm not sure
what the offset for the mv5100 is..
- Sue
[email protected] wrote:
On Wednesday 20 January 2010 11:50:24 [email protected] wrote:
I've tried a different VIPC616 and Octal-232 to no avail.
What about the VME CPU, or the VME chassis (some VME backplanes have
jumpers
in them too, although their settings aren't likely to cause your
symptoms).
Do you have access to another working system with the same hardware in
that
you could try booting with this exact same st.cmd file?
- Andrew
--
The best FOSS code is written to be read by other humans -- Harald Welte
I just tried it on a VME5100 (instead of VME2700) in a test crate and it
was picked up fine using the same Ipac. So now it's at least isolated to
this IOC hardware and additional software. What's still weird is that
doing m(0xfbff0000,2) on the problem IOC shows all memory set to ffff.
vxwrks@iocfel7 -> m(0xfbff0000,2)
fbff0000: ffff-
fbff0002: ffff-
fbff0004: ffff-
fbff0006: ffff-
fbff0008: ffff-
fbff000a: ffff-
...
...
Wesley
- Replies:
- Re: Ipac with VIPC616 Wesley Moore
- References:
- Ipac with VIPC616 wmoore
- Re: Ipac with VIPC616 Andrew Johnson
- Re: Ipac with VIPC616 wmoore
- Re: Ipac with VIPC616 Andrew Johnson
- Re: Ipac with VIPC616 wmoore
- Navigate by Date:
- Prev:
Re: Ipac with VIPC616 wmoore
- Next:
Re: Ipac with VIPC616 Wesley Moore
- 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: Ipac with VIPC616 wmoore
- Next:
Re: Ipac with VIPC616 Wesley Moore
- 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
|