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

[fpga] Add timestamp for bitstream identification via USR_ACCESS reg #5279

Merged
merged 1 commit into from
Feb 19, 2021

Conversation

vogelpi
Copy link
Contributor

@vogelpi vogelpi commented Feb 18, 2021

This PR modifies the bitstream generation to add a timestamp in the USR_ACCESS register for later identification. This is useful to find out which bitstream is currently loaded on a running FPGA.

We would primarily use this feature for the SCA setup but it doesn't hurt to enable it also for non-SCA targets. This is related to lowRISC/ot-sca#39.

This commit modifies the bitstream generation to add a timestamp
in the USR_ACCESS register for later identification. This is useful to
find out which bitstream is currently loaded on a running FPGA.

Signed-off-by: Pirmin Vogel <vogelpi@lowrisc.org>
@vogelpi
Copy link
Contributor Author

vogelpi commented Feb 18, 2021

@alphan I successfully tested that the hook works and the setting gets the right value. However, I didn't test that the register can actually be read with the ChipWhisperer API. Since you've been playing around with that, it would be great if you could try it out.

@alphan
Copy link
Contributor

alphan commented Feb 18, 2021

Thanks @vogelpi, I'll let you know when I have a chance to try this change.

Copy link
Contributor

@imphil imphil left a comment

Choose a reason for hiding this comment

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

Can't hurt either way, so let's get this in.

@vogelpi
Copy link
Contributor Author

vogelpi commented Feb 19, 2021

Okay, thanks @imphil for the approval. I am merging this then. I don't expect a problem with the CW API, but if we find something it won't be a problem to alter this.

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.

None yet

3 participants