Problems burning Kickstart

[tomse]

I'm not sure if the 150 is too slow,
it's for A1200

byte/word mode ??
can you explain more please ?

cheers
/Tomse

[alexh]

Some EPROM programming software already knows you're using a 16-bit EPROM. Most have the ability to swap bytes (i.e. byte or word mode) in the programming software for 16-bit mode.

[tomse]

well.. when choosing the 27c400 it knows that a 16bit adapter needs to be used,
so I guess it already writes as 16 bit (?).

if any other person with a Willem programmer could probably verify this :-)

atleast I haven't seen any byte/word feature in the software, so I guess it's automatic.

[kipper2k]

Originally Posted by tomse

well.. when choosing the 27c400 it knows that a 16bit adapter needs to be used,
so I guess it already writes as 16 bit (?).

if any other person with a Willem programmer could probably verify this :-)

atleast I haven't seen any byte/word feature in the software, so I guess it's automatic.

Check this thread out, it has some info on Willem software...
http://eab.abime.net/showthread.php?t=46636

[tomse]

if you are refering to the step-by-step guide opening, swap byte, saving and closing.

then this is what I've done.. well almost, I didn't save as I don't see any reason for it.

my only guess is as alex suggests, that the 150ns roms are too slow.

but It would be nice to have this confirmed before I buy a 10 batch eproms (or 2 if I can find them)

[Toni Wilen]

150ns is too slow for A1200. ~140ns or faster needed. A3000 and A4000 have ROM speed jumpers, A1200 does not.

Read your original ROMs to confirm correct interleave and byteswap.

[tomse]

thanks for the info Toni.

Unfortunately my original roms got fried when trying to mount a Fast ATA mk3, so I only have the dump file I made of it while it was still working :-(

[spotUP]

for those trying to make a kickstart, this looks kinda kick ass!

http://aminet.net/package/util/libs/execlibrary

[blasterreal]

[alexh]

Originally Posted by spoUP

for those trying to make a kickstart, this looks kinda kick ass!
http://aminet.net/package/util/libs/execlibrary

Interesting stuff. I wonder how it holds together for A4000? (i.e. 512Kbyte ROM limitation.)

Originally Posted by blasterreal

Why doesn't scsi.device have the version v43.45?

[blasterreal]

I am using http://www.doobreynet.co.uk/amiga.html scsi 44.2 patch. because 43.45 included some bug.

The rom included.

- scsi.device 44.2
- con.hanler >Kingcon.handler v40.4 http://aminet.net/package/util/shell/KingCON_404
- exec.library v45.22
- filesystem v45.15
- ram-handler v44.24
- ramlib v40.3
- shell v45.27
- trackdisk.device v40.2
- graphics.library 40.25b8
- smartfilesystem 1.279

[Cosmos]

>scsi.device 44.2

I'm not ok with assembling a raw source with opt=3 : not a good idea, we don't know exactly with precision what Phxass change...
I already said that at Doobrey... Excuse me Doob', you are a brillant coder, but you can't do that !

When I use opt=3, graphics.library beta don't works...


>because 43.45 included some bug

Oh ? Where ?

[alexh]

I'd be interested in working out the best selection of upgrades and patches which will fit in a 512Kbyte 3.9.1 ROM for A4000D. Unfortunately they are hard limited to 512Kbytes.

[rkauer]

@Alexh: Not exactly (maybe a mod can move this bit of discussion to another thread?).

Doobrey already show how to add hardware support for 1Mb ROM for A4000.

I think I need to dig some links of this matter.

All I remember is the A4000 mobo already have the places to put the lacking hardware. And the parts are easy to find and cheap!

[alexh]

Originally Posted by rkauer

@Alexh: Not exactly Doobrey already show how to add hardware support for 1Mb ROM for A4000.

Erm?? If you need to add extra hardware then the A4000D doesn't support 1Mbyte ROM?

Originally Posted by rkauer

All I remember is the A4000 mobo already have the places to put the lacking hardware. And the parts are easy to find and cheap!

This is not true for A4000D.

Originally Posted by Doobrey

The 'Fat Gary' chip in A3000, A4000 and A4000T only generates the /ROM_OE chip select for the normal 512K ROM \@ $F80000

http://eab.abime.net/showpost.php?p=557999&postcount=15

I seem to remember that A4000D motherboard also does not have enough address lines wired to the ROM sockets.

[rkauer]

Yes you are right, was only for A4000T. End of discussion.

[blasterreal]

@Cosmos,
Hello Friend,this pictures show my problem. "scsi.device 43.45" create a problem my a1200 but "scsi.device 44.2" not problem my amiga 1200.


http://img691.imageshack.us/i/noproblem.jpg/
http://img202.imageshack.us/i/problemyd.jpg/

My startup-sequnce config ,

remapollo module devs:modules/bootmenu_44.7 devs:modules/console_40.10 devs:modules/exec_45.22 devs:modules/filesystem.resource_45.10 devs:modules/Ram-Handler_44.24 devs:modules/romupdate_44.57 devs:modules/scsi.device_43.45 devs:modules/shell_45.27


stack 8000
c:SetPatch noromupdate QUIET
mudrap


C:Version >NIL:

C:AddBuffers >NIL: DF0: 15

FailAt 21



C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys

C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ



Resident >NIL: C:Assign PURE

Resident >NIL: C:Execute PURE



Assign >NIL: ENV: RAM:ENV

Assign >NIL: T: RAM:T

Assign >NIL: CLIPS: RAM:Clipboards

Assign >NIL: REXX: S:

Assign >NIL: PRINTERS: DEVS:Printers

Assign >NIL: KEYMAPS: DEVS:Keymaps

Assign >NIL: LOCALE: SYS:Locale

Assign >NIL: LIBS: SYS:Classes ADD

Assign >NIL: HELP: LOCALE:Help DEFER

Assign >NIL: MUI: SYS:MUI

Assign >NIL: Libs: MUI:libs ADD

BindDrivers

C:Mount >NIL: DEVSOSDrivers/~(#?.info)



C:LoadMonDrvs



SetEnv Language "english"

SetEnv Workbench $Workbench

SetEnv Kickstart $Kickstart

UnSet Workbench

UnSet Kickstart



C:AddDataTypes REFRESH QUIET

C:IPrefs

C:ConClip



Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities



SYS:System/REXXMast >NIL:



IF EXISTS S:User-Startup

Execute S:User-Startup

EndIF



Resident Execute REMOVE

Resident Assign REMOVE



C:LoadWB

EndCLI >NIL:

[Cosmos]

Whaou...


For the v43.45, I take the v43.43 from the BB2, and apply the patchs from Aminet... Nothing more, nothing less...

Please, try with the v43.43...

[tomse]

I finally figured out what the problem was.

the kick rom that was grabbed from mem, needs to be recompiled using Remus.
since otherwise it's useless.
I didn't use the remus to begin with, since I just wanted to have my A1200 back online then I can fiddle with making 3.9 roms later.

what I did was only to split the grabbed kick rom and concatenate it to itself..

btw.. a free and easy way to concatenate without additional tools is using the copy command in windows:

copy /b rom.low + rom.low u6a.rom
copy /b rom.hi + rom.hi u6b.rom

(the /b makes sure it's copied as binary)
rom.low = first 256kb of the rom
rom.hi = last 256kb of the rom

this is so much easier than using total commander where you need to have a numbering of the files, and 2 copies of them aswell.

thanks for your help all

[stachu100]

Originally Posted by Toni Wilen

150ns is too slow for A1200. ~140ns or faster needed. A3000 and A4000 have ROM speed jumpers, A1200 does not.

Read your original ROMs to confirm correct interleave and byteswap.

What about 27C4100-10 or 27C4100-12?
They are slower than 27C400, but 100ns or 120ns should be enough.
They seem to be 100% pin-to-pin compatible with 27C400 as well.