Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] Western Electric 321 Development System Schematics?
Date: Fri, 01 Dec 2023 19:25:31 +0000	[thread overview]
Message-ID: <PxztFWGBMmXtJf7DRAGXITLnBZGc8NXDTxsAQrdaGPSdTWt4dwFBS6Jftlq1pgR71Y0tefkQIiaot2ZqWsbTp9Zu7cyYCMQc9QMnirQZL6A=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Hello everyone, I was wondering if anyone is aware of any surviving technical diagrams/schematics for the WECo 321EB or WECo 321DS WE32x00 development systems? Bitsavers has an AT&T Data Book from 1987 detailing pin maps, registers, etc. of 32xxx family ICs and then another earlier manual from 1985 that seems to be more focused on a technical overview of the CPU specifically. Both have photographs and surface level block diagrams, but nothing showing individual connections, which bus leads went where, etc. While the descriptions should be enough, diagrams are always helpful.

In any case, I've recently ordered a 32100 CPU and 32101 MMU I saw sitting on eBay to see what I can do with some breadboarding and some DRAM/DMA controllers from other vendors, was thinking of referring to any available design schematics of the 321 development stuff for pointers on integrations. Either way, i'm glad the data books on the hardware have been preserved, that gives me a leg up.

Thanks for any insights!

- Matt G.

[-- Attachment #2: Type: text/html, Size: 2076 bytes --]

                 reply	other threads:[~2023-12-01 19:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='PxztFWGBMmXtJf7DRAGXITLnBZGc8NXDTxsAQrdaGPSdTWt4dwFBS6Jftlq1pgR71Y0tefkQIiaot2ZqWsbTp9Zu7cyYCMQc9QMnirQZL6A=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.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).