github dekajoule/oos mho-dev-12
MHO900 test build 12: mho-acq-1 with diagnostics (development build)

latest releases: mho-dev-15, mho-dev-14, mho-dev-13...
pre-releaseone hour ago

Development build for testing on an MHO900. Not a release. mho-acq-1, third try, with diagnostics. Not yet
verified on hardware.

On hp197's MHO98 mho-dev-11 ran the whole start for the
first time: bring-up, ADCs, link, FPGA, front end, an acquisition that completed, and a frame read from the board.
The frame held real samples but no signal (a flat line at -9 mV). This build tries the next suspects in the same run,
each with one acquisition, and reports what each one saw:

  • the front ends' status read on all four channels (do they answer?),
  • every FSM channel mask, and all four channels at once (is the signal on another lane?),
  • 0x1004 written again (two of its bits did not read back),
  • the ADC registers that did not read back written once more.

The last line is RESULT: IT MEASURES ... if the first acquisition or any variant held the square wave.

Your snapshot from mho-check.py version 9 stays valid. Install this build as you did dev-11, then run
oos-mho-live again with the probe compensation signal on the snapshot's channel. The steps are in issue #4.

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

Don't miss a new oos release

NewReleases is sending notifications on new releases.