Author Topic: CSA8000 (Read 11123 times)

cncjerry · « **on:** July 24, 2019, 10:50:01 pm »

OK, I was talked into purchasing a CSA8000 for $150. Don't ask how, but it included delivery to my house.

It tries to boot to the network with a PXE error later. I saw about using corrupt.exe to get it to boot into setup but haven't had luck getting it to boot from diskette. Maybe my DOS is hosed, but it was good last time I used it. I wanted to get into setup to see if I can figure out the drive problem and then add a drive to the unit. I was emailing with Jay and he recommended a new thread.

Overall the unit looks near perfect. I can't get a display on the main screen, just on a secondary attached to the SVGA port on the back.

So to begin, what version of DOS has been used with these in the past? Can I boot from the front diskette or should I use a CD? I have an external diskette drive as well.

I have most OS versions including NT, Win2k, 98, XP, etc.

Thanks,

Jerry

coromonadalix · « **Reply #1 on:** July 24, 2019, 11:35:42 pm »

You can or could be able to remove the pxe network boot in the bios setup, with an attached keyboard you should be able to enter in it ...

You have plenty of manuals on google
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=2ahUKEwj4_t7C2s7jAhVDXqwKHarQDl4QFjAAegQIAxAB&url=http%3A%2F%2Fdownload.tek.com%2Fmanual%2F071174502.pdf&usg=AOvVaw1t6lqE0ByEQByZueSQP9Hq

https://www.artisantg.com/info/PDF__54656B74726F6E69785F435341383030305F544453383030305F4D616E75616C.pdf

They where dos 3.3 initially

you have a website https://www.bootdisk.com/bootdisk.htm
I think the dos 6.22 has cdrom drivers in it, create a disquette and try to boot from it once you had the chance to get in the bios and see if you can enable a floppy drive (if not already enabled ??) and change it to the first bootable device ??

and a thread here
https://www.eevblog.com/forum/repair/tektronix-csa-8000-tds-8000-repair-experiences/

cncjerry · « **Reply #2 on:** July 24, 2019, 11:40:08 pm »

The issue is I can't get into the BIOS setup. I have to boot a diskette and corrupt the date/time with an executable I was sent. This will force it to go into BIOS setup. From there I should be able to figure some things, mainly what's going on with the drive.

I don't know why it's not booting DOS off my diskette. I think the diskette is DOS 6.22, at least that's what it says.

coromonadalix · « **Reply #3 on:** July 24, 2019, 11:55:16 pm »

okay is there an jumper for a clear cmos (ie bios reset ??) maybe a board reset could help you ??

cncjerry · « **Reply #4 on:** July 25, 2019, 12:06:37 am »

I made a 6.22 DOS, booted it up, used the corrupt.exe to set the clock to invalid. I then checked some of the settings, yanked out the diskette and it rebooted. I have a working windows system. There is a splash screen right in the middle but nothing that looks like an oscilloscope. Apps run, etc. I see tekvisa is loaded.

So now what? is this a working scope? I think it is missing some drivers or something. But the hard drive boots fine. I did prompt for some missing drivers, so maybe if I reboot it again now I'll go further.

Not bad for $150! Ha, I still need a module. Anyone have a cheap electrical module?

Thanks for the pointers.

Jerry

cncjerry · « **Reply #5 on:** July 25, 2019, 12:35:34 am »

so now I have to start digging around. It looks like it is missing the instrument drivers maybe? The TDSCSA8000 app crashes at X:\janus\build\instrument\InstrumentDriver.cpp line 366.

I don't even see an X: drive so I have to go looking for it.

Hints?

Thanks,

Jerry

cncjerry · « **Reply #6 on:** July 25, 2019, 03:34:39 am »

I looked around and can't find the tek firmware for the windows 98 version that is on this system. I guess I can try to find the XP version? I have winxp here someplace...

Ideas? What's the best route to take? I don't want to put much into it until I find out if it works as a scope.

Thanks.

Jerry

cncjerry · « **Reply #7 on:** July 25, 2019, 04:11:16 am »

I found 1.5.2.2 and installed it. The tdscsa8000 scope code hangs after the splash screen and sits there. I must be missing something in the PowerPC section? Back to google.

Thanks for all the pointers so far.

Jerry

Johnny10 · « **Reply #8 on:** July 25, 2019, 05:04:50 am »

Jerry
I believe your issues are the same as Tin's 7404 project describes.

Your going to have to change the NVRAM's on the acquisition board and then replace all the data.

Read through this repair:
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/

Covers CSA 8000 also.

Jwalling · « **Reply #9 on:** July 25, 2019, 09:49:18 am »

Quote from: cncjerry on July 25, 2019, 03:34:39 am

I looked around and can't find the tek firmware for the windows 98 version that is on this system. I guess I can try to find the XP version? I have winxp here someplace...

Ideas? What's the best route to take? I don't want to put much into it until I find out if it works as a scope.

Thanks.

Jerry

As Johnny10 said, it's probably the battery on the PPC board located under the CPU board. But before you pull it to measure it:

1. Have you looked at the console port output yet? Can you post the output so we can see?
2. I have the Intel NLX O/S recovery .ISO which I can post somewhere. I also have a ghost image for serial prefix B01XXXX.
3. What is the serial # of the unit?
4. Check the Windows devices, and make sure all the devices have drivers installed and are not in an error state.

Jay

Jwalling · « **Reply #10 on:** July 25, 2019, 09:58:02 am »

Quote from: cncjerry on July 25, 2019, 12:35:34 am

The TDSCSA8000 app crashes at X:\janus\build\instrument\InstrumentDriver.cpp line 366.

Where is THAT coming from?

coromonadalix · « **Reply #11 on:** July 25, 2019, 10:22:31 am »

I think the op ovethink some issues, first its a computer, resolve one thing at the time, if the os boot, see in the hardware manager possible errors like missing drivers ...

If its based on win 98 at the moment, try to find the right csa software, dont try to upgrade right now.

For other hardware included who make this an csa8000, some member(s) here can help if you tell them infos they ask

Model or serial number, option(s) installed, photos, battery state in volts ....

Jwalling · « **Reply #12 on:** July 25, 2019, 11:10:49 am »

As I said, I have an O/S recovery .ISO file for the Intel NLX board as well as a Ghost image for serial prefix B01XXXX. I've been trying to upload them to http://global-files.net but it keeps stalling after a few hundred MB. You mentioned that you have an FTP server I could upload them to, can you give me the address?

Here's the console port output of a working scope showing the config. You can use it to program your NVRAM if the battery has died:

Code: [Select]

boot device          : sm
processor number     : 0 
host name            : host
file name            : c:\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:\dio_rtc.vsh
other (o)            : nvfs=0x1000

If your console port output already looks similar, don't change anything for now.

It would be helpful to you if you have a few disk drives to experiment with, so you don't have to lose any progress you (may) have already made. You might want to go back to a previous experiment...

Do note that the calibration NVRAM is backed up by battery as well. What a stupid thing Tek did, have they never heard of flash?

But, worry about that after you get the scope to run.

cncjerry · « **Reply #13 on:** July 25, 2019, 12:13:07 pm »

OK, thanks, lots of good info here.

First, let me explain. The computer side of this is running fine. The unit loaded lots of drivers when I first booted it after getting into setup. The touchscreen is working, etc. I'll look at the console port, have to figure that out, and post that up. Also, I've seen quite a few units that sit at that splash screen. Does it pass the tdscsa8000 splash screen if it has no modules in it? I guess what I am asking while I chase this other stuff down from above is, how far can I go with testing without a module in it? Should the scope code come up? I want to get to a point where the investment in a module is justified. If someone has a spare I could use while testing, I'll make it worth your while.

Thanks for all the help!

Jerry

Serial: is B010683

Device manager has no unknown devices and System Information shows there are no "Problem devices" in the list. In device manager I can see the Tek front panel as well as the GPIB adapter.

Jwalling · « **Reply #14 on:** July 25, 2019, 12:33:27 pm »

Quote from: cncjerry on July 25, 2019, 12:13:07 pm

OK, thanks, lots of good info here.

First, let me explain. The computer side of this is running fine. The unit loaded lots of drivers when I first booted it after getting into setup. The touchscreen is working, etc. I'll look at the console port, have to figure that out, and post that up. Also, I've seen quite a few units that sit at that splash screen. Does it pass the tdscsa8000 splash screen if it has no modules in it? I guess what I am asking while I chase this other stuff down from above is, how far can I go with testing without a module in it? Should the scope code come up? I want to get to a point where the investment in a module is justified. If someone has a spare I could use while testing, I'll make it worth your while.

Thanks for all the help!

Jerry

Let's just take this one step at a time.

If the battery on the PPC board is dead, then the NVRAM contents are lost and you'll need to replace the battery and use the info I posted above to reprogram it. The symptoms of dead battery is that it will hang at the splash screen.

You'll need a computer with a serial port set to 9600,n,8,1 and a terminal program (I use Token)
Connect the serial port to the console port using a null modem adapter. Start the terminal program, then power up the CSA8000. You should then see the output from the console port on the computer.
Post this output here.

EDIT: The console port is the 10 pin box header located on the PPC board under the Intel processor board. It is a right angle connector on the right side of the PCB when the scope is facing you. If you haven't already done so, make sure you have a good size fan blowing across the acquisition board to keep it cool.

cncjerry · « **Reply #15 on:** July 25, 2019, 12:48:31 pm »

Is the console port the standard serial port?

Jwalling · « **Reply #16 on:** July 25, 2019, 01:19:25 pm »

Quote from: cncjerry on July 25, 2019, 12:48:31 pm

Is the console port the standard serial port?

Yes, it is a standard RS-232 port. But not the rear serial port - you do know that, yes?

cncjerry · « **Reply #17 on:** July 25, 2019, 01:29:26 pm »

Yes, just got your messages on the port. I'll have to open it up and plug onto that port. Lot's of catching up to do.

Johnny10 · « **Reply #18 on:** July 26, 2019, 04:52:36 pm »

C'mon Jerry.
I know you haven't let this go.
You've been working on this in the wee hours.

cncjerry · « **Reply #19 on:** July 26, 2019, 05:36:40 pm »

been busy, had a 3:30am conf call yesterday, etc, etc.

Just got on the port. Nothing. I have a .A halt on the board. It reads a "DRAM walking 1", Maybe a DRAM issue? I think I see standard DRAM in there and I'm sure I have tons of it around.

Should I start there?

Thanks

Ice-Tea · « **Reply #20 on:** July 26, 2019, 05:47:01 pm »

And check the MoBo for leaking caps.

Does it have any modules? Without it, fairly useless...

cncjerry · « **Reply #21 on:** July 26, 2019, 05:51:49 pm »

The post code is on the PowerPC board and it halts at as I mentioned, ".A". Reading it more carefully, it reads that it passed "DRAM walking 1" and what failed is "NVRAM walking 1". So maybe this is the NVRAM battery? or is the NVRAM bad? I would lean towards the latter but I am going to check the battery.

It looks like an HVAC dream in there so I don't know if I'll be able to get the board out today or not. I have a day job, it sucks, but it pays the bills, or at least 90% of them.

Thanks for the help.

regards,

Jerry

edit: I started disassembly and need to run out for some bandaids. For how massive this thing is everything is crammed in there with lots of sharp edges.

Ice-Tea · « **Reply #22 on:** July 26, 2019, 06:26:21 pm »

Measure the NVRAM battery voltage. And read through the other thread. Will save you time.

cncjerry · « **Reply #23 on:** July 26, 2019, 06:37:52 pm »

NVRAM battery is dead and had reversed voltage. Left the battery off thinking, what the heck, maybe the reverse voltage screwed with it. No change, still a ".A".

I'm setup to change out the NVRAM. I would like confirmation if someone thinks this is the issue. Sort of pointing in that direction. I will change the battery and see if it makes a difference.

cncjerry · « **Reply #24 on:** July 26, 2019, 06:38:55 pm »

I read thru the other thread and in his case he was looping or halting later. I'll go back over it with a finer tooth comb.


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

Author Topic: CSA8000 (Read 11123 times)

Share me