Electronics > Repair
Tek TDS7404 tips about log welcome
charlyd:
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 waiting 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.
charlyd:
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.
Guy_Ellis:
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
Guy_Ellis:
PPS : Meanwhile take a look at this post about NVRAM recovery...
https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/msg3372956/#msg3372956
charlyd:
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: ---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!
->
--- End code ---
Run Diagnose
--- Code: ---DIAGNOSTIC EXECUTION begin
OptionST not tested. (option not enabled)
BK2 not tested (option not enabled)
DIAGNOSTIC EXECUTION finished
--- End code ---
SPC RUN
--- Code: ---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
--- End code ---
Navigation
[0] Message Index
[#] Next page
Go to full version