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.&nbsp; <br>
<br>
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?)<br>
<br>
What I wanted to do is look at the commands getting sent from the Fluke
to the pod.&nbsp; (I.E. what gets sent to the pod when the READ @ 7000
command is sent)&nbsp; 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.&nbsp; 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.&nbsp; Real time code
development and debug baby. :-)<br>
<br>
<br>
<div><span class="gmail_quote">On 11/15/05, <b class="gmail_sendername">Tom McClintock</b> &lt;<a href="mailto:tomm@mgcap.com">tomm@mgcap.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Why stay with the POD at all? Why not a USB to CPU adapter cable or<br>something similar?<br><br><br>tm</blockquote></div><br>-Adam<br>====================<br> <a href="http://www.onecircuit.com">http://www.onecircuit.com
</a><br>====================

_______________________________________________
Techtoolslist mailing list
Techtoolslist@flippers.com
http://seven.pairlist.net/mailman/listinfo/techtoolslist