Expand A500 beyond 16 MB with KS1.3

[Piru]

Doesn't A500 completely lack the uppermost 8 addressing signals anyway?

Just swapping the CPU alone won't give you true 32bit addressing.

[Piru]

If RAM is installed above 16 MB (0x0100 0000), and especially at 0x1000 0000 - 0xFF00 0000. Can the Kickstart v1.3 even handle it ..?, what's needed to add the memory to the available allocation pool?

Calling exec/AddMemList is the easy way. The harder way would be to have autoconfig for the memory. But since you're in control of the whole HW anyway, why bother...

Note however that the maximum address you may use is 0x7fffffff. For instance exec/AllocEntry uses negative return code to indicate failure, and thus >= 0x80000000 cannot be used.

[Piru]

Autoconfig allows you to call exec/AddMemList from an autoboot "rom" (the rom would be embedded in the fpga image).
 
All you'd have to do is respond internally to e80000 space until told to shut up, at which point you'd pass on the accesses to the cpu socket.
 
As you're going to have to have local vs motherboard accesses anyway then it's not going to be much extra logic.
 
The alternative is a command in s:startup-sequence, but thats boring.

The alternative I was thinking about is actually just executing the AddMemList from regular resident tag. Easier than doing the autoconfig magic, at least if you haven't done it before.

[Piru]

how does KS "know" how much RAM is inside the machine when it coldboots?

KS ROM performs a memory test for chip and ranger memory.
Rest is added by autoconfig(TM).