Fix a bug that causes the core to freeze when enabling CV-X-IF while disabling RVC extension #3168
+10
−8
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.
This is an attempt to fix the bug described in #3167.
It appears that when enabling the CV-X-IF interface while disabling the RVC extension, the core freezes during the initialization phase of the debug sequence in the testbench.
I managed to find out that this was caused by a bug inside the Decode stage: the compressed‑instruction channel driver of the CV-X-IF inside the Decode stage is only generated if the RVC extension is enabled. However, this module still drives signals inside the stage even when RVC is off. I proposed a fix in the PR below, although I am not sure it is the cleanest way to address the issue.