Re: [Usbpicprog-technical] upp & pic16f88

[Jasper W. <ja...@po...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 10 Mar 2009, Frans Schreuder wrote:

> Hi Jasper,
> 
> Did the software autodetect the 16F88 as a device?
> I am pretty sure that if it didn't autodetect it, something should be wrong
> with the cable or your breadboard...

Hi,

I've had a chance to look at this again.

My usbpic prog is now programmed with svn version 552 firmware, and i've
using usbpicprog rev 559 on ubuntu 8.10.

usbpicprog corectly identifies 16F88's and a 16F84A. Using the commandline
I can successfully read the 16F84A and reprogram it. If i swap the 16F84A
for a 16F88 the pic programmer appears to be able to read the pic, but the
results are all 1's (i.e. 0xff for data memory, 0xff3f for code memory).

If i try to write to the 16F88 it appears to write correctly (the pic
programmer returns '2' for each chunk written, and 1 when it's done (i added
some debugging)), but when the pic is put into a jdm programmer and read
it's blank.

So it looks as if 16F88's can be neither written or read.

Also if i use the usbpicprog gui it hangs on reading and writing with both
the 16F88 and 16F84A

I need the Hightech C18 compiler to compile the upp firmware? does anyone
have a good link to what needs to be done to get it running under wine?

- -- 
[http://pointless.net/]                                   [0x2ECA0975]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (NetBSD)

iQEVAwUBScFT1ACB+Qwuygl1AQKvzQf/Suk0E36uugl/gDGZETTElDeQeDLcZXZO
+jphk2Dqjnr823EDapH3fqOC68so7gfLZyCZfdokWwhFZa4BKC09+yVQ32z2F9ki
dQvEN+gyte9NYZaVKb5yCmH+QE+mbrfL3T21L/oHvujvRHHSHM6SwnCMnC5zyLPu
pBLt+ElOAIFICKft/sGP2cO5V1mRv4e6E6OsL24ti4pQ7D9sDiXGuQQtDCyRah7J
DeN+FmwRCTpQTUESXmDcCDlVpa67G1VkmYxv2F6KHq2oN6z52WT1JBNTwDEpiGnZ
+PPNuhhzE4foPWENryrg1Op0PX+JIoSCdCAdf65VWWSZASxEEBq11g==
=NHO7
-----END PGP SIGNATURE-----