Author Topic: Tekfwtool for TDS540C firmware upgrade (Read 20556 times)

Galen · « **on:** December 25, 2019, 09:01:18 am »

Hi All, I'm considering to upgrade my TDS540C firmware from 5.0e to 5.2e, to let the banner can show TDS580C, after I upgrade this 540C to 580C.
The most suitable tool is tekfwtool, I think. Even some posts talked a little about tekfwtool, but no dedicated topic about this, I read all them and still not sure about the environmental needed. So I decided to open this thread, dedicating to this tool.

What I have/know now:
1. A PCI-GPIB card (brand NI), on the way to me.
2. A NI GPIB cable, on the way to me.
3. An old computer with PCI slot.
4. Windows98 SE installation CD, and WinXP installation CD (SP3).
5. The firmware of version 5.2e, downloaded.
6. tekfwtool.exe, and the source code (download from the link in eevblog: 'source-code and tekfwtool.exe for using (run only with NI-VISA and Windows', https://stackframe.org/tekfwtool/). It's said this tekfwtool only works in Win98 DOS window mode.

My question:
1. Still need the NI-VISA to drive the GPIB card, right?
2. Based on information on NI website, if I use Win98SE, I need the NI-VISA Ver3.0.1 or lower, but can't find the download. The lowest version is Ver5.4, I downloaded it from NI site, but it supports WinXP SP3 and above (Win7, Win8, etc.)
So question now is, to use this tekfwtool, I need to find NI-VISA 3.0.1 or lower. But searched the net, can't find a link. If I use WinXP, then this tekfwtool still works?
I saw a post said the tekfwtool source code need to be compiled using some tool, but I have no idea how to do it, as I'm not a computer programmer.

Any help on this is very appreciated.

Best Regards,
Galen

madao · « **Reply #1 on:** December 25, 2019, 01:25:22 pm »

I use tekfwtool with NI PCI-GPIB card and Win 7 x64.
I can updating firmware of my TDS754D (now is it TDS784D) from 7.11 to 7.4

IEEE488.2 17.1 (include NI VISA)

Single trouble: i cannot updating my TDS754C firmware (similar as your TDS540C w/o color)

Unit must be running into boot mode. ( cal switch to unprotect and power it)

Quote

run only with NI VISA with NI GPIB stuff on GPIB-0-devices

Press shift and hold it
Press right button of mouse in this folder
Choose "here open command " or " Hier eingabeaufforderung öffnen"

1.)save of nvsram
   put of string "tekfwtool -r example.bin -b 0x04000000 -l 0x20000"

2.)save of old firmware
   put of string "tekfwtool -r example.bin -b 0x01000000 -l 0x400000" (4MB)

3.)clear of firmware
   put of string "tekfwtool -e -b 0x01000000 -l 0x10"

4.)flashing of firmware
   put of string "tekfwtool -p example.bin -b 0x01000000 -l 0x400000"

5.)writing of nvsram (optional)
   put of string "tekfwtool -w example.bin -b 0x04000000 -l 0x20000"


   "example.bin" , you can calling him as you wants, but "*.bin is important.
   Don't modified target.bin, it must be preset.

   Don't flashing on old devices as TDS540, TDS540A , TDS540B, TDS744A, it doesn't support 8 bit flash memory.

Galen · « **Reply #2 on:** December 25, 2019, 03:23:13 pm »

Thanks a lot madao!
As I know, the C serials, firmware version 5.2e should support. Because can find many C models in the firmware.
could you attach the tekfwtool which you used to here? I downloaded one but don't know it works or not.
Very appreciated.
Galen

Galen · « **Reply #3 on:** December 25, 2019, 03:42:51 pm »

Hi madao, I mean Tds784c firmware 5.2e. Just checked the Fw, tds784c and tds794 model number are inside. maybe you can try it.
Or, it's because the flash ic is not supported by the tekfwtool? Therotically, if the flash ic model is the same, this tekfwtool should work.
Galen

Galen · « **Reply #4 on:** December 25, 2019, 04:21:11 pm »

my tds540c flash ic is E28F016SA 16-MBIT (1 MBIT X 16, 2 MBIT X 8)FlashFile MEMORY.
so this tekfwtool should works?

madao · « **Reply #5 on:** December 25, 2019, 06:45:58 pm »

TDS700C firmware fit also in TDS500C .

I have upgrading my TDS754D with Firmware of TDS784D (V7.4), no trouble.
Other case with TDS714L is upgraded with TDS794D (V6.6) Firmware.

Yes, 28F016SA (and 28F160S5) is support by tekfwtool. But i have problem to upgrading my TDS754C. (error by earse of flash)
Not more.. sadly, i am needed firmware-upate on instrument with 28F020 and 28F008.

Important ! downloading all file from page, include target.bin. NEVER modified and replacing him.
Pleas don't ask for make of c-sourcefile for executable file. I am sorry, i haven't know about it.

Again ! It is your risk, what you doing it. Pleas don't hit me ! ;-)

Tantratron · « **Reply #6 on:** December 27, 2019, 10:21:27 am »

Hello Galen,

I'm bit like you trying to connect the dots between different threads, infos dealing on how to save or upgrade firmware as well as on how to save or load the NVRAM via software.

Wether tektool or tekfwtool, there is a need to first make sure GPIB link works correctly to read-write on the different memory maps. It seems both softwares are written in C then it is just matter to compile then link wether Windows, Mac, Linux.

There are 2 interesting thread you might already know but still not clear to me
https://forum.tek.com/viewtopic.php?f=568&t=139999&hilit=TDS784/
https://forum.tek.com/viewtopic.php?f=568&t=138168&hilit=TDS784/

It would be interesting to have the complete memory map of TDS serie C and D which are using 68040 whereas TDS serie no-suffix, A or B uses 68020. Attached the one of TDS520B but we would need similar info for TDS 540C to really make sure not writing or corrupting the internal memories. For example in this case https://www.eevblog.com/forum/repair/gpib-usb-control-between-macbook-air-(macintosh)-and-tds540c/msg2840286/#msg2840286 it would be nice to have an answer why address Ox50009 does not correspond to the 0x4000000 mentioned as NVRAM start in the B-version memory map. Unless the options are stored somewhere else than in the NVRAMs...

One thing which I do not understand, in my case I'm using Macintosh with complete free NI (National Instruments) software to interface with GPIB, for instance VISA. I do have two TDS 540C where attached pictures of the GPIB numbering wether NVRAM disabled to write and NVRAM enable to write. I did choose GPIB address 2 and it shows up correct when booting the TDS in normal mode but it shows for some reason 0x29 when NVRAM is write-enable... why no idea but notice this very same address is used in the tektool.c software and probably in the tekfwtool.c

Another route I'm exploring is to use Python where there seems to be VisaPy compatible with GPIB, NI-488.

Lastly I did manage to also send GPIB commands via a GPIB Terminal from my macintosh where all this command stuff should be universal wether Windows, Mac OS or Linux... see https://www.eevblog.com/forum/repair/gpib-usb-control-between-macbook-air-(macintosh)-and-tds540c/

Albert

Galen · « **Reply #7 on:** December 28, 2019, 05:04:49 pm »

Hi Albert,
Thank you very much for sharing so many information on this. My NI PCI-GPIB card and cable just arrived today. So still no time to try it on my computer.
My computer has PCI slot, it run Win7 now. But I had run DOS on it before, using floppy disks, it has a floppy drive. But no DOS drive for this GPIB card. So I will try Win7 first to test the card and communication with the TDS540C. Will update here the progress.
Thanks again
Galen

Galen · « **Reply #8 on:** December 28, 2019, 05:25:17 pm »

Hi Albert, if you only want to activate the option, then the floppy tool can be used, pls refer my post https://www.eevblog.com/forum/testgear/activate-options-for-tds5xx-6xx-7xx-cd-using-floppy/msg2237949/#msg2237949
This tool is developed by flyte, I have used it successfully add options for my TDS540C. you can try it.
Galen

Galen · « **Reply #9 on:** December 28, 2019, 05:35:04 pm »

The floppy tool post by flyte, a lot discussion inside. https://www.eevblog.com/forum/testgear/tektronix-tds500600700-nvram-floppy-dump-tool/msg2244054/#msg2244054

Tantratron · « **Reply #10 on:** December 28, 2019, 05:54:12 pm »

Quote from: Galen on December 28, 2019, 05:25:17 pm

Hi Albert, if you only want to activate the option, then the floppy tool can be used, pls refer my post https://www.eevblog.com/forum/testgear/activate-options-for-tds5xx-6xx-7xx-cd-using-floppy/msg2237949/#msg2237949
This tool is developed by flyte, I have used it successfully add options for my TDS540C. you can try it.
Galen

Hi Galen, to activate any option is easily done by software and NI-GPIB-USB-HS interface wether you're using Windows, Mac or Linux. In my case, I've done it this week with my MacBook Air as you can read this post https://www.eevblog.com/forum/repair/gpib-usb-control-between-macbook-air-(macintosh)-and-tds540c/msg2839268/#msg2839268

At some point if we can manage everything via GPIB and software, this will be much quicker, safer and cheaper. However on the topic to copy NVRAM and the firmware, I'm still on my learning curve so not sure how to do it via GPIB with my Macintosh.

My point anyway, once USB-GPIB link exists then it solves already the topic to enable options and frees from more complex old equipment like Floppy disk and non-official tektronix tool kit.

I do need to solve the NVRAM and firmware update so your thread helps as a trigger.

By the way, I do have a TDS540C like yourself with firmware V5.0.E so maybe you could share the most recent firmware version if it is authentically dumped from a working TDS540C

Thanks, Albert

Galen · « **Reply #11 on:** December 28, 2019, 05:56:46 pm »

Hi Albert, you said'I did choose GPIB address 2 and it shows up correct when booting the TDS in normal mode but it shows for some reason 0x29 when NVRAM is write-enable...', I think it's the boot loader fixed this GPIB address at 0x29, to 'listen' any command wheNVRAM switch is put in unprotected. That's the reason that tekfwtool use GPIB address 0x29.
Galen

geostep · « **Reply #12 on:** December 30, 2019, 10:55:39 pm »

Hi Galen,

I have a Tek 540C as well running V5.0e. I'm interested in upgrading it to 5.2 (or better).
Could you please share the files. And any notes regarding firmware changes?

I did a quick Google search but couldn't find any hits on 540C firmware.

Thanks!

- George

Galen · « **Reply #13 on:** December 31, 2019, 04:01:42 am »

Hi George,
you can go to KO4BB, then Mnuals, search for TDS784C, you can find the 5.2 firmware.
The tools include: tekfwtool, GPIB card, computer of cause, and NI-488, NI-VISA. I have downloaded the original firmware and NVRAM. But still not try to change the firmware now.
May I know what triggered the firmware change for you?
Regards,
Galen

Galen · « **Reply #14 on:** December 31, 2019, 04:26:19 am »

HI George, I mean updating the firmware is a risky job. May brick your scope. So far, I didn't try that, so no more comments now. May be some body in this forum who success in updating TDS540C, but I didn't find from search.
thanks
Galen

Tantratron · « **Reply #15 on:** December 31, 2019, 05:00:52 am »

Quote from: Galen on December 31, 2019, 04:26:19 am

HI George, I mean updating the firmware is a risky job. May brick your scope. So far, I didn't try that, so no more comments now. May be some body in this forum who success in updating TDS540C, but I didn't find from search.
thanks
Galen

Your thread is bit dangerous because in the first place, you say to have the 5.2e firmware for a TDS540C then it turns out you've found only the 5.2e firmware for TDS784C from this website http://www.ko4bb.com/getsimple/index.php?id=manuals&dir=Tektronix/Tektronix_-_TDS5xx_TDS6xx_TDS7xx_Digital_Phosphore_Oscilloscopes/TDS784C_firmware_v5.2e

Maybe the TDS784C firmware would work on TDS540C, no idea but for sure but direct tekfwtool writing to NVRAMs EEPROMS might be fatal if no basic information on the memory map, how the SW checks the HW options...

On a side note, this other webpage http://www.ko4bb.com/getsimple/index.php?id=enable-tds754d-options of KO44B is very useful as a synthesis of how easy we can set options by SW, modern GPIB communication with any type of computer

Galen · « **Reply #16 on:** December 31, 2019, 06:07:21 am »

Hi Albert, the TDS784C firmware downloaded from KO4BB also works for TDS540C and TDS580C, and many other TDSxxxC. Because I checked that firmware, TDS580C and TDS540C model number are inside, plus many other TDSxxxC listed inside.

I have dumped the 5.0 firmware from my scope, the TDS580C is not listed in side. So obviously, it doesn't support TDS580C. That's the reason I got 'TDSxxx' in the banner.
Thanks,
Galen

geostep · « **Reply #17 on:** December 31, 2019, 11:16:47 pm »

Hi Galen,

Thanks for the insight and cautions. I'm interested in opening up my 540C to a 580C as well. Yes, there are risks including bricking. It would be nice to see if it will display 580C instead of xxx when trying the 16 different 0 ohm jumper combinations. As well as getting the scope to 1 GHz. Not that I don't need a 1 GHz scope, but there is fun and adventure in trying to get there.

- George

geostep · « **Reply #18 on:** December 31, 2019, 11:43:05 pm »

I looked at the version 5.2e binary file that Tantratron referenced from the KO4BB website.

In the file "TDS784C_fimware_EPROM_5.2e_flashmem.bin" the following info can be found starting at location 284C34h. I have replaced null (00h) characters with commas for clarity.

TDS 784C,TDS 744,TDS 744C,TDS 724C,TDS 540C,TDS 520C,TDS 782C,TDS 754C,TDS 794,TDS 580C,TDS xxx,$VersionString:

It does hint that this file *could* be used on all of these models.

If anyone reading this knows this to be true/has done this firmware upgrade please speak up and let us know about your experience, good or bad.

- George

Galen · « **Reply #19 on:** January 01, 2020, 05:32:30 am »

The tekfwtool I used can't program the flash properly, in Win7 + PCI-GPIB. After I flash the new firmware in, the TDS540C can't start. then I flash in the original backuped firmware, it still dead.

sad......

Tantratron · « **Reply #20 on:** January 01, 2020, 05:37:36 am »

Quote from: Galen on January 01, 2020, 05:32:30 am

The tekfwtool I used can't program the flash properly, in Win7 + PCI-GPIB. After I flash the new firmware in, the TDS540C can't start. then I flash in the original backuped firmware, it still dead.

sad......

Do you mean and confirm now your TDS540C is bricked or dead ?

Galen · « **Reply #21 on:** January 01, 2020, 05:42:26 am »

Quote from: Galen on January 01, 2020, 05:32:30 am

The tekfwtool I used can't program the flash properly, in Win7 + PCI-GPIB. After I flash the new firmware in, the TDS540C can't start. then I flash in the original backuped firmware, it still dead.

sad......

I read the firmware after flash it in, use hex editor to compare them, there are many data un-match.
Because the write-in is too fast?

Galen · « **Reply #22 on:** January 01, 2020, 05:44:46 am »

Quote from: Tantratron on January 01, 2020, 05:37:36 am

Quote from: Galen on January 01, 2020, 05:32:30 am
The tekfwtool I used can't program the flash properly, in Win7 + PCI-GPIB. After I flash the new firmware in, the TDS540C can't start. then I flash in the original backuped firmware, it still dead.

sad......
Do you mean and confirm now your TDS540C is bricked or dead ?

it can still communicate with the tekfwtool. Just the write-in has a lot wrong data.
so I think it's not the firmware problem, it's the tekfwtool I used not write-in the right data.

madao · « **Reply #23 on:** January 01, 2020, 05:45:03 am »

It must be erase at first. Without erase is correct programming of flash impossible.
Write of flash is much other than ordinary memory.

Saving of him is possible, you need Flasher, which could flash this type, desoldering him.

Galen · « **Reply #24 on:** January 01, 2020, 05:58:10 am »

Quote from: madao on January 01, 2020, 05:45:03 am

It must be erase at first. Without erase is correct programming of flash impossible.
Write of flash is much other than ordinary memory.

Saving of him is possible, you need Flasher, which could flash this type, desoldering him.

I used the erase command -e -b 0x01000000 -l 0x10, isn't right? why the length is so short (0x10)?
thanks.


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

Author Topic: Tekfwtool for TDS540C firmware upgrade (Read 20556 times)

Share me