Re: [Usbpicprog-technical] win7 testing

[Mark J. <hel...@gm...>]

Hello friends, I've been having some difficulty using the UPP in
Windows 7 32-bit. The software and drivers appear to install and run
correctly, and the UPP firmware can be updated and verified
successfully, but I can not read or write to a target 18LF2553,
16F628, or 16F84A. I'd be happy to test and debug what I can, but
admittedly, C++ is not my forté.

What happens is, when writing a device, programming always stops near
the end of the code block. The hardware freezes with the green and red
LEDs lit, and after about four seconds, the following error is
displayed:

http://img101.imageshack.us/img101/6571/usberror.png

At this point, the UPP must be unplugged, the software "Disconnected",
the UPP reconnected, and the software "Connected" to re-establish
communication. Oddly, "Autodetect" was able to determine every
connected PIC.

For a read example, this is what happens when I tried reading a
working 16F84A. The target "coffee machine" circuit is fully
functional and can be ICSP-updated using my old programmer, a PICALL
from www.picallw.com. UPP correctly identifies the 16F84A and gives no
error reading it, yet returns the following .hex file:

:020000040000FA
:10000000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F00
:10001000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3FF0
:10002000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3FE0
  ... many more lines following this pattern ...
:1001F000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F0F
:10020000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFE
:10021000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3FEE
:1002200000000000000000000000000000000000CE
:1002300000000000000000000000000000000000BE
:1002400000000000000000000000000000000000AE
  ... many more lines, etc ...
:1003100000000000000000000000000000000000DD
:1003200000000000000000000000000000000000CD
:1003300000000000000000000000000000000000BD
:100340000000000000000030003FFF3FFF3FFF3F84
:10035000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3FAD
:10036000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F9D
:10037000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F8D
  ... etc ...
:1006D000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F2A
:1006E000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F1A
:1006F000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F0A
:1007000000000000000000000000000000000000E9
:1007100000000000000000000000000000000000D9
:1007200000000000000000000000000000000000C9
  ... etc ...
:1007D0000000000000000000000000000000000019
:1007E0000000000000000000000000000000000009
:1007F00000000000000000000000000000000000F9
:020000040000FA
:1042000048004F005400200043004F004600460085
:1042100045004500200048004500520045002100AF
:10422000000020004F006E006C007900200031007B
:1042300035002000430065006E007400730020000C
:1042400020000000200020004600520045005300DE
:10425000480020004200520045005700450044003D
:104260002000200000002000200049006E007300A4
:10427000650072007400200043006F0069006E004A
:020000040000FA
:02400E000F00A1
:00000001FF

Note that the EEDATA was read correctly! "HOT COFFEE HERE!,0" etc.
Below is part of the original .hex file for comparison:

:020000040000FA
... legitimate code here ...
:0407E000AE20E32B39
:02400E00F93F78
:1042000048004F005400200043004F004600460085
:1042100045004500200048004500520045002100AF
:10422000000020004F006E006C007900200031007B
:1042300035002000430065006E007400730020000C
:1042400020000000200020004600520045005300DE
:10425000480020004200520045005700450044003D
:104260002000200000002000200049006E007300A4
:10427000650072007400200043006F0069006E004A
:00000001FF

Any ideas? This is using an ICSP cable about 2cm long, and a quality
shielded USB2.0 cable about 2m long. Thanks!

Regards,
Mark