Skip to content

← Firmware Downloads

Post-install setup · Reborn (Y2Linux) · Y2

M2-USBSTATE-01 — ready for owner device test

Debian-based Linux with a fast clickwheel interface for the Innioasis Y2.

Instructions published by the project, shown here word for word.

M2-USBSTATE-01 — ready for owner device test

> **Historical record.** The dates, candidate identity, "current" claims, > next steps and permissions below belong to this recorded boundary. See > [current state](../CURRENT_PLATFORM_STATE.md) for the latest physically observed result.

Returned physical photos confirm all 21 reads, zero DMA control words and BEAT 50 without reported errors. The original pending-test handoff below is historical.

2026-09-09, active M2 #28 and USB prerequisite #27/#23. Offline validated; this candidate has not been flashed or hardware tested. The preceding clock-probe photos confirm no errors through BEAT 50, timer IRQ reporting, VUSB and inherited USB clock enables. M1 remains complete; M2 exit remains unqualified.

Candidate

/home/luca/Dokumente/Code/Y2Linux/out/m2-usbstate-01/BOOTIMG.img

1,095,680 bytes; SHA-256: 8c1f701b61a1adb70b1377071e6cb885cda989a422fd75d626cd5c7da5bdb5e7.

Screen/build M2-USBSTATE-01, kernel 6.18.0-y2-m2-usbstate1. Exact read contract.

The first successful sleep is followed by the proven cached PWRAP and clock snapshot, then 21 read-only USB observations if all supply/clock guards hold: MAC POWER/DEVCTL/HWVERS, three interrupt-enable masks, seven digital PHY bytes and eight DMA control words. No new hardware write is added. This neither initializes the controller nor changes clocks, PHY calibration, USB mode, VBUS or DMA ownership. USB enumeration/ttyACM is not expected yet.

Validation

Ignored output retains ELFs, config, input lock, source snapshot, logs, focused disassembly and SHA256SUMS. No repeated unchanged ROM/recovery/source audit or duplicate reproducibility build was performed. No physical-device action occurred.

Owner test and evidence

Use the established BOOTIMG-only test/recovery procedure and **60 seconds maximum from power-on**. Stock preloader/LK, partitions and calibration remain protected. Expected terminal stage is STOP: RESTORE ANDROID at BEAT 50.

Expected: screen/heartbeat, briefly READ USB STATE, then continuing progress. Successful reads show USB RC:0 VALID:001FFFFF, PW:0 /3 CLK:0/15, increasing timer IRQ count and these raw rows:

Raw values are unknown until the trial; neither nonzero DMA nor PHY state should be silently interpreted as failure/success. Only valid-mask bits are evidence: bits 0–5 are POWER/DEV/HW/TXE/RXE/USBE, 6–12 PHY68..6E, 13–20 DMA0..7. On supply/clock guard refusal, rows instead show PERI/MUX/PLL/PWR for diagnosis. USB RC:-19 refuses prerequisites, -16 is a resource conflict, -12 a mapping failure; the heartbeat should continue. A bus hang may freeze at the pre-probe stage; use the existing bounded manual recovery procedure.

Return full-screen photos near BEAT 10 and BEAT 50/STOP, or the exact last visible stage on failure. Include USB RC/VALID, PW/CLK, all four raw rows, timer count, uptime, MemTotal, mount/sleep status and LAST ERR. Also report selected image hash (flashed/readback hash if available from the usual procedure), host elapsed time, USB cable state, any reset/freeze and restoration outcome if done.

Retained prior image: out/m2-usbclk-01/BOOTIMG.img, SHA-256 602080eb199f3a4be30082ee114dfeb97ef414e10d8ad4acf5d239f2096cd6ec. The owner-proven stock/FM restore and M1 fallback boundaries are unchanged. Work stops here for the owner test; #23/#27/#28 remain open and M3 is deferred.

Published by the schulzcode/y2linux project [1] [3]