Author Topic: Help TDS7104 identify embedded lan (Read 12943 times)

Daxxin · « **on:** August 30, 2015, 01:26:05 pm »

hi , got recently this tds7104 apparently look fine but till now no chance to see it running
because lack od hd and cd , just installed an 2,5 ide formatted hd , dont have cd reader with slim
jae adapter at this time , so i tried to boot via pxe network and everything working fine except windows 2000 setup
stop due lacking NIC driver , tried many drivers downoaded in $OEM but seems no one working
hope someone identify the correct drivers and point where download thanks so much.

TiN · « **Reply #1 on:** August 30, 2015, 01:45:17 pm »

It's Intel 559

Daxxin · « **Reply #2 on:** August 30, 2015, 02:14:46 pm »

Its bg82559 not BD , downloaded from intel ..PRO100 drivers for this chipset but wont load them ..maybe bootp server misconfigured

new299 · « **Reply #3 on:** August 30, 2015, 04:57:08 pm »

I don't know what kind of Ethernet chip is uses I'm afraid but I have access to a TDS7054 in Japan and can check next time I'm there. I think I have the original install discs here and will check those. If you're repairing the scope I wrote up my repair notes here: http://41j.com/blog/2014/08/tektronix-tds7054-repair/

lukier · « **Reply #4 on:** August 30, 2015, 05:06:34 pm »

Quote from: new299 on August 30, 2015, 04:57:08 pm

I don't know what kind of Ethernet chip is uses I'm afraid but I have access to a TDS7054 in Japan and can check next time I'm there. I think I have the original install discs here and will check those. If you're repairing the scope I wrote up my repair notes here: http://41j.com/blog/2014/08/tektronix-tds7054-repair/

That is pretty awesome. Especially the part when you say you got TDS7054 for $200

How come, if you don't mind? I wish I could get working/repairable TDS5k/7k even for three times more

Smith · « **Reply #5 on:** August 30, 2015, 05:24:02 pm »

Did you set the BIOS LAN setting right? My TDS7154 has one. Copied from the Tek website, saves me taking a look because I'm lazy.

How do I Enable or Disable the LAN and connect a TDS5000(B)+ TDS6000(B) or TDS7000(B) Series oscilloscope to the Network?
Answer:

You can connect the scope to a network to enable printing, file sharing, internet access, and other communications functions. Before you make the connection, do the following steps to enable (the default) network access to the Oscilloscope:

1. Begin with the scope power off
2. Attach a PS2 keyboard and mouse to the scope
3. Power up the scope
4. As the scope begins to boot, press the keyboard F2 key repeatedly until the message Entering Setup, or Loading Setup on some Oscilloscopes appears
5. Use the keyboard right arrow key to highlight Advanced
6. Use the keyboard down arrow key to highlight Peripheral Configuration and press Enter
7. Use the keyboard down arrow key to highlight LAN Device and press Enter
8. Use the keyboard Up/Down arrow key to highlight Enabled and press Enter
9. Press the keyboard F10 key to save, and exit
10. Once the Oscilloscope has completed auto boot up minimize the scope application using TekScope File menu Minimize or (right-mouse-click Minimize on some scopes) to access the Window desktop.
11. Use the Windows network setup utility to define the Oscilloscope as a network client and configure it for your network. You can find the network setup utility in the Windows Start menu if you select Settings > Control Panel and then double-click Network.
12. Consult your network administrator for specific instructions to make these settings.

new299 · « **Reply #6 on:** August 30, 2015, 05:37:37 pm »

Quote from: lukier on August 30, 2015, 05:06:34 pm

Quote from: new299 on August 30, 2015, 04:57:08 pm
I don't know what kind of Ethernet chip is uses I'm afraid but I have access to a TDS7054 in Japan and can check next time I'm there. I think I have the original install discs here and will check those. If you're repairing the scope I wrote up my repair notes here: http://41j.com/blog/2014/08/tektronix-tds7054-repair/

That is pretty awesome. Especially the part when you say you got TDS7054 for $200 How come, if you don't mind? I wish I could get working/repairable TDS5k/7k even for three times more

If you look around, faulty test equipment can be very cheap in Japan. That one I picked up in Akihabara (Keisokuki land). I also got a TDS5052 for the same price there.

Shipping scopes out of Japan on the other hand is a major pain. There's some export rule which says you can't ship scopes with a bandwidth over some insane value, I think 100GHz from memory. That's fine, but the result is that /every/ scope shipped requires a "parameter sheet" from the manufacturer. So you need to ring Tektronix, give them the serial number and wait a week to get the parameter sheet... sigh...

That could go some way to explaining the lower value of broken test equipment as sales are limited to internal markets only for the most part.

lukier · « **Reply #7 on:** August 30, 2015, 05:48:45 pm »

Quote from: new299 on August 30, 2015, 05:37:37 pm

If you look around, faulty test equipment can be very cheap in Japan. That one I picked up in Akihabara (Keisokuki land). I also got a TDS5052 for the same price there.

Shipping scopes out of Japan on the other hand is a major pain. There's some export rule which says you can't ship scopes with a bandwidth over some insane value, I think 100GHz from memory. That's fine, but the result is that /every/ scope shipped requires a "parameter sheet" from the manufacturer. So you need to ring Tektronix, give them the serial number and wait a week to get the parameter sheet... sigh...

That could go some way to explaining the lower value of broken test equipment as sales are limited to internal markets only for the most part.

Interesting. I've read about awesome bargains if you are in Silicon Valley (and USA in general to some extent), I see quite a bit of T&M gear from Israel on eBay (and often in a horrible state) but I didn't know about Japan.

I suppose you've paid more for the paperwork and shipping than for the scope

Unfortunately, in the UK / EU it is somehow very tricky to get such sweet deals. I check eBay frequently and it is mostly PAT testers and metal detectors

There are some professional traders with insane prices. The notable exceptions are KJDS and TopLoser

With my kind of income I could perhaps gamble $200 on a "parts/repair" state TDS5k/7k (the worst case is that the aquisition board is fried and the game is over), but not much more, too risky.

new299 · « **Reply #8 on:** August 30, 2015, 06:21:59 pm »

Quote from: lukier on August 30, 2015, 05:48:45 pm

I suppose you've paid more for the paperwork and shipping than for the scope

Unfortunately, in the UK / EU it is somehow very tricky to get such sweet deals. I check eBay frequently and it is mostly PAT testers and metal detectors There are some professional traders with insane prices. The notable exceptions are KJDS and TopLoser

Paperwork was free, just time consuming and as I don't speak Japanese very well involved hassling my wife a lot.

I'm back in the UK. eBay is pretty much useless as far as I can tell. However I've got some nice gear at auction here. Check the Equipnet auctions. I picked up some R&S CTRUs which make reasonable spectrum analyzers for about 100GBP and on the scientific side of things some nice lab equipment too.

Daxxin · « **Reply #9 on:** August 30, 2015, 08:52:29 pm »

just very near to complete ..for the moments hangs on splash screen , but atleast completed the pxe boot configuration , work in progress

Daxxin · « **Reply #10 on:** August 31, 2015, 10:13:50 am »

..installing , the problem installation stuck at splash was the permission to read files from shared folder , applied correctly created Null Session Share WIA_RIS_SHARE
fixed and running , software used: SERVA 64bit non-commercial version acting as dhcp-tftpd server , i guess the original os was win98.

Daxxin · « **Reply #11 on:** August 31, 2015, 12:09:30 pm »

ok everything installed and seems there no problems with boards+drivers but it stuck at tekscope start splash and the display
on ppc board looping ,, 4-5-6-7-8-A-H-L ..here starts the troubles?

Jwalling · « **Reply #12 on:** August 31, 2015, 12:46:00 pm »

All you need is here. you have to re-enter the boot parameters in the PPC board if your battery is dead:
https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/

Jay

Daxxin · « **Reply #13 on:** August 31, 2015, 02:15:36 pm »

Yes thanks , i checked battery before was 2,98V maybe disconnecting the cap i have erased all stored data?
anyway i am preparing connector cable for tht j790 but at the moment i am confused about what to send in the terminal

Daxxin · « **Reply #14 on:** August 31, 2015, 03:46:39 pm »

did what TiNsuggestingabout vxWorks but something still wrong
hes scope is csa my is td7104
this the terminal log:

Quote

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: Creat0xing new NVRAM file1fffe08 system
tcsTableUnpack: checksum failed on buffer
tcsTableLoadFromNVRAM: tcsTableUnpack failed
(tRootTask): memPartAlloc: block too big - 2123556858 in partition 0x337ebc.
KERNEL: THERMAL CONTROL INITIATED
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 = 23609056 = 0x1683ee0
ld < TekScopeSM.o
value = 23608416 = 0x1683c60

pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)
new symbol "pDbDev" added to symbol table.
pDbDev = 0x1685820: value = 23615552 = 0x1685840 = pDbDev + 0x20
pDBfs = dosFsMkfs("/db", pDbDev)
new symbol "pDBfs" added to symbol table.
pDBfs = 0x1683aa0: value = 23608064 = 0x1683b00 = 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 = 21752576 = 0x14beb00

initSysWaiter()
value = 0 = 0x0

raxInit
value = 0 = 0x0
paiInit
done
value = 16918356 = 0x1022754 = 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")
0x168a6c0 (tShell): Device failed to verify at address 0x0000.
0x168a6c0 (tShell): Burning new code into AT90S4434 processor.
0x168a6c0 (tShell): 1370 bytes successfully programmed.
value = 1 = 0x1
cd "pc:"
value = 0 = 0x0

raxInitializeDevices
done
0x168a6c0 (tShell): (Re)starting Acq Processor
value = 21749672 = 0x14bdfa8

excHookAdd(stopStressForException)
value = 16705228 = 0xfee6cc = stopStressForException

dsyInit
value = 21740904 = 0x14bbd68
dsyWPApplyNextRegs
value = 16908232 = 0x101ffc8 = DsyRegisterTable + 0xab0

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

nvram_initFileSys
0x168a6c0 (tShell): >> Kernel version 1.0.8.0 does not match Boot ROM version 1.0.3.0
value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba5b8e3

TmgrInit("/db")
0x168a6c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x168a6c0 (tShell): Problem reading serial number from disk!!
0x168a6c0 (tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
0x168a6c0 (tShell): Problem reading option key from disk!!
0x168a6c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...
0x168a6c0 (tShell): Problem reading serial number from disk!!
value = 0x168a6c0 (0tShell): NO BACKUP OPTION KEY FOUND, RESTORING VALUE FROM DISK...
= 0x0x168a6c00 (tShell): Problem reading option key from disk!!

PhxProxyInit
value = 20753600 = 0x13cacc0
rtlInit
value = 0 = 0x0

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

hwAccount_init
0x168a6c0 (tShell): ERROR: memory sizes: demuxa=4M demuxb=4M demuxc=4M demuxd=4M
0x168a6c0 (tShell): demuxe=0M demuxf=0M demuxg=0M demuxh=0M
sysEnetAddrGet: 5f:77:45:bc:55:9f
value = 1 = 0x1

GpibInit

data access
Exception current instruction address: 0x00ef2cfc
Machine Status Register: 0x0000b130
Data Access Register: 0x93e10084
Condition Register: 0x48200043
Data storage interrupt Register: 0x40000000

2f1588 vxTaskEntry +60 : shell ()
281b88 shell +18c: 281bb4 ()
281dbc shell +3c0: execute ()
281f3c execute +d8 : yyparse ()
305d4c yyparse +7a8: 303cb0 ()
303e28 yystart +8f8: GpibInit ()
ebe310 GpibInit +dc : gpibLoadPackage(ParseTreeSrun*,void(*)(ParseTreeSrun*,int,PTErrorSrun*,)) ()
ebe10c 0xgpibLoadPackage(Pa168a6c0rseTreeSrun*, (void(*)(ParseTreeStShellrun*,int,PTErr): orSrun*,))memPartFree+: invalid block 580xff809c0 in partition 0x337ebc.
: loadPackage__13ParseTreeSrunPFP13ParseTreeSruniP11PTErrorSrun_viP11PTErrorSrun ()
ef220c 0x168a6c0 (tShell): memPartFreeloadPackage: invalid block __130xParseTreeSrunPFP13ff7ff40ParseTreeSrun in partition iP11PT0xErrorSrun_viP11PTE337ebcrrorSrun.
+20 : 0x168a6c0 (tShell): memPartFreegpibDispl: invalid block ayCm0xds(ParseTreeSrun*,ff7f4c0int,PTErrorSr in partition un*)0x337ebc (.
)
e8ec44 0x168a6c0 (tShellgpibDisplayCmd): s(ParseTreeSrun*,memPartFreeint,PTErr: invalid block orSr0xun*)ff7ea40 in partition +0x337ebc.
1e4: 0x168a6c0 (tShell): addCommand__13ParsmemPartFreeeTreeSrun: invalid block PCcP0xCl7CRRSruniP11PTErff7dfc0rorSrun in partition (0x337ebc.
)
ef2344 0x168a6c0 (tShell): memPartFreeaddCommand: invalid block __130xParseTreeSrunPCcPCff7d540l7CRRSruniP11 in partition PTErro0xrSrun337ebc.
+104: 0x168a6c0 (tShell): memPartFreeaddHeaderDef__: invalid block 13Pa0xrseTreeSrunR13Headff7cac0erDefSrunP7IA in partition BSrunR0x11PTErrorSrun337ebc (.
)
ef2424 0x168a6c0 (tShelladdHeaderDef__13Par): seTreeSrunR13HeadmemPartFreeerDefSrun: invalid block P7IA0xBSrunR11PTErrorSruff7c040n in partition +0x337ebc.
38 : 0x168a6c0 (addHeaderDef__17PartShellseTreeNodeSrun): R13HeaderDefSrunimemPartFreeP7IABSrun: invalid block R11P0xTErrorSrunff7b5c0 in partition (0x337ebc)
.
ef2888 0x168a6c0 (tShelladdHeaderDef__17Par): seTreeNodeSrunR13memPartFreeHeaderDef: invalid block Srun0xiP7IABSrunR11PTErrff7ab40orSrun in partition +0x337ebc.
1dc: isMatchWithSubNode__C17ParseTreeNodeSrunR9KWDefSrunRi ()
ef2bd8 isMatchWithSubNode__C17ParseTreeNodeSrunR9KWDefSrunRi+54 : __eq__C17ParseTreeNodeSrunRC9KWDefSrun ()
shell restarted.

Done executing startup script c:\vxBoot\dio_rst.vsh
KERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!

need different parameters? herad some relays clicking but splash still stuck and ldisplay showing blinking minus -

Jwalling · « **Reply #15 on:** August 31, 2015, 05:39:41 pm »

Try programming it with this one I got from a working TDS7104:

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

Daxxin · « **Reply #16 on:** August 31, 2015, 08:07:17 pm »

with this parameter was able to run tekscope but still problems , look at pics center of screen
is black cant view channel signals , dont have installed 3d rage agp 2x drivers because cannot find them for win2k
do you think is that the problem or ati chipset is only for external monitor? ,
then second picture there no option installed or scope serial i tried to boot once with parameter
NvramClearDb = 1 enabled but i see log everything failed about restore because looking for constantcals and install disk files

nctnico · « **Reply #17 on:** August 31, 2015, 11:43:15 pm »

You really need to install the OS the scope software is designed for. The videocard needs the Tektronix drivers (usually included somewhere in the software package you can download from Tektronix) because it is not a standard videocard. The scope signals are drawn onto the screen using some kind of overlay which goes around Windows.

Daxxin · « **Reply #18 on:** September 01, 2015, 05:44:15 am »

tought only chip69000 is working with instrument panel not interacting with rage 3d
if someone has this drivers pls share them.

Jwalling · « **Reply #19 on:** September 01, 2015, 10:01:33 am »

Quote from: Daxxin on September 01, 2015, 05:44:15 am

tought only chip69000 is working with instrument panel not interacting with rage 3d
if someone has this drivers pls share them.

What is the serial # of the scope? I do have some ghost images for these. Also, where are you located?

Jay

Daxxin · « **Reply #20 on:** September 01, 2015, 10:27:19 am »

sent you pm anyway serial is B020764 .Italy.

Jwalling · « **Reply #21 on:** September 01, 2015, 05:54:21 pm »

Quote from: Daxxin on September 01, 2015, 10:27:19 am

sent you pm anyway serial is B020764 .Italy.

I just sent you the link for a working image taken from B020612. Please let me know how it goes!
Don't forget to use ANOTHER disk drive!

Jay

Daxxin · « **Reply #22 on:** September 02, 2015, 09:12:49 am »

its working!

Thanks to Jawalling for his big help and hints , thanks to TiN for his useful info.
just need to reassemble the cabinet.

Jwalling · « **Reply #23 on:** September 02, 2015, 09:58:00 am »

Excellent and you're very welcome!

Enjoy the scope!

Jay

TiN · « **Reply #24 on:** September 14, 2015, 05:10:01 pm »

Great.

Jwalling, I can host image as well to make it easier for others in future, if you want to have it pub.


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

Author Topic: Help TDS7104 identify embedded lan (Read 12943 times)

Share me