Tony Knerr
Member
Thanks for the fix, Chuck. Is there someone here able and willing to program a pic for me (and others)?
VCF West | Aug 01 - 02 2025, | CHM, Mountain View, CA |
VCF Midwest | Sep 13 - 14 2025, | Schaumburg, IL |
VCF Montreal | Jan 24 - 25, 2026, | RMC Saint Jean, Montreal, Canada |
VCF SoCal | Feb 14 - 15, 2026, | Hotel Fera, Orange CA |
VCF Southwest | May 29 - 31, 2026, | Westin Dallas Fort Worth Airport |
VCF Southeast | June, 2026 | Atlanta, GA |
li think it's time i built myself a couple of these...
I've never had much luck with WinPIC--I use a JDM programmer on an old P3 system running 2K and IC-PROG 1.06B. I guess YMMV.
... Soo, I can't tell if I'm getting the new code in since I can't read them back, and they still work because they may still have 0.93 code in them.
I think my options are buy a batch of new PICs or buy a new programmer. aurgh!
A few diagnostic tools contain keyboard checking functionality. CheckIt is one.Alternately, is there a program that displays onscreen what key is pressed?
Really strange things are happening with AT2XT microcodeI used JDM and IC Prog (1.06B) runing on virtual machine in Core 2 and everything worked fine for progs that i have developed myself with MPLAB. When i tried to flash AT2XT 0.92 with it, it failed in a way described by hargle. Then i have set up Win95 under two Slot-1 PentiumII-233 box and set up direct port access in IC-prog's settings. Using it, i could successfully read and flash AT2XT prog.
Or at least that's my experience with the 12F6x chips. I have successfully overrided this by putting a 9vdc on the MCLR prior to
pluggin the RS232 into the programmer, then unpluggin the 9vdc as soon as I hit the program button, effectively reviving all of my chips.