TeamAROS Bounty #23 AROS Kickstart Replacement ROM

[Doobrey]

For UAE, you`re limited to a 1Mb rom image
 The first 512k @$f80000 , and the second @$E00000 (which UAE calls the extended rom space). Just remember to add a jump to the startup code from $E00004, since that block will be mapped to 0 on bootup.

[Doobrey]

jdiffend wrote:
I suppose I could write a utility to extract devices like the trackdisk.device from the current ROM and turn it into a disk based version until someone writes a replacement.

I`ve already got that far with Remus.
 Unfortunately, it`s the {bleep}ing extraction that I`m rewriting at the moment !
Lemme know what 3.1 Kickstart you`ve got, and I can send you something split it up for you.

[Doobrey]

jdiffend wrote:

I'd be happy to do a board layout if I have time.  Are you addressing the additional ROM space at the same location as UAE has it?  I could make a new board design based on the ROM switcher I already made and add the address decoding logic and a wires for the extra address line etc.  I figure one PAL would hold all the logic.

Yup..I`m building a GAL programmer now to get it all done and do the final testing.

It works pretty much as you`ve described, a jumper/switch to select either real rom or flash,another to select which is programmable at @$e00000 , and one last jumper to select either 1mb of flash or select the high or low 512k of flash if you want 2 different rom images.

The only other thing I`ve done is invert A19, so $f80000 is mapped to the lower 512kb etc, cos that way I can use the 16kb parameter block of the flash using my own nonvolatile.library for storing things like boot settings.

Get well soon, hope it wasn`t through enjoying the new year too much..
[/quote]