It is designed for THS, but can be used for other models by rewriting the cfg.
You can dump the flash with the attached cfg.
Drag and drop the .cfg into the .exe and it should dump automatically.
I have not tested fluke and I don't think it works.
Just enter UHM mode and execute the GB command.
I don't think it will corrupt anything, etc.
It takes time because it reads and saves one byte at a time.
dumpcal.cfg: Just the cal data backup takes less than a minute.
dumpflash.cfg: Backing up the entire flash takes longer, about 5 minutes.
It can be write flash, and there is a cfg, but I will publish it after some more research.
The reason for CI25 is that the firmware has data that is initialized and loaded when the checksum of the cal data does not match.
In the case of THS firmware, the THS3014 data is loaded (maybe. because Model Number for VER&CAL is THS3014).
After comparing that data with the 3024 data, we found that CI25 and CI90 are different.
CI90 rewrites $4000819C by 2 bytes. Little endian; 1229 for THS3024 and 1230 for THS3014, but what that means is not known.
CI25 rewrites $400080C4 by 1 byte; seems to accept 0-3, 2 for THS3024, 1 for THS3014.
Tried 0-3, same settings for SG, 250MHz, -20db, forgot to install the 50 ohm terminator.
I think 0=60MHz, 1=100MHz, 2=200MHz, 3=500MHz.
I forgot to get an image at ci 25,0, almost the same as at ci 25,1.
The attenuation will change, but other than that, I can't say for sure. It is very likely that the cal data does not fit either.
I also tried CI 25,3 (500MHz?) but nothing changes, it can't reach 500MHz, it is attenuated and completely flat.
In order CI 25 1, 2, 3.


