----- Original Message -----
Sent: Wednesday, July 09, 2003 10:03
AM
Subject: Re: Loading a compiled program;
Run UUT
There are samples of loading & running
UUT code in the Vector test scripts for Asteroids based on the CAT Box
trick to draw a "+" to the screen. To make the Vector test work you must
disable the WD RESET.
Any program of length is going to need to service
the WD RESET or depend on it to be disabled.
You might want to read up more on the "Quick
Test" or "Hyper Test" pods as they use a similar method of RAM
testing.
Kev
Has anyone done this before? Building a
compiled program, loading it byte by byte into memory, and then doing Run
UUT? I was playing around with this last night, but I couldn't get it to
work. (6809E based system). Could be lots of things at this point, and I'm
going to review the Troubleshooter documentation, but I thought I'd ask.
Talk of testing RAMs made me think to try a few tests to see how easy it
would be to build a "fast RAM" tester. I just took a snippet of code from
the Qix self-test and wanted to run a modified version of that. However,
even a simple test where I'm writing to a specific address did not seem to
work. Been a looong time since I wrote assembly, and I've never had to
bother looking at the generated op codes! The code was relocatable
code.
On a related note, it appears that it's
possible to write some z80 code that could be executed by the 9010A base
unit. You can't use the Fluke compiler, however, because you'd need to have
a slightly different record structure for the program. This is part of the
reason that I was asking about interest level in a new compiler. That, and
the fact that there are gaps in the programming language that might be easy
to fill.
JB