>By the way: I'm allmost ready with the Elekor SC/MP emulator
>when finaly done I will may it aviable.
Ok which version of the SC/MP?
ISP8A500 (PMOS part)
isp8a600 (aka 8060 NMOS)
SC/MPII 807x
(the 8073 was the version with NIBBLE a Tiny BASIC in internal rom)
There were subtle to not so subtle differences. I have two of the three
(original PMOS and 8073).
Allison
>Happy vax, it now has a console. :) Of course I have to load the new
license
>pack somehow. I have it on a dos floppy, is there any nice way to get
my
>vaxstation to mount this?
>--
>Jim Strickland
>jim(a)DIESPAMMERSCUMcalico.litterbox.com
Run VMSlicense and type in the info... it's not that hard. VMS cant'
mount dos. The easy way would be to push it through the
PC(or whatever) serial line while emulating a console.
Allison
From: Richard Erlacher <richard(a)idcomm.com>
Use the editor that comes with the mailer, please.
>Actually, it's not simple at all to set up the boards with dozens of
jumpers
>and pin fields for strappable options. Moreover, while the port
locations
>are pretty simple to set up in accordance with the "default" settings,
there
>are numerous things that, while not left to chance, are not completely
clear
>as described in the doc.
As if I dont know this? I have an ISBC80/10 and a BLC80204 plus several
Hurikon Multibus boards. It's a task I've done before along with
designing
for multibus. Whats the point? You set up the board to a common config
and with that write a dumb monitor for those addresses. Added t that
code is some diagnostic stuff to blink leds or toggle lines that would
otherwise do nothing to show there is a cpu and some ram operational
if it doesnt talk to the console.
>> code generator was created.
>>
>I didn't mean to suggest I want to produce a code generator for those,
as
>they already exist. I just don't want to wade into a new compiler if it
>doesn't support several commonly used MCU's. The Hi-Tech compiler is
I havent a clue why you said that at all since the origin of the smallc-c
compiler is 8080? I still have the original DDJ articles with sources.
Allison
Well, I just purchased a VT220 (amber) and a scsi box from Will Jennings.
Cost me $50 and a cardboard box, delivered. Will's a good guy to deal with.
Happy vax, it now has a console. :) Of course I have to load the new license
pack somehow. I have it on a dos floppy, is there any nice way to get my
vaxstation to mount this?
--
Jim Strickland
jim(a)DIESPAMMERSCUMcalico.litterbox.com
-----------------------------------------------------------------------
BeOS Powered!
-----------------------------------------------------------------------
From: Richard Erlacher <richard(a)idcomm.com>
>I have the original manual, and it has no hint of a monitor, aside from
one
>they sold as a separate product. I'm planning to use the monitor to
test
>the various boards I have.
Then you dont have the software manual. My memory of the board was
three books a users manual, one on the hardware, and the software manual.
I know as I loaned out the software manual for my 80/10 years ago and
never saw it again.
>According to the Intel doc's, the 8010,8020, and 8024 boards all used
the
>same hardware addresses, as did the monitors they sold for them. That
will
>serve me well, as I intend to use a script running on a terminal
emulator on
>the PC in order to verify proper operation of the various features on
the
>board.
As long as you know the addresses and setup for the ports and all
it's pretty simple.
>while the 8024 has an 8085. It was not a very nice piece of work, so
I'm
>hopeful I can find something a bit more up to date. The Intel monitor
was
>delivered to the customer who paid for it back in the '70's, and I
haven't
>seen one since. I'm just not interested in writing a monitor just for
the
They never changed it much save for a bug fix or two through the early
80s.
use the monitor for the SBCs either the 8080 or 8085. Intel had the same
basic one they used all over the place.
>Does anybody know the Hi-Tech 'C' compiler for CP/M well enough to know
>whether it produces 8080 code?
It does, its a compiler switch. Crummy code though.
>half-a-dozen 'C' compilers for CP/M, any one of which should produce
8080
>code, but AFAIK the Hi-tech (Pacific) compiler is the only one that also
has
>a version for several other CPU's as well, so it would be worth using
just
>for the exercise. I could justify writing an original monitor in a 'C'
>dialect portable to several MCU's, but not just one. I might as well
do
>that in assembler.
It's your pain. I dream in 8080/85/z80 so its no big deal to write a 1k
monitor. It's likely easier now as I have a basic monitor on hand that
ive used for years and could be tweeked for that.
Of course any of the published monitors for 8080 like the LLL AMS80
(KILOBAUD) monitor will do as well. If you have Burskys book
The S100 bus handbook there is a copy of Vector Ones monitor in
there.
A monitor for a a ISBC80xx or BLC80xx is a rather basic thing and
should easily fit in a 2716 (I've done nice ones for 2708!).
>Aztec, BDS, Whitesmith, among others, are all history. <sigh> Maybe the
>"small-C" (Hendrix) could be used, since I can write my own code
generator.
>I'd rather skip that step though.
small-C _IS 8080_! that was the original version, it was later that z80
code
generator was created.
Allison
At 08:15 AM 10/28/00 -0700, Gene wrote:
>> buy the OS. I hand disassembled the H-17 ROM and figured
>> how to read and write to the floppy. I took a 8080 listing
>> for a FIG Forth and put that on it with my disk interface
>Now THAT is dedication. :)
>
>> docs and such that I have as well. Maybe someone local can
>> scan stuff that that I don't have the time to deal with.
>> ( I live in Santa Cruz Ca. ).
>
>This would be great! Thanks!
>
>g.
>
Gene,
It looks like you're getting offers for stuff from all over the place.
It should be a GOOD website.
Joe
From: Richard Erlacher <richard(a)idcomm.com>
>National made an extension on the 8048, i.e. the 8050, and the 8035 in
the
>form of an 8040. It had 256 bytes of on-board RAM, but otherwise pretty
>well compatible with the Intel parts. They pushed it pretty hard for a
year
>or two.
Signetics did the 8050 as well.
I know I have their manuals and 5 or 10 of the NSC8050s (pull EA and
you have romless usability. I was NEC single chip product support
during those years. So from about 76 to 85 I ahve a pretty good
collection of intel or intel compatable vendors docs.
Allison
From: Bill Pechter <pechter(a)pechter.dyndns.org>
>> > My Sparcstation was never so strange. I guess Unix is Unix is Unix,
but
>> > VMS is odd.
;) From the point of view of someone that went
OS/8->TOPS10->CP/M->RT-11->RSTS11->VMS
Unix is odd.
Seriously, I have no beef with unix save for just like DEC OSs are a
culture
thing so it is for unix as well.
Allison
From: Richard Erlacher <richard(a)idcomm.com>
>Well, I checked my 1980 National Semi MCS-48 data book and found not
only
>that there was no 8154, but that the 8155 and 8156 were not listed
(yet)
>either. They did make them, however, because I have them (INS8155,56)
among
>my parts.
The NS8156/55 were introduced a year or so later.
>would appear together with products coming from device families intended
to
>replace the MCS-48. It must have lived iwithin a fairly narrow window.
National did the 804x for a while.
>NEC and a few others made the 8155 and '56, so they might have made a
>version of the 8154 as well.
They did not. the 8154 was an oddball part.
Allison
From: Richard Erlacher <richard(a)idcomm.com>
I've not yet found a board-resident monitor for the Intel iSBC 8024
board. I've got a number of these on hand and have used sadly inadequate
resources that worked (barely) for what I've been doing with them, but
would like to make it worthwhile writing a set of test scripts for my
notebook funcitoning as a terminal attached to the iSBC 8024.
Find the manual for that. The code they used it in it. Also they used
the same monitor
in a lot of products with mostly address changes.
Allison
