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
