The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: TangentDelta via TUHS <tuhs@minnie.tuhs.org>
To: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: [TUHS] Linotron 202 Information
Date: Tue, 12 May 2020 19:36:43 +0000	[thread overview]
Message-ID: <fQmps4l3GgzBn-ROSo5OmVt5d5-E3gi-ar1lyB3js0wI3YcHBLss68J0L-gU-mN9-wPm7cuM4sdjtgxrlEVRUk6PGp6zpTmzeNk_fXtJ87k=@protonmail.com> (raw)

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

Hello.

I have a pair of controller card cages out of Mergenthaler Linotron 202 photo-typesetting machines. Sadly the machines themselves were scrapped, and these card cages are all I was able to save.

The controllers use Computer Automation Naked Mini processors, which are relatively small 16-bit minicomputers designed for embedded control applications. I've been hacking on these for a few months now and have built up a system bus pinout diagram and several schematics. I haven't been able to find any technical information online in regards to the specific model of Naked Mini processor used in the 202, but I have found a trove of documents for other Naked Mini models on Bitsavers.

I pulled the 512x4bit "boot ROM" mentioned in the "Experience with the Mergenthaler Linotron 202 Phototypesetter, or, How We Spent Our Summer Vacation" paper and dumped it, but the resulting binary doesn't produce any sane-looking code when manually disassembled using the documents on Bitsavers and reference, no matter how I arrange the nybbles. The processor also does not appear to respect the control opcodes issued by the Computer Automation LSI series programming console that I obtained. This has led me to the hypothesis that this is not a stock "Naked Mini" or later "Naked Milli" processor, but something specific to Mergenthaler.

My goal is to get the processor to run my own code, and eventually design my own MaxiBus peripherals to use with it.

If anyone knows where I can look for more information in regards to the 202 and the Naked Mini processor, or has any stories of working on these machines, I would greatly appreciate it!

Thanks.

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

             reply	other threads:[~2020-05-12 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 19:36 TangentDelta via TUHS [this message]
     [not found] ` <CAG=a+riRLizQNSEy8bL9ik3vQdRpz_bvMAR+6PHKDCL3xL4OUQ@mail.gmail.com>
2020-05-14 13:05   ` TangentDelta via TUHS

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='fQmps4l3GgzBn-ROSo5OmVt5d5-E3gi-ar1lyB3js0wI3YcHBLss68J0L-gU-mN9-wPm7cuM4sdjtgxrlEVRUk6PGp6zpTmzeNk_fXtJ87k=@protonmail.com' \
    --to=tuhs@minnie.tuhs.org \
    --cc=tangentdelta@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).