Need Tektronix TDS220 firmware file

[mmaseda]

I need a bin or hex firmware file for a TDS220.  Would like V1.17 or later for programming a 27C040 EPROMs.

[JFJ]

The firmware file in Intel Hex format is too big for this forum (the file is 1.441MB and the limit is 1MB). A binary version of the file is only 512KB, but .bin files are not accepted by the forum. So, I changed the binary file's extension to .txt before uploading it. Please change it back to .bin when you have saved it.

Version 1.19 firmware is Tektronix part number 163-0792-06. The checksum will be 02B9FBC5 or FBC5 (depending on how your programmer displays it).

[mmaseda]

Got it !!!  Thanks

[cardre]

Reviving this old post, wondering if you have or know what the latest firmware is for the accompanying TDS2CM communication model for the TDS210 and TDS220? The unit I'm borrowing from a friend has CMV:v1.02 and if I can upgrade both for him, would be good. Thanks.

[Nprod]

Reviving this post again - does anybody here have TDS220 firmware that's 2.0 and later? I also saw that you can upgrade a TDS2CM module to a TDS2MM one if you swap out the RAM and EPROM and then flash the TDS2MM.hex on it as described here: http://www.edaboard.com/thread8031.html

Sadly that thread is ancient and they only gave out the .hex file for it via PM... If anybody has these it would be greatly appreciated.

[scopeman]

Attached is firmware for the TSD2MM and the TDS2CM modules. To upgrade a CM to a MM you need to upgrade the SRAM and burn the firmware as follows

1. Replace 32kx8 RAM memory with 128k x 8/SO32/70ns/5V
2. Replace EPROM memory with 27C040 (512k x 8/PLCC32/70ns/5V)

Good Luck,

Sam
Scopeman

[Nprod]

Oh wow, thank you so much scopeman! 

[scopeman]

No problem glad to help. I have a TDS224 that I upgraded the CM module to a MM years ago. I don't have the firmware for the scope itself though. Never had to update that.

Sam
W3OHM
Scopeman

[scopeman]

Also Nprod let us know how you make out!

[OH2LIY]

Hello, I did try this with no luck. I replaced SRAM to Sony cxk581000am-70  (standard 128kx8 SRAM, first what I did find in my storage). I didn't have 27C040, instead I used 29F040. Using 29F040 CM (plain communication software) works nicely with bigger memory, but  when replaced to MM software, scope just freezes during boot up. 28C040 vs. 29F040 should be similar, if scope don't try to write anytyhing to memory.



OH2LIY

[chronos42]

I did it with a TDS220. I replaced the RAM with a 70nS 128k X 8 Renesas RAM and programmed the MM Firmware in a 27C040 from Atmel.

It worked without any problems and makes this 21 years old scope attractive again.

BTW:
Without changing the RAM the TDS hangs in a bootloop with the MM firmware.

@OH2LIY: maybe something is wrong with your RAM.

[OH2LIY]

SRAM is probably ok, because TDS2CM (plain I/O software) runs on it (also using 29F040). If SRAM size is only difference between CM vs. MM software, I'll probably change it again to some different model...


Ramppa, OH2LIY

[JacquesBBB]

I did it with a TDS220. I replaced the RAM with a 70nS 128k X 8 Renesas RAM and programmed the MM Firmware in a 27C040 from Atmel.

It worked without any problems and makes this 21 years old scope attractive again.

Interesting.  What are the additional features with this change ?

As I have not looked precisely to the board, I dont understand precisely the changes to be made.
As you say, two chips need to be changed. Do you know their numbers on the board ?
What are the original values of these chips ?

Thanks

[Nprod]

Interesting.  What are the additional features with this change ?

You get an FFT option, that's the only difference compared to the TDS2CM. It's a nice upgrade because actual TDS2MM modules are hard to find and still very expensive.

[chronos42]

You also get risetime and falltime measurment.

And for me it was lot of fun to finally get these options for this old scope.

I saved my TDS 220 from the junk, brought it back to life and I like it.
I cannot explain why, but I really like this litte scope. I have much better scopes in my lab, but for repair jobs I mostly use the TDS 220.

[Beerden]

Reviving this post again - does anybody here have TDS220 firmware that's 2.0 and later? I also saw that you can upgrade a TDS2CM module to a TDS2MM one if you swap out the RAM and EPROM and then flash the TDS2MM.hex on it as described here: http://www.edaboard.com/thread8031.html

Sadly that thread is ancient and they only gave out the .hex file for it via PM... If anybody has these it would be greatly appreciated.

Thanks for reviving this post. Any word on the firmware 2.0 and later for the TDS220 (does it exist?)

Anyway, I have some additional info to add here:

A FLASH memory device can be used in place of the OTP EPROM for the TDS220 main board.

The EPROMs are getting harder to find (and they're one-time programmable!), but the FLASH "cousins" in these 32-pin PLCC packages are still available.

I was able to change the AM27C040-150JC OTP EPROM at socket U302 on the TDS220 main board to a AM29F040B-90JC (5V) FLASH (AMD/Spansion) already handy from my personal stash.

There is a small pin difference between the 27C040 32-pin PLCC and the AM29F040B-90JC 32-pin PLCC:

 pin 1 is Vpp on the 27C040 OTP EPROM, but is A18 (address bit) on the 29F040B
 pin 3 is A18 on the 27C040 OTP EPROM, but is WE# on the 29F040B

This pin difference needs to be corrected to work with the 29F040B; luckily the solution is already provided for by R306 and R307 resistor options for the U302 socket that connects pin 1 to pin 3:

Remove the 39.2 Ohm 1206 size resistor at R306
Install a 1206 size shunt (0 Ohm, or short length of wire) at the empty pads for R307
Insert the 29F040B in the U302 socket

My scope was at v1.16 and now it's v1.19!

I'm looking into the TDS2CM upgrade to TDS2MM now...

[scopeman]

Bin file for the TDS2MM and instructions to update a TDS2CM to a TDS2MM is attached.

Sam
W3OHM

[Beerden]

Hello, I did try this with no luck. I replaced SRAM to Sony cxk581000am-70  (standard 128kx8 SRAM, first what I did find in my storage). I didn't have 27C040, instead I used 29F040. Using 29F040 CM (plain communication software) works nicely with bigger memory, but  when replaced to MM software, scope just freezes during boot up. 28C040 vs. 29F040 should be similar, if scope don't try to write anytyhing to memory.



OH2LIY

The difference between the 27C040 and the 29F040 is three pin assignments, Vpp and A18 at pin 1 respectively, and A18 and WE# at pin 31 respectively. So without a bit of PCB modification, the 29F040 is not expected to work as a drop-in replacement.

Pin 1 of the 29F040 is A18, the upper address bit, which on the 27C040 is at pin 31. Pin 31 on the 29F040 is the WE# pin. The TDS2MM firmware is likely larger than the CM firmware and may need access to this pin.

It is unlikely, as you guessed, that software would try writing to this region of memory, so it should be safe to connect pin 1 to pin 31 on the PCB. This same "trick" is done on the TDS220 motherboard, but is actually provided by a resistor shunt option, and a 29F040B works there!

To support this connection, the AM29F040 datasheet says (paraphrased), "Write cycles are inhibited by holding any one of OE# = low, CE# = high or WE# = high. To initiate a write cycle CE# and WE# must be low while OE# is high", so in the case where A18 is attached to WE#, then OE# = low (read cycle) will override the WE# function for any state of A18.

I also hope to use a 29F040B on my TDS2CM, but the TDS2CM will require a wiring modification. Unfortunately, pin 1 of the U206 PLCC socket is directly connected to a via to the ground plane (Vpp programming voltage on the 27C040), so this makes modification for a 29F040B tricky for pin 1, but not impossible.

As far as I can tell A18 traces from pin 1 of the J101 header to the 20-pin PLD at U104 pin 4 U104 and to pin 31 of the U206 PLCC socket (A18 on 27C040), so access to A18 to pin 1 of the 29F040 might be easiest as a wire from pin 4 of U104.

Also, for the 32-pin SRAM option, A18 is left floating on the PCB, so perhaps attaching a wire to ground at U204 pin 1 (A18) would allow larger capacity SRAM chips to work properly (often easier to source these days!); a floating address pin could lead to unexpected behavior.

[OH2LIY]

Tnx Beerden! I did compare datasheets between 27C040 and 29F040, but probably I was too hurry/lazy and didn't spot that small difference (I did have nagging feeling, that there was something HW differences between proms and flash).


Ramppa

[OH2LIY]

Success! Bend flash pins 1 and 31 up (can be done once). Then use narrow tape strips between flash and socket pins  (I used capton, it worked nicely), and just solder flash pin 1 to  U104 pin 4 and flash pin 31 to closest VCC (pin 32 is closest, just bridge them).


Ramppa

[Beerden]

Success! Bend flash pins 1 and 31 up (can be done once). Then use narrow tape strips between flash and socket pins  (I used capton, it worked nicely), and just solder flash pin 1 to  U104 pin 4 and flash pin 31 to closest VCC (pin 32 is closest, just bridge them).


Ramppa

Thanks! I can also confirm the modification I wrote up also works, I have the MM v1.00 working on what used to be a CM and now have FFT functions!

I elected to jumper over pin 31 to pin 1 with a short tiny wire within the socket body. First though I had to remove the pin 1 pad (ground) from beneath the socket: desoldered the socket pin 1, lifted it up, applied heat to the pad until it separated from the PCB and pulled it out with tweezers. I put kapton tape under pin 1 in case the socket pin touched the original ground via. Then I soldered the wire from pin 1 to pin 31.

This allows me to remove and re-insert the FLASH chip if needed (well, you never know!)



I also replaced the 28-pin SRAM at U204 with a ISSI IS62C1024AL-35QLI which I found on Digi-Key as 706-1041-ND, and there are no problems with using this part.

However, U204 SOP-32 footprint A17 (pin 31) is tied to 5V and A18 (pin 1) is floating. I left that unmodified and everything works fine, but I'm thinking I will experiment with actually connecting A17 and A18 to the signals. I'm anticipating either failure or no change in behavior. Apparently the software doesn't need more than A0-A16 (17 bits) anyway. But keeping A18 from floating is probably a good idea.
 

[shakalnokturn]

Thanks to scopeman-Sam for sharing the files!

I have just done the conversion myself using a M5M51008CFP-70 SRAM and SST28SF040A Flash, both from my scavenged parts stock.
/WE (31) was kapton isolated and left floating (internal pull-up), A18 (1) was kapton isolated from the socket and wired to U104-(4) as seen on photos above.

[Vorlon]

There is a small pin difference between the 27C040 32-pin PLCC and the AM29F040B-90JC 32-pin PLCC:

 pin 1 is Vpp on the 27C040 OTP EPROM, but is A18 (address bit) on the 29F040B
 pin 3 is A18 on the 27C040 OTP EPROM, but is WE# on the 29F040B

This pin difference needs to be corrected to work with the 29F040B; luckily the solution is already provided for by R306 and R307 resistor options for the U302 socket that connects pin 1 to pin 3:

Remove the 39.2 Ohm 1206 size resistor at R306
Install a 1206 size shunt (0 Ohm, or short length of wire) at the empty pads for R307
Insert the 29F040B in the U302 socket

In my TDS220 that wasn't sufficient to run with a 29F040. I also had to isolate the WE# pin and pull it up.

[Nprod]

Also Nprod let us know how you make out!

Something a little strange happened, i used an Atmel 27C040 EPROM for the TDS2MM firmware and when i installed the module, the screen of the scope went blank. Looking at it up close i could make out the boot screen text saying all the self-checks passed - turns out the contrast had gone down by quite a bit. If i boot with the old 27C010 EPROM the contrast returns to its old setting, so it appears that the module is causing a change in the LCD's contrast voltage when running in "TDS2MM mode". The LCD itself is not factory original, i got it from some old stock warehouse on aliexpress and it requires a low contrast setting to look correct for some reason, which made the difference with the MM on more noticeable.

[scopeman]

That's a new one on me. It has been at least 10 years ago when I converted my units and I would have to do a lot of digging to remember what I did then.
All of my units were genuine Tek units with the Tek LCD so I have no clue as to what the problem could be and since schematics for these scopes have been closely guarded by Tek they have never been available AFAIK.

So good luck with that and let me know if you find anything.

Could it have anything to do with the speed of the rom or any configuration jumpers? I don't know.

Sam
W3OHM