Development build for testing on an MHO900. Not a release. It's built for the testers in #4 and #248, after
mho-dev-1 started on an MHO98 and an MHO934.
Still no acquisition and the demo signal on screen. New in this build
(docs/mho.md):
- Front panel, listened to: oos-ui reads UART0 with the DHO's frames. Keys with the DHO's codes work, and every
frame goes to/tmp/oos-panel.log. OOS sends nothing to the panel.oos-panel(over SSH) shows the log, and when
you ask it to, sends a version query, "UI loaded", or all LEDs on/off. - WLAN: the RTL8821CU stick that comes with the MHO900 gets the
rtw88driver and its firmware. - Model: the vendor.bin keys are also searched in the stock package's compressed libraries. If the search still
finds nothing, System info says what it searched. Setting the model by hand:echo "model = MHO98" > /oos/limits.conf. - Bring-up, step 1, by hand only:
oos-fpgad bringup --hw-code 3 --yesswitches on the acquisition board's
supplies the way the stock system does. It reads the clock chip's ID and, if that's right, writes the unit's own
clock table. It loads the unit's own FPGA image, starts PCIe and reads the first FPGA registers. All of it is
volatile: a power-off undoes it. Nothing is written to a flash or partition. Nothing runs it on its own.
Not yet verified on hardware: everything new above. The platform part of mho-dev-1 ran on two units.
| File | What |
|---|---|
oos-mho900-dev-2.img
| the OOS image, for the install on a second card (boot/card-install.py)
|
oos-mho900-dev-2.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-2 (branch oos-mho) with kernel/build-base.sh and OOS_BOARD=mho boot/build-dev-image.sh, Linux 6.12.115 (config: CONFIG_RTW88_8821CU=m added). 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 new firmware files come from
linux-firmware unchanged, with their licence in the image.