Skip to content

MHO900 platform test build 7 (development build, no acquisition)

Pre-release
Pre-release

Choose a tag to compare

@dekajoule dekajoule released this 22 Nov 00:15
· 70 commits to main since this release

Development build for testing on an MHO900. Not a release. It's mho-dev-6
with the front panel's LEDs driven. Still no acquisition and the demo signal on screen.

  • Front panel LEDs: oos-ui now sets the LEDs as on the DHO800/900 (Run/Stop, Single, channels, ...). On an MHO934
    (#248) the keys and knobs send the DHO's codes and the LED frames switch all LEDs, so the protocol is the same;
    which LED lights for which state on the MHO900 is what this build lets you check. No power command goes to the panel.
  • tools/mho-check.py version 7 (in the source of this tag) also reads the ADC clock count 0x1210 under the
    stock system.

Verified on units (mho-dev-6, an MHO98 #4 and an MHO934 #248): the bring-up gets through every step: clock, FPGA
image, PCIe (5.0 GT/s x4), the FPGA's registers, and both ADCs answer all reads behind the FPGA's bridge.
Not yet verified on hardware: the LED assignment on the MHO900.

File What
oos-mho900-dev-7.img the OOS image, for the install on a second card (boot/card-install.py)
oos-mho900-dev-7.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-7 with kernel/build-base.sh and OOS_BOARD=mho boot/build-dev-image.sh, Linux 6.12.115,
the same kernel and device tree as mho-dev-5. 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.