Who can provide TDS2024C EPROM firmware backup?

[lern01]

The EPROM firmware of one of my TDS2024C oscilloscopes is damaged. I hope that friends from the almighty EEVblog can provide me with a copy.Or the firmware of TDS2004C and 2014C will also work. Thank you very much!
Email:lern01@outlook.com

[darkspr1te]

It's quite possible that no one has it or has access to it. Other reason could be that some users dont daily this site and you may find a answer in a few days.




I dont have the hardware so I cannot help you there. Do you know how to recover it if you get the firmware ? do you know the JTAG pins for programming ?




darkspr1te

[lern01]

It's quite possible that no one has it or has access to it. Other reason could be that some users dont daily this site and you may find a answer in a few days.




I dont have the hardware so I cannot help you there. Do you know how to recover it if you get the firmware ? do you know the JTAG pins for programming ?




darkspr1te

I know, I have a TL866 programmer. I've done other models before.

[eb4fbz]

TDS1000C and TDS2000C all share the same firmware. You can even find the binary inside the Tek official upgrade. https://www.tek.com/en/support/software/firmware/firmware-update-tds1000c-sc-and-tds2000c

[lern01]

TDS1000C and TDS2000C all share the same firmware. You can even find the binary inside the Tek official upgrade. https://www.tek.com/en/support/software/firmware/firmware-update-tds1000c-sc-and-tds2000c

I need .bin or .hex file. Because the firmware in my EPROM is damaged, the oscilloscope cannot be turned on.

[coromonadalix]

and  please dont be pushy  "  No one responded, hey... "    this is not a good behaviour here

wait and be patient,    if some one want to help or can help   you 'll get some answers

[lern01]

and  please dont be pushy  "  No one responded, hey... "    this is not a good behaviour here

wait and be patient,    if some one want to help or can help   you 'll get some answers

sorry. I don't mean anything else.

[lern01]

Waiting for good news

[darkspr1te]

Do you have a dump of the current firmware, even though it's damaged ?  if so can you post it so i can compare it to the update file and maybe figure out it's format , it seems to be a vxworks system by Wind River tech


darkspr1te

[darkspr1te]

I did some hunting around and found that the firmware might be here
http://www.ko4bb.com/getsimple/index.php?id=manuals&dir=Tektronix


 with further info on the device here
https://www.eevblog.com/forum/testgear/reverse-engineering-tds2cmtds2mm/


and
https://www.eevblog.com/forum/repair/tektronix-tds1002/
https://www.eevblog.com/forum/testgear/tektronix-tds1000b-series-hacks/75/


i've looked at the tds100x models and bootloader looks almost identical and found the same data in the firmware flash,


darkspr1te

[lern01]

Do you have a dump of the current firmware, even though it's damaged ?  if so can you post it so i can compare it to the update file and maybe figure out it's format , it seems to be a vxworks system by Wind River tech


darkspr1te

My oscilloscope turned out to be a TDS3014C and was functioning normally. The original plan was to upgrade to TDS2024C, but I forgot to verify it when dumping. It is estimated that wrong data was read during the dumping process. Attached is the file I dumped for your analysis. Thank you for your help!

[lern01]

I have the dump files of TDS2014B and TDS2022C here. They are both good, but I don’t know how to modify them. I have tried patching TDS2014B and TDS2022C firmware to TDS2024C respectively without success. When patching TDS2014B to TDS2024C, the oscilloscope works normally but displays TDS2014B. This is probably because the firmware versions are different. Patch TDS2022C to TDS2024C, after powering on, the three green lights are stuck, probably because the checksum has not been modified correctly.  I have never understood how to modify the checksum.

[darkspr1te]

So I understand this in my head,
You got a TDS2014C (*not TDS3014C) and you dumped the firmware, then you tried to patch to add TDS2024C functions and wrote new firmware, you mention if you use TDS2014B patched to TDS2024C options it does function but not with additional features and still displays TDS2014B as model number ?


Also you say the attached bin dump (in rar format not zip) was the original dump but unverified when read? but not modified?


if you could post the TDS2014B/22C as well, i get a better understanding when I see many firmwares, I start to see patterns


did you try the python auto patch script provided in the links I gave you with the "working TDS2014B" firmware ?


i will look over and have a go at reversing the 68k bootloader first, to see if that has any bearing on it.


darkspr1te

[lern01]

So I understand this in my head,
You got a TDS2014C (*not TDS3014C) and you dumped the firmware, then you tried to patch to add TDS2024C functions and wrote new firmware, you mention if you use TDS2014B patched to TDS2024C options it does function but not with additional features and still displays TDS2014B as model number ?


Also you say the attached bin dump (in rar format not zip) was the original dump but unverified when read? but not modified?


if you could post the TDS2014B/22C as well, i get a better understanding when I see many firmwares, I start to see patterns


did you try the python auto patch script provided in the links I gave you with the "working TDS2014B" firmware ?


i will look over and have a go at reversing the 68k bootloader first, to see if that has any bearing on it.


darkspr1te

Yes, the oscilloscope still displays TDS2014B.

It turns out that I used the python automatic patching script in the link to upgrade to TDS2024C and programmed it into the EPROM, covering the original 2014C firmware in the EPROM. After starting the oscilloscope, the three green lights were always on and the screen turned on and off repeatedly. Since there is no verification when dumping the TDS2014C firmware, there is a problem with the dumped backup. The same phenomenon occurs when the original dumped TDS3014C backup is programmed into EPROM. Attached is the firmware backup of TDS2014B and TDS2022C.

[darkspr1te]

You mentioned TDS3014C again, do you again mean TDS2014C? (please clarify as all i know is the 100x/200x use same code buyt the tds30xx model dont)


Sorry I am just trying to understand all the models here and what you actually have on your desk and what we have in terms of firmware.


I looked at the python patch and seen it does not support C models in code yet , I assume so as the model number (ID)  for the 2022C(TDS2022C_C031908_rom.bin)  firmware is 0x18 and in python script it's 0x0B  for 2022B, so am assuming that with the TDS1001C-EDU having a ID of 0x28 the C models have different ID's so the python patch needs updating for these model id's no doubt as it does define different LCD's and the booting code need to know which ones to use


Which firmware file (unmodified or modded) boots and just displays TDS2014B ?


 do you have the RS232 or GPIB interface ? as we can change model number and bandwidth via this interface , this is already known






darkspr1te

[lern01]

You mentioned TDS3014C again, do you again mean TDS2014C? (please clarify as all i know is the 100x/200x use same code buyt the tds30xx model dont)


Sorry I am just trying to understand all the models here and what you actually have on your desk and what we have in terms of firmware.


I looked at the python patch and seen it does not support C models in code yet , I assume so as the model number (ID)  for the 2022C(TDS2022C_C031908_rom.bin)  firmware is 0x18 and in python script it's 0x0B  for 2022B, so am assuming that with the TDS1001C-EDU having a ID of 0x28 the C models have different ID's so the python patch needs updating for these model id's no doubt as it does define different LCD's and the booting code need to know which ones to use


Which firmware file (unmodified or modded) boots and just displays TDS2014B ?


 do you have the RS232 or GPIB interface ? as we can change model number and bandwidth via this interface , this is already known






darkspr1te

What I have now is TDS2014C, not TDS3014C. python patch supports C model. I upgraded to TDS2022C using TDS2002C and it was successful. TDS2014C only has USB port.