VOGONS


First post, by Lostdotfish

User metadata
Rank Member
Rank
Member

Bought a non-working Voodoo 1 card to look at repairing and I've hit a dead end.

The attachment PXL_20251106_133402724.jpg is no longer available

When it arrived, it had some trace damage to the back of the card (repaired with enamelled wire) and several pins on the TMU were slightly bent and shorting on neighbouring pins. I realigned the pins carefully and while doing this, noticed a 33 ohm resistor network was damaged with 1 resistor being completely open. I replaced this network.

Testing card with Mojo, it reports everything ok except TMU power on sense comes back as 0xdead and then bogus number of TMUs message at the end. Sooooo, the TMU is not recognised.

I reflowed all pins on the TMU and the FBI chips. I have verified pin continuity from the PCB pad to the IC leg at the top of the IC. TMU is soldered just fine with no shorts.

Still getting TMU power on sense 0xdead.

I doubled checked my trace repair to make sure that the traces are not shorting to each other and that I have continuity from each end of the repaired traces by scraping vias and testing continuity along the trace. All checks out.

I have checked all the ferrites, most of the resistors and the caps (as best I can - but all get a sensible reading in diode mode on my meter)

Starting to wonder if this TMU is actually dead but before I consign the card to the parts bin, have I missed something...?

The attachment PXL_20251106_133414140.jpg is no longer available
The attachment PXL_20251106_133411997.MP.jpg is no longer available
The attachment PXL_20251106_133409888.Ma.jpg is no longer available
The attachment PXL_20251106_133407412.jpg is no longer available

Ignore the flux residue, card needs a good clean if I get it back to life.

Last edited by Lostdotfish on 2025-11-06, 15:25. Edited 1 time in total.

Reply 1 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member

just tested the relays for good measure and they click over as expected when 5v is applied to the coils...

Reply 2 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member

Here's another question ... does anyone know how many layers this board is? The damage to the traces on the back of the card was quite deep... is it possible that I have broken traces buried in the board layers that I cannot see? The damage is just above where the TMU is on the otherside of the card.

Reply 3 of 24, by Rwolf

User metadata
Rank Member
Rank
Member

It looks like a normal 4-layer board with gnd/pwr planes in the middle to me.

One thing I tend to do is to test the solder connections on the TMU:s type of pins, is using a fine needle or toothpick, just slide it gently along the legs and listen for the 'ping' that indicated a good solder attachment, if a pin is loose from the pad it will not make the same sound.

Reply 4 of 24, by Postman5

User metadata
Rank Member
Rank
Member

Check for cracks in the soldering under the memory chips pins.

Reply 5 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
Rwolf wrote on 2025-11-06, 17:58:

It looks like a normal 4-layer board with gnd/pwr planes in the middle to me.

One thing I tend to do is to test the solder connections on the TMU:s type of pins, is using a fine needle or toothpick, just slide it gently along the legs and listen for the 'ping' that indicated a good solder attachment, if a pin is loose from the pad it will not make the same sound.

I've reflowed both 3dfx chips and checked pin by pin under the scope. They're sound.

Reply 6 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
Postman5 wrote on 2025-11-06, 19:37:

Check for cracks in the soldering under the memory chips pins.

checked as well - all super sound

Reply 7 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
Lostdotfish wrote on 2025-11-06, 15:06:

Here's another question ... does anyone know how many layers this board is? The damage to the traces on the back of the card was quite deep... is it possible that I have broken traces buried in the board layers that I cannot see? The damage is just above where the TMU is on the otherside of the card.

I have checked pretty much everything I can check now... I am leaning towards thinking there must be damage to a trace in one of the inner layers of the board. As far as MOJO is concerned - the TMU does not exist nor does any of it's attached memory...

This is the trace repair - it is directly behind the passives at the top of the TMU. The cut is quite deep...

The attachment PXL_20251106_192811893.jpg is no longer available

Wish I had a spare TMU so I could swap test that and see if it is actually dead or not...

Reply 8 of 24, by Imperious

User metadata
Rank Oldbie
Rank
Oldbie

You didn't mention whether You have tested the voltage to the TMU? which I assume will be on the +ve of c43.
My Diamond monster had a bad memory chip that caused the TMU and/or FBI to get quite hot when I was testing it.
Check all the network resistors in ohms mode, if even 1 has gone high that could be it.

Atari 2600, TI994a, Vic20, c64, ZX Spectrum 128, Amstrad CPC464, Atari 65XE, Commodore Plus/4, Amiga 500
PC's from XT 8088, 486, Pentium MMX, K6, Athlon, P3, P4, 775, to current Ryzen 5600x.

Reply 9 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
Imperious wrote on Yesterday, 00:36:

You didn't mention whether You have tested the voltage to the TMU? which I assume will be on the +ve of c43.
My Diamond monster had a bad memory chip that caused the TMU and/or FBI to get quite hot when I was testing it.
Check all the network resistors in ohms mode, if even 1 has gone high that could be it.

I popped the card back in my test system so that I can get a meter on it while powered.

All the yellow caps have 5v where expected.

All the TMU RAM ICs have 5v on pin 1

The TMU has 5v on pin 153

So I have to assume that TMU and RAM are all powered correctly.

MOJO output looks like this.

The attachment Screenshot 2025-11-07 090919.png is no longer available

and logging

sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 1
sst1InitMapBoard(): vAddr:0xe6000000 pAddr:0xe6000008 Dev:0xf 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)
sst1InitRegisters(): Setting up FAST DRAM Configuration
ERROR: b_sum=0x030 r_sum=0x060
sst1InitFillDeviceInfo(): Retry #1 for chip GetInfo()...
ERROR: b_sum=0x030 r_sum=0x060
sst1InitFillDeviceInfo(): Retry #2 for chip GetInfo()...
ERROR: b_sum=0x030 r_sum=0x060
sst1InitFillDeviceInfo(): Retry #3 for chip GetInfo()...
ERROR: b_sum=0x030 r_sum=0x060
sst1InitFillDeviceInfo(): Retry #4 for chip GetInfo()...
ERROR: b_sum=0x030 r_sum=0x060
sst1InitRegisters(): ERROR filling DeviceInfo...

Still stuck but obviously something not happy when setting up the DRAM but I guess if the TMU isn't talking, then it can't bring that RAM online...

Reply 10 of 24, by Imperious

User metadata
Rank Oldbie
Rank
Oldbie

see my repair post here for some ideas 3dfx Voodoo 1 fault diagnosis and repair

You can try and reduce the amount of FBI and/or TMU memory available then test with tomb raider and see if any signs of life are there.
If one of the TMU memory chips is bad it could stop the TMU functioning.

Atari 2600, TI994a, Vic20, c64, ZX Spectrum 128, Amstrad CPC464, Atari 65XE, Commodore Plus/4, Amiga 500
PC's from XT 8088, 486, Pentium MMX, K6, Athlon, P3, P4, 775, to current Ryzen 5600x.

Reply 11 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
Imperious wrote on Yesterday, 09:40:

see my repair post here for some ideas 3dfx Voodoo 1 fault diagnosis and repair

You can try and reduce the amount of FBI and/or TMU memory available then test with tomb raider and see if any signs of life are there.
If one of the TMU memory chips is bad it could stop the TMU functioning.

I removed the 4 TMU RAM chips and tested the card. Same result - TMU 0xdead

I went ahead and removed the 4 FBI RAM chips as well - so the card currently has no RAM on it at all - still getting TMU 0xdead

I'm going to solder the TMU RAM back into the FBI positions and test again...

Reply 12 of 24, by Imperious

User metadata
Rank Oldbie
Rank
Oldbie

What system specs are You testing it on? Voodoo 1 cards generally don't like faster cpus like athlons or p3's above 800mhz or thereabouts.
Do any of the chips get hot when testing. The TMU and FBI especially should be warm at least when powered up.

Atari 2600, TI994a, Vic20, c64, ZX Spectrum 128, Amstrad CPC464, Atari 65XE, Commodore Plus/4, Amiga 500
PC's from XT 8088, 486, Pentium MMX, K6, Athlon, P3, P4, 775, to current Ryzen 5600x.

Reply 13 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
Imperious wrote on Yesterday, 11:09:

What system specs are You testing it on? Voodoo 1 cards generally don't like faster cpus like athlons or p3's above 800mhz or thereabouts.
Do any of the chips get hot when testing. The TMU and FBI especially should be warm at least when powered up.

I have an immaculate copy of this same card that works flawlessly in my system.

Both TMU and FBI are warm to the touch when the system is on

Reply 14 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member

Progress!

Soldered the TMU RAM to the lower 4 positions.

The attachment PXL_20251107_130410405.jpg is no longer available

Going to solder in the other 4 and see if I get funky textures...

Reply 15 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member

So 3D apps now trigger the relays to click over but black screen on output.

Guess we play hunt the faulty RAM module now.

Reply 16 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
Lostdotfish wrote on Yesterday, 13:45:

So 3D apps now trigger the relays to click over but black screen on output.

Guess we play hunt the faulty RAM module now.

Any idea why I'm getting 1MB reported on the TMU when no TMU RAM is currently installed?

Reply 17 of 24, by technokater

User metadata
Rank Newbie
Rank
Newbie

Well, could be that the card's BIOS or the tool does not actually probe for memory but assume it's presence based on possible hardware configurations and 1 MB is the bare minimum.

Reply 18 of 24, by Lostdotfish

User metadata
Rank Member
Rank
Member
technokater wrote on Yesterday, 14:13:

Well, could be that the card's BIOS or the tool does not actually probe for memory but assume it's presence based on possible hardware configurations and 1 MB is the bare minimum.

No BIOS on Voodoo 1/2 cards.

Reply 19 of 24, by technokater

User metadata
Rank Newbie
Rank
Newbie

Didn't check the hardware, but on banshee that is what the driver does to detect the memory size. According to the datasheet, texture memory can be 1-4 MB EDO DRAM, thus I would assume the tool just uses this as a minimum.