Skip to content

device/tegu MODEM-PLAN: G3-A, the automatic chip select boot - #179

Merged
derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:tegu-g3a-record
Oct 30, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:tegu-g3a-record

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

The one DTB round the plan set out when GNSS was parked ran this morning: gn3 plus the autocs and fb0 overlays from linux-omarchy-mobile#137, 8-bit words at stock's 3.07 MHz, attended on the charger. The modem came up, the 12-second session kept every counter at zero (no bad checksums, no hardfault, no UFS error handler), Kepler went CODELOAD to OPERATIONAL, and then gnssd hit the same CHPP permanent failure the plan records for about half the earlier tries; the profile stopped itself and the palmtop was rebooted. So automatic chip select and feedback delay 0 change the checksum picture, not the CHPP outcome. What this round still doesn't reproduce is stock's 32-bit words with the controller's own swap; that is G3-A2, and the section says what has to be built for it (the swap-mode Image exists, the 32-bit gnss_spi variant doesn't). The status line carries the result. One method note: the kit's hands-free guard refused the push, so the kit's packed images went through the repository's own bin/omamobile push from a scratch checkout carrying the kit's descriptor.

Docs only; tools/pr-check passes; no identifiers.

One DTB round on 2026-10-30 with the autocs and fb0 overlays at stock's clock and 8-bit words: the modem up, the session clean on every counter, Kepler to OPERATIONAL and then the same CHPP permanent failure as before, without a bad checksum this time. G3-A2 (32-bit words with the controller's swap) is the boot left to build; the status line says so.
@derekross
derekross merged commit 29bc2b6 into derekross:main Oct 30, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Thank you, a clean record of the round the plan set out: zero bad checksums, then the same CHPP failure, which narrows it to word size. I see 070d4d97f on kernel #137 now; if that's the 32-bit variant, "written, not built yet" would keep the next step exact in a later update. Merged.

derekross pushed a commit that referenced this pull request Nov 1, 2026
… tree (#265)

Stage 0 for the Pixel 6a (bluejay, gs101): the device descriptor and
notes, every value sourced from Google's GPL bluejay device tree at
android-16.0.0_r0.9 (board id 0x20506, rev 0x10000, A0/B0 soc_id, the
S6E3FC3 panel at 1080x2400). The descriptor carries no register write
and no probe. Images wait for the board DTS in linux-omarchy-mobile#179.

Maintainer edits at merge: link kernel #179, describe the board-id rule
in plain words, and drop a source line that backs no value.

Closes #265

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 2, 2026
…not yet booted (#319)

Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ss#179)

One DTB round on 2026-10-30 with the autocs and fb0 overlays at stock's clock and 8-bit words: the modem up, the session clean on every counter, Kepler to OPERATIONAL and then the same CHPP permanent failure as before, without a bad checksum this time. G3-A2 (32-bit words with the controller's swap) is the boot left to build; the status line says so.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… tree (derekross#265)

Stage 0 for the Pixel 6a (bluejay, gs101): the device descriptor and
notes, every value sourced from Google's GPL bluejay device tree at
android-16.0.0_r0.9 (board id 0x20506, rev 0x10000, A0/B0 soc_id, the
S6E3FC3 panel at 1080x2400). The descriptor carries no register write
and no probe. Images wait for the board DTS in linux-omarchy-mobile#179.

Maintainer edits at merge: link kernel derekross#179, describe the board-id rule
in plain words, and drop a source line that backs no value.

Closes derekross#265

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants