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.
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 ?
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 ?
# remove '#' from next line to set powerup scope state to factory default:
# NvramClearDb = 1
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:Quote# 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.
oh right I misunderstood you.
IIRC I've seen a keygen being mentioned somewhere in that forum
Hey, no idea why the link doesn't work. Happy to send a copy to you if you want to PM me.
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.
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.
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
You can create a bootup dos disk from another computer with a floppy using the setup from http://www.allbootdisks.com/download/dos.html
cheers
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.