[Coco] FPGA 6809

[Bill Pierce]

Good work Dave. Would you send me copies? I'll add it to my "NitrOS9 conversion to Coco" files LOL
One of these days I'll get back to working on that project... Too many projects... NEED MORE COFFEE!!

 

 


Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo at aol.com


 

 

-----Original Message-----
From: Dave Philipsen <dave at davebiz.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Tue, Sep 1, 2015 11:14 am
Subject: Re: [Coco] FPGA 6809


Good news!  After stripping linefeeds and tabs from the source files and 
after
resolving which files are for Level1 and which are for Level2 and 
which are
shared by both I was able to assemble Krn with the stock OS9 
assembler.  On the
CoCo3 FPGA running at 25 MHz with source files on SD 
card it completes the task
in 6 seconds.  Not bad!  0 errors, 30 
warnings, and $0F00 program bytes
generated.

Dave Philipsen



On , Bill Pierce via Coco wrote:
> Dave, according
to William Astle (lwtools author), the lwtools
> assembler IS a single pass
assembler. I'm assuming it treats "asm"
> files similar to the way RMA works, by
assembling an object file with
> a variable table (or temp file), to reference
when functions and
> variables are referenced in other sources then linkiing the
object
> files to create the executable.
> I'm not really sure this is the case,
and William will probably
> correct me, but I imagine it's something similar.
>
Many of the sources in the Nitros9 repo ar multi-part with different
> parts
used for different configurations.
> 
> Some of the sources are in RMA format
and in that respect, functions
> CAN be called from other sources without
"include" or "use"
> references, similar to C and RMA in OS9, hence the need for
finding
> all references to any "changed" names, or at least this is what it
>
seems is going on. The makefiles is where a lot of the majic is done.
>
Remember, this a PC assembler, not OS9.
> 
> I knew you said you were only
assembling a few of files, but my intent
> was meant as a warning to any future
attemp to include more files.
> There's a lot more there than meets the eye
:-)
> 
> I have pulled many of the Nitros9 sources and "massaged" them to
>
assemble in Nitros9, some were pretty easy... some were a nightmare,
> some were
damned near impossible without almost rewriting them! These
> files have moved a
long way from the Coco!
> 
> The Nitros9 repo builds complete disks for 9
different computers, two
> different cpus, two different levels (1 & 2), 2 clock
types (NTSC &
> PAL), about 8 different HD systems, 3 or 4 different floppy
systems,
> and does "most" of it from one general set of sources in 2
passes...
> one to compile for each machine, and one to create the disk images
of
> several types each!
> 
> It's actually pretty amazing to watch it all
build... but I would
> still rather see it scroll by on a Coco (or emulator),
and as Bill
> Noble will tell you, originally when they started NitrOS9, it WAS
all
> done on a Coco! :-)
> 
> 
> 
> 
> Bill Pierce
> "Charlie stole the handle,
and the train it won't stop going, no way
> to slow down!" - Ian Anderson -
Jethro Tull
> 
> 
> 
> My Music from the Tandy/Radio Shack Color Computer 2 &
3
> https://sites.google.com/site/dabarnstudio/
> Co-Contributor, Co-Editor for
CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> Global Moderator
for TRS-80/Tandy Color Computer Forums
> http://www.tandycoco.com/forum/
> 
>
E-Mail: ooogalapasooo at aol.com
> 
> 
> 
> 
>
https://pairlist5.pair.net/mailman/listinfo/coco

-- 
Coco mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco