Sonnet 7200 PCI programming

[grelbfarlk]

Originally Posted by klx300r

works amazing on my X1000 thanks

How does CandyFactoryPro run?

[jbenam]

(from another thread, talking about PCIe PowerPC)

Originally Posted by Hedeon

I can't seem to find the 128MB memory on those cards. I see the ROM and some 64k RAM. And the configuration block of the PCI-CPU bridge. So there where it is stuck atm. Plus the Prometheus needs an arbiter update as it is too strict on bus time-outs.

Which PCIe PowerPC are you referring to? The Killer 2100 NIC?

[Hedeon]

Originally Posted by jbenam

(from another thread, talking about PCIe PowerPC)

Which PCIe PowerPC are you referring to? The Killer 2100 NIC?

Yes.

[jbenam]

Originally Posted by Hedeon

Yes.

Dang, I even bought the Startech PCIe to PCI adapter for it some months ago

I thought it was working on the Prometheus, though?

[Hedeon]

Originally Posted by jbenam

Dang, I even bought the Startech PCIe to PCI adapter for it some months ago

I thought it was working on the Prometheus, though?

The card is seen and configured exactly the same as on my X5000.

But if you mean by working access to the CPU and RAM, then no.

[jbenam]

Originally Posted by Hedeon

The card is seen and configured exactly the same as on my X5000.

But if you mean by working access to the CPU and RAM, then no.

Went back ten pages and it seems I somehow misread what you wrote back then. Oh well, fingers crossed that you can somehow get it to work one of these days.

[cloverskull]

Hey friends, I found some older posts discussing Amithlon, but I wanted to touch base again since it looks like there's been a lot of discussion since. Is it hypothetically possible to use the Sonnet project with an Amithlon? I have hardware to build and test things on hand here.

My motivation for doing so is because I personally feel that coupling this project with Amithlon is pretty consistent with the spirit of this project in general...find more common alternatives to rare/expensive Amiga gear for running classic software.

Thanks!

[grelbfarlk]

Does Amithlon work with the current version of the pci.library from Elbox?

In relation to the other thread, there are lots and lots of brand new 1GHz+ PPC chips available. In addition there are finished, purchasable newly manufactured PPC PCIe cards today. Some people were waiting on a definitive answer whether the PPC PCIe cards were feasible before blowing some cash on test boards.

[cloverskull]

I think Amithlon basically uses openpci type logic to communicate through the linux kernel directly with the PCI hardware. I could be wrong, but this is my understanding.

I think the long pole in the tent for getting a true hardware rig up and running these days isn't PPC cards any more, it's actually big box Amigas. It seems like the only moderately common hardware someone can expect to find in decent shape nowadays is an A1200, or a DIY Amithlon rig. I've had PPC hardware for years waiting to find a suitable big box Amiga :P

[Jpor]

Originally Posted by grelbfarlk

Does Amithlon work with the current version of the pci.library from Elbox?

The Elbox PCI.library is proprietary to Mediators. So the answer to your question is no.

You can’t also use openpci with Mediators either. Also tried on G-REX that I have and no Dice.

[jbenam]

Originally Posted by Jpor

You can’t also use openpci with Mediators either. Also tried on G-REX that I have and no Dice.

It most certainly worked with Mediators until a certain point. Then I seem to remember that Elbox did some shenanigans (cease and desist?) and OpenPCI stopped supporting them.

IIRC OpenPCI supports/supported G-REX as well.

[grelbfarlk]

I wasn't sure what Amithlon used for a pci.library that they emulated, unless Amithlon has its own x86 pci.library? I thought it supported openpci at one point but didn't know what was supported as an emulated PCI environment or how that worked.

[neocdtv2]

Have somebody maybe tried the following setup:
1. Amiga 1200
2. Micronik Busboard 6.7 Zorro 3
3. Mediator for Zorro 3 (http://eu-shop.elbox.com/en_GB/p/Med...T-3V-MK-IV/623)
4. A3660

I'm still missing some components to test, mainly a3660 and Mediator. And other expenses got priority, so not sure when i will all of the components. But then I could test it

[spudje]

Si, I'm finally ready to build my AA3000+ setup.

I have the following:
AA3000+ 16 MB FastRAM 3.2.1 ROM
CSMk2 060 128 MB
External SCSI2SD v5.5
Firebird Prometheus PCI DB
Apocalypse PPC PCI
Voodoo 3 PCI
Ethernet PCI

What is the latest software I need for:
- Prometheus library
- sonnet library/ppc library
- Voodoo & ethernet drvers for prometheus

Thanks!

[spudje]

Never mind, I think I collected all needed files on this forum.

[spudje]

Deja-vu... pfff

OK, so I guess now I can revert back to this thread

I have my AA3000+ system (see post #4974 http://eab.abime.net/showpost.php?p=...postcount=4974) running in such a way it runs GearsPPC (full screen)

No MMU libs installed yet.

Things that go wrong:
- GearsPPC windowed gives me memory error (and orange guru (0100 0009), see image.

- Wipeout gives screen corruption in 800x600, see image. It works fine in 640x480, but gurus (8000 0004) after around 15 minutes. Different behaviour than on my A4k where it simply froze the screen. However may still be heat related. I have no AHI installed yet and sound is corrupted too, but I remember that from earlier and iirc AHI fixes this.

- Quake 2 I struggle to get running. I have latest gl quake, a QuakeGUI tool and when I double click the quake2 executable it loads but then I get a dark grey screen and nothing happens anymore. I guess this game needs to be started differently and i Forgot how. (Yes I have the actual game data on there as well )

Are there any ENVARCs I need to set. Can I still rely on this guide with my setup https://github.com/Sakura-IT/SonnetA...ki/Good-Config and ignore the mediator part? Are there any prometheus ENVARCs to set, next to the DMAsize=2048 tooltype which I've set in the prometheus voodoo monitor driver.

Thanks!!

Version, showconfig, pci info, etc.

- Latest Prometheus firmware for Firestorm (E3B)
- PrmLibs41 from Hedeon
- prm-rtl8029.device 1.3
- openpci_8139.device 1.2b4
- OP-FM801v0.9b (sound)
- prmscan 1,6
- DMAlist 1.2

----------------------------

Prometheus DMA memory lister v 1.2
DMA memory detected, block listing...

Start End Size Owner
---------------------------------------------------------------
$40DFCC00 $40E07FFF 46080
$40E08000 $40FFCBFF 2051072 FREE
---------------------------------------------------------------

----------------------------

*** Warp 3D files versions: ***

Warp3D.library - ver.4.2 (67648 bytes)
Warp3DPPC.library - ver.4.2 (100852 bytes)

*** Warp 3D for A3/4000 files versions: ***

W3D_Picasso96.library - ver.4.2 (38664 bytes)
W3D_Picasso96_PPC.library - ver.4.2 (20508 bytes)
W3D_AvengerBE.library - ver.4.2 (295716 bytes)
W3D_AvengerBE_PPC.library - ver.4.2 (392596 bytes)
W3D_AvengerLE.library - ver.4.2 (282312 bytes)
W3D_AvengerLE_PPC.library - ver.4.2 (359436 bytes)

rtg.library - ver.42.1226 (232464 bytes)
emulation.library - ver.41.493 (36540 bytes)
Picasso96API.library - ver.2.407 (24628 bytes)
ahi.device - file N/A
68040.library - ver.46.3 (43924 bytes)
68060.library - ver.46.4 (65128 bytes)
warp.library - file N/A
ppc.library - file N/A

----------------------------

OpenPciInfo v1.5 12.03.2005 by Titan

openpci.library v2.1 opened
Bus Prometheus detected

----------------------------------
Internal Configuration Space infos
VendorID : $121a
DeviceID : $5
ClassRevision : $03000001
PCI_REVISION_ID $01
Header Type : $00 (0=Normal/1=Bridge/2=Cardbus)
PCI_SUBSYSTEM_ID $0057
Command : $0003
I/O space PCI_COMMAND_IO
Memory space PCI_COMMAND_MEMORY
PCI_LATENCY_TIMER : $00
----------------------------------
Pci Device Slot Num : 0, Func Num : 0
Vendor : 3dfx Interactive Inc
Device : Voodoo3 All Voodoo3 chips, 3000
VendorID : $121a
DeviceID : $5
ClassCode: 0x030000
IRQNumber: 5
MemAddr0 : $42000000 - $43ffffff 32768 kbytes
MemAddr1 : $40000000 - $41ffffff 32768 kbytes
IOAddr2 : $5fe01000 - $5fe010ff 256 bytes
RomAddr : $44010000 - $4401ffff
RomSize : 65536 bytes 64 kbytes
No Bus Master Capable
Card PCI_STATUS
Doesn't support 66 Mhz PCI 2.1 bus
Accept fast-back to back
What's Enabled in the Card ?
I/O space PCI_COMMAND_IO
Memory space PCI_COMMAND_MEMORY

----------------------------------
Internal Configuration Space infos
VendorID : $1186
DeviceID : $1300
ClassRevision : $02000010
PCI_REVISION_ID $10
Header Type : $00 (0=Normal/1=Bridge/2=Cardbus)
PCI_SUBSYSTEM_ID $1303
Command : $0007
I/O space PCI_COMMAND_IO
Memory space PCI_COMMAND_MEMORY
Bus mastering PCI_COMMAND_MASTER
PCI_LATENCY_TIMER : $00
----------------------------------
Pci Device Slot Num : 1, Func Num : 0
Vendor : D-Link System Inc
Device : DFE-530TX Fast Ethernet Adapter
VendorID : $1186
DeviceID : $1300
ClassCode: 0x020000
IRQNumber: 0
IOAddr0 : $5fe01100 - $5fe011ff 256 bytes
MemAddr1 : $44000000 - $440000ff 256 bytes
Bus Master Capable
Card PCI_STATUS
Doesn't support 66 Mhz PCI 2.1 bus
Accept fast-back to back
What's Enabled in the Card ?
I/O space PCI_COMMAND_IO
Memory space PCI_COMMAND_MEMORY
Bus mastering PCI_COMMAND_MASTER

----------------------------------
Internal Configuration Space infos
VendorID : $1057
DeviceID : $480b
ClassRevision : $06000002
PCI_REVISION_ID $02
Header Type : $00 (0=Normal/1=Bridge/2=Cardbus)
PCI_SUBSYSTEM_ID $1057
Command : $0007
I/O space PCI_COMMAND_IO
Memory space PCI_COMMAND_MEMORY
Bus mastering PCI_COMMAND_MASTER
PCI_LATENCY_TIMER : $00
----------------------------------
Pci Device Slot Num : 2, Func Num : 0
Vendor : Motorola
Device :
VendorID : $1057
DeviceID : $480b
ClassCode: 0x060000
IRQNumber: 0
MemAddr0 : $44001000 - $44001fff 4 kbytes
MemAddr1 : $44002000 - $44002fff 4 kbytes
MemAddr3 : $44040000 - $4407ffff 256 kbytes
Bus Master Capable
Card PCI_STATUS
Support 66 Mhz PCI 2.1 bus
Accept fast-back to back
What's Enabled in the Card ?
I/O space PCI_COMMAND_IO
Memory space PCI_COMMAND_MEMORY
Bus mastering PCI_COMMAND_MASTER
2048bytes MEM_PCI DMA Mem Allocated : 40e08000
16384bytes MEM_PCI DMA Mem Allocated : 40e08800
Free Mem 2048
2040bytes MEM_NONCACHEABLE DMA Mem Allocated : 40e08000
Free Mem 2040
4096bytes MEM_NONCACHEABLE DMA Mem Allocated : 40e0c800
Free Mem 4096
Free Mem 16384
300000 bytes MEM_NONCACHEABLE DMA Mem Allocated : 40e08000
Free Mem 300000

----------------------------

Prmscan 1.6 by Grzegorz Kraszewski.
PCI cards listing:
-------------------------------------------------
Board in slot 0, function 0
Vendor: unknown ($121A)
Device: unknown ($0005)
Revision: 1.
Device class 03, subclass 00.
Address range: 42000000 - 43FFFFFF (32 MB).
Address range: 40000000 - 41FFFFFF (32 MB).
Address range: 5FE01000 - 5FE010FF (256 B).
64 kB of ROM at 44010000 - 4401FFFF.
Board driver: 3dfxVoodoo.chip.
-------------------------------------------------
Board in slot 1, function 0
Vendor: unknown ($1186)
Device: unknown ($1300)
Revision: 16.
Device class 02, subclass 00.
Address range: 5FE01100 - 5FE011FF (256 B).
Address range: 44000000 - 440000FF (256 B).
Board driver: openpci.library.
-------------------------------------------------
Board in slot 2, function 0
Vendor: unknown ($1057)
Device: unknown ($480B)
Revision: 2.
Device class 06, subclass 00.
Address range: 44001000 - 44001FFF (4 kB).
Address range: 44002000 - 44002FFF (4 kB).
Address range: 44040000 - 4407FFFF (256 kB).
Board driver: NONE.
-------------------------------------------------

[Hedeon]

Looks like DMA memory allocation is screwed up. Try the new prometheus.card and 3dfxvoodoo.chip too. I think it is also attached to post 1 of this thread.

[spudje]

I'm already using them
prometheus.library 4.1
Prometheus.card 7.600
3dfxVoodoo3.chip 7.16

Maybe I set the monitor tooltype wrongly for DMA (DEVS:monitors/voodoo). This is what I did. Used the Cybervision3D monitor, renamed it too voodoo and set depicted tooltypes.

[Hedeon]

Remove the network card. And run the PCI list programs after you have started up the PPC.

[spudje]

As a means to troubleshoot, or as in, forget about the network card