Please see remarks embedded below.
Dick
----- Original Message -----
From: ajp166 <ajp166(a)bellatlantic.net
To: <classiccmp(a)classiccmp.org
Sent: Saturday, October 28, 2000 8:10 PM
Subject: Re: Monitor for iSBC 8024
From: Richard Erlacher <richard(a)idcomm.com
>I have the original manual, and it has no hint of a monitor, aside from
<snip
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.
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.
>while the 8024 has an 8085. It was not a very nice piece of work, so
<snip
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.
I try not to dream in those . . . too little market for it any longer.
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.
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
available in several verisons for several MCU's I am inclined to use.
Learning a set of quirks is one part of the task. Of course, the code would
have to be cleaned up once the compiler coughs it up. Perhaps not too much,
though, since it is primarily important that it be able to ensure that all
the I/O bits work, and that the CTC and PIC work correctly. If the USART
doesn't work right it should be obvious enough just about right away.