chip-mainline v1.1 - the download can actually be flashed
v1.0 shipped a rootfs and a kernel but no bootloader, so nothing in it
could be written to a board without reproducing an undocumented U-Boot
build first. The flashing guide also consumed rootfs.ubifs while the
release published rootfs.ubi, and referred to two scripts that were not
in the repository.
This release publishes the whole boot chain, built in CI from a
documented patch series against upstream U-Boot v2022.01, plus a
flashing initramfs and a single-command flasher:
sudo ~/chip-mainline/scripts/flash-release.sh ~/chip-release
It verifies the download, boots a flashing system into the board's RAM
over FEL, writes the rootfs, mounts it to confirm it worked, and only
then writes the boot chain. --diagnose writes nothing at all and reports
which boot stage is broken, for a board that used to boot and stopped.
An earlier v1.1 tag was cut and withdrawn. Its devicetree carried
mainline's dr_mode = "otg" on usb_otg, because the patch series had
never captured the dr_mode = "peripheral" the development tree used.
With "otg" the CDC gadget never binds: no ttyGS0, no usb0, over the same
micro-USB port the board is powered from. That image booted and could
not be reached by any documented route. patches/0003 fixes it; CI now
asserts the property on the built DTB, not only in the source; and the
fix has been confirmed on hardware by booting the released kernel with
the corrected devicetree and watching the gadget enumerate.
The kernel is otherwise unchanged from v1.0 - same configuration, same
compiler, same hash-pinned Debian packages.
Known: no end-to-end flash of a released image onto a board had
completed when this tag was cut. Its components have each been exercised
on hardware; the whole sequence has not.