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
A bit of circuitry has been added to AxiTop that allows 1 instance to be reset without taking down the whole AXI bus. But this only works for reads. It also stops instances from reading ahead much further after it finishes.
The reason this does not works for writes yet is that it is more complex (the circuit will need to keep track of an active bursts, so that it will generate the exact number of data beats that is expected due to the original write request), and because the design already waits for all the writes to finish before the done flag is asserted (and the software normally waits for the done flag before resetting). However, if an instance was improperly configured or gets stuck for some other reason, we still want to be able to reset it (although note that you can always reset the entire design).
The text was updated successfully, but these errors were encountered:
A bit of circuitry has been added to AxiTop that allows 1 instance to be reset without taking down the whole AXI bus. But this only works for reads. It also stops instances from reading ahead much further after it finishes.
The reason this does not works for writes yet is that it is more complex (the circuit will need to keep track of an active bursts, so that it will generate the exact number of data beats that is expected due to the original write request), and because the design already waits for all the writes to finish before the
done
flag is asserted (and the software normally waits for the done flag before resetting). However, if an instance was improperly configured or gets stuck for some other reason, we still want to be able to reset it (although note that you can always reset the entire design).The text was updated successfully, but these errors were encountered: