1mb rom for A1200

[utri007]

I have read thread about making/burning rom, but there is no thread what could be inside of it. Another important question wich is not answered here, how can I test it with real Amiga? Blizkick doesn't support 1mb roms, I don't know how would remapollo do?

But queations are :

My main goal would be to make a possible to boot from CD-Rom, is possible and how?

Can I add a network driver to it?

What would be best choises for a exec and graphics.library? How a about scsi.device?

icon.library is ok, but are there newer workbench.libarary somewhere?

Is there a lists what has other people put inside of it?

I don't want to fill it with "beta stuff"

[mfilos]

Originally Posted by utri007

My main goal would be to make a possible to boot from CD-Rom, is possible and how?

No it's not. Maybe if Doobrey makes it in the future (who knows)...

Originally Posted by utri007

Can I add a network driver to it?

If the network driver is romable, you could. What's the point though? It's more relevant to put USB stack and USB driver in order to boot from USB stick for example instead of having just the network drive in ROM.

Originally Posted by utri007

What would be best choises for a exec and graphics.library? How a about scsi.device?

For Exec there aren't many choices. BB2's is stable enough and for older cases you can have Piru's Exec.
For scsi.devices there are Doobrey's, Cosmos's, Don Adan's and Toni/Chris's.
Imho for SFS filesystem I found the best scsi.device to be Doobreys. For PFS3 my personal choice is Don Adan's and Cosmos's.

Originally Posted by utri007

icon.library is ok, but are there newer workbench.libarary somewhere?

Icon library archive on Aminet has also a patch for Workbench.library to get it up to version 45.132 (from 45.131).

Originally Posted by utri007

Is there a lists what has other people put inside of it?

Some of the modules I have on my personal custom 3.9 ROM are:
- exec.library 45.20 (updated from BB2)
- battmem.resource 40.0 (updated from Don Adan)
- bootmenu 44.7 (updated from BB2)
- cia.resource 40.0 (updated from Don Adan)
- console.device 44.10 (updated from BB3/BB4)
- datatypes.library 44.48 (updated from BB3/BB4)
- dos.library 42.1 (updated from Don Adan)
- filesystem.resource 46.0 (updated from Don Adan)
- filesystem 45.16 (updated from BB3/BB4)
- graphics.library 41.24 (updated from Don Adan)
- icon.library 46.4.326 (updated from PeterK)
- intuition.library 41.0 (patched with PowerWindows)
- input.device 50.26 (updated from Poseidon archive)
- mathffp.library 41.0 (updated from Don Adan)
- misc.resource 38.0 (updated from Don Adan)
- potgo.resource 38.0 (updated from Don Adan)
- ram-handler 44.24 (updated from BB2)
- romboot 44.2 (updated from Ratte)
- scsi.device 43.47 (updated from Cosmos)
- shell 45.27 (updated from BB3/BB4)
- wbtask 40.0 (updated from Don Adan)
- workbench.library 45.132 (updated from PeterK)
- hrtmodule 2.33 (HRTMon modules from Toni Willen)
- IDE_DelayFix (BlizKick module)
- NoClick (BlizKick module)
- patchmath020-ALL (BlizKick module)
- romfixes2 (BlizKick module)

[demolition]

Originally Posted by utri007

Another important question wich is not answered here, how can I test it with real Amiga? Blizkick doesn't support 1mb roms, I don't know how would remapollo do?

For ACA accelerators, acatune can maprom 1MB ROMs. I am loading a 1MB ROM from HDD on my 1200, mainly to get an updated scsi.device.

[utri007]

Could it be possible to use acatune's map rom feature with blizzard/apollo?

[demolition]

No, it is made only for ACA accelerators. However, I think the Blizzard cards should be able to map 1MB ROMs as well. I took the 1MB ROM header from the BlizKick package.

[mfilos]

No you can't. BlizKick can kick up to 512KB ROM

[roy bates]

remapollo cant map 1mb either so thats out of the question 1.7 is on aminet,i heard that 1.8 would allow this but i never tried it myself.

[Ratte]

Originally Posted by mfilos

Some of the modules I have on my personal custom 3.9 ROM are:
(....Don Adan)

He is (only) resourcing all modules (just like 100 bytes wbfind) and recompiled them.
There is nothing new, only the risk of broken (bad resourced) code.
If you like higher version numbers i can hack wbfind/exec/what ever v99.9+ for you ....

[mfilos]

Changing the version number is easy simply with Hex Edit (as I done already on some patched modules by me to know the difference).
I didn't know Don Adan's modules were simply resourced ones. I was under the impression that they also had improved code and some bug fixes (like for example the scsi.device).

[hooverphonique]

I guess softkicking using mmu (set040, etc.) would allow for larger roms.. after all, it is the rom itself that must support looking for romtags within the extra 512kb.. The softkicking software needs to support remapping multiple address spaces then, of course, since roms larger than 512kb need that.

[chaos]

Somewhat offtopic:

How does the CPU access 1MB ROMs - the upper half, since the normal 512kB ROM is already mapped at the end of Amiga 24bit memory space? Is this done with some MMU (or MMU-like) hardware mapping tricks? I guess if you are able to place he whole kickstart ROM in RAM, this is not a problem. But using actual physical 1MB EPROM is not possible I guess?

[mfilos]

Originally Posted by chaos

...But using actual physical 1MB EPROM is not possible I guess?

Ofc it's possible!
A600/A1200 can use 1MB ROM easily. A3000/A4000 need ROMY (the extra pcb and logic made by SpeedGeek). A500/2000 need 2 signals (Gary's Pin 35, Pin 36 tied to 27C800's Pin 1 and Pin 42) but still doable.

I first used an 1MB physical ROM succesfully 3 years ago.

[chaos]

Originally Posted by mfilos

Ofc it's possible!
A600/A1200 can use 1MB ROM easily. A3000/A4000 need ROMY (the extra pcb and logic made by SpeedGeek). A500/2000 need 2 signals (Gary's Pin 35, Pin 36 tied to 27C800's Pin 1 and Pin 42) but still doable.

I first used an 1MB physical ROM succesfully 3 years ago.

Great! Looks like I was reading the Amiga memory map wrongly
So the 1MB kickstart ROM can use the address space 0xf00000 to 0xffffff, right?

I should implement 1MB kickstart support for minimig right now

EDIT: stupid me, according to schematics, it seems my A500+ actually supports 1MB ROMs by default - I always wondered why the longer kickstart slot

[Toni Wilen]

1M address space is E00000-E7FFFF and F80000-FFFFFF. 2M adds A80000-B7FFFF.
F00000-F7FFFF is not part of KS ROM space. It is some kind of expansion ROM space, also used by CDTV extended ROM.

[chaos]

Originally Posted by Toni Wilen

1M address space is E00000-E7FFFF and F80000-FFFFFF. 2M adds A80000-B7FFFF.
F00000-F7FFFF is not part of KS ROM space. It is some kind of expansion ROM space, also used by CDTV extended ROM.

Thanks for the explanation.

It seems this is more complex than I thought. Which ROM address gets mapped to address 0 when kickstart overlay is enabled at boot? Does this depend on the Amiga type? For example, for Amigas with 256KB ROMs, the address should be 0xfc0000, for Amigas with 512KB ROMs 0xf80000, but for A1200 the address should be 0xe00000 (according to docs I found, this is the first part of the 1MB ROM, the second is at 0xf80000)?

To the original poster : sorry for hijacking your thread a little

[Toni Wilen]

Technically it is E0 ROM that always appears at 0 (if 1M capable MB, don't remember what 2M capable MBs do but I think it was one of the A8/B0 areas).

It isn't that complex, same ROM just appears multiple times in address space if not all address lines are connected.

256k = same 2x256k at F8 and E8 (and A8/B0). 512k = same 512k at F8 and E8 (and A8/B0) and so on..

[tom256]

Here You go, full Amiga 1200 memory map:


5.0 A1200 Memory Map
Address Size
000000 to 1FFFFF 2 MB Chip RAM(or system ROM overlay)
200000 to 5FFFFF 4 MB Zorro II expansion space
600000 to 9FFFFF 4 MB Credit Card memory if CC present
A00000 to A1FFFF 128 KB Credit Card Attributes
A20000 to A3FFFF 128 KB Credit Card I/O
A40000 to A5FFFF 128 KB Credit Card Bits (similar to CDTV)
A60000 to A7FFFF 128 KB PC I/O
A80000 to B7FFFF 1 MB System ROM selected
B80000 to BEFFFF 448 KB Not used(Reserved for CDTV)
BF0000 to BFFFFF 64KB 8520CIAs
C00000 to CFFFFF 1 MB C00000 Memory
D00000 to D7FFFF 512 KB PC memory
D80000 to D8FFFF 64 KB SPARE chip select
D90000 to D9FFFF 64 KB ARCNET chip select
DA0000 to DA3FFF 16 KB IDE drive
DA4000 to DA4FFF 16 KB IDE reserved
DA8000 to DAFFFF 32 KB Credit Card and IDE configregisters
DB0000 to DBFFFF 64 KB Not used(reserved for external IDE)
DC0000 to DCFFFF 64 KB Real Time Clock(RTC)
DD0000 to DDFFFF 64 KB RESERVED for DMA controller
DE0000 to DEFFFF 64 KB Not Used
DF0000 to DFFFFF 64 KB Chip Registers
E00000 to E7FFFF 512 KB System ROM(lst half if 1MB ROM)
E80000 to EFFFFF 512 KB Configuration and I/O card space
F00000 to F7FFFF 512 KB Flash ROM space
F80000 to FFFFFF 512 KB System ROM(2nd half if 1MB ROM


From http://www.ianstedman.co.uk/downloads/A1200FuncSpec.txt

[RedskullDC]

Hi Tony, et al.

Originally Posted by Toni Wilen

Technically it is E0 ROM that always appears at 0 (if 1M capable MB, don't remember what 2M capable MBs do but I think it was one of the A8/B0 areas).

Should always be the $E0 bank that appears at $00 when using 1/2MB roms and *OVR is active.
(A19 active for 1MB, A19 and A20 active for 2MB).

Amiga Address Lines:
A A A A A
2 2 2 2 1
3 2 1 0 9

0 0 0 0 0 $0 ROM appears at $00 when *OVR low
1 0 1 0 1 $A8 System ROM selected (2MB area)
1 0 1 1 0 $B0 System ROM selected (2MB area)
1 1 1 0 0 $E0 System ROM(lst half if 1MB ROM)
1 1 1 1 1 $F8 System ROM(2nd half if 1MB ROM)

Cheers,
Red

[delshay]

As the FastATA plugs into this socket maybe something can be done to enhance FastATA performance by adding something in the rom or better still FastATA have a redesign and firmware change to use 1Mb roms.

[mfilos]

But the FastATA is just mounted in the kickstart sockets of A1200 which by default support 1MB ROMS
The only thing that could benefit the FastATA would be an updated ATA3.driver which would be ROMable in order for not having to declare it in Startup-Sequence to patch the scsi.device.