The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rosenfeld@grumpf.hope-2000.org (Hans Rosenfeld)
Subject: [TUHS] Codata restoration - day 1
Date: Fri, 10 Oct 2014 22:13:03 +0200	[thread overview]
Message-ID: <20141010201303.GF25824@grumpf.hope-2000.org> (raw)
In-Reply-To: <B2E15B59-0249-468F-A4CF-CB1D099F0006@leedsbeckett.ac.uk>

Hi Michael,

On Fri, Oct 10, 2014 at 05:26:58PM +0000, Engel, Michael wrote:
> The serial cable is working, we tried all sorts of handshake configurations.
> If we get any characters back (the system is running at 9600 baud, I tried
> all combinations of 7/8 bit, none/even/odd/mark/space parity and 1/2 stop
> bits), these are garbled and contain mostly "1" bits (0xfc, 0xfe, 0xff or 
> similar).
> 
> The UART itself seems to work (exchanged it with the one from the non
> working board - same result), so now I suspect the AM26LS32 RS423
> driver to be the culprit.

I've had that a few times with PDP11s and VAXen from the 80s. The line
receivers suddenly died, showing exactly the symptoms you describe.
Those were different chips (ua96XX), but the concept is the same.
Replacing them with newer chips from the same family worked without
problems.


Hans


-- 
%SYSTEM-F-ANARCHISM, The operating system has been overthrown



  parent reply	other threads:[~2014-10-10 20:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 17:26 Engel, Michael
2014-10-10 18:00 ` Dave Horsfall
2014-10-10 19:21   ` Engel, Michael
2014-10-10 19:55     ` Dave Horsfall
2014-10-12 18:18       ` Erik Fair
2014-10-11 21:48     ` Clem Cole
2014-10-10 20:13 ` Hans Rosenfeld [this message]
2014-10-10 20:37   ` Warner Losh

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=20141010201303.GF25824@grumpf.hope-2000.org \
    --to=rosenfeld@grumpf.hope-2000.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).