Tektronix DPO4054 stucked at tektronix splash screen - Page 1
Forum section: electronics / repair

author: tekfanatic94
author_rank: Newbie
timestamp: January 07, 2018, 03:44:54 pm
content: Hello everybody,First of all I would like to wish you all the best for the New Year!I'm actually trying to repair a TEKTRONIX DPO4054 that doesn't boot, it stays stucked at the DPO splashscreen.After investigating I've captured the following console port trace:.....Major ver num: 2 Minor ver num: 68Initializing MiaPA Bus error. Skipping initialization of devices on PA busInitializing Ibm440Initializing HFD204ADCInitializing HFD204ADC.......I've compared this trace with one of a DPO4032 that works fine:....Initializing MiaAdg523 detected, patching reg offsetsInitializing Tek0005Initializing Ibm440Initializing HFD204ADCInitializing HFD204ADC....It seems that the scope failed to communicate with the ADG523 and TEK0005 ASICs, that are connected on the PA Bus .My question is, does any one knows what is the PA BUS and which ICs on the PCB are the ADG523 and TEK0005 ?If somebody can help me it will be great :-)Thanks in advance for your interest and your help !

author: mairo
author_rank: Unknown
timestamp: January 20, 2018, 02:53:46 am
content: Hi all,I think I may have similar problem - My Tek DPO4054 is also stuck at the initial 'splash screen' - it happened yesterday.The scope has never had any issues, or signs of such. Few years ago, I updated the firmware to the newest one available (2.68).Yesterday while monitoring two 5V PWM signals the scope suddenly turned OFF by itself (screen and fan OFF), and then after ~1sec back ON again by itself, but this time it just got stuck at its 'splash screen'. I do not think it was a power surge as there were other equipment also running and non of them showed any sign of losing power.Now when you turn the scope ON, it just shows the Tek 'splash screen' and I can hear the fan turning ON, but that's it, it just stays at this level. Normally, the splash screen will show up first, following by the fan and a clicking of relays, and then the screen showing the waveforms will appear.I tried to load the firmware back, but nothing happens, just stows the splash screen, and the fan is running as well.Any help will be greatly appreciated!

author: pinkman
author_rank: Regular Contributor
timestamp: January 20, 2018, 05:56:59 am
content: FWIW these scopes are quite repairable, but due to their low depreciation (they are still worth decent $ when sold by a repuatble test equipment vendor) there is not much repair info out there, and this will continue to be true until they get closer to obsoletion. As they approach obsoletion, the common failure mode will dictate whether they are even around 10 yeras from now. ASIC failures will permanently brick the scope. BOM and schematic likely will never be released. Due to limited number of these scopes in circulation and limited software upgrade potential, combined with how easy it is to activate existing software options, it is unlikely that much effort will ever be put into firmware analysis. Repairs on this series are still very expensive and most of those non-corporate persons in the know understandably won't give away the information that is out there. Due to Tek restructuring/changing hands after the development of this series, I fear that much of the really useful information will be lost forever.If ASIC has failed, you're better off buying another scope, I do not believe that you will find a replacement. If you were able to x-ray the BGA's you might find some potential issue there but I haven't repaired enough of these to know how common this is. Make sure all supply rails are regulating properly. You should be able to use another scope to discover which bus you're looking for, but the actual problem may not be apparent unless you can compare measurements to a known working scope. Be aware that there is little difference between the MSO/DPO4000 series especially from this respect and any DPO/MSO40x2 or x4 should work for comparison. Good luck.

author: JohnPi
author_rank: Regular Contributor
timestamp: February 28, 2019, 05:14:59 am
content: I have 3 of these scopes stuck like this. Two are DPO 4054 and one is a DPO 4104. I opened the 4104 up to see what was inside -- there is a small blue pushbutton on the main PCB (behind the screen) -- pushing it seems to restart the (failing) boot process.The fans are all running, and screen is bright -- but the buttons don't work and it doesn't move from the splash screen. Any ideas on what I can do to get past this ? Since both 4054 are stuck at the same point, I don't think there is any value in swapping modules.

author: switch998
author_rank: Contributor
timestamp: February 28, 2019, 06:30:55 am
content: Quote from: JohnPi on February 28, 2019, 05:14:59 amI don't have a 4054 to help, but outside of verifying the required voltages, I would start out by finding a UART port and capture the console output to find where the scope is freezing and perhaps execute a couple commands if a prompt is available. If there is an onboard lithium cell / battery backed RAM chip (particularly if it has an integrated RTC), you might want to verify they are still good since some scopes can freeze if those are not working properly.Edit: I see that the first post has a sample output from another user. If you have a bus error like the OP I would suggest X-Raying the BGAs like another user suggested. Here's a an issue on the DPOP7104 where a rework on the ADC resolved their issue:https://translate.google.com/translate?hl=en&sl=zh-CN&u=http://www.uxcer.com/NewsShow.asp%3FBid%3D20&prev=search

author: pbarton
author_rank: Frequent Contributor
timestamp: February 28, 2019, 05:49:07 pm
content: A possible fix here.....?https://forum.tek.com/viewtopic.php?t=140138Try replacing the prescaler for the PA bus. U380 (HMC438)

author: JohnPi
author_rank: Regular Contributor
timestamp: March 03, 2019, 01:50:36 am
content: Is there any particular reason this IC is likely to fail ? on 3 units ?p.s. where is it on the board ?

author: mairo
author_rank: Unknown
timestamp: March 30, 2019, 07:17:53 am
content: Where on the board is U380, I still have mine. After all I am sure it is not a major issue just a single component somewhere ... I did take mine to a Tek repair centre, they spend 3 weeks on it and the final verdict was that itpossiblyneeds a new US$3k main board... either these guys know nothing about theirs scopes, or are trying to take advantage and make money of it ... just ended up paying $100 for the check up.

author: mairo
author_rank: Unknown
timestamp: April 12, 2019, 01:22:25 am
content: My scope is alive! Changed U380 and now boots and works well. It was originally stuck on the splash screen. Early last year when the problem occurred, I took it to Tek service center, where after staying for 3 weeks, the verdict was that it 'probably' needs a new mother board, which will cost ~US$3000.00, but also not 100% sure if it will work after the swap. I told them that I will not be going ahead with this 'repair' and so they offered me a 'free' disposal of the unit, however I still had to pay AU$110.00 for the service of looking at the scope. .... I payed the service fees and took the scope back - I can sell just the buttons for 5-10 bucks each ...Thank you to whoever found and shared the solution!Forgot to add: The exact part number I used is HMC438MS8GE, from Digikey. P/n 1127-2962-ND. Hot air is required for the rework as the IC has a pad underneath.

author: stj
author_rank: Super Contributor
timestamp: April 12, 2019, 11:15:09 am
content: Quote from: mairo on April 12, 2019, 01:22:25 amsounds like you took it to Apple!!

author: pinkman
author_rank: Regular Contributor
timestamp: June 20, 2019, 02:51:31 pm
content: This is an excellent follow-up, there should be a thread dedicated to fixing these scopes due to the small amount of information out there. Nice work.

author: dogbert
author_rank: Contributor
timestamp: June 28, 2019, 12:25:58 am
content: Any idea about where the console port is? Thanks

author: analogRF
author_rank: Super Contributor
timestamp: December 28, 2019, 07:53:34 pm
content: Quote from: mairo on April 12, 2019, 01:22:25 amdid you also look at the debug serial port? can you let me know where the serial port is located?

author: mairo
author_rank: Unknown
timestamp: September 06, 2020, 10:18:25 pm
content: No, I have not looked at the serial port, neither know where it is. The fix was just done by replacing the IC.

author: winniethepooh_icu
author_rank: Contributor
timestamp: September 07, 2020, 06:41:14 am
content: Congrats on fixing an excellent scope. We have quite a few of these on the bench with their TDP active probes and everyone loves them. I prefer one over any of the new agilent machines we have. We have had to open a few of them up over the years (the ones that get left on all night every night by the old timers) but have only had power supply circuit failures. Beautiful machines.

author: JohnPi
author_rank: Regular Contributor
timestamp: November 21, 2020, 07:38:41 pm
content: Does anyone have a photo of where U308 is on the PCB ?

author: analogRF
author_rank: Super Contributor
timestamp: November 21, 2020, 08:20:07 pm
content: upper left corner, above the ADC clearly marked U380what are the symptoms? that chip is not the only fault that prevents the scope to boot. actuallywhen that chip is checked by the firmware, quite a bit must have fallen into its place already,PA Bus doesnt get accessed/checked until the scope software starts. Firmware must have been successful before thatdo you have splash acreen or no acreen at all?

author: JohnPi
author_rank: Regular Contributor
timestamp: November 21, 2020, 08:45:43 pm
content: Actually it's a DPO 4104. The splash screen (and the fan) comes up within a second or so when powered up, but remains stuck there.I measured the power supply voltage; it was OK.

author: analogRF
author_rank: Super Contributor
timestamp: November 21, 2020, 10:01:49 pm
content: check all the voltages on the board, there are many DCDC converters, you need to check them all first but most probably they are okyeah, unfortunately U380 is not the only thing that can cause this...serial debug console can tell you if it is the PA Busthat is causing this or not. If that's the case, then U380 is the culprit. YOu can also check it yourself if you have a high frequency FET probeand high freq scope or spectrum analyzer, that chip is a simple divide 4 IIRChave you tried to "force" the firmware via the USB stick (see the firmware installation manual)?use a USB stick that has LED showing data activity. If the USB at least gets accessed, I think you have passed a critical pointand the scope software starts a little after that, so there is a chance that U380 is stopping itbut if USB does not get accessed, the thing is stopping in earlier steps and has nothing to do with U380...

author: JohnPi
author_rank: Regular Contributor
timestamp: November 21, 2020, 10:12:54 pm
content: I'll try the USB stick 1st. My SA goes to 1 GHz (my other scope is only ~ 200 MHz), I'l check if I can see anything with the SA.Where are the debug console pins ?

author: analogRF
author_rank: Super Contributor
timestamp: November 22, 2020, 02:42:54 am
content: IIRC, there is a 2GHz VCO that gets divided by 4 via that U380, so there should be 500MHz on its output (it's differential output but you can probe one line and see) if there is nothing, check to see if the VCO and U380 have received power already. I am not sure but they might be turned on only when the scope software starts which is way down the line in the boot process. In fact the last step is running the scope software which checks a lot of stuff first...

author: JohnPi
author_rank: Regular Contributor
timestamp: November 22, 2020, 04:24:37 am
content: The 5 V on the board is OK (~ 5.1 V). U380 also has 5 V; I can't see signals at its input or output, but my SA picks up strong 440 MHz and 880 MHz around there. If that is what is expected and it wasn't dividing, I wouldn't see this (divided from 2.2 GHz ?)The inputs are also biased around 5V; the outputs at about 4.6 & 4.4 V which seems about right. With the scope off, I measure ~ 60 Ω at the inputs and ~ 87 Ω at the outputs -- that also seems about what I would have expected.The coin cell (left side) is glued down (not replaceable ?); it measures 3.0 V. If it wasn't glued. I'd replace it, but 3 V is probably OK for now.For reference, here's the back of the scope. U830 is on the bottom right.

author: analogRF
author_rank: Super Contributor
timestamp: November 22, 2020, 04:37:39 am
content: the VCO is 2.5GHz and the chip divides by 5. My bad

author: JohnPi
author_rank: Regular Contributor
timestamp: November 22, 2020, 04:56:05 am
content: But I see 440 MHz, definitely not 500 MHz (2.5 GHz ÷ 5); also there's an 880 MHz component --> it's not a 50 % duty cycle signal. The ÷ 5 means that the output would not be 50 % duty cycle.Just in case it was the coin cell, I forced 3.5 V on it and powered on -- no difference.There is a small pushbutton on the main board; when I press it, the display turns off and turns on again after a couple of seconds when released.Any hints on how to see the boot log ? Where are the Tx/Rx points ?

author: Jwalling
author_rank: Unknown
timestamp: November 25, 2020, 09:46:42 am
content: Quote from: JohnPi on November 22, 2020, 04:56:05 amA question I've seen asked a number of times (myself included), but never gets answered for some reason!

author: JohnPi
author_rank: Regular Contributor
timestamp: November 26, 2020, 09:46:46 pm
content: Doesanyonehave info on where the serial logging port is ?I have 4 of these machines that all failed in a similar way. One I checked doesn't seem to have U380 bad.

author: adrianh
author_rank: Contributor
timestamp: January 02, 2021, 03:33:19 pm
content: I have a DPO4014 that is stuck in an endless splash screen-reboot loop. Any information on the serial console location would be appreciated!

author: jjd
author_rank: Contributor
timestamp: January 14, 2021, 12:07:05 am
content: Seeing I'm not alone I signed up just to say me too.A recent change has my DPO4034 stuck on the splash screen.Chatted with Tektronix support today and it appears they don't know about this problem. They had no idea of what could be causing it but opened a ticket...Like others found, troubleshooting information is extremely limited and most of what I found was user and service manuals.The troubleshooting guide in the SM is a joke:Does instrument display power up screen?- No, check power supply (wiggle wires and test a couple power rails)- Yes, Does instrument pass diagnostics?-- Yes - Scope is OK, pat yourself on the back and have a cookie-- No - Run self test and determine which module to replaceThis started yesterday after sitting around for a month off, but powered. The first time restarting I gave up and power cycled and after an hour or so it was alive. I don't know why, but last night I powered it down. Today it's worse. I get a black for 5-7 minutes during that time the fan goes from overdrive to normal, after that the splash screen displays. I may get a couple relay clicks, the button LEDs reset to just Fine and Run/Stop (green) and a faint back light to CH1 enable button.ADD prevents me from staring at the USB stick for 7 minutes waiting for a LED to blink, that's a long time doing nothing.At least this is a work scope, and I can get a replacement. I'll suggest someone in the lab may want to check U830 to see if that helps.

author: pcwrangler
author_rank: Regular Contributor
timestamp: January 14, 2021, 06:50:59 pm
content: Quote from: Jwalling on November 25, 2020, 09:46:42 amStill trying to find this if anyone has information.

author: m k
author_rank: Super Contributor
timestamp: January 16, 2021, 01:25:30 pm
content: https://www.manualslib.com/manual/1340283/Tektronix-Mso4104b.html?page=18#manualIs this even remotely similar?JTAG seems to be a bit off placed.USB device connector being serial from inside is a bit far.And if it is meant to be used that way there most likely are potential connection taps somewhere.

author: pcwrangler
author_rank: Regular Contributor
timestamp: January 29, 2021, 04:41:31 am
content: I'm actually working on an MSO4104(non B) and my board doesn't even match that manual. The original manual didn't have the JTAG interface in the service manual. Does anyone have a 4104B that can take a picture of that J9201? I assume it will look similar across the board. Once we have the right interface I can find the pinout.

author: m k
author_rank: Super Contributor
timestamp: January 30, 2021, 10:47:17 am
content: Manualslib wasn't very supportive.Many models were leading to few manuals.If console is somewhere, like is quite possible, at least one model has a command "Console" in the ROM,where can it be, where it can't be.What kind of a connection is the option module, standard USB?How far from the CPU is the probe?Is it possible that RS-232 trigger is used as a part of a console port?

author: ApertureScience
author_rank: Contributor
timestamp: February 10, 2021, 01:28:07 pm
content: The Tx Pin is located on the 20-pin connector at the bottom. With the screen facing up, its the 2nd pin in the first row.Good read on the topic:https://debugmo.de/2013/03/whats-inside-tektronix-dpo5034/

author: ApertureScience
author_rank: Contributor
timestamp: February 10, 2021, 01:43:32 pm
content: I also bought a DPO4054, whis is also stuck at splash screen. Replaced U380 prescaler, but nothing changed. My bootlog suggests either DEMUX or RAM, maybe...For clarification: The ADC talks to the RAM via the DEMUX chips. There are 4 512Mbyte chips per DEMUX. I tried to layout the functional groups below, based on my guess.ADCU271DEMUXU270 U370RAMU162 U171 U0170 U0180 U470 U480 U0462 U0471

author: analogRF
author_rank: Super Contributor
timestamp: February 10, 2021, 01:50:23 pm
content: can you post the boot log?

author: ApertureScience
author_rank: Contributor
timestamp: February 10, 2021, 01:57:22 pm
content: Heres my bootlog. It suggest something along U370 Demux. So either Demux or one of the associated RAMs.I hat to attach the file, i guess because of the encoding errors.U-Boot 1.1.4 (Jan 8 2007 - 11:12:14) Tektronix, Inc. V1.06CPU: AMCC PowerPC 440EP Rev. B at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz)I2C boot EEPROM enabledInternal PCI arbiter enabled, PCI async ext clock used32 kB I-Cache 32 kB D-CacheBoard: Tektronix Route66 IBM 440EP Main BoardVCO: 666 MHzCPU: 333 MHzPLB: 133 MHzOPB: 66 MHzEPB: 66 MHzI2C: readyDRAM: 128 MBFLASH: 64.5 MBPCI: Bus Dev VenId DevId Class Int00 13 10b5 9056 0680 1800 15 1002 4c59 0300 17DISP: Type 1In: serialOut: serialErr: serialEnter password - autobooting in 3 seconds## Booting image at f0000000 ...Image Name: Linux-2.4.20_mvl31-440ep_evalImage Type: PowerPC Linux Multi-File Image (gzip compressed)Data Size: 1441010 Bytes = 1.4 MBLoad Address: 00000000Entry Point: 00000000Contents:Image 0: 1033953 Bytes = 1009.7 kBImage 1: 407042 Bytes = 397.5 kBVerifying Checksum ... OKUncompressing Multi-File Image ... OKcmdline is console=ttyS0,9600 quiet bigphysarea=519 panic=2 root=/dev/mtdblock7 rw mem=131072kLoading Ramdisk to 07f2b000, end 07f8e602 ... OKChecking for firmware update...No USB mass storage devices found to update from.Linux 2.4.20_mvl31-440ep_eval V 1.15 Tektronix Route66 Tue Jun 22 15:19:50 PDT 2010stat of /var/log/dmesg failed: No such file or directoryrm: cannot remove '/var/run/*': No such file or directoryWarning: loading NiDKEng-1.6 will taint the kernel: non-GPL license - ProprietarySeehttp://www.tux.org/lkml/#export-taintedfor information about tainted modulesWarning: loading NiDUsb-1.6 will taint the kernel: non-GPL license - ProprietarySeehttp://www.tux.org/lkml/#export-taintedfor information about tainted modulesWarning: loading tek will taint the kernel: non-GPL license - ProprietarySeehttp://www.tux.org/lkml/#export-taintedScope application starting (normal mode)---------------------- startScopeApp() running Init code ----------------------versionBuildFWVersionString(): TimestampString: 25-Apr-12 11:13VersionFIRMWAREVERSIONversion: v2.68Major ver num: 2 Minor ver num: 68Initializing MiaAdg523 detected, patching reg offsetsInitializing Tek0005Initializing Ibm440Initializing HFD204ADCInitializing HFD204ADCModel id: 0x02Initializing Ltc1658DacBoard id: 0x00Initializing M859Initializing M859Initializing M859Initializing M859HFD144 ID_REG = 0x00001440HFD144 ID_REG = 0x00001440HFD144 ID_REG = 0x00001440HFD144 ID_REG = 0x00001440Initializing Hfd144Initializing Hfd144Initializing Hfd144Initializing Hfd144Open Max5362 successful.Initializing Max5362Initializing Ltc1661DacInitializing Ltc1661DacInit ADT7468 and locking.Factory Checksum: Stored: 36701, Calculated: 36701 - OKSpc CheckSum: stored: 24980 calculated: 24980 - OKDemux initializationDram calibrationdmx 03 ERROR: 10_calDramStep29: Dram1 GrpD 29.2.4 byte 97: exp/act 0x06/0x0e (bits: 3)dmx 03 ERROR: 10_calDramStep29: Dram1 GrpDC 29.2.4 byte 99: exp/act 0x06/0x36 (bits: 4 5)dmx 03 ERROR: 10_calDramStep29: 29.2.5.1 couldn't align data with rdLtncy, rdAckLtncydmx 03: DramCal FAILED *****Dram calibration completeDram Calibration results:-------------------------dmx 02: PASSEDdmx 03: FAILED *****ERROR: 10_calDramStep29: Dram1 GrpD 29.2.4 byte 97: exp/act 0x06/0x0e (bits: 3)Demux initialization completeStarting POST diagsDiag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x0Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x10Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x20Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x30Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x40Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x50Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x60Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x70Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x80Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x90Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0xa0Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0xb0Failure at address 0xc0Failure at address 0xd0Failure at address 0xe0Failure at address 0xf0dmx 03 ERROR: 10_calDramStep29: Dram1 GrpD 29.2.4 byte 97: exp/act 0x06/0x0e (bits: 3)dmx 03 ERROR: 10_calDramStep29: Dram1 GrpDC 29.2.4 byte 99: exp/act 0x06/0x36 (bits: 4 5)dmx 03 ERROR: 10_calDramStep29: 29.2.5.1 couldn't align data with rdLtncy, rdAckLtncydmx 03: DramCal FAILED *****Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000fefe 0xfefeffff 0xfefe0101Diag Failure: Mode 100 7, U370,U270, 0x00000101 0x0101ffff 0x0101fefeDiag Failure: Mode 100 7, U370,U270, 0x0000fdfd 0xfdfdffff 0xfdfd0202Diag Failure: Mode 100 7, U370,U270, 0x00000202 0x0202ffff 0x0202fdfdDiag Failure: Mode 100 7, U370,U270, 0x0000fbfb 0xfbfbffff 0xfbfb0404Diag Failure: Mode 100 7, U370,U270, 0x00000404 0x0404ffff 0x0404fbfbDiag Failure: Mode 100 7, U370,U270, 0x0000f7f7 0xf7f7ffff 0xf7f70808Diag Failure: Mode 100 7, U370,U270, 0x00000808 0x0808ffff 0x0808f7f7Diag Failure: Mode 100 7, U370,U270, 0x0000efef 0xefefffff 0xefef1010Diag Failure: Mode 100 7, U370,U270, 0x00001010 0x1010ffff 0x1010efefDiag Failure: Mode 100 7, U370,U270, 0x0000dfdf 0xdfdfffff 0xdfdf2020Diag Failure: Mode 100 7, U370,U270, 0x00002020 0x2020ffff 0x2020dfdfDiag Failure: Mode 100 7, U370,U270, 0x0000bfbf 0xbfbfffff 0xbfbf4040Diag Failure: Mode 100 7, U370,U270, 0x00004040 0x4040ffff 0x4040bfbfDiag Failure: Mode 100 7, U370,U270, 0x00007f7f 0x7f7fffff 0x7f7f8080Diag Failure: Mode 100 7, U370,U270, 0x00008080 0x8080ffff 0x80807f7fDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 8, U271, calloc failed, 0Diag Failure: Mode 100 8, U271, calloc failed, 0Finished POST diagsacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedcalNonXopReadAcqChanData: Number of Bytes Read is less than requested: actual 0 requested 685Class 3 Calibrate Id 0 Instance 0 Severity 3 20:08:38 Tue Feb 9 2021 (thread: tUsrRoot) file powerup line 0 HF Step Offset FailederrAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVEClass 3 Calibrate Id 0 Instance 0 Severity 3 20:08:38 Tue Feb 9 2021 (thread: tUsrRoot) file powerup line 0 A Powerup Cal Test FailederrAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVEacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failedacqUpWriteLong failed---------------------- startScopeApp() running Start code ---------------------

author: ApertureScience
author_rank: Contributor
timestamp: February 10, 2021, 02:12:10 pm
content: This is my guesstimate for the pcb. There are 4 more ram chips on the back of the board. Maybe someone with more experience can confirm? Not too sure about the frontend chips directly under the metal cans and the different green colored ic in the middle.

author: analogRF
author_rank: Super Contributor
timestamp: February 10, 2021, 02:50:37 pm
content: U370 is indeed DMUX 3Acq DRAM memories: U462,U471 are on the bottom side of the board right beneath the U470 and U480 (4 chips grouped together)there are 4 more chips grouped together on the left side (top and bottom)based on my experience even if one of the DRAm chips (in each group) is bad you get error indicating all 4 of them i dont know why...butit is hard to find and it is much more likely that the DMUX U370 is badOnce I tried to reflow it (after removing the heatsink which is a painful experience and can damage the board) but didnt helphowever my hot air is pretty lousy and I am still thinking that reflow should have fixed it anyways...what is surprising to me is that all those Diag errors should not prevent the scope software from running at the end. You may not get traces on channels but the scope software should still run after those errors based on what I have seen on multiple occasionsafter "Finished POST diags" you should get something like this no matter if the POST diags failed or not:Code:---------------------- startScopeApp() running Start code ------------------------------------------- startScopeApp() running Run code -----------------------SIOCSIFFLAGS: Link has been severedOK to connect by: telnet DPO4104-04SKBP 1072SocketServerService: Socket server daemon started on port 4000.Protocol: Raw-----------------------------------------------------------------startScopeApp() complete; duration = 27.873596 seconds=================================================================PID to Task info written to /tmp/threads.txtPower Up Completed at 15:40:10so those "acqUpWriteLong failed" is new to me at least....actually you have reached a point that it saysCode:startScopeApp() running Start codebut nothing after that...I have a feeling that on top of the Acquisition failures there is also something wrong with the computer/cpu section maybeHave 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.

author: Jwalling
author_rank: Unknown
timestamp: February 10, 2021, 07:42:12 pm
content: Quote from: ApertureScience on February 10, 2021, 01:28:07 pmThanks for that! That question has been asked many times, but never seems to get an answer.

author: Jwalling
author_rank: Unknown
timestamp: February 10, 2021, 07:49:03 pm
content: Quote from: ApertureScience on February 10, 2021, 01:57:22 pmIf you press the button for "Insert code" it will work the way you think.Code:U-Boot 1.1.4 (Jan 8 2007 - 11:12:14) Tektronix, Inc. V1.06CPU: AMCC PowerPC 440EP Rev. B at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz)I2C boot EEPROM enabledInternal PCI arbiter enabled, PCI async ext clock used32 kB I-Cache 32 kB D-CacheBoard: Tektronix Route66 IBM 440EP Main BoardVCO: 666 MHzCPU: 333 MHzPLB: 133 MHz

author: ApertureScience
author_rank: Contributor
timestamp: February 11, 2021, 12:21:27 pm
content: Quote from: analogRF on February 10, 2021, 02:50:37 pmThe 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!

author: analogRF
author_rank: Super Contributor
timestamp: February 11, 2021, 02:35:07 pm
content: Quote from: ApertureScience on February 11, 2021, 12:21:27 pmthere 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 boardalso there is still a chance that your problem might be a firmware corruption issue. The unit has V2.68 which is the last versionbut you can still force it to update the firmware from USB. Since your unit has no problem up to that firmware update messageI 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..

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 11, 2021, 05:12:25 pm
content: Quote from: ApertureScience on February 10, 2021, 01:57:22 pmI've been searching for this info for so long. Thank you for the assist!What were your serial connection settings? 9600,8,1,N ?

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 11, 2021, 07:05:43 pm
content: 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

author: analogRF
author_rank: Super Contributor
timestamp: February 11, 2021, 08:02:30 pm
content: Quote from: pcwrangler on February 11, 2021, 07:05:43 pmWow! this one stops really really early on. Never seen them stop so early. But I believe it is more likely to be repairabledoes 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 seehow 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

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 11, 2021, 08:26:10 pm
content: Quote from: analogRF on February 11, 2021, 08:02:30 pmYes, I have repeated it dozens of times to be sure it is consistant.QuoteI know the voltages on the top right of the board at J890 are all correct. Thanks for the guidance on the rest. I'll check those too.QuoteUnfortunately the only scope I have right now is a DS1054z and the probes that came with it. However, the quality of the address activity looks pretty good considering my equipment. I don't suspect an issue there, except how it ends abruptly at the same time the boot log stops. I2C on the other hand...I do appreciate your help.

author: analogRF
author_rank: Super Contributor
timestamp: February 11, 2021, 09:40:39 pm
content: Quote from: pcwrangler on February 11, 2021, 08:26:10 pmno, there are other voltages on the board that dont appear on that connectorplus the DDR termination suppliesif all activities suddenly stop, have you checked the CPU clock? there are several crystal oscillators on both sides of the boardbut I think the CPU clock is generated on the bottom side. It was marked either Y650 or Y560.

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 11, 2021, 11:01:08 pm
content: Quote from: analogRF on February 11, 2021, 09:40:39 pmThe oscillator at Y650 is 27MHz and looks good, steady through the whole process.There are two LTC3728 and one LTC3729 that all look ok. The PGOOD signal on all of them isn't pulled down. How else would I test these?The EEPROM at U431 has steady power but no activity on the one address line that isn't directly tied to ground. There are only 2 pulses low on the SDA and one on the SCL upon boot, exact same results every time.What do the DDR termination supplies look like? Do you have a location I can reference?Thanks

author: analogRF
author_rank: Super Contributor
timestamp: February 12, 2021, 01:41:48 am
content: Quote from: pcwrangler on February 11, 2021, 11:01:08 pmdid you check all the crystal oscillators? there are several of them. at least two I remember were on the bottom side. Remember the CPU clock is 333MHz which is not directly generated by any crystal so there must be a PLL somewhere to multiply one of those crystal frequencies up to 333MHzor maybe the CPU has that PLL implemented inside of itself. This is the time you should start reading through datasheets of componentsto get a grip on how each of them is supposed to behave. I'd start by CPU architecture and pin out.IF everything is suddenly stopped and there is no activity, either a clock has stopped or the CPU is halted or reset. So finding those pins is importantI think this CPU has no internal ROM (check?), so I guess that I2C EEPROM provides the small bit of code needed to start a boot loader but from where? or perhaps the EEPROM actually contains the bootloader itself? 1KB seems too small for that I guess but who knowsyour system is halted in the middle of that small code (or boorloader) for some reason. at that point nothing has been initialized yet I thinkbut DDR memory is probably already in play here so checking that supply termination is a good start. That is a specialized regulator IC soldered very near the CPU I dont remember the P/N but just look around the CPU and you will see it.i dont think not having activity on that address line of the EEPROM is important. what is important is what are data/address that are going in and data coming out. maybe it's a good idea to use I2C decoding on the SDA/SCL lines of that chip and see what you get and compare with what the datasheet says about the signaling of that EEPROM.But first and foremost is (1) all voltages including the DDR termination chip (2) all crystal oscillators (3) finding out if the CPU is halted or reset

author: ApertureScience
author_rank: Contributor
timestamp: February 14, 2021, 05:34:18 pm
content: analogRF, I just found your thread regarding the dpo4104. I dont know how I didnt find it beforehandI tried the firmware update....so it gets past the boot screen, but only on firmware lower than 2.68. It still crashes afterwards with not being able to handle button presses because of errors and finally kernelpanic

author: analogRF
author_rank: Super Contributor
timestamp: February 14, 2021, 06:27:17 pm
content: Quote from: ApertureScience on February 14, 2021, 05:34:18 pmI'd still think there is also a problem in the CPU/computer area and not just the acquisition.can you post the new boot log after forcing the firmware refresh

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 15, 2021, 12:52:24 am
content: Quote from: analogRF on February 12, 2021, 01:41:48 amAll oscillators on both sides are present and stable. The CPU does have an integrated PLL.QuoteI checked every pin imaginable from the vias under the BGA. The only suspect was clkEn which enables the RAM clock. It is steady at 2.2v instead of the documented 2.5v in the CPU datasheet. However, I believe that is still within SSTL 2 specs.QuoteYou were right. I confirmed the CPU bootstrap is configured to gather boot configuration from the 16 bytes on the I2C EEPROM. I believe that is telling the CPU to get the bootloader from the 4MB flash chip at U822. The CE and OE pins between the CPU and U822 start enabled and then go high at the same time the boot log stops. I think bootloader instructions are interrupted because of this. I just don't know why the CPU is doing this.QuoteI confirmed the DDR termination regulator is at U650 and is behaving as specified in the datasheet.QuoteSadly, I have ruled out voltages, DDR termination and oscillators. I will attempt an I2C decode just to see what it looks like but I think we are beyond the I2C EEPROM step in the boot process.Is it possible that the bootloader on the flash is damaged or missing at my halt point due to a failed FW update? I do have the means to program that chip if necessary. It feels like I'm so close!

author: analogRF
author_rank: Super Contributor
timestamp: February 15, 2021, 02:11:53 am
content: Quote from: pcwrangler on February 15, 2021, 12:52:24 amexcellent piece of troubleshootingThis is the most important information that we have by now and you should focus on this flash memory U822. I also think it does contain the bootloader code. Can you remove the sticker andpost the part number?you are right, based on what you have gathered, the I2C EEPROM has done its job and I dont think it is at fault.I'd guess the bootloader flash is corrupted. At least at this point and with the other information that we have, this seems to be the most likely cause. It happensThat chip is easy to desolder and solder back in. If I remember correctly it is QFP package with J-leads, right? so one course of action would be tojust desolder it and read it and perhaps get a similar chip off another scope and re program this one.one last thing to check, if you let the scope run for while, does any component get hot? I mean only the CPU, DRAM or the flash chips?

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 15, 2021, 05:04:51 am
content: Quote from: analogRF on February 15, 2021, 02:11:53 amU822 is a Am29LV040B PLCC. Does anyone have a dump of this chip? This MSO4104(non-B) has the same version header as others have posted from different versions of the 4000. "U-Boot 1.1.4 (Jan 8 2007 - 11:12:14) Tektronix, Inc. V1.06". I'm not sure if that means it's universal and interchangeable but I also found this same version digging through the downloadable FW update from Tek. Maybe I'll desolder and compare the two.QuoteUnfortunately, no. This was the first thing I checked with an IR cam, hoping to find a simple short.

author: m k
author_rank: Super Contributor
timestamp: February 15, 2021, 06:42:43 pm
content: My guess is that F-line is good and if that flash has a checksum it's good also.Based on an assumption that the programmer is not doing the text letter by letter.There seems to be a leap from F-line to next.If there is a watchdog, is it so accurate that it will never let through more or less than that F.Processes seems to be asyncronous, many processing entities I guess.How long is one letter sent, is that time too long, can it really pin point anything.If PCI-signals are easily accessed I'd check that the bus is alive.

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 16, 2021, 09:49:51 pm
content: After desoldering and dumping the existing code on U822 I can see it contains more than just the bootloader. I compared it to the bootloader.img obtained via 'binwalk -e' of the latest firmware from the Tektronix website. Some fancy dd work on this might merge them, overwriting the bootloader portion to make things work but I would rather receive a U822 dump from someone else in the community so I know it is a functional copy. The results are below.binwalk of U822 dump (524KB)Quotebinwalk of bootloader.img from Tek (262KB)Quote

author: analogRF
author_rank: Super Contributor
timestamp: February 16, 2021, 10:21:11 pm
content: looks like there are two different versions of u-boot in U822? but why?if the flash was really corrupted, I believe the chances that binwalk could extract even that much informationwas slim. Still it could be corrupted in just a few bytes somewhere but that is very unlikely in my view.The fact that binwalk can still extract this much info is 'probably' a sign that flash is not at fault

author: analogRF
author_rank: Super Contributor
timestamp: February 18, 2021, 02:17:16 am
content: assuming the flash chip is ok, I think the cpu stalls when she wants to communicate with a peripheral device/chip and perhaps does not get the right response/acknowledge. At this early stage I think it is more likely to be a device on the PCI busCode:PCI: Bus Dev VenId DevId Class Int00 13 10b5 9056 0680 1800 15 1002 4c59 0300 17the first device is the PCI Bus Master chip made by PLX (PCI9056) and the second device in the list is the ATI Mobility Radeon graphics processorbut how to troubleshoot their connection? is beyond me...

author: m k
author_rank: Super Contributor
timestamp: February 18, 2021, 06:46:04 pm
content: If there is a real PCI connector its IDSEL should blink.If it does then at least the controller is alive.Quote from: analogRF on February 16, 2021, 10:21:11 pmMy guess is that the older one is a backup bootloader.Something like when writing a new bootloader fails backup one is still ok.So can one think that good behaving Tek has done the same with everything?

author: pcwrangler
author_rank: Regular Contributor
timestamp: February 18, 2021, 10:38:22 pm
content: Quote from: analogRF on February 18, 2021, 02:17:16 amvcc and clock are good on the PCI9056 at U560 but the IDSEL(thanks m k) line is stuck low. The datasheet of this chip and the 440EP CPU show their IDSEL pins as input. Anyone know the source?BTW: I programmed the flash with the downloaded and extracted bootloader.img just to see what would happen but it wouldn't even provide a boot log, completely dead. I reprogrammed it with the original code and it's back to the previous behavior. I thought I would add this here just in case someone is playing with firmware in the future. I suppose a merge of that img file with the original code might work but I believe you all are correct; if it was damaged I wouldn't get much useful info out of it.

author: analogRF
author_rank: Super Contributor
timestamp: February 18, 2021, 10:46:29 pm
content: could it be that CPU is receiving a false interrupt from a device onboard?

author: m k
author_rank: Super Contributor
timestamp: February 19, 2021, 12:32:02 pm
content: Good, or bad, now it's at least known that something excact is clearly something it shouldn't.Is it a cause is another thing.I don't know the correct PCI naming policies and the whole PCI hierarchy has always been a bit messy.A controller can also be PCI to PCI and then another PCI controller is what you think is the first one.Did I read it right that this 440EP can also be a PCI controller, so the 2nd in PCI line.One construction model is CPU-PLB-bridge-PCI-controller/bridge-stuff.There is also a method called PCI boot, where PCI memory can be accessed without configuration, it can obviously be misused for what ever purposes.In this case it's quite possible that PCI something is predefined.Since the system knows that some parts are there, or should be, always, it can expect them.So if PCI 9056 is not first its missing ID request can be fine, but since that other boot log has it as first, one must follow that.Though it doesn't exclude that there isn't something else before that but would it be completely silent in the log.For the interrupt,if it's PCI and not configured it should be ingnored.One method for IDSEL is to decode one address line for each PCI connection IDSEL.PPC440EPx-GRx manual says that device 1 is AD11.If those addresses are used elsewhere there must be a chip with enable in between somewhere.

author: ApertureScience
author_rank: Contributor
timestamp: May 30, 2021, 09:48:18 am
content: So i'm back on my project!I got some compatible RAM chips and found a shop that can swap them for me.To understand the error messages better I reversed the firmware, but nothing especially helpful came up. To tackle the 10_calDramStep29 error i wanted to narrow down the selection of the 4 ram chips associated with DEMUX 3 (aka U370).Now the part that is pure speculation. The error message format goes:Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001What had me confused is that four RAM chips are listed with three memory adresses. I thought those were supposed to be the memory addresses currently on the DEMUX buses, even though there should be four then. But I think these are linked to the DRAM groups D and DC quoted by an error message before:dmx 03 ERROR: 10_calDramStep29: Dram1 GrpD 29.2.4 byte 97: exp/act 0x06/0x0e (bits: 3)dmx 03 ERROR: 10_calDramStep29: Dram1 GrpDC 29.2.4 byte 99: exp/act 0x06/0x36 (bits: 4 5)Hence why the second and third address are always the same. My guess would be that that group D and C are the third and fouth RAM probably, so U470 and U0462.Does somebody have an opinion on that?

author: ApertureScience
author_rank: Contributor
timestamp: May 30, 2021, 09:52:03 am
content: I will also try to reball the DEMUX.

author: ApertureScience
author_rank: Contributor
timestamp: May 30, 2021, 10:02:57 am
content: Regarding the acqUpWriteLong failed error, in the firmware i found the function outputting it. I have no idea what it does! Raw decompiled code aheadCode:undefined8 acqUpWriteLong(ulong *param_1,ulong param_2,uint param_3,int param_4){undefined4 uVar1;uint uVar2;undefined4 in_LR;uVar2 = CDmxUpXfr::write(*(CDmxUpXfr **)(*(int *)(*(int *)(CDemuxs::m_physicalToLogicalIndexMap + param_4 * 4) *4 + CDemuxs::m_dmxs) + 0x40),param_1,param_3,param_2);uVar1 = 0;if (uVar2 != param_3) {errPrintf("acqUpWriteLong failed\n");uVar1 = 0xffffffff;}return CONCAT44(uVar1,in_LR);}

author: ApertureScience
author_rank: Contributor
timestamp: May 30, 2021, 10:08:34 am
content: Also interesting function that tells a bit about the memory layout. Not sure why it seems to show gaps though...Code:ushort convByteIdxToGrpIdx(uint offset){int local_20 ;local_20 = 0x10003;local_20 = 2;local_20 = 0x50007;local_20 = 0x40006;return *(ushort *)((int)local_20 + (offset & 7) * 2);}This looks weird, maybe some magic on the address bus. 0x10000 is very close to 2^16, implying some 16bit wide bus.Or.. I am totally wrong about my assumptions and everything is specified down to the SDRAM architecture to achieve the necessary acess times.

author: MarkF3837
author_rank: Newbie
timestamp: January 04, 2022, 01:06:50 am
content: On my DPO4104, there is an opening in the bottom of the metal shield. Inside is a 2-row, 20-pin 1.27 mm pitch connector. With the 'scope upside down & facing away from you, the second pin from the left in the top row is the TxD pin (data from 'scope). The pin to its right is ground. I haven't searched for the RxD pin.Signal level is 3.3V. Data rate is 9600 bps.

author: Skyhi
author_rank: Newbie
timestamp: July 30, 2022, 03:42:06 pm
content: Hi all, just wanted to say I joined this forum because I was looking for pointers on repairing a DPO 4104.In my case re-flowing the BGA flash IC's U840, U832, U821 and U820 solved my 'stuck at boot' problem. I flooded them with flux and used a heater underneath and used a hand air station with a small noozle until I saw them bubble and 're-seat' themselves.If it happens again I plan on removing them and re-balling (with leaded solder of course).Been working great for a while now!Best regards,Will

author: analogRF
author_rank: Super Contributor
timestamp: August 01, 2022, 11:33:51 am
content: Quote from: Skyhi on July 30, 2022, 03:42:06 pmmay I ask what temperature/air speed did you use? Did you also put the board on pre-heater?This is a huge and thick board, I am very reluctant (read scared) to do reflowing

author: Skyhi
author_rank: Newbie
timestamp: August 01, 2022, 12:16:40 pm
content: I did use a pre-heater underneath the board - it is a fairly small hot air setup and it had it set all the way on for heat. As for the hand air station the nozzle I used was around 7mm in diameter - I had the heat to max and kept the air flow fairly low to keep things from blowing around. I also removed the backup battery before I started heating things just to make it a little safer. When I get back to work on Tuesday I will list the equipment that I used and give you a better idea of the airspeed I used. I had initially figured out something was up in that area of the board just by using my heat gun at home just on the top of the board while trying to power up the unit and it booted! But as soon as it cooled off again it would freeze as described. I don't normally like putting as much heat into the parts as I did but I figured the die in the packages where insulated by the plastic and I really did need to get them hot enough for the solder underneath to liquefy and re-harden to achieve a good connection after the process.

author: Jwalling
author_rank: Unknown
timestamp: August 02, 2022, 09:03:43 am
content: Quote from: Skyhi on August 01, 2022, 12:16:40 pmCan you test the scope to see if it still gets an IP address when attached to a network? On a DPO3000 I worked on that had a dead battery, the MAC address was lost and couldn't be recovered.Thanks.

author: Skyhi
author_rank: Newbie
timestamp: August 03, 2022, 11:30:53 am
content: Hmm I was seeing an error (when not connected to my network) as per this image when I booted the scope and I could not seem to set a new IP address but as soon as I plugged it into my router I could update the settings and the connection test passed.

author: Skyhi
author_rank: Newbie
timestamp: August 03, 2022, 11:35:44 am
content: This is the equipment that I used for my fix - I think I had the airspeed set to around 3.5 on the hand held hot air station.

author: analogRF
author_rank: Super Contributor
timestamp: August 03, 2022, 11:41:14 am
content: Quote from: Jwalling on August 02, 2022, 09:03:43 amI think, similar to DPO4000, the MAC address is stored in a u-boot environment variable (ethaddr) and thus stored in the flash.I dont think it has anything to do with the battery. I think only volatile settings such as IP address or user setups might be stored in the battery back up NVRAM.

author: ApertureScience
author_rank: Contributor
timestamp: April 26, 2024, 07:37:55 am
content: After a long break I reinvested some time in my broken scope and a new hot air station. I reflowed U370 and something changed.Code:U-Boot 1.1.4 (Jan 8 2007 - 11:12:14) Tektronix, Inc. V1.06CPU: AMCC PowerPC 440EP Rev. B at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz)I2C boot EEPROM enabledInternal PCI arbiter enabled, PCI async ext clock used32 kB I-Cache 32 kB D-CacheBoard: Tektronix Route66 IBM 440EP Main BoardVCO: 666 MHzCPU: 333 MHzPLB: 133 MHzOPB: 66 MHzEPB: 66 MHzI2C: readyDRAM: 128 MBFLASH: 64.5 MBPCI: Bus Dev VenId DevId Class Int00 13 10b5 9056 0680 1800 15 1002 4c59 0300 17DISP: Type 1In: serialOut: serialErr: serialEnter password - autobooting in 3 seconds## Booting image at f0000000 ...Image Name: Linux-2.4.20_mvl31-440ep_evalImage Type: PowerPC Linux Multi-File Image (gzip compressed)Data Size: 1441010 Bytes = 1.4 MBLoad Address: 00000000Entry Point: 00000000Contents:Image 0: 1033953 Bytes = 1009.7 kBImage 1: 407042 Bytes = 397.5 kBVerifying Checksum ... OKUncompressing Multi-File Image ... OKcmdline is console=ttyS0,9600 quiet bigphysarea=519 panic=2 root=/dev/mtdblock7 rw mem=131072kLoading Ramdisk to 07f2b000, end 07f8e602 ... OKChecking for firmware update...No USB mass storage devices found to update from.Linux 2.4.20_mvl31-440ep_eval V 1.15 Tektronix Route66 Tue Jun 22 15:19:50 PDT 2010stat of /var/log/dmesg failed: No such file or directoryWarning: loading NiDKEng-1.6 will taint the kernel: non-GPL license - ProprietarySee http://www.tux.org/lkml/#export-tainted for information about tainted modulesWarning: loading NiDUsb-1.6 will taint the kernel: non-GPL license - ProprietarySee http://www.tux.org/lkml/#export-tainted for information about tainted modulesWarning: loading tek will taint the kernel: non-GPL license - ProprietarySee http://www.tux.org/lkml/#export-tainted for information about tainted moScope application starting (normal mode)---------------------- startScopeApp() running Init code ----------------------versionBuildFWVersionString(): TimestampString: 25-May-11 15:07VersionFIRMWAREVERSIONversion: v2.58Major ver num: 2 Minor ver num: 58Initializing MiaAdg523 detected, patching reg offsetsInitializing Tek0005Initializing Ibm440Initializing HFD204ADCInitializing HFD204ADCModel id: 0x02Initializing Ltc1658DacBoard id: 0x00Initializing M859Initializing M859Initializing M859Initializing M859HFD144 ID_REG = 0x00001440HFD144 ID_REG = 0x00001440HFD144 ID_REG = 0x00001440HFD144 ID_REG = 0x00001440Initializing Hfd144Initializing Hfd144Initializing Hfd144Initializing Hfd144Open Max5362 successful.Initializing Max5362Initializing Ltc1661DacInitializing Ltc1661DacInit ADT7468 and locking.CANNOT SET FAN PARAMETERS - CONTROLLER LOCKEDFactory Checksum: Stored: 36701, Calculated: 36701 - OKSpc CheckSum: stored: 24980 calculated: 24980 - OKDemux initializationDram calibrationdmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullUpStrengthERROR: DramDqPullUp can not pull up.Bit Fields A - H: (All bytes would be 0xff for a good cal.0xff 0xff 0xf7 0xf7 0xff 0xff 0xff 0xffdmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullDownStrengthERROR: DramDqPullDown can not pull down.Bit Fields A - H: (All bytes would be 0xff for a good cal.0x0 0x0 0x0 0x3 0x0 0x0 0x0 0x0dmx 03: DramCal FAILED *****Dram calibration completeDram Calibration results:-------------------------dmx 02: PASSEDdmx 03: FAILED *****ERROR: 06_calDriveStrength: didn't find good value for DramDqPullUpStrengthDemux initialization completeStarting POST diagsDiag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x0Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x10Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x20Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x30Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x40Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x50Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x60Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x70Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x80Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0x90Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0xa0Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002Failure at address 0xb0Failure at address 0xc0Failure at address 0xd0Failure at address 0xe0Failure at address 0xf0dmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullUpStrengthERROR: DramDqPullUp can not pull up.Bit Fields A - H: (All bytes would be 0xff for a good cal.0xff 0xff 0xf7 0xf7 0xff 0xff 0xff 0xffdmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullDownStrengthERROR: DramDqPullDown can not pull down.Bit Fields A - H: (All bytes would be 0xff for a good cal.0x0 0x0 0x0 0x3 0x0 0x0 0x0 0x0dmx 03: DramCal FAILED *****Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000fefe 0xfefeffff 0xfefe0101Diag Failure: Mode 100 7, U370,U270, 0x00000101 0x0101ffff 0x0101fefeDiag Failure: Mode 100 7, U370,U270, 0x0000fdfd 0xfdfdffff 0xfdfd0202Diag Failure: Mode 100 7, U370,U270, 0x00000202 0x0202ffff 0x0202fdfdDiag Failure: Mode 100 7, U370,U270, 0x0000fbfb 0xfbfbffff 0xfbfb0404Diag Failure: Mode 100 7, U370,U270, 0x00000404 0x0404ffff 0x0404fbfbDiag Failure: Mode 100 7, U370,U270, 0x0000f7f7 0xf7f7ffff 0xf7f70808Diag Failure: Mode 100 7, U370,U270, 0x00000808 0x0808ffff 0x0808f7f7Diag Failure: Mode 100 7, U370,U270, 0x0000efef 0xefefffff 0xefef1010Diag Failure: Mode 100 7, U370,U270, 0x00001010 0x1010ffff 0x1010efefDiag Failure: Mode 100 7, U370,U270, 0x0000dfdf 0xdfdfffff 0xdfdf2020Diag Failure: Mode 100 7, U370,U270, 0x00002020 0x2020ffff 0x2020dfdfDiag Failure: Mode 100 7, U370,U270, 0x0000bfbf 0xbfbfffff 0xbfbf4040Diag Failure: Mode 100 7, U370,U270, 0x00004040 0x4040ffff 0x4040bfbfDiag Failure: Mode 100 7, U370,U270, 0x00007f7f 0x7f7fffff 0x7f7f8080Diag Failure: Mode 100 7, U370,U270, 0x00008080 0x8080ffff 0x80807f7fDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffffDiag Failure: Mode 100 8, U271, calloc failed, 0Diag Failure: Mode 100 8, U271, calloc failed, 0Finished POST diagsClass 2 Level 2 acq error from sysTaskCreate in acqInit 001:11:45 Fri Apr 26 2024 (thread: tUsrRoot)Class 2 Acquire Id 99 Instance 0 Severity 2 01:11:45 Fri Apr 26 2024 (thread: tUsrRoot) file errPublic.c line 663 (null)errAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVEClass 2 Acquire Id 4 Instance 0 Severity 1 01:11:45 Fri Apr 26 2024 (thread: tUsrRoot) file acqPublic.c line 483 (null)errAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVEAll tasks suspended by errLogDataMsg call from tUsrRooterrSuspendAll called from tUsrRootBacktrace: (depth of 6 shown)/usr/local/bin/scopeApp.ppcep(errSuspendAll+0x6c)/usr/local/bin/scopeApp.ppcep(errLogDataMsg+0x3d0)/usr/local/bin/scopeApp.ppcep(errLogMsg+0x5c)/usr/local/bin/scopeApp.ppcep(_Z8acqErroriiiiPci+0xbc)/usr/local/bin/scopeApp.ppcep(_Z7acqInitv+0x3b0)/usr/local/bin/scopeApp.ppcepClass 22 System Id 0 Instance 22 Severity 2 01:11:45 Fri Apr 26 2024 (thread: tUsrRoot) file sysError.c line 191 (null)cmdParmGetIntMsgPoll() error processing cmd for parm 151, clientId: 0, retCode: -1System status:SheetMemSize=0, TotalNumSheets=0, bus state=-1, xop state=0MeasAbort=0, MathAbort=0CurrentTransactionState=-1, CurrentTransactionParm=Invalid parm idCurrentTransactionType=-1, arg1Type=0, arg2Type=0Sys tasks and their state:NameTaskIdPriPipeMsgs/MaxHandler--------------------------------ext0n/an/aerrSuspendAllThread(): could not suspend fpIntTask, retCode = -1errSuspendAllThread(): could not suspend fpUnloadCmdQueueThread, retCode = -1errSuspendAllThread(): could not suspend fpIrqMonitor, retCode = -1errSuspendAllThread(): could not suspend usbHotplug, retCode = -1errSuspendAllThread(): could not suspend UsbOutputMgr, retCode = -1errSuspendAllThread(): could not suspend piUsb, retCode = -1errSuspendAllThread(): could not suspend piVGpib, retCode = -1errSuspendAllThread(): could not suspend probesSharedUnloadCmdQueueThread, retCode = -1errSuspendAllThread(): could not suspend autoset, retCode = -1errSuspendAllThread(): could not suspend cal, retCode = -1errSuspendAllThread(): could not suspend diag, retCode = -1errSuspendAllThread(): could not suspend fp, retCode = -1errSuspendAllThread(): could not suspend hc, retCode = -1errSuspendAllThread(): could not suspend UsbSicInputMsgMgr, retCode = -1errSuspendAllThread(): could not suspend wfmMgrTest, retCode = -1errSuspendAllThread(): could not suspend search, retCode = -1errSuspendAllThread(): could not suspend periodicZoom, retCode = -1errSuspendAllThread(): could not suspend periodicClockAnimation, retCode = -1errSuspendAllThread(): could not suspend periodicBusyIndicAnimation, retCode = -1errSuspendAllThread(): could not suspend math, retCode = -1errSuspendAllThread(): could not suspend meas, retCode = -1errSuspendAllThread(): could not suspend measImmed, retCode = -1errSuspendAllThread(): could not suspend piCmdIntfc, retCode = -1errSuspendAllThread(): could not suspend ref, retCode = -1errSuspendAllThread(): could not suspend rtl, retCode = -1errSuspendAllThread(): could not suspend tHttpd, retCode = -1errSuspendAllThread(): could not suspend tVxi11SRQd, retCode = -1errSuspendAllThread(): could not suspend tVxi11Rpcd, retCode = -1errSuspendAllThread(): could not suspend bus, retCode = -1errSuspendAllThread(): could not suspend mitlRb, retCode = -1errSuspendAllThread(): could not suspend VgpibRead, retCode = -1errSuspendAllThread(): could not suspend VgpibWrite, retCode = -1errSuspendAllThread(): could not suspend tSocketServerService, retCode = -1errSuspendAllThread(): could not suspend tSocketResponseThread, retCode = -1errSuspendAllThread(): could not suspend UsbTmcEventDispatcher, retCode = -1errSuspendAllThread(): could not suspend inputOverload, retCode = -1errSuspendAllThread(): all threads in list suspendederrSuspendAll(): TASK tUsrRoot SHOULD NOT BE HERE!!!

author: ApertureScience
author_rank: Contributor
timestamp: April 26, 2024, 07:40:29 am
content: I now have error messages regarding DramDqPullUpStrength and DramDqPullDownStrength. Im considering putting the old ram chips back and maybe diong a complete reball of U370.

author: ApertureScience
author_rank: Contributor
timestamp: April 26, 2024, 08:59:22 am
content: I remeasured all 75Ohm termination resistors and some seem to measure around 38Ohm. So probably two lines shorted together. I took off all associated ram and no change. So complete reball of U370 it is. Now waiting for some BGA stencils and solder balls.

author: rainbow
author_rank: Contributor
timestamp: July 21, 2024, 07:09:44 pm
content: Hi ApertureScience,have you fixed the issue reballing U370?Thank you

author: humgar
author_rank: Regular Contributor
timestamp: May 30, 2025, 09:11:38 am
content: 38 ohm sounds like half of 75ohm, so you might have accidentally touched two pins so two parallel resistors are measured the same time.I had the same error message as you did on the console, almost line by line, exceptCode:Dram calibrationdmx 03 ERROR: 08_calDramReceive: Dram2 GrpE alignEdge: sig0 CalMaxZeros: no non-zero valuesdmx 03 ERROR: 08_calDramReceive: Dram2 GrpEF alignEdge: sig0 CalMaxZeros: no non-zero valuesdmx 03: DramCal FAILED *****Dram calibration completeDram Calibration results:-------------------------dmx 02: PASSEDdmx 03: FAILED *****ERROR: 08_calDramReceive: Dram2 GrpE alignEdge: sig0 CalMaxZeros: no non-zero valuesDemux initialization completeI reballed U370 and replaced all the DDR2 chips. For good measure I also replaced the DDR2 voltage regulator LP2996 and nothing changed.