hw: fix FSM of v0.t fetching - #148
Merged
Merged
Conversation
Navaneeth-KunhiPurayil
approved these changes
Aug 29, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In a case of two masked instructions executed consecutively with the same mask, with a configuration with 4 IPUs, the FSM of v0.t fetching misbehaves: the v0_t_read_done flag goes low too late, which, in the case of long vectors, triggers the wrong calculation of vl_q.
So, to fix it, change the signal vfu_rsp_valid_o to signal last_request that makes the flag low.
Since the issue shows up only when 4 IPUs are used, the 4 IPU config is added.