Author Topic: Hacking the Rigol DHO800/900 Scope  (Read 1945805 times)

Evi and 24 Guests are viewing this topic.

Offline iMo

  • Super Contributor
  • ***
  • Posts: 5759
  • Country: li
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3275 on: January 14, 2025, 09:29:03 am »
I would not indicate time duration for the self-cal as it may take much longer (ie. 36 minutes in my case after upgrade to 1.04 with the vanilla 804 v 1.03, probes disconnected) and some people may try to stop the self-cal before it actually finished then..
It will stop with a message that the self-cal has been successful written on the display.

..Probably self-calibration will do nothing, but it's 15 minutes, so it's worth to try.

PS: I would also let the scope run for several hours before the self-cal, such all inside the scope get at the right temperature..
« Last Edit: January 14, 2025, 09:47:28 am by iMo »
Readers discretion is advised..
 

Offline ebourg

  • Contributor
  • Posts: 34
  • Country: fr
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3276 on: January 14, 2025, 09:41:15 am »
So, I have prepared a short instruction on disabling signature verification by the system and installing modified web control and oscilloscope applications.
Disabling signature verification is necessary so that the system considers the installed applications trusted (supposedly they are signed with a system key) and gives these applications access to all services. Without this, the modified oscilloscope application will not be able to save screenshots, and the modified web control will not be able to show the oscilloscope screen.

Thank you for figuring this out! Out of curiosity, what did you change in services.jar? Is it possible to build the modified jar from your GitHub project?
 

Offline shapirus

  • Super Contributor
  • ***
  • Posts: 1813
  • Country: ua
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3277 on: January 14, 2025, 10:36:05 am »
So, I have prepared a short instruction on disabling signature verification by the system and installing modified web control and oscilloscope applications.
Disabling signature verification is necessary so that the system considers the installed applications trusted (supposedly they are signed with a system key) and gives these applications access to all services. Without this, the modified oscilloscope application will not be able to save screenshots, and the modified web control will not be able to show the oscilloscope screen.

Thank you for figuring this out! Out of curiosity, what did you change in services.jar? Is it possible to build the modified jar from your GitHub project?
https://www.eevblog.com/forum/testgear/hacking-the-rigol-dho800900-scope/msg5408810/#msg5408810 ;)
 
The following users thanked this post: iMo, AndyBig

Offline iMo

  • Super Contributor
  • ***
  • Posts: 5759
  • Country: li
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3278 on: January 14, 2025, 01:25:22 pm »
Btw., is the mod via the procedure with modding the vendor.bin reversible, such the changes are not detectable? What I've seen somewhere the RKey.data becomes Key.data after the mod.
So perhaps returning the original RKey.data and vendor.bin will make it vanilla again (like "Make Rigol Vanilla Again")??..
« Last Edit: January 14, 2025, 01:27:59 pm by iMo »
Readers discretion is advised..
 

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3279 on: January 14, 2025, 01:26:58 pm »
You can backup whole /rigol/data directory.

Offline AndyBig

  • Frequent Contributor
  • **
  • Posts: 539
  • Country: ru
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3280 on: January 14, 2025, 01:29:25 pm »
So, I have prepared a short instruction on disabling signature verification by the system and installing modified web control and oscilloscope applications.
Disabling signature verification is necessary so that the system considers the installed applications trusted (supposedly they are signed with a system key) and gives these applications access to all services. Without this, the modified oscilloscope application will not be able to save screenshots, and the modified web control will not be able to show the oscilloscope screen.

Thank you for figuring this out! Out of curiosity, what did you change in services.jar? Is it possible to build the modified jar from your GitHub project?
No, there is only a pre-built services.jar on GitHub. You can rebuild it yourself, which is what shapirus did, his rebuilt file is on my GitHub :) He found this method online and applied it. I tried to rebuild it myself, but something didn't work the first time and I didn't bother to figure out what the problem was with it, I just used the file provided by shapirus :)
In short - in this file, in several signature verification methods, you need to make them always return zero.
 

Offline lordstein

  • Contributor
  • Posts: 19
  • Country: co
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3281 on: January 14, 2025, 05:32:12 pm »
i have problem with the probe compesation on the chanel 3, is the chanel since I already tried another probes.



Looks like overcompensated. Probably self-calibration will do nothing, but it's 15 minutes, so it's worth to try.

If self-calibration will not help, reach Your seller and request guaranty service. I guess it's due to the flux residues or failure at manufacturing IC which is the heart of all four AFD.

Can You measure input capacitance of all four channels?
I got these measurements when measuring capacitance at the outputs with the multimeter
1: 1.64nf
2: 1.60nf
3: 1.84nf
4: 1.58nf
 

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1492
  • Country: de
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3282 on: January 14, 2025, 06:00:09 pm »
I'm afraid the measurement of the input capacitance with a multimeter may not be accurate. A check with an RLC bridge type instrument (Shannon Tweezers) results in 15.82pF, 15.86pF, 15.8pF and 15.92pF for channels 1~4. These figures match well with the specified 15pF and the tolerance is about what's to be expected.
 

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1492
  • Country: de
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3283 on: January 14, 2025, 07:16:59 pm »
Unfortunately...got to ask for some assistance. I just "half-bricked" my scope  :-//

After successfully installing @AndyBig's U/I patch and playing around with it a little (really nice add-ons by the way), I decided to change the time zone in "rigol/shell/start_rigol_app.sh" -- pulled it, edited it, pushed it. Upon the next reboot, the scope only booted to the "RIGOL" splash screen, or so it seems. At least no relays are clicking or LEDs flashing. I still can access the scope via "adb" and the web app allows me to make a screenshot...of the "RIGOL" splash screen. Pushed the original "start_rigol_app.sh" back on the scope -- no change. Please see attached the list of running processes if that may be helpful. It seems everything is running, but anyway, no scope app on the screen. Maybe someone has got a hint for me what to try before I restore the SD card image that I took some time ago.

Thanks,
Thomas


Code: [Select]
rk3399_rigol:/ # ps
USER      PID   PPID  VSIZE  RSS   WCHAN              PC  NAME
root      1     0     10524  2024  SyS_epoll_ 00004ccd60 S /init
root      2     0     0      0       kthreadd 0000000000 S kthreadd
root      3     2     0      0     smpboot_th 0000000000 S ksoftirqd/0
root      4     2     0      0     worker_thr 0000000000 S kworker/0:0
root      5     2     0      0     worker_thr 0000000000 S kworker/0:0H
root      7     2     0      0     rcu_gp_kth 0000000000 S rcu_preempt
root      8     2     0      0     rcu_gp_kth 0000000000 S rcu_sched
root      9     2     0      0     rcu_gp_kth 0000000000 S rcu_bh
root      10    2     0      0     smpboot_th 0000000000 S migration/0
root      11    2     0      0     smpboot_th 0000000000 S watchdog/0
root      12    2     0      0     smpboot_th 0000000000 S watchdog/1
root      13    2     0      0     smpboot_th 0000000000 S migration/1
root      14    2     0      0     smpboot_th 0000000000 S ksoftirqd/1
root      16    2     0      0     worker_thr 0000000000 S kworker/1:0H
root      17    2     0      0     smpboot_th 0000000000 S watchdog/2
root      18    2     0      0     smpboot_th 0000000000 S migration/2
root      19    2     0      0     smpboot_th 0000000000 S ksoftirqd/2
root      20    2     0      0     worker_thr 0000000000 S kworker/2:0
root      21    2     0      0     worker_thr 0000000000 S kworker/2:0H
root      22    2     0      0     smpboot_th 0000000000 S watchdog/3
root      23    2     0      0     smpboot_th 0000000000 S migration/3
root      24    2     0      0     smpboot_th 0000000000 S ksoftirqd/3
root      26    2     0      0     worker_thr 0000000000 S kworker/3:0H
root      27    2     0      0     smpboot_th 0000000000 S watchdog/4
root      28    2     0      0     smpboot_th 0000000000 S migration/4
root      29    2     0      0     smpboot_th 0000000000 S ksoftirqd/4
root      31    2     0      0     worker_thr 0000000000 S kworker/4:0H
root      32    2     0      0     smpboot_th 0000000000 S watchdog/5
root      33    2     0      0     smpboot_th 0000000000 S migration/5
root      34    2     0      0     smpboot_th 0000000000 S ksoftirqd/5
root      35    2     0      0     worker_thr 0000000000 S kworker/5:0
root      36    2     0      0     worker_thr 0000000000 S kworker/5:0H
root      37    2     0      0      devtmpfsd 0000000000 S kdevtmpfs
root      38    2     0      0     rescuer_th 0000000000 S netns
root      39    2     0      0     rescuer_th 0000000000 S perf
root      40    2     0      0     console_th 0000000000 S kconsole
root      41    2     0      0       watchdog 0000000000 S khungtaskd
root      42    2     0      0     rescuer_th 0000000000 S writeback
root      43    2     0      0     ksm_scan_t 0000000000 S ksmd
root      44    2     0      0     rescuer_th 0000000000 S crypto
root      45    2     0      0     rescuer_th 0000000000 S bioset
root      46    2     0      0     rescuer_th 0000000000 S kblockd
root      47    2     0      0     worker_thr 0000000000 S kworker/4:1
root      48    2     0      0     rescuer_th 0000000000 S devfreq_wq
root      49    2     0      0     rescuer_th 0000000000 S cfg80211
root      50    2     0      0     cpufreq_in 0000000000 S cfinteractive
root      52    2     0      0     rescuer_th 0000000000 S rpciod
root      68    2     0      0         kswapd 0000000000 S kswapd0
root      69    2     0      0     rescuer_th 0000000000 S vmstat
root      70    2     0      0     fsnotify_m 0000000000 S fsnotify_mark
root      71    2     0      0     rescuer_th 0000000000 S nfsiod
root      72    2     0      0     rescuer_th 0000000000 S cifsiod
root      104   2     0      0     irq_thread 0000000000 S irq/224-rockchi
root      105   2     0      0     irq_thread 0000000000 S irq/225-rockchi
root      106   2     0      0     irq_thread 0000000000 S irq/226-rockchi
root      107   2     0      0     irq_thread 0000000000 S irq/227-rockchi
root      108   2     0      0     irq_thread 0000000000 S irq/228-rockchi
root      109   2     0      0     irq_thread 0000000000 S irq/45-ff670000
root      110   2     0      0     rescuer_th 0000000000 S vcodec
root      111   2     0      0     irq_thread 0000000000 S irq/41-ff650000
root      112   2     0      0     irq_thread 0000000000 S irq/40-ff650000
root      113   2     0      0     rescuer_th 0000000000 S vcodec
root      114   2     0      0     irq_thread 0000000000 S irq/43-ff660000
root      115   2     0      0     rescuer_th 0000000000 S bioset
root      116   2     0      0     rescuer_th 0000000000 S bioset
root      117   2     0      0     rescuer_th 0000000000 S bioset
root      118   2     0      0     rescuer_th 0000000000 S bioset
root      119   2     0      0     rescuer_th 0000000000 S bioset
root      120   2     0      0     rescuer_th 0000000000 S bioset
root      121   2     0      0     rescuer_th 0000000000 S bioset
root      122   2     0      0     rescuer_th 0000000000 S bioset
root      123   2     0      0     rescuer_th 0000000000 S bioset
root      124   2     0      0     rescuer_th 0000000000 S bioset
root      125   2     0      0     rescuer_th 0000000000 S bioset
root      126   2     0      0     rescuer_th 0000000000 S bioset
root      127   2     0      0     rescuer_th 0000000000 S bioset
root      128   2     0      0     rescuer_th 0000000000 S bioset
root      129   2     0      0     rescuer_th 0000000000 S bioset
root      130   2     0      0     rescuer_th 0000000000 S bioset
root      131   2     0      0     rescuer_th 0000000000 S bioset
root      132   2     0      0     rescuer_th 0000000000 S bioset
root      133   2     0      0     rescuer_th 0000000000 S bioset
root      134   2     0      0     rescuer_th 0000000000 S bioset
root      135   2     0      0     rescuer_th 0000000000 S bioset
root      136   2     0      0     rescuer_th 0000000000 S bioset
root      137   2     0      0     rescuer_th 0000000000 S bioset
root      138   2     0      0     rescuer_th 0000000000 S bioset
root      139   2     0      0     rescuer_th 0000000000 S bioset
root      140   2     0      0     rescuer_th 0000000000 S nvme
root      141   2     0      0     kthread_wo 0000000000 S spi1
root      142   2     0      0     kthread_wo 0000000000 S spi2
root      144   2     0      0         msleep 0000000000 D kworker/0:1
root      146   2     0      0     worker_thr 0000000000 S kworker/1:1
root      147   2     0      0     irq_thread 0000000000 S irq/115-rk808
root      148   2     0      0     irq_thread 0000000000 S irq/35-rockchip
root      149   2     0      0     rescuer_th 0000000000 S dm_bufio_cache
root      150   2     0      0     worker_thr 0000000000 S kworker/4:2
root      151   2     0      0     irq_thread 0000000000 S irq/26-mmc1
root      152   2     0      0     rescuer_th 0000000000 S bioset
root      153   2     0      0     worker_thr 0000000000 S kworker/1:2
root      154   2     0      0     mmc_queue_ 0000000000 S mmcqd/0
root      155   2     0      0     rescuer_th 0000000000 S binder
root      156   2     0      0     rescuer_th 0000000000 S ipv6_addrconf
root      157   2     0      0     wait_woken 0000000000 S krfcommd
root      159   2     0      0     irq_thread 0000000000 S irq/46-rga
root      160   2     0      0     worker_thr 0000000000 S kworker/2:1
root      161   2     0      0     rescuer_th 0000000000 S deferwq
root      162   2     0      0     rescuer_th 0000000000 S hpd_queue
root      163   2     0      0     irq_thread 0000000000 S irq/55-ff940000
root      164   2     0      0     rescuer_th 0000000000 S gpu_power_off_w
root      166   2     0      0     worker_thr 0000000000 S kworker/3:1
root      167   2     0      0     worker_thr 0000000000 S kworker/u13:1
root      168   2     0      0     rescuer_th 0000000000 S kbase_job_fault
root      169   2     0      0     worker_thr 0000000000 S kworker/u12:2
root      170   2     0      0     worker_thr 0000000000 R kworker/u12:3
root      172   1     5780   1068  poll_sched 00004ccd90 S /sbin/ueventd
root      174   2     0      0     worker_thr 0000000000 S kworker/4:1H
root      175   2     0      0     worker_thr 0000000000 S kworker/5:1H
root      176   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p10
root      177   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      179   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p9-
root      180   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      184   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p11
root      185   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      189   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p16
root      190   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      192   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p15
root      193   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
logd      194   1     18020  3600  sigsuspend 7379817d4c S /system/bin/logd
root      199   2     0      0     kauditd_th 0000000000 S kauditd
root      203   1     5348   2704  __skb_recv 00eb9b24a8 S /system/bin/debuggerd
root      204   1     10288  3340  __skb_recv 7d6b439b24 S /system/bin/debuggerd64
root      205   1     18148  5976  hrtimer_na 7a06161574 S /system/bin/vold
root      206   204   9904   604   __skb_recv 7d6b43a67c S debuggerd64:signaller
root      208   203   5092   536   __skb_recv 00eb9b36dc S debuggerd:signaller
root      215   2     0      0     worker_thr 0000000000 S kworker/0:1H
root      217   1     6432   932   SyS_epoll_ 000047cc78 S /sbin/healthd
root      219   1     8932   2820  SyS_epoll_ 70e5cf0b84 S /system/bin/lmkd
system    220   1     9156   2312  binder_thr 7a1ad4ec74 S /system/bin/servicemanager
system    221   1     262208 40272 SyS_epoll_ 7f33d6cb84 S /system/bin/surfaceflinger
shell     223   1     7716   2576  wait_woken 7e4bc3d67c S /system/bin/sh
shell     224   1     14144  1036  poll_sched 00004a5c90 S /sbin/adbd
root      227   1     4744   300   __skb_recv 0000410c58 S /system/xbin/su
root      231   1     7716   1792  sigsuspend 795014bd4c S /system/bin/sh
root      233   1     2154796 133704 poll_sched 75d819fca4 S zygote64
root      234   1     1592648 119412 poll_sched 00f0c5b734 S zygote
audioserver 235   1     26404  8932  binder_thr 00efd6d68c S /system/bin/audioserver
drm       236   1     13860  6484  binder_thr 00f290f68c S /system/bin/drmserver
root      237   1     9620   2512  unix_strea 784fd2767c S /system/bin/installd
keystore  238   1     12640  4404  binder_thr 74be3bfc74 S /system/bin/keystore
mediacodec 239   1     33192  9416  binder_thr 00ef20268c S media.codec
media     240   1     38440  11984 binder_thr 00f35f068c S /system/bin/mediadrmserver
mediaex   241   1     45224  9992  binder_thr 00e73b168c S media.extractor
media     242   1     67324  14408 binder_thr 00f092868c S /system/bin/mediaserver
root      243   1     26908  5056  binder_thr 7a1ed36c74 S /system/bin/netd
root      244   1     10436  3792  poll_sched 7f11debcbc S /system/vendor/bin/crashlogd
root      246   1     10188  1936  devkmsg_re 728b6a167c S /vendor/bin/log-watch
system    247   1     12328  4300  binder_thr 7432e06c74 S /system/bin/gatekeeperd
root      248   1     8272   2040  hrtimer_na 7d57a7c574 S /system/xbin/perfprofd
root      252   231   10100  4108  poll_sched 77df44acbc S /system/bin/sshd
root      253   1     7716   2548  sigsuspend 7d2c42ed4c S /system/bin/sh
root      262   253   9096   1768  __skb_recv 71da75d6dc S /system/vendor/bin/logcatext
root      279   2     0      0     worker_thr 0000000000 S kworker/3:1H
root      291   2     0      0     rescuer_th 0000000000 S kbase_event
root      549   2     0      0     worker_thr 0000000000 S kworker/2:1H
root      550   2     0      0     worker_thr 0000000000 S kworker/u13:2
system    559   233   2201276 205720 SyS_epoll_ 75d819fb84 S system_server
root      592   2     0      0     worker_thr 0000000000 S kworker/1:1H
root      636   2     0      0     rescuer_th 0000000000 S kbase_event
u0_a15    651   233   1787376 161492 SyS_epoll_ 75d819fb84 S com.android.systemui
system    665   233   1779444 111424 SyS_epoll_ 75d819fb84 S com.android.settings
root      683   2     0      0     rescuer_th 0000000000 S rtw_workqueue
root      687   2     0      0     rescuer_th 0000000000 S kbase_event
media_rw  732   205   0      0        do_exit 0000000000 Z sdcard
root      776   2     0      0     down_inter 0000000000 S RTW_CMD_THREAD
root      779   2     0      0     worker_thr 0000000000 S kworker/0:2
wifi      822   1     14312  7112  poll_sched 7d811decbc S /system/bin/wpa_supplicant
root      932   2     0      0     rescuer_th 0000000000 S kbase_event
u0_a5     961   233   1572436 73564 SyS_epoll_ 75d819fb84 S android.ext.services
system    994   233   1577156 80032 SyS_epoll_ 75d819fb84 S android.rockchip.update.service
system    1009  233   1575600 73236 SyS_epoll_ 75d819fb84 S com.android.keychain
system    1024  233   1776148 140528 SyS_epoll_ 75d819fb84 S com.rigol.launcher
u0_a27    1049  233   1577600 75652 SyS_epoll_ 75d819fb84 S com.android.printspooler
u0_a4     1067  233   1584764 93480 SyS_epoll_ 75d819fb84 S android.process.media
root      1131  2     0      0     rescuer_th 0000000000 S kbase_event
root      1146  2     0      0     worker_thr 0000000000 S kworker/3:2
u0_a7     1156  233   1572632 73624 SyS_epoll_ 75d819fb84 S com.android.managedprovisioning
system    1174  233   1592948 96572 SyS_epoll_ 75d819fb84 S com.rigol.launcher:Watchdog
system    1188  233   1630248 105276 SyS_epoll_ 75d819fb84 S com.rigol.webcontrol
root      1295  2     0      0     worker_thr 0000000000 S kworker/5:2
system    1329  1024  4744   308      do_wait 0000411078 S su
system    1331  1329  4744   140   unix_strea 0000410f70 S su
root      1333  1     4744   140      do_wait 0000411078 S /system/xbin/su
root      1334  1333  4744   148      do_wait 0000411078 S /system/xbin/su
root      1335  1334  7716   2644   pipe_wait 799ae1767c S sh
root      1398  2     0      0     worker_thr 0000000000 S kworker/5:1
root      1407  2     0      0     worker_thr 0000000000 S kworker/1:0
system    1408  233   1689076 116656 hrtimer_na 75d81a0574 S com.rigol.scope
root      1430  2     0      0     worker_thr 0000000000 S kworker/u13:0
root      1431  2     0      0     worker_thr 0000000000 R kworker/u12:0
shell     1433  224   7716   2684  sigsuspend 7490cc4d4c S /system/bin/sh
root      1436  1433  4744   304      do_wait 0000411078 S su
root      1437  1436  6808   140   wait_woken 0000410f70 S su
root      1439  1     4744   140      do_wait 0000411078 S /system/xbin/su
root      1442  1439  4744   148      do_wait 0000411078 S /system/xbin/su
root      1443  1442  7716   2596  sigsuspend 74ae5d4d4c S sh
root      1454  1443  9116   2440           0 751294e67c R ps
rk3399_rigol:/ #
 

Offline shapirus

  • Super Contributor
  • ***
  • Posts: 1813
  • Country: ua
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3284 on: January 14, 2025, 07:27:11 pm »
Unfortunately...got to ask for some assistance. I just "half-bricked" my scope  :-//

After successfully installing @AndyBig's U/I patch and playing around with it a little (really nice add-ons by the way), I decided to change the time zone in "rigol/shell/start_rigol_app.sh" -- pulled it, edited it, pushed it. Upon the next reboot, the scope only booted to the "RIGOL" splash screen, or so it seems. At least no relays are clicking or LEDs flashing. I still can access the scope via "adb" and the web app allows me to make a screenshot...of the "RIGOL" splash screen. Pushed the original "start_rigol_app.sh" back on the scope -- no change. Please see attached the list of running processes if that may be helpful. It seems everything is running, but anyway, no scope app on the screen. Maybe someone has got a hint for me what to try before I restore the SD card image that I took some time ago.
At last, I'm not alone.

I had precisely the same issue. Half-brick after changing the time zone. In my case it eventually booted after I left it sitting powered on, I think it took a few hours. When it finally booted, I restored the original time zone and never touched it again.
 
The following users thanked this post: TurboTom

Offline AndyBig

  • Frequent Contributor
  • **
  • Posts: 539
  • Country: ru
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3285 on: January 14, 2025, 07:40:10 pm »
I just measured the capacitance of the oscilloscope off at 100 kHz:
- oscilloscope input: 17.25 pF
- probe on 1:1 divider (connected to the oscilloscope, of course): 79.34 pF
- probe on 1:10 divider: 13.97 pF
The readings differ slightly between channels, within 0.2 pF.
 

Offline AndyBig

  • Frequent Contributor
  • **
  • Posts: 539
  • Country: ru
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3286 on: January 14, 2025, 07:50:08 pm »
Unfortunately...got to ask for some assistance. I just "half-bricked" my scope  :-//

After successfully installing @AndyBig's U/I patch and playing around with it a little (really nice add-ons by the way), I decided to change the time zone in "rigol/shell/start_rigol_app.sh" -- pulled it, edited it, pushed it. Upon the next reboot, the scope only booted to the "RIGOL" splash screen, or so it seems. At least no relays are clicking or LEDs flashing. I still can access the scope via "adb" and the web app allows me to make a screenshot...of the "RIGOL" splash screen. Pushed the original "start_rigol_app.sh" back on the scope -- no change. Please see attached the list of running processes if that may be helpful. It seems everything is running, but anyway, no scope app on the screen. Maybe someone has got a hint for me what to try before I restore the SD card image that I took some time ago.

Thanks,
Thomas

It is better to look at the logcat output a minute after turning on the oscilloscope. Most likely, the reason for the failure to boot will be displayed there.
Under Windows, the adb logcat >logcat.txt command will save the output to the logcat.txt file in the current directory. Run this command, wait 3-5 seconds, interrupt it with Ctrl+C. Nothing is displayed on the screen, everything is written to the file.

Actually, I've changed the time zone in the startup script several times, and this has never happened before. Maybe when editing the script is saved with damage? Like the added UTF-8 header, or replacing \r with \r\n ?
« Last Edit: January 14, 2025, 07:52:05 pm by AndyBig »
 
The following users thanked this post: Fungus, TurboTom

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3287 on: January 14, 2025, 07:51:33 pm »
Unfortunately...got to ask for some assistance. I just "half-bricked" my scope  :-//

After successfully installing @AndyBig's U/I patch and playing around with it a little (really nice add-ons by the way), I decided to change the time zone in "rigol/shell/start_rigol_app.sh" -- pulled it, edited it, pushed it. Upon the next reboot, the scope only booted to the "RIGOL" splash screen, or so it seems. At least no relays are clicking or LEDs flashing. I still can access the scope via "adb" and the web app allows me to make a screenshot...of the "RIGOL" splash screen. Pushed the original "start_rigol_app.sh" back on the scope -- no change. Please see attached the list of running processes if that may be helpful. It seems everything is running, but anyway, no scope app on the screen. Maybe someone has got a hint for me what to try before I restore the SD card image that I took some time ago.

Thanks,
Thomas


Code: [Select]
rk3399_rigol:/ # ps
USER      PID   PPID  VSIZE  RSS   WCHAN              PC  NAME
root      1     0     10524  2024  SyS_epoll_ 00004ccd60 S /init
root      2     0     0      0       kthreadd 0000000000 S kthreadd
root      3     2     0      0     smpboot_th 0000000000 S ksoftirqd/0
root      4     2     0      0     worker_thr 0000000000 S kworker/0:0
root      5     2     0      0     worker_thr 0000000000 S kworker/0:0H
root      7     2     0      0     rcu_gp_kth 0000000000 S rcu_preempt
root      8     2     0      0     rcu_gp_kth 0000000000 S rcu_sched
root      9     2     0      0     rcu_gp_kth 0000000000 S rcu_bh
root      10    2     0      0     smpboot_th 0000000000 S migration/0
root      11    2     0      0     smpboot_th 0000000000 S watchdog/0
root      12    2     0      0     smpboot_th 0000000000 S watchdog/1
root      13    2     0      0     smpboot_th 0000000000 S migration/1
root      14    2     0      0     smpboot_th 0000000000 S ksoftirqd/1
root      16    2     0      0     worker_thr 0000000000 S kworker/1:0H
root      17    2     0      0     smpboot_th 0000000000 S watchdog/2
root      18    2     0      0     smpboot_th 0000000000 S migration/2
root      19    2     0      0     smpboot_th 0000000000 S ksoftirqd/2
root      20    2     0      0     worker_thr 0000000000 S kworker/2:0
root      21    2     0      0     worker_thr 0000000000 S kworker/2:0H
root      22    2     0      0     smpboot_th 0000000000 S watchdog/3
root      23    2     0      0     smpboot_th 0000000000 S migration/3
root      24    2     0      0     smpboot_th 0000000000 S ksoftirqd/3
root      26    2     0      0     worker_thr 0000000000 S kworker/3:0H
root      27    2     0      0     smpboot_th 0000000000 S watchdog/4
root      28    2     0      0     smpboot_th 0000000000 S migration/4
root      29    2     0      0     smpboot_th 0000000000 S ksoftirqd/4
root      31    2     0      0     worker_thr 0000000000 S kworker/4:0H
root      32    2     0      0     smpboot_th 0000000000 S watchdog/5
root      33    2     0      0     smpboot_th 0000000000 S migration/5
root      34    2     0      0     smpboot_th 0000000000 S ksoftirqd/5
root      35    2     0      0     worker_thr 0000000000 S kworker/5:0
root      36    2     0      0     worker_thr 0000000000 S kworker/5:0H
root      37    2     0      0      devtmpfsd 0000000000 S kdevtmpfs
root      38    2     0      0     rescuer_th 0000000000 S netns
root      39    2     0      0     rescuer_th 0000000000 S perf
root      40    2     0      0     console_th 0000000000 S kconsole
root      41    2     0      0       watchdog 0000000000 S khungtaskd
root      42    2     0      0     rescuer_th 0000000000 S writeback
root      43    2     0      0     ksm_scan_t 0000000000 S ksmd
root      44    2     0      0     rescuer_th 0000000000 S crypto
root      45    2     0      0     rescuer_th 0000000000 S bioset
root      46    2     0      0     rescuer_th 0000000000 S kblockd
root      47    2     0      0     worker_thr 0000000000 S kworker/4:1
root      48    2     0      0     rescuer_th 0000000000 S devfreq_wq
root      49    2     0      0     rescuer_th 0000000000 S cfg80211
root      50    2     0      0     cpufreq_in 0000000000 S cfinteractive
root      52    2     0      0     rescuer_th 0000000000 S rpciod
root      68    2     0      0         kswapd 0000000000 S kswapd0
root      69    2     0      0     rescuer_th 0000000000 S vmstat
root      70    2     0      0     fsnotify_m 0000000000 S fsnotify_mark
root      71    2     0      0     rescuer_th 0000000000 S nfsiod
root      72    2     0      0     rescuer_th 0000000000 S cifsiod
root      104   2     0      0     irq_thread 0000000000 S irq/224-rockchi
root      105   2     0      0     irq_thread 0000000000 S irq/225-rockchi
root      106   2     0      0     irq_thread 0000000000 S irq/226-rockchi
root      107   2     0      0     irq_thread 0000000000 S irq/227-rockchi
root      108   2     0      0     irq_thread 0000000000 S irq/228-rockchi
root      109   2     0      0     irq_thread 0000000000 S irq/45-ff670000
root      110   2     0      0     rescuer_th 0000000000 S vcodec
root      111   2     0      0     irq_thread 0000000000 S irq/41-ff650000
root      112   2     0      0     irq_thread 0000000000 S irq/40-ff650000
root      113   2     0      0     rescuer_th 0000000000 S vcodec
root      114   2     0      0     irq_thread 0000000000 S irq/43-ff660000
root      115   2     0      0     rescuer_th 0000000000 S bioset
root      116   2     0      0     rescuer_th 0000000000 S bioset
root      117   2     0      0     rescuer_th 0000000000 S bioset
root      118   2     0      0     rescuer_th 0000000000 S bioset
root      119   2     0      0     rescuer_th 0000000000 S bioset
root      120   2     0      0     rescuer_th 0000000000 S bioset
root      121   2     0      0     rescuer_th 0000000000 S bioset
root      122   2     0      0     rescuer_th 0000000000 S bioset
root      123   2     0      0     rescuer_th 0000000000 S bioset
root      124   2     0      0     rescuer_th 0000000000 S bioset
root      125   2     0      0     rescuer_th 0000000000 S bioset
root      126   2     0      0     rescuer_th 0000000000 S bioset
root      127   2     0      0     rescuer_th 0000000000 S bioset
root      128   2     0      0     rescuer_th 0000000000 S bioset
root      129   2     0      0     rescuer_th 0000000000 S bioset
root      130   2     0      0     rescuer_th 0000000000 S bioset
root      131   2     0      0     rescuer_th 0000000000 S bioset
root      132   2     0      0     rescuer_th 0000000000 S bioset
root      133   2     0      0     rescuer_th 0000000000 S bioset
root      134   2     0      0     rescuer_th 0000000000 S bioset
root      135   2     0      0     rescuer_th 0000000000 S bioset
root      136   2     0      0     rescuer_th 0000000000 S bioset
root      137   2     0      0     rescuer_th 0000000000 S bioset
root      138   2     0      0     rescuer_th 0000000000 S bioset
root      139   2     0      0     rescuer_th 0000000000 S bioset
root      140   2     0      0     rescuer_th 0000000000 S nvme
root      141   2     0      0     kthread_wo 0000000000 S spi1
root      142   2     0      0     kthread_wo 0000000000 S spi2
root      144   2     0      0         msleep 0000000000 D kworker/0:1
root      146   2     0      0     worker_thr 0000000000 S kworker/1:1
root      147   2     0      0     irq_thread 0000000000 S irq/115-rk808
root      148   2     0      0     irq_thread 0000000000 S irq/35-rockchip
root      149   2     0      0     rescuer_th 0000000000 S dm_bufio_cache
root      150   2     0      0     worker_thr 0000000000 S kworker/4:2
root      151   2     0      0     irq_thread 0000000000 S irq/26-mmc1
root      152   2     0      0     rescuer_th 0000000000 S bioset
root      153   2     0      0     worker_thr 0000000000 S kworker/1:2
root      154   2     0      0     mmc_queue_ 0000000000 S mmcqd/0
root      155   2     0      0     rescuer_th 0000000000 S binder
root      156   2     0      0     rescuer_th 0000000000 S ipv6_addrconf
root      157   2     0      0     wait_woken 0000000000 S krfcommd
root      159   2     0      0     irq_thread 0000000000 S irq/46-rga
root      160   2     0      0     worker_thr 0000000000 S kworker/2:1
root      161   2     0      0     rescuer_th 0000000000 S deferwq
root      162   2     0      0     rescuer_th 0000000000 S hpd_queue
root      163   2     0      0     irq_thread 0000000000 S irq/55-ff940000
root      164   2     0      0     rescuer_th 0000000000 S gpu_power_off_w
root      166   2     0      0     worker_thr 0000000000 S kworker/3:1
root      167   2     0      0     worker_thr 0000000000 S kworker/u13:1
root      168   2     0      0     rescuer_th 0000000000 S kbase_job_fault
root      169   2     0      0     worker_thr 0000000000 S kworker/u12:2
root      170   2     0      0     worker_thr 0000000000 R kworker/u12:3
root      172   1     5780   1068  poll_sched 00004ccd90 S /sbin/ueventd
root      174   2     0      0     worker_thr 0000000000 S kworker/4:1H
root      175   2     0      0     worker_thr 0000000000 S kworker/5:1H
root      176   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p10
root      177   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      179   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p9-
root      180   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      184   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p11
root      185   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      189   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p16
root      190   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      192   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p15
root      193   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
logd      194   1     18020  3600  sigsuspend 7379817d4c S /system/bin/logd
root      199   2     0      0     kauditd_th 0000000000 S kauditd
root      203   1     5348   2704  __skb_recv 00eb9b24a8 S /system/bin/debuggerd
root      204   1     10288  3340  __skb_recv 7d6b439b24 S /system/bin/debuggerd64
root      205   1     18148  5976  hrtimer_na 7a06161574 S /system/bin/vold
root      206   204   9904   604   __skb_recv 7d6b43a67c S debuggerd64:signaller
root      208   203   5092   536   __skb_recv 00eb9b36dc S debuggerd:signaller
root      215   2     0      0     worker_thr 0000000000 S kworker/0:1H
root      217   1     6432   932   SyS_epoll_ 000047cc78 S /sbin/healthd
root      219   1     8932   2820  SyS_epoll_ 70e5cf0b84 S /system/bin/lmkd
system    220   1     9156   2312  binder_thr 7a1ad4ec74 S /system/bin/servicemanager
system    221   1     262208 40272 SyS_epoll_ 7f33d6cb84 S /system/bin/surfaceflinger
shell     223   1     7716   2576  wait_woken 7e4bc3d67c S /system/bin/sh
shell     224   1     14144  1036  poll_sched 00004a5c90 S /sbin/adbd
root      227   1     4744   300   __skb_recv 0000410c58 S /system/xbin/su
root      231   1     7716   1792  sigsuspend 795014bd4c S /system/bin/sh
root      233   1     2154796 133704 poll_sched 75d819fca4 S zygote64
root      234   1     1592648 119412 poll_sched 00f0c5b734 S zygote
audioserver 235   1     26404  8932  binder_thr 00efd6d68c S /system/bin/audioserver
drm       236   1     13860  6484  binder_thr 00f290f68c S /system/bin/drmserver
root      237   1     9620   2512  unix_strea 784fd2767c S /system/bin/installd
keystore  238   1     12640  4404  binder_thr 74be3bfc74 S /system/bin/keystore
mediacodec 239   1     33192  9416  binder_thr 00ef20268c S media.codec
media     240   1     38440  11984 binder_thr 00f35f068c S /system/bin/mediadrmserver
mediaex   241   1     45224  9992  binder_thr 00e73b168c S media.extractor
media     242   1     67324  14408 binder_thr 00f092868c S /system/bin/mediaserver
root      243   1     26908  5056  binder_thr 7a1ed36c74 S /system/bin/netd
root      244   1     10436  3792  poll_sched 7f11debcbc S /system/vendor/bin/crashlogd
root      246   1     10188  1936  devkmsg_re 728b6a167c S /vendor/bin/log-watch
system    247   1     12328  4300  binder_thr 7432e06c74 S /system/bin/gatekeeperd
root      248   1     8272   2040  hrtimer_na 7d57a7c574 S /system/xbin/perfprofd
root      252   231   10100  4108  poll_sched 77df44acbc S /system/bin/sshd
root      253   1     7716   2548  sigsuspend 7d2c42ed4c S /system/bin/sh
root      262   253   9096   1768  __skb_recv 71da75d6dc S /system/vendor/bin/logcatext
root      279   2     0      0     worker_thr 0000000000 S kworker/3:1H
root      291   2     0      0     rescuer_th 0000000000 S kbase_event
root      549   2     0      0     worker_thr 0000000000 S kworker/2:1H
root      550   2     0      0     worker_thr 0000000000 S kworker/u13:2
system    559   233   2201276 205720 SyS_epoll_ 75d819fb84 S system_server
root      592   2     0      0     worker_thr 0000000000 S kworker/1:1H
root      636   2     0      0     rescuer_th 0000000000 S kbase_event
u0_a15    651   233   1787376 161492 SyS_epoll_ 75d819fb84 S com.android.systemui
system    665   233   1779444 111424 SyS_epoll_ 75d819fb84 S com.android.settings
root      683   2     0      0     rescuer_th 0000000000 S rtw_workqueue
root      687   2     0      0     rescuer_th 0000000000 S kbase_event
media_rw  732   205   0      0        do_exit 0000000000 Z sdcard
root      776   2     0      0     down_inter 0000000000 S RTW_CMD_THREAD
root      779   2     0      0     worker_thr 0000000000 S kworker/0:2
wifi      822   1     14312  7112  poll_sched 7d811decbc S /system/bin/wpa_supplicant
root      932   2     0      0     rescuer_th 0000000000 S kbase_event
u0_a5     961   233   1572436 73564 SyS_epoll_ 75d819fb84 S android.ext.services
system    994   233   1577156 80032 SyS_epoll_ 75d819fb84 S android.rockchip.update.service
system    1009  233   1575600 73236 SyS_epoll_ 75d819fb84 S com.android.keychain
system    1024  233   1776148 140528 SyS_epoll_ 75d819fb84 S com.rigol.launcher
u0_a27    1049  233   1577600 75652 SyS_epoll_ 75d819fb84 S com.android.printspooler
u0_a4     1067  233   1584764 93480 SyS_epoll_ 75d819fb84 S android.process.media
root      1131  2     0      0     rescuer_th 0000000000 S kbase_event
root      1146  2     0      0     worker_thr 0000000000 S kworker/3:2
u0_a7     1156  233   1572632 73624 SyS_epoll_ 75d819fb84 S com.android.managedprovisioning
system    1174  233   1592948 96572 SyS_epoll_ 75d819fb84 S com.rigol.launcher:Watchdog
system    1188  233   1630248 105276 SyS_epoll_ 75d819fb84 S com.rigol.webcontrol
root      1295  2     0      0     worker_thr 0000000000 S kworker/5:2
system    1329  1024  4744   308      do_wait 0000411078 S su
system    1331  1329  4744   140   unix_strea 0000410f70 S su
root      1333  1     4744   140      do_wait 0000411078 S /system/xbin/su
root      1334  1333  4744   148      do_wait 0000411078 S /system/xbin/su
root      1335  1334  7716   2644   pipe_wait 799ae1767c S sh
root      1398  2     0      0     worker_thr 0000000000 S kworker/5:1
root      1407  2     0      0     worker_thr 0000000000 S kworker/1:0
system    1408  233   1689076 116656 hrtimer_na 75d81a0574 S com.rigol.scope
root      1430  2     0      0     worker_thr 0000000000 S kworker/u13:0
root      1431  2     0      0     worker_thr 0000000000 R kworker/u12:0
shell     1433  224   7716   2684  sigsuspend 7490cc4d4c S /system/bin/sh
root      1436  1433  4744   304      do_wait 0000411078 S su
root      1437  1436  6808   140   wait_woken 0000410f70 S su
root      1439  1     4744   140      do_wait 0000411078 S /system/xbin/su
root      1442  1439  4744   148      do_wait 0000411078 S /system/xbin/su
root      1443  1442  7716   2596  sigsuspend 74ae5d4d4c S sh
root      1454  1443  9116   2440           0 751294e67c R ps
rk3399_rigol:/ #


IMHO timezone was unrelated. See logs with logcat or dmesg.

adb root
adb shell
logcat | more

Offline mwb1100

  • Frequent Contributor
  • **
  • Posts: 720
  • Country: us
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3288 on: January 14, 2025, 08:00:25 pm »
the adb logcat >logcat.txt command will save the output to the logcat.txt file in the current directory. Run this command, wait 3-5 seconds, interrupt it with Ctrl+C. Nothing is displayed on the screen, everything is written to the file.

Should be able to use the "-d" option to have logcat dump current contents of the log then exit.  That way you don't need to do the "wait 3-5 seconds, interrupt it with Ctrl+C" dance.

Code: [Select]
adb logcat -d >logcat.txt

Maybe when editing the script is saved with damage? Like the added UTF-8 header, or replacing \r with \r\n ?

I'll bet you're right about the \r\n - all to easy to do when editing on Windows, and surprising how confused many linux applications are by it.
 
The following users thanked this post: TurboTom, AndyBig

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3289 on: January 14, 2025, 08:07:33 pm »
I'll bet you're right about the \r\n - all to easy to do when editing on Windows, and surprising how confused many linux applications are by it.

I think bash doesn't care about line endings. However Im not using Windows (Linux only) for about 20 years, so maybe something was changed.

Offline shapirus

  • Super Contributor
  • ***
  • Posts: 1813
  • Country: ua
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3290 on: January 14, 2025, 08:10:51 pm »
In my case I obviously edited it where the line endings can only be \n, but I don't remember if I used adb to pull/push the boot script. That might be what affected it in some way.

If I ever try this again, I'll pay more attention: md5sum before/after, checking diff, etc.

p.s. as far as I recall, I found literally nothing in the logs. Hope TurboTom has more luck.
« Last Edit: January 14, 2025, 08:15:31 pm by shapirus »
 
The following users thanked this post: TurboTom

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3291 on: January 14, 2025, 08:19:39 pm »
There is also Rigol logs dir: /data/logs/tools_log/

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1492
  • Country: de
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3292 on: January 14, 2025, 08:40:11 pm »
I pulled the logcat output (attached to this message), and as it seems, the watchdog tries to restart the scope app several times without success, outputting something like this:

"ContextImpl: Calling a method in the system process without a qualified user:" ...which may actually be the case  ;)

But seriously, could that possibly be related to disabling the signature verification in order to be able to install the patched scope app? Strange thing is that it worked very well before I tried to change the time zone. I made sure that nothing else except Asia/Shanghai -> Europe/Berlin got changed, no CR to CR/LF or whatever mess-up. I also tried putting back the original "rigol/shell/start_rigol_app.sh" from the .GEL firmware update file.

Anyway, thanks a lot for the input so far. If all "repair" attempts fail, I can still write back the SD card image. But I'ld rather understand what caused the trouble...

Cheers,
Thomas
 

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3293 on: January 14, 2025, 08:43:38 pm »
Failure that You never experienced before is a very good reason to learn something new.

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3294 on: January 14, 2025, 08:48:11 pm »
This is strange...

Quote
01-18 16:50:32.588   560   560 W PackageManager: Failed to parse /system/app/Sparrow: Package com.rigol.scope at /system/app/Sparrow ignored: updated version 1008000 better than this 1008000
01-18 16:50:32.713   560   560 W PackageManager: Failed to parse /system/app/Webcontrol: Package com.rigol.webcontrol at /system/app/Webcontrol ignored: updated version 1 better than this 1

But later it's being executed and...

Quote
01-15 04:14:24.194  1101  1101 E [RIGOL.SCOPE]: [drv_panel.c][DrvPanel_GetHardwareGpioVerion][368]:GPIO SYS FD ERROR

This is strange, like something with DT (Device Tree - which is not in filesystem but on the beginning of SD card) or maybe related with modules.

Please give me output of lsmod and dmesg.

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1492
  • Country: de
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3295 on: January 14, 2025, 08:56:13 pm »
Here they are:

Code: [Select]
rk3399_rigol:/ # lsmod
Module                  Size  Used by
8188eu               2016009  0

Output of dmesg is attached as a text file.
 

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3296 on: January 14, 2025, 08:56:18 pm »
Also try this (as root):

echo 148 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio148/direction
echo 1 > /sys/class/gpio/gpio148/value

cat /sys/class/gpio/gpio148/value
cat /sys/kernel/debug/gpio

Pin 148 is not used by this scope (I did huge reverse engineering with my scope).

Offline norbert.kiszka

  • Frequent Contributor
  • **
  • Posts: 623
  • Country: pl
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3297 on: January 14, 2025, 08:59:10 pm »
Here they are:

Code: [Select]
rk3399_rigol:/ # lsmod
Module                  Size  Used by
8188eu               2016009  0

Output of dmesg is attached as a text file.

Forget what I said before. You don't have modules loaded by start_rigol_app.sh (insmod something.ko).

Maybe it doesn't have execution permission.

To check it: ls -l /rigol/shell/start_rigol_app.sh

To fix it: chmod a+x /rigol/shell/start_rigol_app.sh

Offline AndyBig

  • Frequent Contributor
  • **
  • Posts: 539
  • Country: ru
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3298 on: January 14, 2025, 08:59:42 pm »
In my case I obviously edited it where the line endings can only be \n, but I don't remember if I used adb to pull/push the boot script. That might be what affected it in some way.

If I ever try this again, I'll pay more attention: md5sum before/after, checking diff, etc.

p.s. as far as I recall, I found literally nothing in the logs. Hope TurboTom has more luck.
It is also possible that the script file loses its attributes after editing.
I just tried to remove the "executable" attributes from the startup script (chmod 666) and the oscilloscope application stopped starting. Everything is like with Shapirus and TurboTom - just a splash screen and nothing happens. I did not find anything related to this script in the logcat and terminal logs via com port.
After restoring the "executable" attributes (chmod 777) everything worked.
 
The following users thanked this post: TurboTom

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1492
  • Country: de
Re: Hacking the Rigol DHO800/900 Scope
« Reply #3299 on: January 14, 2025, 09:01:00 pm »
Maybe something related to this message ?

Code: [Select]
[    2.193746] e2fsck: Superblock last mount time is in the future.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf