tektronix TDSxxx tektool tekfwtool legal modification

[Tantratron]

Hello all,

Some of TDSxxx owners have used either tektool or tekfwtool software for repairing, upgrading through GPIB communication. These tools were developed around 10 years ago by Sven Schnelle in Germany (member DXL). For those with no GPIB interface, there have been options based on floppy disk method developed by Wim De Muynck (member FLYTE) in Belgium.

Early 2020, Ragnar Sunblad (member RAGGE) in Sweden spent lot of time to create a GitHub repository https://github.com/ragges/tektools hosting the different software source file (original C, compiled executable) due to many versions or hard to locate on different servers. Myself in France have forked the repo https://github.com/tantratron/tektools because I'm using MacOS, in fact the general Make file made by Ragnar makes it possible to automatically compile all C files wether Windows, MacOS or Linux.

One interesting situation occured when Mathias Korn (member MADAO) in Germany kind of rewrote a heavy change on tektool.c so it could flash many memories beyond 28F160S5 28F016SA (it is able now to flash 28F008SA 28F010 and 28F020 found in very old TDS models).

Another interesting situation occurred that the tekfwtool would not work correct on 28F160S5 so it would brick my oscilloscope. In the past, the same tekfwtool would brick an oscilloscope on 28F016SA then Ragnar change bit of the program. The tekfwtool now works fine on 28F016A so I’ve decided to understand source code written in C because it bricks any 28F160S5 oscilloscope. The tekfwtool is not easy to understand because it creates kind of 68k cookie downloaded in the DRAM of the TDS so I've decided to rewrite tektool to work on buffer mode for 28F160S5 flash so very fast on its execution.

I plan to write the buffer-page version for 28F016SA later for tektool (maybe do the same for 28F008SA) because the actual unified tektool is very slow when using a GPIB-USB interface. To correct the bug of the tekfwtool is really more complex, one needs a 68K cross compiler which I cannot find working on MacOS.

Matt kindly warned me there is a risk to publish the source file, he did not do it because the legal status or ownership of initial tektool.c and tekfwtool.c are not described anywhere (i.e. no GNU).

So we are in a situation of Github reposting say the original files, tracking where they come from in internet, how to compile them, understand why tektool and tekfwtool do not work both on 28F160S5 and 28F016SA. However if modifying these files like to improve their features or solve bugs (i.e. 28F160S5 and 28F016A, old flashfile types), is it legal to re-use the original work of Sven Schnelle ?

Furthermore does tektronix company could complain even though these TDS500 TDS700 oscilloscope are very old ?

Thanks for any comments, advices and suggestions.

Albert

[coromonadalix]

Well  you could ask Tek  how they would react to this .... having their consent or not is the 1st thing to do

You'll know how to act .... because your coding,  even if you try to protect it in a way could leak in the web ...  or you put a warning that it is not approved by Tek ...

If the 2 github repo havent been taken down is a good sign or not

[dxl]

Feel free to use my source as long as you're using it in GPL2 compatible ways. There's nothing Tek could do about the tekfwtool package i wrote. It just uses the bootloader protocol to download a special firmware and flash the firmware.

[alm]

Well  you could ask Tek  how they would react to this .... having their consent or not is the 1st thing to do

You may not want to wake up sleeping lawyers.

[coromonadalix]

Indeed ....

[madao]

Thanks..

 I'll reading about GPL v2

Then, i'll take time and clean up my source file (specially 28F008SA and 28F0x0 parts ).

I haven't learing  C programming, only  a autodidact and i was bullied from a arrogant programmers.
While i modification and write  "old flash"-part, i have c programming skill since one years.

regards
matt