| T O P I C R E V I E W |
| pquesinb |
Posted - 12/09/2010 : 11:26:43
Still getting that error message when programming a PIC18F452 with version 6.00 of USBPrg.
- Phil |
| 6 L A T E S T R E P L I E S (Newest First) |
| ZLM |
Posted - 01/08/2011 : 10:30:05
Chip has to be erased and pass the blank check before it can be programmed new data. Otherwise the verify code will fail. |
| PStechPaul |
Posted - 01/05/2011 : 23:15:48
Here are the problems I have had:
I am now getting config verify failures on a PIC16F72 device with a larger program than the other project. However I can read the device and the config seems OK.
I am using MPLAB 8.63 and Intel Hex32 which has last lines:
:02400E00353F3C
:00000001FF
That seems to indicate the address of the config memory is 400E (big-endian) and the data is 353F (big-endian) or 3F35 (little-endian). The address in MPLAB is 2007 and the data is 3F35. Your programmer reads the config correctly as 3F35 in address 2007.
It may be significant that the address 400E is exactly twice the correct address 2007, or in other words the address seems to be shifted by one bit.
I tried changing the hex file as follows:
:02200700353F63
:00000001FF
But it still failed to verify. I read the PIC and saved as hex:
:10200000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE0
:104000003F3F3F3F3F3F3F3FFFFFFFFFFFFFB53FCA
I read the device on the PicStart Plus and the config looked OK at address 2007, but when I exported in hex it showed the config in address 400E.
Now I don’t know what I should trust.
I verified the device as programmed on the GQ-4X, using the PicStart Plus and the original hex file, and it was OK.
And now I verified it using the GQ-4X, and it verified OK. And I also tried again with the GQ-4X and it erased and programmed OK.
I loaded another hex file, wrote to the PIC, and got a verify error:
Verifying... Code
VerifyFailed, Address=0x000004, Device=0x34, Buffer=0x3F
VerifyFailed
I tried the original file again, set speed=3, and got this:
Speed = 3
ID check OK
Writing... Code
Elapsed time: 65.12 seconds.
Device write completed OK
ID check OK
Writing... Data
Elapsed time: 0.30 seconds.
Device write completed OK
ID check OK
Writing... User ID
Elapsed time: 0.30 seconds.
Device write completed OK
ID check OK
Verifying... Code
VerifyFailed, Address=0x000009, Device=0x18, Buffer=0xD8
VerifyFailed
Elapsed time: 7.13 seconds.
I did an erase and write:
Verifying... Configuration
Configuration VerifyFailed
Elapsed time: 62.92 seconds.
Somehow the speed changed back to +2.
I did a double-write erase and program:
Writing... Configuration
Write Completed
Verifying... Configuration
Configuration VerifyFailed
Elapsed time: 9.99 seconds.
I tried to verify the device on the PICstart Plus and it failed in program memory. I erased it and programmed it in about 22 seconds and it verifies OK. Tried another verify on the GQ-4X and it became unresponsive and I shut down the program.
Launched again; had to unplug and reconnect the USB. Tried a verify:
Verifying... User ID
VerifyFailed, Address=0x000000, Device=0x00, Buffer=0x3F
VerifyFailed
Elapsed time: 6.59 seconds.
Back on PICstart Plus, verifies OK. Closed GQ-4X software, switched to other USB port, installed drivers again (?), launched software, same problem:
Verifying... User ID
VerifyFailed, Address=0x000000, Device=0x00, Buffer=0x3F
VerifyFailed
Elapsed time: 3.81 seconds.
I was able to read the device and then do a successful verify, but it fails when I load the hex file.
|
| phil789 |
Posted - 01/05/2011 : 16:44:27
Hi i'm programming the PIC18F2550 with v6.0 and my verify err has gone now! |
| ZLM |
Posted - 01/01/2011 : 12:13:32
hi pquesinb, can you send your hex file to support@mcumall.com? The problem need to be reproduced in order to fix the problem. |
| pquesinb |
Posted - 01/01/2011 : 10:57:23
This error still is not fixed. Which PIC are you programming successfully and are you using a GQ-4X? If so, which version of the firmware does it have?
- Phil |
| phil789 |
Posted - 12/22/2010 : 15:24:34
my err msg has now gone in v6.0 it does what it should.. |
|
|
