rtVAX 300 ...Docs someone?

[Holm Tiffe]

Hi folks,

I've got an ISA Board with an rtVAX 300 processor lately, it was mounted
in an old 486 PeeCee and was used for some process control.

A friend gave the board to me (in conjunction with an Comtrol Rocketport
4 Port Serial Card and an Adaptec 1542CF) since he meant I'm the only
one that has some use for such things :-)
The board is from a Company called "AEON Systems Incorporated" and is
called ISA300.

In the moment I have an KAV30 VME Bus board from another friend here
with the same rtVAX 300 Processor on it. Both the ISA and The VME
Version using SCN2681 for the serial ports and this isn't that, what a
NetBSD Bootloader is knowing. I get this after the Power up:

rtVAX 300 V1.2

E...D...C...B...A...9...8...

>>>

and I can do a b eza0, then it tries to mopboot, it is loading the file
but the loader than stalls...

>>> b eza0

83 BOOT SYS


-EZA0

2..1..0..

..until I press the halt button.

Here are some pictures:

http://www.tiffe.de/images/11122012114.jpg
http://www.tiffe.de/images/KAV30-AD-1.jpg
http://www.tiffe.de/images/KAV30-AD-2.jpg
http://www.tiffe.de/images/KAV30-AD-3.jpg

Here is the 32bit ROM Image:

http://www.tiffe.de/Robotron/VAX/isa300-rom.bin.gz

I want to boot NetBSD on that ISA-300 thing, that where really nice..
Can someone help in some way? The VME Board is for later...


Regards,

Holm

[John Wallace]

On Dec 16, 7:47 pm, Holm Tiffe <h...@freibergnet.de> wrote:
> Hi folks,
>
> I've got an ISA Board with an rtVAX 300 processor lately, it was mounted
> in an old 486 PeeCee and was used for some process control.
>
> A friend gave the board to me (in conjunction with an Comtrol Rocketport
> 4 Port Serial Card and an Adaptec 1542CF) since he meant I'm the only
> one that has some use for such things :-)
> The board is from a Company called "AEON Systems Incorporated" and is
> called ISA300.
>
> In the moment I have an KAV30 VME Bus board from another friend here
> with the same rtVAX 300 Processor on it. Both the ISA and The VME
> Version using SCN2681 for the serial ports and this isn't that, what a
> NetBSD Bootloader is knowing. I get this after the Power up:
>
> rtVAX 300 V1.2
>
> E...D...C...B...A...9...8...
>
>  >>>
>
> and I can do a b eza0, then it tries to mopboot, it is loading the file
> but the loader than stalls...
>
>  >>> b eza0
>
>   83 BOOT SYS
>
> -EZA0
>
> 2..1..0..
>
> ..until I press the halt button.
>
> Here are some pictures:
>

> http://www.tiffe.de/images/11122012114.jpghttp://www.tiffe.de/images/KAV30-AD-1.jpghttp://www.tiffe.de/images/KAV30-AD-2.jpghttp://www.tiffe.de/images/KAV30-AD-3.jpg

>
> Here is the 32bit ROM Image:
>
> http://www.tiffe.de/Robotron/VAX/isa300-rom.bin.gz
>
> I want to boot NetBSD on that ISA-300 thing, that where really nice..
> Can someone help in some way? The VME Board is for later...
>
> Regards,
>
> Holm

Wow. Hadn't seen one of those (an rtVAX300 on an ISA card) before,
seen a few KAV30 and rtVAX in general though.

Please excuse if any of following questions are silly, I don't speak
NetBSD.

Does NetBSD need demand paging (or, a variant on that theme, if built
for VAX does it expect VAX-style MMU capable of supporting demand
paging)? The RTvax300 doesn't do that, it's only supported DEC OS is
VAXELN which gets by just fine without demand paging. Or something
like that.

Is NetBSD actually known to work on rtVAX300? A quick search reveals
some discussion on the mailing list in 2002, e,g, as archived at
http://mail-index.netbsd.org/port-vax/2002/11/12/0009.html (including
more important details on MMU differences).

If you are moving in these circles (what other kind of folk had
KAV30s?) you may already have access to some VAXELN knowledge. If you
do have that, I'd see if you can get a simple VAXELN system loaded
just to check as much as possible before moving even further into
rarely explored territory - NetBSD on rtVAX.

Best of luck!

[John Wallace]

On Dec 16, 7:47 pm, Holm Tiffe <h...@freibergnet.de> wrote:

> Hi folks,
>
> I've got an ISA Board with an rtVAX 300 processor lately, it was mounted
> in an old 486 PeeCee and was used for some process control.
>
> A friend gave the board to me (in conjunction with an Comtrol Rocketport
> 4 Port Serial Card and an Adaptec 1542CF) since he meant I'm the only
> one that has some use for such things :-)
> The board is from a Company called "AEON Systems Incorporated" and is
> called ISA300.
>
> In the moment I have an KAV30 VME Bus board from another friend here
> with the same rtVAX 300 Processor on it. Both the ISA and The VME
> Version using SCN2681 for the serial ports and this isn't that, what a
> NetBSD Bootloader is knowing. I get this after the Power up:
>
> rtVAX 300 V1.2
>
> E...D...C...B...A...9...8...
>
>  >>>
>
> and I can do a b eza0, then it tries to mopboot, it is loading the file
> but the loader than stalls...
>
>  >>> b eza0
>
>   83 BOOT SYS
>
> -EZA0
>
> 2..1..0..
>
> ..until I press the halt button.
>
> Here are some pictures:
>

> http://www.tiffe.de/images/11122012114.jpghttp://www.tiffe.de/images/KAV30-AD-1.jpghttp://www.tiffe.de/images/KAV30-AD-2.jpghttp://www.tiffe.de/images/KAV30-AD-3.jpg

>
> Here is the 32bit ROM Image:
>
> http://www.tiffe.de/Robotron/VAX/isa300-rom.bin.gz
>
> I want to boot NetBSD on that ISA-300 thing, that where really nice..
> Can someone help in some way? The VME Board is for later...
>
> Regards,
>
> Holm

Another thought, even more random - have you checked the voltages on
the power supplies? The rtVAX300 wasn't exactly a low-power device,
and I don't know what would happen (to PC or rtVAX) if some voltage
was out of tolerance.

[Roger Ivie]

On 2012-12-17, John Wallace <johnwa...@yahoo.co.uk> wrote:
> Does NetBSD need demand paging (or, a variant on that theme, if built
> for VAX does it expect VAX-style MMU capable of supporting demand
> paging)? The RTvax300 doesn't do that, it's only supported DEC OS is
> VAXELN which gets by just fine without demand paging. Or something
> like that.

rtVAX300 is a CVAX. It's earlier variants of the rtVAX that had
funky paging.

I do have documents *somewhere* buried in a box in a storage shed,
but it'll probably be several years before they surface (and I'll
only find them accidentally; that's the way it goes).

The rtVAX300 documents have a really nice writeup of the CVAX
pin-bus, FWIW.

Never heard of one on an ISA board, though.
--
roger ivie
ri...@ridgenet.net

[Holm Tiffe]

NetBSD is a full flavored BSD Unix inclusive demand paging and No, it
seems that nobody ver tried to run it on an rtVAX 300.

I've read the old articles too and I'm hope that Roger is right when he
means that the rtVAX 300 is a full featured CVAX processor with a
functioning VM; Sustem. (He is my only source for that information).


My Problem with the NetBSD at the moment is that serial chip thats build
the console interface, I don't know where it sits in the Memory or IO
Space and the Jump vectors to the console output aren't know to me this
time.

Regards,

Holm

[Holm Tiffe]

On 18.12.2012 02:29, Roger Ivie wrote:
> On 2012-12-17, John Wallace<johnwa...@yahoo.co.uk> wrote:
>> Does NetBSD need demand paging (or, a variant on that theme, if built
>> for VAX does it expect VAX-style MMU capable of supporting demand
>> paging)? The RTvax300 doesn't do that, it's only supported DEC OS is
>> VAXELN which gets by just fine without demand paging. Or something
>> like that.
>
> rtVAX300 is a CVAX. It's earlier variants of the rtVAX that had
> funky paging.
>
> I do have documents *somewhere* buried in a box in a storage shed,
> but it'll probably be several years before they surface (and I'll
> only find them accidentally; that's the way it goes).

Hmm, that doesn't sound very good to mee..

>
> The rtVAX300 documents have a really nice writeup of the CVAX
> pin-bus, FWIW.
>
> Never heard of one on an ISA board, though.

Yes, I'm too. That Board ist the only one I ever saw. Don't knopw what
happened to my links above, all concatenated thogether.. :-|

My Problem is, that I'm far away from being a VAX Guru and VAX Assembler
I have seen before, but that's all.I'll trya to contact this AEON
Systems Company now, but I don't think that I get a useful answer..
Roger please tell me what you knowabout this rtVAX, maybe it helps a litte..

Regards,

Holm

[Bob Koehler]

In article <slrnkcvhon...@stench.no.domain>, Roger Ivie <ri...@ridgenet.net> writes:
>
> rtVAX300 is a CVAX. It's earlier variants of the rtVAX that had
> funky paging.

I thought some variations of the rtVAX had only user and kernel
mode (enough for VAXEln).

[Roger Ivie]

Indeed. Early versions where they went through the bother of designing
a special processor. Those were based on MicroVAX II.

The rtVAX300 is a CVAX + SGEC + console + ROM + glue in a module.

I have a prototype rtVAX400, which is SOC + SGEC + console + ROM
hanging on my cubicle wall. There was a nasty bug in the arbitration
circuitry of the FPGA that never got sorted out.
--
roger ivie
ri...@ridgenet.net

[Holm Tiffe]

...are you sure about the console in the rtVAX300? On both boards(ISA +
VME) that I have here is an SCN2681 mounted to do the serial interface,
the smallest Version of that chip w/o the handshake singals.

The ROM also is external...
Regards,

Holm

[Roger Ivie]

On 2012-12-18, Holm Tiffe <ho...@freibergnet.de> wrote:
> ...are you sure about the console in the rtVAX300?

Not entirely. It's been many years since I fiddled with one, and
I was never that involved in it to begin with.

> The ROM also is external...

IIRC, the rtVAX300 had an on-board ROM containing the console firmware.
The external ROM would supply a customer image that could be booted
using the on-board console firmware. However, I may be mistaken
about this, also; as I said, I was never much involved with the
300. I no longer have any rtVAX300s hanging around that don't have
their box on (they were typically potted in a larger shell that
had information like their model number and MAC address engraved
on it; a previous employer manufactured the prototype run for
DEC, so I had access to a handful that had failed manufacturing
tests and were not delivered).
--
roger ivie
ri...@ridgenet.net

[John Wallace]

On Dec 18, 8:24 pm, Roger Ivie <ri...@ridgenet.net> wrote:

That tallies with my recollection, but we already know that my memory
is not 100%: Basic boot ROM internal, real OS to be booted either from
external PROM or (typically) from the network, maybe from SCSI (did
anybody ever try booting VMS on one of these? I'm not aware...).

I found a paper KAV30 Programmers Reference but it's part of the
VAXELN docset, ie it'll already be on CD or t'Internet somewhere and,
being focused on VAXELN, says nothing I could find aout booting an OS
other than VAXELN. It does mention (extremely briefly) booting from an
external ROM.

[John Wallace]

On Dec 18, 2:10 pm, Holm Tiffe <h...@freibergnet.de> wrote:
> On 18.12.2012 02:29, Roger Ivie wrote:
>

I'm going to (again) suggest you have a look around for VAXELN
resources. I realise it may not be easy, but rtVAX300 resources in
general are very sparse.

You're getting output on the console so the console clearly works
before transferring to the OS.

My memories are distant, but I would assume (!) that the console
serial port info is configurable somewhere in VAXELN, which means you
can find out from VAXELN what address it is using, and then adjust
your NetBSD to match (assuming you can see console output from
VAXELN). Even if it's not configurable, the relevant driver may be
present as part of the standard VAXELN kit.

As an alternative, is there not some flavour of console command that
allows you to examine the IO space and see what addresses are used?
It's been a while since I did this kind of thing but I do seem to
recall the MicroVAX 3xxx (CVAX?) consoles had something along those
lines. Whether it was also present in an rtVAX console is perhaps a
slightly different question.

Best of luck.

[Roger Ivie]

On Dec 18, 2:10 pm, Holm Tiffe <h...@freibergnet.de> wrote:
> Hmm, that doesn't sound very good to mee..

I went and poked about in my storage shed a bit this afternoon. I think
I know which pile of boxes it's in, but it's not in any of the boxes
in that pile that are easy to get to.
--
roger ivie
ri...@ridgenet.net

[Roger Ivie]

On 2012-12-16, Holm Tiffe <ho...@freibergnet.de> wrote:
> Hi folks,
>
> I've got an ISA Board with an rtVAX 300 processor lately, it was mounted
> in an old 486 PeeCee and was used for some process control.

I am currently holding the following documents in my grubby little
fingers:

- Two copies of a rather hefty document titled "rtVAX 300 Hardware
Information Kit: Hardware User's Guide" (EK-382AB-UG-002).
- One copy of the depressingly slim "rtVAX 300 Hardware Information Kit:
Programmer's Guide" (EK-383AA-PG-001), which seems to be all about
writing VAXeln device drivers.
- One copy of the even slimmer "rtVAX 300 Release Notes" (EK-417AA-RN-001)

According to Chapter 6 (Console and Boot ROM Interface):

"The rtVAX 300 processor module does not contain an internal console
serial-line unit (SLU); however, 16 console registers are reserved in
the rtVAX 300 processor reserved space to select and program an external
Signetics 2681 console dual universal asynchronous receive/transmitter
(SCN 2681 DUART). These regosters occupy physical locations 201000000 to
2010003F. The built-in firmware of the rtVAX 300 programs and
communicates with the external SCN 2681 DUART, which implements these
console registers."

It then refers to table 3-13 for a list of the registers. That table
says:

20100000 Channel A mode registers (MRA1, MRA2) (R/W)
20100004 Channel A status register (R)
Channel A clock select register (CSRA) (W)
20100008 Reserved (R)
Channel A command register (CRA)
2010000C Channel A receive holding register (RHRA) (R)
Channel A transmit holding register (THRA) (W)
20100010 Input port change register (IPCR) (R)
Auxiliary control register (ACR) (W)
20100014 Channel A/B interrupt status register (ISR) (R)
Channel A/B interrupt mask register (IMR) (W)
20100018 Counter/timer interval register upper (CTU) (R)
Counter/timer interval register upper (CTUR) (W)
2010001C Counter/timer interval register lower (CTL) (R)
Counter/timer interval register lower (CTLR) (W)
20100020 Channel B mode register (MRB1, MRB2) (R/W)
20100024 Channel B status register (SRB) (R)
Channel B clock select register (CSRB) (W)
20100028 Reserved (R)
Channel B command register (CRB) (W)
2010002C Channel B receive holding register (RHRB) (R)
Channel B transmit holding register (THRB) (W)
20100030 Reserved (R/W)
20100034 Input port register (R)
Output port configuration register (OPCR) (W)
20100038 Start counter command register (R)
Set output port bits command register (W)
2010003c Stop counter command register (R)
Reset output port bits commnad register (W)

--
roger ivie
ri...@ridgenet.net

[Roger Ivie]

On 2012-12-26, Roger Ivie <ri...@ridgenet.net> wrote:
> I am currently holding the following documents in my grubby little
> fingers:
>
> - Two copies of a rather hefty document titled "rtVAX 300 Hardware
> Information Kit: Hardware User's Guide" (EK-382AB-UG-002).

I'm actually mistaken. I have to versions of this document:
EK-382AB-UG-001 and EK-382AB-UG-002. The addresses I quoted were
taken from the -002 revision.
--
roger ivie
ri...@ridgenet.net

[Holm Tiffe]

I ove you a beer :-)

You are great, thank you very much.

I'll try to find out what happens when I write some bytes to that
adresses and later will try to patch the netbsd's boot.

Regards,

Holm

[Holm Tiffe]

On 26.12.2012 23:47, Roger Ivie wrote:

Short test:

>>> help

DEPOSIT [{ /B | /W | /L }] [{ /P | /V | /I }] [/U] [/N:<n>]
[{ <addr> | <sym> | + | - | * | @ } [<datum>]]
EXAMINE [{ /B | /W | /L }] [{ /P | /V | /I }] [/U] [/N:<n>]
[{ <addr> | <sym> | + | - | * | @ }]
SET BOOT <ddau>
SET BFLG <bflg>
SET HALT <1-3>
SET TRIG <0-1>
SHOW { BOOT | BFLG | ETHER | HALT | MEM | TRIG }
INITIALIZE
UNJAM
BOOT [/[R5:]<bflg>] { EZA0 | PRA0 | PRBx | CSBx }
CONTINUE
START <addr>
REPEAT <cmd>
TEST <n>
FIND [{ /MEM | /RPB }]
XFER <addr> <cnt> ...
HALT
HELP

>>> d/b 2010000C 41
A
>>> d/b 2010000C 42
B
>>> d/b 2010000C 43
C
>>>

:-)

There is no test on this console to display the used IO Space.

Regards and a happy new year,

Holm

[Roger Ivie]

On 2012-12-26, Roger Ivie <ri...@ridgenet.net> wrote:

> - One copy of the depressingly slim "rtVAX 300 Hardware Information Kit:
> Programmer's Guide" (EK-383AA-PG-001), which seems to be all about
> writing VAXeln device drivers.
> - One copy of the even slimmer "rtVAX 300 Release Notes" (EK-417AA-RN-001)

I've scanned these two and thrown them up on my Google Docs thingie.
I've marked them public, which Google tells me means you don't have to
tell Google who you are to read them.

Programmer's Guide:
https://docs.google.com/file/d/0B0bm31mTHM8oV2JrS3NQQVIzYzA/edit

Release Notes:
https://docs.google.com/file/d/0B0bm31mTHM8obHlCaDJKQ3ZjcVk/edit

These two are of limited use. Scanning the hardware user's guide will
take more work since it has fold-out pages for timing diagrams and the
simple-minded scanner I used this time can't do that. So I'll have to
fire up my bigger scanner (still no document feeder, though; :-( ).

I'll also have to go B&W TIFF or something as these smallish documents
are still outrageously huge.
--
roger ivie
ri...@ridgenet.net

[Bill Gunshannon]

In article <slrnkdq1ae...@stench.no.domain>,

You could also consider sending them to Al Kossow at bitsavers.

bill

--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
bill...@cs.scranton.edu | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>

[Charles Richmond]

"Bill Gunshannon" <bill...@cs.uofs.edu> wrote in message
news:ak5pi6...@mid.individual.net...

> In article <slrnkdq1ae...@stench.no.domain>,
> Roger Ivie <ri...@ridgenet.net> writes:
>> On 2012-12-26, Roger Ivie <ri...@ridgenet.net> wrote:
>>> - One copy of the depressingly slim "rtVAX 300 Hardware Information Kit:
>>> Programmer's Guide" (EK-383AA-PG-001), which seems to be all about
>>> writing VAXeln device drivers.
>>> - One copy of the even slimmer "rtVAX 300 Release Notes"
>>> (EK-417AA-RN-001)
>>
>> I've scanned these two and thrown them up on my Google Docs thingie.
>> I've marked them public, which Google tells me means you don't have to
>> tell Google who you are to read them.
>>
>> Programmer's Guide:
>> https://docs.google.com/file/d/0B0bm31mTHM8oV2JrS3NQQVIzYzA/edit
>>
>> Release Notes:
>> https://docs.google.com/file/d/0B0bm31mTHM8obHlCaDJKQ3ZjcVk/edit
>>
>> These two are of limited use. Scanning the hardware user's guide will
>> take more work since it has fold-out pages for timing diagrams and the
>> simple-minded scanner I used this time can't do that. So I'll have to
>> fire up my bigger scanner (still no document feeder, though; :-( ).
>>
>> I'll also have to go B&W TIFF or something as these smallish documents
>> are still outrageously huge.
>
> You could also consider sending them to Al Kossow at bitsavers.
>

Bill, the problem with sending documents to Al Kossow is... Al is "nine
years behind on his ironing", as Phyllis Diller would have said. Al is a
very busy guy... and what he is busy with usually is *not* scanning
documents. I asked Al once, and for scanning documents for bitsavers, he
recommends scanning at 400 dpi B&W TIFF and using level 4 CCITT Fax
compression (I know it's *not* called CCITT anymore... but that is the name
that sticks in my head). For the color covers to manuals, I think he
suggests 200 dpi jpegs. Even with all this care, a manual can easily run 40
to 60 meg in size as a PDF.

My suggestion about the larger documents is... look into software that will
stitch together documents that are too large to scan in one go. Many of us
are forced to this... because the larger scanners are so expensive.

--

numerist at aquaporin4 dot com

[Holm Tiffe]

I've got a manual in the meantime that helps a little.

Take a look at here:

http://www.tiffe.de/Robotron/VAX/

There are some pictures and the file 382ABUG2.PDF which is the RTVAX 300
Hardware User Guide.

With this manual and a little Help from you and the friends from the
cct...@classiccmp.org mailing list I've managed to get this:

>>> b eza0

83 BOOT SYS


-EZA0

2..1..0..

vax_cpudata: a000006
vax_cputype: a
vax_boardtype: a000000
vax_boardtype(sie): a000009
fromnet: 1

>> NetBSD/vax boot [1.11 (Thu Jan 3 17:33:22 CET 2013)] <<
>> Press any key to abort autoboot 0
SGEC: Ethernet address 00:00:f8:50:93:14
Trying BOOTP
Using IP address: 192.168.50.20
myip: rtvax (192.168.50.20)
root addr=192.168.50.50 path=/data/home/exports/rtvax
2587200+174320 [211280+200960]=0x3071a0

?06 HLT INST
PC = 800E2E9D
>>>

This is the NetBSD 6.0 Generic kernel that is knowing nothing
about that Hardware, I've expected that halt, but I have hacked up
NetBSDs network boot loader to make something useful on this rtVAX300.

No this thing gets complicated, I know almost nothing about VAX Buses
devices and the VM System, have subscribed to the port-vax mailingslist
from majo...@netbsd.org, mabe I can get this thing to run NetBSD...

Regards,

Holm

[Roger Ivie]

On 2013-01-03, Holm Tiffe <ho...@freibergnet.de> wrote:
> There are some pictures and the file 382ABUG2.PDF which is the RTVAX 300
> Hardware User Guide.

It certainly looks like the document I have.

> No this thing gets complicated, I know almost nothing about VAX Buses
> devices and the VM System, have subscribed to the port-vax mailingslist
> from majo...@netbsd.org, mabe I can get this thing to run NetBSD...

You'd probably want to start with a configuration similar to the
MicroVAX 3100, which is also a CVAX-based system with SGEC.

Good luck!
--
roger ivie
ri...@ridgenet.net

[bbro...@yahoo.com]

Hi All,

Firstly, I can shed a little light on the Aeon board described in this thread if anyone's interested. Secondly, we're looking for any and all rtvax300 documentation available as well as a Vaxeln Toolkit if anyone has one. I really appreciate what documentation you've posted.

Bob

[John Wallace]

If I remember rightly, VAXELN kits and online documentation were on
the VAX/VMS layered product CDs for many years (but the product was
never on Alpha so it has to be a CD set for VAX). It shouldn't be that
hard to get hold of a copy? VAXELN V4.6, a quite late version, came
out in 1996 and includes rtVAX 300 support, but for most purposes the
previous couple of versions would do too. Find a VAX ConDist CD set
from the early to mid 1990s and see what's there? I thought I had some
here, but cannot find them right now.

Paper documentation might be slightly trickier, but for most purposes
(!that again?) the online stuff would be sufficient. A search for
"VAXELN sysworks" should find the VAXELN docs in bookreader format.
Finding something to read them with is another story, but as you may
need a VAX/VMS system (real or emulated) on which to use VAXELN, you
might as well start with BOOKREADER on VMS DECwindows too. It will
hopefully give you an idea of how hard to look for the paper docs.

PostScript-format documentation was available for many DEC products at
various times. Afaik, that never applied to VAXELN.

I'd be interested in hearing a little of what attracted the Aeon folks
to the rtVAX/VAXELN environment; if you feel like posting some info
about the Aeon board, I'd read it.

Best of luck!

[ne...@eli.com]

Hi Holm

We could use the RT300 you have. We have lots of vintage DEC stuff here and could trade you for them. I would pay all shipping costs if you have interest.

You can check our website www.eli.com we deal in EOL DEC, SUN , HP Brocade equipment.

Thanks

Neal

[bbro...@yahoo.com]

Hi John,

Don't know why Aeon specifically used the rtvax300. I do know they released quite a few different designs that used it. There is a VME300 as well as several versions of an ISA based design that ADE used for the semi industry. Our experience is with that particular platform. We're currently producing a replacement for the old ISA300D board that ADE used. It goes in a wafer scanner that checks bow and warp and runs on a SCO unix pc. Obviously rtvax300 modules are limited in availability and we are in the process of migrating the design to a newer embedded platform like 68000. We are collecting any and all development tools for this old system as they may shed some light on certain issues we've run into. We managed to get a toolkit already. Thanks again. Bob

[Roger Ivie]

On 2013-01-30, bbro...@yahoo.com <bbro...@yahoo.com> wrote:
> Don't know why Aeon specifically used the rtvax300.

Because VAX is awesome?
--
roger ivie
ri...@ridgenet.net