You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2020. It is now read-only.
Currently the way the arbiter is organized can cause the payload of AXI beats (address, data, etc.) to change after the valid signals has been asserted. This violates the AXI4 standard. Rework the arbiter such that it holds on to its decision until the request is cleared. This should be easily doable by having the round-robin flag jump to the selected master.
The text was updated successfully, but these errors were encountered:
Currently the way the arbiter is organized can cause the payload of AXI beats (address, data, etc.) to change after the
valid
signals has been asserted. This violates the AXI4 standard. Rework the arbiter such that it holds on to its decision until the request is cleared. This should be easily doable by having the round-robin flag jump to the selected master.The text was updated successfully, but these errors were encountered: