Author Topic: Unified tektool released ! (Firmware flash tools for old Tektronix TDS series) (Read 27054 times)

madao · « **on:** February 12, 2020, 05:47:43 pm »

Hello people

What is unified tektool ? It is a tools, which can dump and write over GPIB memory of Tektronix TDS with 3 digit serie. (except TDS200/300 Series)

Reason for my project with "unified tektool"
https://www.eevblog.com/forum/repair/tekfwtool-for-tds540c-firmware-upgrade/
(Long story)
Short story: tekfwtool can't support other than Flash 28F160S5 (which it is using in later TDS 500D/700D series) and other tektool can only 28F016SA (use in C & early D serie). Need for tools for flashing of older instrument is high.
(Whit this tektool/tekfwtool , you can read and write memory of old instruments, but not program of flash)

I have write tektool, which support all flash type in old TDS serie, it use auto-detection for flash-operation. Since TDS540 with 28F010 up to TDS784D with 28F160S5.
A little disadvantage: Program of flash take much more time (up to 40 minute for unit with 28F020, most ~12-15 minute, with NI PCI-GPIB) Programming with USB-GPIB-Adapter take nearly one hour. tektool & tekfwtool is faster (page programming /small 68k code )
A side notice: unified tektool can also flashing firmware to old TDS400 and new TDS400A serie. (It was a bit difficult, i guess, my TDS420 has not so good flash) But it is POSSIBLE ! :-) (my TDS430A corpse with TDS420 CPU live again)

Supported flash:

Quote

      //0x01a7 = 28F010 (AMD)
      //0x012a = 28F020 (AMD)
      //0x89b4 = 28F010 (intel)
      //0x89bd = 28F020 (intel)
      //0x89a0 = 28F016SA
      //0x89a2 = 28F008SA
      //0xb0d0 = 28F160S5

How to use ?
Connect GPIB cable to o'scope.
Important step: switch unit to "unprotect" and power it -> unit start into bootloader mode.
After success flashing -> switch back to protect.

TDS500-700 serie

TDS400 serie

Quote

0.)identify of flash type (optional, recommend)
   put of string "tektool -i -b 0x1000000 -l 0x10"

1.)save of nvsram (not for TDS400 serie, unknown address)
   put of string "tektool -r example.bin -b 0x4000000 -l 0x20000" (recommend 0x100000)

2.)save of old firmware
   put of string "tektool -r example.bin -b 0x1000000 -l 0x400000" (by 28F010 = 0x180000, by 28F020 = 0x300000 instead 0x400000)

3.) fill zero to flash ( only for old flash as 28F010 and 28F020)
   put of string "tektool -z -b 0x1000000 -l 0x10"


4.)clear of firmware
   put of string "tektool -e -b 0x1000000 -l 0x10"

5.)flashing of firmware
   put of string "tektool -p example.bin -b 0x1000000 -l 0x400000" (by 28F010 = 0x180000, by 28F020 = 0x300000 instead 0x400000)

6.)writing of nvsram (optional, not for TDS400 serie, unknown address)
   put of string "tektool -w example.bin -b 0x4000000 -l 0x20000" (recommend 0x100000)

(VERY recommend: Switch unit off and on, before verify of firmware. Pleas wait 10 seconds after power-it , then switch protect-switch to "protect" for safe verify.)

7.)verify of firmware (optional)
   put of string "tektool -v example.bin -b 0x1000000 -l 0x400000" (28F010= 0x180000, 28F020 = 0x300000 instead 0x400000)


   "example.bin" , you can calling him as you wants, but "*.bin is important.

Notice:
All firmware of flash except 28F010 and 28F020 is "0x400000" (4 MB ) length
28F010 (TDS540 and similar) , "0x180000" (1.5 MB) length
28F020 ( TDS544A, old 700A-Serie) , 0x300000 (3 MB ) length
Notice²: -l = length, little L, not big I

And the most important notice: It is your risk, pleas don't hit me, if your unit is bricked.

A little bad news: C-sourcefile, i want not at frist to publish it. Because i don't know about law & right. It is heavy modified tektool.c to cover all old TDS-instrument. And: I have strange c coding style. I am offended/insulting often for this style.

@ragge, you can contact me for getting of c-sourcefile.

Here a compiled tektool for using with NI-Adapter (GPIB0, IEE488.2 driver from NI) and Windows PC (7 & 10)

tektool.zip (36.61 kB - downloaded 772 times.)

I can compile executable file for you.
Pleas give me sourcefile from your GPIB adapter (Agilent, whatever) and i compile for you.
Sourcefile is most *.h file and *.c or *.obj. Pleas read programmer manual from your gpib adapter.

Greetings
matt

Nx-1997 · « **Reply #1 on:** February 13, 2020, 06:21:03 am »

Thanks. Tested working on TDS620B (Flash type: 28F008SA). GPIB adapter used: 82357B, on Win 10.

madao · « **Reply #2 on:** February 13, 2020, 02:36:49 pm »

Oh, it runs with agilent adapter. But 50 Minute for program is damn slow !
Program on 28F008SA time take with NI PCI-GPIB ~14 minute.

But, most important: It runs.

Can i get TDS620B Firmware ?

Greetings
matt

Nx-1997 · « **Reply #3 on:** February 13, 2020, 07:09:22 pm »

Yes, of course. For NVRAM I used the "0x04000000 -l 0xa0000" address. I think its possible to convert a 620B to 644B and beyond but I haven't really tried anything.

madao · « **Reply #4 on:** February 13, 2020, 08:29:42 pm »

TDS620B Firmware cover also TDS684B,680B , 644B, 640B and 620B.
(I have open this Firmware with notepad++ and search "TDS 620B". TDS620B is not alone.)
In this case, swapping of acquisition board is enough.
But thanks for firmware, i am collecting of firmware for puplishing at someone time.

A little notice: It exists few instrument with hole of 384kb between 128kB (important) and 512kB (not important, only waveform, etc) NVSRAM. Only TDS500A (probably also TDS600A ) Series have 512kB NVSRAM (DS1250/1650) with important dump.

madao · « **Reply #5 on:** February 16, 2020, 01:27:21 pm »

A news notice: unified tektool is capable to program firmware to TDS400A Series (with 28F008SA Flash, 0x400000 length)

It take with NI GPIB-USB-A (old, frist GPIB.-USB from NI) much time (read , it needs ~ 400 seconds ). (very recommed: use GPIB-Card for desktop-PC, it is much faster)

Greetings
matt

charlyd · « **Reply #6 on:** February 25, 2020, 04:24:53 pm »

Hello Madao, this is old info. i assume your are new to the topic tektronix and good to add is that the version tektool & tekfwtool differ a lot.
Not really in what they do but the time to program your firmware with tektool it takes hours for the TDS784D and with tekfwtool a few minutes.

you can also get your EEPROM content with a tool called : getcaldate ( i will check the exactname when i am at home)

madao · « **Reply #7 on:** February 25, 2020, 05:30:53 pm »

Reason, why my unified tektool need more time: It use telegram (2 bytes) for bootloader of TDS instrument and it has much latency. (PCI-GPIB and TDS784D ~1ms, TDS400 is much slower, ~1.5ms )
Sidenotice: USB-based GPIB-controller is famous for slow responsing. If you strech telegram up to 512 bytes and you lose time at only one latency of 1-1.5ms. -> Data transfer is much faster. This way is impossible for flash writing (write-time 10µs ) .

Tekfwtool upload 68k code to TDS instrument's RAM and 68k code receives data-block (512byte) from PC and control flash-programming. This is why, tekfwtool is much faster. tektool (only 28F016SA) use block flash program. It is also faster. Probably, i'll adding block-programming for newer flash for saving time. But i can't write 68k code.

But: you can use tekfwtool for flashing unit with 28F160S5. unified tektool take with NI PCI_GPIB at TDS784D: 14 minutes. Of coruse, i use also tekfwtool, if i want program flash at 500/700D.

Most important: Now, you can program flash at old devices with 28F010/020 & 28F008SA. This was my main goal for unified tektool.
(and you have no risk for buying the spare part with wrong firmware. -> You can buy someone and program with correct firmware, finished !)

Greetings
matt

analogRF · « **Reply #8 on:** May 06, 2020, 10:44:42 pm »

Hi madao,
I used your tool in my setup (win98se, PCI-GPIB, NI488.2 drivers from NI ftp server that were good for win98)
to flash my dead TDS784D. It has two E28F016SA chips.

I can read the NVRAM and the flash. But when I try "-i" option it gives 0x0000 and cannot identify the flash ID
and when I try to program it, again it fails at the start because of the same error (flash ID not identified)

any advice?

youxiaojie · « **Reply #9 on:** May 28, 2020, 08:11:59 pm »

can this program backup the firmware?

pigrew · « **Reply #10 on:** June 07, 2020, 02:00:27 pm »

Quote from: youxiaojie on May 28, 2020, 08:11:59 pm

can this program backup the firmware?

Yes, I was able to do that with the read command (see the first post in this thread (tektool -r example.bin -b 0x1000000 -l 0x400000)).

I used a NI GPIB-USB-HS adapter on Windows 10 to upgrade the firmware of a TDS784D from 7.2e to 7.4e. It took 91 minutes for the firmware write to finish. Enabling HS488 settings for the adapter didn't make any significant speed difference. Reading the firmware was faster, about 70 seconds.

The boot ROM was identical for firmwares 7.2e and 7.4e (there was no need to update it). I did backup the NVRAM, too.

madao · « **Reply #11 on:** June 07, 2020, 03:01:04 pm »

Quote from: analogRF on May 06, 2020, 10:44:42 pm

Hi madao,
I used your tool in my setup (win98se, PCI-GPIB, NI488.2 drivers from NI ftp server that were good for win98)
to flash my dead TDS784D. It has two E28F016SA chips.

I can read the NVRAM and the flash. But when I try "-i" option it gives 0x0000 and cannot identify the flash ID
and when I try to program it, again it fails at the start because of the same error (flash ID not identified)

any advice?

Hello,
have you type "tektool -i -b 0x1000000 -l 0x1" ? (lenght variabel is not important 0x10 or 0x1223, whatever, but base adress must be correct )

It must came Flash ID, if only zero, then is someone on Flash-Ciruit wrong-.

It is correct, without known FlashID is Flashing impossible. It is neccessary, because flash algorithm is not same at all type .

Greetings
matt

Galen · « **Reply #12 on:** June 15, 2020, 08:08:46 am »

Hi Matt, so great you completed this project. I download it and saved as 'Unify tektool'. I don't have opportunity to try it as of now. But thank you very much for developed this tool and clarified many things about the TDSxxx scopes flushing, and your help on my TDS540C firmware updating. Good job Sir!

rodd · « **Reply #13 on:** September 24, 2020, 07:31:54 pm »

Hi,

I have succeeded in using the Unified Tektool with an Agilent 82357B USB/GPIB adapter!!!

Thanks to the replies of madao and NX-1997 I succeeded and would like to post what worked for me.

My setup: Computer with Windows 10 x64, Agilent 82357B USB/GPIB adapter (probably a Chines clone) and Scope: TDS684A.
I started by installing the Keysight IOLibSuite_18_1_25310 and the CommandExpert_MSI_1_9_034.
I started the app and was happy to see that it could connect to the scope.
Then I started a command DOS window (as an admin) and tried Tektools, but it was unable to connect to the scope.
The error message was:
"Unable to open device
ibsta = 0x8000 iberr = 01"
I sent a PM to madao, which siad that this error meant that Tektool was unable to connect to the scope.
He suggested to install the NI-VISA drivers and make sure that I had flipped the protect switch to unprotect ( which I had forgotten to do the first time).
So I searched and found the installer of the NI-VISA drivers called NI IVI Compliance Package.
During install there was a message of conflicting VISA drivers (NI and Keysight).
After installing the driver I tried again without success.
So I PM NX-1997 that had posted in this thread he could do it with the USB/GPIB and Windows 10, and he suggested to " configure the Keysight software to use NI VISA, also configure it to support legacy NI-488.2" and so I did and changed the configuration according to the attached images.
After this last change I could make it work.
I am not sure if there would be necessary to install the NI driver package.

madao · « **Reply #14 on:** September 25, 2020, 04:51:32 am »

I can't help here much, because i have only NI-Adapter.

But few member has success with Keysight /Fakilent USB Adapter.
It must be possible.

My fresh idea: You can try: Start your Tek normal and send *IDN? over communication tool from agilent/Keysight , did it reply?
I have a case, which TLS216 from friend have fried GPIB-ciruit.
And check please: Is your GPIB Adapter setting to GPIB0 ? It may not being GPIB1 and somes.

Greetings
matt

Nx-1997 · « **Reply #15 on:** September 25, 2020, 05:01:56 am »

I used this program with a fake Agilent 82357B on windows 10 to backup and flash the firmware on my tds784d and tds684b. So I can confirm that this program supports Agilent 82357B, fake and genuine ones. Its good practice to install NI visa because Keysight visa is usually not supported by many softwares. For example, python library pyvisa only supports NI visa.

I wonder if we can mod the firmware to include more features, unfortunately I am not skilled enough to pull this off.

lucatz · « **Reply #16 on:** November 06, 2020, 11:00:20 pm »

Hi All,

Where do we find TDS latest firmware files? Tektronix does not post officially it seems

Thanks
Luca

Nx-1997 · « **Reply #17 on:** November 07, 2020, 04:55:35 am »

Search on this website: http://w.ko4bb.com/getsimple/index.php?id=manuals&dir=Tektronix/Tektronix_-_TDS5xx_TDS6xx_TDS7xx_Digital_Phosphore_Oscilloscopes

madao · « **Reply #18 on:** November 27, 2020, 08:16:46 pm »

Or ask me !

If you wanted a TDS540D Firmware, you can use TDS784D Firmware. Explain: TDS500/700 firmware is since C serie same. But you must stay to frist firmware-count. You can't use Firmware 7.4e from TDS784D on TDS784D with 6.3e. You can update from 5.0e to 5.3e (i am looking after this firmware), but not to 6.6e.

Greetings
matt

lucatz · « **Reply #19 on:** November 27, 2020, 08:45:01 pm »

Hi Madao,

I have TDS540a with version 3.8.3e. I found some other ones on ko4bb that seem compatible with version 3.8.7e. I basically look into file in hex mode to see if my 540A shows in list. If you have anything more recent would be happy to get it. Does upgrading FW erase calibration? I used your tool ( Thank YOU

) to backup mine and also backed up NVram. Hopefully when bat goes out i will be in good posture to restore.

james_s · « **Reply #20 on:** November 27, 2020, 10:05:32 pm »

Is it possible to get this to support the Prologix USB GPIB adapters? Due to some clones that have been developed Prologix is rapidly becoming the defacto standard, at least for hobbyists.

madao · « **Reply #21 on:** November 28, 2020, 06:57:49 pm »

If you give me source file for prologix GPIB controller, then is it possible.

Or: can you try with this tektool ? (This tektool run with agilent & NI controller)

@lucatz

yes , it is in most case possible: upgrade without losing of calibration data, because most firmware use same calibration data schema.
If it is failed, you can going back to old firmware.

james_s · « **Reply #22 on:** November 28, 2020, 09:50:50 pm »

The thread is here: https://www.eevblog.com/forum/projects/ar488-arduino-based-gpib-adapter/

It enumerates as a USB serial port and uses mostly standard GPIB commands.

SergeyMinin · « **Reply #23 on:** December 13, 2020, 01:40:42 pm »

Hey. My TDS 654C oscilloscope has firmware version v5.1e. Does anyone have a newer firmware version for the TDS 654C? And please tell me is it true that version v5.2e from TDS 784C is suitable for my oscilloscope?

Sergey

madao · « **Reply #24 on:** December 13, 2020, 01:50:55 pm »

No, TDS500/700 and TDS600 is extremely difference by acquisition board. You can put newest TDS500 Firmware to TDS700, if suffix is same. But never to TDS600. Same with TDS600 firmware at 500/700 units. Difference between 500/700 is minor by software. (no colour display, it is all !)

A luck, you have asked me :-)

Greetings
matt

madao · « **Reply #25 on:** December 13, 2020, 01:52:48 pm »

Quote from: james_s on November 28, 2020, 09:50:50 pm

The thread is here: https://www.eevblog.com/forum/projects/ar488-arduino-based-gpib-adapter/

It enumerates as a USB serial port and uses mostly standard GPIB commands.

Oh, it look good, but i must take time for him. (actually , i have less time :-/ )

vaualbus · « **Reply #26 on:** May 01, 2021, 11:05:12 pm »

Were you find those firmware list? I'm looking if possible to update my TDS firmware to newer mine is 2.13 I see there a 2.16e.
You think is that possible? I guess there has not diffs between the version?

hgross · « **Reply #27 on:** June 05, 2021, 12:24:27 pm »

Hello Matt (madao),
Thank you very much for your tektool. Together with Ghidra it opens new possibilities for me to understand and hopefully repair old TDSxxx Scopes. I was able to repair a TDS644A and it seems to work 100 % o.k. but the self test fails due to the digACCalDiag test. The built-in frequency test range seems to be set too narrow. Either my firmware (3.8.5e), which I have copied from KO4BB is not good for my TDS644A or something in the file is corrupt. Could anyone in this forum provide a similar or even newer firmware for the TDS6xxA series?
Regards
Helmut, DL5HG

vaualbus · « **Reply #28 on:** June 17, 2021, 03:25:09 pm »

We shall reverse engineer the firmware yeah, apparently reading the extended service manual I got for the TDS540A they had a tool that described and allow to execute any of the diagnostics procedures tha the TDS520 repair manual suggest to run. I guess there is ay to write such a a program our self and finally allow to simplify the repairs of these scopes.

vaualbus · « **Reply #29 on:** June 17, 2021, 03:32:10 pm »

Can you provide the tools for Win98/95 so we can use with the official card suggest in the manuals that is the ISA National GPIB-PCII/IIA Card?

drforbin · « **Reply #30 on:** June 20, 2021, 12:17:15 am »

I'd like source code if possible

eurgenca · « **Reply #31 on:** September 18, 2021, 08:59:44 am »

Hello, Matt.
I have a faulty tds420a and I want to play with your software. I don't have GPIB adapter and need to buy one.
Does this sw work with USB to GPIB adapters or I must find some ISA/PCI card?
Thanks, Sebastijan.

madao · « **Reply #32 on:** September 18, 2021, 11:50:47 am »

100% confirm: it works with NI GPIB Adapter, USB or PCI or PCIe, is not important. Important is NI 488.2

(not 100% confirm, work with agilent GPIB-USB Adapter, doze people told me, it works)

eurgenca · « **Reply #33 on:** September 18, 2021, 01:00:14 pm »

Hello.
So this chinese clone will be o.k.?

https://www.aliexpress.com/item/1005002298355146.html?spm=a2g0s.8937460.0.0.67972e0e7Yk0v5

Sebastijan.

Tantratron · « **Reply #34 on:** September 18, 2021, 03:39:01 pm »

Quote from: eurgenca on September 18, 2021, 01:00:14 pm

Hello.
So this chinese clone will be o.k.?

https://www.aliexpress.com/item/1005002298355146.html?spm=a2g0s.8937460.0.0.67972e0e7Yk0v5

Sebastijan.

If I were you, best to buy a used NI-GPIB-USB (made in Hungary) where for sure it works including with Macintosh.

eurgenca · « **Reply #35 on:** September 18, 2021, 04:26:43 pm »

Hi. I suppose you thinking on something like this:

https://www.aliexpress.com/item/32827480178.html?spm=a2g0s.8937460.0.0.78302e0e8V6ayj

Tantratron · « **Reply #36 on:** September 18, 2021, 04:43:13 pm »

Quote from: eurgenca on September 18, 2021, 04:26:43 pm

Hi. I suppose you thinking on something like this:

https://www.aliexpress.com/item/32827480178.html?spm=a2g0s.8937460.0.0.78302e0e8V6ayj

Yes that is correct but be careful with Chinese clone because there could be firmware issues. But that is the correct model except they do not show what is printed on its back. My company TANTRATRON in France has bought recently 5 used of these units from Europe, in fact from Hungary via eBay.

The advantage of these legacy NI (National Instruments) is that NI offers free software for Windows, MacOS and Linux so you can really do very serious stuff with TDSxxx and other test lab projects. I do use MacOS only for years where it is not clear if Agilent is so Universal with different platform.

Ironically the chinese clone of NI-GPIB-USB states original from Hungary but someone needs to explain why these units are sold from China... there must a catch but maybe I'm too paranoid

Albert

Tantratron · « **Reply #37 on:** September 20, 2021, 08:47:04 am »

P.S. Regarding chinese clone of National Instruments NI-GPIB-USB issues, there is one interesting thread https://www.electronics-lab.com/community/index.php?/topic/48408-ni-gpib-usb-hs-issues-no-original-fake-hack-firmware-replacement-from-orginal/&tab=comments#comment-165981

eurgenca · « **Reply #38 on:** September 20, 2021, 02:36:46 pm »

Yes I read that.
Today I bought this clone from max-bit but I only need this adapter for firmware upgrade and other testing. If this works with sw ver 17.0 I think that is this good for me.

lastguy · « **Reply #39 on:** September 20, 2021, 06:50:24 pm »

Interesting to found the problem is not counterfeit from China, but NS 17.6 added counterfeit check, to make it works NS removed all its older legal parts, so these NS parts becomes counterfeil.
the solution is to use NS 17.0. not sure current solution.

HighPrecision · « **Reply #40 on:** September 23, 2021, 05:15:43 pm »

Hi,

I'm trying to update the firmware of an old TDS744A scope (s/n: B012xxx), using the unified tektool software, my PC is the Thinkpad X301 with Win7, installed NI-488.2 v20 connected with interface 'GPIB-USB-HS'.

ID of flash chips is: 0x012a = 28F020 (AMD)

I'm getting this errors with backup commands for NVRAM and Flash:
"read_memory: response reading failed"

I used these commands to read:
tektool -r NVRAM-original.bin -b 0x4000000 -l 0xA0000
tektool -r OLDFW-backup.bin -b 0x1000000 -l 0x300000

Any idea to resolve this problem ?

Thanks!

HighPrecision · « **Reply #41 on:** September 24, 2021, 08:04:10 am »

Problem solved relaxing GPIB interface timing.

DC1MC · « **Reply #42 on:** September 24, 2021, 08:16:47 am »

Hello all, maybe someone here could help me, could anybody provide a firmware version newer than 4.1 for a TDS724A ? My previous request got totally buried

.

Many thanks,
DC1MC

HighPrecision · « **Reply #43 on:** September 24, 2021, 09:16:17 am »

Hello,

I've found firmware v4.2.1e for my TDS744A, same oscilloscope with 4 input channels.

DC1MC · « **Reply #44 on:** September 24, 2021, 10:53:01 am »

Quote from: HighPrecision on September 24, 2021, 09:16:17 am

Hello,

I've found firmware v4.2.1e for my TDS744A, same oscilloscope with 4 input channels.

I found it as well, the problem is that TDS724A is the strange animal with 2+2 channels and I don't know if it's compatible

.

madao · « **Reply #45 on:** September 24, 2021, 05:05:16 pm »

Quote from: DC1MC on September 24, 2021, 10:53:01 am

Quote from: HighPrecision on September 24, 2021, 09:16:17 am
Hello,

I've found firmware v4.2.1e for my TDS744A, same oscilloscope with 4 input channels.

I found it as well, the problem is that TDS724A is the strange animal with 2+2 channels and I don't know if it's compatible .

This newer firmware will work with your units.

DC1MC · « **Reply #46 on:** September 24, 2021, 05:26:20 pm »

Quote from: madao on September 24, 2021, 05:05:16 pm

Quote from: DC1MC on September 24, 2021, 10:53:01 am
Quote from: HighPrecision on September 24, 2021, 09:16:17 am
Hello,

I've found firmware v4.2.1e for my TDS744A, same oscilloscope with 4 input channels.

I found it as well, the problem is that TDS724A is the strange animal with 2+2 channels and I don't know if it's compatible .

Many thanks @madao for taking the time to check, unfortunately after fiddling a bit with the heavy guys (520A and the 724A) I've decided to set them free for younger and stronger people , see the TEA thread and BSW forum soon, the new owners could take care of updating the FW and doing the upgrading tricks.

Cheers,
DC1MC

This newer firmware will work with your units.

TERRA Operative · « **Reply #47 on:** October 20, 2021, 03:44:28 am »

I successfully updated the firmware on my older version TDS784C from 5.0a to 5.2e, using an ebay sourced Keysight 82357B USB-GPIB adapter.
Here's the full instructions on how I did it, combining info from madao and rodd.

1.) Install Keysight IO Controls and set settings as shown in the included images. (This is important to allow tektools utility to access the GPIB adapter!)

2.) Run IO Controls (Icon should appear in task bar) and run Keysight Connection Expert.

3.) Plug 82357B USB-GPIB adapter into PC and scope. Turn hidden switch in scope to unprotected mode and turn on scope.

4.) Check for the scope appearing in Keysight Connection Expert as shown in the included image.

5.) Open Command Prompt and navigate to folder containing tektool.exe

6.) Type in the following commands shown in quotes (don't type the quote marks).

7.) Identify flash type "tektool -i -b 0x1000000 -l 0x10"

8.) Save existing NVSRAM (not for TDS400 series, unknown address) "tektool -r NVSRAMSave.bin -b 0x4000000 -l 0x100000"

9.) Save old firmware "tektool -r example.bin -b 0x1000000 -l 0x400000" (28F010 = 0x180000, 28F020 = 0x300000 instead of 0x400000)
(example.bin = name of existing firmware file)

10.) Fill zero to flash (only for old flash 28F010 and 28F020) "tektool -z -b 0x1000000 -l 0x10"

11.) Clear firmware "tektool -e -b 0x1000000 -l 0x10"

12.) Flash new firmware "tektool -p example.bin -b 0x1000000 -l 0x400000" (28F010 = 0x180000, 28F020 = 0x300000 instead of 0x400000)
(example.bin = name of new firmware file)
This will take a while. On a TDS784C, it took just under 45 minutes or so.

13.) Writing NVSRAM back into memory (optional, not for TDS400 series, unknown address) "tektool -w NVSRAMSave.bin -b 0x4000000 -l 0x100000"

14.) IMPORTANT: Power cycle unit before verification of firmware. Wait 10 seconds after power-on, then switch protect-switch to "protect" for safe verification.

15.) Verification of firmware "tektool -v example.bin -b 0x1000000 -l 0x400000" (28F010= 0x180000, 28F020 = 0x300000 instead of 0x400000)
(example.bin = name of newly flashed firmware file)

16.) Reboot scope, enjoy.

16a.) I did a factory reset on my scope for good measure, just to make sure there were no incompatible settings etc from the old firmware to the new firmware.

Johnny10 · « **Reply #48 on:** October 20, 2021, 07:25:57 am »

picburner · « **Reply #49 on:** October 21, 2021, 02:35:58 pm »

There is also a firmware v5.3 for the TDS784C, someone in this forum owns it but has never made it available.

TERRA Operative · « **Reply #50 on:** October 23, 2021, 11:29:13 am »

Quote from: picburner on October 21, 2021, 02:35:58 pm

There is also a firmware v5.3 for the TDS784C, someone in this forum owns it but has never made it available.

Ooh, do you know who?

Tantratron · « **Reply #51 on:** October 23, 2021, 11:46:34 am »

Quote from: TERRA Operative on October 23, 2021, 11:29:13 am

Quote from: picburner on October 21, 2021, 02:35:58 pm
There is also a firmware v5.3 for the TDS784C, someone in this forum owns it but has never made it available.

Ooh, do you know who?

picburner is right, there are out there some of these TDS with 5.3e firmware but nobody is willing to GPIB extract then share. Few weeks ago, I almost bought a TDS540C on eBay-France where the partially failed scope did have the 5.3e but price was too high plus its acquisition board was not 1M neither 2M. For the moment, I only use 5.2e for C series and 6.6e for D series where no idea if there is an improvement if using 5.3e versus 5.2e for C series.

TERRA Operative · « **Reply #52 on:** October 23, 2021, 04:46:36 pm »

Can you send me whatever firmware versions you have? (I have 5.0e and 5.2e already)? I'll post them to the tekwiki for future reference.

https://w140.com/tekwiki/wiki/TDS784

picburner · « **Reply #53 on:** October 23, 2021, 05:20:09 pm »

I read about this firmware some time ago in this forum in a topic regarding the old TDS scopes, now I can't find it.
You can find all the latest firmware releases of the old TDS on the ko4bb website.
I have a TDS784C with firmware v5.2e

Ross2 · « **Reply #54 on:** February 25, 2022, 06:44:06 am »

I have V5.3e but I have been having a problem getting connected to the gbic port with a usb to gbic.

TERRA Operative · « **Reply #55 on:** February 25, 2022, 07:49:14 am »

What GPIB-USB adapter are you using? I have the Agilent/Keysight one found on ebay and using the Keysight IO software works fine.

I am very interested in a copy of your firmware if we can figure out how to get it copied out.

Ross2 · « **Reply #56 on:** February 25, 2022, 09:09:37 am »

I Just have a cheap "UGPlus USB to GPIB" from ebay. I just ordered the Keysight 82357b. I'm not sure it that's the issue, It could be something that I am doing wrong. I can not turn off the "Off Bus" setting on the GBIP settings on ether scope. I tried it on a TDS640a and a TDS754c that was upgraded to a TDA784c. It's under Utility - System Config - IO - GPIB.

picburner · « **Reply #57 on:** February 25, 2022, 09:43:55 am »

These inexpensive adapters "live on their own" in the sense that they do not meet the VISA standard.

In fact, in the product description it says: "The software includes ASCII format command/data transfer functions and binary data/file transfer functions between PC and GPIB equipment. We already compact everything you need for driving the equipment with GPIB interface. Therefore, you can eliminate the complicated VISA library ".

The problem is that just for this reason they are not compatible with applications that use the VISA standard as in the case of "Unified Tektool"

Tantratron · « **Reply #58 on:** February 25, 2022, 11:26:24 am »

I've been using my MacBook Air and the legacy GPIB-USB from National Instruments, it works very good with many operations.

picburner · « **Reply #59 on:** February 25, 2022, 01:51:48 pm »

In fact, I was referring to Ross2's "UGPlus USB to GPIB" adapter.
There should be no problems whatsoever with adapters from Keysight and National Instruments.

TERRA Operative · « **Reply #60 on:** February 25, 2022, 04:44:58 pm »

Quote from: Ross2 on February 25, 2022, 09:09:37 am

I just ordered the Keysight 82357b. I'm not sure it that's the issue, It could be something that I am doing wrong. I can not turn off the "Off Bus" setting on the GBIP settings on ether scope. I tried it on a TDS640a and a TDS754c that was upgraded to a TDA784c. It's under Utility - System Config - IO - GPIB.

I don't change any GPIB settings in the scope after a factory reset and the connection works fine, tested with 7 different scopes now. Once you get the Keysight GPIB adapter, you should be able to connect.

I just got the HDD option for my scope installed, but minimum firmware required seems to be 5.3 (I have 5.2) so I'm waiting with bated breath to get a copy of your firmware now.

madao · « **Reply #61 on:** February 25, 2022, 05:40:13 pm »

yes, pleas save this firmware :-)

unified Tektool (same as orginal tekfwtool & tektool) requiered (NI) VISA Interface. But few people told it already.

Tantratron · « **Reply #62 on:** February 26, 2022, 05:57:05 am »

P.S. You might check this repository https://github.com/ragges/tektools

Tantratron · « **Reply #63 on:** March 02, 2022, 05:39:44 am »

Quote from: Ross2 on February 25, 2022, 06:44:06 am

I have V5.3e but I have been having a problem getting connected to the gbic port with a usb to gbic.
(Attachment Link)

It would be great to have a copy of 5.3e firmware, thank you

TERRA Operative · « **Reply #64 on:** March 19, 2022, 03:02:44 pm »

Just a bump as a reminder to Ross2 to copy out that 5.3e firmware.

Ross2 · « **Reply #65 on:** March 23, 2022, 04:54:02 am »

Coming soon

Display went bad, it has been repaired. so far, I connected to the GPIB queried the port and got a response.

I have several other TDS scopes to repair and upgrade. 540, 640, 644 and a 744. I will be looking for information on upgrading and the newest firmware and soft option to enable.

Thank you

TERRA Operative · « **Reply #66 on:** March 23, 2022, 06:24:05 am »

I can help you with the firmware/option upgrades for the TDS600/700

If you have the means for calibration, you can increase the bandwidth limit too.

Ross2 · « **Reply #67 on:** March 23, 2022, 07:57:25 am »

TY. That would be great. I noticed that there a 2 empty spam pads, I was thinking of increasing the sram. Is there any benefit increasing it?

madao · « **Reply #68 on:** March 23, 2022, 02:28:34 pm »

two empty SRAM pad near D1 connector: it is "for future use", which it is never used.

NathanFulton · « **Reply #69 on:** April 03, 2022, 03:16:14 am »

Hey I just scored a TDS 754C that was decommissioned from a calibration lab not too long ago cause it had some minor problems. Just checked the firmware and...

I've been following your TDS 6/7/8XX repair videos on youtube and would love to help out. I don't have a USB-GPIB interface but I have been building a DOS 6.22-based NI GPIB-PCII/IIA rig. I've gotten as far as installing TDS700C Field Adjustment and NI-488.2 DOS software and having it recognize the GPIB card, but I can't get Field Adjustment software to see the scope...

Think it would be possible to dump the firmware with this old-school setup? I've only just started tinkering with this so hopefully I can figure out whatever config problem I have to get it working. Meanwhile, I've already used the software from here: https://www.eevblog.com/forum/testgear/tektronix-tds500600700-nvram-floppy-dump-tool/ to dump the NVRAM contents in anticipation of replacing the aging Dallas chips. I don't suppose the firmware is already in that dump, is it?

Lemme know if you have any ideas.

--------------------
Edit:
I was able to get Field Adjustment working thanks to this thread: https://www.eevblog.com/forum/testgear/tektronix-tds700a-field-adjust-software-help-needed/ The dips/jumpers on my card weren't set correctly.

I tried running tektool.exe in DOS 6.22 and unfortunately it just says "This program cannot be run in DOS mode."
Let me see if I can get a slightly more modern OS on this thing...

TERRA Operative · « **Reply #70 on:** April 03, 2022, 03:57:48 am »

Oh nice. I'm happy to help out where I can.
Feel free to start a new thread with your questions, and Iink me to it and I'll help wherever I can.

As for dumping the firmware, the tool in this thread might possibly work on your computer as it is DOS based.
The NVRAM dump is only that, the Firmware is a second thing that is dumped out seperately.

For the GPIB connection, try disabling anything and everything that's not needed in your BIOS (serial ports, parallel ports, etc) to remove possibility for addressing conflicts.
Then also do a factory reset on your scope to make sure there's no hidden settings messing things up.

NathanFulton · « **Reply #71 on:** April 03, 2022, 07:33:01 pm »

Just a trip report: I got TekTool running after installing Win98, but it can't seem to find the scope. I tried changing the GPIB address between 0 and 1 but no luck. The Field Adjustment software still works under these conditions and can still see the scope.

My current config is:
Windows 98 SE
National Instruments GPIB-PCII/IIA Rev 1 ISA card, configured like this: https://www.eevblog.com/forum/testgear/tektronix-tds700a-field-adjust-software-help-needed/msg563939/#msg563939

I'm gonna be busy for most of today but I intend to keep poking at it...

NathanFulton · « **Reply #72 on:** April 04, 2022, 05:45:27 am »

Alright I got it! I have not verified this with hardware, but looks good from a cursory glance with HxD. "$VersionString: FV:v5.3e"

I needed to install drivers/software found here: ftp://ftp.ni.com/support/gpib/win98-95/drv-english and then configure the dip switch again to account for the new default resources Win98 assigned to it. It was the 2B8 config found in the example on page 2-10 (26) here: https://www.apexwaves.com/pdf/manuals/GPIB-PCII/archived--getting-started-with-your-gpib-pcii-iia-and-the-gpib-software-for-windows-98-95-and-specifications.pdf

madao · « **Reply #73 on:** April 04, 2022, 05:52:41 am »

I have a quesition: Did run unified tektool on win98se and old NI GPIB card ?

(big thanks for 5.3e Firmware)

NathanFulton · « **Reply #74 on:** April 04, 2022, 06:02:44 am »

Quote from: madao on April 04, 2022, 05:52:41 am

I have a quesition: Did run unified tektool on win98se and old NI GPIB card ?

(big thanks for 5.3e Firmware)

You're very welcome, thank you for making this possible! And yes, I noted my basic setup above. My major troubles were just finding correct info about the hardware/drivers and getting them configured correctly. Once I could get to a state where the NI software could talk to the card, Unified Tektool was able to work just fine.

TERRA Operative · « **Reply #75 on:** April 04, 2022, 01:48:45 pm »

I just upgraded my TDS784C to 5.3e, and it worked fine. Awesome! Big thanks to NathanFulton!

picburner · « **Reply #76 on:** April 27, 2022, 05:47:35 pm »

Me too have successfully updated my TDS784C to v5.3e.
Time taken 1132 seconds with an NI pcmcia card and 28f016sa flash memory.

calmissile · « **Reply #77 on:** May 27, 2022, 02:07:20 am »

Could someone please post or email me a compiled version of TekTool or TekFWtool for DOS or WIN98.
I am using a NI PCII/IIA GPIB board that works fine.

Doug W6GOT
calmissile@gmail.com

madao · « **Reply #78 on:** May 28, 2022, 05:54:26 am »

Hi calmissle

Excuse me, i wouldn't compile software for old PCII/IIA card, because.
I must installed compiler for MS-DOS and searching source file for this card.
But i want check, does work it with Win XP and Win9x and NI 488.2 software?

My software ability is low.

DC1MC · « **Reply #79 on:** May 28, 2022, 10:13:16 am »

The one from here doesn't work ?

https://github.com/fenugrec/tekfwtool

I have a wonderful Virtual Box with Borland C++ 3.1 that I can make available to @madao or compile it myself as long as you have the card drivers and library.

NathanFulton · « **Reply #80 on:** June 06, 2022, 07:33:55 am »

Quote from: calmissile on May 27, 2022, 02:07:20 am

Could someone please post or email me a compiled version of TekTool or TekFWtool for DOS or WIN98.
I am using a NI PCII/IIA GPIB board that works fine.

I was able to get Unified TekTool running on Win98SE. I needed to put this DLL in the same directory as tektool.exe to get it to work. It comes from the Visual C++ redistributable from around 1998.

jeroen74 · « **Reply #81 on:** October 22, 2022, 04:33:31 pm »

Would these tools work with a very early TDS540 (no suffix) with probably the oldest firmware around? It still works, and I don't know if the NVRAM has ever been replaced so I want to back it up before it starts dying.

TERRA Operative · « **Reply #82 on:** October 22, 2022, 05:40:28 pm »

Copying out the firmware and NVRAM won't hurt anything, so worth a try.

If you get it out successfully, feel free to post it here and let us know the firmware version so I can upload it to Tekwiki for posterity.

jeroen74 · « **Reply #83 on:** October 22, 2022, 06:38:52 pm »

Just went to check the firmware, it's v1.10e.

jeroen74 · « **Reply #84 on:** October 24, 2022, 02:18:31 pm »

So I tried to get it to work today, and surprisingly, after installing all the stuff for the NI GPIB-USB-B adapter the tool works right-away.

I can't get it to identify the Flash chips though:

Code: [Select]

C:\tektools>tektool5 -i -b 0x1000000 -l 0x10
base: 01000000
Flash ID1: 0x89898989
identify failed

I managed to download the firmware, but I have no idea if it's actually a proper image

There's readable text in it that make sense but could as well be an incomplete image.

Used this command to get the attached bin file.

Code: [Select]

tektool5 -r fw1_10e.bin -b 0x1000000 -l 0x400000

DonnieJ · « **Reply #85 on:** December 06, 2022, 05:36:12 am »

After getting this TDS684B serial B010740 running again, first order of business was to set about backing up the battery backed up RAM modules. I found this https://github.com/ragges/tektools and specifically https://github.com/ragges/tektools/tree/master/tdsNvramFloppyTool/tdsNvramFloppyDumper doesn’t work. I had to use the Minimal version https://github.com/ragges/tektools/tree/master/tdsNvramFloppyTool/tdsNvramMinimalFloppyDumper which put the NVRAM on the floppy disk. I used the minimal EEPROM dumper to also dump the acquisition board factory calibration. Files below in the B010740 archive.

The question is why did the non minimal version not work?

I found Tom Verbeure’s work here https://tomverbeure.github.io/2020/07/11/Option-Hacking-the-Tektronix-TDS-420A.html  TDS420 is slightly different family, but using the same basic architecture. He documents using Ghidra to look at the ROMs.  The ROM in this TDS684B is version 4.3e, but I decided to work on 4.4.1e in Ghidra because that is where this thing will likely end up. The C programs in symext.zip below generate symbol tables to load into Ghidra from the ROM images.

Of course, these have VXWorks, and the internal ’shell’ will run any C function that is in the ROM symbol table. The non minimal version is trying to spawn a task from the startup.bat file on the disk:

taskSpawn ("nvramdumper",1,0x0,40000,sysExecScript,"fd0:/nvdump.app”)

The v4.4.1e (and v4.3e) ROMs don’t have an sysExecScript() function (at least in the symbol table), and so this fails. But after some work in Ghidra setting up decompiling (loading symbols, manually and automatically, manually finding code segments), there is a lot we can do. This https://www.ing.iac.es/~docs/external/vxworks.old/Programmers-Guide-5.4.pdf and https://www.ecb.torontomu.ca/~courses/ee8205/Data-Sheets/Tornado-VxWorks/vxworks/ref/loadLib.html suggest that we can load a.out format 68k code directly into memory.

So, let’s build a compiler. See the script compiler-build.sh below in 'C for TDS.zip'. It took a bit of doing because the specific versions are critical... bit rot means that (basically) only these versions support m68k a.out, and also running on x86-64 linux. Then we can try a simple hello world program:

jeff:~/work/m68k$ cat t.c
extern int open(char * n, int f, int m);
extern int write(int fd, char * buf, int n);
extern void close(int fd);

void do_it()
{
  int fd;

  fd=open("fd0:/test.txt",0x0202,0x01ff);
  write(fd, "Hello!", 6);
  close(fd);
}
jeff:~/work/m68k$
jeff:~/work/m68k$ ./usr/bin/m68k-aout-gcc -Os -c t.c

In theory, we just copy the .o object file over to a floppy, and have the scope load it in startup.bat (files in C for TDS.zip). Then put the floppy in and power on… and see the screen shot.

TEST.TXT is created on the disk, along with LOG.TXT that startup.bat created. Here is what they contain:

jeff:$ cat /Volumes/NO\ NAME/LOG.TXT
value = 4 = 0x4
ioGlobalStdSet(2,outdev)
value = 8 = 0x8

printf("Log test %d\n", 42)
Log test 42
value = 12 = 0xc

printf("running ls\n");
running ls
value = 11 = 0xb
ls "fd0:/"
STARTUP.BAT
T.C
T.O
T.S
FSEVEN~1
value = 0 = 0x0

printf("loading module...\n");
loading module...
value = 18 = 0x12
fd=open("fd0:/t.o",0,0777)
new symbol "fd" added to symbol table.
fd = 0x51ede30: value = 7 = 0x7
loadModule(fd, 1)
value = 0 = 0x0
close(fd)
value = 0 = 0x0

printf(" done.\nRun do_it\n")
done.
Run do_it
value = 17 = 0x11

do_it()
value = 0 = 0x0

printf("exiting script\n")
exiting script
value = 15 = 0xf
close(outdev)
jeff:$
jeff:$
jeff:$ cat /Volumes/NO\ NAME/TEST.TXT
Hello!

Yup. We can write code for these scopes in C.

DonnieJ · « **Reply #86 on:** December 27, 2022, 06:16:51 am »

Traveling the road others have gone... here is a first pass source code and binary of a tektool variant (pretty much a re-write):
- that works with AR488 (and maybe Prologix) GPIB adapters.
- runs on Unix-like systems
- limited for the moment to 28F008SA flash, but easily changed
- is fairly fast (about 20min) to write a TDS684B firmware, uses extensive target device side code
- but is still a little cranky, mostly timeout issues with AR488.

Binaries in here are for MacOS X, but it can easily be compiled for Linux. AR488 may need some of my patches also, I've not pushed them upstream yet.
See the readme in the archive for my notes, WIP.

I've successfully updated scope B010470 from 4.2e to 4.4.1e... which I think is the last release. Hopefully solves some strange vxWorks behavior I was seeing.

Looking for collaborators, even in person (back in Tokyo after the holidays), for testing at least on other TDS hardware.

Cheers, and happy holidays.

TERRA Operative · « **Reply #87 on:** December 27, 2022, 01:44:14 pm »

I have the following scopes in my collection I can toy with, as long as they won't get bricked (I want to eventually sell them!), I'm also in Chiba but work in Tokyo, so not too far away.

I only have the Agilent GPIB - USB adapter, a Contec GPIB - PCMCIA card, and the National Instruments PCII/IIA card in my DOC PC though so I can't do extensive testing with other more modern GPIB adapters.

TDS620B
TDS644A
TDS680B
TDS714L
TDS754D
TDS784C

Tantratron · « **Reply #88 on:** January 11, 2023, 02:59:58 pm »

Quote from: madao on February 12, 2020, 05:47:43 pm

Short story: tekfwtool can't support other than Flash 28F160S5 (which it is using in later TDS 500D/700D series) and other tektool can only 28F016SA (use in C & early D serie). Need for tools for flashing of older instrument is high.

Quote from: madao on February 25, 2020, 05:30:53 pm

But: you can use tekfwtool for flashing unit with 28F160S5. unified tektool take with NI PCI_GPIB at TDS784D: 14 minutes. Of coruse, i use also tekfwtool, if i want program flash at 500/700D.

Hello and Happy New year,

As for as I know, the tekfwtool unfortunately does not work on 28F160S5 flashfile memories as stated above.

You might want to read my recent experience of bricking one TDS754D and one TDS784D in this post https://www.eevblog.com/forum/repair/tekfwtool-for-tds540c-firmware-upgrade/msg4619995/#msg4619995 when using tekFWtool.

Tekfwtool is very fast to flash 28F016A with success but very fast to brick 28F160S5.

Unless proven wrong, at your own risk.

Albert

madao · « **Reply #89 on:** January 11, 2023, 04:43:36 pm »

Quote from: jeroen74 on October 24, 2022, 02:18:31 pm

So I tried to get it to work today, and surprisingly, after installing all the stuff for the NI GPIB-USB-B adapter the tool works right-away.

I can't get it to identify the Flash chips though:
Code: [Select]
C:\tektools>tektool5 -i -b 0x1000000 -l 0x10 base: 01000000 Flash ID1: 0x89898989 identify failed
I managed to download the firmware, but I have no idea if it's actually a proper image There's readable text in it that make sense but could as well be an incomplete image.

Used this command to get the attached bin file.
Code: [Select]
tektool5 -r fw1_10e.bin -b 0x1000000 -l 0x400000

This "tektool5" is not my "unified tektool"

unified tektool is capable programming flash of very old TDS540.
you can downloading it on first post here (pleas scroll to end of first posting, download " tektool.zip" )
https://www.eevblog.com/forum/repair/unified-tektool-released-!-(firmware-flash-tools-for-old-tds-series)/msg2915458/#msg2915458

Fuma · « **Reply #90 on:** June 17, 2023, 09:48:54 am »

Hello, I have a problem programming the flash 28F010.
If I use the command "tektool -p example.bin -b 0x1000000 -l 0x180000" they are only programmed the flash from 0x1080000 to 0x1100000 ( bank 2 )
But the curious thing:
If I use the command "tektool -p short.bin -b 0x1080000 -l 0x7FFFF" they are programmed the flash from 0x1080000 to 0x1100000 ( bank 2 )
If I use the command "tektool -p short.bin -b 0x1100000 -l 0x7FFFF" they are programmed the flash from 0x1100000 to 0x1180000 ( bank 3 )
The bank 1 not programmed in any case.

The command Read and Erase work perfectly.
This happens with 2 different flash card and 2 different oscilloscope TDS540.
I tried to use 2 different PCI-GPIB National card, but the problem is always the same.
it would be possible to solve this problem ?
Are there any other tests I can try?
Thank you in advance.

Sergio

Tantratron · « **Reply #91 on:** June 17, 2023, 10:38:56 am »

Hello Sergio,
Regarding the special case of 28F010 or further the 28F020, there are two models made respectively by Intel and AMD. Who is manufacturer of your 28F010 ?
In case, check attached instructions from madao on length versus flash type.
Albert

Fuma · « **Reply #92 on:** June 17, 2023, 08:19:30 pm »

Hello Albert,
thank you for your interest, I have 2 flash card, one is AMD and one is INTEL and the problem is the same.
I have already read all the instructions of madao.
The lenght 0x180000 for the 28F010 is correct because before to erase I had the backup and the file matches with firmware found in Internet. The are 12 chip x 128K ( 131072 ) = 1.572Kbyte = 0x180000.

madao · « **Reply #93 on:** June 18, 2023, 04:10:14 am »

i haven't clue, why it doesn't write data into flash.
Flash program algorithm is same with newer flash on TDS-serie.

Difference of amd and intel shouldn't make problem, because: erase , programming and needing of zero filling is excatly same. Only difference between AMD and Intel is quality. (Intel erasing works much faster and less difference by tries of erase on 12 flash )

Sad, i can't check it again on TDS540 /520 anymore, all is already sold. But i can told, i have check with this puplished unified tektool with all flash. (also one unit with mixed amd /intel flash on one firmware-board )

I can check on TDS544A (not much others than TDS540 with 28F020 ), soon (TM)

Fuma · « **Reply #94 on:** June 18, 2023, 03:41:44 pm »

Today the tektool program behaved differently: it programmed bank 1 and 2 correctly and bank 3 all FF, perhaps it depends if I switch the oscilloscope off and on again at each command ..... it's strange.
Just my curiosity, but during the programming of the cells does not make a check? the program does not give any programming errors.
Thank you.

madao · « **Reply #95 on:** June 18, 2023, 05:35:35 pm »

this is why: verifty-function is avaible.

Fuma · « **Reply #96 on:** June 19, 2023, 08:23:49 pm »

Verify function gives the error "Firmware corrupt at address 0x100001" that is the start of Bank 3.
I prefer to load the created dump into a binary file reader program to see what is actually loaded in the memories and bank 3 I only see FF. I'm sure the tektool program is having problems on my TDS540.

Tantratron · « **Reply #97 on:** June 20, 2023, 04:02:44 pm »

Hello Fuma,
Could you make a close view of the 4 flashfile chips from your processor board ?
When you erase all of them with unified tektool command then read all of them again with tektool, are all the values correctly erased ?
Albert

Fuma · « **Reply #98 on:** June 20, 2023, 08:05:18 pm »

Hello Albert,
for the first question, the scope it opened, what exactly should I see?
Second question, yes of course, all cells are FF.
Today I discovered another problem, there is a difference between Intel and AMD chip. With Intel banks 1 and 2 are programmed with many cyclic errors, while with AMD they are programmed perfectly. To solve the problem on at least one flash card, tomorrow I'll unsolder the 4 chips of bank 3 and I want to try to program them with the willem eprom programmer but I have to make a adapter and a basic program that divides the binary file of bank 3 into 4 files for each chip ( from 32 to 8 bit bus ).
But I would not unsolder 12 chips for the card with chip Intel !

Tantratron · « **Reply #99 on:** June 21, 2023, 03:12:11 am »

Hello Fuma, yes I meant that you open your scope, look for the 4 flashfile chips then make a close view picture of the 4 chips. If you make a global view of the processor board, we can then tell you where to find the chips then you make a close view picture. Now it seems you have found the issue if there is a mix of AMD and Intel chips, even though on paper they're interchangeable, in practice wether new or older, their response could be different hence your problem.

Fuma · « **Reply #100 on:** June 21, 2023, 08:23:06 pm »

Hello, as you can see from the attached photo, i have 2 original memory cards, one with all intel chips and one with all amd chips.
I have already removed 4 memories from the AMD card to program them with the Eprom programmer. I disconnected the 3 pins of the 74F139 decoder address to invert the banks and deceive the tektool but it doesn't work because when there are 2 banks already programmed the third bank don't program it ...... more and more mysterious.
Other ideas ?

Tantratron · « **Reply #101 on:** June 23, 2023, 02:47:41 pm »

Hello Fuma,

In my humble opinion, you might take more risks or loose more time to de-solder, program outside the memory card these flashfile chips. Maybe you could ask Madao who wrote in C the specific routines for 28F010 28F020 to send you the code then you could modify the program if you are good in C to do remote testing of chip health.

P.S. Maybe check this post while ago https://www.eevblog.com/forum/repair/tekfwtool-for-tds540c-firmware-upgrade/msg2898960/#msg2898960 discussing specifics of 28F010 and 28F020 versus later flashfile chips.

Good luck, Albert

Shonky · « **Reply #102 on:** July 10, 2023, 01:08:27 am »

Quote from: DonnieJ on December 27, 2022, 06:16:51 am

Traveling the road others have gone... here is a first pass source code and binary of a tektool variant (pretty much a re-write):
- that works with AR488 (and maybe Prologix) GPIB adapters.
- runs on Unix-like systems
- limited for the moment to 28F008SA flash, but easily changed
- is fairly fast (about 20min) to write a TDS684B firmware, uses extensive target device side code
- but is still a little cranky, mostly timeout issues with AR488.
....

I have used this on a TDS644B (converted to TDS684B with the 4 ID resistors removed on the acquisition board). I used the AR488 v3 with Arduino micro pro interface. I was mainly looking to backup the NVSRAM on mine. I have not attempted to do any reprogramming yet.

I did have to change "ttyGPIB" in ib.c to "/dev/ttyACM0" for my specific interface and recompiled on Ubuntu 20.04 for x86 and it worked just fine. Once it did seem to get into a funk and I had to power cycle the scope. I did do something like interupt it whilst reading. GPIB seems to to not like getting interrupted.

I have only used it to read the firmware (v4.3e) which I verified read 100% correctly against a copy of the firmware I found on the internet. So I'm fairly comfortable that it reads correctly.

Code: [Select]

./tektool --read firmware.bin --base 0x1000000 --length 0x400000
It read the 128k + 512k SRAM too and I can see the 512k repeating as a copied version by reading further. I can also see the RTC in the first 16 bytes at 0x4000000

Code: [Select]

./tektool --read nvsram.bin --base 0x4000000 --length 0xA0000

keystone · « **Reply #103 on:** July 15, 2023, 09:38:33 pm »

Hello Terra Operative. I realize this is a rather older posting but I just found it. I have 3 TDS scopes, 620A, 640A, and a 644A. Was wondering if you could help me with step by step instructions to retrieve my NVRAM contents in these so I can replace the old DS1650Y and DS1286 ICs. I have an Agilent USB-GPIB 82357B device and the Agilent IO controls software loaded on an XP computer with a serial port and USB ports. I am not sure of the memory addresses of these ICs that I need to copy/save. Could you please help me? Thank you for posting what you did but I am not sure if it all applies to my situation. Thank you.

keystone · « **Reply #104 on:** July 15, 2023, 09:43:43 pm »

Quote from: keystone on July 15, 2023, 09:38:33 pm

Hello Terra Operative. I realize this is a rather older posting but I just found it. I have 3 TDS scopes, 620A, 640A, and a 644A. Was wondering if you could help me with step by step instructions to retrieve my NVRAM contents in these so I can replace the old DS1650Y and DS1286 ICs. I have an Agilent USB-GPIB 82357B device and the Agilent IO controls software loaded on an XP computer with a serial port and USB ports. I am not sure of the memory addresses of these ICs that I need to copy/save. Could you please help me? Thank you for posting what you did but I am not sure if it all applies to my situation. Thank you.

Quote from: TERRA Operative on October 20, 2021, 03:44:28 am

I successfully updated the firmware on my older version TDS784C from 5.0a to 5.2e, using an ebay sourced Keysight 82357B USB-GPIB adapter.
Here's the full instructions on how I did it, combining info from madao and rodd.

1.) Install Keysight IO Controls and set settings as shown in the included images. (This is important to allow tektools utility to access the GPIB adapter!)

2.) Run IO Controls (Icon should appear in task bar) and run Keysight Connection Expert.

3.) Plug 82357B USB-GPIB adapter into PC and scope. Turn hidden switch in scope to unprotected mode and turn on scope.

4.) Check for the scope appearing in Keysight Connection Expert as shown in the included image.

5.) Open Command Prompt and navigate to folder containing tektool.exe

6.) Type in the following commands shown in quotes (don't type the quote marks).

7.) Identify flash type "tektool -i -b 0x1000000 -l 0x10"

8.) Save existing NVSRAM (not for TDS400 series, unknown address) "tektool -r NVSRAMSave.bin -b 0x4000000 -l 0x100000"

9.) Save old firmware "tektool -r example.bin -b 0x1000000 -l 0x400000" (28F010 = 0x180000, 28F020 = 0x300000 instead of 0x400000)
(example.bin = name of existing firmware file)

10.) Fill zero to flash (only for old flash 28F010 and 28F020) "tektool -z -b 0x1000000 -l 0x10"

11.) Clear firmware "tektool -e -b 0x1000000 -l 0x10"

12.) Flash new firmware "tektool -p example.bin -b 0x1000000 -l 0x400000" (28F010 = 0x180000, 28F020 = 0x300000 instead of 0x400000)
(example.bin = name of new firmware file)
This will take a while. On a TDS784C, it took just under 45 minutes or so.

13.) Writing NVSRAM back into memory (optional, not for TDS400 series, unknown address) "tektool -w NVSRAMSave.bin -b 0x4000000 -l 0x100000"

14.) IMPORTANT: Power cycle unit before verification of firmware. Wait 10 seconds after power-on, then switch protect-switch to "protect" for safe verification.

15.) Verification of firmware "tektool -v example.bin -b 0x1000000 -l 0x400000" (28F010= 0x180000, 28F020 = 0x300000 instead of 0x400000)
(example.bin = name of newly flashed firmware file)

16.) Reboot scope, enjoy.

16a.) I did a factory reset on my scope for good measure, just to make sure there were no incompatible settings etc from the old firmware to the new firmware.

TERRA Operative · « **Reply #105 on:** July 16, 2023, 04:24:09 am »

You can just follow the instructions I provided, it will work for any TDS500/600/700 series scope.
I haven't tried any different GPIB adapters, but others should work.
I have a National Instruments GPIB-USB adapter now that I will try when I get back from holiday in a week. I'll update the instructions then.

Or you can use a chip programmer like the TL866ii etc to read the chips after you pull them out and then copy the data straight in to the new chips. I did this for a TDS540 scope and it worked well.

Also, please post your files (zip them up per scope) here and let us know the scope model and firmware revision as shown on the splash screen at boot.
If they are ones I don't have, I'll add them to tekwiki for archival purposes to make them available for anyone else who might need them.

keystone · « **Reply #106 on:** July 16, 2023, 05:41:37 am »

Quote from: TERRA Operative on July 16, 2023, 04:24:09 am

You can just follow the instructions I provided, it will work for any TDS500/600/700 series scope.
I haven't tried any different GPIB adapters, but others should work.
I have a National Instruments GPIB-USB adapter now that I will try when I get back from holiday in a week. I'll update the instructions then.

Or you can use a chip programmer like the TL866ii etc to read the chips after you pull them out and then copy the data straight in to the new chips. I did this for a TDS540 scope and it worked well.

Also, please post your files (zip them up per scope) here and let us know the scope model and firmware revision as shown on the splash screen at boot.
If they are ones I don't have, I'll add them to tekwiki for archival purposes to make them available for anyone else who might need them.

Thank you for the reply. I have been trying to get the windows 10 computer running keysight IO suite 2022 to talk to my tek tds 640A and not having any luck. I have followed your instructions but no joy. I get a "failed discovery service" message. USB-GPIB led is green. Could there be a conflict with some NI stuff I have on computer? Do I have to worry about the scope I/O settings? Thanks for your help.

Shonky · « **Reply #107 on:** July 16, 2023, 07:08:42 am »

Quote from: keystone on July 16, 2023, 05:41:37 am

Thank you for the reply. I have been trying to get the windows 10 computer running keysight IO suite 2022 to talk to my tek tds 640A and not having any luck. I have followed your instructions but no joy. I get a "failed discovery service" message. USB-GPIB led is green. Could there be a conflict with some NI stuff I have on computer? Do I have to worry about the scope I/O settings? Thanks for your help.

Are you putting the scope in unprotected mode? The screen should be blank and it doesn't fully boot. The GPIB address is fixed in this mode - there is nothing to configure.

keystone · « **Reply #108 on:** July 17, 2023, 07:37:46 am »

Yes, the scope is in unprotected mode. I get nothing when trying to connect with the keysight connection expert.. After I get the failed discovery service message it goes to the screen where it says "loading instruments" and just stays there. I think something might be wrong with the software settings. It seems relatively simple to hook up and run the IO software but I'm missing something. I need someone to lead me step by step as I don't understand this software. A video on youtube about this would be great. Does anyone know of something like that? I've worked on this a couple of years ago and didn't get anywhere. Now I have dug it out and tried again but not getting anywhere. I would appreciate any help possible. Thank you.

TERRA Operative · « **Reply #109 on:** July 17, 2023, 07:50:22 pm »

Completely uninstall all GPIB software and then just install the Keysight IO Suite.
You might have conflicts with the VISA drivers from different companies. There's no way to know what is going on with your setup unless we begin from a clean start.

keystone · « **Reply #110 on:** July 17, 2023, 09:32:21 pm »

Quote from: TERRA Operative on July 17, 2023, 07:50:22 pm

Completely uninstall all GPIB software and then just install the Keysight IO Suite.
You might have conflicts with the VISA drivers from different companies. There's no way to know what is going on with your setup unless we begin from a clean start.

I tried, followed your instructions that you posted earlier and it didn't work for me. I will remove all keysight and NI software and just reinstall keysight and see what happens. Thanks.

keystone · « **Reply #111 on:** July 20, 2023, 07:55:50 am »

Quote from: keystone on July 17, 2023, 09:32:21 pm

Quote from: TERRA Operative on July 17, 2023, 07:50:22 pm
Completely uninstall all GPIB software and then just install the Keysight IO Suite.
You might have conflicts with the VISA drivers from different companies. There's no way to know what is going on with your setup unless we begin from a clean start.
I tried, followed your instructions that you posted earlier and it didn't work for me. I will remove all keysight and NI software and just reinstall keysight and see what happens. Thanks.

Update: I got my agilent 82357B USB-Gpib adapter working with my windows 10 computer and TDS640A. Yey! When I tried to get my flash ID I got failed. Don't know why. I uninstalled the Keysight and NI stuff and tried to reinstall only keysight IO suite but it said I still had some other company's software on computer so I intalled it anyway and told it to be primary and that worked. I guess the keysight IO suite was installed as secondary Visa at first. Now, question as to what to type in for the nvram contents for my tds620A, 640A, and 644a scopes? Would they all be the same addresses and lengths? Can someone tell me what to use for these entries? Thank you. I'm making progress!

leonpav · « **Reply #112 on:** April 11, 2024, 08:23:40 pm »

Hello Tek scope folks!

My Tek794D is getting old, and I just wanted to report that I've successfully saved the NVRAM by the instructions from the first post here

I have the NI USB-HS adapter.
Seems the Tektool was happy with my Win7+NI drivers and it reported: "0x89a0 = 28F016SA". Now I must save the FW as well...

Big thanks to all the developers here!!! :DDD


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee