Adding CV32E40Pv2 Design issues list #668
Merged
+0
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Pascal Gouedo <pascal.gouedo@dolphin.fr>
MikeOpenHWGroup
approved these changes
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @mike
Here is the file listing ALL v1.8.0 design issues, either documentation, simulation, lint/coding/style or formal verification, created after cv32e40p_v1.0.0 tag end of 2020.
It is mentioning their status and there are still 4 opened in cv32e40p repo.
2 are about lint warnings and RTL coding style that I think could be closed.
1 is about Hardware Loops single-stepping using a real physical debugger connection. No way to reproduce and maybe only concerning openocd or PULP debug modules problems. I don't know how to manage this one wrt the "freeze".
Last one (612) is a question about potential RTL problem. But as cv32e40p_prefetch_controller is fully covered without any waiver, this is either not visible performance problem or not a valid comment/question?
Thanks to help to decide about those opened issues.
Regards,
Pascal.