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
with this approach if start address is big enough final address may exeed width of signal in the interfaces, which leads to a simulation failure
Also, can you please give a comment on why "cycles" is necessary? For example, i can see simulations, where burst == FIXED, and then this request is divided into a number of cycles, all with different addresses
The text was updated successfully, but these errors were encountered:
That's a good point, I should add a check to read() that checks that address + length is in range and throws an exception in that case. Good point about FIXED, I think that should generate multiple operations against the same address, I'll fix that. And I suppose that also means the length check should be ignored for the FIXED burst type.
TBH, I don't think I have any tests for anything other than INCR, so there may be some issues here and there with FIXED and WRAP.
"cycles" is simply a computation of how many transfer cycles are required to execute the requested transfer based on the starting address and length.
cocotbext-axi/cocotbext/axi/axil_master.py
Line 503 in e21b9ff
with this approach if start address is big enough final address may exeed width of signal in the interfaces, which leads to a simulation failure
Also, can you please give a comment on why "cycles" is necessary? For example, i can see simulations, where burst == FIXED, and then this request is divided into a number of cycles, all with different addresses
The text was updated successfully, but these errors were encountered: