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.
Some hardware syntheses require driving interfaces with blocking beats part of the time, and non-blocking beats part of the time. However, calling both
Push()
andPushNB()
(or bothPop()
andPopNB()
) on the same interface, even in separate parts of the code to synthesize, causes Catapult HLS to stop with the error "Multiple writers to signal <signal name>".In some cases, it may be possible to call
PushNB()
/PopNB()
inside a loop to implement blocking-like behavior only using the non-blocking function. However, some protocols, such as AXI4-Stream, mandate that "Once <signal> is asserted it must remain asserted until the handshake occurs", so such an implementation would be invalid.PushBOrNB()
andPopBOrNB()
therefore implement a single ModularIO protocol that is able to perform both blocking and non-blocking beats.