gnupic@linuxhacker.org

I have been using the Warp13a with the tm4  firmware  and the tm4.c 
linux code from
Newfound Electronics for the the 16F628 and 16F876. I have modified it 
for my environment.

Whe attempting to use picp, I observed that the warp13a was slow to 
respond to one of the
picp multi-byte command sequences and split the command into separate 
transmissions.
Now it also works. I wrote a program to capture  the RS232  traffic and 
used it to log the
operation of Windows MP Lab and then compared the  output with the  
capture from picp.
No science or protocol specification, just luck in finding a significant 
difference.

I would like to switch to the 18F series but this current thread is 
causing concern. I don't
want to modify the board, upgarde the software, and spend another three 
months developing
and debugging the Linux utilities to support the device.

Regards,
   George

Rick Mann wrote:

> Actually, as far as the 16f877, I've found picp to work great with the 
> Warp13a.
>
> On Oct 24, 2003, at 10:42, John Rehwinkel wrote:
>
>> Probably not.  I have a Warp13, and it no longer supports the TM4 
>> protocol.
>> I expect they removed this in order to make room for supporting more 
>> types
>> of PIC programming.  Now it only emulates a picstart, but not well 
>> enough
>> for picp to work with it.
>>