Sonnet 7200 PCI programming - Page 237

Hedeon · 08 May 2021, 13:33

Nice. So it is a MPC8314E. Address range and size seem wrong though.

trixster · 08 May 2021, 14:03

Do you need anymore information?

Hedeon · 08 May 2021, 14:55

Not really. Those chips don't work with warp3d and prometheus (well, at least the MPC8343E does not) and I am not going to send back and forth beta libs to try to implement something I don't have here.

trixster · 08 May 2021, 15:00

No probs! Happy to shove this board in the post, but I guess if you don't have one yourself it's not much point spending the time and effort to implement support. They dont fit in the case in any case, too wide!

Hedeon · 08 May 2021, 15:02

Having said that I saw one for sale from Germany for 25 Euros, so what the hell..

trixster · 08 May 2021, 15:14

ha, great!

Hedeon · 08 May 2021, 15:15

Now looking for AMC to PCIe carrier card.

Hedeon · 08 May 2021, 15:34

Quote:

Originally Posted by trixster

Do you need anymore information?

Give me a prmscan output and a serial output with this lib if you can, please.

trixster · 08 May 2021, 16:15

sashimi is the best i can do for serial output, it gives info when openpciinfo runs

Code:

openpciinfo
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 : 1, Func Num : 0 
Vendor   : 3dfx Interactive Inc 
Device   : Voodoo3 All Voodoo3 chips, 3000
VendorID : $121a 
DeviceID : $5
ClassCode: 0x030000
IRQNumber: 5
MemAddr0 : $62000000 - $63ffffff 32768 kbytes
MemAddr1 : $60000000 - $61ffffff 32768 kbytes
IOAddr2  : $7fe01000 - $7fe010ff 256 bytes
RomAddr  : $64000000 - $6400ffff
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 : $1957 
DeviceID : $b6
ClassRevision : $0b200012 
PCI_REVISION_ID $12
Header Type : $00 (0=Normal/1=Bridge/2=Cardbus)
PCI_SUBSYSTEM_ID $1103
Command : $0006 
Memory space PCI_COMMAND_MEMORY
Bus mastering PCI_COMMAND_MASTER
PCI_LATENCY_TIMER : $00
----------------------------------
Pci Device Slot Num : 0, Func Num : 0 
Vendor   :  
Device   :  
VendorID : $1957 
DeviceID : $b6
ClassCode: 0x0b2000
IRQNumber: 0
MemAddr0 : $70000000 - $700fffff 1024 kbytes
MemAddr1 : $68000000 - $6fffffff 131072 kbytes
Bus Master Capable
Card PCI_STATUS
Doesn't support 66 Mhz PCI 2.1 bus
Doesn't accept fast-back to back
What's Enabled in the Card ?
Memory space PCI_COMMAND_MEMORY
Bus mastering PCI_COMMAND_MASTER

----------------------------------
Internal Configuration Space infos
VendorID : $12d8 
DeviceID : $e111
ClassRevision : $06040002 
PCI_REVISION_ID $02
Header Type : $01 (0=Normal/1=Bridge/2=Cardbus)
Command : $0000 
PCI_LATENCY_TIMER : $80
----------------------------------
Pci Device Slot Num : 2, Func Num : 0 
Vendor   : Pericom Semiconductor 
Device   :  
VendorID : $12d8 
DeviceID : $e111
ClassCode: 0x060400
IRQNumber: 0
No Bus Master Capable
Card PCI_STATUS
Support 66 Mhz PCI 2.1 bus
Accept fast-back to back
What's Enabled in the Card ?
2048bytes MEM_PCI DMA Mem Allocated : 60dfbc00
16384bytes MEM_PCI DMA Mem Allocated : 60dfc400
Free Mem 2048
2040bytes MEM_NONCACHEABLE DMA Mem Allocated : 60dfbc00
Free Mem 2040
4096bytes MEM_NONCACHEABLE DMA Mem Allocated : 60e00400
Free Mem 4096
Free Mem 16384
300000 bytes MEM_NONCACHEABLE DMA Mem Allocated : 60dfbc00
Free Mem 300000

11/0.System:> 

prmscan

Prmscan 1.6 by Grzegorz Kraszewski.
PCI cards listing:
-------------------------------------------------
Board in slot 1, function 0
Vendor: 3dfx Interactive Inc
Device: Voodoo3 All Voodoo3 chips, 3000
Revision: 1.
Device class 03, subclass 00.
Address range: 62000000 - 63FFFFFF (32 MB).
Address range: 60000000 - 61FFFFFF (32 MB).
Address range: 7FE01000 - 7FE010FF (256 B).
64 kB of ROM at 64000000 - 6400FFFF.
Board driver: 3dfxVoodoo.chip.
-------------------------------------------------
Board in slot 0, function 0
Vendor: 

Device: unknown ($00B6)
Revision: 18.
Device class 0B, subclass 20.
Address range: 70000000 - 700FFFFF (1 MB).
Address range: 68000000 - 6FFFFFFF (128 MB).
Board driver: NONE.
-------------------------------------------------
Board in slot 2, function 0
Vendor: Pericom Semiconductor
Device: unknown ($E111)
Revision: 2.
Device class 06, subclass 04.
Board driver: NONE.
-------------------------------------------------


10/0.System:> 


sashimi
Sashimi installed ([Ctrl]+C or "Break 9" to remove)
Prm_ReadConfigLong offset 0x8 result 0x3000001
Prm_ReadConfigWord offset 0x4 result 0x3
Prm_ReadConfigByte offset 0x3C
Prm_ReadConfigLong offset 0x10 result 0x2000000
Prm_ReadConfigLong offset 0x14 result 0x8
Prm_ReadConfigLong offset 0x18 result 0x1001
Prm_ReadConfigLong offset 0x1C result 0x0
Prm_ReadConfigLong offset 0x20 result 0x0
Prm_ReadConfigLong offset 0x24 result 0x0
Prm_ReadConfigLong offset 0x8 result 0xB200012
Prm_ReadConfigWord offset 0x4 result 0x6
Prm_ReadConfigByte offset 0x3C
Prm_ReadConfigLong offset 0x10 result 0x10000000
Prm_ReadConfigLong offset 0x14 result 0x8000000
Prm_ReadConfigLong offset 0x18 result 0xFF00000C
Prm_ReadConfigLong offset 0x1C result 0xFFFFFFFF
Prm_ReadConfigLong offset 0x20 result 0xFFFFC004
Prm_ReadConfigLong offset 0x24 result 0xFFFFFFFF
Prm_ReadConfigLong offset 0x8 result 0x6040002
Prm_ReadConfigWord offset 0x4 result 0x0
Prm_ReadConfigByte offset 0x3C
Prm_ReadConfigLong offset 0x10 result 0x0
Prm_ReadConfigLong offset 0x14 result 0x0
Prm_ReadConfigLong offset 0x18 result 0x10100
Prm_ReadConfigLong offset 0x1C result 0x101
Prm_ReadConfigLong offset 0x20 result 0x10100400
Prm_ReadConfigLong offset 0x24 result 0x10001
Prm_ReadConfigWord offset 0x0 result 0x121A
Prm_ReadConfigWord offset 0x2 result 0x5
Prm_ReadConfigLong offset 0x8 result 0x3000001
Prm_ReadConfigByte offset 0x8
Prm_ReadConfigByte offset 0xE
Prm_ReadConfigWord offset 0x2E result 0x57
Prm_ReadConfigWord offset 0x4 result 0x3
Prm_ReadConfigByte offset 0xD
Prm_ReadConfigWord offset 0x6 result 0x90
Prm_ReadConfigWord offset 0x4 result 0x3
Prm_ReadConfigWord offset 0x0 result 0x1957
Prm_ReadConfigWord offset 0x2 result 0xB6
Prm_ReadConfigLong offset 0x8 result 0xB200012
Prm_ReadConfigByte offset 0x8
Prm_ReadConfigByte offset 0xE
Prm_ReadConfigWord offset 0x2E result 0x1103
Prm_ReadConfigWord offset 0x4 result 0x6
Prm_ReadConfigByte offset 0xD
Prm_ReadConfigWord offset 0x6 result 0x10
Prm_ReadConfigWord offset 0x4 result 0x6
Prm_ReadConfigWord offset 0x0 result 0x12D8
Prm_ReadConfigWord offset 0x2 result 0xE111
Prm_ReadConfigLong offset 0x8 result 0x6040002
Prm_ReadConfigByte offset 0x8
Prm_ReadConfigByte offset 0xE
Prm_ReadConfigWord offset 0x4 result 0x0
Prm_ReadConfigByte offset 0xD
Prm_ReadConfigWord offset 0x6 result 0x82B0
Prm_ReadConfigWord offset 0x4 result 0x0

Hedeon · 08 May 2021, 16:26

Nice! Could you read and write from the 128mb range?

trixster · 08 May 2021, 16:31

i'm not sure quite how to do that?

I ran bustest on the range 68000000-6fffffff and it seemed to work - showed that speed was 6.6MB/s for read and write

Hedeon · 08 May 2021, 17:13

I meant use a hex editor, write something and read it back to see if the memory is usable.

torsti76 · 08 May 2021, 20:55

I decided to try and fix all hardware problems of my machine first. Will hopefully be back with better debug info in a few days.

jbenam · 08 May 2021, 21:46

Any idea if the cheap PXE8112 based adapters might work?

@trixter and @torsti76
What kind of PLX chips have your bridges got?

Thanks.

torsti76 · 08 May 2021, 22:13

This is with my spare Voodoo, 'screen' as terminal in Linux, and a PCI-E USB3.1 card in the PCI-PCIE-bridge:

Code:

[AddBus] busnr: 0, parentbusnr: 0
[ConfigurePrometheus] scanning bus slot: 0, cfspace: 0x5FC10000
[ConfigurePrometheus] pb_BridgeCnt: 1
We found a graphic card!
QueryCard 0x5FC10000
[AddRequest] pb 0x71BE210, pbus 0x7222D18, size 0x2000000, pri 25, type 0, tag 0x7222D9C, reg 0x5FC10010
nodepri 25
[AddRequest] pb 0x71BE210, pbus 0x7222D18, size 0x2000000, pri 25, type 2, tag 0x7222DAC, reg 0x5FC10014
nodepri 26
[QueryCard] memsize: 0x100
[AddRequest] pb 0x71BE210, pbus 0x7222D18, size 0x100, pri 8, type 1, tag 0x7222DBC, reg 0x5FC10018
nodepri 8
[AddRequest] pb 0x71BE210, pbus 0x7222D18, size 0x10000, pri 16, type 0, tag 0x7222DFC, reg 0x5FC10030
nodepri 16
conf: 0x5FC10000 bus: 0, slot: 0
[ConfigurePrometheus] scanning bus slot: 1, cfspace: 0x5FC20000
[ConfigurePrometheus] pb_BridgeCnt: 1
QueryCard 0x5FC20000
[QueryCard] memsize: 0x100
[AddRequest] pb 0x71BE210, pbus 0x7222D18, size 0x100, pri 8, type 1, tag 0x7222F1C, reg 0x5FC20010
nodepri 8
[AddRequest] pb 0x71BE210, pbus 0x7222D18, size 0x100, pri 8, type 0, tag 0x7222F2C, reg 0x5FC20014
nodepri 8
[AddRequest] pb 0x71BE210, pbus 0x7222D18, size 0x10000, pri 16, type 0, tag 0x7222F7C, reg 0x5FC20030
nodepri 16
conf: 0x5FC20000 bus: 0, slot: 1
[ConfigurePrometheus] scanning bus slot: 2, cfspace: 0x5FC40000
[ConfigurePrometheus] Found a PCI-PCI Bridge. BusNr: 1
[AddBus] busnr: 1, parentbusnr: 0
[ConfigurePrometheus] pbusnr: 0, busnr: 1
[ScanBus] scanning bus slot: 0, cfspace: 0x5FD10000
[ScanBus] scanning bus slot: 1, cfspace: 0x5FD10800
[ScanBus] scanning bus slot: 2, cfspace: 0x5FD11000
[ScanBus] scanning bus slot: 3, cfspace: 0x5FD11800
[ScanBus] scanning bus slot: 4, cfspace: 0x5FD12000
[ScanBus] scanning bus slot: 5, cfspace: 0x5FD12800
[ScanBus] scanning bus slot: 6, cfspace: 0x5FD13000
[ScanBus] scanning bus slot: 7, cfspace: 0x5FD13800
[ScanBus] scanning bus slot: 8, cfspace: 0x5FD14000
[ScanBus] scanning bus slot: 9, cfspace: 0x5FD14800
[ScanBus] scanning bus slot: 10, cfspace: 0x5FD15000
[ScanBus] scanning bus slot: 11, cfspace: 0x5FD15800
[ScanBus] scanning bus slot: 12, cfspace: 0x5FD16000
[ScanBus] scanning bus slot: 13, cfspace: 0x5FD16800
[ScanBus] scanning bus slot: 14, cfspace: 0x5FD17000
[ScanBus] scanning bus slot: 15, cfspace: 0x5FD17800
[ScanBus] scanning bus slot: 16, cfspace: 0x5FD18000
[ScanBus] scanning bus slot: 17, cfspace: 0x5FD18800
[ScanBus] scanning bus slot: 18, cfspace: 0x5FD19000
[ScanBus] scanning bus slot: 19, cfspace: 0x5FD19800
[ScanBus] scanning bus slot: 20, cfspace: 0x5FD1A000
[ScanBus] scanning bus slot: 21, cfspace: 0x5FD1A800
[ScanBus] scanning bus slot: 22, cfspace: 0x5FD1B000
[ScanBus] scanning bus slot: 23, cfspace: 0x5FD1B800
[ScanBus] scanning bus slot: 24, cfspace: 0x5FD1C000
[ScanBus] scanning bus slot: 25, cfspace: 0x5FD1C800
[ScanBus] scanning bus slot: 26, cfspace: 0x5FD1D000
[ScanBus] scanning bus slot: 27, cfspace: 0x5FD1D800
[ScanBus] scanning bus slot: 28, cfspace: 0x5FD1E000
[ScanBus] scanning bus slot: 29, cfspace: 0x5FD1E800
[ScanBus] scanning bus slot: 30, cfspace: 0x5FD1F000
[ScanBus] scanning bus slot: 31, cfspace: 0x5FD1F800
[ConfigurePrometheus] pb_BridgeCnt: 2
QueryCard 0x5FC40000
conf: 0x5FC40000 bus: 0, slot: 2
[ConfigurePrometheus] scanning bus slot: 3, cfspace: 0x5FC80000
[ConfigurePrometheus] pb_BridgeCnt: 2
WriteAddresses
[WriteAddresses] Bus 0 count 7
[WriteAddresses] Pri: 26, addr: 0x0, bus: 0
[WriteAddresses] Pri: 25, addr: 0x2000000, bus: 0
[WriteAddresses] Pri: 16, addr: 0x4000000, bus: 0
[WriteAddresses] Pri: 16, addr: 0x4010000, bus: 0
[WriteAddresses] Pri: 8, addr: 0x4020000, bus: 0
[WriteAddresses] Pri: 8, addr: 0x4020000, bus: 0
[WriteAddresses] Pri: 8, addr: 0x4020000, bus: 0
[WriteAddresses] Bus 1 count 0

So, apparently the bridge is found and scanned. @Hedeon does it detect the USB card ?

Hedeon · 08 May 2021, 22:22

No, it does not.

torsti76 · 08 May 2021, 23:38

Quote:

Originally Posted by jbenam

Any idea if the cheap PXE8112 based adapters might work?

@trixter and @torsti76

What kind of PLX chips have your bridges got?

Thanks.

Mine has written on it:

P17C9X
111SLBFDE
1738GT

It's not for PMC cards but for PCI-E

Hedeon · 08 May 2021, 23:57

Updated the libraries (See first post). Added support for the PCIe Bigfoot 2100 NIC without having one to my disposal so it probably won't work.

But if you want to test, use the debug versions (with sashimi).

trixster · 09 May 2021, 00:17

output from debug versions of libs:

Code:

sashimi
Sashimi installed ([Ctrl]+C or "Break 9" to remove)
Started Library Init routine
Version: $VER: powerpc.library 17.14 beta (08.05.21)

Detected Firestorm/Firebird PCI bridge
Opening of support libraries completed
3DFX card detected, Gfx address at 60000000, config address at 62000000
Size of Gfx card in PCI memory is 02000000
Detected e300 based PPC PCI card
Prm_ReadConfigWord offset 0x4 result 0x6
Prm_WriteConfigWord offset 0x4 data 0x6
Setting up 08000000 of PPC memory at 68000000
Setting up PPC card config base at 70000000
Setting up VGA PCI window at C0000000 located from 00000000 with size 800FE000
Setting up VGA config block for 3DFX Voodoo located at 62000000
Waiting on PPC card to respond

'PowerPC CPU not responding' comes up

Hedeon · 09 May 2021, 01:03

Have to wait till I get mine then.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WANTED: PCI Sound Card VORTEX2 SuperQuard / SQ2500 or Turtlebeach SantaCruz pci card	keropi	MarketPlace	12	15 March 2017 02:48
Wanted:Sonnet Technologies QuadDoubler 50 (Doubler 4000)	kronuz	MarketPlace	0	16 June 2013 00:29
eBay : Sonnet Quaddoubler	alexh	MarketPlace	3	07 May 2013 00:50
Overlay problem on GeForce 7200	Leandro Jardim	support.WinUAE	1	10 August 2010 15:50
Prometheus PCI & Voodoo 3 PCI GFX Card	Slayer	support.Hardware	21	05 September 2006 10:57

08 May 2021, 13:33	#4721
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Nice. So it is a MPC8314E. Address range and size seem wrong though.

08 May 2021, 14:03	#4722
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,337	Do you need anymore information?

08 May 2021, 14:55	#4723
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Not really. Those chips don't work with warp3d and prometheus (well, at least the MPC8343E does not) and I am not going to send back and forth beta libs to try to implement something I don't have here.

08 May 2021, 15:00	#4724
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,337	No probs! Happy to shove this board in the post, but I guess if you don't have one yourself it's not much point spending the time and effort to implement support. They dont fit in the case in any case, too wide!

08 May 2021, 15:02	#4725
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Having said that I saw one for sale from Germany for 25 Euros, so what the hell..

08 May 2021, 15:14	#4726
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,337	ha, great!

08 May 2021, 15:15	#4727
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Now looking for AMC to PCIe carrier card.

08 May 2021, 16:26	#4730
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Nice! Could you read and write from the 128mb range?

08 May 2021, 16:31	#4731
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,337	i'm not sure quite how to do that? I ran bustest on the range 68000000-6fffffff and it seemed to work - showed that speed was 6.6MB/s for read and write

08 May 2021, 17:13	#4732
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	I meant use a hex editor, write something and read it back to see if the memory is usable.

08 May 2021, 20:55	#4733
torsti76 Registered User Join Date: May 2018 Location: Germany, Baden-Wuerttemberg Posts: 387	I decided to try and fix all hardware problems of my machine first. Will hopefully be back with better debug info in a few days.

08 May 2021, 21:46	#4734
jbenam Italian Amiga Zealot Join Date: Jan 2009 Location: Italy Age: 36 Posts: 1,910	Any idea if the cheap PXE8112 based adapters might work? @trixter and @torsti76 What kind of PLX chips have your bridges got? Thanks.

08 May 2021, 22:22	#4736
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	No, it does not.

08 May 2021, 23:57	#4738
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Updated the libraries (See first post). Added support for the PCIe Bigfoot 2100 NIC without having one to my disposal so it probably won't work. But if you want to test, use the debug versions (with sashimi).

09 May 2021, 01:03	#4740
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Have to wait till I get mine then.

Currently Active Users Viewing This Thread: 2 (0 members and 2 guests)