Local slot autoconfig - how?

[Heiroglyph]

Interestingly, the Warp Engine 040 seems to be faking Z3 for the SCSI.

It's mapped as the first Zorro3 card in the Z3 address space and its configuration information looks just like a Zorro3 card.

I guess that validates one way of doing it.

Looks like the Cyberstorm MK3 uses the diagnostic ROM area to configure like Toni suggested.

Since pretty much everything has to work with the Cyberstorms and it doesn't take up zorro 3 space, that sounds like the direct, easy way to go.

No weird address changes needed either.

[billt]

The change log for KS3.1 says they expanded the memory check to add an additional 3x256MB, but I haven't tested it on hardware yet.

I'm not planning to use RAMSLOT though, I'd rather decode it myself.

I wonder if 3.5/3.9 updates changed anything further?

Where does one read about this ramslot n 3.1 etc?

[Heiroglyph]

I can't remember where I found it, but it's in the kickstart 3.1 change log.

Here is the part for expansion library:

Code: [Select]

expansion 40.2

    - New - A1200 specific build that can detect CPU Slot RAM ($08000000)
if you have a 32-bit addressing CPU installed.  The CPU slot area
is 128meg in size (just like the A3000) but has the addition of
a wrap check at each 1meg of space in the CPU address space to make
low-cost RAM expansion possible without jumpers.  (It is now possible
to get 128Meg SIMMs so a single SIMM on a CPU card could make a
128Meg of FAST RAM system )

The reason that this has to be A1200 specific (at least for now)
is that the behavior of the existing A500/A2000 CPU cards with
respect to 32-bit addresses is very undefined.  They act very
strangely and differently making it very difficult to safely figure
out if these cards are operating correctly or not.

No code changes for anything but the new A1200 version of the
library.  (39.8)

    - Bumped version to V40.  (40.1)

    - Two major bugs found in the A3000 memory test/CPU Card test.
Both were fixed.  (40.1)

    - CPU Card space is now able to be more than 128Meg.  (We can grab
3 * 256Meg more since we don't start Zorro-III until $40000000
anyway...)  (40.1)

    - CPU Card space test now also does mirror testing.  (40.1)

    - Due to the fixes, some forms of the code have gotten a bit smaller,
specifically, the A3000, A4000, and A1200 versions.  (40.1)

    - Reworked the memory test to deal with extra-high capacitance
bus systems.  (40.2)

Accidentally posted too early...

RAMSLOT seems to just be a chip select.  I'm not sure why you wouldn't just decode it yourself, it seems of little help.

[Zac67]

_RAMSLOT saves you the hassle of decoding yourself, of course it's possible (you'll need to block _AS to the motherboard though to make sure nobody else is answering).

[Heiroglyph]

That really only tells me that the access is in the local slots range and as far as I know I'd have to wait on the 25mhz ramsey instead of running at full CPU speed for local accesses.

The local slot docs even mention that if speed is a concern (when isn't it?) you should decode it yourself and ignore RAMSLOT.

[Zac67]

True. When you're not running synchronously to the mobo it doesn't make sense anyway.

[mousehouse]

This thread is a very nice read for someone who is trying to get some level of understanding about the Amiga hardware, AUTOCONFIG, etc.

I could only find the local slot documentation here:
http://www.thule.no/haynie/systems/amiga3k/docs/a3kcpu.pdf

Is there any additional documentation available that anybody is willing to share?

@Heiroglyph, curious to hear what you're working on!

[Oli_hd]

First an unrelaited fact I got from a guy at Amitrix about a ram card they were working on.
The CDTV's diagnostic connector doesnt have autoconfig and they added the memory by having a timed delay so after x milliseconds any read from the autoconfig address is taken as being aimed at the card.
Now I would think there was a time out on the autoconfig process but as the cfg line is simply passed from board to board there may not be.

The second way is to assume before presenting the first board with a cfgin sig it looks at the autoconfig address and sees if anythings there. It would account for any CPU slot board being first on the list .

As for the ram CS line on the fast slot, still use it as that 128Meg is fixed and if not used you have lost 128Meg of address space for no reason.

[Zac67]

Since you're living on our own bus you can simply emulate autoconfig for your onboard devices and start to pass it to the mainboard once you're done (think we had that before) - no need for hacks.

That CDTV hack you mention seems to be faking autoconfig where it isn't possible for real (pretty dumb to miss that since autoconfig just takes a single gate per slot). There must be a little more to it than that - you'll need to do the fake after the last (real) board is configured (otherwise they'd be trying to configure simultaneously) - I guess it isn't too easy to detect the last board but there probably is a pattern to react to.

_CFGIN doesn't time out, it's more beautiful than that. _CFGIN is driven by the previous _CFGOUT ORed with the previous(!) _CFGIN. _CFGOUT is pulled low by the mainboard but driven high by an unconfigured board - that way delaying the _CFGIN for the next board if present.