| Electronics > Repair |
| Tektronix DPO4054 stucked at tektronix splash screen |
| << < (9/16) > >> |
| ApertureScience:
--- Quote from: analogRF on February 10, 2021, 02:50:37 pm ---Have you done all the sanity checks? There are 'tons' of DC-DC converters on the board and DDR power supply chips that you should check first. --- End quote --- The Ram chips itself need the 2.5V rail which has a testpoint in the power supply section, ill check the ripple. Maybe there are some DC-DC for local regulation. Ill will poke around a bit. The good thing with one DEMUX and associated ram apparently working i can compare behavior. I knew chances of fixing this were slim, but a name brand scope to replace my old HP54522 was just too tempting. Ill keep you updated and thanks for the suggestions! |
| analogRF:
--- Quote from: ApertureScience on February 11, 2021, 12:21:27 pm --- --- Quote from: analogRF on February 10, 2021, 02:50:37 pm ---Have you done all the sanity checks? There are 'tons' of DC-DC converters on the board and DDR power supply chips that you should check first. --- End quote --- The Ram chips itself need the 2.5V rail which has a testpoint in the power supply section, ill check the ripple. Maybe there are some DC-DC for local regulation. Ill will poke around a bit. The good thing with one DEMUX and associated ram apparently working i can compare behavior. I knew chances of fixing this were slim, but a name brand scope to replace my old HP54522 was just too tempting. Ill keep you updated and thanks for the suggestions! --- End quote --- there are many DC-DC converters on board generating various voltages for all sorts of components. It maybe that even the two DEMUXes and associated memories might get their supplies from different regulators. In any case the first thing is to check all regulators on board also there is still a chance that your problem might be a firmware corruption issue. The unit has V2.68 which is the last version but you can still force it to update the firmware from USB. Since your unit has no problem up to that firmware update message I am sure it will be able to reflash the firmware. In one case I had a 4104 which showed acquisition errors (it was booting correctly though, it was not stuck) and could not pass SPC I reflashed the firmware and it fixed it. I never understood why... EDIT: the reason I suggest a firmware reflash is that I still think the scope software should have started even after those acquisition hardware errors. They should not prevent the software from running, in fact you should have two channels working most probably. I have had cases with acquisition errors (of various kinds) but the scope boots and some channels that didnt have error, would work. so my guess is that the problem may not be just acquisition hardware.. |
| pcwrangler:
--- Quote from: ApertureScience on February 10, 2021, 01:57:22 pm ---Heres my bootlog.... --- End quote --- I've been searching for this info for so long. Thank you for the assist! What were your serial connection settings? 9600,8,1,N ? |
| pcwrangler:
Any idea why mine halts at the F in "Flash:" line in the boot log every time? I confirmed address line activity also halts. --- Quote ---CPU: AMCC PowerPC 440EP Rev. C at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz) I2C boot EEPROM enabled Internal PCI arbiter enabled, PCI async ext clock used 32 kB I-Cache 32 kB D-Cache Board: Tektronix Route66 IBM 440EP Main Board VCO: 666 MHz CPU: 333 MHz PLB: 133 MHz OPB: 66 MHz EPB: 66 MHz I2C: ready DRAM: 128 MB F --- End quote --- |
| analogRF:
--- Quote from: pcwrangler on February 11, 2021, 07:05:43 pm ---Any idea why mine halts at the F in "Flash:" line in the boot log every time? I confirmed address line activity also halts. --- Quote ---CPU: AMCC PowerPC 440EP Rev. C at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz) I2C boot EEPROM enabled Internal PCI arbiter enabled, PCI async ext clock used 32 kB I-Cache 32 kB D-Cache Board: Tektronix Route66 IBM 440EP Main Board VCO: 666 MHz CPU: 333 MHz PLB: 133 MHz OPB: 66 MHz EPB: 66 MHz I2C: ready DRAM: 128 MB F --- End quote --- --- End quote --- Wow! this one stops really really early on. Never seen them stop so early. But I believe it is more likely to be repairable does it consistently fail exactly at that point? It is very early on during the boot loader execution. I strongly suggest you check out all voltages and DDR termination supplies (there is one or two of them on the top) and many other DC-DC converters. There are also two polyphase regulators are on the back (LTC3729 chips) but you can trace their outputs on the top. It seems to me one or more chips are not getting power. If that's not the case then I'd try to monitor the I2C EEPROM on the back of the board (U431 a 24C01 EEPROM) I think with some probing you should be able to fix this one. You say there is activity but it is critical to see how is the "quality" of pulses. For that you need good probing techniques and low capacity probes. preferrably even FET probe but at least something like Tek P6139 |
| Navigation |
| Message Index |
| Next page |
| Previous page |