Hacking the Rigol MSO5000 series oscilloscopes

[tv84]

If calib was lost, more basic infos would be lost: S/N, model, etc.

None of that happens!

Even with the FRAM wiped we can recover the scope. The thing is resilient.

[ykurban]

the subject seems to be a little scattered.

can someone who made the last update collect all the files and the procedure under one post?

[ve2mrx]

Hi ykurban,

Start reading from here: https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg3002776/#msg3002776

All the information is on that post and the following ones. You need the AutoPatcher, the patch file for your firmware version and patch.txt file modified for your firmware version patch. Edit: Ensure patch.txt has "Linux-style" line endings, LF only. Notepad++ can do it on Windows

https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2704640/#msg2704640
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2251380/#msg2251380
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg3024236/#msg3024236
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg3024342/#msg3024342

Martin

[ykurban]

thank you for your response ve2mrx

turns out, i was doing everything right, but there is a problem with my flash memory.


when i restart my scope with usb plugged in, patch worked fine. Before that, i was getting "no package found" error

i used 3 files for patch, and attached a screenshot of my flash memory.
 

[santacruzjohn55]

Hi running into difficulties running the patch route through ssh. This is with the no-phone-home patch. When I reboot after below, it doesn't fully boot. I also tried the 3 files on a flash drive, but it keeps saying 'No package detected'. I notice that my .GEL file is 130kb, where as the screen shot above shows 133kb. Any tricks I should be looking at?

Code: [Select]

<root@rigol>ls -l
total 22324
-rwxrwxr-x    1 root     root      22558088 May 22 03:41 appEntry

Code: [Select]

<root@rigol>md5sum /rigol/appEntry
2efa4605b83bf1af48bf6736bfae3255  /rigol/appEntry
<root@rigol>cp /tmp/appEntry /rigol/
<root@rigol>md5sum /rigol/appEntry
60f1ca21475ffe9444213c2d9a571a99  /rigol/appEntry

[rodorr]

I just received my new MSO5074 and I updated everything and it all went very smoothly, thanks to all of the hard work others here on the forum have performed. I was just wondering if, at this point I should go ahead and run the built in calibration sequence or just leave it as is. By the way, I did not do a calibration before I did the updates. I am not noticing anything in particular being out of tolerance, just wondering what the consensus is regarding calibration. Thanks again to all of those who have helped on this forum.

Thanks,

rodorr

[Cerebus]

I just received my new MSO5074 and I updated everything and it all went very smoothly, thanks to all of the hard work others here on the forum have performed. I was just wondering if, at this point I should go ahead and run the built in calibration sequence or just leave it as is. By the way, I did not do a calibration before I did the updates. I am not noticing anything in particular being out of tolerance, just wondering what the consensus is regarding calibration. Thanks again to all of those who have helped on this forum.

Thanks,

rodorr

Run the calibration as you would normally ignoring the fact that you've upgraded. i.e. Run the calibration when you're using the scope at a significantly different temperature from when you last calibrated it (usually about 5º - see the manual for model specific details) or if it's 'too long' since you last ran it. For instance, it's about a month since I last ran a cal on mine, that's not 'too long', but the ambient temperate here now is 26.9ºC (England, at 23:30 hrs in May? You're kidding me, right?), it was probably 20ºC when I last ran it, so it's time for a cal when I next turn the scope on. You can't calibrate too often, unless it reaches OCD levels, but more than once a month or when temperature dictates is usually unnecessary.

[thm_w]

I just received my new MSO5074 and I updated everything and it all went very smoothly, thanks to all of the hard work others here on the forum have performed. I was just wondering if, at this point I should go ahead and run the built in calibration sequence or just leave it as is. By the way, I did not do a calibration before I did the updates. I am not noticing anything in particular being out of tolerance, just wondering what the consensus is regarding calibration. Thanks again to all of those who have helped on this forum.

Thanks,

rodorr

I would run a cal when you have time, it takes quite a few minutes. Don't need to do it before the update.
Can be of some use to reduce DC offsets, eg if you notice a grounded signal is significantly off from 0V, etc.

[Martin72]

Oh boys, how easy life is for a siglent owner...

[Gandalf_Sr]

Oh boys, how easy life is for a siglent owner...

OK, pray tell; how is life easy for a Siglent owner?

[Martin72]

Once hacked ( in an "easy" way), you never must fear about it when a next update appear.

[Gandalf_Sr]

I'm there already 

[santacruzjohn55]

Can someone give me an md5sum of a working auto-updater .GEL file? I think my problems might be that or my USB stick.

[TK]

I'm there already 

Doesn't Rigol require repatching and hacking after a firmware upgrade?

[santacruzjohn55]

Never mind, the 4th USB drive I tried worked.

Just had to learn how to use the 3 seashells ^H^H^H^H^H^H^H files.

Thanks to all the hard work, the auto-updater is definitely the way to go.

[Gandalf_Sr]

I'm not sure it does

[TK]

As you are patching a specific executable (appEntry?), I think you do need to hack after a firmware upgrade, and of course you need someone keep the hack updated as it is specific for a firmware release

[tv84]

Once hacked ( in an "easy" way), you never must fear about it when a next update appear.

The "easy" way is also available in Rigol, from the start, but patching became mainstream...

[ebclr]

What is the actual latest firmware hacked, Are this  available as unique gel file  , to be loaded on USB sticker, this path thing is confusing

[ykurban]

i uploaded a video of bode plot function

[Martin72]

Could it be that bode plotting is much more faster than on the siglent sds2k+ ?


edit: forget it, it was played fast forwarding...

[texaspyro]

i uploaded a video of bode plot function

What was your connection configuration for this test?

[MegaVolt]

 

https://youtu.be/2dHbGTSPTGg

P.S.  How do you build youtube videos?

[santacruzjohn55]

Roughly this is what worked for me,
Get a new, brand name usb stick.

Go to the Rigol site and download the latest firmware. version: 01.03.00.01
Download the .GEL flie from the zip file to your usb stick, then do a local upgrade.
once complete, clear the data off the usb stick

Go here: https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg3024342/#msg3024342

download the zip file in that post. unzip the contents, (2 files) to your USB stick

Go here: https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg3025330/#msg3025330

download the file. rename it, removing the .DOC, copy that to your usb stick.

Your usb stick's contents should look like the file listing here, https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg3077233/#msg3077233

So, now you have a freshly upgraded scope that has been rebooted.
Insert your usb stick.
Select local upgrade.
. The screen should turn white with black text. It should ask you to press a button on the scope to upgrade.
After this completes, i think you have to press any button twice.

If you get a 'package not found', try another usb stick.
Or verify that the files look exactly like  the pictures.

[ve2mrx]

@tv84 What is the "easy" way you mention? I have read too much in this thread to remember!

Martin