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

author: zimu0502
author_rank: Newbie
timestamp: September 04, 2020, 01:57:08 am
content: Hello everyone,I have one Tektronix DPO4034B scope,It was normal yesterday,but now stucked at tektronix splash screen.When I press the power on key,A few leds lights on for the first time on the keypad area,one led light on for the second time,and the third time,none leds lights on.But every time there was a relay action sound.I noticed in this posthttps://www.eevblog.com/forum/repair/tektronix-dpo4054-stucked-at-tektronix-splash-screen/msg1405131/#msg1405131,someonesuggested replacing the prescaler for the PA bus. U380 (HMC438),But I can't find it on this model's motherboard.I would appreciate any advice,thanks.

author: tixdave
author_rank: Newbie
timestamp: March 30, 2021, 07:23:20 pm
content: I know this is a little old but maybe it can be revived.I also have a DPO4034B that is stuck on the splash screen. I just found out that the serial debug port is hidden inside of the VGA port, pins 4 (Tx) & 11 (Rx). Baud rate is 115200.The DPO4034B does not have the same prescaler U380 that the DPO4054 has that I can find, but I don't think I am having an issues with that.Looks like my issues may be because of some temp failure?? Not sure why it would just suddenly fail. Any help would be appreciated.Here is the debug output:Code:U-Boot 2009.08 (Mar 03 2011 - 17:01:14) Tektronix, Inc. V1.01CPU: AMCC PowerPC 460EX Rev. B at 600 MHz (PLB=200, OPB=100, EBC=50 MHz)No Security/Kasumi supportBootstrap Option F - Boot ROM Location I2C (Addr 0x54)Internal PCI arbiter disabled32 kB I-Cache 32 kB D-CacheBoard: Tektronix Route66B AMCC 460EX Main Board PVR 130218a4VCO: 1200 MHzCPU: 600 MHzPLB: 200 MHzOPB: 100 MHzEBC: 50 MHzProgramming SDIA...doneI2C: readyDRAM: 512 MB /FLASH: 128 MBPCI: Bus Dev VenId DevId Class Int00 0d 1172 0004 ff00 18In: serialOut: serialErr: serialBoard version: 1 (Proto) 4 channel DPOI/O board version: 3SDIA version: 0133Calibrating VCO...doneNet: ppc_4xx_eth0Enter password - autobooting in 3 seconds## Booting kernel from FIT Image at f8040000 ...Verifying Hash Integrity ... crc32+ sha1+ OK## Loading init Ramdisk from FIT Image at f8040000 ...Verifying Hash Integrity ... crc32+ sha1+ OK## Flattened Device Tree from FIT Image at f8040000Verifying Hash Integrity ... crc32+ sha1+ OKBooting using the fdt blob at 0xf824a230Uncompressing Kernel Image ... OKLoading Ramdisk to 1f130000, end 1f1ff5e6 ... OKLoading Device Tree to 00ffa000, end 00fff0d0 ... OKChecking for firmware update...No USB mass storage devices found to update from.Linux 2.6.31.4 V 1.11 Tektronix BK Mon Feb 13 10:06:16 PST 2012Scope application starting (normal mode)---------------------- startScopeApp() running Init code ----------------------versionBuildFWVersionString(): TimestampString: 15-Nov-12 14:28VersionFIRMWAREVERSIONversion: v2.90Major ver num: 2 Minor ver num: 90Initializing SdiaMain Board HW Rev: 0x09Initializing Tek0005Initializing Ibm460Initializing HFD204ADCInitializing HFD204ADCMain Board HW ID: 0x06AFE Board SW ID: 0x04Main Board SW ID: 0x03Initializing Adt7476HFD144 NOT presentHFD144 NOT presentHFD144 NOT presentHFD144 NOT presentInitializing AfeInitializing MDOInitializing Adf4350Initializing Tek026Initializing Tek026Initializing Tek026Initializing Tek026Initializing Tek026Initializing Dac5571Initializing Tmp421Initializing Tmp421Initializing Tmp421Initializing Tmp421Initializing Tmp421Unrecognized fanControllerMfgId = 0x00.Unknown fanControllerDeviceIdU-Boot 2009.08 (Mar 03 2011 - 17:01:14) Tektronix, Inc. V1.01CPU: AMCC PowerPC 460EX Rev. B at 600 MHz (PLB=200, OPB=100, EBC=50 MHz)No Security/Kasumi supportBootstrap Option F - Boot ROM Location I2C (Addr 0x54)Internal PCI arbiter disabled32 kB I-Cache 32 kB D-CacheBoard: Tektronix Route66B AMCC 460EX Main Board PVR 130218a4VCO: 1200 MHzCPU: 600 MHzPLB: 200 MHzOPB: 100 MHzEBC: 50 MHzProgramming SDIA...doneI2C: readyDRAM: 512 MB /FLASH: 128 MBPCI: Bus Dev VenId DevId Class Int00 0d 1172 0004 ff00 18In: serialOut: serialErr: serialBoard version: 1 (Proto) 4 channel DPOI/O board version: 3SDIA version: 0133Calibrating VCO...doneNet: ppc_4xx_eth0Enter password - autobooting in 3 seconds## Booting kernel from FIT Image at f8040000 ...Verifying Hash Integrity ... crc32+ sha1+ OK## Loading init Ramdisk from FIT Image at f8040000 ...Verifying Hash Integrity ... crc32+ sha1+ OK## Flattened Device Tree from FIT Image at f8040000Verifying Hash Integrity ... crc32+ sha1+ OKBooting using the fdt blob at 0xf824a230Uncompressing Kernel Image ... OKLoading Ramdisk to 1f130000, end 1f1ff5e6 ... OKLoading Device Tree to 00ffa000, end 00fff0d0 ... OKChecking for firmware update...No USB mass storage devices found to update from.Linux 2.6.31.4 V 1.11 Tektronix BK Mon Feb 13 10:06:16 PST 2012Scope application starting (normal mode)---------------------- startScopeApp() running Init code ----------------------versionBuildFWVersionString(): TimestampString: 15-Nov-12 14:28VersionFIRMWAREVERSIONversion: v2.90Major ver num: 2 Minor ver num: 90Initializing SdiaMain Board HW Rev: 0x09Initializing Tek0005Initializing Ibm460Initializing HFD204ADCInitializing HFD204ADCMain Board HW ID: 0x06AFE Board SW ID: 0x04Main Board SW ID: 0x03Initializing Adt7476HFD144 NOT presentHFD144 NOT presentHFD144 NOT presentHFD144 NOT presentInitializing AfeInitializing MDOInitializing Adf4350Initializing Tek026Initializing Tek026Initializing Tek026Initializing Tek026Initializing Tek026Initializing Dac5571Initializing Tmp421Initializing Tmp421Initializing Tmp421Initializing Tmp421Initializing Tmp421Unrecognized fanControllerMfgId = 0x00.Unknown fanControllerDeviceIdfanControlTarget.cpp fanControlSetFactory: Fan Controller MFG ID 0xfffffffe unrecognized.ialInit(): AFE id 0x4, rev 0x5, bI 3Factory Checksum: Stored: 53782, Calculated: 53782 - OKSpc CheckSum: stored: 2270 calculated: 2270 - OKDemux initializationDram calibrationDram calibration completeDram Calibration results:-------------------------DramCal has PASSED on all DemuxsDram calibrationDram calibration completeDram Calibration results:-------------------------DramCal has PASSED on all DemuxsDemux initialization completeStarting POST diagsDiag Failure: Mode 100 0, U3801,Temp, High Limit -5, value 0Diag Failure: Mode 100 0, Ambient,Temp, High Limit -5, value -1Diag Failure: Mode 100 0, U5501,Temp, High Limit -5, value 0 Class 22 System Id 0 Instance 33 Severity 2 20:58:42 Tue Mar 30 2021 (thread: tUsrRoot) file sysError.c line 139 (null)errAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVEClass 20 User Interface Id 0 Instance 401 Severity 1 20:58:42 Tue Mar 30 2021 (thread: tUsrRoot) file uiError.c line 272 (null)errAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVEAll tasks suspended by errLogDataMsg call from tUsrRooterrSuspendAll called from tUsrRoot threadBacktrace: (depth of 18 shown)/usr/local/bin/scopeApp.ppcex(utilBacktrace+0x38)/usr/local/bin/scopeApp.ppcex(errSuspendAll+0x54)/usr/local/bin/scopeApp.ppcex(errLogDataMsg+0x400)/usr/local/bin/scopeApp.ppcex(errMsg+0x5c)/usr/local/bin/scopeApp.ppcex(uiPanic+0x44)/usr/local/bin/scopeApp.ppcex(uiSendEventMsg+0x198)/usr/local/bin/scopeApp.ppcex(diagTemperatureMonitor+0x254)/usr/local/bin/scopeApp.ppcex(_Z16diagTempFunctionv+0x888)/usr/local/bin/scopeApp.ppcex(_Z8diagTempv+0x18)/usr/local/bin/scopeApp.ppcex(_Z11diagRunTestP11TestRoutine+0x38)/usr/local/bin/scopeApp.ppcex(diagRunPostDiags+0xd4)/usr/local/bin/scopeApp.ppcex/usr/local/bin/scopeApp.ppcex(_Z13startScopeAppiPPc+0x164)/usr/local/bin/scopeApp.ppcex(_Z12user_sysinitiPPc+0x2c)/usr/local/bin/scopeApp.ppcex(_Z9root_taskiPPciiiiiiii+0xb0)/usr/local/bin/scopeApp.ppcex(_Z12task_wrapperPv+0x80)/lib/libpthread.so.0/lib/libc.so.6(clone+0x84)Class 22 System Id 0 Instance 22 Severity 2 20:58:42 Tue Mar 30 2021 (thread: tUsrRoot) file sysError.c line 191 (null)cmdParmGetIntMsgPoll() error processing cmd for parm 162, 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:Name TaskId Pri Pipe Msgs/Max Handler---- ------ --- ---- -------- -------ext 0 n/a n/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 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 mask, retCode = -1errSuspendAllThread(): could not suspend math, retCode = -1errSuspendAllThread(): could not suspend meas, retCode = -1errSuspendAllThread(): could not suspend measImmed, retCode = -1errSuspendAllThread(): could not suspend histogram, retCode = -1errSuspendAllThread(): could not suspend piCmdIntfc, retCode = -1errSuspendAllThread(): could not suspend ref, retCode = -1errSuspendAllThread(): could not suspend rf, retCode = -1errSuspendAllThread(): could not suspend rfMeas, retCode = -1errSuspendAllThread(): could not suspend rtl, retCode = -1errSuspendAllThread(): could not suspend thttpd, retCode = -1errSuspendAllThread(): could not suspend external thttpd comms, retCode = -1errSuspendAllThread(): could not suspend dhclient status, retCode = -1errSuspendAllThread(): could not suspend avahi service status, 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 inputOverload, retCode = -1errSuspendAllThread(): could not suspend tSocketServerService, retCode = -1errSuspendAllThread(): all threads in list suspendederrSuspendAll(): TASK tUsrRoot SHOULD NOT BE HERE!!!

author: tixdave
author_rank: Newbie
timestamp: April 14, 2021, 04:54:18 pm
content: I replaced U1101 the ADT7476 but that didn't seam to fix any issues. I thought it might be related to the following issues:Unrecognized fanControllerMfgId = 0x00.Unknown fanControllerDeviceIdfanControlTarget.cpp fanControlSetFactory: Fan Controller MFG ID 0xfffffffe unrecognized.andDiag Failure: Mode 100 0, U3801,Temp, High Limit -5, value 0Diag Failure: Mode 100 0, Ambient,Temp, High Limit -5, value -1Diag Failure: Mode 100 0, U5501,Temp, High Limit -5, value 0 Class 22 System Id 0 Instance 33 Severity 2 20:58:42 Tue Mar 30 2021 (thread: tUsrRoot) file sysError.c line 139 (null)It looks like to me that the reason it is shutting down and suspending all threads is because of the temp failure. I wonder if there is a sperate fan controller than then U1101?Any thoughts or help would be appreciated.Thanks

author: mikehank
author_rank: Regular Contributor
timestamp: March 15, 2022, 08:37:32 pm
content: Believe it or not this is probably a bad I2C repeater on the front panel board. U302 or U306 i cant remember. The fan controller is on the i2c bus and the repeater is weak.

author: tixdave
author_rank: Newbie
timestamp: March 16, 2022, 10:20:47 pm
content: Quote from: mikehank on March 15, 2022, 08:37:32 pmThanks mikehank for the suggestion. It doesn't totally make sense, but I will try replacing the repeater. Looks like it is U306 on the front panel board. I don't have a 9515A on hand, but I do have a 9517A which looks like it can be a functional replacement for the 15A but I will need to get Vcc over to pin 1.

author: tixdave
author_rank: Newbie
timestamp: March 17, 2022, 10:42:14 pm
content: Replaced U306 with a 9517A and it seems to be working. Haven't seen any issues yet and no errors on the serial port! Ran a SPC just fine.Thanks mikehank!

author: mikehank
author_rank: Regular Contributor
timestamp: March 18, 2022, 06:06:15 pm
content: No problem. Also as an FYI if you ever lose fans meaning no spin there are fuses for each fan connector they will sometime get blown. I think this happens when one of the demuxes reports over temp and the fans are asked to work harder than they are supposed to. Fuses are 32VDC .5A. Opps sorry this is for MSO/DPO4K non B's. The B's and MDO's don't have this issue.

author: JohnPi
author_rank: Regular Contributor
timestamp: March 27, 2022, 12:18:13 am
content: I have a DPO4104 that is stuck on the splash -- that comes up in about 10 s. I can't find any debug (or any signals at all) on the VGA port (e.g. pins 4, 11, GND=15). Any other location to look for debug messages ?

author: mikehank
author_rank: Regular Contributor
timestamp: March 28, 2022, 06:03:54 pm
content: zimu0502,The DPO4KB's do not have a prescaler. That function is handed now handled by the trigger chip(Tek005). Anyway to your issue be sure that your comm settings are 115k baud. Also is the front panel on/off led green or orange when you turn the unit on?

author: mikehank
author_rank: Regular Contributor
timestamp: March 29, 2022, 11:01:23 pm
content: JohnPi,Check all the oscillator's around the CPU. The processor has a UART in it and is the source of the boot script. I think its 60mhz clock. But check them all if you can.

author: Samoen
author_rank: Newbie
timestamp: January 14, 2023, 02:49:41 pm
content: Hi Mike,TEK DPO4034BI had the same "stuck at splash screen" issue. Went ahead and followed the advise above, R&R'ed U306 (PN PCA9515ADP), 8TSSOP package, I2C repeater buffer.The scope successfully booted! Warning message appeared at initial startup: "Unit last shutdown unexpectedly due to an over temperature condition. Check fan operation, dust, ect.. or return to TEK for service." New issue, looks like my front panel interface board is not responding now. Front panel lights are lit but no response when operating any functions. See attached for a picture where I'm stuck.CH1 is default on at startup, it measures signal. Display shows current date/ time.Thoughts?

author: mikehank
author_rank: Regular Contributor
timestamp: January 17, 2023, 04:08:16 pm
content: Hi Samoen,Make sure that the cable between the front panel and mainboard is fully inserted on both sides. Its pretty easy to have it only partially seated.

author: Samoen
author_rank: Newbie
timestamp: January 23, 2023, 12:20:38 am
content: Reseated the cable into both boards, no luck. Also ohm'ed it out, the cable is fine.I the buttons on the USB interface board do not work either (Save, Menu, Default Setup, Utility). The only thing that does anything is when I plug a USB stick into the USB port. I get a very brief prompt stating "Please Wait". It comes and goes within a couple msec. I attached a picture for reference.

author: mikehank
author_rank: Regular Contributor
timestamp: January 23, 2023, 05:46:16 pm
content: Hi Samoen,If you pulled the front panel board away from the front chassis make sure the ribbon cable is seated well. Also make sure all the grounding tabs are in properly and not rotated. I suspect the issue was introduced during assembly and is not part of the original defect. Slowly backtrack you assembly and make sure all is well.

author: analogRF
author_rank: Super Contributor
timestamp: July 08, 2023, 03:26:55 am
content: HiCan somebody confirm whether in DPO4034B the +1.5V rail (in the row of power supply test points) is up and running after turning on the scope?I have a DPO4034B stuck at splash screen and the remedies mentioned in this thread didnt help. However, I noticed that all power suppliesare ok except that +1.5V which reads ZEROI have spent a couple of hours trying to trace that rail to where it is generated and/or where it is used with no luckI am beginning to think that maybe it just does not exist on 4034B and only exists on MSO or 4104B or on MDOs?I do not see it being used anywhere on the board except by an uninstalled chip.Still I could be totally wrong and have not seen its origin.