Skip to content
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

get address for DICE artifacts from config #731

Open
flihp opened this issue Aug 24, 2022 · 2 comments
Open

get address for DICE artifacts from config #731

flihp opened this issue Aug 24, 2022 · 2 comments
Assignees
Labels
trust quorum Enablement for trust quorum (probably sprockets related)
Milestone

Comments

@flihp
Copy link
Contributor

flihp commented Aug 24, 2022

Our prototype currently hard codes these addresses in the source code. Getting them from the chip.toml at build time would be better. At first look doing so would require adding some plumbing to xtask. The data we would need is in the 'chip' key from the top level toml table but AFAIK the currently available methods for getting at the app toml exposed to tasks at build time aren't sufficient:

  • build_util::config exposes the app config that includes tables under [config]:
    pub fn config<T: DeserializeOwned>() -> Result<T> {
  • build_util::task_config exposes tables under the [task_name] table:
    pub fn task_config<T: DeserializeOwned>() -> Result<T> {
@flihp flihp self-assigned this Aug 24, 2022
@flihp flihp added the trust quorum Enablement for trust quorum (probably sprockets related) label Aug 29, 2022
@cbiffle
Copy link
Collaborator

cbiffle commented Apr 27, 2023

It seems like there are symbols being generated by the build system that can give you the address of this area. Is this still a thing?

@cbiffle cbiffle added this to the Unscheduled milestone Apr 27, 2023
@flihp
Copy link
Contributor Author

flihp commented May 8, 2023

This work has fallen behind other tasks and I haven't thought much about it beyond the initial comment. AFAIK this is mostly a plumbing exercise to surface the required data at build time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
trust quorum Enablement for trust quorum (probably sprockets related)
Projects
None yet
Development

No branches or pull requests

2 participants