Hi folks,
Needing to work with 16F628A PIC's, I recently upgraded from the Picall 16PRO v.10 to v.13 and then programmer ceased working properly. (using 16F84A)
I use the Kit 96 unit, which worked very well on v0.10 .
The .hex files are compiled with the MicroEngineering PicBasic Compiler program.
However, v0.13 doesn't get past the first byte when attempting to program - the usual error message "buffer = xxxx, device = 3FFF".
I even tried the latest v.15a but the same result.
I have two identical Kit 96's and both give the same result.
Manual testing in Settings Menu didn't show any problem.
My PC is an IBM 166mHz, Windows 98SE.
I tried using my Windows XP machine but no result there either.
I would like to be able to program 16F628A's, so I need the later versions to do so.
Also, I've tried clean installing the files but still no result.
So, I have reverted to v0.10 to at least be able to work 16F84A's.
Does anyone have any suggestions as to what could be the cause?
Is there a known conflict associated with Win 98SE and the v.013, v015a?
Regards,
kenmac
Needing to work with 16F628A PIC's, I recently upgraded from the Picall 16PRO v.10 to v.13 and then programmer ceased working properly. (using 16F84A)
I use the Kit 96 unit, which worked very well on v0.10 .
The .hex files are compiled with the MicroEngineering PicBasic Compiler program.
However, v0.13 doesn't get past the first byte when attempting to program - the usual error message "buffer = xxxx, device = 3FFF".
I even tried the latest v.15a but the same result.
I have two identical Kit 96's and both give the same result.
Manual testing in Settings Menu didn't show any problem.
My PC is an IBM 166mHz, Windows 98SE.
I tried using my Windows XP machine but no result there either.
I would like to be able to program 16F628A's, so I need the later versions to do so.
Also, I've tried clean installing the files but still no result.
So, I have reverted to v0.10 to at least be able to work 16F84A's.
Does anyone have any suggestions as to what could be the cause?
Is there a known conflict associated with Win 98SE and the v.013, v015a?
Regards,
kenmac