Hacking the Rigol MSO5000 series oscilloscopes

[faktorqm]

Hi, with that patch, ssh will remain available at next boot? I want to have it permanently. Thank you!

[c0d3z3r0]

EDIT: Hmm, the SSH enabling coding "upgrade" from c0d3z3r0 now fails with the new firmware.

just reboot scope and you got perfectly working sshd, ignore error.

Ignore the error (this is normal bc it's not a real fw update). SSH gets started right away. Only network settings have to be checked.
Oh SSH is pretty slow on the first connection (~30sec).

[c0d3z3r0]

Hi, with that patch, ssh will remain available at next boot? I want to have it permanently. Thank you!

Yes

[Finity]

Excellent work. Successful permanent (ish) SSH communication with PUTTY. Thanks again!

[c0d3z3r0]

Excellent work. Successful permanent (ish) SSH communication with PUTTY. Thanks again!

Great! Could you test the appEntry thing?

[Finity]

Hopefully will have some time after work tonight to run the appentry thing and give some results.

[beatman]

today try again the update and it works.i only disable the startup/ last to default and after update and reboot scope works normaly.very nice optimizations.

[Finity]

Alright, here is the result of entering "/rigol/appEntry -run" at the <root@rigol> prompt while connected to MSO5000 via SSH:

<root@rigol>/rigol/appEntry -run
7 2048 16 2 "/dev/fb0"
servscpi.cpp 120 "The bound address is already in use"
Cal Data: "/rigol/data/cal_1.hex"
default setting by user set
insmod: can't insert '/rigol/drivers/libcomposite.ko': File exists
insmod: can't insert '/rigol/drivers/usbtmc_dev.ko': File exists
usbtmc.cpp 129 error:can not open /dev/usbtmc_dev,fd:-1

insmod: can't insert '/rigol/drivers/usb_gpib.ko': File exists
!!!!!!!!!!!!!!!!!!!CCU wait stop fail---------------------

Reads quite dramatic at the end, like a computer's dying words. It made me go look at the scope in the garage to make sure it hadn't caught on fire while I was telnetting from upstairs. Of course it was fine

Hope this info is helpful to those that know what it means

[ilyxa]

Reads quite dramatic at the end, like a computer's dying words. It made me go look at the scope in the garage to make sure it hadn't caught on fire while I was telnetting from upstairs. Of course it was fine

You forgot to kill "old" appEntry (e.g. something like pkill appEntry) and tried to run new instance, nothing scare.

[gharac]

Another successful upgrade to a MSO5074 using the 00.01.03.02.02 GEL file from RigolNA build date 2022-12-05.

I always get "error: no patch file 'patch.txt' found on drive" when patching. But patch.txt, ds5000Update.GEL and 01_03_02_02.bspatch are available on the stick. And the firmware is of course 00.01.03.02.02 with build date 2022-12-05.
What am I missing?


Update: Works fine. It was an usb stick issue (as usual)

[c0d3z3r0]

Alright, here is the result of entering "/rigol/appEntry -run" at the <root@rigol> prompt while connected to MSO5000 via SSH:

<root@rigol>/rigol/appEntry -run
7 2048 16 2 "/dev/fb0"
servscpi.cpp 120 "The bound address is already in use"
Cal Data: "/rigol/data/cal_1.hex"
default setting by user set
insmod: can't insert '/rigol/drivers/libcomposite.ko': File exists
insmod: can't insert '/rigol/drivers/usbtmc_dev.ko': File exists
usbtmc.cpp 129 error:can not open /dev/usbtmc_dev,fd:-1

insmod: can't insert '/rigol/drivers/usb_gpib.ko': File exists
!!!!!!!!!!!!!!!!!!!CCU wait stop fail---------------------

Reads quite dramatic at the end, like a computer's dying words. It made me go look at the scope in the garage to make sure it hadn't caught on fire while I was telnetting from upstairs. Of course it was fine

Hope this info is helpful to those that know what it means

ilyxa is right, could you try once again like this? pkill -9 appEntry; /rigol/appEntry -run

Edit: nevermind, errors appear here even without pkill, so it doesn't matter. Thanks for testing!

[Finity]

Here are the errors using the "pkill -9 appEntry; /rigol/appEntry _run


7 2048 16 2 "/dev/fb0"
Cal Data: "/rigol/data/cal_1.hex"
default setting by user set
insmod: can't insert '/rigol/drivers/libcomposite.ko': File exists
insmod: can't insert '/rigol/drivers/usbtmc_dev.ko': File exists
insmod: can't insert '/rigol/drivers/usb_gpib.ko': File exists

[c0d3z3r0]

Here are the errors using the "pkill -9 appEntry; /rigol/appEntry _run


7 2048 16 2 "/dev/fb0"
Cal Data: "/rigol/data/cal_1.hex"
default setting by user set
insmod: can't insert '/rigol/drivers/libcomposite.ko': File exists
insmod: can't insert '/rigol/drivers/usbtmc_dev.ko': File exists
insmod: can't insert '/rigol/drivers/usb_gpib.ko': File exists

Found another thing... my /rigol/data/vendorlog.txt reads "vendor data invalid". What does yours say?

[salviador]

Hi,

i have a problem i installed original firmware "v00.01.03.02.02 2023/01/04"
but maybe I haven't finished upgrading, now when I start the MSO it freezes almost at the end of loading and stays block

Now I tried reinstalling the firmware with secret menu Start MSO and press Hold Single
but nothing  continues to boot normally until it block

[ilyxa]

Hi,

i have a problem i installed original firmware "v00.01.03.02.02 2023/01/04"
but maybe I haven't finished upgrading, now when I start the MSO it freezes almost at the end of loading and stays block

Now I tried reinstalling the firmware with secret menu Start MSO and press Hold Single
but nothing  continues to boot normally until it block

(Attachment Link)

for clarification, Start/Stop - is it Red or Green (to clarify some staff)? imho this hang seems not specific f/w update but for not default settings while boot.

It's a bit tricky, you don't need hold Single button, just switch unit off, then press power button, right after momentary press Single button few times until menu appears, try "Default Settings" (not fw upgrade) first.

[salviador]

ohhhh wow thank you so much , Now I try to reinstall the original firmware

[ilyxa]

ohhhh wow thank you so much , Now I try to reinstall the original firmware

)

1st - which color of Start/Stop button after unsucsessful boot (green or red)?
2nd - try to set defaults in hidden menu before reinstalling  microcode, it can help.

[salviador]

ohhhh wow thank you so much , Now I try to reinstall the original firmware

)

1st - which color of Start/Stop button after unsucsessful boot (green or red)?
2nd - try to set defaults in hidden menu before reinstalling  microcode, it can help.

start/stop is orange

I try restore defaul in hidden menu and now work! , now try patch
thanks

[Sharp]

I did the upgrade this morning.  It did not go without hiccups so I thought I would report my findings

1. My scope HW version is 01.00.000 and was updated and patched to the previous release
2. I'm using a 4GB USB drive formatted as Fat32.  The drive is empty except for the FW files or patch files (not at the same time).  I'm pretty sure that I have used this drive before for updates
3. I downloaded and extracted MSO5_FW_Update to the flash drive
4. Updated using the local upgrade options feature
5. On reboot the startup gas gage goes to full and then stalls.  Dang
6. Second reboot - no change
7. Enter the secret menu by pressing Single button during reboot.  Two options presented: Upgrade Firmware and Restore Defaults
8. Tried Upgrade Firmware - scope reports a FW error
9. Tried Restore Defaults - the scope boots and shows FW 00.01.03.02.02(!)
10. Ran the patch using the local upgrade option.  Can confirm that the patch does not reboot the scope upon completion
11. Reboot scope, all options show forever 

Thanks to lujji and everyone else who has worked enhancing this scope
Unlike NoisyBoy, my scope was not running using default settings

Did the update - selected "Restore Defaults" - but I want to add to tcottle's good list above - Keep the USB stick in the MSO until the update boot has finished ( FW 00.01.03.02.02)
My update worked fine and are now running  FW 00.01.03.02.02 with all options active 

[w.v.s.]

Could someone please check on their MSO5 if these errors appear there as well, when running "pkill -9 appEntry; /rigol/appEntry -run"? FW version doesn't matter, but would be good to know which one.

with FW 00.01.03.00.01

Code: [Select]

/rigol/appEntry _run
7 2048 16 2 "/dev/fb0"
messageExchange.cpp 172 pCurrentIntf == NULL
insmod: can't insert '/rigol/drivers/libcomposite.ko': File exists
insmod: can't insert '/rigol/drivers/usbtmc_dev.ko': File exists
insmod: can't insert '/rigol/drivers/usb_gpib.ko': File exists

So, since I now can ssh and sftp (very helpful!), does anybody have a cross-compiler set up for this scope (LF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.16) ?

[c0d3z3r0]

Could someone please check on their MSO5 if these errors appear there as well, when running "pkill -9 appEntry; /rigol/appEntry -run"? FW version doesn't matter, but would be good to know which one.

Code: [Select]

<root@rigol>/rigol/appEntry -run
7 2048 16 2 "/dev/fb0"
!!!rom head fail
!!!rom inl fail
!!!rom head fail
!!!rom inl fail


with FW 00.01.03.00.01

Code: [Select]

/rigol/appEntry _run
7 2048 16 2 "/dev/fb0"
messageExchange.cpp 172 pCurrentIntf == NULL
insmod: can't insert '/rigol/drivers/libcomposite.ko': File exists
insmod: can't insert '/rigol/drivers/usbtmc_dev.ko': File exists
insmod: can't insert '/rigol/drivers/usb_gpib.ko': File exists


Thank you! Is there anything in your /rigol/data/vendorlog.txt?

[w.v.s.]

Thank you! Is there anything in your /rigol/data/vendorlog.txt?

same text as in yours.

[c0d3z3r0]

Thank you! Is there anything in your /rigol/data/vendorlog.txt?

same text as in yours.

weird, but probably a bug then...

[w.v.s.]

Did anyone try DOOM ( https://github.com/Spritetm/prboom-mso5k ) with a later version of the firmware? Did the  firmware upgrades so far only change the application software or also more fundamental stuff like libc or the kernel?

Update: Tried it and it worked with my firmware.

[sjm]

I can confirm success.

a) from system settings, set it to always boot up with default settings and power cycle
b) upgrade firmware with the official image available at Rigol NA
c) reboot, check that new version is actually running, and some of the software options are gone as expected
d) run a local upgrade with the patch files available here, wait patiently for the scope to wake up again -- and then power cycle
e) check that software version is the latest one and with all the options enabled, yes they are.

Now the scope is running self-calibration. Everything seems fine.