From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Codata restoration - day 1
Date: Fri, 10 Oct 2014 14:37:04 -0600 [thread overview]
Message-ID: <2FE72B5A-E2ED-4EEC-A872-17D075BA83DC@bsdimp.com> (raw)
In-Reply-To: <20141010201303.GF25824@grumpf.hope-2000.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
These days, you can buy 5.0V or 3.3V to USB adapters in the hobbyist or robotics section of many computer stores. I’ve used them to trouble shoot blown driver chips to verify they really were toast. Be careful of the voltage levels, though, since many 3.3V products can’t tolerate 5.0V…
Warner
On Oct 10, 2014, at 2:13 PM, Hans Rosenfeld <rosenfeld at grumpf.hope-2000.org> wrote:
> 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
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141010/d3ecb218/attachment.sig>
prev parent reply other threads:[~2014-10-10 20:37 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
2014-10-10 20:37 ` Warner Losh [this message]
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=2FE72B5A-E2ED-4EEC-A872-17D075BA83DC@bsdimp.com \
--to=imp@bsdimp.com \
/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).