Skip to content

fix: Drive usage_o low if not supported - #357

Open
gbellocchi wants to merge 1 commit into
masterfrom
gb/fix-unknown-usage-stream-fifo
Open

fix: Drive usage_o low if not supported#357
gbellocchi wants to merge 1 commit into
masterfrom
gb/fix-unknown-usage-stream-fifo

Conversation

@gbellocchi

Copy link
Copy Markdown

Problem
This PR includes a solution for issue #356. The cc_stream_fifo_optimal_wrap originally assigned an unknown state to usage_o when Depth == 32'd2. This issue was first found when running Spyglass checks into the snitch_cluster (PR #330).

Solution
This fix simply defines the signal state and drives it low if not supported. The specific value of usage_o should not be problematic in this case since the port is generally not connected when instantiated at a higher hierachy.

The `cc_stream_fifo_optimal_wrap` originally assigned an unknown state to `usage_o` when `Depth == 32'd2`. This fix simply defines the signal state and drives it low if not supported. The specific value of `usage_o` should not be problematic in this case since the port is generally not connected when instantiated at a higher hierachy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant