Since after release 20231204, no fast RAM is detected in Kickstart <2.0

[rittwage]

20231204 is the last release where it worked.

In both 2024 releases, and the 2025 release, fast RAM is not detected under Kickstart 1.3

It looks to me like the Toccata code broke it. It messed with the autoconfig code.

[rhester72]

Further discussion here:

https://misterfpga.org/viewtopic.php?t=8924

[sorgelig]

I've pushed the fix, so you can test in unstable/nightly build.

[rhester72]

Confirmed, thanks sorgelig! 1.3 and 2.x both work as expected and the Toccata is autoconfigged in both cases.

[sorgelig]

I've added more changes in autoconfig. Please test it.

[rhester72]

Tested every combination of 68000/68020, KS 1.2/1.3/2.04/3.1 and chip/24-bit/32-bit RAM possible, and every combination worked as expected (including proper presentation of Toccata). Two anomalies that are probably correct:

• KS 1.2 on 68020 Gurus running SysInfo
• KS 1.3 on 68020 with 32-bit fast doesn't show fast RAM at all (I think that is normal and only worked on the A3000 with its RAMsey custom chip)

Short version: Looks good!

[bfbiii]

I can double check tonight!

For Zorro III with Kick 1.3 and 020, you need to add it manually. Easiest way is with the early version of Addmem found on YKick or AutoAddRam. Both on Aminet.

https://aminet.net/package/util/misc/ykick

https://aminet.net/package/util/boot/AutoAddRAM

(Hope those are the correct links)

[rhester72]

@bfbiii Makes sense, KS 1.x predates 32-bit RAM addressing entirely.

[bfbiii]

Long story short: this looks good to me.

Details: I can run Kickstart 1.2-3.2.2 with access to Fast RAM as expected with little exception.

The biggest exception is I cannot add Zorro III RAM to 1.3 manually in 020 mode using AutoAddRAM above. I'm able to do that with WinUAE and OEM.

Ancillary stuff: on this build, and OEM, Sysinfo will crash without SetPatch 1.34 or later. This is noted in the docs. Unfortunately I can make it crash in so many additional circumstances I can't get to the bottom of it. Suffice it to say you can make it crash on an Amiga and MiSTer.

Regardless, the Toccata code seems to work, and manual Zorro III RAM accessibility in 1.3 should probably be addressed in a different thread.

[sorgelig]

Thanks for testing.
I'm not familiar so deep into manual Zorro III adding. May be some details may give me clues.
But why you need Zorro III in KS1.3? Isn't Zorro III appeared in Amiga 4000 where minimum KS was 2.0(or 3.0?).

[sorgelig]

• (I think that is normal and only worked on the A3000 with its RAMsey custom chip)

this is definitely not implemented in the core

[bfbiii]

I believe that's true. A3000 is what I just tested it on. I definitely don't NEED any of these features :-) But I am working on a long-term project that is incredibly personal and extremely, extremely sad, nothing to be sharing here, but it involves working in 1.3 exclusively and making it SHINE. So I end up in corner cases with the machine. It's not necessary for MiSTer, but now it's something out there to possibly be preserved someday :-)

[bfbiii]

I thought about this a bit more and I believe you can take Kickstart 1.3, install it in an A1200 and manually access a 32-bit ram expansion. But I will test that in reality and share it in the forum if there's anything to it. Meanwhile congrats on squashing this bug.

[bfbiii]

I have looked some more into the viability of accessing Zorro III and other 32-bit memory using AmigaDOS 1.3 and this is viable and has historical precedent as well. The RAM design simply needs to have a contingency for such a situation. I will post a feature request with more detail. Meantime, someone with power should probably close this issue. The fix above has been incorporated into the latest release: Minimig_20250203.rbf

[sorgelig]

somehow slipped that nasty PR.