Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Spartan 6 MPMC - more ports?
27 views
Skip to first unread message
Oliver Mattos
Jan 20, 2012, 5:05:41 PM1/20/12
to
Hi,
I have a Spartan 6 project with 7 IP cores wanting VFBC connections to a memory controller. My problem is the MPMC configuration tool won't seem to let me do that because the MPMC can't be configured to have that many VFBC connections.
I'm trying to build a picture-in-picture device for HDMI (6 inputs, 1 output).
Is there a way to "chain" memory controllers to achieve this? Alternatively is there a VFBC bus "splitter/arbitrator" to allow me to connect multiple VFBC IO cores to a single MPMC port? I am reasonably certain memory bandwidth will be OK, providing arbitration/buffering is ok.
(I am a bit new to Xilinx EDA tools, and am probably a bit off topic for this group - please be kind!)
I have a Spartan 6 project with 7 IP cores wanting VFBC connections to a memory controller. My problem is the MPMC configuration tool won't seem to let me do that because the MPMC can't be configured to have that many VFBC connections.
I'm trying to build a picture-in-picture device for HDMI (6 inputs, 1 output).
Is there a way to "chain" memory controllers to achieve this? Alternatively is there a VFBC bus "splitter/arbitrator" to allow me to connect multiple VFBC IO cores to a single MPMC port? I am reasonably certain memory bandwidth will be OK, providing arbitration/buffering is ok.
(I am a bit new to Xilinx EDA tools, and am probably a bit off topic for this group - please be kind!)
Christopher Head
Jan 26, 2012, 2:55:00 AM1/26/12
to
On Fri, 20 Jan 2012 14:05:41 -0800 (PST)
Oliver Mattos <oma...@gmail.com> wrote:
> (I am a bit new to Xilinx EDA tools, and am probably a bit off topic
> for this group - please be kind!)
You may get better results in comp.arch.fpga as this group is more
Oliver Mattos <oma...@gmail.com> wrote:
> (I am a bit new to Xilinx EDA tools, and am probably a bit off topic
> for this group - please be kind!)
intended for language discussions rather than vendor-specific hardware
primitives.
Chris
0 new messages