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.

[bobasaurus]

I have a weird problem... I just updated the firmware on my DHO924S to the latest version on Rigol's website (00.01.02.00.02) and now the screen is mirrored:





What the heck caused this?  Is it a setting I can change? 

The touch digitizer still works in the normal orientation (it's not inverted).  If I plug it into an HDMI monitor, the monitor shows the output in the correct orientation. 

[bobasaurus]

Hmmm... it mirrored itself back to the normal orientation again after waiting for a while without touching it.  Very odd. 

Edit: I restarted it and the screen is mirrored once more

[TimFox]

I was just watching "Dracula" (1931) where Bela Lugosi says "I dislike mirrors;  Dr van Helsing will explain."

[bobasaurus]

I downloaded the same firmware files again, removed everything from the flash drive, copied these fresh files to the flash drive, verified with WinMerge that they weren't corrupted, then updated the firmware on the scope again.  Now it's the correct orientation and has stayed that way through a couple restarts.  So maybe file corruption, or some weird setting (like RTL layout?) that carried over from the old stock firmware that's now overwritten. 

Edit: Darn, it mirrored itself again after running for a while.  Very odd, maybe a hardware issue with the display?

[norbert.kiszka]

Edit: Darn, it mirrored itself again after running for a while.  Very odd, maybe a hardware issue with the display?

My guess it's a corrupted device tree or Android settings. I have copy of dtb, so it will be in the attachment.

[bobasaurus]

After doing the self calibration of the scope it seems to have stabilized and stayed in the correct orientation... we'll see. 

Norbert, I'm not sure what to do with that dtb file, is there a guide somewhere?

[norbert.kiszka]

Norbert, I'm not sure what to do with that dtb file, is there a guide somewhere?

DTB stands for Device Tree Blob. This is a compiled device tree information about existing devices and their settings for a system kernel (modified Linux in this case). In a desktop computers usually You don't have such thing, because 99.999% is detected automatically and settings are driven by the drivers (modules) and the kernel. But in a so called embedded devices (also computers) mostly You need to give that information "by hand".

Rigol put Linux kernel and DTB directly into SD card (without file system). Use binwalk to check address and size of Your DTB and You can make binary comparison and change it (with dd or anything else) if it looks corrupted.

[Fohdeesha]

Long time no post....back in the market for a scope, had a 1054z ages ago but gave it away when I got out of RF stuff. Needing a scope again in the ~500 dollar range and it's come down to a DHO800 or a siglent. Reading a lot of this thread is pretty disheartening - would you guys say for use as a simple scope for RF type work and light protocol decode it would be fine? I do see a lot of very surprising bugs with LA features on the DHO900 stuff, I can't believe these releases made it out of testng (if there was any)

[Fungus]

would you guys say for use as a simple scope for RF type work and light protocol decode it would be fine?

Yes.

The DHO900 doesn't seem like a great purchase to me but the DHO804? Yep. It's great value.

Makes the DS1054Z feel like an antique by comparison. Protocol decode is orders of magnitude better.

[bobasaurus]

At this point I think I'd go with the Siglent instead... the bugs are kind of ridiculous on my Rigol. 

[Fungus]

At this point I think I'd go with the Siglent instead... the bugs are kind of ridiculous on my Rigol.

There's a new firmware that fixes just about everything.

I don't know if the bode plot is better or not, but bus have been fixed.

[TimFox]

At this point I think I'd go with the Siglent instead... the bugs are kind of ridiculous on my Rigol.

There's a new firmware that fixes just about everything.

I don't know if the bode plot is better or not, but bus have been fixed.

What is the new version and release date, and how to load?
I'm still waiting for a useful Bode plot, since that is why I bought the DHO914S in the first place last year.

[csuhi17]

That update was withdrawn due to a fatal bug.
Still waiting for the fix. It is impossible to estimate when the usable and safe version will be released.

[norbert.kiszka]

What is the new version and release date, and how to load?
I'm still waiting for a useful Bode plot, since that is why I bought the DHO914S in the first place last year.

Nobody knows when they will publish newer firmware update. Maybe tomorrow, maybe after 3 years and maybe never. Rigol is extremely slow with fixing bugs.

They made 1.03.06 and shortly after they put it back to the 1.02.02 probably due to bug that can brick Your scope.

I think probably it will be faster and better to do a full reverse engineering and made the whole thing from scratch. Personally I made a working system (orangerigol - see in my footer), so somebody can do at least app only - working with a current FPGA firmware.

[Fungus]

I'm still waiting for a useful Bode plot, since that is why I bought the DHO914S in the first place last year.

I don't have a 900 but Bode plot isn't mentioned in the release notes for the new firmware.

[TimFox]

I'm still waiting for a useful Bode plot, since that is why I bought the DHO914S in the first place last year.

I don't have a 900 but Bode plot isn't mentioned in the release notes for the new firmware.

Which version of firmware are you referring to?

[Fungus]

That update was withdrawn due to a fatal bug.
Still waiting for the fix. It is impossible to estimate when the usable and safe version will be released.

The new version exists.

It wasn't released last week because it was a national holiday in China and Rigol was closed.

Fingers crossed for this week.

[Fungus]

I don't have a 900 but Bode plot isn't mentioned in the release notes for the new firmware.

Which version of firmware are you referring to?

Release notes:

v00.01.03.00.04  2024/07/11

1. Solve the problem of vertical gear adjustment disappearing.
2. Solve the problem of Math module filter operation saving screen waveform in. csv file format and program controlled acquisition being empty.
3. DHO800 adds 5M storage depth.
4. Resolve the issue of channel 4 triggering status not being remembered when loading the last value.
5. Increase screen brightness adjustment function.
6. Solve the problem of auto failure when the instrument is connected to a self checking square wave and in a state above 2x gears.
7. Solve the problem of eliminating burrs in adjusting the time base waveform during waveform recording and playback.
8. Support modifying measurement items after opening the measurement module.
9. Add SMB network storage function.
10. Solve the problem of SPI decoding failure in digital channels.
11. Solve the problem of AX and BX following changes when the tracking cursor changes in time base.
12. Solve the problem of unstable triggering of 2Hz triangular wave input in 100ms non rolling mode.
13. Resolve the issue of inconsistency between webcontrol resolution and instrument screen.
14. Add quick on/off function.
15. Solve the problem of video triggering function not functioning properly.
16. Solve the problem of small sparrow RS232 triggering not being able to be triggered at low baud rates.
17. Resolve multilingual translation errors.

[norbert.kiszka]

That update was withdrawn due to a fatal bug.
Still waiting for the fix. It is impossible to estimate when the usable and safe version will be released.

The new version exists.

It wasn't released last week because it was a national holiday in China and Rigol was closed.

Fingers crossed for this week.

With a speed of a Rigol company, I will expect anything new from they somewhere in the next year.

[RogerG]

Hi,

the TP Link WIFI doesnt work anymore when connected directly into the scope's USB. But it still works when connected through an USB hub.

Any ideas?

[norbert.kiszka]

the TP Link WIFI doesnt work anymore when connected directly into the scope's USB. But it still works when connected through an USB hub.

Put it directly and try to reboot. If You unplug it and plug it back without reboot, it won't work. Sadly, it's Android instead of "regular" Linux.