Sonnet 7200 PCI programming

[Hedeon]

No clue. I have the same setup as you. It still tries to access address 0. Maybe snoop dos shows a fail.

[jkdsteve]

Originally Posted by Hedeon

No clue. I have the same setup as you. It still tries to access address 0. Maybe snoop dos shows a fail.

I appreciate you looking and I’ll keep trying.

The one thing failing is pci.library - is that a Mediator thing or is Warp3D looking for gfxbase of Voodoo there?

ppc.library also daily because I’ve renamed the emulation lib for testing.

I found the correct version of AmigaAMP on my other machine and I’ve also got Voxelspace working correctly. Warp68k works well too. My daily chore yesterday was reading this entire thread.

What I’m still puzzled by is the slowdown of Warp PPC Datatypes and possibly the SCSI(this may be a non issue but I’m tired from testing)- you can literally see the difference in refresh.

I saw that datatypes should work, so my only thing left to blame is Amiga 3.2 ROMs

[Hedeon]

The guide tells you when to execute InitPPC in the S-S if you want PPC datatypes to work correctly. Otherwise datatypes get loaded in the wrong memory and the PPC cannot work full speed.

Also, I think they removed the PPC support from picture.datatype. Only the 3.9 one has it.

Failing on pci.library is correct. Not sure which components check for it, but it is normal.

[Hedeon]

Thanks to Pipper, there were some updates to prometheus.card and prometheus.library a week ago or so. I'll upload them soon. Had some trouble putting it on CVS/git so the changelog got messed up. Biggest thing is fixing support for DMA memory other than voodoo3 (S3 Virge and Permedia2 now too) and some other minor stuff. It will not fix your issue with Warp3D however. Seeing the zero access I am thinking you are missing a library.

[jkdsteve]

Originally Posted by Hedeon

The guide tells you when to execute InitPPC in the S-S if you want PPC datatypes to work correctly. Otherwise datatypes get loaded in the wrong memory and the PPC cannot work full speed.

Yes, I used all the help from this thread and when I was helped before setting up my Mediator…believe me this is driving me crazy.

It’s the dither function of the PPC datatype which is slow - if I turn this off it goes super fast but it’s still slower than 060 datatype and WarpOS with the WarpDT on the CSPPC

Originally Posted by Hedeon

Also, I think they removed the PPC support from picture.datatype. Only the 3.9 one has it.

Failing on pci.library is correct. Not sure which components check for it, but it is normal.

At this point I’m considering building 3.9!!!!!

[jkdsteve]

Just for fun, the Warp 3D PPC stuff all runs if I select a standard Amiga screen mode (not P96.)

Wrong p96 version? Maybe it worked with an earlier Prometheus lib/card or 3dfx driver and is now foobar?

Maybe something wrong with my Firebird :-/

[Hedeon]

Not sure what you mean? It works on AGA? That shouldn't be.

[grelbfarlk]

Or do you mean you leave workbench in an AGA mode then start your Warp3D PPC application using the Voodoo then it works?

[jkdsteve]

Originally Posted by grelbfarlk

Or do you mean you leave workbench in an AGA mode then start your Warp3D PPC application using the Voodoo then it works?

StormMesa_Warp3D_PPC demos displays in a window on an AGA workbench…at vastly reduced colours. Verified it’s using the PPC for calculations and probably a lot of the 68k for bitmap writes. Looks like a lot of small 8(?)byte writing.

I just built an OS39 boot disk along with using 3.1 ROMS and Warp3D PPC stuff don’t work on the Voodoo Display - this was my last ditch attempt.

Since I’m using an AA3000+, when the monitor switch kicks in all I get is a grey screen, same as every other attempt. :-/

[jkdsteve]

Originally Posted by grelbfarlk

Or do you mean you leave workbench in an AGA mode then start your Warp3D PPC application using the Voodoo then it works?

Unfortunately, no.

[Hedeon]

You sure you are not using the ppc on the CS? AGA should not work with the PCI cards. The PPC cannot access chip ram.

[Hedeon]

StormMesa has its own libraries too. And might be running in SW mode. Gears_PPC is the real test program.

[jkdsteve]

Originally Posted by Hedeon

StormMesa has its own libraries too. And might be running in SW mode. Gears_PPC is the real test program.

Ah yes, I forgot Mesa will do soft render as a fallback but at least it’s using the PPC

It can't be using the CSPPC because there's no ppc.library available and the only powerpc.library installed is 17.14 from the thread start.

Can’t get any Warp3D PPC hardware stuff to run, it either locks the machine hard or overwrites critical areas (Machine will reboot with 9short and one long power light flash and there’ll usually be a RED screen…)

Looks like this will go back into my Mediator.

[Hedeon]

Originally Posted by jkdsteve

Ah yes, I forgot Mesa will do soft render as a fallback but at least it’s using the PPC

It can't be using the CSPPC because there's no ppc.library available and thee only powerpc.library installed is 17.14 from the thread start.

If you run Mesa and after that do a Getinfo, how many DSI emulations does it say? Can you show a library overview (from Scout or something similar) after InitPPC?

[jkdsteve]

Originally Posted by Hedeon

If you run Mesa and after that do a Getinfo, how many DSI emulations does it say? Can you show a library overview (from Scout or something similar) after InitPPC?

There's a lot of DSIs, increasing the longer the program runs and looks like it doesn't even open Warp3D.library when rendering to Amiga screen mode

CPU: PPC 750 (PVR = 70000203)
CPU clock: 800.000000 MHz
Bus clock: 100.000000 MHz
Instruction Cache: ON and UNLOCKED
Data Cache: ON and UNLOCKED
Page table location: 16F00000
Page table size: 1024 KBytes
PPC Uptime: 60.638793 seconds
CPU load: 0.00%
System load: 0.00%
L2 Cache: ENABLED
L2 State: COPY-BACK
L2 Size: 512 KBytes
FPU Align Emulation: 0 times
DSI Emulation: 13424 times


Address Pri OpenC RPC Name & Version

$08243498 0 1 5 3dfxVoodoo.chip 7.16 68k
$08023BBC 0 1 27 68060.library 46.15 68k
$08437654 0 0 19 amigaguide.datatype 47.26 68k
$08433DFC 0 0 35 amigaguide.library 45.5 68k
$083180B4 0 5 14 asl.library 47.9 68k
$0838C23C 0 3 143 bsdsocket.library 4.347 68k
$08242988 -30 0 12 cgxvideo.library 41.6 68k
$0838BD44 0 0 39 commodities.library 45.2 68k
$082BB5D0 -30 4 40 cybergraphics.library 41.4 68k
$0809D860 0 0 53 datatypes.library 47.3 68k
$08244218 0 0 21 diskfont.library 47.1 68k
$08023488 0 59 193 dos.library 47.23 68k
$08233C2C -30 1 55 emulation.library 40.389 68k
$0800092C -100 3 150 exec.library 47.7 68k
$000046CC -20 10 27 expansion.library 47.1 68k
$08233D20 0 11 29 gadtools.library 47.16 68k
$08013AFC 0 1 179 graphics.library 47.4 68k
$0830EAD0 100 1 13 hid.class 4.5 68k
$082C0600 0 1 13 hub.class 4.5 68k
$082350D4 0 14 34 icon.library 51.4 68k
$08239EA8 0 7 45 iffparse.library 45.3 68k
$0868BAB8 0 1 5 ilbm.datatype 47.6 68k
$0801BA24 0 1 202 intuition.library 47.51 68k
$080189F0 0 1 8 keymap.library 47.1 68k
$080184DC 0 1 42 layers.library 46.2 68k
$08243C70 0 0 36 locale.library 47.29 68k
$0830FDE0 0 1 13 massstorage.class 4.5 68k
$08436170 0 1 16 mathieeedoubbas.library 47.2 68k
$08023AE0 0 1 16 mathieeesingbas.library 47.1 68k
$085ADCA8 0 1 76 mmu.library 46.22 68k
$08437474 0 1 38 muigfx.library 19.9 68k
$08696F28 0 4 33 muilowlevel.library 19.9 68k
$084363AC 0 4 51 muimaster.library 19.35 68k
$08E92670 0 2 13 muirexx.library 19.9 68k
$08054DD0 0 2 5 muiwinborder.class 19.9 68k
$080559C0 0 1 5 NList.mcc 20.147 68k
$08390420 0 1 5 NListview.mcc 19.102 68k
$085AE438 -90 0 24 p5emu.library 46.1 68k. <-what starts this?
$08432A74 0 1 6 picture.datatype 47.15 68k
$08286308 0 4 101 poseidon.library 4.5 68k
$7EEF6C70 0 8 151 powerpc.library 17.14 68k
$08242FB0 0 1 8 Prometheus.card 7.600 68k
$082431D0 0 3 21 prometheus.library 4.2 68k
$0843600C 100 6 86 rexxsyslib.library 47.2 68k
$0823AA7C -70 2 59 rtg.library 40.3945 68k
$084371F4 0 4 10 screennotify.library 1.0 68k
$083918A4 0 2 43 usergroup.library 4.30 68k
$08000250 0 61 76 utility.library 47.3 68k
$08242A84 -30 0 22 vilintuisup.library 2.9 68k
$08497880 0 0 4 warp.library 5.1 68k
$0830571C 0 11 23 workbench.library 47.36 68k

[Hedeon]

OK, I guess the DSI is fast enough to make it work. I once had plans to make it use pages instead of just bytes, words and longs. And update everything when a context switch happened and a write had happened to the page. But seeing 99% now already works good enough, I didn't implement it.

Anyway, I think we are out of options, sadly. The lib list looks correct.

[Hedeon]

Would expect the page table at 17f00000 though.

EDIT, It's the same here. I cannot remember why it isnt at 17f00000. Now there seems to be nothing at 17000000-18000000 which is 16MB.

EDIT2: The I/O and config space of the Prometheus is residing there, now I remember.

[grelbfarlk]

You sure your system is actually stable for non Warp3D apps? You say voxelspace is still crashing.
If you can run that for say an hour without crashes, try to run something demanding like Amigenerator, you don't have to play it but just open Sonic and let it run the demo for an hour without crashes.
If it's still crashing when either of these 2D apps are running you've got other problems. It could be something as simple as a finicky P96 mode.

But if you're getting crashes in simple PPC apps you need to resolve that first before thinking about Warp3D.

[jkdsteve]

Originally Posted by grelbfarlk

You sure your system is actually stable for non Warp3D apps? You say voxelspace is still crashing.
If you can run that for say an hour without crashes, try to run something demanding like Amigenerator, you don't have to play it but just open Sonic and let it run the demo for an hour without crashes.
If it's still crashing when either of these 2D apps are running you've got other problems. It could be something as simple as a finicky P96 mode.

But if you're getting crashes in simple PPC apps you need to resolve that first before thinking about Warp3D.

I thought about trying to create new, simple one mode P96 Settings. I may still try.

Today I just pulled the Voodoo3 and PPC back into my 4k/Mediator and it worked immediately.

The last thing I’m going to do is check with a new power supply with ATX adapter - I’ve seen no signs of it wilting but you never know!!!

AmiGenerator is PPC SEGA emulator? Suppose I have to find ROMs too?

[grelbfarlk]

Well one ROM. Sonic.bin. Or any ROM really.
Or some app that is going to run the CPU at 100% while also drawing a lot, with sound too. Doom is not a bad idea either but run it at 640x480 or whatever mode you're trying to run your Warp3D app at, also with AHI so you know that's not causing any issues either.

The point is, if you are thrashing the CPU and GFX card in 2D for extended periods and have no doubt they are completely stable, then go ahead and try to get Warp3D running.

If that isn't working, well what's the problem then? Probably power, try reseating the power supply to motherboard connector a few times or spray some isopropyl in it. See if this affects the stability at all.
But if it's not that, then maybe just rearranging your cards will make a difference. I don't know about Prometheus but do whatever order Trixster and co are doing.