Problems burning Kickstart

[DigitalKeeper]

Originally Posted by Nightshft

<snip> And interestingly the A500 is more picky about speed than f.e. an A1200 or many other Amigas. <snip>

Affirmative!


I've tested the Eproms with 150ns - and most of my A500 don't like it; the "120ns" would be run fine


At this Point -> i only use the "120ns" Eproms, i.e. 27C400; 27C800; 26C1600

[nikoskob]

Originally Posted by DigitalKeeper

Affirmative!


I've tested the Eproms with 150ns - and most of my A500 don't like it; the "120ns" would be run fine


At this Point -> i only use the "120ns" Eproms, i.e. 27C400; 27C800; 26C1600

To add to that, i just burnt a 105ns 27c400 for my A500+ and it works fine. No issues yet, if this helps.

[MickGyver]

I have made a tool to simplify working with roms (for Amiga etc). It is called EPROM Tool and you can get it here:

http://daemonbite.com/files/linked/EPROMToolV09.zip

(Windows only at the moment)

[RoC]

Have been using the Nightshift’s EPROM tool for some time, which made the rom preparation for burning super easy.

I will try this new Mick Gyver’s tool as well.

[DigitalKeeper]

Nice; i'll have a look for it - Please make it possible to integrate German and other languages, i.e. via "lang.txt" - then we can translate it

Look at this - RomWizard - Very Cool Program:



And the "Eprom Hexxer" from Nightshift - i use this

[Jope]

I use srec_cat from the srecord package. No gui to slow me down, so it can be fully scripted and it will do just about anything you can imagine to various binary/srec/intel hex files.

[Mickoz]

Originally Posted by amethyst

In answer to the Computolio's original question, here's how to burn a kickstart eprom set for an amiga a1200 in 4 easy steps:

Requirements

• Eprom Programmer (with support for 27C400)
• WinHex utility (registered version) or write your own code to perform Steps 1 to 2.
• Kickstart rom file being used in WinUAE (not encypted and legally created from your own set of A1200 kickstart roms, of course)
• Two blank 27C400 eproms

Step 1: Split the kickstart rom file
In WinHex select: Tools -> FileTools -> Dissect -> Wordwise (16-bit)
Select source kickstart rom file
Type in destination filename#1 eg. U6A_tmp.rom (00000-3FFFF for U6A)
Type in destination filename#2 eg. U6B_tmp.rom (00000-3FFFF for U6B)
Now you have two smaller rom files

Step 2: Fill addressable unused memory space for both eproms
Now, we're going to copy the contents of addresses 00000-3FFFF to 40000-7FFFF for U6A_tmp.rom
To do this, in WinHex select: Tools -> FileTools -> Concatenate
Type in destination file for a blank rom file to be created (eg. U6A.rom)
Append file U6A_tmp.rom to U6A.rom
Repeat this again, append source file U6A_tmp.rom to U6A.rom
Select Done and a message box will appear: 524288 bytes from 2 files were concatenated to "U6A.rom"

Repeat Step 2 using U6B_tmp.rom to create U6B.rom

Step 3: Burn the kickstart eproms
Start up eprom programmer software with 27C400 device selected.
Load U6A.rom to the buffer
Perform a swap BYTE operation on the buffer contents
Insert a 27C400 eprom into the eprom programmer and burn buffer to the eprom.
Apply opaque sticky label over the eprom window and mark it "U6A"

Repeat Step 3 for U6B.rom, marking it "U6B"


Step 4: Install eproms into A1200
Insert eprom U6A into U6A socket and eprom U6B into U6B socket (make sure the eprom has correct pin connections and orientation).
Power up and hey presto it works!

For more details on opening up your amiga and installing the eproms read the amiga kickstart guide from aminet.

I hope someone else benefits from my tweaking of the original post to suit an Amiga 3000 and using Winhex to byte swap.

Here's how to burn a kickstart eprom set for an amiga a1200 or a3000 in easy steps:

For Amiga 3000, replace U6A with U181 and U6B with U180

Requirements
• Eprom Programmer (with support for 27C400)
• WinHex utility (registered version) or write your own code to perform Steps 1 to 2.
• Kickstart rom file being used in WinUAE (not encypted and legally created from your own set of A1200 kickstart roms, of course)
• Two blank 27C400 eproms
Step 1: Split the kickstart rom file
In WinHex select: Tools -> FileTools -> Dissect -> Wordwise (16-bit)
Select source kickstart rom file
Type in destination filename#1 eg. U6A_tmp.rom (00000-3FFFF for U6A)
Type in destination filename#2 eg. U6B_tmp.rom (00000-3FFFF for U6B)
Now you have two smaller rom files

Step 2: Fill addressable unused memory space for both eproms
Now, we're going to copy the contents of addresses 00000-3FFFF to 40000-7FFFF for U6A_tmp.rom
To do this, in WinHex select: Tools -> FileTools -> Concatenate
Type in destination file for a blank rom file to be created (eg. U6A.rom)
Append file U6A_tmp.rom to U6A.rom
Repeat this again, append source file U6A_tmp.rom to U6A.rom
Select Done and a message box will appear: 524288 bytes from 2 files were concatenated to "U6A.rom"

Repeat Step 2 using U6B_tmp.rom to create U6B.rom

Step 2b: Load U6A.rom into Winhex and select all, then Edit - Modify Data - Select "Reverse byte order" with a value of 2, save out as U6A_swapped.rom

Repeat Step 2b for U6B.rom to create U6B_swapped.rom

Step 3: Burn the kickstart eproms
Start up eprom programmer software with 27C400 device selected.
Load U6A_swapped.rom to the buffer
Insert a 27C400 eprom into the eprom programmer and burn buffer to the eprom.
Apply opaque sticky label over the eprom window and mark it "U6A"

Repeat Step 3 for U6B.rom, marking it "U6B"


Step 4: Install eproms into A1200 or A3000
Insert eprom U6A into U6A and eprom U6B into U6B socket or U180 into U180 and U181 into U181 socket(make sure the eprom has correct pin connections and orientation).

[Jope]

Or from a posix shell (linux, mac, wsl) after you have installed srecord

This splits the file:
srec_cat source.rom -Binary -split 4 0 2 -byte-swap -o hi.rom -Binary
srec_cat source.rom -Binary -split 4 2 2 -byte-swap -o lo.rom -Binary

Then double it to fill a 27c400:
cat hi.rom hi.rom > hi.bin
cat lo.rom lo.rom > lo.bin

Make a little shell script so you can just call it once against your rom file.. (this is for my own future benefit because I always have to look at the manpage for srec_cat because I do these so seldom ;-)

#!/bin/bash

[ ! -f $1 ] && echo "File not found: $1" && exit 1

srec_cat "$1" -Binary -split 4 0 2 -byte-swap -o /tmp/"$1"hi -Binary
srec_cat "$1" -Binary -split 4 2 2 -byte-swap -o /tmp/"$1"lo -Binary
cat /tmp/"$1"hi /tmp/"$1"hi > "$1"-hi.bin
cat /tmp/"$1"lo /tmp/"$1"lo > "$1"-lo.bin
rm /tmp/"$1"hi /tmp/"$1"lo

[Hub750]

Hi, for 1200
1)use 27c160
2)speed 27160 =< 100..very important or will not work!
3)Burn
4)enjoye.

[Hub750]

and never leave an EEprom half full, always fill it.

[retrofriends]

I have done a video on the process step-by-step, using SRecord instead of WinHEX ($$$). I wish I had seen Jope's post first before wasting an hour trying to get the syntax correct for srec_cat.exe. Had to educate myself on the difference between "Word" splitting and "bit" splitting. As an alternative, I used the tried-and-true Windows copy command to concatenate the images.

Video here: [ Show youtube player ]

[RoC]

Wrong post. Sorry

[tech3475]

I just want to confirm, is it ok to use 27C800 with OS 3.2 on an Amiga 1200?

I have a couple of these lying around but if they're a problem I'll just buy a pre-written set when I order OS 3.2.

[Jope]

You can use them, but most of the chip will be wasted. You should duplicate the contents of the 512k bin files to get 1MB files for burning.

[tech3475]

Originally Posted by Jope

You can use them, but most of the chip will be wasted. You should duplicate the contents of the 512k bin files to get 1MB files for burning.

Thanks.

[brett71]

Recently, I bought a bunch of AMD 27C400's off eBay from two different sellers, both from China, and the chips were all pretty much identical, i.e. came from the same source. I've had these sitting on the shelf for a while, and only was until last night that I cracked out my TL866 that I bought after I got the 27C400's and plugged in an adapter board that I made a couple of weekends ago. I suspected these chips were probably re-marked, I confirmed this was the case after watching a YouTube video on how to pull the Chip IDs out of the ROM's.

The Chip ID for these Chinese AMD 27C400's came back as "00c2 b800" instead of "0001 009d" which is correct for the AMD ROMs. The ROMs I actually have appear to be MX 27C4111's. I'm assuming this means it's in the MX 27C4100 line, perhaps a newer revision?

The question I have is: Are the MX 27C4100/4111 chips equivalent to the AMD 27C400's?

[demolition]

They are pin compatible but with much worse access time, so 4100 might not be fast enough. You can try without breaking anything though.

[A4000Bear]

Originally Posted by brett71

The question I have is: Are the MX 27C4100/4111 chips equivalent to the AMD 27C400's?

I have been using MX27C4100 EPROMs in all my Amigas (A1200, A4000, A3000) and they work fine.

[brett71]

Originally Posted by A4000Bear

I have been using MX27C4100 EPROMs in all my Amigas (A1200, A4000, A3000) and they work fine.

I think the only catch to the EPROMs I have is if the speed of the EPROM is appropriate for the Amiga as a Kickstart ROM. I have no idea if there is a way to test that without uncovering the original markings somehow.

[merlinkv]

With Remus 1.80 I have build a nice Kickstart 3.9 1MB for my A1200D with next modules, libraries and devices ...

First ROM

ADD Modules/44.57_ROMUpdate(3.9bb2)/exec_45.20(A1200-A500)
ADD Blizkick/1MB_ROM
ADD Modules/40.68(A1200)/audio.device_37.10
ADD Modules/40.68(A1200)/battclock.resource_39.3
ADD Modules/40.68(A1200)/battmem.resource_39.2
ADD Modules/44.57_ROMUpdate(3.9bb2)/bootmenu_44.7(68020)
ADD Modules/40.68(A1200)/card.resource_40.4
ADD Modules/40.68(A1200)/carddisk.device_40.1
ADD Modules/40.68(A1200)/cia.resource_39.1
ADD Modules/40.68(A1200)/con-handler_40.2
ADD Modules/44.57_ROMUpdate(3.9bb2)/console.device_44.8
ADD Modules/40.68(A1200)/disk.resource_37.2
ADD Modules/MerlinKV/dos.library
ADD Modules/40.68(A1200)/expansion_40.2(A1200)
ADD Modules/BB4/FileSystem.resource
ADD Work2:Install/BoingBag3.9-3&4/Files1/L/FastFileSystem
ADD Modules/40.68(A1200)/gadtools.library_40.4
ADD Modules/MerlinKV/icon.library
ADD Modules/40.68(A1200)/input_40.1
ADD Modules/40.68(A1200)/intuition.library_40.85
ADD Modules/40.68(A1200)/keymap.library_40.4
ADD Modules/MerlinKV/layers.library
ADD Modules/MerlinKV/mathffp.library
ADD Modules/MerlinKV/mathieeesingbas.library
ADD Modules/40.68(A1200)/misc.resource_37.1
ADD Modules/40.68(A1200)/potgo.resource_37.4
ADD Modules/3.9-44.57_ROMUpdate(BB2)/ram-handler_44.24_NoBss
ADD Modules/40.68(A1200)/ramdrive_39.35
ADD Modules/40.68(A1200)/ramlib_40.2
ADD Modules/MerlinKV/romboot44_3
ADD Work2:Install/BoingBag3.9-3&4/Files2/Devs/scsi-A1200.device
ADD Modules/3.9-44.57_ROMUpdate(BB2)/shell_45.7
ADD Modules/40.68(A1200)/timer.device_39.4
ADD Modules/BB4/trackdisk.device
ADD Modules/MerlinKV/utility.library
ADD Modules/40.68(A1200)/wbtask_39.1
ADD Blizkick/ROMFixes_2.7

Extended ROM

ADD Others/ROMHeader/ROMHeader_E0
ADD Others/DummyCDstrap
ADD Modules/Blizkick/BPPCFix
ADD Modules/MerlinKV/datatypes.library
ADD Modules/MerlinKV/graphics.library
ADD Work2:Install/BoingBag3.9-3/Files1/libs/workbench.library
ADD Modules/MerlinKV/pfs3aio
ADD Modules/MerlinKV/SmartFilesystem

-------------------

ROM is plenty of space for that reason I have put the workbench.library inside.

ROM is really working like a charm.

Time to boot without HDD or floppy inserted is about 2-3 seconds.

Tested on 27C800 for single ROM setup and with M27C160/MX29F1615 (100ns) for four ROMs setup on my KS switcher.