Tek TDS7404 repair attempt. - Page 1
Forum section: electronics / repair

author: Jwalling
author_rank: Unknown
timestamp: February 12, 2016, 07:34:12 pm
content: Have a Tek TDS7404 on my bench for repair. Scope application hangs after loading Windows 98Checking the console port, my initial findings were that the Dallas chip was bad:romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...Expected Value: 0x00000001Actual Value: 0x00000081Location: 0xFD0E0000romPost: NV-MEMORY Walking-one test failed.I replaced the DALLAS DS1245YP-100. The chip was a surface mount device, Digikey part # DS1245YP-100+Battery was dead as well, so that was also replaced.Now it (usually) boots OK, but the scope acts very strangely. Odd number-based .exe files were causing crashes in the \Windows\temp\ folder.I suspected that there were one or more virus's on the scope. Sure enough, there was:02/11/2016 02:38:44 PM,High,~2.exe (W32.HLLW.Nebiwo) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actionsperformed: 102/11/2016 02:38:40 PM,High,~2306.exe (Backdoor.Sdbot) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actionsperformed: 3602/11/2016 02:38:35 PM,High,~719a.exe (Backdoor.Sdbot) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actionsperformed: 5402/11/2016 02:38:30 PM,High,~6376.exe (Backdoor.Litmus (2)) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actionsperformed: 3202/11/2016 02:38:26 PM,High,~00d7.exe (Backdoor.Litmus (2)) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actionsperformed: 4903/06/2015 01:11:42 PM,High,ophcrack-win32-installer-3.6.0.exe (Pwdump) detected by Auto-Protect,Quarantined,Resolved - No ActionRequired,Threat Actions performed: 111/01/2014 07:04:49 AM,High,wfps08beta.exe (Trojan.ADH) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actionsperformed: 110/01/2014 03:03:23 PM,High,Trojan.Gen.2 detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions performed: 107/21/2014 08:52:08 AM,High,a0156429.exe (Trojan.ADH.2) detected by Auto-Protect,Quarantined,Resolved - No Action Required,Threat Actionsperformed: 207/21/2014 08:52:08 AM,High,a0156428.exe (Infostealer.Bucuper) detected by Auto-Protect,Quarantined,Resolved - No Action Required,ThreatActions performed: 107/21/2014 05:27:22 AM,High,ofertacoloors_looksafe.exe (Trojan.ADH.2) detected by Virus scanner,Quarantined,Resolved - No ActionRequired,Threat Actions performed: 407/21/2014 05:27:10 AM,High,ofertacloud_backup_setup.exe (Infostealer.Bucuper) detected by Virus scanner,Quarantined,Resolved - No ActionRequired,Threat Actions performed: 205/03/2014 08:17:41 AM,Medium,tw562.exe (WS.Reputation.1) detected by Download Insight,Quarantined,Resolved - No Action Required,ThreatActions performed: 110/25/2013 01:24:04 PM,High,gjsphwzf.exe.part (Suspicious.Cloud.9) detected by Download Insight,Quarantined,Resolved - No ActionRequired,Threat Actions performed: 1Rather than trying to fight these nasty little things, I re-imaged the hard drive with a clean known-good image.Now it's up and running and passes SPC and self tests from the utility menu. No more crashes.However, the last remaining problem is that about 1 in 10 attempts to power up the unit, the PPC board will hang like so:Code:UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: MPC106 Walking-one passed.romPost: MPC106 configuration passed.romPost: First PCI access passed.romPost: PC87560 Walking-one passed.romPost: PC87560 configuration passed.romPost: DEC21554 configuration passed.romPost: PERFORMING ROM CHECKSUM TEST...romPost: ROM checksum passed.romPost: PERFORMING DRAM CELL TEST...romPost: Enabling data cache...romPost: Data cache enabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: DRAM Cell test passed.romPost: Disabling data Cache...romPost: Data cache disabled.romPost: Disabling instruction cache...romPost: Instruction cache disabled.romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...romPost: Writing address to each *address...romPost: Reading address from each *address...romPost: DRAM march test passed...romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...romPost: Enabling data cache...romPost: Data cache enabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: Writing address to each *address...romPost: Reading address from each *address...romPost: DRAM march test passed...romPost: PERFORMING DRAM WALKING-ONE TEST...romPost: DRAM Walking-one test passed.romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...romPost: NV-MEMORY Walking-one test passed.romPost: Disabling data Cache...romPost: Data cache disabled.romPost: Disabling instruction cache...romPost: Instruction cache disabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: POWER-UP DIAGNOSTIC COMPLETE.VxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.4.0Creation date: Nov 2 2000, 11:03:34Press any key to stop auto-boot...1 0auto-booting...boot device : smprocessor number : 0file name : c:/vxboot/vxWorks.stinet on backplane (b): 192.168.0.1:ffffff00host inet (h) : 192.168.0.2gateway inet (g) : 192.168.0.1flags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:/vxboot/topscript.hwInitializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching networkPC1 dio device driver installedinterface lo0... done.Attaching DIO client... done.Loading c:/vxboot/vxWorks.st...1773516Starting at 0x200000...Host Name: bootHostUser: targetInitializing backplane net with anchor at 0x16e0000... done.Backplane anchor at 0x16e0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching network interface lo0... done.Adding 6008It always have exactly at this point. Right after the 6008.It should look like this:Code:Adding 6008 symbols for standalone.]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997CPU: Tektronix HPP - PowerPC 740. Processor #0.Memory Size: 0x2000000. BSP version 1.0.8.0 .WDB: Ready.KERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:/vxboot/topscript.hw ...Once it boots it'll run for hours on end with no issues.Currently, I'm running the scope with the PPC memory and NLX motherboard's memory located on the NLX board. This is allowing me to run Memtest86+ 5.01 on both DIMM modules - so far Memtest has completed one pass with no errors.Any ideas or thoughts are much appreciated.Jay

author: nctnico
author_rank: Super Contributor
timestamp: February 12, 2016, 07:42:49 pm
content: Sounds like an intermittent contact. Did you reseat (pull out / plug in) all the connectors?

author: pasta2018
author_rank: Regular Contributor
timestamp: July 31, 2020, 11:17:01 pm
content: Quote from: Jwalling on February 12, 2016, 07:34:12 pmMine is also stop at adding 6008 sometime，really confusing

author: Jwalling
author_rank: Unknown
timestamp: August 01, 2020, 08:39:22 am
content: I ended up replacing the PPC board.

author: charlyd
author_rank: Frequent Contributor
timestamp: December 20, 2020, 08:11:16 am
content: First i used a default comport outbeak cable, which i had laying arround frm the earlier days, for the console port connecting, that ended up the same for me like you written in the posts above.The scope hanging/freezing half way, for sure too much and wrong wired .SOLVED:Then i made a custom 3 wire adapter only the channel one connected and that workout like a charm.Scope is not hanging anymore and everything is showed in the log while booting.

author: m k
author_rank: Super Contributor
timestamp: December 20, 2020, 03:06:01 pm
content: So other end of console connection is sending wait, my buffer is full?Seems more like the connection is disturbing one input.That can be easily checked with the serial port led tester.If nothing is connected then maybe a statusline loopback can help.(rts-cts and dtr-dsr(-dcd) shorted)Bad connection can do peculiar things.

author: charlyd
author_rank: Frequent Contributor
timestamp: January 12, 2021, 08:59:52 pm
content: i had something similair stopping halfway the boot process.i looked into my bootsettings. believe me or not after clearing other(o) nvfs =0x1000so empty this option. then my scope booted ok