Repository navigation
Signing target 9: xip (code the pod runs from its W25Q) - #86
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Firmware 4.0.2+ builds
blob-xip.bintogether 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-blobsalready 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 addsTargetXIPand the name.Found on hardware (benchpod-c2f662, an XIP_RAM dev build): with this change the CLI reports
xip signature: okand sends it.Tests
go test ./internal/fwsign/: target 9 maps both ways, the unused numbers have no name.🤖 Generated with Claude Code