Author Topic: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU) (Read 324888 times)

smaultre · « **Reply #550 on:** May 25, 2020, 05:26:35 pm »

Hello my friends!
I received my "for parts" TDS 7104 item (many brokens parts, damaged MB, damaged (craked) NLX raiser, missing capacitors, BAD BIOS, BAD Acquisition and control boards FLASHs, missing HDD OS..., and even make it boot's for a several time..(there's some problems with SPC procedure.. but not right now..) NOW, After attempt to add some memory (+256Mb DIMM), and after several BIOS resettings.
I can't enter to the BIOS config!!! Even just reflash it from emergency FDD 1'44.
Who can help me with the CMOS corrupt utility??
On the Tek forum, i'll cant reach it.

Johnny10 · « **Reply #551 on:** May 25, 2020, 06:03:25 pm »

I had this problem a few months ago when my cmos battery died.
It kept me from getting into BIOS and also shutdown the 7104 screen.

I needed to access the VGA connector in back with separate monitor.
You need to install KILLCMOS on floppy MS-DOS start-up disk.
Boot from the floppy and run program.

Takes about 20 seconds.
Took 4 hours to find all equipment to put program on disk :-(

awjennin · « **Reply #552 on:** May 26, 2020, 01:27:56 pm »

The last thing I can think of to get past my "Unsupported Hardware Detected" firmware loading error is to beg/cheat/borrow for a ghosted image - Is anyone capable and willing to help me with that??
SF810 Motherboard, Win2k or WinXP

Mega thank you in advance!

elektropionir · « **Reply #553 on:** May 26, 2020, 01:48:59 pm »

I have SU810 not SF, but it could still work since it is almost the same board. It is about 2GB in size, an image clone of the 24GB drive.
I will upload it somewhere, just tell me if you wish to try it.
You can delete the serial number files when you clone it.
If you clone it to a larger drive you can resize partition later.

smaultre · « **Reply #554 on:** May 26, 2020, 03:09:12 pm »

Bingo! now i corrupt my flash and re-install .gho image from xDevs.
to my 440zx motherboard and it works!
Scope shows 4 lines for 4 channels, each channels triggered, and shows adequate (and same) info, from internal calib.generator, and from my arbstudio gen. lasts to 125Mhz..

But trying to load selftest shows me, that all steps is PASS, but Misc (the last) step, has number 511, 2-fail counts errors.

And it fails to pass SPC tests.

My device goes (parts cond), without any HDD and OS. I install and run an (gho) image from another xDevs scope.
And in properties, it shows not mine(back panel), serial and option numbers. Thats because it was reflashing it corrupted configs, and calibratings binaries from the image file from vxBoot (from xDevs)??

Or there is a hardware problem (broken equip IC) ??

And another bug- that, when i try to reinstall the newest scope app version 2.5.3.2008, its hangs application, on tektronix logo from start. It there is any tricks??

and when i try to put 512Mb CF card to PCMCIA slot, it slows the scopes data displays and not appear as disk drive or something.. BUT the "-" on "8"indicator segment, cause blinks an another way periods.
Does the win98 controls that PCMCIA adapter slots? can i add an 4xUSB2.0 PCMCIA adapter or WI-FI or other??

awjennin · « **Reply #555 on:** May 30, 2020, 02:27:59 am »

Quote from: elektropionir on May 26, 2020, 01:48:59 pm

I have SU810 not SF, but it could still work since it is almost the same board. It is about 2GB in size, an image clone of the 24GB drive.
I will upload it somewhere, just tell me if you wish to try it.
You can delete the serial number files when you clone it.
If you clone it to a larger drive you can resize partition later.

1000 THANK YOU's to ELEKTROPIONIR - I am absolutely elated, this scope is running!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I restored your disk image to my HDD, and had to reinstall all Tek drivers on first power-up, but when completed I rebooted scope, and it fired right up!!!!!!!

You have provided an end to my 2month obsession - Thank you!!!

smaultre · « **Reply #556 on:** May 30, 2020, 04:43:02 am »

what i got:
PCMCIA malfunction cause by interrupts.

It can't pass the SPC, because channels, have some DC offsets by mV, from zero.
I delete cal files (on vxBoot) goes with another scope sys image. But it dont help.

I add my bootlog, and SPC log as a txt.
Its physical malfunction of frontend modules or calibration issule??

smaultre · « **Reply #557 on:** June 04, 2020, 06:51:48 am »

my friends, during the SPC trying I've got "out of SPC thermal zone" which IC makes the thermal sensing??

flyte · « **Reply #558 on:** June 09, 2020, 08:19:02 pm »

FYI: I've posted an NVRAM + PowerPC BIOS dump script for the TDS6000B/7000B series

https://www.eevblog.com/forum/testgear/tektronix-tds6000b7000b-series-nvram-dump-script/

At least one person in this thread had a corrupt BIOS and corrupt NVRAMs are only a matter of time.

smaultre · « **Reply #559 on:** June 12, 2020, 02:45:44 pm »

Quote from: smaultre on June 04, 2020, 06:51:48 am

my friends, during the SPC trying I've got "out of SPC thermal zone" which IC makes the thermal sensing??

Hello again, all of my troubles caused by incorrect input module identification. After reinstalling the new firmware from TEK site.
SPC have "pass" stratus. Thanks for everyone!!!
If you need to PCMCIA works- Disable LAN on BIOS...

benzn · « **Reply #560 on:** June 14, 2020, 12:12:18 am »

Hi folks,

My TDS7404 died after working great a few months ago. After having it unplugged for a few months, I went to turn it on and found that the x86 side of the machine appears to have a dead graphics adapter. I can't get into the BIOS setup and no amount of CMOS clearing will bring things back. It does appear to be functional enough to run MS-DOS headless, however, which I can verify by typing commands that make things beep (there's no serial console on the motherboard is there?). You can read a bit more in another thread [1].

I haven't been able to find any evidence of anyone bringing their scope back from this symptom, so my question here is: given that the PPC board seems healthy (boots up to "L" on the 8-segment display) and the power supply voltages check out according to the Service Manual, it seems like I should be able to swap out the BL440ZX with a Windows 7 upgrade kit from eBay [2], which includes a SF/SU810 motherboard and hopefully things should spring back to life (also I'll get a much faster (in terms of usability) scope out of it!), since the bad BIOS/Video Adapter lives on the x86 motherboard.

Am I correct in my assumptions? Is there anything else I should try?

[1] https://www.eevblog.com/forum/general-computing/need-help-to-recover-bios-on-intel-bl4400zx-tek-tds-8000-scope/msg3095758/#msg3095758.

[2] https://www.ebay.com/itm/Windows-7-SSD-Upgrade-Kit-for-Tektronix-TDS7054-7104-7154-7254-7404-CSA7154-7404/184131076942?ssPageName=STRK%3AMEBIDX%3AIT&var=691843642964&_trksid=p2060353.m1438.l2649

Jwalling · « **Reply #561 on:** June 14, 2020, 09:46:08 am »

Quote from: benzn on June 14, 2020, 12:12:18 am

Hi folks,

My TDS7404 died after working great a few months ago. After having it unplugged for a few months, I went to turn it on and found that the x86 side of the machine appears to have a dead graphics adapter. I can't get into the BIOS setup and no amount of CMOS clearing will bring things back. It does appear to be functional enough to run MS-DOS headless, however, which I can verify by typing commands that make things beep (there's no serial console on the motherboard is there?). You can read a bit more in another thread [1].

I haven't been able to find any evidence of anyone bringing their scope back from this symptom, so my question here is: given that the PPC board seems healthy (boots up to "L" on the 8-segment display) and the power supply voltages check out according to the Service Manual, it seems like I should be able to swap out the BL440ZX with a Windows 7 upgrade kit from eBay [2], which includes a SF/SU810 motherboard and hopefully things should spring back to life (also I'll get a much faster (in terms of usability) scope out of it!), since the bad BIOS/Video Adapter lives on the x86 motherboard.

Am I correct in my assumptions? Is there anything else I should try?

This will get you up and running with the video set to PCI instead of AGP as it should be, even if the on-board graphics are bad. You will need to change the battery on the CPU board as it is likely dead.
It is a DOS boot floppy with a utility to restore the correct CMOS contents which I just made from a TDS7104 with the BL440ZX MB. When you hear three beeps, press F10 to continue booting. When the floppy access light goes out, the CMOS should be restored. Then press CTRL ALT DEL to warm boot the MB. You should then have the LCD display back.

benzn · « **Reply #562 on:** June 14, 2020, 01:32:19 pm »

Wow, Jwalling, thank you! That worked and I'm back in action! Not sure what I can do to repay you, but you have my extreme gratitude 🙏

This makes me wonder if the AGP graphics were always dead (at least since I got the unit) and I never noticed because the BIOS was successfully switching off of them to the PCI graphics... until the CMOS battery died. I was a bit puzzled at how sitting quietly, unplugged on a shelf could be so catastrophic for the motherboard and perhaps it wasn't after all.

Also as an FYI for other folks, I successfully used WinImage (the trial) on Windows 10 to write Jwalling's boot disk to a floppy with a USB drive. There was some amount of unplugging and re-plugging in the USB floppy drive to clear contention on it so that WinImage would work properly but it eventually worked.

Now to put humpty dumpty back together again!

Jwalling · « **Reply #563 on:** June 14, 2020, 07:21:43 pm »

Quote from: benzn on June 14, 2020, 01:32:19 pm

Wow, Jwalling, thank you! That worked and I'm back in action! Not sure what I can do to repay you, but you have my extreme gratitude 🙏

You're welcome! I'm glad it worked.

Lahay_Alexey · « **Reply #564 on:** July 05, 2020, 03:35:53 pm »

Hello Jwalling. I have a similar problem with TDS7054 as Awjennin: UNSUPPORTED HARDWARE DETECTED. Please give me a link to the image you provided to Awjennin.

pasta2018 · « **Reply #565 on:** July 19, 2020, 01:00:59 am »

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.

I also find to extract the firmeware 2.5.5, you can see the performance verification installation file,which can be installed and run performence test or adjustment automatically if you have a fluke 9500 with four probes.

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.3.0
Creation date: Jun 28 2000, 16:52:12




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.169.0.2
user (u)             : anonymous
ftp password (pw)    : anonymous
flags (f)            : 0x1008
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 PC1 dio device driver installed
interface 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.1 .
                             WDB: Ready.

usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
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 = 23662208 = 0x1690e80
    ld < TekScopeSM.o
value = 23661568 = 0x1690c00

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x16927c0: value = 23668704 = 0x16927e0 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1690a40: value = 23661216 = 0x1690aa0 = 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")
0x1697660 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - n
o programming needed.
value = 1 = 0x1
     cd "pc:"
value = 0 = 0x0

    raxInitializeDevices
0x1697660 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x1697660 (tShell): (Re)starting Acq Processor
value = 23688240 = 0x1697430

    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

    nvram_initFileSys
0x1697660 (tShell): >> Kernel version 1.0.8.1  does not match Boot ROM version 1
.0.3.0
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4e943

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

    sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0

    hwAccount_init
0x1697660 (tShell): >> Setting PLL to 1.25e+09 Hz.
sysEnetAddrGet: d5:7b:95:df:75:53
value = 7 = 0x7

    GpibInit
value = 133284512 = 0x7f1c2a0

    wfmMemInit(1)
value = 47300320 = 0x2d1bee0

    vertInstall
value = 47293284 = 0x2d1a364

    calConStatus = cc_init(2)
0x1697660 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x
2d1a240
0x1697660 (tShell): nvMem_read succeeded
0x1697660 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0
x2d1a300
0x1697660 (tShell): nvMem_read succeeded
0x1697660 (tShell): extd chksum failed, stored = 0xffffffff calc = 0x28d5a0ee
0x1697660 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory

0x1697660 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x1697660 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x1697660 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x1697660 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x1697660 (tShell): cc_restoreBank: can't open file calConStatusC:/vxBoot/calCon
s/ = 2
0x16976600x (tShell): cc_init: bank 1341eec2 chksum failed, NOT reset to factory

: v0xalue = 1697660 (tShell164335): cc_restoreBank: can't open file  = 0xC:/vxBo
ot/calCons/281ef3
0x1697660
 (tShell): cc_init: bank
3 chksum failed, NOT reset to factory
    updateT0xrigCal1697660 (tShell
): cc_restoreBank: can't open file vC:/vxBoot/calCons/al5ue =
0x1697660 (tShell0): cc_init: bank  = 0x5 chksum failed, NOT reset to factory
00x1697660 (tShell
): cc_restoreBank: can't open file
C:/vxBoot/calCons/  6  MathMeasCreateThe
MathandMeasurementL0xibraries1697660 (tShell
): cc_init: bank value = 6 chksum failed, NOT reset to factory
471207040x1697660 = 0x (tShell): 2cf0140cc_restoreBank: can't open file
C:/vxBoot/calCons/7    initAcqMapper
0x
1697660 (tShell): cc_init: bank value 7=  chksum failed, NOT reset to factory
0x01697660 (tShell):  = 0xcc_restoreBank: can't open file 0C:/vxBoot/calCons/
8
0x    trigMapInit1697660
 (tShell): cc_init: bank value = 8 chksum failed, NOT reset to factory
00x1697660 = 0x (tShell): 0cc_restoreBank: can't open file
C:/vxBoot/calCons/    ds15yMapInit
0x1697660 (
tShell): cc_init: bank value = 15 chksum failed, NOT reset to factory
00x1697660 = 0x (tShell): cc_chkLimits: 0CC_VERT_ATTENIMBAL_100X_CH2
 was ; reset to factory
    mathMapper0xInit1697660 (tShell
): cc_chkLimits: CC_VERT_ATTENIMBAL_1X_CH2value =  was is0; reset to factory
 = 0x0x1697660 (tShell0): initAcqMapper: Enter

    utilMapInit
value = 47118048 = 0x2cef6e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20164752 = 0x133b090 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 23688072 = 0x1697388
    dsyMapHookup
value = 23688176 = 0x16973f0
    utilMapHookup
value = 23688208 = 0x1697410

    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 23688168 = 0x16973e8
    fastFrameMapHookup
value = 23688192 = 0x1697400
    trigMapHookup
value = 23688200 = 0x1697408
    vertMapHookup
value = 23688192 = 0x1697400
    spcMapHookup
value = 23688192 = 0x1697400
    autosetMapHookup
value = 23688232 = 0x1697428
    timeSyncMapHookup
value = 23688224 = 0x1697420
    auxTrigMapHookup
value = 23688208 = 0x1697410
    dpoMapHookup
value = 23688200 = 0x1697408


    TmgrStartup
value = 46252048 = 0x2c1c010
    PhxProxyStartup
value = 46201504 = 0x2c0faa0
    taskDelay(2)
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 46040768 = 0x2be86c0

    gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 45502752 = 0x2b65120

    enablePowerupDiags = 0
enablePowerupDiags = 0x1311330: value = 0 = 0x0

    runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
0x2bc59a0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2bc59a0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2bc59a0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
value = 17780784 = 0x10f5030 = SoftSwitchesRegisterTable + 0x48

    rtlStartup
value = 0 = 0x0

    tsComp
value = 0 = 0x0

    ################### topScript ends ###############################

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

Jwalling · « **Reply #566 on:** July 19, 2020, 08:58:31 am »

Quote from: pasta2018 on July 19, 2020, 01:00:59 am

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.

pasta2018 · « **Reply #567 on:** July 20, 2020, 12:48:11 am »

It’s really great of you! Maybe I can compare your file with mine to see what’s the difference except calconstans ，I wonder how could this happen unless someone had done adjustment not completely.

Jwalling · « **Reply #568 on:** July 25, 2020, 09:03:39 am »

Does anyone know if there is a way to trash the contents on the Dallas DS1245 chip on the PPC board?
This one has a PDIP, and I'd rather not remove the chip if it can be done from the console port.
I'm replacing this board in a TDS7104 and I need to get rid of the serial # and key.

joeschm@comcast.net · « **Reply #569 on:** July 26, 2020, 06:57:02 pm »

Hi All,

I have a TDS7104 that I just rebuilt the disk on. Everything seems to work fine except I can't do a successful SPC. I get a fail message on the display. I have attached a terminal to the PPC console port. I get slightly different errors each time I run SPC, but all look bad.

I have tried calConStatus = cc_init(1), which seems to execute okay.

I have checked the power supply voltages, and all are good.

So, is my acquisition board toast?

Thanks much

spc_log1.txt (5.77 kB - downloaded 217 times.)

spc_log2.txt (8.34 kB - downloaded 162 times.)

pasta2018 · « **Reply #570 on:** July 27, 2020, 07:19:07 am »

It’s hard to find a new x24165 now,I used a AT24C16B instead， I will try this in a few days.Thanks.

pasta2018 · « **Reply #571 on:** July 27, 2020, 07:40:45 am »

Quote from: pasta2018 on July 27, 2020, 07:19:07 am

It’s hard to find a new x24165 now,I used a AT24C16B instead， I will try this in a few days.Thanks.

Maybe AT24C16B is not a right choose,I will try to find a right chip again.

Jwalling · « **Reply #572 on:** July 27, 2020, 09:17:11 am »

A 24C16 will work fine.

pasta2018 · « **Reply #573 on:** July 31, 2020, 07:12:04 am »

Quote from: Jwalling on July 27, 2020, 09:17:11 am

A 24C16 will work fine.

Thanks，the error 521 disappeared now，I have made some simple test and the test results seems to be acceptable

Jwalling · « **Reply #574 on:** July 31, 2020, 08:50:03 am »

Quote from: pasta2018 on July 31, 2020, 07:12:04 am

Quote from: Jwalling on July 27, 2020, 09:17:11 am
A 24C16 will work fine.
Thanks，the error 521 disappeared now，I have made some simple test and the test results seems to be acceptable

You're welcome, that's great! Does it meet it's BW spec?


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU) (Read 324888 times)

Share me