Skip to content

oakMOSS v0.5.0-beta.1

Choose a tag to compare

@CatalyticArkun CatalyticArkun released this 10 Oct 01:39
· 113 commits to main since this release

oakMOSS v0.5.0-beta.1

System card (SD1) images for three MagicX handhelds. This beta installs updates without a reflash, can run spruceOS from the system card itself, and keeps a debug record of every boot when you ask it to.

Downloads

Device Image
MagicX Mini Zero 28 oakmoss-zero28-v0.5.0-beta.1-sd1.img.xz
MagicX Zero 40 oakmoss-zero40-v0.5.0-beta.1-sd1.img.xz
XU RETRO / MagicX XU20 V32 oakmoss-xu20-v0.5.0-beta.1-sd1.img.xz

Before you start

  • Back up your stock system card. A full image of it is the only way back to stock.
  • Use spruceOS v4.5.0 or a newer nightly. It goes on a second card, formatted FAT32 (exFAT won't mount), or on the system card (see below).
  • Your spruceOS card is not changed: games and saves stay on it.
  • Coming from v0.4.2-beta.1 or older, write the image once. This is the first release with two system slots; later releases can then update it in place.

Install

  1. Write the image to the system card with Raspberry Pi Imager or a similar tool (in Imager: "Use custom", then pick the .img.xz). Leave verification on. The image replaces the oakMOSS system on the card.
  2. Once the card is ejected, put it straight into the device. On Windows, don't plug it back into the PC first: Windows can rewrite the card's partition table so it no longer boots. If that happens, write it again.
  3. The system card goes in the slot your stock system card came from, and the spruceOS card in the other slot.
  4. Power on. The first boot takes a few seconds longer: it adds a SPRUCEOS partition in the rest of the system card.

What's new

  • Updates without a reflash. The system card now has two slots. An oakmoss-<device>-<version>.omupd file at the root of either card installs into the other slot on the next boot, with the charger in or the battery at 30 % or more. If the new slot does not start, the device goes back to the old one by itself.
  • spruceOS on the system card. The first boot adds a SPRUCEOS partition in the free space of the system card. Boot the card in the device once, put it in a PC, and copy spruceOS onto that drive: the device then runs without a second card. When both cards carry spruceOS, the second card's runs; the system card's runs when the second card has none. The other card is mounted at /media/sdcard1, where spruceOS lists its games next to the main card's.
  • No frontend screens. With no spruceOS on either card, the device shows "No frontend detected, charging" on the charger and "No frontend, power off in 10s" without it.
  • Debug mode. An empty file named oakmoss-debug at the root of the SPRUCEOS drive makes the device record every boot and shutdown on the card, with the kernel's progress marks. It is off without the file. See docs/debugging.md.
  • Zero 40: the boot picture stays on screen until the menu. The black screen of 1-2 seconds after the boot picture is gone.
  • The case LED's blue light stays off while the device runs, on all three devices. Red still shows charging. (Stock firmware lights the blue.)
  • Cleaner power-off: the shutdown steps run one at a time, so the cards are unmounted before the power goes.
  • spruceOS's update check no longer offers an installed nightly again (BusyBox tr character classes).
  • Newer libraries: zlib 1.3.1 replaces 1.2.8, and OpenSSL 1.1.1w replaces 1.1.0i.

Known limitations

  • When spruceOS runs from the system card, its USB storage mode shares the second card instead. Fixed in spruceOS (PR #1804): nightlies newer than 4.5.3-20261009.3 carry it.
  • Debug mode: when spruceOS runs from the system card, the full records are not written to it, only the summary in Saves/spruce/oakmoss-debug.log. Fixed in v0.5.0-beta.2.
  • Zero 40: going to sleep takes about 4 seconds.
  • Beta: tested on one unit of each device.

Updates

The oakmoss-<device>-v0.5.0-beta.1.omupd files update a system card that already has two slots, which only images from this release on have. Put one at the root of either card and restart. These also carry the bootloader and device tree, which changed in this release.

Checksums

sha256sum -c SHA256SUMS checks the downloads. Each *-BUILD-INFO.txt lists exactly what went into its image.

SHA-256 of the decompressed images
5347d81512f625ad8efc462e714d586158eb73f55e7a562fd0657095036d9106  oakmoss-zero28-v0.5.0-beta.1-sd1.img
1d19ed360c3526781d2d1426fbf2885bb4cd5ae3d3f1038eb650fc9b482230de  oakmoss-zero40-v0.5.0-beta.1-sd1.img
a564e37cb107523fe6c51e128ed85680f93bd818cb7763dea581dba7b6ddd406  oakmoss-xu20-v0.5.0-beta.1-sd1.img