Skip to content

OOS 0.1.3

Choose a tag to compare

@deckerjulian deckerjulian released this 09 Nov 20:29
· 550 commits to main since this release

Fourth version of OOS, an open operating system for the Rigol DHO800/DHO900. A bug-fix release.

Experimental. It has only run on one DHO924S. Read the disclaimer, the status and the known limits first. Measurements are not calibrated to any standard.

Installing and updating

No build needed: Installation.

From 0.1.1 or 0.1.2: install oos-0.1.3.oosupd through http://<scope>:8080/update. The scope restarts into the new build by itself (kexec) and installs it from there. Then switch it off at the mains, wait 30 seconds and switch it on: that start is the trial. From 0.1.0 the install is direct, followed by the same power-cycle.

What changed

  • Fix: with deep memory and many edges that seldom reach the 10 % and 90 % levels, the rise and fall time search held the main thread for half a minute: no picture, no SCPI, no web. The search now stops at the neighbouring edges. Only an edge whose levels do not occur between its neighbours drops out of the mean.
  • tools/device-test.py: the time base test waits long enough for a record at 50 ms/div.

Full list: CHANGELOG.md.

Files

File What
oos-0.1.3.img boot image, for the second-card install in the README
oos-0.1.3.oosupd update package for a running OOS, signed with the maintainer key (id 4dbd03d9763869dd), which every build trusts
DHO800_DHO900_OOS_Install.GEL install from a USB stick through the stock system's Storage > Upgrade, without opening the scope; keep its name
SHA256SUMS checksums
linux-6.12.115-base.tar.xz kernel source, needed to build the kernel: put it into kernel/src/
busybox_1.37.0*, e2fsprogs-1.47.2.tar.xz, wpa_supplicant-2.11.tar.gz sources of the other programs in the image

State

On the DHO924S the fix ran in RAM on top of 0.1.2: the random-settings test that stalled about every second time passed 8 of 8 runs over WLAN. This exact package has not run on the unit. The start-up code is that of 0.1.2, whose code passed a power-on there. Host tests pass, the USB install passes its simulation on a card file, and the register sequences of the acquisitions are the same as in 0.1.2 (tools/plan-matrix.sh).

Not run on the unit for this version or 0.1.2: the generator tests of tools/device-test.py.