Skip to content

Initial Build system - #16

Merged
pamaury merged 3 commits into
lowRISC:mainfrom
pamaury:build_system
Sep 9, 2026
Merged

Initial Build system#16
pamaury merged 3 commits into
lowRISC:mainfrom
pamaury:build_system

Conversation

@pamaury

@pamaury pamaury commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

This is a adapted version of #6 to the new infrastructure. We should have merged this ages ago but apparently we forgot it during the release flow creation. Also include a change due to lowRISC/opentitan#30887

@AlexJones0 AlexJones0 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this seems good to me - but with the caveat that I am not familiar with the ot-sku code.

For the final commit, maybe you should instead merge / pull in #15?

Comment thread REPO.bazel Outdated
Comment thread skus/open/rom_ext/BUILD Outdated
":signed",
],
ecdsa_key = {
"//open/keys/root:keyset": "ot00-earlgrey-a2-root-ecdsa-prod-0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: this is hardcoding the SKU which was generic in skus/open/perso/BUILD: is there a reason we know this must be ot00, or is it worth keeping this generic?

(repeated below for the SPHINCS+ key)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I copied the commit from Chris but I agree that this is not ideal. In fact we ideally shouldn't even set the sku at all and instead have one target per sku? @cfrantz what do you think?

Comment thread skus/shared/repo/BUILD.bazel Outdated
Comment thread extension.bzl
Comment thread skus/open/rom_ext/BUILD

package(default_visibility = ["//visibility:public"])

SKU = "ot00"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have currently duplicated the approach of perso but I think we should generalize this. I am proposing to postpone this to an issue.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, this is fine to merge as is and can easily be extended upon in an issue / a separate PR after further discussion.

pamaury and others added 3 commits September 8, 2026 16:08
Create the initial bazel targets for build and release of
personalization binaries and ROM_EXT binaries.

This PR depends on opentitan#30146.
Addresses #5.

Signed-off-by: Chris Frantz <cfrantz@google.com>
Signed-off-by: Amaury Pouly <amaury.pouly@gmail.com>

@AlexJones0 AlexJones0 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, though I'm not sure if the FPGA test CI failures warrant some further investigation before we can merge.

@pamaury

pamaury commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator Author

There was a failure due to a download, I rerun them (https://github.com/lowRISC/opentitan/actions/runs/34236431239/job/102102157219) and the result seems better. I will merge, we can investigate specific failures later to see if they need further fixing.

@pamaury
pamaury merged commit a022d80 into lowRISC:main Sep 9, 2026
2 of 4 checks passed
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.

3 participants