Rigol DHO800/900 Oscilloscope Bug Reports + Firmware

[Fungus]

RIGOL just released a software update, hopefully it fixes some stuff like the LA channels not decoding SPI

The release notes say it's fixed, it's item 10 on the list.

See my thread here: https://www.eevblog.com/forum/testgear/rigol-dho800900-new-firmware-1-03/

[csuhi17]

Hm,
it seems that Rigol has withdrawn their newest firmware release: DHO800_DHO900(Software)Update_v00.01.03.00.06.zip. It vanished from their websites.

Has anybody info about this? Can or should I do back to v00.01.02 ?

many thanks

Juergen

Heads up, guys, I think I found a really bad bug in the new firmware.

I think it's related to the XY mode crash bug which was reported earlier.

Setting defaults lets you open XY window, no problem, but I think I powered down the 'scope yesterday when it was in XY mode and today it won't boot up any more. The 'scope app crashes on startup.

ADB is running OK, even  Webcontrol is running OK, but the scope app won't start.

I found this in the log file which seems to confirm the XY window is the problem:

Code: [Select]

09-09 02:54:40.536  1095  1095 D AndroidRuntime: Shutting down VM
--------- beginning of crash
09-09 02:54:40.536  1095  1095 E AndroidRuntime: FATAL EXCEPTION: main
09-09 02:54:40.536  1095  1095 E AndroidRuntime: Process: com.rigol.scope, PID: 1095
09-09 02:54:40.536  1095  1095 E AndroidRuntime: java.lang.NullPointerException: ServiceEnum.getEWaveGridsFromValue1(t) must not be null
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at com.rigol.scope.views.grid.XYGridRulderView$2.onChanged(GridRulerView.kt:1509)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData.considerNotify(LiveData.java:131)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:149)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData.setValue(LiveData.java:307)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData$1.run(LiveData.java:91)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:755)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6157)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:912)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:802)
09-09 02:55:29.290   559   872 I am_crash: [1374,0,com.rigol.scope,684244549,java.lang.NullPointerException,ServiceEnum.getEWaveGridsFromValue1(t) must not be null,GridRulerView.kt,1509]
09-09 02:55:29.291   559   872 W ActivityManager:   Force finishing activity com.rigol.scope/.MainActivity
09-09 02:55:29.291   559   872 I am_finish_activity: [0,61604609,1283,com.rigol.scope/.MainActivity,force-crash]
09-09 02:55:29.291   559   872 I am_focused_stack: [0,0,1,finishActivity adjustFocus setFocusedActivity]
09-09 02:55:29.292   559   872 I wm_task_moved: [1281,1,0]
09-09 02:55:29.295   559   872 I am_focused_activity: [0,com.rigol.launcher/.MainActivity,finishActivity adjustFocus]
09-09 02:55:29.295   559   872 I am_pause_activity: [0,61604609,com.rigol.scope/.MainActivity]
09-09 02:55:29.297   559   872 I sysui_action: [316,-1]
09-09 02:55:29.298  1374  1374 I Process : Sending signal. PID: 1374 SIG: 9

I've tried downgrading the firmware via command line. It does the same thing.

I even tried an older firmware image (Dave's original image as posted in the hacking thread!) and it still won't start.

How do I get it to revert to default settings on boot (ie. with no XY window open)?

I did "hold down the DEFAULT button" on power-up thing but that doesn't work. There has to be a way, surely, but Google is failing me here.

Bottom line: Do NOT power off your DHO in XY mode until we figure this out!

[lunix]

Setting defaults lets you open XY window, no problem, but I think I powered down the 'scope yesterday when it was in XY mode and today it won't boot up any more. The 'scope app crashes on startup.

My scope had the same failure to boot, but after using the feature to load the previously used setup on booting.  I unplugged all of the cables overnight, and it booted the next day.  And, yes- I do regret buying this scope.  And, no- RIGOL doesn't seem to care.

[norbert.kiszka]

Setting defaults lets you open XY window, no problem, but I think I powered down the 'scope yesterday when it was in XY mode and today it won't boot up any more. The 'scope app crashes on startup.

My scope had the same failure to boot, but after using the feature to load the previously used setup on booting.  I unplugged all of the cables overnight, and it booted the next day.  And, yes- I do regret buying this scope.  And, no- RIGOL doesn't seem to care.

Rigol went from cheap and good enough to cheap and not-good enough.