Short:        Accelerator connector/expansion bus test
Author:       photon@scoopex1988.org (Henrik Erlandsson)
Uploader:     photon scoopex1988 org (Henrik Erlandsson)
Type:         util/moni
Version:      1.0
Architecture: m68k-amigaos
Distribution: Aminet
Kurz:         Apollo 1260 Turbokarte Expansion bustest

This was made for testing out issues when running Apollo 1260 @ 100 MHz, 
but can be used with any accelerator with fastmem. If you can run your 
turbo card with no fastmem but it fails when you put in fastmem, you 
can rule out all chips until only the CPU is left, without opening 
your Amiga. One test, fast-f2f, is the stress test for heavy bus use. 
Run it until it stops flashing, 30 minutes should mean you have a 
stable CPU + memory chain and the problem with freezing is due to 
other heavy use, sometimes heavy (overclocked!) FPU use causes CPU 
shutdown due to overheating, for example.

No other component like HDD interface, Indivision, wrong 
Workbench setup etc is involved, because the system is off during 
testing. You can run this from a clean boot CLI with no other command 
than your CPU setup command, if necessary.



Apollo Bus Test
---------------
by H. Erlandsson aka Photon of Scoopex

This was made for testing out issues when running Apollo 1260 @ 100 MHz, 
but of course test the bus on any accelerator (UNLESS there is free 
fastram somewhere else in the machine and it has priority).

The purpose is to run code either internally on the Apollo 1260, copying 
data only using its onboard bus, or do so using the expansion port bus.

With this, you can hopefully test out connector problems or bus logic 
problems running the Apollo at high speeds ( > 80 MHz). Make sure your rig 
works at 80 MHz, and then use this to debug overclocked speeds.


If all 8 combinations work (especially "fast-f2f") and the cpu still hangs 
(colors stop flashing), these problems are eliminated and all that remains 
is the CPU. (Because the RAMs worked at 80 MHz, and they are 60 ns, ie. up 
to spec. So there can be no problem there, all that remains is ensuring 
correct voltage and amperage (use a 400W+ PSU with 20+A on 5V and 3.3V, and 
make sure 5V is >=5.0V under load), and check the cooling.)


It turns off the system, copies 128K of data over cache boundaries and 
executes the code to do that in either chipmem or fastmem.

USAGE:
Start with fast-f2f. This runs code completely internally on the Apollo.

Run this for at least 10 minutes, if the colors stop flashing, note the time.

Then run fast-f2c. If it runs the full 10 minutes, the problem is not with 
the bus (ie. connector/bus chip).

The other 6 combos are there for whatever fault-searching you want to use 
them for. "fast-f2f" stresses the CPU the most while not using the expansion 
bus, and all others use it, and "chip-c2c" stresses the CPU the least doing so.

/Photon


