Problems burning Kickstart

[amigamaniac]

Just did a quick google of the KS 3.5. I wouldn't touch it if you have it, apparently it is juts a rubbish fake. I think KS 3.9 has patches applied for OS3.9 or some such thing. And that is a good one I believe.

Nathan

[alexh]

A LONG time ago (talking 1998/9) I made my own KS3.1 EPROMs for an A3000 using 27C400. They didn't work and I didnt have a ROM tower so I used a pair of 27C2048 (might have been 27C220) EPROM's instead and they did work.

I had a very early A3000 (one used to develop Days of Thunder and Birds of Prey at Argonaut!) with KS1.4 ROM's inside.

[amigamaniac]

Yeah, I saw from the close-up photo's in the The Big Book of Amiga Hardware that the A3000 had a different ROM part than the other Amiga's a while back. But then someone assured me it was the same part. And then I saw a ROM tower (before I knew it was called that), and it was obvious it was some sort of adapter. It all makes sense now. Those guys probably have the wrong ROM for use without a ROM tower.

Nathan

[JackTheKnife]

Here is a question from Polish Amiga Forum:

When I burned Kickstart 3.1 and 2.04, the machine didn't start. Instead of picture of flying diskette I had the black screen. I waited for 5 minutes, but no result... But paradox: when I burn Kickstart 1.2-1.3, the machine starts well. I think, that problem goes from additional chip mem. I have revision 6A and 8 chips of ram. I have changed JP7A and JP2. Workbench see RAM well, but when i reset my Amiga, it is Guru Meditation. After click picture appears (Insert Workbench 1.3). I used AT49F040 (70ns) flash chips, program was modifyed. Who can help me?

[Zetr0]

@Jack

that sounds like a dodgy program to me...

rev 6 (check)
70ns access speed (check)
1 MB Chip ram hack.. (check)
ROM failure (*?!)

the 1mb rom hack shouldn't interfere with the rom access at all, well not that I know of, is he sure he is using the RIGHT rom file... I have been caught out a couple of times in my hastyness

[BYTEMAN]

Originally Posted by JackTheKnife

Here is a question from Polish Amiga Forum:

Hello All. I asked for this question. I burned kickstarts 2.04-3.1. ROMs worked correctly on WinUAE. I don't know what is it. ROM 1.3 burned works well. I used KickFlash-500 device.

[Zetr0]

I did have an instance where a 3.1 rom file would work in winuae but not in my A600

[Toni Wilen]

Originally Posted by Zetr0

I did have an instance where a 3.1 rom file would work in winuae but not in my A600

Then it wasn't real 3.1 ROM file for A600

If 100% confirmed ROM image isn't working when burned/flashed to real chips = not a rom image problem. Should be quite obvious

[Zetr0]

@TW

I kinda figured that, I got the image from a dubious source so i put it down to that.

[BYTEMAN]

Originally Posted by Toni Wilen

Then it wasn't real 3.1 ROM file for A600

If 100% confirmed ROM image isn't working when burned/flashed to real chips = not a rom image problem. Should be quite obvious

But if I burn Kick1.2-1.3, Amiga boots well.

[Toni Wilen]

Originally Posted by Sasha

But if I burn Kick1.2-1.3, Amiga boots well.

Upper or lower 256K mapped/programmed incorrectly? (256k<>512k rom)

Note that black screen will also happen if last 16 bytes of ROM are incorrect. (68000/010 Amigas only)

[BYTEMAN]

Originally Posted by Toni Wilen

Upper or lower 256K mapped/programmed incorrectly? (256k<>512k rom)

Note that black screen will also happen if last 16 bytes of ROM are incorrect. (68000/010 Amigas only)

I haven't checked it yet.

There were no errors when image was burnt.

Maybe (I don't know exactly), this problem goes from Chip-ram expansion (8 chips on Rev6 board). When I turn my Amiga on, it boots well, but when I reset, Amiga shows me Guru . (See attachment).

[BYTEMAN]

Yeah, I made it!!! Now my Ami works with kickstart 3.1, but only when JP2 is in lower position (512 chip and 512 slow mem).

There (http://zx.pk.ru/showthread.php?p=172456) are modifyed versions of Kickflash progs. Additions: verifing, keys at start, write procedures for AT49F040

[Damion]

Anyone had luck with the TOP2048 or easypro?

I've had nothing but problems with my Willem. I can read ROM contents no problem, and the dumps work fine with WinUAE. However, I can't get it to write... the thing just b0rks the first bytes of the EPROM, then craps out. I've tried every manner of jumpers, software, external PSUs, io drivers, parallel port bios settings, 10 different chips, 4 different computers, etc etc... The only thing I haven't tried is an old computer or laptop running Win98. I thought I was losing it, until I read this quote from Toni Wilen:

Note that Willem isn't trouble free either. For example I can only program EPROMs if Willem is connected to laptop on docking station (that includes parallel port, no parport on laptop itself)

Other PCs (and other laptops I found) only program few bytes and then it aborts with an error.. Laptop works 100% perfectly :-) (Parallel port bios settings have no effect)

One more question - is it possible I'm not erasing my chips long enough? I usually go just a few minutes at a time, until they pass blank check. I'm wondering if it's possible they could pass blank check, yet still not be wiped enough... yet, the consistency of how the Willem fails writing makes me think it's something with the Willem (or its software)... and since I can't be arsed to install Win98 on something, I think it's time to try another programmer. :/ Easypro seems to get some decent reviews.

[prowler]

Originally Posted by Damion

One more question - is it possible I'm not erasing my chips long enough? I usually go just a few minutes at a time, until they pass blank check. I'm wondering if it's possible they could pass blank check, yet still not be wiped enough...

Hi Damion,

Have you tried dumping the ROMs as a sure way of checking if they are blank? Just a long shot... I also think it far more likely that the Willem is the culprit.

prowler

[Damion]

Originally Posted by prowler

Hi Damion,

Have you tried dumping the ROMs as a sure way of checking if they are blank? Just a long shot... I also think it far more likely that the Willem is the culprit.

prowler

Hey prowler,

I'm going to double check, I may also separate a few chips and give them an extra few minutes after passing blank check. Also ordered some more chips from a different manufacturer to play with.

I've found quite a few threads on other forums about this exact issue with the Willem. Seems you have a lucky hardware combo if it writes 27Cxxx. :/

[Toni Wilen]

Originally Posted by Damion

Anyone had luck with the TOP2048 or easypro?

No, I have Wellon VP-380 which works perfectly and is fast. I guess all cheap chinese eprommers or more or less similar

However, I can't get it to write... the thing just b0rks the first bytes of the EPROM, then craps out.

This is the exact same problem I had. It wrote 1 to 1000 bytes and fails with an error (and last failed byte is wrong, one or more bits that should have been left at one have been cleared).

ONLY working PC is a HP laptop(!) on a docking station (which includes parallel port). "Standard" 8-bit EPROMs work fine.

[Chain]

willem stops programming if he found eeprom isnt erased.
always use blank check before programming
and give them 20 minutes in uv eraser

[Toni Wilen]

Originally Posted by Chain

willem stops programming if he found eeprom isnt erased.
always use blank check before programming
and give them 20 minutes in uv eraser

"ok. I didn't know they need to be erased first!!11"

[Damion]

Originally Posted by Toni Wilen

No, I have Wellon VP-380 which works perfectly and is fast. I guess all cheap chinese eprommers or more or less similar

Awesome, I think I'll pick up a VP380 and end the headache.

This is the exact same problem I had. It wrote 1 to 1000 bytes and fails with an error (and last failed byte is wrong, one or more bits that should have been left at one have been cleared).

ONLY working PC is a HP laptop(!) on a docking station (which includes parallel port). "Standard" 8-bit EPROMs work fine.

Wild. I tried 4 PCs, and was about to install Win98 on an old Compaq iPaq before having enough.


@chain

All EPROMs pass blank check OK. I am going to give it another go with the Hitachi parts though, just for kicks. So far no luck with the AMD and Macronix chips.