Skip to content

Signing target 9: xip (code the pod runs from its W25Q) - #86

Merged
wardviaene merged 1 commit into
mainfrom
xip-blob
Nov 21, 2026
Merged

wardviaene merged 1 commit into
mainfrom
xip-blob

Conversation

@wardviaene

Copy link
Copy Markdown
Member

What

Firmware 4.0.2+ builds blob-xip.bin together with the firmware: rarely used code (the USB flash protocols, coming) that runs straight from the pod's W25Q flash (embeddedci-com/benchpod-firmware#218 and the XIP session PR after it). Release CI signs it as target 9 (8 stays the Wi-Fi bridge's identity certificate).

install-blobs already installs whatever the manifest lists and the pod reports a slot for, but it did not know target 9, so it sent the blob without its signature and the pod refused it (signature: none). This adds TargetXIP and the name.

Found on hardware (benchpod-c2f662, an XIP_RAM dev build): with this change the CLI reports xip signature: ok and sends it.

Tests

go test ./internal/fwsign/: target 9 maps both ways, the unused numbers have no name.

🤖 Generated with Claude Code

Firmware 4.0.2+ builds blob-xip.bin with the firmware (code that runs straight
from the W25Q) and signs it as target 9; 8 stays the Wi-Fi bridge's identity.
Without the name, install-blobs sent the blob without its signature and the pod
refused it ("signature: none"). TargetXIP and the name, plus a test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wardviaene
wardviaene merged commit 5ff2872 into main Nov 21, 2026
2 checks passed
@wardviaene
wardviaene deleted the xip-blob branch November 21, 2026 04:15
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