-
Hi all,
I have been working intermittently for six years |O on a seemingly impossible to finish project. I had the (bad) luck to get my first CSA-8000, a cheap one coming from eBay.de, on 2011 . It was clearly a unit which someone has tried to fix and had let it go... Now I know why!!!
I documented my first attempts to get it working on my WEB:
http://jvgavila.com/csa8000.htm (http://jvgavila.com/csa8000.htm)
Well, to make a very long story short, I have worked so far on six units (five CSA-8000 and one TDS-8000, which are exactly the same). Four of them are mine. None of them works fine yet... The best unit, which I was able to get running on Windows 98 (it was an old hardware unit), even passing the compensation procedure, decided to stop working and have not had the nerve to get back to it. For the other three units, one is a parts unit, and the other two, which run Windows 2000 software, work BUT don't pass the compensation procedure.
All in all, it seems to me that the acquisition board (ACQ BOARD) is the most delicate item on these units. There are several versions of it and I have seen that the hardware has some patches on it which probably are needed to comply with some specifications. These patches are small plug-in circuits. I have seen units with just one of them and other with five of them. Then there are some ACQ boards which have the STROBE coax cables connected and some which not. And they don't seem to be fully interchangeable.
Of course, another very common problem is the NVRAM batteries. There are three of them and all go bad. I have replaced quite a bit of them and have managed to fix the POWER PC non-booting problem but then, the battery on the ACQ BOARD generates calibration faults. I wonder if someone has found the correct way to re-calibrate the mainframe and get rid of those faults.
So, please, could you share your work on these units?. I hope someday to have at least one fully working mainframe ::)
Regards,
Jose
-
This may help
https://forum.tek.com/viewtopic.php?t=138009 (https://forum.tek.com/viewtopic.php?t=138009)
-
This may help
https://forum.tek.com/viewtopic.php?t=138009 (https://forum.tek.com/viewtopic.php?t=138009)
Thanks, I will sure use that info!
Now I am dealing with an XP Upgrade for the CSA8000, which is being kind of a nightmare :(
After several attempts, I had (read later) been able to run the latest version of the Tek software (5.2.1.3), but the front panel did not respond nor the touch panel. I guess that is a matter of XP drivers, right?
To be sure it was not a hardware problem, I have reinstalled the old mainboard with Windows 98 software. But the PC refuses to boot as the BIOS battery was gone and, after replacement, there is no way to enter the BIOS. I have seen you commented on the Tek forum, some years ago, about a program to corrupt the time & date on the BIOS. I wonder if you can share it with me.
OK, so I have returned back to the XP mainboard... to find that now there is no way to properly boot the Windows XP!. It keeps on the welcome display (the one with the progress bar) forever. In safe mode I can get it to boot. But I don't understand why now it does not boot as it did some hours ago |O
Regards,
Jose
-
Well, I have got back to work the Windows XP installation, except for the touch display and the front panel controls. Any hint on this? :-//
As I have two other semi-working units, the other questions about getting into BIOS on the Intel BL440ZX mainboard remain.
Regards,
Jose
-
This may help
https://forum.tek.com/viewtopic.php?t=138009 (https://forum.tek.com/viewtopic.php?t=138009)
Thanks, I will sure use that info!
Now I am dealing with an XP Upgrade for the CSA8000, which is being kind of a nightmare :(
After several attempts, I had (read later) been able to run the latest version of the Tek software (5.2.1.3), but the front panel did not respond nor the touch panel. I guess that is a matter of XP drivers, right?
To be sure it was not a hardware problem, I have reinstalled the old mainboard with Windows 98 software. But the PC refuses to boot as the BIOS battery was gone and, after replacement, there is no way to enter the BIOS. I have seen you commented on the Tek forum, some years ago, about a program to corrupt the time & date on the BIOS. I wonder if you can share it with me.
Jose
Hi Jose,
I sent the file to your email. Did you get it?
-
Hi Jay,
Did you use the GMAIL account?. I have not got it. One trick is to send it with a different extension, like '.ex0' so it is not interpreted as an executable file by the e-mail server. I have also looked on the spam filter but there is no sign of it.
Thanks!
Jose
-
Hi Jay,
Did you use the GMAIL account?. I have not got it. One trick is to send it with a different extension, like '.ex0' so it is not interpreted as an executable file by the e-mail server. I have also looked on the spam filter but there is no sign of it.
Thanks!
Jose
Hi Jose,
Must have gotten deleted by the server. Here it is. There's a nasty bug in many of the motherboards in the TDS6000 7000 and 8000 scopes and that won't allow you to get into the BIOS setup under some conditions. It will say that it's entering setup, but will skip past it instead and try to PXE boot. This MS-DOS executable will corrupt the contents of the CMOS, and allow you to enter the BIOS setup again.
-
Hi Jose,
Must have gotten deleted by the server. Here it is. There's a nasty bug in many of the motherboards in the TDS6000 7000 and 8000 scopes and that won't allow you to get into the BIOS setup under some conditions. It will say that it's entering setup, but will skip past it instead and try to PXE boot. This MS-DOS executable will corrupt the contents of the CMOS, and allow you to enter the BIOS setup again.
Yes, this is exactly what happened to two of my units. On first one, I thought the board was bad. But, when it happened on another one, I searched on Internet and found your comments on that problem :-+
I will report back when I have the chance to check this on those units.
I am still fighting with the XP problem with the front panel controls and touch panel. The touch panel is even listed as a device on XP and the software for it, from 3M, is present and works. I wonder if it could be a problem with the POWER PC board, as those items are directly connected to it.
Regards,
Jose
-
Was it working with the original O/S?
-
Was it working with the original O/S?
That is the reason to fix the Intel BL440ZX mainboard with your program ;)
Once I get into BIOS and have the mainboard back to working condition, I will try it with the Windows 98 SE installation.
Regards,
Jose
-
Was it working with the original O/S?
Well, I have had some time to check your program. Brilliant !!! :-+ :-+ :-+
I have been able to enter BIOS settings on the Intel BL440ZX mainboard and then restart the unit with the old Windows 98 SE software (which came with the unit). With it, the touch panel and the front panel controls work flawlessly :D
So it seems a matter of Windows XP software. I will reinstall the Windows XP-compatible mainboard and will try to get the unit fully working. I will let you know what I find.
Thanks again!
Jose
-
There are other threads discussing the close cousin of your scope:
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/ (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/)
I think the PC motherboard is the same. Somebody over there discussed the subject of drivers for Win XP and they might even be posted at Tin's web site.
Good luck :)
-
There are other threads discussing the close cousin of your scope:
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/ (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/)
I think the PC motherboard is the same. Somebody over there discussed the subject of drivers for Win XP and they might even be posted at Tin's web site.
Good luck :)
Yes, I found the reason on that thread :clap:
This is the relevant information:
The only hardware configuration necessary is to set the two USB jumpers for the front panel setting as the second USB port is used to connect to the oscilloscope's front panel through the NLX backplane connector.
Once I have modified the default jumper position, on next boot the front panel controls and the touch panel have worked fine :-+
Now for the next problem: compensation fails on this unit. And also on my two other semi-working units! |O
Regards,
Jose
-
Hey,
I'm working on fixing one of these too. By any chance do you know what the B: drive is. I've been looking all over for it. I have a feeling that it has to do with the NLX interface because I've tried plugging in different drives, removing them, swapping out the RAM, etc. I'm getting some floppy discs tomorrow so I'm guessing that I can just put a DOS program on there and execute the CMOS file (As I have the same issue with getting into the BIOS). I so happened to just have one, and I got something only once, but then it never booted to the Floppy again, which I thought was weird. One other interesting artifact that I found was that the PowerPC doesn't ever get past a certain point. I have attached the output below:
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...
1
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : c:\progra~1\tdscsa~1\firmware\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) : 0x1008
target name (tn) : target
startup script (s) : c:\progra~1\tdscsa~1\firmware\dio.vsh
other (o) : nvfs=0x1000
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
But It never gets passed the Backplane anchor,
Any ideas?
This program is in the Flash on the Motherboard. The HDD seems like it's broken because it rattles, but when I plug it into a converter I am able to get all of the files off of it (so I made a backup). So I am kind of stuck here. I mean the other possibility is that this is just a motherboard issue, so I have a motherboard on its way to see how that turns out. Anyways if you have any input or thoughts on the problem(s), I'm all ears.
Thanks,
Simon
-
Hello!
This is the correct boot of my Windows XP system right now:
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...
1
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : c:\progra~1\tdscsa~1\firmware\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) : 0x1008
target name (tn) : target
startup script (s) : c:\progra~1\tdscsa~1\firmware\dio.vsh
other (o) : nvfs=0x1000
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network interfacPC1 dio device driver installed
e lo0... done.
Attaching DIO client... done.
Loading c:\progra~1\tdscsa~1\firmware\vxWorks.st...1771964
Starting at 0x200000...
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 6006 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.5.
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:\progra~1\tdscsa~1\firmware\dio.vsh ...
dbFsIoctl: invalid code 3
cd "c:/progra~1/tdscsa~1/firmware"
value = 0 = 0x0
*0xfec00000 = 0x04b00080;*0xfee00000 = 0x17009002
ppp_parms + 0xfe84f680 = 0xfec00000: value = 78643328 = 0x4b00080
ppp_parms + 0xfea4f680 = 0xfee00000: value = 385912834 = 0x17009002
*0xfec00000 = 0x88a10080;*0xfee00000 = 0x01800000
ppp_parms + 0xfe84f680 = 0xfec00000: value = -2002714496 = 0x88a10080 = ppp_parms + 0x8865f700
ppp_parms + 0xfea4f680 = 0xfee00000: value = 25165824 = 0x1800000
*0xfe008002 = 0;*0xfe00800e = 0;*0xfe008012 = 0
ppp_parms + 0xfdc57682 = 0xfe008002: value = 0 = 0x0
ppp_parms + 0xfdc5768e = 0xfe00800e: value = 0 = 0x0
ppp_parms + 0xfdc57692 = 0xfe008012: value = 0 = 0x0
symSyncTimeoutSet 600000
value = 600000 = 0x927c0
ld <hi32.o
value = 31002016 = 0x1d90da0 = Hi32SystemProcessorBoard + 0xa98
Hi32SystemProcessorBoard = 1
Hi32SystemProcessorBoard = 0x1d90308: value = 1 = 0x1
CmdDspDevName = "/dev/cmddsp0"
new symbol "CmdDspDevName" added to symbol table.
CmdDspDevName = 0x1d90cc0: value = 31002464 = 0x1d90f60 = CmdDspDevName + 0x2a0
hi32Drv
value = 0 = 0x0
hi32DevCreate CmdDspDevName,0x80006000,0xa0000000,3
value = 0 = 0x0
ld <cmddsp.o
value = 31000320 = 0x1d90700 = Hi32SystemProcessorBoard + 0x3f8
ld <acqdsp.o
value = 31000800 = 0x1d908e0 = Hi32SystemProcessorBoard + 0x5d8
ld <diagcmddsp.o
value = 31008192 = 0x1d925c0
ld <diagModule_wmp.o
value = 31007552 = 0x1d92340
ld < systemLibraryCode.o
value = 31007104 = 0x1d92180
CSSDefaultDioDisable=0
CSSDefaultDioDisable = 0x1b203e0: value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 31001312 = 0x1d90ae0 = Hi32SystemProcessorBoard + 0x7d8
ld < nvSysLib.o
value = 30999648 = 0x1d90460 = Hi32SystemProcessorBoard + 0x158
ld < bucket.o
value = 31003968 = 0x1d91540 = CmdDspDevName + 0x880
MathMeasCreateMappingFcns = 1
MathMeasCreateMappingFcns = 0x1a541f0: value = 1 = 0x1
TmgrExecuteAllMappingFunctionsEnable=1
TmgrExecuteAllMappingFunctionsEnable = 0x1a506f4: value = 1 = 0x1
ld < as.o
value = 28451296 = 0x1b221e0
ld < ifcProxy.o
value = 28450720 = 0x1b21fa0
acqCheckForCmdDsp=1
new symbol "acqCheckForCmdDsp" added to symbol table.
acqCheckForCmdDsp = 0x1d90660: value = 1 = 0x1
ld < rtlLibTarget.o
value = 28337696 = 0x1b06620
ld < slotMgrLightLibTarget.o
value = 28294080 = 0x1afbbc0
sysExtMemAddToPool memSysPartId ,0x02000000 ,0x02000000
value = 0 = 0x0
MathMeasDisableParseExpr = 1
new symbol "MathMeasDisableParseExpr" added to symbol table.
MathMeasDisableParseExpr = 0x3fff400: value = 1 = 0x1
use100Breakpoints=1
use100Breakpoints = 0x12ebd5c: value = 1 = 0x1
pWfmMemPool=0
pWfmMemPool = 0x1ab1d60: value = 0 = 0x0
AcqLibFourChannelProto = 0
new symbol "AcqLibFourChannelProto" added to symbol table.
AcqLibFourChannelProto = 0x3fff3a0: value = 0 = 0x0
AcqExecHardWireChannelSources = 0
AcqExecHardWireChannelSources = 0xf8b450: value = 0 = 0x0
doTekprobeExec=1
doTekprobeExec = 0x1060e20: value = 1 = 0x1
pDbDev = ramDevCreate(0, 640, 1024, 1024, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x3f5f2c0: value = 67105536 = 0x3fff300
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x3f5dba0: value = 66449888 = 0x3f5f1e0
copy ("TDS666.DBF", "/db/TDS666.DBF")
value = 0 = 0x0
dbPath = "/db/"
new symbol "dbPath" added to symbol table.
dbPath = 0x3f5daa0: value = 66444064 = 0x3f5db20 = dbPath + 0x80
wfmMemInit 0
value = 54057344 = 0x338d980
jNVInitMgrs
value = 0 = 0x0
TmgrInit(dbPath)
value = 0 = 0x0
rtlInit
value = 0 = 0x0
MathMeasCreateTheMathandMeasurementLibraries
value = 48238240 = 0x2e00ea0
initAcqMapper
value = 48126784 = 0x2de5b40
autosetMapInit
value = 48126336 = 0x2de5980
mathMapperInit
value = 0 = 0x0
initUtilityMapper
value = 48119488 = 0x2de3ec0
initWfmXmtrMapper
value = 48115040 = 0x2de2d60
commInit__Fv
value = 0 = 0x0
JanusProxyInit
value = 48082048 = 0x2ddac80
acqExecAllocUploadBuffers
value = 47446176 = 0x2d3f8a0
acqExecInitWfmHdrTemplates
value = 47418848 = 0x2d38de0
autosetInit__Fv
value = 0 = 0x0
TmgrHookup
value = 0 = 0x0
rtlHookup
value = 0 = 0x0
hookupAcqMapper
value = 31028064 = 0x1d97360
autosetMapHookup
value = 31028080 = 0x1d97370
MathMeasMapHookup
value = 31027872 = 0x1d972a0
hookupUtilityMapper
value = 31028056 = 0x1d97358
hookupWfmXmtrMapper
value = 31028056 = 0x1d97358
commHookup__Fv
value = 0 = 0x0
JanusProxyHookup
value = 0 = 0x0
autosetHookup__Fv
value = 28231776 = 0x1aec860 = waitForTransCompleteSem(sem_des*,int*)
taskSpawn "startEmbedded", 50, 0x0008, 100000, startEmbeddedOperation
value = 47160480 = 0x2cf9ca0
Done executing startup script c:\progra~1\tdscsa~1\firmware\dio.vsh
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> done
done
done
done
connectionTask: handshaking with peer...
connectionTask: handshaking with peer - done.
connectionTask: handshaking with peer...
connectionTask: handshaking with peer - done.
connectionTask: handshaking with peer...
If the PC mainboard is not starting up right, I think it is normal for the POWER PC one to get stuck at the point you show.
What I did to get back to work the older PC mainboard (not the newer one for XP) was to place the BIOS jumper on the 2-3 position (the jumper just side-by-side the CMOS battery, which is usually between 1-2) and then put an MS-DOS 6.2 boot disk on drive A. Yes, I got also the Drive B not ready error, but after that, the mainboard booted and I was able to run the corrupt.exe program.
On next reboot, it entered BIOS SETUP and I was able to reset to default values, change the VIDEO BOARD to PCI (so it uses the built-in display) and then exit saving info. I put back the jumper to 1-2 and then I got back the Windows 98 SE functionality.
I hope this helps!
Regards,
Jose
-
Hey,
I'm working on fixing one of these too. By any chance do you know what the B: drive is. I've been looking all over for it. I have a feeling that it has to do with the NLX interface because I've tried plugging in different drives, removing them, swapping out the RAM, etc. I'm getting some floppy discs tomorrow so I'm guessing that I can just put a DOS program on there and execute the CMOS file (As I have the same issue with getting into the BIOS). I so happened to just have one, and I got something only once, but then it never booted to the Floppy again, which I thought was weird. One other interesting artifact that I found was that the PowerPC doesn't ever get past a certain point. I have attached the output below:
snip
But It never gets passed the Backplane anchor,
Any ideas?
This program is in the Flash on the Motherboard. The HDD seems like it's broken because it rattles, but when I plug it into a converter I am able to get all of the files off of it (so I made a backup). So I am kind of stuck here. I mean the other possibility is that this is just a motherboard issue, so I have a motherboard on its way to see how that turns out. Anyways if you have any input or thoughts on the problem(s), I'm all ears.
Thanks,
Simon
It won't get past that until the Windows O/S starts to boot.
-
Cool, I got the unit to boot. I was using DOS 6.22, and a USB Floppy converter using Windows 10. I should have known not to do that even though I was running '95 on a VM. I just grabbed an old computer and boom it worked just as you said. I'm going to try to upgrade this one to XP as well. If I make any progress I'll post.
Thanks,
Simon
-
Cool, I got the unit to boot. I was using DOS 6.22, and a USB Floppy converter using Windows 10. I should have known not to do that even though I was running '95 on a VM. I just grabbed an old computer and boom it worked just as you said. I'm going to try to upgrade this one to XP as well. If I make any progress I'll post.
Thanks,
Simon
Great news!. Which mainboard do you have?. The Windows XP version runs only on newer ones, the Intel SU810 NLX. They are available on eBay at decent prices. Then you would need the XP System Restoration DVD and an XP Pro licence to activate it. The application software can then be downloaded from Tektronix.
Regards,
Jose
-
I ordered one of those boards (Intel SU810 NLX) because I have the MUCH older BL440ZX motherboard. I actually am pretty close to getting XP to upgrade on this setup (So I think). I have like 20 copies of XP Professional (all service packs). I've had a bit of success with SP2 interestingly enough. I made a copy of the other HDD to play with. Interestingly enough this scope didn't fail any of the tests. Maybe I got lucky? But it only loaded the software correctly once. I started sampling with the 80C02 characterizing a few pulses to make sure that the scope wasn't "lying" with its time domain and that all of the pulses "lined up" properly [I read your web page and looked for similar problems]. Too bad I didn't take any pictures because like I said, it won't go back. I think that the original HDD was corrupt so that explains all of the crashes. I've done quite a bit to the setup to make it run more smoothly, but it's still getting there. It might be a bad idea to try to get this current setup to run XP, but I've got until tomorrow or Wednesday until I get the motherboard so I'll just mess with it.
Oh, I forgot to mention, I managed to get a copy of the system restore stuff too for XP.
On another note: Have you heard of Win 7 running on these scopes because I found it interesting somebody was selling software for the scope to run Win 7?
Simon
-
On another note: Have you heard of Win 7 running on these scopes because I found it interesting somebody was selling software for the scope to run Win 7?
Simon
Doubt that's possible. The i810 chipset only supports 512MB DRAM. The video chipset would be a problem as well.
Where did you see that?
-
I ordered one of those boards (Intel SU810 NLX) because I have the MUCH older BL440ZX motherboard. I actually am pretty close to getting XP to upgrade on this setup (So I think). I have like 20 copies of XP Professional (all service packs). I've had a bit of success with SP2 interestingly enough. I made a copy of the other HDD to play with. Interestingly enough this scope didn't fail any of the tests. Maybe I got lucky? But it only loaded the software correctly once. I started sampling with the 80C02 characterizing a few pulses to make sure that the scope wasn't "lying" with its time domain and that all of the pulses "lined up" properly [I read your web page and looked for similar problems]. Too bad I didn't take any pictures because like I said, it won't go back. I think that the original HDD was corrupt so that explains all of the crashes. I've done quite a bit to the setup to make it run more smoothly, but it's still getting there. It might be a bad idea to try to get this current setup to run XP, but I've got until tomorrow or Wednesday until I get the motherboard so I'll just mess with it.
Oh, I forgot to mention, I managed to get a copy of the system restore stuff too for XP.
On another note: Have you heard of Win 7 running on these scopes because I found it interesting somebody was selling software for the scope to run Win 7?
Simon
Yes, I saw them on eBay last week... And they sold the same mainboard for it!. But prices were out of sight completely... and now they are gone.
Regards,
Jose
-
Yes, I saw them on eBay last week... And they sold the same mainboard for it!. But prices were out of sight completely... and now they are gone.
Regards,
Jose
Do you have a link for those, Jose?
-
http://www.ebay.com/itm/TDS6000-TDS7000-TDS8000-Windows-7-Upgrade-Kit-with-chassis-TDS6000-TDS7000-TDS-/401335497819?hash=item5d7175b45b:g:BSkAAOSwTf9ZThVn (http://www.ebay.com/itm/TDS6000-TDS7000-TDS8000-Windows-7-Upgrade-Kit-with-chassis-TDS6000-TDS7000-TDS-/401335497819?hash=item5d7175b45b:g:BSkAAOSwTf9ZThVn) Look at that? It seems it works? But I don't know why you would need Win 7 because from what I thought all of the newest updates are for XP.
Simon
-
Oops!. I thought they were sold by same seller, so I had not located it today ;)
So the mainboard may be different, but they say also 512MB and 800MHz... not too fast for Windows 7, I think. Windows Experience Index is 1.0 according to the picture.
Regards,
Jose
-
Maybe this one is the one you were looking for:
http://www.ebay.com/itm/Tektronix-TDS7054-TDS7104-TDS-CSA7404-TDS-CSA8000-Windows-XP-Upgrade-Opt-Chassis-/182637750824?epid=96961873&hash=item2a860eea28:g:tyYAAOSwMmBV1pBR (http://www.ebay.com/itm/Tektronix-TDS7054-TDS7104-TDS-CSA7404-TDS-CSA8000-Windows-XP-Upgrade-Opt-Chassis-/182637750824?epid=96961873&hash=item2a860eea28:g:tyYAAOSwMmBV1pBR)
Simon
-
http://www.ebay.com/itm/TDS6000-TDS7000-TDS8000-Windows-7-Upgrade-Kit-with-chassis-TDS6000-TDS7000-TDS-/401335497819?hash=item5d7175b45b:g:BSkAAOSwTf9ZThVn (http://www.ebay.com/itm/TDS6000-TDS7000-TDS8000-Windows-7-Upgrade-Kit-with-chassis-TDS6000-TDS7000-TDS-/401335497819?hash=item5d7175b45b:g:BSkAAOSwTf9ZThVn) Look at that? It seems it works? But I don't know why you would need Win 7 because from what I thought all of the newest updates are for XP.
Simon
That's nuts. :palm:
https://support.microsoft.com/en-ph/help/10737/windows-7-system-requirements (https://support.microsoft.com/en-ph/help/10737/windows-7-system-requirements)
MS recommends 1GB RAM minimum and 1GHz CPU.
When you start loading analysis software (And I've seen some that will use over 300MB of memory) you're going to use up all the memory and be using the swap file on the disk drive. Performance must suck!
-
This makes no sense to me, but I installed 128Mb of ECC SDRAM into the motherboard (That's it!), ran SP2, and right now XP is installed. I will run more thorough tests with the OS, but it's booting, and seems to be running like a champ on my current setup. :box: I will mention though, I have another partition on the HDD for XP, and have the old '98 setup on another partition as well. (This keeps the PowerPC board happy). I can't seem to figure out how to install the Tek 8000 Series Oscilloscope Application, as I got TekVisa Installed and all of that. I guess I'll go fish for it on the disk.
I'll keep you posted,
Simon
-
Maybe this one is the one you were looking for:
http://www.ebay.com/itm/Tektronix-TDS7054-TDS7104-TDS-CSA7404-TDS-CSA8000-Windows-XP-Upgrade-Opt-Chassis-/182637750824?epid=96961873&hash=item2a860eea28:g:tyYAAOSwMmBV1pBR (http://www.ebay.com/itm/Tektronix-TDS7054-TDS7104-TDS-CSA7404-TDS-CSA8000-Windows-XP-Upgrade-Opt-Chassis-/182637750824?epid=96961873&hash=item2a860eea28:g:tyYAAOSwMmBV1pBR)
Simon
Yes, but that one is for XP. In fact, the kit I have got is one of these, but I didn't pay for it directly. It is a long story...
Jose
-
So I installed the drivers for the 7k series on my scope and edited my PowerPC parameters to match the new firmware, but the scope won't load the scope program. Any ideas? (I successfully installed the v5.2 Software)
Thanks!
Simon
-
So I installed the drivers for the 7k series on my scope and edited my PowerPC parameters to match the new firmware, but the scope won't load the scope program. Any ideas? (I successfully installed the v5.2 Software)
Thanks!
Simon
How does the POWER PC mainboard log compares to the one I published on this thread?. As my unit boots and works on XP, that could be a good lead.
Jose
-
Hey,
Mine looks very similar. (I am just using D drive instead of C)
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...
1
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : d:\progra~1\tdscsa~1\firmware\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) : 0x1008
target name (tn) : target
startup script (s) : d:\progra~1\tdscsa~1\firmware\dio.vsh
other (o) : nvfs=0x1000
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 d:\progra~1\tdscsa~1\firmware\vxWorks.st...1771964
Starting at 0x200000...
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 6006 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.5.
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 d:\progra~1\tdscsa~1\firmware\dio.vsh ...
dbFsIoctl: invalid code 3
cd "c:/progra~1/tdscsa~1/firmware"
value = 0 = 0x0
*0xfec00000 = 0x04b00080;*0xfee00000 = 0x17009002
ppp_parms + 0xfe84f680 = 0xfec00000: value = 78643328 = 0x4b00080
ppp_parms + 0xfea4f680 = 0xfee00000: value = 385912834 = 0x17009002
*0xfec00000 = 0x88a10080;*0xfee00000 = 0x01800000
ppp_parms + 0xfe84f680 = 0xfec00000: value = -2002714496 = 0x88a10080 = ppp_parms + 0x8865f700
ppp_parms + 0xfea4f680 = 0xfee00000: value = 25165824 = 0x1800000
*0xfe008002 = 0;*0xfe00800e = 0;*0xfe008012 = 0
ppp_parms + 0xfdc57682 = 0xfe008002: value = 0 = 0x0
ppp_parms + 0xfdc5768e = 0xfe00800e: value = 0 = 0x0
ppp_parms + 0xfdc57692 = 0xfe008012: value = 0 = 0x0
symSyncTimeoutSet 600000
value = 600000 = 0x927c0
ld <hi32.o
value = 31002016 = 0x1d90da0 = Hi32SystemProcessorBoard + 0xa98
Hi32SystemProcessorBoard = 1
Hi32SystemProcessorBoard = 0x1d90308: value = 1 = 0x1
CmdDspDevName = "/dev/cmddsp0"
new symbol "CmdDspDevName" added to symbol table.
CmdDspDevName = 0x1d90cc0: value = 31002464 = 0x1d90f60 = CmdDspDevName + 0x2a0
hi32Drv
value = 0 = 0x0
hi32DevCreate CmdDspDevName,0x80006000,0xa0000000,3
value = 0 = 0x0
ld <cmddsp.o
value = 31000320 = 0x1d90700 = Hi32SystemProcessorBoard + 0x3f8
ld <acqdsp.o
value = 31000800 = 0x1d908e0 = Hi32SystemProcessorBoard + 0x5d8
ld <diagcmddsp.o
value = 31008192 = 0x1d925c0
ld <diagModule_wmp.o
value = 31007552 = 0x1d92340
ld < systemLibraryCode.o
value = 31007104 = 0x1d92180
CSSDefaultDioDisable=0
CSSDefaultDioDisable = 0x1b20480: value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 31001312 = 0x1d90ae0 = Hi32SystemProcessorBoard + 0x7d8
ld < nvSysLib.o
value = 30999648 = 0x1d90460 = Hi32SystemProcessorBoard + 0x158
ld < bucket.o
value = 31003968 = 0x1d91540 = CmdDspDevName + 0x880
MathMeasCreateMappingFcns = 1
MathMeasCreateMappingFcns = 0x1aa60b8: value = 1 = 0x1
TmgrExecuteAllMappingFunctionsEnable=1
TmgrExecuteAllMappingFunctionsEnable = 0x1aa2694: value = 1 = 0x1
ld < as.o
value = 28451456 = 0x1b22280
ld < ifcProxy.o
value = 28450880 = 0x1b22040
acqCheckForCmdDsp=1
new symbol "acqCheckForCmdDsp" added to symbol table.
acqCheckForCmdDsp = 0x1d90660: value = 1 = 0x1
ld < rtlLibTarget.o
value = 28340096 = 0x1b06f80
ld < slotMgrLightLibTarget.o
value = 28287200 = 0x1afa0e0
sysExtMemAddToPool memSysPartId ,0x02000000 ,0x02000000
value = 0 = 0x0
MathMeasDisableParseExpr = 1
new symbol "MathMeasDisableParseExpr" added to symbol table.
MathMeasDisableParseExpr = 0x3fff400: value = 1 = 0x1
use100Breakpoints=1
use100Breakpoints = 0x14f6e34: value = 1 = 0x1
pWfmMemPool=0
pWfmMemPool = 0x1abf1f0: value = 0 = 0x0
AcqLibFourChannelProto = 0
new symbol "AcqLibFourChannelProto" added to symbol table.
AcqLibFourChannelProto = 0x3fff3a0: value = 0 = 0x0
AcqExecHardWireChannelSources = 0
AcqExecHardWireChannelSources = 0x119ecfc: value = 0 = 0x0
doTekprobeExec=1
doTekprobeExec = 0x128cbc4: value = 1 = 0x1
pDbDev = ramDevCreate(0, 640, 1024, 1024, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x3f5f2c0: value = 67105536 = 0x3fff300
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x3f5dba0: value = 66449888 = 0x3f5f1e0
copy ("TDS666.DBF", "/db/TDS666.DBF")
value = 0 = 0x0
dbPath = "/db/"
new symbol "dbPath" added to symbol table.
dbPath = 0x3f5daa0: value = 66444064 = 0x3f5db20 = dbPath + 0x80
wfmMemInit 0
value = 55695744 = 0x351d980
jNVInitMgrs
value = 0 = 0x0
TmgrInit(dbPath)
value = 0 = 0x0
rtlInit
value = 0 = 0x0
MathMeasCreateTheMathandMeasurementLibraries
value = 50112544 = 0x2fca820
initAcqMapper
value = 50083584 = 0x2fc3700
autosetMapInit
value = 50083168 = 0x2fc3560
mathMapperInit
value = 0 = 0x0
initUtilityMapper
value = 50076320 = 0x2fc1aa0
initWfmXmtrMapper
value = 50072160 = 0x2fc0a60
commInit__Fv
value = 0 = 0x0
JanusProxyInit
value = 50038272 = 0x2fb8600
acqExecAllocUploadBuffers
undefined symbol: acqExecAllocUploadBuffers
Done executing startup script d:\progra~1\tdscsa~1\firmware\dio.vsh
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
But I think I see what's wrong. I'll copy the OS over to a fresh drive and let you know, because everything is on the D: drive right now, and it seems that the code needed it to be on the C: drive.
Simon
Edit:
It seems to make no difference if I change the .vsh file.
Edit 2:
I will just wait for the board to come in tomorrow and see what it does.
-
Got the whole scope working! Getting some Optical Modulators tomorrow so that I can mess with the scope.
Simon
-
Hello Everyone,
My boss bought a CSA8000 off of eBay that had a failed hard drive. He asked me to put a new SATA hard drive in it and install Windows 2000. I got a little back plane converter to put in a SATA drive in the place if the IDE. Here is what I have so far. The unit came to me, failed hard drive, no video on the display (works with external monitor), drive B error at boot up, PXE boot (no hard drive seen), says it will enter setup when F2 is pressed (never goes into setup). CD player does not open.
So, I downloaded a BIOS update for Intel BL440ZX board from the Intel site. Put it on a bootable floppy and booted the system up with the floppy. It came up and ran the BIOS update (big mistake). Now when I try to boot it up, there is nothing. No display, no boot sounds, no post, etc. I remove the CMOS battery, nothing. I set the CMOS jumper to pins 2/3 from 1/2, still nothing.
I read somewhere after the fact not to update the BIOS using firmware updates from the Intel site. That is what I did. How can I get this thing back with the right BIOS firmware so it will somewhat boot again?
PS - If I take the jumper off the pins and power on, it will try to read the floppy drive. Won't boot from it, but I believe that setting is to restore a BIOS if I had the proper files.
Thanks for your help!
ID10T Error
-
Got the whole scope working! Getting some Optical Modulators tomorrow so that I can mess with the scope.
Simon
Great news!!!
Please, try the compensation procedure for the mainframe (and any plug-in you may have) and let us know the results. If the unit passes, you have got a good one :-+
Regards,
Jose
-
Anyone have any thoughts on how I can re-flash the BIOS and where I can get the required BIOS files?
Thanks,
-
Anyone have any thoughts on how I can re-flash the BIOS and where I can get the required BIOS files?
Thanks,
Sorry, I have not (yet!) needed to do that on any of my units. All other possible faults have happened, though |O
One possible solution is to get a replacement mainboard. It would be cheap enough, I guess, as when you update to Windows XP there is a surplus mainboard left. I have one but I live in Spain, a bit far from you.
Regards,
Jose
-
Thanks Jose!
Yeah, I live in the States. A bit far to ship. I wished I wouldn't of tried updating the BIOS. It was posting, although I couldn't go into setup or see the drives. I contacted Tektronix and they don't seem to be able to help me. All they say is to ship the unit in for repair. Not sure what that would cost. I want to put Windows 2000 on it. I tried everything I could think of. I don't get any display now. It would be nice if we could back out the BIOS update I did. It had to be the right update for that board or I wouldn't think it would have taken it.
Would anybody be able to take a backup of their BIOS and send me the files? It would be greatly appreciated!
Thanks!
-
@EB5AGV Compensation passes, everything passes! I guess I lucked out!!! I ran all the tests. The only thing is that one of these modules that I bought hasn't been calibrated since 1999! I'm sure there's a calibration procedure somewhere. (I heard it's really well documented)
@ID10TError Did you hook up an external display (The top port)? If there is any output I can guide you through that because I had to go through that procedure, it took many many hours to figure out. (I also saw on another forum DO NOT FLASH INTEL BIOS, so I didn't, but hey maybe it will still work because my XP machine runs the Intel BIOS)
-
@tpsimon - I do have an external monitor hooked up because the built in display does not appear to be working. However, I get no display, post, beeps, nothing. If I remove the CMOS jumper from all the pins, when I turn it on, you can hear it try to access the floppy drive, but still no display. I read somewhere where it would read a disk with the correct backup BIOS on it and reload it. I was hoping to find someone with a good BIOS they could make a backup copy for me and I can see if that will load. Any thoughts?
-
@ID10TError Unfortunately I do not have a copy of the software BIOS for that Motherboard Model. My unit did not come with any backup CDs etc. You can grab a new motherboard with all the CDs on Ebay; that is probably your best bet.
Simon
-
go to Ilya's web site: (Tin) :-+
https://xdevs.com/fix/csa7404/
and read carefully. You might find the information you're looking for. :)
-
Hi everyone
I have been given the Task to repair a TDS 8000. I'm an IT person btw.
So far i have replaced the cpu, upgrade to 512Mb and installed windows Xp . it seems the MB is the SU 810. Most drivers had been installed so far
I have read all the pages i could find on the web and this forum. The Tek scope application will hangs when launched , so i am getting a new battery for the power pc.
What is my next step to make sure the nvram is functional and power pc boots again. I am reading this page https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/ (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/)
but is confuse about how to get a serial connected and also load the proper powerpc firmware/booltlaoder
Thanks for your help. :)
-
Hi guys,
I've got a sick puppy (the harddisk is flapping about) of a CSA8200 (same family as TDS8000 series).
Can anyone point me in the right direction for the reinstall windows.... doesn't appear available from the tek site.
much appreciated!
-
Hi guys,
I've got a sick puppy (the harddisk is flapping about) of a CSA8200 (same family as TDS8000 series).
Can anyone point me in the right direction for the reinstall windows.... doesn't appear available from the tek site.
much appreciated!
This is an older post... though for the record :popcorn::
You can place the HD in a zip lock or sealed freezer bag and freeze then take out and backup and/or clone the drive to save time on re-installation. You can repeat this until you recover the data. Sure beats hunting down an exact board for the drive and replacing to recover the data... that is... if the board is bad.
If you want, you can perform error checking also.
I'm prepping to do this before I open the case of the TDS-8000B I purchased for a great deal and am hoping to restore to use as the "oscilloscope I don't want to use too much, since costs so much, though is my best scope." :D
-
hello,
could you help? I am having drivers issues trying to reconstruct from winXP. Could you help?
-
Hey, could you guide into what you did to have XP working?
I am suspecting that the PCI1225 is part of the problem that has conflicts on my unit (no enough resources).
Thank you,
Gaston
-
Jose, could you help? I am stuck on XP upgrade.
Gaston
-
Hey, could you guide into what you did to have XP working?
I am suspecting that the PCI1225 is part of the problem that has conflicts on my unit (no enough resources).
Thank you,
Gaston
I think the PCI1225 MAY be the PCMCIA controller. If so, that's not a problem. Check the vendor ID in the device manager - if it's TI then don't worry about it, your problem lies elsewhere.
-
Hi Jay, Recently happen to my unit CSA8000 which I can't enter to boot setup and keep on error show drive A & B drive error. For 1st time shall I run your corrupt.zip through floppy disk? Thanks in advance for your advise.
-
Hi Jay, Recently happen to my unit CSA8000 which I can't enter to boot setup and keep on error show drive A & B drive error. For 1st time shall I run your corrupt.zip through floppy disk? Thanks in advance for your advise.
Yes, that will allow you to get into the BIOS setup again. One of the most idiotic BIOS bugs I've ever seen...
You will need to connect a VGA monitor to the NLX motherboards VGA port, then set the default video from AGP to PCI in the BIOS.
-
Dear all,
I'm looking for restore CD's for a CSA8000. It was running under W98; but i'm afraid the original disk died. Because it was alreay a 2nd hand , i unfrtunately don't get them.
Is there any one able to make copy/image of those ?
I basically need the special OS CD. It seems the application is available on Tek site.
Thank you.
Vincent
-
Dear all,
I'm looking for restore CD's for a CSA8000. It was running under W98; but i'm afraid the original disk died. Because it was alreay a 2nd hand , i unfrtunately don't get them.
Is there any one able to make copy/image of those ?
I basically need the special OS CD. It seems the application is available on Tek site.
Thank you.
Vincent
Not sure if you still need this, but see attached for .torrent file.
Use https://www.qbittorrent.org/ (https://www.qbittorrent.org/) to download it!
-
Dear broken TDS8000 owners,
I have to say, I was reading the eevblog posts over years, and really here and there get very good advice or hints.
I have been repairing test equipment for mmm say more than 20 years now profesionally, but not for much profit, more for fun.
Since my main job is the design of radar and test equipment. But dont want to talk long here.
Here I want to give something back to the forum.
TDS8000 mostly suffer from flash corruption in the Xilinx 95xxx CPLDs. This is probably through the excessive heat on the motherboard in combination of time.
So errors look different on each scope, as bits may toggle in any of the 10 CPLDs. To find this out I sadly needed to buy 2 scopes
and read out CPLD flash contents. Since some of them have same content, i was able to reconstruct the original content.
On one PCB one CPLD was even dead.
Please find instructions attached. These files allowed me to successfully reapair two mainboards.
Please have fun and share.
-
Good morning,
I have just acquired a broken down TDS8200 and I would like to have some information concerning the operating system supplied with it as well as the possibility of obtaining a copy of it or even a disk image. The information on the web concerning this model being rare, I could not highlight if there was a correlation between this model (8200) and the models of the TDS/CSA 8000 series as well as iteration B. It seems to me that it is a special version of Windows 2000 which is installed. It also seems to me that this model (8200) must be a bit more recent than the 8000B models, well I think. In short, a lot of uncertainties and questions...
To read to you.
-
Good morning,
I have just acquired a broken down TDS8200 and I would like to have some information concerning the operating system supplied with it as well as the possibility of obtaining a copy of it or even a disk image.
I'm looking to buy a used unit myself and came across a link on ebay (below) where the seller is selling the restore package (and even options) based on the main board version you have.
https://www.ebay.com/itm/266268928704 (https://www.ebay.com/itm/266268928704)
May be worth a shot to ask.
-
THANKS,
The price is exorbitant though. Aimed more at professionals... :( :(
-
Hello i need help with original WIN98 or WIN2000 ISO image for 8000 series.
-
with free registration on xdev's you have a ghost image of an csa-8000 ---- 381 megs
-
Done, now CMOS Error 171... Any new info?
-
it would be nvram errors due to a dead battery, and you may have lost your cal constant of the ACQ board ...
a small thread
https://www.eevblog.com/forum/testgear/tds8000-dc-calibrator-adjustment-procedure-does-not-produce-expected-results/ (https://www.eevblog.com/forum/testgear/tds8000-dc-calibrator-adjustment-procedure-does-not-produce-expected-results/)
and sadly nothing on the TEK forums ...
-
Thank you again! I read this thread several mounts ago, there no any new info for a long time..