> >maybe try with the Wisp628 directly in the PC (no cable). 

> Bingo! This was exactly the solution. I attached the Wisp628 
> directly to 
> the serial port and it worked flawlessly with a 16F84A and a 
> 16LF648A. 
> It looks like I was using a defective cable, or maybe it is 
> too long (6 
> Ft)?

A cable of a few *meters* should be no problem if it is reasonable
quality cable. I would still bet there is some wire not connected, or
maybe it is a crossover (0-modem) cable?

> Just a couple of questions: why when I read back any 
> programmed hex file 
> to a chip I get a smaller hex file (few bytes less)?

There is some freedom in how to format a hex file (number of bytes per
line). Also the readback will by default omit words that seem to be
usused ( = in the erased state, 16F code space: value 0x3FF).


> C:\Archivos de Programa\XWisp\serialwin32.py:88: DeprecationWarning: 
> integer arg
> ument expected, got float
>   win32file.SetCommTimeouts(self.hComPort, timeouts)
> Any ideas about the reason I am getting this?

Because Python changed slightly after I wrote this (or rather, after I
grabbed that library).

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 

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