Page 1 of 1
PIC18F14K50 Verification failed
Posted: 19 Jan 2023 08:22
by Hudvel Tristik
Dear,
I'm using EasyPIC v7a and Codegrip ver.1.6.2.
Whenever PIC18F14K50 is installed on the board and a hex file is written, "Verification failed" is displayed in the "Write operation" window. The hex file seems to be written.
Why does the verification fail?
I look forward to hearing from you.
Regards,
Re: PIC18F14K50 Verification failed
Posted: 20 Jan 2023 08:41
by filip
Hi,
Can you please post the detailed photo of the hardware setup and the CODEGRIP/MCU options screenshot ?
Regards,
Filip.
Re: PIC18F14K50 Verification failed
Posted: 20 Jan 2023 16:09
by hexreader
I can confirm that there is indeed an issue with PIC18F14K50 verification using latest Codegrip software/firmware.
Connecting older mikroProg to external debug socket of EasyPIC v7a works perfectly with verify.
On-board Codegrip programmer fails verify with same board configuration and whatever Codegrip settings are chosen.
My conclusion - bug in Codegrip software or firmware
Happy to be proved wrong
Re: PIC18F14K50 Verification failed
Posted: 03 Feb 2023 12:31
by hexreader
I see that there is a new Codegrip firmware version 1.6.3 available today.
Sadly this has not fixed the problem
Re: PIC18F14K50 Verification failed
Posted: 09 Feb 2023 12:15
by IvanJeremic
Hi,
You can disable the verification after write to avoid this issue.
- verify.png (34.61 KiB) Viewed 773 times
I have attached my LED Blinking HEX which works fine for me:
I didn't even turn off the verification after write and it worked, it didn't verify the code but it did write it.
Also what i would like you to do is to Erase your chip, then click Blank and at the end click on Flash.
- erase.png (7.08 KiB) Viewed 773 times
After that click on CONFIG and then on Cell size in the upper right corner.
- config.png (34.42 KiB) Viewed 773 times
Select One Byte and send me the screenshot of what you get.
- one.png (3.01 KiB) Viewed 773 times
- wyg.png (32.94 KiB) Viewed 773 times
Regards,
Ivan.