Skip to content

fix(rynk): report locked bootloader jumps - #954

Closed
HaoboGu wants to merge 1 commit into
feat/rynk_protocolfrom
agent/pr848-bootloader-lock-status
Closed

fix(rynk): report locked bootloader jumps#954
HaoboGu wants to merge 1 commit into
feat/rynk_protocolfrom
agent/pr848-bootloader-lock-status

Conversation

@HaoboGu

@HaoboGu HaoboGu commented Jul 15, 2026

Copy link
Copy Markdown
Collaborator

What

Check the device lock state before sending the fire-and-forget bootloader jump, and return Rejected(Locked) when the device is locked.

Why

Locked devices reject bootloader jumps in firmware, but the host API previously returned Ok(()) because it deliberately did not wait for a reply. Default locked configurations therefore reported success without entering the bootloader.

Root cause

A fire-and-forget command cannot distinguish a successful reset from a lock-gate rejection.

Impact

Unlocked jumps gain one lock-status request. The actual jump remains fire-and-forget because a successful device resets before replying.

Checks

  • cargo test bootloader_jump
  • cargo test lock_gate_rejects_and_reports
  • wasm-pack build --target web --dev

Built on #848.

@HaoboGu HaoboGu closed this Jul 15, 2026
@HaoboGu
HaoboGu deleted the agent/pr848-bootloader-lock-status branch July 16, 2026 02:20
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.

1 participant