Problems burning Kickstart

[alexh]

Ok, so I'm refurbishing 3 A4000D's all with KS3.0 ROM's so I figured I'd burn some KS3.x ROMs

So I start with the base v40.068 KS3.1 ROM and then use RomSplit & Remus to apply the ROM patches from BoingBag #2. I want to add the newer scsi.device v43.45

What other things should I look to add?

I'm limited to 512Kbytes with it being an A4000.

I know almost nothing about the work done on exec etc.

[Mad-Matt]

There are some os39 updates since bb2. including :-
console.device 44.10 from 44.8
filesystem 45.16 from 45.13 (ffs)
shell 45.27 from 45.7

if having to remove workbench.lib to make room, the wbfind from A4000T 40.70 rom may be useful. (Workbench.lib in libs will be used)

mathieeesingbas.lib from A3000 40.68 rom may be useful for space too if the A4000 will always have an fpu. (no integer only option).

I also added Intuition.lib patched for powerwindows (part of romsplit).

[FOL]

Originally Posted by alexh

Ok, so I'm refurbishing 3 A4000D's all with KS3.0 ROM's so I figured I'd burn some KS3.x ROMs

So I start with the base v40.068 KS3.1 ROM and then use RomSplit & Remus to apply the ROM patches from BoingBag #2. I want to add the newer scsi.device v43.45

What other things should I look to add?

I'm limited to 512Kbytes with it being an A4000.

I know almost nothing about the work done on exec etc.

I normally do it in order, 3.1, 3.9 BB1, then BB2, then BB3, then BB4.
Obviously as your limited on space, pick the best sutff out, .

Be awesome to be able to compress stuff inthe rom, so you can get more i there, .

[mfilos]

For A4000 I made the following changes to the Kickstart...

- Exec 45.24 (instead of 40.10)   -->    OS3.9 BB4
- BootMenu 44.7 68020 (instead of 40.5)   -->    OS3.9 BB2
- Console.device 44.10 (instead of 40.2)   -->    OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47)   -->    OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1)   -->    OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1)   -->    OS3.9 BB4
- Icon.library 46.4.209 (instead of 40.1)   -->    OS3.9 BB4
- Misc.resource 37.2 (instead of 37.1)   -->    OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4)   -->    OS3.9 BB3
- Ramlib 40.3 (instead of 40.2)   -->    OS3.9 BB4
- SCSI.device 44.2 (instead of 40.5)   -->    OS3.9 BB3
- Shell 45.27 (instead of 40.2)   -->    OS3.9 BB3
- Trackdisk.device 40.2 (instead of 40.1)   -->    OS3.9 BB4

You only need to have Workbench.library 45.131 from BB3 put into LIBS: since it doesn't fit inside.
Sadly since the space is so limited you can't put much more stuff (like Cosmos KingCON-Handler or Graphics.library)

I'm also attaching you the Remus project file for you to take a look with an editor (change the paths accordingly if you wanna use it as a template for your own ROM).

[alexh]

Thanks for the info everyone

The wbfind thing... what is that about?

Does the A3000 mathieeesingbas.lib save space? I may well have to research that. A4000D-CR will always have an FPU as like A3000 it's on the motherboard.

[Mad-Matt]

Yeah the A3000 mathieeesingbas.lib is fpu only so its a little smaller then the versions in other kickstarts. not by much, but it helps

wbfind was in the A4000T rom because workbench.lib was no longer in rom but in libs:
it may be useful to have for compatability if you need to remove workbench.lib to make space for other os39 lib updates.

icon.lib can be left out for space too as os39 setpatch will load it from libs: , but I leave the original os3.1 version in rom as its small and keeps compatability.

[A4000Bear]

I have been attempting to create 3.9 ROMS for my A4000D using Remus & ROMsplit, and have failed miserably every time. The Amiga shows no sign of life at all with the burnt ROMs installed.

In an effort to isolate the problem, I then tried to simply copy the contents of my existing 3.1 ROMs, again using Remus and ROMsplit. Again no luck.

I then took the 3.1 ROMs from my Amiga and copied them directly. This worked, so the EPROMS and burner I'm using are confirmed as working.

This is what I'm using:
ROMS: MX27C4100-10
Burner: TOP3000
ROMsplit version: 1.0rc15
Remus version: 1.0rc35

The settings in Remus are as follows:
ROMbase = $F80000
ROMsize = 512K
Image type = Split & swapped
Checksum = yes

Briefly, this is what I'm doing (when trying to simply copy 3.1 to new ROMS):
Using ROMsplit, I click on 'Grab ROM', then 'Select All' then 'Extract Files'
The contents of the Kickstart are then saved successfully.

Using Remus, I select where the ROM contents were previously saved. The various files from the ROM are displayed in the right window. I doubleclick on each of them to copy them to the left window. Using the settings shown above, I then click on 'Compile' and I provide a filename. The LO and HI files save successfully.

These are then burnt onto properly erased EPROMS, and they compare OK with the original files. But when I put them in my A4000, they do not work at all. They also do not compare with 'real 3.1 ROMS', though the ASCII data display in the programmer looks superficially the same. Note that I am not attempting to make 3.9 ROMS for this test, merely creating 3.1 ROMS.

I have attached the rpf file generated from Remus from when I was testing. See below.

Given there are lots of people out there who have successfully created A4000 ROMS, I'm sure someone could point me in the right direction.

Thanks
David

[mfilos]

As I see the whole procedure you're doing everything right.
My only difference is that I user NORMAL instead of Split & Swapped and also choose Speed ROM as well.

In the end upon compile I had the kick.rom file (512kb).
Then you can use the SplitROMImage command inside tools with the following declaration:
1> cd Remus/Tools
1> SplitROMImage RAM:kick.rom SWAP

That will give you an 0 as output and you'll see that you're gonna have 2 files HI and LO as well that you'll be burning to your programmer.

Only thing I don't know... if the MX27C4100-10 EPROMS you're using are compatible with 27C400 ones (they can be the same but I don't for sure).
Also are you sure you haven't putted them opposite way (I mean the Hi in Lo's position physical in the socket)?

[A4000Bear]

Originally Posted by mfilos

As I see the whole procedure you're doing everything right.
My only difference is that I user NORMAL instead of Split & Swapped and also choose Speed ROM as well.

In the end upon compile I had the kick.rom file (512kb).
Then you can use the SplitROMImage command inside tools with the following declaration:
1> cd Remus/Tools
1> SplitROMImage RAM:kick.rom SWAP

That will give you an 0 as output and you'll see that you're gonna have 2 files HI and LO as well that you'll be burning to your programmer.

Only thing I don't know... if the MX27C4100-10 EPROMS you're using are compatible with 27C400 ones (they can be the same but I don't for sure).
Also are you sure you haven't putted them opposite way (I mean the Hi in Lo's position physical in the socket)?

Thanks, Mfilos, I'll give your suggestion a try.

The MX27C4100 EPROMS do have the same pinout as the 27C400, and in fact, I have seen genuine Kickstart ROMs using the MX27C4100. In any case I did try copying the original kickstarts directly to the MX27C4100 EPROMs, and they worked fine.

I found that the 'LO' chip corresponds to U175 and the 'HI' chip corresponds to U176. I did try them in the alternate sockets, just in case, but there was no difference.


*** UPDATE ***
I just tried your suggestion, Mfilos, but the ROMs still don't work.

[orange]

nope, MX27C4100 is different from MX27C400. it's a common mistake since former is so easier to obtain.

[alexh]

Originally Posted by orange

nope, MX27C4100 is different from MX27C400.

Pretty sure there is no such thing as an MX27C400.

The MX27C4100 _IS_ Macronix's 27C400 EPROM.

The datasheets show that the MX27C4100DC-10 is pin compatible with other 27C400 devices such as the Atmel AT27C400 and the ST M27C400.

They should work fine with Amiga.

I've got 10's of them so I'll try one soon. (But I shouldn't need to as there are discussions everywhere of people using MX27C4100DC-10 with Amiga with no issues)

[orange]

ah, well I was wrong, mistook it for '27C4001-100'

@A4000Bear
iirc, there is a jumper for setting ROM speed in A4000, have you tried that?

[Cosmos]

@orange

Yes, put it on 160ns !

[A4000Bear]

Originally Posted by orange

ah, well I was wrong, mistook it for '27C4001-100'

@A4000Bear
iirc, there is a jumper for setting ROM speed in A4000, have you tried that?

Yes I have, thanks.

In any case, I have decided to give my attempts at updating the A4000 ROM a break, and I am now working on updating my A2000. I'm having much more success here, and basically all I need to do now is to finalise and tweak what I want to include.

Once I have done that, I'll try the A4000 again.

[Pacemaker]

Hi

I want to buy a Willem programmer. But I don't know with which adapter.
I want to burn a patched kick for my A1200. Could you help me to figure out the right adapter?

Thanks

[Jope]

The right adapter is the one that can accept 27c400 or 27c4100 chips.

[A4000Bear]

Finally got back to trying to make a Kickstart ROM for an A4000 and have had some success.

There is a possible compatibility problem I have found with the new Exec 45.25 and my A4000D with a Macrosystems Warp Engine. With the Warp Engine jumpered so that the SCSI autoboot is OFF, everything is fine. The kickstart screen comes up, and the machine will boot from a floppy. It also works well with a standard Commodore 030 card and IDE drives.

But if the Warp Engine's SCSI autoboot is ON, the machine constantly cycles between a very dark grey and black screen.

Everything works fine when I create the same kickstart, but using Exec 45.20, from OS3.9.



Any suggestions?

[mfilos]

I had exactly the same issue with my BPPC's SCSI.
With exec 45.20 from BB2 no issues while with 45.25.02 (previous version since now the latest is 45.25.15) I had this Black screen reboots.

http://eab.abime.net/showthread.php?p=763436#post763436

Haven't tried yet the latest 45.25.15 version of exec.library due to no time, but will and report back in the related thread.

[A4000Bear]

Originally Posted by mfilos

Haven't tried yet the latest 45.25.15 version of exec.library due to no time, but will and report back in the related thread.

I just tried it with the Warp Engine mentioned previously and the new 45.25.15 exec. Still the same as before, where it's OK when SCSI autoboot disabled, but repeated cycling of dark grey and black sceeens when SCSI is on.

[merlinkv]

Hi to all,

Just received my new stuff to make my own EPROM's:

- Willem True USB Programmer GQ-X4
- ADP-054 16 Bit EPROM 40/42 pin ZIF adapter
- Some AMD 27C400's & 27C800's with speeds from 50 to 120ns
- UV eraser

My steps:

- Installed drivers & soft: OK
- Selected the 27C400
- Inserted EPROM in the 42 pins ZIF socket in the correct way
- Check if EPROM is Blank: OK
- Loaded KS image in the buffer (.rom and/or .bin).

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