Occasional ContributorHow effective is the video Frame Buffer core when storing in memory?
The Video and Image Processing (VIP) Suite IP has a Video Frame Buffer (VFB) core, named Frame Buffer II IP Core, that can take streaming images on the Avalon-ST IF and save it into memory using Avalon-MM IF, for using a DDR3 memory controller.
In my application, the VFB Frame Buffer II IP Core has these interfaces:
- Streaming video: Avalon-ST IF width 48 bits (for 2 pixels in parallel of each 24 bits)
- Memory interface: Avalon-MM IF width 64 bit
Since the memory bandwidth is critical, I want to determine the expected amount of overhead, but I am unable to find any information about this in the "Video and Image Processing Suite User Guide (UG-VIPSUITE | 2021.02.12)".
So, how effectively does the VFB Frame Buffer II IP Core pack the 48-bit Avalon-ST IF data into the memory using the 64-bit Avalon-MM IF ? For example, is the 48 bit Avalon-ST data packed back-to-back in memory, or is the 48-bit Avalon-ST data aligned to the 64-bit Avalon-MM data size, thereby introducing an overhead of 33 %.
The information is in document ""Video and Image Processing Suite User Guide (UG-VIPSUITE | 2021.02.12)" section "16.7.3. Memory Map for Frame Reader or Writer Configurations" paragraph "The frame data is tightly packed into memory and aligned on frame (or field) boundaries to minimize storage usage and maximize memory bandwidth usage."
So the data is tightly packed in memory.
