Repository navigation
MHO900 test build 14: capture-all and recipes (development build)
Pre-releaseDevelopment build for testing on an MHO900. Not a release. mho-acq-1 with a workflow that needs fewer round
trips. Not yet verified on hardware.
One recording under the stock system covers everything: mho-check.py version 11, --capture-all, records the
stock system's cold start of the acquisition board (FPGA and drivers reloaded with the stock tools, the program
started again, as at power-on): the front ends' whole set-up and every ADC register write in order (watched with
mho-poll, read only), then it takes the snapshot.
Later tries need no new image: oos-mho-live now runs
- the capture by itself, when
/oos/mho-capture.txtis there, - a recipe from
/oos/mho-recipe.txt: a text file with the steps of the start, so a different order or variant
is one copied file, - a newer
oos-fpgadfrom/oos/bin/oos-fpgad: one copied program instead of an install.
The steps are in issue #4.
| File | What |
|---|---|
mho-check.py |
the check tool, version 11 (also in the source of this tag) |
mho-poll |
the watcher --capture-all pushes to the scope (aarch64, static, read only); keep it next to mho-check.py |
oos-mho900-dev-14.img |
the OOS image, for the install on a second card (boot/card-install.py, then boot/switch.py oos) |
oos-mho900-dev-14.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 |
this build's oos-fpgad alone, for /oos/bin/oos-fpgad on a scope with mho-dev-13 |
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-14 (build 20261122-180425) 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.