EasyManua.ls Logo

Sage II - RAM Memory Test

Sage II
115 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
SAGE rr SERVTCE
MANUAL
[1.0]
POWER-UP ROUTINE
INITIALIZATION
(cont)
PROM CHECKSUM
TEST:
Both
PR0Ms
have
sirnple
checksums. The ROM test
calculates the
checksum
of the
ROMs
to insure
that
the BOOTSTRAP
program
itself is
ok.
l,lessages
"PROM
I
bad"
or
"PROI"I
2
bad" w111
display tf
possible
otherwlse
the
cpu
will halt
and
the
CPU light
will
be RED. Because
this error
and
a CpU
error are
catastrophlc,
ro further
information
can be
given.
PROM
1
refers
to
the
EVEN
memory addresses
(package
U17)
while
PROM
2
refers
to
the
ODD
memory addresses
(package
Ul8).
VI
I.
O
2 RAI,I
HEHORY
TEST
:
A11
RAM
memory existing
in
the system is
tested
next.
NOTE:If
Switches
516
and
B
of
GROUP
A are
set
OFFTOFF,ON
respectively
then
this test will
be
bypassed and
a
message
"Bypassed
rnit"
will
display.
The
processor
enters
the
debugger.
This
option is
used to inspect
memory after a
program
crash.
The
test
of
the first
128K of RAM is
run in
the
following
manner:
Each
long
word
Each long
word
(t+
(4
bytes)
is
set to
00000000
and
read
back.
bytes)
is
set
to FFFI-FFFF
and read
back,
Then it
is
set to its
own address
and
program
goes
on to next
long word.
When all
128K
is
done,
each long
word
is
read to
see
if it
stil1
conEalns
lts
address.
Then
the top
word
of each
128K
bank
is read
to
see
if
that
bank
exists.
Once the si-ze
of the
addiEional
memory is
determined, it
is
checked
just
as
the flrst
128K
was.
This
test
w111
take
a few
seconds.
Then the
message
"RAIyl
SIZE
=
xxXXXX" will
be displayed.
If
a
bad
memory
location
was found
then an
error ls
displayed:
BAD
memory
G
(addr)
is
(A
digit
value) instead
of
(A
dtglt
value)
The
program
stops
at the first
bad location
it finds.
Because
it re-
reads
the
location
to
print
out the
error
message,
the
error
value
may
be the
expected
value
if the
RAM is intermlttent
and
reads
correctly
the
second
time.
The
processor
will
attempt
to enter
the
debugger
after
a
memory
error.
If the failed
memory
occurs
in
the
debugger
stack
area
(worklng
down
from
400H),
the
debugger
may
fail
to
operate
correctly
after
the
memory
error.
11