EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: TiN on September 15, 2013, 05:59:51 pm
-
This thread is dedicated to Tektronix TDS7000 platform based scopes (TDS7054,TDS7104,TDS7154,TDS7254,TDS7404,CSA7054,CSA7154,CSA7404)
Some information can be useful for newer TDS7000B platform as well, as they are based on similar modules.
Recently I acquired Tektronix CSA7404 scope, bought as dead for parts, at nice price. Unit come in pretty bad physical shape :-BROKE:
(http://dev.xdevs.com/attachments/download/607/IMAG0170.jpg)
All plastic exterior parts except front panel were missing. Outside aluminum shielding/case covers were bent on corners, looked that scope was dropped on angle.
(http://dev.xdevs.com/attachments/download/608/IMAG0172.jpg)
Despite of damages and poor look - it still was able to power on and booting Windows 98 OS. Hard drive had bad SMART status and was making clicking noise, so obviously it's going to be replaced with new HDD as one of first steps of scope restoration.
(http://dev.xdevs.com/attachments/download/609/IMAG0175.jpg)
While machine was able to boot OS without problems, main scope application, TekScope was unable to start. It was just showing welcome splash screen and hanging there. Downloading fresh copy of TekScope 2.5.3 Firmware for CSA7000/TDS7000 from Tektronix site (http://www.tek.com/oscilloscope/tds7254-software/csa7000-and-tds7000-series-firmware-upgrade) and reinstalling application did not help either.
Before we dig in, let's take a look on high-level block diagram of Tektronix CSA7404 from service manual (http://dev.xdevs.com/attachments/download/633/071701102%20CSA7000%20TDS7000%20Service%20manual%20.pdf) :
(http://dev.xdevs.com/attachments/download/605/csa7404_diagram.png)
There are four main modules/boards in scope.
x86 PC system (NLX motherboard, Socket 370 Celeron 850/128/100 Coppermine CPU, i810 chipset, onboard VGA, network, USB, SDRAM PC133 x 2 slots (only one used with 256MB DIMM) (http://dev.xdevs.com/attachments/download/613/_XPC8517.jpg)
PowerPC system (Tektronix custom board with interface to NLX and ACQ board (had installed 256MB DIMM on it)) (http://dev.xdevs.com/attachments/download/612/_XPC8515.jpg)
Acquisition board (ACQ, front-end to scope channels, custom Tektronix high-speed ASICs with dedicated RAM and interface to PowerPC board) (http://dev.xdevs.com/attachments/download/611/_XPC8568.jpg)
Main power supply board (cross compatible, at least with tested CSA7404 and TDS7704B) (http://dev.xdevs.com/attachments/download/625/PSU.jpg)
I also had access to working Tektronix TDS7704B, which come handy to check some parts and do board-level testing. Obviously both these scopes use common architecture, and share same power supply board and similar (but not interchangeable) PowerPC/x86 combo. As first measure of any electronic device troubleshooting - check power. Swap whole power supply module from TDS7704B to CSA7404 showed no functional issues or differences, which tells me that power supply to other boards from mains PSU is OK.
Initial testing and debug
First step will be visual inspection of all internals of scope to see, if any components or boards are physically damaged or missing :-/O.
(http://dev.xdevs.com/attachments/download/610/csa7404_acqh.jpg)
On acquisition board there was missing heatsink on one of big National Semi custom ASICs for channel 3. New heatsink was bought are placed on chip, hoping that it's BGA connection to board is intact.
On x86 board there was leaky output electrolytic capacitor in CPU DC-DC convertor. It was replaced to new one, which is common operation for servicing old computer motherboards already for a while. As a side note, considering cost of such scopes even today it's quite unpleasant to see low-end CapXon capacitors being used.
As was already stated earlier - there were no power supply board problems, as all voltages were present, and no visual damages were observed either. Swapping PSU from another scope did not make scope progress on loading app any further.
Interconnect boards (P200 between PPC board and ACQ, power delivery interconnect boards) were fine too, replacing them to same from TDS7704B did not change anything. So problem lied either in acquisition board, or PowerPC board or interfacing between NLX and PPC boards or PPC/ACQ. Interesting fact, that removing interconnect board P200 from PPC to ACQ on TDS7704B did exactly same - TekScope app stopped working and hung on welcome splash screen. This gives us information, that TekScope app needs to communicate successfully with PPC and ACQ boards to be able to start.
After some checks of x86 side of scope and trying to run few HDDs with Windows 2000 no obvious problems was found. CD-ROM drive was changed to DVD-RW from old laptop. Connection was standard notebook PATA. Original IBM Travelstar DARA-206000 6GB 4200RPM disk was changed to fresh IBM Travelstar IC25N020ATDA04-0 20GB drive. New Windows 2000 SP4 Professional was installed as maximum supported OS on this series scopes. Given current Celeron 850MHz CPU and 256MB this setup should run smoothly for beginning.
Moving our focus to PowerPC board as main suspect. This module There is handy debug 7-segment single digit debug LED, which according to service manual have next codes:
(http://dev.xdevs.com/attachments/download/604/csa7404_diag.png)
This LED is located on PPC board near riser connector and easily visible even when outer aluminum shell is installed.
(http://dev.xdevs.com/attachments/download/616/80port.jpg)
Our board during power up and after was rolling from ".8" code to "L", stays there for couple seconds, and then restarting from start again, and doing this infinitely in loops. On working TDS7704B post code LED was going from ".8" to "L", then when OS started goes to "P" and finally to flashing "-", staying there when TekScope application running. Looks like PowerPC board unable to finish it's booting sequence.
NVRAM Failure (Scope boots, OS boots, but TekScope application hangs on welcome splash screens, front panel not responding
Due to age of these machines and usage of battery-backed NVRAM (Dallas DS1245) it's not rare that onboard 3V battery (similar to ones used in usual computers for CMOS data retention) loose it's voltage. Unluckily, boot parameters and configuration is stored in PowerPC NVRAM as well, so after battery failure scope likely to fail, due to inability to load boot ROM from x86 PC system HDD. Visual diagnosis can be done by observing TekScope application to hang on splash screen, and debug POST code indicator rolling codes over and over from 4 to L on PPC board. This is happening because when PPC boot loader lost its boot settings and cannot find correct ROM anymore, it reboots after 10 seconds to try again. That's why it's staying on "L" phase for 10 sec before it repeats loop.
Quickly I found users with very same issues with their TDS7000/CSA7000 series machines here (http://www1.tek.com/forum/viewtopic.php?f=5&t=5195&st=0&sk=t&sd=a&hilit=vxWorks)
NVRAM repair solution / fix
First step is to replace faulty battery and allow Dallas NVRAM to be functional again.
Locate NVRAM on PPC board:
(http://dev.xdevs.com/attachments/download/617/nvram.jpg)
On CSA7404 it's near NLX riser connector, and have PowerCAP module on top of DALLAS DS1245YP-100. PowerCAP is just simple PCB with BR1632 battery soldered on and plastic cover. I replaced old battery (voltage on it was 0.7V after removal :bullshit:) with new Panasonic BR1632A/FA. Make sure polarity is correct when soldering battery on. Latch PowerCAP with new battery back on top of NVRAM.
Now we need to reset again correct boot parameters. To do so there are few extra tools are required:
* Serial interface to your host, or RS232-USB dongle
* Few wires for connecting PowerPC debug serial port
* Any terminal software which can work on serial port
I had no RS232 on my PC, but had few UART-USB interface bridges based on Silabs CP2103. RS232 levels are converted from UART by onboard MAX232 Driver IC (http://www.ti.com/lit/ds/symlink/max232.pdf) , which is located near NLX riser connector on PPC board. I connected GND (Pin 15), TX (Pin 11), RX (Pin 12) to Silabs CP2103 dongle inputs and connected terminal at 9600, 8N1 settings.
(http://dev.xdevs.com/attachments/download/618/serial.jpg)
First boot output with 9600 baud rate, 8N1 settings :
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.4.0
Creation date: Nov 2 2000, 11:03:34
Press any key to stop auto-boot...
7 6 5 4 3 2 1 0
auto-booting...
boot device : ??D?h?
processor number : 0
flags (f) : 0x0
Network interface D¦h unknown.
Can't load boot file!!
[VxWorks Boot]: Starting at 0xfff00100...
Then it rebooted and repeated above sequence again, and again, and again.
OK, so now we know that PowerPC board works, but obviously boot device "??D?h?" does not look right, thus it cannot load ROM and boot it's OS.
So let's halt auto-booting process by sending any char to terminal. By doing so we can stop loop and try to interact with PPC system. Now can send "?" command:
[VxWorks Boot]: ?
? - print this list
@ - boot (load and go)
p - print boot params
c - change boot params
l - load boot file
g adrs - go to adrs
d adrs[,n] - display memory
m adrs - modify memory
f adrs, nbytes, value - fill memory
t adrs, adrs, nbytes - copy memory
e - print fatal exception
n netif - print network interface device address
N - set ethernet address
$dev(0,procnum)host:/file h=# e=# b=# g=# u=usr [pw=passwd] f=#
tn=targetname s=script o=other
Boot flags:
0x02 - load local system symbols
0x04 - don't autoboot
0x08 - quick autoboot (no countdown)
0x20 - disable login security
0x40 - use bootp to get boot parameters
0x80 - use tftp to get boot image
0x100 - use proxy arp
0x1000 - use dio to get boot image
available boot devices: feippc bp sm
After some experimenting and searching web, I found somebody who had similar issues with CSA8000 oscilloscope (http://www1.tek.com/forum/viewtopic.php?f=5&t=4665&p=7819). Tried very similar parameters and discovered that they work fine after minor modification for my system:
Send "c" command to set settings:
[VxWorks Boot]: c
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : sm
processor number : 0
host name : host
file name : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.168.0.2
user (u) : anonymous
ftp password (pw) (blank = use rsh): anonymous
flags (f) : 0x1000
target name (tn) : target
startup script (s) : c:\vxBoot\dio_rst.vsh
other (o) : nvfs=0x1000
I used path to standard location on my x86 HDD partition, which is hidden folder c:\vxBoot. So if your location different - path need to be corrected. Inet/network addresses are used by internal interface between x86 and PPC. No ethernet cable was connected to either network ports on scope itself.
Now reboot scope.
...
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.4.0
Creation date: Nov 2 2000, 11:03:34
Press any key to stop auto-boot...
7 6 5 4 3 2 1 0
auto-booting...
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network PC1 dio device driver installed
interface lo0... done.
Attaching DIO client... done.
Loading c:\vxBoot\vxWorks.st...1773516
Starting at 0x200000...
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.0 .
WDB: Ready.
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: WARNING: Creating new NVRAM file system
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
tcsSynchronizeSensors: ERROR: Failed to create '/dev/tsAmbAcq'
tcsSynchronize: ERROR: Sensor synch failed
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:\vxBoot\dio_rst.vsh ...
dbFsIoctl: invalid code 3
cd "pc:c:/vxboot"
value = 0 = 0x0
tcsLoadTableToNVRAM "setup.tcs"
value = 0 = 0x0
#
# hopefully you get this message at the end:
# 'value = 0 = 0x0'
# REBOOT!!!
Great, now PowerPC board boots (diag POST LED shows "P" after "L" which means boot image is running). Now change dio_rst.vsh script to original top-level script (http://dev.xdevs.com/attachments/download/619/topScript.hw) which was recovered from native Win98 HDD folder c:/vxBoot. I renamed topScript.hw to dio_rst.vsh to match boot settings:
Executing startup script c:\vxBoot\dio_rst.vsh ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23662048 = 0x1690de0
ld < TekScopeSM.o
value = 23661408 = 0x1690b60
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
... bla-bla ...
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
Done executing startup script c:\vxBoot\dio_rst.vsh
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
Now scope application able to run successfully, and I got first waveforms on screen :).
(http://dev.xdevs.com/attachments/download/636/info.jpg)
Also seem like this particular scope got all options enabled, but some applications required for those options are missing, as I had installed fresh OS.
So system/software spec is:
CSA7404 (4GHz, optical hardware present) running Windows 2000 Pro SP4 Ru
TekScope version 2.5.3
Option 4M: 32 Meg Max 8M/Channel
Disk Drive Measurements 2 (Option 48)
Option 49
USB 2.0 Test package (Option 50)
Option 51
Option 52
Option 53
Option 54
RT-Eye Serial Compliance and Analysis
InfiniBand Compliance Module
PCI-Express Compliance Module
Pretty nice set got there for use in digital/PC hardware development and debug. Scope input interface for all four channels is proprietary TekConnect, and inputs are all 50 Ohm only. So to be able use regular passive BNC probes high-impedance adapter system TCA-1MEG is required, to use 50 ohm direct interface to target environment one can use TCA-BNC or TCA-292MM or TCA-SMA (http://www.tek.com/sites/tek.com/files/media/media/resources/60W_14970_6.pdf). As drawbacks of high-performance capabilities of such high-speed scopes special probing accessories are required, increasing total using cost. Passive probes cannot be used without TCA-1MEG.
Already got pair of Tektronix P7380 8GHz Differential probes, which are designed for high-speed signal acquisition with special solder-on tip system. Going to buy some lower speed single-ended active probes as well later.
Using this probe is really using for debug hardware, like DDR interfaces on VGA/DIMMs/MB's:
(http://dev.xdevs.com/attachments/download/626/dqs1.jpg)
DDR3 DIMM clock measurement
(http://dev.xdevs.com/attachments/download/629/ddr3_1333.jpg)
(http://dev.xdevs.com/attachments/download/630/ddr1333.jpg)
RT-Eye report:
(http://dev.xdevs.com/attachments/download/631/ddr3_1333e.jpg)
PCI-Express 1.0 report
(http://dev.xdevs.com/attachments/download/632/pcie.png)
Next steps:
* Design and assemble few custom probes for high-impedance environment
* Installing missing options software :-DMM
Bonus:
Replace LEDs behind front panel indicators and push-buttons, just like in newer DSO/MSO series. :-/O
(http://dev.xdevs.com/attachments/download/627/4ch.jpg)
To be continued...
Original wiki page on my site (http://dev.xdevs.com/projects/csa7404/wiki/Wiki)
Thanks for reading 8)
-
Thanks for posting, neat to see it back in action.
-
Drool... A wooden casing would be neat 8)
-
Thanks, for sharing an interesting story. May I ask how much did you pay for it and from where?
-
Careful swapping that motherboard out. The motherboard uses a custom bios that allows the VXworks to become bus master and take control over the harddisk prior to boot !
Don't make the mistake of flashing a regular bios in there , it will brick the machine. I've been there and done that ! the correct bios can be found on the harddisk as well as the flash utility for it. a stock motherboard will not work. there are only two motherboards that work in this machine and the 810 is the most performant of the two. the other runs win2000....
let it be ...
The other annoyance is loosing the ram contents. it removes the serial number from the machine and disables all options.
There is a way to restore it but you need a gpib adapter and send a commmand to the machine to contact the security manager and give it the root key.
-
That is a very nice writeup on the repair, very nice scope as well.
-
Sooo.. can I send you a board for PCIe compliance testing :)
-
Ha, to do so need to have much more than just 4G scope. Even if leave alone BER measurements, just CEM boards and fixtures cost quite a money :). And for PCIe Gen3 at least 16G bw required.
I got scope for just little over one K$, and main reason was because could not resist grabbing it , not because real need right now. Had no scope for personal use, just thought nice to have one at home.
-
Well, I got some update today, because received new goodies for scope.
Got 512MB and 256MB PC133 SDRAM DIMMs. x86 NLX motherboard refused to detect 256Mbit 512MB DIMM, so had to install 2x256MB into PC board
and 512MB on PowerPC board.
And CPUs:
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/936044w.jpg)
It's Pentium III 1000E (1000/256/100/1.75V, Coppermine-256), original Celeron 850/128/100 from scope and pair of Tualatin 1400S (1400/512/133/1.45V).
Pentium III 1000E drop-in to socket and worked flawlessly, booted right in with 100MHz FSB, 1.75ish Vcore.
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/936047w.jpg)
For those who want try upgrade their TDS7000/CSA7000's - beware to use 100MHz FSB chip, not 133MHz as such will run on 100MHz only, which will give only 750MHz (100*7.5 ratio = 750 for 133MHz native CPU).
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/936053w.png)
But top glorious Pentium III-S 1.4GHz did not work so easily, Vcore was 1.3V, but nothing happen after power on...
Obviously Intel NLX motherboard in TDS7000/CSA7000 do not support Tualatin natively and I needed to do some surgery to bypass that >:D
You can see already finished modified CPU bottom left on photo above.
What did I do:
1. Isolate pins AN3 (DYN_OE), AJ3 (RESET#2) from socket (I just desoldered pins right off CPU)
2. Isolate pin AK4 and connect it with AN11 via 1Kohm resistor (on CPU package)
3. Connect AM34 and AK36. (VID25mv signal tie to GND, to have correct Vcore VID operation)
4. Remove pins G35, G37 ? N37.
5. Connect G35,G37 and N37 together on CPU package.
That's it, after these modifications on CPU - it booted up and run smooth on 100MHz BCLK (native ratio on 1400S is 10.5, so 100*10.5 = 1050MHz).
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/936051w.jpg)
Vcore voltage is correct too, 1.46V, so nothing to worry about.
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/936052w.png)
So far only one thing left to do - receive covers and casing parts from Tektronix to completely restore outer looks on scope.
No more upgrades planned.
-
Got parts from Tektronix today :)
-
so how does your scope run with the upgraded CPU? I might look into do this as my TDS7404 is slow as hell!
-
Smooth and nice (but I think that's more because I added memory to 512MB total, rather than CPU).
Btw, I still have those CPUs, which I don't really need now ;)
So far:
New covers installed. Missing label for front panel and black cover for aux inputs on front.
Did not installed floppy drive (who needs them today?).
And missing some screws, need find them first.
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/938180w.jpg)
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/938183w.jpg)
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/938181w.jpg)
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/938182w.jpg)
So far spend around 2.5K$ on everything (including pair of P7380 probes), which is still quite a lot, but considering
this scope level - i think it was worth every penny :) :-BROKE :clap:
UPD: Went cleap-nut and just printed labels on paper and stick them to panels. :-DD
(http://fotkidepo.ru/photo/115530/50763YFb9eDuCDQ/938321w.jpg)
Now gotta hunt and wait patiently for good priced TCA-BNC adapters, TCA-1MEG high-impedance adapter. Already won pair of P6245 1.5GHz 1:10 active probes (for parts condition too, lol), and need think about iView (its just GPIB-USB dongle and couple BNC-BNC cables).
Tried iView on my TLA714 with NI GPIB-USB-HS and worklab TDS7704B, was nice neat feature to see everything in TLA software tool, eliminating need to mess with scope controls.
-
Just in case anyone needs drivers for TDS7000/TDS7000B/CSA7000/CSA7000B series scopes:
Display driver from TDS7000B/CSA7000B (http://xdevs.com/test/Tektronix/Tektronix_7000/Chips and Tech display V.2.50G.rar)
USB Front Panel driver for TDS7000/7000B/CSA7000/7000B (http://xdevs.com/test/Tektronix/Tektronix_7000/Front Panel V.1.0.rar)
PowerPC board driver for TDS7000/7000B/CSA7000/7000B (http://xdevs.com/test/Tektronix/Tektronix_7000/Tek PPC Driver Win2K.rar)
All drivers except display were tested on TDS7704B and CSA7404, with Windows 2000 Professional english.
Display driver is only for 7000B, i did not needed it on CSA7404
TekScope software itself 2.5.3 for TDS7000/CSA7000 (same as one posted on Tek website)
TDS2.5.3 TekScope (http://xdevs.com/test/Tektronix/TekScope/tds2.5.3_2008.06.09.10.42.00_5150_EN.exe)
-
BTW, I pulled the following out of a TDS7404 that had been under Tektronix maintenance and should be the correct default values.
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.4.0
Creation date: Nov 2 2000, 11:03:34
Press any key to stop auto-boot...
1
[VxWorks Boot]: ?
? - print this list
@ - boot (load and go)
p - print boot params
c - change boot params
l - load boot file
g adrs - go to adrs
d adrs[,n] - display memory
m adrs - modify memory
f adrs, nbytes, value - fill memory
t adrs, adrs, nbytes - copy memory
e - print fatal exception
n netif - print network interface device address
N - set ethernet address
$dev(0,procnum)host:/file h=# e=# b=# g=# u=usr [pw=passwd] f=#
tn=targetname s=script o=other
Boot flags:
0x02 - load local system symbols
0x04 - don't autoboot
0x08 - quick autoboot (no countdown)
0x20 - disable login security
0x40 - use bootp to get boot parameters
0x80 - use tftp to get boot image
0x100 - use proxy arp
0x1000 - use dio to get boot image
available boot devices: feippc bp sm
[VxWorks Boot]: p
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
[VxWorks Boot]:
-
:-+ :-+ :-+ :-+ :-+ :-+ :-+ :-+ :-+ :-+ Awesome Job!
Tom, NW0LF
-
Great job!
Where can you find the system restore cd image? For a tds7054. There isn't one posted on the tek website.
-
I did not had system restore CD image.
Just installed usual Win2000 OS, installed drivers for PPC board and USB Front panel (I had posted them earlier here) and downloaded TekScope 2.5.3 from tek site.
-
I'll vouch for the drivers that TiN posted are the same as what's included on the hard drive after a restore from original system restore CD's. I double-checked them to see if he happened to have anything newer than what I already had, and they matched. However for those who have expanded their memory to 512MB and would like to jump to Windows XP, I'd suggest hunting down the v2.51c "release" Windows XP driver for the proprietary Chips and Technology LCD interface. The filename is "wxpv251c.zip". The other drivers are generic enough that they run under Windows XP OK. Tektronix went through a number of different NLX motherboard vendors over the production run, so depending upon your particular motherboard, you may also need to track down the Intel Ethernet driver. Replacing it with the Intel SU810 NLX motherboard guarantees Windows XP built-in driver support for all of the on-board peripherals.
-
Great job!
Where can you find the system restore cd image? For a tds7054. There isn't one posted on the tek website.
YOu won that auction did you? Lucky bastard.
-
Hi TiN.
Do you know if the software Tek App V5.1 [TLA] has support for the TDS7xx series?
Thanks. :-+
-
Seems so, at list TDS7xx scopes and TDS694 are in the list, but probably some functions will not be working (there is extra clock, which is shown as not used in drawing diagram). On TDS7xxx it goes to EXT REF input on scope, but those older scopes don't have EXT REF input.
Take this info as is, as I don't have ability to check if that combo actually work.
In worst case you still can use TLA with scope, just connect trigger output from TLA to scope trigger input (even non-tektronix is fine, lol),
and route analog outputs from TLA7AA4 into scope channels, and you will have signals from LA triggered on scope screen.
Just not as neat as having everything in same TLA app, that's it. (Even using iView one must adjust horisontal/vertical scale on scope itself, cannot use TLA app to do those adjustments).
-
Seems so, at list TDS7xx scopes and TDS694 are in the list, but probably some functions will not be working (there is extra clock, which is shown as not used in drawing diagram). On TDS7xxx it goes to EXT REF input on scope, but those older scopes don't have EXT REF input.
Take this info as is, as I don't have ability to check if that combo actually work.
In worst case you still can use TLA with scope, just connect trigger output from TLA to scope trigger input (even non-tektronix is fine, lol),
and route analog outputs from TLA7AA4 into scope channels, and you will have signals from LA triggered on scope screen.
Just not as neat as having everything in same TLA app, that's it. (Even using iView one must adjust horisontal/vertical scale on scope itself, cannot use TLA app to do those adjustments).
Ok, thanks. :-+
But if the LA's "wfrm/s" (triggers/s) are greater than the oscilloscope's wfrm/s (rearm time), the oscilloscope will not be able to follow LA's triggers.
This is a problem, because: How do you know what oscilloscope's captures goes with what LA's triggers?
And if the above problem is solved the phase has to be adjusted too. So it's a mess, and better to use compatible instruments.
Because surely they have already thought of this, and have fixed this.
Or am I wrong?
-
All TLA trigger setup is internal to TLA modules, and then you select output trigger to scope.
Then can use skew adjustment in scope, at least that's available in TDS/CSA7404 and 7704 i tried. Dunno about other models, but should be there too.
Even not adjusted, unless you watch something with hundreds of MHz, will be quite okay.
I shown example non-compensated iView capture here (https://www.eevblog.com/forum/testgear/tla-hacks-)/msg311238/#msg311238).
TLA7AA4 outputs connected to scope inputs (thru TCA-BNC) via mismatched BNC-BNC cables and SMA-SMA (thru TCA-SMA).
iView setup using recommended connections, and with generic BNC-BNC cables. Interface - NI generic GPIB-HS-USB connected to my remote machine
(as I run TLA only remotely, don't even have NI-VISA on mainframe itself).
-
I shown example non-compensated iView capture here (https://www.eevblog.com/forum/testgear/tla-hacks-)/msg311238/#msg311238).
@TiN:
At least 2us long, in the image above. All was captured without pauses? Ie are not overlapping catches?
And what is the maximum length?
-
Capture on post i linked was around 100nS long.
One catch, yes. You have TLA, right? Your questions seem strange, as for owner of TLA frame, as that's
pretty much just TLA operation. :)
-
No, I don't have a TLA. If I had one, then would not bother you with my questions.
I just want to know, how it works in conjunction with an oscilloscope.
My apologies if I've bothered you. :-[
-
Hm, somehow i thought you had one.
In simple words - TLA works like logic analyzer, iView scope brings analog waveform into TLA app window, that's it. Scope need to be set in correct horizontal/vertical ranges to capture signal well manually. TLA can trigger external scope (any scope) by BNC output, which can be synced to capture trigger of TLA itself.
Also there few more functions for high-speed signal verification, like iVerify, but that's pretty specific to some usage cases.
There is no other link except this, regarding TLA application and iView. I would not focus too much on specifically buying scope which supports Tek TLA iView.
Most of the time I use TLA just alone, debugging digital stuff. If I need see signal - i'd rather just hook a scope to interested signal and not bother with getting TLA and scope both setup right.
TLA is not really realtime device, it's working differently that usual RT scope. Sample count may way from few hundred samples to 32M like on my hacked TLA7AA4 or even more on modern hi-end modules like TLA7BB4 or 7BC4.
You can download TLA application and play with it a little, it have demo mode when no real mainframe detected.
-
You can download TLA application and play with it a little, it have demo mode when no real mainframe detected.
Yes, off line mode.
Thanks. :-+
-
Great guide OP, thanks for that!
I have a scope (TDS7104) which hangs at the program start-up and I have followed your instructions on how to repair it (i.e. swapping the NVRAM battery and flashing). However, it's behaving a bit wierd after I opened it up; it doesn't boot anymore! :-BROKE
You see the bios boot-up on the screen but after that I just get a error saying "Incorrect system" and it doesn't want to proceed. I have looked at the diagnostic led and it hangs on '.8'. Have you experienced anything like this?
It was a while ago I tried to repair it and now it's just collecting dust, but I could get more details in the coming week.
Thanks in advance.
-
error saying "Incorrect system"
Seem your windows/HDD is bad, you need fix it first, and make Windows 2000 bootable :)
-
But the funny thing is that it stopped booting properly right after I opened it up.
Also, forgot to say; sometimes (~once every 100th boot-up) it actually boots into windows. So I guess the HDD is working fine.
-
Check your harddrive. Maybe have bad sectors, which is not rare given age of those units.
It must boot every time :)
-
Ok, I'll try that! Thanks :)
-
Tried booting the scope up today. I had scanned the harddrive for errors, it found a couple which I fixed. Put it back into the scope and it booted!! :scared: I restarted it a couple of times and it worked fine! I got the looping diagnostic led which is described in the first post.
I then proceeded with changing the NVRAM battery and connected the required RS232 cables. Tried booting it up... nope :palm:. It seems I am back on square one, the diagnostic led has hanged on '.8' and I get the error message 'Incorrect system'.
I think the disk is fine but something weird is happening when I am fiddling with the battery.... any clues? :(
-
What is your RS232 log? Can you post it here? There is a chance that PPC board may corrupt your MBR or FS on HDD.
-
Sure, will do that! I didn't get any data when trying to read the RS232-bus, but that might be because I have a USB<->RS232 adapter, so I guess I have to switch pins from 11&12 ->13&14? Or maybe it is easier to connect it somewhere else on the board?
Thanks for your quick replies!
-
Careful swapping that motherboard out. The motherboard uses a custom bios that allows the VXworks to become bus master and take control over the harddisk prior to boot !
Don't make the mistake of flashing a regular bios in there , it will brick the machine. I've been there and done that ! the correct bios can be found on the harddisk as well as the flash utility for it. a stock motherboard will not work. there are only two motherboards that work in this machine and the 810 is the most performant of the two. the other runs win2000....
let it be ...
The other annoyance is loosing the ram contents. it removes the serial number from the machine and disables all options.
There is a way to restore it but you need a gpib adapter and send a commmand to the machine to contact the security manager and give it the root key.
@free_electron:
very preciouse comment, thanks. can you please be a little more specific here. how to call the flashing software and how to deal with the other boards (they are needed in the system to power the nlx board as you know).
i have the issue that I need to replace the nlx mainboard (a su810 from intel). can i just disable the other two pci devices (ppc board and graphics chip) by the two jumpers, boot into windows, call the flsahing sw (how?), flas the firmware hub, and all this without destroying the boards
-
The Intel SU810 NLX motherboard guarantees Windows XP built-in driver support for all of the on-board peripherals. Electrically, it is a great match, but the ports on the rear may not line up depending upon the motherboard tray that your particular oscilloscope happens to have. (Tektronix went through multiple motherboard vendors for that oscilloscope over the years.) One can flash it with Intel's last BIOS update for that motherboard, version P10, which also supports later, faster processors. This can be done in-system without any other precautions. One can find this particular board on eBay by searching for "Intel D810 NLX". One will want to proactively replace the CMOS battery as these motherboards are new, very old stock. 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.
-
hi. many thanks.
actually the board in my 7104 is exactly a intel su810. same name, same number (tek also used readisys e.g., but mine is the intel). I had just ordered the one on ebay, is on its way.
so here are some additional questions:
-but how do i flash it?
-and as free_electron states, how do i avoid it destoys the syste as he has experienced?
mine actually is in reset all the time. I also have a thread a little earlier about in the test equipment section about the reset issue. any comments here?
-
I bought SU810 before as well, when was debugging scope, but it never worked.
Original in CSA7404 is SF810 Radisys, so after all it was all PPC configuration and NVRAM issue, so did nothing regarding x86 board, kept original board and replaced bodged capacitor and updated CPU to Pentium III-S 1400 (which working on 1050MHz due to 100MHz FSB).
SU810 missing interface bridge chip (National semi if I recall correctly).
When installed it was not powerin on at all. Did not bother much to find out why, just left it collecting dust now.
-
I disabled both ppc baord and graphics chip, but my su810 (it is original intel, no radisys in my 7104) is in reset, so seems dead.
my only hope at this time is the new su810. nobody seems to have a hint how to debug su810 generating a reset and I have no schematics.
-
If you dig around a little on Intel's website you'll find reference designs for their chipsets. Did you check whether the CPU is still working?
-
thanks, today I found a reference design for 810 chipset. the reset signal seems to be generated by the 810 gmch chip, which is a black boy essentially. i have ordered a celeron replacement cpu, which i will plug in just for tests, but i think the cpu is not the problem, since it is held in reset.
-
Another great upgrade to juice up one of these tired, old oscilloscopes is to install an inexpensive SSD. I went with the Kingspec KSD-PA25.6 PATA 44-pin MLC SSD. They can run as little as $50 delivered at the low-end, and range in capacities from 16GB to 128GB. While the SSD does not make it run that much faster during operation like the processor upgrade does, it does allow it to cold boot much more quickly and get away from the unreliable old notebook hard disk drives. In the scheme of things, it seems like it's a worthwhile investment to me.
-
@csmith:
yes, agreed, i did that with another 7104 where the hdd had actually failed. if this one ever gets so far i will do the same. also the other drives should be replaced by nos ones.
also, I will replace the batteries by socketed and bigger batteries on a pcb that can easier be replaced (the one on the ppc board is a nightmare).
but first I would need to get your help how to flash the bios without killing the rest of the system...
-
Poor thing died again. TekScope app shows splash screen, but hangs on it.
Yes, NVRAM battery.
Error in boot line:
]d«k[ÆÑ?_æëä6)4??â?2«óô
^
Can't load boot file!!
Probably battery was not fresh, as it was only 9 month since I first got CSA7404 and fixed it.
And most of time it was just sitting on shelf turned off.
At such times one might appreciate that time was spend to write a worklog and post all photos and workarounds online, as now getting it fixed only takes five minutes to replace cell, hook serial terminal and write correct data for PPC config.
And good excuse to fix another minor issue with self-calibration data storage for probes.
-
A little update, with EEVBlog forum member magic, we can get keys for options on TDS7000/CSA7000 and probably other 70000 series scopes too :)
Quick check of concept proof with my CSA7404:
(http://dev.xdevs.com/attachments/1009/options_ffff.jpg)
16 options enabled :)
Need to find out which bit does what and we good to go!
-
Hello,
I've been trying to connect to the UART on my 7404. I've established a serial link, but everything that comes up in the terminal is garbled junk.
Any ideas would be greatly appreciated!
Thanks in advance!
-
You probably have incorrect speed settings for UART port.
-
Are you referring to the baud rate? I'm using 9600. I've also tried a few different terminal programs, they all display the same garbled txt. Any other ideas? Thanks again!
-
Are you connecting at the J790 right-angle dual-row 10-pin header with RS-232 levels or at the MAX232 with TTL levels like TiN did? The data may be inverted depending upon your expectations.
-
I connected to the MAX232, should I be using the J790? if so do you know the pinout for it?
-
Please, if anyone knows the pinout for the console port. I would be very grateful.
-
Its pretty easy to probe pinout with just DMM. I did not use console port because I have plenty USB-UART(TTL) adapters using Silabs CP2103 bridge, but no RS232, so i needed to hook on TTL side of MAX :)
Its really not much things can go wrong, unless your bridge dongle somewhat faulty.
Make sure you have robust ground connection between pc and scope.
-
I guess I'm still confused, and thanks again for your help. I'm using a SiLabs CP2102-EB, do I connect to the console or the MAX?
-
If your board have level convertor before cp2102 then you can use console port.
If not then u need use TTL pins on MAX.
You can search for information regarding difference between UART and RS232 voltage levels and convertors.
Will all due respect, given that you messing with internals of hiend scope, you should know that anyway ;)
-
I connected to the MAX232, should I be using the J790? if so do you know the pinout for it?
the pins are connected to the max232 through 100 ohm resistors
-
Recently I came into possession of a tds7104. At first it seemed as if, its just the NVRAM battery problem (scope app splash screen can't start). After i made a backup of the old hdd (win 98) when i noticed that the diagnostic led just shows ".8". I tried to look at the boot up process from the Rs232 console, but it seems as if nothing goes on. In the service manual it is shown, that the UART initialization , takes place after the first test is concluded. So am i missing something or it is a fault in the power pc board?
-
I have been probing around the MCU on the power pc board. It seems as one or more of the power rails has have been shorted. C352: 3,19V , C235 0,84V C240 & C143: 0,85V(this should be2,5V from the dc/dc) C232:0,52V (while the main 3,3V lines seem to be fine)
U442 marked "BeY" i think it's a AND gate or maybe a TVS. It seems to be damaged, aleast between pin 5(VCC) and pin 3(GND) it measures a few tens of ohms (30-80). So i need to find or atleast locate another faulty chip nearby
Turns out the PT6409P (2,5V switching reg died) after i wired the 2,5V line from a powersupply the powerpc board finaly showed somthing other then .8 the diagnostic led showes 0 or 3 so it seems somthing is still wrong with the MCU (CR874 indicates reset at times) still nothing on uart. It seems i need to replace the board...
Update:
There might be still hope ! After replacing the 2 SO8 transistor pair on the PT6409P ( Si4431 , Si4412 i could only source 4410 but it seems to work fine) the power pc board cycles through it's tests and finialy boots if assembled, untill the screens shows a blue screen memory parity error
here is what i got on the console port (witha newly installed xp and 2.5.3 firmware):
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
romPost: MPC106 Walking-one passed.
romPost: MPC106 configuration passed.
romPost: First PCI access passed.
romPost: PC87560 Walking-one passed.
romPost: PC87560 configuration passed.
romPost: DEC21554 configuration passed.
romPost: PERFORMING ROM CHECKSUM TEST...
romPost: ROM checksum passed.
romPost: PERFORMING DRAM CELL TEST...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM WALKING-ONE TEST...
romPost: DRAM Walking-one test passed.
romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...
romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: POWER-UP DIAGNOSTIC COMPLETE.
Hel
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.3.0
Creation date: Jun 28 2000, 16:52:12
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topScript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network inPC1 dio device driver installed
terface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773516
Starting at 0x200000...
Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23666688 = 0x1692000
ld < TekScopeSM.o
value = 23666048 = 0x1691d80
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1693940: value = 23673184 = 0x1693960 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691bc0: value = 23665696 = 0x1691c20 = pDBfs + 0x60
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
0x16987e0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0
excHookAdd(stopStressForException)
value = 17557980 = 0x10be9dc = stopStressForException
dsyInit
value = 21806728 = 0x14cbe88
dsyWPApplyNextRegs
value = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x16987e0 (tShell): >> Kernel version 1.0.8.1 does not match Boot ROM version 1.0.3.0
value = 21801472 = 0x14caa00
TmgrInit("/db")
value = 0 = 0x0
PhxProxyInit
value = 20822560 = 0x13dba20
rtlInit
value = 0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
hwAccount_init
0x16987e0 (tShell): >> Setting PLL to 1.25e+09 Hz.
sysEnetAddrGet: cc:aa:88:ba:da:dd
value = 7 = 0x7
GpibInit
value = 133284512 = 0x7f1c2a0
wfmMemInit(1)
value = 47300320 = 0x2d1bee0
vertInstall
value = 47293284 = 0x2d1a364
calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x2d1a240
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0x2d1a300
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x16987e0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x16987e0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/calCon1Status
0x16987e0 (tShell = ): cc_init: bank 0x1 chksum failed, NOT reset to factory
1341eec0x16987e0: value = (tShell): 131055cc_restoreBank: can't open file C:/vxBoot/calCons/ =2 0x
0x16987e0 (tShell1ffef): cc_init: bank
2 chksum failed, NOT reset to factory
0x16987e0 (tShell updateTrigCal):
cc_restoreBank: can't open file value C:/vxBoot/calCons/= 30
0x16987e0 (tShell): = 0xcc_init: bank 03 chksum failed, NOT reset to factory
0x16987e0 (tShell):
cc_restoreBank: can't open file MC:/vxBoot/calCons/at5hMeasCreateTheMatha
ndMeasurementLibrar0xies16987e0 (tShell):
cc_init: bank 5 chksum failed, NOT reset to factory
valu0xe = 16987e0 (tShell47120704): cc_restoreBank: can't open file = 0xC:/vxBoot/calCons/2cf01406
0x16987e0
(tShell): cc_init: bank initA6cqMapper chksum failed, NOT reset to factory
0x16987e0 (tShellvalue = ): cc_restoreBank: can't open file 0C:/vxBoot/calCons/ = 0x7
0x16987e00 (tShell): cc_init: bank
7 chksum failed, NOT reset to factory
trigMapIn0xit16987e0 (tShell):
cc_restoreBank: can't open file valueC:/vxBoot/calCons/ =8
0x16987e0 (tShell): 0cc_init: bank 8 chksum failed, NOT reset to factory
= 00xx16987e0 (tShell): 0cc_restoreBank: can't open file
C:/vxBoot/calCons/ dsy9MapInit
0x16987e0 (tShell
): cc_init: bank value = 9 chksum failed, NOT reset to factory
00x16987e0 ( = 0xtShell): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
10
0x16987e0 ( mathMapperInittShell
): cc_init: bank value = 10 chksum failed, NOT reset to factory
00x16987e0 = 0x (tShell): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
11
0x16987e0 utilMapInit (tShell
): cc_init: bank value = 11 chksum failed, NOT reset to factory
471180480x16987e0 = 0x (tShell): 2cef6e0cc_restoreBank: can't open file
C:/vxBoot/calCons/12
0x16987e0 (tShell
): cc_init: bank TmgrHookup12 chksum failed, NOT reset to factory
0x16987e0value = (tShell0): cc_restoreBank: can't open file = C:/vxBoot/calCons/0x130
0x16987e0 (tShell
): cc_init: bank 13 PhxProxyHookup chksum failed, NOT reset to factory
0x16987e0value = (tShell0): cc_restoreBank: can't open file =C:/vxBoot/calCons/ 014x
0x16987e0 (tShell0): cc_init: bank 14
chksum failed, NOT reset to factory
0x hookupAcqMapper16987e0
(tShell): cc_restoreBank: can't open file value = C:/vxBoot/calCons/2011564752
0x16987e0 (tShell = 0x): cc_init: bank 133b09015 chksum failed, NOT reset to factory
= 0x16987e0AcqMapperRtlDat (aListtShell): cc_restoreBank: can't open file
C:/vxBoot/calCons/ MathMeasM16apHookup
0x16987e0 (
tShell): cc_init: bank value = 16 chksum failed, NOT reset to factory
23692550x216987e0 (tShell): = 0xcc_loadV: CC_TRIGtrigLineGain16985 was 08>; clipped
0x
16987e0 (tShell): dsyMapHookupcc_chkLimits:
CC_TRIGtrigLineGain was ; reset to factory
value0x = 16987e0 (tShell): 23692656initAcqMapper: Enter
= 0x1698570
utilMapHookup
value = 23692688 = 0x1698590
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 23692648 = 0x1698568
fastFrameMapHookup
value = 23692672 = 0x1698580
trigMapHookup
value = 23692680 = 0x1698588
vertMapHookup
value = 23692672 = 0x1698580
spcMapHookup
value = 23692672 = 0x1698580
autosetMapHookup
value = 23692712 = 0x16985a8
timeSyncMapHookup
value = 23692704 = 0x16985a0
auxTrigMapHookup
value = 23692688 = 0x1698590
dpoMapHookup
value = 23692680 = 0x1698588
TmgrStartup
0x2c9cf40 (tmgr):
TmgrTaskInit: Last powerup failed, going to default setup
value = 46644144 = 0x2c7bbb0
PhxProxyStartup
value = 46578592 = 0x2c6bba0
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 46478848 = 0x2c53600
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006
and the boot with the "original" win98 and firmware:
done.
Attaching network PC1 dio device driver installed
interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773508
Starting at 0x200000...
Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.7.1 .
WDB: Ready.
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23666688 = 0x1692000
ld < TekScopeSM.o
value = 23666048 = 0x1691d80
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1693940: value = 23673184 = 0x1693960 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691bc0: value = 23665696 = 0x1691c20 = pDBfs + 0x60
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 17800576 = 0x10f9d80 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): Processor failed to verify after byte #0.
Burning new AVR processor code.
0x16987e0 (tShell): 1340 bytes successfully programmed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0
excHookAdd(stopStressForException)
value = 17589548 = 0x10c652c = stopStressForException
dsyInit
value = 21807176 = 0x14cc048
dsyWPApplyNextRegs
value = 17790452 = 0x10f75f4 = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x16987e0 (tShell): >> Kernel version 1.0.7.1 does not match Boot ROM version 1.0.3.0
value = 21801920 = 0x14cabc0
TmgrInit("/db")
value = 0 = 0x0
PhxProxyInit
value = 20817184 = 0x13da520
rtlInit
value = 0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
hwAccount_init
sysEnetAddrGet: cc:aa:88:ba:da:dd
value = 7 = 0x7
GpibInit
value = 133684384 = 0x7f7dca0
wfmMemInit(1)
value = 47697632 = 0x2d7cee0
vertInstall
value = 47690596 = 0x2d7b364
calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x2d7b240
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0x2d7b300
0x16987e0 (tShell): nvMem_read succeeded
calConStatus = 0x1342b14: value = 0 = 0x0
updateTrigCal
value = 0 = 0x0
MathMeasCreateTheMathandMeasurementLibraries
value = 47518016 = 0x2d51140
initAcqMapper
0x16987e0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
trigMapInit
value = 0 = 0x0
dsyMapInit
value = 0 = 0x0
mathMapperInit
value = 0 = 0x0
utilMapInit
value = 47515360 = 0x2d506e0
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 20167864 = 0x133bcb8 = AcqMapperRtlDataList
MathMeasMapHookup
value = 23692552 = 0x1698508
dsyMapHookup
value = 23692656 = 0x1698570
utilMapHookup
value = 23692688 = 0x1698590
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 23692656 = 0x1698570
fastFrameMapHookup
value = 23692672 = 0x1698580
trigMapHookup
value = 23692680 = 0x1698588
vertMapHookup
value = 23692672 = 0x1698580
spcMapHookup
value = 23692672 = 0x1698580
autosetMapHookup
value = 23692712 = 0x16985a8
timeSyncMapHookup
value = 23692704 = 0x16985a0
auxTrigMapHookup
value = 23692688 = 0x1698590
dpoMapHookup
value = 23692680 = 0x1698588
TmgrStartup
0x2cfe0c0 (tmgr):
TmgrTaskInit: Last powerup failed, going to default setup
value = 47056848 = 0x2ce07d0
PhxProxyStartup
value = 46991296 = 0x2cd07c0
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 46891568 = 0x2cb8230
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 4663012
-
Thanks for your help with the pinout! I've reconfigured the boot parameters in the NVRAM successfully.
Sadly it seems like a BIOS issue now, I'm unable to get into the BIOS to make sure it sees the HD. I've tried the bios jumper to no avail.
Does anyone know if there is a trick to get into the BIOS? F2 key brings up the "Entering Setup", but it never actually enters the BIOS, just continues to try and boot from the network. Ideas?
Thanks
-
Wierd, just tried on my CSA, it enters BIOS just fine with F2 key.
Shows Entering setup... then bar on bottom loads and it's in the BIOS like Flynn..
-
There is an option in it's bios to lockout the setup in security, by default it should be disabled. Try to remove the NLX battery and short the sockets pins fora few sec then place back the battery (that should reset to some factory settings in theory)
-
Just to be sure i tried it also with a new NVRAM module, after messing with the boot parameters i could get it to boot till windows but the vxWorks systematically froze at points, with a ping sound on the rs232 terminal (with the wrong boot parameters, yet the QA+tests finished without an error) or get a blue screen (parity error) randomly while the vxWorks almost finished loading. (L->-P-> "-" blinked and the power pc board shut down) Occasionally the scope stoped with ".6" diagnostics error which is again related to the dram. So in conclusion i think there's something wrong with the power pc ram module. Or some other logic ic on that low ohms 5V rail...
-
I tried shorting the pins on the NLX battery, no luck. What's interesting is I have a CSA8000 as well and it does the same exact thing. The "entering setup" flashes a few times and then it continues to boot without entering setup. |O .....
-
That's odd. Did you try without the hdd or with the J840 and J841 power pc and display bypass jumpers shorted, on an external monitor?
-
Yes, I've tried all jumper combinations including the PPC J840. The only one that causes any difference in startup is with J781 completely removed; then it just beeps. I've been using an external monitor and have tried with both HDD installed, w/o HDD. I've swapped ram to try and trick it to stop for config changes; no change.
Does anyone know what the "DIAG SEL" dip switches are used for on the PPC?
Thanks!
-
you can find it in the service manual (the link is posted by TiN or on his site) that sounds as theres something wrong with the mother board or the CPU. How many beeps ? This might explain why you can't enter bios if the comp part doesn't work there is some mo9re info about bios errors related to start up beeps at the end of the manual also.
-
After some more measurements, one pin of the replaced U442 (2 pos input AND gate) didn't reflow properly, i reworked it and now the scope boots and runs the app ! (with the "fresh" NVRAM, for some reason with the old one it keeps hanging while the vx stuff boots) diagnostics and self cal all passed
-
That is very well spotted ! :-+ I suppose the scope is working now?
-
I'm throwing in the towel on this TDS 7104. If anyone is interested in buying it for parts/repair let me know. I also have a TDS 8000 for parts as well.
Thanks for all your help,
-Kevin
lostphoton@gmail.com
-
If I where you I'd put it on Ebay. What do you expect to get for it pricewise?
-
Thanks for your help with the pinout! I've reconfigured the boot parameters in the NVRAM successfully.
Sadly it seems like a BIOS issue now, I'm unable to get into the BIOS to make sure it sees the HD. I've tried the bios jumper to no avail.
Does anyone know if there is a trick to get into the BIOS? F2 key brings up the "Entering Setup", but it never actually enters the BIOS, just continues to try and boot from the network. Ideas?
Thanks
Hello,
I think you will find that if you remove the coin cell on the NLX processor board for a minute or so with the AC power cord disconnected, then put it back in and power up, it will cause the BIOS to get a CMOS checksum error, and prompt you to enter the BIOS setup. You may need to connect an external monitor to the motherboards SVGA video on first power up. In the BIOS there is a setup option to use PCI video which will then cause the scope to use the video located on the power PC board.
I sent you a PM on this, but didn't hear back from you, so I'm posting this here.
Jay
-
A little update, with EEVBlog forum member magic, we can get keys for options on TDS7000/CSA7000 and probably other 70000 series scopes too :)
Quick check of concept proof with my CSA7404:
(http://dev.xdevs.com/attachments/1009/options_ffff.jpg)
16 options enabled :)
Need to find out which bit does what and we good to go!
Hi Tin,
I recently picked up a TDS7104 myself. This one was missing it's hard drive. After sorting that out, and repairing a SPC issue I noted two things: It had option 3M which was a nice surprise, but it would crash the tek scope application when I ran the diagnostic.
After fiddling around with different ghost images for the scope and messing around through the console port I found that option 3M had disappeared, but now I have option Jitter analysis 2, which wasn't there before. |O
Crap! I'd much rather have option 3M back...
I suspect that it was my mucking about with the console port settings. The original looked like this:
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topScript.hw
But it seems I cannot go back to that, as the prompts are now somewhat different.
Update: I also just noticed that the serial number reported in the about menu now does not match what is on the sticker of the unit in the back of the scope. The "about" menu reports it as B021068, but the sticker says it is B021079! I bet that has something to do with it!
Would you have any idea how I could get option 3M back?
Thanks!
Jay
-
Hi Tin,
I recently picked up a TDS7104 myself. This one was missing it's hard drive. After sorting that out, and repairing a SPC issue I noted two things: It had option 3M which was a nice surprise, but it would crash the tek scope application when I ran the diagnostic.
After fiddling around with different ghost images for the scope and messing around through the console port I found that option 3M had disappeared, but now I have option Jitter analysis 2, which wasn't there before. |O
Crap! I'd much rather have option 3M back...
I suspect that it was my mucking about with the console port settings. The original looked like this:
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topScript.hw
But it seems I cannot go back to that, as the prompts are now somewhat different.
Update: I also just noticed that the serial number reported in the about menu now does not match what is on the sticker of the unit in the back of the scope. The "about" menu reports it as B021068, but the sticker says it is B021079! I bet that has something to do with it!
Would you have any idea how I could get option 3M back?
Thanks!
Jay
Funny - after asking the question and exploring this for awhile I figured it out!
In the folder \vxBoot there are two files .key and .sn The .sn contains the serial number.
I deleted the .key and modified the .sn file with a hex editor so it would have the correct serial number of the scope according to the sticker on the back. I then booted the scope and entered in the option key on the sticker in the rear.
Voila! option 3M is back! :-+
Jay
-
Maybe dump your dallas chip?
I'm somewhat planing to get a cheap TDS 7154/7254 once one appears cheaply on ebay and then hack it to 32M.
If there's a collection of NVRAM dumps and their options, we can figure out which bit enables which option, so every TDS owner can hack their scope to 16M/32M memory.
-
If there's a collection of NVRAM dumps and their options
No need for that, need just little time, as there is way to generate option keys for any S/N :)
I am in progress of writing article for it (also supports not only TDS7k series gear ;))
-
Maybe dump your dallas chip?
I'm somewhat planing to get a cheap TDS 7154/7254 once one appears cheaply on ebay and then hack it to 32M.
If there's a collection of NVRAM dumps and their options, we can figure out which bit enables which option, so every TDS owner can hack their scope to 16M/32M memory.
While there is a Dallas/Maxim chip on the power PC board, it's surface mount and I wouldn't take the chance of de-soldering it, especially now that I've got everything up and running. I don't think the options are stored there like on the TDS500 through TDS700 series, but I could be wrong... Maybe somebody else knows?
Jay
-
Just a few comments to this topic. It is obvious from the comments here that the csa8000 and the tds 7104 have different settings in the vxworks boot file. I have verified the 7104 settings as listed in a recent comment above for my 7104, and they do work. I learned this the hard way, as I replaced my sram battery (under power, it was 10+ years old) to avoid a loss of data, but somehow the contacts of the new battery were intermittent (bent contacts), so i lost all data. so watch out for this as you use a new battery.
the settings can be entered with a terminal through serial line, you do not need to enter data that is irrelevant (such as e.g. the ethernet path, it is not used, just hit enter in this case). all data to be entered is listed above a recent comment, no further data needed. my scope now behaves a little different, it does a full hw selftest at startup, compared to a limited one before (more relays clicking and more test data comming through the serial line), I suspect this is because I set "flag" at 0x1008 rather than 0x1000.
-
Poor thing died again. TekScope app shows splash screen, but hangs on it.
Yes, NVRAM battery.
Probably battery was not fresh, as it was only 9 month since I first got CSA7404 and fixed it.
And most of time it was just sitting on shelf turned off.
Hi Tin,
It may interest you to know that a CSA8000 that I repaired for a friend about 8 months ago that had a bad battery (Same as the one in your scope) also died after sitting on a shelf. According to Maxim, these are supposed to be good for 10 years. I'm wondering if there was a batch problem with these chips. The scope is on it's way back to me, I'm going to do some current measurements to see how much the chip draws when the scope is unplugged.
Jay
-
that sounds like what was happening to me, because initially the scope worked with a new battery, but then died, due to insufficient contact (an interruption when I moved it during re-assembly), the battery pins were bent a little as it seems when I bought them, so I bent them back and it worked. my battery was from 2013 and reads above 3v. so watch out.
on another topic re. the 7104, i have a friend who owns one too, and when he switches on the rear power switch, it does not boot, you need to press the front key in addition. mine powers on once power is applied (rear switch on) , without having to switch it on with the front button. I would like to change this, as I am powering all my equipment off with a central switch, and repowering always switches on the scope.
any ideas? the internal power jumper on the ppc board is not set, so that is not the issue. might have to do with the psu (bios and win98 are not active at that time, so no settimgs there), any ideas?
-
that sounds like what was happening to me, because initially the scope worked with a new battery, but then died, due to insufficient contact (an interruption when I moved it during re-assembly), the battery pins were bent a little as it seems when I bought them, so I bent them back and it worked. my battery was from 2013 and reads above 3v. so watch out.
on another topic re. the 7104, i have a friend who owns one too, and when he switches on the rear power switch, it does not boot, you need to press the front key in addition. mine powers on once power is applied (rear switch on) , without having to switch it on with the front button. I would like to change this, as I am powering all my equipment off with a central switch, and repowering always switches on the scope.
any ideas? the internal power jumper on the ppc board is not set, so that is not the issue. might have to do with the psu (bios and win98 are not active at that time, so no settimgs there), any ideas?
I believe that there's a setting in the BIOS for that. Power on after power fail or last state.
Jay
-
yes, you are right, somehow I had overlooked that when I checked the BIOS initially, maybe driven by the idea that the BIOS would not be active at time of applying power. anyway, thanks, that helped a lot.
-
Poor thing died again. TekScope app shows splash screen, but hangs on it.
Yes, NVRAM battery.
Probably battery was not fresh, as it was only 9 month since I first got CSA7404 and fixed it.
And most of time it was just sitting on shelf turned off.
Hi Tin,
It may interest you to know that a CSA8000 that I repaired for a friend about 8 months ago that had a bad battery (Same as the one in your scope) also died after sitting on a shelf. According to Maxim, these are supposed to be good for 10 years. I'm wondering if there was a batch problem with these chips. The scope is on it's way back to me, I'm going to do some current measurements to see how much the chip draws when the scope is unplugged.
Jay
Finally got the CSA8000 back. Yup, the battery was dead; I purchased it direct from Digikey, so not likely to be a questionable battery from the start. Using a power supply set to 3VDC running through a current meter when I initially connected the source to the chip it reads in the micro-amp range. When I powered on the scope it still read in the micro-amp range. When I powered off the scope - whether from the rear panel or front power button it draws 1.8mA.
So, looks like a bad chip.
It's marked:
Dallas
Semiconductor
DS1646P-120
POWERCAP
0038GC
121630
Tin, if yours goes dead again, I'd be curious if yours is marked similar...
Jay
-
Mine CSA7404 is still fine.
Also was browsing ebay the other day, and spotted TDS7104 boards for sale, including PPC board.
It had EDIP32 DS1245Y on it :)
-
hi
i used a regular rs232 port
and i got all kind of marks on the rs232 screen
i attached also the vga output
thanks in advance
o.
-
Hi,
Have laid my hands on a tds7104 without hard disk and dead NVRAM battery on PPC board. It has a SU810 m.board with Pentium III 750MHz and 128M RAM . The PPC has also 128M RAM. After installing Win 2K with application v2.5.3 it hangs when starting the application. Diagnostic LED on PPC stays on P. The configutation of the NVRAM looks a bit different compared to the other ones seen in previous posts; it has more parameters?! I configured it the best I could.
There must be an error somewhere but I can't find it. Can someone point it to me? Here is the console dump attached. Thank you for reading.
-
Do you have correct files in hidden folder c:/vxBoot?
Can you attach topScript.hw to check?
-
I have looked over your attached dump file.
There is an Exeption in the last few lines "Exception current instruction address:". I had the same problem (TDS7054).
The solution was to enter " other (o): nvfs=0x0000 " in the PPC configuration (stored in the NVRAM).
This was discoused here: https://www.eevblog.com/forum/testgear/non-booting-defectivetds7054/ (https://www.eevblog.com/forum/testgear/non-booting-defectivetds7054/)
So maybe worth a try :)
-
Yes, it partially helps. Now I got a blinking status on the ppc, but application still hangs. Seems the kernel version does not match boot rom version? (whatever that means?) I am attaching both the ppc dump file and the topScript.hw
Hopefully someone can explain and solve this.
Thanks,
Serge
-
Forgot to attach the files, very tired...
Thanks,
Serge
-
That is very interesting.
My TDS7054 was working fine and after some days its hanging also with a blinking status at almost the same position!
One of the last posts "Kernel version 1.0.8.1 does not match Boot ROM version 1.0.3.0", you can see also in dump filee of correct working scopes!
So this should not be the problem. The next lines in dump, I think describes the problem, what ever it means.
My TDS7054 starts the TekScope app and the Relays are clicking once, then a failure Message pops up (see attached pic).
I will post my dump later today, I'm still at work :(
-
Windows 98? Why not install 2000 at least :)
Try this topscript.hw if it's any different.
Also your config little different than mine, as:
<code>
boot device : sm
processor number : 0
host name : host
file name : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.168.0.2
user (u) : anonymous
ftp password (pw) : anonymous
flags (f) : 0×1000
target name (tn) : target
startup script (s) : c:\vxBoot\dio_rst.vsh
other (o) : nvfs=0×1000
</code>
Direction of dashes ("\") vs ("/") may matter as well.
Also check .vsh file.
-
I did install Windows 2000, then XP and have this problem. You also mention in the configutation a dio_vst.rsh file, I don't have it in the vxBoot folder. The v2.5.5 Tek firmware did not install it. Where did it come from?
Serge
-
Hi everybody,
I worked on my problems with the TDS7054 and I hope that I have found a final solution.
As described I get this DIO.exe "illigal operation" failure, so I decided to install fresh Win2K, cause the Win98 Version was installed in 2001. After installation and get all necessary drivers I started the Tek Scope Software 2.5.5. Everything worked, the scope buttons where on screen, the frontpanel worked correct, but there was no waveforms shown on the screen |O.
In the documents of my scope I found an Win2k updateoffer direct from Tektronix. There was written, to update my TDS7054 the mainboard must be changed :--
So I conclude:
My Scope has the old BL440ZX PC Mainboard with an Celeron 533 Prozessor on it and with this board it isn't possible to run Win2k and WinXP. If anyone knows a solution to run a newer OS on my scope please describe here!
So deeply disappointed I installed WinME (had no 98 install CD and ME supports USB Sticks) on a newer Harddrive.
After insalling all drivers and the TekScope App at least my Scope work fine whitout the DIO.exe failure. :phew:
@ Serge: Have you managed get your Scope working?
schersch
-
Did you install correct Cirrus graphics card drivers? TekScope software using some special access to draw viewforms directly on video memory, not transfer data to GUI app to show. Unless you have proper graphics driver, you will not see waveforms.
-
I installed Drivers for ATI Rage Pro and Chips and Technolgies 6900! These two graphiccontroller should be inside my scope. The Chips and technologies 6900 was a bit hard to find for Win2k, but found one anyway, which worked.
I don't know for shure, but it seems for Win2k there is the need for an SU810 Mainboard :(
-
I was cleaning home lab today and happen to find Intel SU810 board, which I have no use for.
Bought it while ago while was repairing my scope, but did not use.
It have a little corner damage near edge connector, with two pads cut, and I remember that was trying to boot it in my scope, but failed,
so conditions unknown. It's genuine Intel SU810, E139761 so might not be even usable in scope, as my CSA7404 have SF810 board with different layout and NI bridge on it. I can ship it to you for price of shipping (EMS from Taiwan). Also have few CPUs for it, Celeron 850 (128K/100MHz/1.75V), Pentium III 1000 (256K/100MHz/1.75V) coppermines and Pentium III-S 1400 (512K/133MHz/1.45V) Tualatin. I bought two 1400-S CPUs before, and after simple modifications (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg301679/#msg301679) made mine working in scope at 1050MHz with 100MHz FSB clock.
-
Thanks TiN for this thread. I picked up a scope for cheap that the previous owners had clearly tried to repair. It has a new HDD and ram thanks to them. Thanks to your thread, it's back up and running.
Had to put the logic analyzer on the console port :palm:
-
Hey TiN. I used this article to make a TDS 7054 fly back to life. BOY DOES IT FLY! What a beautiful machine.
Thanks for this thread, it will help me pay my tuition this year.
Cheers,
Brad
-
I had a TDS7104 that wouldn't boot anymore and was failing POST on a .A display which is NVRAM failed memory test. The battery for the NVRAM was dead but so was the NVRAM chip itself as it wouldn't read what was written to it. So I replaced the entire Dallas DS1245Y module and PowerCap battery and its come back to life and working perfectly. While replacing the Dallas chip I also bought a spare PPC board that I've also tested and it works perfectly too. Now I have two working PPC boards (Tektronix TDS7104 Scope PPC Processor Board PN G9F-2746-00) so I have one available for sale. If your 7104 needs a new PPC board, let me know. I'm sure someone needs it and I don't any more. Its fully tested and works great.
-
If there's a collection of NVRAM dumps and their options
No need for that, need just little time, as there is way to generate option keys for any S/N :)
I am in progress of writing article for it (also supports not only TDS7k series gear ;))
Hi Tin,
Did you ever write this article or make any progress? I'd love to mess around and add options to my 7104...
Jay
-
Posted (http://xdevs.com/guide/tek_key/) a draft.
I don't have time to finish it up properly, if anyone have wish to help - can list which bit unlocks which option, to create nice little table with respective data.
Also such approach works for TLA gear, but need check first.
-
First of all, a huge thank you to TiN and the rest of you for the information shared here!
I recently got my hands on a failed TDS7104 and thanks to this thread I was able to have it up and running after a 2-evening repair. :D
It was basically the same story as told in post 99 by Gearhd1026 above. Both the NVRAM module and the battery module needed replacing (diagnostic stuck on .A and the console messages reported NVRAM self test failure.)
My unit has the 2M memory option which was re-activated by doing the NvRamClear operation.
Trying the keygen software provided by TiN, I find that I can also get the SM (serial mask) option by entering the flags 020400 (02=2M, 04=SM) but not much else. Filling the remaining flags with 0xff bytes just point to uninstalled apps. Has anybody else had more success? I am uncertain if specific software for the SM option has previously been installed on my unit or if it was activated by the key alone.
-
Great to hear another fix. After unlocking options you will need to install software. Most of it you can download from Tek site.
-
Aha! Thanks TiN, I did not realize that this (old) application software is still available. :)
The unlocking bits for these applications appear from the 7th byte of the option data and onwards.
After trying a few of the apps, I see the need for more speed on the PC motherboard .. so I will continue looking into your suggestions for upgrades. I have already ordered memory DIMMs, as my unit was populated with only 128MB.
-
I have read a lot, but can't figure this out: will a TDS7154 with 850MHz cpu & 512MB ram run XP? I know there are update kits, but I want to know if I could just install XP from a CD and install the Tek software.
-
Seems like it does. I have used another hard drive, but the XP install does feel a little faster. But I think the boot process does take a little bit longer, but not much. After installing Windows XP Pro SP3 from a standard CD the screen went blank. Seems like the wrong video card was used, but I couldn't change anything. It would boot in VGA mode and save mode (F8). After booting in save mode with second monitor to the NLX board all was fine. After installing all drivers the TDS firmware pack worked. For future reference, an unknown USB device needed the USB front panel driver, the other unknown device needed the PPC board driver. After installing the right video driver (2.5.1) the first waveforms showed up.
I still want to try a PIII 1GHz CPU, this might make it feel even faster.
Still trying to fix the inputs. 1 is blown, and rarely works, 2 is OK, 3 is way out of spec and sometimes doesn't work, 4 is slightly out of spec and sometimes doesn't work. At least the ADC's seem to work.
-
It sounds like you're on the right track. I feel like Windows XP is a decent compromise between the fast boot time of Windows 98 with ancient network stack and the slightly longer boot time of Windows XP, but with a much more robust network stack. The official Tektronix Windows 2000 load takes like 5 minutes to boot - nearly intolerable for me. I had an opportunity to conduct some boot timing trials and the boot time difference between 566, 850, and 1Ghz processors is within 15 seconds of each other. It makes a difference, but they're all going to be around the 90 second mark to first waveform display from power-on. I attribute the lack of a more significant variance due to the fact that BIOS initialization time is about the same and a chunk of the boot time is spent downloading and initializing the PPC board, which doesn't change at all. The 100MHz FSB speed to the memory is limiting the faster processors as well.
My biggest problem with the older stock motherboards was that I was unable to find a suitable NIC driver for Windows XP. That's what lead me to upgrading them first thing to the Intel SU810 NLX motherboard for which Windows XP recognizes everything at installation time. There were two different versions of the NLX motherboard tray though, so one needs to determine whether the SU810 will fit the tray in their scope. Otherwise some work with a nibbler tool may be necessary. Which motherboard does your scope have, and were you able to find a Windows XP driver for the NIC?
-
Did you use a normal hard drive or SSD? I usually upgrade equipment with a hard drive to a compact flash card. That at least kills most of the seek times. I have a Tektronix TLA704 with a Pentium-1 200MHz but that doesn't need 5 minutes to boot Win2k.
-
The Windows 2000 experience would have been with the original 4200RPM 2.5" drive, but the comparison to Windows 98 was valid at that time. Per my prior posts in this thread, I later went with Kingspec KSD-PA25.6 PATA 44-pin MLC SSD's as the original drives are becoming unreliable with age even if one wants to withstand their tardiness. That drive will drop right into Tektronix' proprietary drive tray.
-
Im using a standard PATA 40GB Samsung 5400rpm 8mb drive.
I don't know about the mainboard, but I couldn't find a NIC driver for XP too. I thought it may be the boot settings (cmos -r nonet) messing with it
. I guess my boot time is between 1 and 2 minutes until the first waveforms appear. I could probably save some seconds removing unwanted services and removing & disabling everything I don't need.
-
Has anybody ever fixed one of the 50ohm input resistors? They are probably blown, but I cant find them. I would guess they are near the Teledyne input relays. The relays themselves look to be ok. Thats a good thing, as they look to be hard to get and extremely pricey. As the 50 ohm resistor can take 5Vrms it would have to be a 1/2 watt 50ohm or two 1/4 watt 100ohm resistors. At 1,5 GHz I would expect 1 resistor. Should be quite easy to find.
I'm also having trouble with channel 3 and 4 not triggering. Unfortionately I cant find anything about the whole aquisition board / system.
-
Mmm, some photos perhaps?
-
If You can shown the pic maybe its easier to give any sugestion but for working up to 1.5Ghz I believe you need an RF style resistor.
this a 50 Ohm 150w just for example.
http://www.rfparts.com/dummy-loads/dummyloads-surface/tg150-50.html (http://www.rfparts.com/dummy-loads/dummyloads-surface/tg150-50.html)
-
Here we go:
(http://i.imgur.com/q6KaAj5.jpg)
1. Bottom CH 1 and 2
(http://i.imgur.com/RYI87cw.jpg)
2. Bottom middle
(http://i.imgur.com/YDvwohA.jpg)
3. Bottom CH 3 and 4
(http://i.imgur.com/VkoaX98.jpg)
4. Top CH 1 and 2
(http://i.imgur.com/Mx64Xp5.jpg)
5. Top middle
(http://i.imgur.com/IHVhF56.jpg)
6. Top CH 3 and 4
(http://i.imgur.com/91LVDV2.jpg)
7. Bottom close-up
(http://i.imgur.com/sbf5nRP.jpg)
8. Top Close-up
Top is top as seen by the machine, NOT the PCB.
-
May be those 4 resistors that look that they are in parallel, one set per channel? R1140, R1141,R1142, R1143 and R1240, R1241. R1242, R1243 :-//
-
Nope, looked at that already. Could it be possible the resistors placed in the ADC? Input impedance is 50Ohm +/- 2,5%, which I thought was odd for such a high end device. An internal resistance (in an ASIC) would of course be more difficult to match precisely than a "simple" SMD resistor.
-
Nope, looked at that already. Could it be possible the resistors placed in the ADC? Input impedance is 50Ohm +/- 2,5%, which I thought was odd for such a high end device. An internal resistance (in an ASIC) would of course be more difficult to match precisely than a "simple" SMD resistor.
Some of those Teledyne relays may have the resistors internal to the relay, they refer to them as attenuator relays. I know that this is the case on Agilent 54831B and 54832B scopes... See attached pdf for Teledyne A150 series which are on the Agilent scopes I mentioned. One of them is actually custom made for Agilent IIRC. Good luck!
Jay
-
Pretty possible as resistors are in relays, as they have to work not to 1.5GHz but to 4+GHz, as top of the line TDS7404 uses same ACQ board, or almost same, and TDS7704B is very similar.
Or it could be those square thingy's on rigid lines in thermal shrink, but that's just ferrite bead likely to be.
Here are some photos of TDS7704B guts:
(http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_1_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_2_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_2.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_3_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_3.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_4_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_4.jpg)
(http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_8_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_8.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_5_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_5.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_7_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_7.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_6_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_6.jpg)
(http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_9_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_9.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_10_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_10.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_11_1.jpg) (http://doc.xdevs.com/doc/Tektronix/TDS7704B/photo/tds7704b_11.jpg)
-
Pretty possible as resistors are in relays, as they have to work not to 1.5GHz but to 4+GHz, as top of the line TDS7404 uses same ACQ board, or almost same, and TDS7704B is very similar.
Or it could be those square thingy's on rigid lines in thermal shrink, but that's just ferrite bead likely to be.
I believe your second guess is correct - I think those are ferrite beads as well. They look similar to Agilent 54835A and 54845A rigid lines from the attenuator assemblies.
Smith, I can't see the relays well enough to get a part number. Maybe that would help.
Jay
Sm
Jay
-
They are Teledyne RF170 - 0015 relais. BTW they are not 15V, they are 5V (~60 ohm coil resistance)
-
They are Teledyne RF170 - 0015 relais. BTW they are not 15V, they are 5V (~60 ohm coil resistance)
Naturally, that part number isn't in the pdf. :palm:
Jay
-
A little help please, I have on road a TDS5052B without probes, I have seen two new N2890A Agilent passive probes with same characteristics as Tektronix P5050.
My question, Will I get a good result with N2890A Agilent and Tektronix TDS5052B?
-
Still nothing found for the inputs, but I do got the network driver working under XP! It's on the Intel SU810 mainboard. I have searched the internet for hours, nothing worked. I saw other people having this problem too, so I was already looking for a USB / PCMCIA card. Turns out there was a driver map on the original Win98 HDD. Turns out the network driver map has a WIN 2K or XP compatible driver. The machine is running windows update right now!
-
Well, not much progress. Couldn't enable any of the options with TiN's keygen. The original key (with no options) validates ok, but the Tek software won't accept any new key created. Ill look into that some other time.
Channel 3 is now within 5% of the other channels reading. Been switching manually (with a 5V PSU) and comparing channels, and the resistance of the relay near the ADC's was 85 instead of 50ohms. Soldered in some parallel resistance and now it's close to 50 ohm. Strange thing is, it has to be a few ohms lower than other channels to be within spec. Guess it won't do 1,5GHz no more, but at least it should be usable in lower frequency ranges.
Channel 1 is still a showstopper. It has a 280mV offset on the ranges of 50mV and lower. Offset is the same on all ranges. Input will not produce any decent measurement. With an 1kHz 1Vpp signal I can see something superposed on the 280mV offset on the lowest ranges although roughly 200times lower than expected.
This messes up the SPC, so it wont remember its settings. It just says fail, and all channels on every range seems to have zero offset, except for the lower ranges of channel one (the 280mV offset).
I guess I could replace the relays with standard RF170 relays and place my own (quality) resistors in parrallel, but I cant seem to get these relays anywhere. Tried desoldering one of them, but the 12 layer board will take some more work than a standard desoldering gun.
-
Progress again: switched the Copermine Celeron 850 for a Tualatin Celeron 1200 (256kb, 100MHz fsb) with the same mods as tin posted on page 1. Runs fine at 1200MHz at 1,51Vcore.
I was looking at the mainboard, after seeing moreproblems with bad caps. I replaced the two caps (1500 and 2200uF 6,3V. The last one was completely dried out and was bulging up and down. While I was there I also placed a dip socket for the DS1245 NVRAM.
-
I just bought a TDS7404B which boots to Windows 2000, but Tekscope freezes on the splash screen. I've tried reinstalling Tekscope without change. So far, I haven't seen any obvious problems.
The PPC board's diagnostic LED only shows "8." which never changes at any point. The PPC board does show up in the device manager. Could this be an NVRAM problem?
-
Sounds very like it :) Try to see if your NVRAM settings correct, if they are not - you know what to do. :-+
How you all guys solving probe situation on these scopes (ones with proprietary TekConnect ports, not BNC) ?
BNC adapters cost relatively a lot, and they don't allow high-impedance inputs either.
-
Yeah, that's a bummer. The tca-1meg (or something like that) easily go over a grand on ebay. With 4 channels that's a lot! I personally am thinking about building some simple few MHz preamplifiers with buf634 or something like that for basic every day use. Personally I don't need that GHz speed, and if I do, it will take some good active probes, so that problem is solved.
Still looking at my scope. Yesterday I looked at the acquisition board with a thermal camera. Three op-amps where I think the trigger circuit is idle at 40C, and then one of them ramps up over 100C in a few seconds when the first waveforms appear. Probably it's oscillating. There are 3 of them in a row, and the other 2 just keep working at ~40C. Maybe that's the reason the trigger on channel 3 and 4 are not working. I'll replace it and see what happens.
-
Also make sure to check the supply voltages on the opamps.
-
One other issue is that the Windows 2000 OS is in pretty bad shape. It takes about 15 minutes to shut down and various tasks that have to be forced to end. That's even after upgrading the RAM to 2GB and CPU to a 3.06 GHz P4.
Does anyone have an image of the 2000 (or better yet, XP) restore disc they could share? It has an Intel D845GVAD2 motherboard.
-
I dont know about the 7000B series, but this is my experience with my 7000 series: I had no recovery CD, just the old Win98 HDD and some drivers from the internet. I placed a new (bigger and faster) HDD, and just installed WinXP from a XP Prof SP3 CD-Rom, installed the drivers, and installed the latest firmware (The tools package, this includes the scope program) from the Tek website. Did windows update, and now everything runs fine! XP runs that much better than Win 98/2K. You might even be able to run Windows 7. Your HW should be able run Win 7 without problems, but be sure to check if your SW supports Win 7.
I did get some CMOS tools from the old hdd, as I was unable to find it anywhere. This was it.
-
I dont know about the 7000B series, but this is my experience with my 7000 series: I had no recovery CD, just the old Win98 HDD and some drivers from the internet. I placed a new (bigger and faster) HDD, and just installed WinXP from a XP Prof SP3 CD-Rom, installed the drivers, and installed the latest firmware (The tools package, this includes the scope program) from the Tek website. Did windows update, and now everything runs fine! XP runs that much better than Win 98/2K. You might even be able to run Windows 7. Your HW should be able run Win 7 without problems, but be sure to check if your SW supports Win 7.
I did get some CMOS tools from the old hdd, as I was unable to find it anywhere. This was it.
I'll give that a try. I was never able to get a generic Windows installation to work properly on my TDS5054 (problems installing the drivers for the acquisition board). Since this is newer, it's possible the drivers are better.
-
Windows did not include the drivers for the ppc board and front panel. I downloaded the drivers mentioned earlier on this tread.
-
Windows did not include the drivers for the ppc board and front panel. I downloaded the drivers mentioned earlier on this tread.
When I tried to to a clean Windows installation on my 5054, I used the drivers contained in the "Tektronix" dir on an official hard drive image. I was never able to get the acquisition board drivers to install properly. It doesn't seem to be fully plug & play, and I was getting various errors in the device manager. Even after finding an error free combination, Tekscope still didn't detect the acquisition board.
Back to the 7404B... I pulled the Dallas NVRAM, and it still has valid looking data, so I don't think the battery is dead. While I had the PPC board out, I did a little probing around with an ohm meter, and I noticed that the PPC reset button measures 775 ohms across it. That seems low, so I will start by checking the reset line when I put it back together. My flexible PCI extender cable will come in handy here since the ATX board sits directly on top of the PPC board.
-
How did you determine that NVRAM have correct data? I'd suggest use serial console to check all parameters.
-
How did you determine that NVRAM have correct data? I'd suggest use serial console to check all parameters.
It's not blank as I would expect if the battery was dead, and I can see the location of the vxworks boot files in plain text, so it's not full of garbage.
The reset button seems to be working fine (at least there's 3.3v on the reset button). There's absolutely no activity on the console port. Both TX lines are flat from power on, all the way until the scope application hangs.
I've checked all the power supply voltages that are listed in the manual, and all the DC voltages on the PPC board look reasonable with none that are obviously missing.
I did a little probing around the PPC board with an oscilloscope, and I can't find any activity. Even the DS1245 has nothing on any of the address, or data lines (all high). Even the chip select and output enable pins are high.
-
The console port should be outputting data from the second it starts. A standard mainboard com port "breakout cable" works great. You could try probing the TTL pins of the max232. Maybe its defective.
What do you see on the seven segment display next to the console port, any progress on that?
You might want to reset your CMOS from the mainboard too, cant hurt anything.There are 3 eprom/flash chips on my ppc board probably on yours too. Maybe you can check these for activity? Small chance, but could the sdram memory be defective?
-
There's nothing going into the MAX232.
The 7 segment shows 8. constantly.
I have probed the socketed 29LV040, but I see no activity. I'll take a look at the others later. I guess clearing CMOS can't hurt.
Swapping the 512MB DIMM on the PPC board was the first thing I tried.
I've scoped out dozens of random test points around the PPC board, and I've only seen DC voltages apart from the various crystal oscillators.
I think I need to focus on the PPC chip itself and see if I can verify the basics such as power supply, clock, and reset based on the datasheet.
How long after power on should it take fro the PPC board to show signs of life on the 7 segment, or console port? Does it boot from the hard drive before, or after Windows boots?
-
I think I need to focus on the PPC chip itself and see if I can verify the basics such as power supply, clock, and reset based on the datasheet.
I would follow that strategy also... Check whether the basic conditions for the CPU to run are there.
-
How long after power on should it take fro the PPC board to show signs of life on the 7 segment, or console port? Does it boot from the hard drive before, or after Windows boots?
As far as i can remember the 7 segment display runs from the moment it starts booting. The last stage (running the software and viewing the waveforms appear) it shows a blinking "-".
The console port runs from booting, about until the waveforms appear. They also show info when calibrating, doing SPC, self check etc.
I'm still working on mine, it still has issues. Last week all inputs stopped working until I turned it on again. I'm re-soldering the press fit connectors for the data bus, just in case. The case had a mayor impact before all these issues started (long before I got it). Took me ages to get the frame kind of straight. It was hit on the corner besides the connector, and some connections weren't looking very nice, it looked like the solder around these pins was dented and cracked on some places. They are a pain to solder. Already done the PCB interfacing the PPC and acquisition board, just have to do the PPC and acquisition board.
At least I got the main board caps fixed and the NVRAM will be replaced soon. Switched from Win98 to XP pro, new CPU and HDD, the computer runs fine now. Voltages look OK to, just found some distortion on the +/- 15V supplies, probably due to oscillation in one of the opamp (wich runs at a comfortable 110C).
-
The Tek TDS5052B (2004) does not lead NVRAM uses CMOS Flash PLCC32 welded directly to the board.
The Boot is in a CMOS eprom and options trading in a CmosFlash.
AMD uses 32pin memories, pa 3M optio would need to replace the U1320 16MB ?? but never fabricate memories PLLC32pin AMD 16MB?
U2.....unlocated on board???....... IC, Memory; CMOS EEPROM; 2K, 256X8, 2.5V.......Stores touch screen calibration alignment data
U720...PCI board.........Xilinx XC18V01...... IC, Memory, CMOS PROM 1 M.....Program PAI FPGA at boot up
U1320...PCI board...... AMD AMLV010b.......IC, Memory, CMOS, FLASH,
128 X 8 bit.......Option Key, Event Log, IO Processor Code, Fan Cal Constants
U1800...Acquisition board.....????......IC, Memory, CMOS EEPROM, 2 k X 8...Calibration Constants, Probe Data
U400.... PCI board....AMD AM29LVo10B....IC, Memory, CMOS, FLASH 128 X 8 bit..... ????????
U1501.... back PCI board....AMD AM29F010B....am29F010B
1 Megabit (128 K x 8-bit)CMOS Flash.....?????????
-
Just in case anyone needs drivers for TDS7000/TDS7000B/CSA7000/CSA7000B series scopes:
Display driver from TDS7000B/CSA7000B (http://xdevs.com/test/Tektronix/Tektronix_7000/Chips and Tech display V.2.50G.rar)
USB Front Panel driver for TDS7000/7000B/CSA7000/7000B (http://xdevs.com/test/Tektronix/Tektronix_7000/Front Panel V.1.0.rar)
PowerPC board driver for TDS7000/7000B/CSA7000/7000B (http://xdevs.com/test/Tektronix/Tektronix_7000/Tek PPC Driver Win2K.rar)
Sadly all of these links are now dead.
Anyone still got the drivers?
-
Fixed, server had upgraded storage array, forgot symlink to /test URI.
All these links back now.
-
Hi,
I recently picked up a TDS 7054 without the HDD, and this had almost the same issues as the one posted here earlier(the battery on PPC board was dead). Thanks to the post, I was able to replace the battery and set boot parameters through the serial port.
But when the PPC board tries to boot, it hangs when the message from serial port shows "Backplane anchor at 0x1e80000... Attaching network interface sm0... done" and the 7seg shows "L".
I installed Windows 2000 Professional, TekScope, and tried to install the drivers posted here and successfully installed two of them but when the PowerPC board driver was installed the OS displayed BSoD on dblib.sys and it is disabled now. Does this mean that the PPC board is broken?
I would like to hear any ideas..., and please tell me if I did something wrong because this is my first post.
Thanks in advance.
-
Downloaded current BIOS From CSA7404:
Tektronix CSA7404 Intel SF810 motherboard BIOS dump (http://doc.xdevs.com/doc/Tektronix/CSA7404/firmware/CSA7404.BIN) - CRC32 Checksum: C357A520
(http://xdevs.com/doc/Tektronix/CSA7404/firmware/csa7404_bios.jpg)
-
I think I need to focus on the PPC chip itself and see if I can verify the basics such as power supply, clock, and reset based on the datasheet.
I would follow that strategy also... Check whether the basic conditions for the CPU to run are there.
Here's an update on my dead PPC board for my TDS7404B. I'm powering the board with a standard PC ATX power supply connected to the socket that normally provides power to the PC motherboard. This allows much better access to the PPC board for troubleshooting, and provides all the needed voltages.
The problem seems to be with the reset circuit. Almost all of the reset pins that I can identify are low. This includes the PPC CPU, memory controller, Intel PCI bridge, Intel LAN chip, and NI GBIB chip. Also, the OE# and CE# pins for the PPC BIOS are high. I've verified clock and power to all the major parts. Apart from that, there is absolutely no activity anywhere on the PPC board.
I'm gradually verifying everything I can trace, but it's not easy with all the hidden traces, and some difficult to identify parts around what I think is the reset circuit. I've tried manually changing the reset lines I have identified to the high state, but so far there has been no sign of life. I don't think anything is dragging the rest line down because each chip seems to have its own independent reset signal. I could probably find the problem in 10 minutes if I had a schematic...
Does anyone know anything about the reset circuit? I'm assuming it's generated on the PPC board, but someone correct me if it might come from the acquisition board, or some other location. Does Tektronix have any favorite reset generator ICs that I should look for?
-
Have you looked into powergood from onboard DC-DCs? Usually on PC hardware like motherboards and videocards powergood from onboard bucks driving resets to ensure correct ramped voltages and proper power sequence. Might be same case here.
-
Have you looked into powergood from onboard DC-DCs? Usually on PC hardware like motherboards and videocards powergood from onboard bucks driving resets to ensure correct ramped voltages and proper power sequence. Might be same case here.
That's a good point which I hadn't considered. The ATX PC board must be getting a valid powergood signal since it boots, but I don't know about the PPC. It's a new starting point that might lead somewhere.
-
there so many nlx bords models with different chipsets , the firmware of x86 board is standard or custom? tried to backup it?
-
Fixed NVRAM again :)
test (https://www.youtube.com/watch?v=Qx02R9OX98E)
-
Fixed NVRAM again :)
test (https://www.youtube.com/watch?v=Qx02R9OX98E)
Hi Tin,
Since you've replaced the battery not too long ago, you may have a bad NVRAM that uses excessive current.
See page 6 reply #78 and #82 of this thread when I asked you about this observation I had on a CSA8000 I had worked on. Might want to do some current measurements - I reworked a snap-on battery by removing the battery and adding wires to do testing outside of the chassis since it's a PITA to get to.
As a side note/rant, why the fuck do T&M manufacturers put such critical data in battery backed RAM when flash has been around for 20+ years? :-BROKE
I remember working on a plug-in for the HP 70004A mainframe (don't remember which one - sorry) that actually put the *firmware* in SRAM! |O
The battery was dead, and so (of course) was the plug-in. So sorry, no longer supported by Agilent.
*sigh*
Jay
-
I measured current with new NVRAM, it was about 4uA. I guess high current issue was there in old NVSRAM, as it sucked battery within few month before. And then it was not storing/corrupting data even with fresh bat, so that's why I replaced chip.
-
Beautiful, thanks for sharing :)
-
Hi
planning to recap my 7104 but some of caps (especially the smallest c908 etc..) cannot read values there is a pic with map of capacitor values
or schematic of martek psu? thanks
-
Sorry, don't have it, and I'd rather not take my scope apart, currently using it at sick 3458a.
-
Im restoring a TDS7404. There's some conflict with both PCMCIA controllers (Ti PCI-1225 cardbus controller, vxWorks.st wont load) on the Win2000 install, but on XP install one works so vxWorks loads, the tek app runs, but there some thing still wrong with pci bus cause the NVram can't read anything from the hdd. Diagnostics passes on all tests, only fails at misc with: 531. That means it's out of cal and the SPC also fails cause it can't write into the NVRAM) Could this be some kind of hardware or software problem ?
Update: after a Bios reset, the win2k install kept getting BSoD on startup (dbwdn.sys cannot load). But the Xp install finaly has no hardware conflict what so ever, yet the probelm that the NVRAM can't read from Hdd still consists.
Solution: well turns out there where some files missing or had wrong format, after clearing nvram db, rewriting eeprom bios and setting up new db, now it works !
-
I just got a TDS7404, inspired by this thread! Hopefully I am not in over my head. Luckily it works, well, two channels anyway. I have some basic questions:
1. It's running W98SE. How far is it sensible to upgrade the OS? I'd like to at least go with W2000, but if XP will run ok might try that.
2. What preventative maintenance things should I do once inside besides the obvious - change mobo battery, clean dust...
3. Any obvious things to check on the two dead channels? I guess I have lot of manual to read through, not even sure how to run the SPC test. I don't have a PS/2 keyboard and mouse yet, just been poking at the screen.
Thanks for any pointers.
-
Win2000 works fine and probably is the best choice. Probably the fastest and most stable version there is, anyway. We have good success (months of daily use) with a Transcend TS32GPSD330 SSD to replace the (failing) HDD.
I would give the electrolytic caps on the PC board a good look. We have a 7054 at work with its one Lelon Crapacitor having failed, causing all sorts of strange behaviour. Power supply and Acq board use high quality capacitors exclusively. Also remove the CPU heatsink, clean and apply new thermal grease, it was dried out and crumbly on ours.
-
Thanks for the tips Robert! Amazingly didn't have a torx set anywhere at work, so will take one in from home today so I can open the case. The HD is definitely a worry, IBM Deskstar, so that needs to be replaced ASAP. It only has 256MB, so I will have to find some compatible memory and get that to 512. Will definitely survey the caps once its apart.
Ran all diagnostics, everything passes but SPC. Channels 3-4 trigger, channel 2 won't trigger but can show a waveform. Channel 1 just low level noise regardless of input. 2-4 can show 170 ps risetimes from the fastest pulse source I have, so not bad considering. All knobs seem to work, all the basic software functions, CD, ethernet, VGA out. Haven't tried the GPIB or parallel ports but will soon. Overall looks like a good buy.
Will try W2000 pro on the SSD you suggest once I get them.
-
Overall looks like a good buy.
I wouldn't say *that* until you get it working, unless you got it real cheap! ::)
Jay
-
Ran all diagnostics, everything passes but SPC. Channels 3-4 trigger, channel 2 won't trigger but can show a waveform. Channel 1 just low level noise regardless of input. 2-4 can show 170 ps risetimes from the fastest pulse source I have, so not bad considering.
Check U1801, on the Acquisition board for discoloration and or bumbs, atleast that chip should be responsible for ch1-2 triggering (atleast i have a same model with similar problem, still trying to source the part and or searching for donor boards it's used in TDS6K / 7K and TDS694C )
-
matyco- That chip looks ok on mine. I will try to attach pics, but this is my first time doing so on this forum so maybe it shows up as first one below?
The channel 1 no signal issue turns out to be at least partially obvious (see 2nd pic, blown trace). Obviously could be other problems, I haven't tried repairing the trace yet to see what happens. Focusing on the pc and software upgrades for now. I am hopeful since CH1 does show noise, baseline not offset or jumping, but yeah it will be a huge chunk of luck if its just the trace.
By the way, a LOT of the chips on the acq board run really hot, like burn your fingers if you touch the heatsink. Is that normal? The fans don't really direct any flow down there, kind of bothers me.
PC upgrade status:
CPU was a snap, the SL5VQ, new thermal paste of course. Fired right up and works fine. I *might* be getting a second one of these, if so, will send it on to whomever wants it for their scope. Long story, but essentially it was a bit of a pain finding them, first place cancelled, and buying 2 from the next buyer was only marginally more than 1. But 1 of the 2 shipped turned out to be wrong CPU, they are sending the correct one. Anyway this was a low-skill drop in upgrade, well worth it.
RAM I am stuck on, have to order something different. See third pic - these are 256MB 133, PC won't even POST with them in (EDIT - will POST if I leave OEM in 1st slot, but the additional RAM still won't be recognized). Did I miss a spec? Maybe they need to be CL2 or something?
SSD works fine. W2000 SP3 installed easily, but then ran into sudden shutdowns. Couldn't tell exactly what was causing them, but shut down audio, ethernet, and PCMCIA to free their IRQs and it seems to be OK now. Installed the video and front panel drivers and the PPC server, and tekscope. Unfortunately it gets to the splash screen and ... stops. Task Manager shows "WindowsScopeSer" taking 99% of CPU. If I leave it for a long time it crashes out and tells me it needs to reboot. I tried some rounds of uninstall/reinstall to see if the order matters and no good.
-
Overall looks like a good buy.
I wouldn't say *that* until you get it working, unless you got it real cheap! ::)
Jay
It was cheap enough that even as a 2 ch win98 4GHz scope out of calibration it was a good deal. I was expecting it to show up barely functional. Someone's already offered me more than I paid for it, as-is.
But yeah, it will be sweeter if it can be running on 2000, and I can eventually trigger and use the other channels.
-
RAM I am stuck on, have to order something different. See third pic - these are 256MB 133, PC won't even POST with them in (EDIT - will POST if I leave OEM in 1st slot, but the additional RAM still won't be recognized). Did I miss a spec? Maybe they need to be CL2 or something?
What type of motherboard is in your scope? Usualy these are limited to FSB 100Mhz
SSD works fine. W2000 SP3 installed easily, but then ran into sudden shutdowns. Couldn't tell exactly what was causing them, but shut down audio, ethernet, and PCMCIA to free their IRQs and it seems to be OK now. Installed the video and front panel drivers and the PPC server, and tekscope. Unfortunately it gets to the splash screen and ... stops. Task Manager shows "WindowsScopeSer" taking 99% of CPU. If I leave it for a long time it crashes out and tells me it needs to reboot. I tried some rounds of uninstall/reinstall to see if the order matters and no good.
What character code is displayed on the PPC board? "P" ? Check the rs232 console and post the message log.
-
RAM I am stuck on, have to order something different. See third pic - these are 256MB 133, PC won't even POST with them in (EDIT - will POST if I leave OEM in 1st slot, but the additional RAM still won't be recognized). Did I miss a spec? Maybe they need to be CL2 or something?
What type of motherboard is in your scope? Usualy these are limited to FSB 100Mhz
SSD works fine. W2000 SP3 installed easily, but then ran into sudden shutdowns. Couldn't tell exactly what was causing them, but shut down audio, ethernet, and PCMCIA to free their IRQs and it seems to be OK now. Installed the video and front panel drivers and the PPC server, and tekscope. Unfortunately it gets to the splash screen and ... stops. Task Manager shows "WindowsScopeSer" taking 99% of CPU. If I leave it for a long time it crashes out and tells me it needs to reboot. I tried some rounds of uninstall/reinstall to see if the order matters and no good.
What character code is displayed on the PPC board? "P" ? Check the rs232 console and post the message log.
It's an SF810 mobo. I thought the 133 memory should work fine at 100MHz FSB since it's a rating. Also TiN seemed to get by fine with this. Anyway, I got a couple of sticks of exactly the original RAM and it is now working with 512MB.
Still stuck on the W2k+SSD. W98 on old drive still runs fine. Here is what I get from the console:
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.4.0
Creation date: Nov 2 2000, 11:03:34
Press any key to stop auto-boot...
1
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
Then nothing.
-
Do you have all the correct files in vxboot? Also I'm not exactly remember, but shouldn't folder name be vxBoot? Perhaps it's case sensitive?
-
I compared with old W98 install and two files were missing from vxBoot directory - .key and .sn. They just have the option key and serial of the instrument in a particular format, identical to what is printed on the back cover. Copied the files over, but no luck, it still stops at the same place. Did I miss a step?
Forgot to mention above PPC led stops at "L".
-
Forgot to mention above PPC led stops at "L".
If it won't change to P, that has something to do with wrong parameter boot setting or some other PPC related problem (some odd driver, IRQ) Try to change bios settings for IRQ, and check PCMCIA drivers (atleast i had similar trouble with those one time)
-
Yep, should be P and then change to dash "-" after vxWorks init done. All parameters are case sensitive, check them
-
My TDS7404 is showing the blue screen of death (0x0000007B saying Inaccessible_Boot_Device) when it boots up. :(
I wonder if the NLX battery needs to be replaced, or does the blue screen of death portends to something more sinister that may have gone wrong? Any help would much be much appreciated.
-
My TDS7404 is showing the blue screen of death (0x0000007B saying Inaccessible_Boot_Device) when it boots up. :(
I wonder if the NLX battery needs to be replaced, or does the blue screen of death portends to something more sinister that may have gone wrong? Any help would much be much appreciated.
Not the battery. Stop 0x7B is indicative of a disk drive or disk controller issue.
Jay
-
Thanks the tip. I was hoping it wouldn't that difficult. Darn.
I will remove the case and see what the indicator says. Will keep you posted.
Happy Holidays!
-
jaywye,
If you're going into the case anyway, one simple thing to try is take the HD out of the caddy and plug it directly into the IDE cable. Ii learned this by switching HDs several times after which the adapter on the caddy got damaged and now I get a no OS error with HDs that otherwise work fine connected directly.
TiN and matyco,
Still trying, thanks for the pointers. Have all the vxboot files there and capitalization checked and fixed where needed. I believe the problem is in the drivers/IRQ, trying to narrow it down and find everything. For sure there is a problem in ethernet and maybe pci bridge. Paid work keeps getting in the way so slow progress.
-
Thanks the tip. I was hoping it wouldn't that difficult. Darn.
I will remove the case and see what the indicator says. Will keep you posted.
Happy Holidays!
One thing to try and easy as well - disconnect the CD-ROM data cable. It could cause problems on the ATAPI bus.
Another thing - I don't remember whether DMA should be anabled in the BIOS for IDE devices. If it's set to enabled, try setting it to PIO mode.
What is the serial # of your unit? I may have a Ghost image...
Jay
-
Thanks the tip. I was hoping it wouldn't that difficult. Darn.
I will remove the case and see what the indicator says. Will keep you posted.
Happy Holidays!
One thing to try and easy as well - disconnect the CD-ROM data cable. It could cause problems on the ATAPI bus.
Another thing - I don't remember whether DMA should be anabled in the BIOS for IDE devices. If it's set to enabled, try setting it to PIO mode.
What is the serial # of your unit? I may have a Ghost image...
Lastly, if running the scope with all the covers off, make sure you direct a fan over the ACQ board!!!
Jay
-
If I buy a TDS/CSA8000 that won't boot at all, is there any way of getting hold of a replacement disk drive image?
-
If I buy a TDS/CSA8000 that won't boot at all, is there any way of getting hold of a replacement disk drive image?
http://www.jvgavila.com/csa8000.htm (http://www.jvgavila.com/csa8000.htm)
-
Hi Jay (Jwalling),
I have found a system restore CDs for my TDS7404. I did a system restore, and it seems that the physical media has failed. So, I am going to replace the hard drive soon.
In the meantime, if anyone needs a system restore CD for their TDS7000 series scope, let me know. I should be able to help.
Thanks,
-jeremy-
-
I had some CD images too:
TekScope_Opt_App_071-1078-25_063-3478-25 (https://xdevs.com/doc/Tektronix/TDS7000/TekScope_Opt_App_071-1078-25_063-3478-25.7z)
TekScope_Opt_App_1.0.10_071-1883-01_063-3914-10 (https://xdevs.com/doc/Tektronix/TDS7000/TekScope_Opt_App_1.0.10_071-1883-01_063-3914-10.7z)
Did not install these myself, but should be legit. (I just installed standard Win2000, installed TekScope software, drivers, and that's it, it worked from then).
-
I had repaired and upgraded a TDS7104 using the excellent info on this thread. It has been working perfectly for months, but just yesterday a very strange fault occurred.
When the record length is set <= 2000 samples, everything works perfectly. As soon as I set the record length > 2000 samples, all the traces simply disappear and the scope responds very slowly to changes in settings. The Windows UI and front panel LEDs etc are still responsive, but the trace and trigger markers move very slowly.
Weirdly, slightly larger record lengths (up to 5000 as far as I can tell) appear partially when I enable horizontal zoom. (See attached picture for a screenshot of this behaviour - notice the trace is invisible in the top window). Without zoom enabled the trace is invisible.
Enabling FastAcq also induces the same fault symptoms.
The fault first occurred when I was using the scope as normal, record length was some large value. Suddenly all the traces froze and the scope became unresponsive. I rebooted and it is now permanently as I described.
I have tried restoring default settings, reinstalling the TekScope software and using an old, previously working hard drive. This has made no difference. Diagnostic test returns all pass, supply voltages all good, NVRAM battery is fresh.
I am running Windows XP with a SU810 motherboard, which I upgraded from the original Bl440ZX/Win98, but it has been working perfectly with this configuration for months.
It almost seems to me like some kind of display rendering issue when there is more than a certain number of points on the screen. Don't know what to make of that though...
I can't make any sense of this. Has anyone else seen this problem? Does anyone have any ideas for how to even begin troubleshooting this? I'd be very grateful for any ideas.
-
I'm still working on my TDS7404B with a powerPC board that seems to be stuck in reset. I was given a tip that it stays in reset until the driver is loaded. Can anyone confirm this? The original drive boots, but it's definitely got some problems. Windows 2000 is running very sluggishly, and it won't shut down fully. I'm going to attempt a clean Windows install, but if anyone has the TDS7000B OS restore disc and would be willing to share a copy, I would prefer that.
If my TDS5054 is any predictor, doing a clean installation and getting the drivers to install properly is difficult or impossible. Every time I've tired with that scope, I get various device conflicts, code 10's and a non working scope. Fortunately, I have a working image for the TDS5000.
-
Joined the TDS7000 club! A very kind friend offered up a TDS7104 that has a few issues and is beyond disgusting inside(so much brown dirt not a single part # on a chip is readable). The BNC's on the front are also green in color with corrosion. Supposedly it came from a motherboard manufacturer in Taiwan.
The nvram powercap battery is dead of course but it seems I also need a new nvram so I ordered one tonight:
romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...
Expected Value: 0x00000001
Actuall Value: 0x00000000
Location: 0xFD0E0000
romPost: NV-MEMORY Walking-one test failed.
Oh the joys of windoze 98 and 128 mb of ram - at least that part boots fine. Assuming it all starts working I'll looking mb, HD and OS upgrades.
-
Joined the TDS7000 club! A very kind friend offered up a TDS7104 that has a few issues and is beyond disgusting inside(so much brown dirt not a single part # on a chip is readable). The BNC's on the front are also green in color with corrosion. Supposedly it came from a motherboard manufacturer in Taiwan.
The nvram powercap battery is dead of course but it seems I also need a new nvram so I ordered one tonight:
romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...
Expected Value: 0x00000001
Actuall Value: 0x00000000
Location: 0xFD0E0000
romPost: NV-MEMORY Walking-one test failed.
Oh the joys of windoze 98 and 128 mb of ram - at least that part boots fine. Assuming it all starts working I'll looking mb, HD and OS upgrades.
By any chance, is your NVRAM the one with the snap cap battery and in an SMD package? I just repaired a TDS7404 that was failing the walking one test. It's not the first time I've replaced one of these chips either; last year I replaced one in a CSA8000. If you're feeling brave, you can replace the SRAM on the underside, I believe. Cost is only a couple of bucks instead of $50 or more. I haven't tried this method yet, but I kept the defective chips and the next time this comes up I'm going to attempt this instead.
Jay
-
Yes, it is the snapcap SMD package. I have already ordered it and it has been shipped so I am getting one either way. For other people with the same problem it appears swapping it has fixed the problem. Swapping out some ram at the same time may not hurt though.
-
Yes, it is the snapcap SMD package. I have already ordered it and it has been shipped so I am getting one either way. For other people with the same problem it appears swapping it has fixed the problem. Swapping out some ram at the same time may not hurt though.
I'm beginning to think that Dallas/Maxim had a lot code problem with these. My defective one that failed the walking ones test is marked:
DS1245YP-100
0035GC
120052
Philippines
Now that I think of it, I also replaced one in the last several years that would draw excess current on the battery when in standby mode. I mentioned it in this thread, I believe. What are the markings on your bad chip, if I may ask?
Jay
-
Yes, it is the snapcap SMD package. I have already ordered it and it has been shipped so I am getting one either way. For other people with the same problem it appears swapping it has fixed the problem. Swapping out some ram at the same time may not hurt though.
I'm beginning to think that Dallas/Maxim had a lot code problem with these. My defective one that failed the walking ones test is marked:
DS1245YP-100
0035GC
120052
Philippines
Now that I think of it, I also replaced one in the last several years that would draw excess current on the battery when in standby mode. I mentioned it in this thread, I believe. What are the markings on your bad chip, if I may ask?
Jay
Mine is:
DS1245YP-100
0131HH
301963
Philippines
I notice this one has a Dallas DS13D12 non-volatile controller on it as well as the ram chip. The newer ones look to only have a single chip. My replacement should be here Saturday.
-
New (but very old stock) nvram arrived today. It was made in 2002 so it should feel right at home in the scope. Did the NVRAM programming and powered the scope up. It booted as expected and all looked good until I tried the horizontal control. It was 99% dead, 100 rotations might get it to change one time. This was actually a bit of a relief as there was a sharpie written "X H" written above the channel 1 input. I had feared it meant channel 1 was bad but it obviously indicated the horizontal control was bad. I removed the horizontal rotary encoder and carefully opened it up. I polished the silver traces with an eraser, cleaned with alcohol and reassembled. It is as good as new! All self tests pass as does SPC. So it seems all of the basic hardware is now working fine. There is still hours more work cleaning the unit. I have already spent more then an hour with a compressor cleaning the boards. Even 80 PSI wasn't enough to get the dirt/debris off the boards. I had to lightly brush them as well. I normally use an ESD safe vacuum to clean boards but it was pointless. The LCD screen is also separated from the touch screen panel so I need to reattach them and hopefully get the alignment better. Right now the touch screen is a good 5 mm off in the horizontal direction.
So far I am very pleased. I will be ordering an SSD, 512 megs ram for the each of the boards and a faster CPU. The parts are so cheap it is totally worth it. It will also be nice to leave Win98 behind.
-
The LCD screen is also separated from the touch screen panel so I need to reattach them and hopefully get the alignment better. Right now the touch screen is a good 5 mm off in the horizontal direction.
Re alignment: You may already know this, but there should be a touch screen calibration utility on the scope. Usually there's a shortcut on the desktop.
Jay
-
The LCD screen is also separated from the touch screen panel so I need to reattach them and hopefully get the alignment better. Right now the touch screen is a good 5 mm off in the horizontal direction.
Re alignment: You may already know this, but there should be a touch screen calibration utility on the scope. Usually there's a shortcut on the desktop.
Jay
I was thinking there should be a calibration for it, just hadn't looked for it. thank you!
I rebuilt the LCD today as it was falling apart. I removed the LCD and then the touchscreen glass from the LCD. The tape that holds it all together was still good but the foam between the tape had perished. It took a good two hours but I got all of the old tape off and everything clean. I used some automotive body trim double sided tape to reattach the touchpanel and then used some thin foam to keep pressure between the touch panel glass and the aluminum frame. The scope is now100% reassembled and working great. The only option installed is jitter analyzer. Once I rebuild the OS and install XP I will look into enabling further options. I will order a SSD and ram today. I may also order a CPU if I can determine the best one to get.
lastly, having this working means I need some better scope probes. I don't really feel like buying active probes just yet, what do you people recommended for a 500 MHz passive probe?
edit - added a pic of the scope as it is now showing a 60 MHz square wave and the original gross knobs. I didn't take a picture of it before I started but I did take a shot of the front panel knobs after cleaning one of them(and being shocked it cleaned so well). The knobs are a fair representation of how dirty the entire thing was inside and out, the front BNC's were also all green with corrosion. All in all 2 hours for the repair(s) and 12 hours cleaning so far.
edit #2 - ssd, ram and a CPU ordered. Looking into some nice probes for it.
-
Some random info for this thread:
Digikey part # P299-ND is a pretty close match to the battery in the Dallas power cap. To make it fit you just need to bent two tabs 90 degrees and then trim off the excess length. This is much nicer then trying to solder directly to a battery or paying for an entire new power cap.
I plugged a MS USB wireless mouse into my scope, Win98 found drivers which impressed me. However after installing the USB drivers the scope app could no longer start. I was finally able to get it work again by installing the newest version of the Tek apps. So if you have an older version(I think I had 2.4.2) don't plug any other USB devices in.
Lastly, does anyone have the PC motherboard bios update mentioned as being required for windows 2000 and newer? My board has Main bios version 01.02.07 installed.
-
OK, a full day of struggling but I finally have XP installed and working reliably. I bought ram, a new CPU and an SSD. I had to play around with the ram I bought but eventually got 256mb installed in the powerpc and 512mb for the PC. I bought the same CPU as TiN. If you can do the soldering mods needed on the CPU then you've past micro rework 101 - it was fun but also a challenge.
My biggest problem was that XP would install but then crash or lockup after running for a few minutes. Being I had changed so many parts I had to keep swapping things around to isolate the problem. In the end it was the SSD. I then pulled the SSD out and tried it in my desktop and it worked perfect. I tried installing XP a few more times but it always had the same problem. I finally tried formatting it as NTFS instead of FAT32 and now it works fine. I can't explain why that should make any difference.
I have a Radisys motherboard and the network driver and video drivers were not included in XP. The network driver is posted in the thread a few pages back - it worked perfect. I also searched for the video driver previously recommended(wxpv251c) and it worked great - I have attached to this post. The front panel, and powerpc driver were downloaded from TiN's site. Once all drivers were installed I installed Tekscope v2.5.5 from the Tek website, it worked fine.
Once it was all up and running I restored the following files from my original harddrive to the vxboot directory:
.sn
.key
and the "CalCons" directory
This restored the serial number, the options key and the SPC settings etc.
Now I will spend some time playing with the various option software and key gen.
If anyone has restored a machine with no original hard drive and hasn't restored their serial # but wants to let me know and I'll create the proper .sn file for you.
price breakdown of the mods:
16 gig Samsung SSD - $30 shipped
256mb x 3 ram - $10 shipped
1.4 GHz CPU - $7 shipped
Now I can finally try out the two new P6139B probes I bought for it.
edit - well crap. The scope is working fine but some of the displayed characters are wrong. Such as it displays the symbol for the british pound instead of the ohm symbol or similar. I assume it is a keyboard/character set or region issue. Has anyone else run into this problem?
-
edit - well crap. The scope is working fine but some of the displayed characters are wrong. Such as it displays the symbol for the british pound instead of the ohm symbol or similar. I assume it is a keyboard/character set or region issue. Has anyone else run into this problem?
Copy windows fonts from your old harddrive to the new. There are three specific Tek fonts and even the ones from win98 work fine with XP - at least in mine.
I have the same scope but put in SU810 MB. No problems whatsoever with XP other than the fonts initially.
-
edit - well crap. The scope is working fine but some of the displayed characters are wrong. Such as it displays the symbol for the british pound instead of the ohm symbol or similar. I assume it is a keyboard/character set or region issue. Has anyone else run into this problem?
Copy windows fonts from your old harddrive to the new. There are three specific Tek fonts and even the ones from win98 work fine with XP - at least in mine.
I have the same scope but put in SU810 MB. No problems whatsoever with XP other than the fonts initially.
Thank you sir!
I toured through the Win98 drive and located the three Tek fonts. I then installed them on the Win XP install. It told me the fonts were already installed yet after a reboot the proper symbols are now displayed.
I have attached the three fonts for others to use.
-
Thank you. I had same issue, but never bothered to fix it.
Another issue I have, is that scope dont remeber last settings on power reboot. E.g. it boots with default settings always. Anyone had that? Perhaps bad vxWorks config I have?
-
Thank you. I had same issue, but never bothered to fix it.
Another issue I have, is that scope dont remeber last settings on power reboot. E.g. it boots with default settings always. Anyone had that? Perhaps bad vxWorks config I have?
Hmm. Mine is defaulted at each power on as well. It also did that with the original Win98 HD. I suppose it could be related to the vxworks config but I would have thought it would simply be a config saved on the PC harddrive.
Does anyone's TDS7000 save the last used settings automatically?
-
Felt like playing with some equipment tonight.
On my TDS7104 the 3dB bandwidth looks to be 1.15 GHz. My P6139B (500 MHz rated) probes 3dB point is 700 MHz. The input SWR of the scope channels when set to 50 ohms is 1.2 or less below 1 GHz. I played with the FFT mode of the scope and if I select the right combo of settings it crashes. To show basic carriers up to 2 GHz is works reasonably well though.
-
Felt like playing with some equipment tonight.
On my TDS7104 the 3dB bandwidth looks to be 1.15 GHz. My P6139B (500 MHz rated) probes 3dB point is 700 MHz. The input SWR of the scope channels when set to 50 ohms is 1.2 or less below 1 GHz. I played with the FFT mode of the scope and if I select the right combo of settings it crashes. To show basic carriers up to 2 GHz is works reasonably well though.
Are there any minidump files in C:\WINDOWS\Minidump?
Are you running the latest Tekscope application version 2.5.5?
I don't know whether this may apply to XP based TDS7054/TDS7104, but worth a look:
http://www.tek.com/oscilloscope/tds7054-software/windows-oscilloscope-virus-and-patch-update (http://www.tek.com/oscilloscope/tds7054-software/windows-oscilloscope-virus-and-patch-update)
Jay
-
I don't think it is really the PC scope app that is crapping out as much as either the powerPC board or acquisition board. It only happens when I am trying to see a low frequency FFT with a low RBW and really start messing with the sample rate and resolution. I was able to get it to crash with the original Win98 install as well. I don't plan to use the scope as a spectrum analyzer anyway, I have better ones in the lab already. The documentation from Tek really talks about how good the spectral analysis is though so I wanted to see what they thought all the hype was about.
-
I don't think it is really the PC scope app that is crapping out as much as either the powerPC board or acquisition board. It only happens when I am trying to see a low frequency FFT with a low RBW and really start messing with the sample rate and resolution. I was able to get it to crash with the original Win98 install as well. I don't plan to use the scope as a spectrum analyzer anyway, I have better ones in the lab already. The documentation from Tek really talks about how good the spectral analysis is though so I wanted to see what they thought all the hype was about.
Fair enough, but if there are any minidumps, I could analyze them to see what's crashing.
Jay
-
Hello @ all,
I found your Forum and read about the repair of a TDS from Tektronix.
Cause is, we had in our Laboratory a TDS7104 which run well since 15 years and then suddenly it does not boot.
Screen was:
B: Drive Error
Press F1 to Resume
When F1 was pressed, the Screen
PXE-E61: Media Test failture, check cable
PXE-M0F: Exiting LANDesk (R) Service Agent II
was displayed.
Reboot and press F2 for BIOS it says "Entering BIOS" but it doesnt do it.
So I changed the BIOS Battery and Battery Cap Dallas DS9034PC from the NVRAM, which was empty.
Next I read in the Forum to get the Output from the RS232 Interface onboard, and soldered a Jack to
the MAX232 for communicate with a Terminal Program on the PC.
Now the Problem is, I dont get a valid output from the RS232.... !?!!?
I configurated the RS232 to 9600 Baud and 8N1 but when I switch on the TDS, I get only hieroglyphics... !?!
So I think, the ASCIIs dont interpreted right, and try to change the RS232 Settings and Terminal Settings in multiple types,
but no meaningfull output was generated ... !?!?
With an Oscilloscope the Impulses look good and when I'm send a character I can see the right coded Impulses!
The PPC Board is booting after switch on from ".8" and count normaly up to "L".
After about 10s it boots again from "4" to "L" and so on and on .....
The Harddisk Drive I had check in a other System, it is readable and without Errors.
So I think, the NVRAM has forgotten the correct Address for boot and I must corred it,
but I dont come into the Routine over RS232 because the hieroglyphical Terminaloutput.
When I press a Button on the TDS Keyboard, the charakter was send correct via RS232
and the PPC breaks the Roundbooting Process, as descibed! (http://)
Booting up to L is correct, Breaking is correct -> it works,
but i dont see a correct Output.
has anybody an Idea???
thx ahead for help
73, Oliver
-
Welcome to the forum. I'd recommend double checking your serial port connections. Instead of soldering to the max chip I would plug into the header as documented on page 2 or 3 of this thread.
-
Yep, there is header right on the edge near power reg. No soldering required. Make sure you tap right lane and that your dongle is OK. I personally never used RS232 in my debug for this scope, only 3.3V UART-USB, thats why I was connecting to MAX in my case with grabbers.
-
Hello Steve (VE7FM) nice to meet you on this Band :-)
and TiN
mny thnx for answering.
Preliminary Result:
Ok, I had soldered an Adapter for 10Pin Jack to RS232 and it works, I get an Output!! :clap:
So next, I had programmed the Parameter like on Page 1.
It boots now, but not up to the End.
It hangs now at Level "L" on the 7-Segment-Display.
The next Steps "done" and "Attaching Network PCI dio device driver .... " doesnt works.
(Picture)
Perhaps the Path for the Starting Scipt ist different on my system???
I must look at home with my HDD Adapter for the path's on the Harddisk
and look forward next week.
73 & 55 & happy Eastern to all
Oliver, DC7OG
-
Make sure you have correct files in your c:/vxBoot folder (usually hidden).
After successful boot and loading vxWorks shows just a dash ('-') on 7-segment display. That's what you want.
dio_rst.vsh is startup script I have on my scope, but it's not default name, which is usually topScript.hw if my memory not betray me.
-
Hello Steve (VE7FM) nice to meet you on this Band :-)
and TiN
mny thnx for answering.
Preliminary Result:
Ok, I had soldered an Adapter for 10Pin Jack to RS232 and it works, I get an Output!! :clap:
So next, I had programmed the Parameter like on Page 1.
It boots now, but not up to the End.
It hangs now at Level "L" on the 7-Segment-Display.
The next Steps "done" and "Attaching Network PCI dio device driver .... " doesnt works.
(Picture)
Perhaps the Path for the Starting Scipt ist different on my system???
I must look at home with my HDD Adapter for the path's on the Harddisk
and look forward next week.
73 & 55 & happy Eastern to all
Oliver, DC7OG
Looks like it's waiting to get the files from the NLX PC hard drive. Does the scope boot into Windows?
Jay
-
As TiN mentioned he used a custom startup script(to confuse us all).
Change the startup line to the following:
startup script (s) : c:/vxboot/topScript.hw
-
Hello TiN, Steve and Jay,
thx for Information, no problem,
i had read my HDD with 2,5" Adapter and had found the
topScript.hw!
I will try next Tuesday, when I'm in Highschool again and i think
with the right entrys it will work!
Jay: No it hangs at boot time and doesnt found the correct script
on HDD,
i think thta's because i had used the special entrys from TiN and not the
normal global entry. :-) So no Windows can boot.
CU Oli
-
Scope must be able to boot Windows even with wrong settings for PPC. Driver need to be working to have PPC take it's stuff from the drive. If your scope dont boot OS, you need fix that and x86 issues first ;)
-
Scope must be able to boot Windows even with wrong settings for PPC. Driver need to be working to have PPC take it's stuff from the drive. If your scope dont boot OS, you need fix that and x86 issues first ;)
+1
OliGie, you may have a corrupt drive. What is the serial # of the scope? I have a number of Symantec Ghost images for these.
Also, if you press F8 at boot time, do you get options for how to boot Windows (safe mode, etc.)
Does the BIOS even detect the drive?
Jay
-
Hello
Please help me to solve the problem.
My TDS7104 has a problem.
After the DPX man show up, no more progressing like attached JPG file. the diagnostic LED indicates from 4 to L continually.
the message from NVRAM is as attached file. there are "Error in boot line" and can't load boot file" error message.
the TDS7104 worked well until a few weeks ago, but sometimes later no more progressing after the DPX man show up. So what I did are as below.
1> Replaced the NVRAM and NVRAM Cap by new one.
2>Reinstalled Application software (Tek Scope, TekVISA manager, VXl-11 Sever control)
There is no difference before and after the component changed.
What shall I do, please help me how to fix the problem.
Thanks in advance
Best regards,
Frank
-
Your boot parameters gone, so you must enter them back using that serial console. Just read few posts above and follow same procedure :)
-
Your boot parameters gone, so you must enter them back using that serial console. Just read few posts above and follow same procedure :)
Thanks TiN, I read all the posts but I couldn't understand well.
1>To which file, should I enter boot parameters?
2>topscript.hw is a boot file?
3>Which program should I use to enter parameters, I use Notpad but the file is saved as ".txt"
4>I just added the topscript.hw that you did upload to the C:\vcBoot\, but the problem is same as before.
Sorry for disturbing you.
Frank
-
Hallo friends,
it looks not good with my Oszi.
I correct the right file topScript.hw, but all looks the same as before.
The PPC boots up to "L" and waits for the host.
The host (NLX Board) but although dont boot.
With the Boot Process the Button F2 for entering Setup dont works.
He try on Disk and Int18h Network to boot and said then
Drive B not found
Press F1
but then the Process beginns again.
I think the BIOS from NLX is broken?!
So I decided to try flash the BIOS on NLX, load the correct files on a DOS Disk,
an do it. The programming was 100% successful and he requested to reboot,
but now i had a black screen, no more Keyboard and nothing is working!?!
:palm:
have a nice day
Oli
-
Yikes...Which BIOS did you flash? Seems wrong one...
frankoh
Follow this guide here (https://xdevs.com/fix/csa7404/). When it's booting, and print:
Press any key to stop auto-boot...
7 6 5 4 3 2 1 0
press 'c' on serial console
then enter parameters like in article.
topScript.hw is boot config file which you need to point to. It's default installed into c:/vxBoot hidden folder on your HDD.
-
Ouch, flashing the bios is probably a very bad idea. It sounds more like some other hardware failed or perhaps the PC motherboard also needed a new battery.
-
Hello Steve,
yes, it it was my last way to try a repair, because all other things i had daon and taste.
Yes, had changed the empty Batt on NLX Board too. And when i had boot the scope,
i was, that the screen appear: Press F2 to Setup ... and when i pressed F2 nothing
happens, but you see a flutter of the signs, that the Keyboard Input was read.
Normaly when I start a Computer and press F2 or Del I get the Screen of the BIOS / CMOS.
Here not. So I could not change the Startparameter, like HDD Cylinder, Heads, Sectors, Order,
Date and so on. I think the Prom is defekt in Partsin this case.
I look further for this and report again. In the Moment the Semester will start and I had some
other things to do.
thx a lot
73 Oliver
-
Did you replace capacitors around CPU VRM? On my SF810 they were some garbage brand with few already bulged. That could cause ur problems.
-
Hello TiN,
Ok I must look, but up to this time I had not saw some defekt Capacitors or brands!?
thx Oli
-
Yikes...Which BIOS did you flash? Seems wrong one...
frankoh
Follow this guide here (https://xdevs.com/fix/csa7404/). When it's booting, and print:
Press any key to stop auto-boot...
7 6 5 4 3 2 1 0
press 'c' on serial console
then enter parameters like in article.
topScript.hw is boot config file which you need to point to. It's default installed into c:/vxBoot hidden folder on your HDD.
Hello TiN,
First of all, thanks for your advice and comment. :)
The problem is not gone away yet.
Where should I look into to fix the problem?
I entered the boot file that you mentioned according to your instruction through the 232C cable.
After that, the scope show "can't load boot file" and "boot device : ^D". I tried several times with various data but the results are same as before.
The attached "boot_data_input.jpg" file show what I entered with terminal program, and the attached "boot_error.txt" is a log data after I entered the boot data. the "win98 tree.jpg" is the file of vxBoot directory.
Should I replace the NVRAM again with new one? Because it seems that the data is not stored in the RAM.
Rgds,
Frank
-
Why c:WvxBoot , should be c:\vxBoot :)
-
Why c:WvxBoot , should be c:\vxBoot :)
I typed the "\" but the "\" is displayed like W depending on the program.
please look at the attached file, in notepad "\" is displayed as same as you mentioned, but in DOS mode "\" is displayed like "W".
-
Good morning,
Just coming on this very interesting thread after looking for information to repair a Tektronix DPO7104.
The model I have in hands is close, but seems more recent than the models discribed in this thread.
My unit presents symptoms very similar to those described here. The scope run XP pro. It boots perfectly, run Xp perfectly as well, all the utilities are working fine. But ... when launching the application, it just present a fix screen, but never opens the scope interface.
For security, I have made a copy of the hdd, I can make all the tests I want without any risk to loose files or information.
I have opened the scope, but not completely dismantled the acquisition board (not that easy). But, at this stage, I can have a good vision of the two boards on the bottom of the unit. The Pentium Board is fine.
No seen any leaky cap, not burned component. The PS delivers good rails. But, not found any Dallas or NONvolatile ram.
So, at this stage, I would be very interested if anybody had to face the same problem, and how the issue has been faced.
Thanks a lot for your help.
Best regards,
DominiqueB
-
Welcome, DominiqueB.
I'd be happy to help, but I has not seen DPO guts before to suggest anything solid. While approach possibly is similar, config data (if that's the issue) might be stored in flash or EEPROM somewhere else. If you can upload your files (directions at link in my sub), with hires photos of boards which you already got access to, we can try to find the problem.
Do you see any serial debug connector or port? That would be first step to try in my book.
-
Hello all
I have 2 TDS8000B, also failed in PPC board, about debug LED, one board stopped in".8",and nothing output from serial port,maybe PPC CPU failured,I just want to give up, the other LED stopped in "A",and serial port message also shows "NVRAM test failed".I just replaced failure backup battery on NVRAM chip,but it still failed on same position.
Who can tell me how to do next?
-
Hello all
I have 2 TDS8000B, also failed in PPC board, about debug LED, one board stopped in".8",and nothing output from serial port,maybe PPC CPU failured,I just want to give up, the other LED stopped in "A",and serial port message also shows "NVRAM test failed".I just replaced failure backup battery on NVRAM chip,but it still failed on same position.
Who can tell me how to do next?
Post the exact failure/data from the console port. I've had to replace several of those Dallas/Maxim chips that failed.
Jay
-
Well, you replaced NVRAMs, that's good. But there are one more step to do, covered in article (https://xdevs.com/fix/csa7404/). Try it and let us know.
-
Well, you replaced NVRAMs, that's good. But there are one more step to do, covered in article (https://xdevs.com/fix/csa7404/). Try it and let us know.
I think he only repaced the battery, TiN. At least that what is sounds like... ;)
Jay
-
Hello all
I have 2 TDS8000B, also failed in PPC board, about debug LED, one board stopped in".8",and nothing output from serial port,maybe PPC CPU failured,I just want to give up, the other LED stopped in "A",and serial port message also shows "NVRAM test failed".I just replaced failure backup battery on NVRAM chip,but it still failed on same position.
Who can tell me how to do next?
Post the exact failure/data from the console port. I've had to replace several of those Dallas/Maxim chips that failed.
Jay
Thank you,you means I need replace whole NVRAM chip no only battery on it?Is it damaged?
-
Well, you replaced NVRAMs, that's good. But there are one more step to do, covered in article (https://xdevs.com/fix/csa7404/). Try it and let us know.
Thanks answer from Taiwan, I can't open you link,maybe should use VPN here (you know in mainland)? Could you introduce your link general?
-
Well, you can reference first post in this thread, which covers all required details as well.
-
Well, you can reference first post in this thread, which covers all required details as well.
You first post no referenced to replace NVRAM chip.My serial messages show below. Should I replace whole chip?
-
Seems so.
Then you have to write configuration to NVRAM via console.
-
Thank you,you means I need replace whole NVRAM chip no only battery on it?Is it damaged?
Damaged, no. But it appears to be defective after seeing your console port output. Looks to have a stuck data bit. The ones I've to replace were surface mount parts. I'd be curious if yours is too.
Jay
-
Thank you,you means I need replace whole NVRAM chip no only battery on it?Is it damaged?
Damaged, no. But it appears to be defective after seeing your console port output. Looks to have a stuck data bit. The ones I've to replace were surface mount parts. I'd be curious if yours is too.
Jay
I guess its same as you. You have replaced whole SMD part? This one is not easy to order.
-
I bought my replacement nvram from eBay, it was older stock but was new and has been working great. It was also pretty cheap.
-
Thank you,you means I need replace whole NVRAM chip no only battery on it?Is it damaged?
Damaged, no. But it appears to be defective after seeing your console port output. Looks to have a stuck data bit. The ones I've to replace were surface mount parts. I'd be curious if yours is too.
Jay
I guess its same as you. You have replaced whole SMD part? This one is not easy to order.
Yes, but a hot air rework station helped me. :) Why is it not easy to order? They seem to be readily available...
I have several bad ones with stuck bits. The next time I need one, I'm going to try and replace the TSOP SRAM on the underside of the board and save some money. I think they're only a couple of bucks versus $39 for the module from Digikey. You could try and do the same. I'll take a look this morning at one and let you know what the device is.
EDIT: the device is Cypress CY62128LL-70ZC. Cypress doesn't make that part anymore, but this one should be a suitable replacement: http://www.digikey.com/product-detail/en/cypress-semiconductor-corp/CY62128ELL-45ZXI/428-2040-ND/1205235 (http://www.digikey.com/product-detail/en/cypress-semiconductor-corp/CY62128ELL-45ZXI/428-2040-ND/1205235)
Jay
-
I used regular iron with wide tip to remove chip. No hotair craze :)
Vid (https://www.youtube.com/watch?v=Qx02R9OX98E)
-
I used regular iron with wide tip to remove chip. No hotair craze :)
Holy crap, you work fast! I couldn't even see the tip on your iron to comment! :-DD
Jay
-
Yes, but a hot air rework station helped me. :) Why is it not easy to order? They seem to be readily available...
I have several bad ones with stuck bits. The next time I need one, I'm going to try and replace the TSOP SRAM on the underside of the board and save some money. I think they're only a couple of bucks versus $39 for the module from Digikey. You could try and do the same. I'll take a look this morning at one and let you know what the device is.
EDIT: the device is Cypress CY62128LL-70ZC. Cypress doesn't make that part anymore, but this one should be a suitable replacement: http://www.digikey.com/product-detail/en/cypress-semiconductor-corp/CY62128ELL-45ZXI/428-2040-ND/1205235 (http://www.digikey.com/product-detail/en/cypress-semiconductor-corp/CY62128ELL-45ZXI/428-2040-ND/1205235)
Jay
OK, I also find this RAM chip on local Taobao shop, the oscilloscope now store in my friend house,next time I will deal with it again.
And I also think remove this Dallas chip, best choose is iron with more tin on a side of pin, hot air sometimes will damage other components around (some net problem,I cant see TIN's video,I guess we use the same method)
-
I also prefer to use a large tip to remove parts like the nvram. Add a little extra solder and then heat all of the pins and lift one side up carefully. Remove the excess solder so that side is now free. You can then heat all of the pins on the second side and lift it off. It is pretty easy with a little practice.
BH7JUO - nice to meet you here, 73 de VE7FM
-
I also prefer to use a large tip to remove parts like the nvram. Add a little extra solder and then heat all of the pins and lift one side up carefully. Remove the excess solder so that side is now free. You can then heat all of the pins on the second side and lift it off. It is pretty easy with a little practice.
BH7JUO - nice to meet you here, 73 de VE7FM
Never tried this. Got a picture of the tip you use? TiN's video was way too fast to see what he uses. The length down one side of this particular device is almost 1" !
Jay
-
You can hit magic button pause. :) I used ERSA 4.2mm chisel to remove chip and ERSA 102PDLF0.4 to solder pins on new one.
-
You can hit magic button pause. :)
It was too fast to even pause! I think it needs a frame-by-frame button ;)
I used ERSA 4.2mm chisel to remove chip and ERSA 102PDLF0.4 to solder pins on new one.
4.2mm would only do 5 pins or so at a time. I was thinking you heated the whole side at a time. Am I being thick? :-//
Jay
-
You can hit magic button pause. :)
It was too fast to even pause! I think it needs a frame-by-frame button ;)
I used ERSA 4.2mm chisel to remove chip and ERSA 102PDLF0.4 to solder pins on new one.
4.2mm would only do 5 pins or so at a time. I was thinking you heated the whole side at a time. Am I being thick? :-//
Jay
4.2mm sounds about right. I can post a picture of my tip tonight. In my case I lay a bead of solder along all of the pins to help hold some heat. I then just run the iron back and forth to flow all of the solder and then lift it up about 1mm. It probably sounds a little scary but it really works great and just needs a little practice. I have hot air equipment as well but in the case of the nvram I prefer the soldering iron method.
-
Put big solder blob on a side and toss it with tip from corner to corner to melt all pins side. Carefully lift released side bit up. Switch other side, do same. After few iterations, chip pins will be free from PCB. Important not to apply any force, that will rip pads apart from PCB.
After some practice, you can remove chips in seconds. Use wide chisel tip is to maximize heat transfer from iron. It's all about thermal transfer and surface area. Seeing iron settings any higher than 300? always make me cry.
-
I also prefer to use a large tip to remove parts like the nvram. Add a little extra solder and then heat all of the pins and lift one side up carefully. Remove the excess solder so that side is now free. You can then heat all of the pins on the second side and lift it off. It is pretty easy with a little practice.
BH7JUO - nice to meet you here, 73 de VE7FM
Nice to meet you too, VE7FM.This desoldering method also apply to some TQFP chips(not too much pins),I tried to dismantle some chips (like STM32 MCU)success with it :-+ :-+ :-+
-
Hi,
My TDS7404 (Win98) booted up fine several weeks ago. It has always been plugged in. Well, it was unplugged for a couple weeks and now it won't boot. The screen is completely blank with all the front panel buttons and such lit up. The floppy whirs a bit, then there are 2 beeps, then nothing. I plugged in a keyboard to see if some key combos would at least get the display to do something, but nothing has worked.
Any ideas what the problem could be? Again, it booted up fine a couple of weeks ago, and the only thing that has changed is that it was unplugged from the wall. I can imagine that the NVRAM battery could be dead, but would that cause the display to be completely blank?
Do any of you know of some troubleshooting procedures?
Thanks!!
Richard
-
Your x86 PC took a sick pill. I'd take the covers off, search for any bad parts, replace CMOS 3V battery cell and replace electrolytic caps around CPU socket. Then power it back on and check if it boots. If not check voltages from PSU. X86 pc and OS must be bootable even without correct NVRAM on PPC board.
-
Hi,
My TDS7404 (Win98) booted up fine several weeks ago. It has always been plugged in. Well, it was unplugged for a couple weeks and now it won't boot. The screen is completely blank with all the front panel buttons and such lit up. The floppy whirs a bit, then there are 2 beeps, then nothing. I plugged in a keyboard to see if some key combos would at least get the display to do something, but nothing has worked.
Any ideas what the problem could be? Again, it booted up fine a couple of weeks ago, and the only thing that has changed is that it was unplugged from the wall. I can imagine that the NVRAM battery could be dead, but would that cause the display to be completely blank?
Do any of you know of some troubleshooting procedures?
Thanks!!
Richard
Hook a monitor up to the SVGA port. Do you get video there? I suspect that you will, and see that the MB is reporting a CMOS checksum error.
Jay
-
Hook a monitor up to the SVGA port. Do you get video there? I suspect that you will, and see that the MB is reporting a CMOS checksum error.
Jay
That's probably it. For some odd reason, Tek didn't modify the BIOS to set the PCI video card for the internal LCD as the default display. Instead, it defaults to the AGP/chipdet video when the CMOS setting are lost.
-
Hook a monitor up to the SVGA port. Do you get video there? I suspect that you will, and see that the MB is reporting a CMOS checksum error.
Jay
That's probably it. For some odd reason, Tek didn't modify the BIOS to set the PCI video card for the internal LCD as the default display. Instead, it defaults to the AGP/chipdet video when the CMOS setting are lost.
Yup. "Gee Wally, what a dumb thing to do." |O
The fact that he's getting a floppy access and two BIOS beeps (which is CMOS checksum failure) it's probably prompting press F2 to enter setup. MB uses a standard CR2032 battery.
Jay
-
Good evening, I'm sorry but I need help with my Tek TDS 7054, I use the operating system Win98 and I'm not getting the boot TekScope, it crashes. I bought this equipment in the state, was not with any program of Tektronix, only OS and follow the steps reported here, the link downloaded: http://www.tek.com/oscilloscope/tds7254-software/csa7000-and-tds7000 (http://www.tek.com/oscilloscope/tds7254-software/csa7000-and-tds7000) -series-firmware-upgrade and not get hit, always fighting. Can someone help me??? Greetings!
-
Hello all. ;)
I found your Forum and read about the repair of a TDS from Tektronix.
The reason is that we have had in our lab in the TDS7104, who suddenly ceased to make measurements.
Win 98 operating system boots, Tektronix also downloaded the app, but the measurement does not produce.
The PPC Board is booting after switch on from ".8" and count normaly up to "-".
Help revive TDS7104. :-BROKE
Best Regards,
Alexandr Litchenko
-
Hi again. ;D
Maybe someone can share the value of the voltage reference points. Very interested in the Acquisition board.
Best Regards,
Alexandr Litchenko :-+
-
Vitaju :)
Did you check power supply voltages? Given that almost all modules failed with errors - maybe some voltage is off? Try swapping DIMM module (PC100 256MB) on PPC board.
Check visually if any burnt/hot parts around. Your scope seem to have good NVRAM, otherwise it would not get into TekScope app, but worth to check serial log output, like covered in this thread on first page.
-
Hi guys (and girl, 'scope repair isn't just for boys is it?)
I have been gifted a broken TDS7404. I know, I'm a lucky "£$%£$.
I was hoping that the fault was going to be a flat NVRAM battery, Windows boots perfectly, but the 'scope application hangs at the splash screen. Sadly it's not going to be that easy. NVRAM is fine. I've hooked up to the serial port and I can see VxWare booting successfully. TopScript hangs at the point it tries to initiate the acquisition board, baulking that there is no response from the Acq. board processor.
So, I guess I'm looking at a fault on the Acq. board, the PPC board, or a power supply unique to the Acq. board (something sent over the front power distribution board, that's not on the rear power distribution board.)
My problem is, I don't know what signals and voltages should be present anywhere in the box. Hence this post. I'm looking for some clues.
Let's start with the PA Bus.
What is a PA Bus? Is this a Tektronix proprietary bus? How is it connected to the PPC? I've googled and found nothing.
Looking at the serial output, the PPC board has a 750. No surprise there. From memory, this processor uses a 60x bus. Presumably there's a bridge chip between the 60x bus and the PA bus.
Does anyone have any details about the PA Bus, or the PPC to PA bus bridge chip please?
Can anyone tell me what power rails are supposed to ship to the Acq board over the front power distribution board please?
If it helps, I do actually know what happened to this 'scope. I was using it at work happily, then accidentally switched it off at the wall socket, rather than using the front panel button. On reboot it was faulty.
Many thanks in advance for any assistance.
-
If it helps, I do actually know what happened to this 'scope. I was using it at work happily, then accidentally switched it off at the wall socket, rather than using the front panel button. On reboot it was faulty.
Many thanks in advance for any assistance.
That shouldn't have hut the hardware, but it certainly could have corrupted some files on the hard drive. I'd start by reinstalling the scope application, then possibly the entire OS before digging into the hardware too much.
-
If it helps, I do actually know what happened to this 'scope. I was using it at work happily, then accidentally switched it off at the wall socket, rather than using the front panel button. On reboot it was faulty.
Many thanks in advance for any assistance.
That shouldn't have hut the hardware, but it certainly could have corrupted some files on the hard drive. I'd start by reinstalling the scope application, then possibly the entire OS before digging into the hardware too much.
Thanks for the suggestion. Yes I have already checked the contents of the Vxboot directory. I have already uninstalled and re-installed the software.
Here is the serial log. As you'll see the PPC is happily attached to the Windows HDD and is loading firmware merrily from vxboot. The issue occurs when the PPC tries to communicate with the acquisition board.
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.4.0
Creation date: Nov 2 2000, 11:03:34
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network PC1 dio device driver installed
interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773500
Starting at 0x200000...
Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.7.0.
WDB: Ready.
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topscript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23666688 = 0x1692000
ld < TekScopeSM.o
value = 23666048 = 0x1691d80
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1693940: value = 23673184 = 0x1693960 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691bc0: value = 23665696 = 0x1691c20 = pDBfs + 0x60
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 16983988 = 0x10327b4 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): Program enable command didn't echo back properly.
value = 0 = 0x0
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
0x16987e0 (tShell): Acq processor powerup failure!
-
The work continues, but at a pretty slow rate. I have a lot of other plates spinning.
Last night I took a look at the front and rear power distribution boards (from now on 'PDB'). They look like simple 2 sided PCBs, with GND on the outside of the chassis and power on the inside. Nice and easy to probe. I took a bunch of measurements with a DVM and annoyingly left them at home. I'll post them up later.
The rear PDB is good. I see 3.3V, 5V, 12V and I think 9ish V (can't remember exactly.) This is what I'd expect as this board feeds the x86 and PPC boards, all of which appear to be happy.
The front PDB measurements weren't so good. 3.3V was present, but the other power rails were not doing so well. I had a 0.9V, a 0.76V & a 0.09V. I took a quick impedance check of each rail to GND, all were in the tens of ohms range, so the PSU isn't folding due to over current.
I've not pulled the power supply board out to take a gander yet. But TiN has posted a picture of one...
https://dev.xdevs.com/attachments/download/625/PSU.jpg (Thanks TiN :-+ )
Front PDB connector is top left. Rear PDB connector is middle left. Without studying the photo too hard, there's a handy silk screen line denoting the low and high voltage sections of the board. It starts bottom left and terminates top right. Straddling the line are two large power transformers, each roughly in line horizontally with one of the power distribution board connectors. On the RH side of each there are a set of identical TO220s and a heatsinked power FET.
It looks very much to me like there are two more or less discrete SMPS supplies on this board. I'd hazard a guess that the one associated with transformer T7 is dedicated to the Front PDB and has gone pop.
So it's good news, a power fault. This is far better than a fault on the acquisition PCB. That board is stuffed with FPGAs that would be difficult to source and impossible to reprogram. I'm far happier having a PSU to fix. Even better news, as all the rails on the Front PDB are stuffed (I need to determine if the 3.3V that I did get is wired directly to the Rear PDB before I can be sure) I think I can suspect something on the primary side of T7, or something shared on the secondary.
Even better better news, it looks like the two implementations of SMPS are copies of roughly the same schematic. So I can compare working with non working.
OK, enough prose. Is anyone able to help me please by measuring the DC voltages on the front PDB?
Thanks.
-
OK as promised, here we go.
Rear power distribution board.
A/B/C 1 GND
A/B/C 2 Measured 3.54V
A/B/C 16 Measured 5.34V
A/B/C 27 Measured 12.75V
A/B/C 30 Measured 8.77V
:-+
Front power distribution board.
A/B/C 1 GND
A/B/C 2 Measured 0.95V
A/B/C 11 Measured 0.145V
A/B/C 17 Measured 0.768V
A/B/C 20 Measured 0.09V
A/B/C 22 Measured 3.36V
:--
-
I might take the hood off my scope for you, if you can share photo with exact points you want to measure :) :-DMM
-
TiN that's an awesome offer.
I typed a detail response and have deleted it.
I was checking the service manual (http://dev.xdevs.com/attachments/download/633/071701102%20CSA7000%20TDS7000%20Service%20manual%20.pdf (http://dev.xdevs.com/attachments/download/633/071701102%20CSA7000%20TDS7000%20Service%20manual%20.pdf)) for a diagram showing the measurement points, and on page 6-66 ( >:D ) I found a table with the voltages I need.
Many thanks, but no measurements needed.
-
:box: Round 2 :box:
The PSU board came out nice and easy. And would you believe it, this is what I found nestling next to the switching FETs for the transformer T7 that I suspected above:
(https://c1.staticflickr.com/1/402/32015118160_b45f81040d_b.jpg)
(Dear Santa,
Thank you very much for the marco extension tubes wot I got for Christmas. They are very hand and I am having a lot of fun taking photos of exploded electronics!)
The chip is a UC3844|https://www.onsemi.com/pub/Collateral/UC3844-D.PDF (http://UC3844|https://www.onsemi.com/pub/Collateral/UC3844-D.PDF) a fixed frequency PWM controller.
Pin 5 is GND, pin 7 is VCC, which according to the datasheet is 12 to 25V.
Looks like once upon a time there may have been a component where that crater is now.
Not too far away is the other, near identical (working) channel. Here's a pic, same extension rings, different lens. ::)
(https://c1.staticflickr.com/1/627/32272231791_8743e03202_b.jpg)
Yup, two SMT ceramic caps across pins 5 to 7 (notice how one of them looks leaky?)
Next thing to do was break out the meter.
Pin 5 on both chips are linked. That makes sense, it's GND.
Pin 7 on the working channel is linked to the blown trace on the faulty channel.
So these two chips share power and GND. Good news! One of the channels works, so there can't be a power fault.
I think that this was just a smoothing cap that's gone pop. Judging by the leakage on the other channel's cap, they are either not sufficiently over rated, or VCC had a transitory high, I'd have expected more damage in the latter case.
If we assume a cap with a DC rating too low, then the SOIC near the crater is probably good. I just need to clean some of the carbon off and reconnect it, looks like the cap fire melted the traces. I hope the chip is good, the datasheet says its obsolete.
Oh, more good news, this looks like a simple 2 layer PCB. So I don't think there will be any internal damage.
Here's another gratuitous macro ring crater shot:
(https://c1.staticflickr.com/1/690/32353374356_902a173458_b.jpg)
-
There's nothing in a ceramic cap to leak. That residue looks like flux to me. It's not unusual for SMD ceramic caps to short circuit due to a defect, or physical damage. If there's enough current available, they will get hot a burn. I'd pull one of the good one to measure its value. The datasheet for that IC should give you an upper limit for the voltage. Be sure to remove every trace of carbon to avoid future trouble.
-
Andy, you are of course correct. That'll teach me not to post when I'm tired!
The 3844 was removed and the PCB traces cut short of the charred PCB. The charred PCB was sealed with nail varnish and the traces were yellow wired back. Sadly the 'scope still didn't work.
Whilst On Semi don't make the 3844 any more, lots of other vendors do. A £1 chip was acquired from Mouser (£12 postage) and the 3844 was replaced. The scope was booted and volia! All is working.
I'd love to keep this, I don't have a DSO at home. But sadly I can't afford to keep a piece of kit this valuable for home use, it'll have to go up for sale.
Many thanks for the assistance offered and rendered here.
-
I went through this wonderful blog thread last year to fix my TDS7104 - replaced battery on NVRAM. Now, it is dead again. Replaced battery with giant external battery pack. Still ran that down in a couple of months. So, I will be replacing the NVRAM and battery this time. I've had this happen before over the years with Dallas Semi NVRAM increasing power usage after > 10 years. Don't really know why the quiescent current goes up so much. :)
-
Greetings.
I recently obtained a TDS7104, and this forum really help alot :-+
getting these old stuff, is really like betting a lottery , as stuff might fail.
The su810 nlx really is a old board but, I didn't even bother upgrading the firmware, ,
and the NVRAM battery cap lifespan is unknown, it might need change anytime soon :-//
Really hope these machines run for years , so far I upgraded a newer IDE diskdrive with win xp and a celeron 1.2 tualatin
My spec is
TekScope version 2.5.5
Option 3M: 16 Meg Max 4M/Channel
SM Serial Mask testing
Disk Drive Measurements 2 (Option 48)
USB 2.0 Test package (Option 50)
Communication Pulse Measurement 2
App 54 Avail : not installed
Power Measurement 3
Ethernet Compliance test software
Jitter analysis Advance.
Jitter analysis Essentials
Can and Lin Timing and protocol decode software.
Anyone knows what software is for the, App 54 Avail : not installed?
-
Hi TIn
how can i know the ram on the PPC board?
is there a log in vxboot folder?
Thanks
-
Anyone knows what software is for the, App 54 Avail : not installed?
App 54 is the same as option number 54, that is, PW2 power measurements. Since you have PW3 (option #62) it does not matter. Your scope has been upgraded sometime from PW2 to PW3.
-
App 54 is TDSRG - I think this is report generator.
-
App 54 is TDSRG - I think this is report generator.
Maybe it is, maybe it is not.
I went back to check my sources and PW2 came to this key:
TDS5104 B020149 9WSFG-QYL5H-993AA-GFXED-VD4GB-Z option 2M ; 2A ; PW2
So far the bit positions have been 100% consistent across the whole range of windows based TDS scopes.
I still think the last sentence of my previous reply is correct explanation for the missing app.
-
App 54 is TDSRG - I think this is report generator.
Maybe it is, maybe it is not.
I went back to check my sources and PW2 came to this key:
TDS5104 B020149 9WSFG-QYL5H-993AA-GFXED-VD4GB-Z option 2M ; 2A ; PW2
So far the bit positions have been 100% consistent across the whole range of windows based TDS scopes.
I still think the last sentence of my previous reply is correct explanation for the missing app.
This picture may do the trick.
Note the position of TDSRG between TDSCPM2 and TDSPWR3.
Then note this Ebay listing where it is missing:
http://www.ebay.com/itm/TEKTRONIX-TDS7154B-Oscilloscope-4CH-1-5GHz-20GS-s-5M-SM-J2-USB-CP2-PW3-ET3-JA3-/292060163891?hash=item4400246f33:g:cUwAAOSwB-1YzaUw (http://www.ebay.com/itm/TEKTRONIX-TDS7154B-Oscilloscope-4CH-1-5GHz-20GS-s-5M-SM-J2-USB-CP2-PW3-ET3-JA3-/292060163891?hash=item4400246f33:g:cUwAAOSwB-1YzaUw)
EDIT: Forgot the picture.
-
This picture may do the trick.
Note the position of TDSRG between TDSCPM2 and TDSPWR3.
Then note this Ebay listing where it is missing:
http://www.ebay.com/itm/TEKTRONIX-TDS7154B-Oscilloscope-4CH-1-5GHz-20GS-s-5M-SM-J2-USB-CP2-PW3-ET3-JA3-/292060163891?hash=item4400246f33:g:cUwAAOSwB-1YzaUw (http://www.ebay.com/itm/TEKTRONIX-TDS7154B-Oscilloscope-4CH-1-5GHz-20GS-s-5M-SM-J2-USB-CP2-PW3-ET3-JA3-/292060163891?hash=item4400246f33:g:cUwAAOSwB-1YzaUw)
I enabled application 54 on my scope and even after re-installing PW3 I do not see TDSRG option, just a note that app 54 is available but not installed.
From TDSPWR3 readme:
Product: TDSPWR3 (Power Measurements 3)
Version: 1.8.1
Date : 14-Jul-05
...clip...
* This application installs Report Generator. Report Generator
is a common feature shared by several applications. If you install another
application which includes a newer version of Report Generator, then Report
Generator will be updated to the newer version. You can check the version from
Report Generator Help>About.
Perhaps different scopes with different firmwares show TDSRG on place of app 54. Or app 54 is PW2 that has been uninstalled when installing PW3 and TDSRG is shown by different firmware before TDSPWR3 regardless of app 54 bit.
Do you have installation files for plain TDSRG?
BTW, that ebay link you provided is a funny one. $2k for left, top and right plastics and a HDD bodged in a scope that was previously a rack mount unit without HDD and DVD. Miraculously it has got some options too, compare to what is shown on back panel sticker. Seems like there are some people trying to get financial gain from enabling options on scopes that do not have those. I wonder how long it takes Tek to take notice.
-
This picture may do the trick.
Note the position of TDSRG between TDSCPM2 and TDSPWR3.
Then note this Ebay listing where it is missing:
http://www.ebay.com/itm/TEKTRONIX-TDS7154B-Oscilloscope-4CH-1-5GHz-20GS-s-5M-SM-J2-USB-CP2-PW3-ET3-JA3-/292060163891?hash=item4400246f33:g:cUwAAOSwB-1YzaUw (http://www.ebay.com/itm/TEKTRONIX-TDS7154B-Oscilloscope-4CH-1-5GHz-20GS-s-5M-SM-J2-USB-CP2-PW3-ET3-JA3-/292060163891?hash=item4400246f33:g:cUwAAOSwB-1YzaUw)
I enabled application 54 on my scope and even after re-installing PW3 I do not see TDSRG option, just a note that app 54 is available but not installed.
From TDSPWR3 readme:
Product: TDSPWR3 (Power Measurements 3)
Version: 1.8.1
Date : 14-Jul-05
...clip...
* This application installs Report Generator. Report Generator
is a common feature shared by several applications. If you install another
application which includes a newer version of Report Generator, then Report
Generator will be updated to the newer version. You can check the version from
Report Generator Help>About.
Perhaps different scopes with different firmwares show TDSRG on place of app 54. Or app 54 is PW2 that has been uninstalled when installing PW3 and TDSRG is shown by different firmware before TDSPWR3 regardless of app 54 bit.
Do you have installation files for plain TDSRG?
BTW, that ebay link you provided is a funny one. $2k for left, top and right plastics and a HDD bodged in a scope that was previously a rack mount unit without HDD and DVD. Miraculously it has got some options too, compare to what is shown on back panel sticker. Seems like there are some people trying to get financial gain from enabling options on scopes that do not have those. I wonder how long it takes Tek to take notice.
Sorry, I don't have TDSRG - I've just seen it before on a scope.
That Ebay item is not mine... It's possible that the options were purchased after the original ship date. Dunno.
-
I just picked up a CSA8000 on the cheap, hangs on splash screen. I replaced the NVRAM battery/cover on the Power PC board, but am unable to bring anything up on hyperterminal when connecting with a serial/serial cable. Any help would be appreciated!
-
I've not seen a CSA8000, but I'm going to assume that it is very similar to the TDS7000 series. If it's not I suggest a new thread.
Assuming it is...
What do you get on the 7 seg display?
I think that the PPC board shares power with the x86 board. So because you're getting a splash screen we can assume that the power to both boards is OK.
Are you absolutely sure that you have wired up the serial port correctly? And have the right UART settings.
If you genuinely have no serial output and nothing on the 7 seg display, then look at power, resets & clocks to the PPC.
-
Yes, it is similar to the 7000 series. LED cycles through 4-9, A,H,L, then repeats the sequence. Connection is via the serial port in back directly to an old Optiplex running hyperterminal, settings 9600/8/none/1/none. Thanks in advance for any help!
-
Yes, it is similar to the 7000 series. LED cycles through 4-9, A,H,L, then repeats the sequence. Connection is via the serial port in back directly to an old Optiplex running hyperterminal, settings 9600/8/none/1/none. Thanks in advance for any help!
The debug serial port is on the right hand side, not the back.
-
You should have a serial output.
As above, the diagnostic serial port is inside the chassis on the PPC board. May I respectfully suggest that you read the thread?
-
Respectfully, I read the entire thread prior to posting; my apparent error was (mistakenly) thinking that because the original posting didn't have a serial port on the computer for hyperterminal connection (and mine does), I would be able to connect directly via the serial port in back. As I have experience with Cisco routers and switches, I figured this would be a relatively simple task.
I have no interest in hijacking the thread, however I do have an interest in getting this unit working. PM with detailed instructions are appreciated, heck, I would even be open to paying someone to program the darned thing as this point.
-
OK, please accept my apologies.
So have you found the serial port? There's a clear picture in the first post of this thread.
In the very first post TiN talks about the MAX232, if you have no serial, this is the likely candidate.
Since we know the PPC is having trouble booting, I suggest that serial output from the PPC is going to help! You absolutely, definitely should be getting serial diags. at this stage.
-
I've been reading this thread off and on for a week. I am currently waiting on some parts for another scope so I've been fiddling with my TDS7154B. It had no hard drive but I had laptop drive that works well so I gave it a shot. I finally managed to get XP installed and after some struggles, I got The firmware to install (V5.1.3 for my scope).
The Front Panel driver didn't work for me. I figured the file might have become corrupt and I wanted to download it again but TiN's server is timing out on me unfortunately. Has anyone tried this driver on a 7154B? Do I need a different driver for this scope?
I'm also having problems getting programs to install on XP now. However it did let me install a wifi dongle because I couldn't get the ethernet to connect. It says connected but when I go to load IE, it loads for a sec then stops. The same happens with the wifi dongle :palm:
I think I need to uninstall TeKscope and remove all the traces using geek and then try and reinstall all my x86 drivers first. I know this thread is over 2 months old but there's more information in this one thread for these models than anywhere by far, and I'm desperate to get this unit going on the software side so I can move on to the hardware.
Here's the messages I'm getting since I can't get the Front Panel driver to work. Help :-BROKE
-
Server is back up, so try download driver again.
-
Server is back up, so try download driver again.
Got it :-+ Let me ask you something, what do you think my issue could be? I should have installed all the XP drivers first, then the Tek apps last? I'm also not sure which USB peripheral is the one for the front panel in device manager. Point and click has me spoil so I'm not sure if I'm installing it wrong. I uzip, then there are just 2 files there one .inf and one .bin I think. I tried to update driver but windows says it can't find the correct drive, and that could be because I'm trying to update the wrong USB :-//
You're guidance is greatly appreciated!
-
Just manually install the driver for the USB device. As I remember there was only one unknown USB device, which is FP. Second is PCI device which is PPC board.
-
Just manually install the driver for the USB device. As I remember there was only one unknown USB device, which is FP. Second is PCI device which is PPC board.
Below is a picture of what is showing up in XP device manager. I don't see any of the unknown devices on the USB branch, it's all PCI. I think there is something I missed or there is a difference in the way the 7154B connects versus the other TDS7XXX but I'm not sure.
I'm going to start from scratch. I'm going to do a fresh format and XP install and see if I can get all the drivers together and install them right after XP. Then install V5.1.3 TekScope again. I'm hoping that will do it.
Also my board is the intel D865GLC and I took some pics where the front panel ribbon cable connects to PPC and of the bios in hopes that you and the rest of the pros maybe can help me out. I'm going to take a break while XP is installing and come back and give it another shot.
By the way TiN, the way you brought that thing back to life is crazy! When I grow up, I wanna be just like you :-+
Thanks again for your time!
-
Does anyone happen to have the touchscreen driver / calibration utilities handy? I backed up the Windows 98 drivers for the Dynapro-branded touch screen, but have been drawing a blank when trying to find equivalent win2k drivers.
-
Does anyone happen to have the touchscreen driver / calibration utilities handy? I backed up the Windows 98 drivers for the Dynapro-branded touch screen, but have been drawing a blank when trying to find equivalent win2k drivers.
I think I can help. Can you get the VID in the device manager?
-
Bdah... My 7404 dead again...battery went empty, again!
Replaced the battery, reset PPC boot settings as before. Thing boots and acquire data, but guess what? Triggering is broken now.
None of the channels can trigger on the waveform edge. However if I set trigger to Timeout - it triggers just fine. WTF? :-BROKE
Self-test says ACQ and Trigger all fine and pass tests, but Misc section failed (521, 3), which in detailed shows Factory Cal integrity fail, Cal run fail and cal 2 integr fail.
I'd assume it lost factory calibration data? How to restore it back? I tried to run SPC, but it failed it.
-
Bdah... My 7404 dead again...battery went empty, again!
Replaced the battery, reset PPC boot settings as before. Thing boots and acquire data, but guess what? Triggering is broken now.
None of the channels can trigger on the waveform edge. However if I set trigger to Timeout - it triggers just fine. WTF? :-BROKE
Hi TiN,
I think your Dallas NVRAM is drawing too much current. I've seen this a number of times and posted about it in this thread and others.
I've also seen TDS7K scopes get into a state where they no longer trigger properly. When it happens I just press "default setup", then start over.
-
Well, default setup does nothing.
I measured current, it's 0.4uA, which is fine. I need somehow restore factory cal. :\.
-
Well, default setup does nothing.
I measured current, it's 0.4uA, which is fine. I need somehow restore factory cal. :\.
When measuring the current, you have to turn the scope on, then power off, otherwise the Dallas chip thinks it's new and does not connect the battery.
Isn't the factory cal. stored on the disk drive?
-
Just manually install the driver for the USB device. As I remember there was only one unknown USB device, which is FP. Second is PCI device which is PPC board.
Below is a picture of what is showing up in XP device manager. I don't see any of the unknown devices on the USB branch, it's all PCI. I think there is something I missed or there is a difference in the way the 7154B connects versus the other TDS7XXX but I'm not sure.
I'm going to start from scratch. I'm going to do a fresh format and XP install and see if I can get all the drivers together and install them right after XP. Then install V5.1.3 TekScope again. I'm hoping that will do it.
Also my board is the intel D865GLC and I took some pics where the front panel ribbon cable connects to PPC and of the bios in hopes that you and the rest of the pros maybe can help me out. I'm going to take a break while XP is installing and come back and give it another shot.
By the way TiN, the way you brought that thing back to life is crazy! When I grow up, I wanna be just like you :-+
Thanks again for your time!
Since it is running XP will it allow you to install driver booster from iobit and update to the latest drivers ?
http://www.iobit.com/en/driver-booster.php? (http://www.iobit.com/en/driver-booster.php?)
-
Since it is running XP will it allow you to install driver booster from iobit and update to the latest drivers ?
http://www.iobit.com/en/driver-booster.php? (http://www.iobit.com/en/driver-booster.php?)
I'm not sure. I was able to get it up and running with all the drivers installed. It took a while (user error), but got it done with help from the forum. :-+
-
Isn't the factory cal. stored on the disk drive?
Huh? Where :)
I have copied CalCons folder into c:/vxBoot, but either it doesn't like the data anymore or something is messed up.
I played with boot script for vxWorks, and got Cal run fail 531 error to go away. However other two stays still, and thing does not work with edge trigger. Works with advanced delay timeout trigger though. So I think trigger hardware itself is fine, it's just trigger cal is corrupted/lost. :(
Might as well give up and put the whole box for sale, with probes and everything (2 x P7380, some adapters). :'(
-
Might as well give up and put the whole box for sale, with probes and everything (2 x P7380, some adapters). :'(
It is a sad day indeed when the mighty TiN gives up on a repair.
-
Isn't the factory cal. stored on the disk drive?
Huh? Where :)
I have copied CalCons folder into c:/vxBoot, but either it doesn't like the data anymore or something is messed up.
I played with boot script for vxWorks, and got Cal run fail 531 error to go away. However other two stays still, and thing does not work with edge trigger. Works with advanced delay timeout trigger though. So I think trigger hardware itself is fine, it's just trigger cal is corrupted/lost. :(
Might as well give up and put the whole box for sale, with probes and everything (2 x P7380, some adapters). :'(
It sounds like a can of worms. And here was I thinking that one of these scopes maybe worth owning one day :(
-
Is there a procedure for enabling the options on these scopes ?
Can you use other serial numbers with different options enabled or is it more complicated like changing bits in the NVRAM etc ?
cheers
-
Hello everyone!
A quick message to let everyone know that I've also recently purchased a TDS7404 from ebay with a misc: 531 error.
I've opened it up, found out that the CMOS & NVRAM batteries are completely flat and will therefore order new ones.
I should also mention that wiring the UART like described in the article above is not correct, as the UART TX will actually short the MAX232 output... better buy a RS232 adapter with its cable!
Anyway, this is what I see in the log, which makes me think it's NVRAM related
0x16987e0 (tShell): >> DB file CRC FAILED
0x16987e0 (tShell): >> seed is 0x90690e4e
0x16987e0 (tShell): >> original db crc is 0x9f0f06b8
0x16987e0 (tShell): >> DB file CRC FAILED
0x16987e0 (tShell): >> seed is 0x2f674096
0x16987e0 (tShell): >> original db crc is 0xc6143439
0x16987e0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x16987e0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK..
Anyway, I've made a complete backup of what was present in the scope HDD if anyone needs it!
-
Quick questions:
My scope doesn't display any S/N in the information menu. Is that so because the nvram contents may be corrupted?
I've found a .sn and .key file inside the vxboot... are these supposed to be flashed into the nvram once I clear it?
-
Hi
I've recently acquired a TDS7054 with no hard drive and a flat battery on the PC motherboard.
I have replaced the battery and installed Windows XP on a new hard drive with maximum FAT32 partition size of 32GB and updated all of the drivers using DriverMax.
I have installed the latest Tektronix firmware 2.5.3 for this model and now just get the TekScope Splash screen.
Connecting up a serial terminal to the PPC console port I have setup the standard boot parameters but it stops booting after the following lines. It doesn't seem to get to the part where it loads the boot files.
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
Could this be an issue with Windows XP or the hard drive formatted using FAT32 ??
cheers
-
Do you have vxBoot dir with files on disk C:?
-
Hi
I've recently acquired a TDS7054 with no hard drive and a flat battery on the PC motherboard.
I have replaced the battery and installed Windows XP on a new hard drive with maximum FAT32 partition size of 32GB and updated all of the drivers using DriverMax.
I have installed the latest Tektronix firmware 2.5.3 for this model and now just get the TekScope Splash screen.
cheers
Going from memory here...
I think 2.5.3 is for the 7154 or higher bandwidth scopes. Latest for the 7054/7104 is 2.5.5
I know that 2.5.5 won't work right on the 7154 and higher scopes, but I don't know if the reverse is true.
Also, try re-seating the connectors between the NLX motherboard and the PPC board.
Lastly, check device manager and be sure that all the devices have installed correctly other than the PCMCIA and the ATI graphics chip that don't work in these scopes when running XP.
-
Do you have vxBoot dir with files on disk C:?
Yes it's in c:\vxBoot
When specifying the directories in the boot parameters do you use forward or back slashes ??
Also I could not find dio_rst.vsh on the HD so I just used topScript.hw which is what they used here https://forum.tek.com/viewtopic.php?f=568&t=136976&p=279248&hilit=vxBoot#p279248
cheers
boot device : sm
processor number : 0
host name : host
file name : c:/vxBoot/vxWorks.st
inet on ethernet (e) : 192.168.0.1: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) : 0x1000
target name (tn) : target
startup script (s) : c:/vxBoot/topScript.hw
other (o) : 0
-
Hi
I've recently acquired a TDS7054 with no hard drive and a flat battery on the PC motherboard.
I have replaced the battery and installed Windows XP on a new hard drive with maximum FAT32 partition size of 32GB and updated all of the drivers using DriverMax.
I have installed the latest Tektronix firmware 2.5.3 for this model and now just get the TekScope Splash screen.
cheers
Going from memory here...
I think 2.5.3 is for the 7154 or higher bandwidth scopes. Latest for the 7054/7104 is 2.5.5
I know that 2.5.5 won't work right on the 7154 and higher scopes, but I don't know if the reverse is true.
Also, try re-seating the connectors between the NLX motherboard and the PPC board.
Lastly, check device manager and be sure that all the devices have installed correctly other than the PCMCIA and the ATI graphics chip that don't work in these scopes when running XP.
Sorry I did use firmware 2.5.5 for the 7054 ;)
I took a screen shot of the Device Manager. When I checked the PPC battery I did spray the connectors on the riser board and PPC board but I will check the other connector on the PC motherboard.
cheers
-
What is that PCI Bridge without the driver? If that's PPC board, then it cannot talk to PC PCI side and get it's desired RTOS stuff from vxBoot. :-BROKE
-
What is that PCI Bridge without the driver? If that's PPC board, then it cannot talk to PC PCI side and get it's desired RTOS stuff from vxBoot. :-BROKE
It uses an Intel BL440ZX motherboard and the only official drivers I could find are here which doesn't appear to include the PCI bridge drivers
https://downloadcenter.intel.com/product/50298/Intel-Desktop-Board-BL440ZX
I did not use any of these drivers because I let DriverMax do it stuff.
According to the manual the chipset used is:-
Chipset Intel® 82440ZX AGPset (on the 66-Mhz host bus), consisting of:
· Intel® 82443ZX PCI/AGP controller (PAC)
· Intel® 82371EB PCI/ISA IDE Xcelerator (PIIX4E)
cheers
-
What is that PCI Bridge without the driver? If that's PPC board, then it cannot talk to PC PCI side and get it's desired RTOS stuff from vxBoot. :-BROKE
It uses an Intel BL440ZX motherboard and the only official drivers I could find are here which doesn't appear to include the PCI bridge drivers
https://downloadcenter.intel.com/product/50298/Intel-Desktop-Board-BL440ZX
I did not use any of these drivers because I let DriverMax do it stuff.
According to the manual the chipset used is:-
Chipset Intel® 82440ZX AGPset (on the 66-Mhz host bus), consisting of:
· Intel® 82443ZX PCI/AGP controller (PAC)
· Intel® 82371EB PCI/ISA IDE Xcelerator (PIIX4E)
cheers
Drivermax will never find drivers for the Tektronix specific hardware like the front panel, ACQ controller, and the Asilent/CHIPs video controller. I can help you in a few hours... Stand by.
-
Put these in the root folder of the scopes hard drive.
-
Put these in the root folder of the scopes hard drive.
Thanks Jay, I will give it a go tomorrow ;) Also did yours come with a program called CMOS.exe used to program NVRAM on the NLX board ? I'd like to get rid of that annoying network search when the thing boots up. I found some description of it here.
http://41j.com/blog/2014/08/tektronix-tds7054-repair/ (http://41j.com/blog/2014/08/tektronix-tds7054-repair/)
cheers
-
Also did yours come with a program called CMOS.exe used to program NVRAM on the NLX board ? I'd like to get rid of that annoying network search when the thing boots up. I found some description of it here.
http://41j.com/blog/2014/08/tektronix-tds7054-repair/ (http://41j.com/blog/2014/08/tektronix-tds7054-repair/)
cheers
Yes, I have that as well. I may not get a chance to post it till tomorrow.
-
Cmos.exe program
-
Hello,
I got a few time ago a defective TDS7054 and I'm trying to repair it.
Thanks to this forum and especially this thread, I was able to perform several tests and corrective actions. Unfortunately without success.
The problem: Windows 98SE boots normally but the instrument hangs on the TekScope Splash screen.
What I have done :
- Update to firmware V2.5.5 -> no change
- Quick internal visual examination -> no trace of damage
- PPC 7 segments LED indicates normal booting sequence up to the blinking (-)
- Connexion of console port to an old laptop (fitted with COM port) -> boot listings below
- Checking of PPC NVRAM battery (PowerCap) -> dead, 0.29V. Connexion of a fresh CR2032 battery to the PowerCap with external wiring
- Attempt tu restore boot parameters from console (no need, parameters seemed correct, see below)
- PPC booting with the file executing : tcsLoadTableToNVRAM "setup.tcs". This file is named tcsTopScript.vsh in my VxBoot folder -> TekScope still hangs
- Editing of topScript.hw in order to execute "NvramClearDb = 1", then rebooting with topScript.hw restored in initial state -> no change
- Checking of the NLX board CMOS battery -> OK, 3V. Anyway, initialization of the BIOS parameters with the MSDOS command CMOS -r nonet -> no change
- Cleaning of edge connectors NLX board to riser board, and riser board to PPC board -> no change
- Checking of power supply voltages (service manual page 6.56) : all correct well within tolerances except fan voltage (should be 9.8V, measured 13.2V). I suppose fan voltage is not critical and not the source of TekScope anomaly.
- External VGA monitor connected to NLX SVGA port : displays a text saying Windows initialized the display adapter (see below).
- External VGA monitor connected to PPC VGA port : same image as flat panel.
Remarks :
- At the end of the PPC booting sequence, I can hear relays clicking, I suppose on the acquisition board.
- After power off, the NVRAM drains abnormal current from the battery : I measured varying current between 0.5 to 2mA ! However, the NVRAM test during POST does not fail.
After all this I am a little desperate |O. Does someone have an idea ?
Thank you for reading,
Pascal
-
Replace the nvram - they are famous for dying, replacing the battery is rarely enough.
-
Even if the NVRAM test pass during the POST ?
-
Yes, I had same issue, NVRAMs data bit was stuck low. Replacement fixed that. Maxim still has replacements in this package.
-
Ok, thank you TheSteve and TiN, I will try this action and will keep you informed.
Pascal
-
Replace the nvram - they are famous for dying, replacing the battery is rarely enough.
Agree with Steve and TiN. I've seen a number of these that draw too much current.
Also, these are worrying:
...
tcsSynchronize: ERROR: DAC synch failed
AND
...
Exception current instruction address: 0x00223e50
It looks like something is crashing. Try re-seating the DIMM on the PPC board. If you have a known good DIMM, try that as well. Also, if you put the PPC DIMM into the NLX motherboard, you can run memtest86+ on it.
-
Put these in the root folder of the scopes hard drive.
I have got a bit further with the driver installs ;) Now still some conflict with the display driver. (see the screen grab below)
But the thing boots into Vxworks and I can hear some of the relays click over but hangs a bit of the way through it. I was wondering what startup script are you using ?
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
romPost: MPC106 Walking-one passed.
romPost: MPC106 configuration passed.
romPost: First PCI access passed.
romPost: PC87560 Walking-one passed.
romPost: PC87560 configuration passed.
romPost: DEC21554 configuration passed.
romPost: PERFORMING ROM CHECKSUM TEST...
romPost: ROM checksum passed.
romPost: PERFORMING DRAM CELL TEST...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM WALKING-ONE TEST...
romPost: DRAM Walking-one test passed.
romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...
romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: POWER-UP DIAGNOSTIC COMPLETE.
Hel
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.3.0
Creation date: Jun 28 2000, 16:52:12
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : C:/vxBoot/vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.168.0.2
user (u) : anonymous
ftp password (pw) : anonymous
flags (f) : 0x1000
target name (tn) : target
startup script (s) : C:/vxBoot/topScript.hw
other (o) : 0
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network iPC1 dio device driver installed
nterface lo0... done.
Attaching DIO client... done.
Loading C:/vxBoot/vxWorks.st...1773516
Starting at 0x200000...
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
KERNEL: THERMAL CONTROL INITIATED
Executing startup script C:/vxBoot/topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23666688 = 0x1692000
ld < TekScopeSM.o
value = 23666048 = 0x1691d80
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1693940: value = 23673184 = 0x1693960 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691bc0: value = 23665696 = 0x1691c20 = pDBfs + 0x60
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): Device failed to verify at address 0x0000.
0x16987e0 (tShell): Burning new code into AT90S4434 processor.
0x16987e0 (tShell): 1342 bytes successfully programmed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
0x16987e0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0
excHookAdd(stopStressForException)
value = 17557980 = 0x10b
-
Put these in the root folder of the scopes hard drive.
I have got a bit further with the driver installs ;) Now still some conflict with the display driver. (see the screen grab below)
But the thing boots into Vxworks and I can hear some of the relays click over but hangs a bit of the way through it. I was wondering what startup script are you using ?
The console port output, maybe you can see where yours veers off:
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
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topScript.hw
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 c:/vxboot/vxWorks.st...1773344
Starting at 0x200000...
Host Name: bootHost
User: target
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 6003 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.0.
WDB: Ready.
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TDS7000.o
value = 30997472 = 0x1d8fbe0
ld < TDS7000sm.o
value = 31006400 = 0x1d91ec0
pDbDev = ramDevCreate(0, 512, 1024, 1024, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1d92160: value = 31007104 = 0x1d92180 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1d91d00: value = 31006848 = 0x1d92080 = pDBfs + 0x380
copy ("TDS7000.DBF", "/db/TDS7000.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 31005792 = 0x1d91c60
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 22856896 = 0x15cc4c0 = PaiBaseRegisterTable + 0x750
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x1d987e0 (tShell): 1268 bytes successfully verified.
Acq processor FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programm
ing needed.
value = 0 = 0x0
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
value = 31032752 = 0x1d985b0
excHookAdd(stopStressForException)
value = 22628428 = 0x159484c = stopStressForException
dsyInit
value = 0 = 0x0
dsyWPApplyNextRegs
value = 22847264 = 0x15c9f20 = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x1d987e0 (tShell): >> Restoring exisiting filesystem in NVRAM...
value = 29213952 = 0x1bdc500
TmgrInit("/db")
0x1d987e0 (tShell): >> Commit hwAccount_Scope_serial string[7] <B010714ªªªªªªªªª
>
0x1d987e0 (tShell): >> Writing new checksum 0x86b3 to nvram....
0x1d987e0 (tShell): >> Commit opt_currOptKey string[64] <PHK4J-MFHKL-2NDQW-L922W
-L2HV4-JK7J>
0x1d987e0 (tShell): >> Writing new checksum 0x86b3 to nvram....
value = 0 = 0x0
PhxProxyInit
value = 28169120 = 0x1add3a0
rtlInit
value = 0 = 0x0
GpibInit
value = 0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
hwAccount_init
sysEnetAddrGet: cc:aa:88:ba:da:dd
value = 0 = 0x0
wfmMemInit(1)
value = 48209632 = 0x2df9ee0
vertInstall
value = 0 = 0x0
calConStatus = cc_init(2)
0x1d987e0 (tShell): Reading 280 bytes of service cal data from EEPROM into 0x2df
9b80
0x1d987e0 (tShell): x24165_read succeeded
calConStatus = 0x17ebe1c: value = 0 = 0x0
MathMeasCreateTheMathandMeasurementLibraries
value = 48038592 = 0x2dd02c0
initAcqMapper
0x1d987e0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
trigMapInit
value = 0 = 0x0
dsyMapInit
value = 0 = 0x0
mathMapperInit
value = 0 = 0x0
utilMapInit
value = 48035936 = 0x2dcf860
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 18799740 = 0x11edc7c = cppNetMgrEndOfTransmission(CppNetMgr*)
MathMeasMapHookup
value = 31032592 = 0x1d98510
dsyMapHookup
value = 31032696 = 0x1d98578
utilMapHookup
value = 31032720 = 0x1d98590
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 31032696 = 0x1d98578
fastFrameMapHookup
value = 31032704 = 0x1d98580
trigMapHookup
value = 31032712 = 0x1d98588
vertMapHookup
value = 31032680 = 0x1d98568
spcMapHookup
value = 31032688 = 0x1d98570
autosetMapHookup
value = 31032744 = 0x1d985a8
timeSyncMapHookup
value = 31032720 = 0x1d98590
auxTrigMapHookup
value = 31032720 = 0x1d98590
dpoMapHookup
value = 31032712 = 0x1d98588
TmgrStartup
value = 47412752 = 0x2d37610
PhxProxyStartup
value = 47362208 = 0x2d2b0a0
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 47262480 = 0x2d12b10
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 47221936 = 0x2d08cb0
enablePowerupDiags = 0
enablePowerupDiags = 0x17c43cc: valu0xe = 2db1c80 (tmgr): 0>> Commit opt_currOpt
Key string[ = 0x640] <PHK4J-MFHKL-2NDQW-L922W-L2HV4-JK7J>
runPowerupD0xiags2db1c80 (tmgr):
>> Writing new checksum 0x86b3 to nvram....
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
dbFsIoctl: invalid code 1
value = 22847264 = 0x15c9f20 = DsyRegisterTable + 0xab0
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
################### topScript ends ###############################
Done executing startup script c:/vxboot/topScript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x2ca8db0 (CalWatch): Temperature transition out of SPC-supporting range.
0x2ca8db0 (CalWatch): Temperature transition into SPC-supporting range.
Forget the ATI video under XP, you need to install the Asilent video driver which I posted above.
But I don't think the video driver is the problem...
Do you want me to post the two scripts in the image I saved off?
-
Hello Jwalling,
PPC and NLX boards use exactly the same model of 128Mb DRAM.
I first ran Memtest86+ on the NLX DRAM -> no error
Then I swapped DRAMs between NLX and PPC and ran Memtest again -> no error
Then I restarted normally the oscilloscope (with DRAMs still swapped) -> no change, same tcsSynchronize ERROR and exception, and Tekscope freeze as before.
-
Hello Jwalling,
PPC and NLX boards use exactly the same model of 128Mb DRAM.
I first ran Memtest86+ on the NLX DRAM -> no error
Then I swapped DRAMs between NLX and PPC and ran Memtest again -> no error
Then I restarted normally the oscilloscope (with DRAMs still swapped) -> no change, same tcsSynchronize ERROR and exception, and Tekscope freeze as before.
Can't think of anything else to try except checking the interconnect boards for bent pins. Still, you have a questionable NVRAM in there; I would consider replacing it before going any further. I remember seeing one that would pass the PPC diagnostics, yet fail the scopes diagnostics after the application loaded.
-
Put these in the root folder of the scopes hard drive.
I have got a bit further with the driver installs ;) Now still some conflict with the display driver. (see the screen grab below)
But the thing boots into Vxworks and I can hear some of the relays click over but hangs a bit of the way through it. I was wondering what startup script are you using ?
The console port output, maybe you can see where yours veers off:
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
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topScript.hw
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 c:/vxboot/vxWorks.st...1773344
Starting at 0x200000...
Host Name: bootHost
User: target
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 6003 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.0.
WDB: Ready.
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TDS7000.o
value = 30997472 = 0x1d8fbe0
ld < TDS7000sm.o
value = 31006400 = 0x1d91ec0
pDbDev = ramDevCreate(0, 512, 1024, 1024, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1d92160: value = 31007104 = 0x1d92180 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1d91d00: value = 31006848 = 0x1d92080 = pDBfs + 0x380
copy ("TDS7000.DBF", "/db/TDS7000.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 31005792 = 0x1d91c60
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 22856896 = 0x15cc4c0 = PaiBaseRegisterTable + 0x750
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x1d987e0 (tShell): 1268 bytes successfully verified.
Acq processor FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programm
ing needed.
value = 0 = 0x0
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
value = 31032752 = 0x1d985b0
excHookAdd(stopStressForException)
value = 22628428 = 0x159484c = stopStressForException
dsyInit
value = 0 = 0x0
dsyWPApplyNextRegs
value = 22847264 = 0x15c9f20 = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x1d987e0 (tShell): >> Restoring exisiting filesystem in NVRAM...
value = 29213952 = 0x1bdc500
TmgrInit("/db")
0x1d987e0 (tShell): >> Commit hwAccount_Scope_serial string[7] <B010714ªªªªªªªªª
>
0x1d987e0 (tShell): >> Writing new checksum 0x86b3 to nvram....
0x1d987e0 (tShell): >> Commit opt_currOptKey string[64] <PHK4J-MFHKL-2NDQW-L922W
-L2HV4-JK7J>
0x1d987e0 (tShell): >> Writing new checksum 0x86b3 to nvram....
value = 0 = 0x0
PhxProxyInit
value = 28169120 = 0x1add3a0
rtlInit
value = 0 = 0x0
GpibInit
value = 0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
hwAccount_init
sysEnetAddrGet: cc:aa:88:ba:da:dd
value = 0 = 0x0
wfmMemInit(1)
value = 48209632 = 0x2df9ee0
vertInstall
value = 0 = 0x0
calConStatus = cc_init(2)
0x1d987e0 (tShell): Reading 280 bytes of service cal data from EEPROM into 0x2df
9b80
0x1d987e0 (tShell): x24165_read succeeded
calConStatus = 0x17ebe1c: value = 0 = 0x0
MathMeasCreateTheMathandMeasurementLibraries
value = 48038592 = 0x2dd02c0
initAcqMapper
0x1d987e0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
trigMapInit
value = 0 = 0x0
dsyMapInit
value = 0 = 0x0
mathMapperInit
value = 0 = 0x0
utilMapInit
value = 48035936 = 0x2dcf860
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 18799740 = 0x11edc7c = cppNetMgrEndOfTransmission(CppNetMgr*)
MathMeasMapHookup
value = 31032592 = 0x1d98510
dsyMapHookup
value = 31032696 = 0x1d98578
utilMapHookup
value = 31032720 = 0x1d98590
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 31032696 = 0x1d98578
fastFrameMapHookup
value = 31032704 = 0x1d98580
trigMapHookup
value = 31032712 = 0x1d98588
vertMapHookup
value = 31032680 = 0x1d98568
spcMapHookup
value = 31032688 = 0x1d98570
autosetMapHookup
value = 31032744 = 0x1d985a8
timeSyncMapHookup
value = 31032720 = 0x1d98590
auxTrigMapHookup
value = 31032720 = 0x1d98590
dpoMapHookup
value = 31032712 = 0x1d98588
TmgrStartup
value = 47412752 = 0x2d37610
PhxProxyStartup
value = 47362208 = 0x2d2b0a0
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 47262480 = 0x2d12b10
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 47221936 = 0x2d08cb0
enablePowerupDiags = 0
enablePowerupDiags = 0x17c43cc: valu0xe = 2db1c80 (tmgr): 0>> Commit opt_currOpt
Key string[ = 0x640] <PHK4J-MFHKL-2NDQW-L922W-L2HV4-JK7J>
runPowerupD0xiags2db1c80 (tmgr):
>> Writing new checksum 0x86b3 to nvram....
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
dbFsIoctl: invalid code 1
value = 22847264 = 0x15c9f20 = DsyRegisterTable + 0xab0
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
################### topScript ends ###############################
Done executing startup script c:/vxboot/topScript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x2ca8db0 (CalWatch): Temperature transition out of SPC-supporting range.
0x2ca8db0 (CalWatch): Temperature transition into SPC-supporting range.
Forget the ATI video under XP, you need to install the Asilent video driver which I posted above.
But I don't think the video driver is the problem...
Do you want me to post the two scripts in the image I saved off?
Yes please do. I am using active file compare to compare the console outputs.
I did noticed the follwing descrepancies comparing with TiN's console output.
This is from my scope:-
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
And this is from TiN's scope:-
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
I do notice that Windows XP has trouble with the Asilant video driver. It says it cannot load the drivers so is just defaulting to the standard VGA driver.
It's possible that this thing cannot work under XP.
I may try another build using Windows 98.
Regards
David
-
Yes please do. I am using active file compare to compare the console outputs.
I do notice that Windows XP has trouble with the Asilant video driver. It says it cannot load the drivers so is just defaulting to the standard VGA driver.
It's possible that this thing cannot work under XP.
I may try another build using Windows 98.
Regards
David
It should be able to work under XP. I've done it myself. Let me check again though my images.
Here's the two files.
-
Try this video driver.
-
Hello Jwalling,
PPC and NLX boards use exactly the same model of 128Mb DRAM.
I first ran Memtest86+ on the NLX DRAM -> no error
Then I swapped DRAMs between NLX and PPC and ran Memtest again -> no error
Then I restarted normally the oscilloscope (with DRAMs still swapped) -> no change, same tcsSynchronize ERROR and exception, and Tekscope freeze as before.
Can't think of anything else to try except checking the interconnect boards for bent pins. Still, you have a questionable NVRAM in there; I would consider replacing it before going any further. I remember seeing one that would pass the PPC diagnostics, yet fail the scopes diagnostics after the application loaded.
Yes, I have to change the NVRAM, at least for the excessive leakage current which depletes the battery in a few weeks. This is not a good health sign... These DS1245YP are quite expensive here. Best offer I have found is at Farnell at 40€.
I will also verify a few questionable electrolytics on the PPC board.
Anyway, I will keep you informed.
Thank you for your time,
Pascal
-
Yes, I have to change the NVRAM, at least for the excessive leakage current which depletes the battery in a few weeks. This is not a good health sign... These DS1245YP are quite expensive here. Best offer I have found is at Farnell at 40€.
I will also verify a few questionable electrolytics on the PPC board.
Anyway, I will keep you informed.
Thank you for your time,
Pascal
Yes, they are ridiculously expensive for a lousy SRAM and a voltage monitoring chip. I HATE Maxim. Not only for their prices, but the EOL'ing of components with no suitable replacements.
-
Try this video driver.
Hi Jay
Is this the same one you gave me in the Tektronix bundle ?
cheers
-
Try this video driver.
Hi Jay
Is this the same one you gave me in the Tektronix bundle ?
cheers
I wasn't sure as they came from different images, but now that I look at them both, it would appear so.
They won't install manually for you?
-
Try this video driver.
Hi Jay
Is this the same one you gave me in the Tektronix bundle ?
cheers
I wasn't sure as they came from different images, but now that I look at them both, it would appear so.
They won't install manually for you?
I just point Windows at the relevant directory and let it install it but it gets stuck on the last dll and just sits there indefinitely. How did you install yours ?
cheers
-
I just point Windows at the relevant directory and let it install it but it gets stuck on the last dll and just sits there indefinitely. How did you install yours ?
cheers
Same way as you're trying. How about disabling the ATI video, and uninstalling the Chips video from the device manager. Then re-boot the scope and let it try to install again?
-
I just point Windows at the relevant directory and let it install it but it gets stuck on the last dll and just sits there indefinitely. How did you install yours ?
cheers
Same way as you're trying. How about disabling the ATI video, and uninstalling the Chips video from the device manager. Then re-boot the scope and let it try to install again?
If I try uninstalling the ATI driver from the Device Mangler it just hangs. Also the bios allows you to select between AGP and PCI graphics but selecting PCI to enable the scope operation doesn't appear to disable it completely. I had better luck when I used my Win XP SP3 build rather than the Win XP SP2 build which seems to pick up the ATI card for some reason.
Do you know what those NVRAM buffer errors are caused by ? Is this an issue with the NVRAM ?
cheers
-
If I try uninstalling the ATI driver from the Device Mangler it just hangs. Also the bios allows you to select between AGP and PCI graphics but selecting PCI to enable the scope operation doesn't appear to disable it completely. I had better luck when I used my Win XP SP3 build rather than the Win XP SP2 build which seems to pick up the ATI card for some reason.
Do you know what those NVRAM buffer errors are caused by ? Is this an issue with the NVRAM ?
cheers
It hangs when you Uninstall the ATI video, or just disabling it, which I recommended?
If you're referring to this:
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
To be honest, I've no idea... Are you sure that the NVRAM is OK, and have you run memtest86+ on the PPC memory?
-
If you're referring to this:
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
To be honest, I've no idea... Are you sure that the NVRAM is OK, and have you run memtest86+ on the PPC memory?
On my TDS7054, when the NVRAM battery was flat and before trying to restore its content, I had exactly the same errors :
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
After executing [tcsLoadTableToNVRAM "setup.tcs"] and [NvramClearDb = 1] as explained in this thread, these two errors disappeared in the boot log.
-
If I try uninstalling the ATI driver from the Device Mangler it just hangs. Also the bios allows you to select between AGP and PCI graphics but selecting PCI to enable the scope operation doesn't appear to disable it completely. I had better luck when I used my Win XP SP3 build rather than the Win XP SP2 build which seems to pick up the ATI card for some reason.
Do you know what those NVRAM buffer errors are caused by ? Is this an issue with the NVRAM ?
cheers
It hangs when you Uninstall the ATI video, or just disabling it, which I recommended?
If you're referring to this:
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
To be honest, I've no idea... Are you sure that the NVRAM is OK, and have you run memtest86+ on the PPC memory?
It hangs if I try to unistall it or disable it.
I've done the memtest on the PC memory and it checks out ;)
-
If you're referring to this:
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
To be honest, I've no idea... Are you sure that the NVRAM is OK, and have you run memtest86+ on the PPC memory?
On my TDS7054, when the NVRAM battery was flat and before trying to restore its content, I had exactly the same errors :
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
After executing [tcsLoadTableToNVRAM "setup.tcs"] and [NvramClearDb = 1] as explained in this thread, these two errors disappeared in the boot log.
I'm a bit confused on this aspect of it.
Do i set the startup script to run setup.tcs with NvramClearDb = 1 in the script ??
cheers
-
If you're referring to this:
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
To be honest, I've no idea... Are you sure that the NVRAM is OK, and have you run memtest86+ on the PPC memory?
On my TDS7054, when the NVRAM battery was flat and before trying to restore its content, I had exactly the same errors :
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
After executing [tcsLoadTableToNVRAM "setup.tcs"] and [NvramClearDb = 1] as explained in this thread, these two errors disappeared in the boot log.
Interesting. I've never seen that behavior. When the battery is dead, I see the exact same thing as shown in the OP from TiN.
-
I have attached the boot logs (taken from console port) to my post Reply #313.
I attach them here again for convenience (two files, one before any repair attempt, then after trying to refresh the NVRAM content).
Since the two errors disappeared (but in my case the tcsSynchronize error is still there), we can conclude they can be related to the NVRAM content.
I hope this will help.
However, to my opinion, the effects of a depleted NVRAM battery are not necessary always the same from one unit to another, since we cannot predict which RAM cells will first lose their content.
Regards,
Pascal
-
OK made some progress tonight. Yesterday I decided to start from scratch again and reinstall Windows as I may have screwed it up along the way doing all of the driver updating etc. Also the thing wouldn't shut down properly and I was getting BSOD when I booted up. It was in a mess so it needed a makeover.
So this time before I installed Windows XP SP3 I made sure the video card was set to PCI in the BIOS and not AGP. The last time I installed windows I had it set to AGP which uses the onboard ATI chip rather than the C&T chips on the PPC board. You can tell because the video displays on an external monitor instead of the oscilloscope LCD display. You don't want this as it appears to confuse windows later on with all sorts of driver issues.
After windows has installed itself it may display at 800x600 and not fit on the screen properly. If this happens go into Control Panel and change the display settings back to 640x480 16 bits resolution.
Now if you go into device manager you will note a whole lot of exclamation marks for some of the drivers such as display etc. This is where you need to install the drivers that Jay has kindly made available to us. In my case there were two VGA drivers that had exclamation marks so Windows obviously picked up the onboard ATI chipset which you don't use in this app ! So you should be able to update one of these drivers using the Asilant C&T driver. Now update the PCI and touch screen drivers as well and don't worry about the PCMCIA driver.
OK so now the scope is going through its motions but is still hanging on like last time :(
excHookAdd(stopStressForException)
value = 17557980 = 0x10b
So I'm looking at Tin's setup and note that for other (o) : nvfs=0x1000 whereas mine is set to 0 so I change it and sure enough the scope boots up completely and is working now !!
Now the only problem is that when I run the diagnostics i get miscellaneous failure of 531. Not sure what that is.
cheers
david
-
Now the only problem is that when I run the diagnostics i get miscellaneous failure of 531. Not sure what that is.
From the manual: NOTE . If diagnostic error message 531 is displayed, run signal-path compensa-
tion and then rerun Instrument Diagnostics.
Hope that's all it is.
-
Now the only problem is that when I run the diagnostics i get miscellaneous failure of 531. Not sure what that is.
From the manual: NOTE . If diagnostic error message 531 is displayed, run signal-path compensa-
tion and then rerun Instrument Diagnostics.
Hope that's all it is.
Yes that fixed it up ;)
Also what is the deal with the serial number thing as it appears to have defaulted to standard factory settings as far as options are concerned.
Is there anyway to bump up the options ?
cheers
david
-
Yes that fixed it up ;)
Also what is the deal with the serial number thing as it appears to have defaulted to standard factory settings as far as options are concerned.
Is there anyway to bump up the options ?
In the [help] [about] pulldown menu, what is the serial # of the unit?
A picture would be great!
-
Yes that fixed it up ;)
Also what is the deal with the serial number thing as it appears to have defaulted to standard factory settings as far as options are concerned.
Is there anyway to bump up the options ?
In the [help] [about] pulldown menu, what is the serial # of the unit?
A picture would be great!
Hi Jay
This is what I get from the About screen. Now the funny part about it is that it appears to have defaulted to Option 1M because I can crank up the record length on one channel to 2Meg which according to the specs is the 1M option. Wouldn't mind the 3M option which is the max this model can do ;)
-
Hi Jay
This is what I get from the About screen. Now the funny part about it is that it appears to have defaulted to Option 1M because I can crank up the record length on one channel to 2Meg which according to the specs is the 1M option. Wouldn't mind the 3M option which is the max this model can do ;)
Now try it with all four channels on. ;)
In the c:\vxboot folder there are two important files. You will need to edit these with the serial number on the rear of the unit and the current option key on the same sticker in a hex editor and drop them in there.
It will need to be rebooted after doing this for the scope to see the updated serial/option key.
-
Hi Jay
This is what I get from the About screen. Now the funny part about it is that it appears to have defaulted to Option 1M because I can crank up the record length on one channel to 2Meg which according to the specs is the 1M option. Wouldn't mind the 3M option which is the max this model can do ;)
Now try it with all four channels on. ;)
In the c:\vxboot folder there are two important files. You will need to edit these with the serial number on the rear of the unit and the current option key on the same sticker in a hex editor and drop them in there.
It will need to be rebooted after doing this for the scope to see the updated serial/option key.
Yes it's still 2M on 1 channel and 500k on all 4 channels but the 1M option is now showing up in the About menu !
Where is the serial number stored in these things ?
cheers
-
Hi Jay
This is what I get from the About screen. Now the funny part about it is that it appears to have defaulted to Option 1M because I can crank up the record length on one channel to 2Meg which according to the specs is the 1M option. Wouldn't mind the 3M option which is the max this model can do ;)
Now try it with all four channels on. ;)
In the c:\vxboot folder there are two important files. You will need to edit these with the serial number on the rear of the unit and the current option key on the same sticker in a hex editor and drop them in there.
It will need to be rebooted after doing this for the scope to see the updated serial/option key.
Yes it's still 2M on 1 channel and 500k on all 4 channels but the 1M option is now showing up in the About menu !
Where is the serial number stored in these things ?
cheers
It's stored on the disk drive in the .sn file and also in the NVRAM on the PPC board. If the info is lost in the NVRAM, then the scope retrieves it from the drive. Sometimes it takes a few boots to recover it. That's probably what happened in your case. If you lose the NVRAM contents and the disk drive, that's when editing those two files is required.
-
Hi Jay
This is what I get from the About screen. Now the funny part about it is that it appears to have defaulted to Option 1M because I can crank up the record length on one channel to 2Meg which according to the specs is the 1M option. Wouldn't mind the 3M option which is the max this model can do ;)
Now try it with all four channels on. ;)
In the c:\vxboot folder there are two important files. You will need to edit these with the serial number on the rear of the unit and the current option key on the same sticker in a hex editor and drop them in there.
It will need to be rebooted after doing this for the scope to see the updated serial/option key.
Yes it's still 2M on 1 channel and 500k on all 4 channels but the 1M option is now showing up in the About menu !
Where is the serial number stored in these things ?
cheers
It's stored on the disk drive in the .sn file and also in the NVRAM on the PPC board. If the info is lost in the NVRAM, then the scope retrieves it from the drive. Sometimes it takes a few boots to recover it. That's probably what happened in your case. If you lose the NVRAM contents and the disk drive, that's when editing those two files is required.
I'd previously removed the NVRAM battery on the PPC board to test it so it would have lost the contents. It appears that if you use any other serial number and key it will not accept it so the serial number must be stored elsewhere on the board.
Also do you know if it's possible for this scope to remember the last settings because every time I reboot it defaults to it's own settings and ignores where I left it last time. I can't see any options to do this.
cheers
-
I'd previously removed the NVRAM battery on the PPC board to test it so it would have lost the contents. It appears that if you use any other serial number and key it will not accept it so the serial number must be stored elsewhere on the board.
Also do you know if it's possible for this scope to remember the last settings because every time I reboot it defaults to it's own settings and ignores where I left it last time. I can't see any options to do this.
cheers
That's not what I've experienced when mucking around with these scopes. For instance, I remember one that had a dead battery, and a dead hard drive. I replaced the battery, and programmed the NVRAM. Then I imaged a new drive with an image from another scope. It assumed the serial # and option key from the scope that I imaged it with.
RE: the scope not remembering it's last settings, I see that all the time, so I think it's a bug in the firmware that never got fixed. Very annoying. It doesn't happen every time but quite often.
-
I'd previously removed the NVRAM battery on the PPC board to test it so it would have lost the contents. It appears that if you use any other serial number and key it will not accept it so the serial number must be stored elsewhere on the board.
Also do you know if it's possible for this scope to remember the last settings because every time I reboot it defaults to it's own settings and ignores where I left it last time. I can't see any options to do this.
cheers
That's not what I've experienced when mucking around with these scopes. For instance, I remember one that had a dead battery, and a dead hard drive. I replaced the battery, and programmed the NVRAM. Then I imaged a new drive with an image from another scope. It assumed the serial # and option key from the scope that I imaged it with.
RE: the scope not remembering it's last settings, I see that all the time, so I think it's a bug in the firmware that never got fixed. Very annoying. It doesn't happen every time but quite often.
But in that case you should be able to use other serial numbers and keys but you can't with the scope I have. Have you tried other keys and sn's ??
cheers
-
I'd previously removed the NVRAM battery on the PPC board to test it so it would have lost the contents. It appears that if you use any other serial number and key it will not accept it so the serial number must be stored elsewhere on the board.
Also do you know if it's possible for this scope to remember the last settings because every time I reboot it defaults to it's own settings and ignores where I left it last time. I can't see any options to do this.
cheers
That's not what I've experienced when mucking around with these scopes. For instance, I remember one that had a dead battery, and a dead hard drive. I replaced the battery, and programmed the NVRAM. Then I imaged a new drive with an image from another scope. It assumed the serial # and option key from the scope that I imaged it with.
RE: the scope not remembering it's last settings, I see that all the time, so I think it's a bug in the firmware that never got fixed. Very annoying. It doesn't happen every time but quite often.
But in that case you should be able to use other serial numbers and keys but you can't with the scope I have. Have you tried other keys and sn's ??
cheers
Well, yes, by accident. Just as I said above, right? When that happened, I had to wipe the Dallas chip by removing the battery, then edit .sn and .key offline to get the correct serial # back.
-
I'd previously removed the NVRAM battery on the PPC board to test it so it would have lost the contents. It appears that if you use any other serial number and key it will not accept it so the serial number must be stored elsewhere on the board.
Also do you know if it's possible for this scope to remember the last settings because every time I reboot it defaults to it's own settings and ignores where I left it last time. I can't see any options to do this.
cheers
That's not what I've experienced when mucking around with these scopes. For instance, I remember one that had a dead battery, and a dead hard drive. I replaced the battery, and programmed the NVRAM. Then I imaged a new drive with an image from another scope. It assumed the serial # and option key from the scope that I imaged it with.
RE: the scope not remembering it's last settings, I see that all the time, so I think it's a bug in the firmware that never got fixed. Very annoying. It doesn't happen every time but quite often.
But in that case you should be able to use other serial numbers and keys but you can't with the scope I have. Have you tried other keys and sn's ??
cheers
Well, yes, by accident. Just as I said above, right? When that happened, I had to wipe the Dallas chip by removing the battery, then edit .sn and .key offline to get the correct serial # back.
Were you able to get other options by using other sn's and matching keys ? I think i tried this first and the other keys and sn's would not be recognized so i'm pretty sure the sn is hard coded into another chip but I was still able to use the original sn and key and restore the original nameplate option without erasing the NVRAM ! What model is your scope ?
-
Were you able to get other options by using other sn's and matching keys ? I think i tried this first and the other keys and sn's would not be recognized so i'm pretty sure the sn is hard coded into another chip but I was still able to use the original sn and key and restore the original nameplate option without erasing the NVRAM ! What model is your scope ?
RE: Options. I didn't try that, but I'm sure it would work.
My observation is that it's not hard coded and only stored in the two locations I mentioned. You could repeat my (unexpected) experiment by wiping the Dallas chip, and editing the two files offline. :popcorn:
I don't remember what model # it was - either a TDS7054 or a TDS7104. I no longer have it as it was a repair job for a customer.
-
I'd previously removed the NVRAM battery on the PPC board to test it so it would have lost the contents. It appears that if you use any other serial number and key it will not accept it so the serial number must be stored elsewhere on the board.
Also do you know if it's possible for this scope to remember the last settings because every time I reboot it defaults to it's own settings and ignores where I left it last time. I can't see any options to do this.
cheers
That's not what I've experienced when mucking around with these scopes. For instance, I remember one that had a dead battery, and a dead hard drive. I replaced the battery, and programmed the NVRAM. Then I imaged a new drive with an image from another scope. It assumed the serial # and option key from the scope that I imaged it with.
RE: the scope not remembering it's last settings, I see that all the time, so I think it's a bug in the firmware that never got fixed. Very annoying. It doesn't happen every time but quite often.
But in that case you should be able to use other serial numbers and keys but you can't with the scope I have. Have you tried other keys and sn's ??
cheers
Well, yes, by accident. Just as I said above, right? When that happened, I had to wipe the Dallas chip by removing the battery, then edit .sn and .key offline to get the correct serial # back.
Were you able to get other options by using other sn's and matching keys ? I think i tried this first and the other keys and sn's would not be recognized so i'm pretty sure the sn is hard coded into another chip but I was still able to use the original sn and key and restore the original nameplate option without erasing the NVRAM ! What model is your scope ?
Hey snoopy!
Regarding the serial number problem, I had the exact same one with a tds7404 I purchased! I also had to replace the nvram battery.
The solution: in the boot console, you can see:
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
In the vxboot folder, you'll find a .tcs file (if I remember correctly). Simply remove that #, reboot the scope, put it again and your serial number will be fetched again from the .sn.
-
I'd previously removed the NVRAM battery on the PPC board to test it so it would have lost the contents. It appears that if you use any other serial number and key it will not accept it so the serial number must be stored elsewhere on the board.
Also do you know if it's possible for this scope to remember the last settings because every time I reboot it defaults to it's own settings and ignores where I left it last time. I can't see any options to do this.
cheers
That's not what I've experienced when mucking around with these scopes. For instance, I remember one that had a dead battery, and a dead hard drive. I replaced the battery, and programmed the NVRAM. Then I imaged a new drive with an image from another scope. It assumed the serial # and option key from the scope that I imaged it with.
RE: the scope not remembering it's last settings, I see that all the time, so I think it's a bug in the firmware that never got fixed. Very annoying. It doesn't happen every time but quite often.
But in that case you should be able to use other serial numbers and keys but you can't with the scope I have. Have you tried other keys and sn's ??
cheers
Well, yes, by accident. Just as I said above, right? When that happened, I had to wipe the Dallas chip by removing the battery, then edit .sn and .key offline to get the correct serial # back.
Were you able to get other options by using other sn's and matching keys ? I think i tried this first and the other keys and sn's would not be recognized so i'm pretty sure the sn is hard coded into another chip but I was still able to use the original sn and key and restore the original nameplate option without erasing the NVRAM ! What model is your scope ?
Hey snoopy!
Regarding the serial number problem, I had the exact same one with a tds7404 I purchased! I also had to replace the nvram battery.
The solution: in the boot console, you can see:
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
In the vxboot folder, you'll find a .tcs file (if I remember correctly). Simply remove that #, reboot the scope, put it again and your serial number will be fetched again from the .sn.
I think you mean topScript.hw
Yes you can easily change the serial number by overwriting the .sn file but it won't acknowledge the options that come with the corresponding key. It only seems to acknowledge the original serial number and key that came with the scope. I've tried clearing the NVRAM contents by removing the battery and booting up with a new serial number and key but it still won't give me any other options. If I put the original serial number and key back then it sees the 1M option so my conclusion is the serial number is stored somewhere else on the board.
cheers
-
oh right I misunderstood you.
IIRC I've seen a keygen being mentioned somewhere in that forum :)
-
oh right I misunderstood you.
IIRC I've seen a keygen being mentioned somewhere in that forum :)
If you find anything let us know ;)
cheers
-
I want to install 2M option in my tds5054 too :)
-
The code is still up on the xDevs site (https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/). There are some hints in the code about how to enable various options, but I think I ended up just setting a bunch of FF's and enabling everything.
########################################################################
4
# options masks/names/descriptions, conversion functions
5
6
# 01 - 1M
7
# 02 - 2M
8
# 04 - 3M
9
# 06 - 2M 2A
10
# 08 - 4M
11
# 00 00 00 00 00 00 04 - USB
12
# 00 00 00 00 00 00 20 - JT3
13
# 00 00 00 00 00 00 00 80 - ET3
14
# 00 00 00 00 00 00 00 00 08 - JA3
15
16
# 00 00 05 00 00 00 00 00 00 10 - ASM DDRA DJA
17
# 00 44 00 00 00 00 02 08 - SM ST J1 J3E
18
# 04 40 00 00 00 00 06 C0 10 - 3M JT2 USB2 ST
19
# 04 44 FF 03 00 00 8D A3 EF FF 17 - 10XL, MTH, PTH1, ASM, LT, DDRA, SLE, EQ, TDSDDM2, TDSUSB2, YDSCPM2, RTE, IBA, PCI, TDSDVI, TDSET3, SAS, TDSHT3, TBD, JA3, TDSPTD, TDSVNM, DPOPWR, TDSHT3v1.3, 73, 74, DJE, DJA, 77, 78, 79, SVE, SVP, SVM, SLA
-
How do you download the files from that link ?
cheers
-
Thanks, but the link doesn´t works :(
Do you have a copy?
Thanks!
-
Hey, no idea why the link doesn't work. Happy to send a copy to you if you want to PM me.
-
Hello everybody.
I bought TDS7154 without HDD. I'm trying to install software.
Found on this forum the necessary driver. Thank you so much!
But not all. also needed controller Texas Instrument PCI-1225 CardBus.
Maybe there is someone?
The installation algorithm is not quite clear.
Tell me please, who knows how to install correctly.
-
Hey, no idea why the link doesn't work. Happy to send a copy to you if you want to PM me.
I'm not finding either sites up:
https://xdevs.com/guide/tek_key/
https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/
I'd be very thankful for a copy.
Background if you are interested:
I received a few days back a TDS8000B that was stated on eBay as having Power Supply issues where they noted:
"Originally it was working but came back to us with a bad power supply. About once out of 20 times it will power on and light up. Sometimes it turns off by itself while booting. Most times it won't turn on at all then will make faint clicking ticking noise in the right rear of the unit. Screen has some scratching."
I powered on the unit and first time not thinking about having a keyboard plugged in to login and perform more testing as my brain was set to modern day touch screens with keyboards that appear on-screen as factory default. Powered on no issues, though is slow Windows 2000 Pro for sure.
After plugging in a USB keyboard with a USB to PS2 keyboard adapter, I pressed the power button on the front panel and was having no success with being able to use the keyboard to log in. I am guessing something to do with USB keyboard drivers is the reason.
Now, after holding the front panel power button for over 7 seconds, the unit powered off. When I tried to power back on, I heard a mechanical clock ticking sound with nothing happening. When I switched the power switch on the back of the unit the ticking sound slowly went away and all subsequent attempts to power on have failed with nothing happening.
Before I open the case up... any ideas to consider as I am making a giant leap into working on this system as I am still not yet graduated from a TDS-520 repair/restore... though am moving forward on that and learning a lot.
Just reading this page topic summary has bridged the programming firmware and electronics components like NVRAM and microcontroller gaps I've had.
-
Hey, no idea why the link doesn't work. Happy to send a copy to you if you want to PM me.
I'm not finding either sites up:
https://xdevs.com/guide/tek_key/ (https://xdevs.com/guide/tek_key/)
https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/ (https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/)
I'd be very thankful for a copy.
Background if you are interested:
I received a few days back a TDS8000B that was stated on eBay as having Power Supply issues where they noted:
"Originally it was working but came back to us with a bad power supply. About once out of 20 times it will power on and light up. Sometimes it turns off by itself while booting. Most times it won't turn on at all then will make faint clicking ticking noise in the right rear of the unit. Screen has some scratching."
I powered on the unit and first time not thinking about having a keyboard plugged in to login and perform more testing as my brain was set to modern day touch screens with keyboards that appear on-screen as factory default. Powered on no issues, though is slow Windows 2000 Pro for sure.
After plugging in a USB keyboard with a USB to PS2 keyboard adapter, I pressed the power button on the front panel and was having no success with being able to use the keyboard to log in. I am guessing something to do with USB keyboard drivers is the reason.
Now, after holding the front panel power button for over 7 seconds, the unit powered off. When I tried to power back on, I heard a mechanical clock ticking sound with nothing happening. When I switched the power switch on the back of the unit the ticking sound slowly went away and all subsequent attempts to power on have failed with nothing happening.
Before I open the case up... any ideas to consider as I am making a giant leap into working on this system as I am still not yet graduated from a TDS-520 repair/restore... though am moving forward on that and learning a lot.
Just reading this page topic summary has bridged the programming firmware and electronics components like NVRAM and microcontroller gaps I've had.
Sounds like caps in the power supply or possibly on the motherboard.
Also if you can't get into the bios setup you need to first check your cmos battery on the NLB motherboard and replace it if it is dead. Likewise for the power PC board. If your scope is anything like the experience I had with a TDS7054 then you probably still won't be able to get into the bios setup so you need to boot up in dos on a floppy and run a program like killCMOS to reset your CMOS memory and then you will, beable to get into the bios setup.
http://www.majorgeeks.com/files/details/killcmos.html (http://www.majorgeeks.com/files/details/killcmos.html)
You can create a bootup dos disk from another computer with a floppy using the setup from http://www.allbootdisks.com/download/dos.html (http://www.allbootdisks.com/download/dos.html)
cheers
-
Hello everybody.
I bought TDS7154 without HDD. I'm trying to install software.
Found on this forum the necessary driver. Thank you so much!
But not all. also needed controller Texas Instrument PCI-1225 CardBus.
Maybe there is someone?
The installation algorithm is not quite clear.
Tell me please, who knows how to install correctly.
Send me your email address ;)
cheers
-
Sounds like caps in the power supply or possibly on the motherboard.
Also if you can't get into the bios setup you need to first check your cmos battery on the NLB motherboard and replace it if it is dead. Likewise for the power PC board. If your scope is anything like the experience I had with a TDS7054 then you probably still won't be able to get into the bios setup so you need to boot up in dos on a floppy and run a program like killCMOS to reset your CMOS memory and then you will, beable to get into the bios setup.
http://www.majorgeeks.com/files/details/killcmos.html (http://www.majorgeeks.com/files/details/killcmos.html)
You can create a bootup dos disk from another computer with a floppy using the setup from http://www.allbootdisks.com/download/dos.html (http://www.allbootdisks.com/download/dos.html)
cheers
Since the HD slides out really easy... I'm going to plan to scan for errors and invest in replacing with a SSD to make sure I have a backup since HD's do fail.
Older computers have CD-ROM issues too, though I've not experienced having to replace a laptop CD/DVD-ROM drive. Might not be a bad item to consider. Interesting how the two boards from what I read are competitors systems, i.e. Power PC and Intel.
Once I open the cover, I'll use a stethoscope to trace where the noise is coming from and go from there. My thought was loose wire on transformer/torroid filter or something capacitor related though the frequency of the sound is higher than 50/60Hz though not in the KHz range. I wasn't sure if a transistor can make a noise also like that since I don't comprehend how and not sure why there would be a relay doing that unless there is some sort of fail safe tripped.
Here is a video of the sound that you can here at ~22 second in: https://www.youtube.com/watch?v=jG3vnesqhAY&feature=youtu.be (https://www.youtube.com/watch?v=jG3vnesqhAY&feature=youtu.be)
I'm not quite into adjustments on the scope yet since I need to read more if can be made from BIOS, Keysight IO or NI GPIB interface apps. However, any ideas on the down links for future reference and reading regarding options even though that is the last thing I need to be concerned with?
Best Regards
-
Hello everybody.
Some time ago I bought TDS7104 scope with PPC boot problem.
I have repaired it. Many thanks for TiN !.
I have replaced dallas battery with two AA lithium batteries. But the batteries were working no longer then two months.
After few try with new batteries I have build replacement chip with FRAM. It works well now.
I attach some photos with the replacement chip.
Tom.
-
Hello everybody.
Some time ago I bought TDS7104 scope with PPC boot problem.
I have repaired it. Many thanks for TiN !.
I have replaced dallas battery with two AA lithium batteries. But the batteries were working no longer then two months.
After few try with new batteries I have build replacement chip with FRAM. It works well now.
I attach some photos with the replacement chip.
Tom.
Likely that the Dallas chip was using too much current. I've seen that a number of times now. (Allows me to say once again that DALLAS/MAXIM SUCKS!)
Anyway, you made a custom board? :wtf:
-
Your FRAM board is very nice - you should consider selling them or sharing the PCB and parts list.
-
Hello everybody,
Some good news following my posts last september about my TDS7054. It is now working fine :-+.
Many thanks to the members of this fantastic forum, especially Jay, TheSteve and TiN who helped me to focus quickly on the NVRAM issue.
I eventually unsoldered this NVRAM from the PPC board and tested it separately : it proved defective. Curiously, it seems that the access time when reading data was substantially longer than specified : the chip needed several ms (yes, milliseconds) to output data. Moreover, the standby current was around 600µA, which depletes very quickly the backup battery.
Before ordering a new NVRAM, I decided to try to replace the SRAM chip soldered on the underside of the NVRAM.
The standard Cypress SRAM chip have been replaced by an Alliance Memory AS6C1008-55TIN chip (costs around 2€...).
Since I am not familiar with SMD rework, it was a pain to manage the 0.5mm pitch but I eventually succeeded.
With the new SRAM chip, the standby current is now 4µA. It's a bit higher than expected but I plan to install in a convenient location a CR123 battery I have on hand and connect it to the NVRAM by wires. The CR123 capacity should provide decades of autonomy (in theory..).
And of course the TDS now powers up normally. The SPC runs also without error :)
Pascal
-
Congratulations Tom (TxB) for your FRAM board. Very impressive.
It looks as professional as the surrounding PPC board.
Pascal
-
Hi,
After two weeks replacement chip with FRAM memory works well.
I have two partially mounted boards without FRAM soldered to share if someone need it.
If there is some need I can order few pcb more.
I attach schematics of the board.
Tom.
-
Hi Tom (TxB),
The genuine DS1245 includes a circuit to write-protect the SRAM chip as soon as the Vcc voltage goes out of tolerance during power down. In your design, don't you worry about random writes during power-down, which may corrupt stored data ?
Pascal
-
Besides that, I have just seen that HP also used similar Dallas/Maxim NVRAM DIP28 chips, with non serviceable lithium battery, directly soldered on PCB, in their top-rated 3458A 8.5 digits multimeter, to store VITAL calibration data :palm:
-
Hi,
The chip used as NV memory: FM28V100 has internal write inhibit function if supply is out of tollerance.
I test the scope everyday and it work with my chip without problem for three weeks.
Tom.
-
Hello ALL,
I'm a newcomer here attracted by this GREAT thread.
After read this thread, I got a used but full functional TDS7254B for about 35000 RMB in China, a great deal.
I'd like to know is there many people have TDS7000B series? Is there any thread talk about how to improve/hack this series?
Thanks.
-
Hi,
The chip used as NV memory: FM28V100 has internal write inhibit function if supply is out of tollerance.
I test the scope everyday and it work with my chip without problem for three weeks.
Tom.
Nice. I'll make a clone of this design. I just got a TDS7104 for free. I'm looking into upgrading the CPU and RAM. I'll also search for an IDE SSD.
I guess the 3M option is the maximum record length memory.
(https://uploads.tapatalk-cdn.com/20180217/a1ee151d36f328d1a4f5af440481c8bc.jpg)(https://uploads.tapatalk-cdn.com/20180217/902442080aa082df34b8f6dc5b2c60e2.jpg)
-
Hi,
After two weeks replacement chip with FRAM memory works well.
I have two partially mounted boards without FRAM soldered to share if someone need it.
If there is some need I can order few pcb more.
I attach schematics of the board.
Tom.
Can you share the layout?
Has anyone replaced the floppy drive with a Gotek floppy emulator?
One option would be to route an USB extension cable to the floppy slot.
I would like to have an USB port at the front for saving waveforms and images
-
Phew.... I though at first this only got 50ohm inputs. Luckily this model also got 1M inputs.
Has anyone made diy active probes for TDS7000 series?
-
Only fault so far is signal path compensation failure. It passed the fifth time. Any idea what may be the cause?
The prope compensation square wave got some spiking. Is it normal?(https://uploads.tapatalk-cdn.com/20180219/2e19045b641e45984992b079e027a18f.jpg)(https://uploads.tapatalk-cdn.com/20180219/62408f9b00f87c11a30753cf87dc7864.jpg)
-
@plazma
Please write to priv about the chip with FRAM.
Tom
-
Is it possible to get more info about the SPC fail from the PPC debug port?
-
I'd like to know is there many people have TDS7000B series? Is there any thread talk about how to improve/hack this series?
I have the TDS8000 and TDS8000B and am interested in hacking to improve this series also. Read through the thread as there are a few easy upgrades documented well.
I would like to see DIY Options modules and probes since they are so expensive. Anyone aware of references?
Thanks
:popcorn:
-
One option would be to route an USB extension cable to the floppy slot.
I would like to have an USB port at the front for saving waveforms and images
I haven't opened my TDS8000(B) up yet though am guessing the floppy is a slim or smaller height as I want to say there are smaller height than the 1" drives that were on the market like half inch in height. Parts lists notes 0.5 IN.
In regards to the USB, a USB hub I'm thinking will work with a USB 3.5" drive also... though velcro an extension cable on the case may be easier to implement unless there is room to cut into. I have to look inside to see what the space and connections are like.
I haven't looked at the BIOS capabilities for use as the USB as a FLOPPY.
The USB options seem real easy unless there is a BIOS limitation for FLOPPY boot up functions.
-
I assembled the FRAM board today. I'll install it later after I receive the rest of the upgrade parts.
(https://i.imgur.com/r3U4rrQ.jpg)
-
A little update, with EEVBlog forum member magic, we can get keys for options on TDS7000/CSA7000 and probably other 70000 series scopes too :)
Quick check of concept proof with my CSA7404:
(http://dev.xdevs.com/attachments/1009/options_ffff.jpg)
16 options enabled :)
Need to find out which bit does what and we good to go!
Hi Tin,
I recently picked up a TDS7104 myself. This one was missing it's hard drive. After sorting that out, and repairing a SPC issue I noted two things: It had option 3M which was a nice surprise, but it would crash the tek scope application when I ran the diagnostic.
After fiddling around with different ghost images for the scope and messing around through the console port I found that option 3M had disappeared, but now I have option Jitter analysis 2, which wasn't there before. |O
Crap! I'd much rather have option 3M back...
I suspect that it was my mucking about with the console port settings. The original looked like this:
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topScript.hw
But it seems I cannot go back to that, as the prompts are now somewhat different.
Update: I also just noticed that the serial number reported in the about menu now does not match what is on the sticker of the unit in the back of the scope. The "about" menu reports it as B021068, but the sticker says it is B021079! I bet that has something to do with it!
Would you have any idea how I could get option 3M back?
Thanks!
Jay
Just wanted to add that I just restored a TDS7104 with these settings. Thanks for sharing :D
-
Figured this is as good a place as any to ask: I'm putting back together the TDS7104 but I can either put her back in a rack mount jacket or I can, I think, take the trim of a CSA8000 and make here a nice desktop unit.
What would you guys do? What would be easiest to sell?
-
Well, the trim of the CSA8000 doesn't fit anyway, so I put her back together with the rack handles :-+
-
Hello!
May anybody help me with TDS7154B? Can't find right video driver for Tvia CyberPro 5202 video card (received error message: "videport.cpp error ----> CreateVideoPort::hr::..............")?
Thank you!
-
Hello everybody.
I need some help with DPO7104 scope.
I'm trying to restore system and aplications after hdd serious crash in DPO7104 scope in our lab.
After lots of attempts I can install dpo software version 5.3.5.
However during aplication startup there is an error: clr20r3.
Maybe someone can provide original restore disc contents ?.
I looks I don't have some driver installed.
HDD image from working DPO7104 will be also very usefull fo me.
-
Would love to help but I sold mine :-\
-
May be someone can help with information about unlocking options on this oscilloscopes?
-
Gents, I got a TDS7104 on the bench that has NVRAM restored but there are still some issues. Mostly 'forgetting' saved states, stuff like that. I'm also missing a file: 'dio_rst.vsh'
Anyone has it for me by any chance?
*edit*: never mind. Read page 5 8)
Anyone ever fixed the fact it doesn't rememeber mast state?
-
The serial port pinout on the 10 pin connector is easy: it is such that if you get a 10 pin connector to IDC ribbon cable, then a female 9 pin D connector to IDC ribbon cable, it will work with your standard RS232 line from a PC.
-
Hey,
Recently had the need to decode some UART data and replay it over an arbitrary waveform generator. Wrote a quick python script to do the decode and show the resulting frames on the scope and on a bitmap on my laptop. Library supports most low speed serial protocols and USB 2.0 as well, so should be pretty flexible. Including in case anyone else finds it useful:
import ivi
import numpy as np
import vxi11
import re
from numpy import *
from matplotlib import pyplot as plt
import ripyl
import ripyl.streaming as stream
import ripyl.protocol.uart as uart
from collections import OrderedDict
try:
import matplotlib
matplotlib_exists = True
except ImportError:
matplotlib_exists = False
if matplotlib_exists:
import ripyl.util.plot as rplot
class AsciiWaveform:
def __init__(self, waveformString ):
waveform_list = re.split(';',waveformString)
self.CURVE(waveform_list[17])
def CURVE(self,value):
# Make this faster later
waveform = []
for val in re.split(',',value):
try:
waveform.append(float(val)/6400)
except:
pass
self.waveform = np.array(waveform)
tds = vxi11.Instrument("192.168.1.25")
awg = ivi.tektronix.tektronixAWG2021("ASRL::COM5,19200::INSTR")
tds.write("DATA:SOURCE CH1")
tds.write("DATA:ENCDG ASCII")
tds.write("DATa:BYT_NR 1")
record_length = int(tds.ask("HORizontal:RECOrdlength?"))
tds.write('DATa:STOP {}'.format(record_length))
tds.write("CURSor:VBArs SNAp")
waveform_data = tds.ask("WAVFrm?")
awf = AsciiWaveform( waveform_data )
# transfer to AWG2021
awg.outputs[0].arbitrary.create_waveform(awf.waveform)
awg.outputs[0].arbitrary.gain = max(awf.waveform)
awg.outputs[0].arbitrary.offset = float(tds.ask("WFMInpre:YOFf?"))
awg.arbitrary.sample_rate = tds.ask("HORizontal:MAIn:SAMPLERate?")
awg.outputs[0].enabled = True
sample_period = float(tds.ask("WFMOutpre:XINcr?"))
txd = stream.samples_to_sample_stream(awf.waveform, sample_period)
bits = 8
parity = 'even'
stop_bits = 1
polarity = uart.UARTConfig.IdleHigh
baud_rate = 115200
records = list(uart.uart_decode(txd, bits, parity, stop_bits, polarity, baud_rate=baud_rate))
data = [rec.data for rec in records]
lines = ''.join(chr(d) for d in data).split()
tds.write("CH1:LABEL:NAMe \"{}\"".format(lines))
tds.write("CH1:LABEL:XPOS 5")
tds.write("CH1:LABEL:YPOS 3.5")
txd = stream.samples_to_sample_stream(awf.waveform, sample_period)
channels = OrderedDict([('Volts', txd)])
title = 'UART Plot'
plotter = rplot.Plotter()
plotter.plot(channels, records, title, label_format=stream.AnnotationFormat.Text)
plotter.show()
-
Recently had the need to decode some UART data and replay it over an arbitrary waveform generator. ...
Not sure I follow, can you share more details? You sampled data from scope and analyzed using python, or ? :-BROKE
-
Yah so it's pretty difficult to run any modern software directly on the scope, even with it being upgraded to WinXP. Most packages that will do waveform analysis rely on Intel instruction sets like MMX that don't exist on the Celeron processor my scope uses. Since the scope runs a VXI-11 server you can connect to it over TCP and do things like copy waveform data / draw labels. To decode my captured UART waveform I ran the above script on my laptop, which dumped the waveform, decoded it, and generated an image / labeled the waveform on the scope with the resulting ascii data.
Separately I wanted to replay the captured waveform with some introduced noise, so the script also shows how to take the captured waveform and send it to an arbitrary waveform generator.
-
Yah so it's pretty difficult to run any modern software directly on the scope, even with it being upgraded to WinXP. Most packages that will do waveform analysis rely on Intel instruction sets like MMX that don't exist on the Celeron processor my scope uses.
The TDS7000 scopes use a minimum of a 500MHz socket 370 Celeron which does have MMX. MMX was introduced with the socket 7 processors (a 233MHz Pentium IIRC).
-
Excellent info thanks! I actually tried running this script on my scope with a 1.x version of anaconda (newer versions need windows 7 or higher I think) and the runtime threw an exception about the cpu architecture not supporting a specific instruction set extension. Must have misremembered the specific error though.
EDIT: attached a screenshot - it fails on SSE2 instructions
-
I assembled the FRAM board today. I'll install it later after I receive the rest of the upgrade parts.
(https://i.imgur.com/r3U4rrQ.jpg)
Just wondering... Did you ever install it? Does it work?
-
Hey, could you help? I have a CSA8000 that get stuck on the initialization screen of the 8000 series scope. I already changed the battery (used a bigger one this time, no use to change it to the same) and I had the cables connected to the MAX232 chip as you shown on your photos, plugged in with micro connector. I do have some serial to USB device (NI USB to RS232) that I connected, but I fail to capture the activity in any terminal.
Is connecting the USB-232 OK or the chip connections that you show are only UART signals? What terminal software you use to capture all that chat?
Thank you very much in advance,
Gaston
GastonBA@gmail.com
-
I use Putty. You can also catch it on the 2x8 0.100" on the edge of the board
-
I am connecting like this through a USB to serial National Instrument device, that does not show any activity.
Programming putty just show me a green cube. Something is wrong.
Could someone confirm that these connections are intended for Serial device and not a other kind, like UART?
Thank you,
Gaston
-
I got it working by browsing the million posts that are in this repair topic... Got the side RS232 connection port made with a special cable. Thank you all.
-
Hello All,
My TDS7054 was finally working fine. I removed the 3 V battery on the motherboard for couple of minutes and placed it back. subsequently the scope stopped working. When it is turned on, all its buttons light up and stay on, you can hear floppy drive noise and couple of beeps but display remains blank, that is all, no further activity!
I hope someone be able to guide me through solving this problem. I am hoping that there will not be a need for programming anything which is beyond my capability as I am not a computer specialist.
Regards
-
The 3V battery of the 'windows system'? That's the CMOS battery, in which case the Bios 'forgot' to put the screen on the LCD screen. Attach a display with VGA cable on the back.
It's probably stuck on 'CMOS checksum error' or 'Keyboard error' or some such which is also why it is not booting very far.
-
The 3V battery of the 'windows system'? That's the CMOS battery, in which case the Bios 'forgot' to put the screen on the LCD screen. Attach a display with VGA cable on the back.
It's probably stuck on 'CMOS checksum error' or 'Keyboard error' or some such which is also why it is not booting very far.
What he said. You have to plug into the motherboards VGA port instead of the scope out VGA port. In the BIOS setup, set the default video interface to PCI instead of AGP/onboard. Save and reboot.
Tek should have had the BIOS customized for this. :--
-
Gentlemen,
I really appreciate for your help and your fast reply. I know now what to do.
I however have one more problem (my original problem that led me to remove the CMOS battery). Some two weeks ago, I decided to replace the scope's hard drive with a SSD (bad bad mistake!). The scopes hard drive got damaged during making the image file (friend was helping) and although I have the original restoration dick that came with the scope, it was giving the lack of memory error message when I tried to recover TEK's original win98. Finally TEK emailed me with the right restoration file and I managed to install the original win98 on SSD along with the firmware 2.55. This process by itself was a major time sink for me (FAT 32 formatting for the SSD to be recognized, etc, etc).
After everything working again, I needed to install the scope's option, but realized that the scope's serial number was somehow missing on TEK Scope program. I called TEK for help and they wanted me to send them the scope for repair! That is when I came across your website and learned that one could add a .sn in vxBoot folder to provide the serial number to the scope. I decided to experiment first with an example file that was provided by someone with their own serial number, since I did not know how to create and edit HEX files. Well, it did work, but the scope has stuck with the wrong serial number and I can't override the wrong serial number (on the positive side, I now know how to edit HEX files :)). I still can't install the original options. After further reading on your website, I learned that one should both delete the .sn file and remove the battery for the Dallas chip to be wiped clean in order to change the serial number to is original value. You may laugh, but the only battery that I could clearly see, was the CMOS battery on the motherboard so I removed it, which of course added to my original problems.
Would you please let me how I can override the wrong serial number stored on the scope and replace it with the original one so that I can install its options.
Thanks in advance.
-
You may want to read through the entire thread. Taking away the battery from the Dallas chip will keep the Tek soft from working until you restore the contents of it.
-
Good morning guys, I just got a TDS7054 and in the product description it was saying “it doesn’t work”. It happens that at the first moment I turned on, it showed a white screen, and about 2 minutes later it turned off and didn’t turned on again. I checked up the boards and seems like there is no damaged components. The PPC board doesn’t give any operation signal. I tried to measure the voltage of the power supply, but the only voltage found was the + 5VDC in pin c1 of the rear power distribution. When I do the jumper on Power-On Debug on the PPC card, all LEDs flash once more without any operation signal. Has anyone ever seen such problem? Could anyone give me any suggestions? And, another thing, is there a way to perform the voltage test on the power supply with it off the oscilloscope.
-
Hello All,
Some messages above was mentioned the board with FRAM, does someone has the gerber file for the board please ?
Best Regards
(https://i.imgur.com/r3U4rrQ.jpg)
-
Hi Guys,
Just want to add to the thread some things.
My tds7104 had a broken 2.5V dcdc converter module on the poeerpc board.
After removing the w soic8 fets with hot air, it was clear, that this was due to nad soldering - actually it looked as if there was never solder under some pads.
I checked the fets externally and they were working fine.
After resoldering them properly rhe ppc board started up nicely and I saw first time the scope application :-)
Best regards,
Kai
-
Thanks to this great forum I was able to restore a TDS7104.
BIOS battery was dead on the BL440ZX mainboard and HDD was missing. Would not enter BIOS at startup and would not recognize any drive on the second IDE channel. Default video output was VGA (no output on the LCD).
I therefore loaded up a DOS floppy and corrupted the CMOS (a small program called "corrupt.exe" was posted in another thread). I could then enter BIOS and switched to PCI video output. This also solved the missing second IDE channel and I could boot the CDROM.
I then installed a fresh WIN 2K SP4 copy on a 40GB HDD, the required Tek drivers posted in this thread and the Tek app v2.5.5 (max version for this scope).
NVRAM battery was still juicy though on the low side. Of course to find that out one would need to take it apart and RAM content just vanishes |O. So I reconfigured the PPC boot sequence via the serial console. Now the scope app started just fine, the relays were clicking and front panel was switching. However there was no trace in display and SN and key was missing.
I edited the SN and key files with the data on the back of the scope, placed them in the c:\vxBoot\ folder and modified the topScript.hw file by uncommenting the line "# NvramClearDb = 1". I boot once and the SN and key were transferred to the NVRAM. I then commented back the line. Now the SN and key were available in the scope app but still no trace.
Some other thread offered a hint: the custom PPC video driver was not loaded properly so I reloaded the files in Windows Device Manager. This did the magic: the scope is now fully functional and passes the self diagnosis flawlessly.
I did try to install Win 98SE but the scope app just kept crashing. So I will stay with Win 2K for the moment. CPU is much cooler than in Win 98 and it's fast enough. RAM consumption is a bit on the high side so I might supplement it.
Thanks TiN, Jwalling and all the others for the great info!
-
So... Have another one of these on my bench. Two actually. This one boots but hangs in windows trying to load the application. Also crashes when you plug in a USB mouse in one of the ports. Serial was clean (ie loaded NVRAM fine...) but this doesn't look great:
tcsLoadTableToNVRAM "pc:c:/vxBoot/setup.tcs"
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): Program enable command didn't echo back properly.
logTask: 1 log messages lost.
value = 0 = 0x0
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
0x16987e0 (tShell): Acq processor powerup failure!
Hmm, cracking her open. Any guesses as to what my next move would be?
(https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/?action=dlattach;attach=681671;image)
-
Eh, well, I'll tell you.
I cracked open another 7404B to swap the Intel boards. Guess what...
(https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/?action=dlattach;attach=689235;image)
-
My TDS7154 came from Taiwan, lots of dust inside but otherwise in very good shape in and out. On power up, all front face LEDs are lit, fans spinning and nothing else was going on. By accident I discovered that W2000 boots up after 5 minutes or so. Power PC (PPC) 7 segment display was solid on .8 no activity on console port. I went through all eevblog posts related to TDS7104 as originated by TiN, learned a lot but couldn’t make meaningful start. I contacted andy2000 because symptoms on his TDS7154B were similar to mine. He responded but couldn’t help at the time, he helped me greatly later with opening the world of options. Big thanks. Because I learned a lot, or better to say everything about TDS scopes from this forum I thought it would be fair to share my experience and potentially help somebody new like me. In retrospect, all the answers were already in the forum trail, thanks TiN. I just didn’t read them right and understood things correctly. Reading back the same posts as my understanding of the problem became better was the path to the solution.
In summary my TDS7154 needed PPC fix, hardware, new DC/DC converter PT6409P and Dallas NVRAM DS1245Y – 120 chip and, software, restoring NVRAM data using service port and directing vxWorks boot sequence to copy serial number (SN) form hidden directory c:\vxBoot\.sn file to the NVRAM.
There are folks in the forum that mentioned DC/DC converter on the PPC board and I initially didn’t pay much attention to it. Nevertheless, after checking voltage as per the service manual table (all values were good) I checked DC/DC chip output too and it was 0.4V instead of 2.5V. I struggled removing it from the board, could not desolder 3 ground pins in the middle. In the end I had to swing it left and right until all pins broke, then I hot air blew the stubs out. Pins on the removed chip were still accessible so I hooked up 5V to input and ground and indeed the output was missing. I thought what might have caused the failure, quick resistance check on the PPC board did not show any shorts. I attributed the failure to the chip itself. Removing Dallas NVRAM was a breeze, version I have is older DIL with encapsulated battery. I thought of grinding off the case to expose the battery, chop off the original and solder new one on top but gave up for fear of damaging the PCB. I’m not sure that it was even defective, it was reasonable to assume the battery is dead given the vintage of the instrument. I thought of installing a socket, unfortunately didn’t have one in the shop. I reassembled everything, on power up all was good except for the missing SN on the scope Help/About page.
I celebrated too early, restoring the SN turned out to be more challenging than I anticipated. I spent some time following eevblog folks’ steps (i.e. removing the # in # NvramClearDb = 1 line of vxBoot/topScript.hw script and making sure that .key and .sn files are there and have correct content). I also used HyperTerminal on console port (old RS232 ribbon cable was perfect interconnect between RS232 cable and console port, it was difficult to find one) to see if there are any errors while booting but all looked normal and terminated correctly when scope application is loaded and running. Not that I have a need for it (as a matter of fact I don’t have any need for the scope itself except for the challenge of fixing it) or the options, it is just part of the whole adventure. I Ghost imaged existing HD to 2 SSD disks, both work correctly so I’ll be more confident playing aggressively with software artifacts.
I reread again eevblog posts related to vxWorks boot sequence, did some Google work to educate myself on vxWorks subject and I realized that I didn’t read the eevblog posts carefully enough to see important details as outlined in the initial TiN post. With new understanding using service port and HyperTerminal I stopped vxWorks boot sequence by hitting any key at the right time. Then used “p” to see/record initial parameters the most important being flags (f): 0x1008. I used “c” command parameter to force vxWorks boot to copy *.sn from HD location by setting flags (f): 0x1000, and other (o): nvfs=0x1000. I kept startup script (s) :c:\vxBoot\topscript.hw, used “p” again to verify that I entered the right thing, then “@” to reboot and the whole script flew, 7 segment went through P then blinking ‘-“. I didn’t see Help/About updated until I shut down the instrument and rebooted again. Voila, all was good now, S/N was correct and options were listed. Since I was in vxWorks mood I tried different .sn (not equal to the S/N printed on the back of the scope and inside on the chassis) but I was not able to install any options, either I don’t know what I’m doing or the S/N is hard coded somewhere in the PPC board or elsewhere. I’ll have to read eevblog TDS trail again; I remember somebody was talking about this.
Big thanks goes to TiN and all other folks who contributed and helped me to fix the device. In my view, the biggest help is to know that there are still good and competent people somewhere in the universe, so the hope still remains despite all the buffoonery we witness every day!
-
Hello
I bought TDS7104 without HDD.
Just installed usual Win2000 OS in 32GB ssd, installed drivers for PPC board and USB Front panel and downloaded TekScope 2.5.5 from tek site.
Tek scope starts up.
However, there are buttons that are not glowing.
Also, such a screen appears and does not work properly.
Do you know any solution?
-
Yup, you need read a thread :).
Keys don't work because USB FP driver not installed.
Screen does not show signals because Tek VGA driver not installed.
-
The code is still up on the xDevs site (https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/). There are some hints in the code about how to enable various options, but I think I ended up just setting a bunch of FF's and enabling everything.
########################################################################
4
# options masks/names/descriptions, conversion functions
5
6
# 01 - 1M
7
# 02 - 2M
8
# 04 - 3M
9
# 06 - 2M 2A
10
# 08 - 4M
11
# 00 00 00 00 00 00 04 - USB
12
# 00 00 00 00 00 00 20 - JT3
13
# 00 00 00 00 00 00 00 80 - ET3
14
# 00 00 00 00 00 00 00 00 08 - JA3
15
16
# 00 00 05 00 00 00 00 00 00 10 - ASM DDRA DJA
17
# 00 44 00 00 00 00 02 08 - SM ST J1 J3E
18
# 04 40 00 00 00 00 06 C0 10 - 3M JT2 USB2 ST
19
# 04 44 FF 03 00 00 8D A3 EF FF 17 - 10XL, MTH, PTH1, ASM, LT, DDRA, SLE, EQ, TDSDDM2, TDSUSB2, YDSCPM2, RTE, IBA, PCI, TDSDVI, TDSET3, SAS, TDSHT3, TBD, JA3, TDSPTD, TDSVNM, DPOPWR, TDSHT3v1.3, 73, 74, DJE, DJA, 77, 78, 79, SVE, SVP, SVM, SLA
It works!, firts I have ask Tektronix for a quote for 2M option with out answer, is a old scope, may be is out of support.
Now I have 8 megapoints for sweep!
:scared: :scared: :scared: :scared:
-
i have a PC motherboard (the pentium board) , PowerPC motherboard (the one with the powerpc process, dallas chip and led display that runs vxworks) , acquisition board (damaged , but a good donor for parts and connectors !) , power supply and LCD / touchscreen for sale for these machines.
Working PC motherboard : 150$
Working PowerPC controller : 150$
Acquisition board (shot. broken channel , missing some heatsinks ). Good donor for the special input connectors and rigid cables. : 50$
Power supply board : 150$
Touchscreen ( has a small scratch, but works fine ) : 100$
-
Quote from: dretay on November 29, 2017, 23:42:37 (https://www.eevblog.com/forum/index.php?topic=20744.msg1362960#msg1362960)The code is still up on the xDevs site
(https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/ (https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/)). There are some hints in the code about how to enable various options, but I think I ended up just setting a bunch of FF's and enabling everything.
########################################################################
4
# options masks/names/descriptions, conversion functions
5
6
# 01 - 1M
7
# 02 - 2M
8
# 04 - 3M
9
# 06 - 2M 2A
10
# 08 - 4M
11
# 00 00 00 00 00 00 04 - USB
12
# 00 00 00 00 00 00 20 - JT3
13
# 00 00 00 00 00 00 00 80 - ET3
14
# 00 00 00 00 00 00 00 00 08 - JA3
15
16
# 00 00 05 00 00 00 00 00 00 10 - ASM DDRA DJA
17
# 00 44 00 00 00 00 02 08 - SM ST J1 J3E
18
# 04 40 00 00 00 00 06 C0 10 - 3M JT2 USB2 ST
19
# 04 44 FF 03 00 00 8D A3 EF FF 17 - 10XL, MTH, PTH1, ASM, LT, DDRA, SLE, EQ, TDSDDM2, TDSUSB2, YDSCPM2, RTE, IBA, PCI, TDSDVI, TDSET3, SAS, TDSHT3, TBD, JA3, TDSPTD, TDSVNM, DPOPWR, TDSHT3v1.3, 73, 74, DJE, DJA, 77, 78, 79, SVE, SVP, SVM, SLA
It works!, firts I have ask Tektronix for a quote for 2M option with out answer, is a old scope, may be is out of support.
Now I have 8 megapoints for sweep!
:scared: :scared: :scared: :scared:
Hi, all old url's for "testing" options don't work anymore. Is there anyway to get information how to do this option "testing"? :)
Ramppa
-
I came along a TDS7154B and the test shows an error for DemuxG and DemuxH (377 and 378). Everything else seems to work. The memory on the acquisition board are Cypress CY7C1361B-133AC i think. But there are 64 of them and obviously it could be something else. So any information is welcome ! Is there any more information on the serial when one is running this test ? Thanks !
-
Hi guys, I was able to repair a TDS7054 thanks to this forum: THANK YOU!! (specially TiN that started the whole thing) ^-^
I do have a couple of questions:
a) I've seen that memory used should be PC133 but mine says PC100: As I'm looking to upgrade, what should I be aiming for? (my MOBO is a BL440ZX)
b) Do you know where I can find the program for the options? (I already have 3M but I don't mind testing the others)
c) What's the benefit of upgrading the OS to win2000? (I feel that win98 is fast and I can't see how it's limiting me at the moment)
d) Is it possible to do serial decoding with this oscilloscope? (UART mainly)
Thank you!
-
a) You wouldn't see a difference be it PC100 or PC133.
c) I think w2k is easier to work with if you have network/usb drives etc.
d) Nope, too old stuff.
-
Finally I got my TDS5054. It's mechanically quite badly abused (dropped), but I managed to fix bottom covers. Electrically it's seems to be working nicely (SPC gives OK). I added connector to serial port, but there is only couple character when scope is starting application and there is no c:\vxboot folder. I tried to find some debugging information to this series, but there is very little to found.
I also looked acq board/front end modules (didn't remove covers), there is capasitors to gnd on every modules back side (C325+C332) and instantly I remembered how to modify TDS754->TDS784 500MHz->1GHz bandwidth. Is this similar difference between TDS50**/TDS51** 500/1000MHz...
Ramppa
-
there is no c:\vxboot folder.
It may be hidden... Check your explorer view options.
-
Hi, I'm little late, but does anyone have this option stuff saved?
Ramppa
Quote from: snoopy on 2017-12-24, 15:50:07 (https://www.eevblog.com/forum/index.php?topic=20744.msg1382816#msg1382816)>Quote from: PrecisionAnalytic on 2017-12-24, 09:06:03 (https://www.eevblog.com/forum/index.php?topic=20744.msg1382634#msg1382634)>Quote from: dretay on 2017-12-05, 07:19:04 (https://www.eevblog.com/forum/index.php?topic=20744.msg1366917#msg1366917)Hey, no idea why the link doesn't work. Happy to send a copy to you if you want to PM me.
I'm not finding either sites up:
https://xdevs.com/guide/tek_key/ (https://xdevs.com/guide/tek_key/)
https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/ (https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/)
I'd be very thankful for a copy.
Background if you are interested:
I received a few days back a TDS8000B that was stated on eBay as having Power Supply issues where they noted:
"Originally it was working but came back to us with a bad power supply. About once out of 20 times it will power on and light up. Sometimes it turns off by itself while booting. Most times it won't turn on at all then will make faint clicking ticking noise in the right rear of the unit. Screen has some scratching."
I powered on the unit and first time not thinking about having a keyboard plugged in to login and perform more testing as my brain was set to modern day touch screens with keyboards that appear on-screen as factory default. Powered on no issues, though is slow Windows 2000 Pro for sure.
After plugging in a USB keyboard with a USB to PS2 keyboard adapter, I pressed the power button on the front panel and was having no success with being able to use the keyboard to log in. I am guessing something to do with USB keyboard drivers is the reason.
Now, after holding the front panel power button for over 7 seconds, the unit powered off. When I tried to power back on, I heard a mechanical clock ticking sound with nothing happening. When I switched the power switch on the back of the unit the ticking sound slowly went away and all subsequent attempts to power on have failed with nothing happening.
Before I open the case up... any ideas to consider as I am making a giant leap into working on this system as I am still not yet graduated from a TDS-520 repair/restore... though am moving forward on that and learning a lot.
Just reading this page topic summary has bridged the programming firmware and electronics components like NVRAM and microcontroller gaps I've had.
Sounds like caps in the power supply or possibly on the motherboard.
Also if you can't get into the bios setup you need to first check your cmos battery on the NLB motherboard and replace it if it is dead. Likewise for the power PC board. If your scope is anything like the experience I had with a TDS7054 then you probably still won't be able to get into the bios setup so you need to boot up in dos on a floppy and run a program like killCMOS to reset your CMOS memory and then you will, beable to get into the bios setup.
http://www.majorgeeks.com/files/details/killcmos.html (http://www.majorgeeks.com/files/details/killcmos.html)
You can create a bootup dos disk from another computer with a floppy using the setup from http://www.allbootdisks.com/download/dos.html (http://www.allbootdisks.com/download/dos.html)
cheers
-
Quote from: Jwalling on Today at 11:45:10 (https://www.eevblog.com/forum/index.php?topic=20744.msg2671674#msg2671674)>Quote from: OH2LIY on Yesterday at 23:31:04 (https://www.eevblog.com/forum/index.php?topic=20744.msg2670804#msg2670804)
there is no c:\vxboot folder.
It may be hidden... Check your explorer view options.
Hi, all explorer setting should be in right position to show hidden files/folder. This is TDS5054, should there be \vxboot folder?
Ramppa
-
Thank You to Everyone who was/is active on this project! I just activated ab. every possible options to my scope :D
Ramppa
-
Thank You to Everyone who was/is active on this project! I just activated ab. every possible options to my scope :D
Ramppa
Do you know what means AV NV?
-
Hi everybody,
I worked on my problems with the TDS7054 and I hope that I have found a final solution.
As described I get this DIO.exe "illigal operation" failure, so I decided to install fresh Win2K, cause the Win98 Version was installed in 2001. After installation and get all necessary drivers I started the Tek Scope Software 2.5.5. Everything worked, the scope buttons where on screen, the frontpanel worked correct, but there was no waveforms shown on the screen |O.
In the documents of my scope I found an Win2k updateoffer direct from Tektronix. There was written, to update my TDS7054 the mainboard must be changed :--
So I conclude:
My Scope has the old BL440ZX PC Mainboard with an Celeron 533 Prozessor on it and with this board it isn't possible to run Win2k and WinXP. If anyone knows a solution to run a newer OS on my scope please describe here!
So deeply disappointed I installed WinME (had no 98 install CD and ME supports USB Sticks) on a newer Harddrive.
After insalling all drivers and the TekScope App at least my Scope work fine whitout the DIO.exe failure. :phew:
@ Serge: Have you managed get your Scope working?
schersch
Hi schersch and all, I have some new info:
1) It DOES work!
I mean, I've managed to install win2000 on a BL440ZX. Steps are what someone here already mentioned:
a) Fresh win2000 install
b) Install custom drivers (for front end, fonts, etc.)
c) Replace the standard "Chips and Tech 69000" driver with the one mentioned here
d) Install 2.5.5 firmware: this is where it got difficult because no matter what I did, it always mentioned that the file was "corrupt" while decompressing the install exe.
What I did is take the different setup files directly from the temp directory of my previous win98 installation.
Unfortunately I can't attach them here because it weights around 60MB but if anyone wants to retrieve them you can by starting an installation of the exe on your "regular" PC and when you get the message that "This is not a TDS...etc etc" you simply go to the TEMP directory mentioned in the first step and grab the folders and setup files from it ;)
e) Voilà! :-+
2) I've installed 512MB and 256MB DIMMS on the mainboard slots but they're topped at 128MB only each. I think this is a BIOS thing: I'll try to find a newer one (are there?) my current version is: 4B4LZ0XA.86A.0007.P04
3) With both slots of RAM occupied with 128MB and a 4200RPM Hitach Travelstar I get a boot time of 2mins 10 secs aprox: not great but not unbearable either.
4) I can't seem to see a difference by installing more than 128MB on the PPC board... does anyone do?
-
Regarding bullet 2, I found this later BIOS version:
* 4B4LZ0XA.86A.0012.P05.9911041309
* CPU BIOS Updates: MU665(03)
* Intel UNDI, PXE-2.0 (build 074)
P05-0012:
* Note: This bios is not compatible with the boot block of P04-0007 or earlier BIOSes.
* Fixed issue where system would delay before booting Windows NT when using a SCSI drive and not having IDE-HDD before the SCSI Adapter in the boot order.
* Fixed PMM allocate to consider unallocated memory holes for allocation of new memory.
* Fixed serial port device node static configuration changes.
* Added DMI memory structures.
* Removed Serial Port B setup questions and PnP device node.
* Fixed Fault Tolerant update of Vital Product Data (VPD)
* Errata: Recovery via LS-120 not currently supported.
Although the 3rd bullet could be the answer to removing the limit of 128MB I'm not sure if it's compatible (specially because of the "Note" part) does anyone know?
-
You must use double-sided 256MB DIMMs to get to 512MB
-
I just had a look at a few images I have. There is no \vxboot folder.
-
You must use double-sided 256MB DIMMs to get to 512MB
Mmmm, I'm not sure I follow you, I put one DIMM of 512MB and got only 128MB recognised: what BIOS/MOBO you have?
-
You must use double-sided 256MB DIMMs to get to 512MB
Mmmm, I'm not sure I follow you, I put one DIMM of 512MB and got only 128MB recognised: what BIOS/MOBO you have?
512MB DIMMs will not work properly at all in the BL440ZX board.
256MB DIMMs will work if they are double sided. IOW, 16 memory chips (8 on each side of the PCB) need to be on a 256MB module for all the memory to be detected. This is a chipset limitation.
-
I see, thanks for the information! ;)
-
I see, thanks for the information! ;)
No problem. I just noticed that you were discussing BIOS versions for the MB. I would NOT recommend flashing unless the BIOS was released by Tek!!! You might end up with a door-stop.
-
I'm not finding either sites up:
https://xdevs.com/guide/tek_key/
https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/
I'd be very thankful for a copy. My email motor242@list.ru
-
I really need help installing touchpad drivers. Windows XP operating system. Thank .
-
Funny I should see this thread, purchased a TDS7254 for a cheap price, just arrived and has no HD.
Any ideas where I might be able to get an image for Win2Kpro embedded for it?
Otherwise this thing is looking OK, at least physically and from the intel side of the equation it seems to function OK.
-
Wolfy007, Install Windows XP! If you have a 440zx motherboard, there are drivers in this thread. To restore NVRAM, use a natural PC232 that connects to the Console connector. The only thing that did not work out for me was to launch the touch panel. The working version of the Telescope program is 2.5.5. The one on the Tektroniks website version 2.5.3 did not work for me.
-
No problems, will give it a go tomorrow.
-
Well so far so good, nearly all up and running (Intel 810 chipset). Just need CPU update and get the ethernet working, and waiting on TCA adapters for final testing.
[attach=1]
-
Well tore it down to do a closer inspection, clean it a bit (fairly clean already), check caps etc, then I saw the two chips pictured on the acquisition board.
Last date code appears to be mid2002 for this scope, fans run smoothly, caps are looking in good shape and power on diagnostics pass. Voltages look OK, but on extended diagnostic I get a couple errors as shown below.
Appear to be part of triggering on the acquisition board. Dont suppose anyone has a dodgy acquisition board with these two chips still in good shape that they wont mind donating to this project? Or if you know a reliable supplier with stock. Chip required is the Tektronix 156827800 (x2).
Regards
Nik
-
Well tore it down to do a closer inspection, clean it a bit (fairly clean already), check caps etc, then I saw the two chips pictured on the acquisition board.
Last date code appears to be mid2002 for this scope, fans run smoothly, caps are looking in good shape and power on diagnostics pass. Voltages look OK, but on extended diagnostic I get a couple errors as shown below.
Appear to be part of triggering on the acquisition board. Dont suppose anyone has a dodgy acquisition board with these two chips still in good shape that they wont mind donating to this project? Or if you know a reliable supplier with stock. Chip required is the Tektronix 156827800 (x2).
Regards
Nik
Those are the same chips that are on the TDS694C.
https://www.eevblog.com/forum/repair/looking-for-someone-who-can-replaceswap-tek-tds694c-trigger-chips-for-$/ (https://www.eevblog.com/forum/repair/looking-for-someone-who-can-replaceswap-tek-tds694c-trigger-chips-for-$/)
-
Thanks Jay, Ill keep my eyes open for one of those as a spares unit also.
Regards
Nik
-
Hello everyone,
Would you help me to Close TDS7254B SPC fail issue or give me some suggestions? However thanks for your help in advance.
The TDS7254B can pass all Diagnostic as attach picture and only fail in SPC calibration,however I check the PowerPC board's debug info via few wires to connect PowerPC debug serial port,however the error info as below when run the SPC calibration instruction,
################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x3814820 (aAcqDpoExecutor): 20OCT19 15:38:45 U
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.80 minutes
However I have restore the WINXP system with TEK TDS7KB RestoreCD and reinstall the Tekscope software,but the issue same as before,and "M866CompCalibrator 3c Failed" "M866CompCalibrator 4c failed" the info is very confusion,what is M866? It's Chip IC or software instruction? What is 3c and 4c? it's mean the 3rd channel and 4rd Channel? |O
and Total PowerPC bootinfo as below,
romPost: I am alive .
uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
romPost: L2 cache turned on.
romPost: MPC107 Walking-one passed.
romPost: MPC107 configuration passed.
romPost: Intel21555 PCITOPCI bridge 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: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
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 - IBM 750CXe
Version: 5.3.1
BSP version: 2.0.1.10
Creation date: Sep 30 2003, 07:53:07
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching networPC1 dio device driver installed
k interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773468
Starting at 0x200000...
Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6034 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 - IBM 750CXe. Processor #0.
Memory Size: 0x2000000. BSP version 2.0.1.10.
WDB: Ready.
done
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topscript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1692d40: value = 23670112 = 0x1692d60 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691720: value = 23669856 = 0x1692c60
ld < TekScope.o
value = 23657440 = 0x168fbe0
ld < TekScopeSM.o
value = 23660544 = 0x1690800
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
loggerInit
Serial No: B020790
value = 21822832 = 0x14cfd70
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 23661184 = 0x1690a80
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 16129500 = 0xf61ddc = PaiBaseRegisterTable + 0x804
configureACL
SUCCESS
value = 0 = 0x0
verifyAcqBoardID
value = 0 = 0x0
tcsLoadTableToNVRAM "pc:c:/vxBoot/setup.tcs"
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
logTask: 1 log messages lost.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0
excHookAdd(stopStressForException)
value = 15840048 = 0xf1b330 = stopStressForException
dsyInit
value = 0 = 0x0
dsyWPApplyNextRegs
value = 16110116 = 0xf5d224 = DsyRegisterTable + 0xbd0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
value = 21793056 = 0x14c8920
TmgrInit("/db")
value = 0 = 0x0
PhxProxyInit
value = 20333344 = 0x1364320
rtlInit
value =0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x1c000000
value = 0 = 0x0
hwAccount_init
sysEnetAddrGet: 4d:54:5c:c8:c0:64
Scope Model: TDS7254B
value = 0 = 0x0
GpibInit
value = 502610496 = 0x1df53a40
wfmMemInit(1)
value = 62205664 = 0x3b52ee0
vertInstall
value = 62198148 = 0x3b51184
calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 358 bytes of service cal #1 data from NV[3:0] into 0x3b51000
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): Optical hardware is not present.
calConStatus = 0x127d1dc: value = 0 = 0x0
vertPostCalRestoreInstall
value = 0 = 0x0
MathMeasCreateTheMathandMeasurementLibraries
value = 62025376 = 0x3b26ea0
initAcqMapper
0x16987e0 (tShell): initAcqMapper: Enter
value = 0 = 0x0
trigMapInit
value = 0 = 0x0
dsyMapInit
value = 0 = 0x0
mathMapperInit
value = 0 = 0x0
utilMapInit
value = 62019520 = 0x3b257c0
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 19321872 = 0x126d410 = AcqMapperRtlDataList
MathMeasMapHookup
value = 23692552 = 0x1698508
dsyMapHookup
value = 23692656 = 0x1698570
utilMapHookup
value = 23692688 = 0x1698590
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 23692648 = 0x1698568
fastFrameMapHookup
value = 23692672 = 0x1698580
trigMapHookup
value = 23692680 = 0x1698588
vertMapHookup
value = 23692672 = 0x1698580
spcMapHookup
value = 23692672 = 0x1698580
autosetMapHookup
value = 23692712 = 0x16985a8
timeSyncMapHookup
value = 23692704 = 0x16985a0
auxTrigMapHookup
value = 23692688 = 0x1698590
dpoMapHookup
value = 23692680 = 0x1698588
TmgrStartup
value = 61194384 = 0x3a5c090
PhxProxyStartup
value = 61143840 = 0x3a4fb20
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 61017376 = 0x3a30d20
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 60967680 = 0x3a24b00
enablePowerupDiags = 0
enablePowerupDiags = 0x123dbdc: value = 0 = 0x0
runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
<< POWERUP DIAGS FINISHED >>
execution time 0 sec>>
Test "351" - Acquisition-->HFStep-->PhaseCal started
Test execution time 6.3768 sec
value = 0 = 0x0
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
paiPrintVersionNumber
Pai version: 4.52
value = 18 = 0x12
################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x3814820 (aAcqDpoExecutor): 20OCT19 15:38:45 U
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x1641830 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x1641830 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.80 minutes
DIAGNOSTIC EXECUTION begin
Test "111" - Processor-->Memory-->DRAMWalk1 started
Test execution time 6.875e-06 sec
Test "112" - Processor-->Memory-->DRAMCell started
Test execution time 0.047812 sec
Test "113" - Processor-->Memory-->DRAMMarch started
Test execution time 0.014548 sec
Test "121" - Processor-->PCI Bus-->Scan Test started
Test execution time 1.7788e-05 sec
Test "211" - RegAccess-->DACs-->Daculator started
Test execution time 0.00036913 sec
Test "221" - RegAccess-->Direct R/W-->DEMUX started
Test execution time 0.0023205 sec
Test "222" - RegAccess-->Direct R/W-->Dsy started
Test execution time 0.00032442 sec
Test "223" - RegAccess-->Direct R/W-->SBTL started
Test execution time 0.00013178 sec
Test "224" - RegAccess-->Direct R/W-->SGTL started
Test execution time 0.00029986 sec
Test "231" - RegAccess-->IIC-->Pogo_U1 started
Test execution time 0.00040611 sec
Test "241" - RegAccess-->PLL-->Serial started
Test execution time 9.2548e-05 sec
Test "251" - RegAccess-->Serial-->AtoD started
Test execution time 0.00019014 sec
Test "252" - RegAccess-->Serial-->U1093 started
Test execution time 2.7115e-05 sec
Test "253" - RegAccess-->Serial-->U1251 started
Test execution time 0.00019577 sec
Test "254" - RegAccess-->Serial-->U1500 started
Test execution time 0.00027058 sec
Test "311" - Acquisition-->Memory-->MemData started
Test execution time 5.0736 sec
Test "312" - Acquisition-->Memory-->MemAddr started
Test execution time 4.9452 sec
Test "313" - Acquisition-->Memory-->DataFormat started
Test execution time 2.4118 sec
Test "321" - Acquisition-->Acq Modes-->SubSample started
Test execution time 5.3287 sec
Test "322" - Acquisition-->Acq Modes-->PeakDetect started
Test execution time 39.147 sec
Test "323" - Acquisition-->Acq Modes-->HiRes started
Test execution time 5.3411 sec
Test "331" - Acquisition-->Vertical-->50OhmOvld started
Test execution time 0.083668 sec
Test "332" - Acquisition-->Vertical-->ADC Connects started
Test execution time 7.0864 sec
Test "341" - Acquisition-->Interrupt-->Bit Tests started
Test execution time 4.9321 sec
Test "351" - Acquisition-->HFStep-->PhaseCal started
Test execution time 5.8304 sec
Test "361" - Acquisition-->PLL-->Clock Freq started
Test execution time 0.44611 sec
Test "371" - Acquisition-->MemSpeed-->DemuxA started
Test execution time 3.9665 sec
Test "372" - Acquisition-->MemSpeed-->DemuxB started
Test execution time 3.9569 sec
Test "373" - Acquisition-->MemSpeed-->DemuxC started
Test execution time 3.9557 sec
Test "374" - Acquisition-->MemSpeed-->DemuxD started
Test execution time 3.9562 sec
Test "375" - Acquisition-->MemSpeed-->DemuxE started
Test execution time 3.9563 sec
Test "376" - Acquisition-->MemSpeed-->DemuxF started
Test execution time 3.9579 sec
Test "377" - Acquisition-->MemSpeed-->DemuxG started
Test execution time 3.9557 sec
Test "378" - Acquisition-->MemSpeed-->DemuxH started
Test execution time 3.9561 sec
Test "411" - Trigger-->Inputs-->Line started
Test execution time 0.072346 sec
Test "412" - Trigger-->Inputs-->Ch1 started
Test execution time 0.36608 sec
Test "413" - Trigger-->Inputs-->Ch2 started
Test execution time 0.35029 sec
Test "414" - Trigger-->Inputs-->Ch3 started
Test execution time 0.35027 sec
Test "415" - Trigger-->Inputs-->Ch4 started
Test execution time 0.35036 sec
Test "421" - Trigger-->Internals-->TimerA1 started
Test execution time 0.10003 sec
Test "422" - Trigger-->Internals-->TimerA2 started
Test execution time 0.099752 sec
Test "423" - Trigger-->Internals-->Btrig started
Test execution time 0.10234 sec
Test "424" - Trigger-->Internals-->BtrigEvents started
Test execution time 0.11884 sec
Test "425" - Trigger-->Internals-->TimeInterp started
Test execution time 9.3269e-06 sec
Test "426" - Trigger-->Internals-->Holdoff started
Test execution time 0.033352 sec
Test "511" - Misc-->Cal Integrity-->Factory Cal started
Test execution time 6.0577e-06 sec
Test "512" - Misc-->Cal Integrity-->SPC (run SPC) started
Test execution time 1.8269e-06 sec
Test "521" - Misc-->GPIB-->Interface started
Test execution time 0.0005699 sec
DIAGNOSTIC EXECUTION finished in 115.5 sec
(http://)
-
I am trying to repair a 7054 scope that's missing quite a few parts. So If someone has any spares, please let me know. Here's what I am missing:
- Front keypad panel;
- Front plastic bezel;
- Top and bottom aluminum covers;
- NLX riser board;
- Front and Rear power distribution boards;
- cPCI connector board;
- cooling fans (6pcs on a chassis);
- front connector cover (black strip below the screen and keypad).
- DVD with a chassis
- floppy with a chassis
- hard drive caddy.
If somebody has this stuff laying around please let me know.
-
I came along a TDS7154B and the test shows an error for DemuxG and DemuxH (377 and 378). Everything else seems to work. The memory on the acquisition board are Cypress CY7C1361B-133AC i think. But there are 64 of them and obviously it could be something else. So any information is welcome ! Is there any more information on the serial when one is running this test ? Thanks !
You are lucky because this problem might be easy to fix. You need to connect the RS232 adapter to to the serial port (there are instructions earlier on this thread) and run diagnostics again. The diagnostics will literally print the U*** labels of the memory on the PCB. Make a note of it, take out the ACQ PCB, locate the memory and replace it.
I just repaired my CSA7404 this way a couple of days ago.
-
Hello
I bought TDS7104 without HDD.
Just installed usual Win2000 OS in 32GB ssd, installed drivers for PPC board and USB Front panel and downloaded TekScope 2.5.5 from tek site.
Tek scope starts up.
However, there are buttons that are not glowing.
Also, such a screen appears and does not work properly.
Do you know any solution?
You definitely want to install the VXWORKS files on your C: drive. For this you'll need to install the Firmware update, download from Tek website: https://www.tek.com/oscilloscope/tds7054-software/tds7104-and-7054-firmware-upgrade (https://www.tek.com/oscilloscope/tds7054-software/tds7104-and-7054-firmware-upgrade)
-
@stan_cool, your mailbox is apparently full.
-
Just wondering.. Does anyone know where the actual cal data is stored? On the ACQ board I presume? What's the tech? EEPROM? Or another nasty NVRAM?
-
Hello Ice-Tea
I think the CAL data is divided into two parts, the factory service CAL data part is stored in NVRAM of PPC board, and the user SPC CAL data is stored in the hard disk C:\vxBoot\calCons\
however please refer below info from debug port of PPC board,What do you think about the following SPC fail issue? |O
calConStatus = cc_init(2)
0x16987e0 (tShell): Reading 358 bytes of service cal #1 data from NV[3:0] into 0x3b4f000
0x16987e0 (tShell): nvMem_read succeeded
0x16987e0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/11
0x16987e0 (tShellcalConStatus): cc_restoreBank: can't open file = C:/vxBoot/calCons/0x13
0x16987e0127d1dc (tShell): : value = cc_restoreBank: can't open file 26624C:/vxBoot/calCons/ = 0x14
0x16987e06800 (tShell): Optical hardware is not present.
################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> 0x380aa40 (aAcqDpoExecutor): 16OCT19 02:27:03 U
0x391a030 (CalWatch): Temperature transition into SPC-supporting range.
0x1630bb0 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x1630bb0 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x1630bb0 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x1630bb0 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.93 minutes
0x3621830 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x3621830 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x3621830 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x3621830 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.80 minutes
0x35f0550 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x35f0550 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x35f0550 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x35f0550 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.75 minutes
DIAGNOSTIC EXECUTION begin
Test "111" - Processor-->Memory-->DRAMWalk1 started
Test execution time 7.0673e-06 sec
Test "112" - Processor-->Memory-->DRAMCell started
Test execution time 0.047657 sec
Test "113" - Processor-->Memory-->DRAMMarch started
Test execution time 0.014168 sec
Test "121" - Processor-->PCI Bus-->Scan Test started
Test execution time 1.7981e-05 sec
Test "211" - RegAccess-->DACs-->Daculator started
Test execution time 0.00036928 sec
Test "221" - RegAccess-->Direct R/W-->DEMUX started
Test execution time 0.0023184 sec
Test "222" - RegAccess-->Direct R/W-->Dsy started
Test execution time 0.00032087 sec
Test "223" - RegAccess-->Direct R/W-->SBTL started
Test execution time 0.00013231 sec
Test "224" - RegAccess-->Direct R/W-->SGTL started
Test execution time 0.00030058 sec
Test "231" - RegAccess-->IIC-->Pogo_U1 started
Test execution time 0.00036548 sec
Test "241" - RegAccess-->PLL-->Serial started
Test execution time 9.2548e-05 sec
Test "251" - RegAccess-->Serial-->AtoD started
Test execution time 0.00019005 sec
Test "252" - RegAccess-->Serial-->U1093 started
Test execution time 2.7163e-05 sec
Test "253" - RegAccess-->Serial-->U1251 started
Test execution time 0.00019572 sec
Test "254" - RegAccess-->Serial-->U1500 started
Test execution time 0.00027029 sec
Test "311" - Acquisition-->Memory-->MemData started
Test execution time 5.0754 sec
Test "312" - Acquisition-->Memory-->MemAddr started
Test execution time 4.9457 sec
Test "313" - Acquisition-->Memory-->DataFormat started
Test execution time 2.4118 sec
Test "321" - Acquisition-->Acq Modes-->SubSample started
Test execution time 5.3284 sec
Test "322" - Acquisition-->Acq Modes-->PeakDetect started
Test execution time 39.131 sec
Test "323" - Acquisition-->Acq Modes-->HiRes started
Test execution time 5.3404 sec
Test "331" - Acquisition-->Vertical-->50OhmOvld started
Test execution time 0.083696 sec
Test "332" - Acquisition-->Vertical-->ADC Connects started
Test execution time 7.0857 sec
Test "341" - Acquisition-->Interrupt-->Bit Tests started
Test execution time 4.9328 sec
Test "351" - Acquisition-->HFStep-->PhaseCal started
Test execution time 5.8304 sec
Test "361" - Acquisition-->PLL-->Clock Freq started
Test execution time 0.4462 sec
Test "371" - Acquisition-->MemSpeed-->DemuxA started
Test execution time 3.9646 sec
Test "372" - Acquisition-->MemSpeed-->DemuxB started
Test execution time 3.9564 sec
Test "373" - Acquisition-->MemSpeed-->DemuxC started
Test execution time 3.9567 sec
Test "374" - Acquisition-->MemSpeed-->DemuxD started
Test execution time 3.9563 sec
Test "375" - Acquisition-->MemSpeed-->DemuxE started
Test execution time 3.9563 sec
Test "376" - Acquisition-->MemSpeed-->DemuxF started
Test execution time 3.9563 sec
Test "377" - Acquisition-->MemSpeed-->DemuxG started
Test execution time 3.9564 sec
Test "378" - Acquisition-->MemSpeed-->DemuxH started
Test execution time 3.9562 sec
Test "411" - Trigger-->Inputs-->Line started
Test execution time 0.074533 sec
Test "412" - Trigger-->Inputs-->Ch1 started
Test execution time 0.36537 sec
Test "413" - Trigger-->Inputs-->Ch2 started
Test execution time 0.35027 sec
Test "414" - Trigger-->Inputs-->Ch3 started
Test execution time 0.35029 sec
Test "415" - Trigger-->Inputs-->Ch4 started
Test execution time 0.3503 sec
Test "421" - Trigger-->Internals-->TimerA1 started
Test execution time 0.10009 sec
Test "422" - Trigger-->Internals-->TimerA2 started
Test execution time 0.10127 sec
Test "423" - Trigger-->Internals-->Btrig started
Test execution time 0.11828 sec
Test "424" - Trigger-->Internals-->BtrigEvents started
Test execution time 0.11882 sec
Test "425" - Trigger-->Internals-->TimeInterp started
Test execution time 9.2788e-06 sec
Test "426" - Trigger-->Internals-->Holdoff started
Test execution time 0.033313 sec
Test "511" - Misc-->Cal Integrity-->Factory Cal started
Test execution time 6.2981e-06 sec
Test "512" - Misc-->Cal Integrity-->SPC (run SPC) started
Test execution time 1.9231e-06 sec
Test "521" - Misc-->GPIB-->Interface started
Test execution time 0.00057072 sec
DIAGNOSTIC EXECUTION finished in 115.5 sec
0x365b550 (SPC task): cc_loadV: CC_TRIGdcGain3c was 0; clipped
0x365b550 (SPC task): ** M866CompCalibrator 3c failed -- ...wrote cal constant CC_TRIGdcGain3c to 0.000000, failed
. **
0x365b550 (SPC task): cc_loadV: CC_TRIGdcGain4c was 0; clipped
0x365b550 (SPC task): ** M866CompCalibrator 4c failed -- ...wrote cal constant CC_TRIGdcGain4c to 0.000000, failed
. **
total cal time 3.95 minutes
-
Hello everybody and thanks for the great pieces of information you're sharing!!
I'm working on a CSA8000B which boots but then gets stuck on flash screen.
PPC diagnosis shows "P" steadily, so no infinite boot loop as has been described for many units.
Still it is stuck. Any ideas?
I'd like to connect RS232 to see, whether there is any insight from the boot log.
Although I read through pretty much everything, I'm not quite sure how to connect to the J790 header on the ppc board.
I understand, I need to connect RXD, TXD and GND- correct?
Which pins are this on the header? Any photo maybe?
What voltage levels are there? Is it 3.3 or 5V?
Appreciate any info!!
-
Oh? Wasn't expecting call to be on the PPC board. Think I need to look into that a bit further then..
AS for your error: have you double checked the directory actually exists? That it is not protected?
Perpf:
(https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/?action=dlattach;attach=109424;image)
you need TX1 and RX1
-
Hi guys!
I have my repaired TDS7254B booting successfully (which is much thanks to the fantastic content of this thread) but it requires an acquisition board repair - the analog mux for ADCs has a connection problem. About a year ago I removed the heatsink and reflowed the BGA back on the acquisition board, and the problem was fixed!
Long story short, I was tinkering this weekend and noticed the same problem re-appearing. I am going to attempt to remove and re-ball the BGA with leaded solder as it seems as if the exact same failure happened again after a year of use - likely thermal cycling related. Anyway, this is a very risky operation to perform as Tek won't even sell or support one of these acq boards. I looked on ebay at replacement acquisition boards should this open heart surgery not go well. Below is a list of purchasable options, now the problem is figuring out which scopes each board is compatible with. I spent a few hours scouring all the service manuals for TDS7K, TDS7KB, CSAx compiling references but am still without a clue what many of these parts belong to :scared:
672-1592-02
672-1686-61 //TDS7154B
672-1694-55 //TDS7154
665-1686-10 //TDS7154B
672-5276-00
672-5276-54
672-5276-01
672-5276-52
671-5337-00
I've received several listings of Acq board PNs/models I'll list here for other people looking for correlations or substitute boards:
672-1595-02 //TDS7404
672-1694-55 //TDS7404
672-1686-01 //CSA7404
665-1686-02 //TDS7404B
679-6477-01 //TDS7404B
672-1686-01 //TDS7404B
672-1718-11 //TDS7254B
665-1718-11 //TDS7254B
679-5673-11 //TDS7254B
679-5476-11 //CSA7404B
655-1732-11 //CSA7404B
It seems there are lots of the 672-5276 parts on the market, I would assume this belongs to something popular. Alltest (the ebay vendor) doesn't have the donor instrument information [other than that these are for TDS7xxxxy], so I am hoping to figure this out online. I know how to perform a board ID override and have SN/KEY info for most of the TDS7k, TDS7kB, CSA models. It would be nice to upgrade to 4GHz BW, but I'd be happy with just having my 7254B back in service.
Can anyone help? The primary unknowns are 672-5276, 671-5337, 672-1592. What does the suffix mean (appears to be a version or similar)? Any ideas of other service manuals to examine?
Then there is the question of whether I will even be able to swap a new acquisition board in, even if I found the exact replacement part. Will the scope be able to regenerate its own CAL info or will I have a useless piece of hardware anyway?
Thanks!
-
Hi Ice-Tea
yes you can double check the nvram in PPC board,however i can find the below file in NVRAM,I think TDS7000.CVN and TDS7000.CVO is factory service CAL data
EVENTLOG.DAT
TDS7000.CVO
APPSTR.BIN
TDS7000.CVN
TDS0.DBS
For mine SPC error: I double check the user SPC CAL data is stored in the hard disk C:\vxBoot\calCons\ and more details as attach picture
and The last time SPC passed was at 2019/10/15 3:37，so we can find the file modify history in the picture with file 9 10 11 13 14
if SPC Fail will modify the file 12 16 only and I have confirmed that all directories have full access rights.
This is a very headache SPC issue |O I ready to check the CompCalibrator MOD of the ACQ board,
I am very grateful if you can help provide some advice or direction
-
As it's user call only: backup the files, delete the contents of the entire directory and run SPC again?
-
Hi Ice-Tea
I tried to delete all the files in the CalCons directory. After executing spc again, I will only get 12 16 files. Other files can't be generated, and spc still fails.
Hello bipolarjunction
My oscilloscope is also TDS7254B, and I am fixing the problem of SPC failure, so I can just tell you that my TDS7254B acquisition board model is as follows, hope can help you.
672-1718-11
And I have another TDS7704B acquisition board information as follows
672-1686-01
and As My TDS7254B's ACQ board has two resistors that have fallen off.Would you help me measure the resistance value of the two resistors (R1027 and R1026) on your TDS7254B ACQ board?
and the position as attach picture,I am trying to fill these two resistors.however thanks for your help in advance.
-
Hello Snoopy,
I'd be happy to help! I measure 25 ohms for both R1027 and R1076, which appear to be the resistors in question in your image. My part number is identical.
By taking a look at this board, there is another code that appears more consistent with the part numbers supplied by Alltest - with 5xxx figures. I may ask them if they can take another look for the other PN stickers on the boards they have.
I am surprised to learn that your 7704B has the 672-1686-01 in it - it appears that my reading of the parts list in the service manual was backwards! I thought the 1686 corresponded to 1.5G, rather than 7. This is quite good news if I can run the 7GHz acq board, but unfortunately I lack an SN/key for the 7704B. It is a risky purchase (~$1k). Perhaps with the board ID override to 7404B I could proceed with my SN/key info for 7404B using the 7704B acq. :-/O
NOTE: All images posted are of 672-1718-11 TDS7254B acquisition board.
-Matt
-
Hello bipolarjunction
Thank you for your quick reply and great help. and share more details partnumber in ACQ board as below,
However, I need to remind you that the Relays of the TDS7704B have a completely different structure from the TDS7254B.
For details, please see the physical picture of the TDS7704B acquisition board.The Relays of the TDS7704B are external,
but the Relays of the TDS7254B are Onboard,Good Lucky for you :D
TDS7254B
672-1718-11
665-1718-11
679-5673-11
TDS7704B
665-1686-02
679-6477-01
672-1686-01
-
snoopy,
I'm happy to help, thank you also for the information! Please keep posting the cal file process for your issue!
Generally, success to report here. Today I took the board to work and properly reflowed the MUX IC. I think the failure was probably due to the fact that when I did the job the first time, I was so afraid to overheat the board I probably didn't adequately heat the job. Today I used an IR preheater, took my time with the hot air. Booted, self-test, SPC, and ran all day at full sample rate.
I'm considering attempting a retrofit of the 7704B acq board. I eagerly await the path to rectifying cal files as snoopy trudges the path.
Thanks!
-
I'm not finding either sites up:
https://xdevs.com/guide/tek_key/
https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/
I'd be very thankful for a copy. My email gjchome@163.com
-
Hi Tin,
Did you ever write this article or make any progress? I'd love to mess around and add options to my TDS5054...
My email:gjchome@163.com.
-
I'm considering attempting a retrofit of the 7704B acq board.
Thanks!
I would expect the 7704b board will work in your 7254b scope, however you will most likely need to update your firmware, those are the vxworks files and Atmel images stored in your c:/vxboot hidden folder. This is not a problem for now, since you can simply download 7704b firmware from Tek website.
However, I don't think Alltest really guarantees that the board is working or they have a way to test it. I've heard of a person, who bought two 6604 ACQ boards from them, and was able to successfully convert a TDS7054 into TDS6604! They only had to replace the chassis because the standoffs and front port openings were incompatible. However both boards were faulty, the best of the two works fine, but none of the triggers work.
-
bipolarjunction
Maybe I found out how to re-do SPC for a new ACQ board. There is a need to execute this command（calConStatus = cc_init(1)）, which will completely erase the SPC calibration data of your previous ACQ board, and then rewrite the original factory CAL data when re-executing After SPC, all user CAL data in the directory c:\vxBoot\CalCons will be regenerated, but it is recommended that you back up all the files under c:\vxBoot\CalCons before running this command.
-> calConStatus = cc_init(2)
0x167bce0 (tShell): Reading 358 bytes of service cal #1 data from NV[3:0] into 0x164d7e0
0x167bce0 (tShell): nvMem_read succeeded
0x167bce0 (tShell): Optical hardware is not present.
calConStatus = 0x127d1dc: value = 0 = 0x0
-> calConStatus = cc_init(1)
0x167bce0 (tShell): Erasing sector 3 of the M25P20 FLASH
0x167bce0 (tShell): Storing 358 bytes of service cal #1 data from 0x1ffe500 into NV[3:0]
0x167bce0 (tShell): NV service cal data verified.
0x167bce0 (tShell): Optical hardware is not present.
calConStatus = 0x127d1dc: value = 131071 = 0x1ffff
I have done this on my TDS7254B, but unfortunately the problem of SPC fail still exists. This also proves that my problem is not caused by SPC software or data storage, but due to hardware failure, so I am focusing now. U1021 MAX9601（Ultra-High-Speed Comparators）, I measured all the power-on voltage data of the U1021 high-speed comparator and the ground resistance of the power-off as attach picture. The very obvious problem is that the U1021 Pin9 & Pin10 does not have any voltage input, and in the case of turning off the power. PIN12 is directly shorted to ground (measured impedance is 0 ohms). Another very doubtful situation is that the U1021 chip has a relatively large amount of heat and the surface is a bit hot. I am considering replacing this chip, but I need to be clearer before replacing it. Whether this chip is really damaged, Would you please help to measure the voltage data of Pin9 Pin10 Pin11 Pin12 of your ACQ board U1021 and the ground resistance data of the power-off, which will help me to judge this more clearly, whether the chip is good or not,Thanks
B&R
Snoopy
-
Sure, I can make the measurements on Monday
-
Hi again & thanks for reply!
Looks like I'll replace the NVRAMS. If they are still working, is there a way to read and store the contents in order to rewrite them into the new ones after replacement?
thanks for any input!
-
Hello everybody!
I've connected to the J790 console port through a USB-SER dongle. It looks like there is a connection up, however the readout is all garbled.
Hitting the "space"-key with the CSA8000 showing "P" on the PPC-board causes some text to be received- however it's unreadable.
any ideas? I'd really appreciate help!
thanks!!
-
Please check the console port setting as 9600 8N1
-
Hi & thanks for the quick reply!
I also suspected the baudrate, but it wasn't!
I got that fixed myself: Although maybe a bit stupid I'll post it here- just in case someone else runs into the same issue.
The USB-Serial adapter I got didn't work as expected. I got another one (with a DB9-connector) which worked. I suspect the first one merely converted to TTL-Signals, ending up with an inverted signal (compared to RS232). This would explain the garbled output. Now it works just fine on 9600,8n1
So now I'm getting closer to my problem: The unit hangs on the splash screen, PPC-diag reports: "P".
As you can see in attached console output, pretty much at the end it mentions *** Starting SIMULATED Acquisitions *** and a bit later it hangs on "connectionTask: handshaking with peer...".
Does anyone have an idea of what's going on?
Any help appreciated!
cheers!
-
Hello & thanks for sharing your work!
Do you happen to know what could be the reason (or at least what component might be involved) when PPC-Diag doesn't switch from "P" to blinking "-" (on my CSA8000B)?
thanks & all the best!
-
Hi All,
I'm trying to repair a TDS7404B that starts into Windows 2000 normally but hangs on the Tek application splash screen. The seven -segment debug shows very erratic behavior (I will attach a link to a video), jumping from '5' to '9' to 'h' and other interesting things, before ultimately stopping on '7'. I replaced the NVRAM module and tried three different new ones but the problem persists. I checked all the voltages as per the service manual and they are in spec, even DC/DC module. Has anyone encountered this before? What might cause the startup debug sequence to behave so erratically?
https://youtu.be/f7JcgQHpBps video of startup
romPost: I am alive .
uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
romPost: L2 cachå
romPost: I am alive .
uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
romPost: L2 cache turned on.
romPost: MPC107 Walking-one passed.
romPost: MPC107 configuration passed.
romPost: Intel21555 PCITOPCI bridge 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: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
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 - IBM 750CXe
Version: 5.3.1
BSP version: 2.0.1.10
Creation date: Sep 30 2003, 07:53:07
Press any key to stop auto-boot...
1
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching networPC1 dio device driver installed
k interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...
-
As I watched the video more closely I realized I was looking at the 7-segment display upside down. |O
It is actually the other way around on my 7104. But when I look at it almost frame by frame I see that it repeats the opening sequence of .8, 1, 2, 3, 4, then goes back to .8 then back through the sequence to 9 and seems to skip A and ultimately hangs on L. It's hard to see because the sequence goes through some of the steps quite fast.
Also, I've checked to see that the vxboot files are where the PPC board is looking for them and they check out.
Any advice would be much appreciated.
-
Check that you have proper files on c:\vxBoot hidden folder. Properly loaded and running PPC board should display dash on LED display, when OS is booted.
-
All the appropriate files are in the c:/vxboot locations the boot parameters direct to, they are just not loading to the PPC. Has anyone run into this before? I even changed out the RAM stick on the PPC with a NOS stick and that did not help either. Could this be a failure on the acquisition board or the connector between the PPC and AQB?
Thanks,
-
Hi, add me to the list of people late to the party. If anyone has this info can they send it to me, either via the forum or to nsummy@hotmail.com Thanks!!!!!!!!!! :-+ :-BROKE
Hi, I'm little late, but does anyone have this option stuff saved?
Ramppa
Quote from: snoopy on 2017-12-24, 15:50:07 (https://www.eevblog.com/forum/index.php?topic=20744.msg1382816#msg1382816)>Quote from: PrecisionAnalytic on 2017-12-24, 09:06:03 (https://www.eevblog.com/forum/index.php?topic=20744.msg1382634#msg1382634)>Quote from: dretay on 2017-12-05, 07:19:04 (https://www.eevblog.com/forum/index.php?topic=20744.msg1366917#msg1366917)Hey, no idea why the link doesn't work. Happy to send a copy to you if you want to PM me.
I'm not finding either sites up:
https://xdevs.com/guide/tek_key/ (https://xdevs.com/guide/tek_key/)
https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/ (https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/)
I'd be very thankful for a copy.
Background if you are interested:
I received a few days back a TDS8000B that was stated on eBay as having Power Supply issues where they noted:
"Originally it was working but came back to us with a bad power supply. About once out of 20 times it will power on and light up. Sometimes it turns off by itself while booting. Most times it won't turn on at all then will make faint clicking ticking noise in the right rear of the unit. Screen has some scratching."
I powered on the unit and first time not thinking about having a keyboard plugged in to login and perform more testing as my brain was set to modern day touch screens with keyboards that appear on-screen as factory default. Powered on no issues, though is slow Windows 2000 Pro for sure.
After plugging in a USB keyboard with a USB to PS2 keyboard adapter, I pressed the power button on the front panel and was having no success with being able to use the keyboard to log in. I am guessing something to do with USB keyboard drivers is the reason.
Now, after holding the front panel power button for over 7 seconds, the unit powered off. When I tried to power back on, I heard a mechanical clock ticking sound with nothing happening. When I switched the power switch on the back of the unit the ticking sound slowly went away and all subsequent attempts to power on have failed with nothing happening.
Before I open the case up... any ideas to consider as I am making a giant leap into working on this system as I am still not yet graduated from a TDS-520 repair/restore... though am moving forward on that and learning a lot.
Just reading this page topic summary has bridged the programming firmware and electronics components like NVRAM and microcontroller gaps I've had.
Sounds like caps in the power supply or possibly on the motherboard.
Also if you can't get into the bios setup you need to first check your cmos battery on the NLB motherboard and replace it if it is dead. Likewise for the power PC board. If your scope is anything like the experience I had with a TDS7054 then you probably still won't be able to get into the bios setup so you need to boot up in dos on a floppy and run a program like killCMOS to reset your CMOS memory and then you will, beable to get into the bios setup.
http://www.majorgeeks.com/files/details/killcmos.html (http://www.majorgeeks.com/files/details/killcmos.html)
You can create a bootup dos disk from another computer with a floppy using the setup from http://www.allbootdisks.com/download/dos.html (http://www.allbootdisks.com/download/dos.html)
cheers
-
All the appropriate files are in the c:/vxboot locations the boot parameters direct to, they are just not loading to the PPC. Has anyone run into this before? I even changed out the RAM stick on the PPC with a NOS stick and that did not help either. Could this be a failure on the acquisition board or the connector between the PPC and AQB?
Thanks,
Go into the windows device manager. Is there anything in there that has a question mark or exclamation mark? (I believe its normal to have 2 exclamation marks for the Texas Instruments cardbus countrollers)
-
Since I have seen a few people ask here (me included), if anyone is looking for the code to unlock options for the 7000 series, I found the source code here: https://0xacab.org/mitic/tek-ssc/tree/master
-
It looks like I've cleared up the hanging application issue with the TDS7404. I was reading through the install notes for the firmware update and came across this:
- Existing Windows 2000 oscilloscopes upgrading to version 2.5.3
can manually fix a problem with saving files (setups, images,
references, etc.) to remote filesystem devices through an
upgrade of the DIO service. Note this problem does not exist on
Windows 98 or factory-shipped 2.5.3 oscilloscopes. You will
need to obtain a copy of the dioservice.exe file from the
software updates section at www.tektronix.com (http://www.tektronix.com), or your Tektronix
representative.
How to update DIOService on Windows 2000:
1. Click Start->Settings->Control Panel->Administrative Tools->Services
2. In the right pane, right click on "DIO Service"
3. Select "Properties"
4. In the General tab page, click on "Startup type" dropdown list
5. Select "Manual"
6. Click OK
7. Reboot
8. Copy the dioservice.exe file to C:\WINNT
9. Click OK to replace the old dioservice.exe
10. Change "Startup type" to "Automatic" by following procedures 1-4
11. Reboot
I checked and found that the unit's DIO Service was set to "Manual" so when I clicked on "Start" I heard the acq relays start clicking and a few seconds later I had waveforms on the screen. I set DIO to "automatic" and now the scope's Tek application starts up normally on power up.
But since I replaced the NVRAM (probably unnecessarily) I lost the serial number info on that and for some reason the .sn file in c:/vxBoot is empty. So I have lost all the options this scope came with. I copied the .sn file from a 7104 and used a Hex editor to change the serial number to the number that matches the 7404, put that new .sn file in vxBoot, and set the flag in the boot file to "0x1000", but the scope did not take the serial number and still lists the serial number as "-" and no options in the "About this scope" window. Can someone help me create a correct .sn file with my scope's serial number?
Thanks.
-
Did anyone ever manage to get the firmware on the PPC board updated without booting into windows?
Got this:
romPost: L2 cache turned on.
romPost: MPC107 Walking-one passed.
romPost: MPC107 configuration passed.
romPost: Intel21555 PCITOPCI bridge configuration passed.
romPost: PERFORMING ROM CHECKSUM TEST...
romPost: ROM checksum failed.
Expected Value: 0x0000E120
Actuall Value: 0x0000E11F
After which it stops. I can force it to continue the boot but then it hangs a bit further. So I figured to uprade/reflash the FW but I don't see how..
-
It looks like I've cleared up the hanging application issue with the TDS7404. I was reading through the install notes for the firmware update and came across this:
- Existing Windows 2000 oscilloscopes upgrading to version 2.5.3
can manually fix a problem with saving files (setups, images,
references, etc.) to remote filesystem devices through an
upgrade of the DIO service. Note this problem does not exist on
Windows 98 or factory-shipped 2.5.3 oscilloscopes. You will
need to obtain a copy of the dioservice.exe file from the
software updates section at www.tektronix.com (http://www.tektronix.com), or your Tektronix
representative.
How to update DIOService on Windows 2000:
1. Click Start->Settings->Control Panel->Administrative Tools->Services
2. In the right pane, right click on "DIO Service"
3. Select "Properties"
4. In the General tab page, click on "Startup type" dropdown list
5. Select "Manual"
6. Click OK
7. Reboot
8. Copy the dioservice.exe file to C:\WINNT
9. Click OK to replace the old dioservice.exe
10. Change "Startup type" to "Automatic" by following procedures 1-4
11. Reboot
I checked and found that the unit's DIO Service was set to "Manual" so when I clicked on "Start" I heard the acq relays start clicking and a few seconds later I had waveforms on the screen. I set DIO to "automatic" and now the scope's Tek application starts up normally on power up.
But since I replaced the NVRAM (probably unnecessarily) I lost the serial number info on that and for some reason the .sn file in c:/vxBoot is empty. So I have lost all the options this scope came with. I copied the .sn file from a 7104 and used a Hex editor to change the serial number to the number that matches the 7404, put that new .sn file in vxBoot, and set the flag in the boot file to "0x1000", but the scope did not take the serial number and still lists the serial number as "-" and no options in the "About this scope" window. Can someone help me create a correct .sn file with my scope's serial number?
Thanks.
Use the .sn file attached and replace Bxxxxxx with whatever your SN is.
To have the right options please update the .key file xxxxx-xxxxx-xxxxx-xxxxx with the option key on the back of your scope.
Store both files in c:/vxBoot/. Then look up topScript.hw file and uncomment the line "# NvramClearDb = 1" by removing the #. Reboot once so the SN an key are stored in the NVRAM and then comment back.
This did it for me. The files are taken from my TDS7104.
-
Unfortunately I've tried that several times. I have the key file and sn file in the vxboot directory, in the right format just like files you attached (thank you for that) and I clear the nvram with the omission of the "#" and the machine still won't take the serial number. Very frustrating. I tried changing the boot flags, but that hasn't worked either. Interestingly, the machine (a 7404B) always goes back to the original boot params no matter how many times I change them. Set the boot flag to 0x1000 and the next time it reboots it's back to 0x1008.
-
Seems like this is more the place to be for my problem.
I'm completely stuck with the repair of a TDS6804B scope some less honest seller has sold me, as the acquisition board has been stripped in what seems to be an unscrupulous try-and-error repair attempt. A bit of everything is missing: some MCUs, an analog multplexer, some ADCs, two VCOs, a handful of passives. What were they thinking? :palm: A total shame, whoever did this to such great piece of equipment. :--
I'm quite desperately looking for:
- A donor acquisition board of a -B series scope: TDS7154B, TDS7254B, TDS7404B, TDS7704B, TDS6604B or TDS6804B. Bad or good, anything would be better than nothing at this point. Those on Ebay are simply too expensive for this kind of adventure.
- Some really helpful person who could make detailed pictures of the original TDS6804B acquisition board and perhaps measure a couple of components. Even willing to pay a fee for it.
A ton of thanks in advance to anyone can help me with this. :clap:
-
I'm completely stuck with the repair of a TDS6804B scope some less honest seller has sold me, as the acquisition board has been stripped in what seems to be an unscrupulous try-and-error repair attempt. A bit of everything is missing: some MCUs, an analog multplexer, some ADCs, two VCOs, a handful of passives. What were they thinking? :palm: A total shame, whoever did this to such great piece of equipment. :--
It's very likely that someone was harvesting parts from your scope to fix another. Even if you were to find all the parts for it, it probably has other issues as well - otherwise, why take parts from a good working scope?
I do not envy your task!
-
It's very likely that someone was harvesting parts from your scope to fix another. Even if you were to find all the parts for it, it probably has other issues as well - otherwise, why take parts from a good working scope?
I do not envy your task!
That's indeed highly likely, but still, it's a shame. You don't give up on a device like this. They did use pro soldering equipment, I can see that, but their diagnostics skills seemed way less impressive.
Still, I'm prepared to give it a try in case I find a -B series donor board and more info (it seems TDS6/7000B series share a lot of components, based on photo observations). Once the VCOs are running and the main MCUs and other smaller stuff are back into place, it may show some signs of early life and real diagnosis fight can start. :box:
So, anyone having one of these TDS6/7000B acquisition boards lying around or for sale, for free, bad or good?
-
I have two almost working 6804B's, I can send you pictures of the boards. Would be cool to collaborate on repair of these devices. Do you have any info on the architecture of AQ board?
-
I have two almost working 6804B's, I can send you pictures of the boards. Would be cool to collaborate on repair of these devices. Do you have any info on the architecture of AQ board?
Currently I don't have any, but I'll figure it out very soon ;) I'll get in touch with you via PM for personal details.
-
Can anybody help,I did that as change the file sn,key and removed the#in the file，then I restart the instrument,now it seems stuck as the picture shows,should I wait or change the NVRAM battery?
-
[/quote]
Use the .sn file attached and replace Bxxxxxx with whatever your SN is.
To have the right options please update the .key file xxxxx-xxxxx-xxxxx-xxxxx with the option key on the back of your scope.
Store both files in c:/vxBoot/. Then look up topScript.hw file and uncomment the line "# NvramClearDb = 1" by removing the #. Reboot once so the SN an key are stored in the NVRAM and then comment back.
This did it for me. The files are taken from my TDS7104.
[/quote]
I just changed the three files and then restart my instrument . And then it stuck, can anyone give me some tips？Have I missed something?
-
Hi Guys!
Would like to share some repair info back on the TDS7104, in this case the power supply.
I turned on my TDS7104 recently after a long time and it smelled strange and did not turn on. I immediately removed the power supply, inspected it visually.
The effect was:
- strange smell (but no Smoke)
- A clicking noise about 3-4 times per seconds when powered
- the RED LED close to IC310 was blinking with the same frequency as the clicking sound.
Began reverseengineering the schematic based on the PCB and doing lots of measurements.
Capacitor C97 was measured to have an ESR of 2 Ohm. This was unexpected high, allthough not tremendously too high.
I replaced it with another one (only had a 100V type lying arround, so it does not fit mechanically perfectly). This was my luck, because
I had to mount it with a distance to the PCB, and only because of this, I noticed this here:
https://youtu.be/4Kj9WRJPUvI
Note: The smoke is not coming from the cap, it is coming out of the PCB. Furthermore, there are sparks on the PCB.
Microscope inspection showed, that the CAP got incontinent and left it's jam on the PCB, where it etched it partly ways. After removing this, it turned out to have left a 1mms deep hole in the PCB. Likely this dielectricum got conductive too, otherwise there would not have been sparks.
After cleaning + remounting the new cap, the Supply was perfectly working again!
Best regards,
Kai
Still, I think this might happen to other CAPs too. Maybe worth to replace nearly all eletrolythic capacitors?!?
-
Hi Guys!
Would like to share some repair info back on the TDS7104, in this case the power supply.
I turned on my TDS7104 recently after a long time and it smelled strange and did not turn on. I immediately removed the power supply, inspected it visually.
The effect was:
- strange smell (but no Smoke)
- A clicking noise about 3-4 times per seconds when powered
- the RED LED close to IC310 was blinking with the same frequency as the clicking sound.
Began reverseengineering the schematic based on the PCB and doing lots of measurements.
Capacitor C97 was measured to have an ESR of 2 Ohm. This was unexpected high, allthough not tremendously too high.
I replaced it with another one (only had a 100V type lying arround, so it does not fit mechanically perfectly). This was my luck, because
I had to mount it with a distance to the PCB, and only because of this, I noticed this here:
https://youtu.be/4Kj9WRJPUvI
Note: The smoke is not coming from the cap, it is coming out of the PCB. Furthermore, there are sparks on the PCB.
Microscope inspection showed, that the CAP got incontinent and left it's jam on the PCB, where it etched it partly ways. After removing this, it turned out to have left a 1mms deep hole in the PCB. Likely this dielectricum got conductive too, otherwise there would not have been sparks.
After cleaning + remounting the new cap, the Supply was perfectly working again!
Best regards,
Kai
Still, I think this might happen to other CAPs too. Maybe worth to replace nearly all eletrolythic capacitors?!?
My power supply had the same symptoms that you described, but in my case I still can't fix it. I performed the capacitance and ESR measurement of the capacitors with my DE-5000 meter, but found nothing out of the norm.
-
Can anybody help,I did that as change the file sn,key and removed the#in the file，then I restart the instrument,now it seems stuck as the picture shows,should I wait or change the NVRAM battery?
Hi everyone, glad to be a member of this forum.
You need to see the status of the seven-segment Power PC board diagnostic display.
Codes are described in the service manual.
-
Hello. I became the owner of TDS7054, and it is somewhat broken.
I want to tell you what I found out while I was working on the device and listening to it.
Perhaps my colleagues from the forum will be able to give some advice on whether I'm on the right path or not.
- Here is the history of the device according to the selle:
- The device worked fine at one point.
- Then the device began to lose the user settings after a reboot.
- The seller and his partner read this forum and decided to provide the necessary, but not qualified help for the device. :bullshit: on its own.:horse:
The actions of the "rescuers":
- Ordered with ebay assembly DS1245YP-100.
- They disassembled the device and replaced it on a thermostat with a hairdryer DS1245YP-100.
- They did not carefully assemble the device and broke several pins on the PA bus circuit board connector. It was restored with a wire.
[attach=3]
[attach=1]
- The device stopped loading the program, hanging on the splash screen.
[attach=8]
- It’s not clear why that they couldn’t explain to me, but the MAX232 was unsoldered, they said that they thought the device would boot from this.
- I diagnosed the following:
- The device turns on and the Win 2000 is loading fine. The software freezes on the splash screen.
On the diagnostic seven-segment indicator Power PC board is constantly ".8".
[attach=2]
- The pins are restored on the PA bus circuit board using pins from RJ-45.
- On the board, there are traces of MAX232 soldering and traces of warming up the south bridge of PC87560 (silk-screen printing turned yellow - position marking)
[attach=4]
[attach=5]
- A resistor is torn off the back of the board, under the CPU. CPU_RESET chain. Restored focusing on neighboring components in this circuit at 33 ohms.
[attach=6]
- Processor voltage ~ 2.6V - is normal and the rest of the board voltage is normal.
- The voltage of the power connectors is in accordance with the documentation.
- There is generation on all quartz resonators.
- There is no data exchange on data buses.
- HRESET# signal from the MPC740 CPU and MPC106 Northbridge is not removed.
- The output signal CPURST of the south bridge of PC87560 is not disabled.
- The input signals of PC87560 PM_PWRGOOD 3.3V and RESET_IN # 3.3V are good, but CPURST 3.3V.
[attach=7]
- When the CPURST is pulled to the ground, there is activity that appears on the boot rom U580 data buses, I think the MPC106 north bridge reads the software.
- In my opinion, the PC87560 is not working.
- The PC87560 I purchased on ebay, is being delivered.
- I purchased the MAX232.
- I ordered F28V100 to replace the manufacture of replacement DS1245YP-100.
- Analyzing all the data that was obtained, I think this is what happened:
- Without going into details the "rescuers" read the first post of this forum thread.
- The DS1245YP-100 is soldered.
- They soldered the wires to MAX232 from PC87560 side. They were not attentive.
I think they had a USB to COM-port converter (with a glimpse of PL2303), which had to be connected to the debug port, and not was not soldered to the MAX232. - The PC87560 received +/- 12V, which destroyed it and changed the code on the diagnostic seven-segment indicator Power PC board.
- They tried to unsolder the MAX232 thinking that they only burned it.
- Not achieving their result, they tried to fry the PC87560.
- They finally realized that they did not have sufficient qualifications and sold the device.
I have a few questions:
- I want to ask the more experienced specialists in repairing forum participants, to evaluate my diagnostics, and to give advice if I missed something.
- There is not enough documentation on the PC87560. Is there a circuit on the TDS7054?
- Perhaps there are people who know power-on sequence Power PC board?
- Dear TxB, I ask you to send a gerberfile if possible for the manufacture of a board on F28V100. My email is the-hedgehog@yandex.ru
- Is it possible to remake the device in the TDS7104? If the question is not correct, please inform the-hedgehog@yandex.ru
Thanks to everyone who had the patience to read this.
-
Would still replace the capacitor, that I highlighted and carefully clean the pad below it. I know of one other case, where exactly this was the cause.
Maybe it is better to even replace all CAPS. Just did this, because I was afraid of other capacitors dying in a few weeks from or so. Several of them had ESR values of e.g. 3 Ohms instead of the expected 0.0x Ohms, that the same caps from different locations had.
To ease, here a List, that I compiled. The diameter and height is just an approximation. Costs were ~40EUR for all capacitors, took me about 2h to replace. Some pads are very difficult to remove solder from, due to huge thermal mass. For some spots I needed the support of a heatgun. Take care, that you don't destroy vias, better heat up too long, than too short.
Here the list - Sorry, no shopping links included, I ordered those from a german catalog vendor.
Height [mm] Diameter [mm] Voltage rating Value Temp
C807 15 6,5 63 100u 105
C89 12 5 63 10u 105
C61 39 12 35 1500u 105
C62 39 12 35 1500u 105
C63 39 12 35 1500u 105
C78 39 12 35 1500u 105
C68 39 12 35 1500u 105
C57 39 12 35 1500u 105
C77 39 12 35 1500u 105
C74 39 12 35 1500u 105
C71 39 12 35 1500u 105
C72 39 12 35 1500u 105
C38 39 12 35 1500u 105
C39 39 12 35 1500u 105
C41 39 12 35 1500u 105
C32 39 12 35 1500u 105
C36 39 12 35 1500u 105
C37 39 12 35 1500u 105
C30 39 12 35 1500u 105
C31 39 12 35 1500u 105
C29 39 12 35 1500u 105
C27 39 12 35 1500u 105
C23 39 12 35 1500u 105
C26 39 12 35 1500u 105
C65 39 12 35 1500u 105
C70 39 12 35 1500u 105
C903 38,5 12,7 35 1500u 105
C347 12 6,5 35 22u 105
C116 20 10 35 330u 105
C115 20 10 35 330u 105
C113 20 10 35 330u 105
C114 20 10 35 330u 105
C900 20 10 50 330u 105
C528 12 5 50 4,7u 105
C18 53 35 450 470u 105
C19 53 35 450 470u 105
C93 12 5 50 6,8u 105
CU1 15 6,5 35 68u 105
C84 15 6,5 35 68u 105
C97 15 6,5 35 68u 105
C95 15 6,5 35 68u 105
C500 15 6,5 35 68u 105
C908 15 6,5 35 68u 105
-
Lahay_Alexey, did you restore the configuration parameters in NVRAM via console? Do you get any console output on debug UART port?
I'd start from there, before cooking parts like previous owner :palm:
-
TiN thanks for answering. I am not very good with English and maybe you didn’t understand everything from my previous post. It is not possible to restore the NVRAM parameters at the moment, the PPC board is not working, the PC87560UDB south bridge is out of order. The previous owner crippled the chip when trying to connect to the debug port incorrectly. Now it makes no sense to connect to the debug port, it does not reach the initialization of the com port. Debug port is implemented, just in PC87560UBD, but it does not work correctly. PC87560UBD does not remove the reset from the processor and north bridge. If you independently pull up the processor reset and the north bridge to the ground, then bootrom is read and everything stops with the code "1" on the seven-segment indicator and the debug port is silent. PC87560UBD ordered, waiting. As it comes, I will change it and I will try to work with the debug port.
-
Can anybody help,I did that as change the file sn,key and removed the#in the file，then I restart the instrument,now it seems stuck as the picture shows,should I wait or change the NVRAM battery?
thanks to everyone, this problem was fixed after I reinstall the 2.5.5 firmware.
-
Hello
I really need some help with setting and changing up booting parameters using a console. I have read this whole topic and few others multiple times.
I have TDS7104 that is in almost perfect condition, the power cap battery is new, the unit has an older motherboard with 500MHz celeron.
The 7 segment display counts up to L, and stops there.
The console also just stops outputing data after attempting to attach a HDD.
It is the same if HDD was in or out of the unit. Floppy drive, HDD and CD rom are all detected in bios. If I boot into dos using win98 boot disk I can access floppy and CD drive but HDD C: is not detected.
Hard disk works, I checked it in a PC, and everything looks fine. I did not try to boot from it, but it is certainly not damaged, because I just cloned it to another newer drive and the issue still persists.
Now, the really strange part is that when I use c command in console, and I change boot parameters (for example target name to "target" from this default value given bellow) to the same ones posted in this topic by TiN and others i confirm that they are active and taken using p command. It looks perfect, however when I restart the unit, non of the changes are saved. I am back to the old values
Is there a command to save the given values? Are they saved automatically? I feel like I am missing something obvious. |O
Thanks you in advance.
Here is the dump from the console:
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.8.0
Creation date: Jun 27 2003, 09:52:32
Press any key to stop auto-boot...
1
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
-
Hello, I just want to give some update on my lack of progress. |O
Inspired by this post and topic from user Jwalling (https://www.eevblog.com/forum/testgear/high-failure-rate-of-maxim-integrated-ds1245yp-100-chips-on-tds7000-scopes/msg1169449/#msg1169449) I removed a powercap and solder a large shunt resistor in series with the battery to measure current draw of the NVRAM chip because I was perplexed by not being able to store any data in the NVRAM, and the boot parameters just reverting to default values.
The current drawn from battery was about 7.5nA, and that sounds too low, but could still be acceptable. The battery was older but not depleted, voltage was about 3.2V.
When unit was powered bat. current was 0.
Jwalling wrote that he measured about 20nA current load when unit is powered off.
Now for the interesting part. I could never get HDD to show me a partition when booting into DOS from a floppy.
I tried to format and create one using FDISK but the process would usually fail. It looks like connection between HDD, CD drive and motherboard is highly unreliable.
I noticed that sometimes bios would not recognize CDDrive or HDD. Sometimes it would find them if I put a little pressure on IDE connector but with incorrect names.
For example toshiba HDD would be shown as "TNSHIBA" and IBM DARA HDD would be shown as "D@R@" (last bit in a ascii char byte obviously wrong).
I will take out riser card and inspect cables, and connector fingers to see if something is obviously wrong. If someone has a hint, any suggestion is welcomed.
-
Well I worked on this whole night, and here is a last shout into the void.
The problem was in the connections between PowerPC and NLX motherboard. Some pads were dirty but main issue was that the riser board was somehow very sensitive to position and angle of the motherboard.
The mechanics of this particular unit were putting a lot of pressure on one side of the board. It took me a while to level everything and secure the boards in place.
Now it boots every time and passes self test. I did not need to play around with boot parameters in console. default values just worked.
I cloned a HDD into an SSD. For few of my instruments I use DeLOCK 62495 adapter and small mSata. This works really well.
Since this unit has an older motherboard i decided to upgrade sometimes in the future to Intel SU810, but I cannot find a bios for that board, even if many members have confirmed that their TDS7104 has that board inside...
I also have a 100MHz FSB Coppermine Celeron CPU that is slightly faster than what TiN originally did with Pentium 3. 1100/128/100/1.75V, number SL5XR.
I expect it should work without mods.
If someone has a bios for the intel board, can you please share it.
-
...and now I ran into another issue with the TDS7104 power supply. The analog power supply (+-15V, +-5V) is dead. The board makes a funny noise, that is hard to locate.
However: I reverse engineered the schematic of the whole analog power supply section.
Temperature protection, over voltage protection, over current protection, everything you can imagine is there.
Cause of my issue is not yet identified, but this schematic will help.
No warantee, that this is 100%correct, use at own risk.
UPDATE: The attachment was not correct and containsed only a single page. Fixed.
-
Hello, Xyphro. You did a great job, thank you. I have a request: I am trying to improve the characteristics of TDS7054 to TDS7104 and I need a photo of the acequion board area. Required area in the photo from the attachment:
[attach=1]
At the end - the report from me.
-
How did you know, that my tds7104 is open :-D
Find below.
If you find a way to improve tds7104 to 4GHz analog bandwidth, let me know :-)
Let me know, if you need more photos, can also PM them.
-
Thank you for the photo. Unfortunately, tds7104 can only be changed to TDS7404 by radical replacement of the acquisition board and casing. You can specify the values of the following resistors from the photo:
R781, R791, R782, R792, R783, R793, R784, R794.
-
My 7104 was also opened and I was uploading a photo but Xyphro already posted it.
@xyphro
When you say it makes a strange noise, can you be more specific? Is it a click or a buzz? Periodic?
Are you testing the PSU outside the unit? Are other voltages present, from other converters? So we know the issue is not in the input side/PFC.
I ask this because usually such problem would not be in these protection OTP/OVP parts.
With the schematic you posted is a bit hard to tie everything around and primary side of the circuit is missing.
+-15V and +-5V are separate secondaries of trafo T7. There is a peak current control loop from each of the secondaries that probably ties back to primary over opto.
My suggestion if you are confident in troubleshooting SMPS, and have proper equipment, take out power supply, supply it from isolation trafo, it can be a small one since the unit is unloaded.
Start the power supply. I think there was a pinout in the service manual and you can find which pin is turn on pin.
If you have a working scope check the signals from each of the current trafos 1K resistors. It could be that one secondary is overloaded/shorted and it pulls the entire voltage down, or control simply turns off because the peak current was exceed. That would be easily seen on the scope.
That would manifest in a sharp periodic clicking usually, depending on how the overload was implemented in these converters.
If you see nothing, or very low current through the secondaries, you can check directly voltages on the secondary windings in front of current trafos. and go from there.
If you see nothing there too, the problem is on the primary side, and you will have to trace out the primary driving circuit. That is less complex than what you already did.
Good luck.
Edit: Do not touch heatsinks when power is on. They are most likely tied to + or - Vbulk and it can kill you. I am not sure who will read this in the future, so I have to write it.
-
Thank you for the photo. Unfortunately, tds7104 can only be changed to TDS7404 by radical replacement of the acquisition board and casing. You can specify the values of the following resistors from the photo:
R781, R791, R782, R792, R783, R793, R784, R794.
Send me an email in Private messages I will send you high res photos
-
Moin Electopionier,
I included the primary side in the schematic. The pdf has 4 pages. Also the current monitoring. The current monitoring is global to the board. Digital and analog supplies current monitors are all tied together, likely to turn of via the power on/of optocopler path.
I began probing when it was connected, im the meantime I have it externally, yes with isolation transformer and proper precautions (when I repaired my 1st smps about 25 years ago, I made that mistake touching the cooling plate :-)). I hooked up loads to the supply.
So... Digital sipplies are all ok, including the +3v3, for that reason I focus on the analog supply path. OTP OVP OCP is not triggering, this globally turns off the suplly.
Focus now is the primary side of the analog transformer.
There is a voltage feedback loop over an optocouplet and +-5V are the ones, that are taken to close the loop.
What I notice here is, that the optocoupler works. After a short amount of turn on and off, it goes to permanent off state.
Still, ths VFB of uc3844 is 2.51V, which is, because the COMP pin has 4.2V and only due to the resistive divider path with the 68K1 resistor you get that voltage.
This looks a bit tight dimensioned, considering, that 2.5V is the nominal threshold here.
Replacing the uc3844 resulted in no change of this behaviour.
Oh... The ISense path shows a slowly changing DC voltage of 300..500mV, which is funny, will look in that domain a bit further. Would not expect DC here, especially not, if the OUT pin is continously LOW.
Edit: The sounds are mainly some clicking and sometimes a (sorry for german: Pfeifen, with about 400Hz frequency). I tried long time to find the location of that sound, but failed (Another incidence of where a "sound camera" would be cool to have).
Beeing more an RF guy, SMPS are a bit of miracle, allthough I understand the principle well, lacking a bit of experience how it exactly works to the latest details (like the current sensing path), allthough I repaired already quite a few, so any comments welcome.
I attached the primary side of the schematic + notes of some voltages I measured on the UC3844. Whenever I measure a DC voltage with a multimeter, I also checked with the scope, if it is really DC or not. So.. UC3844 is pretty stable in the sense of, that nothing is toggling there.
Best regards,
Kai
Ps: REF shows proper 5V on the uc3844! The big capacitors and PFC are ok and show proper voltages (otherwise the digital supply wom't work too).
-
Oh, what I think is funny is the primary switching side of the main transformer.
JP1 is here the first 4 pins of transformer T7.
There seems to be only a single coil, which is between pin 2 and 4. Pin 1 and 3 seem nowhere connected. Still pin 1 is connected to GND. Maybe there is some additional windings as protection layer?
Or is from my T7 a winding dead?
Does anybody have by coincidence the Scope open and can measure T7 resistances on the primary side, to crosscheck? (Pin 1 is for me the one on the primary side, pointing towards the yellow Fuse F51).
Conceptual question: Why is there a high and a low side switch (driven with solated gate drive), while only a low side switch would be good enough and do exactly the same?
-
Hello Xyphro
I am happy that you have some experience working on SMPSs and take proper safety measures.
I am not surprised that replacing the IC did not help you, the control ICs really do not fail in these units often. Sorry I missed the page with prim.
I would give you a small advice, when troubleshooting these circuits you must have structured approach. These are very repairable but please take things slow, replacing components on random will always cause more damage then original fault. Do not jump to voltages around control IC right away, because most often the problems are in power section not control section.
1) Check the currents directly on shunt resistors R12. You should see triangular waveform there, and certainly no dc component. Is the trafo being driven? if not then...
2) Check gate driving on the directly on the push pull output before 4x10ohm resistors. What do you see there?
I did not really understand your explanation regarding optocoupler, but here is what you should have.
In normal operation if the measured output voltage is 0V (or much lower than reference) on the secondary side, optocoupler transistor on the primary side should be opened. You should see 0V on VFB pin.If you see higher voltage there that would indicate that feedback path is falsely telling controller that voltage is too high and it should bring it down and stop switching.
Edit: My mistake, i wanted to say that if opto transistor is OFF you will see some voltage on the Vfeedback pin. That is good. The optocoupler's collector is connected to current source. COMP pin is open collector and is driven from current source. This voltage is compared to internal sawtooth generator to create driving PWM. 0V on comp pin would equal to 0%duty cycle. 2.5 or 2.51 is where duty cycle starts increasing to max of 50%. So all is ok there. Probably the problem is in the driving section. My advice is still valid. Sorry for the mistake.
Can you confirm this?
Update: can you draw the trafo in your PDF that I can see. But open ended windings are not uncommon in SMSPs trafo desing. Those are sometimes connected to a copper shield and sometimes are a real winding with 20-30 turns called compensation windings that create "fake" capacitance between primary and secondary side winding terminals and compensate injected RF current. It is a mark of good desing, and not damaged trafo.
As you see I design these types of power supplies for a living :)
-
Conceptual question: Why is there a high and a low side switch (driven with solated gate drive), while only a low side switch would be good enough and do exactly the same?
We have many topologies and all provide different benefits to designers. Yours is 99% a dual switch flyback. You can see a short explanation here. (https://www.st.com/en/applications/power-supplies-and-converters/two-switch-flyback-converter.html) But in general dealing with flybacks main issue is how to overcome large transients when the low side mosfet switches off and what to do with energy stored in leakage inductance. This can be few watts actually and is usually dissipated and that creates heat and losses. In dual switch flyback that energy is re-used by returning it to Cbulk.
-
Thanks for your valueable feedback. Especially giving that topology a name for better understanding on my side. It also gives indirectly the hint, that the transformer is ok.
The replacement of the controller was a quick shot, I don't replace more untill I see the problem :-)
Will do the proposed measurements.
Right now there are 2 phases: after power on it seems to switch for some seconds and then stops.
VFB get's too high indeed, for that reason it stops switching.
What confuses me is, that the comp pin is high, stating correctly a too high voltage, but this comp pin is also making the voltage on the VFB 2.51V, which is so close to the 2.5V threshold of the comparator in the uc3844.
The voltage accross the 750Ohm resistor is btw. 0V in that state, so the optocouplet is signalling correctly too low voltage, matching, what I see on the DC low voltage side.
Anyway, more debug this afternoon, based on your proposed measurements. This will only work after power on for a few seconds.
Best regards,
Kai
-
Hi Kai, please see edit of my previous post. I made a stupid mistake in my explanation that I corrected. I haven't read my post after publishing.
-
Could not wait until end of the day :-)
Did some measurements, please find attached.
The ISense behaviour is puzling me. The Current shunt is 0V continously, still ISense shows some voltage. As this is below 1V, I'd expect it not beeing the cause output toggling off, but well....
This seems to come somehow from the transistor circuit connected between REF, RT/CT pin and ISENSE (is this for slow start?).
-
No issues, thanks for fixing.
It is clearly very visible, that this is your daily job :-)
I hope I show expertize too in showing, that I can measure this without a lot of magnetically coupled spikes on the scope :-)
-
I know how you feel when you work on something out of your field. I just spent 2-3 days adjusting the drift on my Advantest spectrum analyser and tracking gen hoping that I do not damage it even more. :)
Kai, these control ICs are very standard and almost everyone has one. I made you a short simulation in LTspice so you can see what you should expect when there is no feedback from opto. LT1244 is the same IC but made by LT/analog devices.
Can you check if you also have clock signal present in Ct/Rt? Something is keeping the IC off, we must find what that is. So far the control voltage feedback looks OK.
EDIT: I see that you measure 0V at clock signals, that is quite strange. Ah, that was pin 4 of the opto, not control IC. That looks good. Check for shorts on the timing capacitor pin4 of control IC, during startup or continuous operation we should always have clock there. I feel like something is loading that point. The NPN transistor should not do that unless it is damaged but voltage also does not match the expected oscillator voltage. There is something wrong there.
What you can do, if it is not too difficult, you can for example remove 47R5 on output pin so the unit does not turn on while you inspect. Tie push pull to ground so we have no accidental turn-ons even if unlikely.
Remove that NPN from timing circuitry and see if you will get correct oscillator voltage. The ic should always have that, there is nothing in the datasheet that would disable the oscillator that I can see.
Another point, DC offset on Isense pin is also quite common. It lifts the input of the current comparator from 0V so that control loop has some space to set feedback voltage lower than Isense and keep duty cycle safely to 0% taking into account offset voltages in IC and any noise coupling into sense pin. Another benefit is a slope compensation that makes these types of converters more stable, but I will not go into that.
-
Thanks again. The RT/CT is clearly not showing any oscillation.
I get 2.5V with random noise on it, but not the typical RC oscillation characteristics, as visible in your simulation.
Finally something, where I can check deeper.
-
From the datasheet i think that if the voltage on the cap does not rise above 2.8-3V the oscillator will not reset, it will not try to discharge the cap.
Usually oscillators in these ICs are just a simple analog comparator with hysteresis. Loading the capacitor point with 2-3kOhm could keep the voltage too low.
Another possibility could be for example that you have instead of 3k65 a lower resistance, or that you have a breakdown in NPN transistor. That would source more than 10mA into Rt/Ct pin and it would prevent IC from discharging the 2n2 capacitor. You can measure this nondestructively by observing charging of Ct during turn on. It should have time constant of stated component values, and if it is too fast or too slow you have your answer.
-
Your guess was right: The Transistor was broken - was unable to measure the diode between Base and emitter.
This can only have been a side effect. Now the UC3844 oscillates like in your simulation, but (and a big but): Once replaced, it oscillates for some time and then breaks again. Then I replace it again and it works again for some time.
Also the (audible) noise is back (which was gone before).
I also measured the voltage accross the current shunt. Now I see something there.
What I see is not, what I would expect ideally. I see short bursts every few oscillation cycles, having swinging also towards the negative side (note: the ch2 is set to AC coupling in the attached screenshot, but with DC coupling it looks exactly the same).
I can not fully exclude, if those are measurement artifacts. I soldered a coaxial cable across the current shunt, but maybe still something coupled in here.
Will now probe step by step towards the FET gates, but right now I suspect something wrong in the final stage FET stage.
Best regards,
Kai
-
Ok, now we know why the IC did not start. Large positive peaks could kill this transistor by exceeding negative max Vbe that is usually around 5V. That is why i suggested first to remove driving from push pull stage.
I was afraid that underlying problem is still present.
Check the driving signals at the output of push pull and shunt voltage. Does the effect appear at turn on or turn off? I assume turn off.
To make sure that what you see is real, you can short your coax both ends on gnd or high side and see if the effect is still there. If it is it is not real. But i suspect that what you see is real. Shunt resistor is very low values, it would take a lot of power to inject that much noise.
Such high peaks and impulses I would usually see in short circuit conditions either across primary or one of the secondary windings. Measuring output directly on the current transformers can tell you if some secondary is shorted somewhere.
Do you see a ramp current during ON period on the shunt? The amplitude would be much lower than the peaks you show so I cannot tell from the picture.
-
I know it is a pain, but at this stage to be safe, i would for example remove the fuse in series with high side fet and supply the converter from a lab power supply. Other converters are all fine. but this one i would supply from like 30-40V and a lab PSU with current limit. Check if the body diodes of Mosfets as well as gate resistances are all normal. This should be possible to do in circuit.
It would be much safer for you and for the PSU to find shorts and opens when working with low voltages. You can leave 18V Vcc that is fine.
Disconnect the PSU. You can use also small 9V battery, and a 1k resistor and try to turn on and off each MOSFET, check by measuring Rdson. These are simple steps that will tell you if it makes sense to investigate the circuit in more details, or the problem is obvious. I assumed you already found no visible damage on mosfets. Sometimes that happens.
-
Hi again,
I tested now:
Body diodes of the IRFP460 (not IRFP640 as I wrote in the PDF)
- present as expected :-)
- RDS(ON) of Q10 is 0.23Ohm and it turns off as expected
- RDS(ON) of Q9 is 0.235Ohm and also that one turns off as expected
Furthermore, I tested the voltage limiting circuit with the 2 18V zener diodes. Also here I see, that it limits correctly to roughly 18.8V. I tested this in both directions to ensure, that both the zener diodes work as expected.
I measured (CR80/81) and also they properly conduct only in one direction and show very low Vf as expected.
I right now now injected 30V into the Fuse (Fuse removed) and also injected the 18V externally.
The UC3844 oscillator still oscillates and the ISense pin still shows the same huge voltage transient. So far so good.
Unfortunately I have killed the NPN transistor FMMT720 of the isolated gate drive transformer driving circuit due to a measurement mistake.
Reichelt order is out, too tired now to replace it with another transistor from a different section of the power supply.
What I think I had seen is, that the amplitude of the transformer (T52), that drives the gates was for one of the final stage FETs about only half as high as for the other ones. Unfortunately seconds after this, I killed the above mentioned transistor.
I will check further tomorrow. Learned a lot today in terms of SMPS testing metothology today, thanks for your hints.
Getting a bit afraid, that the actual transformer T7 is killed. This would likely be the killer criteria and the way forward for me to replace the full power supply. I expect this is a custom made transformer, that is not available off the shelf.
Next steps for me:
- Replace the Gate drive FMMT720 transistor.
- Check, if my observations with the different voltage amplitudes for the 2 final stage FETS is correct.
- Maybe replace the primary side coil from the transformer with a resistor and measure ISense again?
- Continue investigations on the secondary side (but could that kill components on the primary side? Based on the schematic I can first decouple the 15V path, to check, if there is a short present
Best regards,
Kai
PS: Attached how it looks like now. Need to remove a lot of flux at the end, but well, lot's of cables. NICE :-)
-
Hi again,
I tested now:
Body diodes of the IRFP460 (not IRFP640 as I wrote in the PDF)
- present as expected :-)
- RDS(ON) of Q10 is 0.23Ohm and it turns off as expected
- RDS(ON) of Q9 is 0.235Ohm and also that one turns off as expected
Furthermore, I tested the voltage limiting circuit with the 2 18V zener diodes. Also here I see, that it limits correctly to roughly 18.8V. I tested this in both directions to ensure, that both the zener diodes work as expected.
I measured (CR80/81) and also they properly conduct only in one direction and show very low Vf as expected.
I right now now injected 30V into the Fuse (Fuse removed) and also injected the 18V externally.
The UC3844 oscillator still oscillates and the ISense pin still shows the same huge voltage transient. So far so good.
Unfortunately I have killed the NPN transistor FMMT720 of the isolated gate drive transformer driving circuit due to a measurement mistake.
Reichelt order is out, too tired now to replace it with another transistor from a different section of the power supply.
What I think I had seen is, that the amplitude of the transformer (T52), that drives the gates was for one of the final stage FETs about only half as high as for the other ones. Unfortunately seconds after this, I killed the above mentioned transistor.
I will check further tomorrow. Learned a lot today in terms of SMPS testing metothology today, thanks for your hints.
Getting a bit afraid, that the actual transformer T7 is killed. This would likely be the killer criteria and the way forward for me to replace the full power supply. I expect this is a custom made transformer, that is not available off the shelf.
Next steps for me:
- Replace the Gate drive FMMT720 transistor.
- Check, if my observations with the different voltage amplitudes for the 2 final stage FETS is correct.
- Maybe replace the primary side coil from the transformer with a resistor and measure ISense again?
- Continue investigations on the secondary side (but could that kill components on the primary side? Based on the schematic I can first decouple the 15V path, to check, if there is a short present
Best regards,
Kai
PS: Attached how it looks like now. Need to remove a lot of flux at the end, but well, lot's of cables. NICE :-)
Good work. Primary side looks ok so far. You can check if all the diodes on the secondary are all ok. Usually that would make your short.
I am talking about diodes that come after current transformers BR5,6,7,8,9... If the diode that is placed between ground and Elco is shorted in any of the secondaries it would create such spikes in the off period that you see in primary.
I suspect a short on the secondary because prim. short would usually be much harder and kill the primary mosfets and fuse first... Also it would be probably more in synch with gate driving signal. And there we see some 1us delay.
That is why I said would like to see shunt voltage/prim current and gate driving to see is the current impulse happens during mosfet ON or OFF period. These are all educated guesses, i cannot be sure before testing.
I still think it is unlikely you killed your trafo. You are correct that it is not of the shelf part. However these supplies are difficult to come by and expensive.
Even if trafo is dead, perhaps we can rebuild it. We are not there yet. Lets take things slow.
You can for example easily check secondary diodes, and then disable secondaries by opening current trafos. They are connected with just normal wire, you can lift one side and disconnect it. I would first try +-15V and put a small load on +-5V output, and then do it other way around.
Disconnect +-5V and put some small load on 15V to limit flyback voltage...
That still looks ok :) , you can clean it up nicely once we find a problem. Just try not to damage PCB by using too high temperature to solder/desolder small parts. That can really make life difficult.
-
Hi again,
will not forget about this, saw it yesterday after writing my email also:
"That is why I said would like to see shunt voltage/prim current and gate driving to see is the current impulse happens during mosfet ON or OFF period."
Maybe I continue this evening, can take a transistor from the digital supply until replacement arrives. Have likely a 12h-16h job for a bringup in the more comfortable dual digit GHz domain today...
Best regards,
Kai
-
No need to hurry, do not risk damage to other parts. Golden rule is if it isn't broken, don't fix it.
Exception would be, if you already have the unit out, you could replace electrolytic caps of small diameter. I am not talking about large 1500uF nichicon placed at outputs (if i remember correctly) but those tiny 5mm elcos 63V some 100u and some other values. Those limit your lifetime and die all the time. Often causing other failures. I really do not like finding those in my PSU.
-
This is a short step by step on how I got Win-XP to work on TDS7104, and presumably other TDS7000.
1) I bought a used SU810 motherboard, that apparently came out of a Gateway PC. These are identical to intel MBs you can sometimes find on ebay. Intel has also deleted all the documents about their legacy products so finding any software for these was not easy.
Motherboard has a bios version P12, that i cannot find anywhere, and I cannot find anything about it.
This motherboard fits perfectly in the tray and ports align perfectly.
I placed 2 pieces of double sided 256MB RAM sticks for total of unbelievable 512MB. :-DD
USB Jumpers: Motherboard has 2 usb ports. There are two unpopulated jumpers behind a port. You must populate them and fit jumpers on position 2-3 and 5-6. Upper usb port is internally wired and used to talk to front panel. More info can be found in Intel SU810 PDF documentation.
2) I found a rare Celeron 100MHz FSB that work on 1.1GHz so much better than 500MHz that was originally there. I still cannot confirm if 133MHz fsb CPU would work here. I even found for 5 euro, unused aftermarket cooler for socket 370 and it is very quiet.
2.5) I kept old HDD as a backup but installed MSata to 44pin IDE DeLOCK 62495 adapter. I used it in few other instruments like CMU200 and it always worked wonderfully. And it is much faster.
3) Install standard Win XP. I used small and cheap 20 euro wireless keyboard and mouse and a usb dongle, because I like to use a mouse with my scope. I do not like to touch the screen of my instruments. It worked perfectly during installation. OS recognizes most of the hardware.
4) Most of the problems I had was with drivers for Texas Instruments PCI-1225 CardBus Controller. These were creating conflict on PCI bus and preventing PowerPC board to talk to the PC.
Drivers were luckily provided by user snoopy, but I believe that they were also posted in this thread in a zip file "tektronix.zip".
You must manually force OS to use the driver unsup.inf. and device will be registered as "unsupported" but it will work.
5) Graphic drivers for Chips and Technologies AGP Rage do not work with WIN XP. The correct driver is in the same zip file under CHIPS. You must again manually force use of this driver in device manager.
6) Front panel driver is also there. As well as driver that windows shows as "other PCI bridge". That is driver for tektronix PowerPC board. It is in folder PCI2PCI.
7) Install IVI driver that can be downloaded from TEK website called IVIDriver3.9_066045315_0.exe. First install part in shared folder then COM.
8 ) Install TekScope driver/Firmware again found on tek website. File is called TDS7104_7054_V2.5.5_066031808.exe.
By this point VXworks.st would load and tekscope app should work.
I had issues where file TekScope.o did not want to load for some reason. There was an error shown in console. But I had a backup of hard drive with Win98 that was previously installed and working, and I copied the same file over and then it loaded without problem. I think this is probably something i did because I was experimenting trying to get it to work. And I installed and uninstalled bunch of these drivers multiple times.
That is all. I just wanted to write a short to the point guide since information in this thread is all over the place and it took me too much time to set this all up.
BONUS:
-HDD Raw copy tool is perfect for making backup images and cloning drives. I used it for all kinds of mediums, from ssd to compact flash.
-The old BL440 motherboard had Tektronix splash screen when PC was booting. This new one has an ugly Gateway logo that is a cube with cow colored pattern. I found this guide how to change splash screen in these motherboards (https://www.intel.com/content/www/us/en/support/articles/000006606/boards-and-kits/desktop-boards.html). I will try it out later. Actually if you want tektronix splash screen you can skip the entire first part on how to prepare an image and convert it to .usr file. There is file called LOGODATA.USR in old win98 tektronix/bios folder together with iflash utility. But I will use iflash that comes with a bios for this motherboard. Hope it works.
-
OK, another small update. I managed to change the splash screen. I found a SU810 bios version P10 on rebyte.me
You can find it in the attachment for those who need it together with tektronix logo file. I know this is just visual effect but the cow logo was really bothering me :)
There is another version of P10 bios update utility file SUAP10EB.EXE that is supposed to work straight out of windows but it did not work for me. This DOS variant works ok.
1) it is a self extracting file (runs in win xp, not in win 10), place it in new folder and follow the steps in the intel guide.
2) run.bat creates bootable floppy so copy the logo to it, and rename AUTOEXEC.BAT to AUTOEXEC.BAK. Name does not matter really but if you do not change extension the process tries to only flash the bios part, and it does not give you control in iflash utility. Everything is done automatically within few seconds and then you must restart. The user area where logo is stored is unchanged.
The rest is simple as described in the guide, you just update user data area with the logo in .USR format, and reboot.
-
I find this thread so interesting, it reflects a kind of "failure is not an option" engineering approach to be able to fix anything. It even made me go look on eBay for a TDS7000 to fix up but the financial aspect doesn't look particularly compelling for me. On eBay it seems to cost $1,200 for an "as-is" TDS7104 that I then have to spend a load of time and money on and even after I make it all work, I need a $350 TNC-BNC adapter for every channel and what I end up with is an old 1 GHz, 4 channel scope.
If I found a TDS7104 in a dumpster and was offered some TNC-BNC adapters for $100 each, maybe.
I'm not knocking you guys, just reflecting on some real-world financial aspects.
-
Hi Gandalf,
I compare such things always with prople spending time in solving Sudokus or crossword puzzles. Looks like a waste of time, but entertains. Certainly you are right, but solving technical issues is the major fun of engineering. And in worst case you learn a new problem solving technique or get to know a nice technical concept that other engineers designed, to learn from.
Best regards,
Kai
-
Hi Gandalf,
I compare such things always with prople spending time in solving Sudokus or crossword puzzles. Looks like a waste of time, but entertains. Certainly you are right, but solving technical issues is the major fun of engineering. And in worst case you learn a new problem solving technique or get to know a nice technical concept that other engineers designed, to learn from.
Best regards,
Kai
I agree :popcorn:
-
Hi Gandalf,
The TDS7104 does not require a TPA-BNC adapter. It is equipped with conventional BNC. A TPA-BNC adapter is required starting from TDS7154 and higher.
-
Hi!
Short update from the power supply:
I have turned my isolation transformer into an adjustable DC supply with a rectifier+capacitor, so that I can inject higher voltages than 30V into the primary side.
After lot of debugging, checking, if the voltage feedback loop works, ...
It turns out, that my external load resistor on the +5V was not connected properly anymore.
Basically it turned out, that when this resistor is not present, the choke L13 begins to "sing", thus making audible noise. As secondary effect all supply voltages drop in that condition heavily.
After connecting the 15Ohm resistor again to the +5V, everything was all of the sudden working again, with 1 exception: The +-15V only has voltages of about +-12V to +-13V, as function of the load on the +5V.
While a load dependency is not surprising (only +-5V are regulated), the fact, that the +-15V is so much off is a bit surprising to me, because I think the whole intention of the supply is to generate a voltage higher than nominal with the switched mode supply part and then limiting it with a final stage of a discretely build up linear regulator, to get less power supply ripple and better accuracy.
I could not find any further fault. There are clearly not shorts in the secondary path. All diodes are properly working too.
Only the 2N2222 transistor on the RT/CT / ISENSE branch was broken + I replaced the FMMT619 and FMMT720, because I broke them myself due to a measurement fault.
The 2N2222 transistor did not break again. If this missing load on the +5V could have caused this?
Cross fingers, that the acquisition board is not broken due to a fault in the supply.
Best regards,
Kai
PS: I attached a measurement of OUT and the voltage accross the RSENSE resistor. It is clear, that it occurs, when OUT is turned ON.
-
Oh btw. Current ramps are also present on the ISense!
-
Strike, it works!
Loading both +5v and -5v with 15 OHM got btw. also the +-15V to its expected levels.
Have plugged the supply back into the scope:
Very happy for today, it works (see picture showing it still only half assembled) !!! Thanks Electropionir for your remote support in this thread.
Next Step is to get windows XP + ssd running.
Best regards,
Kai
-
Sorry for my late reply. I was occupied yesterday whole day.
That looks good. I am very happy that it works.
I am trying to understand about underlying fault to evaluate if it is likely that this will occur again.
I can understand that transistor failing in case of large current peaks as they were present on the shunt. That is completely possible. One simple preventative measure here would be for example to place a small micromelf signal schottky /40-60V/ in series with emiter of MMBT2222 and 619 ohm. That would take care of negative vbe and I think prevent the transistor from damage.
I checked some photos online, since i never took out PSU out of my unit.
From the primary setup I assumed this was a 2 switch flyback, however your last oscilloscgraph and presence of L13 inductor makes certain that this is actually a 2 switch forward. That is quite popular topology for stabilizing multiple uncontrolled outputs.
However such large currents can only (other than a hard short) be present in case of one of the diodes on the primary side still conducting at the turn on moment.
These diodes would usually have large reverse recovery current, they are old components, and that would be a huge current impulse that could excite such oscillations. No load conditions make that more likely but still...That is quite a reach in logic that would require more evidence.
Contact me if the problem appears again. Good luck with setting up windows. I just went through that few days ago as evident from my previous post.
I really like the different color matched diodes for different channels. Very nice!
Did you replace them yourself? What components did you use?
-
Hi again!
The idea with the diode is good. Maybe this prevents further breakdowns. But I agree, it does not feel like the full final solution yet. Let's use it and monitor further behaviour.
The LEDs I bought from Aliexpress. Could not find similar LEDs anywhere else:
https://de.aliexpress.com/item/32820923105.html
Theese were the closed ones, compared to the original ones. I just see, that they are not available anymore, but if you google for "1,5mm LED diode Licht Weiß Gelb Rot Grün Orange Blau", then you will find other available LEDs of the same type.
I could not identify within this thread, if SF810 supports Windows XP - only SU810 seems to be confirmed here, still will try it out and let know the outcome.
Best regards,
Kai
-
I repaired the Power Supply CCA via another thread, but have had a heck of a time getting Tek Firmware to load... I have tried Win2kSP4, and now XP. I've loaded the graphics drivers (Asiliant), disabled the Intel drivers, loaded drivers for front panel, and PCI / PPC. The power-pc status led blinks "-", and even loaded the IVI drivers. Ive read through this thread like 3 times.. and although i'm usually pretty exhausted when i finally get time to work on this scope, i feel like i can't make any progress on this issue.
Every time I try to install Tek 2.5.5 firmware, I get an "UNSUPPORTED HARDWARE DETECTED" error... has anyone seen similar?
Note: My unit came w/o HDD, caddy, or working cd-rom. Currently, I have a WD Scorpio Blue IDE HDD (NTFS) plugged directly in to the 40-pin IDE cable, Secondary slot. Again, i'm not using the Hard drive caddy - so i've plugged it direct - after removing the little connector converter card.
I found a replacement for the CD-rom (now, a dvd-rw) which i plugged in to the Primary 40-pin IDE cable.
Everything installed fine, and SW loads, PPC blinks "-", and after boot i hear relays clicking on the Acq. board, and fans change speed. But each time I try to install that Firmware software.....
(Thanks in advance!!)
[attachimg=1]
-
Clicking relays and everything you described tells us that the hardware is working and that PC motherboard communicates ok with PowerPC. If you check the console output you will probably see that VXworks loaded.
What I do not understand is how can that happen BEFORE you install the TekScope 2.5.5 firmware??
That firmware is what makes vxboot and other folders to appear on C. You do not copy that manually.
Have you tried following the guide I posted few posts ago?
-
That is an interesting observation.
How does the scope function start without the software installed?
-
@elektropionir
I had copied the vxboot folder on to the drive from a previous installation attempt (which was obtained through opening up ghosted images). I loosely followed your guide. However, it did call me to question my Mobo - Radisys SF810. Would it stand to reason that this was original component in TDS7054? Think there's any harm in loading TiN's bios in to it? i've spent 2 months on this, and i'm ready to trash the scope. if a bios bricks it, whats the loss at this point? ha
I can deal with troubleshooting HW, but SW puts me in a bad mood.
@Johnny10
I had manually copied the vxboot folder on to the C-drive as stated above. When i do that, and the scope clicks as it initializes.. It gives me hope that there's a path to success. So, in the interim, i've renamed the folder to vxboot_old so that it doesn't initialize on boot.
When App SW blocks an installation because it thinks its not a TDS7k scope... its extremely frustrating. starting to worry that i got a custom HW-blend of scope that isn't going to be restored easily / if at all.
If i knew what specific area of HW was flagging the SW and causing the issues, at least i could be rationale in my troubleshooting.
Today i borrowed a Tek HDD caddy from someone and verified that there's no special wiring in the caddy that the installer's checking for. I also moved the HDD and DVD drive back and forth between Primary and Secondary IDE slots... This did not allow the installer to run either, however, the DVD drive did not show up when in Secondary slot.. odd.
So i'm at a loss.. anyone have similar challenges?
-
Reading through those exceptionally long threads can wear you out.
But they do reveal various issues different users have come across.
I have repaired a couple of these scopes and if I remember correctly.
That is not the correct hard drive.
Also TIN and a few others have explained in detail how to connect to the startup software routine.
I wanted to upgrade operating system and memory but I have that very limited BL motherboard.
Yours is the more upgradeable board.
It is not as simple as upgrading your home computer hardware.
BIOS is Tek specific, those PC100 memory sticks are even layout specific.
I cloned the hard drive from one machine to the next and scope started up without a problem.
Only difficulty was changing serial number to get options to work correctly.
But I had same motherboard across units and ordered same vintage hard drive online, wasn't there a GB limit?
-
I installed yesterday on a fresh ssd windows XP on my SF810 mainboard with 512MB RAM and 900 MHz CPU.
It worked like charm with Electropionirs description (thanks!) and the files you find here from other contributors (also thanks) . Did not need to copy any files from the old HD, also the licenses are still there.
The look and feel is much better, much more responsive. The scope application performance itself did not change as expected :-)
2 hints: an external vga screen is required for setup & the native lcd resolution is 640x480.
Best regards,
Kai
Ps: I used an older 32GB SSD, an adapter with 32GB msata ssd got not detected by the bios at all.
-
@xyphro
Great news! Now we know for sure that SF810 motherboard works also. I expected it to work since they are almost identical to SU810.
I also had some issues initially with msata and adapter with a scope until I found a correct position for the jumper. When bios recognized the scope I had no more problems.
There are posts in this topic discussing importance of tektronix specific BIOS firmware for SF/SU810 motherboards. That is not correct. Multiple members (myself included) have stock intel BIOS. Actually I have some unspecified Gateway Desktop bios, that is a version of official P10 intel bios. The scope works, if operating system and drivers work correctly.
Furthermore, bios present in Tektronix/BIOS folder in the units that came originally with SU810 boards is identical P10 bios that was on intel website (before it was removed) and can now be found on other bios databases like rebyte.me.
I just wanted to write this in clear terms because I wasted time thinking that bios is important.
@awjennin
Disk adapter makes absolutely no difference. I did most of the repair work without hdd adapted, plugging the disk directly into the cable because it was easier to remove and connect to my PC to make a backup.
I would not mix files/drivers from TiNs scope since TDS7404 is significantly different than 7104/7054. I cannot assure you that it would work. Keep HDD and CD drive in the positions marked on backside of NLX riser board.
Try to follow the guide, format the drive, install fresh copy of XP and proceed from there. The only thing you need from other scopes are the drivers I described. And nothing else, and certainly not vxboot.
Also check the console output and you can post results here as others have done. Perhaps there is some obvious error shown there. I assume you already got correct header to DB9 adapter.
-
I tried different jumper positions out , did not work. But I have another adapter as the one you have. The same setup is recognized well on my R&S FSEM, which is I guess older as the tds7104. It also got detected by a usb to PATA converter.
Anyway, was happy to have found the older pata ssd.
-
It is not as simple as upgrading your home computer hardware.
BIOS is Tek specific, those PC100 memory sticks are even layout specific.
Dear Johnny10 this is a misconception. I believe that spreads from few very old topics on tek forum.
My unit works perfectly with non tek bios, and I know for a fact that others who replaced BL440 to SU810 have no issues with bios and the scope will work.
It is quite literally as upgrading home PC.
I have 2 sticks of 256MB 133MHz rated ram, from 2 different manufacturers Hyundai and Infineon, and I got those for 1euro on ebay. I ran memtest for 4hours without issues.
The important thing is that the memory is 2 sided, that it has 16 ICs soldered on both sides. Reason why that is important is that the bios for these old motherboards could not address more than 16MB per IC for some reason. I cannot find links now but I discovered articles from about 20 years ago describing this.
@Xyphro
Great, I was also looking for those old SSDs that are native pata, but they are really rare and often expensive. I found some no brand Chinese ones but I would not trust those. I have no basis for the assumption except that there are no data on reliability, and I can get known brand msata for same money...
-
As I said, I have repaired two of these units that I bought broken.
The BL board is different from the board you have. You are correct the memory needs to be double sided.
I bought 4 different types of PC100 and PC133 and only the one worked.
I did shy away from trying to find a SU810 board because of reading about BIOS problems.
Jwalling gave me the best memory tips at the time. Also that changing memory on Power PC board wouldn't speed the scope noticeably.
Have you found that also?
elektropionir you are quite capable.
I went back and read your posts after writing my first post, thought of deleting mine.
awjennin sounded a bit tired of it all and I wanted to say that there is enough information in this thread to fix the 7104 if you keep at it.
Xyphro, thanks for your posts also.
-
Thanks to everyone who posts details on here!! This thread is a treasure trove of information, and i have read through it about 3 times now
@elektropionir
for some reason i missed the dedicated positions for CDROM/HDD on the riser card, which is also indicated in the service manual. My mistake! What I found tonight was odd - If the DVD-RW is installed in the Primary IDE, its recognized just fine. However, if it's plugged in to the correct Secondary slot, its not recognized. In fact, if i manually set it to CD-ROM and save&reboot, it comes up as "none". The HDD shows up and boots just fine in either Primary or Secondary slot... very odd! Also, I noticed that both 40-pin IDE cables that were in my scope are the same part number (174-4231-00). This is called out as the CDROM cable in the service manual. the HDD cable is called out as 174-4321-00 in the manual. However i speculate that this is just different length cable for cable management purposes. a 40-pin ribbon cable is a 40-pin cable, right? (high-speed signal-integrity aside)
When i deemed the original CDROM bad 4 wks ago, i recycled it. Now i'm really kicking myself - as i wish i could test that datapoint. I found another laptop drive (another DVD-RW), and it is not recognized in the Secondary IDE slot either.
@Xyphro - i really appreciate your comments on your install. Its an excellent data point to know that WinXP on an SSD, SF810 mobo, with 512MB is a valid combination. That helps me exclude those variables when troubleshooting. Much thanks!
@Johnny10 - I think i made a mistake early on, starting to read through this forum half way through - and because many people are troubleshooting a scope that is simply not launching Tek app software, i got the idea that the vxboot folder was a prerequisite for installation. However based on your comments and rereading this forum, i understand that the "Tek Firmware 2.5.5" (for my tds7054) includes the scope software, as well as vxboot, and other critical files. Ya, i am getting a little exhausted on this troubleshooting. However, my OCD keeps me coming back each night to continue hammering on it. (that might include a real hammer one of these days - lol)
-
In a display of exhaustion and confusion, i was lying face down on the floor, contemplating many things... then it hit me, i tossed the old CDROM in the recycle - but i hadn't dropped it off at the scrap yard yet... So, I checked and sure enough it was still there. Brushed it off, and installed in to the Secondary IDE location. the bios recognized it!!
Also, I mis-diagnosed the cdrom as a bad drive. It turns out that its just old enough (2002) that it doesn't read CD's that were burned at high speed. The OEM WinXP CD is read just fine, though. These old pc inter-op details are starting to come back to me from my earlier days...
So, I reinstalled XP sp3 again (on 160Gb PATA, NTFS formatted to 146GB), just to get a clean start. Installed the graphics, front panel, pci drivers, and IVI softwares (and also putty, 7zip, and notepad++). PPC board is booting through step L (it attaches to backplane/network, and attaches DIO client... but can't find the vxboot folder (as i haven't installed yet), so it then reboots and tries again. looping.)
Then, I attempted to install firmware from TDS7104_7054_V2.5.5_066031808.EXE, yet I still get a failure.... out of ideas. all I can imagine is that:
1) theres an interface / memory that the installer is polling, but it doesn't ack or the data is wrong, so the installer pukes.
2) The HDD is too big, and i either need to partition it down to 16GB or similar... or simply find an old PATA HDD that's smaller.
I will keep digging..
So my contributions tonight are these:
1) certain DVD drives are recognizable in the Primary IDE, but NOT the Secondary! This includes:
- HL (Hitachi-LG) GMA-4082N-Z DVD-RAM
- Toshiba/Samsung TS-L462 CD-RW/DVD-ROM
2) The original CD-RW that is recognized in Secondary IDE is a TEAC CD-W28E
-
Hello my friends!
I received my "for parts" TDS 7104 item (many brokens parts, damaged MB, damaged (craked) NLX raiser, missing capacitors, BAD BIOS, BAD Acquisition and control boards FLASHs, missing HDD OS..., and even make it boot's for a several time..(there's some problems with SPC procedure.. but not right now..) NOW, After attempt to add some memory (+256Mb DIMM), and after several BIOS resettings.
I can't enter to the BIOS config!!! Even just reflash it from emergency FDD 1'44.
Who can help me with the CMOS corrupt utility??
On the Tek forum, i'll cant reach it.
-
I had this problem a few months ago when my cmos battery died.
It kept me from getting into BIOS and also shutdown the 7104 screen.
I needed to access the VGA connector in back with separate monitor.
You need to install KILLCMOS on floppy MS-DOS start-up disk.
Boot from the floppy and run program.
Takes about 20 seconds.
Took 4 hours to find all equipment to put program on disk :-(
-
The last thing I can think of to get past my "Unsupported Hardware Detected" firmware loading error is to beg/cheat/borrow for a ghosted image - Is anyone capable and willing to help me with that??
SF810 Motherboard, Win2k or WinXP
Mega thank you in advance!
-
I have SU810 not SF, but it could still work since it is almost the same board. It is about 2GB in size, an image clone of the 24GB drive.
I will upload it somewhere, just tell me if you wish to try it.
You can delete the serial number files when you clone it.
If you clone it to a larger drive you can resize partition later.
-
Bingo! now i corrupt my flash and re-install .gho image from xDevs.
to my 440zx motherboard and it works!
Scope shows 4 lines for 4 channels, each channels triggered, and shows adequate (and same) info, from internal calib.generator, and from my arbstudio gen. lasts to 125Mhz..
But trying to load selftest shows me, that all steps is PASS, but Misc (the last) step, has number 511, 2-fail counts errors.
And it fails to pass SPC tests.
My device goes (parts cond), without any HDD and OS. I install and run an (gho) image from another xDevs scope.
And in properties, it shows not mine(back panel), serial and option numbers. Thats because it was reflashing it corrupted configs, and calibratings binaries from the image file from vxBoot (from xDevs)??
Or there is a hardware problem (broken equip IC) ??
And another bug- that, when i try to reinstall the newest scope app version 2.5.3.2008, its hangs application, on tektronix logo from start. It there is any tricks??
and when i try to put 512Mb CF card to PCMCIA slot, it slows the scopes data displays and not appear as disk drive or something.. BUT the "-" on "8"indicator segment, cause blinks an another way periods.
Does the win98 controls that PCMCIA adapter slots? can i add an 4xUSB2.0 PCMCIA adapter or WI-FI or other??
-
I have SU810 not SF, but it could still work since it is almost the same board. It is about 2GB in size, an image clone of the 24GB drive.
I will upload it somewhere, just tell me if you wish to try it.
You can delete the serial number files when you clone it.
If you clone it to a larger drive you can resize partition later.
1000 THANK YOU's to ELEKTROPIONIR - I am absolutely elated, this scope is running!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I restored your disk image to my HDD, and had to reinstall all Tek drivers on first power-up, but when completed I rebooted scope, and it fired right up!!!!!!!
You have provided an end to my 2month obsession - Thank you!!!
-
what i got:
PCMCIA malfunction cause by interrupts.
It can't pass the SPC, because channels, have some DC offsets by mV, from zero.
I delete cal files (on vxBoot) goes with another scope sys image. But it dont help.
I add my bootlog, and SPC log as a txt.
Its physical malfunction of frontend modules or calibration issule??
-
my friends, during the SPC trying I've got "out of SPC thermal zone" which IC makes the thermal sensing??
-
FYI: I've posted an NVRAM + PowerPC BIOS dump script for the TDS6000B/7000B series
https://www.eevblog.com/forum/testgear/tektronix-tds6000b7000b-series-nvram-dump-script/ (https://www.eevblog.com/forum/testgear/tektronix-tds6000b7000b-series-nvram-dump-script/)
At least one person in this thread had a corrupt BIOS and corrupt NVRAMs are only a matter of time.
-
my friends, during the SPC trying I've got "out of SPC thermal zone" which IC makes the thermal sensing??
Hello again, all of my troubles caused by incorrect input module identification. After reinstalling the new firmware from TEK site.
SPC have "pass" stratus. Thanks for everyone!!!
If you need to PCMCIA works- Disable LAN on BIOS...
-
Hi folks,
My TDS7404 died after working great a few months ago. After having it unplugged for a few months, I went to turn it on and found that the x86 side of the machine appears to have a dead graphics adapter. I can't get into the BIOS setup and no amount of CMOS clearing will bring things back. It does appear to be functional enough to run MS-DOS headless, however, which I can verify by typing commands that make things beep (there's no serial console on the motherboard is there?). You can read a bit more in another thread [1].
I haven't been able to find any evidence of anyone bringing their scope back from this symptom, so my question here is: given that the PPC board seems healthy (boots up to "L" on the 8-segment display) and the power supply voltages check out according to the Service Manual, it seems like I should be able to swap out the BL440ZX with a Windows 7 upgrade kit from eBay [2], which includes a SF/SU810 motherboard and hopefully things should spring back to life (also I'll get a much faster (in terms of usability) scope out of it!), since the bad BIOS/Video Adapter lives on the x86 motherboard.
Am I correct in my assumptions? Is there anything else I should try?
[1] https://www.eevblog.com/forum/general-computing/need-help-to-recover-bios-on-intel-bl4400zx-tek-tds-8000-scope/msg3095758/#msg3095758. (https://www.eevblog.com/forum/general-computing/need-help-to-recover-bios-on-intel-bl4400zx-tek-tds-8000-scope/msg3095758/#msg3095758.)
[2] https://www.ebay.com/itm/Windows-7-SSD-Upgrade-Kit-for-Tektronix-TDS7054-7104-7154-7254-7404-CSA7154-7404/184131076942?ssPageName=STRK%3AMEBIDX%3AIT&var=691843642964&_trksid=p2060353.m1438.l2649 (https://www.ebay.com/itm/Windows-7-SSD-Upgrade-Kit-for-Tektronix-TDS7054-7104-7154-7254-7404-CSA7154-7404/184131076942?ssPageName=STRK%3AMEBIDX%3AIT&var=691843642964&_trksid=p2060353.m1438.l2649)
-
Hi folks,
My TDS7404 died after working great a few months ago. After having it unplugged for a few months, I went to turn it on and found that the x86 side of the machine appears to have a dead graphics adapter. I can't get into the BIOS setup and no amount of CMOS clearing will bring things back. It does appear to be functional enough to run MS-DOS headless, however, which I can verify by typing commands that make things beep (there's no serial console on the motherboard is there?). You can read a bit more in another thread [1].
I haven't been able to find any evidence of anyone bringing their scope back from this symptom, so my question here is: given that the PPC board seems healthy (boots up to "L" on the 8-segment display) and the power supply voltages check out according to the Service Manual, it seems like I should be able to swap out the BL440ZX with a Windows 7 upgrade kit from eBay [2], which includes a SF/SU810 motherboard and hopefully things should spring back to life (also I'll get a much faster (in terms of usability) scope out of it!), since the bad BIOS/Video Adapter lives on the x86 motherboard.
Am I correct in my assumptions? Is there anything else I should try?
This will get you up and running with the video set to PCI instead of AGP as it should be, even if the on-board graphics are bad. You will need to change the battery on the CPU board as it is likely dead.
It is a DOS boot floppy with a utility to restore the correct CMOS contents which I just made from a TDS7104 with the BL440ZX MB. When you hear three beeps, press F10 to continue booting. When the floppy access light goes out, the CMOS should be restored. Then press CTRL ALT DEL to warm boot the MB. You should then have the LCD display back.
-
Wow, Jwalling, thank you! That worked and I'm back in action! Not sure what I can do to repay you, but you have my extreme gratitude 🙏
This makes me wonder if the AGP graphics were always dead (at least since I got the unit) and I never noticed because the BIOS was successfully switching off of them to the PCI graphics... until the CMOS battery died. I was a bit puzzled at how sitting quietly, unplugged on a shelf could be so catastrophic for the motherboard and perhaps it wasn't after all.
Also as an FYI for other folks, I successfully used WinImage (the trial) on Windows 10 to write Jwalling's boot disk to a floppy with a USB drive. There was some amount of unplugging and re-plugging in the USB floppy drive to clear contention on it so that WinImage would work properly but it eventually worked.
Now to put humpty dumpty back together again!
-
Wow, Jwalling, thank you! That worked and I'm back in action! Not sure what I can do to repay you, but you have my extreme gratitude 🙏
You're welcome! I'm glad it worked.
-
Hello Jwalling. I have a similar problem with TDS7054 as Awjennin: UNSUPPORTED HARDWARE DETECTED. Please give me a link to the image you provided to Awjennin.[attach=1]
-
hi everyone, really glad to learn from this thread. recently i got a tds7104,boot stop at the scope start screen,I use vxboot to reset and now it boots ok.
but self test ,it reports 521 factory cal integrity ,factory cal data error. I read the boot log,it seems that it can't open some cal file in C:\vxboot\calcon. And i checked in C:\vxboot\calcon, there do missed cal file named 1 to 8 and 15,could this be the cause of error 521? Can anybody share the files ? Or any other suggestion.
I also find to extract the firmeware 2.5.5, you can see the performance verification installation file,which can be installed and run performence test or adjustment automatically if you have a fluke 9500 with four probes.
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
romPost: MPC106 Walking-one passed.
romPost: MPC106 configuration passed.
romPost: First PCI access passed.
romPost: PC87560 Walking-one passed.
romPost: PC87560 configuration passed.
romPost: DEC21554 configuration passed.
romPost: PERFORMING ROM CHECKSUM TEST...
romPost: ROM checksum passed.
romPost: PERFORMING DRAM CELL TEST...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM WALKING-ONE TEST...
romPost: DRAM Walking-one test passed.
romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...
romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: POWER-UP DIAGNOSTIC COMPLETE.
Hel
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.3.0
Creation date: Jun 28 2000, 16:52:12
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : c:/vxboot/vxworks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.169.0.2
user (u) : anonymous
ftp password (pw) : anonymous
flags (f) : 0x1008
target name (tn) : target
startup script (s) : c:/vxboot/topscript.hw
other (o) : nvfs=0x1000
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network PC1 dio device driver installed
interface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxworks.st...1773516
Starting at 0x200000...
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topscript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23662208 = 0x1690e80
ld < TekScopeSM.o
value = 23661568 = 0x1690c00
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x16927c0: value = 23668704 = 0x16927e0 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1690a40: value = 23661216 = 0x1690aa0 = pDBfs + 0x60
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x1697660 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - n
o programming needed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
0x1697660 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x1697660 (tShell): (Re)starting Acq Processor
value = 23688240 = 0x1697430
excHookAdd(stopStressForException)
value = 17557980 = 0x10be9dc = stopStressForException
dsyInit
value = 21806728 = 0x14cbe88
dsyWPApplyNextRegs
value = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x1697660 (tShell): >> Kernel version 1.0.8.1 does not match Boot ROM version 1
.0.3.0
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4e943
TmgrInit("/db")
0x1697660 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x1697660 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
value = 0 = 0x0
PhxProxyInit
value = 20819360 = 0x13dada0
rtlInit
value = 0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
hwAccount_init
0x1697660 (tShell): >> Setting PLL to 1.25e+09 Hz.
sysEnetAddrGet: d5:7b:95:df:75:53
value = 7 = 0x7
GpibInit
value = 133284512 = 0x7f1c2a0
wfmMemInit(1)
value = 47300320 = 0x2d1bee0
vertInstall
value = 47293284 = 0x2d1a364
calConStatus = cc_init(2)
0x1697660 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x
2d1a240
0x1697660 (tShell): nvMem_read succeeded
0x1697660 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0
x2d1a300
0x1697660 (tShell): nvMem_read succeeded
0x1697660 (tShell): extd chksum failed, stored = 0xffffffff calc = 0x28d5a0ee
0x1697660 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
0x1697660 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x1697660 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x1697660 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x1697660 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x1697660 (tShell): cc_restoreBank: can't open file calConStatusC:/vxBoot/calCon
s/ = 2
0x16976600x (tShell): cc_init: bank 1341eec2 chksum failed, NOT reset to factory
: v0xalue = 1697660 (tShell164335): cc_restoreBank: can't open file = 0xC:/vxBo
ot/calCons/281ef3
0x1697660
(tShell): cc_init: bank
3 chksum failed, NOT reset to factory
updateT0xrigCal1697660 (tShell
): cc_restoreBank: can't open file vC:/vxBoot/calCons/al5ue =
0x1697660 (tShell0): cc_init: bank = 0x5 chksum failed, NOT reset to factory
00x1697660 (tShell
): cc_restoreBank: can't open file
C:/vxBoot/calCons/ 6 MathMeasCreateThe
MathandMeasurementL0xibraries1697660 (tShell
): cc_init: bank value = 6 chksum failed, NOT reset to factory
471207040x1697660 = 0x (tShell): 2cf0140cc_restoreBank: can't open file
C:/vxBoot/calCons/7 initAcqMapper
0x
1697660 (tShell): cc_init: bank value 7= chksum failed, NOT reset to factory
0x01697660 (tShell): = 0xcc_restoreBank: can't open file 0C:/vxBoot/calCons/
8
0x trigMapInit1697660
(tShell): cc_init: bank value = 8 chksum failed, NOT reset to factory
00x1697660 = 0x (tShell): 0cc_restoreBank: can't open file
C:/vxBoot/calCons/ ds15yMapInit
0x1697660 (
tShell): cc_init: bank value = 15 chksum failed, NOT reset to factory
00x1697660 = 0x (tShell): cc_chkLimits: 0CC_VERT_ATTENIMBAL_100X_CH2
was ; reset to factory
mathMapper0xInit1697660 (tShell
): cc_chkLimits: CC_VERT_ATTENIMBAL_1X_CH2value = was is0; reset to factory
= 0x0x1697660 (tShell0): initAcqMapper: Enter
utilMapInit
value = 47118048 = 0x2cef6e0
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 20164752 = 0x133b090 = AcqMapperRtlDataList
MathMeasMapHookup
value = 23688072 = 0x1697388
dsyMapHookup
value = 23688176 = 0x16973f0
utilMapHookup
value = 23688208 = 0x1697410
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 23688168 = 0x16973e8
fastFrameMapHookup
value = 23688192 = 0x1697400
trigMapHookup
value = 23688200 = 0x1697408
vertMapHookup
value = 23688192 = 0x1697400
spcMapHookup
value = 23688192 = 0x1697400
autosetMapHookup
value = 23688232 = 0x1697428
timeSyncMapHookup
value = 23688224 = 0x1697420
auxTrigMapHookup
value = 23688208 = 0x1697410
dpoMapHookup
value = 23688200 = 0x1697408
TmgrStartup
value = 46252048 = 0x2c1c010
PhxProxyStartup
value = 46201504 = 0x2c0faa0
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 46040768 = 0x2be86c0
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 45502752 = 0x2b65120
enablePowerupDiags = 0
enablePowerupDiags = 0x1311330: value = 0 = 0x0
runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
0x2bc59a0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2bc59a0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2bc59a0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
value = 17780784 = 0x10f5030 = SoftSwitchesRegisterTable + 0x48
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
################### topScript ends ###############################
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
-
hi everyone, really glad to learn from this thread. recently i got a tds7104,boot stop at the scope start screen,I use vxboot to reset and now it boots ok.
but self test ,it reports 521 factory cal integrity ,factory cal data error. I read the boot log,it seems that it can't open some cal file in C:\vxboot\calcon. And i checked in C:\vxboot\calcon, there do missed cal file named 1 to 8 and 15,could this be the cause of error 521? Can anybody share the files ? Or any other suggestion.
Error 521 is the EEPROM on the acquisition board has been corrupted. It's reference designation is U1052.
Here is a known good U1052 binary from a TDS7104. Obviously it won't have the correct constants for your scope, but it will get rid of the error.
Otherwise you'll need to have a proper calibration with adjustments done.
-
It’s really great of you! Maybe I can compare your file with mine to see what’s the difference except calconstans ，I wonder how could this happen unless someone had done adjustment not completely.
-
Does anyone know if there is a way to trash the contents on the Dallas DS1245 chip on the PPC board?
This one has a PDIP, and I'd rather not remove the chip if it can be done from the console port.
I'm replacing this board in a TDS7104 and I need to get rid of the serial # and key.
-
Hi All,
I have a TDS7104 that I just rebuilt the disk on. Everything seems to work fine except I can't do a successful SPC. I get a fail message on the display. I have attached a terminal to the PPC console port. I get slightly different errors each time I run SPC, but all look bad.
I have tried calConStatus = cc_init(1), which seems to execute okay.
I have checked the power supply voltages, and all are good.
So, is my acquisition board toast?
Thanks much
[attach=1][attach=2]
-
It’s hard to find a new x24165 now,I used a AT24C16B instead， I will try this in a few days.Thanks.
-
It’s hard to find a new x24165 now,I used a AT24C16B instead， I will try this in a few days.Thanks.
Maybe AT24C16B is not a right choose,I will try to find a right chip again.
-
A 24C16 will work fine.
-
A 24C16 will work fine.
Thanks，the error 521 disappeared now，I have made some simple test and the test results seems to be acceptable
-
A 24C16 will work fine.
Thanks，the error 521 disappeared now，I have made some simple test and the test results seems to be acceptable
You're welcome, that's great! Does it meet it's BW spec?
-
A 24C16 will work fine.
Thanks，the error 521 disappeared now，I have made some simple test and the test results seems to be acceptable
You're welcome, that's great! Does it meet it's BW spec?
I dont have a 1GHz sinewave signal, but I believe the BW spec will no be a big issue, instead, maybe the dc voltage error is more obviously.
And now I find another problem ,each time I shutdown and then restart the scope, the scope goback to default status(before I shutdown it,I open 4 channel display,and after reboot,only CH1 is displayed. And each time after it restart, ch2 baseline offset is quite big,I have to run spc eachtime to make it right.
Seems each time I restart the scope,it loads the factory default. I attach my bootfile here, does anyone know what's the reason?
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
romPost: MPC106 Walking-one passed.
romPost: MPC106 configuration passed.
romPost: First PCI access passed.
romPost: PC87560 Walking-one passed.
romPost: PC87560 configuration passed.
romPost: DEC21554 configuration passed.
romPost: PERFORMING ROM CHECKSUM TEST...
romPost: ROM checksum passed.
romPost: PERFORMING DRAM CELL TEST...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM WALKING-ONE TEST...
romPost: DRAM Walking-one test passed.
romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...
romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: POWER-UP DIAGNOSTIC COMPLETE.
Hel
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.3.0
Creation date: Jun 28 2000, 16:52:12
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.0:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.168.0.2
user (u) : anonymous
ftp password (pw) : anonymous
flags (f) : 0x1000
target name (tn) : target
startup script (s) : c:\vxBoot\topScript.hw
other (o) : nvfs=0x1000
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network PC1 dio device driver installed
interface lo0... done.
Attaching DIO client... done.
Loading c:\vxBoot\vxWorks.st...1773516
Starting at 0x200000...
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]] Can
not regis
ter service: RPC: U nable to send; errn]]]]] ] ]]]] ]]]]] ]]]]]]]]
]]]] ]] ]]]] ]]]]]]] ]]]] o =
13
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]una
ble to register
(WINDVIEW, WINDVIEW _VERS_CURRENT, udp)]]]]]]] ]]]]] ] ]]]]]] ] ]]]
]]]] ]] ]]]] ]]]] ]]]] ]]]].
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:\vxBoot\topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23737024 = 0x16a32c0
ld < TekScopeSM.o
value = 23705952 = 0x169b960
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x169bc00: value = 23706656 = 0x169bc20 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x169b7e0: value = 23706400 = 0x169bb20 = pDBfs + 0x340
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 23705408 = 0x169b740
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 17639480 = 0x10d2838 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x155fde0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - n
o programming needed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
0x155fde0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x155fde0 (tShell): (Re)starting Acq Processor
value = 22412208 = 0x155fbb0
excHookAdd(stopStressForException)
value = 17426908 = 0x109e9dc = stopStressForException
dsyInit
value = 21784264 = 0x14c66c8
dsyWPApplyNextRegs
value = 17629356 = 0x10d00ac = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x155fde0 (tShell): >> Kernel version 1.0.8.1 does not match Boot ROM version 1
.0.3.0
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba45503
TmgrInit("/db")
0x155fde0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x155fde0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
value = 0 = 0x0
PhxProxyInit
value = 21018368 = 0x140b700
rtlInit
value = 0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
hwAccount_init
0x155fde0 (tShell): >> Setting PLL to 1.25e+09 Hz.
sysEnetAddrGet: d5:7f:95:df:75:53
value = 7 = 0x7
GpibInit
value = 133284512 = 0x7f1c2a0
wfmMemInit(1)
value = 47300320 = 0x2d1bee0
vertInstall
value = 47293284 = 0x2d1a364
calConStatus = cc_init(2)
0x155fde0 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x
2d1a240
0x155fde0 (tShell): nvMem_read succeeded
0x155fde0 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0
x2d1a300
0x155fde0 (tShell): nvMem_read succeeded
0x155fde0 (tShell): extd chksum failed, stored = 0xffffffff calc = 0x28d5a0ee
0x155fde0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x155fde0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x155fde0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/2
0x155fde0 (tShellcalConStatus): cc_init: bank = 2 chksum failed, NOT reset to f
actory
0x0x155fde01321eec (tShell): cc_restoreBank: can't open file : value C:/vxBoot/c
alCons/= 3164335
0x155fde0 (tShell = 0x): cc_init: bank 281ef3 chksum failed, NOT reset to factor
y
0x155fde0 (
tShell): cc_restoreBank: can't open file updateTrigCaC:/vxBoot/calCons/l5
0x155fde0 (tShell): value = cc_init: bank 05 chksum failed, NOT reset to factory
= 0x0x155fde0 (tShell0): cc_restoreBank: can't open file
C:/vxBoot/calCons/6
0x155fde0 (tShell): MathMeasCreatcc_init: bank eTheMa6thandMeasurementLib ch
ksum failed, NOT reset to factory
rar0xies155fde0 (tShell):
cc_restoreBank: can't open file valuC:/vxBoot/calCons/e 7=
0x155fde0 (tShell47120704): cc_init: bank = 0x7 chksum failed, NOT reset to fac
tory
2cf01400x155fde0
(tShell): cc_restoreBank: can't open file initAcqC:/vxBoot/calCons/Ma8pper
0x155fde0 (tShell
): cc_init: bank value = 8 chksum failed, NOT reset to factory
00x155fde0 (tShell = 0x): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
15
0x155fde0 (tShell trigMapInit):
cc_init: bank 15 chksum failed, NOT reset to factory
val0xue = 155fde0 (tShell0): cc_chkLimits: CC_VERT_ATTENIMBAL_100X_CH2 = 0x was
; reset to factory
00x155fde0
(tShell): cc_chkLimits: dsyMCC_VERT_ATTENIMBAL_1X_CH2apInit was ; reset to
factory
0x155fde0value = (tShell0): initAcqMapper: Enter
= 0x0
mathMapperInit
value = 0 = 0x0
utilMapInit
value = 47118048 = 0x2cef6e0
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 20033680 = 0x131b090 = AcqMapperRtlDataList
MathMeasMapHookup
value = 22412040 = 0x155fb08
dsyMapHookup
value = 22412144 = 0x155fb70
utilMapHookup
value = 22412176 = 0x155fb90
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 22412136 = 0x155fb68
fastFrameMapHookup
value = 22412160 = 0x155fb80
trigMapHookup
value = 22412168 = 0x155fb88
vertMapHookup
value = 22412160 = 0x155fb80
spcMapHookup
value = 22412160 = 0x155fb80
autosetMapHookup
value = 22412200 = 0x155fba8
timeSyncMapHookup
value = 22412192 = 0x155fba0
auxTrigMapHookup
value = 22412176 = 0x155fb90
dpoMapHookup
value = 22412168 = 0x155fb88
TmgrStartup
value = 46269840 = 0x2c20590
PhxProxyStartup
value = 46219296 = 0x2c14020
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 45990560 = 0x2bdc2a0
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 45502752 = 0x2b65120
enablePowerupDiags = 0
enablePowerupDiags = 0x12f1330: value = 0 = 0x0
runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
value = 17649712 = 0x10d5030 = SoftSwitchesRegisterTable + 0x48
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
################### topScript ends ###############################
Done executing startup script c:\vxBoot\topScript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
-
And now I find another problem ,each time I shutdown and then restart the scope, the scope goback to default status(before I shutdown it,I open 4 channel display,and after reboot,only CH1 is displayed. And each time after it restart, ch2 baseline offset is quite big,I have to run spc eachtime to make it right.
Run a self test when this happens, but do not run SPC. Does it get an error 531?
-
And now I find another problem ,each time I shutdown and then restart the scope, the scope goback to default status(before I shutdown it,I open 4 channel display,and after reboot,only CH1 is displayed. And each time after it restart, ch2 baseline offset is quite big,I have to run spc eachtime to make it right.
Run a self test when this happens, but do not run SPC. Does it get an error 531?
Thanks for your reply. I run self test ，the results are all pass even I don’t run spc。 Also sometimes when I start the scope ，it may stop at adding 6008 .
-
Thanks for your reply. I run self test ，the results are all pass even I don’t run spc。 Also sometimes when I start the scope ，it may stop at adding 6008 .
Do you know the state of the battery on the PPC board?
-
Thanks for your reply. I run self test ，the results are all pass even I don’t run spc。 Also sometimes when I start the scope ，it may stop at adding 6008 .
Do you know the state of the battery on the PPC board?
Do you mean the battery for NVRAM ，DS9034PC，I checked the old one ,voltage is about 2.98V，and then I bought a new ds9034pcx(new ds9034pc is hard to find, the pcx is with crystal ，I checked this new pcx，voltage is about 3.4V) now I use the new ds9034pcx in my scope. Not sure whether the voltage is right.Maybe I have to buy another battery to give it a try
-
2.98V should be fine. Are you sure it's making contact?
I ask because if it's not, it may not be apparent. On later serial #s, even if the battery is flat, the boot parameters get set correctly, presumably from the BIOS on the PPC board. I am working on a TDS7104 with serial prefix B052XXX which I had to erase the PDIP dallas chip because the serial # did not match the rear sticker. After erasing it, the scope booted fine, and pulled the serial # from the disk.
-
Hello i also jump into this topic because i bought myself a TDS7404 too. the unit has win98 installed and has an trigger 463 error in the diagnostics from what i could see.
While waiting on the unit to arrive. does maybe anybody know what this problem could be. the Manual point me to optionST but there doesn t ring a bell already
i will add a compilation picture to clear my question. why is there a second option sticker on top of the earlier (original) sticker. upgraded by tek or??
-
This is more than likely a failed trigger chip, it is a known problem on the TDS7154, TDS7254 & I think the TDS7404, where the trigger chips cook themselves over time. The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.
-
This is more than likely a failed trigger chip, it is a known problem on the TDS7154, TDS7254 & I think the TDS7404, where the trigger chips cook themselves over time. The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.
The trigger ICs are there for edge trigger only. If they fail, you should still be able to trigger on logic levels which is handled by a different mechanism.
The parts are unfortunately impossible to get. That's why I bought a broken acquisition board to have a spare, when the next one blows on my CSA7404...
-
Hello thanks for your reply. KrudyZ do you also think it is the chip, like Wolfy007 says?
mmmm then i took the wrong guess i suppose..
but isn t it that the ACQ board test also fails with a failling trigger chip? i mean to say i would expect more errors then just the 463 which is pointing to optionST.
I saw the post in this topic from Wolfy007 post #445 with 3 errors uncluded the ACQ board then i would suspect the Tektronix 156827800 chips. but also now?
btw the unit also gives an in-operatable error because calibration is not valid
-
The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.
7054&7104 ?? or vs 7154....7404??? I think that triggers on 7054...7104 is same?
-
i did some extra research. from what i found it is related to the option added by the option key on the back. So i have some hope the unit is lost in its options.
Somebody on the forum here well known with these options: OptionST Serial Mask Testing and Option Serial Pattern for special communication purpose.
Or maybe have seen this option on other scopes? more info about these trigger option added in the attachments
-
The TDS7054 and TDS7104 used different chips and dont appear to be affected by trigger failures as far as I can tell.
7054&7104 ?? or vs 7154....7404??? I think that triggers on 7054...7104 is same?
Yes, thats right, the TDS7054/TDS7104 are different to the TDS7254&TDS7404.
-
What if i wanted to backup my Nvram content so i have a backup. what is the most simpel way to do so. or can the content easily be rebuilded after replacing the NVram or BR1632 Battery.
-
[attach=2]Hi Jay, you have replaced the NVram in the 7000 series many time i assume. my question is i have see the current drawing thing from TiN his CSA7404.
but is that on all models from 7000 series or just his model? is it a miss development thing? if yes what can i do about it?
Is buidling in a better battery 3v - 1000mA a good option. to drill a hole in the powercap so it comes truth the powercap cover?
or was this problem only with TiN his unit?
greetz charly
[editted: and so i did]
-
Hi Jay, you have replaced the NVram in the 7000 series many time i assume. my question is i have see the current drawing thing from TiN his CSA7404.
but is that on all models from 7000 series or just his model? is it a miss development thing? if yes what can i do about it?
Is buidling in a better battery 3v - 1000mA a good option. to drill a hole in the powercap so it comes truth the powercap cover?
or was this problem only with TiN his unit?
greetz charly
Not 100% sure I understand the question, but I have observed them drawing more current than they should/as from a new device as well.
-
Hi Kris, ok so if i understand well the current drawing is high in all the 7000 series because of how there are developped.
And how long do they last again,............after i replaced the NVram chip as well as the battery with new onces? an other 20years or so..
maybe a strange question because in previous scope it worked like this. but i read this threat over en over en have seen more then one scope fail after a short period of not used.
So if i can expect a not booting unit anymore after being powered of for 6 month. i will not be really happy and try to avoid this by changing the SRAM part of the setup by what i saw an Alliance - AS6C1008-55TIN chip and feeded by a 3v - 1000mA battery and not the original 120mA
-
My memory may be a bit rust and i'm not sure we're taling 100% about the same thing but... The NVRAM in these devices is battery backed up and unlike with other NVRAMS, the battery is actually accesible if you pop the hood (many other are potted). So you can replace the battery if you wish, which is a cheaper and easier approach. *But* it seems some of these NVRAM devices draw way too much current, draining the replacement battery pretty fast. As far as I know, this had nothing to do with the Tektronix but rather with the NVRAM itself.
-
I can confirm that about the NVRAM current draw. On my 7104 I replaced the NVRAM battery with one 5 times bigger but it ran out in a day or two. Only when I found a replacement of the chip did my scope start working again.
-
Hi yes for sure. I go for swapping them both. that is my plan..
But i have an other important question. the weak spot are the Trigger chips [tektronix 156827800]
i read and see a lot about them inside the models TDS/CSA7254 & TDS/CSA7404 and these chips seem to die easily and concern me because i wanted to renew my equiptment with this unit on my bench so it has to be reliable for a longer period
What can be done, so they will not die? can a heatsink give them a long life?
Or better question: what is a possible course for them to burn-out? Is this input related, just heat, not enough airflow or..?
[EDIT] After a closer inspection my unit also has one chip hit. So, anyone having one of these TDS694C or TDS6/7000 acquisition boards lying around or for sale, for free, bad or good? or trigger chip for sale [tektronix 156827800] please PM
-
today i tried to debug my boot process.
What i saw was:
- when i don t connect the breakout cable to J790 connected to a win98 hyperterm pc. the scope boots-up ok and also starts tekscope software complete ending in diagnose screen with the Trigger error 463.
- when i put in the com-port breakout cable the boot stop at "L" on the 7 seg display and tek scope only start and doesn t pass the logoscream ( sort of freeze ) .
when power on the debug info starts scrolling and ends at
-------------------below i pasted small versions from the end before boot procedure stops------
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: POWER-UP DIAGNOSTIC COMPLETE.
Hel
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 7
------------------------------------------------------------
next time it ends like this
-------------------------------------------------------------
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: POWER-UP DIAGNOSTIC COMPLETE.
Hel
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - P "£$$%^%£$Y&**I()(
----------------------------------------------------------------------
and i will add the option screenshot. and diagnostic screen. where i see corruption too.
who can answer this for me? -> i saw here in the topic in post #454 written: the factory service CAL data part is stored in NVRAM of PPC board.
if that is the case how can i export that factory service CAL data part out of the NVRAM of PPC board and what if not?
i didn t see any writing before #454 about this factory cal issue.
-
Swapping the NVram (piggybag) battery:
First i want to swap out the battery ( and check the voltage level on it) to see if a new battery that helps in booting with a console port connected.
I save myself more time to export the content.
I hope Flyte reads this for his tool ;-) i am willing to help export specific info ( adresses ). so please PM me.
-
On Saturday, the CMOS battery died on my second 7104.
It blanked the TDS7104 screen and kept me from getting into BIOS.
Battery was dated 1995.
Replaced battery.
Access the VGA connector in back with separate monitor.
You need to install KILLCMOS application on floppy MS-DOS start-up disk.
I used a 2SHD 1.44MB High Density floppy on a XP OS machine.
When formatting disk there is a check for create MS-DOS disk.
Online I downloaded a KILLCMOS program. (https://www.majorgeeks.com/files/details/killcmos.html (https://www.majorgeeks.com/files/details/killcmos.html))
Extracted file and installed on floppy.
Boot from the floppy type dir in the command line.
Find and and run KILLCMOS .
CTRL Alt Delete
F2 Setup
Your BIOS is now accessible.
Change config of BIOS to default settings.
Change Display to PCI
Save and restart oscilloscope.
-
Hi Johnny10 thanks for the info, but my NVram did not yet die. i want to keep the content so i am working on a way to keep it powered. when replacing the Piggybag battery.
Question: i am curious to people who did feed the DS9034P with additional 5 volt to keep it powered and meanwhile pull the powercap with battery and replace it.
@Johnny10 what motherboard are you talking about? the SF810 or the SU810.
i have them both and for sure they behave total different and bios settings are different too. where SF810 has monitor of voltages and SU810 has not.
Question: if i do a DB clear by taking away the # in the topScript.hw and boot is the complete content gone so my factory service call also.?
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
-
This method works on the motherboard CMOS battery failure only.
My motherboard is BL440ZX running Win98 OS.
-
Looking at all the content inside this post, it would be helpful for some to also look at my new post about a TDS7404:
https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/msg3374538/#msg3374538 (https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/msg3374538/#msg3374538)
After a lot of script problem, i'm back to having a booting TDS7404 without the correct S/N |O
-
today i feeded my NVram with external +4.6v on pin5 and pin 17 to GND.
then i lifted the powercap and took out the old battery.
drilled two holes at the right place in the powercap cover and attached a CR2477 socket. i had to reverse it so it would fit next to the NLX bus connector on the Powerpc baord and after swapping the wiring arround, clicked it back in place on the NVram.
the battery socket en powercap cover look ed as if it is one pieces and the total reworked cap fits ok under the aluminium Intel board frame.
reconnected everything and ready to power-up...
ok ready for booting for the first time.
will the scope fully startup??
-windows xp booted fine.
-tekscope software started and ran to the end ( the 8 digit display nicely showed the flashing "-" )
-my error was gone
-my options were empty. (was this because of the corruption)
i am still curious how to check if the fact. service call. info is still in.
-
Does anyone know if there is a way to trash the contents on the Dallas DS1245 chip on the PPC board?
This one has a PDIP, and I'd rather not remove the chip if it can be done from the console port.
I'm replacing this board in a TDS7104 and I need to get rid of the serial # and key.
Yes you can, just copy a empty file inside the NVRAM space.
-
Does anyone know if there is a way to trash the contents on the Dallas DS1245 chip on the PPC board?
This one has a PDIP, and I'd rather not remove the chip if it can be done from the console port.
I'm replacing this board in a TDS7104 and I need to get rid of the serial # and key.
Yes you can, just copy a empty file inside the NVRAM space.
How is that done?
-
Does anyone know if there is a way to trash the contents on the Dallas DS1245 chip on the PPC board?
This one has a PDIP, and I'd rather not remove the chip if it can be done from the console port.
I'm replacing this board in a TDS7104 and I need to get rid of the serial # and key.
Yes you can, just copy a empty file inside the NVRAM space.
How is that done?
I have made some scripts that make this possible. best to look at my repair post, scripts are available over there.
https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/msg3415738/ (https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/msg3415738/)
-
A 24C16 will work fine.
Thanks，the error 521 disappeared now，I have made some simple test and the test results seems to be acceptable
You're welcome, that's great! Does it meet it's BW spec?
I dont have a 1GHz sinewave signal, but I believe the BW spec will no be a big issue, instead, maybe the dc voltage error is more obviously.
And now I find another problem ,each time I shutdown and then restart the scope, the scope goback to default status(before I shutdown it,I open 4 channel display,and after reboot,only CH1 is displayed. And each time after it restart, ch2 baseline offset is quite big,I have to run spc eachtime to make it right.
Seems each time I restart the scope,it loads the factory default. I attach my bootfile here, does anyone know what's the reason?
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
romPost: MPC106 Walking-one passed.
romPost: MPC106 configuration passed.
romPost: First PCI access passed.
romPost: PC87560 Walking-one passed.
romPost: PC87560 configuration passed.
romPost: DEC21554 configuration passed.
romPost: PERFORMING ROM CHECKSUM TEST...
romPost: ROM checksum passed.
romPost: PERFORMING DRAM CELL TEST...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: DRAM Cell test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...
romPost: Enabling data cache...
romPost: Data cache enabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: Writing address to each *address...
romPost: Reading address from each *address...
romPost: DRAM march test passed...
romPost: PERFORMING DRAM WALKING-ONE TEST...
romPost: DRAM Walking-one test passed.
romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...
romPost: NV-MEMORY Walking-one test passed.
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
romPost: Enabling instruction cache...
romPost: Instruction cache enabled.
romPost: POWER-UP DIAGNOSTIC COMPLETE.
Hel
VxWorks System Boot
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.3.0
Creation date: Jun 28 2000, 16:52:12
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.0:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.168.0.2
user (u) : anonymous
ftp password (pw) : anonymous
flags (f) : 0x1000
target name (tn) : target
startup script (s) : c:\vxBoot\topScript.hw
other (o) : nvfs=0x1000
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network PC1 dio device driver installed
interface lo0... done.
Attaching DIO client... done.
Loading c:\vxBoot\vxWorks.st...1773516
Starting at 0x200000...
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]] Can
not regis
ter service: RPC: U nable to send; errn]]]]] ] ]]]] ]]]]] ]]]]]]]]
]]]] ]] ]]]] ]]]]]]] ]]]] o =
13
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]una
ble to register
(WINDVIEW, WINDVIEW _VERS_CURRENT, udp)]]]]]]] ]]]]] ] ]]]]]] ] ]]]
]]]] ]] ]]]] ]]]] ]]]] ]]]].
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:\vxBoot\topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23737024 = 0x16a32c0
ld < TekScopeSM.o
value = 23705952 = 0x169b960
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x169bc00: value = 23706656 = 0x169bc20 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x169b7e0: value = 23706400 = 0x169bb20 = pDBfs + 0x340
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 23705408 = 0x169b740
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 17639480 = 0x10d2838 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x155fde0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - n
o programming needed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
0x155fde0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x155fde0 (tShell): (Re)starting Acq Processor
value = 22412208 = 0x155fbb0
excHookAdd(stopStressForException)
value = 17426908 = 0x109e9dc = stopStressForException
dsyInit
value = 21784264 = 0x14c66c8
dsyWPApplyNextRegs
value = 17629356 = 0x10d00ac = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x155fde0 (tShell): >> Kernel version 1.0.8.1 does not match Boot ROM version 1
.0.3.0
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba45503
TmgrInit("/db")
0x155fde0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x155fde0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
value = 0 = 0x0
PhxProxyInit
value = 21018368 = 0x140b700
rtlInit
value = 0 = 0x0
sysExtMemAddToPool memSysPartId,0x02000000,0x06000000
value = 0 = 0x0
hwAccount_init
0x155fde0 (tShell): >> Setting PLL to 1.25e+09 Hz.
sysEnetAddrGet: d5:7f:95:df:75:53
value = 7 = 0x7
GpibInit
value = 133284512 = 0x7f1c2a0
wfmMemInit(1)
value = 47300320 = 0x2d1bee0
vertInstall
value = 47293284 = 0x2d1a364
calConStatus = cc_init(2)
0x155fde0 (tShell): Reading 280 bytes of service cal data from EEPROM[0] into 0x
2d1a240
0x155fde0 (tShell): nvMem_read succeeded
0x155fde0 (tShell): Reading 66 bytes of service cal data from EEPROM[280] into 0
x2d1a300
0x155fde0 (tShell): nvMem_read succeeded
0x155fde0 (tShell): extd chksum failed, stored = 0xffffffff calc = 0x28d5a0ee
0x155fde0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x155fde0 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/1
0x155fde0 (tShell): cc_init: bank 1 chksum failed, NOT reset to factory
0x155fde0 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/2
0x155fde0 (tShellcalConStatus): cc_init: bank = 2 chksum failed, NOT reset to f
actory
0x0x155fde01321eec (tShell): cc_restoreBank: can't open file : value C:/vxBoot/c
alCons/= 3164335
0x155fde0 (tShell = 0x): cc_init: bank 281ef3 chksum failed, NOT reset to factor
y
0x155fde0 (
tShell): cc_restoreBank: can't open file updateTrigCaC:/vxBoot/calCons/l5
0x155fde0 (tShell): value = cc_init: bank 05 chksum failed, NOT reset to factory
= 0x0x155fde0 (tShell0): cc_restoreBank: can't open file
C:/vxBoot/calCons/6
0x155fde0 (tShell): MathMeasCreatcc_init: bank eTheMa6thandMeasurementLib ch
ksum failed, NOT reset to factory
rar0xies155fde0 (tShell):
cc_restoreBank: can't open file valuC:/vxBoot/calCons/e 7=
0x155fde0 (tShell47120704): cc_init: bank = 0x7 chksum failed, NOT reset to fac
tory
2cf01400x155fde0
(tShell): cc_restoreBank: can't open file initAcqC:/vxBoot/calCons/Ma8pper
0x155fde0 (tShell
): cc_init: bank value = 8 chksum failed, NOT reset to factory
00x155fde0 (tShell = 0x): cc_restoreBank: can't open file 0C:/vxBoot/calCons/
15
0x155fde0 (tShell trigMapInit):
cc_init: bank 15 chksum failed, NOT reset to factory
val0xue = 155fde0 (tShell0): cc_chkLimits: CC_VERT_ATTENIMBAL_100X_CH2 = 0x was
; reset to factory
00x155fde0
(tShell): cc_chkLimits: dsyMCC_VERT_ATTENIMBAL_1X_CH2apInit was ; reset to
factory
0x155fde0value = (tShell0): initAcqMapper: Enter
= 0x0
mathMapperInit
value = 0 = 0x0
utilMapInit
value = 47118048 = 0x2cef6e0
TmgrHookup
value = 0 = 0x0
PhxProxyHookup
value = 0 = 0x0
hookupAcqMapper
value = 20033680 = 0x131b090 = AcqMapperRtlDataList
MathMeasMapHookup
value = 22412040 = 0x155fb08
dsyMapHookup
value = 22412144 = 0x155fb70
utilMapHookup
value = 22412176 = 0x155fb90
rtlHookup
value = 0 = 0x0
horizMapHookup
value = 22412136 = 0x155fb68
fastFrameMapHookup
value = 22412160 = 0x155fb80
trigMapHookup
value = 22412168 = 0x155fb88
vertMapHookup
value = 22412160 = 0x155fb80
spcMapHookup
value = 22412160 = 0x155fb80
autosetMapHookup
value = 22412200 = 0x155fba8
timeSyncMapHookup
value = 22412192 = 0x155fba0
auxTrigMapHookup
value = 22412176 = 0x155fb90
dpoMapHookup
value = 22412168 = 0x155fb88
TmgrStartup
value = 46269840 = 0x2c20590
PhxProxyStartup
value = 46219296 = 0x2c14020
taskDelay(2)
value = 0 = 0x0
gpibHwInitC
value = 0 = 0x0
gpibTaskSpawn
value = 45990560 = 0x2bdc2a0
gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"
value = 45502752 = 0x2b65120
enablePowerupDiags = 0
enablePowerupDiags = 0x12f1330: value = 0 = 0x0
runPowerupDiags
done
dipSwitch = 0x0, enablePowerupDiags = 0, puMode=0
CalDiagPowerUpDiagsEnabled = 0
!! SKIPPING POWERUP DIAGNOSTICS !!
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
0x2b188e0 (digHFTask): >> Setting PLL to 1.25e+09 Hz.
value = 17649712 = 0x10d5030 = SoftSwitchesRegisterTable + 0x48
rtlStartup
value = 0 = 0x0
tsComp
value = 0 = 0x0
################### topScript ends ###############################
Done executing startup script c:\vxBoot\topScript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
Hello. My TDS 7104 presents the same 521 error. I bought some used X24165 chips, and try to replace it.
My English is terrible. Hope you can understand me. :-DD
-
Hi i would be carefull with pulling these eeproms. Inside are your factory cals stored and your scope needs tobe re-calibrated for sure. nowadays no FAS is available anymore and equiptment like a fluke 9500B needs to be part of your workbench or you will get yourself into an extra problems. $$$
is the rest of your scope ok bohrzqc . post log here.
-
Hi i would carefull with pulling these eeproms. Inside are your factory cals stored and your scope needs tobe re-calibrated for sure. nowadays no FAS is available anymore and equiptment like a fluke 9500B needs to be part of your workbench or you will get yourself into an extra problems. $$$
is the rest of your scope ok bohrzqc . post log here.
After replaced the X24165 chip, the 521 error still exists. I wonder whether only replacing the X24165 chip is OK or some cal data should be written to the chip. Jay upload the cal data of his 7104. So the cal data should be written to the chip?
I bought some AT24C16B chips, and plan to replace tomorrow.
Maybe I solved the baseline offset is reset to the factory default. First delete the calConStatus = cc_init(2) in the boot file, save the file. Restart the scope. Add the calConStatus = cc_init(2) to the original place again, and save the file, restart the scope.
However, this method is useless for another 7104. Maybe this due to the X24165 chip. Not sure. :palm:
-
After replaced the X24165 chip, the 521 error still exists. I wonder whether only replacing the X24165 chip is OK or some cal data should be written to the chip. Jay upload the cal data of his 7104. So the cal data should be written to the chip?
Yes. If you use my cal data, the error should go away, but won't be valid for obvious reasons.
-
Hi bohrzqc: is this what you did? and what did it bring you?
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg2764508/#msg2764508 (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg2764508/#msg2764508)
-
Hi bohrzqc: is this what you did? and what did it bring you?
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg2764508/#msg2764508 (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg2764508/#msg2764508)
No.
calConStatus = cc_init(1) cannot settle the problem of the offset of the baseline, only can reset the cal data to factory values. I think resetting the factory cal values is useless. My method is not always effective. Maybe we should wait for expert Jay or TiN to settle the problem.
-
hi yes that is why i asked, because what did you do exactly in post #607 i am trying to figure out why you did those things.
-
Hi, thank you a lot for this forum.
I recently got a tds7154 from someone who find it.
I had to change the bios battery, find an hdd, install windows 2000 and the drivers.
Now, Tekscope launch but I can't see any trace, so I tried with windows XP and got the same problem. It takes measurement (we can see the range adapt with the input while clicking on autoset) but the trace are not displayed.
Have anyone an idea of what it could be?
:)
-
Hi, thank you a lot for this forum.
I recently got a tds7154 from someone who find it.
I had to change the bios battery, find an hdd, install windows 2000 and the drivers.
Now, Tekscope launch but I can't see any trace, so I tried with windows XP and got the same problem. It takes measurement (we can see the range adapt with the input while clicking on autoset) but the trace are not displayed.
Have anyone an idea of what it could be?
:)
Looks like the video driver. Make sure it is an Asiliant driver.
-
@ludow, don t run the unit opened without a big fan blowing over the ACQ and or PSU. Normally with case closed the airflow is directed over the boards. with open case board run too hot.
-
yes thanks that was exactly this :-+
-
yes thanks that was exactly this :-+
The driver, you mean?
-
yes exactly, thank you :)
-
Does anyone know the right adress for the eeprom asumming it is this X24165 (written in earlier post here) also for the TDS7404 ?
Just nice to know, where is it exactly located on the ACQ board?
I'd rather not (yet) remove the chip if it can be done from the console port or GPIB after after builing a tool for it to export and import content.
I want to get closer to the error where all onces as the checksum of 0xffffffff are stored. that is not ok.
extd chksum failed, stored = 0xffffffff calc = 0xdb766060
0x16975c0 (tShell): cc_init: extended bank17 chksum failed, NOT reset to factory
Jay do you know the starting adress?
-
Jay do you know the starting adress?
I do not.
-
Hi Guys!
After long time I wanted to use my (several times successfullz repaired) TDS7104 again.
However, trouble happened:
I turned it on and the internal LCD stayed white, the Frontpanel all lit, but it still seemed to boot properly. After some time of waiting, the relays clicked and I could operate with the frontpanel the probe, e.g. pressing the 1MOhm/50Ohm button actuated the relay, I could turn on/off channels, ...
[attach=1]
Of course I attached an external screen to the PC VGA port). When powering on there was no signal detected, after windows booted, the screen detected a 640x400 pixel sync signal, but the screen keeps blank (tested the screen, it works and I used the same for installing windows XP before).
I thought it was a smart idea to remove the PC CMOS Bios battery (on the SF810 mainboard). However, since that point the PC scope application does not start anymore. The 7 segment display shows a blinking "-" sign and the frontpanel does not react anymore.
Having had issues with the power supply before I of course checked the power supply and all voltage rails show proper voltages.
Does anybody have a clue what I can look for?
Without VGA signal I am really clueless how I can access that guy to check a few things.
Best regards,
Kai
Edit: Tried to boot from CD. It boots, but still no display content :(
-
Uodate: now the scope application boots again and frontpanel is reactive, still internal and external screens are dead.
Dors anybody know how to clear cmos? I removed the battery already for 1h with no external power applied, but that does not seem to help.
-
I left the TDS7104 unpowered and without CMOS battery over night.
Result: The PC board does not boot at all anymore, also the push power button on the frontpanel does not power the scope on anymore. When I bridge the power on jumper, it turns on, als the CPU fan rotates, probing some caps on the PC board shows nice expected voltages.
All power supplies are present, also standby voltage.
I am very close to say: I am done with the scope, looking how often I already repaird stuff.
Anybody close to Germany wants a nice neverending hobby project? :-)
Edit: The Debug console of PPC seems dead, when I power on with the power_on jumper. The 7 segment led shows an 8 permanently.
-
Probed several signals on the NLX riser card.
PWOK (input to NLX) is signalling, that power is OK
#FPReset is high, so the NLX board is not kept permanently in RESET
Voltages are all present
The SOFT_ON/OFF# signal is correctly going low, when the frontpanel power pushbutton is pressed
PS_ON# output from NLX goes correctly LOW
I guess, I need a new NLX board :-(
-
On Saturday, the CMOS battery died on my second 7104.
It blanked the TDS7104 screen and kept me from getting into BIOS.
Battery was dated 1995.
Replaced battery.
Access the VGA connector in back with separate monitor.
You need to install KILLCMOS application on floppy MS-DOS start-up disk.
I used a 2SHD 1.44MB High Density floppy on a XP OS machine.
When formatting disk there is a check for create MS-DOS disk.
Online I downloaded a KILLCMOS program. (https://www.majorgeeks.com/files/details/killcmos.html (https://www.majorgeeks.com/files/details/killcmos.html))
Extracted file and installed on floppy.
Boot from the floppy type dir in the command line.
Find and and run KILLCMOS .
CTRL Alt Delete
F2 Setup
Your BIOS is now accessible.
Change config of BIOS to default settings.
Change Display to PCI
Save and restart oscilloscope.
-
Lets hope I get there again, that it tries to boot from floppy disc. Right now I think the SF810 board is broken.
Anybidy has a NLX board for sale?
-
Hi why not pull out the X86 board and feed it with external PSU. of course check the coin battery for 3v. but i assume you already did.
connect a VGA monitor to the onboard svga.
and see what happens.
-
That is feasible, but not easy as there is no AT or ATX supply connector. I have the riser pinout. Honestly, before soldering 30 cables for a test, I wait now for a new board to arrive from Israel. If this is not going to help, I will likely sell it.
As the signals and voltages towards the board are ok and it is not trying to boot, I expect the mainboard to be broken.
-
hi i would just pull the board out of the scope and connect by soldering at the end (printside)of the riser connector [NOT THE COPPER CONTACTS FOR SURE] the 4 voltages, +5/-5/+12/-12 wires from an old atx psu. and if the board is really dead there is not much to loose. checked caps already
-
Hi!
I need to run killcmos headless. I can out it in autostart.bat to do so. But: do I need to press any button? If so, which ones?
Best regards,
Kai
Edit:
I managed to run. Killcmos does not need any keypresses, it also resets the oc afzer execution. Bios was correctly shoeing that cmos data is corrupt.
Still my pc board boots only every now and then. I esit for replacement board.
The ppc works fine, just if the PC does not boot and show a vga signal, it is also not capable to load from harddisk its image. Story thus continues... :-(
-
There is an eBay seller that has provided a kit to upgrade the TDS 7000 series.
You could contact him about the many options.
I found this a couple of years back as I repaired my two TDS7104s.
I wonder just how much of a difference faster CPU makes to oscilloscope?
Imagine boot-up would be faster but scope? I don't know.
https://www.ebay.com/itm/184796108047?hash=item2b06b4d50f:g:LQEAAOSwyytdYzXq (https://www.ebay.com/itm/184796108047?hash=item2b06b4d50f:g:LQEAAOSwyytdYzXq)
-
I Have a TDS7104 Which the application just hangs in the splash screen. If I understood the problem correctly I need to pull of the plastic cap from the Dallas "chip" and replace the battery underneath. My Problem is, that I can't seem to get the plastic cap off and I don't want to damage anything. What the trick to getting it of?
After replacing the battery, I understand tthat I will have to reset the NVRAM. What's the easiest way to do that?
The second problem the scope has that during boot the built in screen shows that the screen has been recognized andI should configure it under Windows. After boot, it is set up as the secondary screen with the VGA output being the primary even with no screen attached. There also doesn't seem to be a way to configure the built in screen as primary. Is this problem related to something else or do I need to repair another thing for that to work again?
-
Read through the thread.
The screen going over to VGA is from dead BIOS battery.
-
I already replaced the BIOS battery. This unfortunately didn't change anything. I read through the first fifty or 100 posts and all I found is that I nee to pull of the plastic cap but not how without damaging anything.
I just thought that maybe somebody with more experience could give me quick summary or point me towards the right posts since this thread has more than 600 posts.
-
You have to reset BIOS chip by using KILLCMOS program.
-
On Saturday, the CMOS battery died on my second 7104.
It blanked the TDS7104 screen and kept me from getting into BIOS.
Battery was dated 1995.
Replaced battery.
Access the VGA connector in back with separate monitor.
You need to install KILLCMOS application on floppy MS-DOS start-up disk.
I used a 2SHD 1.44MB High Density floppy on a XP OS machine.
When formatting disk there is a check for create MS-DOS disk.
Online I downloaded a KILLCMOS program. (https://www.majorgeeks.com/files/details/killcmos.html (https://www.majorgeeks.com/files/details/killcmos.html))
Extracted file and installed on floppy.
Boot from the floppy type dir in the command line.
Find and and run KILLCMOS .
CTRL Alt Delete
F2 Setup
Your BIOS is now accessible.
Change config of BIOS to default settings.
Change Display to PCI
Save and restart oscilloscope.
-
My tds7104 had a different dallas nvram: DS1245Y-120.
If you wonder where to find the battery contacts... They are burried much deeper into the molding as for other dallas NVRAMs.
See attached photo for location help in case you want to put a new battery in :-)
-
Sorry, the + and - labels are swapped!
-
I do have the one from the first post but I still do not seem to be able to figure out how to remove the plastic cover without uncomfortable amounts of force.
-
The answer to my question about how to get the cap off can actually be found in this data sheet - who would have thought :palm: : https://datasheets.maximintegrated.com/en/ds/DS9034PC.pdf (https://datasheets.maximintegrated.com/en/ds/DS9034PC.pdf) : Stick a screwdriver into the slot of the cover and lever it to the opposite side (away from the large brown connector).
I'm going to do a write-up on the whole battery replacement process as soon as I get the new battery delivered.
-
I seems to be 1 step away from having a working scope again: After setting the settings to what another TDS7104 owner reported I get these error messages on the serial console. Does anbody know, how to fix this or at least what the exact problem is here?
The both errors I see are:
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
and
can't open input 'TDS7000.o'
errno = 0x1c0001 (S_symLib_SYMBOL_NOT_FOUND)
Press any key to stop auto-boot... 1 0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topScript.hw
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 c:/vxboot/vxWorks.st...1773344
Starting at 0x200000...
Host Name: bootHost
User: target
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 6003 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.0.
WDB: Ready.
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topScript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TDS7000.o
can't open input 'TDS7000.o'
errno = 0x1c0001 (S_symLib_SYMBOL_NOT_FOUND)
Done executing startup script c:/vxboot/topScript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
->
-
I've gotten rid of the first error (tcsTableUnpack: checksum failed on buffer; tcsTableLoadFromNVRAM: tcsTableUnpack failed) by uncommenting NvramClearDb = 1 for one boot und commenting it again afterwards.
The other error
can't open input 'TDS7000.o'
errno = 0x1c0001 (S_symLib_SYMBOL_NOT_FOUND)
is still there. What's strange is that the file TDS7000.o i right there in the C:\vxBoot folder.
-
Update: After adding a new battery to the Dallas IC I have put a small 3d printed casing arround it - looks clearner as my previous hot glue massacre.
I also created 3d models for the Tektronix knobs. You can find them attached. I am yet not sure if I like my colour concept, but they nicely fit.
I printed them at 0.14mm layer hight, 1mm wall thickness with 97% scaling, no support. Depending on the accuracies of your printer you might need a different model scaling factor. Try out first e.g. 3 different scaling factors and chose the one that gives you the best snap-fit.
-
.................
I also created 3d models for the Tektronix knobs. You can find them attached. I am yet not sure if I like my colour concept, but they nicely fit.
I printed them at 0.14mm layer hight, 1mm wall thickness with 97% scaling, no support. Depending on the accuracies of your printer you might need a different model scaling factor. Try out first e.g. 3 different scaling factors and chose the one that gives you the best snap-fit.
Nice, you need post about those here too:
https://www.eevblog.com/forum/testgear/replacement-knobs-feet-and-fittings-for-test-equipment/ (https://www.eevblog.com/forum/testgear/replacement-knobs-feet-and-fittings-for-test-equipment/)
-
Hello, friends!
I need your help.
I purchased an inexpensive TDS7054 oscilloscope on Ebay.
The oscilloscope loads Windows, but does not load Tektronix software.
At first I thought that the problem was a faulty Dallas battery, but when I opened it, it turned out that the battery is working (> 3v).
Then I paid attention to the fact that I do not have a VxBoot folder on my hard drive and there are no drivers for 2 devices in the device manager.
Most likely, the previous owner of this oscilloscope replaced the hard drive and copied the data from the old one, but for some reason did not copy VxBoot and it is possible that the drivers also failed.
Can you please tell me what is better for me to do next?
If someone can please share the files from the hard drive or a copy of the Tek installation disc.
Thanks in advance for your help
-
I reinstalled my tds7104 2 times from scratch. You need to install the scope software from the tek site. It brings the file with it as part of install. I can also zip you mine in case you are stuck. If you look for adventures also a fully working hd image.
-
In case your power button flatband cable broke (those type of cables are made for max 5 bending cycles) - here a cheap replacement.
Order it as 0.6mm PCB and cut the PCB with a scisor, put a normal flatband cable in between, solder 2 leds on it: And done!
The original cable is offered for 350 US$ right now on ebay - flex pcb remakes for about 50 US$ and this one just costs < 5 US$ and does the job as good as the others.
-
hello anybody have an idea why this error is pointing to....
i got it after installing a different ghost image, which was initially taken from this scope in a working situation, the image worked well before.
the TDS7404 has a new nvram for about 1/2 year ago.
see screenshot
The PPC Board is booting after switch on from ".8" and count normaly up to "-".
Windows boots perfectly, but the 'scope application hangs at the splash screen.
nvram corruption??
[editted: YES it was. See post #649]
looking into the logs from earlier exports this is what it shoud be: but why out of the blue stuck here?? My .sn .key files are in the vxboot in place
TmgrInit("/db")
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
value = 0 = 0x0
PhxProxyInit
value = 20819072 = 0x13dac80
rtlInit
value = 0 = 0x0
-
I had lots of errors in the log. Even after putting an image of the original delivered HD I had the still issues and already was about to dump the scope.
Unbelieveable, but with a complete reinstallation of winxp and all tools it got back to working state.
-
today i replace my 6 month old nvram for the Fram board [see attachment 1:]
and yes it works again. see post #647 i have 2 last issues still.
1) No SN & KEY.
2) SPC fail.
both worked after i replacement the old nvram with a new nvram, but as told that nvram died again after 6 month that NVRAM i fitted an Alliance chip on but one way or an other no luck.
can the SPC fail issue be generated because of sn & key not installed.
cleardb =1. didn 't work yet.
today a day after...i worked out that not filling in some bootsetting can make the difference: stop with "C" and walkthrough step by step try to delete hostname (host) and username ( target) fill in both areas the "." and <enter>
in the end use "@" to continue booting and "P" to show...
but there is an other thing i discovered i see in my bootlog the lines NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK... are missing.
one line is for the key en one line for the serial i assume
can anybody explain why they are not shown?
[see attachment 2:] the leftside log: the log with NVRAM installed before it died and the rightside log: you see the FRAM bootlog
why are the two lines not entered while booting?
[editted:] that the lines are gone is only a sign that the fram-board is working as it suppose to. when those two lines popup means the SN and KEY stored in the NVram are not in reach or not stored correct ;-)
so next step is: how to force the unit from re-initializing as in first boot after replacment. ( not clearDB )
[EDITTED: for the SN needs the cal-switch in the back of the PPC board tobe switched to unprotect then the serial is written from the .SN file to the NVram in the next boot]
-
the problem is fixed with all FF FF FF to the fram or nvram, that way i forced the nvram or eq. into a re-init of the scope
But the most important info i can tell for sure now is that. if your nvram content is not what it should be. also combined with no .sn and .key the SPC will fail....keep that in mind.
next to fix is the
TCA-1MEG and P7260 and P7380
[editted: opened a new topic for this one]
-
i have installed WINXP on a 7404 and playing around i discovered that when i add options ST and SM which give you a lot more trigger options i do not get the bottom options added like in the picture.
can this be because of WINXP installed and the software is just WIN2000 compatible.
i am wandering if somebody with WINXP installed on his 7404 culd do a test. and add a options key like 08 44 XX XX XX XX XX XX XX XX ... [where the 08 stand for 4M ) and the double 4 like "44" stand for both ST(4 on the left) and SM ( 4 on the right).
it is easy to do create a key ( i can help you if you don t know how it works) add the extra options in your scope reboot at least 1 time and see if these option appear.
i added pictures from a working enviroment but are they also added on a WINXP installed scope?
how can i do this quick test on this WINXP installed 7404 scope? and see if they appear and disappear when changing the "00" -> "44" -> "00" in the key
-
Hi!
I have a TDS7404 where the front LCD remains completely white when booted (it worked fine a few months ago, but after sitting for a while and trying it now it doesn't show anything anymore). It does still seem to boot successfully though, and I get a display output over the PPC VGA port.
On the NLX VGA port, I also just get a white display output.
I can boot into Windows 2000 fine when I enable VGA mode in the F8 menu.
Also, I've taken it apart and notice on the 7-segment display that the PPC board boots fine too (blinking "-" symbol).
I've read that in the BIOS you need to enable PCI video output, but that option does not seem to exist in my BIOS.
Any pointers as to what I can try? I have a floppy drive and some disk on order too.
Thanks!
-
@DebboR what does your debug console output say? please post your log here.
-
To all of you who have been so dedicated to keeping this topic going:
I only recently found this by tripping over it in another search I was doing for work stuff, and joined in the fun. My eyes are now falling out of my head, but the information available here seems to be more thorough that anything Tek ever published - so great job. I own a 5054B-NV-AV, and honestly it does most everything I require of it, and it's been a solid scope for some time now, however having read so many bad stories about it I thought I may be better off at least getting a clone of the HDD before it dies.
That led down a trail of frustrations - no matter what I tried I could not get it to boot from either USB or 'DVD' Rom drive - and I have a fair amount of experience with older PC gear! So here's the skinny on what I've found that I hope helps somebody along their path:
1) The Mobo's in these older units are from a time when PC hardware was changing very rapidly, so they can and will be stubborn about things, and booting is no stranger in this department.
2) There may be several mildly different variants of the same general design, so don't assume yours will behave the same as another's.
3) Booting from CD Filesystems (and USB for that matter) will be fraught with issues, especially if it's a borrowed version or a roll-your-own version.
(Intel even published the fact that there was a pathway to problems in this area..)
4) Persistence will pay off. In my case I discovered that the 'DVD Rom' drive was very particular about what type of disk was used - only the oldest ones I still had on hand would work - and they were dated back to 2005-ish.
5) Pay attention to the boot process - the only discs I was able to boot had EFI boot sectors, some of the linux hybrids will probably boot, but not all - and it's likely you'd be hard pressed to get anything newer than 2010 to boot in OEM hardware.
6) You can boot these into a live linux setting which opens up a lot of possibilities. (see pic)
I have a nice MDO super-duper scope in the lab at work, but my favorite and the one that stays on my bench (mostly because it's too heavy to walk away with) is the DPO7104.
It is old and cranky (not too unlike myself) and that's fine - perhaps someday I'll buy it at auction - if I ever decide to carry it down the hall.
Thank you to all of you - and keep up the good work!
PS.. the image attached below is for your viewing pleasure - the TDS5054B running crunchbang linux (which was what finally allowed me to image that hard disk).
-
Tried swapping the NLX board, no fix.
After this, I took apart the display assembly and re-seated the connectors, which fixed the issue! Definitely worth a try if somebody is experiencing similar issues.
No clue why this happened, the scope was sitting on my desk and hadn't been touched since the last time I powered it off fine.
@charlyd The PPC board booted fine (from the 7-seg display), so I didn't grab any logs, but thanks for the help!
-
I somehow can't seem to figure out how to generate a proper option key.
I did a fresh install of the scope with Windows XP. I just installed the Scope software und the required drivers. I did not copy any sn or key files from the old installation. It seemed to configure every thing correctly on its own.
The serial number (B031754) on the back of the scope matches with that in the about menu and the 2M option, that came with the scope was recognized automatically. Here, the option key on the back matches the one in the about menu as well.
I tried generating a key for the 3M option key like this:python gen.py tds7104 B031754 04
I get this:PF9D3-M6GHM-JTF8F-5
which obviously is not a proper option key. If I enter it into the option installation masks of the scopes software it also tell me that.
Could somebody maybe tell what exactly the parameters of the key generator program have to be? What exactly is the option mask supposed to be?
As a sanity check: If I enter the currently installed option key that came with the scope into the validate function, it shows me the correct serial number.
-
I somehow can't seem to figure out how to generate a proper option key.
I did a fresh install of the scope with Windows XP. I just installed the Scope software und the required drivers. I did not copy any sn or key files from the old installation. It seemed to configure every thing correctly on its own.
The serial number (B031754) on the back of the scope matches with that in the about menu and the 2M option, that came with the scope was recognized automatically. Here, the option key on the back matches the one in the about menu as well.
I tried generating a key for the 3M option key like this:Code: [Select] (https://www.eevblog.com/forum/javascript:void(0);)python gen.py tds7104 B031754 04
I get this:Code: [Select] (https://www.eevblog.com/forum/javascript:void(0);)PF9D3-M6GHM-JTF8F-5
which obviously is not a proper option key. If I enter it into the option installation masks of the scopes software it also tell me that.
Could somebody maybe tell what exactly the parameters of the key generator program have to be? What exactly is the option mask supposed to be?
As a sanity check: If I enter the currently installed option key that came with the scope into the validate function, it shows me the correct serial number.
I was able to answer my own question:
The option mask has to have a fixed length. That means that the trailing digits have to filled with zeros. If you just wanted the 3M option, the corresponding option mask would be:040000000000000000000000000000000000I fiddled around with the masks given in the program but didn't know how to enable exactly the options I wanted. This is why I ended up with this mask:
04FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
This seems to enable all possible software option and 3M. If all you see are the memory depth and SM options and apart from that only "App XX Avail: not installed" you have to install the appropriate software packages
from the Tektronix website and reboot the scope. After that the options will show up.
Nevertheless, there will still be a lot of options that are marked as "not installed" since they don't exist for the scope. If anybody knows how to do this properly, any information would be very welcome.
-
hi when you are looking for the options ST and SM here they are: (later i saw i already type it above |O)
00 44 00 00 00 0..................
ST is the left "4" and SM is the right "4".
where in your long string:
first 04 = 2M and 08 = 4M (max for non b-versions)
hope this helps for you ;-)
-
yesterday i opened a new topic on getting the content of a Eeprom from the TDS7404.
Who can help me out with an export his TDS7404 Eeprom location U1052
there are many boards with broken trigger chips circulating arround , i guess those content should be ok too. who wants to upload a TDS7404 ACQ CAL MEM U1052 - X28165
to help others always export your Eeprom before running the following command.
because as far as i see it was emptied and drops error 521 in the diagnostics after i ran the CalConStatus = cc_init(1)
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> calConStatus = cc_init(1)
0x16301e0 (tShell): cc_init: extended bank4 reset to factory
0x16301e0 (tShell): Storing 300 bytes of service cal data from 0x15fb200 into EEPROM[0].
0x16301e0 (tShell): EEPROM service cal data verified.
0x16301e0 (tShell): cc_init: extended bank17 reset to factory
0x16301e0 (tShell): Storing 82 bytes of service cal data from 0x1601160 into EEPROM[300].
0x16301e0 (tShell): EEPROM service cal data verified.
0x16301e0 (tShell): cc_init: bank 0 reset to factory
0x16301e0 (tShell): cc_init: bank 1 reset to factory
0x16301e0 (tShell): cc_init: bank 2 reset to factory
0x16301e0 (tShell): cc_init: bank 3 reset to factory
0x16301e0 (tShell): cc_init: bank 5 reset to factory
0x16301e0 (tShell): cc_init: bank 6 reset to factory
0x16301e0 (tShell): cc_init: bank 7 reset to factory
0x16301e0 (tShell): cc_init: bank 8 reset to factory
0x16301e0 (tShell): cc_init: bank 9 reset to factory
0x16301e0 (tShell): cc_init: bank 10 reset to factory
0x16301e0 (tShell): cc_init: bank 11 reset to factory
0x16301e0 (tShell): cc_init: bank 12 reset to factory
0x16301e0 (tShell): cc_init: bank 13 reset to factory
0x16301e0 (tShell): cc_init: bank 14 reset to factory
0x16301e0 (tShell): cc_init: bank 15 reset to factory
0x16301e0 (tShell): cc_init: bank calConSt16atus reset to factory
= 0x16301e0 (tShell0x): Optical hardware is not present.
1335528: value = 262143 = 0x3ffff
->
-
When i use
0444FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFI still only get SM although ST should also be available for TDS7104 scopes according to the manual... strange.
The maximum memory depth for the 7104 model (and maybe the 7054) is 3M (mask 04...). That's also what my scope now reports after upgrading the options.
-
I put together a github repo with the the most important stuff to get the scope going with Windows 2000/XP and a stand-alone version of the python script to unlock the options:
https://github.com/exit-failure/tds7000 (https://github.com/exit-failure/tds7000)
I still have to update and clarify a couple of things. If you have anything that you think I should add, please let me know.
-
Thank you all so, so much for all your help here !
A friend of mine gave me a TDS7054 that my school was about to throw away. Dead HDD. I need a full reinstallation and I'm using Exit_failure's work to activate it.
I'll let you know if everything looks cool, gonna try an IDE-to-SD-Card adapter and install a fresh Win 2000 SP4 on it.
Seems like the python standalone app worked fine, I just had to manually change the directories but it generated a key I'll try later.
Fingers crossed I'll be able to make the whole thing boot on the new SD card again.
-
Quote from: RPuccio on 06-02-2022, 18:44:19 (https://www.eevblog.com/forum/index.php?topic=20744.msg3990326#msg3990326)
Thank you all so, so much for all your help here !
A friend of mine gave me a TDS7054 that my school was about to throw away. Dead HDD. I need a full reinstallation and I'm using Exit_failure's work to activate it.
I'll let you know if everything looks cool, gonna try an IDE-to-SD-Card adapter and install a fresh Win 2000 SP4 on it.
Seems like the python standalone app worked fine, I just had to manually change the directories but it generated a key I'll try later.
Fingers crossed I'll be able to make the whole thing boot on the new SD card again.
Great I could help. Let me if you have any questions.Also maybe think about replacing the two button cell batteries. One might be a little bit tricky to replace since it is inside of a module. I the scope has been broken for some time and has not been powered during that time, given the age of the scope. They might go bad soon if they're not already. I solved the problem by removing the old battery soldering some wires to the contact and glueing a standard CR2032 holder on top of the POWER CAP module. You can find information on how to do most of that in the first post of this thread.
-
Oh, I've only replaced one at the moment. The main issue here is find a way to boot the scope's PC !
F2 does not enter the bios setup, and I have basically no hard drive for that scope. The internal 7-segment display shows all the normal procedure and locks up on "L", indicating the PC is waiting for something to boot on.
I don't have a floppy drive, nor do I have an image file of the original drive or anything that could help. My computers at home are too recent and Win 2000 does not want to install on a new drive from those. I'm trying different methods and they all seem to fail, including going through the ethernet LAN port, which gives me a nice TRAP 00000006 EXCEPTION error - too bad !
I'm thinking about flashing an original img on a new SATA drive and using an IDE to SATA adapter... Doing my best, but I'm not knowledgeable enough (yet) to repair that beast alone !
-
Since there has been a PM request to publish my NVRAM-replacement board design, and I don't plan to make a business of this, I attached the whole project to this message.
The project has been designed on Target3001! ECAD which isn't that common but it's with what I started and stayed... ;) I guess the evaluation version may suffice to modify the project, this may be necessary to replace the voltage regulator since it's somewhat awkward to source currently. Modification is not necessary if you just want to reproduce my design -- an archive with the required gerber files is inlcuded.
Whatsoever, I wish you best of success repairing your "TEK Boxes", and I'ld be happy if I could contribute a little bit with this project... ;D
-
Quick update !
Using PXE boot I've been able to run FreeDOS and do a KILLCMOS to finally change the boot order of the scope : CD drive, then IDE-HDD, then Floppy.
Now, when booting on my img file of Windows 2000, the screen shows "Starting Windows", with the loading bar going fully up, and nothing more ? Internal 7-segment still displays "L" and I can't boot into safe mode either.
The system does not boot into the CD drive either, even though I placed a Windows 2000 install disk in it - weird ?
I also need to upgrade the poor 128MB of RAM the PC has. If I can find a way to put up to 512MB, I might be able to run a windows install from PXE without the TRAP 00000006 EXCEPTION error message.
Any tips would be appreciated, or even better, a working img file I could burn to my IDE HDD ;D
-
At last, I finally got windows 2000 setup not to crash and it installed correctly ! Now the Tektronix software shows an error message when booting up, I think I need to install all the required drivers and check the communication with the powerPC
-
Update : I've been able to install windows 2000 with much trouble (it was installing as "D:\" instead of "C:\"). Now that it is fixed, I've installed the drivers, and the PCI2PCI driver crashes the computer. I need to delete DIOSERVICES.exe, as well as the three other .sys files to make Windows work again. And obviously, that driver is the one doing all the communication work between the PowerPC and the main board. I'm a bit stuck here, is my TDS impossible to repair ? Any tips ? Thanks a lot :'( |O
-
AT LAST, it is working again, thanks to TiN and my friend ! TiN had a ghost image of a Win98 TDS7104 and sent it to me. My friend converted it on a VM into a .img file which I will upload very soon.
It seems to be perfectly compatible with my TDS7054, and the software instantly recognized the serial number and option key corresponding to my scope - NVRAM is good for now I guess.
I've installed an SD Card in place of the dead HDD, and it works fine. I've been able to activate 3M and SM options on the scope, but not much more. Maybe I am not using the keygen correctly ?
This is what I use :
Model : TDS7054
Serial number : B010118
Option mask : 04FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Output key : XKNAJ-2EU3E-84836-Y2UBZ-8UEMS-WVR4W-FC2YB-98SEM-SWVB which seems wrong ?
The option mask might be in cause here, as the 3M and SM options were activated using option mask 04FFFF
The scope works perfectly, but if I can get a few more options out of it, it would be even better ! Thanks for your help :)
-
AT LAST, it is working again, thanks to TiN and my friend ! TiN had a ghost image of a Win98 TDS7104 and sent it to me. My friend converted it on a VM into a .img file which I will upload very soon.
It seems to be perfectly compatible with my TDS7054, and the software instantly recognized the serial number and option key corresponding to my scope - NVRAM is good for now I guess.
I've installed an SD Card in place of the dead HDD, and it works fine. I've been able to activate 3M and SM options on the scope, but not much more. Maybe I am not using the keygen correctly ?
This is what I use :
Model : TDS7054
Serial number : B010118
Option mask : 04FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Output key : XKNAJ-2EU3E-84836-Y2UBZ-8UEMS-WVR4W-FC2YB-98SEM-SWVB which seems wrong ?
The option mask might be in cause here, as the 3M and SM options were activated using option mask 04FFFF
The scope works perfectly, but if I can get a few more options out of it, it would be even better ! Thanks for your help :)
I getXKNAJ-2EU3E-84836-Y2UBZ-8UEMS-WVR4W-FC2YB-98SEM-SWVBas well.
The last block does not necessarily have to contain 5 characters. Just try it :-)
Maybe take a picture of the original option key if anything goes wrong and you have to restore it.
-
Thanks a lot Exit_Failure.
Let me be doomed ! I already put it once but obviously made a mistake while typing, I've being more careful this time and it works :scared: :-DD
It even shows "App 51 avail : not installed" and so on for all the app ID possible. Mission succeeded !
I've also calibrated it and it passed all the self-test. Victory !
Here is a mega link for TiN's win98 image, tested and working on his TDS7104 and my TDS7054 : https://mega.nz/file/8oZk3DxA#lVMpnDMNth2c7z9f2eEgmPmujBiUAqkjlEqnBJkNOtA
For those wanting to replace the original HDD, here is how to do it.
- First, be sure that the TDS computer has a working BIOS. In my case, the 7-segment display was going up to "L" and stopped there.
- Buy a replacement IDE HDD, or anything else that could work. In my case, I use a 16GB SD Card and an SD Card to IDE adapter, it fits in the little HDD drawer without much trouble.
- Download the win98 .img file to a working computer
- Use a software like WinImage or Balena Etcher to burn the image to the replacement drive. You can open .img file with WinImage, it will work, that's what I did.
- Eject the replacement drive from your modern computer and plug it into the scope.
- It should work right away, just wait for it to tell you "wait for your TDS7000 series scope to boot into windows"
- You'll certainly be asked a password to enter the network. It is not mandatory, just use the touchscreen and click on "okay". Windows does not have your keyboard or mouse drivers yet, so you'll have to have a working touchscreen before. I could redo the image if needed, just shoot me a PM.
If the computer fails to boot into windows right away, you can try to use the KILLCMOS program to force it to enter the setup. You are not forced to use floppy disks, even though that's way easier. In my case, I used Serva to establish a LAN connection with the computer, FreeDOS 1.2 to boot into a command line and the KILLCMOS program to reset the BIOS parameters.
Hopefully this might help other people :)
-
Hello ;),
I have been following the conversation on the eevblog forum for several days https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/650/ (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/650/) and I saw that you provide an image under an environment W98. Thank you for this picture.
I would like to know if you managed to migrate your TDS7054 to W2000 and if all the applications work. I'm interested because a few people tell me that the timing issues on my TDS7254 could be caused by software issues. Indeed I am convinced that my TDS7254 was the subject of an incomplete reinstallation before its purchase.
If the W2000 environment works on your TDS7054 and without abusing your kindness, would it be possible to obtain an image of the W2000 environment with the installation procedure that you performed during this migration.
I hope that the translation by g..le will be correct.
-
Hello ;) ,
I have been following the conversation on the eevblog forum for several days https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/650/ (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/650/) and I saw that you provide an image under an environment W98. Thank you for this picture.
I would like to know if you managed to migrate your TDS7054 to W2000 and if all the applications work. I'm interested because a few people tell me that the timing issues on my TDS7254 could be caused by software issues. Indeed I am convinced that my TDS7254 was the subject of an incomplete reinstallation before its purchase.
If the W2000 environment works on your TDS7054 and without abusing your kindness, would it be possible to obtain an image of the W2000 environment with the installation procedure that you performed during this migration.
I hope that the translation by g..le will be correct.
I can only talk about my TDS7104 but I managed to get I working with Windows 98SE, Windows 2000 and Windows XP. I can pull an Image of the Win XP installation in a couple of days if you want me to.
-
I've just updated the github repo (https://github.com/exit-failure/tds7000 (https://github.com/exit-failure/tds7000)) with an extensive section about replacing the NVRAM backup battery and restoring the necessary settings:
https://github.com/exit-failure/tds7000/blob/main/NVRAM/README.md (https://github.com/exit-failure/tds7000/blob/main/NVRAM/README.md)
-
Hello exit_failure,
I just looked at your gitbhub repository and it's very good work. My TDS7254 works with some problems in "trigger EDGE" synchronization mode. On the other hand, when I use the “ADVANCED trigger” mode, it works very well. What I would like to do is make a backup of the CMOS and NVRAM contents before putting in a backup battery because mine is from 2012 and migrating to a W2000 or XP environment with all the applications working fine.
I care a lot about my TDS7254 and I wouldn't want to break it, that's why I want to take all the necessary precautions before making NVRAM and software modifications. I ordered equipment to do the job (mat, anti-static bracelets, welding stripper etc…).
I would like to receive your image under XP of your TDS7104 to try it on my TDS7254.
Cordially.
Translation by G..e.
-
Hello exit_failure,
I just looked at your gitbhub repository and it's very good work. My TDS7254 works with some problems in "trigger EDGE" synchronization mode. On the other hand, when I use the “ADVANCED trigger” mode, it works very well. What I would like to do is make a backup of the CMOS and NVRAM contents before putting in a backup battery because mine is from 2012 and migrating to a W2000 or XP environment with all the applications working fine.
I care a lot about my TDS7254 and I wouldn't want to break it, that's why I want to take all the necessary precautions before making NVRAM and software modifications. I ordered equipment to do the job (mat, anti-static bracelets, welding stripper etc…).
I would like to receive your image under XP of your TDS7104 to try it on my TDS7254.
Cordially.
Translation by G..e.
Hi Claudius,I never backed anything up since mine came with a dead battery anyway. I don't know if there is any calibration data or anything else that needs to be backed up which will be lost permanently. You can display the necessary settings for board to board communication and the boot process by attaching a serial console in the way described at the repo and taking screenshots/copying the text.
Maybe somebody else knows if there is anything else worth backing up.
After reinstalling the operating system or applying an image you always have to run the self calibration from the TekScope application.
Also maybe consider getting a separate HDD/SSD for the new installation so you can put the old one back in the scope if anything goes wrong.
Please give me a week or so for the image. I have a lot of work that requires my attention at the moment. :-(
-
Hello,
I have already imaged the original 40 GB HDD and replaced it with a 128 GB Sata SSD. In addition I replaced the CMOS battery. It works very well and it starts much faster. I read that if you manipulate the NVRAM, you will have to configure everything. What I don't know how to do at the moment. Fortunately, there are specialists who share their information with beginners like me. With their experiences it seems easy to them, but for me who has never done any manipulations on this scope I have an apprehension is much more complicated. This afternoon I just received my USB-serial cable, I will connect it and see what happens when my TDS7254 starts up.
A big thank you for your image and I will wait all the time necessary and I take this opportunity to order another SSD.
-
Hi Claudius ! I haven't even try to upgrade to Win2000 as the Win98 image works fine here ! Also, it seems like we already chat a bit on French' "Leboncoin" ;D
Thanks a lot Exit_failure for your help ! I'm gonna check the Github repository.
-
Hi Claudius ! I haven't even try to upgrade to Win2000 as the Win98 image works fine here ! Also, it seems like we already chat a bit on French' "Leboncoin" ;D
Thanks a lot Exit_failure for your help ! I'm gonna check the Github repository.
Hello RPuccio,
Yes, absolutely, we discussed on LBC.fr. I'm still trying to fix my sync issue. I had a few discussions on other forums about this and I was strongly advised to reinstall everything. Indeed, as I wrote previously, I think that my scope was reinstalled just before my purchase and that the synchronization fault could come from there. That's why I would like to backup NVRAM, CMOS because I made an image of my HDD (installed by vendor) and it does not contain NVRAM and CMOS contents.
I am not reassured to disassemble my scope. This is why I want to take the maximum precaution. The beginnings start badly, I have just bought a USB-COM serial link and for the moment I have no character displayed on the Terminal console when starting the scope (I use CoolTerm on PC W10).
Since I don't have anything extra to do a full reinstall, I'll try with an image other than mine. I would prefer to have all the elements to do a complete installation.
I'm glad to know that your oscilloscope is working properly. Is it a full install or an image? If it's a full install with W98, would it be possible to get your full procedure with all the softwares.
-
Hi,
Recently i got a Tek TDS7404 DPO with No power-on response.
gone thru the entire service manual. checked the unit by removing all the boards one by one to locate the fault: with powersupply board , PPC board and rear power distribution board in loop , but the result is null.
With Mains power-on, Standby led glows on PSB without Debug poweron jumper on PPC, if the pins shorted with jumper led goes off.
no further response.
How to find out which one is faulty : powersupply or PPC.
Gone thru the entire thread but dint come across this sort of problem.
Can we check power supply in standalone condition if so pls any help is appreciated
hopefully i might get successful in repairing this with ur help Thanks a lot
-
Hi,
I recently bought a working TDS 7054 from an industry auction for next to nothing. It stopped working last week, being stuck at the TekScope splashscreen.
With the help of this thread, I was able to fix it by spotwelding a new battery to the NVRAM powercap and reconfiguring it. The PC Mainboard had a leaking capacitor which did not affect performance yet but which I of course replaced.
I just wanted to say thank you to TiN. Stay strong! I hope you are fine and that this despicable invasion is soon put to an end.
-
Hi Claudius, my file is a W98 image, not a full install.
-
@everybody: repairing his 7154/7254/7404 Scope ( non B Version) . did you ever think about glue-ing heatsinks on the trigger chips otherwise they will die overtime |O and your unit becomes useless.!
(Chips are obsolete / not available anymore.)
@Claudius089: i hope it is not yet too late. -> sympthon is edge triggering problems
when working on those units without heatsinks on the trigger chips use a forced airflow over the ACQ board.
-
Hi Claudius, my file is a W98 image, not a full install.
Hello @RPuccio,
Like me, I only have one hard drive iso. I thought you did a full install.
I recovered on the web a W9..SE os in iso cd and a bootable dos 6.2 diskette. What I would like to know is if I reinstall W9..SE, do we find all the applications (drivers, third-party applications, etc.) for it to work correctly. I went to Tek site and found the main application (CSA7000 AND TDS7000 SERIES FIRMWARE UPGRADE - V2.5.3) but no drivers on the hardware. I don't know what drivers I need to install for graphics card, touch screen etc...
I already installed pcs completely, but at least I knew all the hardwares boards inside and I can say that sometimes it was not easy, so for a complex oscilloscope like TDS7254, I prefer to take all my precautions which will save me a lot of surprises.
I have to replace the battery of the famous NVRAM. I assume that disconnecting the battery, the data will be lost and it will certainly be necessary to configure everything.
I try to document myself on the information that passes through the COM port. It starts badly, I bought a USB-COM converter and I can't communicate with the oscilloscope. I shunted RD&TD and on my PC terminal when I send a character I receive it. It proves that the USB-COM converter is working.
Translation by go..le
-
@everybody: repairing his 7154/7254/7404 Scope ( non B Version) . did you ever think about glue-ing heatsinks on the trigger chips otherwise they will die overtime |O and your unit becomes useless.!
(Chips are obsolete / not available anymore.)
@Claudius089: i hope it is not yet too late. -> sympthon is edge triggering problems
when working on those units without heatsinks on the trigger chips use a forced airflow over the ACQ board.
Hello @Charlyd
For the moment I have not fully opened the oscilloscope. I replaced the CMOS battery. I'm scheduled to fully open it to replace the NVRAM battery (it's from 2012). When it's disassembled I'll put the heatsinks on the chips.
Thanks for this info.
Translation by go..le
-
hi
TEK TDS7404
not switching on
this condition is
standalone powersupply with mains switch on on the
now its in standby mode
-
now this pic is with rear power distribution board connected between
powersupply & PPC board
-
Thank you everyone for the massive contributions, and exit-failure on the github repo.
I'm currently repairing a TDS 8000 scope, and unwittingly removed the aquire board nvram battery :palm:
Does anyone know if the option rom software works with 8000 series scopes too?
-
I dont find the AGP/PCI select option either,
Do you have solution?
thanks
-
hi,
Could you please give me a copy of TDS7104 win2k image or ghost files?
When I reinstall windows2000 , I met the“UNSUPPORTED HARDWARE DETECTED”
-
Hi reviving this thread loll
What are the problems i may face if the N-vram battery is dead, i have an 7254B who began to lock while using it, sometimes take a long time to boot from the TEK DPO logo / page
Sometimes it hang while running, but pass all spc tests ??
It has the latest 865 motherboard, the mobo battery was changed 1 week ago, i had clock problems and lan setup lost loll
It has the ds1245y-120 chip 28 pins i think on the power pc board year 2005, surely must be dead ???
Did manage to copy the vxboot folder on usb key just in case
-
@coromonadalix if you have a programmer always good to replace the nvram DS1245Y of the TDS7254B and solder in a socket.
but from my interrested. what windows pc type motherboard is installed in your scope? i guess Intel desktop but can you share some pictures and also from the vga/ bridge card.
-
hello everyone
I fix the HDD operation system and replace the dead DS1245Y 。due to lack and fake DS1245Y，I use TI BQ4013YMA-70N to replace DS1245Y
It seems worked ok.
I pass all selftest but SPC failed.
I use the console to monitor whats wrong abot SPC test:
0x973310 (Ch1 Gain Cal): >> Error at step ChanCalPart2.36: FineOffset DAC Nonconvergent during cal of Reference (10X) Attenuator Gain
0x2c46a70 (CalWatch): Temperature transition into SPC-supporting range.
Is some DAC in Acq. board dead？ Is anybody know which DAC is it?
thanks
73!
-
It's an p4 2,8ghz with 2gb of ram
When i'll re open it i'll take some pictures ... still need to use it while it doesn't create / have too many problems
I ordered at digikey a ds1245y-120 pdip around 50$ CAD ?? the tricky part will be to remove that chip ... will need an vacuum desoldering tool
Did read thru all this thread :phew: for the nvram backup script, i found out i can force a factory reset and apparently put back stuff in the nvram, i have no experiences for these kind of stuff loll but feel relieved.
Found out that the motherboard is in DHCP mode for the lan, and apparently or it seems the TEK Scope software will push an ip address ??
Pushed XP Sp3 pack into it without problems ... did put XP in classical mode with the ''best optimal mode'' in the performance settings
Managed to find an usb hdd dock with Ide and sata ports who can clone hard drives and i'll do an hdd image just in case
May be tempted to put an pata ssd in it to slightly optimise to boot time, but mostly to get rid of an aging drive
And i did found out i have a slight touch screen offset, even with the calibration utility, it can't be corrected.
From the middle screen to the bottom, i have around 3 to 5 mm offset in the mouse pointer ...
In my case all SPC tests passes .... but sometimes the scope hangs without reasons, have to restart it ?
You have partial service manual for the tds7000 series, but haven't found a complete manual if there is one ?? Links ??
-
@coromonadalix. i used my denon sc7000 to desolder the Dalles chip. and afterwards i placed this socket.(see picture for the quality type)
i will be happy and curious to see your pictures.
maybe you can share the bios version fro. your unit.
When you enter the bios with [DEL or [F2] you find a setting called " silent boot " enabled . when switching to disabled you see lots of more info while posting and also bios info.
greetz charly
-
thks
I did get an nvram bin file and somekind of bios bin file ?? not sure this bios file is the mainboard one ?? The file size seems okay with the extracted bios ??
I know there is an universal bios tool, gonna try this one too
I have extracted / backed the VXboot folder contents, all the drivers, calibration files etc ...
I'm gonna post them in a while and send them to KO4BB too
EDIT
The board is an Intel D865GLC (Tektronix boot logo) bios rev : BF86510A.86A.0075.P24
P4 2.8ghz fsb 533mhz
Primary video is : pci, use Tvia Display Driver V.5.2.005
Bios file : just remove the .txt extension
Bios file extracted thru the nvram backup script ?? remove the .txt extension
Attached files are the files found here and github to backup the nvram, i used the 6000-7000 one
Edit 2
For the motherboard : it can support up to 4 gig of ddr400 ram and fsb800 cpu ??
Not sure i want to go al the way up ??
Will it affect tekscope ??
Edit 3
Attached calcons files, spc was done recently and passed all tests ??
-
Need CalCons files .
Could someone upload there TDS7104 c:\vxBoot\CalCons files?
like 0~16 0~16.sta
I found 0~15 files match the BANK0~BANK15 and 16/16.sta match user cal SPC data
I met a 521 error
and when I calConStatus = cc_init(2)
I met
0x1641540 (tShell): cc_restoreBank: can't open file C:/vxBoot/calCons/0
0x1641540 (tShell): cc_init: bank 0 chksum failed, NOT reset to factory
etc.
So I need these files. Plase help me
Thanks
VY 73! :-//
-
here's the calcon of our 7254B, spc has pass all tests and was done recently
-
thank you :-+
-
hi everyone, really glad to learn from this thread. recently i got a tds7104,boot stop at the scope start screen,I use vxboot to reset and now it boots ok.
but self test ,it reports 521 factory cal integrity ,factory cal data error. I read the boot log,it seems that it can't open some cal file in C:\vxboot\calcon. And i checked in C:\vxboot\calcon, there do missed cal file named 1 to 8 and 15,could this be the cause of error 521? Can anybody share the files ? Or any other suggestion.
Error 521 is the EEPROM on the acquisition board has been corrupted. It's reference designation is U1052.
Here is a known good U1052 binary from a TDS7104. Obviously it won't have the correct constants for your scope, but it will get rid of the error.
Otherwise you'll need to have a proper calibration with adjustments done.
Thanks your U1502 binary files ,I fix my TDS7104 521 errors
:) :clap:
Thanks charlyd give me a lot guide and advices :popcorn:
-
hi @BG8AAK thanks your welcome.. :-+
ok here i am again with a CSA7404B
This unit is fully passing all Diagnostics ok but when SPC is ran it gives a fail with M866CompCalibrator error on all 4 trigger
DIAGNOSTIC EXECUTION finished in 140.94 sec
0x38fc090 (CalWatch): Temperature transition into SPC-supporting range.
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain1b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 1b failed -- ...wrote cal constant C
C_TRIGdcGain1b to 0.000000, failed
. **
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain2b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 2b failed -- ...wrote cal constant C
C_TRIGdcGain2b to 0.000000, failed
. **
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain3b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 3b failed -- ...wrote cal constant C
C_TRIGdcGain3b to 0.000000, failed
. **
0x37ca7d0 (SPC task): cc_loadV: CC_TRIGdcGain4b was 0; clipped
0x37ca7d0 (SPC task): ** M866CompCalibrator 4b failed -- ...wrote cal constant C
C_TRIGdcGain4b to 0.000000, failed
. **
can this be a problem with the MAX9601 dual pecl-output comparator? from what i see and compare my output is fully "0" ; clipped on all 4 channels....where "snoopy_lei" has small values on only 2 channels.
anybody already work on the M866CompCal failed errors?
While searching for this error i ordered a New DS1245Y to start off but it will take some time to arrive. meanwhile i am wandering if this problem is known already or quit new.
from the posts i have seen i guess it happens occasionally on the newer B models.
-
i found in a SPC debug output from an different TDS7404 ( Non B version)
taken without the trigger chips installed the error is a sort of equal and this confirms a trigger problem in the B version.
-
may i drop a question here to all software guru and experts
is it possible to write a script or create a small program like TEKTOOL
to export the TDS7000 eeprom content, like it is done with the TDS700 series.
i think there is a need for this.
-
Hi,
Everyone, My TDS7104 is not working now, I have replaced the DS1245-120 with DS1245-120+, after reboot the unit, the following log we got, please help to check what happen. thanks.
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.8.1
Creation date: Jun 27 2003, 09:52:39
Press any key to stop auto-boot...
1
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]: c
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : sm
processor number : 0
host name :
file name : c:/vxboot/vxWorks.st
inet on ethernet (e) :
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
user (u) :
ftp password (pw) (blank = use rsh):
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
other (o) :
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]:
[VxWorks Boot]: @
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network intPC1 dio device driver installed
erface lo0... done.
Attaching DIO client... done.
Loading c:/vxboot/vxWorks.st...1773516
Starting at 0x200000...
Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topscript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
ld < TekScope.o
value = 23666688 = 0x1692000
ld < TekScopeSM.o
value = 23666048 = 0x1691d80
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1693940: value = 23673184 = 0x1693960 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691bc0: value = 23665696 = 0x1691c20 = pDBfs + 0x60
copy ("TekScope.DBF", "/db/TekScope.DBF")
value = 0 = 0x0
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 21818112 = 0x14ceb00
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
0x16987e0 (tShell): >> Setting PLL to 1.25e+09 Hz.
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 23692720 = 0x16985b0
excHookAdd(stopStressForException)
value = 17557980 = 0x10be9dc = stopStressForException
dsyInit
value = 21806728 = 0x14cbe88
dsyWPApplyNextRegs
value = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
#xiangzhe add
# tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
nvram_initFileSys
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4d7c3
TmgrInit("/db")
0x16987e0 (tShell): Assertion failed: status == EXIT_SUCCESS, file ../src/dbmsInterfaceLibrary.cpp, line 14916
ppc board system is halt and the win2000 display the welcome screen of Tektronix and then no response.
-
So I came across this thread randomly and I wanted to pay it forward and help however I can. I've recently acquired a TDS7245B scope on ebay that seems to be a bit unique since it came preloaded with windows XP from the factory with the 4M ST and USB options keys enabled. I intend to mirror and replace the hard drive with an SSD. If anybody can tell me about creating ghost images (I assume this just means an image of the hard drive), then this particular configuration might be a valuable addition to the collection.
-
To be sure, you kill the tektronix software with the xp task manager, and you copy everything in the VXWork folder on a usb key and other driver folders ...
You have some commands to backup the mainboard bios, calcons, vxbios and other things .. we have the 7254B model at my job
The nvram (ds1245) with integrated cell died, but we had backups ... and i have downloaded everything from TEK website, juuust to be sure.
I will order an ssd drive, it is very slow to boot, I upgraded it to XP sp3, killed all useless stuff in it (Msn, Outlook etc..) and we do not let it connect to the web,
since Xp is outdated
And yes we have the latest motherboard for it, i did find the original Intel (non TEK bios logo for it), and it did receive all the ram it can use.
Cost an arm for the calibration (Around 1k$$)
To clone a drive you have some free software or paid, disk genius, macrium reflect, drive image etc ...
just a tip
Always use another computer to clone a drive, an working / booted computer can not backup itself, and / or if your bios permit it , boot from an usb key with some already made Window PE disks like Strelec ... they have tools you need to clone on another drive
If you do it, take some note about the software and the version used ... i used a second computer with an external ide dock for the backup in my case
They are big machines, but i love them loll classic settings no fuss loll I love the huge screen
I have the new sds 1xxx rigol models, i have some hard time figuring out all the functions loll and more easy on theses old era stuff loll
-
To be sure, you kill the tektronix software with the xp task manager, and you copy everything in the VXWork folder on a usb key and other driver folders ...
You have some commands to backup the mainboard bios, calcons, vxbios and other things .. we have the 7254B model at my job
The nvram (ds1245) with integrated cell died, but we had backups ... and i have downloaded everything from TEK website, juuust to be sure.
I will order an ssd drive, it is very slow to boot, I upgraded it to XP sp3, killed all useless stuff in it (Msn, Outlook etc..) and we do not let it connect to the web,
since Xp is outdated
Thanks for the reply, I appreciate the tip on killing tekscope before copying the vxworks folder. I didn't realize that when I copied it the first time. Was there anything special you needed to do in order to upgrade to SP3? I currently have SP2. I've read this whole thread start to finish but I must have missed or wasn't paying attention to commands on backing up the mainboard bios, calcons, vxbios etc? Is there a list somewhere you could point me to? Really appreciate it!
Justin
-
for sp3 nothing special
With the task manager called from CRTL ALT DELETE, kill the tektronix process, start a new task, write "explorer" and do what you have to do, use an usb key with the sp3 pack on it
And reboot the scope normally
Gonna search for the scripts, they where mostly found here .... and i use the original intel bios, it can access the bios more easily ... but you have to be very careful for the video section if you mess things, the lcd display will not work correctly BUT i dont know for sure the motherboard you have ....
Clean the unused stuff in xp with the add remove application in control panel ...
As stated PLS do a cloned drive file before messing with things, just in case ....... a good dust clean up too, take anti static precautions
-
Another great upgrade to juice up one of these tired, old oscilloscopes is to install an inexpensive SSD. I went with the Kingspec KSD-PA25.6 PATA 44-pin MLC SSD. They can run as little as $50 delivered at the low-end, and range in capacities from 16GB to 128GB. While the SSD does not make it run that much faster during operation like the processor upgrade does, it does allow it to cold boot much more quickly and get away from the unreliable old notebook hard disk drives. In the scheme of things, it seems like it's a worthwhile investment to me.
Ok this is kind of a dumb question admittedly but I've spent all day trying to clone a drive which should be easy. I'm going from the original 40GB travelstar IC24N040ATMR04-0 to a 64GB Kingspec KDS-PA25.6 PATA 44-pin MLC SSD. I've tried cloning with acronis 2017, clonezilla, HDDGuru all with no success. I've tried booting with master mode enabled on the PATA drive, slave mode, and cable mode as well. It seems that I'm not able to boot to this drive even though the bios has recognized the drive each time. Is there any reason you can think of that this wouldn't work on a windows XP machine? I either get a disk read error or a flashing cursor that never goes away depending on which cloning software I'm using.
-
Are you doing it on another computer ?? or try to use the main (scope) ??? Because you can't do a clone of the runing (host) computer, wnindows lock files while running
Or start a fresh installation with the ssd in the scope, windows will fomat and prepare the drive ?? and you rebuild everything .....
If the bios see it, normally it should go fine ?? unless weird compatibility problems ? or the cloning fail to prepare the mbr / boot sector correctly ??
-
Are you doing it on another computer ?? or try to use the main (scope) ??? Because you can't do a clone of the runing (host) computer, wnindows lock files while running
Or start a fresh installation with the ssd in the scope, windows will fomat and prepare the drive ?? and you rebuild everything .....
If the bios see it, normally it should go fine ?? unless weird compatibility problems ? or the cloning fail to prepare the mbr / boot sector correctly ??
I'm using bootable media like clonezilla or acronis which loads it's own operating system so the drives in question are not being run at the time of cloning. At this point I suspect it's a bad drive because I've tried sector by sector cloning even and it still won't boot. The bios does in fact see it but then I get a disc read error so I'm going to try a new drive and see what happens.
Thanks for the advice!
-
Hi,
As far as I know all TDS7000B Series with B020000> Serial Numbers had Factory Off Intel D865GLC MB's with a Windows XP SP2 Installation.
I ordered for my TDS7000B a "NEW" 40 GB Hitachi Travelstar HDD (same as the old, including RPM). For Cloning I used an old Vista Desktop with free SATA Slots and DeLock 22-Pin SATA to 44-Pins IDE Adapters. In addition I downloaded a "Legacy" Macrium Reflect Version from www.filehorse.com (http://www.filehorse.com) with a Windows 10 Desktop and installed the 32-Bit program on the Vista 32-Bit Desktop. No Registration or needed Keys. A plus when you install Programs on Offline PC's.
Before I started the Cloning Process I had to Initialize and Format the "New" Hitachi HDD (Disk Management). All this worked without any obstacles,
Succes,
Calibrationfixture
-
Thanks, really appreciate the advice. I ordered a hitachi Travelstar and we'll see where that gets me.
Hi,
As far as I know all TDS7000B Series with B020000> Serial Numbers had Factory Off Intel D865GLC MB's with a Windows XP SP2 Installation.
I ordered for my TDS7000B a "NEW" 40 GB Hitachi Travelstar HDD (same as the old, including RPM). For Cloning I used an old Vista Desktop with free SATA Slots and DeLock 22-Pin SATA to 44-Pins IDE Adapters. In addition I downloaded a "Legacy" Macrium Reflect Version from www.filehorse.com (http://www.filehorse.com) with a Windows 10 Desktop and installed the 32-Bit program on the Vista 32-Bit Desktop. No Registration or needed Keys. A plus when you install Programs on Offline PC's.
Before I started the Cloning Process I had to Initialize and Format the "New" Hitachi HDD (Disk Management). All this worked without any obstacles,
Succes,
Calibrationfixture
-
So it turned out to be a bad drive. I appreciate the help.
On a side note, now that I've got the new cloned drive booting, does anyone know if the key generator works with the B versions as well? Wntering a model number with a B doesn't seem to work. I tried dropping the B and entering my serial number but the keys it's generating don't work when using the 04FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF option mask.
-
Hi,
The Program supports the TDS5000(B), TDS7000(B), CSA7000(B), TDS6000(B/C), DPO7000 and DSA/DPO70000 (No Letters) Series. For the more recent MSO70000 Series I don't know.
I used for my TDS7404B Option Masks: 10 44 FF FF FF FF FF FF FF (14 x F). With this I enabled as far as I know all possible Options for the TDS7000B Series (i.c.w. Scope Application V 5.1.3), including Max Record Length (64 Mp). With help of:
https://xdevs.com/doc/Tektronix/TDS5000B/
I installed TDSVNM (former App. 61) and TDSPTD (former App. 69) Option Modules.
Succes,
Calibrationfixture
-
Thanks Calibrationfixture, I really appreciate your help. I was referring to the TDS7254B so that's great to hear I should be able to get all of the options working. From the link you posted, it's not clear to me how you are using the TDS5000B folder for the TDS7404B? It appears this folder contains disc images for the TDS5000B. Did you mean this folder instead?
https://xdevs.com/doc/Tektronix/TDS7000/Additional%20Scope%20Software%20for%20Options/
I see the TDSVNM application there but not the TDSPTD.
-
Hi,
In the TDS5000B Folder you see also:
https://xdevs.com/doc/Tektronix/TDS5000B/tektronix_options_sw_disk_1.dd
The Option Software for the TDS5000B and TDS7000B Series is the same.
In addition for a TDS7254B with SN B020126 your input must be for example:
.\gen.py TDS7254B B020126 1044FFFFFFFFFFFFFF (14 x F)
For a DPO7254 the string of F's after the First 4 Digits must be 20 at least. For its Maximum Record Length (Option 10RL) the First 2 Digits must be 04.
Succes,
Calibrationfixture
-
Got it, thanks a lot calibration fixture! Just got it fully unlocked using the option mask you gave me. Working on getting the options image installed now. I can't thank you enough!
-
Thank you for the nice board.
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/350/ (https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/350/)
I replaced NVRAM with this FRAM and it passed the POWER-UP Diagnostic and VXworks now boots! However, as the console below shows, it says the block is too large and stops with Assertion failed. So Tekscope is still stuck at the splash screen. If anyone has a solution, please help!
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.7.0
Creation date: Jun 12 2002, 11:45:18
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
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 c:/vxboot/vxWorks.st...1773500
Starting at 0x200000...
Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.7.0.
WDB: Ready.
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topscript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
pDbDev = ramDevCreate(0, 512, 128, 128, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1682d20: value = 23670112 = 0x1692d60
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1681900: value = 23604288 = 0x1682c40
ld < TekScope.o
value = 21167072 = 0x142fbe0
ld < TekScopeSM.o
value = 21166624 = 0x142fa20
copy ("TekScope.DBF", "/db/TekScope.DBF")
copy: error writing file.
value = -1 = 0xffffffff = pDbDev + 0xfe97d2df
overrideFPdefaults()
value = 0 = 0x0
measurePPCtimebase
value = 0 = 0x0
registerMemPartitionSizes ( 0x00000000 )
value = 0 = 0x0
semInitForQueueCheckLogMsg
value = 23673216 = 0x1693980
initSysWaiter()
value = 0 = 0x0
raxInit
value = 0 = 0x0
paiInit
done
value = 16944404 = 0x1028d14 = PaiBaseRegisterTable + 0x948
verifyAcqBoardID
Inappropriate Acq board ID found: 0x7
value = 0 = 0x0
tcsLoadTableToNVRAM "pc:c:/vxBoot/Setup.tcs"
value = 0 = 0x0
updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")
0x16987e0 (tShell): 1368 bytes successfully verified.
AVR processor FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.
value = 0 = 0x0
cd "pc:"
value = 0 = 0x0
raxInitializeDevices
done
0x16987e0 (tShell): (Re)starting Acq Processor
value = 22411048 = 0x155f728
excHookAdd(stopStressForException)
value = 16732228 = 0xff5044 = stopStressForException
dsyInit
value = 22405032 = 0x155dfa8
dsyWPApplyNextRegs
value = 16934280 = 0x1026588 = DsyRegisterTable + 0xab0
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
nvram_initFileSys
0x16987e0 (tShell): memPartAlloc: block too big - 38884352 in partition 0x337eac.
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba5e3e3
TmgrInit("/db")
0x16987e0 (tShell): Assertion failed: EXIT_SUCCESS == retValue, file ../src/tmgrClass.cpp, line 1487
-
have you tried this:
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
to
NvramClearDb = 1
it should force a state reset ?
the "fun" sarcasm is to get onto a windows like os or boot into something else to edit the file .........
-
I got an error that TekScope.o could not be opened. but, something seems to be going on.
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
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 c:/vxboot/vxWorks.st...1773516
Starting at 0x200000...
Host Name: bootHost
User: target
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.1 .
WDB: Ready.
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:/vxboot/topscript.hw ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/vxBoot"
value = 0 = 0x0
pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1692d40: value = 23670112 = 0x1692d60 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1691720: value = 23669856 = 0x1692c60
ld < TekScope.o
'an't open input 'TekScope.o
errno = 0x3d0002 (S_objLib_OBJ_UNAVAILABLE)
Done executing startup script c:/vxboot/topscript.hw
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-
I just got a TDS7154B and while it’s in good working order I’d like to try to keep it that way as long as possible. I’m imaging the HDD and replacing it with an SSD, replacing the CMOS battery and taking a look at the RTC on the PPC board too.
One thing in particular I’m looking at is adding heat sinks to the trigger chips on the acquisition board, as it seems this is a common failure mode and they’re unobtanium. The board I have is 679-5674-11 (or maybe 665-1719-11, that’s another label right beside the first). I did a visual inspection of the visible side of the board and don’t see the infamous chips. I also looked at the other side of the board online (don’t want to remove it if I can help it) and I don’t see any devices which have the correct package.
Doesn’t this board/scope use the same trigger ICs as the other models in this series? Are there any other things I should be taking care of while I have it open to help keep this in top shape as long as possible? The caps on both the motherboard and PPC board look pretty good, which surprised me.
-
Hello team. I am a bit struggling with my TDS 7404. I've got it with broken HDD and when i restored it, I hit the problem with Dallas chip on PPC has lost its settings. I hooked up serial to the side of the scope , as per TIN notes and recreated configuration for PPC. I even saw scope SW started once, but when I rebooted scope it stuck in the same place - on splash screen of the SW. Indicator on the board shows letter "P" constantly . Here is output from terminal connected to the PPC console port . Is there any ideas why it is stuck again ?
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.4.0
Creation date: Nov 2 2000, 11:03:34
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
host name : host
file name : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.168.0.2
user (u) : anonymous
ftp password (pw) : anonymous
flags (f) : 0x1000
target name (tn) : target
startup script (s) : c:\vxBoot\topScript.hw
other (o) : nvfs=0x1000
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network inPC1 dio device driver installed
terface lo0... done.
Attaching DIO client... done.
Loading c:\vxBoot\vxWorks.st...1773516
Starting at 0x200000...
Initializing backplane net with anchor at 0x16e0000... done.
Backplane anchor at 0x16e0000... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6008 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997
CPU: Tektronix HPP - PowerPC 740. Processor #0.
Memory Size: 0x2000000. BSP version 1.0.8.0 .
WDB: Ready.
usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0
data access
Exception current instruction address: 0x00223f30
Machine Status Register: 0x0000b030
Data Access Register: 0xd40f1a00
Condition Register: 0x20000042
Data storage interrupt Register: 0x40000000
Task: 0x1fffe08 "tRootTask"
When I am pressing CtrlC to the screen I see following
2f1588 vxTaskEntry +60 : 223d6c ()
223d6c usrRoot +458: usrNvFsInit ()
206abc usrNvFsInit +18c: dosFsDevInit ()
2a1838 dosFsDevInit +260: 2a6170 ()
2a6230 dosFsTimeSet +2ac: 2a6a84 ()
2a6de8 dosFsTimeSet +e64: 2a210c ()
2a23c8 dosFsDevInitOptionsSet+aec: 2a210c ()
2a21e8 dosFsDevInitOptionsSet+90c: 2a0b50 ()
2a0b78 symSRemove +c8c: 2a5cdc ()
293c34 ramDevCreate +1f0: bcopy ()
-
Thank you not to put a veryyyy long boot info like the previous threads
First does the windows boot completly or get stuck too, if it boot can you show us the device manager / peripherals if they are all ok and not having some exclamation errors ...
The computer side must be perfect before the scope side
https://xdevs.com/fix/csa7404/
you see on xdevs the P code : loading files from host ............................ there could still be some installation problems, something is missing for a complete TEK software boot
Have you checked on hp all the softwares drivers etc ... i still have backups from our 7254 drivers etc ... i can or could give some help BUT IT'S a B version
-
I received a CSA7404B without a HDD, so I'm in the process of setting that up. I received the OS restore ISOs from Tektronix for my particular unit (they indicated this is BIOS revision number specific). The installation appears to work - it completes and doesn't throw any errors. However, I'm not able to reboot into the HDD. The screen goes dark after the "Tektronix Enabling Innovation" display and doesn't give any indication that anything is happening.
I attached a serial port to the PPC board and see the following boot up log:
romPost: I am alive .
uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
romPost: L2 cache turned on.
romPost: MPC107
romPost: I am alive .
uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
romPost: L2 cache turned on.
romPost: MPC107 Walking-one passed.
romPost: MPC107 configuration passed.
romPost: Intel21555 PCITOPCI bridge 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: PERFORMING DRAM MARCH TEST WITH CACHE OFF...
romPost: Disabling data Cache...
romPost: Data cache disabled.
romPost: Disabling instruction cache...
romPost: Instruction cache disabled.
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 - IBM 750CXe
Version: 5.3.1
BSP version: 2.0.1.10
Creation date: Sep 30 2003, 07:53:07
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
The diagnostic LED gets to state "L" where it remains.
I don't see any obvious errors in this boot sequence other than it doesn't make it past this stage.
I also compared the HDD contents of my working TDS7104 to this CSA7404B. The top level listing of the CSA7404B is:
-rwxrwxrwx 1 matt users 150528 Jun 19 2003 arcldr.exe
-rwxrwxrwx 1 matt users 163840 Jun 19 2003 arcsetup.exe
-rwxrwxrwx 1 matt users 0 Jul 2 2003 AUTOEXEC.BAT
-rwxrwxrwx 1 matt users 213 Sep 23 2003 boot.ini
-rwxrwxrwx 1 matt users 0 Jul 2 2003 CONFIG.SYS
drwxrwxrwx 1 matt users 248 Oct 10 2003 Documents and Settings
drwxrwxrwx 1 matt users 86 Jul 2 2003 Inetpub
-rwxrwxrwx 1 matt users 0 Jul 2 2003 IO.SYS
-rwxrwxrwx 1 matt users 0 Jul 2 2003 MSDOS.SYS
-rwxrwxrwx 1 matt users 34724 Jun 19 2003 NTDETECT.COM
-rwxrwxrwx 1 matt users 214432 Jun 19 2003 ntldr
-rwxrwxrwx 1 matt users 805306368 Oct 20 2003 pagefile.sys
drwxrwxrwx 1 matt users 656 Oct 14 2003 Program Files
drwxrwxrwx 1 matt users 250 Oct 10 2003 RECYCLER
-rwxrwxrwx 1 matt users 453 Jul 8 2003 Shortcut to Embedded Console.lnk
drwxrwxrwx 1 matt users 24 Jul 2 2003 System Volume Information
drwxrwxrwx 1 matt users 602 Oct 10 2003 Tektronix
drwxrwxrwx 1 matt users 2396 Oct 11 2003 WINNT
And here's the top-level of the TDS7104:
drwxrwxrwx 1 matt users 154 Jul 22 2004 APP7_TDSDAS_17_JUN18
-rwxrwxrwx 1 matt users 150528 Jun 19 2003 arcldr.exe
-rwxrwxrwx 1 matt users 163840 Jun 19 2003 arcsetup.exe
-rwxrwxrwx 1 matt users 136 Jan 9 2003 AUTOEXEC.BAT
-rwxrwxrwx 1 matt users 222 Sep 18 2003 boot.ini
drwxrwxrwx 1 matt users 8 Sep 18 2003 Cabs
-rwxrwxrwx 1 matt users 0 Jan 10 2003 CONFIG.SYS
drwxrwxrwx 1 matt users 150 Jan 28 2003 Documents and Settings
-rwxrwxrwx 1 matt users 1211 Feb 20 2001 Embedded Console.ht
drwxrwxrwx 1 matt users 114 Jan 10 2003 Inetpub
-rwxrwxrwx 1 matt users 0 Jan 10 2003 IO.SYS
-rwxrwxrwx 1 matt users 0 Jan 10 2003 MSDOS.SYS
-rwxrwxrwx 1 matt users 755 Jul 22 2004 msildbg.log
-rwxrwxrwx 1 matt users 34724 Jul 22 2002 NTDETECT.COM
-rwxrwxrwx 1 matt users 214432 Sep 10 2003 ntldr
-rwxrwxrwx 1 matt users 805306368 Nov 16 2020 pagefile.sys
drwxrwxrwx 1 matt users 28 Jul 22 2004 Plugins
drwxrwxrwx 1 matt users 1032 Apr 5 2007 Program Files
-rwxrwxrwx 1 matt users 10155 Feb 23 2001 RAD_HD.EXE
-rwxrwxrwx 1 matt users 860 Feb 13 2001 RADSCAN.EXE
drwxrwxrwx 1 matt users 178 Jan 28 2003 RECYCLER
drwxrwxrwx 1 matt users 24 Jan 10 2003 System Volume Information
drwxrwxrwx 1 matt users 94 Feb 5 2004 TekApplications
drwxrwxrwx 1 matt users 60 Apr 5 2007 TekScope
drwxrwxrwx 1 matt users 314 Sep 18 2003 Tektronix
drwxrwxrwx 1 matt users 0 Feb 5 2004 Temp
drwxrwxrwx 1 matt users 296 Apr 5 2007 vxBoot
drwxrwxrwx 1 matt users 10 Feb 4 2004 VXIpnp
drwxrwxrwx 1 matt users 8 Sep 12 2003 Windows
drwxrwxrwx 1 matt users 3920 Apr 10 2020 WINNT
Notably, the CSA7404B is missing the vxBoot directory, among others. So it's probably not so surprising it can't boot. The Tektronix contact insists this OS restore is all I should need though to re-install Windows.
Any ideas? Should I just try to add the vxBoot directory and resident files to the CSA7404B?
Thanks!
-
check autoexec.bat and config.sys, boot.ini by editing them, would be stupid to point to another partition ???? normally vxboot / vxwork is on the main C:\ ??
i would copy the good vxwork folder ... worth a try ?
-
check autoexec.bat and config.sys, boot.ini by editing them, would be stupid to point to another partition ???? normally vxboot / vxwork is on the main C:\ ??
i would copy the good vxwork folder ... worth a try ?
AUTOEXEC.BAT on the CSA7404B is empty (0 bytes). Here are the contents on my TDS7104:
@echo off
c:\RAD_HD.EXE
REM This is the CMOS Restore Program.
REM It will restore CMOS settings to factory
REM recommended settings.
CONFIG.SYS are empty on both.
Here is boot.ini on CSA7404B:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect /kernel=ntoskrn1.exe
And on TDS7104:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect /bootlog /kernel=ntoskrn1.exe
What do you think about the AUTOEXEC.BAT? Should I copy that over from the TDS7104? The CSA7404B also doesn't have the RAD_HD.EXE file though.
As for the vxBoot directory, I can try that and let you know.
-
I copied vxBoot over to the CSA7404B. That didn't work, but I noticed from the serial log that there were some changes to file name capitalization, so I changed vxBoot to vxboot and topScript.hw to topscript.hw. Unfortunately still no luck - I still get stuck at the same step.
-
I haven't updated the .sn and .key files in the vxboot directory yet (they're still set for my TDS7104). Not sure if that's a problem.
-
It seems a few other people have been stuck at this stage in the boot sequence and the "L" LED diagnostic. One suggestion was to make sure all the drivers are complete and one individual provided a "Tektronix" folder. From a quick look, I think mine is ok. Here's the full file listing:
Tektronix
├── Adobe
│ └── AR505enu.exe
├── Audio 5.10.3686
│ ├── 5.10.3686.certified.exe
│ ├── data1.cab
│ ├── data1.hdr
│ ├── data2.cab
│ ├── delcabs.bat
│ ├── iac97k4.sys
│ ├── iac97u4.dll
│ ├── ich
│ │ ├── nt4
│ │ │ ├── iac97k4.sys
│ │ │ ├── iac97u4.dll
│ │ │ ├── oemsetup.inf
│ │ │ └── setupnt4.dll
│ │ └── wdm
│ │ ├── setuphlp.dll
│ │ ├── stac97.cat
│ │ ├── stac97.inf
│ │ └── stac97.sys
│ ├── ikernel.ex_
│ ├── layout.bin
│ ├── oemsetup.inf
│ ├── setup.bmp
│ ├── setup.exe
│ ├── setuphlp.dll
│ ├── setup.ini
│ ├── setup.inx
│ ├── setup.iss
│ ├── setupnt4.dll
│ ├── stac97.cat
│ ├── stac97.inf
│ ├── stac97.log
│ ├── stac97.sys
│ ├── stacconfig.exe
│ ├── stfindcs.sys
│ ├── stfndcsd.dll
│ ├── stfndcsv.vxd
│ └── st_inst.ini
├── Chips and Tech display V.2.50G
│ ├── Chips2Kd.dll
│ ├── chips2k.inf
│ ├── Chips2Km.sys
│ ├── CHIPSDAN.HLP
│ ├── CHIPSDEU.HLP
│ ├── CHIPSDSP.HLP
│ ├── CHIPSDSP.ICO
│ ├── CHIPSESP.HLP
│ ├── CHIPSFIN.HLP
│ ├── CHIPSFRA.HLP
│ ├── CHIPSITA.HLP
│ ├── CHIPSJPN.HLP
│ ├── CHIPSNLD.HLP
│ ├── CHIPSNON.HLP
│ ├── CHIPSPTB.HLP
│ ├── ChpGamma.dll
│ ├── ChpsPtrt.exe
│ ├── chpstart.exe
│ ├── CNTNTDSP.DLL
│ ├── desc.txt
│ ├── DISK1
│ ├── install.txt
│ └── LICENSE.TXT
├── ClickNBurn
│ ├── Autorun.dxr
│ ├── AUTORUN.INF
│ ├── CNBP2
│ │ ├── Autorun
│ │ │ ├── Ar.bmp
│ │ │ ├── Ar.exe
│ │ │ ├── Ar.ico
│ │ │ ├── Ar.ini
│ │ │ └── vssver.scc
│ │ ├── Autorun.inf
│ │ ├── Click'N Burn Pro 2.0 (English) Setup.exe
│ │ ├── Click'N Burn Pro 2.0 (French) Setup.exe
│ │ ├── Click'N Burn Pro 2.0 (German) Setup.exe
│ │ ├── Click'N Burn Pro 2.0 (Italian) Setup.exe
│ │ ├── Click'N Burn Pro 2.0 (Spanish) Setup.exe
│ │ ├── Readme.txt
│ │ └── Shortcut to Click'N Burn Pro 2.0 (English) Setup.exe.lnk
│ ├── CnD3d
│ │ ├── CUSTDATA.INI
│ │ ├── manual.pdf
│ │ ├── setup.exe
│ │ └── vssver.scc
│ ├── CnESLE
│ │ ├── setup.exe
│ │ └── vssver.scc
│ ├── PxEngineUpdate342.exe
│ ├── Serial Number.txt
│ ├── StompProjector.exe
│ ├── vdla
│ │ ├── DLA.msi
│ │ ├── HISTORY.BLD
│ │ ├── Ins9XMsi.exe
│ │ ├── InsNTMsi.exe
│ │ ├── mfc42.dll
│ │ ├── msvcrt.dll
│ │ ├── pconfig.dcf
│ │ ├── readme.txt
│ │ ├── Setup.exe
│ │ ├── Setup.ini
│ │ ├── urldata.ini
│ │ └── vssver.scc
│ └── vsb
│ ├── buildnfo.txt
│ ├── data10.cab
│ ├── data1.cab
│ ├── data1.hdr
│ ├── data2.cab
│ ├── data3.cab
│ ├── data4.cab
│ ├── data5.cab
│ ├── data6.cab
│ ├── data7.cab
│ ├── data8.cab
│ ├── data9.cab
│ ├── DATA.TAG
│ ├── drvwcdb.vxd
│ ├── fconfig.dcf
│ ├── HISTORY.BLD
│ ├── _INST32I.EX_
│ ├── _ISDel.exe
│ ├── lang.dat
│ ├── layout.bin
│ ├── license.ENU
│ ├── os.dat
│ ├── pconfig.dcf
│ ├── pnpninst.exe
│ ├── pnpwtape.exe
│ ├── readme.er
│ ├── readme.txt
│ ├── rptENU.zip
│ ├── _Setup.dll
│ ├── Setup.exe
│ ├── SETUP.INF
│ ├── SETUP.INI
│ ├── setup.ins
│ ├── setup.lid
│ ├── _sys1.cab
│ ├── _sys1.hdr
│ ├── urldata.ini
│ ├── _user1.cab
│ ├── _user1.hdr
│ └── vssver.scc
├── Embedded Console.ht
├── Front Panel V.1.0
│ ├── TekFPUsb.inf
│ └── TekFPUsb.sys
├── INF_Intel 82801DB ICH4
│ └── infinst_enu.exe
├── Intel Application Accelerator 2.3
│ ├── iaa23_enu.exe
│ └── Readme.txt
├── Lan 6.4C0735
│ ├── APPS
│ │ ├── PROSet
│ │ │ └── WIN2K
│ │ │ ├── 1028.mst
│ │ │ ├── 1030.mst
│ │ │ ├── 1031.mst
│ │ │ ├── 1033.mst
│ │ │ ├── 1034.mst
│ │ │ ├── 1035.mst
│ │ │ ├── 1036.mst
│ │ │ ├── 1040.mst
│ │ │ ├── 1041.mst
│ │ │ ├── 1042.mst
│ │ │ ├── 1043.mst
│ │ │ ├── 1044.mst
│ │ │ ├── 1046.mst
│ │ │ ├── 1053.mst
│ │ │ ├── 2052.mst
│ │ │ ├── ANSMW2K.INF
│ │ │ ├── ANSMXP.INF
│ │ │ ├── ANSPW2K.INF
│ │ │ ├── ANSPXP.INF
│ │ │ ├── iansmsg.dll
│ │ │ ├── iansw2k.cat
│ │ │ ├── iansw2k.sys
│ │ │ ├── ianswxp.cat
│ │ │ ├── ianswxp.sys
│ │ │ ├── PROSet.exe
│ │ │ ├── PROSet.msi
│ │ │ └── s8023Dev.Reg
│ │ ├── SETUP
│ │ │ └── SETUPBD
│ │ │ └── W98-XP32
│ │ │ ├── NetInst.dll
│ │ │ ├── SetBDRes.dll
│ │ │ ├── SetupBD.exe
│ │ │ └── SetupBD.ini
│ │ └── TOOLS
│ │ ├── DIAG1000.EXE
│ │ ├── diag100.exe
│ │ ├── IDADAPT.EXE
│ │ └── IDADAPT.TXT
│ ├── license.rtf
│ ├── MakeDisk
│ │ └── Make2KXP.bat
│ ├── PRO100
│ │ ├── WIN2K
│ │ │ ├── e100bmsg.dll
│ │ │ ├── e100bnt5.cat
│ │ │ ├── e100bnt5.din
│ │ │ ├── e100bnt5.inf
│ │ │ ├── e100bnt5.sys
│ │ │ ├── intelnic.dll
│ │ │ └── PROUnstl.exe
│ │ └── WINXP32
│ │ ├── e100b325.cat
│ │ ├── e100b325.din
│ │ ├── e100b325.inf
│ │ ├── e100b325.sys
│ │ ├── e100bmsg.dll
│ │ ├── intelnic.dll
│ │ └── PROUnstl.exe
│ ├── PRO1000
│ │ ├── WIN2K
│ │ │ ├── e1000msg.dll
│ │ │ ├── e1000nt5.cat
│ │ │ ├── e1000nt5.din
│ │ │ ├── e1000nt5.inf
│ │ │ ├── E1000NT5.SYS
│ │ │ ├── intelnic.dll
│ │ │ └── PROUnstl.exe
│ │ └── WINXP32
│ │ ├── e1000325.cat
│ │ ├── e1000325.din
│ │ ├── e1000325.inf
│ │ ├── E1000325.sys
│ │ ├── e1000msg.dll
│ │ ├── intelnic.dll
│ │ └── PROUnstl.exe
│ ├── Readme.txt
│ ├── RelNotes.rtf
│ ├── Setup.exe
│ ├── v6.4_PRO2KXP_only.exe
│ └── verfile.tic
├── Semtec Touch Screen Calibrator V.1.00.70.1
│ ├── CALIBR.CPL
│ ├── INSTALL.EXE
│ ├── rathook.dll
│ ├── RATPTR.EXE
│ ├── TSCREEN.INF
│ └── TSCRLF.SYS
├── Tektronix Custom Drivers
│ └── v 1.11 Service
│ ├── dbfs.sys
│ ├── dblib.sys
│ ├── dbWdm.inf
│ ├── dbWdm.sys
│ ├── DIOSERVICE.exe
│ └── Readme.txt
├── tvia
│ ├── dpms.scr
│ ├── igscp.ini
│ ├── IGSDISP.dll
│ ├── IGSMINI.sys
│ ├── IGSMM.SYS
│ ├── IGSMW32.500
│ ├── IGSMW32.520
│ ├── IGSMW32.522
│ ├── IGSMW32.530
│ ├── IGSMW32.560
│ ├── igspsp.dll
│ ├── IGS_TEK.INF
│ ├── IGSVCAP.SYS
│ ├── README.TXT
│ ├── RMIGAVID.500
│ ├── RMIGAVID.520
│ ├── RMIGAVID.522
│ ├── RMIGAVID.530
│ ├── RMIGAVID.560
│ ├── TVIAHLP_tek.cnt
│ ├── TVIAHLP_tek.HLP
│ ├── Tviahlp_x86.cnt
│ ├── Tviahlp_x86.HLP
│ ├── TviaHook.dll
│ ├── TVIA_MV.500
│ ├── TVIA_MV.520
│ ├── TVIA_MV.522
│ ├── TVIA_MV.530
│ └── TviaSrv.exe
├── ver 30518p
│ ├── installnotes.doc
│ ├── MAINDIR1.cab
│ ├── readme.txt
│ ├── Setup.exe
│ └── SYSDIR1.cab
├── Version P16 Bios
│ └── BIOS FILES
│ ├── AUTOEXEC.BAT
│ ├── BEEP.COM
│ ├── BIOS.REC
│ ├── DESC.TXT
│ ├── DISKIMG.EXE
│ ├── EXECUTE.BAT
│ ├── IFLASH.EXE
│ ├── LICENSE.TXT
│ ├── LOGODATA.USR
│ ├── Make a P16 Disk.IMA
│ ├── P16-0040.BI1
│ ├── P16-0040.BI2
│ ├── P16-0040.BI3
│ ├── P16-0040.BI4
│ ├── P16-0040.BI5
│ ├── P16-0040.BI6
│ ├── P16-0040.BIO
│ ├── P16-0040.ITK
│ ├── P16-0040.SIG
│ ├── README.TXT
│ ├── RUN.BAT
│ ├── SW
│ │ ├── DESC.TXT
│ │ ├── DISKIMG.EXE
│ │ ├── LICENSE.TXT
│ │ ├── LY86AP16IB.EXE
│ │ ├── P16-0040.ITK
│ │ ├── README.TXT
│ │ ├── RUN.BAT
│ │ └── SW.EXE
│ ├── SW.EXE
│ └── TOKEN
└── Video_Intel Extreme Graphics 6.13.01.3317
├── autorun.inf
├── Graphics
│ ├── data1.cab
│ ├── data1.hdr
│ ├── data2.cab
│ ├── ikernel.ex_
│ ├── Install.cfg
│ ├── layout.bin
│ ├── Setup.exe
│ ├── Setup.ini
│ ├── setup.inx
│ ├── setup.iss
│ ├── Support
│ │ ├── shpshftr.dll
│ │ └── SignTime.dll
│ └── Win2000
│ ├── a302.cat
│ ├── a302.inf
│ ├── a302.sys
│ ├── a303.cat
│ ├── a303.inf
│ ├── a303.sys
│ ├── a304.cat
│ ├── a304.inf
│ ├── a304.sys
│ ├── a305.cat
│ ├── a305.inf
│ ├── a305.sys
│ ├── a306.cat
│ ├── a306.inf
│ ├── a306.sys
│ ├── a307.cat
│ ├── a307.inf
│ ├── a307.sys
│ ├── a308.cat
│ ├── a308.inf
│ ├── a308.sys
│ ├── a309.cat
│ ├── a309.inf
│ ├── a309.sys
│ ├── a310.cat
│ ├── a310.inf
│ ├── a310.sys
│ ├── a311.cat
│ ├── a311.inf
│ ├── a311.sys
│ ├── a312.cat
│ ├── a312.inf
│ ├── a312.sys
│ ├── hccutils.dll
│ ├── hkcmd.exe
│ ├── i830mnt5.cat
│ ├── ialmcoin.dll
│ ├── ialmdd5.dll
│ ├── ialmdev5.dll
│ ├── ialmdnt5.dll
│ ├── ialmgdev.dll
│ ├── ialmgicd.dll
│ ├── ialmkchw.sys
│ ├── ialmnt5.inf
│ ├── ialmnt5.sys
│ ├── ialmrem.dll
│ ├── ialmrnt5.dll
│ ├── ialmsbw.sys
│ ├── igfxcfg.exe
│ ├── igfxcpl.cpl
│ ├── igfxdev.dll
│ ├── igfxdgps.dll
│ ├── igfxdiag.exe
│ ├── igfxdo.dll
│ ├── igfxeud.dll
│ ├── igfxhara.lhp
│ ├── igfxharb.lhp
│ ├── igfxhchs.lhp
│ ├── igfxhcht.lhp
│ ├── igfxhcsy.lhp
│ ├── igfxhdan.lhp
│ ├── igfxhdeu.lhp
│ ├── igfxhell.lhp
│ ├── igfxheng.lhp
│ ├── igfxhenu.lhp
│ ├── igfxhesp.lhp
│ ├── igfxhfin.lhp
│ ├── igfxhfra.lhp
│ ├── igfxhfrc.lhp
│ ├── igfxhheb.lhp
│ ├── igfxhhun.lhp
│ ├── igfxhita.lhp
│ ├── igfxhjpn.lhp
│ ├── igfxhk.dll
│ ├── igfxhkor.lhp
│ ├── igfxhnld.lhp
│ ├── igfxhnor.lhp
│ ├── igfxhplk.lhp
│ ├── igfxhptb.lhp
│ ├── igfxhptg.lhp
│ ├── igfxhrus.lhp
│ ├── igfxhsve.lhp
│ ├── igfxhtha.lhp
│ ├── igfxhtrk.lhp
│ ├── igfxpph.dll
│ ├── igfxrara.lrc
│ ├── igfxrarb.lrc
│ ├── igfxrchs.lrc
│ ├── igfxrcht.lrc
│ ├── igfxrcsy.lrc
│ ├── igfxrdan.lrc
│ ├── igfxrdeu.lrc
│ ├── igfxrell.lrc
│ ├── igfxreng.lrc
│ ├── igfxrenu.lrc
│ ├── igfxresp.lrc
│ ├── igfxress.dll
│ ├── igfxrfin.lrc
│ ├── igfxrfra.lrc
│ ├── igfxrfrc.lrc
│ ├── igfxrheb.lrc
│ ├── igfxrhun.lrc
│ ├── igfxrita.lrc
│ ├── igfxrjpn.lrc
│ ├── igfxrkor.lrc
│ ├── igfxrnld.lrc
│ ├── igfxrnor.lrc
│ ├── igfxrplk.lrc
│ ├── igfxrptb.lrc
│ ├── igfxrptg.lrc
│ ├── igfxrrus.lrc
│ ├── igfxrsve.lrc
│ ├── igfxrtha.lrc
│ ├── igfxrtrk.lrc
│ ├── igfxsrvc.dll
│ ├── igfxtray.exe
│ ├── ikch8xx.cat
│ ├── ikch8xx.inf
│ ├── isb8xx.cat
│ ├── isb8xx.inf
│ ├── oemdspif.dll
│ ├── shpshftr.dll
│ ├── vch.cat
│ ├── Vch.inf
│ ├── Vch.sys
│ ├── wa301a.cat
│ ├── wa301a.inf
│ ├── wa301a.sys
│ ├── wa301b.cat
│ ├── wa301b.inf
│ └── wa301b.sys
├── ReadMe.txt
└── win2k_xp.exe
Also, the official OS restore CD should have all the requisite drivers.
-
I noticed some of the boot parameters look a bit off:
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
In addition to the changed capitalizations, I think those should be backslashes. Unfortunately, using 'c' to change boot parameters doesn't persist.
-
I tried changing them to exactly what TiN had in his post, (and then using '@' to boot), but no luck.
-
L code from : https://xdevs.com/fix/csa7404/ (https://xdevs.com/fix/csa7404/)
EDIT see the last lines of this thread message
real strange, the cd-rom you got, can you lauch the installer in admin mode, or something is funky ... it is supposed to install everything you need ???
But you talk about a bios version as a bare minimum ?? i dont know about this one ... do you have some infos ?
But the cd-rom listing show a P16 version of the bios, i think (not sure) but some versions bios goes up to the last who is "P25"
witch i have for the 7254 at my job (but the original Intel, not the TEK crippled/limitted one)
Stuck like this .... i would try something stupid as installing the tds7k TEK system files and see where it goes
have you checked in the device manager if all is ok, any exclamation mark, it could spoil everything ?? the pc side must be perfect ...
Is it me ? but seeing the cd-list, i dont see any TEK related installations, seems mostly like an driver CD ??
The ClicknBurn folder is intriguing ? is it to create more installation files ?
Or this folder : ver 30518p ??
I dont have any original tds7k cd-rom to compare ... but have al TEK files / drivers and the hdd backup
Ours 7254 is running on xp sp3 with some tweaks in the os to get rid of the junk, and running it in classic mode wich is less consuming in ressources
sorry if i lost some thread tracks loll or i repeat myself loll
------------------------------------------------------------------------------
https://xdevs.com/doc/Tektronix/CSA7404/ (https://xdevs.com/doc/Tektronix/CSA7404/)
Almost at the end you have : tds2.5.3_2008.06.09.10.42.00_5150_EN.exe
And 3x VxBoot folder archives or backup copies .....
OR
https://dev.xdevs.com/projects/csa7404/files (https://dev.xdevs.com/projects/csa7404/files)
------------------------------------------------------------
tds7k zipped file : https://www.jabse.com/dl2.php?file=L1Rla3Ryb25peC9DU0E3NDA0L1REUzcwMDAyay56aXA- (https://www.jabse.com/dl2.php?file=L1Rla3Ryb25peC9DU0E3NDA0L1REUzcwMDAyay56aXA-)
not sure if this one is a bull backup or setup files etc ....
It is an full os reinsallation iso and the win2k sp4 ...
-
My mistake, I've provided somewhat incomplete information about the installation CD and the resulting installation on the HDD. Here are links to the installation ISOs:
disk 1: https://drive.google.com/file/d/1BZwyrxn3TVarZnL3mOxXxlZpr7UYXGtQ/view?usp=sharing (https://drive.google.com/file/d/1BZwyrxn3TVarZnL3mOxXxlZpr7UYXGtQ/view?usp=sharing)
disk 2: https://drive.google.com/file/d/1jCqaUhgUN9EXMnqPsNRks5by8cXsn3HZ/view?usp=sharing (https://drive.google.com/file/d/1jCqaUhgUN9EXMnqPsNRks5by8cXsn3HZ/view?usp=sharing)
These were provided to me by Tektronix for BIOS Version LY84510A.86A.0040.P16. Tektronix informed me that the restore ISOs are particular to the BIOS revision number. I have another set of discs for which I don't know the BIOS version and which didn't work in my scope (the installation didn't complete). I can upload these too if people are interested.
FYI I may not keep these up here forever, but if someone reads this in the future and wants copies, send me a personal message, I should still have them.
The directory listing I provided earlier was only of the Tektronix folder, not the rest. I've attached a file that includes the full, recursive file listing. This is not the same thing as the installation ISOs. This is what is created on the HDD after performing the installation with those ISOs.
have you checked in the device manager if all is ok, any exclamation mark, it could spoil everything ?? the pc side must be perfect ...
Can you clarify how to do this? Don't I need to have a running Windows to open the device manager? I never get to the Windows boot stage. Maybe there's another way to accomplish this?
https://xdevs.com/doc/Tektronix/CSA7404/ (https://xdevs.com/doc/Tektronix/CSA7404/)
Almost at the end you have : tds2.5.3_2008.06.09.10.42.00_5150_EN.exe
And 3x VxBoot folder archives or backup copies .....
OR
https://dev.xdevs.com/projects/csa7404/files (https://dev.xdevs.com/projects/csa7404/files)
------------------------------------------------------------
tds7k zipped file : https://www.jabse.com/dl2.php?file=L1Rla3Ryb25peC9DU0E3NDA0L1REUzcwMDAyay56aXA- (https://www.jabse.com/dl2.php?file=L1Rla3Ryb25peC9DU0E3NDA0L1REUzcwMDAyay56aXA-)
not sure if this one is a bull backup or setup files etc ....
It is an full os reinsallation iso and the win2k sp4 ...
Thanks I'll take a look through these and see what differs from my system and see if I need to copy over drivers etc. It still seems a bit weird to me that the official installation ISO contains some drivers but not all the requisite ones (esp when the rep at Tektronix insisted it should contain all drivers). But, worth a shot.
The thing I'm hung up on now is that boot parameters look subtly wrong and I'm not able to change them in a way that persists. If the battery had died I would expect the info to be garbled. Not sure what's up there.
Anyway I won't have time to test these things until tonight, but I'll post back this evening with any findings from this. Thanks for the help. And please do clarify how to use the device manager if you can! That sounds like it would be very useful to check driver status.
-
You mean windows does not boot completly ??
Hum well
i would say, format everything, re-install everything, be sure the OS is fully operational, and install the tek stuff after being sure you dont have any problems in the device manager
the device manager can be called on a desktop shortcut, create a shortcut and for the properties you write devmgmt.msc
it will create an icon on your windows desktop, and you'll be able to see if there is problems with drivers installation ...
The known problem with the p16 bios was the graphic (even mentioned here on another thread) initialization in the bios, sometimes it would not set to internal PCI ... that was resolved on the P25 ...
-
You mean windows does not boot completly ??
Hum well
i would say, format everything, re-install everything, be sure the OS is fully operational, and install the tek stuff after being sure you dont have any problems in the device manager
Correct, Windows doesn't boot at all. It sounds like the OS installation discs I have aren't working. Weird. The Tek rep indicated this has worked many times before. What do other people do? Install generic Windows 2k PRO SP4 and then populate drivers and vxBoot as needed? I can try that.
The known problem with the p16 bios was the graphic (even mentioned here on another thread) initialization in the bios, sometimes it would not set to internal PCI ... that was resolved on the P25 ...
I think the Tek rep mentioned this too and I checked it and it was fine. Is it worth trying to update the BIOS to P25? I'm a bit nervous to mess around with the BIOS.
-
do you have opened the scope to physically check the motherboard capacitors ?? they could play some tricks, and they are not easy to change ...
ill check the 2 links you provided
Hum made by powerquest, and the second iso as one file mentioning tds5k in it ???? not even sure it's the good images for your scope ?
I would redo a full os install say from an genuine w2k cd-rom, or the tds7k zip file link i've sent you, you have an os iso in it and the w2k sp4 in it, even the os serial is there ...
Burn an cd-rom at 4x ... low speed
For the serial you should have the sticker on the casing
Your posted cdrom listing / index / folders have the needed drivers you will be able to use
Normally you will need the vga drivers, the touch screen drivers, front panel drivers, lan, audio, ICH (intel chipset) ... and the one for the TVIA board something loll
the p25 bios can be upgraded from a windows os ... if i recall it can wait until you have a fully working os
Do you have a separated "normal" ATX computer board and a agp/pci slot separated interface board, or you have one edge of the mainboard who slot in a backplane board on the side
I'm sometimes confused between the A and B models, since you wrote an non B model loll
But OS side is the same
If the cd-rom is ok you should be able to boot from it ... win2k ones where bootable if i recall
If you finally manage to get a os boot
Xdev's tds7000 non B softwares and drivers ??
https://xdevs.com/doc/Tektronix/TDS7000/ (https://xdevs.com/doc/Tektronix/TDS7000/)
https://www.tek.com/en/support/software/firmware/csa7000-and-tds7000-series-firmware-upgrade-v253 (https://www.tek.com/en/support/software/firmware/csa7000-and-tds7000-series-firmware-upgrade-v253)
but i have sent you a link for this one, you need an free tek registration to get it.
Or
https://dev.xdevs.com/attachments/591 (https://dev.xdevs.com/attachments/591)
tds2.5.3_2008.06.09.10.42.00_5150_EN.exe
-
ill check the 2 links you provided
Hum made by powerquest
and one file mention tds5k in it ???? not even sure it's the good images for your scope ?
Where are you seeing tds5k? I checked the ISOs and HDD after installation and don't see anything about tds5k. Mind clarifying? I do see a folder on the installed HDD labelled "Version P16 Bios" which makes me think these are the correct installation ISOs. Or at least correct for the BIOS version.
I would redo a full os install say from an genuine w2k cd-rom, or the tds7k zip file link i've sent you, you have an os iso in it and the w2k sp4 in it, even the os serial is there ...
Ok thanks, I'll try that and let you know when I'm back in front of the scope tonight. As for the zip file, are you sure that's complete? I'm seeing this when trying to unzip:
$ unzip TDS70002k.zip
Archive: TDS70002k.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of TDS70002k.zip or
TDS70002k.zip.zip, and cannot find TDS70002k.zip.ZIP, period.
Burn an cd-rom at 4x ... low speed
For the serial you should have the sticker on the casing
Your posted cdrom listing / index / folders have the needed drivers you will be able to use
Normally you will need the vga drivers, the touch screen drivers, front panel drivers, lan, audio, ICH (intel chipset) ... and the one for the TVIA board something loll the one who link the scope side to the pc ...
the p25 bios can be upgraded from a windows os ... if i recall it can wait until you have a fully working os
This is all very helpful, thanks! I'll try the installation this way.
Do you have a separated "normal" ATX computer board and a agp/pci slot separated interface board, or you have one edge of the mainboard who slot in a backplane board on the side
I'm sometimes confused between the A and B models, since you wrote an non B model loll
But OS side is the same
If the cd-rom is ok you should be able to boot from it ... win2k ones where bootable if i recall
Xdev's tds7000 non B softwares and drivers ??
https://xdevs.com/doc/Tektronix/TDS7000/
This is a "B" version, so I think some of the drivers will be different from eg TiN's. But I'll start with the OS and then worry about the drivers when I'm able to boot into w2k.
Thanks again! I'll keep you posted.
-
you have a "rem tds5k" note in the autoexec.bat of the second iso file you provided
@ECHO OFF
REM Use for TDS5K Ashland
the tds70002k.zip file open correctly in peazip archiver i use ????
oooohhh k it is a B version loll Normally you start the os, install everything (drivers) and you use the v2.5.5 and v5.13 firmware file from TEK who is the latests ones
TDS7104_7054_V2.5.5_066031808.exe
tds7154b_tds7254b_tds7404b_csa7404b_firmware_v5.1.3_066050014.exe
can't remember the installation order loll
that's what i did when our 7254 slightly crashed, dead dallas DIP model .. and an os corruption, that's why i've talked about XP Sp3 ...
And the Intel non TEK branded bios, since i needed more bios settings .... with the TEK you can not do DEL to enter the bios until you do a killcmos to bring the bios settings
BF86510A.86A.0077.P25.IB.exe
And i don't care if the TEK logo is not there loll
-
you have a "rem tds5k" note in the autoexec.bat of the second iso file you provided
@ECHO OFF
REM Use for TDS5K Ashland
Oh, that's from the TDS7104(A) I have. That one is working fine and I was using it as an (imperfect) point of comparison for the CSA7404B. I have no idea about the installation on the TDS7104 as I didn't do that myself - it was working fine when I received it.
autoexec.bat is completely empty on the CSA7404B.
-
I tried a stock w2k sp4 installation ISO but I still can't get past the same step. I'll try with the installation ISO from the zip next. It doesn't look like the problem is with vxworks.st or topscript.hw in vxboot as, judging by what others have posted, those are loaded/executed later.
-
have you inspected the internals ? mobo capacitors etc ... try another ram stick ... youre not supposed to have installation problems, unless the computer side has problems
Ide drive ? try another ?
Ram
Capacitors
try a cmos reset on the mainboard
pull out the mobo on a vench and try to install as a pc ??
-
Good call. 4 caps on the microATX board are bulging and none of them (desoldered) measure like a cap anymore. Parallel DC resistance across all of them is a steady 8ohms. I don't have these on hand so I'll need to order some, but I'll report back when I've replaced them.
I powered up the board externally (caps still in circuit) and measured 1.47 VDC across those caps. I'm not sure if that's what it should be. Ripple didn't seem that high - about 7 mVrms.
After desoldering all 4 visibly bulging caps there's still about 8ohms across the rail. The yellow caps appear to be wired in parallel. I wonder if one or more of those is bad too.
-
Actually, I measured the parallel impedance of all the remaining (yellow) caps. I think there are 6 of these and are nominally 560u 4V. This plot looks fine to me, so I'm not sure the DC resistance I measured with a DMM is indicative of a problem. I'm ordering some anyway just in case though. Still, the 4 bulging caps are definitely bad and will be replaced.
-
Well I replaced those caps but still no luck. I also replaced the microATX battery, which had died. I'm still getting stuck at diagnostic LED "L".
I tried installing windows directly onto the microATX from the bench. I used the official tektronix installation and it didn't work. Same symptom: I just see a blinking cursor when I try to boot into Windows. I don't think it would be the RAM that's causing this as the Windows installation procedure works at least to some extent.
I did notice a bit of a weird symptom where if I leave the battery in circuit, after installation the microATX CPU fan doesn't turn on and I think maybe the CPU doesn't either. When I remove it I can boot, but still never run Windows from the HDD.
-
I have a TDS7104 with Win98. A couple years ago it would spontaneously turn itself on so I unplugged it, guessing it may be a CMOS battery issue. Yesterday, before powering up again, I opened it up, pulled out the coin cell but found it to be 3V, so I put it back. Thought that while it was open, I'd backup the hdd. So I proceeded to dd the 6GB hdd to an image file, then put the disk back and power up. That's when the trouble began.
Presently, i have no display out either VGA port. It was displaying a few messages out the NLX but wouldn't let me get into Setup. The Entering Setup message would flicker and wouldn't go into the menus, but display a message (I forget now about) something about PXE boot. Keyboard was working, but now I don't get any clicking sounds when I hold down a key.
The hdd reads fine on a Linux dongle.
On the PPC, I am stuck at "L" On the debug console, I get to:
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
I don't get the second "done" or anything beyond. Where to go from here?
Update: I moved the hdd to the DVD cable and got two beeps from the bios. I moved it back and now I've got VGA again from the NLX. The error message is from Intel LANDesk:
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting LANDesk (R) Service Agent II
Still stuck on "L" and "Backplane anchor at 0x1e80000... Attaching network interface sm0... done"
Also, the F2 to enter setup displays rapidly flickering text "Entering Setup" for a second or two but doesn't go into Setup. I've seen others describe this same behavior, but can't find any resolutions.
When I boot an MSDOS floppy, "dir C: " gives me "Invalid drive specification". I tried booting from floppy and a different hdd and got the same response.
-
Seems you lost some bios settings i think, thats why in some posts, i put the latest intel variant to get all the original options, the TEK branded bios has crippled features ...
On some cases you have to use killcmos to bring the bios into an error and play in it
you have to get the settings right, to boot properly
had fun for a few hours just for the damn lcd config on a B model
-
Thanks for the reply, coromonadalix. I can't find killcmos - was going to try that... It's been removed for download from a number of locations and labeled a trojan in others.
But is it OK to flash a standard bios? My bios is 4B4LZ0XA.86A.0007.P04.9904191150.
I also find it very puzzling that no disk I try gets recognized. I even tried a win98 boot floppy, boot with CD drive option and it tells me there is no optical drive found. Is the PPC holding onto a bus or something of the sort?
Also, I think I read somewhere that there's a way to disable the PPC and just run the NLX board but I can't find anything on how to do. Since nothing I attach to the PATA bus gets recognized, that might help with the diagnosis.
- confused and tired :P
-
https://www.majorgeeks.com/files/details/killcmos.html (https://www.majorgeeks.com/files/details/killcmos.html)
windows or the browser will block it, just allow it .... never had problems with this site, my killcmos come from them
If evything is okay, no disconnected wires etc .... it should be a matter to pitch in the good hdd specs, find you drive sectors / platters / etc .. and manually enter it
did you change the master slave jumper ??
in the bios you may have primary and secondary ide settings ?? i think you can use the motherbaord outside the scope with an external psu, and see if it works
are the capacitors goods on the mobo, not buldged in anyways ?
-
No Crap-acitors today. I ran killcmos and got into bios finally. Thanks. Now when I boot, I get "Incorrect System! Press any key to reboot"
:P
-
find the magic recipe for the drive ... until it sees it, is there an auto detect mode in the ide / hhd bios settings ?
-
Up and running! All I changed in CMOS was date/time and AGP -> PCI. (HDD was autodetect) It then came alive. :-+
Thanks for the help
Update: It's dead, Jim. Won't even power up now. Clicks off in a second. :--
Update 2: Never give up! I tore it apart, yanked the PS to look for bad caps, found nothing. Put the PS back and tested it w/o the NLX board (there's a debug/pwron jumper on the PPC board). The power came on and the status was a ".8" on the 7seg LED. Put the NLX board back and it booted up again into a working scope. I was at this point before, then I put the case on and it wouldn't boot. I'll update after i inspect the interconnect boards under uScope then reassemble with case. Before I reassemble, I'm going to install a db9 on the back panel connected to the PPC. :-+
Update 3: Cut a hole in the chassis for a db9 - when I went to reassemble, it collided. Oops. Cut it a second time vertically and covered most of the mistake with aluminum tape. Doesn't look too bad and works great! I bought a Win7 upgrade kit from stlabs on eBay (SU810, PIII, DVD drive, 32G PATA SSD s/w preinstalled). They have a stripped down version of Win7 that boots up in reasonable time and gives me network access. Wasn't working at first, various behaviors. I contacted the seller and he suggested the riser to the NLX is fussy.
After some measurements, I found that the board wants to be parallel to the mounting plane at about 0.210" from the plate to the board bottom. This makes the card edge go into the connector without any stress with the connector at its correct position. After careful remounting, all problems are gone and it runs like a champ!
[attach=2]
-
Good morning,
I've had a TDS 8200 for a month that wouldn't start. The problem was with the motherboard (leaky capacitors). At the same time I went through this discussion thread and checked the battery of the ppc card thinking that it was soldered on the chip so I removed the cover thinking that it was only a cover. what a disappointment when once removed I see that the battery is attached to the cover :palm: There, I understand that the data from the chip is now gone somewhere in paradise...
Confirmation when booting unit that hangs on Tektronix software boot image. Although having acquired knowledge for repair from a hardware point of view, as far as programming is concerned, I am a beginner. I found thanks to this discussion thread how to establish a connection between my TDS and my pc via the rs232 and the J790 connector. I use as monitoring software: Advanced serial port monitor. For a week I have tried to enter various commands without success to date. Compared to what is mentioned several times throughout this discussion, I couldn't find the folder and file like many of you: c:/vxboot/vxWorks.st
I've only found this that comes closest: c:\Program Files\TDSCSA8000\Firmware\vxWorks.st
Copy my console log as it was before I started playing with it.
auto-booting...
Error in boot line:
¼ÿ.þ.çðk÷N¼¯ºŒ&Ô©d‰rãaÕo.°¯2‚?È•gµ~¹ÇÙÿ.¯.ᦽ‘÷‘ÈC..̪€.¦WQÛîu²œ.Ø.¯«pK¦ŸF
H…&¢§ÿ1ÀOé.‘.N.
¿Ëî“Ÿ_.ØÏ|ÞÜ×x%td!´bqWöIù.Ê.Ð.B.RîRSçiÔ÷Ž"ÂÌ%”R:RZGN]J¿ú°`&Ò[
¥ìƒ^…òÏ“¾Û.ôr±Ý—ð².ætƒTc¥½ŽoNæ.ŽÍccv_.•[ÿ«S2.Ô./æ .>—$i.êë€..̃ükDg§!tûϸÖmÄZÂT@:Ï0.½Æ7>
^
Can't load boot file!!
[VxWorks Boot]: Starting at 0xfff00100...
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
Creation date: Jul 26 2002, 10:13:07
Press any key to stop auto-boot...
7
6
5
4
3
2
1
0
Here are the system properties:
(https://i.postimg.cc/fyPfkkVd/20230423-133318a.jpg)
Where can I find this vxworks folder ?
(https://i.postimg.cc/BQ0SWBZf/Hard-disk.jpg)
(http://)
By this message I hope to find a help, thank you in advance. To read to you.
-
I dont think you have more hdd partitions
Normally vxWorks sit on the C:\ or root if i may say
Can you re-install the scope software ? dont know for the 8000 series
and we see after the auto booting message you have garbage ... corruption issues / file issues
I dont think just loosing the battery would cause this ? our tds7254B still booted after the dallas died on me ? sure the cal will take a hit, but you should be able to do an spc check ??
-
Thank you for the answer. I'm not at all familiar with command lines. I'm playing a little sorcerer's apprentice to tell you the truth...
For me I only have the vxWorks file found here:
(https://i.postimg.cc/NGyQwdr5/Tree-structure-complete.jpg)
-
By carrying out multiple tests I managed to partially load the program but it stops as shown in the quote below. :-// Does anyone understand what this means ?? I don't have a topscript file on my disk ??!!
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
done.
Attaching network intPC1 dio device driver installed
erface lo0... done.
Attaching DIO client... done.
Loading c:\vxWorks.st...1771964
Starting at 0x200000...
Initializing backplane net with anchor at 0x1de0010... done.
Backplane anchor at 0x1de0010... Attaching network interface sm0... done
done.
PC1 dio device driver installed
Attaching network interface lo0... done.
Adding 6006 symbols for standalone.
=========
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 BPRB=412 BPRT=8 NBR=8 BO=0
nvfs: STATUS: Mounting existing NVRAM file system
KERNEL: THERMAL CONTROL INITIATED
Executing startup script c:\vxWorks.st ...
dbFsIoctl: invalid code 3
ELF...
syntax error
Done executing startup script c:\vxWorks.st
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
-> [/quote]
-
in 2019 on a thread answered by TIN
You need to use c:\vxBoot\topScript.hw in standard config.
??
https://www.eevblog.com/forum/testgear/tektronix-tds7104-scope-hang-on-splash-screen/ (https://www.eevblog.com/forum/testgear/tektronix-tds7104-scope-hang-on-splash-screen/)
-
Good morning,
thanks for the help !
I copied pasted the text displayed in the wen page of the indicated link; but I'm no further ahead. Maybe we could try to load the complete missing files. Could someone pass me the VxWorks Boot or vxboot folder and topscript.hw ??
-
goodmoring @Yroger swap out your NVram. 95% it died overtime, sure there lies part of your problem.
then run a clearDB ( see topscript) and you be good to go.. also check you 3v batteries on the MB boards. and swap them ;-)
-
My ppc battery is ok !!
nvram dallas acquisition board battery is ok !! This is what is displayed now. it looks like it's progressing...a little...
What is displayed in the last lines, I am not a programmer and I do not see what he is talking about ??
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (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:\dio_rst.vsh ...
dbFsIoctl: invalid code 3
################### topScript starts ###############################
cd "dbfs:c:/dio_rst.vsh"
value = 0 = 0x0
value = 0 = 0x0
"value" is overloaded - Please select:
1: value__C24RWHashDictionaryIteratorP13RWCollectable
2: value__C24RWCollectableAssociation
3: value__C24RWHashDictionaryIterator
4: value__24RWCollectableAssociationP13RWCollectable
Enter <number> to select, anything else to stop: new symbol "value" added to symbol table.
value = 0x1d90c00: value = 0 = 0x0
Done executing startup script c:\dio_rst.vsh
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!
then run a clearDB ( see topscript)
Where can i find it?
-
@Yroger
replace your NVram and follow the procedure as written many times here in the topic.
99% of al the weird messages and corruption while booting are Dallas - NVram related !!
these errors like in the log are NVRam related it is not only the battery which is important .. just swap out. the nvram
- booting -> re-enter the right bootsetting
- clearDB -procedure (topscript.hw) !! unhide system folders in windows and you l find vxboot dir in the root of c:\ ( make a complete copy before your edit anything )
- rebuild NVram content from you eeprom field cal. by booting few times and follow the debug what is happening.
after putting back the remark in line # clearDB..... 2 more reboots should do the work
btw post here your boot settings please. so we can check if they are good
-
Good morning,
as said previously I have no Vxboot folder on the hard drive even when displaying the hidden folders and files of the system !! Maybe it's named differently as the scope is from the 8000 series... I only found files that looked a bit similar in the firmware folder see below:
[url=https://ibb.co/jDwsdNf](https://i.ibb.co/1TXj3gQ/TDS8200.jpg) (http://<a href="https://ibb.co/jDwsdNf"><img src="https://i.ibb.co/1TXj3gQ/TDS8200.jpg" alt="TDS8200" border="0"></a>)[/url]
Thank you for help
-
ok.check in your boot settings after you connected to you debug port. with a terminal progr. and check if the correct files is set.
-
i have a TDS7154 for repair with option Available 60. displayed
i guess it is TDSET2 because ET2 is written on the back i have option software TDSET3 (TDSET2 is not downloadble anymore) but that does not clear my avail. 60 in the option screen does anybody still have the install file TDSET2 or know how to get rit of the available 60. in the option screen list. when using TDSET3 software.
is this a registry setting or something? where Ethernet Compliance is getting filled in?
i still have old OS (chinese version) where parts of the option are visible in some folders as tdset2 folder, what do i need?
-
i went for a second strategy taking the orginal disk (chinese W2K) and tried to change the language back to let say 0409 English US
i copied in the complete documents and settings from the english OS disk W2KSP3 so after a reboot i could read the most again.. apart from the logonscreen and the shutdown screen.
i tried to swap out the whole winnt\system32\config folder and yes that helped met getting the OS to english but my options were broken . grrrrr so now i am looking for how to easy change the loginscreen and shutdown screen.
is this a registry setting which i overlooked or do i need to swap some files? if yes which onces. .?
and not to forget i still haven t back my ascii set so no backshlash and more and chinese caracters so where can this be changed?
-
i think you should start all new and re-install everything ....
the tek software is still available for the 7k series, and you have updates files too to add into your installation, but for your option, maybe before going too far, an registry export should be good
ill check in the 7254 at my job
maybe some people here, can chime and check for this folder ??
@charlyD there is some tek option generator code here, python based ??
or
startup script c:\vxBoot\dio_rst.vsh ???
BUt if i recall was the options loaded thru vxboot topScript.hw file at boot stage ??
-
Hi why should i reinstall if this disk is working ok.
apart from drivers difference the disks are a sort of interchangable. which does not mean you don t have to do anything.
i don t have the W2K restore disks for the SF810 boards and the TDSet2 is not downloadable anywhere i found in the manual from TDSet3 you need to uninstall TDSet2 first but then it doesn t fill the option Ethernet Compliance or whatis called.
so the chinese pre-install works great, with a small last little problem the correct caracters and logon and shutdown in chinese. both are ok when i swap out the system32\config
so it must be in the registry hive somewhere. i will come back on this one as soon as it is fixed.
-
i think you should try to correctly install win2k language pack .... it should correct your keyboard login logout etc ...
ill poke in our scope later today or this week for tdset2 .... if you have this folder do you see some inf files ?? an executable ???
do you really need this option ?
for the registry, i'm not so sure it will be easy, normally you export all related registry keys in to a reg file and try to import it ... switching hive files is not simple, you need all the other drivers folders etc ... and you do it on an second computer with your bootable drive and you chineese one ... the scope os must not load ...
Im not sure (no pun intended) the win2k registry contains all you need, i think tekscope is seen as an application on top of windows, and contain all it need to work ... i think the secrets may reside in the VXWORK folder(s)
checking all the scripts etc ... may help you ???
-
Hi thanks for your reply. i tried the language packs already but will try again. i want to bring the unit to its original (options) state which is ST and ET2 . i exported parts of the registry already from the english US installed OS but i can not get the right part one way or another. things to do which if found on the web will not work .....yet. or let say it different i didn t find the right clue.
btw i even tried SP4 _english and changed some reg setting to 0409 but nothing
-
Sadly
TDS7254B on Xp Sp3
TDS7404 on Win98
both are TDSET3 ????
no setup file where laying around ?? :(
-
i fixed everything despide it took me a long time, i had to change the codepage from 936 back to 850 and the oemcp and acp in the registry and unstall the east asia lang. with the MUI language pack. but all English now and loaded wirh options .thanks for the help and your time @coromonadalix
-
did people here workput which option byte is which
in the keygen. i saw lots of reader.txt but most of them were tables and Keys from units. so directions are welcome.
i posted already here first two is 4m(long record length) , second two is ST and SM.
and for the rest i am curious...
-
hi everyone, really glad to learn from this thread. recently i got a tds7104,boot stop at the scope start screen,I use vxboot to reset and now it boots ok.
but self test ,it reports 521 factory cal integrity ,factory cal data error. I read the boot log,it seems that it can't open some cal file in C:\vxboot\calcon. And i checked in C:\vxboot\calcon, there do missed cal file named 1 to 8 and 15,could this be the cause of error 521? Can anybody share the files ? Or any other suggestion.
Error 521 is the EEPROM on the acquisition board has been corrupted. It's reference designation is U1052.
Here is a known good U1052 binary from a TDS7104. Obviously it won't have the correct constants for your scope, but it will get rid of the error.
Otherwise you'll need to have a proper calibration with adjustments done.
Thanks your U1502 binary files ,I fix my TDS7104 521 errors
:) :clap:
Thanks charlyd give me a lot guide and advices :popcorn:
Hey bg8aak, Good Morning, I sent you a private message, could you reply?
-
thanks for the compliment 😉.
can anybody help me with TDSSET2 and maybe other older options. i have both option CD/DVDs posted here on the evv.
but i am looking for separate options not on those cd/dvd.
which could be downloaden in the earlier days....
can you help me out so i can reinstall them. now they start but nothing happens i see a sort of opening the option and then disappear in the corner , no error is displayed so that ok.
may i can check some settings so al is in place?
-
do you mean theses on TEK ?? i have an account there and i have all of theses with
tds7704b_firmware_v5.1.3_066050111.exe main files for restoration / re-install
CSA7154-7404_TDS7154-7254-7404_2.5.3_066031605.exe fw upgrades
EthernetTestUtilitySetup_066079619 wich is tdsset3 if i recall
Jitter_App.exe
ProtocolTriggerandDecode.exe
TDSCPM2_v3_1_0.exe
TDSDDM2V3_0_1.exe
TDSDVD_V1_2_2.exe
TDSUSB2_Setup_066140005.exe
TDSVNM.exe
would you post your link for your cd roms option / files ??
-
yes that is right but i specially mean :
TDSPWR2 NOT 3
TDSET2 NOT 3
-
only thing so far on tek
DPOPWR Advanced Power Analysis Solution for
DPO7000C, DPO-MSO5000, DPO-MSO5000B,DPO-DSA-MSO70000C, DPO-DSA70000D, MSO-DPO70000DX, DPO70000SX-Win7 - V10.1.2
Version: V 10.1.2
Release Date: 8/27/2017 12:00:00 AM
not being rude while i salute your tenacity
I think you ae chasing some ghosts of the past ?? tdsset3 as been out for a very long time
there is a seller on ebay who claim some recovery disk for many Tek models around 300 usd ?? wich is a rip off, and sadly there was some alternate tek ftp hosting sites who went down ...
and other sellers for some original tek disks BUT they dont list their content ??
-
Hi to All,
On this moment I am looking for the 063-3836-00: Operating System Restore Disk(s) Set for the CSA7000B, TDS7000B, TDS6000B and TDS6000C Series. Anybody who will share its image?
Greetings,
Calibrationfixture
-
[Solved] repairing a powerPc board i got this error i have replaced the nvram with a fram . can this be related to the swap ?
booting the unit doesn t give any error before the VxWorks logo part, and when i had a fram soldering fault a while ago on an other unit i got an error already in the beginning. after resoldering the fram that unit booted without errors anymore but this log looks different but i can be mistaken of course.
any suggestions?
today i fixed the powerPc board the problem was wfminit related. I guess this board had seen liquid /water...?! because tracks were corroded & broken , discovered under the microscope.
-
Hi all! I am repairing a TDS7054, and I am getting stuck at the the Loading phase of the PPC boot (L on the 7seg LED). Here is some context for my repair.
Originally, scope ran Win2000 and would boot into the OS, but TekScope would not start. 7seg showed .A, so after replacing the NVRAM chip and PowerCap, everything worked perfectly! I had ordered a compact flash card and IDE adapter, but just before I could copy everything, the hard drive died.
Now I've done a fresh install of WinXP SP3, and installed TekScope package and various drivers I've found. Now the PowerPC gets stuck at the L phase, and TekScope does not run.
I am missing a driver for 'Other PCI Bridge Device' in device manager, I am not sure if I need any other drivers or packages for the OS or PPC.
The PPC outputs up to here, and then gets stuck:
Press any key to stop auto-boot...
0
auto-booting...
boot device : sm
processor number : 0
file name : c:/vxboot/vxWorks.st
inet on backplane (b): 192.168.0.1:ffffff00
host inet (h) : 192.168.0.2
gateway inet (g) : 192.168.0.1
flags (f) : 0x1008
target name (tn) : tds7000
startup script (s) : c:/vxboot/topscript.hw
Initializing backplane net with anchor at 0x1e80000... done.
Backplane anchor at 0x1e80000... Attaching network interface sm0... done
Any help or download links would be amazing, thank you!
-
list your device pid / vid properties i have backup of many drivers
-
you miss your dioservice inter board driver. connects your powerPC board wirh your Intel board. it is called tektronix PowerPc or so i suggest to install v1.12 that is the latest. you have to install drivers located in the tektronix folder.
send me a dm. i will help you.
-
Hello! After digging around further on this thread I was able to find the PPC board driver :).
BUT I am still missing the Touch Screen drivers and calibration software if anyone has those pretty please!
Additionally I was able to recover data of the old Win2000 drive, so if anyone needs either hard drive image for Win2000 or WinXP just let me know. I can also send any drivers if you don't want to dig around in the forum for hours.
-
Good morning,
Has anyone ever encountered the following problem with a CSA8000:
When loading VxWorks at the 'boot device' line I get strange characters instead of 'SM' and obviously a little further on when loading it notifies me: 'Can't load boot file!!'
I tried the 'C' command but it jumps directly to the 'processor number' line every time !! The '_' command does not work for the boot device line. So I can't modify the boot device line. (the following lines can be modified without problem)
Anyone have a solution?
ps: Windows 98 starts normally and of course the Tektronix application remains frozen on the start page.
-
Good morning,
Has anyone ever encountered the following problem with a CSA8000:
When loading VxWorks at the 'boot device' line I get strange characters instead of 'SM' and obviously a little further on when loading it notifies me: 'Can't load boot file!!'
I tried the 'C' command but it jumps directly to the 'processor number' line every time !! The '_' command does not work for the boot device line. So I can't modify the boot device line. (the following lines can be modified without problem)
Anyone have a solution?
ps: Windows 98 starts normally and of course the Tektronix application remains frozen on the start page.
be sure to check any cr lf cr+lf commands sent when you type ?? or local echo may disturb you ... had to put it at off
had some problems in the console port of the tds7k im trying to revive ...
-
TDS7404 story
I'm doing an tug of war with an tds7404, the nvram died, read tons of threads trying to figure out the console port pins and how to recover / rebuild the nvram contents
I'm left with 2 unknown things in the nvram content, i can not find any infos about them, just different values... ?
flags (f) : 0x1000 seems ok ?
other (o) : nvfs=0x1000 had to put zero, if not, it would stall after vxWorks ascii logo
On the hardware side (Radsys su810 mobo, P9 bios), i can acces the bios with F2,
It's a mess trying to put 98 on this gimmick, cd-drom reject most modern cd-r burnt at 4x, i dont have any original w98 cd's,
Tried to boot on it with many tryouts by putting the floppy 1st, cd-rom in second etc ... no avail, even external usb dvd's not working ..... blah blah and i tossed 1 year ago tons of thoses drives, cd dvd ones grrrr |O
I swap primary vs secondary ide port, a more modern slim dvd-r will work, not the hdd drive (report bad size) 98 wont install ...
tons of hw related problems just because i dont have new ones or more recent ones to swap them lol
The most problems i have, is the touch screen drivers and the front panel drivers, i have many or same ones, no avail
Q : as some one have them ?? even tried one from a 7254 no avail ??
Xdev's site files are down, wich is very frustrating, there is a repo, but way incomplete
EDIT : apparently its not xdev's related ???
yesterday
I managed to get on Ebay for under 60$ an Gateway MX842 NLX mobo (Celeron 900 on it) used in gatweay E-3400 tower, this one has an intel 815 chipset (fsb 100 and 133) and has an beautiful nlx edge card with all modern standard 40 pins 2x ide ports, floppy, pci slots .... atx supply plug etc ...
This is the highest possible option : you have the Intel BL440Zx, the Radsys SU810, and i will try this one, i know the Radsys is working, doubts on the ide (very old) and the slim drive ....
I have on it an celeron 5xx Mhz who's slow as hell loll
For sure you can put an 1000/256/100 cpu on it but they are sold sometimes high $$$
If someone have th Fp panel drivers and Touch drivers .... and the Power Pc file (to compare)
Help
-
Xdev's site files are down, wich is very frustrating
When was the last time you checked?
-
Hi,
This is the new location of xdevs its Tektronix Documents:
https://xdevs.mymsk.cloud/doc/Tektronix/
Succes,
Calibrationfixture
-
yes i used the provided link, but things are missing from his csa7404 ... repair thread ....
anyway i'll redo everything again, maybe the cd-r i used was at 4x too fast ?
I just found from a friend, originals of w98 w2k and a few slim drives i had not thrown out loll ...
still confused about the nrvam contents, still no answers
flags (f) : 0x1000 i saw 1008 on some threads ??
other (o) : nvfs=0x1000 i used 0 ??
For sure i'll test the gateway board when i have it .... bit do my battle on the SU810 ... tds7404 with the old original powercap nvram
Is there an user with an 7404 who can show the boot process of the power pc board on it's console port ?
thks
aaaaand i search the : Semtec Touch Screen Calibrator V.1.00.70.1
-
This is the new location of xdevs its Tektronix Documents:
https://xdevs.mymsk.cloud/doc/Tektronix/
Just go here (https://doc.xdevs.com/) and register for access to the original.
-
oh damn never saw this page ... thks
request sent
a well learned lesson of not doing proper backups before the 7404 crashed, the 7254b was easy to restart ... vs this one ?? i did backup the vxWork folder but not took the log of the powerpc |O
i read about the motherboard pickyness on some instances ...
had to re-read the entire thread, still miss a few things ...
-
Hi again,
Thank you alm. Does it mean that the link I provided is "suspect" ?
Calibrationfixture
-
Thank you alm. Does it mean that the link I provided is "suspect".
I'm not sure. It's certainly not related to xdevs.com. As far as I know it's a copy made without knowledge of the xdevs.com team (of which I'm not a member). I don't know who made this copy. It's unlikely to be updated with new documents that are uploaded to xdevs.com given that sucking up all the bandwidth with downloading everything was the reason for taking down doc.xdevs.com in the first place.
-
Hello coromonadalix
You wrote:
be sure to check any cr lf cr+lf commands sent when you type ??
or local echo may disturb you ... had to put it at off
As said in a previous message I am not at all familiar with the commands what do you mean by turning off the local echo ??
Thanks for the help.
Below are the commands that appear on a csa 8000:
? - print this list
@ - boot (load and go)
p - print boot params
c - change boot params
l - load boot file@
g adrs - go to adrs
d adrs[,n] - display memory
m adrs - modify memory
f adrs, nbytes, value - fill memoryen
t adrs, adrs, nbytes - copy memory
e - print fatal exception,
n netif - print network interface device address
N - set ethernet addresNs
$dev(0,procnum)host:/file h=# e=# b=# g=# u=usr [pw=passwd] f=#
tn=targetname s=script o=other
Boot flags:
0x02 - load local system symbols
0x04 - don't autoboot
0x08 - quick autoboot (no countdown)
0x20 - disable login security
0x40 - use bootp to get boot parameters
0x80 - use tftp to get boot image
0x100 - use proxy arp
0x1000 - use dio to get boot image
available boot devices: feippc bp sm
[VxWorks Boot]: [VxWorks Boot]:
-
7404 scope non B model with tca adapters
hi because on some serial terminal softwares, some have local echo on by default and or other settings, you have to find the right ones
and it was messing the keyboard commands in my case
if everything is right, when you see the power pc log / console port going on, and you see an 10 9 8 7 6 5 4 .. countdown, normally any key press will stop the power pc booting process, it will simply halt
once done pressing "c" will enter the settings or re-write them correctly
this page will help you understand
https://xdevs.com/fix/csa7404/
or the 1st page of this thread by TIN
Sadly in all of our scopes stories, we have to fiddle a lot to find our answers, TEK forums, answers i gave and forgot etc ...
With tons of search, tests and tryouts, downloads etc ...
i'll know more in the next week if i'll be sucessfull
i have with members help got tons of drivers ... not sure if i have all of them
some mobo drivers etc ... found original win98se and win2k cd's, lots of slim drives etc ... Ghost files, Img files etc ...
and ordered some ide44 pins to sata interface converter from fleabay, i found out some 64gb industrial Sandisk ssd ...
Intel Chipset 815 Gateway MX842 NLX motherboard to push the pc side system to the max
man this scope take lot of ressources loll souvenirs and know how ... ooooold days
-
if everything is right, when you see the power pc log / console port going on, and you see an 10 9 8 7 6 5 4 .. countdown, normally any key press will stop the power pc booting process, it will simply halt
once done pressing "c" will enter the settings or re-write them correctly
So what you call "the echo" is when the startup program runs in a loop and to stop it you have to press a key when 12345...
So so far so good and I can change all the settings except the hard drive. I also did various manipulations without success.
-
settings like hardrive ?? the folder location ? physical drive exchange ?
you need to have a vxBoot folder on your c: drive
other people mentioned sometimes it had another name ...
normally on the drive root folder, check folder names .... and in it you will see an key file sn file calcon / calcons folder ...
and yes
it is normally hidden and sometimes read only, in windows you need to change the explorer settings to show hidden folders, i normally unhide it and remove the read only attributes
-
As soon as I can I will share the problem encountered.
Thank
-
hello! On working my CSA7154 post code LED is staying at '.A' and the screen was staying at TekScope application running. Can anybody tell me if this is an issue with NVRAM or something else? Thank you from the bottom of my heart！ :-[ :-[
-
I checked the manual, and the error with '.A' is Walk a one through NVRAM memory location. Cache is disabled. Walk a one through bus XPC_ISA_D. I don't understand what bus XPC_ISA_D is.
-
have you checked the nvram state, what model do you have ? show us photos
mine died, old powercap model and gave the same symptoms, stalled on tekscope boot
you need to have the power pc console port logs to know where it stalls, sure the led display helps but ... you may need to reconfigure the nvram ...
some said it died in some case, battery or the memory chip itself, in our tds 7254b it's the more modern dip version, we bought 2x of them, and put them on ic socket, and redo the nvram configs
but on a 7404, the same story happened but i'm in the progress or re installing everything, the Radisys SU810 mobo is very picky to the extreme, im waiting for original windows disks, does not accept burned ones ??
-
Thank you very much for your reply, I will try to check NVRAM. :) :)
I bought the DS9034PCX and the original model was a DS9034PC .
This photo is my original NVRAM.
-
When configuring NVRAM, does the motherboard need to be powered on?
-
ah that su cker loll i have this one who died on me, i cobled up an cr2032 coin cell socket further away and soldered wires into this nvram, you see the small rectangle notch on the top near the brown nlx connector, with an small flat screw driver you can pop the top off and see the insides
you will be able to check the battery voltage BUT DOING SO FOR SURE THE NVRAM CONTENTS WILL DIE if it is not already dead
and i hope the nvram is still good, some claimed defectives ones ...
and yes to reprogram it you need to power the scope
have an rs232 access thru a terminal software and the power pc board and redo some configs
on the 7404 i have "j790 markings" 10 pins idc connector normally found on the power pc board edge and i plugged an rs232 cable and a rs232 usb adapter
-
thank you for your reply!
I'll put in a new battery and do the NVRAM configuration on Monday.
Thank you again! :)
-
i would replace your NVram i had one which looked good still stange errors af swap errors gone. even better place a FRAM.
-
some familiar with this error, bad AG ?
acqEngVerifyTrigInfo: bad AG! demux = 2
-
I successfully connected the instrument! ! ! ! ! ! But I can't send the command. Can anyone tell me how to do this? :palm: :palm: :palm:
The picture is the information after I connected to the machine. The NVRAM looks like it has died.
-
check the 1st page of this thread
while the countdown goes to zero, not after, you have to stop it while pressing a keyboatd key / any key
and go like tin did
type "c" it will enter the commands, when pressing enter, it will go down 1 line by 1 line, if you do a mistake, you can redo them again, it will cycle all the way down and begin anew
-
I can't send any commands like "?" "c" .I don't know how to solve this problem. Yesterday's picture was just the machine booting up for self-test....
-
I tried several times and didn't see the countdown. I think configuring NVRAM is too difficult for me. :-// :-//
-
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...
Expected Value: 0x00000001
Actuall Value: 0x00000000
Location: 0xFD0E0000
romPost: NV-MEMORY Walking-one test failed.
The above is all the contents of the machine self-test |O
-
You won't be able to communicate with the scope until you replace the bad NVRAM. Communication isn't possible till the early self test passes.
-
oh!!! Thank you very much! ! !
-
Managed to get a tds7404 running, Radisys Su810 crap Mobo, 256mb of ram
I had to buy 2x hdd, i put one as the cd-rom substitute with all the needed stuff in it
Put an Celeron 1.1Ghz instead of the lousy 566 Mhz one, waiting for more ram
Installed win98se with tekscope 2.55 it works, but i have spc errors to iron out
EDIT now on Win Me and Tekscope v2.53
Made an raw image backup of win98se no tek installation(s)
This is what works for me in the nvram content
boot device : sm
processor number : 0
host name : host
file name : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.1: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) : 0x1000
target name (tn) : tds7000 -----> i've been told to keep it like this, if not, tekscope does'nt save some settings ??
startup script (s) : c:\vxBoot\topscript.hw
other (o) : 0x0
Still have doubts on the flags and other sections,
if i put something else in the flag like 0x1008, tekscope stalls
if i change other setting like 0x1000 tekscope starts but no traces of ch1 ch2 .....
For those who have low brightness on the lcd, you have to get the right chips tech 9000 drivers, in the advanced section you have gamma correction ...
I have searched tons of drivers and all i could find on xdev's site and help from others, all the iso's, windows installs etc ...
had to install unofficial usb drivers packages to get some usb keys to work, very picky on brand or storage sizes.
The touch screen is working as an HID device, i can not calibrate it ?? (slight offset, but workable) i have to dismantle the scope to check which company did the touchscreen interface on COM2 ??? not sure i want to go there ...
Win ME All seems to work, divers to find, mostly the video ones, the chip and tech 9000 is very important in my case, if not i got garbled traces, and low brightness (gamma set at 2.0) ??? attached here, picky on usb drives brands and sizes
Win2k I got hw resource conflict between the pcmcia slots and the lan interface (was discussed here) and Tekscope 2.5.3 or 2.5.5 would not give scope traces on the screen
XP Sp3 Stuck in a continuous boot loop an minus 39 minutes, absolutely can't finish the setup ?? even upgrading from Win ME or Win2k, I wanted to read the vid's and pid's of the hardware :--
Win7 as an extreme measure, not even sure that will work loll NOT
-----
Will try with an ordered motherboard based on intel 815 from a gateway e-3400 ... well see, for sure the motherboard metal frame need some mods, one more hole for an audio connector, and maybe one db9 port ???
EDIT Well its a pretty tight fit in length, the metal frame is not compatible for sure, the pcb is longer than the Radisys one, and sadly :-BROKE the scope doesn't want to power up, the led power button turn red, and this one would accept an 1.4Ghz Tualatin |O
Even on NLX standards, something must be missing for the gateway, maybe a supply line ?? it was a very low cost purchase :phew:
-----
Good infos here : https://github.com/exit-failure/tds7000/blob/main/NVRAM/README.md (https://github.com/exit-failure/tds7000/blob/main/NVRAM/README.md)
thks to this thread
https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/ (https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/)
to reformat some eeprom ... cleared some problems
all spc pass and self cal pass oooofffffffffffffffff what a ride
-
Copyright 1984-1996 Wind River Systems, Inc.
CPU: Tektronix HPP - PowerPC 740
Version: 5.3.1
BSP version: 1.0.3.0
Creation date: Jun 28 2000, 16:52:12
Press any key to stop auto-boot...
0
auto-booting...
There's no way I can make it stop! what should I do!
-
have you read : https://github.com/exit-failure/tds7000/blob/main/NVRAM/README.md ?
are your terminal software properly configured ? i had to remove "lochal echo" in my terminal it was messing with communications
-
i think the terminal software is properly configured. I'll try to find local echo and delete it.
thank you for your reply.
-
The software I use is tera term and I have tried terminal and hterm, but they have no effect.
Do I need to use other software to communicate?
-
i used multi terminal v1.0.2 because it can open multiple com ports
here's my screenshot i had to correct the target name from a member advise
the black dot at the end is generated by the software (dont care)
with this one you type on the keyboard directly .... not like termite or others who need you to type commands in a specified section
-
Thanks! I'll give it a try!
-
Hey!! I successfully connected the instrument! But I've encountered a new problem. I want to modify the data in the previous row, what should I do?
-
all the infos is given on the first pages of this thread ...
go back and please read carefully everything is there
-
I tried to learn linux instructions for a few days, but it didn't work. . |O |O |O |O
-
I still can't modify the first item....
-
Hey!! I successfully connected the instrument! But I've encountered a new problem. I want to modify the data in the previous row, what should I do?
When you type C it should go to the first row (boot device). Set it to "sm".
-
But when I enter C, it jumps directly to the second line. .
-
I completed the configuration on my old computer. But it looks like I'm in trouble again. .
-
pls not being rude can you make some efforts to show us some correct pictures, orientation etc ....
the picture doesn't help at all
and like the first thread page, you push any keyboard key to stop the countdown, and you type the minus c not the caps C .... you had this in vxworks if you where successful to stop it
[VxWorks Boot]: ?
? - print this list
@ - boot (load and go)
p - print boot params
c - change boot params
l - load boot file
g adrs - go to adrs
d adrs[,n] - display memory
m adrs - modify memory
f adrs, nbytes, value - fill memory
t adrs, adrs, nbytes - copy memory
e - print fatal exception
n netif - print network interface device address
N - set ethernet address
type c and enter, you should begin to do the settings like this : and your entries should be after see in bold, at first youlle se what they are, and after in bold you put yours ....
[VxWorks Boot]: c
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : sm sm
processor number : 0 0
host name : host host
file name : c:\vxBoot\vxWorks.st c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00 192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00 192.168.0.2:ffffff00
host inet (h) : 192.168.0.1 192.168.0.1
gateway inet (g) : 192.168.0.2 192.168.0.2
user (u) : anonymous anonymous
ftp password (pw) (blank = use rsh): anonymous anonymous
flags (f) : 0x1000 0x1000 some had to put 0x1008 in my case it did not help
target name (tn) : target tds7000 this one should be tds7000, otherwise tekscope will not save settings
startup script (s) : c:\vxBoot\dio_rst.vsh c:\vxboot\topscript.hw
other (o) : this one play tricks had to put 0x0 or 0x0000 tekscope had some problems, some have put 0x1000 ???
-
Sorry for giving you a bad impression, my old computer is not connected to the Internet... so I just used my phone to take the photos.
I successfully stopped the boot and set up nvram according to the link. But my 7104 still stays on the 'welcome' interface after booting.
I'll keep trying to fix it, thank you very much for your help.
-
My 7104 successfully entered the oscilloscope! ! !
During the troubleshooting, I found that the NVRAM voltage was abnormal. After replacing it with a new one and setting the NVRAM, my instrument was able to work normally! ! !
Thank you again! ! ! ! ! ! ! ! ! ! ! !
-
:-+ :-+ :-+
bu sure to wait at least 20 mins, with no probes
do a self calibration, it will go clicking for a few minutes, you need to see pass
and do spc when finished you have to get no errors codes on all the informations
it will rewrite files in the calcon folder, in you vxWorks folder on c:\ who could be hidden ...
i had errors because of an eeprom corruption in the acquisition section ...
-
I replaced the sram which is HM628128DLT5SL，but it also show nvram walking one test failed. There is another chip DS13D12，I am not sure I should replace this one or use another new nvram chip.
-
finally I replaced the nvram. and now it's working properly.
-
CNsam wrote:
But when I enter C, it jumps directly to the second line. .
How were you able to solve this problem because for me I am still stuck at this point |O
Thank you.
-
check in your terminal software if ou have local echo or some setting who could hinder cr+lf cr lf ... ??
9600, n , 8 , 1 .....
-
I use CoolTerm 64bits and the local echo seems disabled yet
(https://i.postimg.cc/tgRbJc3M/Capture.jpg)
-
Thanks to coromonadalix because thanks to his advice I was able to solve my "echo" problem when I entered certain commands. In the software I use: Coolterm, in addition to unchecking the local echo box, I had to change the key emulation entry from CR+LF to CR.
======
Unfortunately this was not enough. The Vxboot page loads but then I only have errors displayed. As a result, the program always remains frozen at the start page.
-
the vxboot may load, but you may still have errors, and since its a long boot process try to copy / save it, in a file
i had bad settings it it, and the scope SW stalled on the start page ....
it is not easy, many trials and errors, read tons of threads ...
took me at least 2 weeks to re-start a 7404, getting all the needed materials old stuff etc ... the 7254 i re-started 1 year ago was easier .... more recent stuff vs the 7404 ...
the 4 last pages of this thread and xdev's give you lots to work with
-
Yes quite !! I think my answers are already present somewhere in this topic.
Thank :-+
-
Good morning,
This command line thing is really annoying. On my csa8000 the vxboot starts, but I have errors which still prevent the Tektronix program from starting (see below the copy of the console log)
Dos anyone have an idea to solve this new problem ?
I only left the end of the diary
A++
TpExecDebugTrace = 0x1
TpExecDebugTrace = 0x1314eb8: value = 1 = 0x1
hwaLibStartup
ERROR- Function: acqLibLoadDspProgramVector, SysCall: ioctl, errno 0, Msg: HI32_DRV_EXECUTE
0x31ec480 (hwaStartup): diagLoadCodeForAcqDsps: AcqDSP#0 NOT RESPONDING
ERROR- Function: acqLibGetDspStatus, Msg: acqLibSendCmd
ERROR- Function: acqLibClearAcqErrorStatus, Msg: acqLibGetDspStatus
ERROR- Function: acqLibClearAcqErrorStatus, SysCall: ioctl, errno 0, Msg: HI32_DRV_CLR_ERROR
0x031ec480: hwaStartup:Assertion failed: status != ERROR, file ../src/calDiagMgr.c, line 3681
-
not sure the 8000 series are managed the same way as 7000 series ... for sure the log is not the same or you omited some section ?
and pls put this log into a txt file the thread become way too long
-
@CNsam from what i see he needs to do a clearDB
-
who can help me with figuring out where the instrument ID is set of the TDS7000 series. first i got a tds7404 where i could not get any option key installed. after uninstalling and reinstall the tekscope 2.5.3 software it detect the unit as a tds7254.
then i can imagine the key is not picked up correct. i exported my nvram content. cleared the nvram with all FF , reconfigured it manually like new boorsettings and so but nothing then i decided to revert the earlier saved content back but no change. i guess it will be saved in the NVRAM (in my case FRAM) but it looks like it is not set on that location.
so i need to figure out the location where it can be changed and after another reinstall of the software it detects the unit as a TDS7404 and not a TDS7254.
of course is a dirty workarround to re-generate the option key to a tds7254 but that is not my way of fixing things.
-
hi
I never found out where the model is taken from ..
but can you put your vxwork boot log from the side port connector ? into a txt file ?
-
i have looked into the log but there is nothing found in it apart from bad instrumentID
what i can do tomorrow, swap the board and see if that changes something. the instrumentID is married to the ACQ board i guess.
-
I have no experience with the TDS7000 series, but on related scopes the model is loaded from the acquisition board. I'd first verify that your board hasn't been exchanged from the lower bandwidth model.
If you can communicate with the console, the command raxDbgRead "GTL/BRDID" should tell you the contents of the board id register. The mapping appears to be 0xd = TDS7254 and 0xf = TDS7404. I haven't tested this personally.
The instrument id is a function of the model and the serial number.
-
Hi @Colorburst, yes you are right it is the ACQ board from an other unit i guess. where on the Acq is the Instrument id set. anbody any idea which resistors-set /on what location is used for the selection?
-
And a complete other question, i want to discuss with you technicians...about these 7000 units. did anybody ever had broken trigger chips without visible signs.
normally they get bulgy on top.
or text off or slightly brown Colored.
or even exploded or just one or two pins burned off the chip.
i mean to say:
i now have two trigger chips without any visible sign of broken on a board , which also passes all diag tests. can these chips still be broken ?
-
I'm not familiar with the actual board or the trigger chips, so can't help you there unfortunately.
However, my opinion is that with the acquisition hardware from a TDS7254, your scope is effectively a mislabeled TDS7254. I'd see about fully converting it to a 7254 instead.
Lower BW models tend to have extraneous filters in the signal path and sometimes skip steps in the factory cal. ASIC grades might be different. It can be a very involved modification with many unknowns.
-
Hi,
Contrary to the TDS5000B and Non-B Series and the later DPO, DSA and MSO Series there is, as far as I know, no Memory Erasure and Nonvolatile Parts List for the CSA/TDS7000 Series. Later Documents are labeled Declassification and Security. There is a 077-0524-00 Declassification and Security Document which should list these Parts for the earlier TDS6000 and CSA/TDS7000 Series, but concentrates mainly on the TDS6154C.
Calibrationfixture
-
for those who are struggling to get there ACQ in line with the unit model. Here is what to do.
in the corner is a bridge array where selection can be made.
This can be done by planning a zero Ohm resistor over the right pads. for selection TDS7404 only a R1069 is "0" ohm (bridged)
for tds7254 R1069 and R1062 need to be bridged. so in my case removing R1062 got my board shownieuws as a TDS7404. and in that family the units 7104,7254,7404 have the same boards apart from the generation number.
-
@charlyd
thats for the non B models right ?
thats the question you asked earlier, how did you find out ???
-
hi yes this is for the none B version.
i found out by compare the board with two other 7404 boards i have laying arround.
and these sort of bridge rows are mostly meant for these adjustments.
After removing R1062 (0 ohm) reinstalling the board and booting up, the board messaged like 7404 and the option key was pickup straight away.
-
and for my trigger chips. they seems to be dead. dropping this message...
even thought all diagnostics test are pass
-
sad for you and getting these ..... :palm:
In the 7404 i restarted, theses chips dont have any hs on them, and they seem good for now, no discoloration
all tests passed and all channels where fine with a 3.2Ghz sig generator
i may re-play in it ... since we may buy an sds7000a scope soon, the 7404 was a plan B loll
still had an crazy idea to put an intel 815 in it ... very very tight fit, but seems to miss a voltage to start ??
-
a Quick advise: add heatsinks better yesterday,... then tomorrow, i did some measurement with the flir, chips temps are way too high, without heatsinks they will die eventually.
but i type this message over and over here....