Repository navigation
OOS 0.1.2
Third version of OOS, an open operating system for the Rigol DHO800/DHO900.
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.
Updating
From 0.1.1: install oos-0.1.2.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: a cold start no longer stops at "ADC data lanes" when the sync bit stays the same over the whole sweep while the ADC answers. It goes on like any sweep without a falling edge, and the checks after the eye scan decide.
- USB stick install: dry run, first install over the stock
recoveryand the run again have run on a DHO924S. - For other boards (nothing changes on the DHO800/DHO900): the board is kept apart from the rest.
oos_hal::dhoholds it, the GUI reaches the hardware only throughboard::Board,hal::targetandrootfs/board/<name>describe a board, andrcSasks the board what to start. Channels, generators, memory depths and couplings come from the board. See docs/porting.md.
Full list: CHANGELOG.md.
Files
| File | What |
|---|---|
oos-0.1.2.img |
boot image, for the second-card install in the README |
oos-0.1.2.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 (README, docs/install-usb.md); 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
The same code, apart from the version number, was installed on the DHO924S through the kexec path and passed a power-on with the new start-up scripts (all stages, trial confirmed). This exact package passed the signature check, the kernel load and a dry run of the install on the unit; it has not been started there. The register sequences of the acquisitions are the same as in 0.1.0 (tools/plan-matrix.sh). The USB stick install ran with package 0.1.1 on a unit whose stock system is a modified one.
Not run on the unit for this version: the generator tests of tools/device-test.py.
Known: under a long run of random settings over WLAN, the SCPI server can stop answering for more than 30 s and then come back. It also happens with 0.1.1 (1 of 4 runs, against 2 to 3 of 4 with this build, too few to compare). The scope stays up.