4 Jan
2002
4 Jan
'02
11:59 a.m.
On Jan 4, 15:40, The Wanderer wrote:
Oh dear, I've only seen one once.
working?
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.
Do you have the manual for the M9312? There are several ROMs that might be
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.
I could be wrong about that, of course; I might be confusing it with the
multiplicity of variants of the M9301. I just happen to have an M9301-YC
Pete Turnbull wrote:
> On Jan 2, 21:08, <quapla(a)xs4all.nl> wrote:
> >
> I'm sure there must be people on the list who know more about 11/70s
than
I
do, but since
no-one else has replied yet...
Until know, you're the only one..... Is the memory
powered up and connected? At the right address (you must
Yes, it is running, and
all the leds are on, except one red led (battery
power
available?).
There is 128KW of memory (in 2 64Kw boards)
> have some memory in the lowest 28KW to start up)? Is the cache How do I know if the cache is working?
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.
There are
various things done by the power-up bootstrap diagnostic
True, I have re-read the
M9312, and at address 777644 is the diagnostics
rom start
address. When I load this address and then set 012 in the switch reg,
for some
moments it is blinking leds, and then lets the pause light on. There is
no sensible
address/error code shown at the console which should indicate a diag
failure. from an 11/70.
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.
Anyone else know anything about 11/70's?
--
Pete Peter Turnbull
Network Manager
University of York
5 Jan
5 Jan
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...
8388
days inactive
8389
days old
1 comments
2 participants
participants (2)
-
pete＠dunnington.u-net.com -
quapla＠xs4all.nl