Skip to content

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

Pre-release
Pre-release

Choose a tag to compare

@dekajoule dekajoule released this 21 Nov 19:21
· 58 commits to main since this release

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

  • Bring-up, clock step: it asked for GPIO1_C4 as the clock chip's reset and stopped with "Resource busy". That
    line is the screen panel's reset (as on the DHO800/900), held by the panel driver. The stock clock driver uses only
    chip select, clock, data and sysref_reset. The bring-up and the device tree no longer name or touch GPIO1_C4.

Verified on a unit (mho-dev-3, MHO98): the clock table is read, and WLAN starts right after the boot.
Not yet verified on hardware: this fix, and every bring-up step after power.

File What
oos-mho900-dev-4.img the OOS image, for the install on a second card (boot/card-install.py)
oos-mho900-dev-4.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-4 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.