Problems burning Kickstart - Page 25

Jope · 14 November 2011, 07:45

Quote:

Originally Posted by merlinkv

At this step everything seems to be OK, but when I try to write the EPROM's all times I receive and error (offset image-device) and the process stops. Also I saved the buffer in .bin format and reloaded into the buffer... the same error. Byte swap has no changes: Error....

Then I need to re-erase the EPROM's.......

Anyone can help me?

Thanks

Can you see the correct Vpp in the status window of the GQUSB software vs. what is writen in your EPROM's datasheet? Did you connect additional power to the prommer? Try burning at -2 speed?

merlinkv · 14 November 2011, 08:07

@Jope

Hi mate

Status windows & tests appears to be OK.

I will try this evening with AC power & -2 speed.

Thanks a lot.

More info soon....

Jope · 14 November 2011, 08:56

Status window and tests? There is no automatic test for the Vpp in EPROMs. You can only verify this yourself from the datasheet of the exact chip you are trying to program.

merlinkv · 14 November 2011, 09:09

Yes you're right.

I'm explained bad. I made the GQ-X4 programmer Vpp test, not the EPROM Vpp.

I don't have the EPROM datasheets, but they are AMD / AM27C400-120 (-50, -100) / 1991

I tought these are the good ones, right?

I'm testing with the -120 ......

Quote:

Originally Posted by Jope

Status window and tests? There is no automatic test for the Vpp in EPROMs. You can only verify this yourself from the datasheet of the exact chip you are trying to program.

Jope · 14 November 2011, 09:27

Quote:

Originally Posted by merlinkv

I don't have the EPROM datasheets, but they are AMD / AM27C400-120 (-50, -100) / 1991

It's so easy: https://www.google.com/search?btnG=1...c400+datasheet

Quote:

I tought these are the good ones, right?

They are suitable, yes.

Once you've verified that they are being programmed with the right voltage and they still don't hold the bits in, then they have probably been over-erased and cannot be programmed any more. Unfortunately in this case the only thing you can do is see if you can return them and get a refund from the seller.

merlinkv · 14 November 2011, 09:38

@Jope

Thanks for the info.

As I said, I will try again this evening with AC power at -2 speed....

tomse · 14 November 2011, 10:12

what are the error messages that you get ?

the eproms could be from a bad batch, so they are defective.

don't forget to let the willem programmer settle before starting.
which means, start the application, click somewhere in the interface, and wait 2 min before inserting the eprom.

Jope · 14 November 2011, 12:33

Quote:

Originally Posted by tomse

what are the error messages that you get ?

The error message is that there is a mismatch between the buffer and what got written to the chip.

Quote:

Originally Posted by merlinkv

At this step everything seems to be OK, but when I try to write the EPROM's all times I receive and error (offset image-device) and the process stops.

The original poster didn't specify the error word for word, but I recognised it because I also own one of these GQ Willems and have experienced similar troubles.

Quote:

the eproms could be from a bad batch, so they are defective.

This is also my conclusion. Did you read the last page before hitting reply?

Quote:

don't forget to let the willem programmer settle before starting.
which means, start the application, click somewhere in the interface, and wait 2 min before inserting the eprom.

Interesting if true.

Is that advice valid for the MCUMall.com GQ series of prommers that we're discussing?

These don't use the normal Willem software and I personally have never felt the need to wait for it to settle.

tomse · 14 November 2011, 14:41

Quote:

Originally Posted by Jope

This is also my conclusion. Did you read the last page before hitting reply?

I see I was skipping to next post alittle early.

Quote:

Originally Posted by Jope

Interesting if true.

Is that advice valid for the MCUMall.com GQ series of prommers that we're discussing?

These don't use the normal Willem software and I personally have never felt the need to wait for it to settle.

It's meant for the original Parallel programmer, but afaik the usb version
is a modified version of the same and has a usb controller instead of the parallel port.
so yes :-)

if you feel like it, you can try and program an eprom with pure zero's
this will program all cells (when erased, all bits are 1)

merlinkv · 14 November 2011, 15:53

Hi again,

Blank Check: OK

Writing 27C400's with 00.... 100% OK

But writing any rom/bin image to 27C400's.... stops at the first bytes...

Jope · 14 November 2011, 16:30

Quote:

Originally Posted by tomse

if you feel like it, you can try and program an eprom with pure zero's
this will program all cells (when erased, all bits are 1)

I think I'll give it a go, I have a parallel willem too, so I can program the same chip and see how it goes.

Very curious behaviour though, however I'm not surprised in the least.. I remember having quite a bit of trouble with the parallel one. :-)

merlinkv · 14 November 2011, 20:41

Hi,

I made another more test,

Readed one original KS 2.05....

COMMODORE-AMIGA
391304-02 047
1992 V2-05 37-350
9238XD001

... in the programmer as 27C400. Yes I know is not compatible but the programmer as readed the data from the original KS (not usable, of course).

- I saved the buffer as bin
- Inserted blank EPROM 27C400
- Write/Verify buffer to the EPROM with 100% success

So, I tought the programmer works fine and can program the 27C400's......

Maybe is needed any special config for the Amiga .rom images?

Any idea?

Thanks

Jope · 15 November 2011, 08:30

Did you try to burn the same chip every time?

merlinkv · 15 November 2011, 08:38

Quote:

Originally Posted by Jope

Did you try to burn the same chip every time?

Nope, I've made tests with 12 chips (two or three times each)......

Jope · 15 November 2011, 09:46

At least you found one working unit. :-)

Be careful when erasing, do it in 5min bursts and then blank check and put it back if it's not blank yet. EPROMs are easily ruined if you over-expose them to UV.

orange · 16 November 2011, 10:55

I also think his eprom is worn out/overexposed. its unusable now.
5min might also be too much, have a look here:
http://wiki.xtronics.com/index.php/How_EPROMS_Work

kire_online · 16 November 2011, 11:35

Tried mx27c4100 c10 on GQ-4X via USB and no power adapter, two different chips, same error, I'm using the ADP-054 adapter, the chip is inserted correctly at bottom of the larger zif socket and verified blank before programming.
After failed write the following reads back from both chips;

11 10 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
...
...

Ready
H/W Re: GQ-4X Re-1.40
USB Driver Re.1.0
Software Re. 6.13
Checking new software on server...
<<MX27C4100>>
Put chip in 42 pin socket and bottom aligned with the socket.
This software is updated already.
ID check skipped
Writing... Code
Elapsed time: 0.26 seconds.
Write failed, Address=0x000001, Buffer=0x14 Device=0x10
Write failed
ID check skipped
Writing... Code
Elapsed time: 0.26 seconds.
Write failed, Address=0x000001, Buffer=0x14 Device=0x10
Write failed
ID check skipped
Blank checking... Code
Elapsed time: 3.31 seconds.
Chip is blank
c:\users\admin\desktop\my_kickstart_31_r40_63.rom.
ID check skipped
Writing... Code
Elapsed time: 0.26 seconds.
Write failed, Address=0x000001, Buffer=0x14 Device=0x10
Write failed
ID check skipped
Reading... Code
Elapsed time: 3.32 seconds.
Read completed.

orange · 16 November 2011, 12:05

one thing that might help a bit, is increasing time delays (iirc, there are two sliders in willem), and trying again and again. I managed to write one eprom that way. but it can't be erased now.

kire_online · 16 November 2011, 20:58

Quote:

Originally Posted by merlinkv

Nope, I've made tests with 12 chips (two or three times each)......

Saw your post on the MCUmall forums, same problem I'm having with the MX27C4100 C-10, no idea what's going on.
Can you provide the log window text output, I'd like to compare USB Driver Version etc.
Also provide the HEX values after reading back a failed write to compare to mine.

kire_online · 17 November 2011, 06:18

I suspect it's the difference between the *.rom file and *.bin file

14 November 2011, 20:41	#492
merlinkv Amiga user since 1989 Join Date: Nov 2009 Location: Spain Age: 60 Posts: 119	Hi, I made another more test, Readed one original KS 2.05.... COMMODORE-AMIGA 391304-02 047 1992 V2-05 37-350 9238XD001 ... in the programmer as 27C400. Yes I know is not compatible but the programmer as readed the data from the original KS (not usable, of course). - I saved the buffer as bin - Inserted blank EPROM 27C400 - Write/Verify buffer to the EPROM with 100% success So, I tought the programmer works fine and can program the 27C400's...... Maybe is needed any special config for the Amiga .rom images? Any idea? Thanks Last edited by merlinkv; 15 November 2011 at 05:33.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Problems with 3.1 kickstart in WHDload	zap64uk	project.WHDLoad	7	30 March 2010 00:23
Burning Kickstart Roms	clueless	Hardware mods	8	06 January 2010 13:31
Kickstart problems...	asm1	project.WHDLoad	2	14 March 2009 15:29
Problems with Kickstart 3.1 [was: various posts in a thread in News]	ARTHUR071169	project.GameBase Amiga	33	15 October 2006 13:33
Kickstart 3.1 problems	adgloride	support.Hardware	5	08 June 2004 03:57

14 November 2011, 08:07	#482
merlinkv Amiga user since 1989 Join Date: Nov 2009 Location: Spain Age: 60 Posts: 119	@Jope Hi mate Status windows & tests appears to be OK. I will try this evening with AC power & -2 speed. Thanks a lot. More info soon....

14 November 2011, 08:56	#483
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,925	Status window and tests? There is no automatic test for the Vpp in EPROMs. You can only verify this yourself from the datasheet of the exact chip you are trying to program.

14 November 2011, 09:38	#486
merlinkv Amiga user since 1989 Join Date: Nov 2009 Location: Spain Age: 60 Posts: 119	@Jope Thanks for the info. As I said, I will try again this evening with AC power at -2 speed....

14 November 2011, 10:12	#487
tomse We need more scans! Join Date: Feb 2010 Location: Copenhagen / Denmark Age: 49 Posts: 326	what are the error messages that you get ? the eproms could be from a bad batch, so they are defective. don't forget to let the willem programmer settle before starting. which means, start the application, click somewhere in the interface, and wait 2 min before inserting the eprom.

14 November 2011, 15:53	#490
merlinkv Amiga user since 1989 Join Date: Nov 2009 Location: Spain Age: 60 Posts: 119	Hi again, Blank Check: OK Writing 27C400's with 00.... 100% OK But writing any rom/bin image to 27C400's.... stops at the first bytes...

15 November 2011, 08:30	#493
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,925	Did you try to burn the same chip every time?

15 November 2011, 09:46	#495
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,925	At least you found one working unit. :-) Be careful when erasing, do it in 5min bursts and then blank check and put it back if it's not blank yet. EPROMs are easily ruined if you over-expose them to UV.

16 November 2011, 10:55	#496
orange Registered User Join Date: Apr 2007 Location: Belgrade Posts: 567	I also think his eprom is worn out/overexposed. its unusable now. 5min might also be too much, have a look here: http://wiki.xtronics.com/index.php/How_EPROMS_Work

16 November 2011, 11:35	#497
kire_online Registered User Join Date: Oct 2011 Location: Sydney Posts: 119	Tried mx27c4100 c10 on GQ-4X via USB and no power adapter, two different chips, same error, I'm using the ADP-054 adapter, the chip is inserted correctly at bottom of the larger zif socket and verified blank before programming. After failed write the following reads back from both chips; 11 10 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ... ... Ready H/W Re: GQ-4X Re-1.40 USB Driver Re.1.0 Software Re. 6.13 Checking new software on server... <<MX27C4100>> Put chip in 42 pin socket and bottom aligned with the socket. This software is updated already. ID check skipped Writing... Code Elapsed time: 0.26 seconds. Write failed, Address=0x000001, Buffer=0x14 Device=0x10 Write failed ID check skipped Writing... Code Elapsed time: 0.26 seconds. Write failed, Address=0x000001, Buffer=0x14 Device=0x10 Write failed ID check skipped Blank checking... Code Elapsed time: 3.31 seconds. Chip is blank c:\users\admin\desktop\my_kickstart_31_r40_63.rom. ID check skipped Writing... Code Elapsed time: 0.26 seconds. Write failed, Address=0x000001, Buffer=0x14 Device=0x10 Write failed ID check skipped Reading... Code Elapsed time: 3.32 seconds. Read completed.

16 November 2011, 12:05	#498
orange Registered User Join Date: Apr 2007 Location: Belgrade Posts: 567	one thing that might help a bit, is increasing time delays (iirc, there are two sliders in willem), and trying again and again. I managed to write one eprom that way. but it can't be erased now.

17 November 2011, 06:18	#500
kire_online Registered User Join Date: Oct 2011 Location: Sydney Posts: 119	I suspect it's the difference between the .rom file and .bin file

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)