New Contributor
Regular ContributorHello,
I don't think it possible to fix this issue with device that you have. Our FPGA devices have different pins available so I will advice you to check your design so it can fit with your FPGA device. You could also try different FPGA devices to fit with your design.
I hope this answer helps. Stay safe!
New ContributorDo any Intel FPGAs support 1400+ user I/O pins? I imagine probably not, seeing as how the Arria 10 1150 (which is not small) has significantly less than that at only 624.
I don't think the problem is that the device has insufficient pins, but rather that a large majority of the 1417 ports "requiring" an I/O pin don't actually need to be seen outside of the FPGA as input or output. A RISC-V core certainly shouldn't need 1400 physical I/O connections.
So my question is more along the lines of, how can I parse the ports identified as I/O down to those which actually need to reach outside of the chip? Assuming I am able to identify these truly necessary I/Os in the design, how do I tell Quartus to ignore the others? Are there any compilation tricks for this or do I need a higher-level wrapper with just the essentials? (The design came with a wrapper as the top-level entity, but this induces the 1400 I/O ports, most of which I believe should not be physical I/Os.)
Super ContributorLook at the top-level HDL code and/or the Pin Planner (Assignments menu) All Pins list to see all the top-level I/O required for the design. Quartus would not add any additional pins to the design unless you edit the code.
Regular ContributorHello,
Unfortunately there is no trick to add more pins on Quartus. We have many FPGA lineups that may fit your design.
New ContributorAdding more pins is not at all the route I was aiming for; however, if you would like to point me to an Intel FPGA with 1417+ user I/O pins available I would be interested to hear it.
This RISC-V core from Western Digital was demonstrated on an Artix 7 FPGA, so my assumption is that it could fit on an Arria 10 and that it doesn't actually require 1417 I/O pins. I guess their top-level wrapper needs a higher level wrapper istelf. Or perhaps their compilation flow has some way of excluding a subset of ports from needing to reach physical I/O.
Any example of a RISC-V soft core operating on an Arria 10 would be extremely helpful.
