Whoever designed the pods took the time to understand the functionality of
each respective processor. For example, for processor type ABC, a read
consists of putting the read address on the address in cycle N, then expect
the data in cycle N+1. They then wrote code to support this behavior and
programmed it into the pod, so that when a read command is received from the
Fluke, it performs these functions. For processor XYZ, the read (and thus
POD) behavior would be completely different.
Writing a direct uP USB adapter is certainly possible, but in doing so we
would be reinventing the wheel. (I think some other companies have these?)
What I wanted to do is look at the commands getting sent from the Fluke to
the pod. (I.E. what gets sent to the pod when the READ @ 7000 command is
sent) Once I get a full understanding of the Fluke to POD command interface,
I can then write an ICE (In Circuit Emulator) that supports these pods.
Think about it.. you could write Z80 C or assembly code on your PC, and use
this program to execute it on the native Z80 based system the pod is plugged
into. Real time code development and debug baby. :-)
On 11/15/05, Tom McClintock <tomm@mgcap.com> wrote:
>
> Why stay with the POD at all? Why not a USB to CPU adapter cable or
> something similar?
>
>
> tm
-Adam
====================
http://www.onecircuit.com
====================
_______________________________________________
Techtoolslist mailing list
Techtoolslist@flippers.com
http://seven.pairlist.net/mailman/listinfo/techtoolslist
Received on Wed Nov 16 07:44:26 2005
This archive was generated by hypermail 2.1.8 : Wed Nov 16 2005 - 08:50:01 EST