Jinx wrote:
>> The first method is quite fast, transferring data at a rate up to 30uS 
>> per bit. I use it to transfer 20bits of data + 2 CRC bits, starting w/
>> 2 start bits, for a total of  24 bits. 30uS works if both PICs have a
>> fast clock, slower if 4MHz clock on one PIC.
>>     
>
> I use a PIC RAM sniffer with an LCD using clock/data. Invaluable
> debugger for what's really going on inside the PIC. Every home
> should have one
>
>   
Did you do it yourself? I have a couple of brand-new 4x24 LCD modules 
with backlight.
My plan WAS to use an old DOS PC with a VT52 emulator program running 
and have a tiny PCB pump
out the RAM from Manchester debug code inside the unit being developed. 
Takes about 40 words..
But I like your ICD idea. Hmmm. maybe I could sell a few PCBs and make a 
few USD,
if anyone uses USD anymore, and give away the code...
>> The second method is a memory dump.....
>> ....for even a slow PC to extract and display the information
>>     
>
> I have old DOS boxes around (286/386) that I'd love to put to
> work doing chores like that. When I get around to it that is. The
> sniffer above is OK, but to have all a PIC's RAM and registers
> up on a monitor would be good. It wouldn't be too hard to either
> send it as serial or in through LPT1:
>
>   
I have a wonderful Fujitsu laptop with Win98 (NOT SE) and I use it for 
stuff like that.
But it is limited on size of flash drives, everything. And, alas, it 
CANNOT be updated
(according to Fujitsu). Works for days without coughing in DOS-ONLY 
mode. For  a
while I had Laplink on it but I can't find a cheap program that will 
reliably work on XP
on one end and DOS on the other...


-Bob
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist