« previous next »
Pages: [1]   Go Down

Author Topic: Tek TDS7404 repair attempt.  (Read 3406 times)

0 Members and 1 Guest are viewing this topic.

Offline JwallingTopic starter

  • Supporter
  • ****
  • Posts: 1517
  • Country: us
  • This is work?
Tek TDS7404 repair attempt.
« on: February 12, 2016, 07:34:12 pm »


Have a Tek TDS7404 on my bench for repair. Scope application hangs after loading Windows 98
Checking the console port, my initial findings were that the Dallas chip was bad:

romPost: PERFORMING NV-MEMORY WALKING-ONE  TEST...
Expected Value: 0x00000001
Actual Value: 0x00000081
Location: 0xFD0E0000
romPost: 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 Actions

performed: 1
02/11/2016 02:38:40 PM,High,~2306.exe (Backdoor.Sdbot) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 36
02/11/2016 02:38:35 PM,High,~719a.exe (Backdoor.Sdbot) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 54
02/11/2016 02:38:30 PM,High,~6376.exe (Backdoor.Litmus (2)) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 32
02/11/2016 02:38:26 PM,High,~00d7.exe (Backdoor.Litmus (2)) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 49
03/06/2015 01:11:42 PM,High,ophcrack-win32-installer-3.6.0.exe (Pwdump) detected by Auto-Protect,Quarantined,Resolved - No Action

Required,Threat Actions performed: 1
11/01/2014 07:04:49 AM,High,wfps08beta.exe (Trojan.ADH) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 1
10/01/2014 03:03:23 PM,High,Trojan.Gen.2 detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions performed: 1
07/21/2014 08:52:08 AM,High,a0156429.exe (Trojan.ADH.2) detected by Auto-Protect,Quarantined,Resolved - No Action Required,Threat Actions

performed: 2
07/21/2014 08:52:08 AM,High,a0156428.exe (Infostealer.Bucuper) detected by Auto-Protect,Quarantined,Resolved - No Action Required,Threat

Actions performed: 1
07/21/2014 05:27:22 AM,High,ofertacoloors_looksafe.exe (Trojan.ADH.2) detected by Virus scanner,Quarantined,Resolved - No Action

Required,Threat Actions performed: 4
07/21/2014 05:27:10 AM,High,ofertacloud_backup_setup.exe (Infostealer.Bucuper) detected by Virus scanner,Quarantined,Resolved - No Action

Required,Threat Actions performed: 2
05/03/2014 08:17:41 AM,Medium,tw562.exe (WS.Reputation.1) detected by Download Insight,Quarantined,Resolved - No Action Required,Threat

Actions performed: 1
10/25/2013 01:24:04 PM,High,gjsphwzf.exe.part (Suspicious.Cloud.9) detected by Download Insight,Quarantined,Resolved - No Action

Required,Threat Actions performed: 1

Rather 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: [Select]
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

romPost: 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 Boot


Copyright 1984-1996  Wind River Systems, Inc.





CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.4.0
Creation date: Nov  2 2000, 11:03:34




Press any key to stop auto-boot...
 1 0
auto-booting...


boot device          : sm
processor number     : 0 
file name            : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
flags (f)            : 0x1008 
target name (tn)     : tds7000
startup script (s)   : c:/vxboot/topscript.hw

Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching networkPC1 dio device driver installed
 interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773516
Starting at 0x200000...

Host Name: bootHost 
User: target 
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008

It always have exactly at this point. Right after the 6008.

It should look like this:

Code: [Select]
Adding 6008 symbols for standalone.
 

 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]            
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]            
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]  
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]] 
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Tektronix HPP - PowerPC 740.  Processor #0.
                              Memory Size: 0x2000000.  BSP version 1.0.8.0 .
                             WDB: Ready.

KERNEL: THERMAL CONTROL INITIATED
Executing 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

« Last Edit: February 12, 2016, 07:41:01 pm by Jwalling »
Logged
Jay

System error. Strike any user to continue.
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 28258
  • Country: nl
    • NCT Developments
Re: Tek TDS7404 repair attempt.
« Reply #1 on: February 12, 2016, 07:42:49 pm »
Sounds like an intermittent contact. Did you reseat (pull out / plug in) all the connectors?
Logged
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline pasta2018

  • Regular Contributor
  • *
  • Posts: 52
  • Country: cn
Re: Tek TDS7404 repair attempt.
« Reply #2 on: July 31, 2020, 11:17:01 pm »
Quote from: Jwalling on February 12, 2016, 07:34:12 pm


Have a Tek TDS7404 on my bench for repair. Scope application hangs after loading Windows 98
Checking the console port, my initial findings were that the Dallas chip was bad:

romPost: PERFORMING NV-MEMORY WALKING-ONE  TEST...
Expected Value: 0x00000001
Actual Value: 0x00000081
Location: 0xFD0E0000
romPost: 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 Actions

performed: 1
02/11/2016 02:38:40 PM,High,~2306.exe (Backdoor.Sdbot) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 36
02/11/2016 02:38:35 PM,High,~719a.exe (Backdoor.Sdbot) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 54
02/11/2016 02:38:30 PM,High,~6376.exe (Backdoor.Litmus (2)) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 32
02/11/2016 02:38:26 PM,High,~00d7.exe (Backdoor.Litmus (2)) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 49
03/06/2015 01:11:42 PM,High,ophcrack-win32-installer-3.6.0.exe (Pwdump) detected by Auto-Protect,Quarantined,Resolved - No Action

Required,Threat Actions performed: 1
11/01/2014 07:04:49 AM,High,wfps08beta.exe (Trojan.ADH) detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions

performed: 1
10/01/2014 03:03:23 PM,High,Trojan.Gen.2 detected by Virus scanner,Quarantined,Resolved - No Action Required,Threat Actions performed: 1
07/21/2014 08:52:08 AM,High,a0156429.exe (Trojan.ADH.2) detected by Auto-Protect,Quarantined,Resolved - No Action Required,Threat Actions

performed: 2
07/21/2014 08:52:08 AM,High,a0156428.exe (Infostealer.Bucuper) detected by Auto-Protect,Quarantined,Resolved - No Action Required,Threat

Actions performed: 1
07/21/2014 05:27:22 AM,High,ofertacoloors_looksafe.exe (Trojan.ADH.2) detected by Virus scanner,Quarantined,Resolved - No Action

Required,Threat Actions performed: 4
07/21/2014 05:27:10 AM,High,ofertacloud_backup_setup.exe (Infostealer.Bucuper) detected by Virus scanner,Quarantined,Resolved - No Action

Required,Threat Actions performed: 2
05/03/2014 08:17:41 AM,Medium,tw562.exe (WS.Reputation.1) detected by Download Insight,Quarantined,Resolved - No Action Required,Threat

Actions performed: 1
10/25/2013 01:24:04 PM,High,gjsphwzf.exe.part (Suspicious.Cloud.9) detected by Download Insight,Quarantined,Resolved - No Action

Required,Threat Actions performed: 1

Rather 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: [Select]
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

romPost: 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 Boot


Copyright 1984-1996  Wind River Systems, Inc.





CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.4.0
Creation date: Nov  2 2000, 11:03:34




Press any key to stop auto-boot...
 1 0
auto-booting...


boot device          : sm
processor number     : 0 
file name            : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
flags (f)            : 0x1008 
target name (tn)     : tds7000
startup script (s)   : c:/vxboot/topscript.hw

Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching networkPC1 dio device driver installed
 interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773516
Starting at 0x200000...

Host Name: bootHost 
User: target 
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008

It always have exactly at this point. Right after the 6008.

It should look like this:

Code: [Select]
Adding 6008 symbols for standalone.
 

 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]            
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]            
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]  
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]] 
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Tektronix HPP - PowerPC 740.  Processor #0.
                              Memory Size: 0x2000000.  BSP version 1.0.8.0 .
                             WDB: Ready.

KERNEL: THERMAL CONTROL INITIATED
Executing 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

Mine is also stop at adding 6008 sometime，really confusing
Logged
 

Offline JwallingTopic starter

  • Supporter
  • ****
  • Posts: 1517
  • Country: us
  • This is work?
Re: Tek TDS7404 repair attempt.
« Reply #3 on: August 01, 2020, 08:39:22 am »
I ended up replacing the PPC board.
Logged
Jay

System error. Strike any user to continue.
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 543
  • Country: nl
Re: Tek TDS7404 repair attempt.
« Reply #4 on: December 20, 2020, 08:11:16 am »
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.
« Last Edit: December 20, 2020, 08:18:11 am by charlyd »
Logged
 

Offline m k

  • Super Contributor
  • ***
  • Posts: 2550
  • Country: fi
Re: Tek TDS7404 repair attempt.
« Reply #5 on: December 20, 2020, 03:06:01 pm »
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.
Logged
Advance-Aneng-Appa-AVO-Beckman-Danbridge-Data Tech-Fluke-General Radio-H. W. Sullivan-Heathkit-HP-Kaise-Kyoritsu-Leeds & Northrup-Mastech-OR-X-REO-Simpson-Sinclair-Tektronix-Tokyo Rikosha-Topward-Triplett-Tritron-YFE
(plus lesser brands from the work shop of the world)
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 543
  • Country: nl
Re: Tek TDS7404 repair attempt.
« Reply #6 on: January 12, 2021, 08:59:52 pm »
i had something similair stopping halfway the boot process.
i looked into my bootsettings. believe me or not after clearing other(o)  nvfs =0x1000
so empty this option. then my scope booted ok
Logged
 
Pages: [1]   Go Up
« previous next »

Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf

 


EEVblog Main Site EEVblog on Youtube EEVblog on Twitter EEVblog on Facebook EEVblog on Odysee