EEPROM on A1200?

[motorollin]

IOW, if I want to use 1MB of kickstart, I have to build a KickFlash device :roll: I'm trying to experiment with UAE but for some reason it won't boot with a 40.68 image from my A1200. Grrrrrr....

--
moto

[Doobrey]

_yak_ wrote:
 Does someone there actualy know how the ROM modules are linked together?

They're not linked, simply put one after another...with a couple of exceptions like input/gameport/keyboard ,exec/alerthook etc compiled as one as they share some common routines to save space.

Each resident module contains a resident structure that identifies it( see the Amiga NDK  includes/exec/resident.h)
Basically exec searches through the memory areas it knows could contain a ROM for the RTC_MATCHWORD value ($4afc), if it finds it and the next longword is the address of the $4afc then it knows it's found a resident and then adds it to the resident list ( only if a greater version hasn't already been found etc.)

[_yak_]

Basically exec searches through the memory areas it knows could contain a ROM for the RTC_MATCHWORD value ($4afc), if it finds it and the next longword is the address of the $4afc then it knows it's found a resident and then adds it to the resident list ( only if a greater version hasn't already been found etc.)

So, the conclusion is we CAN use 2x512KB EEPROM chips without problems?

[motorollin]

Well, this rocks quite spectacularly. I used RomSplit to extract a 3.1 ROM image and the 3.9 ROMUpdate. I then removed anything to do with scsi.device (don't need on-board IDE), PCMCIA card (don't need that either) workbench.library (can have that on disk) and the v45 boot menu. Remus then made me a ROM image of everything that was left, and I had 50k to spare. Booted it on E-UAE, and here's the result:



Cool huh! I did get lots of errors in the terminal like "cia_wget: unknown CIA address a8300a PC=f80ede", I hope that won't be a problem when I'm using a real Amiga?

--
moto

[Doobrey]

@Motorollin,
  If it's lots of wgets for addresses between A80000 and B80000 it's OK, it's just looking for residents in an area of memory reserved for another 1MB ROM on the CD32. I'll do a simple patch to stop it.

[motorollin]

Yes that's correct, they are all between those addresses. There was also an illegal instruction, and lost of lines saying "Byte put to custom register DFF110 PC=00FDD8AA" all with different addresses. Is this ok? Will any of these errors cause a problem if the ROM is used on a real Amiga?

--
moto

[Nickman]

I made some research on the Kickflash 1200 product some time back.. i made a post on AW.net about it.
(i'm no longer a member there thats why it says Anonymous)

AW.net Kickflash 1200 vote thread

I still want one

[_yak_]

@ Nickman

Was there also such a tread here, on Amiga.org? I think most of the people here are "classics oriented" :-)

[Doobrey]

motorollin wrote:
There was also an illegal instruction,

Hmm, that doesn't sound good.. was the CPU set to '020 in EUAE ?
If it still happens, could you mail me the .rpf file (if you saved your build list) so I can build it and check it out?

 and lost of lines saying "Byte put to custom register DFF110 PC=00FDD8AA" all with different addresses. Is this ok? Will any of these errors cause a problem if the ROM is used on a real Amiga?

Depends,how many is 'lots'?
It looks like that's trackdisk.device just checking for disks in DF0-3..or was it disk.resource..gah it's late and my brains fried  :crazy: ...anyway, some register accesses in the uae.log are normal..even the bug in exec's chipmem size routine that reads from $200000.
If you boot with your A1200's 40.68 ROM and look at the log you can get an idea of what normally happens.

[TjLaZer]

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"

Hmm when I did it I omitted step 2 and it worked for me!

[ameegah]

TjLaZer wrote:
Hmm when I did it I omitted step 2 and it worked for me!

Yep, if you read through the thread from english amiga board forum link, it says earlier on in the thread that the unused space should be filled "just to be safe" so no surprises that it works fine when you leave it out.

Something to do with the 27c400 having an extra address pin and the possibility of it being left "floating".

[Nickman]

_yak_ wrote:
@ Nickman

Was there also such a tread here, on Amiga.org? I think most of the people here are "classics oriented" :-)

I made this tread at the same time.

[motorollin]

I have just tested my ROM properly in WinUAE by installing OS3.9. Everything went smoothly, and if I cold boot the emulator with no startup-sequence and type "version" it reports kickstart 45.20 and Workbench 45.1 :-)

Setpatch still reboots the machine on cold boot. I'm guessing this is because it's not clever enough to realise it already has 45.20 in ROM, and softkicks the update anyway. Deleting AmigaOS ROM Update stopped this though.

As soon as I get a reply from Willem confirming what hardware I need to programme the chip, I'm going to order  :-D

--
moto

[Johan Samuelsson]

setpatch noromupdate, hmm or was it setpatch skipromupdates  would cure it too i guess.
so, have you burned your rom now?
has anyone burned a 1mb rom?

if anyone has burned a 1mb rom, i'd appreciate some help.
i've created my 1mb rom as two 512k roms in remus.

But after this, I am kind of stuck. Do I use the AOS join command to join them together before burning or...? HELP!

[countzero]

if you're doing for a1200, you create the normal rom and extended roms (from address 0xe00000 as doobrey pointed and with romheader) apply the 1mb patch to your exec. dissect your roms wordwise(16 bit) into u6a and u6b pieces. then concatenate extended roms u6a with normal u6a (extended first) and extended u6b with normal u6b (again, extended first) burn then with byte swap and it should work.

[Johan Samuelsson]

is there any other app than winhex that can do that?
winhex is VERY unstable here.