Why there are so much tin underneath ? And spread unevenly…
Filled Prometheus Resurrector Diagnostic & Repair request
- Thread starter Timtheloon
- Start date
- Replies 39
- Views 1046
According to schematics, if the voltage regulator is shorted (pins 1 and 2), you automatically get C11 shorted.
can you share the schematics for this, please amienslaver,just out of curiousity
timtheloon,its probably a good idea to stop now,short could be anywhere including the xilinx if its on the output of the regulator
timtheloon,its probably a good idea to stop now,short could be anywhere including the xilinx if its on the output of the regulator
Schematics and other files: https://github.com/shanshe/Prometheus-Resurrector/
But I do not see clearly if R102 was mounted or not on this board. UPD: Okay, it's not. Then VO is shorting somewhere, seems.
Last edited:
the resistor shouldnt be there anyway,its a fixed regulator the resistors are for setting the output on a adjustable regulator
edit,i went looking the pads are just under the regulator,r101 and r102 pads are empty
Hi all
so I have removed the damaged PCI slot just to make sure it was not causing the short but short is still there across C11 pads
so I have removed the damaged PCI slot just to make sure it was not causing the short but short is still there across C11 pads
only things left are decoupling on the 3.3v lines,the xilinx chips,and the board itself
you will probably agree its prabobly better to leave it be now
by the way,thats a neat job
you will probably agree its prabobly better to leave it be now
by the way,thats a neat job
You can check schematics in KiCad to see where VDD is connected. Mostly goes to both Xilinx chips where it connected to the ground through decoupling capacitors. You can try to check these capacitors if any of them is shorted. But, as it was said, it could be also inside Xilinx chips as well.
Updating this thread as Tim seems to be too busy (scanning the sales threads? 
).
The board arrived for repair after a long wait.
One of the Xilinx chips was in short-circuit. I desoldered the chip and the short-circuit was gone.
I replaced the faulty chip with new and reprogrammed both Xilinx chips.
I also installed the missing components (PCI connector, 3.3V voltage regulator, tantalum capacitor).
The card has been tested and all PCI slots work now.
Root cause what caused the Xilinx to fail is unknown. Visually there was no sign of damage on the board.
Most likely whatever that was installed to the X301 PCI slot burned the chip.
The card was shipped back to Tim some weeks ago.
).The board arrived for repair after a long wait.
One of the Xilinx chips was in short-circuit. I desoldered the chip and the short-circuit was gone.
I replaced the faulty chip with new and reprogrammed both Xilinx chips.
I also installed the missing components (PCI connector, 3.3V voltage regulator, tantalum capacitor).
The card has been tested and all PCI slots work now.
Root cause what caused the Xilinx to fail is unknown. Visually there was no sign of damage on the board.
Most likely whatever that was installed to the X301 PCI slot burned the chip.
The card was shipped back to Tim some weeks ago.
Sorry @hese I've been playing with that Acorn A3010 and neglected my Amigas
Yes the Master Builder has done it again and the card is now showing in the boot menu of its intended Amiga I've got a bit of work to do with this setup to get it all playing nice and how I am going to support the cards
but you can see it at the top of the expansion boot menu screen
Yes the Master Builder has done it again and the card is now showing in the boot menu of its intended Amiga I've got a bit of work to do with this setup to get it all playing nice and how I am going to support the cards
but you can see it at the top of the expansion boot menu screen
Attachments
mvickers03
Member
Hi Tim, I think this Prometheus was originally mine, I sold it to a guy very cheap privately and he resold on eBay. I don’t think he’s a member here.
Anyways, I flashed an experimental firmware to it in an attempt to improve stability with A4091 which didn’t work well, I suspect it needs reflashing with a stable firmware.
I am pretty confident that was my board at one time as I can tell by the smudging on the chips.
Good luck with it, it worked well for me before flashing the firmware, only issue I had was it didn’t play nice with A4091
Anyways, I flashed an experimental firmware to it in an attempt to improve stability with A4091 which didn’t work well, I suspect it needs reflashing with a stable firmware.
I am pretty confident that was my board at one time as I can tell by the smudging on the chips.
Good luck with it, it worked well for me before flashing the firmware, only issue I had was it didn’t play nice with A4091
mvickers03
Member
I see it’s sorted now 
probably was damaged by the user.
Happy to see it’s alive.
probably was damaged by the user. Happy to see it’s alive.
Hi @mvickers03 that's interesting, the eBay seller refunded me for it when I said it wasn't working so it was not a great loss. I'm glad Hese brought it back to life.
mvickers03
Member
No problems, I wish I would have kept it so I can test it on my 4000t I am on the hunt for an Altera one. I didn’t have the 4000t back then.
I’m hoping it will play nice with the onboard SCSI.
I’m hoping it will play nice with the onboard SCSI.
