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

pre-release40 minutes ago

Development build for testing on an MHO900. Not a release. It's mho-dev-5
with one new, read-only bring-up step. Still no acquisition and the demo signal on screen.

  • Bring-up, new step adc (now the last step, run by default): through the FPGA's SPI bridge it reads the ADC
    clock count and registers 0x00 to 0x0f of both ADCs, and prints each raw word and whether the bridge marked it
    valid. Nothing is written to an ADC. It answers whether the two ADCs answer behind the FPGA.

Verified on a unit (mho-dev-5, MHO98, #4): every step up to pcie: the clock chip takes its table, the FPGA takes
the unit's image (DONE high), PCIe trains at 5.0 GT/s x4, xdma binds the endpoint, and the FPGA version reads as under
the stock system.
Not yet verified on hardware: the adc step.

On a unit that runs mho-dev-5 there is no need to install this: copy oos-fpgad to /tmp and run
/tmp/oos-fpgad bringup --hw-code 3 --yes (it is gone at the next power-off).

File What
oos-mho900-dev-6.img the OOS image, for the install on a second card (boot/card-install.py)
oos-mho900-dev-6.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)
oos-fpgad the bring-up tool of this build alone, for a unit already on mho-dev-5 (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-6 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.

Don't miss a new oos release

NewReleases is sending notifications on new releases.