github dekajoule/oos mho-dev-3
MHO900 platform test build 3 (development build, no acquisition)

pre-releaseone hour ago

Development build for testing on an MHO900. Not a release. It's mho-dev-2
with two fixes from the first run of mho-dev-2 on an MHO98 (#4). Still no acquisition and the demo signal on screen.

  • Bring-up, clock step: the units' clock table starts with a labelled line (R0 (INIT), a tab, the word), which
    stopped oos-fpgad bringup before it touched the clock chip. It's read now, and each line's register number must
    match its word, so a wrong table still stops the step.
  • WLAN: the driver of the stick loaded only after 60 s, because the WLAN script waited for an acquisition
    start-up the MHO900 doesn't have yet. It loads right after the boot now.

Not yet verified on hardware: both fixes, and every bring-up step after power. The platform ran on two units
(mho-dev-1), mho-dev-2 on one, and the bring-up's power step ran on an MHO98.

File What
oos-mho900-dev-3.img the OOS image, for the install on a second card (boot/card-install.py)
oos-mho900-dev-3.oosupd the same image as a signed package, for the install over ADB (oos-update gel-install)
oos-update the install tool of this build, for the scope (aarch64)
MHO900_OOS_Install.GEL the stick install. Not known whether the stock MHO900 update accepts it. Use the ADB or card route
SHA256SUMS checksums

Built from tag mho-dev-3 with kernel/build-base.sh and OOS_BOARD=mho boot/build-dev-image.sh, Linux 6.12.115,
the same kernel configuration as mho-dev-2. Sources: this tag, and the third-party sources of
v0.1.14 (rootfs/deps.lock and the kernel base are the same),
which also holds linux-6.12.115-base.tar.xz.

The instructions are in the issues: #4 and #248.

Don't miss a new oos release

NewReleases is sending notifications on new releases.