Skip to content

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

Pre-release
Pre-release

Choose a tag to compare

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

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

  • Bring-up, FPGA step: it stopped at "/dev/spidev5.0: No such file or directory". The FPGA's SPI port (the SoC's
    spi5) had no fixed number in the device tree, so the kernel named it /dev/spidev2.0. The device tree now gives it
    the stock name /dev/spidev5.0. If the port is missing anyway, the bring-up lists the spidevs there and the
    controller of each (spi5 is ff200000.spi).

Verified on a unit (mho-dev-4, MHO98): the bring-up gets through power and clock (the clock chip reads vendor
ID 0x51 0x04 before and after its 136 words), and in the fpga step PROGRAM_B and INIT_B answer.
Not yet verified on hardware: this fix, the image sent to the FPGA, and every step after it.

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