Skip to content

fix: multiboot always uses the other Keira slot - #39

Closed
black-ghost-off wants to merge 2 commits into
mainfrom
yboichuk/feat/multiboot_guest_slot
Closed

black-ghost-off wants to merge 2 commits into
mainfrom
yboichuk/feat/multiboot_guest_slot

Conversation

@black-ghost-off

@black-ghost-off black-ghost-off commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Summary

MultiBoot picked its guest slot with esp_ota_get_next_update_partition(). That only works with the stock two-slot table (app0/app1).

The new lilka-bootloader layout keeps Retro-Go next to Keira, so the table has 9 OTA apps. If Keira runs from app1 (after an OTA update), the "next" partition is Retro-Go's launcher, and multiboot would overwrite it.

Now the guest slot is the other one of app0/app1. If neither exists, it falls back to the next OTA partition as before. Nothing changes for the stock layout.

Testing

  • Builds as part of Keira (pio run -e v2).
  • Tested on Lilka v2 with the lilka-bootloader layout: Keira boots from app0 and reports OTA partition: app1.

Related Keira PR: lilka-dev/keira#151.

🤖 Generated with Claude Code

With more OTA apps in the partition table (e.g. Retro-Go next to Keira in the
lilka-bootloader layout) esp_ota_get_next_update_partition() from app1 returns
an app that isn't Keira's. Pick app0/app1 explicitly and fall back to the next
OTA partition for other layouts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@frostmorn

Copy link
Copy Markdown
Collaborator

this problem already solved via making a retrogo sliced onto pieces, so I might not push that one

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