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

[Xyphro]

Lets hope I get there again, that it tries to boot from floppy disc. Right now I think the SF810 board is broken.
Anybidy has a NLX board for sale?

[charlyd]

Hi why not pull out the X86 board and feed it with external PSU.  of course check the coin battery for 3v. but i assume you already did.
connect a VGA monitor to the onboard svga.

and see what happens.

[Xyphro]

That is feasible, but not easy as there is no AT or ATX supply connector. I have the riser pinout. Honestly, before soldering 30 cables for a test, I wait now for a new board to arrive from Israel. If this is not going to help, I will likely sell it.

As the signals and voltages towards the board are ok and it is not trying to boot, I expect the mainboard to be broken.

[charlyd]

hi i would just pull the board out of the scope and connect by soldering at the end (printside)of the riser connector [NOT THE COPPER CONTACTS FOR SURE] the 4 voltages, +5/-5/+12/-12 wires from an old atx psu. and if the board is really dead there is not much to loose. checked caps already

[Xyphro]

Hi!

I need to run killcmos headless. I can out it in autostart.bat to do so. But: do I need to press any button? If so, which ones?

Best regards,

Kai
Edit:
I managed to run. Killcmos does not need any keypresses, it also resets the oc afzer execution. Bios was correctly shoeing that cmos data is corrupt.
Still my pc board boots only every now and then. I esit for replacement board.
The ppc works fine, just if the PC does not boot and show a vga signal, it is also not capable to load from harddisk its image. Story thus continues... :-(

[Johnny10]

There is an eBay seller that has provided a kit to upgrade the TDS 7000 series.

You could contact him about the many options.
I found this a couple of years back as I repaired my two TDS7104s.

I wonder just how much of a difference faster CPU makes to oscilloscope?
Imagine boot-up would be faster but scope? I don't know.

https://www.ebay.com/itm/184796108047?hash=item2b06b4d50f:g:LQEAAOSwyytdYzXq

[exit_failure]

I Have a TDS7104 Which the application just hangs in the splash screen. If I understood the problem correctly I need to pull of the plastic cap from the Dallas "chip" and replace the battery underneath. My Problem is, that I can't seem to get the plastic cap off and I don't want to damage anything. What the trick to getting it of?
After replacing the battery, I understand tthat I will have to reset the NVRAM. What's the easiest way to do that?

The second problem the scope has  that during boot the built in screen shows that the screen has been recognized andI should configure it under Windows. After boot, it is set up as the secondary screen with the VGA output being the primary even with no screen attached. There also doesn't seem to be a way to configure the built in screen as primary. Is this problem related to something else or do I need to repair another thing for that to work again?

[Johnny10]

Read through the thread.
The screen going over to VGA is from dead BIOS battery.

[exit_failure]

I already replaced the BIOS battery. This unfortunately didn't change anything. I read through the first fifty or 100 posts and all I found is that I nee to pull of the plastic cap but not how without damaging anything.
I just thought that maybe somebody with more experience could give me quick summary or point me towards the right posts since this thread has more than 600 posts.

[Johnny10]

You have to reset BIOS chip by using KILLCMOS program.

[Johnny10]

On Saturday, the CMOS battery died on my second 7104.
It blanked the TDS7104 screen and kept me from getting into BIOS.
Battery was dated 1995.

Replaced battery.

Access the VGA connector in back with separate monitor.
You need to install KILLCMOS application on floppy MS-DOS start-up disk.
I used a 2SHD 1.44MB High Density floppy on a XP OS machine.
When formatting disk there is a check for create MS-DOS disk.

Online I downloaded a KILLCMOS program. (https://www.majorgeeks.com/files/details/killcmos.html)
Extracted file and installed on floppy.

Boot from the floppy type dir in the command line.
Find and and run KILLCMOS .

 CTRL Alt Delete
 F2 Setup
 Your BIOS is now accessible.
 Change config of BIOS to default settings.
 Change Display to PCI
 Save and restart oscilloscope.

[Xyphro]

My tds7104 had a different dallas nvram: DS1245Y-120.

If you wonder where to find the battery contacts... They are burried much deeper into the molding as for other dallas NVRAMs.

See attached photo for location help in case you want to put a new battery in :-)

[Xyphro]

Sorry, the + and - labels are swapped!

[exit_failure]

I do have the one from the first post but I still do not seem to  be able to figure out how to remove the plastic cover without uncomfortable amounts of force.

[exit_failure]

The answer to my question about how to get the cap off can actually be found in this data sheet - who would have thought  : https://datasheets.maximintegrated.com/en/ds/DS9034PC.pdf : Stick a screwdriver into the slot of the cover and lever it to the opposite side (away from the large brown connector).

 

I'm going to do a write-up on the whole battery replacement process as soon as I get the new battery delivered.

[exit_failure]

I seems to be 1 step away from having a working scope again: After setting the settings to what another TDS7104 owner reported I get these error messages on the serial console. Does anbody know, how to fix this or at least what the exact problem is here?

The both errors I see are:
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed

and

can't open input 'TDS7000.o'
errno = 0x1c0001 (S_symLib_SYMBOL_NOT_FOUND)

Code: [Select]

Press any key to stop auto-boot... 1 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...1773344
Starting at 0x200000...

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

Adding 6003 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.3.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

   
    ld < TDS7000.o
can't open input 'TDS7000.o'
  errno = 0x1c0001 (S_symLib_SYMBOL_NOT_FOUND)

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

[exit_failure]

I've gotten rid of the first error (tcsTableUnpack: checksum failed on buffer; tcsTableLoadFromNVRAM: tcsTableUnpack failed) by uncommenting NvramClearDb = 1 for one boot und commenting it again afterwards.
The other error

can't open input 'TDS7000.o'
errno = 0x1c0001 (S_symLib_SYMBOL_NOT_FOUND)
is still there. What's strange is that the file TDS7000.o i right there in the C:\vxBoot folder.

[Xyphro]

Update: After adding a new battery to the Dallas IC I have put a small 3d printed casing arround it - looks clearner as my previous hot glue massacre.

I also created 3d models for the Tektronix knobs. You can find them attached. I am yet not sure if I like my colour concept, but they nicely fit.
I printed them at 0.14mm layer hight, 1mm wall thickness with 97% scaling, no support. Depending on the accuracies of your printer you might need a different model scaling factor. Try out first e.g. 3 different scaling factors and chose the one that gives you the best snap-fit.

[tautech]

.................
I also created 3d models for the Tektronix knobs. You can find them attached. I am yet not sure if I like my colour concept, but they nicely fit.
I printed them at 0.14mm layer hight, 1mm wall thickness with 97% scaling, no support. Depending on the accuracies of your printer you might need a different model scaling factor. Try out first e.g. 3 different scaling factors and chose the one that gives you the best snap-fit.

Nice, you need post about those here too:
https://www.eevblog.com/forum/testgear/replacement-knobs-feet-and-fittings-for-test-equipment/

[AQUARIUS]

Hello, friends!
I need your help.
I purchased an inexpensive TDS7054 oscilloscope on Ebay.
The oscilloscope loads Windows, but does not load Tektronix software.
At first I thought that the problem was a faulty Dallas battery, but when I opened it, it turned out that the battery is working (> 3v).
Then I paid attention to the fact that I do not have a VxBoot folder on my hard drive and there are no drivers for 2 devices in the device manager.
Most likely, the previous owner of this oscilloscope replaced the hard drive and copied the data from the old one, but for some reason did not copy VxBoot and it is possible that the drivers also failed.
Can you please tell me what is better for me to do next?
If someone can please share the files from the hard drive or a copy of the Tek installation disc.
Thanks in advance for your help

[Xyphro]

I reinstalled my tds7104 2 times from scratch. You need to install the scope software from the tek site. It brings the file with it as part of install. I can also zip you mine in case you are stuck. If you look for adventures also a fully working hd image.

[Xyphro]

In case your power button flatband cable broke (those type of cables are made for max 5 bending cycles) - here a cheap replacement.

Order it as 0.6mm PCB and cut the PCB with a scisor, put a normal flatband cable in between, solder 2 leds on it: And done!

The original cable is offered for 350 US$ right now on ebay - flex pcb remakes for about 50 US$ and this one just costs < 5 US$ and does the job as good as the others.

[charlyd]

hello anybody have an idea why this error is pointing to....
i got  it after installing a different ghost image, which was initially taken from this scope in a working situation, the image worked well before.

the TDS7404 has a new nvram for about 1/2 year ago.

see screenshot

The PPC Board is booting after switch on from ".8" and count normaly up to "-".

Windows boots perfectly, but the 'scope application hangs at the splash screen.

nvram corruption??
[editted:  YES it was.  See post #649]

looking into the logs from earlier exports this is what it shoud be:  but why out of the blue stuck here??  My .sn .key files are in the vxboot in place

Code: [Select]

    TmgrInit("/db")
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
value = 0 = 0x0
    PhxProxyInit
value = 20819072 = 0x13dac80
    rtlInit
value = 0 = 0x0


[Xyphro]

I had lots of errors in the log. Even after putting an image of the  original delivered HD I had the still issues and already was about to dump the scope.

Unbelieveable, but with a complete reinstallation of winxp and all tools it got back to working state.

[charlyd]

today i replace my 6 month old nvram for the Fram board [see attachment 1:]
and yes it works again. see post #647  i have 2 last issues still. 
1)  No SN & KEY. 
2)  SPC fail.   

both worked after i replacement the old nvram with a new nvram, but as told that nvram died again after 6 month that NVRAM i fitted an Alliance chip on but one way or an other no luck.

can the SPC fail issue be generated because of sn & key not installed.
cleardb =1. didn 't work yet.

today a day after...i worked out that  not filling in some bootsetting can make the difference:  stop with "C" and walkthrough step by step try to delete hostname (host) and username ( target)  fill in both areas the "." and <enter>
in the end use "@" to continue booting  and "P"  to show...

but there is an other thing i discovered i see in my bootlog  the lines NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...   are missing. 
one line is for the key en one line for the serial i assume

can anybody explain why they are not shown?

[see attachment 2:]   the leftside log: the log with NVRAM installed before it died  and the rightside log: you see the FRAM bootlog

why are the two lines not entered while booting?

[editted:] that the lines are gone is only a sign that the fram-board is working as it suppose to.  when those two lines popup means the SN and KEY stored in the NVram are not in reach or not stored correct ;-)

so next step is:  how to force the unit from re-initializing as in first boot after replacment.   ( not clearDB )
[EDITTED: for the SN needs the cal-switch in the back of the PPC board tobe switched to unprotect then the serial is written from the .SN file to the NVram in the next boot]