Development build for testing on an MHO900. Not a release. mho-acq-1, fourth try. Not yet verified on
hardware.
What mho-dev-12 showed on two MHO98 (issues #4, #491):
the read-out works, but every lane holds a flat line, and the four front ends answer their status read with
0x0000ff where the stock system reads 0x0440ff. They answer, but are not in their working state. What they most
likely miss is the set-up the stock program gives them when it starts, which no recording so far contains.
mho-check.pyversion 10,--afe-init(attached, and in the source of this tag): under the stock system it
restarts the stock scope program while it records the front ends' bus, and writesmho-afe-init-<model>-<date>.txt.
The screen goes dark for about half a minute; the program's settings stay.- This build sets the front ends up from that file (
/oos/mho-afe-init.txt) before the snapshot's words, and
the diagnostics also read the front end's registers back.
Your snapshot stays valid. The steps are in issue #4.
| File | What |
|---|---|
mho-check.py
| the check tool, version 10 |
oos-mho900-dev-13.img
| the OOS image, for the install on a second card (boot/card-install.py, then boot/switch.py oos)
|
oos-mho900-dev-13.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-13 (build 20261122-174019) with kernel/build-base.sh (the kernel of mho-dev-10) and OOS_BOARD=mho boot/build-dev-image.sh, Linux 6.12.115. Sources: this tag, and the third-party sources of v0.1.14.