Rigol DHO800/900 new firmware... 1.03

[sandor626]

I read your forum only after updating the firmware (and noticing some malfunctions)

[ptluis]

you can easily brick your device!

Technically not a "brick", it still boots, other apps work, just not the 'scope app.

What firmware version "bricked" your scope? v00.01.03.00.04 or v00.01.03.00.06?
I'm still able to download v00.01.03.00.06 from supportint.rigol.com

[norbert.kiszka]

Can somebody share v00.01.03.00.06 ? Looks like its not available on a Rigol page - link goes into error page 

Even maybe other v00.01.03 for a better hacking

[FxDev]

Can somebody share v00.01.03.00.06 ? Looks like its not available on a Rigol page - link goes into error page 

Even maybe other v00.01.03 for a better hacking

https://dosya.co/car0tg1vsc6j/DHO800_DHO900(Software)Update_v00.01.03.00.06.zip.html

[norbert.kiszka]

Can somebody share v00.01.03.00.06 ? Looks like its not available on a Rigol page - link goes into error page 

Even maybe other v00.01.03 for a better hacking

https://dosya.co/car0tg1vsc6j/DHO800_DHO900(Software)Update_v00.01.03.00.06.zip.html

Changes in relation to the v00.01.02.00.02, at first glance:

• FPGA firmware.
• New module fan_gpio_clt.ko - likely after decompilation, we will be able to manage fan voltage as we want. Eventually this can only turn on and off the fan. But there is a trace from a deleted PWM kernel module (both versions).
• New script quick_boot_test.sh - pseudo sleep mode - FPGA, fan and screen backlight is shut down, but CPU is still running (In my tests I was able to run this scope on Debian GNU/Linux and without fan for many hours). Maybe they don't know how to do a S3 mode or Android 7.x is not able to handle it.
• Some strange and top secret staff hidden in a /tools/spidev and "golden_ver" variables in a quick_boot_test.sh.
• All apk files was changed (Launcher.apk, Sparrow.apk, Webcontrol.apk).

Now I think to change only FPGA firmware on my scope and see what will go boom 

[norbert.kiszka]

Now I think to change only FPGA firmware on my scope and see what will go boom 

I did it. After small basic tests I don't see any changes in scope behavior or measurements. Bug in a bode plot is not fixed after this change.

I copied (by overwrite) /rigol/FPGA/BOOT.bin and /rigol/FPGA/BOOT_SelfTest.bin by command adb push.

FPGA was reflashed with command:

Code: [Select]

/rigol/shell/reload_fpga.sh /rigol/FPGA/BOOT.bin 0x400000
Screenshot with a changed FPGA firmware:

[norbert.kiszka]

...
FPGA was reflashed with command:
...

After copying new files from 1.03 (/rigol/tools/spidev, /rigol/drivers/fan_gpio_clt.ko and /rigol/shell/quick_boot_test.sh), making them executable (chmod +x path/to/a/file) and with little changes in a quick_boot_test.sh I managed to make a fully working "pseudo-sleep" in a 1.02, but only via adb:

Code: [Select]

ramzes[member=380248]tm[/member]:~$ adb shell /rigol/shell/quick_boot_test.sh off
...... Quick Power Off ...... Start @ 2024.09.17 05.11.29
lspci
...... Quick Power Off ...... End @ 2024.09.17 05.11.31

ramzes[member=380248]tm[/member]:~$ adb shell /rigol/shell/quick_boot_test.sh on
...... Quick Power On ...... Start @ 2024.09.17 05.11.37

... PLL Init Size = 46
PLL Init : sum use time : 2.3184 s

1.1.3
1
1
3
rx: �������������������
����
��
��

old system version < 2
old golden version need sleep 10
/rigol/tools/spi2boot 0x400000
Boot MultiBoot Image
Waiting 5s For MultiBoot Image Boot...

done


insmod /rigol/driver/xdma.ko

The Kernel module installed correctly and the xmda devices were recognized.
DONE

lspci
00:00.0 Class 0604: Device 1d87:0100
01:00.0 Class 0700: Device 10ee:7022
Starting: Intent { cmp=com.rigol.scope/.MainActivity }
...... Quick Power On ...... End @ 2024.09.17 05.12.07

ramzes[member=380248]tm[/member]:~$

Argument "on" takes around 30 seconds - at least for now.

After "off", network still works and all apps (in exception of a scope app) can be used via http://your.crappy.scope.ip/control.html

Now I will try to make a "game mode" without fan, but most likely I need to make a binary changes in a fan_gpio_clt.ko to make a screen work (backlight/brightness doesn't do the trick).

My modification of a quick_boot_test.sh is in the attachment. Bon apetit!

[norbert.kiszka]

Now I will try to make a "game mode" without fan, but most likely I need to make a binary changes in a fan_gpio_clt.ko to make a screen work (backlight/brightness doesn't do the trick).

I decompiled this module and only one thing it do is turning on and off single GPIO pin. Looks like fan and a backlight are powered from this pin, so for now it will be impossible to turn off the fan and have internal screen visible.

Anyway, I did a game mode in this script - new version is in the attachment.

----------------------------

Make this to go into pseudo-sleep:

Code: [Select]

/rigol/shell/quick_boot_test.sh off
Turn it back on:

Code: [Select]

/rigol/shell/quick_boot_test.sh on
Game mode (scope app disabled and it will not work when loaded by hand). To use scope app, use argument "on", as above.

Code: [Select]

/rigol/shell/quick_boot_test.sh letsplay
---------

Modes can be switched at any time, no matter what mode was before.

Physical power switch most likely will turn it off completely - maybe upgrading Launcher up to 1.03 will help? I will try it tomorrow, because Im tired.

[FxDev]

Can you find out language file. I want to translate to Turkish.

[norbert.kiszka]

Can you find out language file. I want to translate to Turkish.

It's in the Sparrow.apk.

[FxDev]

I dont have any experience on android files
But if you send me the data, i can translate it to Turkish.

[norbert.kiszka]

I dont have any experience on android files
But if you send me the data, i can translate it to Turkish.

First of all, You have to add language option. For that, You have to decompile code from a binary form. How to do it in easiest way with MS code (IDE) plugin is already in a hacking topic.

Also, You can overwrite one of the existing languages...

After making changes, You have to compile it back, check it, and... You get the idea.

[sandor626]

I spent almost 1000 euros on an oscilloscope, my DHO 924S, which doesn't work.
I will wait another 15 days, if Rigol does not solve the problem by releasing a stable firmware version, I will return the oscilloscope to Rigol Italia asking for a refund of what I paid.

[Fungus]

I spent almost 1000 euros on an oscilloscope, my DHO 924S, which doesn't work.

Because of this firmware?

I can't say much (they asked me not to) but things ARE moving and I've learned some very interesting things about Rigol over the last week or so. Expect big changes.

[norbert.kiszka]

I spent almost 1000 euros on an oscilloscope, my DHO 924S, which doesn't work.

Because of this firmware?

I can't say much (they asked me not to) but things ARE moving and I've learned some very interesting things about Rigol over the last week or so. Expect big changes.

In my experience, they don't give a sh*t about users problems of their products.

[NE666]

Expect big changes.

If that glorious future entails no longer farting out half-finished products for customers to beta test in production, in a vacuum, at their own expense, without any clear commitment or timescale to remedy, then I for one welcome our new TE overlords.

I shan't hold my breath.

[RAPo]

Are you referring for specific changes on DHO800/900 firmware  or to a broader topic?

I can't say much (they asked me not to) but things ARE moving and I've learned some very interesting things about Rigol over the last week or so. Expect big changes.

[ebastler]

I can't say much (they asked me not to) but things ARE moving and I've learned some very interesting things about Rigol over the last week or so. Expect big changes.

I heard rumours that we can expect yet another new scope from Rigol, higher-end this time. If that is indeed the case it would not bode well for support and attention on their existing products.

[norbert.kiszka]

I can't say much (they asked me not to) but things ARE moving and I've learned some very interesting things about Rigol over the last week or so. Expect big changes.

I heard rumours that we can expect yet another new scope from Rigol, higher-end this time. If that is indeed the case it would not bode well for support and attention on their existing products.

Soon or later most scope manufacturers will make a another model...

[ebastler]

Soon or later most scope manufacturers will make a another model...

Yes, but some of them have more of a product family or platform approach and less of a tendency to start from scratch with something new before the old products are mature and stable.

Edit: Having said that, they really need to do something in the DHO1000 and 4000 range. Either a refresh which adds logic analyzer and function generator options, or maybe they decided to start over?

[Antonio90]

It's a pity the DHO1000 has bugs, an incomplete FFT and lacks 50 Ohm termination. The hardware and front-end are really outstanding.

[Fungus]

I don't think there's any low-end 'scope with 50-Ohm termination.

Somebody said it's because it's very easy to blow one up if you enable 50 Ohms so they don't want newbies to have it. That sounds believable to me.

[Antonio90]

Maybe, I guess it is off-topic, but the DHO1000 is around 1200€ VAT included, and competes directly with SDS1000X-HD, which has 50 Ohms.
There was some discussion about the FFT in the SDS800X-HD. A few images from the DHO1000 came up as a comparison. https://www.eevblog.com/forum/testgear/sds800x-hd-review-demonstration-thread/msg5483947/#msg5483947
If Rigol were to make a truly good FFT implementation it would have  no match in this price class, thanks to their ASIC.

[J-R]

When I e-mailed Rigol about the DM800 series bugs, the responses were unbelievably bad.  First response was they'd send my comments to R&D for investigation, which is total deflection because people have already commented about this so they surely know about it.  Second response (first response from R&D) was just some marketing junk about how their DMM was better than their previous ones. I hit them again with all of the proof of the issues with links to Youtube timestamps and EEVblog forum posts and their response back was please provide proof of the issues, completely ignoring the proof already provided!  They also said they weren't going to consider the issues reported on the EEVblog since they were from an "informal forum" and that they were not going to investigate the issue any further.

[J-R]

I spent almost 1000 euros on an oscilloscope, my DHO 924S, which doesn't work.
I will wait another 15 days, if Rigol does not solve the problem by releasing a stable firmware version, I will return the oscilloscope to Rigol Italia asking for a refund of what I paid.

You should return it while you still can.  If they fix the bugs, buy a lesser model and "upgrade" it later.