| T O P I C R E V I E W |
| LMQT |
Posted - 10/22/2006 : 08:59:55
Hi,
I can't write on my Atmel AT28C256 
Dipswitches are correctly setting, chip is well selected in the list, but the board can't writing on the chip.
But strangely, it can erase my chips 
My AT28c256 work well on my old Willem Enhanced, so I'm sure the chips are OK.
Appart from my AT28C256, the board GQ-2X works well with many other EPROMs, so the board is OK too.
Anyone has an idea ? |
| 16 L A T E S T R E P L I E S (Newest First) |
| LMQT |
Posted - 11/07/2006 : 10:31:34
v1.07b works perfectly, you're a chief 
Thanks a lot for your reactivity  |
| ZLM |
Posted - 11/05/2006 : 16:45:54
There is a DIP setting error been fixed in 1.07B. (the DIP 10 should be OFF).
The 1.07B is ready for downloading. |
| Danny11 |
Posted - 11/05/2006 : 13:02:36
1.07A worked for 28c256 previous ver. would fail.
Using XP SP1
Ds |
| ZLM |
Posted - 11/04/2006 : 05:30:53
Can you download again? |
| LMQT |
Posted - 11/03/2006 : 13:58:36
Failed immediatly at speed "+2"
Failed in the first 100 bits at speed "+1"
Sometimes failed at speed "0" (5 minutes by writing)
=> it's worth than the beta |
| ZLM |
Posted - 11/03/2006 : 04:34:40
Try Re.1.07. |
| LMQT |
Posted - 11/01/2006 : 03:18:30
Hi,
Some news for the slowness ?  |
| LMQT |
Posted - 10/25/2006 : 09:20:41
quote:
Originally posted by LMQT
v1.07 don't work better :(
- It is more more long : 3 seconds by percent.
- There is no more error just at the begining, but there is one somewhere further.
- No more data was written than the 1.06 (even at addresses before the error of course)
Any other idea mcumall ? :))
Thanks for this try anyway ;)
Edit : after two pass of erasing for the AT28c256, the write operation was successfull 
A second one also !!
So, there is juste the problem of the extreme slowness to solve now (if it is possible) 
Thanks again. |
| LMQT |
Posted - 10/25/2006 : 09:13:35
v1.07 don't work better :(
- It is more more long : 3 seconds by percent.
- There is no more error just at the begining, but there is one somewhere further.
- No more data was written than the 1.06 (even at addresses before the error of course)
Any other idea mcumall ? :))
Thanks for this try anyway ;) |
| ZLM |
Posted - 10/24/2006 : 10:38:43
The full change log will be released once finished the beta test.
Basically fixed some bugs and added new devices to the supported list.
Such as:
-fixed Ctrl+U crash
-fixed PIC CFG read crash
-modified 28C256 flash algorithm
-... and more
|
| dkedrowitsch |
Posted - 10/24/2006 : 06:13:23
Do you have any type of changelog for this Beta so I can see what has been changed/fixed since 1.06.
On first glance I do notice we can resize the window now, but the default size is still maybe 10x10 pixels too small.
|
| ZLM |
Posted - 10/24/2006 : 00:47:41
Would you please download the Re1.07 Beta for tesing?
From: http://www.mcumall.com/download/TrueUSBWillem/TrueUSBWillemGQ-2X1.07BetaSetup.exe
Let me know if it works. |
| mcumall |
Posted - 10/23/2006 : 15:28:24
Well, this looks like something wrong with the write process. We need look the code again. |
| mcumall |
Posted - 10/23/2006 : 11:59:27
We may already know what's exactly happened here.
The error message "Device write failed at address: 0x000000, Buffer=0x65 Device=0x65" showed the device first byte is already write correctly. But it failed on verify process.
The current write algorithm used byte mode to write. The write algorithm has build in verification step after each byte write. If the write mode and verification mode switching speed is faster than chip's speed, the verification will fail. The speed seems not controlled the switching mode here.
EZoSat, would you please confirm that the first byte been write correctly? If this is the case, then it can be easily fixed.
|
| LMQT |
Posted - 10/22/2006 : 22:29:36
ZLM : yes I try to change the speed also, but with no effect at all.
EZoSat : effectively "write failed at address : 0x00 ....."
Will this chip be supported in the next releases ? |
| ZLM |
Posted - 10/22/2006 : 10:50:15
Did you change the speed and try?
Does it read the chip correctly?
What is the exact error when write? |
