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

Help with EPCS1 compressed data

Altera_Forum
Honored Contributor II
‎06-03-2010 04:14 AM
1,140 Views

Hi, 

 

I would like to save money and use the EPCS1 as my configuration device. I compiled my code and I noticed that the size of the pof file was 131272 bytes. I am targeting an EPCS1 device in the project settings and quartus completed the compilation with no problems (with compression turned on). How can I find out what the actual size of the POF file is. It doesn't make sense to me that my pof file (with a size of 131272 bytes) can fit into the EPCS1 since its its 1.04MBit device, and my POF file is 1.05MBits. 

 

Can anyone shed any light on this? 

 

Thanks
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎06-03-2010 09:14 AM
385 Views

did you get the pof size from the windows? the pof file actually contains some header and footer information that is why it seems larger than the actual EPCS size. However these information won't be programmed into the EPCS. Besides, if the data exceeds the actual flash size, the Quartus convert programming file won't allow the generation of the pof file.

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.