The Fragment and Interleave Parameters tab is shown below.
Figure 1. Fragment and Interleave Parameters
- FRAGMENT_SIZE_BYTES
- Specifies the burst fragment size in bytes. If the number of bytes to be transferred in a transaction is greater than the burst fragment size, the AXI transaction is split into multiple burst fragments of a consistent size to allow easier reordering.
- MEM_INTERLEAVE_TYPE
- Memory interleaving allows transactions from a single master to
be spread across multiple HBM pseudo-channels to distribute the memory load:
- none – No pseudo-channel interleaving.
- per memory – Consecutive burst fragments are written to consecutive HBM pseudo channels.
- MEM_COUNT
- This is the number of pseudo-channels to interleave across.
Memory Interleave Example
Take a case where four AXI Masters need to access 512 MB and the 512 MB corresponds to 2 HBM pseudo-channels. It can be more advantageous to use four HBM pseudo-channels in this case to have twice the memory bandwidth for the four masters. In order to do this, MEM_INTERLEAVE_TYPE = per_memory would be selected with MEM_COUNT = 4. The 512 MB would be composed of 128 MB from each HBM pseudo-channel with access alternating/striped across the pseudo-channels on a burst fragment basis.