Sonnet 7200 PCI programming - Page 236

torsti76 · 06 April 2021, 00:31

Quote:

Originally Posted by johnnybarker

Anyone looked at these?

https://www.eaacepr.com/index.php?ma...ucts_id=681004

Looks a pretty dodgy website.

These sites are fake. Ordered a Buster 11 once from a similar site. After 6 weeks pulled my money back through my credit card issuer.

johnnybarker · 06 April 2021, 09:20

Thanks, good to know to avoid it.

Hedeon · 06 May 2021, 03:22

For the AA3000+ people: I looked into the PCI-PCI bridge issues and now at least the Prometheus can see other buses and cards on these buses beyond the bridge.

Did not have many cards to test, however (Exactly 1, a sound card. And it replies as being a bridge. Go figure).

I have to work with old pre-3.1 sources as the final 3.1 sources were lost in a HD crash years ago as far as I understand. In this case, the sources I had read from the wrong PCI CONFIG1 addresses. This was fixed.

This version supports PPC PCI cards unlike the official 3.1 one. I am not sure what is still missing in this version as compared to the final 3.1 version.

torsti76 · 06 May 2021, 07:53

Many thanks for this, @Hedeon ! I really appreciate the pace in which you drive this project and the time and resources you invest into this!

One thing I noticed when comparing the behavior of your (previous) lib version against the "original" 3.1 is that your lib doesn't seem to consider that the Prometheus might be absent from the system.

Let me explain this in more detail:

I've had issues with my AA3000+ recently and did some rework on the board. I then tested it with the installation I've made much earlier, but without the Firebird busboard.
The installation included your prometheus.library from 12/25/2020 as well as a full installation of Picasso96 with the Voodoo stuff.

During testing, tools like "whichamiga" kept crashing. It took me a while to realize that this was due to prometheus.library being in place but no actual Prometheus being found in the system.

Tools like 'showboards' don't crash then, but always show exactly one PCI board with undetermined vendor and product ids. I guess this is some kind of 'placeholder' for the Voodoo, but I'm not sure.

Will try your new version later today for sure! It's still only 1/5 or so the size of the original 3.0 or 3.1 libs, which to me indicates the level of optimization you did to the code.

torsti76 · 06 May 2021, 09:17

On a related note, see attachment. :-) Can try later today if card-bridge combo is seen by the pci scan tools using the new library version.

Have to look after my kids for now...

jbenam · 06 May 2021, 10:27

Quote:

Originally Posted by torsti76

On a related note, see attachment. :-) Can try later today if card-bridge combo is seen by the pci scan tools using the new library version.

I have the same card as well - please let me know if it works on the Prometheus. It might finally be my way out of my PPC years-long nightmare

I'll gladly buy a Prometheus (and sell my Mediator) if that's the case

Hedeon · 06 May 2021, 11:37

I did not really optimize. The 15k prometheus libs were compiled with -DDEBUG I think? I remember seeing debug stuff when I looked into it.

And regarding the crash info, I'll have a look.

torsti76 · 06 May 2021, 14:42

Quote:

Originally Posted by Hedeon

For the AA3000+ people: I looked into the PCI-PCI bridge issues and now at least the Prometheus can see other buses and cards on these buses beyond the bridge.

Just tried with the Bigfoot and the Pericom PCI-PCIE bridge adapter.

prmscan and openpciinfo both list 3 cards (as before) with the last one being the bridge.

Are there any tools required to see beyond the bridge?

Hedeon · 06 May 2021, 16:26

Prmscan output or it didn't happen

Hedeon · 06 May 2021, 20:40

I updated the first post with the current powerpc.library and prometheus.library and their debug equivalents. I'll post updates of the files there from now on.

torsti76 · 06 May 2021, 23:07

Quote:

Originally Posted by Hedeon

Prmscan output or it didn't happen

W/ latest lib from post #1

Hedeon · 07 May 2021, 08:55

Use the debug version with Sashimi, prmscan and without startup sequence. It will give more info

torsti76 · 07 May 2021, 09:04

Quote:

Originally Posted by Hedeon

Use the debug version with Sashimi, prmscan and without startup sequence. It will give more info

I will. If I seem very slow updating the info this is because I have small kids that are out of child care atm. So basically, I can only do testing while they're asleep in the afternoon or at night...

Hedeon · 07 May 2021, 09:40

Also compare with the 15k big prometheus 3.1 library please.

torsti76 · 07 May 2021, 22:52

Debug output using library from post #1:

Code:

0                                                                                        
Cnt: 1t: 0, cfspace: 0x5FC10000                                                          
We found a graphic card![AddRequest] pb 0x71BC468, pbus 0x7222D00, size 0x2000000, pri 2 size 0x2000000, pri 25, type 2, tag 0x74
nodepri 26                                                                               
[QueryCard] memsize: 0x100
[AddRequest] pb 0x71BC46ri 8, type 1, tag 0x7222DA4, regmetheus] scanning bus slot: 1, cometheus] Found a PCI-PCI Bridge. BusNr:1
[AddBus] busnr: 1, parentbusnr: 0
[ConfigurePrometheus] pbusnr: 0, busnr: 1
[ScanBe: 0x5FD10000
[ScanBus] scannin00
[ScanBus] scanning bus slot: 2, cfspace: 0x5FD11000
[ScanBus] scanning bus slot: 3, cfspace bus slot: 4, cfspace: 0x5FD1200] scanning bus slot: 6, cfspace:, cfspace: 0x5FD14000
[ScanBus]0x5FD14800
[ScanBus] scanning bus slot: 10, cfspace: 0x5FD150001, cfspace: 0x5FD15800
[ScanBus: 0x5FD16000
[ScanBus] scanning bus slot: 13, cfspace: 0x5FD168us] scanning bus slot: 15, cfspace: 0x5FD17800
[ScanBus] scanni8000
[ScanBus] scanning bus slot: 17, cfspace: 0x5FD18800
[Scapace: 0x5FD19000
[ScanBus] scanning bus slot: 19, cfspace: 0x5FD19800
[ScanBus] scanning bus s1A800
[ScanBus] scanning bus slot: 22, cfspace: 0x5FD1B000
[ScFD1C000
[ScanBus] scanning bus cfspace: 0x5FD1D000
[ScanBus] s
           [ScanBus] scanning bus slot: 29 scanning bus slot: 30, cfspace: 0x5FD1F000
[ScanBus] scanning 0
[ConfigurePrometheus] pb_BridgeCnt: 2
QueryCard 0x5FC20000
conf: 0x5FC20000 bus: 0, slot: 1
[ConfigurePrometheus] scanning bus slot: 2, cfspace: 0x5FC4000geCnt: 2
[ConfigurePrometheus]  pb_BridgeCnt: 2
WriteAddresses
[WriteAddresses] Pri: 26, addrPri: 25, addr: 0x2000000, bus: 0: 0x4000000, bus: 0
[WriteAddreus: 0
[WriteAddresses] Bus 1 count 0

The screen output on the Amiga itself looks the same, regardless of whether I use the 4.0 or 3.1 lib.

torsti76 · 07 May 2021, 23:02

Just to add, when trying to set up a RTL8139 NIC with OpenPCI, this is the serial output (the system then freezes):

Code:

adConfigByte offset 0x3C
Prm_ReLong offset 0x18 result 0x1001
esult 0x0
esult 0x2000010ong ofnfigLong offset 0x24 result 0x0
Prm_ReadConfigWeadConfigByte offset 0x3C
Prm_Ret 0x14 result 0x4020000
Prm_ReadConfigLong offset 0x18 result ng offset 0x20 result 0x0
Prm_R 0x0
Prm_WriteConfigWord offsetd offset 0x4 result 0x3
Prm_Wri00
Prm_GetPhysicalAddress 0x40F40F7D800
Prm_GetPhysicalAddress 0x40F7E000

Hedeon · 08 May 2021, 00:43

The output is a mess. Half sentences, garbled etc. Doesn't look the same here. And if the 3.1 also does not work for you, then I cannot help any further probably.

The scan of 4.0:

Code:

[AddBus] busnr: 0, parentbusnr: 0
[ConfigurePrometheus] scanning bus slot: 0, cfspace: 0x5FC10000
[ConfigurePrometheus] pb_BridgeCnt: 1
QueryCard 0x5FC10000
[QueryCard] memsize: 0x20
[AddRequest] pb 0x8116680, pbus 0x817CAA0, size 0x20, pri 5, type 1, tag 0x817CB24, reg 0x5FC10010
nodepri 5
conf: 0x5FC10000 bus: 0, slot: 0
[ConfigurePrometheus] scanning bus slot: 1, cfspace: 0x5FC20000
[ConfigurePrometheus] pb_BridgeCnt: 1
We found a graphic card!
QueryCard 0x5FC20000
[AddRequest] pb 0x8116680, pbus 0x817CAA0, size 0x8000000, pri 27, type 2, tag 0x817CC44, reg 0x5FC20010
nodepri 28
[QueryCard] memsize: 0x100
[AddRequest] pb 0x8116680, pbus 0x817CAA0, size 0x100, pri 8, type 1, tag 0x817CC54, reg 0x5FC20014
nodepri 8
[AddRequest] pb 0x8116680, pbus 0x817CAA0, size 0x10000, pri 16, type 0, tag 0x817CC64, reg 0x5FC20018
nodepri 16
[AddRequest] pb 0x8116680, pbus 0x817CAA0, size 0x20000, pri 17, type 0, tag 0x817CCA4, reg 0x5FC20030
nodepri 17
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] Found a PCI-PCI Bridge.
[AddBus] busnr: 2, parentbusnr: 1
Bridge 0 has upper IO support!
[ScanBus] scanning bus slot: 0, cfspace: 0x5FD20000
[ScanBus] scanning bus slot: 1, cfspace: 0x5FD20800
[ScanBus] scanning bus slot: 2, cfspace: 0x5FD21000
[ScanBus] scanning bus slot: 3, cfspace: 0x5FD21800
[ScanBus] scanning bus slot: 4, cfspace: 0x5FD22000
[ScanBus] scanning bus slot: 5, cfspace: 0x5FD22800
[ScanBus] scanning bus slot: 6, cfspace: 0x5FD23000
[ScanBus] scanning bus slot: 7, cfspace: 0x5FD23800
[ScanBus] scanning bus slot: 8, cfspace: 0x5FD24000
[ScanBus] scanning bus slot: 9, cfspace: 0x5FD24800
[ScanBus] scanning bus slot: 10, cfspace: 0x5FD25000
[ScanBus] scanning bus slot: 11, cfspace: 0x5FD25800
[ScanBus] scanning bus slot: 12, cfspace: 0x5FD26000
[ScanBus] scanning bus slot: 13, cfspace: 0x5FD26800
[ScanBus] scanning bus slot: 14, cfspace: 0x5FD27000
[ScanBus] scanning bus slot: 15, cfspace: 0x5FD27800
[ScanBus] scanning bus slot: 16, cfspace: 0x5FD28000
[ScanBus] scanning bus slot: 17, cfspace: 0x5FD28800
[ScanBus] scanning bus slot: 18, cfspace: 0x5FD29000
[ScanBus] scanning bus slot: 19, cfspace: 0x5FD29800
[ScanBus] scanning bus slot: 20, cfspace: 0x5FD2A000
[ScanBus] scanning bus slot: 21, cfspace: 0x5FD2A800
[ScanBus] scanning bus slot: 22, cfspace: 0x5FD2B000
[ScanBus] scanning bus slot: 23, cfspace: 0x5FD2B800
[ScanBus] scanning bus slot: 24, cfspace: 0x5FD2C000
[ScanBus] scanning bus slot: 25, cfspace: 0x5FD2C800
[ScanBus] scanning bus slot: 26, cfspace: 0x5FD2D000
[ScanBus] scanning bus slot: 27, cfspace: 0x5FD2D800
[ScanBus] scanning bus slot: 28, cfspace: 0x5FD2E000
[ScanBus] scanning bus slot: 29, cfspace: 0x5FD2E800
[ScanBus] scanning bus slot: 30, cfspace: 0x5FD2F000
[ScanBus] scanning bus slot: 31, cfspace: 0x5FD2F800
QueryCard 0x5FD10000
conf: 0x5FD10000 bus: 1, slot: 0
[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: 3
QueryCard 0x5FC40000
conf: 0x5FC40000 bus: 0, slot: 2
[ConfigurePrometheus] scanning bus slot: 3, cfspace: 0x5FC80000
[ConfigurePrometheus] pb_BridgeCnt: 3
WriteAddresses
[WriteAddresses] Bus 0 count 5
[WriteAddresses] Pri: 28, addr: 0x0, bus: 0
[WriteAddresses] Pri: 17, addr: 0x8000000, bus: 0
[WriteAddresses] Pri: 16, addr: 0x8020000, bus: 0
[WriteAddresses] Pri: 8, addr: 0x8030000, bus: 0
[WriteAddresses] Pri: 5, addr: 0x8030000, bus: 0
[WriteAddresses] Bus 1 count 0
[WriteAddresses] Bus 2 count 0

And the scan of 3.1 (which shows I need to adapt more of the code of 4.0 to make it similar...except for scaning bus 1 twice...)

Code:

[AddBus] busnr: 0, parentbusnr: 0
[ConfigurePrometheus]
[ConfigurePrometheus] scanning bus slot: 0, cfspace: 0x5FC10000, ht: 0x00, v: 0xEC10, d: 0x2980
[QueryCard] 0x5FC10000
memsize: $20
[QueryCard] conf: 0x5FC10000 bus: 0, slot: 0, func: 0
[ConfigurePrometheus] scanning bus slot: 1, cfspace: 0x5FC20000, ht: 0x80, v: 0x0210, d: 0x6059
We found a graphic card!
[QueryCard] 0x5FC20000
memsize: $100
[QueryCard] conf: 0x5FC20000 bus: 0, slot: 1, func: 0
[QueryCard] 0x5FC20100
[QueryCard] conf: 0x5FC20100 bus: 0, slot: 1, func: 1
[QueryCard] 0x5FC20200
[QueryCard] 0x5FC20300
[QueryCard] 0x5FC20400
[QueryCard] 0x5FC20500
[QueryCard] 0x5FC20600
[QueryCard] 0x5FC20700
[ConfigurePrometheus] scanning bus slot: 2, cfspace: 0x5FC40000, ht: 0x01, v: 0xD812, d: 0x11E1
[ConfigurePrometheus] Found a PCI-PCI Bridge. BusNr: 1
[AddBus] busnr: 1, parentbusnr: 0
[ConfigurePrometheus] pbusnr: 0, busnr: 1
Bridge has upper IO support!
[ScanBus] scanning bus slot: 0, cfspace: 0x5FD10000 ht: 0x00000001
[ScanBus] Found a PCI-PCI Bridge.
[AddBus] busnr: 2, parentbusnr: 1
[ScanBus] Bridge has upper IO support!
[ScanBus] scanning bus slot: 0, cfspace: 0x5FD20000 ht: 0x000000FF
[ScanBus] scanning bus slot: 1, cfspace: 0x5FD20000 ht: 0x000000FF
[ScanBus] scanning bus slot: 2, cfspace: 0x5FD20800 ht: 0x000000FF
[ScanBus] scanning bus slot: 3, cfspace: 0x5FD21000 ht: 0x000000FF
[ScanBus] scanning bus slot: 4, cfspace: 0x5FD21800 ht: 0x000000FF
[ScanBus] scanning bus slot: 5, cfspace: 0x5FD22000 ht: 0x000000FF
[ScanBus] scanning bus slot: 6, cfspace: 0x5FD22800 ht: 0x000000FF
[ScanBus] scanning bus slot: 7, cfspace: 0x5FD23000 ht: 0x000000FF
[ScanBus] scanning bus slot: 8, cfspace: 0x5FD23800 ht: 0x000000FF
[ScanBus] scanning bus slot: 9, cfspace: 0x5FD24000 ht: 0x000000FF
[ScanBus] scanning bus slot: 10, cfspace: 0x5FD24800 ht: 0x000000FF
[ScanBus] scanning bus slot: 11, cfspace: 0x5FD25000 ht: 0x000000FF
[ScanBus] scanning bus slot: 12, cfspace: 0x5FD25800 ht: 0x000000FF
[ScanBus] scanning bus slot: 13, cfspace: 0x5FD26000 ht: 0x000000FF
[ScanBus] scanning bus slot: 14, cfspace: 0x5FD26800 ht: 0x000000FF
[ScanBus] scanning bus slot: 15, cfspace: 0x5FD27000 ht: 0x000000FF
[ScanBus] scanning bus slot: 16, cfspace: 0x5FD27800 ht: 0x000000FF
[ScanBus] scanning bus slot: 17, cfspace: 0x5FD28000 ht: 0x000000FF
[ScanBus] scanning bus slot: 18, cfspace: 0x5FD28800 ht: 0x000000FF
[ScanBus] scanning bus slot: 19, cfspace: 0x5FD29000 ht: 0x000000FF
[ScanBus] scanning bus slot: 20, cfspace: 0x5FD29800 ht: 0x000000FF
[ScanBus] scanning bus slot: 21, cfspace: 0x5FD2A000 ht: 0x000000FF
[ScanBus] scanning bus slot: 22, cfspace: 0x5FD2A800 ht: 0x000000FF
[ScanBus] scanning bus slot: 23, cfspace: 0x5FD2B000 ht: 0x000000FF
[ScanBus] scanning bus slot: 24, cfspace: 0x5FD2B800 ht: 0x000000FF
[ScanBus] scanning bus slot: 25, cfspace: 0x5FD2C000 ht: 0x000000FF
[ScanBus] scanning bus slot: 26, cfspace: 0x5FD2C800 ht: 0x000000FF
[ScanBus] scanning bus slot: 27, cfspace: 0x5FD2D000 ht: 0x000000FF
[ScanBus] scanning bus slot: 28, cfspace: 0x5FD2D800 ht: 0x000000FF
[ScanBus] scanning bus slot: 29, cfspace: 0x5FD2E000 ht: 0x000000FF
[ScanBus] scanning bus slot: 30, cfspace: 0x5FD2E800 ht: 0x000000FF
[ScanBus] scanning bus slot: 31, cfspace: 0x5FD2F000 ht: 0x000000FF
[QueryCard] 0x5FD10000
[QueryCard] conf: 0x5FD10000 bus: 1, slot: 0, func: 0
[ScanBus] scanning bus slot: 1, cfspace: 0x5FD10000 ht: 0x00000001
[ScanBus] Found a PCI-PCI Bridge.
[AddBus] busnr: 2, parentbusnr: 1
[ScanBus] Bridge has upper IO support!
[ScanBus] scanning bus slot: 0, cfspace: 0x5FD20000 ht: 0x000000FF
[ScanBus] scanning bus slot: 1, cfspace: 0x5FD20000 ht: 0x000000FF
[ScanBus] scanning bus slot: 2, cfspace: 0x5FD20800 ht: 0x000000FF
[ScanBus] scanning bus slot: 3, cfspace: 0x5FD21000 ht: 0x000000FF
[ScanBus] scanning bus slot: 4, cfspace: 0x5FD21800 ht: 0x000000FF
[ScanBus] scanning bus slot: 5, cfspace: 0x5FD22000 ht: 0x000000FF
[ScanBus] scanning bus slot: 6, cfspace: 0x5FD22800 ht: 0x000000FF
[ScanBus] scanning bus slot: 7, cfspace: 0x5FD23000 ht: 0x000000FF
[ScanBus] scanning bus slot: 8, cfspace: 0x5FD23800 ht: 0x000000FF
[ScanBus] scanning bus slot: 9, cfspace: 0x5FD24000 ht: 0x000000FF
[ScanBus] scanning bus slot: 10, cfspace: 0x5FD24800 ht: 0x000000FF
[ScanBus] scanning bus slot: 11, cfspace: 0x5FD25000 ht: 0x000000FF
[ScanBus] scanning bus slot: 12, cfspace: 0x5FD25800 ht: 0x000000FF
[ScanBus] scanning bus slot: 13, cfspace: 0x5FD26000 ht: 0x000000FF
[ScanBus] scanning bus slot: 14, cfspace: 0x5FD26800 ht: 0x000000FF
[ScanBus] scanning bus slot: 15, cfspace: 0x5FD27000 ht: 0x000000FF
[ScanBus] scanning bus slot: 16, cfspace: 0x5FD27800 ht: 0x000000FF
[ScanBus] scanning bus slot: 17, cfspace: 0x5FD28000 ht: 0x000000FF
[ScanBus] scanning bus slot: 18, cfspace: 0x5FD28800 ht: 0x000000FF
[ScanBus] scanning bus slot: 19, cfspace: 0x5FD29000 ht: 0x000000FF
[ScanBus] scanning bus slot: 20, cfspace: 0x5FD29800 ht: 0x000000FF
[ScanBus] scanning bus slot: 21, cfspace: 0x5FD2A000 ht: 0x000000FF
[ScanBus] scanning bus slot: 22, cfspace: 0x5FD2A800 ht: 0x000000FF
[ScanBus] scanning bus slot: 23, cfspace: 0x5FD2B000 ht: 0x000000FF
[ScanBus] scanning bus slot: 24, cfspace: 0x5FD2B800 ht: 0x000000FF
[ScanBus] scanning bus slot: 25, cfspace: 0x5FD2C000 ht: 0x000000FF
[ScanBus] scanning bus slot: 26, cfspace: 0x5FD2C800 ht: 0x000000FF
[ScanBus] scanning bus slot: 27, cfspace: 0x5FD2D000 ht: 0x000000FF
[ScanBus] scanning bus slot: 28, cfspace: 0x5FD2D800 ht: 0x000000FF
[ScanBus] scanning bus slot: 29, cfspace: 0x5FD2E000 ht: 0x000000FF
[ScanBus] scanning bus slot: 30, cfspace: 0x5FD2E800 ht: 0x000000FF
[ScanBus] scanning bus slot: 31, cfspace: 0x5FD2F000 ht: 0x000000FF
[QueryCard] 0x5FD10000
[QueryCard] conf: 0x5FD10000 bus: 1, slot: 0, func: 0
[ScanBus] scanning bus slot: 2, cfspace: 0x5FD10800 ht: 0x000000FF
[ScanBus] scanning bus slot: 3, cfspace: 0x5FD11000 ht: 0x000000FF
[ScanBus] scanning bus slot: 4, cfspace: 0x5FD11800 ht: 0x000000FF
[ScanBus] scanning bus slot: 5, cfspace: 0x5FD12000 ht: 0x000000FF
[ScanBus] scanning bus slot: 6, cfspace: 0x5FD12800 ht: 0x000000FF
[ScanBus] scanning bus slot: 7, cfspace: 0x5FD13000 ht: 0x000000FF
[ScanBus] scanning bus slot: 8, cfspace: 0x5FD13800 ht: 0x000000FF
[ScanBus] scanning bus slot: 9, cfspace: 0x5FD14000 ht: 0x000000FF
[ScanBus] scanning bus slot: 10, cfspace: 0x5FD14800 ht: 0x000000FF
[ScanBus] scanning bus slot: 11, cfspace: 0x5FD15000 ht: 0x000000FF
[ScanBus] scanning bus slot: 12, cfspace: 0x5FD15800 ht: 0x000000FF
[ScanBus] scanning bus slot: 13, cfspace: 0x5FD16000 ht: 0x000000FF
[ScanBus] scanning bus slot: 14, cfspace: 0x5FD16800 ht: 0x000000FF
[ScanBus] scanning bus slot: 15, cfspace: 0x5FD17000 ht: 0x000000FF
[ScanBus] scanning bus slot: 16, cfspace: 0x5FD17800 ht: 0x000000FF
[ScanBus] scanning bus slot: 17, cfspace: 0x5FD18000 ht: 0x000000FF
[ScanBus] scanning bus slot: 18, cfspace: 0x5FD18800 ht: 0x000000FF
[ScanBus] scanning bus slot: 19, cfspace: 0x5FD19000 ht: 0x000000FF
[ScanBus] scanning bus slot: 20, cfspace: 0x5FD19800 ht: 0x000000FF
[ScanBus] scanning bus slot: 21, cfspace: 0x5FD1A000 ht: 0x000000FF
[ScanBus] scanning bus slot: 22, cfspace: 0x5FD1A800 ht: 0x000000FF
[ScanBus] scanning bus slot: 23, cfspace: 0x5FD1B000 ht: 0x000000FF
[ScanBus] scanning bus slot: 24, cfspace: 0x5FD1B800 ht: 0x000000FF
[ScanBus] scanning bus slot: 25, cfspace: 0x5FD1C000 ht: 0x000000FF
[ScanBus] scanning bus slot: 26, cfspace: 0x5FD1C800 ht: 0x000000FF
[ScanBus] scanning bus slot: 27, cfspace: 0x5FD1D000 ht: 0x000000FF
[ScanBus] scanning bus slot: 28, cfspace: 0x5FD1D800 ht: 0x000000FF
[ScanBus] scanning bus slot: 29, cfspace: 0x5FD1E000 ht: 0x000000FF
[ScanBus] scanning bus slot: 30, cfspace: 0x5FD1E800 ht: 0x000000FF
[ScanBus] scanning bus slot: 31, cfspace: 0x5FD1F000 ht: 0x000000FF
[QueryCard] 0x5FC40000
[QueryCard] conf: 0x5FC40000 bus: 0, slot: 2, func: 0
[ConfigurePrometheus] scanning bus slot: 3, cfspace: 0x5FC80000, ht: 0xFF, v: 0xFFFF, d: 0xFFFF
[WriteAddresses] mem Pri: 27, addr: 0x00000000, bus: 0
[WriteAddresses] mem Pri: 27, addr: 0x08000000, bus: 0
[WriteAddresses] mem Pri: 17, addr: 0x10000000, bus: 0
[WriteAddresses] mem Pri: 16, addr: 0x10020000, bus: 0
[WriteAddresses] mem Pri: 16, addr: 0x10030000, bus: 0
[WriteAddresses] io  Pri: 08, addr: 0x00001000, bus: 0
[WriteAddresses] io  Pri: 05, addr: 0x00001100, bus: 0

torsti76 · 08 May 2021, 07:28

Yeah, I noticed the mess. Output has been captured with a null modem and Linux. Perhaps, there's a problem with the cable, have to counter-check with sashimi.

However, from my experience with the AA so far, I guess there must be something wrong hardware-wise. I highly suspect a cold solder somewhere at the bus drivers or on the Firebird.
However, without schematics from hese, this is very hard to debug...

On a side note, the 3.1 library I have doesn't provide any serial output. Would you be able to share the one you have for comparison?

Hedeon · 08 May 2021, 11:04

Quote:

Originally Posted by torsti76

On a side note, the 3.1 library I have doesn't provide any serial output. Would you be able to share the one you have for comparison?

Here you go. And I update 4.0 to be more in-line with the output of 3.1.

But again, if 3.1 doesn't see the card, 4.0 will never. I wonder if it is really working as for example when I put in a pci-e soundcard, I only see a second bridge.

trixster · 08 May 2021, 12:27

Using the powerpc lib on the first page and this prometheus 4.0 libs above, this is the output I get from prmscan and openpciinfo with the bridge and killer pci-e card connected:

Code:

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: A0000000 - DFFFFFFF (1024 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.
-------------------------------------------------


System:> 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
MemAddr1 : $a0000000 - $dfffffff 1048576 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

10/0.System:>

obviously trying to start the ppc library results in it saying No supported PPC PCI bridge detected

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

06 April 2021, 09:20	#4702
johnnybarker Registered User Join Date: Dec 2018 Location: Helmsdale Scotland Age: 41 Posts: 181	Thanks, good to know to avoid it.

06 May 2021, 07:53	#4704
torsti76 Registered User Join Date: May 2018 Location: Germany, Baden-Wuerttemberg Posts: 387	Many thanks for this, @Hedeon ! I really appreciate the pace in which you drive this project and the time and resources you invest into this! One thing I noticed when comparing the behavior of your (previous) lib version against the "original" 3.1 is that your lib doesn't seem to consider that the Prometheus might be absent from the system. Let me explain this in more detail: I've had issues with my AA3000+ recently and did some rework on the board. I then tested it with the installation I've made much earlier, but without the Firebird busboard. The installation included your prometheus.library from 12/25/2020 as well as a full installation of Picasso96 with the Voodoo stuff. During testing, tools like "whichamiga" kept crashing. It took me a while to realize that this was due to prometheus.library being in place but no actual Prometheus being found in the system. Tools like 'showboards' don't crash then, but always show exactly one PCI board with undetermined vendor and product ids. I guess this is some kind of 'placeholder' for the Voodoo, but I'm not sure. Will try your new version later today for sure! It's still only 1/5 or so the size of the original 3.0 or 3.1 libs, which to me indicates the level of optimization you did to the code.

06 May 2021, 09:17	#4705
torsti76 Registered User Join Date: May 2018 Location: Germany, Baden-Wuerttemberg Posts: 387	On a related note, see attachment. :-) Can try later today if card-bridge combo is seen by the pci scan tools using the new library version. Have to look after my kids for now...

06 May 2021, 11:37	#4707
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	I did not really optimize. The 15k prometheus libs were compiled with -DDEBUG I think? I remember seeing debug stuff when I looked into it. And regarding the crash info, I'll have a look.

06 May 2021, 16:26	#4709
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Prmscan output or it didn't happen

06 May 2021, 20:40	#4710
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	I updated the first post with the current powerpc.library and prometheus.library and their debug equivalents. I'll post updates of the files there from now on.

07 May 2021, 08:55	#4712
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Use the debug version with Sashimi, prmscan and without startup sequence. It will give more info

07 May 2021, 09:40	#4714
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	Also compare with the 15k big prometheus 3.1 library please.

08 May 2021, 07:28	#4718
torsti76 Registered User Join Date: May 2018 Location: Germany, Baden-Wuerttemberg Posts: 387	Yeah, I noticed the mess. Output has been captured with a null modem and Linux. Perhaps, there's a problem with the cable, have to counter-check with sashimi. However, from my experience with the AA so far, I guess there must be something wrong hardware-wise. I highly suspect a cold solder somewhere at the bus drivers or on the Firebird. However, without schematics from hese, this is very hard to debug... On a side note, the 3.1 library I have doesn't provide any serial output. Would you be able to share the one you have for comparison?

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