Skip to content

Conversation

@pamaury
Copy link
Contributor

@pamaury pamaury commented Dec 4, 2025

Backport #26143

@pamaury pamaury requested review from a team as code owners December 4, 2025 17:29
@pamaury pamaury requested review from AlexJones0, alees24, cfrantz, jwnrt and timothytrippel and removed request for a team, alees24, cfrantz and timothytrippel December 4, 2025 17:29
This updates the individualization firmware to enable patching a single
AST config CSR based on an address and value stored in flash info page 0.
This is activated by a CLI arg `--patch-ast` passed to the orchestrator
script.

Signed-off-by: Tim Trippel <[email protected]>
(cherry picked from commit 2d89b9a)
Copy link
Contributor

@AlexJones0 AlexJones0 left a comment

Choose a reason for hiding this comment

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

LGTM - I'm assuming from context that we no longer disable the OTP runtime checks because we can give this patch for environments that would fail them? Or maybe it was just stale? The lack of an original comment on this makes it a bit hard to understand.

I've left one comment on the original code, feel free to address or delay if convenient for backporting efforts.

parser.add_argument(
"--patch-ast",
action="store_true",
default=False,
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: (on original PR, not backport code) - You don't need default=False for an argparse argument with action="store_true". See the docs:

'store_true' and 'store_false' - These are special cases of 'store_const' that respectively store the values True and False with default values of False and True:

Looking at the orchestrator, it seems like this is repeated for many fields here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I created an issue based on this comment.

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