Products > Test Equipment

New Rigol DS7000

<< < (60/72) > >>

normi:

--- Quote from: tv84 on April 20, 2021, 08:39:45 am ---
--- Quote from: memeruiz on April 19, 2021, 09:50:26 pm ---
The "usual method" is the way Rigol tells us how licenses must be inserted. Have you seen any official method of inserting licenses through copying files in a telnet session?

.

--- End quote ---

I agree you should use the method Rigol recommends to add the license, it is likely that after the license is copied to the scope it then gets processed and a changes made elsewhere. The license file is probably not used after, so you will have to do over the adding by inserting the USB stick with the keys and then do a option install.
@memeruiz
What was the build date on that firmware?
--- End quote ---

memeruiz:

--- Quote from: tv84 on April 20, 2021, 08:39:45 am ---
The "not likely" was an answer to @normi's post.

 :wtf: is a "manually modified appEntry version" if not a patch?

The "usual method" is the way Rigol tells us how licenses must be inserted. Have you seen any official method of inserting licenses through copying files in a telnet session?

"Well, if I changed a bin executable file by hand incorrectly, anything can happen, even corrupting something I guess. But I find that highly unlikely... Except maybe your backup script did something bad there, if it somehow touches that."

With these comments, I'm out.

--- End quote ---

I used vbindiff between an original appEntry and a patched appEntry for the MSO5000. That way I found the data changed by the patch. Not only the offsets but also the particular changed data and also its context (data before and after).

Then, I used a binary editor ghex. This tool has a binary search function. I looked for similar data before and after the patched data in my appEntry MSO7000 file. Then I applied the same changes to the data between. I did a manual patching basically. I have done this before, when files haven't changed much this works fine. In this case the data on the last offset was not that similar on the MSO7000 to the MSO5000.

With respect to the licenses thing. I have never inserted any Rigol licenses yet. This Oscilloscope is very new to me.  I will be asking for the license updates they are giving now for free, then I will discover this license activation method. I don't know how to do it. I did try to scp the .lic files back to the /rigol/data dir. from my backup. That didn't work. I guess it is not the right method. Didn't know this oscilloscope has a telnet port open (it seems very obsolete to be using telnet for anything now a days).

If you are sure your backup script works fine then ignore the message. I was pointing out, it is the only other way I could see any corruption there. I never imagined people could get offended (apparently) by pointing out all possibilities, in technical conversations. I will be more careful from now on ... avoiding getting people unintentionally offended.

memeruiz:

--- Quote from: normi on April 20, 2021, 11:48:26 am ---
--- Quote from: tv84 on April 20, 2021, 08:39:45 am ---
The "usual method" is the way Rigol tells us how licenses must be inserted. Have you seen any official method of inserting licenses through copying files in a telnet session?

.

--- End quote ---

I agree you should use the method Rigol recommends to add the license, it is likely that after the license is copied to the scope it then gets processed and a changes made elsewhere. The license file is probably not used after, so you will have to do over the adding by inserting the USB stick with the keys and then do a option install.
@memeruiz
What was the build date on that firmware?

--- End quote ---

The licenses came with the Oscilloscope already. So I don't have any license files, nor instructions to do this license activation. I will be asking Rigol for the free licenses they are currently offering. I will then discover how to do this and I will have the necessary files. I don't know if the .lic files are the same as the "keys" you are mentioning.

The build date on the firmware I will send it to you privately, I'm afraid there are eyes around here that could use that for blacklisting me.

memeruiz:
A bit of more updates:

I modified the patchfinder.sh for working in Linux.

I ran this script using appEntry_01_01_04_08.bpatch using appEntry.ori.01.01.04.08 against the following appEntries:

appEntry.ori.5k.01.02.00.02   Finds proper offsets
appEntry.ori.5k.01.02.00.03  Finds proper offsets
appEntry.ori.5k.01.03.00.01   Finds proper offsets
appEntry.ori.7k.00.01.01.09.02   No results
appEntry.ori.7k.00.01.02.00.05   No results

Maybe some things must be tweaked in patchfinder.sh to "search better or more" ....

Manually I was able to find most changes against my firmware version (01.01.02.00.06). Except the last binary change. But it didn't work.

Is there a newer patch file than this one:  appEntry_01_01_04_08.bpatch ?
Is there a patch file specifically made for the 7k?

I haven't found any on the forums.

memeruiz:
Good news :)

Got my MSO7014 totally upgraded. Thanks to everybody that contributed so many details of the Osc.

I had to objdump three files:

appEntry.5k.01.01.04.08
appEntry.5k.01.01.04.08_patched  (with appEntry_01_01_04_08.bpatch)
appEntry.ori.7k.01.01.02.00.06

With the object dumps I was able to get a better context on the things I was changing by hand. I think the problem from my first attempt was the last 8byte change. It was a bit more different on the 7k than the other changes.

patchfinder.sh was not able to find these changes between 5k and 7k. Maybe it has to be tweaked to force a stronger lookup for more far away address. I'm not sure how exactly patchfinder looks for the changes. Find attached patchfinder.sh modifed for linux. You still have to install zsh in linux to run it! You also need binutils-arm-linux-gnueabi


--- Code: ---zsh patchfinder.sh appEntry.ori bsdiff patch.txt appEntry.new
--- End code ---

Also find attached the bspatch for MSO7000 firmware version 01.01.02.00.06 (which is not on the Rigol webpage yet for some reason). It could be that this patch also works for older firmware versions. Please check!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod