Products > Test Equipment

Hacking the HDO1k/HDO4k Rigol 12 bit scope

<< < (136/151) > >>

bosav:
yes, it is indeed a typo - the build date is also "2023/10/18 18:14:32"

It's weird that there is no Key.data file - given build numbers/dates, I would expect this should be from the same image

Veteran68:

--- Quote from: ebastler on December 30, 2023, 09:09:02 pm ---Progress -- many thanks for the foolproof instructions, Veteran68! I compiled the program, pushed it over to the scope and ran it, and captured both, the fram.bin file and the console output.

However, the binary file does not have the same data at offsets 0x011C and 0x01C4. The text file starts with a first data block which is indeed the same data that shows up at 0x011C in the binary file, but has 388 bytes (0x184), not 148.


--- Code: ---id:091d data[184]:
C7 00 EE 86 54 DA 36 3D 18 10 53 F9 16 C3 D9 A0 A8 07 2E B0 2D A1 D8 65 82 46 54 F9 75 AD 25 98
...

--- End code ---

Any recommendation what should go into the key.data file? Thank you!

--- End quote ---

My key.data file that lives in /rigol/data matches exactly the 148 bytes starting at offset 0x11C and also the 148 bytes starting at offset 0x01C4 in the fram.bin file generated on my scope. I not only eyeballed them, but selected each block of data and ran a CRC-32 on it inside HxD. All 3 blocks of 148 bytes matched.


--- Quote from: ebastler on December 30, 2023, 09:17:05 pm ---But my hardware version is 3.

--- End quote ---

Interesting, you have one of the rare HW version 3 in a DSO1074 then. When others posted HW v3 they had the DSO1072. I wonder if HW v3 changed how the keys work? I hope not.

bosav:
tried running it as well, just like Veteran68 -- I have two blocks at the same offsets, matching the key.data

ebastler:
Success!

I first tried to generate a 148-byte key.data file from the FRAM data at 0x11C, but the Go program rejected that as "invalid format". But then noticed that voltsandjolts had indeed shown a Key.data file which is 388 bytes long (like that first block in my FRAM dump):


--- Quote from: voltsandjolts on December 30, 2023, 07:45:20 pm ---My scope had key.data in /rigol/data


--- Code: ---D:\adb>adb shell ls -l /rigol/data
total 992
-rwxrwxrwx 1 system system    388 2023-01-09 18:58 Key.data
--- End code ---

--- End quote ---

So I generated a Key.data from those 388 FRAM bytes, pushed it over to the scope and gave it to the Go script as well. And bingo -- valid codes for the memory and 200 MHz bandwidth options!

Thank you all for your quick help and practical support -- I would have been stumped without you!  :-+

It leaves some interesting questions about versions... Is there a second flavor of key.data files (which is however also accepted by the Go script)? Maybe a 128 byte vs. 256 byte net key length, plus whatever checksums?  Is the difference linked to the hardware versions 2 vs. 3?  voltasandjolts, what hardware version does your scope have?

voltsandjolts:
 :-+


--- Quote from: ebastler on December 30, 2023, 10:12:49 pm ---Is the difference linked to the hardware versions 2 vs. 3?  voltasandjolts, what hardware version does your scope have?

--- End quote ---

v2

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