From: asbesto@freaknet.org (asbesto)
Subject: [TUHS] pray for us ! pdp11/34 salvation, continued.
Date: Tue, 4 Nov 2003 15:00:38 +0000 [thread overview]
Message-ID: <20031104150038.GB9037@freaknet.org> (raw)
In-Reply-To: <20031103094916.GE2101@freaknet.org>
Il Mon, Nov 03, 2003 at 09:49:16AM +0000, asbesto rigurgitava:
i quote myself, due to some imprecision (i have a really bad memory,
maybe i have some chip to change inside my mind :)))
> in these days we will try to change the broken chip on the pdp11/34
> RL01 controller board.
No. the "broken" board is the M7891, 128Kx18 bit MOS memory. The
broken chip is E15, a simple SN74LS175.
here's the list of the messages in which i first described our
problem; the messages start at Tue, 15 Oct 2002 07:46:35 +0000,
and they can be find on the mailing list archive here,
http://minnie.tuhs.org/pipermail/tuhs.mbox/tuhs.mbox
A more precise description of the problem was in a message
dated Date: Tue, 15 Apr 2003 00:00:37 +0000:
--------
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...
2) a 5 Kohm 4-resistor bridge named R22 on our diagram, that is phisically
BROKEN. this bridge give +5V on signals named DATA OC L, CSR OC L, OC L
and X ADD OC L. i changed it with a 4.7Kohm 4-resistor bridge, without
any result.
---------
Well
what i did for now is to cut the pin of the broken chip, without
desoldering. I will solder the new chip on the cutted pins, to avoid
desoldering the board.
Some images of the work in progress here:
http://www.freaknet.org/asbesto/pdp11/
Note:
just touching the chip, part of the plastic box went out, as you can
see in the images. Maybe this can identify a real fault on this chip ?
stay tuned! :)
--
[asbesto : freaknet medialab : radio#cybernet : GPG key on keyservers]
[ MAIL ATTACH, SPAM, HTML, WORD, and msgs larger than 95K > /dev/null ]
[http://www.freaknet.org/asbesto IW9HGS http://kyuzz.org/radiocybernet]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20031104/bf39d162/attachment.sig>
next prev parent reply other threads:[~2003-11-04 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 9:49 [TUHS] pray for us ! pdp11/34 operation! :) asbesto
2003-11-04 15:00 ` asbesto [this message]
2003-11-04 19:41 ` [TUHS] pdp11/34 can't boot. help us ! 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=20031104150038.GB9037@freaknet.org \
--to=asbesto@freaknet.org \
/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).