[Coco] FPGA 6809

Mon Aug 31 22:43:14 EDT 2015

Dave, there are actually multiple problems in trying to assemble any of the Nitros9 stuff from the repo on a Coco (or cocofpgs/emulator) in NitrOS9.

First, changing a name in one file, means you need to search EVERY file in the repo for any other reference to that name, including the defs.

Second, ALL the defs need massaging and renaming as the original names have been changed making them absolutely useless from within NitrOS9 itself. You need the new defs because a lot has been added. I have most of the defs converted so I can use the newer system calls in my projects.

Third, in ALL the sources, all the "Section" stuff needs to be removed and in cases of "rma" sources (there are a couple), "section" needs to be replace by "psect" & "endsect" and all variable put in "vsect" and "csect". In some of the "asm" stuff, the:

 ifp1
 use /dd/defs/os9defs
 endif

has been removed and needs to be added (lwtools is one pass so it isn't needed).

Forth, ALL the "multi-platform/multi-cpu" stuff has to be addressed (in every single file). Unless you set some equates, this stuff will drive you up the wall as EVERY file has conditionals for 2 or more build types.

There are a few other problems that I can't recall at the moment, but I know there is more.

I started a project a while back to convert the nitros9 sources to standard OS9 format, but put it aside due to the repo was being overhauled at the time, so I moved on to other projects. It is a much bigger task than you would think!
I would love to see NitrOS9 compile under NitrOS9 for a change. That would be AWSOME!.

Even with the emulators, you can overclock the CPU and assembly is EXTREMELY fast. I do this in compiling C sources in NitrOS9 on Vcc. I compile at about 72mhz and a 125 file multi-source project (HUGE!) compiles in less than a minute. On a real Coco this takes about 3-4 hours.

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: Mon, Aug 31, 2015 9:47 pm
Subject: Re: [Coco] FPGA 6809

Ok, so besides stripping all of the linefeeds and tabs I need to check for
labels that are longer than eight characters.  That shouldn't be too tough to
fix.  Right now, I'm assembling Boot with no errors and Krn is giving me a few;
maybe 15-20.  I'll have to go look at the repo again. When I looked in the defs
folder today (well at least ONE of the defs folders) the defs files I mentioned
were nowhere to be found. 

Any progress on Multicomp-DE0?

Dave Philipsen

> On
Aug 31, 2015, at 8:33 PM, Bill Nobel <b_nobel at hotmail.com> wrote:
> 
> That
would be the reason why.  The source in SourceForge is setup for Toolshed to be
compiled on a pc.  The labels in the code are setup to be longer than 8
characters, which asm in Nitros9 ignores everything beyond.  Even if you get it
compile you will get multiple define errors.  The DEFS files are in the repo
under defs folder.
> 
> Bill Nobel
> 
>> On Aug 31, 2015, at 6:50 PM, Dave
Philipsen <dave at davebiz.com> wrote:
>> 
>> I don't think so.  To be totally
honest I'm not exactly sure how that works.  I'm assuming that the fitter will
assign pins for you if you don't manually assign them.  If you go into the Pin
Planner it should show you a diagram of the FPGA and then below that there is a
section where you can see all of the pin assignments. You should be able to
scroll down to the bottom of that section and double click on <<new node>> to
make a pin assignment.
>> 
>> Quick question on NitrOS9:  Where are the defs
files found in the repository?  I am using some defs files that someone else
gave me on a boot disk image but when I try to assemble the Krn module it is
choking on terms like "D.MLIM", "D.FMBM", "D.BTLO", and a few others.  I have
fairly recent defsfiles (2011) and the defsfile uses os9defs, rbfdefs, scfdefs,
and systype.  Am I missing anything?
>> 
>> Maybe I'm crazy for assembling this
directly under NitrOS9 but the assembler works pretty quickly at 25 MHz.  I
don't have the cross assembler and the dev system set up on a PC.
>> 
>> 
>>
Dave Philipsen
>> 
>> 
>>> On , Bill Nobel wrote:
>>> Would that be the fitter
pins in the pin planner?  I saw those there
>>> and I thought it was a suggested
pin.
>>> Bill Nobel
>>>> On Aug 31, 2015, at 4:30 PM, Dave Philipsen
<dave at davebiz.com> wrote:
>>>> Just something else I thought of:  When starting
a project out from scratch (i.e. CoCo3 or 6809 core on FPGA) there are some
things to take into consideration when assigning pins to devices.  The Altera
FPGAs are divided into physical banks and Altera suggests that the high speed
signals such as address or data lines be grouped together within a bank or
adjacent banks if at all possible.  Also, at least on some devices, there are
certain banks that they consider more well suited for high speed stuff.  If you
do a little research on the 'net you'll find some notes on this in the design
considerations.
>>>> Dave Philipsen
>>>> --
>>>> Coco mailing list
>>>>
Coco at maltedmedia.com
>>>> https://pairlist5.pair.net/mailman/listinfo/coco
>>

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

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