Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
21615 Discussions

Pin for EPCS16 are not displayed

Altera_Forum
Honored Contributor II
‎10-14-2008 08:10 AM
1,275 Views

Hi @ All,  

 

I want to load my Cyclone II FPGA from an EPCS16. In File > Convert Programming File, I generated the programming file.  

In the programmer, I can see the EPCS16, too, as shown in the screen shot below. 

 

But when I open the Assignment editor, the according pins for the EPCS are not shown.  

 

Why aren't they shown and what do I have to do to set them? Does anybody have an idea? 

 

Thanks!
Preview file
45 KB
0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎10-14-2008 10:16 AM
564 Views

Remember, you are programming an image into the EPCS16 (Which is essentially a FLASH device). The image is loaded from the EPCS16 into your Cyclone part at powerup/configuration time. 

 

Why do you need to see pin information about the EPCS16 in the assignment editor? The assignment editor is used to setup pins etc within the target Cyclone device.
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎10-14-2008 11:01 AM
564 Views

:rolleyes: So you mean, that Quartus makes the pin connection automatically and doesn't show them in the Assignment Editor? 

 

Ok, makes sense.  

Thanks a lot for your answer!
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.