Problems burning Kickstart

[Toni Wilen]

Originally Posted by xArtx

Do WinUAE ROM files have the same endianness expected on the physical ROM itself?

It depends. There is 2 1M CD32 variants that WinUAE autodetects, one of them is in exact same format as real CD32 ROM (interleaved and swapped), other is deinterleaved and without swapping.

[xArtx]

Hi does that mean there are 2 different physical ROM types?
Because I doubt there are 2 different Amiga ROM busses

I have versions with different printing, one marked MX8100
which is an ordinary EPROM without the window so OTP.
Later, maybe a mask ROM.

[idrougge]

I'm trying to build a (moderately) custom 3.9 Kickstart, but while it does boot, the Workbench never shows up (just an empty screen with Workbench title row). The workbench.library is in the extended ROM part.

So far I have only tried it out using FS-UAE; could it be that it doesn't fully support extended ROMs or 1 MB ROMs?

[Toni Wilen]

Originally Posted by xArtx

Hi does that mean there are 2 different physical ROM types?

No. It only means winuae recognises all common CD32 rom image variants automatically.

[nogginthenog]

@idrougge Do you have the wbfind module? I think it's needed for extended ROMs.

[idrougge]

WBfind? Not WBtask?

[idrougge]

"Version" command returns "Kickstart 45.47, Workbench 40.42".

"LoadWB" (v38.9) returns with "Invalid resident library".

"Version workbench.library" returns "workbench.library 45.127"

[nogginthenog]

Originally Posted by idrougge

WBfind? Not WBtask?

Nope WBfind:
http://www.mfilos.com/2010/12/guide-...kickstart.html

Please note: I've never burnt a KS ROM, but I have in my possession today 10 x 27C400 EPROMs and an EPROM eraser from China :-)

[idrougge]

Nah, that's when you've left workbench.library out of the ROM entirely.

We'll leave outside though Workbench.library which is rather big and can't be left out (can be put in hard drive's LIBS: folder with no problem). You'd should include the WBFind module in your ROM as well as it's a module that tells the system that the Workbench.library exists in SYS:Libs

[utri007]

Leaving workbench.library out of rom, means that you need always a special boot disk with workbenc.library. If you has floppy wich uses system libraries you need to remember to copy workbench.library to it, or program doesn't work. etc.

[idrougge]

Exactly. That's why I've included workbench.library in the extended ROM.

[SnkBitten]

I have a question..

I have the Willem USB programmer GQ-4x4 and ADP-054 adapter but I'm having a world of frustration trying to burn anything.


I have AM27C400-120 EPROMs. I can read ROMs (A4000D stock 3.0 ROMs, a 1MB custom ROM I have for ROMY) and I can write FF or 00 to an EPROM....but I can not write a Kickstart to it. I've used REMUS to make a kickstart that works very well in WinUAE (512KB) and I've used SplitROMImage with SWAP to prepare it for burning. I've copied the file to double it...

copy A4000.hi /B+A4000.hi /B A4000.512.hi /B

and the same for the .lo file.

Attempting to write .hi gives me a "write failed, address=0x000000, Buffer=0x14 Device=0xFF"
**
Attempting to write .lo give me a "write failed, address=0x000000, Buffer=0xF9 Device=0xFF

I get the same error if I read the 1MB ROM to buffer, swap in my EPROM and attempt a write.

I'm assuming the adapter ADP-054 plugs in from the bottom up and the EPROM plugs in to the adapter (the larger slot on the right) from the bottom up as well with the notch towards the top.

Is there a step I'm missing? It's version 7.11 of the GQ USB Programmer. I've attempted on Win10 x64 and Win7 x64 so far. I've even tried using my UV Eraser to erase the blank EPROMs before writing. Blank check reports blank, writing all FFs reports success. Writing a kickstart results in "write failed.........." immediately at the go (click write, progress bar appears, 0%.. "write failed pops up).

Attempting to write a 512KB ROM for my A4000D before writing a 1MB ROM for my A4000T w/ROMY.

[emufan]

mcumall.com forum, someone with kickstart and same eeprom.
dunno offhand, just searched and found that.

others report about write problems, device was sent back to service.

another one "kickstart error" almost same equipment as yours.

[SnkBitten]

Originally Posted by emufan

mcumall.com forum, someone with kickstart and same eeprom.
dunno offhand, just searched and found that.

others report about write problems, device was sent back to service.

another one "kickstart error" almost same equipment as yours.

After reading those and other threads it doesn't look very promising. I'll try erasing the EPROMs for longer next as that seemed to resolve the issue for a few. I think I did mine for 20 minutes and others are saying 50-60 minutes.

[xArtx]

Great. That’s the EPROM burner I was about to buy.
So this is not a good choice then?

[emufan]

it would be good, if we had a flash based kickstart adapter, these seems to be more reliable in the end.
maybe kipper2k once will continue his project, adding an usb connector so one can program it on a peecee.

[nogginthenog]

@SnkBitten - Damn, it looks like I have the same problem. Tried 3 different chips. Even at -2 speed (which seems to get a bit further). Also have a GQ-4x4 and ADP-054.

Write failed, Address=0x001E15, Buffer=0xE0 Device=0x00

Gonna try my eraser. I guess we all have the same cheapo Chinese eraser!

I noticed a problem with a KS 3.0 chip I pulled. Bit 3 is always zero. So instead of FFFF I'm seeing FFF7 (1111111111110111). I used a screwdriver to pull it so maybe I damaged it (cleaned the pins with a pencil eraser though). The partial ROM I burnt does not have this problem. DIL chip puller ordered.

[idrougge]

DIL chip puller is quite useless for chips of this size.

[nogginthenog]

Success! I've programmed 2 EPROMS. 1 was erased (it failed first time), 1 out of the package.
Not 100% sure what is happening yet.

A 3rd EPROM failed twice. Maybe it needs longer in the eraser? Will try some more tests tomorrow.

Also, I successfully programmed a 27256 EPROM (no adapter needed). Don't have any other types of EPROMs to test.

[nogginthenog]

Originally Posted by idrougge

DIL chip puller is quite useless for chips of this size.

Really? Damn. I don't really want to take the A4000 motherboard out of the case. It's a pain! I have 2 though, so I can experiment with my 'lesser' one.