----- Original Message -----
Sent: Wednesday, July 09, 2003 3:19
PM
Subject: RE: Loading a compiled
program; Run UUT
I
did a small piece of script to read and write 32 bit numbers on a 68000
based board (to try and get an encryption table built up)
the CPU is fast enough that by the time the fluke runs the next
instruction, the CPU has already written the 32 bit number and is on the
HERE: BRA HERE loop so I didn;t need to worry about syncronisation between
the two
output is to a PC on the end of the RS232 option
---
DPY-RALLY ENCRYPTION
DPY-+-PRESS
CONT
STOP
WRITE @ 200000 = 23FC
WRITE @ 200004 =
0006
WRITE @ 200006 = 0010
WRITE @ 200008 =
0000
WRITE @ 20000A = 60FE
REG1 = 0
REG2 = FFFF
AUX-
1: LABEL 1
WRITE @ 200002 = REG1
RUN
UUT 200000
READ @ 100000
AUX-$1+
AUX- +
AUX-$E+
READ
@ 100002
AUX- +
AUX-$E
INC REG1
IF REG2 >= REG1 GOTO
1
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