Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address boundary #19

Closed
rodrigomelo9 opened this issue Jan 29, 2024 · 1 comment
Closed

Address boundary #19

rodrigomelo9 opened this issue Jan 29, 2024 · 1 comment

Comments

@rodrigomelo9
Copy link
Owner

AHB

The minimum address space that can be allocated to a single Subordinate is 1KB, and the start and the end of the
address region must exist on a 1KB boundary. All Managers are designed so that they do not perform incrementing
transfers over a 1KB address boundary. This ensures that a burst never crosses an address decode boundary.

AXI

The maximum size of a transaction is 4KB and transactions are not permitted to cross a 4KB boundary. However,
many Managers generate transactions which are guaranteed to be smaller than this.
A Subordinate or interconnect might benefit from this information. For example, a Subordinate might be able to
optimize away some decode logic. An interconnect striping at a granule smaller than 4KB might be able to avoid
burst splitting if it knows that transactions will not cross the stripe boundary.

@rodrigomelo9
Copy link
Owner Author

A burst must not cross a 4KB address boundary.

Note This prohibition prevents a burst from crossing a boundary between two Subordinates. It also limits the number of
address increments that a Subordinate must support.

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

No branches or pull requests

1 participant