5 Jan
2002
5 Jan
'02
8:41 a.m.
Pete Turnbull wrote:
snip snip
> Do you have the manual for the M9312?
There are several ROMs that might be
Yes, the 9312 has the 233 type rom (11/70 diagnostic, so this is ok).
> on it, with different device bootstraps, and I think there are at least two
> diagnostics PROM options: one for 11/70 and one for other Unibus machines.
> > On the M8132 is a switchblock (1 of
3) which is - according to the doc-
> > the
> > lsw, I have set it to 1M,
> I suspect that should be set to the actual
memory size.
Has the location of the available ram in my case anything to do with the
high address
limit register? According to the usermanual it is the high imit of the
memory, not
it starting address?
On the other hand, the starting address of 400000 can maybe also the
result of some
initial values in the unibus map registers?
> Anyone else know anything about
11/70's?
> --
> Pete Peter Turnbull
> Network Manager
> University of York
Ed
--
The Wanderer | Politici zijn gore oplichters.
quapla(a)xs4all.nl | Europarlementariers: zakkenvullers
http://www.xs4all.nl/~quapla | en neuspeuteraars.
Unix Lives! M$ Windows is rommel! | Kilometerheffing : De overheid
'97 TL1000S | weet waar je bent geweest!
Good question. I'm not sure, I think it's
tested by the diagnostics on the
bootstrap card. I think it's possible to disable it but I don't know how.
It may be in one of the processor handbooks, which I can look up tomorrow.
That's where I checked the value for the LSR and USR.
I swapped the Unibus map and the cache control board, and the machine
behaves
apparently much better. After pressing the bootstrap key (someone made a
small
switch between tabs 1 & 2 of the M9312) and it goes into a sort of loop
after
a second or so. When pressing halt, the address display ends in 344,
while the
data display shows 116.
Also memory location 400000 through 477777 are accessible via the
console and
I can dump data and read from it.
That sounds encouraging. At least it seems to be
running the diagnostic
code. I think, though, that the address it halts at is what tells you what
(if anything) failed the test. If you can tell where it halted, it may be
able to look that up.
At 344 (addr) and 116 in the data display. No idea if this a
valid value
though...