Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)

[bg8aak]

hi everyone, really glad to learn from this thread. recently i got a tds7104,boot stop at the scope start screen,I use vxboot to reset and now it boots ok.
but self test ,it reports 521 factory cal integrity ,factory cal data error. I read the boot log,it seems that it can't open some cal file in C:\vxboot\calcon. And i checked in C:\vxboot\calcon, there do missed cal file named 1 to 8 and 15,could this be the cause of error 521? Can anybody share the files ?  Or any other suggestion.

Error 521 is the EEPROM on the acquisition board has been corrupted. It's reference designation is U1052.
Here is a known good U1052 binary from a TDS7104. Obviously it won't have the correct constants for your scope, but it will get rid of the error.
Otherwise you'll need to have a proper calibration with adjustments done.

Thanks your U1502 binary files ,I fix my TDS7104 521 errors
 

Thanks charlyd give me a lot guide and advices

[charlyd]

hi @BG8AAK thanks your welcome..

ok here i am again with a CSA7404B

This unit is fully passing all Diagnostics ok but when SPC is ran it gives a fail  with  M866CompCalibrator  error on all 4 trigger

Code: [Select]

DIAGNOSTIC EXECUTION finished in 140.94 sec
0x38fc090 (CalWatch): Temperature transition into SPC-supporting range.
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain1b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 1b failed -- ...wrote cal constant C
C_TRIGdcGain1b to 0.000000, failed
. **
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain2b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 2b failed -- ...wrote cal constant C
C_TRIGdcGain2b to 0.000000, failed
. **
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain3b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 3b failed -- ...wrote cal constant C
C_TRIGdcGain3b to 0.000000, failed
. **
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain4b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 4b failed -- ...wrote cal constant C
C_TRIGdcGain4b to 0.000000, failed
. **


can this be a problem with the MAX9601 dual pecl-output comparator?  from what i see and compare my output is fully "0" ; clipped on all 4 channels....where "snoopy_lei" has small values on only 2 channels.

anybody already work on the M866CompCal  failed errors?
While searching for this error i ordered a New DS1245Y to start off but it will take some time to arrive. meanwhile i am wandering if this problem is known already or quit new.

from the posts i have seen i guess it happens occasionally on the newer B models.
 

[charlyd]

i found in a SPC debug output from an different TDS7404 ( Non B version)
taken without the trigger chips installed the error is a sort of equal and this confirms a trigger problem in the B version.

[charlyd]

may i drop a question here to all software guru and experts
is it possible to write a script or create a small program like TEKTOOL
to export the TDS7000 eeprom content, like it is done with the TDS700 series.
i think there is a need for this.

[xiang_zhen]

Hi,
 
    Everyone, My TDS7104 is not working now, I have replaced the DS1245-120 with DS1245-120+, after reboot the unit, the following log we got, please help to check what happen. thanks.

    UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

romPost: MPC106  Walking-one passed.

romPost: MPC106 configuration passed.

romPost: First PCI access  passed.

romPost: PC87560 Walking-one passed.

romPost: PC87560 configuration passed.

romPost: DEC21554 configuration passed.


romPost: PERFORMING ROM CHECKSUM TEST...

romPost: ROM checksum passed.


romPost: PERFORMING DRAM CELL TEST...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.

romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.

romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM WALKING-ONE  TEST...

romPost: DRAM Walking-one test passed.

romPost: PERFORMING NV-MEMORY WALKING-ONE  TEST...

romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.


romPost: POWER-UP DIAGNOSTIC COMPLETE.

Hel










                            VxWorks System Boot


Copyright 1984-1996  Wind River Systems, Inc.





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




Press any key to stop auto-boot...
 1

[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]: c

'.' = clear field;  '-' = go to previous field;  ^D = quit

boot device          : sm
processor number     : 0
host name            :
file name            : c:/vxboot/vxWorks.st
inet on ethernet (e) :
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
user (u)             :
ftp password (pw) (blank = use rsh):
flags (f)            : 0x1008
target name (tn)     : tds7000
startup script (s)   : c:/vxboot/topscript.hw
other (o)            :

[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]: @

boot device          : sm
processor number     : 0
file name            : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
flags (f)            : 0x1008
target name (tn)     : tds7000
startup script (s)   : c:/vxboot/topscript.hw

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

Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008 symbols for standalone.
 

 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]           
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]           
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]] 
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]]
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Tektronix HPP - PowerPC 740.  Processor #0.
                              Memory Size: 0x2000000.  BSP version 1.0.8.1 .
                             WDB: Ready.

tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
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 = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0





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

    raxInitializeDevices
0x16987e0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0
   
    excHookAdd(stopStressForException)
value = 17557980 = 0x10be9dc = stopStressForException
   
   
    dsyInit
value = 21806728 = 0x14cbe88
    dsyWPApplyNextRegs
value = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0

   
   





   
    # remove '#' from next line to set powerup scope state to factory default:
    # NvramClearDb = 1
   
    #xiangzhe add   
    # tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
     
    nvram_initFileSys
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4d7c3
   
    TmgrInit("/db")
0x16987e0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 14916



    ppc board system is halt and the win2000 display the welcome screen of Tektronix and then no response.

[Kimer]

So I came across this thread randomly and I wanted to pay it forward and help however I can.  I've recently acquired a TDS7245B scope on ebay that seems to be a bit unique since it came preloaded with windows XP from the factory with the 4M ST and USB options keys enabled.  I intend to mirror and replace the hard drive with an SSD.  If anybody can tell me about creating ghost images (I assume this just means an image of the hard drive), then this particular configuration might be a valuable addition to the collection.

[coromonadalix]

To be sure,  you kill the tektronix software with the xp task manager,  and you copy everything in the VXWork folder on a usb key and other driver folders  ...

You have some commands to backup the mainboard bios, calcons, vxbios   and  other things ..  we have the 7254B model at my job

The nvram (ds1245) with integrated cell died,  but we had backups   ... and i have downloaded everything from TEK website, juuust  to be sure.

I will order an ssd drive, it is very slow to boot,  I upgraded it to XP sp3,  killed all useless stuff in it (Msn, Outlook  etc..)  and we do not let it connect to the web,
since Xp is outdated

And yes  we have the latest motherboard for it, i did find the original  Intel (non TEK bios logo for it),   and it did receive all the ram it can use.

Cost an arm for the calibration (Around 1k$$)

To clone a drive you have some free software or paid,     disk genius, macrium reflect, drive image  etc ...   

just a tip

Always use another computer to clone a drive, an working / booted computer can not backup itself,    and / or  if your bios  permit it , boot from an usb key with some already made Window PE  disks like Strelec  ...  they have tools you need to clone on another drive

If you do it, take some note about the software and the version used  ...   i used a second computer with an external ide dock for the backup in my case

They are big machines, but i love them  loll  classic settings  no fuss  loll  I love the huge screen   

I have the new sds 1xxx rigol models, i have some hard time figuring out all the functions  loll  and more easy on theses old era stuff   loll

[Kimer]

To be sure,  you kill the tektronix software with the xp task manager,  and you copy everything in the VXWork folder on a usb key and other driver folders  ...

You have some commands to backup the mainboard bios, calcons, vxbios   and  other things ..  we have the 7254B model at my job

The nvram (ds1245) with integrated cell died,  but we had backups   ... and i have downloaded everything from TEK website, juuust  to be sure.

I will order an ssd drive, it is very slow to boot,  I upgraded it to XP sp3,  killed all useless stuff in it (Msn, Outlook  etc..)  and we do not let it connect to the web,
since Xp is outdated

Thanks for the reply, I appreciate the tip on killing tekscope before copying the vxworks folder.  I didn't realize that when I copied it the first time. Was there anything special you needed to do in order to upgrade to SP3?  I currently have SP2.  I've read this whole thread start to finish but I must have missed or wasn't paying attention to commands on backing up the mainboard bios, calcons, vxbios etc?  Is there a list somewhere you could point me to?  Really appreciate it!

Justin

[coromonadalix]

for sp3  nothing special

With the task manager called from CRTL ALT DELETE,  kill the tektronix process,     start a new task,   write "explorer"  and do what you have to do, use an usb key  with the sp3 pack on it

And reboot the scope normally


Gonna search for the scripts, they where mostly found here   ....    and i use the original intel bios, it can access the bios more easily ...  but you have to be very careful for the video section   if you mess things, the lcd display will not work correctly  BUT i dont know for sure the motherboard you have ....


Clean the unused stuff in xp   with the add remove application in control panel ...

As stated  PLS do a cloned drive file before messing with things,   just in case  .......  a good dust clean up too, take anti static precautions

[Kimer]

Another great upgrade to juice up one of these tired, old oscilloscopes is to install an inexpensive SSD. I went with the Kingspec KSD-PA25.6 PATA 44-pin MLC SSD. They can run as little as $50 delivered at the low-end, and range in capacities from 16GB to 128GB. While the SSD does not make it run that much faster during operation like the processor upgrade does, it does allow it to cold boot much more quickly and get away from the unreliable old notebook hard disk drives. In the scheme of things, it seems like it's a worthwhile investment to me.

Ok this is kind of a dumb question admittedly but I've spent all day trying to clone a drive which should be easy.  I'm going from the original 40GB travelstar IC24N040ATMR04-0 to a 64GB Kingspec KDS-PA25.6  PATA 44-pin MLC SSD.  I've tried cloning with acronis 2017, clonezilla, HDDGuru all with no success.  I've tried booting with master mode enabled on the PATA drive, slave mode, and cable mode as well.  It seems that I'm not able to boot to this drive even though the bios has recognized the drive each time.  Is there any reason you can think of that this wouldn't work on a windows XP machine?  I either get a disk read error or a flashing cursor that never goes away depending on which cloning software I'm using.

[coromonadalix]

Are you doing it on another computer ?? or try to use the main (scope)   Because  you can't do a clone of the runing (host) computer, wnindows  lock files while running

Or start a fresh installation with the ssd in the scope,  windows will fomat and prepare the drive ?? and you rebuild everything .....

If the bios see it, normally it should go fine ?? unless weird compatibility problems ?   or the cloning fail to prepare the mbr / boot sector correctly ??

[Kimer]

Are you doing it on another computer ?? or try to use the main (scope)   Because  you can't do a clone of the runing (host) computer, wnindows  lock files while running

Or start a fresh installation with the ssd in the scope,  windows will fomat and prepare the drive ?? and you rebuild everything .....

If the bios see it, normally it should go fine ?? unless weird compatibility problems ?   or the cloning fail to prepare the mbr / boot sector correctly ??

I'm using bootable media like clonezilla or acronis which loads it's own operating system so the drives in question are not being run at the time of cloning.  At this point I suspect it's a bad drive because I've tried sector by sector cloning even and it still won't boot.  The bios does in fact see it but then I get a disc read error so I'm going to try a new drive and see what happens.

Thanks for the advice!

[calibrationfixture]

Hi,

As far as I know all TDS7000B Series with B020000> Serial Numbers had Factory Off Intel D865GLC MB's with a Windows XP SP2 Installation.

I ordered for my TDS7000B a "NEW" 40 GB Hitachi Travelstar HDD (same as the old, including RPM). For Cloning I used an old Vista Desktop with free SATA Slots and DeLock 22-Pin SATA to 44-Pins IDE Adapters. In addition I downloaded a "Legacy" Macrium Reflect Version from www.filehorse.com with a Windows 10 Desktop and installed the 32-Bit program on the Vista 32-Bit Desktop. No Registration or needed Keys. A plus when you install Programs on Offline PC's.

Before I started the Cloning Process I had to Initialize and Format the "New" Hitachi HDD (Disk Management). All this worked without any obstacles,

Succes,

Calibrationfixture

[Kimer]

Thanks, really appreciate the advice.  I ordered a hitachi Travelstar and we'll see where that gets me.

Hi,

As far as I know all TDS7000B Series with B020000> Serial Numbers had Factory Off Intel D865GLC MB's with a Windows XP SP2 Installation.

I ordered for my TDS7000B a "NEW" 40 GB Hitachi Travelstar HDD (same as the old, including RPM). For Cloning I used an old Vista Desktop with free SATA Slots and DeLock 22-Pin SATA to 44-Pins IDE Adapters. In addition I downloaded a "Legacy" Macrium Reflect Version from www.filehorse.com with a Windows 10 Desktop and installed the 32-Bit program on the Vista 32-Bit Desktop. No Registration or needed Keys. A plus when you install Programs on Offline PC's.

Before I started the Cloning Process I had to Initialize and Format the "New" Hitachi HDD (Disk Management). All this worked without any obstacles,

Succes,

Calibrationfixture

[Kimer]

So it turned out to be a bad drive.  I appreciate the help.

On a side note, now that I've got the new cloned drive booting, does anyone know if the key generator works with the B versions as well?  Wntering a model number with a B doesn't seem to work.  I tried dropping the B and entering my serial number but the keys it's generating don't work when using the 04FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF option mask.

[calibrationfixture]

Hi,

The Program supports the TDS5000(B), TDS7000(B), CSA7000(B), TDS6000(B/C), DPO7000 and DSA/DPO70000 (No Letters) Series. For the more recent MSO70000 Series I don't know.

I used for my TDS7404B Option Masks: 10 44 FF FF FF FF FF FF FF (14 x F). With this I enabled as far as I know all possible Options for the TDS7000B Series (i.c.w. Scope Application V 5.1.3), including Max Record Length (64 Mp). With help of:

https://xdevs.com/doc/Tektronix/TDS5000B/

I installed TDSVNM (former App. 61) and TDSPTD (former App. 69) Option Modules.

Succes,

Calibrationfixture

[Kimer]

Thanks Calibrationfixture, I really appreciate your help.  I was referring to the TDS7254B so that's great to hear I should be able to get all of the options working.  From the link you posted, it's not clear to me how you are using the TDS5000B folder for the TDS7404B?  It appears this folder contains disc images for the TDS5000B.  Did you mean this folder instead?

https://xdevs.com/doc/Tektronix/TDS7000/Additional%20Scope%20Software%20for%20Options/


I see the TDSVNM application there but not the TDSPTD.

[calibrationfixture]

Hi,

In the TDS5000B Folder you see also:

https://xdevs.com/doc/Tektronix/TDS5000B/tektronix_options_sw_disk_1.dd

The Option Software for the TDS5000B and TDS7000B Series is the same.

In addition for a TDS7254B with SN B020126 your input must be for example:

.\gen.py TDS7254B B020126 1044FFFFFFFFFFFFFF (14 x F)

For a DPO7254 the string of F's after the First 4 Digits must be 20 at least. For its Maximum Record Length (Option 10RL) the First 2 Digits must be 04.

Succes,

Calibrationfixture

[Kimer]

Got it, thanks a lot calibration fixture!  Just got it fully unlocked using the option mask you gave me.  Working on getting the options image installed now.  I can't thank you enough!

[emonemon0217@gmail.com]

Thank you for the nice board.
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/350/

I replaced NVRAM with this FRAM and it passed the POWER-UP Diagnostic and VXworks now boots! However, as the console below shows, it says the block is too large and stops with Assertion failed. So Tekscope is still stuck at the splash screen. If anyone has a solution, please help!




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.7.0
Creation date: Jun 12 2002, 11:45:18




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


boot device          : sm
processor number     : 0
file name            : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
flags (f)            : 0x1008
target name (tn)     : tds7000
startup script (s)   : c:/vxboot/topscript.hw

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

Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008 symbols for standalone.


 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]]
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Tektronix HPP - PowerPC 740.  Processor #0.
                              Memory Size: 0x2000000.  BSP version 1.0.7.0.
                             WDB: Ready.

tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
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, 128, 128, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1682d20: value = 23670112 = 0x1692d60
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1681900: value = 23604288 = 0x1682c40

    ld < TekScope.o
value = 21167072 = 0x142fbe0
    ld < TekScopeSM.o
value = 21166624 = 0x142fa20

    copy ("TekScope.DBF", "/db/TekScope.DBF")
copy: error writing file.
value = -1 = 0xffffffff = pDbDev + 0xfe97d2df

    overrideFPdefaults()
value = 0 = 0x0

    measurePPCtimebase
value = 0 = 0x0


    registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0

    semInitForQueueCheckLogMsg
value = 23673216 = 0x1693980

    initSysWaiter()
value = 0 = 0x0




    raxInit
value = 0 = 0x0
    paiInit
done
value = 16944404 = 0x1028d14 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID

Inappropriate Acq board ID found:  0x7
value = 0 = 0x0






     tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
value = 0 = 0x0
     updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): 1368 bytes successfully verified.
AVR processor FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
value = 0 = 0x0
     cd "pc:"
value = 0 = 0x0

    raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 22411048 = 0x155f728

    excHookAdd(stopStressForException)
value = 16732228 = 0xff5044 = stopStressForException


    dsyInit
value = 22405032 = 0x155dfa8
    dsyWPApplyNextRegs
value = 16934280 = 0x1026588 = DsyRegisterTable + 0xab0





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

    nvram_initFileSys
0x16987e0 (tShell): memPartAlloc: block too big - 38884352 in partition 0x337eac.
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba5e3e3

    TmgrInit("/db")
0x16987e0 (tShell): Assertion failed: EXIT_SUCCESS == retValue, file ../src/tmgrClass.cpp, line 1487

[coromonadalix]

have you tried this:

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

to 

NvramClearDb = 1 

it should force a state reset ?

the "fun" sarcasm      is to  get onto a windows like os   or boot into something else to edit the file .........

[emonemon0217@gmail.com]

I got an error that TekScope.o could not be opened. but, something seems to be going on.

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


boot device          : sm
processor number     : 0
file name            : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h)        : 192.168.0.2
gateway inet (g)     : 192.168.0.1
flags (f)            : 0x1008
target name (tn)     : tds7000
startup script (s)   : c:/vxboot/topscript.hw

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

Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008 symbols for standalone.


 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]]
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Tektronix HPP - PowerPC 740.  Processor #0.
                              Memory Size: 0x2000000.  BSP version 1.0.8.1 .
                             WDB: Ready.

tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
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
'an't open input 'TekScope.o
  errno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)

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

[aandrew]

I just got a TDS7154B and while it’s in good working order I’d like to try to keep it that way as long as possible. I’m imaging the HDD and replacing it with an SSD, replacing the CMOS battery and taking a look at the RTC on the PPC board too.

One thing in particular I’m looking at is adding heat sinks to the trigger chips on the acquisition board, as it seems this is a common failure mode and they’re unobtanium. The board I have is 679-5674-11 (or maybe 665-1719-11, that’s another label right beside the first). I did a visual inspection of the visible side of the board and don’t see the infamous chips. I also looked at the other side of the board online (don’t want to remove it if I can help it) and I don’t see any devices which have the correct package.

Doesn’t this board/scope use the same trigger ICs as the other models in this series? Are there any other things I should be taking care of while I have it open to help keep this in top shape as long as possible? The caps on both the motherboard and PPC board look pretty good, which surprised me.

[geshka]

Hello team.  I am a bit struggling with my TDS 7404.  I've got it with broken HDD and when i restored it, I hit the problem with Dallas chip on PPC has lost its settings.  I hooked up serial to the side of the scope , as per TIN notes and recreated configuration for PPC.  I even saw scope SW started once, but when I rebooted scope it stuck in the same place - on splash screen of the SW.  Indicator on the board shows letter "P" constantly . Here is output from terminal connected to the PPC console port .  Is there any ideas why it is stuck again ? 

Code: [Select]

UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

romPost: MPC106  Walking-one passed.

romPost: MPC106 configuration passed.

romPost: First PCI access  passed.

romPost: PC87560 Walking-one passed.

romPost: PC87560 configuration passed.

romPost: DEC21554 configuration passed.


romPost: PERFORMING ROM CHECKSUM TEST...

romPost: ROM checksum passed.


romPost: PERFORMING DRAM CELL TEST...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.

romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.

romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...

romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...

romPost: PERFORMING DRAM WALKING-ONE  TEST...

romPost: DRAM Walking-one test passed.

romPost: PERFORMING NV-MEMORY WALKING-ONE  TEST...

romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.


romPost: POWER-UP DIAGNOSTIC COMPLETE.

Hel










                            VxWorks System Boot


Copyright 1984-1996  Wind River Systems, Inc.





CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.4.0
Creation date: Nov  2 2000, 11:03:34




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


boot device          : sm
processor number     : 0
host name            : host
file name            : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h)        : 192.168.0.1
gateway inet (g)     : 192.168.0.2
user (u)             : anonymous
ftp password (pw)    : anonymous
flags (f)            : 0x1000
target name (tn)     : target
startup script (s)   : c:\vxBoot\topScript.hw
other (o)            : nvfs=0x1000

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

Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.

Adding 6008 symbols for standalone.


 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]]
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Tektronix HPP - PowerPC 740.  Processor #0.
                              Memory Size: 0x2000000.  BSP version 1.0.8.0 .
                             WDB: Ready.

usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0

data access
Exception current instruction address: 0x00223f30
Machine Status Register: 0x0000b030
Data Access Register: 0xd40f1a00
Condition Register: 0x20000042
Data storage interrupt Register: 0x40000000
Task: 0x1fffe08 "tRootTask"



When I am pressing CtrlC to the screen I see following

Code: [Select]


2f1588 vxTaskEntry    +60 : 223d6c ()
223d6c usrRoot        +458: usrNvFsInit ()
206abc usrNvFsInit    +18c: dosFsDevInit ()
2a1838 dosFsDevInit   +260: 2a6170 ()
2a6230 dosFsTimeSet   +2ac: 2a6a84 ()
2a6de8 dosFsTimeSet   +e64: 2a210c ()
2a23c8 dosFsDevInitOptionsSet+aec: 2a210c ()
2a21e8 dosFsDevInitOptionsSet+90c: 2a0b50 ()
2a0b78 symSRemove     +c8c: 2a5cdc ()
293c34 ramDevCreate   +1f0: bcopy ()


[coromonadalix]

Thank you not to put a veryyyy long boot info   like the previous threads

First  does the windows boot completly  or get stuck too,  if it boot  can you show us the device manager / peripherals if they are all ok  and not having some exclamation errors ...

The computer side must be perfect before the scope side



https://xdevs.com/fix/csa7404/

you see on xdevs  the P code :   loading files from host  ............................    there could still be some installation problems, something is missing for a complete TEK software boot

Have you checked on hp  all the softwares drivers  etc ...     i still have backups from our 7254   drivers etc ... i can or could give some help  BUT IT'S  a B version