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

CVA6 Pulp Platform issue #2489

Open
dvusingh opened this issue Sep 3, 2024 · 2 comments
Open

CVA6 Pulp Platform issue #2489

dvusingh opened this issue Sep 3, 2024 · 2 comments
Labels
notCV32A65X It is not an CV32A65X issue

Comments

@dvusingh
Copy link

dvusingh commented Sep 3, 2024

Hi,

I am working on the cva6 verification.
There I found that some of the rtl files present under the cva6/vendor/pulp_platform/axi & cva6/vendor/pulp_platform/common_cells are old in comparison to the github pulp-platform area shown below:
https://github.com/pulp-platform/axi
https://github.com/pulp-platform/common_cells/tree/master/src

If I will replace the older cva6/vendor/pulp_platform with updated files present in github pulp-platform and run the cva6 simulations,
So, does its affect the functionality of the cva6 core.

I want some clarification on this to procced effectively to understand the cva6 design implementation.
Any information would be really appreciated.

Thanks

@niwis
Copy link
Contributor

niwis commented Sep 3, 2024

Hello @dvusingh, pulp platform projects generally follow semantic versioning, meaning that minor releases (e.g. v1.2.0 -> v1.3.0) should be fully backwards-compatible. However, pulp-platform/axi is still pre-release (v0.x.y), so functional/interface changes are possible. Upgrading dependencies is usually not a big deal, but it's always a good idea to run regression tests afterward, as they should catch any functional changes.

@dvusingh
Copy link
Author

Hi,

I ran benchmark test case, I don't see any issues with updated pulp_platform files.

Thanks

@JeanRochCoulon JeanRochCoulon added the notCV32A65X It is not an CV32A65X issue label Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notCV32A65X It is not an CV32A65X issue
Projects
None yet
Development

No branches or pull requests

3 participants