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.
Hi, with that patch, ssh will remain available at next boot? I want to have it permanently. Thank you!
Excellent work. Successful permanent (ish) SSH communication with PUTTY. Thanks again!
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
Another successful upgrade to a MSO5074 using the 00.01.03.02.02 GEL file from RigolNA build date 2022-12-05.
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 meansQuote
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
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)
ohhhh wow thank you so much , Now I try to reinstall the original firmware
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.
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
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.
/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
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.01Code: [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?
Thank you! Is there anything in your /rigol/data/vendorlog.txt?
same text as in yours.