Problems burning Kickstart

[orange]

try with new eproms

[A4000Bear]

I have a TOP3000 programmer that does not verify during programming (it is done at completion) A number of times I get a mismatch, and have found that if I immediately burn the EPROM again, with the same file (of course), and without erasing it, I find it always works the second time.

It's as if a memory location is not programmed properly, and having a second go is enough to properly program the offending bit(s).

It might be worth a try.

[orange]

@A4000Bear

that's because eprom cells are analog devices (you'd know that if you had bothered to read the link in my post)

[kire_online]

Who knows the difference if any of a *.rom and a *.bin file as used in the GQ Universal USB Programmer for GQ-4X device ?

The HEX looks as follows for the *.rom File;

11 14 4E F9 00 F8 00 D2 00 00 FF FF 00 28 00 3F
00 28 00 0A FF FF FF FF 00 41 4D 49 47 41 20 52
4F 4D 20 4F 70 65 72 61 74 69 6E 67 20 53 79 73
...
...


And I can see the ASCI contains some readable strings like "Amiga ROM" etc.

Both are 524,288 bytes and checksum 3b7f1493b27e212830f989f26ca76c02049f09ca

[Jope]

Both should be the same.

[A4000Bear]

Originally Posted by orange

@A4000Bear

that's because eprom cells are analog devices (you'd know that if you had bothered to read the link in my post)

I am very aware of that, it is why I tried a second burn in the first place when I encountered the problem.
I have been using and programming EPROMs for nearly 30 years, so I do know a fair bit about their quirks.

[Jope]

Hehe, seems your reputation didn't precede you this time, A4000Bear. :-)

[kire_online]

Originally Posted by merlinkv

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...

I have the exact same problem with the MX27C4100 chips, fails programming immediately if I try a *.rom file.

If I try to program with all 00, it completes and verifies OK. I'm using the same device and adapter, ie GQ-4X with ADP-054 adapter.

[kire_online]

Just did a read using GQ-4X and the 16bit adapter ADP-054 with some odd results. When I perform a byte-swap it almost looks readable, but not quite, see attached screenshot.

You can make out the bit that says;
AOIGA VOO Opgvaving Wywvgo
It should probably read;
AMIGA ROM Operating System

What's going on here ?

Anyone else using the GQ-4X with ADP-054 ?
I insert the ROM for reading into the right hand ZIF socket, ie the larger one, making sure it's aligned at the bottom pins.

Do I need to set any jumpers ?
Do I have a faulty programmer or adapter ?
I can try reading the A590 ROMs without the adapter and check CRC-32 or Checksum-Unsigned, maybe prove it's not the programmer and might be the adapter ?

[kire_online]

Just checked the CRC32 for the A590 ROMs read using the reader directly, ie no adapter required for these. Turns out the CRC32 matched for both with this info I found on the web;

54A A590/A2091 SCSI boot ROM EVEN 390722-02 6 6 6 6 8192 EVEN | 8BIT e536bbb2
54B A590/A2091 SCSI boot ROM ODD 390721-02 6 6 6 6 8192 ODD | 8BIT c0871d25

To me this suggests that the ADP-054 adapter is doing something wrong, or I'm not using it correctly.

[kire_online]

It appears the ADP-054 might be defective, I've inspected closely and there is a bridged solder joint between pins 16 and 17 on the pins that go into the programmer ZIF socket. To the left of A19 and 5V1, can other check their board in case this is normal ?

[Jope]

Bits 2 and 3 are stuck? Perhaps your ADP-054 is broken.

edit: Ah, seems you found one potential solder bridge already. Check for more..

MCUMall's support is pretty good. I suggest you contact them, as this is not really the place for that.

[merlinkv]

Posted some messages to the MCUmall forums.

http://www.mcumall.com/forum/topic.asp?TOPIC_ID=4333

I have the same problem described by @kire_online but my adapter seems to be OK. No strange bridges or bad soldered points.

As I said, the problems are the same.... I have a big stock of different EPROMs, EEPROMs and many others but..... 24 27C400's for 512kb & 8 27C800's for 1MByte are damaged?

Strange because a lot of users reports the old paralell models works great.

[kire_online]

I've removed the solder bridge and ADP-054 seems to read the kickstart rom correctly and checksum is correct. Now I need to test writing one and see if it works.

Originally Posted by merlinkv

Posted some messages to the MCUmall forums.

http://www.mcumall.com/forum/topic.asp?TOPIC_ID=4333

I have the same problem described by @kire_online but my adapter seems to be OK. No strange bridges or bad soldered points.

As I said, the problems are the same.... I have a big stock of different EPROMs, EEPROMs and many others but..... 24 27C400's for 512kb & 8 27C800's for 1MByte are damaged?

Strange because a lot of users reports the old paralell models works great.

Your adapter is faulty, might be a chip maybe, I managed to find a solder bridge on mine which was causing the problem.

[merlinkv]

Hi to all

Long time without updates.

Well, all my problems solved time a go, just purchasing a new programmer. More expensive, but works great under Win x32 and x64: Wellon VP-490 (former 590).

I don't need any adapter for a lot of devices and I'm using the same EPROMs as before without any problem.

[FOL]

If this helps anyone with an A600.

When updating the modules, dont update the bootmenu module that comes with BB2. As this breaks the A600 keyboard support.

Symptom = Escape, Ctrl, left shift, del refuse to work.

Seems odd they have updated module for A500, A1200 and CD32 but nothing for A600. I tried them all just incase one of the others worked.

[mfilos]

You mean the bootmenu_44.7(A500)?
I always used the bootmenu_44.7(68020) on my A600/A4000 as I don't think that you'll ever run OS3.9 with an 68000 CPU

Iirc, it also didn't show the "Expansion Board Diagnostics" button

[FOL]

Originally Posted by mfilos

You mean the bootmenu_44.7(A500)?
I always used the bootmenu_44.7(68020) on my A600/A4000 as I don't think that you'll ever run OS3.9 with an 68000 CPU

Iirc, it also didn't show the "Expansion Board Diagnostics" button

None worked, they all broke the keyboard.
As soon as I put the original rom one back, it all worked fine.

I too always used 020 version, but it screws up the keyboard.
It even shows issue in WinUAE when setup exactly the same as my A600.

It shows all buttons, but as I say keyboard buttons dont work.

[Arnie]

Hi All,

Got myself a Wellon VP390 and managed to burn a scsi patched kickstart 1.3 on a 27c400.

I would now like to tackle a dual kickstart but I only have 27c160 eproms.

Can I use these chips for a dual kickstart?

Previous attempts have so far failed. All I get is a blank screen on both positions of the switch. (tied to pin 1).

If I later decide to do a quad kickstart, how do you switch between the different kickstarts?

[Jope]

Connect everything together but the CS line. Have your switch connect the CS line of the chip you want to use to the socket.