Tektronix TDS7254B Signal Path Compensation fail issue and pass all Diagnostic - Page 1
Forum section: electronics / repair

author: snoopy_lei
author_rank: Newbie
timestamp: October 20, 2019, 07:22:13 am
content: 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.hwKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!-> 0x3814820 (aAcqDpoExecutor): 20OCT19 15:38:45 U0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped0x1641830 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed. **0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped0x1641830 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed. **total cal time 3.80 minutesHowever 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?Code:romPost: I am alive .uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuromPost: 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.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - IBM 750CXeVersion: 5.3.1BSP version: 2.0.1.10Creation date: Sep 30 2003, 07:53:07Press any key to stop auto-boot...0auto-booting...boot device : smprocessor number : 0file name : c:/vxboot/vxWorks.stinet on backplane (b): 192.168.0.1:ffffff00host inet (h) : 192.168.0.2gateway inet (g) : 192.168.0.1flags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:/vxboot/topscript.hwInitializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching networPC1 dio device driver installedk interface lo0... done.Attaching DIO client... done.Loading c:/vxboot/vxWorks.st...1773468Starting at 0x200000...Host Name: bootHostUser: targetInitializing backplane net with anchor at 0x16e0000... done.Backplane anchor at 0x16e0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching 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-1997CPU: Tektronix HPP - IBM 750CXe. Processor #0.Memory Size: 0x2000000. BSP version 2.0.1.10.WDB: Ready.doneKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:/vxboot/topscript.hw ...dbFsIoctl: invalid code 3################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)new symbol "pDbDev" added to symbol table.pDbDev = 0x1692d40: value = 23670112 = 0x1692d60 = pDbDev + 0x20pDBfs = dosFsMkfs("/db", pDbDev)new symbol "pDBfs" added to symbol table.pDBfs = 0x1691720: value = 23669856 = 0x1692c60ld < TekScope.ovalue = 23657440 = 0x168fbe0ld < TekScopeSM.ovalue = 23660544 = 0x1690800copy ("TekScope.DBF", "/db/TekScope.DBF")value = 0 = 0x0loggerInitSerial No: B020790value = 21822832 = 0x14cfd70overrideFPdefaults()value = 0 = 0x0measurePPCtimebasevalue = 0 = 0x0registerMemPartitionSizes ( 0x00000000 )value = 0 = 0x0semInitForQueueCheckLogMsgvalue = 23661184 = 0x1690a80initSysWaiter()value = 0 = 0x0raxInitvalue = 0 = 0x0paiInitdonevalue = 16129500 = 0xf61ddc = PaiBaseRegisterTable + 0x804configureACLSUCCESSvalue = 0 = 0x0verifyAcqBoardIDvalue = 0 = 0x0tcsLoadTableToNVRAM "pc:c:/vxBoot/setup.tcs"value = 0 = 0x0updateAcqProcFirmware("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 = 0x1cd "pc:"value = 0 = 0x0raxInitializeDevicesdone0x16987e0 (tShell): (Re)starting Acq Processorvalue = 23692720 = 0x16985b0excHookAdd(stopStressForException)value = 15840048 = 0xf1b330 = stopStressForExceptiondsyInitvalue = 0 = 0x0dsyWPApplyNextRegsvalue = 16110116 = 0xf5d224 = DsyRegisterTable + 0xbd0# remove '#' from next line to set powerup scope state to factory default:# NvramClearDb = 1nvram_initFileSysvalue = 21793056 = 0x14c8920TmgrInit("/db")value = 0 = 0x0PhxProxyInitvalue = 20333344 = 0x1364320rtlInitvalue =0 = 0x0sysExtMemAddToPool memSysPartId,0x02000000,0x1c000000value = 0 = 0x0hwAccount_initsysEnetAddrGet: 4d:54:5c:c8:c0:64Scope Model: TDS7254Bvalue = 0 = 0x0GpibInitvalue = 502610496 = 0x1df53a40wfmMemInit(1)value = 62205664 = 0x3b52ee0vertInstallvalue = 62198148 = 0x3b51184calConStatus = cc_init(2)0x16987e0 (tShell): Reading 358 bytes of service cal #1 data from NV[3:0] into 0x3b510000x16987e0 (tShell): nvMem_read succeeded0x16987e0 (tShell): Optical hardware is not present.calConStatus = 0x127d1dc: value = 0 = 0x0vertPostCalRestoreInstallvalue = 0 = 0x0MathMeasCreateTheMathandMeasurementLibrariesvalue = 62025376 = 0x3b26ea0initAcqMapper0x16987e0 (tShell): initAcqMapper: Entervalue = 0 = 0x0trigMapInitvalue = 0 = 0x0dsyMapInitvalue = 0 = 0x0mathMapperInitvalue = 0 = 0x0utilMapInitvalue = 62019520 = 0x3b257c0TmgrHookupvalue = 0 = 0x0PhxProxyHookupvalue = 0 = 0x0hookupAcqMappervalue = 19321872 = 0x126d410 = AcqMapperRtlDataListMathMeasMapHookupvalue = 23692552 = 0x1698508dsyMapHookupvalue = 23692656 = 0x1698570utilMapHookupvalue = 23692688 = 0x1698590rtlHookupvalue = 0 = 0x0horizMapHookupvalue = 23692648 = 0x1698568fastFrameMapHookupvalue = 23692672 = 0x1698580trigMapHookupvalue = 23692680 = 0x1698588vertMapHookupvalue = 23692672 = 0x1698580spcMapHookupvalue = 23692672 = 0x1698580autosetMapHookupvalue = 23692712 = 0x16985a8timeSyncMapHookupvalue = 23692704 = 0x16985a0auxTrigMapHookupvalue = 23692688 = 0x1698590dpoMapHookupvalue = 23692680 = 0x1698588TmgrStartupvalue = 61194384 = 0x3a5c090PhxProxyStartupvalue = 61143840 = 0x3a4fb20taskDelay(2)value = 0 = 0x0gpibHwInitCvalue = 0 = 0x0gpibTaskSpawnvalue = 61017376 = 0x3a30d20gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"value = 60967680 = 0x3a24b00enablePowerupDiags = 0enablePowerupDiags = 0x123dbdc: value = 0 = 0x0runPowerupDiagsdonedipSwitch = 0x0, enablePowerupDiags = 0, puMode=0CalDiagPowerUpDiagsEnabled = 0!! SKIPPING POWERUP DIAGNOSTICS !!<< POWERUP DIAGS FINISHED >>execution time 0 sec>>Test "351" - Acquisition-->HFStep-->PhaseCal startedTest execution time 6.3768 secvalue = 0 = 0x0rtlStartupvalue = 0 = 0x0tsCompvalue = 0 = 0x0paiPrintVersionNumberPai version: 4.52value = 18 = 0x12################### topScript ends ###############################Done executing startup script c:/vxboot/topscript.hwKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!-> 0x3814820 (aAcqDpoExecutor): 20OCT19 15:38:45 U0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped0x1641830 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed. **0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped0x1641830 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed. **total cal time 3.80 minutesDIAGNOSTIC EXECUTION beginTest "111" - Processor-->Memory-->DRAMWalk1 startedTest execution time 6.875e-06 secTest "112" - Processor-->Memory-->DRAMCell startedTest execution time 0.047812 secTest "113" - Processor-->Memory-->DRAMMarch startedTest execution time 0.014548 secTest "121" - Processor-->PCI Bus-->Scan Test startedTest execution time 1.7788e-05 secTest "211" - RegAccess-->DACs-->Daculator startedTest execution time 0.00036913 secTest "221" - RegAccess-->Direct R/W-->DEMUX startedTest execution time 0.0023205 secTest "222" - RegAccess-->Direct R/W-->Dsy startedTest execution time 0.00032442 secTest "223" - RegAccess-->Direct R/W-->SBTL startedTest execution time 0.00013178 secTest "224" - RegAccess-->Direct R/W-->SGTL startedTest execution time 0.00029986 secTest "231" - RegAccess-->IIC-->Pogo_U1 startedTest execution time 0.00040611 secTest "241" - RegAccess-->PLL-->Serial startedTest execution time 9.2548e-05 secTest "251" - RegAccess-->Serial-->AtoD startedTest execution time 0.00019014 secTest "252" - RegAccess-->Serial-->U1093 startedTest execution time 2.7115e-05 secTest "253" - RegAccess-->Serial-->U1251 startedTest execution time 0.00019577 secTest "254" - RegAccess-->Serial-->U1500 startedTest execution time 0.00027058 secTest "311" - Acquisition-->Memory-->MemData startedTest execution time 5.0736 secTest "312" - Acquisition-->Memory-->MemAddr startedTest execution time 4.9452 secTest "313" - Acquisition-->Memory-->DataFormat startedTest execution time 2.4118 secTest "321" - Acquisition-->Acq Modes-->SubSample startedTest execution time 5.3287 secTest "322" - Acquisition-->Acq Modes-->PeakDetect startedTest execution time 39.147 secTest "323" - Acquisition-->Acq Modes-->HiRes startedTest execution time 5.3411 secTest "331" - Acquisition-->Vertical-->50OhmOvld startedTest execution time 0.083668 secTest "332" - Acquisition-->Vertical-->ADC Connects startedTest execution time 7.0864 secTest "341" - Acquisition-->Interrupt-->Bit Tests startedTest execution time 4.9321 secTest "351" - Acquisition-->HFStep-->PhaseCal startedTest execution time 5.8304 secTest "361" - Acquisition-->PLL-->Clock Freq startedTest execution time 0.44611 secTest "371" - Acquisition-->MemSpeed-->DemuxA startedTest execution time 3.9665 secTest "372" - Acquisition-->MemSpeed-->DemuxB startedTest execution time 3.9569 secTest "373" - Acquisition-->MemSpeed-->DemuxC startedTest execution time 3.9557 secTest "374" - Acquisition-->MemSpeed-->DemuxD startedTest execution time 3.9562 secTest "375" - Acquisition-->MemSpeed-->DemuxE startedTest execution time 3.9563 secTest "376" - Acquisition-->MemSpeed-->DemuxF startedTest execution time 3.9579 secTest "377" - Acquisition-->MemSpeed-->DemuxG startedTest execution time 3.9557 secTest "378" - Acquisition-->MemSpeed-->DemuxH startedTest execution time 3.9561 secTest "411" - Trigger-->Inputs-->Line startedTest execution time 0.072346 secTest "412" - Trigger-->Inputs-->Ch1 startedTest execution time 0.36608 secTest "413" - Trigger-->Inputs-->Ch2 startedTest execution time 0.35029 secTest "414" - Trigger-->Inputs-->Ch3 startedTest execution time 0.35027 secTest "415" - Trigger-->Inputs-->Ch4 startedTest execution time 0.35036 secTest "421" - Trigger-->Internals-->TimerA1 startedTest execution time 0.10003 secTest "422" - Trigger-->Internals-->TimerA2 startedTest execution time 0.099752 secTest "423" - Trigger-->Internals-->Btrig startedTest execution time 0.10234 secTest "424" - Trigger-->Internals-->BtrigEvents startedTest execution time 0.11884 secTest "425" - Trigger-->Internals-->TimeInterp startedTest execution time 9.3269e-06 secTest "426" - Trigger-->Internals-->Holdoff startedTest execution time 0.033352 secTest "511" - Misc-->Cal Integrity-->Factory Cal startedTest execution time 6.0577e-06 secTest "512" - Misc-->Cal Integrity-->SPC (run SPC) startedTest execution time 1.8269e-06 secTest "521" - Misc-->GPIB-->Interface startedTest execution time 0.0005699 secDIAGNOSTIC EXECUTION finished in 115.5 sec

author: snoopy_lei
author_rank: Newbie
timestamp: October 26, 2019, 11:45:19 am
content: 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 accumulatedover time has caused the current DCGain to exceed the allowable error range.How to adjust the DCgain to the allowable error range?Another possibility is that there isa problem with the NVRAM dataCode:################### topScript ends ###############################Done executing startup script c:/vxboot/topscript.hwKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!-> 0x382ae40 (aAcqExecutor): 27OCT19 01:40:57 U0x1631bf0 (SPC task): cc_loadV: CC_TRIGdcGain3c was -0.00136806; clipped0x1631bf0 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to -0.001368, failed. **0x1631bf0 (SPC task): cc_loadV: CC_TRIGdcGain4c was -0.00100208; clipped0x1631bf0 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to -0.001002, failed. **total cal time 3.80 minutes0x1594dd0 (SPC task): cc_loadV: CC_TRIGdcGain3c was -0.00115893; clipped0x1594dd0 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to -0.001159, failed. **0x1594dd0 (SPC task): cc_loadV: CC_TRIGdcGain4c was -0.00092366; clipped0x1594dd0 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to -0.000924, failed. **total cal time 3.87 minutes

author: Perpf
author_rank: Newbie
timestamp: November 11, 2019, 03:05:56 pm
content: 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!!!

author: charlyd
author_rank: Frequent Contributor
timestamp: October 23, 2022, 12:35:20 pm
content: Hi did you ever find the answer i have a csa7404B here with same error on all 4 channels.

author: mikehank
author_rank: Regular Contributor
timestamp: October 24, 2022, 07:40:01 am
content: 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

author: charlyd
author_rank: Frequent Contributor
timestamp: October 24, 2022, 02:41:30 pm
content: @mikehank : M866 pre amp ....uuh what component are you pointing to i will add my log also to compare ;-)boot + diag + spc ( diag gives All Pass)Code:--------------------------------------------------------------boot ----------------------------------------------------------romPost: I am alive .uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuromPost: 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.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - IBM 750CXeVersion: 5.3.1BSP version: 2.0.1.10Creation date: Sep 30 2003, 07:53:07Press any key to stop auto-boot...0auto-booting...boot device : smprocessor number : 0file name : c:/vxboot/vxWorks.stinet on backplane (b): 192.168.0.1:ffffff00host inet (h) : 192.168.0.2gateway inet (g) : 192.168.0.1flags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:/vxboot/topscript.hwInitializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching networPC1 dio device driver installedk interface lo0... done.Attaching DIO client... done.Loading c:/vxboot/vxWorks.st...1773468Starting at 0x200000...Host Name: bootHostUser: targetInitializing backplane net with anchor at 0x16e0000... done.Backplane anchor at 0x16e0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching 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-1997CPU: Tektronix HPP - IBM 750CXe. Processor #0.Memory Size: 0x2000000. BSP version 2.0.1.10.WDB: Ready.doneKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:/vxboot/topscript.hw ...dbFsIoctl: invalid code 3################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)new symbol "pDbDev" added to symbol table.pDbDev = 0x1692d40: value = 23670112 = 0x1692d60 = pDbDev + 0x20pDBfs = dosFsMkfs("/db", pDbDev)new symbol "pDBfs" added to symbol table.pDBfs = 0x1691720: value = 23669856 = 0x1692c60ld < TekScope.ovalue = 23657440 = 0x168fbe0ld < TekScopeSM.ovalue = 23660544 = 0x1690800copy ("TekScope.DBF", "/db/TekScope.DBF")value = 0 = 0x0loggerInitSerial No: B020198value = 21822832 = 0x14cfd70overrideFPdefaults()value = 0 = 0x0measurePPCtimebasevalue = 0 = 0x0registerMemPartitionSizes ( 0x00000000 )value = 0 = 0x0semInitForQueueCheckLogMsgvalue = 23661184 = 0x1690a80initSysWaiter()value = 0 = 0x0raxInitvalue = 0 = 0x0paiInitdonevalue = 16129500 = 0xf61ddc = PaiBaseRegisterTable + 0x804configureACLSUCCESSvalue = 0 = 0x0verifyAcqBoardIDvalue = 0 = 0x0tcsLoadTableToNVRAM "pc:c:/vxBoot/setup.tcs"value = 0 = 0x0updateAcqProcFirmware("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 = 0x1cd "pc:"value = 0 = 0x0raxInitializeDevicesdone0x16987e0 (tShell): (Re)starting Acq Processorvalue = 23692720 = 0x16985b0excHookAdd(stopStressForException)value = 15840048 = 0xf1b330 = stopStressForExceptiondsyInitvalue = 0 = 0x0dsyWPApplyNextRegsvalue = 16110116 = 0xf5d224 = DsyRegisterTable + 0xbd0# remove '#' from next line to set powerup scope state to factory default:# NvramClearDb = 1nvram_initFileSysvalue = 21792992 = 0x14c88e0TmgrInit("/db")value = 0 = 0x0PhxProxyInitvalue = 20333280 = 0x13642e0rtlInitvalue =0 = 0x0sysExtMemAddToPool memSysPartId,0x02000000,0x1c000000value = 0 = 0x0hwAccount_initsysEnetAddrGet: 1b:15:41:8b:e4:21Scope Model: CSA7404Bvalue = 255 = 0xff = DSP_cc_load_pri_byte_at_pri_load_ar1 + 0xdGpibInitvalue = 502600832 = 0x1df51480wfmMemInit(1)value = 62197472 = 0x3b50ee0vertInstallvalue = 62189956 = 0x3b4f184calConStatus = cc_init(2)0x16987e0 (tShell): Reading 358 bytes of service cal #1 data from NV[3:0] into 0x3b4f0000x16987e0 (tShell): nvMem_read succeeded0x16987e0 (tShell): Complete PFCal NVRAM initialization.0x16987e0 (tShell): Ready to Calibrate Probes.calConStatus = 0x127d1dc: value = 33263 = 0x81efvertPostCalRestoreInstallvalue = 0 = 0x0MathMeasCreateTheMathandMeasurementLibrariesvalue = 61919168 = 0x3b0cfc0initAcqMapper0x16987e0 (tShell): initAcqMapper: Entervalue = 0 = 0x0trigMapInitvalue = 0 = 0x0dsyMapInitvalue = 0 = 0x0mathMapperInitvalue = 0 = 0x0utilMapInitvalue = 61913312 = 0x3b0b8e0TmgrHookupvalue = 0 = 0x0PhxProxyHookupvalue = 0 = 0x0hookupAcqMappervalue = 19321872 = 0x126d410 = AcqMapperRtlDataListMathMeasMapHookupvalue = 23692552 = 0x1698508dsyMapHookupvalue = 23692656 = 0x1698570utilMapHookupvalue = 23692688 = 0x1698590rtlHookupvalue = 0 = 0x0horizMapHookupvalue = 23692648 = 0x1698568fastFrameMapHookupvalue = 23692672 = 0x1698580trigMapHookupvalue = 23692680 = 0x1698588vertMapHookupvalue = 23692672 = 0x1698580spcMapHookupvalue = 23692672 = 0x1698580autosetMapHookupvalue = 23692712 = 0x16985a8timeSyncMapHookupvalue = 23692704 = 0x16985a0auxTrigMapHookupvalue = 23692688 = 0x1698590dpoMapHookupvalue = 23692680 = 0x1698588TmgrStartupvalue = 61080848 = 0x3a40510PhxProxyStartupvalue = 61030304 = 0x3a33fa0taskDelay(2)value = 0 = 0x0gpibHwInitCvalue = 0 = 0x0gpibTaskSpawnvalue = 60904352 = 0x3a153a0gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"value = 60854656 = 0x3a09180enablePowerupDiags = 0enablePowerupDiags = 0x123dbdc: value = 0 = 0x0runPowerupDiagsdonedipSwitch = 0x0, enablePowerupDiags = 0, puMode=0CalDiagPowerUpDiagsEnabled = 0!! SKIPPING POWERUP DIAGNOSTICS !!<< POWERUP DIAGS FINISHED >>execution time 0 sec>>Test "351" - Acquisition-->HFStep-->PhaseCal startedTest execution time 20.7 secvalue = 0 = 0x0rtlStartupvalue = 0 = 0x0tsCompvalue = 0 = 0x0paiPrintVersionNumberPai version: 4.52value = 18 = 0x12################### topScript ends ###############################Done executing startup script c:/vxboot/topscript.hwKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!-> 0x3812b40 (aAcqExecutor): 24OCT22 12:28:33 U--------------------------------------------------------------Diagnostics ----------------------------------------------------------DIAGNOSTIC EXECUTION beginTest "111" - Processor-->Memory-->DRAMWalk1 startedTest execution time 6.8269e-06 secTest "112" - Processor-->Memory-->DRAMCell startedTest execution time 0.050551 secTest "113" - Processor-->Memory-->DRAMMarch startedTest execution time 0.015118 secTest "121" - Processor-->PCI Bus-->Scan Test startedTest execution time 1.7933e-05 secTest "211" - RegAccess-->DACs-->Daculator startedTest execution time 0.00037678 secTest "221" - RegAccess-->Direct R/W-->DEMUX startedTest execution time 0.0023163 secTest "222" - RegAccess-->Direct R/W-->Dsy startedTest execution time 0.00032207 secTest "223" - RegAccess-->Direct R/W-->SBTL startedTest execution time 0.00013216 secTest "224" - RegAccess-->Direct R/W-->SGTL startedTest execution time 0.00030173 secTest "231" - RegAccess-->IIC-->Pogo_U1 startedTest execution time 0.0003662 secTest "241" - RegAccess-->PLL-->Serial startedTest execution time 9.2933e-05 secTest "251" - RegAccess-->Serial-->AtoD startedTest execution time 0.00019029 secTest "252" - RegAccess-->Serial-->U1093 startedTest execution time 2.6923e-05 secTest "253" - RegAccess-->Serial-->U1251 startedTest execution time 0.00019611 secTest "254" - RegAccess-->Serial-->U1500 startedTest execution time 0.00027024 secTest "311" - Acquisition-->Memory-->MemData startedTest execution time 5.0706 secTest "312" - Acquisition-->Memory-->MemAddr startedTest execution time 4.9468 secTest "313" - Acquisition-->Memory-->DataFormat startedTest execution time 2.4118 secTest "321" - Acquisition-->Acq Modes-->SubSample startedTest execution time 5.328 secTest "322" - Acquisition-->Acq Modes-->PeakDetect startedTest execution time 39.147 secTest "323" - Acquisition-->Acq Modes-->HiRes startedTest execution time 5.3412 secTest "331" - Acquisition-->Vertical-->50OhmOvld startedTest execution time 0.083661 secTest "332" - Acquisition-->Vertical-->ADC Connects startedTest execution time 7.0865 secTest "341" - Acquisition-->Interrupt-->Bit Tests startedTest execution time 4.932 secTest "351" - Acquisition-->HFStep-->PhaseCal startedTest execution time 18.567 secTest "361" - Acquisition-->PLL-->Clock Freq startedTest execution time 0.44619 secTest "371" - Acquisition-->MemSpeed-->DemuxA startedTest execution time 3.9646 secTest "372" - Acquisition-->MemSpeed-->DemuxB startedTest execution time 3.9564 secTest "373" - Acquisition-->MemSpeed-->DemuxC startedTest execution time 3.9565 secTest "374" - Acquisition-->MemSpeed-->DemuxD startedTest execution time 3.9565 secTest "375" - Acquisition-->MemSpeed-->DemuxE startedTest execution time 3.9562 secTest "376" - Acquisition-->MemSpeed-->DemuxF startedTest execution time 3.9563 secTest "377" - Acquisition-->MemSpeed-->DemuxG startedTest execution time 3.9564 secTest "378" - Acquisition-->MemSpeed-->DemuxH startedTest execution time 3.9561 secTest "411" - Trigger-->Inputs-->Line startedTest execution time 0.074602 secTest "412" - Trigger-->Inputs-->Ch1 startedTest execution time 0.36551 secTest "413" - Trigger-->Inputs-->Ch2 startedTest execution time 0.35025 secTest "414" - Trigger-->Inputs-->Ch3 startedTest execution time 0.3504 secTest "415" - Trigger-->Inputs-->Ch4 startedTest execution time 0.35018 secTest "421" - Trigger-->Internals-->TimerA1 startedTest execution time 0.10015 secTest "422" - Trigger-->Internals-->TimerA2 startedTest execution time 0.10125 secTest "423" - Trigger-->Internals-->Btrig startedTest execution time 0.11813 secTest "424" - Trigger-->Internals-->BtrigEvents startedTest execution time 0.11882 secTest "425" - Trigger-->Internals-->TimeInterp startedTest execution time 9.3269e-06 secTest "426" - Trigger-->Internals-->Holdoff startedTest execution time 0.033314 secTest "511" - Misc-->Cal Integrity-->Factory Cal startedTest execution time 6.5385e-06 secTest "512" - Misc-->Cal Integrity-->SPC (run SPC) startedTest execution time 3.2212e-06 secTest "521" - Misc-->GPIB-->Interface startedTest execution time 0.00056856 secDIAGNOSTIC EXECUTION finished in 128.26 sec--------------------------------------------------------------SPC ----------------------------------------------------------0x381ae30 (SPC task): cc_loadV: CC_TRIGdcGain1b was 0; clipped0x381ae30 (SPC task): ** M866CompCalibrator 1b failed -- ...wrote cal constant CC_TRIGdcGain1b to 0.000000, failed. **0x381ae30 (SPC task): cc_loadV: CC_TRIGdcGain2b was 0; clipped0x381ae30 (SPC task): ** M866CompCalibrator 2b failed -- ...wrote cal constant CC_TRIGdcGain2b to 0.000000, failed. **0x381ae30 (SPC task): cc_loadV: CC_TRIGdcGain3b was 0; clipped0x381ae30 (SPC task): ** M866CompCalibrator 3b failed -- ...wrote cal constant CC_TRIGdcGain3b to 0.000000, failed. **0x381ae30 (SPC task): cc_loadV: CC_TRIGdcGain4b was 0; clipped0x381ae30 (SPC task): ** M866CompCalibrator 4b failed -- ...wrote cal constant CC_TRIGdcGain4b to 0.000000, failed. **total cal time 4.40 minutes

author: mikehank
author_rank: Regular Contributor
timestamp: October 24, 2022, 05:16:48 pm
content: So your failure for spc is common. Diags are will not pick up the M866 calibration failures. What is happening is spc is applying a calibration signal to the preamp for various measurements and the signal is out of range(too small or too large) and fails. Attached are a couple of pic's that may help. Install a TNC-BNC to the input of a channel and measure for mV. You should not see very much under 5-6 mv or so. If you have more this is the source of the out of range M866 failure.

author: mikehank
author_rank: Regular Contributor
timestamp: October 24, 2022, 05:17:49 pm
content: Here is another file

author: charlyd
author_rank: Frequent Contributor
timestamp: October 25, 2022, 07:17:07 pm
content: Hi Mikehank, yes i have seen this picture but you think the problem is pre-amp related? ok but for all channels then?does any body have a picture of those pre-amp without the heatsink. so the code on top of the chips.ah i just saw you posted 2 messages (with xlsx)...thanks for your help and support...

author: matthuszagh
author_rank: Frequent Contributor
timestamp: August 23, 2023, 07:14:50 pm
content: charlyd, did you ever figure this out? I'm seeing something similar.

author: charlyd
author_rank: Frequent Contributor
timestamp: November 12, 2023, 05:17:22 pm
content: hi Matthus , no i parked the unit and went to the next one.So, you have a similiar issue ?btw somebody explain when 351 - Acquisition-->HFStep-->PhaseCal is displayed in Diagnostic.

author: charlyd
author_rank: Frequent Contributor
timestamp: February 11, 2024, 09:39:14 am
content: hi is there any clearance on the M866 issueM866CompCal failed i now have a TDS7404B with ACQ Diags all pass.this 7404B unit also has a ch3 and ch4 error exact like the 7254B in first post. it looks like it should be a component or circuit for two channels. So that there are two of the same circuits/components for each two channels and one of the two circuits is failing.so i guess there must be a relation. It is a bit difficult to dive deeper because you need to measure on the back side of the ACQ board. someone already experienced with let say extension cables or something?specially to jaywalling because of your experienceany m866 news?i am willing to pay $200 to whom who can point me to the M866 Comp Cal failed solution. like in first post

author: charlyd
author_rank: Frequent Contributor
timestamp: December 07, 2024, 01:17:03 pm
content: Hi its a while since....but i was stuck searching....Today my eye caught this picture... not saying that this is found on the CSA7404B series.but i am still curious if somebody has a failed "B series ACQ board" and is willing to pull of some heatsinks...to get a better board layout... searching for the mysterious M866 in the B series 7000 scopesexact board picture see post #7 abovebecause i have seen only ch 3 and ch4 failing and like in my case all channels failing. This would suggest there are two (or more but i doubt) of these chips equipt.

author: iAleks
author_rank: Regular Contributor
timestamp: January 29, 2025, 12:13:02 am
content: Hi, In scope.exe (5.35.22) i found this: U1200(M866). Its triger IC on picture above its named "Comm trigger". From every preamp coming out two differential signal one to TrackAndHold=>ADC, second to trigger IC.I didn't repair the device with this error. I would try apply some small sinus signal and try change trigger level and watch is there somthing wrong see?failed -- ...wrote cal constant /hmm, what does that mean... why he failed wrote...Im not recommend remove heatsink from this IC!