k9cj5 wrote on 2024-11-08, 16:38:

I have a Diamond Monster 3D II and it was working fine, but now it wont see the TMUs when I load mojo. I checked all the resisto […]
Show full quote

I have a Diamond Monster 3D II and it was working fine, but now it wont see the TMUs when I load mojo. I checked all the resistor gates and they check out ok.

This is the log dump from Mojo. I think I have a loose pin on one of the TMU's maybe? I was hoping someone may be able to give some ideas before I start checking the pins again. Probably should have just checked and reflowed the pins before I asked this but since its such a delicate process and my experience is novice I only want to do it as a last option. At least the ram and chips should be ok. They were working not long ago.

sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 1
sst1InitMapBoard(): vAddr:0x10400000 pAddr:0xd3000008 Dev:0x2a Board:0
sst1InitRegisters(): Setting TREX-to-FBI FIFO THRESHOLD to 0x8...
sst1InitRegisters(): Setting PRELIM FT-CLK delay to 0x8...
sst1InitDacDetect(): Entered...
sst1InitDacDetectICS(): Entered...
dacWr(0x7,0xb)
dacRd(0x5,0x79)
dacRd(0x5,0x2e)
dacWr(0x7,0x1)
dacRd(0x5,0x55)
dacRd(0x5,0x49)
dacWr(0x7,0x7)
dacRd(0x5,0x71)
dacRd(0x5,0x29)
sst1InitDacDetectICS(): Exiting...
sst1InitRegisters(): Storing TREX0INIT0=0x5441
sst1InitRegisters(): Storing TREX0INIT1=0xf420
sst1InitRegisters(): Storing TREX1INIT0=0x5441
sst1InitRegisters(): Storing TREX1INIT1=0xf420
sst1InitRegisters(): Storing TREX2INIT0=0x5441
sst1InitRegisters(): Storing TREX2INIT1=0xf420
sst1InitSetGrxClk(): Entered...
dacWr(0x7,0xe)
dacRd(0x5,0x0)
dacWr(0x4,0xa)
dacWr(0x5,0x7b)
dacWr(0x5,0x6c)
dacWr(0x4,0xe)
dacWr(0x5,0x0)
sst1InitSetGrxClk(): Resetting TMUs after clock change...
sst1InitResetTmus(): Could not reset TMUs...

Sorry I don’t know the answer to your question, but Witchery should be able to tell you where the problem is. Unfortunately you’ll have to wait for it to be released.

https://www.youtube.com/watch?v=wyxRYeUJvWU

I also heared about Witchery on BuB's channel. Where this tool came from? Is it freely available? Too few info even on this forum...

RayeR wrote on 2025-01-21, 23:51:

I also heared about Witchery on BuB's channel. Where this tool came from? Is it freely available? Too few info even on this forum...

It seems like just BuB has access to it right now? There hasn't been any talk of it being released but perhaps it's just not on english forums

k9cj5 wrote on 2024-11-08, 16:38:

I have a Diamond Monster 3D II and it was working fine, but now it wont see the TMUs when I load mojo. I checked all the resisto […]
Show full quote

I have a Diamond Monster 3D II and it was working fine, but now it wont see the TMUs when I load mojo. I checked all the resistor gates and they check out ok.

This is the log dump from Mojo. I think I have a loose pin on one of the TMU's maybe? I was hoping someone may be able to give some ideas before I start checking the pins again. Probably should have just checked and reflowed the pins before I asked this but since its such a delicate process and my experience is novice I only want to do it as a last option. At least the ram and chips should be ok. They were working not long ago.

sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 1
sst1InitMapBoard(): vAddr:0x10400000 pAddr:0xd3000008 Dev:0x2a Board:0
sst1InitRegisters(): Setting TREX-to-FBI FIFO THRESHOLD to 0x8...
sst1InitRegisters(): Setting PRELIM FT-CLK delay to 0x8...
sst1InitDacDetect(): Entered...
sst1InitDacDetectICS(): Entered...
dacWr(0x7,0xb)
dacRd(0x5,0x79)
dacRd(0x5,0x2e)
dacWr(0x7,0x1)
dacRd(0x5,0x55)
dacRd(0x5,0x49)
dacWr(0x7,0x7)
dacRd(0x5,0x71)
dacRd(0x5,0x29)
sst1InitDacDetectICS(): Exiting...
sst1InitRegisters(): Storing TREX0INIT0=0x5441
sst1InitRegisters(): Storing TREX0INIT1=0xf420
sst1InitRegisters(): Storing TREX1INIT0=0x5441
sst1InitRegisters(): Storing TREX1INIT1=0xf420
sst1InitRegisters(): Storing TREX2INIT0=0x5441
sst1InitRegisters(): Storing TREX2INIT1=0xf420
sst1InitSetGrxClk(): Entered...
dacWr(0x7,0xe)
dacRd(0x5,0x0)
dacWr(0x4,0xa)
dacWr(0x5,0x7b)
dacWr(0x5,0x6c)
dacWr(0x4,0xe)
dacWr(0x5,0x0)
sst1InitSetGrxClk(): Resetting TMUs after clock change...
sst1InitResetTmus(): Could not reset TMUs...

Ok so the FBI can't get a response from the TMU(s). Check the pins connecting the FBI and the TMU on the right / furthest from VGA connector.
Here's the pinout of the TMU which is confirmed to be the same for the Voodoo 1 & 2 so I'm not making a new picture, this should be correct for the 500-0010-01 chips too:

The pins that connect the FBI to the TMU are the TF_DATA and FT_DATA lines, 16 of each. TF = TMU to FBI data (receive) and FT = FBI to TMU data (send)

Shreddoc made pictures of the Voodoo 2's FBI chip pinout: Re: Voodoo 2 component map

If you have decent flux and are confident with soldering, just going over all those pins with fresh solder may help. 30 year old solder on QFP chips is not very robust now.

Thermalwrong wrote on 2025-01-22, 01:00:

It seems like just BuB has access to it right now? There hasn't been any talk of it being released but perhaps it's just not on english forums

OK, and is there at least some link to some russion forum where can be read more about it?

RayeR wrote on 2025-01-22, 10:01:

OK, and is there at least some link to some russion forum where can be read more about it?

I also searched for it in the russian-speaking i-net space, but found no info. It's possible that in russian language they don't call it "witchery". From the advertising of the tool through the videos in the BuB's channel it seems to me that its developer is not going to release it for free.

As far as I understand, this program tests only the first 2MB of FBI memory, these are the chips that are on top of the board. And the FBI<->DAC connection. That's all for now. There is no work with TMU and their memory yet. It seems that someone wrote a Voodoo1 testing program a long time ago, and now they are trying to adapt it for Voodoo2. This information is available in the comments to BuB's video

Maybe the y call it волшебство . Ok, at least BuB could wrothe that this tool is under dev/not available than be mystically silent about it...

And BTW where I can find the pinouts and/or ref.design schematic? (the screenshot above)

The tool is in development and isn't available.

@RayeR
I posted here pinouts, a V2 schematic (not reference) : Voodoo2 component map + schematics

RayeR wrote on 2025-01-22, 15:01:

Maybe the y call it волшебство .

Or probably they call it literally "витчери", 'cause russians in their slang mostly russify the english words by replacing "w" with "в". Thanks for reminding me, I didn't even thought to make a search for the strings "витчери"+"3dfx" 😁

RayeR wrote on 2025-01-22, 15:01:

Ok, at least BuB could wrothe that this tool is under dev/not available than be mystically silent about it...

Actually, in one of his Voodoo2 repair videos BuB did mention, that this "witchery" tool is still under development and the developer gave it to him under condition not to share it.

Sorry I didn't mention I'm looking for V1 schematics/pinouts, I currently don't have V2. But curious about all 3dfx... That PCIe beast looks cool 😀

I posted V1 schematics as well. Check this forum for Vodoo 4400H and 4440H, or go to https://sdz-mods.com/ .
Again, not reference schematics.

Thx, interesting projects as I can see. I like the HDMI addon with reverse-socket on RAMDAC, it could be adapted also for others PCI VGA cards. What max. resolution/refresh it supports?

Yes, it could be used on other cards with external RAMDAC. It supports up to 1920x1080@60Hz. Lower resolutions can use a higher refresh rate. But we're a bit off-topic here...

RayeR wrote on 2025-01-22, 15:01:

Maybe the y call it волшебство . Ok, at least BuB could wrothe that this tool is under dev/not available than be mystically silent about it...

And BTW where I can find the pinouts and/or ref.design schematic? (the screenshot above)

For the Voodoo 1, I found this reference schematic for the 3dfx Obsidian GE (voodoo 1) in an arcade schematic: 3Dfx Voodoo 1 - Low level hardware information and diagnostics thread

Do you have a digital microscope or a strong magnifying glass?

It’s advisable to check for loose pins on the FBI and TMU’s. If you find some, you can focus your reflow on those pins rather than touching pins that are good.

It might be just one or two loose pins causing all this trouble.