Author Topic: Tek TDS7404 tips about log welcome  (Read 1444 times)

0 Members and 1 Guest are viewing this topic.

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Tek TDS7404 tips about log welcome
« on: December 20, 2020, 05:56:35 pm »
Hallo i am working on the TDS7404 to get it going again. i posted on other topics but there isn t much response coming anymore. Maybe because it is a retired topic.

a few things i want to clear up first i saw in the CSA7404 topic that it was easy to use a default RS232 outbreak cable from one of those old isa cards .
After trying over and over with a freezing console output and scope freezing at random places i decided to make my own custom 3 wired   -> Tek-2-RS232 convertor ;)

And with succes. Now it showed me lots of output and no freeze, compared with the default fully wired outbreak cable i used before. (could have been possible the wired 2nd channel on the J790)

i bought my scope with a corrupted boot messaging it said:  need calibration and was in a sort of cal state?  i didnt get this error out and together with diagnostic error 463 -> OptionST_ok ->Serial Masking, it looked like corruption in my eyes.
despite of the above spoken 463 error, the diagnostic scan gave ALL PASS, i couldn t test the scope inputs and triggers at all because of the call state and corrupted Options.   
- investigating the trigger chip gave me one chip discolored and one chip a small hole next to one pin.  It gave me the thought of how can all (trigger)diagnoses Pass. is it that my chips are still usable, so i will assume that for now.

after i found out that doing a fresh OS install (winxp) instead of W98 didn t get me out of the strange error( read corruption). so i decided to swap NVram the battery.

In the other topic i wrote that i externally feeded the NVram with +4.6 and gnd (to pins 5,17) and did a battery convert.
From that moment things were different:
the scope "service calibration mode or how shall i call it " corruption looked like solved. i can boot into the unit now and change settings.
but also my serial and option key are both empty, not having done a clearDB in the topscript at all.

so what next... let s restore W98 my old original image (i dont know if the scope ever worked with this W98 installation because a lot of files were dated 2018??).
and from my assumption somebody worked on the unit before.
So while looking arround inside the orignal OS in the under the vxboot folder i found the calcons folder, which only had folders named "12" & "16". 

Onces rolling back to my before made ghost image of the original W98 the key were back again.
So while booting up the unit the .SN and .KEY files are read from disk if they are in place of course.  and yet i still didn t do any clearDB =1 action.

So next up was running the scope diagnostics ( output below)  again and all errors include 463 were gone. Only thing left was under MISC it gave me only one error 531 (needs calibration).
So far so good. Next step is to solve the calibration error 531. So after wating for about 20 minutes until the status under calibration showed - TEMP -  i ran Calibrate. ( see output below)
i ran this with case opened and a big full speed blowing fan over the ACQ board and to give you the advise never power-on the scope without a good airflow or you ll burn out parts.

>> at this point info or tips are needed about the CAL output, what can the cal message point me to and why does it say so many:  "can't open file" even if the files are present like "16"

now with the new so called "Tek-2-RS232 convertor":
i ran the diagnosing which outputted to hyperterm:
DIAGNOSTIC EXECUTION begin

0x34fe320 (digHFTask): cc_saveBank: can't open file C:/vxBoot/calCons/16
0x34fe320 (digHFTask): cc_saveBank: can't open file C:/vxBoot/calCons/16
OptionST not tested. (option not enabled)
BK2 not tested (option not enabled)


DIAGNOSTIC EXECUTION finished

and i ran Calibration outputted to hyperterm:
CALIBRATION EXECUTION begin

0x34a1968 (phaseCalAfterDiags): cc_saveBank: can't open file C:/vxBoot/calCons/16
0x34a1968 (phaseCalAfterDiags): cc_saveBank: can't open file C:/vxBoot/calCons/16
0x365fd70 (CalWatch): Temperature transition out of SPC-supporting range.
0x34fd590 (SPC task): cc_saveBank: can't open file C:/vxBoot/calCons/16
0x34fd590 (SPC task): cc_saveBank: can't open file C:/vxBoot/calCons/16
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain1c was 0; clipped
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain1d was 0; clipped
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain2c was 0; clipped
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain2d was 0; clipped
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain3a was 0; clipped
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain3b was 0; clipped
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain4a was 0; clipped
0x34fd590 (SPC task): cc_loadV: CC_TRIGdcGain4b was 0; clipped
0x34fd590 (SPC task): cc_restoreBank: can't open file C:/vxBoot/calCons/9
0x34fd590 (SPC task): cc_restoreBank: can't open file C:/vxBoot/calCons/14
0x34fd590 (SPC task): cc_restoreBank: can't open file C:/vxBoot/calCons/13
0x34fd590 (SPC task): cc_restoreBank: can't open file C:/vxBoot/calCons/11
0x34fd590 (SPC task): cc_restoreBank: can't open file C:/vxBoot/calCons/10
0x34fd590 (SPC task): cc_saveBank: can't open file C:/vxBoot/calCons/12
0x365fd70 (CalWatch): Temperature transition into SPC-supporting range.


[editted:]
at start  (CalWatch): Temperature transition out of SPC-supporting range
at the end (CalWatch): Temperature transition into SPC-supporting range.

 

« Last Edit: March 08, 2021, 08:22:42 pm by charlyd »
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #1 on: December 21, 2020, 09:05:29 am »
who can help me out with posting here his debug /console log from the 7404 in a fully working state.  please mark to it if you have or have not swapped out the NVram. I saw already difference before and after swapped and reconfiguring. if you have please also post a good diagnostic and SPC log. that is very usefully to compare and figure out.
« Last Edit: December 21, 2020, 09:09:03 am by charlyd »
 

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #2 on: January 09, 2021, 10:21:56 pm »
Hi Charlyd,
Last year we managed to fix a TDS6604 here - same era and same trigger chips.
Strangely the trigger test is not exhaustive (it would pass) but the unit would always fail SPC.
It was not until we replaced the trigger chip (156-8278-00), that SPC would pass.

The chips are almost* impossible to obtain, however there are two of them on the acq. board.
Depending on which one has failed, or by swapping them around you can have trigger functionality on channels 1 and 2.
Channels 3 and 4 will still work, but can't be used a trigger source.

Just recently we purchased a TS7404 which happens to have a faulty trigger chip and of course dead NVRAM - when I get back to town later this month I'll let you know if we are able to get it back to life.

Cheers,
 - Guy

*PS : The only way I found to obtain trigger chips is to purchase a mule acquisition board and remove them
 
The following users thanked this post: charlyd

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #3 on: January 09, 2021, 10:29:07 pm »
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #4 on: January 11, 2021, 05:34:38 pm »
Hi Guy _ellis thanks for you reply.

so this error is pointing to failing trigger chips? i bought myself a donor board a month ago so swapping is an option.
but strangly there are more strange thing happening and that is what i want to exclude before swapping chips.
for example my calcon file present  where 12 (and 12.stat)  and the last one 16 (and16.stat) only those 4 files are present.

i managed to get my hands on a complete CalCons file set from 1 to 16 and copied them inplace. From what is saw the are not opened at all while in SPC is running.   only some number files are touched.. (looking at the date code of the files)

Is this all because of ..........failing SPC failing trigger chips or is there really some strange things happening .

i post my last console log here   -> and at the bottom the diag -> and below the SPC log.

From what i heared these CalCons files  -named [NUMBER] and [NUMBER].stat files- are newly generated in a working enviroment while running SPC and depending on the available options added to the unit,  different version numbers files will appear.   

can anyone confirm this?

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.4.0
Creation date: Nov  2 2000, 11:03:34




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


boot device          : sm
processor number     : 0
host name            : host
file name            : c:/vxboot/vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.1
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
flags (f)            : 0x1008
target name (tn)     : tds7404
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 interface lo0... done.
PC1 dio device driver installed
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773516
Starting at 0x200000...

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.0 .
                             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 = 16983892 = 0x1032754 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






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

    raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 21815208 = 0x14cdfa8

    excHookAdd(stopStressForException)
value = 16770764 = 0xffe6cc = stopStressForException


    dsyInit
value = 21806440 = 0x14cbd68
    dsyWPApplyNextRegs
value = 16973768 = 0x102ffc8 = 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.0  does not match Boot ROM version 1
.0.4.0
value = 21801184 = 0x14ca8e0

    TmgrInit("/db")
value = 0 = 0x0
    PhxProxyInit
value = 20560480 = 0x139ba60
    rtlInit
value = 0 = 0x0


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

    hwAccount_init
sysEnetAddrGet: cd:5a:1f:e9:f8:a0
value = 0 = 0x0

    GpibInit
value = 267500128 = 0xff1ba60

    wfmMemInit(1)
value = 57781984 = 0x371aee0

    vertInstall
value = 57774948 = 0x3719364

    calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 300 bytes of service cal data from EEPROM[0] into 0x
3719220
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Reading 82 bytes of service cal data from EEPROM[300] into 0
x3719300
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): extd chksum failed, stored = 0xffffffff calc = 0xdb766060
0x16987e0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory

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/1
0x16987e0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
calCo0xnStatus16987e0 (tShell = ): cc_restoreBank: can't open file 0xC:/vxBoot/c
alCons/13355282
0x16987e0 (: value = tShell): 164335cc_init: bank  = 0x2 chksum failed, NOT reset to factory
281ef0x16987e0 (tShell): cc_restoreBank: can't open file     C:/vxBoot/calCons/
3
0x16987e0 (tShell    vertPostCalR): estoreInstallcc_init: bank
3 chksum failed, NOT reset to factory
value = 0x16987e00 (tShell): cc_restoreBank: can't open file  = 0xC:/vxBoot/calC
ons/05
0x16987e0
 (tShell): cc_init: bank
5 chksum failed, NOT reset to factory
    MathMe0xasCreateTheMathand16987e0MeasurementLi (brariestShell): cc_restoreBa
nk: can't open file
C:/vxBoot/calCons/value = 6
0x5760236816987e0 (tShell = 0x): cc_init: bank 36ef1406 chksum failed, NOT reset
 to factory

0x16987e0    initAcqMapper (tShell
): cc_restoreBank: can't open file value = C:/vxBoot/calCons/07
0x16987e0 ( = 0xtShell): cc_init: bank 07 chksum failed, NOT reset to factory

0x16987e0 (    trigMapInittShell
): cc_restoreBank: can't open file vaC:/vxBoot/calCons/lu8e =
0x16987e0 (tShell0): cc_init: bank  = 0x8 chksum failed, NOT reset to factory
00x16987e0 (tShell
): cc_restoreBank: can't open file   C:/vxBoot/calCons/  15dsyMapInit
0x16987e0
 (tShell): cc_init: bank value = 15 chksum failed, NOT reset to factory
00x16987e0 = 0x (tShell): 0Optical hardware is not present.

0x16987e0    mathMapperI (nittShell): initAcqMapper: Enter

value = 0 = 0x0
    utilMapInit
value = 57599712 = 0x36ee6e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20074648 = 0x1325098 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 23692552 = 0x1698508
    dsyMapHookup
value = 23692656 = 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
value = 56567920 = 0x35f2870
    PhxProxyStartup
value = 56517376 = 0x35e6300
    taskDelay(2)
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 56365216 = 0x35c10a0

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 55872864 = 0x3548d60

    enablePowerupDiags = 0
enablePowerupDiags = 0x12fad08: value = 0 = 0x0
    EnableHorizInterpolation=1
new symbol "EnableHorizInterpolation" added to symbol table.
EnableHorizInterpolation = 0x14c93a0: value = 1 = 0x1

    runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
value = 0 = 0x0

    rtlStartup
value = 0 = 0x0

    tsComp
value = 0 = 0x0

    ################### topScript ends ###############################

Done executing startup script c:/vxboot/topscript.hw
KERNEL:  RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->


Run Diagnose
Code: [Select]
DIAGNOSTIC EXECUTION begin
OptionST not tested. (option not enabled)
BK2 not tested (option not enabled)

DIAGNOSTIC EXECUTION finished


SPC RUN
Code: [Select]
0x35c6bd0 (CalWatch): Temperature transition into SPC-supporting range.
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain1c was 0; clipped
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain1d was 0; clipped
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain2c was 0; clipped
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain2d was 0; clipped
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain3a was 0; clipped
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain3b was 0; clipped
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain4a was 0; clipped
0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain4b was 0; clipped




« Last Edit: January 31, 2021, 10:12:01 am by charlyd »
 

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #5 on: January 11, 2021, 09:55:38 pm »
Hi Charlyd,

There is a clue to one problem in your logs -> cc_restoreBank: can't open file   C:/vxBoot/calCons/
Check your vxboot directory on the HDD

Repairing these old birds requires a thorough approach as there may be multiple faults - typically NVRAM + trigger chip.
The 6604 we fixed last year had 3 hardware faults (NVRAM, CPU Overheat and trigger chip), and the 7404 we are working on at the moment also has 3 hardware faults (NVRAM, trigger chip and leaky Electro cap).

(i) Check the date/voltage on the NVRAM. If > 10Y replace and re-initialise the contents
(ii) Check the electrolytic caps on the x86 motherboards - if there are any signs of bulging or leakage then replace them
(iii) Run SPC and check console output
(iv) If the SPC reports just a few errors pertaining to trigger, replace discoloured / damaged trigger chip(s) and re-run SPC
(v) If SPC reports multiple errors you may need to replace the Acq. board

I'll be back home next week (it's Summer holidays here) and can run (i) .. (iii) and share the results.

Cheers,
 - Guy

 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #6 on: January 15, 2021, 10:19:42 pm »
Thanks for your reply Guy_Ellis, i copied my whole content from Calibration output in the above post #4  the bottom part

I am wandering if only these 8 lines like:  0x3484270 (SPC task): cc_loadV: CC_TRIGdcGain[XX] was 0; clipped  points to the trigger chips?

If looking on the web i didn t find much CAL/SPC outputs copies in topics from the console port while the unit is in SPC  progress.

I compared and it looked to me that each line pretents the "channel under test" and below the line it displays the error if there is one

so please more info wanted.  as told before all my diags are passed.  apart from "MISC 531 "  (Cal. needed)  or does these  lines mean:  the trigger dcgain = zero   -> conclusion -> clipped -> broken?
i attached a picture from one of my trigger chips from who my first impression would be  -> ok ??
so that is why i ask or can one chip cause trigger problem over all channels ? does one chip influence the other?
who can clear things up so i know for sure before i must start swapping trigger chips ;-)
« Last Edit: January 31, 2021, 10:17:07 am by charlyd »
 

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #7 on: January 15, 2021, 11:21:21 pm »
Hey CharlyD,

I'm back home now and will resume work on the TDS7404 next week, hopefully on Monday.
By the look of it this Acq. board has one faulty trigger chip.

I will capture logs before and after trigger chip replacement.

Cheers,
 - Guy.
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #8 on: January 17, 2021, 06:13:39 pm »
hi guy_ellis, yeah that would be a good idea to see posted here your cal/spc logging output from the console port. before and after replacing a trigger chip. and explained and cleared up which chip display what log output.


[eddited:] part right below is fixed was related to the bootrom update
what is your log output now and do you have  in your bootsettings. other(o)  nvfs=0x1000 or is it empty?
when i put in nvfs=0x1000 my unit hangs while booting.
(is this because of trigger chip /hardware failure).
how does your scope behave with broken chip and as last bootsetting = other(o)  nvfs=0x1000

« Last Edit: January 31, 2021, 10:30:10 am by charlyd »
 

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #9 on: January 18, 2021, 07:40:59 am »
Hi Charlyd,

Ok, let me start with a little good news. I replaced the NVRAM chip and we managed to get the scope to do a complete boot (x86 and PPC)
Attached is the console from the PPC board.

However this unit seems to have other problems. The PPC boot only completes on a cold start. If I try once the unit has warmed up the PPC does not complete booting :-(

Even worse SPC reports pages of errors, so it looks like the Acq. board may have more than just a trigger fault :-(

I have another TDS7404 here, later this week we will fire it up. Maybe I can build one good unit out of the two.

Regards,
 - Guy



 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #10 on: January 18, 2021, 09:10:04 am »
Hi Guy_ellis, just a question did you put a big (18" or even bigger) fan blowing over the unit for the ACQ board and psu before turning on the unit with the case opened?  this is seriously necessary not to cook the unit, see my post #1

btw what do your trigger chips look like? i am trying to get an impression about the lousy quality of the tektronix made trigger chips. I spoke to a good friend of mine yesterday and it is really interresting when and why these chips start to burn out? - aged? - overvoltage? -temp? -bad production quality? or maybe -outer space chip eating bugs  :palm:

i am still very curious to see all sorts of different SPC loggings posted here from (so called) problem units CSA/TDS7254,CSA/TDS7404. so please post your SPC run here. 

what to do: if you fire up the unit with the console port J790 connected it will message after some 20 minutes: 0x3625470 (CalWatch): Temperature transition into SPC-supporting range. or [TEMP] on the LCD.
the press run and wait......and paste the output here.

sometimes by seeing the logs you can make connections between the problems especially for ACQ board problems which can be a mistery. Collecting them here can help other members too.
« Last Edit: January 31, 2021, 10:25:56 am by charlyd »
 

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #11 on: January 19, 2021, 12:14:31 am »
Hi Charly,

You might be right about airflow across the PSU & PPC. I will fit the inner Al. cover and try that and see if it is stable.
If we can achieve stability the we'll run SPC.

As for the Acq. board there is very little airflow down there. Even worse the PCB is upside down, which is a great way to trap heat.
It gets pretty hot down there.
Attached is a photo of the trigger chips.
On the TDS6604 we repaired last year we fitted small heatsinks on the trigger chips to try and keep them a bit cooler.

Regards,
 - Guy.
 

Offline TiN

  • Super Contributor
  • ***
  • Posts: 4308
  • Country: us
  • xDevs.com/live - 24/7 lab feed
    • xDevs.com
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #12 on: January 19, 2021, 03:57:43 am »
U180 looks very dead.  :-BROKE
YouTube | Metrology IRC Chat room | Live-cam | Share T&M documentation? Upload! No MB limit, firmwares, photos.
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #13 on: January 19, 2021, 12:00:57 pm »
@TiN i think you means:  U1801  ;)   ah ok Guy curious about the SPC output when chip are ending (read been warm,hot) or ended (read dead). do you also have picture from after putting on the heatsinks?

@Guy any tips on airflow temperatures for taking them from the board and replacing them.. for not burn them from the board, if i am right these chips have heatsinks on the bottomside soldered to the board as heatspreader.


Last week i updated the Bootrom from 1.0.4.0 to 1.0.8.0 , after that i changes my bootsettings so now ->  other(o) nvfs=0x1000. my unit keeps on going and mount the NVRAM filesystem.
what still can be seen is the checksum error 17 right after "nvMem_read succeeded"
and because i tested my NVram by writing all "aa"  to the chip,  i have to figure out howto reset my mac-adres.

at  hwAccount_init
sysEnetAddrGet: aa:aa:aa:aa:aa:aa

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...


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.8.0
Creation date: Jun 27 2003, 09:52:32




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


boot device          : sm
processor number     : 0
host name            : host
file name            : c:/vxboot/vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
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
other (o)            : nvfs=0x1000

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

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.0 .
                             WDB: Ready.

usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
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 = 23662048 = 0x1690de0
    ld < TekScopeSM.o
value = 23661408 = 0x1690b60

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1692720: value = 23668544 = 0x1692740 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x16909a0: value = 23661056 = 0x1690a00 = 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 = 16983892 = 0x1032754 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






     tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
value = 0 = 0x0
     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16975c0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - n
o programming needed.
value = 1 = 0x1
     cd "pc:"
value = 0 = 0x0

    raxInitializeDevices
done
0x16975c0 (tShell): (Re)starting Acq Processor
value = 21815208 = 0x14cdfa8

    excHookAdd(stopStressForException)
value = 16770764 = 0xffe6cc = stopStressForException


    dsyInit
value = 21806440 = 0x14cbd68
    dsyWPApplyNextRegs
value = 16973768 = 0x102ffc8 = DsyRegisterTable + 0xab0









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

    nvram_initFileSys
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4e9e3

    TmgrInit("/db")
value = 0 = 0x0
    PhxProxyInit
value = 20819072 = 0x13dac80
    rtlInit
value = 0 = 0x0


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

    hwAccount_init
sysEnetAddrGet: aa:aa:aa:aa:aa:aa
value = 0 = 0x0

    GpibInit
value = 267500128 = 0xff1ba60

    wfmMemInit(1)
value = 57781984 = 0x371aee0

    vertInstall
value = 57774948 = 0x3719364

    calConStatus = cc_init(2)
0x16975c0 (tShell): Reading 300 bytes of service cal data from EEPROM[0] into 0x
3719220
0x16975c0 (tShell): nvMem_read succeeded
0x16975c0 (tShell): Reading 82 bytes of service cal data from EEPROM[300] into 0
x3719300
0x16975c0 (tShell): nvMem_read succeeded
0x16975c0 (tShell): extd chksum failed, stored = 0xffffffff calc = 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory

0x16975c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x16975c0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x16975c0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x16975c0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
calC0xonStatus16975c0 (tShell = ): cc_restoreBank: can't open file 0xC:/vxBoot/c
alCons/13355282
0x16975c0: value =  (tShell): 164335cc_init: bank  = 0x2 chksum failed, NOT rese
t to factory
281ef0x16975c0 (
tShell): cc_restoreBank: can't open file     C:/vxBoot/calCons/
3
0x16975c0 (tShell    vertPostCal): RestoreInstallcc_init: bank
3 chksum failed, NOT reset to factory
value = 0x16975c00 (tShell): cc_restoreBank: can't open file  = 0xC:/vxBoot/calC
ons/05
0x16975c0
 (tShell): cc_init: bank
5 chksum failed, NOT reset to factory
    MathM0xeasCreateTheMathan16975c0dMeasurementL (ibrariestShell): cc_restoreBa
nk: can't open file
C:/vxBoot/calCons/value = 6
0x5760236816975c0 (tShell = 0x): cc_init: bank 36ef1406 chksum failed, NOT reset
 to factory

0x16975c0    initAcqMapper (
tShell): cc_restoreBank: can't open file value = C:/vxBoot/calCons/07
0x16975c0 = 0x (tShell): cc_init: bank 07 chksum failed, NOT reset to factory

0x16975c0 (    trigMapInittShell
): cc_restoreBank: can't open file vC:/vxBoot/calCons/al8ue =
0x16975c0 (tShell0): cc_init: bank  = 0x8 chksum failed, NOT reset to factory
00x16975c0 (tShell
): cc_restoreBank: can't open file  C:/vxBoot/calCons/  15 dsyMapInit
0x16975c0
 (tShell): cc_init: bank value = 15 chksum failed, NOT reset to factory
00x16975c0 = 0x (tShell): 0Optical hardware is not present.

0x16975c0    mathMapper (InittShell): initAcqMapper: Enter

value = 0 = 0x0
    utilMapInit
value = 57599712 = 0x36ee6e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20074648 = 0x1325098 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 23687912 = 0x16972e8
    dsyMapHookup
value = 23688016 = 0x1697350
    utilMapHookup
value = 23688048 = 0x1697370

    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 23688008 = 0x1697348
    fastFrameMapHookup
value = 23688032 = 0x1697360
    trigMapHookup
value = 23688040 = 0x1697368
    vertMapHookup
value = 23688032 = 0x1697360
    spcMapHookup
value = 23688032 = 0x1697360
    autosetMapHookup
value = 23688072 = 0x1697388
    timeSyncMapHookup
value = 23688064 = 0x1697380
    auxTrigMapHookup
value = 23688048 = 0x1697370
    dpoMapHookup
value = 23688040 = 0x1697368


    TmgrStartup
value = 56628304 = 0x3601450
    PhxProxyStartup
value = 56577760 = 0x35f4ee0
    taskDelay(2)
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 56365216 = 0x35c10a0

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 56315520 = 0x35b4e80

    enablePowerupDiags = 0
enablePowerupDiags = 0x12fad08: value = 0 = 0x0
    EnableHorizInterpolation=1
new symbol "EnableHorizInterpolation" added to symbol table.
EnableHorizInterpolation = 0x35c6c20: value = 1 = 0x1

    runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
value = 0 = 0x0

    rtlStartup
value = 0 = 0x0

    tsComp
value = 0 = 0x0

    ################### topScript ends ###############################

Done executing startup script c:/vxboot/topscript.hw
KERNEL:  RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->


and from what i read i could also do a
->  cc_init  to reinitialise the scope. I was planning todo this in a later stadium after my Trigger chips are repaired.

anyone ever did the CC_init  command ? 
please post you experience with this command, or tel us all about it.
« Last Edit: January 31, 2021, 10:28:39 am by charlyd »
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #14 on: January 27, 2021, 10:32:56 pm »
last week i fixed my mac-adres by writing the original adress to the correct memory location. so that s fixed.
while waiting for some parts before swapping the trigger chips.
Don t get real much extra SPC info.

any suggestions on:
 
 extd chksum failed, stored 0xfff.....
 CC_init extended bank17 chksum error, NOT reset to factory.

can it be that this error disappears after a passing SPC ??
or is it a in software generate error and can be adjusted by " NOT reset to factory " or when right values are returned "reset to default" or something.
« Last Edit: January 31, 2021, 10:47:17 am by charlyd »
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #15 on: January 31, 2021, 11:03:10 am »
yesterday i worked on an other very strange issue.
I installed a SSD a while ago and it worked ok with the SF810 board. 
Code: [Select]
/ no jumpers on the drive / bios auto detect / direct connected to the cable / without drive bracket / without conversion adapter
[visible in the bios as]
SSD   as primairy   master
CDROM as secondairy master
all worked well and OSses could be installed ok

then i swapped to the newly bought SU810 board with the same config, because i want to end at winXP embedded  with a very small footprint
Code: [Select]
/ no jumpers on the drive / bios auto detect / direct connected to the cable / without drive bracket / without conversion adapter
[visible in the bios as]
SSD   as primairy   master
CDROM as secondairy master
drives were detected as above so no changes were made to the bios drive settings and i started installing W2K, while installing i created a new partition and formatted NTFS.
After the reboot i saw the windows 2000 logo for about 10 seconds and then i got stuck in 0x0000007B (INACCESSIBLE BOOT DEVICE), knowing my SSD is 100% ok.

after troubleshooting for a very long time i figured out that a HDD worked ok and that with an SSD auto detect is not really auto detect in those days bioses.
( both drives HDD and SSD didn t have any jumpers at this time)

so when you go and look inside the bios you see a visual and this looks good but is not!
This is NOT enough.  you have to force your SDD to be the master on the primairy bus. so after placing the right jumper on the drive and the visual doesn t change at all, it all start working.

below you can see what needs to be done
Code: [Select]
/ jumper set to master on the drive / bios no change / direct connected to the cable / without drive bracket / without conversion adapter
[visible in the bios as]
SSD   as primairy   master
CDROM as secondairy master

so keep in mind that jumpering your SSD drive can solve a lot of problems in generally with SSD drives and (older) motherboards.
and then installing Windows 2000 on a SSD was an easy job with a succesfull.

i finished installing wimdows xp embedded pos. and did some tekscope timing.  complete bootup 90sec and shutdown 25sec complete off. 1.0Ghz cpu.
i am still working on getting a 1.4GHz /256/100Mhz Front side bus. But still no succes.


« Last Edit: February 11, 2021, 11:06:00 pm by charlyd »
 

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #16 on: March 05, 2021, 10:11:11 pm »

Hi Charlyd,

Sorry for the delay in coming back to you, work has been very busy lately.

Unfortunately the TDS7704 unit with the faulty trigger chip, might have another fault.
SPC fails big time with pages of error messages. I recall that on the TDS6604 we fixed last year there were only a handful of error messages before we replaced the trigger chip.

Replacing the trigger chips is not too difficult, but due to the board size you might need a second pair of hands.
1. Removal
Apply gel flux to all pins and desolder with a good quality thin wick
Once every pin is desoldered (confirm by probing each pin with a dental pick) put the PCB up on it's edge and heat the PCB directly under the chip with a largish tip in the iron (2-3mm). Use extra solder to improve heat transfer. After 20-30 seconds you should be able to remove chip with a pair of tweezers but keep the heat applied - this is where you need a second set of hands.
2. Cleanup
Using plenty of flux and thin solder wick, remove all excess solder from pads and the area where the slug is soldered - you must get this nice and flat, and clean old flux off with a good flux cleaner.
3. Solder
Apply flux and solder paste on the slug pad on the PCB. I use a low temp paste that melts around 180 degrees.
Drop the chip on and solder two corner pins to hold it in place.
Flip the PCB over and heat the PCB directly under the chip with a largish tip in the iron (2-3mm) for around 30 seconds. Again some extra solder between the tip and the PCB will improve heat transfer.
Flip the PCB over again and confirm that the slug has soldered - push the chip with a small screwdriver and see if it moves. If it does then repeat the heating process.
Once the slug is soldered, solder the rest of the pins and clean any remaining flux off when finished.

Good luck
 - Guy
« Last Edit: March 05, 2021, 10:27:54 pm by Guy_Ellis »
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 SPC or Cal. debugging
« Reply #17 on: March 08, 2021, 08:19:36 pm »
Hi ok,
after some time i managed to change the trigger chips and yes they were both died...

especially the first one took me some time before it was in place how i wanted it and you have to warm up the area arround the chip more then you want but ok.

after booting up the scope with a Fan blowing close over the ACQ board to keep the chips cool and copying in a complete CALcons directory content from an other scope

my SPC still fails.

From what i see in the log i have two problem areas still: ( i copied highlighted parts from the log block )

tips are very welcome, for sure what problem 2 can be??

-------------------------------Problem 1 ------------------------------------
extd chksum failed, stored = 0xffffffff calc = 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory

0x16975c0 (tShell): cc_chkLimits: CC_ACQTI_MAIN_ET_MAX was 162; reset to factory

0x16975c0 (tShell): cc_chkLimits: CC_ACQTI_MAIN_ET_MIN was 984; reset to factory

-------------------------------Problem 2 ------------------------------------

minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
ET cal failure (SLOW FAST)



here is my complete log:
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.8.0
Creation date: Jun 27 2003, 09:52:32




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
other (o)            : nvfs=0x1000

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.0 .
                             WDB: Ready.

usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
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 = 23662048 = 0x1690de0
    ld < TekScopeSM.o
value = 23661408 = 0x1690b60

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1692720: value = 23668544 = 0x1692740 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x16909a0: value = 23661056 = 0x1690a00 = 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 = 16983892 = 0x1032754 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






     tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
value = 0 = 0x0
     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16975c0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - n
o programming needed.
value = 1 = 0x1
     cd "pc:"
value = 0 = 0x0

    raxInitializeDevices
done
0x16975c0 (tShell): (Re)starting Acq Processor
value = 21815208 = 0x14cdfa8

    excHookAdd(stopStressForException)
value = 16770764 = 0xffe6cc = stopStressForException


    dsyInit
value = 21806440 = 0x14cbd68
    dsyWPApplyNextRegs
value = 16973768 = 0x102ffc8 = DsyRegisterTable + 0xab0









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

    nvram_initFileSys
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4e9e3

    TmgrInit("/db")
value = 0 = 0x0
    PhxProxyInit
value = 20819072 = 0x13dac80
    rtlInit
value = 0 = 0x0


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

    hwAccount_init
sysEnetAddrGet: 93:ef:1f:87:c5:2a
value = 0 = 0x0

    GpibInit
value = 267500128 = 0xff1ba60

    wfmMemInit(1)
value = 57781984 = 0x371aee0

    vertInstall
value = 57774948 = 0x3719364

    calConStatus = cc_init(2)
0x16975c0 (tShell): Reading 300 bytes of service cal data from EEPROM[0] into 0x
3719220
0x16975c0 (tShell): nvMem_read succeeded
0x16975c0 (tShell): Reading 82 bytes of service cal data from EEPROM[300] into 0
x3719300
0x16975c0 (tShell): nvMem_read succeeded
0x16975c0 (tShell): extd chksum failed, stored = 0xffffffff calc = 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory

0x16975c0 (tShell): cc_chkLimits: CC_ACQTI_MAIN_ET_MAX was 162; reset to factory

0x16975c0 (tShell): cc_chkLimits: CC_ACQTI_MAIN_ET_MIN was 984; reset to factory

0x16975c0 (tShell): Optical hardware is not present.
calConStatus = 0x1335528: value = 131072 = 0x20000

    vertPostCalRestoreInstall
value = 0 = 0x0

    MathMeasCreateTheMathandMeasurementLibraries
value = 57602368 = 0x36ef140
    initAcqMapper
0x16975c0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
    trigMapInit
value = 0 = 0x0
    dsyMapInit
value = 0 = 0x0
    mathMapperInit
value = 0 = 0x0
    utilMapInit
value = 57599712 = 0x36ee6e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20074648 = 0x1325098 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 23687912 = 0x16972e8
    dsyMapHookup
value = 23688016 = 0x1697350
    utilMapHookup
value = 23688048 = 0x1697370

    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 23688008 = 0x1697348
    fastFrameMapHookup
value = 23688032 = 0x1697360
    trigMapHookup
value = 23688040 = 0x1697368
    vertMapHookup
value = 23688032 = 0x1697360
    spcMapHookup
value = 23688032 = 0x1697360
    autosetMapHookup
value = 23688072 = 0x1697388
    timeSyncMapHookup
value = 23688064 = 0x1697380
    auxTrigMapHookup
value = 23688048 = 0x1697370
    dpoMapHookup
value = 23688040 = 0x1697368


    TmgrStartup
value = 56625168 = 0x3600810
    PhxProxyStartup
value = 56574624 = 0x35f42a0
    taskDelay(2)
0x3681ea0 (tmgr): >> optNewOptKey: Bad instru Id
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 56270400 = 0x35a9e40

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 56356992 = 0x35bf080

    enablePowerupDiags = 0
enablePowerupDiags = 0x12fad08: value = 0 = 0x0
    EnableHorizInterpolation=1
new symbol "EnableHorizInterpolation" added to symbol table.
EnableHorizInterpolation = 0x14bc7e0: value = 1 = 0x1

    runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
ET cal failure (SLOW FAST)
value = 0 = 0x0

    rtlStartup
value = 0 = 0x0

    tsComp
value = 0 = 0x0

    ################### topScript ends ###############################

Done executing startup script c:/vxboot/topscript.hw
KERNEL:  RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
DIAGNOSTIC EXECUTION begin
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
ET cal failure (SLOW FAST)
OptionST not tested. (option not enabled)
BK2 not tested (option not enabled)

DIAGNOSTIC EXECUTION finished
Started SPC ( Calibration )
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
ET cal failure (SLOW FAST)
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
minMain 2000; maxMain 0; minDelay 2000; maxDelay 0
total Acqs 100001; Acqs without change 0; fail
metaMti 100000; metaDti 0; metaMAT 0; metaMUT 0; metaDUT 0
measureTIrangeAndOffset() failed
ET cal failure (SLOW FAST)


« Last Edit: March 16, 2021, 04:22:23 pm by charlyd »
 

Offline Guy_Ellis

  • Contributor
  • Posts: 9
  • Country: au
Re: Tek TDS7404 tips about log welcome
« Reply #18 on: March 09, 2021, 09:08:12 am »
Hi Charlyd,

I have a second TDS7404 here that looks promising.
It had a faulty NVRAM chip which I have replaced, and fitted a new battery.
I have initialised the NVRAM, and it boots.

I haven't had a chance to run SPC yet, but I have attached the logs below for you to compare.

I've had a look at your logs and wonder if it's is a good idea to use cal files from another scope?
I'm pretty sure these can be regenerated - we just need to figure out how to do that?

Regards,
 - Guy.

CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.8.0
Creation date: Jun 27 2003, 09:52:32




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 interface lo0... done.
PC1 dio device driver installed
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.0 .
                             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 = 16983892 = 0x1032754 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






     tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
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
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 21815208 = 0x14cdfa8

    excHookAdd(stopStressForException)
value = 16770764 = 0xffe6cc = stopStressForException


    dsyInit
value = 21806440 = 0x14cbd68
    dsyWPApplyNextRegs
value = 16973768 = 0x102ffc8 = DsyRegisterTable + 0xab0









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

    nvram_initFileSys
value = 21801184 = 0x14ca8e0

    TmgrInit("/db")
value = 0 = 0x0
    PhxProxyInit
value = 20560480 = 0x139ba60
    rtlInit
value = 0 = 0x0


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

    hwAccount_init
sysEnetAddrGet: 9d:0c:f2:b3:66:9f
value = 0 = 0x0

    GpibInit
value = 267500128 = 0xff1ba60

    wfmMemInit(1)
value = 57781984 = 0x371aee0

    vertInstall
value = 57774948 = 0x3719364

    calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 300 bytes of service cal data from EEPROM[0] into 0x3719220
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Reading 82 bytes of service cal data from EEPROM[300] into 0x3719300
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/1
0x16987e0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x16987e0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/2
0x16987e0 (tShell): cc_init: bank 2 chksum failed, NOT reset to factory
0x16987e0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/3
0x16987e0 (tShell): cc_init: bank 3 chksum failed, NOT reset to factory
calConSta0xtus16987e0 (tShell):  = cc_restoreBank: can't open file 0xC:/vxBoot/calCons/13535528
0x16987e0 (tShell: value = ): cc_init: bank 332635 chksum failed, NOT reset to factory
 = 0x0x81ef16987e0 (tShell):
cc_restoreBank: can't open file     C:/vxBoot/calCons/
6
    vertPostCalRest0xoreInstall16987e0 (
tShell): cc_init: bank value = 6 chksum failed, NOT reset to factory
00x16987e0 = 0x (tShell): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
7
0x16987e0 (
tShell): cc_init: bank     MathMeasCr7eateTheMathandMeasu chksum failed, NOT reset to factory
rem0xentLibraries16987e0
 (tShell): cc_restoreBank: can't open file value = C:/vxBoot/calCons/576023688
 = 0x0x16987e0 (tShell36ef140): cc_init: bank
8 chksum failed, NOT reset to factory
    initAcqMap0xper16987e0 (tShell):
cc_restoreBank: can't open file valuC:/vxBoot/calCons/e 15=
0x16987e0 (tShell0): cc_init: bank 15 = 0x chksum failed, NOT reset to factory
00x16987e0 (tShell
): Optical hardware is not present.
 0x   trigMapInit16987e0
 (tShell): initAcqMapper: Enter
value = 0 = 0x0
    dsyMapInit
value = 0 = 0x0
    mathMapperInit
value = 0 = 0x0
    utilMapInit
value = 57599712 = 0x36ee6e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20074648 = 0x1325098 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 23692552 = 0x1698508
    dsyMapHookup
value = 23692656 = 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
value = 56638608 = 0x3603c90
    PhxProxyStartup
value = 56588064 = 0x35f7720
    taskDelay(2)
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 56365216 = 0x35c10a0

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 55878048 = 0x354a1a0

    enablePowerupDiags = 0
enablePowerupDiags = 0x12fad08: value = 0 = 0x0
    EnableHorizInterpolation=1
new symbol "EnableHorizInterpolation" added to symbol table.
EnableHorizInterpolation = 0x365b480: value = 1 = 0x1

    runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
value = 0 = 0x0

    rtlStartup
value = 0 = 0x0

    tsComp
value = 0 = 0x0

    ################### topScript ends ###############################

Done executing startup script c:/vxboot/topscript.hw
KERNEL:  RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->


 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 tips about log welcome
« Reply #19 on: March 12, 2021, 11:45:29 am »
Hi Guy,
Yes this for sure sound good, to figure out how we can get the right CalCons files in pace.
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 tips about log welcome
« Reply #20 on: March 16, 2021, 05:16:01 pm »
picking up where i left last time i took the best position for the airflow over the chips by turning the unit upside down. and connect my W98 monitor pc with Hyperterm to the console port.
starting the fan and booting up the scope again to see if my option key was in because the last log also gave a bad instrument ID.
so i went throught the menus ans saw empty spaces as for the serial and for the key.  so next step was to look in the vxboot for .sn and .key and it they were empty or not.
and from what i saw the were ok.  |O
ok next step CLEARDB  and see what happens. so i swap out a prepared topscript.hw file with the original one. and told the unit to fully reboot.
After that it stop at the bootsettings. and i think my Nvram batterij had been disconnected for a short while while the scope went upside down for the ACQ board to be build out and in and so on... so i turned the unit on the side with the fan all over the ACQ board after i reassemble the Cpu board to check the NVram.

time to boot up and put in so Tekconnect adapter to see where i was with the triggering of the channels.  i did the simple test for each channel for the first impression. default setup -> autosetup and the trigger source on the channel under test. that look quit ok.
and before the 20 minutes warm up were past i ran the diagnose which end like it always did  alle passed except for MISC 531 (calibration needed). i disconnected all inputs and ran SPC after the unit was warmed up and this time with succes.

i had seen in the SManual to rerun diagnose after SPC was passed so i did and all errors were gone now so that part was fixed.

also from what i saw was that
-  If the trigger chips are failed  only 12 & 16 calcon are modified in date after SPC run.
-  If the trigger chips are working ok calcon files 9 & 12 & 16 are modified with still SPC fail.
-  If the trigger chips are working ok and the right procedure has been followed all files in between and incl. 9-15 has been modified in date.
( as a side note:  the Diagnose and SPC only give output in the console like (not tested option not installed ) for the rest no errors. if there is more visible this is pointing to a problem)

so now i end up with 2 errors still in my log:
- the EEprom error:
extd chksum failed, stored = 0xffffffff calc = 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
- and an error i have since i disconnected the NVram and batterij that the
TmgrInit("/db")
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...

the last error can not be a big one it was never there before so..
but the eeprom checksum error.

does anybody know the adress where to peek for the content or maybe already did this and can give me more info.
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 tips about log welcome
« Reply #21 on: April 15, 2021, 09:38:54 pm »
....bump.....

any tips on resolving the error 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory. 

what points to the nvram checksum fail.
« Last Edit: April 15, 2021, 09:40:38 pm by charlyd »
 

Offline charlyd

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: nl
Re: Tek TDS7404 tips about log welcome
« Reply #22 on: April 20, 2021, 04:31:01 pm »
i added a series of available options to the scope by generating the right option key.
now i have a lot of available option numbers. ST and SM is also enabled but the diagnositics error trigger 463 and  misc 451 are back again.

From reading on the forum i had to rerun the calibration and after that the diagnostics again.
- my SPC is passes  but my diagnostics still shows both errors, do i miss a procedure or adjustment in the scope?

another point for now i which available option number i link to which option i am afraid i have to build a option list?
« Last Edit: April 22, 2021, 10:56:33 am by charlyd »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf