Author Topic: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)  (Read 115803 times)

0 Members and 1 Guest are viewing this topic.

Offline CSmith

  • Supporter
  • ****
  • Posts: 23
  • Country: us
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #50 on: August 26, 2014, 03:04:29 am »
Are you connecting at the J790 right-angle dual-row 10-pin header with RS-232 levels or at the MAX232 with TTL levels like TiN did? The data may be inverted depending upon your expectations.
 

Offline LostPhoton

  • Contributor
  • Posts: 9
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #51 on: August 26, 2014, 03:30:38 am »
I connected to the MAX232, should I be using the J790? if so do you know the pinout for it?
 

Offline LostPhoton

  • Contributor
  • Posts: 9
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #52 on: August 30, 2014, 03:27:55 am »
Please, if anyone knows the pinout for the console port. I would be very grateful.
 

Offline TiN

  • Super Contributor
  • ***
  • Posts: 3900
  • Country: tw
  • xDevs.com/live - 24/7 lab feed
    • xDevs.com
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #53 on: August 30, 2014, 03:38:00 am »
Its pretty easy to probe pinout with just DMM. I did not use console port because I have plenty USB-UART(TTL) adapters using Silabs CP2103 bridge, but no RS232, so i needed to hook on TTL side of MAX :)

Its really not much things can go wrong, unless your bridge dongle somewhat faulty.
Make sure you have robust ground connection between pc and scope.
YouTube | Chat room | Live-cam | Have documentation to share? Upload here! No size limit, firmware dumps, photos.
 

Offline LostPhoton

  • Contributor
  • Posts: 9
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #54 on: August 30, 2014, 03:44:43 am »
I guess I'm still confused, and thanks again for your help. I'm using a SiLabs CP2102-EB, do I connect to the console or the MAX?
 

Offline TiN

  • Super Contributor
  • ***
  • Posts: 3900
  • Country: tw
  • xDevs.com/live - 24/7 lab feed
    • xDevs.com
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #55 on: August 30, 2014, 03:48:19 am »
If your board have level convertor before cp2102 then you can use console port.

If not then u need use TTL pins on MAX.
You can search for information regarding difference between UART and RS232 voltage levels and convertors.

Will all due respect, given that you messing with internals of hiend scope, you should know that anyway ;)
YouTube | Chat room | Live-cam | Have documentation to share? Upload here! No size limit, firmware dumps, photos.
 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #56 on: September 17, 2014, 08:38:42 am »
I connected to the MAX232, should I be using the J790? if so do you know the pinout for it?

the pins are connected to the max232 through 100 ohm resistors
 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #57 on: September 18, 2014, 05:12:35 am »
 Recently I came into possession of a tds7104.  At first it seemed as if, its just the NVRAM battery problem (scope app splash screen can't start). After i made a backup of the old hdd (win 98) when i noticed that the diagnostic led just shows ".8". I tried to look at the boot up process from the Rs232 console, but it seems as if nothing goes on. In the service manual it is shown, that the UART initialization , takes place after the first test is concluded. So am i missing something or it is a fault in the power pc board?
« Last Edit: September 18, 2014, 05:14:07 am by matyco »
 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #58 on: September 22, 2014, 05:35:16 am »
I have been probing around the MCU on the power pc board. It seems as one or more of the power rails has have been shorted. C352: 3,19V , C235 0,84V C240 & C143: 0,85V(this should be2,5V from the dc/dc)  C232:0,52V (while the main 3,3V lines seem to be fine)

U442 marked "BeY" i think it's a  AND gate or maybe a TVS. It seems to be damaged, aleast between  pin 5(VCC) and pin 3(GND) it measures a few tens of ohms (30-80). So i need to find or atleast locate another faulty chip nearby

Turns out the PT6409P (2,5V switching reg died) after i wired the 2,5V line from a powersupply the powerpc board finaly showed somthing other then .8  the diagnostic led showes 0 or 3 so it seems somthing is still wrong with the MCU (CR874 indicates reset at times)  still nothing on uart. It seems i need to replace the board...

Update:

 There might be still hope ! After replacing the 2 SO8 transistor pair on the PT6409P ( Si4431 , Si4412 i could only source 4410 but it seems to work fine) the power pc board cycles through it's tests and finialy boots if assembled, untill  the screens shows a blue screen memory parity error

here is what i got on the console port (witha newly installed xp and 2.5.3 firmware):
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.

Hel










                            VxWorks System Boot


Copyright 1984-1996  Wind River Systems, Inc.





CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.3.0
Creation date: Jun 28 2000, 16:52:12




Press any key to stop auto-boot...
 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 network inPC1 dio device driver installed
terface 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 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.1 .
                             WDB: Ready.

KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topScript.hw ...
dbFsIoctl: invalid code 3
    ################### topScript starts ###############################




     cd "dbfs:c:/vxBoot"
value = 0 = 0x0


    ld < TekScope.o
value = 23666688 = 0x1692000
    ld < TekScopeSM.o
value = 23666048 = 0x1691d80

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1693940: value = 23673184 = 0x1693960 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691bc0: value = 23665696 = 0x1691c20 = pDBfs + 0x60
    copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0

    overrideFPdefaults()
value = 0 = 0x0

    measurePPCtimebase
value = 0 = 0x0


    registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0

    semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00

    initSysWaiter()
value = 0 = 0x0




    raxInit
value = 0 = 0x0
    paiInit
done
value = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
value = 1 = 0x1
     cd "pc:"
value = 0 = 0x0

    raxInitializeDevices
0x16987e0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0

    excHookAdd(stopStressForException)
value = 17557980 = 0x10be9dc = stopStressForException


    dsyInit
value = 21806728 = 0x14cbe88
    dsyWPApplyNextRegs
value = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0









    # remove '#' from next line to set powerup scope state to factory default:
    # NvramClearDb = 1

    nvram_initFileSys
0x16987e0 (tShell): >> Kernel version 1.0.8.1  does not match Boot ROM version 1.0.3.0
value = 21801472 = 0x14caa00

    TmgrInit("/db")
value = 0 = 0x0
    PhxProxyInit
value = 20822560 = 0x13dba20
    rtlInit
value = 0 = 0x0

    sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0

    hwAccount_init
0x16987e0 (tShell): >> Setting PLL to 1.25e+09 Hz.
sysEnetAddrGet: cc:aa:88:ba:da:dd
value = 7 = 0x7

    GpibInit
value = 133284512 = 0x7f1c2a0

    wfmMemInit(1)
value = 47300320 = 0x2d1bee0

    vertInstall
value = 47293284 = 0x2d1a364

    calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x2d1a240
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0x2d1a300
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x16987e0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x16987e0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/calCon1Status
0x16987e0 (tShell = ): cc_init: bank 0x1 chksum failed, NOT reset to factory
1341eec0x16987e0: value =  (tShell): 131055cc_restoreBank: can't open file C:/vxBoot/calCons/ =2 0x
0x16987e0 (tShell1ffef): cc_init: bank
2 chksum failed, NOT reset to factory

0x16987e0 (tShell    updateTrigCal):
cc_restoreBank: can't open file value C:/vxBoot/calCons/= 30
0x16987e0 (tShell):  = 0xcc_init: bank 03 chksum failed, NOT reset to factory

0x16987e0 (tShell):
cc_restoreBank: can't open file     MC:/vxBoot/calCons/at5hMeasCreateTheMatha
ndMeasurementLibrar0xies16987e0 (tShell):
cc_init: bank 5 chksum failed, NOT reset to factory
valu0xe = 16987e0 (tShell47120704): cc_restoreBank: can't open file  = 0xC:/vxBoot/calCons/2cf01406
0x16987e0
 (tShell): cc_init: bank     initA6cqMapper chksum failed, NOT reset to factory

0x16987e0 (tShellvalue = ): cc_restoreBank: can't open file 0C:/vxBoot/calCons/ = 0x7
0x16987e00 (tShell): cc_init: bank
7 chksum failed, NOT reset to factory
    trigMapIn0xit16987e0 (tShell):
cc_restoreBank: can't open file valueC:/vxBoot/calCons/ =8
0x16987e0 (tShell): 0cc_init: bank 8 chksum failed, NOT reset to factory
 = 00xx16987e0 (tShell): 0cc_restoreBank: can't open file
C:/vxBoot/calCons/    dsy9MapInit
0x16987e0 (tShell
): cc_init: bank value = 9 chksum failed, NOT reset to factory
00x16987e0 ( = 0xtShell): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
10
0x16987e0 (    mathMapperInittShell
): cc_init: bank value = 10 chksum failed, NOT reset to factory
00x16987e0 = 0x (tShell): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
11
0x16987e0    utilMapInit (tShell
): cc_init: bank value = 11 chksum failed, NOT reset to factory
471180480x16987e0 = 0x (tShell): 2cef6e0cc_restoreBank: can't open file
C:/vxBoot/calCons/12
0x16987e0 (tShell
): cc_init: bank     TmgrHookup12 chksum failed, NOT reset to factory

0x16987e0value =  (tShell0): cc_restoreBank: can't open file  = C:/vxBoot/calCons/0x130
0x16987e0 (tShell
): cc_init: bank 13    PhxProxyHookup chksum failed, NOT reset to factory

0x16987e0value =  (tShell0): cc_restoreBank: can't open file  =C:/vxBoot/calCons/ 014x
0x16987e0 (tShell0): cc_init: bank 14
 chksum failed, NOT reset to factory
 0x   hookupAcqMapper16987e0
 (tShell): cc_restoreBank: can't open file value = C:/vxBoot/calCons/2011564752
0x16987e0 (tShell = 0x): cc_init: bank 133b09015 chksum failed, NOT reset to factory
 = 0x16987e0AcqMapperRtlDat (aListtShell): cc_restoreBank: can't open file
C:/vxBoot/calCons/    MathMeasM16apHookup
0x16987e0 (
tShell): cc_init: bank value = 16 chksum failed, NOT reset to factory
23692550x216987e0 (tShell):  = 0xcc_loadV: CC_TRIGtrigLineGain16985 was 08>; clipped
0x
16987e0 (tShell):     dsyMapHookupcc_chkLimits:
CC_TRIGtrigLineGain was ; reset to factory
value0x = 16987e0 (tShell): 23692656initAcqMapper: Enter
 = 0x1698570
    utilMapHookup
value = 23692688 = 0x1698590

    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 23692648 = 0x1698568
    fastFrameMapHookup
value = 23692672 = 0x1698580
    trigMapHookup
value = 23692680 = 0x1698588
    vertMapHookup
value = 23692672 = 0x1698580
    spcMapHookup
value = 23692672 = 0x1698580
    autosetMapHookup
value = 23692712 = 0x16985a8
    timeSyncMapHookup
value = 23692704 = 0x16985a0
    auxTrigMapHookup
value = 23692688 = 0x1698590
    dpoMapHookup
value = 23692680 = 0x1698588


    TmgrStartup
0x2c9cf40 (tmgr):
                TmgrTaskInit: Last powerup failed, going to default setup
value = 46644144 = 0x2c7bbb0
    PhxProxyStartup
value = 46578592 = 0x2c6bba0
    taskDelay(2)
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 46478848 = 0x2c53600

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006

and the boot with the "original" win98 and firmware:
Code: [Select]
done.
Attaching network PC1 dio device driver installed
interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773508
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 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.7.1 .
                             WDB: Ready.

KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topScript.hw ...
dbFsIoctl: invalid code 3
    ################### topScript starts ###############################




     cd "dbfs:c:/vxBoot"
value = 0 = 0x0


    ld < TekScope.o
value = 23666688 = 0x1692000
    ld < TekScopeSM.o
value = 23666048 = 0x1691d80

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1693940: value = 23673184 = 0x1693960 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691bc0: value = 23665696 = 0x1691c20 = pDBfs + 0x60
    copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0

    overrideFPdefaults()
value = 0 = 0x0

    measurePPCtimebase
value = 0 = 0x0


    registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0

    semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00

    initSysWaiter()
value = 0 = 0x0




    raxInit
value = 0 = 0x0
    paiInit
done
value = 17800576 = 0x10f9d80 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): Processor failed to verify after byte #0.
Burning new AVR processor code.
0x16987e0 (tShell): 1340 bytes successfully programmed.
value = 1 = 0x1
     cd "pc:"
value = 0 = 0x0

    raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0

    excHookAdd(stopStressForException)
value = 17589548 = 0x10c652c = stopStressForException


    dsyInit
value = 21807176 = 0x14cc048
    dsyWPApplyNextRegs
value = 17790452 = 0x10f75f4 = DsyRegisterTable + 0xab0









    # remove '#' from next line to set powerup scope state to factory default:
    # NvramClearDb = 1

    nvram_initFileSys
0x16987e0 (tShell): >> Kernel version 1.0.7.1  does not match Boot ROM version 1.0.3.0
value = 21801920 = 0x14cabc0

    TmgrInit("/db")
value = 0 = 0x0
    PhxProxyInit
value = 20817184 = 0x13da520
    rtlInit
value = 0 = 0x0

    sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0

    hwAccount_init
sysEnetAddrGet: cc:aa:88:ba:da:dd
value = 7 = 0x7

    GpibInit
value = 133684384 = 0x7f7dca0

    wfmMemInit(1)
value = 47697632 = 0x2d7cee0

    vertInstall
value = 47690596 = 0x2d7b364

    calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x2d7b240
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0x2d7b300
0x16987e0 (tShell): nvMem_read succeeded
calConStatus = 0x1342b14: value = 0 = 0x0

    updateTrigCal
value = 0 = 0x0

    MathMeasCreateTheMathandMeasurementLibraries
value = 47518016 = 0x2d51140
    initAcqMapper
0x16987e0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
    trigMapInit
value = 0 = 0x0
    dsyMapInit
value = 0 = 0x0
    mathMapperInit
value = 0 = 0x0
    utilMapInit
value = 47515360 = 0x2d506e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20167864 = 0x133bcb8 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 23692552 = 0x1698508
    dsyMapHookup
value = 23692656 = 0x1698570
    utilMapHookup
value = 23692688 = 0x1698590

    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 23692656 = 0x1698570
    fastFrameMapHookup
value = 23692672 = 0x1698580
    trigMapHookup
value = 23692680 = 0x1698588
    vertMapHookup
value = 23692672 = 0x1698580
    spcMapHookup
value = 23692672 = 0x1698580
    autosetMapHookup
value = 23692712 = 0x16985a8
    timeSyncMapHookup
value = 23692704 = 0x16985a0
    auxTrigMapHookup
value = 23692688 = 0x1698590
    dpoMapHookup
value = 23692680 = 0x1698588


    TmgrStartup
0x2cfe0c0 (tmgr):
                TmgrTaskInit: Last powerup failed, going to default setup
value = 47056848 = 0x2ce07d0
    PhxProxyStartup
value = 46991296 = 0x2cd07c0
    taskDelay(2)
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 46891568 = 0x2cb8230

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 4663012


« Last Edit: October 04, 2014, 12:05:17 am by matyco »
 

Offline LostPhoton

  • Contributor
  • Posts: 9
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #59 on: September 24, 2014, 03:17:09 am »
Thanks for your help with the pinout! I've reconfigured the boot parameters in the NVRAM successfully.

Sadly it seems like a BIOS issue now, I'm unable to get into the BIOS to make sure it sees the HD. I've tried the bios jumper to no avail.
Does anyone know if there is a trick to get into the BIOS? F2 key brings up the "Entering Setup", but it never actually enters the BIOS, just continues to try and boot from the network.  Ideas?

Thanks
 

Offline TiN

  • Super Contributor
  • ***
  • Posts: 3900
  • Country: tw
  • xDevs.com/live - 24/7 lab feed
    • xDevs.com
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #60 on: September 24, 2014, 09:46:36 am »
Wierd, just tried on my CSA, it enters BIOS just fine with F2 key.
Shows Entering setup... then bar on bottom loads and it's in the BIOS like Flynn..
YouTube | Chat room | Live-cam | Have documentation to share? Upload here! No size limit, firmware dumps, photos.
 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #61 on: September 25, 2014, 04:42:53 am »
There is an option in it's bios to lockout the setup in security, by default it should be disabled. Try to remove the NLX battery and short the sockets pins fora few sec then place back the battery (that should reset to some factory settings in theory)
« Last Edit: October 04, 2014, 12:48:21 am by matyco »
 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #62 on: October 06, 2014, 08:46:13 pm »
Just to be sure i tried it also with a new NVRAM module, after messing with the boot parameters i could get it to boot till windows but the vxWorks systematically froze at points, with a ping sound on the rs232 terminal (with the wrong boot parameters, yet the QA+tests finished without an error) or get a blue screen (parity error) randomly while the vxWorks almost finished loading. (L->-P-> "-" blinked and the power pc board shut down) Occasionally the scope stoped with ".6" diagnostics error which is again related to the dram. So in conclusion i think there's something wrong with the power pc ram module. Or some other logic ic on that low ohms 5V rail...
« Last Edit: October 06, 2014, 08:48:11 pm by matyco »
 

Offline LostPhoton

  • Contributor
  • Posts: 9
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #63 on: October 08, 2014, 03:53:58 am »
I tried shorting the pins on the NLX battery, no luck. What's interesting is I have a CSA8000 as well and it does the same exact thing. The "entering setup" flashes a few times and then it continues to boot without entering setup.  |O .....
 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #64 on: October 08, 2014, 07:40:27 am »
That's odd. Did you try without the hdd or with the J840 and J841 power pc and display bypass jumpers shorted, on an external monitor?
 

Offline LostPhoton

  • Contributor
  • Posts: 9
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #65 on: October 08, 2014, 08:19:13 am »
Yes, I've tried all jumper combinations including the PPC J840. The only one that causes any difference in startup is with J781 completely removed; then it just beeps. I've been using an external monitor and have tried with both HDD installed, w/o HDD. I've swapped ram to try and trick it to stop for config changes; no change.

Does anyone know what the "DIAG SEL" dip switches are used for on the PPC?

Thanks!

 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #66 on: October 10, 2014, 10:09:16 am »
you can find it in the service manual (the link is posted by TiN or on his site) that sounds as theres something wrong with the mother board or the CPU.  How many beeps ? This might explain why you can't enter bios if the comp part doesn't work there is some mo9re info about bios errors related to start up beeps at the end of the manual also. 
 

Offline matyco

  • Contributor
  • Posts: 13
  • Country: hu
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #67 on: October 11, 2014, 05:56:52 am »
After some more measurements, one pin of the replaced U442 (2 pos input AND gate) didn't reflow properly, i reworked it and now the scope boots and runs the app ! (with the "fresh" NVRAM, for some reason with the old one it keeps hanging while the vx stuff boots) diagnostics and self cal all passed
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 16823
  • Country: nl
    • NCT Developments
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #68 on: October 11, 2014, 05:59:21 am »
That is very well spotted ! :-+ I suppose the scope is working now?
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline LostPhoton

  • Contributor
  • Posts: 9
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #69 on: October 17, 2014, 02:28:36 am »
I'm throwing in the towel on this TDS 7104. If anyone is interested in buying it for parts/repair let me know. I also have a TDS 8000 for parts as well.
Thanks for all your help,
-Kevin
lostphoton@gmail.com
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 16823
  • Country: nl
    • NCT Developments
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #70 on: October 17, 2014, 03:21:31 am »
If I where you I'd put it on Ebay. What do you expect to get for it pricewise?
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1147
  • Country: us
  • This is work?
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #71 on: November 09, 2014, 10:58:56 pm »
Thanks for your help with the pinout! I've reconfigured the boot parameters in the NVRAM successfully.

Sadly it seems like a BIOS issue now, I'm unable to get into the BIOS to make sure it sees the HD. I've tried the bios jumper to no avail.
Does anyone know if there is a trick to get into the BIOS? F2 key brings up the "Entering Setup", but it never actually enters the BIOS, just continues to try and boot from the network.  Ideas?

Thanks

Hello,

I think you will find that if you remove the coin cell on the NLX processor board for a minute or so with the AC power cord disconnected, then put it back in and power up, it will cause the BIOS to get a CMOS checksum error, and prompt you to enter the BIOS setup. You may need to connect an external monitor to the motherboards SVGA video on first power up. In the BIOS there is a setup option to use PCI video which will then cause the scope to use the video located on the power PC board.
I sent you a PM on this, but didn't hear back from you, so I'm posting this here.

Jay
Jay

System error. Strike any user to continue.
 

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1147
  • Country: us
  • This is work?
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #72 on: November 09, 2014, 11:11:25 pm »
A little update, with EEVBlog forum member magic, we can get keys for options on TDS7000/CSA7000 and probably other 70000 series scopes too :)

Quick check of concept proof with my CSA7404:



16 options enabled :)
Need to find out which bit does what and we good to go!

Hi Tin,

I recently picked up a TDS7104 myself. This one was missing it's hard drive. After sorting that out, and repairing a SPC issue I noted two things: It had option 3M which was a nice surprise, but it would crash the tek scope application when I ran the diagnostic.

After fiddling around with different ghost images for the scope and messing around through the console port I found that option 3M had disappeared, but now I have option Jitter analysis 2, which wasn't there before.  |O
Crap! I'd much rather have option 3M back...

I suspect that it was my mucking about with the console port settings. The original looked like this:


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

But it seems I cannot go back to that, as the prompts are now somewhat different.
Update: I also just noticed that the serial number reported in the about menu now does not match what is on the sticker of the unit in the back of the scope. The "about" menu reports it as B021068, but the sticker says it is B021079! I bet that has something to do with it!

Would you have any idea how I could get option 3M back?

Thanks!

Jay
« Last Edit: November 09, 2014, 11:31:10 pm by Jwalling »
Jay

System error. Strike any user to continue.
 
The following users thanked this post: Ice-Tea

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1147
  • Country: us
  • This is work?
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #73 on: November 10, 2014, 02:05:53 am »

Hi Tin,

I recently picked up a TDS7104 myself. This one was missing it's hard drive. After sorting that out, and repairing a SPC issue I noted two things: It had option 3M which was a nice surprise, but it would crash the tek scope application when I ran the diagnostic.

After fiddling around with different ghost images for the scope and messing around through the console port I found that option 3M had disappeared, but now I have option Jitter analysis 2, which wasn't there before.  |O
Crap! I'd much rather have option 3M back...

I suspect that it was my mucking about with the console port settings. The original looked like this:


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

But it seems I cannot go back to that, as the prompts are now somewhat different.
Update: I also just noticed that the serial number reported in the about menu now does not match what is on the sticker of the unit in the back of the scope. The "about" menu reports it as B021068, but the sticker says it is B021079! I bet that has something to do with it!

Would you have any idea how I could get option 3M back?

Thanks!

Jay

Funny - after asking the question and exploring this for awhile I figured it out!
In the folder \vxBoot there are two files .key and .sn The .sn contains the serial number.
I deleted the .key and modified the .sn file with a hex editor so it would have the correct serial number of the scope according to the sticker on the back. I then booted the scope and entered in the option key on the sticker in the rear.
Voila! option 3M is back!  :-+

Jay
Jay

System error. Strike any user to continue.
 

Offline MadTux

  • Frequent Contributor
  • **
  • Posts: 488
Re: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)
« Reply #74 on: November 10, 2014, 07:13:29 am »
Maybe dump your dallas chip?
I'm somewhat planing to get a cheap TDS 7154/7254 once one appears cheaply on ebay and then hack it to 32M.

If there's a collection of NVRAM dumps and their options, we can figure out which bit enables which option, so every TDS owner can hack their scope to 16M/32M memory.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf