Date: Fri, 17 Mar 1995 03:39:49 -0500
Message-Id: <Pine.SUN.3.91.950317003138.23679Y-100000@kaiwan009.kaiwan.com>
Errors-To: gkulosa@oberon.com
Reply-To: douglas@kaiwan.com
Originator: robot-board@oberon.com
Sender: gkulosa@oberon.com
Precedence: bulk
From: Black Feather Electronics <douglas@kaiwan.com>
To: Multiple recipients of list <robot-board@oberon.com>
Subject: Re: Mac tools for miniboard 2.0

On Fri, 17 Mar 1995, CHARLES DOUGHTY wrote:

> Hello from a new miniboard owner.
> 
> I have programmed miniboards for a course with kids,  using PCs.  So I got one
> for myself.  I have a Mac.  And lots of frustration.
> 
> The boars wotk with the mac versions of hexmon and downloader. I just have No
> way to compile my own programs.
> 
> I built my miniboard, and I am trying to use a Mac to program it.  I got the
> stuff from MIT,  but short of assember,  there seems to be no help.
> 
> Has anyone written tools for the Mac?
> 
> Does anyone know hos to use xcc11 from the MIT site?  I can not get it to
> compile any c program, or even take a command line OK. 
> 
> Anyone know an e-mail address for the author?
> 
> If there is an ASM prog that matches the icc11.exe libraries in the manual,  i'd
> love to get a copy.
> 
> 	thanks in advance
> 	      - chuck
> 
> 

Here's the file I provide on the disk for Mac people, xcc11 and as11 from 
the archives is what I use, I modified them a bit for my own uses using 
"res edit" I suppose you could too. Hope this helps..

You must choose a "xcc11" application that suits your particular need,
they are all the same application, but I went in with "ResEdit" and
modified the "str" (strings) for the starting address of the code and
where the compiler will stick text when it is compiling (actually it's
the assembler that is simply told by the ".asm" file where to stick
the text).
 
There are several versions:
 
xcc11 32K ROM     - For a 27256 (starts at 0x8000, text at 0xF000)
xcc11 8K ROM      - For a 2764  (starts at 0xE000, text at 0xFD00)
xcc11 0x4000      - For 256 RAM (starts at 0x4000, text at 0x7000)
xcc11 0x6000      - For  64 RAM (starts at 0x6000, text at 0xFD00)
 
Notice that there isn't much space for text in the "8K" versions, this
is set for max code usage. You could find the "STRS" with "ResEdit" and
change it if you feel brave enough, I did it only on a COPY of the
application.
 
You will need to check the ".lst" file to see if you have over flowed
memory or code has written over the text area etc....
 
There are two different versions of the assembler, each one is set
to subtract a OFFSET value so that the S19 file generated will load
into 0x0000 in a PROM Programmer. When you load to RAM, you just set
the monitor's OFFSET value to what is needed. My PROM programmer
doesn't have a setting for a OFFSET, maybe yours does.
 
I changed this value in the assembler by re compiling the source code
with Think C, and adding a subtract line into the code.
 
You can tell what the address is in the S19 file, its the first few
"bytes" in the line.
 
When running in RAM, it's a good idea to put this at the start of
your ".c" file, notice that it even comes before the "includes".
This clears the registers, then jumps dirsctly to the "main"
function. If you don't do this, the normal code will set
the stack back to 0x00FF, and this will not allow a return to
the monitor.
 
/* put this in when you are downloading to RAM */
ramjump()
{
#asm
	clra
	clrb
	jmp	_main
#endasm
}
 
#include "z68hc11.h"
#include "zUHCrun.h"
#include "zdelay.c"
/* the rest of your code here */
 
 
Once you have picked the C compiler you want,
to compile "C" file type the command line to it:
 
 <program.c >test.asm
 
 
Notice the SPACE character as the first thing, program.c is your c
source file, test.asm is the output asm file that you use to
assemble.
 
When you run the assembler, a box comes up, don't do anything
but press the keys to type in your file name "test.asm", then
click on the radio button for "output file", type in the name
for your output list file "test.lst", click on save and then click
on the OK button. The file will then assemble.
 
Once you get used to this, you should call your files something
simple to keep typing in names down to a minimum. Like name
them a single character "c" for the C source code, "a" for
the .asm file etc....
 
Don't blame me for all this, it's the way these programs came!