Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)

[charlyd]

Just for my thoughts and that from others...
i saw a lot of posts about unsupported hardware message
when installing Tektronix firmware on a new installed OS like windowsXP , what can be the problem for the unsupported Hardware message.

to start of  for a TDS7104  (fully working on a W2K image)
- Now a newly installed OS winXP
- copied both OEM.xxx files to the system32 folder
- chips B69000 vga driver installed
- frontpanel v1.0 driver installed
- tektronix Bridge driver v1.05 installed

- tektronix Firmware drops error  "unsupported hardware"

on page 22,23 ( same Post) there is lots to read about this error but not what the real problem is.....  a working image is a workarround...  i am curious to the real thing what matters

[coromonadalix]

i may not have followed all of your threads

BUT i would check   all the drivers in windows devices manager   if you see errors, IE drivers not installed, not working, there was some hints on some *.INF files to install too,  some peripherals don't declare themselves, until some INF drivers are installed,  because windows does not know them, or what to do with them, until the INF  help finding them / or get declared as a peripheral / address ranges etc ...

a windows desktop shortcut can be created with  devmgmt.msc

a motherboard change ...   I don't recall if Tekscope search for some id's in the bios,  only thing i can say, on our 7254 B,  i put back an original Intel bios to help restarting it (nvram crash and other things)  and it works, and does show  more options,  but it is some nightmare to reconfigure the lcd screen specs,  if the coin cell dies, runs XP fine

on the 7404 non B   it is fully original,  was restarted too,  Radisys SU810 mobo,  i don't know on this one ..    but  as written before :   not w2k  was working, nor Xp ...


can't play a lot in theses until    we buy an Siglent SDS7404A, thoses TEK's are getting very old

Once again, i know you have searched a lot for os recovery disks,   i would have said and say again, start from scratch, new build ...   do hdd backups ...
install the needed windows from your serial sticker,  if it says win 98  win2k  xp  etc ...

i've lost some of your threads ...  and all your history  .... sorry


some *.INF  files  install themselves  by clicking on them and right click  install ....    even putting them in the windows system 32 folder or else  etc ... will not activate them,  they need to be added in the registry too


posted  an inf   of the 7104  backup  i did,  remove the .txt    rename it to  unsup.inf

the most recent  PCI2PCI bridge driver  v1.11   dont know  for the 1.05   and where you took it ??

there was an cmos utility  to validate the LAN port or not,  attached here too, i think it was done  because there was not enough available IRQ's, if it was enabled, i think you loose an peripheral ??     sorry weak memory at the moment

and i think you had to install some Intel storage drivers too ...   not sure

YES THE REPLY #527     .... please  when linking something   do use the thread number too   

even I  get lost in all of this  loll    see my #943     need to do clean up in my TEK files hdd   

for the TI  card bus drivers
https://www.driverscape.com/download/texas-instruments-pci-1225-cardbus-controller

[charlyd]

Hello thanks was this post in reply to mine ? or just general?
because my case is to install a new OS as written from scratch and find out why things are not working. the things i installed should be enough to get the scope alive unless there is a mismatch somewhere in PID/VID.

there are also two types of PowerPC going arround. one model without the Texas Instruments PCI-1225 CardBus Controller and one with that hardware which can be a struggle. but that to the side for now...

as for the drivers the version i have written are working and original for that model  and indead can later be updated to pci2pci 1.12 (upgrade from 1.05 via 1.11)  and the frontpanel to V2.0

I WILL WRITE THIS IN CAPITAL LETTERS SO IT CATCHES YOUR EYES:  Does somebody have an original  "Drawbridge installation disk". (Tektronix Power PC Board) Maybe left behind on a disk from a scope, so not only the .SYS and .INF files in the PCI2PCI folder

i think i am nearly at the finish of discovering the real problem.

[coromonadalix]

@charlyd

general speaking,  but i know you did a lot of search and work on your side, but it was on other threads if i recall, making it difficult to follow

I never saw the one without the pcmcia card,  if you could post some photos ?

I enabled the lan port while disabled the pcmcia card, no need for that


and i did not encounter the non matching hardware errors on the 7254b and 7404,  so my help is limited, i don't have your scope to play in it ...     unless there is still vxwok config errors ?  you have to be sure on this side 1st,  even without any windows installation booting

The final vxwork console message must say   running  ...   xxx  ticks  etc ... 

Until i got that,  the 7404 scope would accept windows installations w95 and up  ...  the power pc is the scope brains ...  for the w2k   i was never able to fully understand where it began to loop continuously

I never got back on this,  maybe slipstreaming the drivers, creating a new cd iso  would have helped,  but the cd-rom in it was not accepting any burned ones, even with other / newer slim models who could do dvd-rw ones  it was very very picky

@charlyd   if powerpc vxwork is okay, and running / no errors,  the mos important one would be the link card, between the pc side and the power pc mobo,   can you post a picture of it ? 

@charlyd   you did say   it was fully working with W2k ??  why do you want to push it to XP ?  i think you wrote elsewhere you had an XP serial sticker on it ?

At some point you gain nothing,   you gain something with more ram and a faster cpu, it will ease the pc side operations, and finally removing the Msoft crap and background running stuff of that era  will liberate more process power   

it's just a matter of never let the scope go to the web ... what ever the OLD OS is  ...    we use them on a closed network

[calibrationfixture]

Hi coromonadalix,

Before I acquired a TDS7404B I also looked at Non-B's. I noticed there were Scopes with and without a PCM-CardBus. Also noticed that these Models didn't have the Dallas NVRAM with the Clip-On Battery (which I found a pre). I even made a Post on another Forum named: "Which CSA/TDS7000 Serials to avoid". Attached Pictures of, in this case, a late TDS7104 PPC-Board.

And charlyd I agree with coromonadalix. Mostly OS Changes etc. etc. are "a route to despair". With the TLA7012 (Gen1) same story, other MB's even  Windows 7 tries. All leads to nothing and are in my humble view a waste of time. Life is too short.

Calibrationfixture

[coromonadalix]

@calibrationfixture    uh  never saw that thread, can you post a link ?  thks

i do understand if people want the original Os working if the sticker behind say Xp W2k  or else ...  if it's @Charlyd  case

I tried the best i could for the old 7254 B  up to Xp Sp3 +  post Sp3 updates (pseudo Sp4) packages   etc ...


If @charlyd  can post an w2k hdd image of his scope,  for sure  i'll try it  ....  but it has the older power pc board, i had to patch an cr2032  coin battery socket on the nvram     loll   

the new Siglent seems to have been ordered ..  it's a matter of time before they'll  become plan B and C and sit on shelves, mostly the 7404

[charlyd]

If you look in the .INF files you will discover the file and related files are for two type of boards. One with the (VEN_1011&DEV_0046" corresponding to the 21554 PCI-to-PCI bridge on the PowerPC board). and als one for the newer boards with the 21555 chip on it. my guess is the one with the TI -cardbus equipt has the 21555 chip.(bottom picture) the fact that the firmware doesn t detect the 21555 correct is why i ask few posts above for the complete drawbrigde installation disk.  because  by that disk the correct entry on Hklm/System/CurrentControlSet/Enu/Pci/..
there is a "custom key"(SID related) written which could be done maybe manually but better with the disk ,i hope...

So the next step would be test the "Drawbridge Installation Disk" 

[charlyd]

on reply to the posts above. WinXp is for sure a good running OS for the 6000/7000 scopes. This is because the win2K are mostly w2k/winXp drivers.  Win7 is more a no go. didn t try it but also won t want to burn my fingers on that one.  And as for the PowerPC boards there are  4 models:
(with TI-cardbusses)
-  the old model with 21554 with a DS1245YP (piggyback bat.)
-  the old model with 21554 with a DS1245Y PDIP
(without TI-cardbusses)
- the newer model with 21555 with a DS1245YP
- the newer model with 21555 with a DS1245Y
the last two are not supporter with the PowerPC board.
-  the newer model 21555

[coromonadalix]

21555 would have theses :  PCI\VEN_8086&DEV_B555

it is used on some megaraid cards 2001 series ...

https://deviceinbox.com/devsearch/find.php?search=+PCI%5CVEN_8086%26DEV_B555

check here :
ATI_Communications_Processor_LPC_Controller / machine.inf_amd64   / machine.inf             there is a very long inf  stating this 21555 .....    i would

OR here :  https://www.driverscape.com/download/ati-i-o-communications-processor-lpc--controller


hoping theses drivers would kick some peripheral detection and installation


googled a lot     many duds or bad links, theses are the ones i've found


on @calibrationfixture photos  you see an Pericom PI7C8150   it is an pci-pci bridge too

[calibrationfixture]

Hi coromonadalix,

The other Forum was TekScopes, but no replies on the Post. Attached a Picture of a TDS7254 B030485 its Rear with no PCM-Cardbus.

Calibrationfixture

[coromonadalix]

@charlyd

I  found out the drawbridge driver,   the 8000 series have them too,  took me a while to remember it was the pci 2 pci driver 

seeing in the old v1.11 or older pci2pci INF drivers  they call them DEC2155X     notice the X

and yes the vid pid  is : PCI\VEN_1011&DEV_0046

unless mistaken   it should install and declare the 21555 too   since it is considered an general installer BUT

i have tweaked it  into an modded one  (dbwdm2.inf) (remove txt extension)     and the original files are attached / zipped

you  can even try on the pci2pci   1.12 and see ??

in theses old "OS'es"  we could play with theses inf files and not trigger certificate errors, good ol time


------------------------------------

EDIT  ARGH  loll               in the v 1.12  it is already there  loll   man i think i need to go back on vacation  loll 

i have too many TEK files on an dedicated hdd   

[Tektronix]
%PCI\VEN_1011&DEV_0046.DeviceDesc%=DBWDM.Dev, PCI\VEN_1011&DEV_0046
%PCI\VEN_8086&DEV_B555.DeviceDesc%=DBWDM.Dev, PCI\VEN_8086&DEV_B555



[Strings]
FloppyName="Drawbridge Driver Installation Disk"
TEK="Tektronix"
MfgName="Tektronix"
PCI\VEN_1011&DEV_0046.DeviceDesc="Tektronix PowerPC CPU Board"
PCI\VEN_8086&DEV_B555.DeviceDesc="Tektronix PowerPC CPU Board"
DBWDM.SvcDesc="Drawbridge I/O System Driver"
DIOSERVICE="DIO Service"
LOCALSYSTEM="LocalSystem"



normally  on each inf file    (mouse escape)   do an manual install,  it should work, in case of no errors in the device manager,  it means  windows simply doesn't see anything
I do recall installing this one manually,  and it did a few things in windows ...

this 1.12  version  load as a service for the dio ... driver  and should do both Power Pc version (pcmcia / no pcmcia) ...

UNLESS there is still an weird error left      who gives an incompatibility warning      you did show us on a previous thread, your declared devices .....  mmm

[charlyd]

Hello ok now i am curious if the 8000 software has more then only these .INF and .SYS files  in the PCI2PCI  folder under tektronix. 

i have inspected and tested with all these drivers 1.05, 1.10, 1.11, 1.12  ( btw the INF files are all the same with the two " Power Pc board"  entries, but none of them have a " let call it "  complete installation .EXE file.
i can imagine that such a setup forces the entries into the registry, maybe?

when installing the driver in the manual mode ( mouse escape ?)
- You go into the device manager
- choose "update driver"
- choose " have disk" 
- browse and point to the .INF
- it will install that entry which is found in your system ( and in my system the 21554 is not found)

and also the %PCI\VEN_1011&DEV_0046.DeviceDesc%=DBWDM.Dev, PCI\VEN_1011&DEV_0046. will therefore not be installed.
Resulting in the Tektronix FW failing and drop the unsupported Hardware message. ( unless the entries are added into the registry by an installation made on an other system or added manually but this is not simple.. because of : 3&11583659&0&A8


what i can do (i need to find some time) is find out exact which is the entry needed and write a program/script for it so the installation does a system scan and creates the correct entry ..... to be continued....

[charlyd]

lol @coromonadalix  did you look in this link  i filled in the 21554 https://deviceinbox.com/devsearch/find.php?search=PCI%5CVEN_1011%26DEV_0046
only $@WTE%^*%UYT  is coming back     same as the driverscape site which is not good to rely on.

[coromonadalix]

i never saw any installer msi or setup exec  etc ... for the pci2pci,   the DIO service was the only change  TEK said / wrote ?

in the v1.12  you have many files,  normally we have to make windows search in them or force a manual  install of them ??

It would install itself if they where slip streamed in the cd-rom content, windows setup content,  they would go in the syst 32 folder / drivers  etc ...


maybe the originals TEK recovery cd's are   never saw their content ...

theses  files come mostly from recovered hdd contents in the Tektronix folder ONCE the installation is completed 


the only thing in my mind    would be:
   
recover the registry locations of theses on working machines, and export them in a reg file,   dbl click them would help to install references of them,  but you would need  to put them at their right places too  ....

for the manual install of INF : you can do,    mouse right click on the INF file(s),  select install

[charlyd]

i guess it is not that simple. i found the problem and build a little program for it. below is a preview. (runas admin to be sure)
EnableIntel21555Only.exe  should prepair your system so firmware 2.5.5  can be installed.
(if the error "Unsupported Hardware" is dropped on whatever CSA/TDS7000 series, the tool should there be usable too)

from my thought the problem lies in the newest 2.5.5 version not being compatible anymore...

[fdavalos1]

Could you please share with me your PPC nvram dump file?

I have a TDS7104 with a non-working console port and I'm unable to reconfigure the boot parameters.

[pasta2018]

Recently,I have got a tds7154. when run selftest,it shows error 451, in Trigger-BTL- Ch1Edge. After I replaced one of  a chip(marked with s176 104) near the trigger chip. now the selftest is all ok. But spc fails,and the waveform is abnormal(The waveform fills up the screen, the vertical gear adjustment and position adjustment are invalid, the horizontal adjustment time base changes ).
SPC error as attached.

Could someone give me some advice to repair this unit, thanks!