4MB Romy Functional!

[emufan]

Originally Posted by Akira

I had never heard of ROMdisk. It's a great idea.
Can I softkick a modified ROM with MAPROM or does this only work with real ROM chips/emulation?

in the current version you get a 1MB rom file , or 512kb/512kb kick/ext rom.
i'm not sure if those softkicker support 1mb rom file zize.

on the project page you can read: soft-kick'em in your accelerator card

#1) did anyone already ask Christian Vogelgsang aka cnvogelg,
about support for 2 and 4MB roms ?

#2) attached video shows boot 3.1 main disk after soft-reset,
with "set echo on" in startup-sequence - starting Multiview.

[kgc210]

Just ordered a new GAL off him.

Now just need to figure out how and earth I can build a 4MB ROM file. Dont even know how to build a 2MB one, only ever built them 1MB.

@SpeedGeek
Don't know if Cosmos has mention it to you yet but do you think it's possible 27c322 ROM's would work for 8MB ROM?

[SpeedGeek]

Originally Posted by kgc210

Just ordered a new GAL off him.

Now just need to figure out how and earth I can build a 4MB ROM file. Dont even know how to build a 2MB one, only ever built them 1MB.

@SpeedGeek
Don't know if Cosmos has mention it to you yet but do you think it's possible 27c322 ROM's would work for 8MB ROM?

You can find the 4MB Romy version here:

https://eab.abime.net/showthread.php?t=61677

Note: A4000T users need the special Rev. 11 Romy and new P652

P.S. Yes, 8MB is possible but seems really insane considering most A4000 users won't ever use the full 4MB Kickstart. I think Doobrey considered a 2MB Kickstart to be the largest practical size.

[kgc210]

I have a few of the 27c322 as they were alot cheaper than 27c160.
I am interested in in giving the ROM disk ago that utri007 mentioned.
Could get a decent little WB setup loaded up. Probably have a 2MB ROM / 6MB WB split.

[SpeedGeek]

Originally Posted by kgc210

I have a few of the 27c322 as they were alot cheaper than 27c160.
I am interested in in giving the ROM disk ago that utri007 mentioned.
Could get a decent little WB setup loaded up. Probably have a 2MB ROM / 6MB WB split.

If the 27C322 are pin compatible with the compatible 2MB/4MB devices than you should be able to use them... But the 4MB Romy version only enables 4MB of ROM space.

[kgc210]

Are you able to extend the ROMY GAL to address the other 4MB?
Pretty please with sugar on top :P

[fordav1]

27C322 is pin compatible. It's the same as 27C160 but with one extra address line.
I'm using a 27C322 in an A500 Rev 6 board with 8 kickstarts (switchable). Not for any other reason other than because I can ;-)

Kudos to Cosmos for figuring this out!

Kudos to whoever can do something useful with this, as I'm immensely curious and am excited to see what you guys come up with!

[grelbfarlk]

Do any of the Kickstart to Fast RAM remappers know how to handle a 4MB ROM?

[kgc210]

Whats the best method to make 4MB ROM's?
Create your normal 512K one and then make an extended ROM that is 3.5MB?
Or do you need to spilt it further?

[Amiga1992]

Originally Posted by grelbfarlk

Do any of the Kickstart to Fast RAM remappers know how to handle a 4MB ROM?

All the ones I know do max 1MB :/

[NorthWay]

I could open my mouth and say I'll make one, but by the time we'd trash out the requirements I suspect another one would be announced.
PM if you really have >1M.

[nogginthenog]

You can ask Christian Vogelgsang if he can add support for larger ROMs to romtool.
He's a nice guy and quickly added support for BlizKick modules when I asked.
https://github.com/cnvogelg/amitools

This is how I use it. I run Linux, but it might with with CygWin or Windows 10 Bash (I already checked if it supports >512, it doesn't).

romtool -L myrom.txt build -o myrom.rom -t kick -s 512 index.txt

index.txt is just a list of modules:

exec_45.20(A4000)
audio.device_37.10
battclock.resource_39.3
battmem.resource_39.2
<etc>

[kgc210]

Originally Posted by SpeedGeek

If the 27C322 are pin compatible with the compatible 2MB/4MB devices than you should be able to use them... But the 4MB Romy version only enables 4MB of ROM space.

I have read up some more on the 27c322. It has an extra address line A20 which is pin 32. The 27c160 has this as the word/byte select pin (Also on the 40pin ones like 27c400 but it's pin 31 not 32) The Amiga ties this to 5v to select word mode.

So to install a 27c322 I would have to lift pin 32 on both ROM's and tie them to pin 40 on Ramsey? (If support was added to ROMY)

On http://www.amibay.com/showthread.php...306#post649306

Originally Posted by SpeedGeek

- 4MB version address range moved to $01000000-$013FFFFF (should work with exec v45.20 without any patching!)

Does that mean the whole of the 4MB ROM gets seen at that location as a single 4MB chunk?

As when you build a 2MB ROM I believe you set the ROM build to be at $F80000, $E00000 and $A80000.

So to build a 4MB ROM in Remus can you set the ROM Base at $01000000 or do you still have to do $F80000, $E00000, $A80000 and then the last 2MB at $01000000 or am I barking up the wrong tree?

Then if support was added in an 8MB ROMY Gal the address range would be increased to $017FFFFF ?

[Mr.Flibble]

Originally Posted by nogginthenog

You can ask Christian Vogelgsang if he can add support for larger ROMs to romtool.
He's a nice guy and quickly added support for BlizKick modules when I asked.
https://github.com/cnvogelg/amitools

At an initial glance it looks like it's not too much to change it to support other sizes - he's filtering specifically for 256 or 512 as the allowed sizes, should be able to add 1024, 2048 and 4096 to the list without too much trouble - might need to add some more logic around the memory locations and split functions though.

[emufan]

there is already support to build 1MB (tutorial) roms:

First create a Kickstart ROM that supports an external ROM with additional 512 KiB storage.
We use amitool's  romtool  to convert a A1200 Cloanto OS 3.1 to support 1 MiB ROMs:

romtool patch -o kick.rom miga-os-310-a1200.rom 1mb_rom

the above example with romdisk was done this way.

#2) the romdisk 1MB rom: 512k +512k ext -> combined in one file:

ext with romheader: adr:00000000 - 11144EF9 00F80002
std with romheader: adr:00800000 - 11144EF9 00F800D2

maybe someone can spin the wheel, to the point of what to do with the
2nd and 3rd ext rom for the 2mb version.

#3)

tools/romtool.py:    logging.error("No ROM Header in Ext ROM image found!")

so any of the ext roms need the romheader, remus has two:
ROMHEADER_E0 (512k ext)
ROMHADER_A8 (1mb ext)

they do not differ, so I think they can be used for the next
ext roms to build a 4mb or 8mb rom.

so final build order would be:

1st: $E0 - 512k ext incl romheader 11144EF9 00F80002
2nd: $A8 - 1mb ext incl romheader 11144EF9 00F80002
3rd: $F8 - 512k std incl. romheader 11144EF9 00F800D2 - add 2mb_rom patch if not cd32 exec

[SpeedGeek]

Originally Posted by kgc210

I have read up some more on the 27c322. It has an extra address line A20 which is pin 32. The 27c160 has this as the word/byte select pin (Also on the 40pin ones like 27c400 but it's pin 31 not 32) The Amiga ties this to 5v to select word mode.

So to install a 27c322 I would have to lift pin 32 on both ROM's and tie them to pin 40 on Ramsey? (If support was added to ROMY)

On http://www.amibay.com/showthread.php...306#post649306


Does that mean the whole of the 4MB ROM gets seen at that location as a single 4MB chunk?

As when you build a 2MB ROM I believe you set the ROM build to be at $F80000, $E00000 and $A80000.

So to build a 4MB ROM in Remus can you set the ROM Base at $01000000 or do you still have to do $F80000, $E00000, $A80000 and then the last 2MB at $01000000 or am I barking up the wrong tree?

Then if support was added in an 8MB ROMY Gal the address range would be increased to $017FFFFF ?

Cosmos found some 27C322 and also requested 8MB Romy GAL support. Here is my reply:

The 27C322 are not pin compatible...

Now, that exec needs patching and people have enough trouble building 2-4 MB ROMs (still not fully supported in Remus) there are already too many things to go wrong!

Also, I already have 4 Romy versions to support...

@Thread

You always needs the standard 512KB ROM for $F80000 so this leaves 1.5MB / 3.5MB (depending on device size) for the extended ROM $1000000 and up.

[SpeedGeek]

UPDATE:

I've uploaded a 4MB ROMY patch for exec (see post #1). Now you guys can practice your ROM building (and hardware hacking) skills!

[kgc210]

Thanks, will try and get some 27c160 ROMS and place these 27C322 in the drawer for now.

[kolla]

Now just replace ROMs with (faster) flash RAM, and it's full circle