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

[pasta2018]

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?

I dont have a 1GHz sinewave signal, but I believe the BW spec will no be a big issue, instead, maybe the dc voltage error is more obviously.

And now I find another problem ,each time I shutdown and then restart the scope,  the scope goback to default status(before I shutdown it,I open 4 channel display,and after reboot,only CH1 is displayed. And each time after it restart, ch2 baseline offset is quite big,I have to run spc eachtime to make it right.
Seems each time I restart the scope,it loads the factory default. I attach my bootfile here, does anyone know what's the reason?

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.0: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 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)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]  Can
not regis
ter service: RPC: U nable to send; errn]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]]
 ]]]]   ]] ]]]]    ]]]]]]]    ]]]] o =
13
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]una
ble to register
(WINDVIEW, WINDVIEW _VERS_CURRENT, udp)]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]
 ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]].
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       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 = 23737024 = 0x16a32c0
    ld < TekScopeSM.o
value = 23705952 = 0x169b960

    pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x169bc00: value = 23706656 = 0x169bc20 = pDbDev + 0x20
    pDBfs  = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x169b7e0: value = 23706400 = 0x169bb20 = pDBfs + 0x340
    copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0

    overrideFPdefaults()
value = 0 = 0x0

    measurePPCtimebase
value = 0 = 0x0


    registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0

    semInitForQueueCheckLogMsg
value = 23705408 = 0x169b740

    initSysWaiter()
value = 0 = 0x0




    raxInit
value = 0 = 0x0
    paiInit
done
value = 17639480 = 0x10d2838 = PaiBaseRegisterTable + 0x948


    verifyAcqBoardID
value = 0 = 0x0






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

    raxInitializeDevices
0x155fde0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x155fde0 (tShell): (Re)starting Acq Processor
value = 22412208 = 0x155fbb0

    excHookAdd(stopStressForException)
value = 17426908 = 0x109e9dc = stopStressForException


    dsyInit
value = 21784264 = 0x14c66c8
    dsyWPApplyNextRegs
value = 17629356 = 0x10d00ac = DsyRegisterTable + 0xab0









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

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

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

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

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

    GpibInit
value = 133284512 = 0x7f1c2a0

    wfmMemInit(1)
value = 47300320 = 0x2d1bee0

    vertInstall
value = 47293284 = 0x2d1a364

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

0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x155fde0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x155fde0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/2
0x155fde0 (tShellcalConStatus): cc_init: bank  = 2 chksum failed, NOT reset to f
actory
0x0x155fde01321eec (tShell): cc_restoreBank: can't open file : value C:/vxBoot/c
alCons/= 3164335
0x155fde0 (tShell = 0x): cc_init: bank 281ef3 chksum failed, NOT reset to factor
y

0x155fde0 (
tShell): cc_restoreBank: can't open file     updateTrigCaC:/vxBoot/calCons/l5

0x155fde0 (tShell): value = cc_init: bank 05 chksum failed, NOT reset to factory

 = 0x0x155fde0 (tShell0): cc_restoreBank: can't open file
C:/vxBoot/calCons/6

0x155fde0 (tShell):     MathMeasCreatcc_init: bank eTheMa6thandMeasurementLib ch
ksum failed, NOT reset to factory
rar0xies155fde0 (tShell):
cc_restoreBank: can't open file valuC:/vxBoot/calCons/e 7=
0x155fde0 (tShell47120704): cc_init: bank  = 0x7 chksum failed, NOT reset to fac
tory
2cf01400x155fde0
 (tShell): cc_restoreBank: can't open file     initAcqC:/vxBoot/calCons/Ma8pper
0x155fde0 (tShell
): cc_init: bank value = 8 chksum failed, NOT reset to factory
00x155fde0 (tShell = 0x): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
15
0x155fde0 (tShell    trigMapInit):
cc_init: bank 15 chksum failed, NOT reset to factory
val0xue = 155fde0 (tShell0): cc_chkLimits: CC_VERT_ATTENIMBAL_100X_CH2 = 0x was
; reset to factory
00x155fde0
 (tShell): cc_chkLimits:     dsyMCC_VERT_ATTENIMBAL_1X_CH2apInit was ; reset to
factory

0x155fde0value =  (tShell0): initAcqMapper: Enter
 = 0x0
    mathMapperInit
value = 0 = 0x0
    utilMapInit
value = 47118048 = 0x2cef6e0

    TmgrHookup
value = 0 = 0x0
    PhxProxyHookup
value = 0 = 0x0
    hookupAcqMapper
value = 20033680 = 0x131b090 = AcqMapperRtlDataList
    MathMeasMapHookup
value = 22412040 = 0x155fb08
    dsyMapHookup
value = 22412144 = 0x155fb70
    utilMapHookup
value = 22412176 = 0x155fb90

    rtlHookup
value = 0 = 0x0
    horizMapHookup
value = 22412136 = 0x155fb68
    fastFrameMapHookup
value = 22412160 = 0x155fb80
    trigMapHookup
value = 22412168 = 0x155fb88
    vertMapHookup
value = 22412160 = 0x155fb80
    spcMapHookup
value = 22412160 = 0x155fb80
    autosetMapHookup
value = 22412200 = 0x155fba8
    timeSyncMapHookup
value = 22412192 = 0x155fba0
    auxTrigMapHookup
value = 22412176 = 0x155fb90
    dpoMapHookup
value = 22412168 = 0x155fb88


    TmgrStartup
value = 46269840 = 0x2c20590
    PhxProxyStartup
value = 46219296 = 0x2c14020
    taskDelay(2)
value = 0 = 0x0

    gpibHwInitC
value = 0 = 0x0
    gpibTaskSpawn
value = 45990560 = 0x2bdc2a0

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

    enablePowerupDiags = 0
enablePowerupDiags = 0x12f1330: value = 0 = 0x0

    runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
value = 17649712 = 0x10d5030 = 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]

And now I find another problem ,each time I shutdown and then restart the scope,  the scope goback to default status(before I shutdown it,I open 4 channel display,and after reboot,only CH1 is displayed. And each time after it restart, ch2 baseline offset is quite big,I have to run spc eachtime to make it right.

Run a self test when this happens, but do not run SPC. Does it get an error 531?

[pasta2018]

And now I find another problem ,each time I shutdown and then restart the scope,  the scope goback to default status(before I shutdown it,I open 4 channel display,and after reboot,only CH1 is displayed. And each time after it restart, ch2 baseline offset is quite big,I have to run spc eachtime to make it right.

Run a self test when this happens, but do not run SPC. Does it get an error 531?

Thanks for your reply. I  run self test ，the results are all pass even I don’t run spc。 Also sometimes when I start the scope ，it may stop at adding  6008 .

[Jwalling]

Thanks for your reply. I  run self test ，the results are all pass even I don’t run spc。 Also sometimes when I start the scope ，it may stop at adding  6008 .

Do you know the state of the battery on the PPC board?

[pasta2018]

Thanks for your reply. I  run self test ，the results are all pass even I don’t run spc。 Also sometimes when I start the scope ，it may stop at adding  6008 .

Do you know the state of the battery on the PPC board?

Do you mean the battery for NVRAM ，DS9034PC，I checked the old one ,voltage is about 2.98V，and then I bought a new ds9034pcx(new ds9034pc is hard to find, the pcx is with crystal ，I checked this new pcx，voltage is about 3.4V) now I use the new ds9034pcx in my scope. Not sure whether the voltage is right.Maybe I have to buy another battery to give it a try

[Jwalling]

2.98V should be fine. Are you sure it's making contact?
I ask because if it's not, it may not be apparent. On later serial #s, even if the battery is flat, the boot parameters get set correctly, presumably from the BIOS on the PPC board. I am working on a TDS7104 with serial prefix B052XXX which I had to erase the PDIP dallas chip because the serial # did not match the rear sticker. After erasing it, the scope booted fine, and pulled the serial # from the disk.

[charlyd]

Hello i also jump into this topic because i bought myself a TDS7404 too. the unit has win98 installed and has an trigger 463 error in the diagnostics from what i could see.

While waiting on the unit to arrive. does maybe anybody know what this problem could be.  the Manual point me to  optionST but there doesn t ring a bell already

i will add a compilation picture to clear my question. why is there a second option sticker on top of the earlier (original) sticker.  upgraded by tek or??

[wolfy007]

This is more than likely a failed trigger chip, it is a known problem on the TDS7154, TDS7254 & I think the TDS7404, where the trigger chips cook themselves over time. The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.

[KrudyZ]

This is more than likely a failed trigger chip, it is a known problem on the TDS7154, TDS7254 & I think the TDS7404, where the trigger chips cook themselves over time. The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.

The trigger ICs are there for edge trigger only. If they fail, you should still be able to trigger on logic levels which is handled by a different mechanism.
The parts are unfortunately impossible to get. That's why I bought a broken acquisition board to have a spare, when the next one blows on my CSA7404...

[charlyd]

Hello thanks for your reply. KrudyZ do you also think it is the chip, like Wolfy007 says?
mmmm then i took the wrong guess i suppose..

but isn t it that the ACQ board test also fails with a failling trigger chip?  i mean to say i would expect more errors then just the 463 which is pointing to optionST.
I saw the post in this topic from Wolfy007 post #445 with 3 errors uncluded the ACQ board then i would suspect the Tektronix 156827800 chips. but also now?

btw the unit also gives an in-operatable error because calibration is not valid

[smaultre]

The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.

7054&7104 ??  or  vs 7154....7404??? I think that triggers on 7054...7104 is same?

[charlyd]

 i did some extra research. from what i found it is related to the option added by the option key on the back. So i have some hope the unit is lost in its options.
 Somebody on the forum here well known with these options: OptionST Serial Mask Testing and Option Serial Pattern for special communication purpose.
Or maybe have seen this option on other scopes? more info about these trigger option added in the attachments

[wolfy007]

The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.

7054&7104 ??  or  vs 7154....7404??? I think that triggers on 7054...7104 is same?

Yes,  thats right, the TDS7054/TDS7104 are different to the TDS7254&TDS7404.

[charlyd]

What if i wanted to backup my Nvram content so i have a backup. what is the most simpel way to do so. or can the content easily be rebuilded after replacing the NVram or BR1632 Battery.

[charlyd]

Hi Jay, you have replaced the NVram in the 7000 series many time i assume. my question is i have see the current drawing thing from TiN his CSA7404.
but is that on all models from 7000 series or just his model? is it a miss development thing? if yes what can i do about it?
Is buidling in a better battery 3v - 1000mA a good option. to drill a hole in the powercap so it comes truth the powercap cover?

or was this problem only with TiN his unit?

greetz charly

[editted: and so i did]

[Ice-Tea]

Hi Jay, you have replaced the NVram in the 7000 series many time i assume. my question is i have see the current drawing thing from TiN his CSA7404.
but is that on all models from 7000 series or just his model? is it a miss development thing? if yes what can i do about it?
Is buidling in a better battery 3v - 1000mA a good option. to drill a hole in the powercap so it comes truth the powercap cover?

or was this problem only with TiN his unit?

greetz charly

Not 100% sure I understand the question, but I have observed them drawing more current than they should/as from a new device as well.

[charlyd]

Hi Kris, ok so if i understand well the current drawing is high in all the 7000 series because of how there are developped.
And how long do they last again,............after i replaced the NVram chip as well as the battery with new onces?  an other 20years or so..

maybe a strange question because in previous scope it worked like this.  but i read this threat over en over en have seen more then one scope fail after a short period of not used.
So if i can expect a not booting unit anymore after being powered of for 6 month. i will not be really happy and try to avoid this by changing the SRAM part of the setup by what i saw an Alliance - AS6C1008-55TIN chip and feeded by a 3v - 1000mA battery and not the original 120mA

[Ice-Tea]

My memory may be a bit rust and i'm not sure we're taling 100% about the same thing but... The NVRAM in these devices is battery backed up and unlike with other NVRAMS, the battery is actually accesible  if you pop the hood (many other are potted). So you can replace the battery if you wish, which is a cheaper and easier approach. *But* it seems some of these NVRAM devices draw way too much current, draining the replacement battery pretty fast. As far as I know, this had nothing to do with the Tektronix but rather with the NVRAM itself.

[paul@yahrprobert.com]

I can confirm that about the NVRAM current draw.  On my 7104 I replaced the NVRAM battery with one 5 times bigger but it ran out in a day or two.  Only when I found a replacement of the chip did my scope start working again.

[charlyd]

Hi yes for sure. I go for swapping them both.  that is my plan..   

But i have an other important question. the weak spot are the Trigger chips [tektronix 156827800]

i read and see a lot about them inside the models TDS/CSA7254 & TDS/CSA7404 and these chips seem to die easily and concern me because i wanted to renew my equiptment with this unit on my bench so it has to be reliable for a longer period

What can be done, so they will not die?  can a heatsink give them a long life?

Or better question: what is a possible course for them to burn-out?  Is this input related, just heat, not enough airflow or..?

[EDIT] After a closer inspection my unit also has one chip hit. So, anyone having one of these TDS694C or TDS6/7000 acquisition boards lying around or for sale, for free, bad or good? or trigger chip for sale [tektronix 156827800]  please PM

[charlyd]

today i tried to debug my boot process.
What i saw was:
- when i don t connect the breakout cable to J790 connected to a win98 hyperterm pc. the scope boots-up ok and also starts tekscope software complete ending in diagnose screen with the Trigger error  463.
- when i put in the com-port breakout cable the boot stop at "L" on the 7 seg display and tek scope only start and doesn t pass the logoscream ( sort of freeze ) .

when power on the debug info starts scrolling and ends at 

-------------------below i pasted small versions from the end before boot procedure stops------
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 7

------------------------------------------------------------
next time it ends   like this
-------------------------------------------------------------

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 - P "£$$%^%£$Y&**I()(

----------------------------------------------------------------------

and i will add the option screenshot.  and diagnostic screen. where i see corruption too.


who can answer this for me?  ->  i saw here in the topic in post #454 written:  the factory service CAL data part is stored in NVRAM of PPC board. 
if that is the case how can i export that factory service CAL data part out of the NVRAM of PPC board and what if not?
i didn t see any writing before #454 about this factory cal issue.

[charlyd]

Swapping the NVram (piggybag) battery:

First i want to swap out the battery ( and check the voltage level on it) to see if a new battery that helps in booting with a console port connected.
I save myself more time to export the content.

I hope Flyte reads this for his tool ;-) i am willing to help export specific info ( adresses ). so please PM me.

[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.

[charlyd]

Hi Johnny10 thanks for the info, but my NVram did not yet die.  i want to keep the content so i am working on a way to keep it powered. when replacing the Piggybag battery.

Question: i am curious to people who did feed the DS9034P with additional 5 volt to keep it powered and meanwhile pull the powercap with battery and replace it.

@Johnny10 what motherboard are you talking about? the SF810 or the SU810. 
i have them both and for sure they behave total different and bios settings are different too.  where SF810 has monitor of voltages and SU810 has not.

Question: if i do a DB clear by taking away the # in the topScript.hw and boot  is the complete content gone so my factory service call also.?
 
# remove '#' from next line to set powerup scope state to factory default:
    # NvramClearDb = 1

[Johnny10]

This method works on the motherboard CMOS battery failure only.
My motherboard is BL440ZX running Win98 OS.