Author Topic: Tektronix TDS754D FAIL ++ Processor error  (Read 10803 times)

0 Members and 1 Guest are viewing this topic.

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Tektronix TDS754D FAIL ++ Processor error
« on: March 10, 2016, 09:31:41 pm »
Hello I have a TDS754D with a FAIL ++ Processor error the board used is a 679-4349-00 version.  this is the error i got: 
-------------------------------------
Executing Smalltalk
-> ERRORID: 358 nv storage too small more bytes requested than available
Executing Diagnostics from Menu
0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requested than available Start Power-On Diag Sequence
hwAccountant probe routines
Probe for unexpected pending ints

nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
   ExtConst

I swapped both Dallas chips: (1) NVram chip (1250Y-100) and (2) 1486 RTC Clock chip.
After i desoldered the NVram to backup the pins fell off and part of the chip fell off. i tried to export info from the chip but not sure i managed.

Other people told me the unit can be used with out the chip, so the chip doesn t be a part of my error.
i have FV:v7.4e which is a very late firmware version. i only found 6.x and 7.1.1e version no 7.4e version on the web.
i am curious and want advise how to solve my problem.

My unit boots up and looks like it is working 100% ok but what is going wrong with: "nvLibrariansDiag" what causes my FAIL ++ Processor error.

help wanted

 

Offline TAMHAN

  • Frequent Contributor
  • **
  • Posts: 407
  • Country: sk
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #1 on: March 12, 2016, 05:31:08 pm »
Charly, I assume that the error is caused by the scope missing its NVRAM data. Try running an SPC process (signal path comp) first, setting a few options in the scopes user interface before.

If that doesnt solve the problem, getting an image from another TEK754D might be another workable approach.

But this is just a WAG, so ;)
Feel like some additional tamile wisdom? Visit my YouTube channel -> https://www.youtube.com/user/MrTamhan for 10min tid-bits!
 

Offline SAUL BRITTO

  • Frequent Contributor
  • **
  • Posts: 448
  • Country: br
  • Don't Make a Mistake
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #2 on: March 12, 2016, 09:07:19 pm »
Executing Smalltalk
-> ERRORID: 358 nv storage too small more bytes requested than available

What more do you need to understand?
Thank You, for all earth.
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 26755
  • Country: nl
    • NCT Developments
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #3 on: March 12, 2016, 09:15:13 pm »
Executing Smalltalk
-> ERRORID: 358 nv storage too small more bytes requested than available

What more do you need to understand?
This kind of error could mean anything and is most likely due to uninitialised values in the NVRAM. IMHO the only way is to force the scope through some kind of initialisation procedure OR get an NVRAM image from someone.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #4 on: March 14, 2016, 10:08:54 pm »
ok there is something wrong with my NVram but the error is not fixed with a new 1250Y. there are also problems with my DS1486 and i think the options are inside there... uuhh were inside there.  so as a matter a fact after today when i did a extended debug logging after that everything was lost... i did the debugging with (switch 6 and 7 dipped).

after that booting no options anymore...... strangly................. when i dipped 3 ( this short bootup the unit, no long diag) but the scope starts with all options enabled?? this is bit strange for me.

when i run SPC it is passed.

Now i am waiting for my new vp390 programmer to arrive. my TOP853 failed... after verifing my DS1250Y !! 

So after the long debugging today all my CALLs are saying "initializing"  and NO options are showed anymore..

i did some tests:  when i boot my dos computer with GPIB config
                           i can do a clearerr.exe run what clears the errorlog in my scope  -> works perfect!
                          ->  but i can not read nor write the Nvram or flashrom with the tektool  ?? -> doesn t work !
                            i waited for 1 hour and nothing happens ..yes yes i flipped the write protection switch.



ok My logging:

RUNNING FROM DRAM.
DRAM test passed.


   Bootrom Header Checksum passed.
   Bootrom Total Checksum passed.
   BootRom Check Sum passed.
   Bus Error Timeout test passed.

Kernel Diagnostics Complete.

Calling SDM (monitor) Routine.

   Enabling Bus Control register. Value = 0x67
   IMR 1 Register test passed.
   Misc. Register test passed.
   Timer Interrupt test (Auto-Vector) passed.
   NVRam DSACK test passed.
   NVRam Write protected.
   Flashrom DSACK and JumpCode test passed.
   Flashrom Checksums passed.

Bootrom Diagnostics Complete.


DipSwitchValue: 60


Skipping boot loader.
Transferring control to FlashROM.

No PCMCIA option board detected.
FLOPPY: Detected
No ZIP/ZIPplus detected

Adding 7165 symbols for standalone.


CPU: 68EC040.  Processor #0.
Memory Size: 0x1000000.  BSP version 1.0.

Executing Diagnostics
-> ERRORID: 358 nv storage too small more bytes requested than available
ERRORID: 163 diagnostic test failure Start Power-On Sequence

Start Power-On Diag Sequence
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
dspForcedBus ................... pass
cpuDiagD2MiscReg ............... pass
cpuDiagDSPIntMaskReg ........... pass
cpuDiagD1D2Access .............. pass
cpuDiagDsyAccess ............... pass
dsp68kMemTest .................. pass
cpuDiagFIFOMem ................. pass
dspRunVerify ................... pass
dspBusRequestTest .............. pass
dspImplicitBusAccess ........... pass
dspTristarMemTest .............. pass
dsyDiagPM100Reg ................ pass
dsyPM011RegMem ................. pass
dsyLCSRamdacRegMem ............. pass
dsyMonoRamdacRegMem ............ UNTESTED
dsyVGARamdacRegMem ............. pass
dsyDiagPPRegMem ................ pass
dsyDiagRasRegMem ............... pass
dsyDiagAllMem .................. pass
dsyDiagRegSelect ............... pass
dsyDiagRandDotMode ............. pass
dsySeqYTModeV0Intens ........... pass
dsySeqYTModeV1Intens ........... pass
dsySeqYTModeV1Attrib ........... pass
dsySeqYTModeV0Clip ............. pass
dsyDiagSeqXYModeV1 ............. pass
dsyDiagDecayMode ............... pass
dsyRastModeV0Walk .............. pass
dsyRastModeV1Walk .............. pass
dsyRastModeV1Attrib ............ pass
dsyWaitClock ................... pass
dsySplashScreen ................ pass
cpuDiagAllInts ................. pass
nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
   ExtConst

calLibrarianDefaultCk .......... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure calLibrarianDefaultCk
Libs set to factory defaults: 
    PFCal-3C-P6701B, PFCal-4C-P6703B

dspForcedBus ................... pass
acqProcThermistor .............. pass
twoGHz50OhmOvldConf ............ UNTESTED
trigGtlRegisterDiag ............ pass
trigBtlRegisterDiag ............ pass
ch1LogicTypeComp ............... pass
ch2LogicTypeComp ............... pass
ch3LogicTypeComp ............... pass
ch4LogicTypeComp ............... pass
ch1EdgeTrigDiag ................ pass
lineTrigDiag ................... pass
dlyTrigDBETrigAfter ............ pass
dlyTrigDBTRunsAfter ............ pass
slewrateTrigDiag ............... pass
trigAttenSerialReg ............. pass
trigPreampSerialReg ............ pass
trigDTCSerialReg ............... pass
trigExtlSerialReg .............. pass
trigDacSerialReg ............... pass
TICountersDiag ................. pass
gtlBigCountersDiag ............. pass
trigBtlConfidenceDiag .......... pass
trigGtlCompRamDiag ............. pass
digRegisterConf ................ pass
digDataFormatConf .............. pass
digSpeedMemConf ................ pass
digAcqSubSampleConf ............ pass
digAcqPeakDetectConf ........... pass
digAcqHiResConf ................ pass
digAcqMemDataConf .............. pass
digAcqMemAddrConf .............. pass
digInterruptConf ............... pass
digA2DConnectsConf ............. pass
digHFStepConf .................. pass
glitchTrigDiag ................. pass
pulseWidthDiag ................. pass
trigNibDiag .................... pass
digInstaVuXYConf ............... pass
fpDiagConf ..................... pass
optDiagPM110Reg ................ pass
optDiagFloppyCacheMem .......... pass
optDiagFloppyControllerIO ......0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requested than available
 pass
optDiagFloppyDrive ............. UNTESTED
optRS232DuartIO ................ pass
optRS232DuartIntLoop ........... pass
optCentronCntrlReg ............. pass
optTv8bitRegDiag ............... UNTESTED
optTvShiftRegDiag .............. UNTESTED
optTvXparentCodes .............. UNTESTED
optTvDontCareCodes ............. UNTESTED
optTvEdgeAndLevel .............. UNTESTED
optTvSyncLevels ................ UNTESTED
ERRORID: 163 diagnostic test failure **Error count in 1 pu_diag seq passes:
ERRORID: 163 diagnostic test failure .. 1 = Processor
ERRORID: 163 diagnostic test failure .. 1 = Cal Initialization (see error log)
ERRORID: 163 diagnostic test failure thermistor = 118
Executing Smalltalk
ERRORID: 358 nv storage too small more bytes requested than available
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requested than available

Smalltalk/V Sun Version 1.12
Copyright (C) 1990 Object Technology International Inc.
ERRORID: 163 diagnostic test failure extended cal librarian reset

 loop 8,  .25 > TI value > 3.75


« Last Edit: March 14, 2016, 10:26:03 pm by charlyd »
 

Offline TAMHAN

  • Frequent Contributor
  • **
  • Posts: 407
  • Country: sk
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #5 on: March 14, 2016, 11:58:06 pm »
Not 100% sure, but AFAIK, these Teks have a WriteProtect switch for the NVRAM which can be toggled by poking a stick into a hole in the case.

As long as its set to write protect, no access to cal ram.
Feel like some additional tamile wisdom? Visit my YouTube channel -> https://www.youtube.com/user/MrTamhan for 10min tid-bits!
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 26755
  • Country: nl
    • NCT Developments
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #6 on: March 15, 2016, 01:38:18 am »
I see a whole lot of unrelated errors. I'd investigate where the thermistor reading is coming from in the hardware and trace it back to the address/data bus. It could be something is wrong with an address or data bus somewhere which causes various subsystems to fail. It can be hard to find the source of this problem!
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline rx8pilot

  • Super Contributor
  • ***
  • Posts: 3634
  • Country: us
  • If you want more money, be more valuable.
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #7 on: March 15, 2016, 05:42:26 am »
Do you have the service manual already?

I have a TDS754C in daily use, so I wanted to join the discussion to learn something. At the moment, I don't have any suggestions.
Factory400 - the worlds smallest factory. https://www.youtube.com/c/Factory400
 

Offline SAUL BRITTO

  • Frequent Contributor
  • **
  • Posts: 448
  • Country: br
  • Don't Make a Mistake
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #8 on: March 15, 2016, 06:47:20 pm »
ok there is something wrong with my NVram but the error is not fixed with a new 1250Y. there are also problems with my DS1486 and i think the options are inside there... uuhh were inside there.  so as a matter a fact after today when i did a extended debug logging after that everything was lost... i did the debugging with (switch 6 and 7 dipped).

after that booting no options anymore...... strangly................. when i dipped 3 ( this short bootup the unit, no long diag) but the scope starts with all options enabled?? this is bit strange for me.

when i run SPC it is passed.

Now i am waiting for my new vp390 programmer to arrive. my TOP853 failed... after verifing my DS1250Y !! 

So after the long debugging today all my CALLs are saying "initializing"  and NO options are showed anymore..

i did some tests:  when i boot my dos computer with GPIB config
                           i can do a clearerr.exe run what clears the errorlog in my scope  -> works perfect!
                          ->  but i can not read nor write the Nvram or flashrom with the tektool  ?? -> doesn t work !
                            i waited for 1 hour and nothing happens ..yes yes i flipped the write protection switch.



ok My logging:

RUNNING FROM DRAM.
DRAM test passed.


   Bootrom Header Checksum passed.
   Bootrom Total Checksum passed.
   BootRom Check Sum passed.
   Bus Error Timeout test passed.

Kernel Diagnostics Complete.

Calling SDM (monitor) Routine.

   Enabling Bus Control register. Value = 0x67
   IMR 1 Register test passed.
   Misc. Register test passed.
   Timer Interrupt test (Auto-Vector) passed.
   NVRam DSACK test passed.
   NVRam Write protected.
   Flashrom DSACK and JumpCode test passed.
   Flashrom Checksums passed.

Bootrom Diagnostics Complete.


DipSwitchValue: 60


Skipping boot loader.
Transferring control to FlashROM.

No PCMCIA option board detected.
FLOPPY: Detected
No ZIP/ZIPplus detected

Adding 7165 symbols for standalone.


CPU: 68EC040.  Processor #0.
Memory Size: 0x1000000.  BSP version 1.0.

Executing Diagnostics
-> ERRORID: 358 nv storage too small more bytes requested than available
ERRORID: 163 diagnostic test failure Start Power-On Sequence

Start Power-On Diag Sequence
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
dspForcedBus ................... pass
cpuDiagD2MiscReg ............... pass
cpuDiagDSPIntMaskReg ........... pass
cpuDiagD1D2Access .............. pass
cpuDiagDsyAccess ............... pass
dsp68kMemTest .................. pass
cpuDiagFIFOMem ................. pass
dspRunVerify ................... pass
dspBusRequestTest .............. pass
dspImplicitBusAccess ........... pass
dspTristarMemTest .............. pass
dsyDiagPM100Reg ................ pass
dsyPM011RegMem ................. pass
dsyLCSRamdacRegMem ............. pass
dsyMonoRamdacRegMem ............ UNTESTED
dsyVGARamdacRegMem ............. pass
dsyDiagPPRegMem ................ pass
dsyDiagRasRegMem ............... pass
dsyDiagAllMem .................. pass
dsyDiagRegSelect ............... pass
dsyDiagRandDotMode ............. pass
dsySeqYTModeV0Intens ........... pass
dsySeqYTModeV1Intens ........... pass
dsySeqYTModeV1Attrib ........... pass
dsySeqYTModeV0Clip ............. pass
dsyDiagSeqXYModeV1 ............. pass
dsyDiagDecayMode ............... pass
dsyRastModeV0Walk .............. pass
dsyRastModeV1Walk .............. pass
dsyRastModeV1Attrib ............ pass
dsyWaitClock ................... pass
dsySplashScreen ................ pass
cpuDiagAllInts ................. pass
nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
   ExtConst

calLibrarianDefaultCk .......... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure calLibrarianDefaultCk
Libs set to factory defaults: 
    PFCal-3C-P6701B, PFCal-4C-P6703B

dspForcedBus ................... pass
acqProcThermistor .............. pass
twoGHz50OhmOvldConf ............ UNTESTED
trigGtlRegisterDiag ............ pass
trigBtlRegisterDiag ............ pass
ch1LogicTypeComp ............... pass
ch2LogicTypeComp ............... pass
ch3LogicTypeComp ............... pass
ch4LogicTypeComp ............... pass
ch1EdgeTrigDiag ................ pass
lineTrigDiag ................... pass
dlyTrigDBETrigAfter ............ pass
dlyTrigDBTRunsAfter ............ pass
slewrateTrigDiag ............... pass
trigAttenSerialReg ............. pass
trigPreampSerialReg ............ pass
trigDTCSerialReg ............... pass
trigExtlSerialReg .............. pass
trigDacSerialReg ............... pass
TICountersDiag ................. pass
gtlBigCountersDiag ............. pass
trigBtlConfidenceDiag .......... pass
trigGtlCompRamDiag ............. pass
digRegisterConf ................ pass
digDataFormatConf .............. pass
digSpeedMemConf ................ pass
digAcqSubSampleConf ............ pass
digAcqPeakDetectConf ........... pass
digAcqHiResConf ................ pass
digAcqMemDataConf .............. pass
digAcqMemAddrConf .............. pass
digInterruptConf ............... pass
digA2DConnectsConf ............. pass
digHFStepConf .................. pass
glitchTrigDiag ................. pass
pulseWidthDiag ................. pass
trigNibDiag .................... pass
digInstaVuXYConf ............... pass
fpDiagConf ..................... pass
optDiagPM110Reg ................ pass
optDiagFloppyCacheMem .......... pass
optDiagFloppyControllerIO ......0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requested than available
 pass
optDiagFloppyDrive ............. UNTESTED
optRS232DuartIO ................ pass
optRS232DuartIntLoop ........... pass
optCentronCntrlReg ............. pass
optTv8bitRegDiag ............... UNTESTED
optTvShiftRegDiag .............. UNTESTED
optTvXparentCodes .............. UNTESTED
optTvDontCareCodes ............. UNTESTED
optTvEdgeAndLevel .............. UNTESTED
optTvSyncLevels ................ UNTESTED
ERRORID: 163 diagnostic test failure **Error count in 1 pu_diag seq passes:
ERRORID: 163 diagnostic test failure .. 1 = Processor
ERRORID: 163 diagnostic test failure .. 1 = Cal Initialization (see error log)
ERRORID: 163 diagnostic test failure thermistor = 118
Executing Smalltalk
ERRORID: 358 nv storage too small more bytes requested than available
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requested than available

Smalltalk/V Sun Version 1.12
Copyright (C) 1990 Object Technology International Inc.
ERRORID: 163 diagnostic test failure extended cal librarian reset

 loop 8,  .25 > TI value > 3.75

If your NVram are new and the software is a copy of that antique NVram maybe you are dabbing ice.Get a new image without problems is a good ideia.
Thank You, for all earth.
 

Offline keystone

  • Contributor
  • Posts: 35
  • Country: us
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #9 on: March 19, 2016, 09:15:43 pm »
Hi Charlyd.  I agree with Saul Britto.  Get an good nvram image from someone with that scope.  RX8pilot has one close to yours.  Maybe you can pm him about that.  I only have a TDS-644A scope being my latest model.  Have you searched the Tektronics website and forum for help?
 

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #10 on: March 20, 2016, 08:14:34 pm »
Hi the image is not the problem i have one but the programmer is since i can get connection with the tektool. ( i am in research for that otherwise i have to wait for arround 2 weeks). 

but there is more....
after dipping arround with the switches 3 and  6,7  Tektronix ACQUISITION Board was also failed. 

Then i found out there was something with the enabled options. nearly all options were enabled... this is maybe what NCTNICO saw in the logging.
-> enabled options which are not present in the unit i assume...

because i have some connections on vendor site i got a tool to set and reset options in seconds by commandline tools (sharing is not possible sorry) and found that too many options were enabled. i took my orginal setting -> 13 1F 2F 2C <- from the picture from before the failure and pushed those options in the new DS1486 (timekeeper /options set ) and when i boot up and look into the status now the right options are set ok.

-> DS1486   -> new ->  OK -> check.!
-> DS1250Y -> new ->  waiting for tektool or programmer.
-> ACQUISITION Board  -> PASS  -> check
-> SPC -> PASS
-> voltage ref. -> still  initialize
-> frequentie ref.  -> still  initialize


« Last Edit: March 20, 2016, 08:39:42 pm by charlyd »
 

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #11 on: March 20, 2016, 08:42:02 pm »
new logging:


Skipping boot loader.
Transferring control to FlashROM.

No PCMCIA option board detected.
FLOPPY: Detected
No ZIP/ZIPplus detected

Adding 7165 symbols for standalone.


CPU: 68EC040.  Processor #0.
Memory Size: 0x1000000.  BSP version 1.0.

Executing Diagnostics
-> ERRORID: 358 nv storage too small more bytes requested than available
Start Power-On Diag Sequence
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
dspForcedBus ................... pass
cpuDiagD2MiscReg ............... pass
cpuDiagDSPIntMaskReg ........... pass
cpuDiagDsyAccess ............... pass
dsp68kMemTest .................. pass
cpuDiagFIFOMem ................. pass
dspRunVerify ................... pass
dspBusRequestTest .............. pass
dspImplicitBusAccess ........... pass
dspTristarMemTest .............. pass
dsyDiagPM100Reg ................ pass
dsyPM011RegMem ................. pass
dsyLCSRamdacRegMem ............. pass
dsyMonoRamdacRegMem ............ UNTESTED
dsyVGARamdacRegMem ............. pass
dsyDiagPPRegMem ................ pass
dsyDiagRasRegMem ............... pass
dsyDiagRegSelect ............... pass
dsyDiagAllMem .................. pass
dsySeqYTModeV0Intens ........... pass
dsyDiagSeqXYModeV1 ............. pass
dsyRastModeV0Walk .............. pass
dsyRastModeV1Attrib ............ pass
dsyWaitClock ................... pass
dsySplashScreen ................ pass
cpuDiagAllInts ................. pass
nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
        ExtConst, PFCal

calLibrarianDefaultCk .......... pass
dspForcedBus ................... pass
acqProcThermistor .............. pass
twoGHz50OhmOvldConf ............ UNTESTED
ch1EdgeTrigDiag ................ pass
lineTrigDiag ................... pass
digHFStepConf .................. pass
fpDiagConf ..................... pass
optDiagPM110Reg ................ pass
optDiagFloppyCacheMem .......... pass
optDiagFloppyControllerIO ......0x5fffe80 (tRootTask): libError 358, lib EXTCAL,
 id=358, msg=more bytes requested than available
 pass
optDiagFloppyDrive ............. pass
optRS232DuartIO ................ pass
optRS232DuartIntLoop ........... UNTESTED
optCentronCntrlReg ............. UNTESTED
optTv8bitRegDiag ............... UNTESTED
optTvShiftRegDiag .............. UNTESTED
optTvXparentCodes .............. UNTESTED
optTvDontCareCodes ............. UNTESTED
optTvEdgeAndLevel .............. UNTESTED
optTvSyncLevels ................ UNTESTED
Executing Smalltalk
ERRORID: 358 nv storage too small more bytes requested than available
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requeste
d than available

Smalltalk/V Sun Version 1.12
Copyright (C) 1990 Object Technology International Inc.
ERRORID: 163 diagnostic test failure extended cal librarian reset
ERRORID: 360 nv storage ram copy corruption  Probe Filter Cal NVRAM FAIL. Need t
o Init & Cal.

 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 26755
  • Country: nl
    • NCT Developments
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #12 on: March 20, 2016, 09:27:51 pm »
I think the last error tells you what to do: the calibration data must be initialised. Maybe running an SPC and self test will do the trick.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #13 on: April 02, 2016, 02:57:34 pm »
hello ok back on the track again.  i installed the new NVram (1st was broken) after programming of course...

and these are still my errors: i little bit back were i started before i took the Original (old)NVram out.


nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
   ExtConst

ERRORID: 358 nv storage too small more bytes requested than available

optDiagFloppyControllerIO ......0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requested than available 

i think it is still 1 error all together but o course i can be wrong.

anyone the golden tip??


 

Offline dinix

  • Contributor
  • Posts: 17
  • Country: pt
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #14 on: June 28, 2016, 11:37:20 am »
here you can find the 7.4e firmware images:

http://www.ko4bb.com/getsimple/index.php?id=manuals&dir=Tektronix/Tektronix_-_TDS784_TDS794_Digital_Phosphore_Oscilloscope

I would like to know the change logs...
 

Offline dinix

  • Contributor
  • Posts: 17
  • Country: pt
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #15 on: June 29, 2016, 03:35:39 pm »
hello ok back on the track again.  i installed the new NVram (1st was broken) after programming of course...

and these are still my errors: i little bit back were i started before i took the Original (old)NVram out.


nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
   ExtConst

ERRORID: 358 nv storage too small more bytes requested than available

optDiagFloppyControllerIO ......0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requested than available 

i think it is still 1 error all together but o course i can be wrong.

anyone the golden tip??


here you can find the 7.4e firmware images:

http://www.ko4bb.com/getsimple/index.php?id=manuals&dir=Tektronix/Tektronix_-_TDS784_TDS794_Digital_Phosphore_Oscilloscope

I would like to know if anyone was the change logs...
 

Offline zxase258

  • Contributor
  • Posts: 24
  • Country: cn
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #16 on: September 21, 2017, 04:02:09 am »
calLibrarianDefaultCk .......... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure calLibrarianDefaultCk
Libs set to factory defaults: 
    PFCal-3C-P6701B, PFCal-4C-P6703B

Check the  Option 3C/4C(Optical probe cal) ?if enabled , turn if off via GPIB or Console port.

1. unprotected NVRAM  , turn on scope.
2. GPIB send
"PASSWORD PITBULL"
“WORDCONSTANT:ATPUT 327693,0”
“WORDCONSTANT:ATPUT 327694,0”
3. protected NVRAM, power cycle the scope
 

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #17 on: September 22, 2017, 06:36:34 pm »
Ahhh... after a long while of silence.....new options....i will try this in a short while and report back...
 

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #18 on: September 25, 2017, 09:08:27 am »
i tried it last night but it was NOT the solution...
here is my logging again.

Smalltalk/V Sun Version 1.12
Copyright (C) 1990 Object Technology International Inc.
ERRORID: 163 diagnostic test failure extended cal librarian reset

 loop 8,  .25 > TI value > 3.75

RUNNING FROM DRAM.
DRAM test passed.


        Bootrom Header Checksum passed.
        Bootrom Total Checksum passed.
        BootRom Check Sum passed.
        Bus Error Timeout test passed.

Kernel Diagnostics Complete.

Calling SDM (monitor) Routine.

        Enabling Bus Control register. Value = 0x67
        IMR 1 Register test passed.
        Misc. Register test passed.
        Timer Interrupt test (Auto-Vector) passed.
        NVRam DSACK test passed.
        NVRam Write protected.
        Flashrom DSACK and JumpCode test passed.
        Flashrom Checksums passed.

Bootrom Diagnostics Complete.


DipSwitchValue: 0


Skipping boot loader.
Transferring control to FlashROM.

No PCMCIA option board detected.
FLOPPY: Detected

Adding 7165 symbols for standalone.


CPU: 68EC040.  Processor #0.
Memory Size: 0x1000000.  BSP version 1.0.

Executing Diagnostics
-> ERRORID: 358 nv storage too small more bytes requested than available
Start Power-On Diag Sequence
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
dspForcedBus ................... pass
cpuDiagD2MiscReg ............... pass
cpuDiagDSPIntMaskReg ........... pass
cpuDiagDsyAccess ............... pass
dsp68kMemTest .................. pass
cpuDiagFIFOMem ................. pass
dspRunVerify ................... pass
dspBusRequestTest .............. pass
dspImplicitBusAccess ........... pass
dspTristarMemTest .............. pass
dsyDiagPM100Reg ................ pass
dsyPM011RegMem ................. pass
dsyLCSRamdacRegMem ............. pass
dsyMonoRamdacRegMem ............ UNTESTED
dsyVGARamdacRegMem ............. pass
dsyDiagPPRegMem ................ pass
dsyDiagRasRegMem ............... pass
dsyDiagRegSelect ............... pass
dsyDiagAllMem .................. pass
dsySeqYTModeV0Intens ........... pass
dsyDiagSeqXYModeV1 ............. pass
dsyRastModeV0Walk .............. pass
dsyRastModeV1Attrib ............ pass
dsyWaitClock ................... pass
dsySplashScreen ................ pass
cpuDiagAllInts ................. pass
nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
        ExtConst

calLibrarianDefaultCk .......... pass
dspForcedBus ................... pass
acqProcThermistor .............. pass
twoGHz50OhmOvldConf ............ UNTESTED
ch1EdgeTrigDiag ................ pass
lineTrigDiag ................... pass
digHFStepConf .................. pass
fpDiagConf ..................... pass
optDiagPM110Reg ................ pass
optDiagFloppyCacheMem .......... pass
optDiagFloppyControllerIO ......0x5fffe80 (tRootTask): libError 358, lib EXTCAL,
 id=358, msg=more bytes requested than available
 pass
optDiagFloppyDrive ............. pass
optRS232DuartIO ................ UNTESTED
optRS232DuartIntLoop ........... UNTESTED
optCentronCntrlReg ............. UNTESTED
optTv8bitRegDiag ............... UNTESTED
optTvShiftRegDiag .............. UNTESTED
optTvXparentCodes .............. UNTESTED
optTvDontCareCodes ............. UNTESTED
optTvEdgeAndLevel .............. UNTESTED
optTvSyncLevels ................ UNTESTED
Executing Smalltalk
ERRORID: 358 nv storage too small more bytes requested than available
hwAccountant probe routines
  Probe for unexpected pending ints
  Dsp Instr mem size
  Dsp D2 mem size
  Dsp D1 mem size
  Dsy Vect0 mem size
  Dsy Vect1 mem size
  Dsy Wfm0 mem size
  Dsy Wfm1 mem size
  Dsy Text0 mem size
  Dsy Text1 mem size
  Acq number of digitizers
  Acq mem size
  Cpu timer interval uSec
  Cpu Dram size
  NvRam mem size
  Limit to 1GS/sec presence
  Opt Math Package presence
  Opt Telecom Masks presence
  Opt 3C presence
  Opt 4C presence
  Opt RS232/ Cent presence
  Opt 1M presence
  Opt 2M presence
  Acq Intlv Cal Id presence
  Opt TvTrig presence
  Opt TvTrig index
  Dsy color presence
  Opt floppy drive presence
  Opt hard drive presence
  Acq number of user channels
0x5fffe80 (tRootTask): libError 358, lib EXTCAL, id=358, msg=more bytes requeste
d than available
can't open input 'fd0:/startup.bat'
  errno = 0x13 (S_errno_ENODEV)

any ideas
 

Offline denimdragon

  • Regular Contributor
  • *
  • Posts: 223
  • Country: us
  • "Hole charge chaser and wanna-be o-scope fixer"
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #19 on: June 11, 2018, 05:32:30 am »
I hate to be a necromancer, but I have this issue. Did you ever come up with a solution @charlyd?
"Hi there. I'm short in the hair department, do you mind if I pull a few strands from your head? Thanks!"
 

Offline induzer

  • Contributor
  • Posts: 14
  • Country: de
  • employed in the renewable energy branch
    • Laborlogbuch
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #20 on: January 08, 2019, 07:57:00 am »
Has someone tried to replace the IC's U1052 and / or U1055  on the ACQ-Board ?

I can state that the D-series Scopes have stored the Cal-Constants in these I2C-EEPROMs '24C02' on the ACQ-Board.

My TDS540D (the monochrome variant of the 754D) also had a constant fail "FAIL ++ Processor  error" on bootup and while self-test.

Checked the above stated EEPROMs on mine, to see U1055 was brick dead. As a precaution i replaced both chips.

I had preprogrammed the new EEPROMS with images, I belive tinhead had uploaded somewhere here.

My Scope has FW v.7.1.1e, tinhead files where taken from TDS754D with FW v.7.2e

cheers
induzer
« Last Edit: January 08, 2019, 07:59:00 am by induzer »
 

Offline capt bullshot

  • Super Contributor
  • ***
  • Posts: 3033
  • Country: de
    • Mostly useless stuff, but nice to have: wunderkis.de
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #21 on: January 08, 2019, 09:58:33 am »
Has someone tried to replace the IC's U1052 and / or U1055  on the ACQ-Board ?

Yes, I did this some time ago with my TDS580C - resolved some strange error message, can't remember, afair something similar to the OP. Used a known good image from another TDS580, but a complete calibration of the scope should be done anyway, since these cal constants are specific to the particular ACQ board.
Another interesting thing: someone else had swapped the CPU board, leading to the scope not knowing itself - showing TDS??? at startup. Updating the FW to a newer version (can't remember) solved this.
Safety devices hinder evolution
 

Offline keystone

  • Contributor
  • Posts: 35
  • Country: us
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #22 on: March 04, 2019, 12:43:06 am »
I have a Processor fail on bootup of my TDS620A and am trying to communicate with it via the console port.  Can anyone tell me if I need a null modem cable or straight cable?  I have wired the console port adapter cable and it is a straight cable and I havn't got any comm with the scope.  I don't want to hook up a null modem adapter if it will damage anything.  Thank you for your input.
 

Offline charlydTopic starter

  • Frequent Contributor
  • **
  • Posts: 524
  • Country: nl
Re: Tektronix TDS754D FAIL ++ Processor error
« Reply #23 on: February 25, 2020, 04:22:01 pm »
You need to create a special console adapter and plug it in on the cpu board take out the RS232 module
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf