Sonnet 7200 PCI programming

[Hedeon]

DeviceID 1058? 500MHz? Not supported card I am guessing.

[Hedeon]

And run Sashimi

[torsti76]

@xterc is your PPC card the so-called "Apocalypse" in the 128 MB Variant?

[Timtheloon]

@xterc maybe post some picture of the card and close ups of the memory IC’s, someone on here will be able to identify it for you. Maybe you have stumbled on another card which could be made compatible, the fact you are getting some readings from it is surely a good sign.

I remember when I started with my G4 Apocalypse it stated I had 256mb when it only had 128mb, with a lot of help from members on here help me fix the issue

[Hedeon]

And is it jumpered or not

[xterc]

I will get a Sashmi output some time today, but in the meantime... Thank you all for your assistance so far.

The board has 9 X 48LC32M8A2 ICs. 4 on the side of the CPU, 5 on the other side.

I believe these are 32MB packages which would = 256MB (with parity), but I'm sure I've missed something.

When SAX had this board in his mediator setup it registered 128MB.

The board IS jumpered between pins 11 & 12. As a test I de-soldered the jumper and re-tried the board but the system didn't boot properly. So the jumper is back in place now.

I have also tried re-ordering the boards, but this didn't make a difference either.

I have attached 3 pictures. The first is taken at an angle to highlight the memory IC part #. The other two are for reference and show the top and underside of the board. I re-sized these to be more forum friendly, but if there is any reason you need a higher resolution photo let me know.

[xterc]

Originally Posted by Hedeon

And run Sashimi

Here is the RECOVERY output after running StartPPC, BogoMips and then GearsPPC. The 'Detected DSI hit outside of memory bounds at 00000004' occur after running Gears PPC.

RECOVERY WARNING - Data may have been damaged
Started Library Init routine
Version: $VER: powerpc.library 17.14 beta (20.01.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 Harrier based PPC PCI card
Setting PMEP base at 64050000
Setting up Harrier config base at 64051000
Setting up Harrier PIC base at 64000000
Done setting up PPC memory at address 70000000 with size 0F000000
Waiting on PPC card to respond
Accessible PPC memory set up with header at 70410000
Inserted PPC memory into Exec memory list
Library base set up at 7EEF6CB0
Copied PPC kernel code into place
Gort 68K interrupt now running at 07A0C1C4
MasterControl now running at 07A692F8
Completed adding various patches to Exec library
Started Kryten PPC cleanup task
Detected DSI hit outside of memory bounds at 00000004
Detected DSI hit outside of memory bounds at 00000004
Detected DSI hit outside of memory bounds at 00000004
Detected DSI hit outside of memory bounds at 00000004

[Hedeon]

Just the PPC reading execbase at $4 which is counted as a zero page hit.

Why does it say RECOVERY output?

[xterc]

Originally Posted by Hedeon

Just the PPC reading execbase at $4 which is counted as a zero page hit.

Why does it say RECOVERY output?

As the machine crashed I used Sashimi's RECOVERY option to retrieve the text.

[xterc]

Hedeon. If there is any debug information I can give you in please let me know. I do know this card functions properly in a Mediator setup.

If anyone else has any ideas I am all ears...

[grelbfarlk]

Originally Posted by xterc

The board has 9 X 48LC32M8A2 ICs. 4 on the side of the CPU, 5 on the other side.

I believe these are 32MB packages which would = 256MB (with parity), but I'm sure I've missed something.

When SAX had this board in his mediator setup it registered 128MB.

Can see pretty clearly solder flux on the memory so he upgraded it to 256MB, but didn't test the extra 128MB on his Mediator?
Sounds like Sax found some 500MHz (or maybe he "upgraded" that too) boards to resell and dumped them. But at least you have his word that they work properly.

Originally Posted by xterc

I have attached 3 pictures. The first is taken at an angle to highlight the memory IC part #. The other two are for reference and show the top and underside of the board. I re-sized these to be more forum friendly, but if there is any reason you need a higher resolution photo let me know.

I'd like some higher resolution pictures if possible, only to see if I can find any differences to the standard Apocalypse.

[xterc]

Originally Posted by grelbfarlk

Can see pretty clearly solder flux on the memory so he upgraded it to 256MB, but didn't test the extra 128MB on his Mediator?
Sounds like Sax found some 500MHz (or maybe he "upgraded" that too) boards to resell and dumped them. But at least you have his word that they work properly.

I'd like some higher resolution pictures if possible, only to see if I can find any differences to the standard Apocalypse.

It does look like the board has been re-worked, but he sold it as a 128MB board. I just asked him and he said he was 90% sure it was a 128MB board. Before I purchased the board he sent me a video of it running in his Mediator system and it recognized 128MB.

I have attached some high resolution images as requested.

[Hedeon]

If it is really 32M8 then those are 256Mbit (32MB) chips and then the board is 256MB. Picture is not clear enough for me to see. Still, never seen a 500 MHz version.

Old library added standard 128MB except when an ENV setting was used. Current library does 256MB as standard as looks whether the memory wraps around. If so, then 128MB is configured.

EDIT: Looking at the earlier pictures... This card is 256 MB.

[xterc]

I spent the day creating a completely fresh install with a barebones install. The same result. If the new libraries check for memory mirroring then I'm convinced it is a 256MB card.

As Sax is on record with it working as a 128MB card, is there a way of forcing the card to 128MB?

Either way, is there any chance this card could be supported with a new release of the Prometheus library? If so, what information would you need from me to assist?

[Hedeon]

Looks like the card has been tampered with. Did you use the WarpOS memory check programme?

[Hedeon]

Also, maybe a voodoo overheat issue? Try 2D stuff first like voxelspace. And then heavier 2D stuff like ScummVM.

[trixster]

A ‘scalpers special’

I hope the card is ok

[johnnybarker]

Originally Posted by xterc

I spent the day creating a completely fresh install with a barebones install. The same result. If the new libraries check for memory mirroring then I'm convinced it is a 256MB card.

As Sax is on record with it working as a 128MB card, is there a way of forcing the card to 128MB?

Either way, is there any chance this card could be supported with a new release of the Prometheus library? If so, what information would you need from me to assist?

I think I still use an older version of the library which needs the envarc setting for 256mb. If I don't have that it goes back to the 128mb. Presumably Sax was using the older version?

Mine was originally a 128mb card which I upgraded. I did have a wee bit of bother at first but that was because I never cleaned the board up properly afterwards. Once all the flux was removed it worked perfectly- may be worth using some IPA and a toothbrush.

[johnnybarker]

By IPA I mean isopropyl alcohol, not India pale ale.

[Timtheloon]

Originally Posted by trixster

A ‘scalpers special’

Don’t hold back trixster, ahahaha