Repository navigation
Installation
This guide is the short way through. The exact commands and every option are in the README.
There are two ways, both with the files of the latest release, so you do not have to build anything:
-
From a USB stick, with
DHO800_DHO900_OOS_Install.GEL: the scope stays closed, OOS goes on the card that is inside, beside stock. -
On a second card, with
oos-<version>.img: you open the scope, your original card stays untouched in a drawer.
A scope that already runs OOS is updated with oos-<version>.oosupd: see Updates and Going Back.
You need a FAT32 USB stick with at least 200 MiB free.
- Download
DHO800_DHO900_OOS_Install.GELandSHA256SUMSfrom the latest release. Compare the checksum:shasum -a 256 DHO800_DHO900_OOS_Install.GELon macOS,sha256sumon Linux,certutil -hashfile DHO800_DHO900_OOS_Install.GEL SHA256on Windows. It has to match the file's line inSHA256SUMS. - Copy the file to the top folder of the stick and keep its name, the scope looks for it. Next to it, create an empty file
oos-dry-run.txt: the first run then only checks and saves a rescue set. - Start the stock system and put the stick into the front port. If Storage does not show the stick, switch off and on and look again.
-
Storage > Upgrade, choose the file (about 16 MB; a small file starting with
._comes from macOS, leave it) and start. It takes about a minute, and the screen says at the end whether it worked. - Read
oos-install.logon the stick on a computer. It ends withexit code 0. - Delete
oos-dry-run.txtand run the update again. The log now ends withOOS selected for the next power-onandexit code 0. - Copy the folder
OOS-rescuefrom the stick to a computer and keep it: it holds your calibration and the stockrecovery. - Switch off at the mains, wait 30 seconds and switch on. OOS starts. Go on with First Steps.
OOS starts once: the power-on after it starts stock again. To stay on OOS, set System > Boot mode to Persist.
This ran on a DHO924S whose stock system is a modified one; an unmodified stock system has not run it yet, and only the DHO924S is accepted. A kernel that hangs before the first script would need the card taken out: read docs/install-usb.md first.
You will open the scope, which voids the warranty. The boot SD card is inside. Your original card stays untouched in a drawer: OOS only ever goes on a second card.
- A DHO800/DHO900. Only the DHO924S has been tested.
- A second SD card, best of the same size or larger, and a card reader. A smaller card works too, see step 2.
- A computer with macOS. Linux works with
ddbut is untested. - This repository:
git clone https://github.com/deckerjulian/oos.git
-
Back up the original card. Take it out and make an image with
tools/sdcard-clone.sh. Keep the image in two places, then put the card away. -
Write the clone to the second card. From here on you only use this card. Cards of the same nominal size differ by a few MB; if
writesays the image is larger than the card, make a copy that fits and write that one. Only the stock/datapartition at the end gets smaller, the original image is only read:tools/sdcard-clone.sh fit ~/oos-backup/sd-original.img diskM ~/oos-backup/sd-fit.img tools/sdcard-clone.sh write ~/oos-backup/sd-fit.img diskM
On Linux, give the card's size in bytes instead of
diskM(lsblk -bdno SIZE /dev/sdX) and write withdd. -
Get the image. Either download
oos-0.1.4.imgfrom the release and check it againstSHA256SUMS, or build it yourself: Building, on macOS or Linux, also on an x86-64 PC. -
Install OOS on the second card. Do the dry run first, it only prints the plan:
diskutil unmountDisk /dev/diskM sudo python3 boot/card-install.py install /dev/rdiskM --image oos-0.1.4.img --fallback-stock
If the plan looks right, add
--execute. The tool refuses cards without the stock layout. -
Select OOS for the next start:
sudo python3 boot/switch.py oos /dev/rdiskM --execute sudo python3 boot/switch.py show /dev/rdiskM
-
Put the card into the scope, close it, connect Ethernet and switch on. Go on with First Steps.
The stock software has to stay on the card: OOS reads the scope's identity with its help.
The README also describes an install over ADB, which needs a modified stock system and a build of your own.