Products > Test Equipment

Hacking the HDO1k/HDO4k Rigol 12 bit scope

<< < (134/151) > >>

ebastler:

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

--- End quote ---

Thanks. Yes, that's what I expected to find. Nada, unfortunately...


--- Quote ---The Go program runs on your PC, need to install Go compiler.

--- End quote ---

Please note that I was not talking about the Go program which generates the license codes (based on key.data). I know that this one needs to run on the PC. I can run it, but lacking the key.data it will fail, of course.

What I am unclear about is the different Go program which is attached to the post I linked to in my prior post. It is meant to dump the FRAM content, as a way to get to the key.data information when it is not preset in a file, but I don't know how and where to run that program. -- Ah, just saw your edit. If you can figure that one out, many thanks in advance!

voltsandjolts:
Yeh, sorry, thought there was just one Go script, THE one!

But yeh, that FRAM dump Go program needs to run on the scope, after you build it on your PC using Go compiler:


--- Code: ---// build using
// GOOS=linux GOARCH=arm64 go build fRAMdump.go

--- End code ---

Copy executable to scope and run it  :-//


Edit: gimmie a minute I'll try to build the exe

voltsandjolts:
Ah, the Go script requires the logger module which is not supported on Windows, so I'll need to build it on my linux box but am out of time tonight...will look at it tomorrow if someone else doesn't jump in first.

Veteran68:

--- Quote from: ebastler on December 30, 2023, 07:31:19 pm --- I also found a tool which is meant to dump the FRAM, so I could presumably get to the key.data information:

--- End quote ---

Just as FYI, the output fram.bin file produced by fRAMdump.go contains two copies of the key, one starting at offset 0x011C and the next at 0x01C4. The key is 148 bytes.


--- Quote from: voltsandjolts on December 30, 2023, 08:14:46 pm ---Ah, the Go script requires the logger module which is not supported on Windows, so I'll need to build it on my linux box but am out of time tonight...will look at it tomorrow if someone else doesn't jump in first.

--- End quote ---

I just built it on Windows. You have to set the environment properly and those errors will resolve. The other posts are building from Linux and so the env set commands are different.

The correct commands for Windows are:


--- Code: ---go mod init fRAMdump.go
go mod tidy
set GOOS=linux
set GOARCH=arm64
go build fRAMdump.go
--- End code ---

Then adb push "fRAMdump" to a writeable area of the file system (I created /rigol/temp folder), set it's execute bits, and run it as root. It will output to the console but also create the file fram.bin in the same folder.

ebastler:
Many thanks, voltsandjolts and Veteran68! I will try to get that program compiled and over to the scope now.

So far, things aren't looking great for generating options for my scope. I just tried the official memory upgrade which I got bundled with the scope (after nagging Rigol Europe three times). The Rigol website produces a 96-digit hex code, based on my scope's serial number and the entitlement key I got from Rigol. But entering that code via SYST:OPT:INST DHO1000-RLU-01@xxxxx does not produce any response, except for resetting my scope to "beep on" mode. :-[  Instead of the "DHO1000-RLU-01" prefix, which is the option name given on my PDF from Rigol, I also tried HDO1000-RLU and various permutations (DHO/HDO, with or without the -01).

Is the scope supposed to send a reply to the SCPI command? Is the lack of a response and/or the lack of an enabled memory upgrade an indication that my scope's key information is totally missing or messed up?

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