Skip to content

[ate] enable (un)packing seed objects into perso TLV blobs #221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 17, 2025

Conversation

timothytrippel
Copy link
Collaborator

There are two different seed objects (dev seed and generic seed) that need to be unpacked/packed into perso blobs during provisioning. This adds support for the latter.

After lowRISC/opentitan#27423, there are two
seed types that can be exported from the DUT during personalization:
1. "dev_seed", which is a seed that has a particular data format:
https://github.com/lowRISC/opentitan/blob/c4214fe7dfeb5ea3e203d14620bd4af87c451ba3/sw/device/silicon_creator/manuf/base/perso_tlv_data.h#L59
and,
2. a "generic" seed.

Both seed types can be represented in the TLV perso blob structure with
a simple header that contains the size and type (dev seed or generic),
followed by the data bytes.

This simplifies the ATE DLL to be able to represent both seed types with
the same `seed_t` object type.

Signed-off-by: Tim Trippel <[email protected]>
The perso blobs that are RXed/TXed from/to the device during
personalization are a maximum size of 5120 (5k) bytes. However, the
perso blob that is sent from the test program to the registry may be up
to 8192 (8k) bytes.

Signed-off-by: Tim Trippel <[email protected]>
There are two different seed objects (dev seed and generic seed) that
need to be unpacked/packed into perso blobs during provisioning. This
adds support for the latter.

Signed-off-by: Tim Trippel <[email protected]>
@timothytrippel timothytrippel merged commit 7211b9f into lowRISC:main Jun 17, 2025
4 checks passed
@timothytrippel timothytrippel deleted the generic-seed-parsing branch June 17, 2025 01:26
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.

2 participants