CSA8000 - Page 1
Forum section: electronics / repair

author: cncjerry
author_rank: Unknown
timestamp: July 24, 2019, 10:50:01 pm
content: 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

author: coromonadalix
author_rank: Super Contributor
timestamp: July 24, 2019, 11:35:42 pm
content: 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 googlehttps://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=AOvVaw1t6lqE0ByEQByZueSQP9Hqhttps://www.artisantg.com/info/PDF__54656B74726F6E69785F435341383030305F544453383030305F4D616E75616C.pdfThey where dos 3.3 initiallyyou have a websitehttps://www.bootdisk.com/bootdisk.htmI 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 herehttps://www.eevblog.com/forum/repair/tektronix-csa-8000-tds-8000-repair-experiences/

author: cncjerry
author_rank: Unknown
timestamp: July 24, 2019, 11:40:08 pm
content: 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.

author: coromonadalix
author_rank: Super Contributor
timestamp: July 24, 2019, 11:55:16 pm
content: okay is there an jumper for a clear cmos (ie bios reset ??) maybe a board reset could help you ??

author: cncjerry
author_rank: Unknown
timestamp: July 25, 2019, 12:06:37 am
content: 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

author: cncjerry
author_rank: Unknown
timestamp: July 25, 2019, 12:35:34 am
content: 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

author: cncjerry
author_rank: Unknown
timestamp: July 25, 2019, 03:34:39 am
content: 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

author: cncjerry
author_rank: Unknown
timestamp: July 25, 2019, 04:11:16 am
content: 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

author: Johnny10
author_rank: Frequent Contributor
timestamp: July 25, 2019, 05:04:50 am
content: JerryI 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.

author: Jwalling
author_rank: Unknown
timestamp: July 25, 2019, 09:49:18 am
content: Quote from: cncjerry on July 25, 2019, 03:34:39 amAs 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

author: Jwalling
author_rank: Unknown
timestamp: July 25, 2019, 09:58:02 am
content: Quote from: cncjerry on July 25, 2019, 12:35:34 amWhere is THAT coming from?

author: coromonadalix
author_rank: Super Contributor
timestamp: July 25, 2019, 10:22:31 am
content: 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 askModel or serial number, option(s) installed, photos, battery state in volts ....

author: Jwalling
author_rank: Unknown
timestamp: July 25, 2019, 11:10:49 am
content: 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 tohttp://global-files.netbut 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:boot device : smprocessor number : 0host name : hostfile name : c:\vxworks.stinet on ethernet (e) : 192.168.0.2:ffffff00inet on backplane (b): 192.168.0.2:ffffff00host inet (h) : 192.168.0.1gateway inet (g) : 192.168.0.2user (u) : anonymousftp password (pw) : anonymousflags (f) : 0x1008target name (tn) : targetstartup script (s) : c:\dio_rtc.vshother (o) : nvfs=0x1000If 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.

author: cncjerry
author_rank: Unknown
timestamp: July 25, 2019, 12:13:07 pm
content: 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!JerrySerial: is B010683Device 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.

author: Jwalling
author_rank: Unknown
timestamp: July 25, 2019, 12:33:27 pm
content: Quote from: cncjerry on July 25, 2019, 12:13:07 pmLet'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.

author: cncjerry
author_rank: Unknown
timestamp: July 25, 2019, 12:48:31 pm
content: Is the console port the standard serial port?

author: Jwalling
author_rank: Unknown
timestamp: July 25, 2019, 01:19:25 pm
content: Quote from: cncjerry on July 25, 2019, 12:48:31 pmYes, it is a standard RS-232 port. But not the rear serial port - you do know that, yes?

author: cncjerry
author_rank: Unknown
timestamp: July 25, 2019, 01:29:26 pm
content: 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.

author: Johnny10
author_rank: Frequent Contributor
timestamp: July 26, 2019, 04:52:36 pm
content: C'mon Jerry.I know you haven't let this go.You've been working on this in the wee hours.

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 05:36:40 pm
content: 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

author: Ice-Tea
author_rank: Super Contributor
timestamp: July 26, 2019, 05:47:01 pm
content: And check the MoBo for leaking caps.Does it have any modules? Without it, fairly useless...

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 05:51:49 pm
content: 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,Jerryedit: 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.

author: Ice-Tea
author_rank: Super Contributor
timestamp: July 26, 2019, 06:26:21 pm
content: Measure the NVRAM battery voltage. And read through the other thread. Will save you time.

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 06:37:52 pm
content: 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.

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 06:38:55 pm
content: 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.

author: TheSteve
author_rank: Unknown
timestamp: July 26, 2019, 07:50:08 pm
content: The nvram itself seems to fail, so I'd plan to replace it and the battery.

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 08:27:00 pm
content: Steve, thanks, suspected this. I replaced the battery, same problem.Does it start logging before it finished post or after? I'll go back and look at others console logs in a minute to see if it is evident.I flipped some of the diagnostic switches near that alpha display and I guess I bypassed the one failing as I got an "L" but still no log. An "L" reads that it is waiting for the host. I then started the TDSCSA8000 code and it crashed with a MFC42D.dll page fault.I have USB logic analyzers I can put on the pints. I am using the correct port (for the log) but using a USB dongle and they are twitchy when they work. So I'm going scope it first and then if I have a TTL signal, I attach the logic analyzer until I get the ascii dongle working. I also have a breakout box someplace that will blink some lights.I'm starting to think the NVRAM problem is a good one as if that is the problem, it is relatively easy to fix.thoughts?Jerry

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 08:53:38 pm
content: I'm looking at the console port pinout in the other thread. I've probed all the pins, no output at all. I do see where others have console output for each of the diagnostic steps. So I'm wondering if I am looking at it correctly. TXD on the other thread is pins 3 and 6 with ground on 9. I should be seeing something, no?

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 09:20:00 pm
content: hey, we have a log:Code:UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: 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...Expected Value: 0x00000001Actuall Value: 0x00000081Location: 0xFD0E0000romPost: NV-MEMORY Walking-one test failed.So it looks like I have to replace the NVRAM?

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 09:49:38 pm
content: ok, I screwed around and got the console working. I programmed the boot parameters a couple of times and they took. I then had an error about c:\vkworks.st missing, found it and figured all that out. Now the VXworks loads and says it is time slicing etc.I still have the MFC42D.dll page fault. I have the win98 code and I'm going to reload it and see what happens.Seems like progress usually means you are going down the wrong path...Jerry

author: cncjerry
author_rank: Unknown
timestamp: July 26, 2019, 10:07:00 pm
content: I'm reinstalling the software I downloaded from Tek for Win98 version 1.5.2.2, I think to see if it clears up the dll error. I'll run disk check after. I remember wondering what the black handle did above the CDROM so I pulled it, of course, without thinking, who does? Hey, we pull or press everything, correct? I remember finding out it was the disk drive so maybe I corrupted it. I remember another MFC error right around then but reinstalling the code fixed it.I also noticed there are errors above the time-slice message that again look like NVRAM faults. Also, it cant find that one file, dio_rtc.vsh. Unlike the vxworks file, I don't see a copy anywhere on the system.I wish I could get this thing up before investing mucho dinero. I think I am getting close.

author: cncjerry
author_rank: Unknown
timestamp: July 27, 2019, 03:12:41 am
content: well, I screwed around enough. I'm going to order a new NVram for it. I can bypass the error but then I end up with a data access issue. I don't know if it is related, but it does mention NVRAM.At one point it said something about time slicing and I thought it was going to run but didn't. I added another 256MB of memory I had here. I am back to the flash screen hang, no msvc42d.dll page fault error. I wonder i the stock 128MB of memory is bad and was causing the page fault. I can debug that someday when I'm motivated.So Johnny, you won't hear from me until I get the new NVRAM ordered and installed. I'm surprised it does so much in the NVRAM. Is there firmware loaded in there? I entered the config information and that stuck after a few tries but am I missing another step here with the NVRAM? I'll go back and do some reading.Here's the log with the error on the bottom:Code:UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: 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...Expected Value: 0x00000001Actuall Value: 0x00000081Location: 0xFD0E0000romPost: NV-MEMORY Walking-one test failed.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.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.3.0Creation date: Jun 28 2000, 16:52:12Press any key to stop auto-boot...0auto-booting...boot device : smprocessor number : 0host name : hostfile name : c:\vxworks.stinet on ethernet (e) : 192.168.0.2:ffffff00inet on backplane (b): 192.168.0.2:ffffff00host inet (h) : 192.168.0.1gateway inet (g) : 192.168.0.2user (u) : anonftp password (pw) : anonflags (f) : 0x1008target name (tn) : targetstartup script (s) : c:\dio_rtc.vshother (o) : nvfs=0x1000Initializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching networkPC1 dio device driver installedinterface lo0... done.Attaching DIO client... done.Loading c:\vxworks.st...1771964Starting at 0x200000...Initializing backplane net with anchor at 0x1de0000... done.Backplane anchor at 0x1de0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching 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-1997CPU: 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=0data accessException current instruction address: 0x00223b60Machine Status Register: 0x0000b030Data Access Register: 0x140de581Condition Register: 0x80000042Data storage interrupt Register: 0x40000000Task: 0x1fffe08 "tRootTask"

author: Ice-Tea
author_rank: Super Contributor
timestamp: July 27, 2019, 07:57:23 am
content: It's on the board that glues the scope and windows part together. It basically tells the Tektronix board how to "find" the Windows environment, addresses, file locations and such.

author: Jwalling
author_rank: Unknown
timestamp: July 27, 2019, 09:36:52 am
content: Quote from: cncjerry on July 26, 2019, 05:51:49 pmCan you PLEASE post ALL the output from the console port?If it is saying "NVRAM walking 1" failed, then this is very likely the Dallas chip itself. I've seen this chip fail that way more than a few times...

author: cncjerry
author_rank: Unknown
timestamp: July 27, 2019, 09:09:53 pm
content: Would someone mind posting a complete log, from start to time-slice?I changed the nvfs=0x1000 parameter in the boot parameters to nvfs=0x2000 and it now runs all the way down to time slice. But I see an error at the top where it does a cd to "c:/progra~1/tdscsa~1/firmware" (sic) and right after it there's an error. It not easy for me to post the logs but I will try to edit this from the logging computer.I changed the nvfs=0x1000 parameter thinking that is the starting address for the nvram file system it creates and maybe there is a bad spot in the nvram. It does run quite a way further, almost looks like it is going to run as it gets down to the time-slicing message. Splash still hangs though without crashing.I looked on both Mouser and digikey and can't find the NVRAM chip. I see them on ebay but wanted a proper chip. I'll keep looking.thank again.Jerryhere's the log, the error is right after thermal control. Maybe the dio_rtc.vsh isn't unpacked? I had copied it from c:\program files\tdscsa8000\firmware directory.Code:]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997CPU: Tektronix HPP - PowerPC 740. Processor #0.Memory Size: 0x2000000. BSP version 1.0.3.5.WDB: Ready.usrNvFsInit: NAME=/nvram BASE=0xfd0ff000 BPB=512 BPT=8 NB=8 BO=0nvfs: STATUS: Mounting existing NVRAM file systemtcsTableUnpack: checksum failed on buffertcsTableLoadFromNVRAM: tcsTableUnpack failedKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:\dio_rtc.vsh ...dbFsIoctl: invalid code 3cd "c:/progra~1/tdscsa~1/firmware"value = 0 = 0x0*0xfec00000 = 0x04b00080;*0xfee00000 = 0x17009002ppp_parms + 0xfe84f680 = 0xfec00000: value = 78643328 = 0x4b00080ppp_parms + 0xfea4f680 = 0xfee00000: value = 385912834 = 0x17009002*0xfec00000 = 0x88a10080;*0xfee00000 = 0x01800000ppp_parms + 0xfe84f680 = 0xfec00000: value = -2002714496 = 0x88a10080 = ppp_parms + 0x8865f700ppp_parms + 0xfea4f680 = 0xfee00000: value = 25165824 = 0x1800000*0xfe008002 = 0;*0xfe00800e = 0;*0xfe008012 = 0ppp_parms + 0xfdc57682 = 0xfe008002: value = 0 = 0x0ppp_parms + 0xfdc5768e = 0xfe00800e: value = 0 = 0x0ppp_parms + 0xfdc57692 = 0xfe008012: value = 0 = 0x0symSyncTimeoutSet 600000value = 600000 = 0x927c0ld <hi32.ovalue = 31002048 = 0x1d90dc0 = Hi32SystemProcessorBoard + 0xa98Hi32SystemProcessorBoard = 1Hi32SystemProcessorBoard = 0x1d90328: value = 1 = 0x1CmdDspDevName = "/dev/cmddsp0"new symbol "CmdDspDevName" added to symbol table.CmdDspDevName = 0x1d90ce0: value = 31002496 = 0x1d90f80 = CmdDspDevName + 0x2a0hi32Drvvalue = 0 = 0x0hi32DevCreate CmdDspDevName,0x80006000,0xa0000000,3value = 0 = 0x0ld <cmddsp.ovalue = 31000352 = 0x1d90720 = Hi32SystemProcessorBoard + 0x3f8ld <acqdsp.ovalue = 31000832 = 0x1d90900 = Hi32SystemProcessorBoard + 0x5d8ld <diagcmddsp.ovalue = 31008224 = 0x1d925e0ld <diagModule_wmp.ovalue = 31007584 = 0x1d92360ld < systemLibraryCode.ovalue = 31007136 = 0x1d921a0CSSDefaultDioDisable=0CSSDefaultDioDisable = 0x1b20480: value = 0 = 0x0semInitForQueueCheckLogMsgvalue = 31001344 = 0x1d90b00 = Hi32SystemProcessorBoard + 0x7d8ld < nvSysLib.ovalue = 30999680 = 0x1d90480 = Hi32SystemProcessorBoard + 0x158ld < bucket.ovalue = 31004000 = 0x1d91560 = CmdDspDevName + 0x880MathMeasCreateMappingFcns = 1MathMeasCreateMappingFcns = 0x1aa60b8: value = 1 = 0x1TmgrExecuteAllMappingFunctionsEnable=1TmgrExecuteAllMappingFunctionsEnable = 0x1aa2694: value = 1 = 0x1ld < as.ovalue = 28451456 = 0x1b22280ld < ifcProxy.ovalue = 28450880 = 0x1b22040acqCheckForCmdDsp=1new symbol "acqCheckForCmdDsp" added to symbol table.acqCheckForCmdDsp = 0x1d90680: value = 1 = 0x1ld < rtlLibTarget.ovalue = 28340096 = 0x1b06f80ld < slotMgrLightLibTarget.ovalue = 28287200 = 0x1afa0e0sysExtMemAddToPool memSysPartId ,0x02000000 ,0x02000000value = 0 = 0x0MathMeasDisableParseExpr = 1new symbol "MathMeasDisableParseExpr" added to symbol table.MathMeasDisableParseExpr = 0x3fff400: value = 1 = 0x1use100Breakpoints=1use100Breakpoints = 0x14f6e34: value = 1 = 0x1pWfmMemPool=0pWfmMemPool = 0x1abf1f0: value = 0 = 0x0AcqLibFourChannelProto = 0new symbol "AcqLibFourChannelProto" added to symbol table.AcqLibFourChannelProto = 0x3fff3a0: value = 0 = 0x0AcqExecHardWireChannelSources = 0AcqExecHardWireChannelSources = 0x119ecfc: value = 0 = 0x0CalDiagPowerUpDiagsEnabled = 1CalDiagPowerUpDiagsEnabled = 0x128d1b4: value = 1 = 0x1CalDiagLogAtFirstDiag = 1CalDiagLogAtFirstDiag = 0x128d198: value = 1 = 0x1NvLogDebugTrace = 0x3NvLogDebugTrace = 0x1b0cbac: value = 3 = 0x3doTekprobeExec=1doTekprobeExec = 0x128cbc4: value = 1 = 0x1pDbDev = ramDevCreate(0, 512, 1024, 1024, 0)new symbol "pDbDev" added to symbol table.pDbDev = 0x3f7f2c0: value = 67105536 = 0x3fff300pDBfs = dosFsMkfs("/db", pDbDev)new symbol "pDBfs" added to symbol table.pDBfs = 0x3f7dca0: value = 66580960 = 0x3f7f1e0copy ("TDS666.DBF", "/db/TDS666.DBF")value = 0 = 0x0dbPath = "/db/"new symbol "dbPath" added to symbol table.dbPath = 0x3f7dba0: value = 66575392 = 0x3f7dc20 = dbPath + 0x80wfmMemInit 0value = 55827072 = 0x353da80jNVInitMgrs0x1d975c0 (tShell): value = ! Error Log Full - 00 entries != 0x0x1d975c0 (tShell0):! jNVInit: NV log erased - version change !0x1d975c0TmgrInit(dbPath) (tShell): ! Error Log Full - 0 entries !0x1d975c0 (tShell): ! Error Log Full - 0 entries !value = 0 = 0x0rtlInitvalue = 0 = 0x0MathMeasCreateTheMathandMeasurementLibrariesvalue = 50245024 = 0x2feada0initAcqMappervalue = 50216064 = 0x2fe3c80autosetMapInitvalue = 50215648 = 0x2fe3ae0mathMapperInitvalue = 0 = 0x0initUtilityMappervalue = 50209664 = 0x2fe2380initWfmXmtrMappervalue = 50205504 = 0x2fe1340commInit__Fvvalue = 0 = 0x0JanusProxyInitvalue = 50172512 = 0x2fd9260acqExecInitWfmHdrTemplatesvalue = 49967968 = 0x2fa7360autosetInit__Fvvalue = 0 = 0x0TmgrHookupvalue = 0 = 0x0rtlHookupvalue = 0 = 0x0hookupAcqMappervalue = 31028096 = 0x1d97380autosetMapHookupvalue = 31028112 = 0x1d97390MathMeasMapHookupvalue = 31027912 = 0x1d972c8hookupUtilityMappervalue = 31028088 = 0x1d97378hookupWfmXmtrMappervalue = 31028088 = 0x1d97378commHookup__Fvvalue = 0 = 0x0JanusProxyHookupvalue = 0 = 0x0autosetHookup__Fvvalue = 28226984 = 0x1aeb5a8 = waitForTransCompleteSem(sem_des*,int*)taskSpawn "startEmbedded", 50, 0x0008, 100000, startEmbeddedOperationvalue = 49814976 = 0x2f81dc0Done executing startup script c:\dio_rtc.vshKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!-> done0x2d3ed20 (aCalDiagExecutor): CCMgr: Recall ACQ cal constants failed!0x2d3ed20 (aCalDiagExecutor): --> Initializing to defaults!0x2d3ed20 (aCalDiagExecutor): CCMgr: Recall user ACQ comp data failed!0x2d3ed20 (aCalDiagExecutor): --> Initializing to defaults!0x2d3ed20 (aCalDiagExecutor): ! Error Log Full - 0 entries !

author: cncjerry
author_rank: Unknown
timestamp: July 28, 2019, 07:02:40 am
content: shouldn't the PC-side app be coming up at this point? Am I missing a driver or something? I still have the splash screen hang. I'll find the NVRAM someplace and report back.Jay, I have to figure out my FTP server so you can FTP the code to me. I haven't had it up in a while. I own 5 fixed IP addresses so I just have to setup a spare computer. I used to use my email server but I don't have the XP disks.Jerry

author: Jwalling
author_rank: Unknown
timestamp: July 28, 2019, 10:21:57 am
content: Here's the log from a working scope. Note that the battery on the acquisition board is dead so the cal constants were lost. It looks like yours is as well!EDIT: I thought you were getting data errors on the NVRAM? Your output is missing the early part of the test. Why?Code:UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: 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.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.3.0Creation date: Jun 28 2000, 16:52:12Press any key to stop auto-boot...1 0auto-booting...boot device : smprocessor number : 0host name : hostfile name : c:\vxworks.stinet on ethernet (e) : 192.168.0.2:ffffff00inet on backplane (b): 192.168.0.2:ffffff00host inet (h) : 192.168.0.1gateway inet (g) : 192.168.0.2user (u) : anonymousftp password (pw) : anonymousflags (f) : 0x1008target name (tn) : targetstartup script (s) : c:\dio_rtc.vshother (o) : nvfs=0x1000Initializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching network interface lo0... done.PC1 dio device driver installedAttaching DIO client... done.Loading c:\vxworks.st...1773480Starting at 0x200000...Initializing backplane net with anchor at 0x1de0000... done.Backplane anchor at 0x1de0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching network interface lo0... done.Adding 6003 symbols for standalone.]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997CPU: Tektronix HPP - PowerPC 740. Processor #0.Memory Size: 0x2000000. BSP version 1.0.3.1.WDB: Ready.usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0nvfs: STATUS: Mounting existing NVRAM file systemKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:\dio_rtc.vsh ...dbFsIoctl: invalid code 3cd "c:/progra~1/tdscsa~1/firmware"value = 0 = 0x0*0xfec00000 = 0x04b00080;*0xfee00000 = 0x17009002ppp_parms + 0xfe84f098 = 0xfec00000: value = 78643328 = 0x4b00080ppp_parms + 0xfea4f098 = 0xfee00000: value = 385912834 = 0x17009002*0xfec00000 = 0x88a10080;*0xfee00000 = 0x01800000ppp_parms + 0xfe84f098 = 0xfec00000: value = -2002714496 = 0x88a10080 = ppp_parms + 0x8865f118ppp_parms + 0xfea4f098 = 0xfee00000: value = 25165824 = 0x1800000*0xfe008002 = 0;*0xfe00800e = 0;*0xfe008012 = 0ppp_parms + 0xfdc5709a = 0xfe008002: value = 0 = 0x0ppp_parms + 0xfdc570a6 = 0xfe00800e: value = 0 = 0x0ppp_parms + 0xfdc570aa = 0xfe008012: value = 0 = 0x0symSyncTimeoutSet 600000value = 600000 = 0x927c0ld <hi32.ovalue = 30997472 = 0x1d8fbe0 = Hi32SystemProcessorBoard + 0x998Hi32SystemProcessorBoard = 1Hi32SystemProcessorBoard = 0x1d8f248: value = 1 = 0x1CmdDspDevName = "/dev/cmddsp0"new symbol "CmdDspDevName" added to symbol table.CmdDspDevName = 0x1d90f60: value = 31002496 = 0x1d90f80 = CmdDspDevName + 0x20hi32Drvvalue = 0 = 0x0hi32DevCreate CmdDspDevName,0x80006000,0xa0000000,3value = 0 = 0x0ld <cmddsp.ovalue = 31003904 = 0x1d91500 = CmdDspDevName + 0x5a0ld <acqdsp.ovalue = 30999168 = 0x1d90280ld <diagcmddsp.ovalue = 31000896 = 0x1d90940ld <diagModule_wmp.ovalue = 28504576 = 0x1b2f200ld < systemLibraryCode.ovalue = 28503936 = 0x1b2ef80CSSDefaultDioDisable=0CSSDefaultDioDisable = 0x1b0ff80: value = 0 = 0x0semInitForQueueCheckLogMsgvalue = 31005024 = 0x1d91960 = CmdDspDevName + 0xa00ld < nvSysLib.ovalue = 28424672 = 0x1b1b9e0ld < bucket.ovalue = 28425184 = 0x1b1bbe0MathMeasCreateMappingFcns = 1MathMeasCreateMappingFcns = 0x1a98158: value = 1 = 0x1TmgrExecuteAllMappingFunctionsEnable=1TmgrExecuteAllMappingFunctionsEnable = 0x1a9488c: value = 1 = 0x1ld < as.ovalue = 28330400 = 0x1b049a0ld < ifcProxy.ovalue = 29749728 = 0x1c5f1e0acqCheckForCmdDsp=1new symbol "acqCheckForCmdDsp" added to symbol table.acqCheckForCmdDsp = 0x1c5f600: value = 1 = 0x1ld < rtlLibTarget.ovalue = 29751840 = 0x1c5fa20 = acqCheckForCmdDsp + 0x420ld < slotMgrLightLibTarget.ovalue = 29640256 = 0x1c44640sysExtMemAddToPool memSysPartId ,0x02000000 ,0x02000000value = 0 = 0x0MathMeasDisableParseExpr = 1new symbol "MathMeasDisableParseExpr" added to symbol table.MathMeasDisableParseExpr = 0x3fff400: value = 1 = 0x1use100Breakpoints=1use100Breakpoints = 0x1550608: value = 1 = 0x1pWfmMemPool=0pWfmMemPool = 0x1aadb38: value = 0 = 0x0AcqLibFourChannelProto = 0new symbol "AcqLibFourChannelProto" added to symbol table.AcqLibFourChannelProto = 0x3fff3a0: value = 0 = 0x0AcqExecUseChannels=0xFFAcqExecUseChannels = 0x11f74d8: value = 255 = 0xffAcqExecHardWireChannelSources = 0AcqExecHardWireChannelSources = 0x11f74e4: value = 0 = 0x0CalDiagPowerUpDiagsEnabled = 1CalDiagPowerUpDiagsEnabled = 0x12e55f8: value = 1 = 0x1CalDiagLogAtFirstDiag = 1CalDiagLogAtFirstDiag = 0x12e55dc: value = 1 = 0x1NvLogDebugTrace = 0x3NvLogDebugTrace = 0x1b150b4: value = 3 = 0x3doTekprobeExec=1doTekprobeExec = 0x12e500c: value = 1 = 0x1pDbDev = ramDevCreate(0, 512, 1024, 1024, 0)new symbol "pDbDev" added to symbol table.pDbDev = 0x3f7f2c0: value = 67105536 = 0x3fff300pDBfs = dosFsMkfs("/db", pDbDev)new symbol "pDBfs" added to symbol table.pDBfs = 0x3f7dca0: value = 66580960 = 0x3f7f1e0copy ("TDS666.DBF", "/db/TDS666.DBF")value = 0 = 0x0dbPath = "/db/"new symbol "dbPath" added to symbol table.dbPath = 0x3f7dba0: value = 66575392 = 0x3f7dc20 = dbPath + 0x80wfmMemInit 0value = 58186432 = 0x377dac0jNVInitMgrsvalue = 0 = 0x0TmgrInit(dbPath)value = 0 = 0x0rtlInitvalue = 0 = 0x0MathMeasCreateTheMathandMeasurementLibrariesvalue = 52745280 = 0x324d440initAcqMappervalue = 52718336 = 0x3246b00autosetMapInitvalue = 52717920 = 0x3246960mathMapperInitvalue = 0 = 0x0initUtilityMappervalue = 52711232 = 0x3244f40initWfmXmtrMappervalue = 53121184 = 0x32a90a0commInit__Fvvalue = 0 = 0x0JanusProxyInitvalue = 52671488 = 0x323b400acqExecInitWfmHdrTemplatesvalue = 52477088 = 0x320bca0autosetInit__Fvvalue = 0 = 0x0TmgrHookupvalue = 0 = 0x0rtlHookupvalue = 0 = 0x0hookupAcqMappervalue = 31028096 = 0x1d97380autosetMapHookupvalue = 31028112 = 0x1d97390MathMeasMapHookupvalue = 31027920 = 0x1d972d0hookupUtilityMappervalue = 31028088 = 0x1d97378hookupWfmXmtrMappervalue = 31028088 = 0x1d97378commHookup__Fvvalue = 0 = 0x0JanusProxyHookupvalue = 0 = 0x0autosetHookup__Fvvalue = 29687368 = 0x1c4fe48 = waitForTransCompleteSem(sem_des*,int*)taskSpawn "startEmbedded", 50, 0x0008, 100000, startEmbeddedOperationvalue = 52319648 = 0x31e55a0Done executing startup script c:\dio_rtc.vshKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!-> done0x2edb420 (aCalDiagExecutor): CCMgr: Recall ACQ cal constants failed!0x2edb420 (aCalDiagExecutor): --> Initializing to defaults!0x2edb420 (aCalDiagExecutor): CCMgr: Recall user ACQ comp data failed!0x2edb420 (aCalDiagExecutor): --> Initializing to defaults!0x2edb420 (aCalDiagExecutor):  M: 4,0:21:17,23.00,## FIRST TEST ##0x2edb420 (aCalDiagExecutor):  P: 4,0:21:36,23.00,171,AcqCalInfo(2), AcqCalConst(2), AcqCompFactory(2), AcqCompUser(2)0x2edb420 (aCalDiagExecutor):  P: 4,0:21:47,23.00,736,CalStrbs ch7: ACT=18.22mV, EXP>400.00mVdonedonedoneconnectionTask: handshaking with peer...connectionTask: handshaking with peer - done.connectionTask: handshaking with peer...0x2edb420 (aCalDiagExecutor): CCMgr: Recall ACQ cal constants failed!0x2edb420 (aCalDiagExecutor): --> Initializing to defaults!0x2edb420 (aCalDiagExecutor): CCMgr: Recall user ACQ comp data failed!0x2edb420 (aCalDiagExecutor): --> Initializing to defaults!

author: Jwalling
author_rank: Unknown
timestamp: July 28, 2019, 10:47:57 am
content: Quote from: cncjerry on July 28, 2019, 07:02:40 amI was just able to upload the recover disc .ISO for the intel board. Let's see if this works:http://global-files.net/wsrpilEDIT: Looks good! I'll now do the Ghost image for serial prefix B01XXXX, specifically B010243. When it's done, I'll post that link as well.

author: Jwalling
author_rank: Unknown
timestamp: July 28, 2019, 11:44:41 am
content: Ghost image file.http://global-files.net/wj07aj

author: coromonadalix
author_rank: Super Contributor
timestamp: July 28, 2019, 12:50:20 pm
content: Quote from: Jwalling on July 28, 2019, 11:44:41 amPlease could you specify the Ghost version you used .... thks

author: Jwalling
author_rank: Unknown
timestamp: July 28, 2019, 01:11:32 pm
content: Quote from: coromonadalix on July 28, 2019, 12:50:20 pmUnfortunately, that was before I started recording the ghost versions. It's either Ghost03 (2003?) or Ghost 8.2. Any later version should work as well. I think the latest is 11.5.1 before it was discontinued. That's the version I now use for almost everything.

author: cncjerry
author_rank: Unknown
timestamp: July 28, 2019, 04:14:11 pm
content: Quote from: Jwalling on July 28, 2019, 10:21:57 amMy NVRAM is not passing the walking 1 test but it is holding the boot constants. I flipped the dip switches beside the LED and I guess one of them allows it to bypass the error.I didn't know about the acquisition board battery. I'll go looking for that as well.Thanks a ton for uploading the disks. I'll download them in a minute. I would love to get this to the point where I can see if the acquisition board is good.Jerry

author: Johnny10
author_rank: Frequent Contributor
timestamp: July 28, 2019, 04:22:52 pm
content: Were there different processor boards for the CSA8000 series as there are for the TDS 7000 series?i.e. BLX, NLX

author: Jwalling
author_rank: Unknown
timestamp: July 28, 2019, 04:42:35 pm
content: Quote from: Johnny10 on July 28, 2019, 04:22:52 pmApparently there were three. Intel Bali and Radisys. They were all NLX boards AFAIK. This is the folder I have on it. I screwed up somewhere and didn't get (or deleted) the second CD for Bali and Radisys.Having trouble again posting attachments. Ever since this new way of attaching stuff, I've had problems from time to time. Will try again in a few minutes.

author: cncjerry
author_rank: Unknown
timestamp: July 28, 2019, 05:00:38 pm
content: Jay, I tried downloading the files, the iso says it corrupted. I'll try to burn it and see what happens.

author: cncjerry
author_rank: Unknown
timestamp: July 28, 2019, 05:33:06 pm
content: Jay, I tried burning it and same issue. I'll try bringing it down again.

author: cncjerry
author_rank: Unknown
timestamp: July 28, 2019, 06:52:55 pm
content: Hey guys, I just sent Jay a note that I created an FTP site and he can upload the ISOs and ghosts there. I can't leave the site up that long as I had to disable my firewall. If anyone needs the iso in the future, please send me a PM.Jay, I sent the address as a PM. Don't forget binary mode, I know I always do.Thanks!Jerry

author: Jwalling
author_rank: Unknown
timestamp: July 29, 2019, 10:03:46 am
content: Quote from: cncjerry on July 28, 2019, 05:00:38 pmUploading now to your FTP. I opened the original .ISO here and extracted all the files with no problems or errors.EDIT: Both files uploaded OK. Can you check them?

author: Jwalling
author_rank: Unknown
timestamp: July 29, 2019, 10:45:38 am
content: Quote from: cncjerry on July 28, 2019, 04:14:11 pmYeah, but what else does that NVRAM hold? I believe it's a DS1245YP which is 128KB. I would replace it... I've seen at least 10 failures of the SMD version in the past (Dallas/Maxim SUCKS!)

author: cncjerry
author_rank: Unknown
timestamp: July 29, 2019, 03:04:03 pm
content: I can't figure this out. I double clicked on the ISO ( I have to find GHO software) and this one is corrupted according to this system as well.I'm going to bring it over to my mac now and try mounting it there.I should have tried this yesterday but I tried it on two other windows systems with the same failure.Any ideas? Thanks for about the 10th time for sticking with me.edit: just tried it on my mac, the ISO can't be recognized when I tried to mount it or burn it. What software are you using? I had a copy of isobuster a while back, I'll look for it.edit2: Isobuster read it, go figure. Sorry for the extra work!anybody else need this file before I take the FTP site down, please send a PM by EOD today, thanks.

author: Jwalling
author_rank: Unknown
timestamp: July 29, 2019, 04:04:14 pm
content: Quote from: cncjerry on July 29, 2019, 03:04:03 pmNo need really. I just pulled down the ISO from Global files, and it's fine.EDIT: I burned it as well, and it boots to "WRONG SYSTEM!"I guess it checks to see if the motherboard is correct. I don't have a TDS or CSA8000...

author: cncjerry
author_rank: Unknown
timestamp: July 29, 2019, 05:28:18 pm
content: what are you using to open the ISO? I tried ISObuster and it finds missing files but it opens it. I've tried windows10, mac, windows7, windows8, all report a problem for some reason... Winrar reports end of file problem...

author: cncjerry
author_rank: Unknown
timestamp: July 29, 2019, 05:58:10 pm
content: I copied what I could from the CD ISO onto a CD and then booted it. I tried to use the restore utility, PQER, and it can't open the image file for some reason. I noticed when I used ISO buster to find missing files on the ISO that it found something large but I see a file called image.PQI which is about the size of a restore file.I then tried pqer.exe /img=image.pqi and it is asking for an image file password. Any ideas?Thanks again and again...Jerry

author: Jwalling
author_rank: Unknown
timestamp: July 29, 2019, 05:58:48 pm
content: Quote from: cncjerry on July 29, 2019, 05:28:18 pmHow could ISObuster know if there are missing files?I used an old version of UltraISO to open and extract the files from the ISO I posted on Global files. No problems.https://www.ultraiso.com/To burn a CD, I used Nero (also an old version; 6.something or other) I used the "Burn .ISO to disk function"

author: Jwalling
author_rank: Unknown
timestamp: July 29, 2019, 06:02:30 pm
content: Quote from: cncjerry on July 29, 2019, 05:58:10 pmI wonder if the password is on a script / batch file built into the ISO somewhere? If so, you would never be asked for the password.

author: cncjerry
author_rank: Unknown
timestamp: July 29, 2019, 06:14:26 pm
content: I found a command that I tried:PQER /PWD=N16058 /IMG=IMAGE.PQIOn the other site, the /PWD=N 16058 was typed. note the space after the N but when I put the N and 16058 together, it started the restore is is 7% done.I have to run to a meeting, but this is promising... I wish I didn't have to work for a living...Jay - thanks for all the help. I still don't know what is wrong with that ISO...Jerryedit: still restoring, up to 23%, wish me luck guys, send your good thoughts to Sausalito...

author: Jwalling
author_rank: Unknown
timestamp: July 29, 2019, 06:40:21 pm
content: Quote from: cncjerry on July 29, 2019, 06:14:26 pmI don't think there's anything wrong with the posted .ISO There's something else in play here...You'll probably need to install the application software for Win98 when the imaging is done. Should be on Tek's site.You should really also replace that defective NVRAM since we don't know what else is stored there. Don't buy it on Ebay, buy from Digikey or Mouser or you're asking for trouble... It's an active part still in production. Just check the package - it could be PDIP or SMD.

author: cncjerry
author_rank: Unknown
timestamp: July 30, 2019, 02:55:03 am
content: still hung on splash but I had to run out for a meeting. I have a lot of things to go over since I was screwing with the NVRAM boot parameters prior to taking off.I looked on both Mouser and digikey and neither had the IC. Do you know if there is a later chip that works?I'll try that version of ISO you pointed at. ISO buster looks at the directories I guess to see what is missing/corrupted. No idea other than what it said. Isobuster has a "find missing files function." I did finally get it to restore without fail so the image file is good. No idea what's wrong with the ISO. Never had this problem but I've been working with PCs before they were announced having worked for IBM on "the little guy" our nickname for the IBM PC before it came out, and I've yet to see it all.I appreciate all you did. I'll dig into it to make sure the NVRAM is programmed right, etc.Jerry

author: cncjerry
author_rank: Unknown
timestamp: July 30, 2019, 06:07:43 am
content: I downloaded the ISO coded you used and was able to burn a CD for future use.I checked what I could and it is still hanging. The TDSCSA8000 code came installed with the restore. I'll look for the restore instructions to see if there is anything else I have to do. Unless I find something I am on hold until I get the new NVRAM. So you won't hear from me until I get it ordered and installed.I appreciate everything you did to help, Jay, and others that jumped in. I'll take another look at Mouser and digikey before ebay of course.

author: tinhead
author_rank: Super Contributor
timestamp: July 30, 2019, 08:38:58 am
content: i downloaded that iso, burned / converted, with both versions VMware is booting till first configuration of the Installation, so the iso is ok.

author: TurboTom
author_rank: Super Contributor
timestamp: July 30, 2019, 09:09:32 am
content: I had the opportunity to get one of these instruments (TDS8000) including a 80E01 50GHz sampling head for relatively little money maybe six weeks ago. It came equipped with the RadiSys 810 NLX board and the PPC board with the timekeeper NVRAM module (DS1646P). I received it from a research facility where it apparently hadn't seen much use, it appeared to be in almost pristine condition, even only tiny amounts of dust inside. I received it with a full set of documentation and all the recovery CDs. Even the original ESD straps were included... Yet, it appears to be a rather early model with windows 98 installed and the acquisition board with five of its inputs "bodged" with the tiny piggback boards (for whatever reason those were required...).Obviously, the instrument booted but got stuck at the splash screen, indicating a flat PPC NVRAM battery. So I went ahead and replaced the coin cell in the PowerCap clip-on module (the original was down to approx. 0.4V), installed an internal connection from the PPC console serial port to the second, unused com port header on the NLX board (so I can always use the PC section to access the PPC console -- much more comfortable than having to open the instrument and plugging in an external computer). After proper configuration of the boot descriptor, the scope app started and I was able to get at least some functionality.I replaced the PowerCap coin cell of the acquisition board NVRAM while the instument was powered up since there might have been a faint chance that the original battery was still holding up and some useful data was still present there, only to find out that the original battery was down to plain zero! Several calibration attempts didn't turn out permanently successful, and I checked the ACQ NVRAM battery maybe two weeks later to find it's been drained to about 2.5V, indicating that the current consumption of the NVRAM is way too high.I'm about to experiment with an FRAM replacement for the NVRAM (similar to@TxB's approach) since the original components appear to be more than flakey and are unreasonably expensive.Just recently, the instrument failed again to boot into the scope application, indicating that the PPC NVRAM battery went flat again, which means that this module is probably also at fault. Did anybody try to replace the timekeeper NVRAM module with a plain NVRAM or FRAM assembly? Does the PPC board on the TDS/CSA8000 series require a RTC on the PPC board? I'ld very much prefer to install an FRAM work-around on this board as well than having to mess with the batteries again.Funny enough, the original coin cell on the NLX board still was at two point someting volts and kept both CMOS contents and time just fine... Crappy Dalles / Maxim rubbish!I've got one more thing that worries me, having read several reports of individuals with severe problems getting their 8000's to run again without any trouble after swapping batteries: First of all, did anyone succeed to get a TDS/CSA 8000 running without any errors reported, after having replaced the acquisition board NVRAM battery? To me it seems, all the errors that get reported upon startup of the scope application result from invalid information in the NVRAM after it had lost power. The problem with SRAM is that when power is applied, its contents is unpredictable (I remember to have read a paper that stated that this contents can even be used as some kind of "Fingerprint" to identify a certain hardware / chip since due to the microscopic differences during manufacturing, there aren't two SRAM chips that contain the same pattern at power-up, of course still superimposed with random noise, which can be used as a seed to generate "real" random numbers...). And I'm not sure if the "calibration" specified in the service manual is really all that's required to get the instrument set up properly again, or if there's another, more in-depth calibration procedure that's only known to Tek engineers "internally".Any and all additional information on this would be highly appreciated.Thanks,Thomas

author: Jwalling
author_rank: Unknown
timestamp: July 30, 2019, 09:49:51 am
content: Quote from: cncjerry on July 30, 2019, 02:55:03 amIsn't it a DS1245YP variant?https://www.digikey.com/product-detail/en/maxim-integrated/DS1245YP-70IND/DS1245YP-70IND-ND/1196841@TurboTom Yes, another failure mode of these POS chips is high current consumption. I've posted about that before on the forum, as did TiN who had the same problem with his TDS or CSA7404.

author: Jwalling
author_rank: Unknown
timestamp: July 30, 2019, 09:55:45 am
content: Quote from: TurboTom on July 30, 2019, 09:09:32 amI did manage to calibrate one of these after replacing the NVRAM on the ACQ board. I had some help from Cap on the Tek forum:https://forum.tek.com/viewtopic.php?f=568&t=138009&hilit=TDS8000

author: cncjerry
author_rank: Unknown
timestamp: July 30, 2019, 11:12:24 pm
content: Well, you aren't going to believe this... I played with the switches next to the 7-segment LED. One of them bypasses the test failure(s). I switched them until I found just that one. Others must do something to prevent the scoe code from starting and I had them switched on (or off). I then walked over to my external monitor not really paying attention and when I looked up, lo and behold, I had a display! I can't believe I missed it loading after all the times I watched it. 20? 30 times?Anyway, I have errors. Acquisition 1 is NVRAM and I would expect that error. Acquisition 2 is Cal strobes/TI; 3 is also cal strobes/TI; and 7 is the same.So, what does this mean? Calibration? I'll be reading-up on the errors but wanted to get this out there and start collecting opinions.Thanks - making progress, good ? bad?Jerry

author: TurboTom
author_rank: Super Contributor
timestamp: July 30, 2019, 11:36:38 pm
content: I guess this is completely normal if the NVRAM on the acquisition board had been without power. Upon powering up, it's contents is random and hence configures the channels arbitrarily, causing these errors. I've seen them as well on mine and sometimes they even change from power-up to power-up. Though I experimented with the NVRAM battery clip and even replaced the SRAM on the NVRAM module due to too high power consumption, I haven't been able to get rid of all the errors by performing the calibration as described in the service manual and the hints provided in the TEK forum. Since I haven't got a new replacement NVRAM module, my next approach to solve the problem will be trying out an FRAM module once the adapter PCBs arrive. I'm already quite curious if this will be more successful than my previous attempts...

author: cncjerry
author_rank: Unknown
timestamp: July 31, 2019, 12:05:30 am
content: I guess the question is more along the lines of, "is this going to be a useful scope given the errors displayed?"I would have to invest in a module or two and they aren't cheap as we know, which I would do. Also, are these Acquisition subsystems equivalent to each of the slots/channels? I guess I'm asking if I have 5 out of 8 subsystems that are reporting good?Is there an NVRAM on the Acq board that I should replace along the way?Thanks,Jerryps: was beginning to think I would never get this far!

author: TurboTom
author_rank: Super Contributor
timestamp: July 31, 2019, 08:18:28 am
content: Jerry,yes there is an NVRAM on the acquisition board (upper left corner in the attached photo) and in my opinion, that's the one that's the most troublesome to get right by far...The price for the sampling modules is really prohibitive, especially when compared to older equipment. But once in a while good deals are possible, especially for optical modules. I've got an 80E01 that came with the scope and an 80C01-CR that I got for little more than 200 EUR. I'ld love to find a TDR sampling head since this permits a completely new class of measurements but I wasn't lucky so far. There's a lot of damaged stuff floating around and looking at the damage thresholds of the electrical inputs, I guess in all of them the sampling hybrids are shot. I'm not sure in how far TEK used the same hybrids in the modules for the older 11800 / CSA800 series which can be found for considerably less so a purchase of a damaged 80e04 and a good SD-24 as a donor to swap the hybrid may make sense. If such a "hybid" would be anywhere close to calibration or can be properly calibrated at all with available means is a different question.Usage of a sampling scope to look at "wiggly lines" is more troublesome and limited than a conventional scope since you've always got to supply a low-jitter trigger to the instrument, either somehow extracted from the signal itself or from an internal reference clock of the DUT. When testing digital circuitry, the latter shouldn't be much of a problem but probing analog systems may get difficult (though that's not the application that an SO is really meant for).TBH, I currently consider my TDS8000 rather a "toy" to satisfy my TEA than a really useful instrument (to me). But anyway, I like the challenge to get it up and running 100% again, improve it (updated NLX CPU, memory and hard disk already and installed XP and the latest Scope App -- which by the way turned out less troublesome than I expected).And being able to qualify/quantify signals in the low tens of picoseconds range is quite impressive, see second photo. If under these conditions it's reasonable to spend lots of money on good sampling modules is another question that every individual may have a different answer to.Cheers,Thomas

author: Jwalling
author_rank: Unknown
timestamp: July 31, 2019, 10:41:04 am
content: Quote from: cncjerry on July 30, 2019, 11:12:24 pmRun every test you can and post theentirecontent of the console port again from power on, there may be additional information there now.Not sure if running SPC is possible without a module, but if it is, run that as well.

author: cncjerry
author_rank: Unknown
timestamp: July 31, 2019, 06:30:47 pm
content: I ordered new NVRAM and a PowerCAP top for the heck of it. The battery I changed was oK but why worry?I played with the triggering and it triggers so that is somewhat interesting. Front panel buttons are working, etc.If someone in the bay area has an electrical module I could use for testing, please send me a PM. I'll make it up to you the next time you need some CNC work done.I wish the modules from the 11801 worked. I had one of those here until a few weeks ago. I got the 11801 for $100 and got it working but the module had one channel that wasn't up to spec and the scopes internal calibrator was shot so I sold it for the same price.Thanks, I report back when the NVRAM is installed on Monday.Jerry

author: cncjerry
author_rank: Unknown
timestamp: August 01, 2019, 03:58:28 pm
content: the NVRAM errors in the scope diagnostics, are they pointing to the PowerPC NVRAM or the acquisition board NVRAM?

author: Jwalling
author_rank: Unknown
timestamp: August 01, 2019, 04:17:34 pm
content: Quote from: cncjerry on August 01, 2019, 03:58:28 pmPPC.

author: TurboTom
author_rank: Super Contributor
timestamp: August 01, 2019, 09:16:22 pm
content: Quote from: Jwalling on August 01, 2019, 04:17:34 pmAre you sure of that? I always thought the calibration for the ACQ board would be stored in the NVRAM on the ACQ board so it would be possible to swap a calibrated board from one machine to another (or from shelf to an arbitrary CSA / TDS 8000) without having to recalibrate. I guess it basically depends on where the reference oscillator is located if it makes sense to store all the CAL parameters on the PPC NVRAM. At least the calibration source is located on the ACQ board.It's a real shame that TEK only provides such a superficial service manual for this instrument. Gone are the times of component-level information and detailed circuit descriptions...I must be getting oldor as a collegue of mine once told -- when you finally need reading glasses, then you know that you're adult...Cheers,Thomas

author: Jwalling
author_rank: Unknown
timestamp: August 02, 2019, 11:55:56 am
content: Yes, calibration is stored on the ACQ board NVRAM. I thought he was talking about the NVRAM errors in the console output...

author: cncjerry
author_rank: Unknown
timestamp: August 02, 2019, 02:55:46 pm
content: Well, my calibration nvram is posting errors so I guess I should replace that one as well while I am in here.

author: cncjerry
author_rank: Unknown
timestamp: August 05, 2019, 03:53:20 am
content: My PPC side NVram is here. How do you recommend soldering it on? Heat? Iron? I'm worried about the pins on the ram popping off. They are only sort of sprung on and soldered. Heating the pins will loosen them on the chip.Thanks.

author: TurboTom
author_rank: Super Contributor
timestamp: August 05, 2019, 08:00:53 am
content: Hot air of an SMD rework station worked a treat for me. Do one side after the other. The two sides are far enough apart to be able to lift the heated side completely off the board without affecting the "cold" side. The small metal contacts stay on the NVRAM PCB, no need to worry. And since it's leaded solder that's been used on the machine, tempreatures don't need to be excessive. Heat transfer via the metal contacts is also very good.P.S: soldering on worked the same way in reverse for me. I only applied some flux since I didn't clean off the old solder. Just used an iron to "stick" two edge pins of the NVRAM to the pads and then hot air was used while applying some gentle pressure on top of the NVRAM. If I cleaned the board, I would have used SMD solder paste/hot air.

author: Jwalling
author_rank: Unknown
timestamp: August 05, 2019, 11:12:11 am
content: Quote from: cncjerry on August 05, 2019, 03:53:20 amI use a soldering Iron. For these particular chips, I modified a small pointed tip by putting a bend in it.

author: cncjerry
author_rank: Unknown
timestamp: August 06, 2019, 03:03:22 pm
content: I left some solder on the pads on the board. they look good. I'm thinking hot air with some shielding around it as I have a tremor related to early Parkinsons. I guess my soldering days are approaching the end. I wish there was an easy way to test these things because I would hate to put it in and have a problem with it.I need to get the one off the Acq board and replace it as well.I've been trying to negotiate on modules/heads without luck. After all this I might have a lame duck. I'm assuming these heads are worse than those in the 11801 where you would need a wire bonder and electron microscope to repair.Thanks, wish me luck with the soldering.Jerry

author: Jwalling
author_rank: Unknown
timestamp: August 06, 2019, 04:08:20 pm
content: Quote from: cncjerry on August 06, 2019, 03:03:22 pmIf you bought them from areputablesource, I wouldn't worry about that.Might not be a bad idea to hold off on the ACQ board one for now, and see what happens first with the PPC NVRAM...Good luck!

author: cncjerry
author_rank: Unknown
timestamp: August 06, 2019, 05:12:20 pm
content: well, I tried to solder it down using the bent tip as you had. I checked it with a small light. I used a good and tested cap. I then powered it up and it ran the NVram walking 1 test successfully a number of times. I then programmed it, checked it, etc and then I noticed that it wasn't running the walking 1 test and hanging on the ".A", and it had dumped the programming. I checked the cap, all is ok with the voltage. I have to pull the board out and go back over the solder connections. It's pretty tough to solder with my tremor, but I'll get there. The thing I can't figure is that if I was able to program it, and then I printed out the programming which would include a write to the chip and a read back, I wonder why the cap didn't hold the programming? So maybe the cap isn't on right? I checked the voltage and it is at 3.4V.To be clear, if I can program it and read it back, shouldn't the cap hold it, assuming it is on correctly?I'll keep screwing with it.Thanks for the encouragement.Jerry

author: cncjerry
author_rank: Unknown
timestamp: August 06, 2019, 06:41:41 pm
content: I can't get it to hold the boot parameters. The cap is good, I checked the soldering three times. Where the old NVRAM would at least hold the parameters and fail on the NVRam walking 1 test, this won't hold them at all. I can change them and print them right after, but when I reboot it (even without shutting it down) they are gone. I went over all the pins checking the pad to pin continuity and they all test ok. No shorts that I can see.When I first tested it, the NVRAM walking 1 test ran several times in a loop as expected without having the boot parameters. I then entered the parameters and when it rebooted, all looked well and then it started failing the Waling 1 test again with the ".A". I guess the Nvram could be bad now, maybe a loose solder joint in the beginning caused it? I plan to replace the cap for the heck of it. The next thing to do would be to replace the NVram again?What a pisser.Jerry

author: cncjerry
author_rank: Unknown
timestamp: August 06, 2019, 06:54:53 pm
content: new cap, no difference.So I can write the boot params using 'C', read them back using the 'P' command but booting brings up garbage. I wonder if the 'P' command is reading the NVram or just printing out the current boot params?I don't know, maybe I'm at the point of giving up on this one. Soldering in another NVRAM with my tremor is a lot of work and to get it this clean (the soldering that is) is very stressful. I don't know if I could do it again or not.The fact that it ran the NVRAM walking 1 test about 5 or so times leads me to believe the NVRAM failed somewhere along there.Thoughts?Jerry

author: cncjerry
author_rank: Unknown
timestamp: August 06, 2019, 10:47:26 pm
content: well, I went back over the NVRAM as I had one connection that might have been loose and after soldering itfor about that 10th time, now the NVRAM passes all tests. That's the good news. I can get past the walking 1 test, etc.Vxworks boots though, and throws a data exception error. Hadn't seen this before. With the bad NVRAM I was able to get into the scope application, TDSCSA8000 with one of the switches on the PPC board thrown to bypass the errors.So this is new to me but I thought I saw this a while back? I'll post the log as an edit from the other computer.I reseated the memory on the PPC and I'm running a disk scan on the 'C' drive. From there I will reload the code and see if it make a dif.So a little more progress. I'm almost back to last week. I'm starting to think I should have left the old NVRAM in there but now that I have it working...Code:UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: 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.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.3.0Creation date: Jun 28 2000, 16:52:12Press any key to stop auto-boot...0auto-booting...boot device : smprocessor number : 0host name : hostfile name : c:\progra~1\tdscsa~1\firmware\vxworks.stinet on ethernet (e) : 192.168.0.2:ffffff00inet on backplane (b): 192.168.0.2:ffffff00host inet (h) : 192.168.0.1gateway inet (g) : 192.168.0.2user (u) : anonymousftp password (pw) : anonymousflags (f) : 0x1008target name (tn) : targetstartup script (s) : c:\progra~1\tdsca~1\firmware\dio_rtc.vshother (o) : nvfs=0x1000Initializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching networkPC1 dio device driver installedinterface lo0... done.Attaching DIO client... done.Loading c:\progra~1\tdscsa~1\firmware\vxworks.st...1773480Starting at 0x200000...Initializing backplane net with anchor at 0x1de0000... done.Backplane anchor at 0x1de0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching network interface lo0... done.Adding 6003 symbols for standalone.]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997CPU: Tektronix HPP - PowerPC 740. Processor #0.Memory Size: 0x2000000. BSP version 1.0.3.1.WDB: Ready.usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0data accessException current instruction address: 0x00223908Machine Status Register: 0x0000b030Data Access Register: 0x022a92f8Condition Register: 0x24000042Data storage interrupt Register: 0x40000000Task: 0x1fffe08 "tRootTask"edit: I see an error in the boot file: c:\progra~1\tdsca~1\firmware\dio_rtc.vshshould be: c:\progra~1\tdscsa~1\firmware\dio_rtc.vshI'm going to fix it and try again.edit2:same error as above, data accessJerry

author: cncjerry
author_rank: Unknown
timestamp: August 07, 2019, 04:40:45 am
content: Luckily, I did have this error before and I posted it up. I noticed the BSP code on this listing is like 1.0.3.1 and previously it was 1.0.3.5 so it must be a code version problem I'll explore.

author: Jwalling
author_rank: Unknown
timestamp: August 07, 2019, 10:00:39 am
content: Are you sure that file exists in that location?: file name : c:\progra~1\tdscsa~1\firmware\vxworks.stOn the scope I worked on:file name : c:\vxworks.stIf you have any doubts about the PPC memory, you can take out the DIMM and install it on the motherboard for testing. Make a boot floppy of Memtest86+ and run it on the scope.

author: cncjerry
author_rank: Unknown
timestamp: August 07, 2019, 03:36:48 pm
content: Jay, yes, that's the correct address. I got it back up.That error right after:QuoteI had that before and I changed NVFS=0x1000 to NVFS=0x2000 at the bottom of the boot params thinking that the 0x1000 was an address and it had something to do with bad NVRAM in that spot. I changed it this time again and it passed and brought up the interface. I have more ACQ errors than I had before but I think it has to do with the NVRAM on the ACQ board.So now that I'm back where I was (but with a functional NVRAM on the PPC board) I am going to order the NVRAM for the ACQ board and replace it with my vibrating hands.By the way, I have more errors on the diagnostics than I had previously. With a bad NVRAM on the ACQ board this might be related.thanks - onward and upward!Jerry

author: cncjerry
author_rank: Unknown
timestamp: August 07, 2019, 03:47:10 pm
content: Jay, is there a way to load a waveform into the interface to play around? Can you send me one or post it up here?Thanks<- by the way, one of my person favs, right up there with

author: Jwalling
author_rank: Unknown
timestamp: August 07, 2019, 05:11:55 pm
content: Quote from: cncjerry on August 07, 2019, 03:47:10 pmI honestly don't know. I haven't messed around with those scopes much...

author: Jwalling
author_rank: Unknown
timestamp: August 07, 2019, 05:16:47 pm
content: Quote from: cncjerry on August 07, 2019, 03:36:48 pmIt would be quite a coincidence that you have *two* bad in one instrument. I know they suck, but two!?

author: cncjerry
author_rank: Unknown
timestamp: August 07, 2019, 05:33:45 pm
content: well, I can't run calibration without a module and maybe the calibration will fix some of these strobe errors. So I guess I'm going to order the 2nd NVRAM, button it up and wait until I acquire a sampling head.If someone can just save off a waveform into wfm format from a CSA8000 or compatible, I'd like to have it to check the interface on the scope. I tried it from my TDS784A and the format wasn't correct.a bigThank youto all that helped.Jerry

author: Perpf
author_rank: Newbie
timestamp: November 08, 2019, 04:26:59 pm
content: Hello!Thanks for sharing your experience!I#m just stuck with a CSA8000 myself: It shows "P" on the PPC-board but the scope app wont start. The console log shows that it gets to the point where the Kernel runs at 10 ticks per second. However, the app never boots.Do you maybe have an idea where to look for the problem?thanks & all the best, Nils

author: Perpf
author_rank: Newbie
timestamp: November 09, 2019, 05:23:42 pm
content: Hi again!On my Win2K install I'm now running FW 2.5.0.7. However, now the system is complaining that NIdMngr.dll is missing. Could anyone check on his 2.5.0.7 install where this file is?Also I'm still confused about my console dump when comparing it to one posted earlier here: When it's running at 10 ticks... it reads something like "Running simulated acquisition"What could be going on here??Greatly appreciate any ideas!!!

author: bohrzqc
author_rank: Newbie
timestamp: August 26, 2022, 01:50:24 pm
content: Hello, PerpfHave you solved this problem? I've got the same problem with you.I replaced the ACQ board from another CSA8000 scope, then the problem occurs.Quote from: Perpf on November 09, 2019, 05:23:42 pm