| Products > Test Equipment |
| Sniffing the Rigol's internal I2C bus |
| << < (816/899) > >> |
| McBryce:
It's the MSO version that you can find here: http://www.gotroot.ca/rigol/ but after rereading your post, I think you are using the right one already. McBryce. |
| smgvbest:
Ah, Maybe it's this you're doing a rigup license mso1074z_dump.bin 0x1C001 but the input to license is the output of the scan rigup scan mso1074zs.bin > mso1074zs.txt // This reads your dump and writes your public/private key to the output file mso1074zs.txt in this case rigup license mso1074zs.txt 0x1C001 // this reads the mso1074zs.txt file you created above and requests the license for 0x1C001 See if that helps you're using the patched version of rigup the "Hacked up for MSO1000Z(-S) rmd79, 0ff eevblog.com" says that. rmd79, 0ff hacked it to work with the MSO line --- Quote from: zsidoz on November 23, 2015, 06:56:00 am ---@ Sandra, I called the tool with this command line: "rigup license mso1074z_dump.bin 0x1C001", where the bin file is what I saved from the scope memory. @ McBryc, What is that "special patched version" and where can I find it? --- End quote --- |
| Neuro:
2 zsidoz: Could you please write exactly the command string, that you have used to extract the serial number from the dump? |
| zsidoz:
Sandra pointed out the missing step: rigup scan mso1074zs.bin > mso1074zs.txt After that I got the correct license keys and the scope is successfully hacked. Thanks for the awesome support from all of you! |
| smgvbest:
Glad to hear that was it. |
| Navigation |
| Message Index |
| Next page |
| Previous page |