The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cdl@mpl.ucsd.edu (Carl Lowenstein)
Subject: [TUHS] PDP11/34 boot problems, here i am again :)
Date: Tue, 15 Apr 2003 12:42:24 -0700 (PDT)	[thread overview]
Message-ID: <200304151942.h3FJgO900113@opihi.ucsd.edu> (raw)

> From: asbesto <asbesto at freaknet.org>
> To: tuhs at tuhs.org
> Subject: [TUHS] PDP11/34 boot problems, here i am again :)
> 
> well, i think now we have a more complete knowledge of the REAL
> problem !
> 
> the M7891 board (128K x 18 bit MOS MEMORY MODULE) have the D2 red=20
> led light turned ON when turning on the CPU !
> 
> this means PARITY ERROR on this board :(
> 
> checking the board we found 2 problems:
> 
> 1) a 74LS175 chip named E15 on our schematic diagram, that seem
>    phisically BROKEN on an edge (there is a fessure on the plastic
>    DIP package). i can't change it now because i don't have a=20
>    soldering station here to do a nice job, but looking the chip i
>    think it may work...

While you probably _do_ have a real hardware problem with the broken
IC, I think that the red Parity Error light on first turn-on is normal
behavior.  The MOS memory comes up with random values, and about half
of them will have the wrong parity.  Some software routine must turn
off parity error detection and write a known data pattern (all 0's) to
each memory location.  I don't remember whether this is something that
is done by the boot ROM of an 11/34.

    carl
-- 
    carl lowenstein         marine physical lab     u.c. san diego
                                                 clowenst at ucsd.edu




             reply	other threads:[~2003-04-15 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 19:42 Carl Lowenstein [this message]
2003-04-15 21:22 ` asbesto
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15  6:37 Gooijen H
2003-04-15  8:50 ` asbesto
2003-04-15  0:00 asbesto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304151942.h3FJgO900113@opihi.ucsd.edu \
    --to=cdl@mpl.ucsd.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).