Electronics > Repair
Tektronix TDS7254B Signal Path Compensation fail issue and pass all Diagnostic
snoopy_lei:
Hello everyone,
Would you help me to Close TDS7254B SPC fail issue or give me some suggestions? However thanks for your help in advance.
The TDS7254B can pass all Diagnostic as attach picture and only fail in SPC calibration,however I check the PowerPC board's debug info via few wires to connect PowerPC debug serial port,however the error info as below when run the SPC calibration instruction,
--- Code: ---################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x3814820 (aAcqDpoExecutor): 20OCT19 15:38:45 U
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.80 minutes
--- End code ---
However I have restore the WINXP system with TEK TDS7KB RestoreCD and reinstall the Tekscope software,but the issue same as before,and "M866CompCalibrator 3c Failed" "M866CompCalibrator 4c failed" the info is very confusion,what is M866? It's Chip IC or software instruction? What is 3c and 4c? it's mean the 3rd channel and 4rd Channel? |O
--- Code: ---romPost: I am alive .
uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
romPost: L2 cache turned on.
romPost: MPC107 Walking-one passed.
romPost: MPC107 configuration passed.
romPost: Intel21555 PCITOPCI bridge 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: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
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 - IBM 750CXe
Version: 5.3.1
BSP version: 2.0.1.10
Creation date: Sep 30 2003, 07:53:07
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 networPC1 dio device driver installed
k interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773468
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 6034 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 - IBM 750CXe. Processor #0.
Memory Size: 0x2000000. BSP version 2.0.1.10.
WDB: Ready.
done
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topscript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1692d40: value = 23670112 = 0x1692d60 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691720: value = 23669856 = 0x1692c60
ld < TekScope.o
value = 23657440 = 0x168fbe0
ld < TekScopeSM.o
value = 23660544 = 0x1690800
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
loggerInit
Serial No: B020790
value = 21822832 = 0x14cfd70
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 23661184 = 0x1690a80
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 16129500 = 0xf61ddc = PaiBaseRegisterTable + 0x804
configureACL
SUCCESS
value = 0 = 0x0
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.
logTask: 1 log messages lost.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0
excHookAdd(stopStressForException)
value = 15840048 = 0xf1b330 = stopStressForException
dsyInit
value = 0 = 0x0
dsyWPApplyNextRegs
value = 16110116 = 0xf5d224 = DsyRegisterTable + 0xbd0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
value = 21793056 = 0x14c8920
TmgrInit("/db")
value = 0 = 0x0
PhxProxyInit
value = 20333344 = 0x1364320
rtlInit
value =0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x1c000000
value = 0 = 0x0
hwAccount_init
sysEnetAddrGet: 4d:54:5c:c8:c0:64
Scope Model: TDS7254B
value = 0 = 0x0
GpibInit
value = 502610496 = 0x1df53a40
wfmMemInit(1)
value = 62205664 = 0x3b52ee0
vertInstall
value = 62198148 = 0x3b51184
calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 358 bytes of service cal #1 data from NV[3:0] into 0x3b51000
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Optical hardware is not present.
calConStatus = 0x127d1dc: value = 0 = 0x0
vertPostCalRestoreInstall
value = 0 = 0x0
MathMeasCreateTheMathandMeasurementLibraries
value = 62025376 = 0x3b26ea0
initAcqMapper
0x16987e0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
trigMapInit
value = 0 = 0x0
dsyMapInit
value = 0 = 0x0
mathMapperInit
value = 0 = 0x0
utilMapInit
value = 62019520 = 0x3b257c0
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 19321872 = 0x126d410 = 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 = 61194384 = 0x3a5c090
PhxProxyStartup
value = 61143840 = 0x3a4fb20
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 61017376 = 0x3a30d20
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 60967680 = 0x3a24b00
enablePowerupDiags = 0
enablePowerupDiags = 0x123dbdc: value = 0 = 0x0
runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
<< POWERUP DIAGS FINISHED >>
execution time 0 sec>>
Test "351" - Acquisition-->HFStep-->PhaseCal started
Test execution time 6.3768 sec
value = 0 = 0x0
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
paiPrintVersionNumber
Pai version: 4.52
value = 18 = 0x12
################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x3814820 (aAcqDpoExecutor): 20OCT19 15:38:45 U
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.80 minutes
DIAGNOSTIC EXECUTION begin
Test "111" - Processor-->Memory-->DRAMWalk1 started
Test execution time 6.875e-06 sec
Test "112" - Processor-->Memory-->DRAMCell started
Test execution time 0.047812 sec
Test "113" - Processor-->Memory-->DRAMMarch started
Test execution time 0.014548 sec
Test "121" - Processor-->PCI Bus-->Scan Test started
Test execution time 1.7788e-05 sec
Test "211" - RegAccess-->DACs-->Daculator started
Test execution time 0.00036913 sec
Test "221" - RegAccess-->Direct R/W-->DEMUX started
Test execution time 0.0023205 sec
Test "222" - RegAccess-->Direct R/W-->Dsy started
Test execution time 0.00032442 sec
Test "223" - RegAccess-->Direct R/W-->SBTL started
Test execution time 0.00013178 sec
Test "224" - RegAccess-->Direct R/W-->SGTL started
Test execution time 0.00029986 sec
Test "231" - RegAccess-->IIC-->Pogo_U1 started
Test execution time 0.00040611 sec
Test "241" - RegAccess-->PLL-->Serial started
Test execution time 9.2548e-05 sec
Test "251" - RegAccess-->Serial-->AtoD started
Test execution time 0.00019014 sec
Test "252" - RegAccess-->Serial-->U1093 started
Test execution time 2.7115e-05 sec
Test "253" - RegAccess-->Serial-->U1251 started
Test execution time 0.00019577 sec
Test "254" - RegAccess-->Serial-->U1500 started
Test execution time 0.00027058 sec
Test "311" - Acquisition-->Memory-->MemData started
Test execution time 5.0736 sec
Test "312" - Acquisition-->Memory-->MemAddr started
Test execution time 4.9452 sec
Test "313" - Acquisition-->Memory-->DataFormat started
Test execution time 2.4118 sec
Test "321" - Acquisition-->Acq Modes-->SubSample started
Test execution time 5.3287 sec
Test "322" - Acquisition-->Acq Modes-->PeakDetect started
Test execution time 39.147 sec
Test "323" - Acquisition-->Acq Modes-->HiRes started
Test execution time 5.3411 sec
Test "331" - Acquisition-->Vertical-->50OhmOvld started
Test execution time 0.083668 sec
Test "332" - Acquisition-->Vertical-->ADC Connects started
Test execution time 7.0864 sec
Test "341" - Acquisition-->Interrupt-->Bit Tests started
Test execution time 4.9321 sec
Test "351" - Acquisition-->HFStep-->PhaseCal started
Test execution time 5.8304 sec
Test "361" - Acquisition-->PLL-->Clock Freq started
Test execution time 0.44611 sec
Test "371" - Acquisition-->MemSpeed-->DemuxA started
Test execution time 3.9665 sec
Test "372" - Acquisition-->MemSpeed-->DemuxB started
Test execution time 3.9569 sec
Test "373" - Acquisition-->MemSpeed-->DemuxC started
Test execution time 3.9557 sec
Test "374" - Acquisition-->MemSpeed-->DemuxD started
Test execution time 3.9562 sec
Test "375" - Acquisition-->MemSpeed-->DemuxE started
Test execution time 3.9563 sec
Test "376" - Acquisition-->MemSpeed-->DemuxF started
Test execution time 3.9579 sec
Test "377" - Acquisition-->MemSpeed-->DemuxG started
Test execution time 3.9557 sec
Test "378" - Acquisition-->MemSpeed-->DemuxH started
Test execution time 3.9561 sec
Test "411" - Trigger-->Inputs-->Line started
Test execution time 0.072346 sec
Test "412" - Trigger-->Inputs-->Ch1 started
Test execution time 0.36608 sec
Test "413" - Trigger-->Inputs-->Ch2 started
Test execution time 0.35029 sec
Test "414" - Trigger-->Inputs-->Ch3 started
Test execution time 0.35027 sec
Test "415" - Trigger-->Inputs-->Ch4 started
Test execution time 0.35036 sec
Test "421" - Trigger-->Internals-->TimerA1 started
Test execution time 0.10003 sec
Test "422" - Trigger-->Internals-->TimerA2 started
Test execution time 0.099752 sec
Test "423" - Trigger-->Internals-->Btrig started
Test execution time 0.10234 sec
Test "424" - Trigger-->Internals-->BtrigEvents started
Test execution time 0.11884 sec
Test "425" - Trigger-->Internals-->TimeInterp started
Test execution time 9.3269e-06 sec
Test "426" - Trigger-->Internals-->Holdoff started
Test execution time 0.033352 sec
Test "511" - Misc-->Cal Integrity-->Factory Cal started
Test execution time 6.0577e-06 sec
Test "512" - Misc-->Cal Integrity-->SPC (run SPC) started
Test execution time 1.8269e-06 sec
Test "521" - Misc-->GPIB-->Interface started
Test execution time 0.0005699 sec
DIAGNOSTIC EXECUTION finished in 115.5 sec
--- End code ---
snoopy_lei:
After I warmed up all night, I ran SPC again and displayed the following message.the "CC_TRIGdcGain3c" constant have some change,but failed same as before,
As we know The DCGain characterized at factory cal and stored along with all other calibration constants in NVRAM,Perhaps it is because the error that has accumulated
over time has caused the current DCGain to exceed the allowable error range.How to adjust the DCgain to the allowable error range? |O Another possibility is that there is
a problem with the NVRAM data |O
--- Code: --- ################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x382ae40 (aAcqExecutor): 27OCT19 01:40:57 U
0x1631bf0 (SPC task): cc_loadV: CC_TRIGdcGain3c was -0.00136806; clipped
0x1631bf0 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to -0.001368, failed
. **
0x1631bf0 (SPC task): cc_loadV: CC_TRIGdcGain4c was -0.00100208; clipped
0x1631bf0 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to -0.001002, failed
. **
total cal time 3.80 minutes
0x1594dd0 (SPC task): cc_loadV: CC_TRIGdcGain3c was -0.00115893; clipped
0x1594dd0 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to -0.001159, failed
. **
0x1594dd0 (SPC task): cc_loadV: CC_TRIGdcGain4c was -0.00092366; clipped
0x1594dd0 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to -0.000924, failed
. **
total cal time 3.87 minutes
--- End code ---
Perpf:
Hi Snoopy!
Obviously you know a lot about the internals of these scopes. Maybe you can give me a hint, where to look for the problem with my defective CSA8000B?
In particular there are two things which could help:
1. Is there a way to read the data from the NVRAMs on PPC and ACQ-Board in order to write them back after replacement?
2. Mine gets stuck during startup of the scope app. PPC shows "P", i get "Kernel running at 10 ticks per slice", then some connection task is going on and somewhere there it gets stuck... Any ideas??
I'd greatly appreciate any help!!!
charlyd:
Hi did you ever find the answer i have a csa7404B here with same error on all 4 channels.
mikehank:
Hi guys,
The M866 the channel preamp. Check for any output voltage on the input. You don’t have a new SPC so there will be some but not more than 5-6mv
Navigation
[0] Message Index
[#] Next page
Go to full version