| T O P I C R E V I E W |
| pquesinb |
Posted - 07/23/2010 : 16:52:24
ZLM,
I'm posting this again in a separate message to be sure you see it, since I had already replied to the original msg to indicate that you had resolved the 18F452 programming problem.
There's still a problem related to this. When verifying the device, I get a "Configuration VerifyFailed" every time.
The config looks ok when I read it back and check the different items but the error still exists.
Thanks for the quick response on the other issue and have a great weekend.
- Phil |
| 33 L A T E S T R E P L I E S (Newest First) |
| ZLM |
Posted - 10/13/2010 : 18:07:19
no. Only GQ-4X supports this chip. |
| Tony2k |
Posted - 10/11/2010 : 06:41:45
It's possible to program PIC18F2550 with willem gq-3x? |
| ZLM |
Posted - 10/08/2010 : 19:57:52
Can you send us your hex file to support@mcumall.com? |
| quark555 |
Posted - 10/08/2010 : 15:42:56
One more thing, I tried to adjust the configuration bits also from GQ USB, but I got the same results.. (I believe that it shoudl work out!!).. |
| quark555 |
Posted - 10/08/2010 : 14:51:13
Hi ZLM,
Sorry I didn't notice that you posted something over here... well...
I found something new related to this issue, when I compile my program using MikroC for PIC18F4550, the configuration bits are not shown properly when I try to program the PIC.
Regarding what I wrote about saving the file, I opened one hex file, then changed the configuration bits, and saved it... when I tried to load it again; the program was only blank...
For now, any idea why hex generated by mikroC for PIC18F4550 is not working properly with this programmer? |
| ZLM |
Posted - 10/05/2010 : 08:27:15
Managed to reproduce the problem on 16F84, and I found the problem only happen when the hex file has incorrect CFG bit data.
So, after load the hex file, click the Configuration tab and see if any CFG bit are blank. All CFG bit should be assigned. It shoule not be a Blank (unsigned bit) when programming the CFG. |
| ZLM |
Posted - 09/30/2010 : 22:22:48
It is nothing to do with frimware 1.40. Looks like software related.
quark555, can you list the exact steps for this error? start from connect the programmer and start the software. If hex file related, then please attached the hex file.
We only can fix the problem if we can reproduce the bug.
|
| phil789 |
Posted - 09/30/2010 : 12:10:35
ZLM i emailed you for the 1.40 firmware but got no reply from you!!!!! |
| quark555 |
Posted - 09/30/2010 : 11:57:35
Hi,
Well, I thought it was my Hex file, but when I tried another Hex coming from Micrichip for PIC18F4550 USB example, it worked once, and then I was getting the same error (Verify Failed) for 10 times...!!!!
I checked the configurations, and it's not really reading everything all the time.. (Like Oscilator information)..
and here is one more thing, I changes the Configurations, I saved the HEX file, and when loaded again it was BLANK!!!!
I tried all updates mentioned here, but still the same thing.. PLZ I need this to work.. I have a project that I need to finish as soon as possible.... |
| phil789 |
Posted - 09/25/2010 : 13:01:29
as i said in this posting i have another 2 programmers! & both of these Verifying... Configuration perfect with out an err i'm not the only one on the forum with an err hex file has been tested without err.... i will email you for 1..40 firmware... |
| ZLM |
Posted - 09/24/2010 : 23:44:51
Unable to reproduce your problem. So, no way to fix.
see:
Ready
H/W Re: GQ-4X Re-1.40
USB Driver Re.1.0
Software Re. 5.03B
< PIC18F2550*DIP28 >
d:\chiptestfiles\pic18f4550.hex.
ID check OK
Erasing...
Elapsed time: 0.23 seconds.
Erase completed.
Blank checking... Code
Elapsed time: 18.11 seconds.
OK
Blank checking... Data
Elapsed time: 0.45 seconds.
OK
Blank checking... User ID
Elapsed time: 0.17 seconds.
OK
Writing... Code
Elapsed time: 30.30 seconds.
Device write completed OK
Writing... Data
Elapsed time: 2.12 seconds.
Device write completed OK
Writing... User ID
Elapsed time: 0.10 seconds.
Device write completed OK
ID check OK
Verifying... Code
OK
Elapsed time: 18.18 seconds.
ID check OK
Verifying... Data
OK
Elapsed time: 0.78 seconds.
ID check OK
Verifying... User ID
OK
Writing... Configuration
Write Completed
Verifying... Configuration
Device is verified
Elapsed time: 3.63 seconds.
So, the problem maybe related to your hex file. |
| phil789 |
Posted - 09/24/2010 : 01:06:28
any news on this as yet! its been some time....
Verifying... Configuration
Configuration VerifyFailed |
| phil789 |
Posted - 08/26/2010 : 05:01:16
ZLM - when will this be fixed.. thanks.
Verifying... Configuration
Configuration VerifyFailed |
| phil789 |
Posted - 08/18/2010 : 23:49:34
Ready
H/W Re: GQ-4X Re-1.30
USB Driver Re.2.0
Software Re. 5.04 Beta
<<PIC18F2550*DIP28>>
ID check OK
Erasing...
Elapsed time: 0.23 seconds.
Erase completed.
ID check OK
Reading... Code
Elapsed time: 18.00 seconds.
Read completed.
ID check OK
Reading... Data
Elapsed time: 0.63 seconds.
Read completed.
ID check OK
Reading... User ID
Elapsed time: 0.14 seconds.
Read completed.
Reading... Configuration
Read completed.
c:\hex code\test\test.hex.
ID check OK
Writing... Code
Elapsed time: 29.79 seconds.
Device write completed OK
ID check OK
Writing... Data
Elapsed time: 2.12 seconds.
Device write completed OK
ID check OK
Writing... User ID
Elapsed time: 0.10 seconds.
Device write completed OK
ID check OK
Verifying... Code
OK
Elapsed time: 18.23 seconds.
ID check OK
Verifying... Data
OK
Elapsed time: 0.84 seconds.
ID check OK
Verifying... User ID
OK
Writing... Configuration
Write Completed
Verifying... Configuration
Configuration VerifyFailed
Elapsed time: 8.42 seconds.
|
| phil789 |
Posted - 08/18/2010 : 23:41:32
Did everything you said!!!
and still get err! my other 2 programmers do everything correct with out any err at all! only my GQ-4X give err!
ID check OK
Verifying... Code
OK
Elapsed time: 18.20 seconds.
ID check OK
Verifying... Data
OK
Elapsed time: 0.84 seconds.
ID check OK
Verifying... User ID
OK
Writing... Configuration
Write Completed
Verifying... Configuration
Configuration VerifyFailed
Elapsed time: 9.63 seconds |
| ZLM |
Posted - 08/18/2010 : 15:49:12
Did you load any hex file before write?
Try following steps:
1. place the chip
2. read
3. load the hex file
4. erase
5. write |
| phil789 |
Posted - 08/18/2010 : 14:41:06
still err on 18f2550 chip
Configuration VerifyFailed
using - GQUSBPrgRe5.04Beta.exe |
| phil789 |
Posted - 08/18/2010 : 14:40:36
D check OK
Writing... Code
Elapsed time: 29.79 seconds.
Device write completed OK
ID check OK
Writing... Data
Elapsed time: 2.12 seconds.
Device write completed OK
ID check OK
Writing... User ID
Elapsed time: 0.10 seconds.
Device write completed OK
ID check OK
Verifying... Code
OK
Elapsed time: 18.20 seconds.
ID check OK
Verifying... Data
OK
Elapsed time: 0.84 seconds.
ID check OK
Verifying... User ID
OK
Writing... Configuration
Write Completed
Verifying... Configuration
Configuration VerifyFailed
Elapsed time: 18.16 seconds. |
| ZLM |
Posted - 08/18/2010 : 06:04:35
Try this version software:
http://www.mcumall.com/download/TrueUSBWillem/GQUSBPrgRe5.04Beta.exe
|
| ZLM |
Posted - 08/17/2010 : 01:16:46
current firmware level for the GQ-3X has no new release. It is nothing to do with this problem. |
| jmiles |
Posted - 07/29/2010 : 18:51:43
quote:
Originally posted by ZLM
There is a new version GQ-4X firmware Re1.40. The Re1.40 only added support to BR9020. It should not affect the PIC chips. If you do not need to support BR9020, then you do not have to change the firmware to Re1.40. Unless you should wait for sometimes to see if it is a stable version.
What's the current firmware level for the GQ-3X? Would it be a possible cause of the 16F688 problem I reported in the other thread? |
| ZLM |
Posted - 07/28/2010 : 14:03:39
There is a new version GQ-4X firmware Re1.40. The Re1.40 only added support to BR9020. It should not affect the PIC chips. If you do not need to support BR9020, then you do not have to change the firmware to Re1.40. Unless you should wait for sometimes to see if it is a stable version. |
| drskeptical |
Posted - 07/28/2010 : 11:55:51
This is interesting.. I am now wondering if my 4X would work ok with my 16F628's if I had V1.30
I have only just bought my 4X and thisproblem with the 628's is my first outing.
I feel sure that my 4X is not faulty. I desperatly do not wan't to return it as I need it.
Andy |
| pquesinb |
Posted - 07/28/2010 : 11:03:38
Interesting... I wonder what changes were made for rev 1.4. Is it worth the trouble to upgrade from 1.30? |
| phil789 |
Posted - 07/28/2010 : 09:48:04
Hi, can ZLM tell me if there is a new 1.4 firmware as mine says 1.30 |
| drskeptical |
Posted - 07/28/2010 : 09:18:04
Hi Phil,
Thank you for information, I have rev 1.4
Using USB 2.0 and software version 5.03b.
This is the information presented when I plug the 4X in and run the software.
Regards
Andy
|
| pquesinb |
Posted - 07/28/2010 : 07:04:56
Doc,
Does your '4X have revision 1.30 of the firmware? If not, then you'll need to talk to ZLM about what you'll need in order to update it.
ZLM,
Thanks for the heads up on the VerifyFailed issue.
Cheers,
- Phil |
| drskeptical |
Posted - 07/28/2010 : 01:46:07
Hi
I have just tried a PIC 18F452 with my GQ-4X I also get the "Configuration Verify Failed" I know this is ok from my other programmer.
Can anyone test for me the pic 16F628?
This has been a bit of a problem for me.
First I get "Unknown device" when I ID the chip, I get "Failed blank check" after "all" has been erased, then when I try to programe the device I get "Verification fail"
I have 10 of these devices all work OK on my old programmers.
When I use a 16F877A all is ok every time with my GQ-4X.
I have ordered some 16F428A devices to test these.
I wonder if it is a problem with 18 pin devices.
|
| phil789 |
Posted - 07/28/2010 : 00:31:53
thank you for a quick reply. :) |
| ZLM |
Posted - 07/27/2010 : 23:19:19
The extra "Configuration VerifyFailed" will be fixed. |
| phil789 |
Posted - 07/27/2010 : 09:15:48
The pic18f2550 also shows Configuration VerifyFailed" every time. i know the Configuration is good as use the file in another programmer and its ok.. |
| ZLM |
Posted - 07/26/2010 : 15:47:35
The VPP should be ON always for all PIC chips.
We will check the software for the "Configuration Verify Failed" message. But it may take a few weeks since it is not the block bug. |
| pquesinb |
Posted - 07/26/2010 : 08:53:07
One more potential concern... the VPP LED comes on while reading/verifying PICs. Is this normal?
- Phil |
